The indicator of throughput kbit/s per TBF is high than that of kbit/s per PDCH. What is the reason?

These indicators are from ALU GPRS Telecom NPO. 1 user has 1 TBF (minimum) but can also have more than 1 TBFs. In ALU, we have MAX_DL_TBF_per_SPDCH, MAX_UL_TBF_per SPDCH and MAX_PDCH_per_TBF. What is the correlation with throughput? The throughput of the PDCH depends on the Coding Schemes. If 2 users are sharing a single PDCH, with 1 user using it 50% of the time at 30kbps and the other user using it 50% of the time at 40kbps. Therefore PDCH Throughput in this case will be 35kbps. Now, 1 user can have for example, 4 PDCHs at 50kbps. In such cases, the TBF throughput is 200kbps. According to 1 TBF/user, then if we set MAX_UL_TBF_per_SPDCH =4, then in 1 PDCH can be used up to 4 users (in high PDCH Utilization at that time). So if user A has 20% of time at rate 30kbps, user B has 30% of time at 40kbps, user C has 30% of time at rate 60kbps, and the last user D has 20% at rate 50kbps, then the PDCH throughput would be: (0.20*30kbps+0.3*40kbps+0.20*50kbps = 46kbps) But for the TBF throughput of each user is: user A has TBF throughput 6kbps, User B 12 kbps, User C 18kbps and user D 10kbps. Then if we set MAX_PDCH_per_TBF =5, it means that 1 user can have PDCH timeslots up to 5 PDCHs. This condition could be reached when there are still many IDLE PDCHs (no high PDCH utilization at that time).Then if the rate is 50kbps at each, then that user can have TBF Throughput 250kbps, but the PDCH only 50kbps. Since The TBF is the group of PDCHs allocated to 1 user and if 2 users are sharing 1 PDCH. Does this mean that in that 1 PDCH, there are 2 TBFs (1 user 1TBF)? Based on ALU Parameters, it means that 1 TBF can have many PDCHs

(MAX_PDCH_per_TBF) and 1 PDCH can have many TBF (MAX_UL_TBF_per_SPDCH). It is correct that 1 TBF can have many PDCHs and 1 PDCH can have many TBFs. Example: User A has 1 TBF w/ 2 PDCH User B has 1 TBF w/2 PDCH User C has 1 TBF w/1 PDCH User D has 1 TBF w/ 1 PDCH On PDCH 1 (=timeslot of the TRX) User A has 20% of time at rate 30kbps, user B has 30% of time at 40kbps, user C has 30% of time at rate 60kbps, and the last user D has 20% at rate 50kbps, then the PDCH throughout would be (0.20*30kbps + 0.3*40kbps + 0.3*60kbps + 0.20*50) = 46kbps On PDCH 2 (=timeslot 2 of the TRX) User A has 40% of the time at rate 30kbps, user B has 60% at rate 40kbps. (0.40*30kbps + 0.6*40kbps) = 36kbps PDCH throughput of PDCH 1= 46kbps PDCH throughput of PDCH 2= 36kbps TBF Throughput of user A = 0.2*30kbps + 0.4*30kbps = 18kbps TBF throughput of user B = 0.9*40 = 36kbps TBF Throughput of user C =0.3*60kbps = 20kbps Notice that one user will get the same max throughput on all of its PDCH. For example user A has a max throughput per PDCH of 30kbps. That depends on the MCS used. If MCS is equal to MCS-4, then it is MCS4 on all the PDCH. The max number of TSs a user can have depends upon the MS Multi-slot Class as well. Now mostly the max TSs that a user can have in one directions is 4 (e.g 4+1 for Multi-slot Class 8) [Excluding Multi-slot class 30-33]. So even if we increase MAX_PDCH_per_TBF

beyond 4 or 5, it will not have any impact on throughput. A site has 1 E1 and a configuration of 4/4/6. So as 1 TRX requires 2 Abis TS so total no of Abis TSs used would be 31 i.e. (14*2 = 28 for data and +3 (or 2) for Signaling). So that means that there is no Extra Abis TSs configured for the site. Now excluding Bonus+Extra Nibbles, we are only left with BASIC Nibbles per cell. In order to achieve MCS9, we need to have around 5GCH (4.49 Abis nibbles). If we consider Cell A (4 TRX): Total Basic Abis nibbles = (4*8) = 32 Max_PDCH_High_load = 4; MS MULTISLOT CLASS 8 (4+1) for all users. So one user using 4 PDCH would require = (4*4.49) = 18Nibbles. So with this calculation, we can have only 1 user using MCS9 simultaneously in the cell. Because we dont have another 18 Abis Nibbles (only 14 left). Why not take into account the bonus nibbles? In a 4/4/6 BTS, you would have 3BCCH+7SDCCH, thats 10 BONUS nibbles. For clarification: Extra and Bonus nibbles are shareable at the BTS Level BASIC nibbles are shareable only within the same cell.

Furthermore, sub-optimal allocations are also possible. The MFS tries to allocate as many PDCH as possible (up to the multi-slot class limit). But if it cant then it shall allocate less. The MS is able to support those sub-optimal configurations. It can even support PDCH configurations with holes (i.e. PDCH1+PDCH2+PDCH4 and TS3 for somebody elses use) On the protocol stack, LLC is between the SGSN and the MS and RLC is between BTS and MS. Ideally, throughput should be measured at the higher layers of the protocol stack (e.g. IP layer). This gives a better indication of the user perception. However, the BSS cannot collect statistics at layers higher than LLC