GSM Training Materials For Special Subjects

GSM Training Materials for Special Subjects
Optimization of PS Radio Parameters

Suitable for staff with P&O skill certificate IV Issued by GSM Product Support Dept.
Confidential
Version Introduction
Version
V1.0 V2.0
Date
2009-06-30 2009-11-13
Writer
Hou Shuai Hou Shuai
Assessor
Zheng Hao Zheng Hao
Translator
Amendment Records
None
Feng Xiaoying Lu Yan Wang Hangyan
Relevant PS parameters of V6.20.100 series are added.
V3.0
2010-01-18
Hou Shuai
Zheng Hao
Feng Xiaoying Lu Yan Wang Hangyan
1 Relevant PS parameters of V6.20.200 series are added; 2 The introduction to PDTCH allocation algorithm based on the idle threshold of TRX is added.
The optimization of ResourceAdjustThs is modified The optimization of Interval number of Packet Downlink/Uplink Ack/Nack, TBF_EST, and T3192/T3193 is modified.
V1.3
2010-03-31
Hou Shuai
Zheng Hao
Feng Xiaoying Lu Yan Wang Hangyan Feng Xiaoying Lu Yan Wang Hangyan
V2.0
2010-07-21
Hou Shuai
Zheng Hao
This material contains information about research & development trend of ZTE Corporation, and is open only to internal employees!
Confidential
Course Objectives
This material classifies radio parameters related to PS service according to functional modules, and describes in detail the following aspects: the principle of parameters, application context of functions, suggestions for network P&O adjustment, and etc. It is hoped that this may be helpful to daily work in network planning and optimization.
Important Statement: Please be informed that functions such as NCCR, PS preemption/queuing, PFC, PBCCH, C31/32, and PS power control, etc. are not mature in development, and therefore will not be described in this PPT!
Contents
Confidential
Chapter 1 Introduction to Coding Mode Adjustment Algorithms Chapter 2 Introduction to Link Quality Control Function Chapter 3 Introduction to UL TBF Access Mode Chapter 4 Introduction to Window in Data Transmission Chapter 5 Introduction to Functions, Timers and Counters Related to TBF Establishment & Release Chapter 6 Introduction to EDA and Algorithms of UL/DL Timeslot Allocation Decision Chapter 7 Introduction to Cell Reselection Algorithms Based on C1 & C2 Chapter 8 Introduction to BVC & MS Flow Control Algorithms Chapter 9 Introduction to DTM & Paging Coordination Function Chapter 10 Introduction to NACC Function Chapter 11 Introduction to Suspend/Resume Functions Chapter 12 Introduction to Functions & Algorithms Influencing PDTCH Planning Chapter 13 Introduction to Parameters of PDTCHTCH Conversion Chapter 14 Introduction to PreemptiveTrans Bit Function Chapter 15 Introduction to CS Move Function Chapter 16 Introduction to Granularity for UL Block Allocation of GPRS Handset Chapter 17 Introduction to Parameters of Maximum UL/DL Users Allowed Chapter 18 Introduction to Relevant Poc Parameters Chapter 19 Quick Search for PS-related Radio Parameters
Introduction to Coding Mode Adjustment Algorithms

Classifications of coding mode Initial coding mode and its dynamic adjustment
Confidential
EGPRS phone quality measure mode

Interval number of Packet Downlink/Uplink Ack/Nack Average filter period for BEP Uplink measure report period
Confidential
Classifications of coding mode

RLC Modulativ Coding modulati Blks/Radi e Mode scheme on o Blk
CS-1 CS-2 GPRS CS-3 CS-4 MCS-1 MCS-2 MCS-3 MCS-4 EGPRS MCS-5 MCS-6 MCS-7 MCS-8 MCS-9 GMSK
FEC Code Rate

0.45
0.65 0.75 1 0.53 0.66 0.85 1 0.38 0.49 0.76 0.92 1
User bit Rate Family bits/20ms (bps)

160
240 288 400 176 224 296 352 448 592 448+448 544+544 592+592
1
1 1 1 1 1 1 1 1 1 2 2 2
8,000
12,000 14,400 20,000 8,800 11,200 14,800 17,600 22,400 29,600 44,800 54,400 59,200
C B A C B A B A A
8-PSK
Confidential
Initial coding mode and its dynamic adjustment

(V6.20.100e and later versions)
Parameter Name Parameter Paramete (CN) Name (EN) r Code

Cn Nn Xn GPRS Cn Nn Xn GPRS phone init coding Cn Nn Xn
Range & Unit

100,%(>) 0 ~ 255 0 ~ 100,%(>) 1*16 kbps CS1CS2 2~4*16 kbpsCS1CS2CS3 CS4 85 20 25
ZTE Default
CS2CS2
GPRS phones init GPRS InitAttachExc code can be Yes/No h_0 changed 116 kbpsMCS1MCS2 216 kbpsMCS1MCS2 MCS3MCS4MCS5 EGPRS Phone 316 kbpsMCS1MCS2 EGPRS Init Coding MCS3MCS4MCS5MCS6 416 kbpsMCS1MCS2 MCS3MCS4MCS5MCS6 MCS7MCS8MCS9 EGPRS phones EGPRS InitAttachExc init code can be Yes/No h_1 changed
Yes
MCS2MCS5 MCS6 MCS6
Yes
Cn and Nn could be set a little higher to improve the stability in raising coding mode when GPRS service is increased.
Confidential
Initial coding mode and its dynamic adjustment (V6.20.100e and later versions)
In versions before V6.20.100e, only the initial coding mode of GPRS and EGPRS is defined, without setting the upper limit. But considering: 1) Regarding signaling TBF, there is no need to use the highest coding scheme, as there are few bits; 2) Some operators request to disable the highest coding scheme. This aims mainly at GPRS. Some operators worry that the PS may not be used as some MSs do not support CS3/4 coding scheme. So, 1) In V6.20.100e, the meanings of GPRSInitAttSelt and EGPRSInitAttSelt are modified. After the modification, each of thes e two parameters contains four bits, which mean: uplink initial coding scheme, downlink initial coding scheme, uplink highest coding scheme, and downlink highest coding scheme respectively. 2)In V6.20.100e, the parameter Highest coding scheme of signal TBF is added (the main function is realized in V6.20.200e) t o limit the using of the highest coding scheme during the process of transmitting uplink signaling (e.g. PDP activation, routing area update, and etc.)
Parameter Name (CN)

TBF
Parameter Name (EN)
Parameter Code
Range & Unit

MCS1 ~ MCS9 0~8 MCS1~MCS9 0~3 CS1~CS4
ZTE Default
MCS6 5,5,8,8 1,1,3,3
Highest coding scheme of signal SigTBFMaxCode TBF EGPRS EGPRS Phone Init EGPRSInitAttSelt Coding GPRS GPRS init attach GPRSInitAttSelt select
Confidential
EGPRS phone quality measure mode

Paramet Paramet Paramet er Name er Name er Code (CN) (EN)
EGPRS EGPRS phone quality measure mode
Range & Unit
ZTE Default
0MEAN_BEP_TNx0-7and I_LEVEL_TN 0-7will not reportedwhich means TBFMEAN_BEP and CV_BEP of TBF will be reported LinkQuam 1only I_LEVEL_TN0-7will be reported 2 eaMode 2only MEAN_BEP_TNx0-7will be reported 3both MEAN_BEP_TNx0-7and I_LEVEL_TN0-7will be reported.
If mode 1, 2 and 3 are adopted, in which the report is made according to timeslot and may be missed in a few terminals, the dynamic adjustment of coding mode may be affected greatly. The measure mode based on MEAN_BEP and CV_BEP is more reasonable. The value 0 indicates reporting in TBF mode. The measurement values reported include C_Value, Mean_BEP, and CB_BEP. To sum up, mode 0 is recommended: report in TBF mode.
Confidential
Interval number of Packet Downlink/Uplink Ack/Nack
Parameter Name (CN)
ZTE Parameter Range & Parameter Name (EN) Defaul Code Unit t
10 10 10 8
Gprs TBFRRBP Interval number of GPRS TBF GPRSDIRrbpInt 3 ~ 20 downlinks RRBP erVal Egprs TBFRRBP Interval number of EGPRS TBF EGPRSDIRrbpI 6 ~ 60 downlinks RRBP nterVal Gprs TBF Interval number of GPRS TBF GPRSUIAckInte 3 ~ 20 uplinks ACK rVal Egprs TBF Interval number of EGPRS TBF EGPRSUIAckInt 3 ~ 20 uplinks ACK erVal
It indicates the time interval used in transmitting Packet Downlink/Uplink Ack/Nack (Block as the unit ) ; If the parameter is set too low, uplink and downlink resource waste may occur; Too high the value may cause delayed confirmation, which will affect speed, even lead to abnormal TBF release; If GPRS window is fixed to 64, it tends to stagnate. But in EDGE service, the window is relatively large, and is related to the timeslot allocated (please refer to Chapter 4 for details). To sum up, higher value should be set for these parameters to improve the retransmission rate on RLC layer.
Confidential
Average filter period for BEP
Parameter Name (CN)
Parameter Parameter Name (EN) Code

BEPperiodUp
Range & Unit

0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13,14, 15
ZTE Defaul t
4
Average filter BEP period for uplink BEP
Average filter BEPperiodDo BEP period for downlink 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10 wn BEP
Defined the forgetting factor e in BEP calculation formula. If the parameter is set higher, it will help to increase the weight of previous reports, and the BEP thus calculated is more reliable; The unit of the parameter is Block. To sum up, it is recommended to set this parameter as about 10.
Confidential
Uplink measure report period
Parameter Name (CN)
Parameter Name (EN)
Parameter Code
Ulmeasureperiod
Range & Unit

400 ~ 2000, ms
ZTE Default
800
Uplink measure report period
It indicates the period BSC needs to process uplink measure report from BTS. It needs to guarantee that coding mode will not change too frequently; It needs also to guarantee the flexibility of the coding mode; To sum up, the default value in system is reasonable.
Contents
Introduction to Link Quality Control Function

Introduction to link quality control method Introduction to IR principles Introduction to MCS selection algorithm based on BEP Introduction to MCS selection algorithm during retransmission under LA function Introduction to MCS selection algorithm during retransmission under IR function Introduction to MCS selection algorithm during retransmission without LA or IR function Cases of LA application Cases of IR application Introduction to conversion algorithm from IR to LA Relevant parameters
Confidential
Confidential
LQC: link quality control
Link adaptation (GPRS, EGPRS)

Link Quality Control Incremental redundancy EGPRS only
Lower performance Lower memory required
Higher performance Higher memory required Soft combining
Confidential
Introduction to IR principles
MCS9 for Example
Initial send
First Retransmission
Second Retransmission
Introduction to selection algorithm of MCS based on Confidential BEP

8PSK_CV_BEP 0 8 P S K M E A N B E P 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 1 2 3 4 5 6 7 0 G M S K M E A N B E P 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 1 2 GMSK_CV_BEP 3 4 5 6 7
MCS_4 MCS_4 MCS_4 MCS_4 MCS_4 MCS_4 MCS_4 MCS_5 MCS_5 MCS_5 MCS_5 MCS_6 MCS_6 MCS_6 MCS_6 MCS_7 MCS_7 MCS_7 MCS_7 MCS_7 MCS_7 MCS_7 MCS_8 MCS_8 MCS_8 MCS_8 MCS_8 MCS_8 MCS_9 MCS_9 MCS_9 MCS_9
There is slight difference between ZTE algorithms and those stipulated in the protocols, which is helpful to the service stability.
Confidential
Introduction to MCS selection algorithm during transmission under LA function

LA
MCS9 Command MCS MCS9 MCS9 MCS8 MCS6 MCS7 MCS6 MCS6 (Pad) MCS7 MCS6 MCS5 MCS4 MCS3 MCS2 MCS1 MCS6 MCS6 MCS6 (Pad) MCS5 MCS6 MCS5 MCS4 MCS3 MCS2 MCS1 MCS5 MCS3 MCS3 (Pad) MCS5 MCS3 MCS5 MCS4 MCS3 MCS2 MCS1 MCS4 MCS3 MCS3 (Pad) MCS2 MCS3 MCS2 MCS4 MCS3 MCS2 MCS1 MCS3 MCS3 MCS3 (Pad) MCS2 MCS3 MCS2 MCS1 MCS3 MCS2 MCS1 MCS2 MCS3 MCS3 (Pad) MCS2 MCS3 MCS2 MCS1 MCS3 MCS2 MCS1 MCS1 MCS3 MCS3 (Pad) MCS2 MCS3 MCS2 MCS1 MCS3 MCS2 MCS1
MCS8
MCS7 Last MCS MCS6 MCS5 MCS4 MCS3 MCS2 MCS1
MCS8
MCS7 MCS6 MCS5 MCS4 MCS3 MCS2 MCS1
MCS8
MCS7 MCS6 MCS5 MCS4 MCS3 MCS2 MCS1
Last MCS = MCS9 Example Command MCS = MCS5 Re-trans = MCS3
Confidential
Introduction to MCS selection algorithm during transmission under IR function

Command MCS IR MCS9 MCS9 MCS8 MCS7 Last MCS MCS6 MCS5 MCS4 MCS3 MCS2 MCS1 MCS9 MCS8 MCS7 MCS6 MCS5 MCS4 MCS3 MCS2 MCS1 MCS8 MCS6 MCS8 MCS7 MCS6 MCS5 MCS4 MCS3 MCS2 MCS1 MCS7 MCS6 MCS6 (Pad) MCS7 MCS6 MCS5 MCS4 MCS3 MCS2 MCS1 MCS6 MCS6 MCS6 (Pad) MCS5 MCS6 MCS5 MCS4 MCS3 MCS2 MCS1 MCS5 MCS6 MCS6 (Pad) MCS5 MCS6 MCS5 MCS4 MCS3 MCS2 MCS1 MCS4 MCS6 MCS6 (Pad) MCS5 MCS6 MCS5 MCS4 MCS3 MCS2 MCS1 MCS3 MCS6 MCS6 (Pad) MCS5 MCS6 MCS5 MCS4 MCS3 MCS2 MCS1 MCS2 MCS6 MCS6 (Pad) MCS5 MCS6 MCS5 MCS4 MCS3 MCS2 MCS1 MCS1 MCS6 MCS6 (Pad) MCS5 MCS6 MCS5 MCS4 MCS3 MCS2 MCS1
Last MCS = MCS9 Example
Re-trans = MCS6 Command MCS = MCS5
When Last MCS and Command MCS are the same as those under LA, higher rate will be adopted in retransmission.
Confidential
Introduction to MCS selection algorithm during transmission without LA or IR
The selection rule: when MCS are of the same type, select the MCS lower by one grade; MCS9 is an exception; the highest coding mode in retransmission is MCS6, but not MCS8.
Confidential
Example of LA application
PCU MS
Last MSC =
MCS9
MCS9 data block
NACK
command MSC =
MS returns MEAN_BEP=31 and CV_BEP= 7 in DL ack/nack
MCS9 according to
MEAN_BEP and CV_BEP
MCS9 data block
MS returns MEAN_BEP=20 and CV_BEP=5 in DL ack/nack
command MSC =
MCS6
MCS6
MCS7 according to
MEAN_BEP and CV_BEP, so Re-trans MCS = MCS6
Note: according to BEP-based MCS selection algorithm and MCS selection algorithm in retransmission under LA, we can obtain the MCS used in retransmission under LA
Confidential
Example of IR application
Confidential
Introduction to IR-LA conversion algorithm
When MS or BTS doesnt have enough memory, they will notify each other to change to LA mode through Packet Ul/Dl Ack/Nack message.
Confidential
Related parameters
Parameter Name (CN)
Parameter Name Parameter Range & Unit (EN) Code

Yes/No No
ZTE Default
LA+IR Support uplink LA+IR IrSupportUp quality control
DL default: enabled;
The UL switch is displayed on the interface, but the function can not be supported yet; the codes are being written.
Contents Chapter 1 Introduction to Coding Mode Adjustment Algorithms

Chapter 2 Introduction to Link Quality Control Function
Confidential
Chapter 3 Introduction to UL TBF Access Mode

Chapter 4 Introduction to Window in Data Transmission
Chapter 5 Introduction to Functions, Timers and Counters Related to TBF Establishment & Release Chapter 6 Introduction to EDA and Algorithms of UL/DL Timeslot Allocation Decision Chapter 7 Introduction to Cell Reselection Algorithms Based on C1 & C2 Chapter 8 Introduction to BVC & MS Flow Control Algorithms Chapter 9 Introduction to DTM & Paging Coordination Function Chapter 10 Introduction to NACC Function Chapter 11 Introduction to Suspend/Resume Functions Chapter 12 Introduction to Functions & Algorithms Influencing PDTCH Planning Chapter 13 Introduction to Parameters of PDTCHTCH Conversion Chapter 14 Introduction to PreemptiveTrans Bit Function Chapter 15 Introduction to CS Move Function Chapter 16 Introduction to Granularity for UL Block Allocation of GPRS Handset
Chapter 17 Introduction to Parameters of Maximum UL/DL Users Allowed Chapter 18 Introduction to Relevant Poc Parameters Chapter 19 Quick Search for PS-related Radio Parameters
Introduction to UL TBF access mode
Confidential
One-phase access & two-phase access Introduction to EGPRS Packet Channel Request on CCCH Introduction to selection of access mode (twophase access is not forced) Related parameters
Confidential
Comparison between one-phase and two-phase access

MS PCU MS PCU RACH
EGPRS_PACKET_CHANNEL_REQUEST
RACH
AGCH
IMMEDATE_ASSIGNMENT_COMMAND
AGCH
PACKET_UPLINK_ASSIGNMENT
PACKET_RESOURCE_REQUEST
PACCH
PDTCH
DATA BLOCK
PACKET_UPLINK_ASSIGNMENT
PACCH
Time reduce 200ms
DATA BLOCK PDTCH
Phase 2 access
Phase 1 access
When one-phase access is adopted, the access delay is short; The signaling message of TBF establishment success rate is Packet Uplink Assignment. The two-phase access is carried out through sending packet resource request. If the request is not received by BSC, TBF establishment will fail. However, even though the first UL block is not received in one-phase access, MS still has several chances to send UL blocks and BSC has several chances to receive UL blocks. As long as the UL block is received by BSC within specific time (T3156, 5s) and number of blocks (N3104: (3*BS_CV_MAX+9)*number of channels), TBF establishment will succeed. Therefore, TBF establishment success rate is higher when one-phase access is used. In sum, choose not to use the forced two-phase access; decide TBF access mode according to the number of data blocks to be transmitted and whether the TBF type is signaling TBF.
Confidential
Introduction to EGPRS Packet Channel Request on CCCH
MS
PCU
RACH
MS is required to be able to support this signaling;

AGCH
PACKET UPLINK ASSIGNMENT
Compared with the common Channel requests, this signaling carries more information about EGPRS support ability.
DATA BLOCK
PDTCH
Introduction to selection of access mode (two-phase Confidential access is not forced)

Purpose of the packet access procedure
User data transfer requested RLC mode = unacknowledged User data transfer requested RLC mode = acknowledged and number of RLC data blocks 8 (note 1) User data transfer requested RLC mode = acknowledged and number of RLC data blocks > 8 (note 1) Upper layer signalling transfer (e.g. page response, cell update, MM signalling, etc)
EGPRS PACKET CHANNEL REQUEST supported in the cell

EGPRS PACKET CHANNEL REQUEST with access type = 'Two-phase access' EGPRS PACKET CHANNEL REQUEST with access type = 'Short Access' or 'One-phase access' or 'Two-phase access' EGPRS PACKET CHANNEL REQUEST with access type = 'One-phase access' or 'Twophase access' EGPRS PACKET CHANNEL REQUEST with access type = 'signalling' or CHANNEL REQUEST with establishment cause 'onephase access'
EGPRS PACKET CHANNEL REQUEST not supported in the cell

CHANNEL REQUEST with establishment cause = 'Single block packet access' for initiation of a two-phase access CHANNEL REQUEST with establishment cause = 'Single block packet access' for initiation of a two-phase access CHANNEL REQUEST with establishment cause = 'Single block packet access' for initiation of a two-phase access CHANNEL REQUEST with establishment cause = 'Single block packet access' for initiation of a two-phase access or CHANNEL REQUEST with establishment cause value 'one-phase access'
Sending of a measurement report or of a PACKET CELL CHANGE FAILURE
CHANNEL REQUEST with establishment cause = 'Single block packet access'
Sending of a PACKET PAUSE CHANNEL REQUEST with establishment cause = 'Single block packet access' (note 2) message NOTE 1: The number of blocks shall be calculated assuming channel coding scheme MCS-1. NOTE 2: Upon sending the first CHANNEL REQUESTmessage the mobile station shall start timer T3204. If timer T3204 expires before an IMMEDIATE ASSIGNMENT message granting a single block period on an assigned packet uplink resource is received, the packet access procedure is aborted. If the mobile station receives an IMMEDIATE ASSIGNMENT message during the packet access procedure indicating a packet downlink assignment procedure, the mobile station shall ignore the message.
Confidential
Related parameters
Parameter Name Parameter Name (EN) (CN)

MS EGPRS Two phase access
Paramete Range & r Code Unit

TwoPhaseAc Yes/No cess
ZTE Default
Yes
Support EGPRS packet channel EgprsPacket Yes/No request access program Chreq
No
Its suggested to set No to Two-phase access; When EDGE service is enabled, it suggested to Yes to Support EGPRS packet channel request access program.
Contents
Chapter 1 Introduction to Coding Mode Adjustment Algorithms Chapter 2 Introduction to Link Quality Control Function
Confidential
Chapter 3 Introduction to UL TBF Access Mode

Chapter 4 Introduction to Window in Data Transmission Chapter 5 Introduction to Functions, Timers and Counters Related to TBF Establishment & Release Chapter 6 Introduction to EDA and Algorithms of UL/DL Timeslot Allocation Decision
Chapter 7 Introduction to Cell Reselection Algorithms Based on C1 & C2

Chapter 8 Introduction to BVC & MS Flow Control Algorithms Chapter 9 Introduction to DTM & Paging Coordination Function Chapter 10 Introduction to NACC Function Chapter 11 Introduction to Suspend/Resume Functions Chapter 12 Introduction to Functions & Algorithms Influencing PDTCH Planning Chapter 13 Introduction to Parameters of PDTCHTCH Conversion Chapter 14 Introduction to PreemptiveTrans Bit Function Chapter 15 Introduction to CS Move Function Chapter 16 Introduction to Granularity for UL Block Allocation of GPRS Handset Chapter 17 Introduction to Parameters of Maximum UL/DL Users Allowed Chapter 18 Introduction to Relevant Poc Parameters Chapter 19 Quick Search for PS-related Radio Parameters
Introduction to the window of data transmission
Confidential
Introduction to the support ability of GPRS & EDGE service windows Introduction to the selection of windows for ZTE EDGE service
Confidential
Introduction to the support ability of GPRS & EDGE service windows

For GPRS service, the window supported during data transmission is fixed to be 64; there is a high risk of window histeresis, which may seriously impact data throughput. For EDGE service, the max window supported is 1024, which can be dynamically adjusted according to occupation of timeslots at MS. In EDGE service, window size is carried in the following messages:
PACKET_UL_ASSIGNMENT PACKET_DL_ASSIGNMENT PACKET_TIMESLOT_RECONFIGURE
Introduction to the selection of windows for ZTE EDGE service

Window size 64 96 128 160 192 224 256 288 320 352 384 416 448 480 512 544 576 608 640 672 704 736 768 800 832 864 896 928 960 992 1024 Reserved Coding 0 1 10 11 100 101 110 111 1000 1001 1010 1011 1100 1101 1110 1111 10000 10001 10010 10011 10100 10101 10110 10111 11000 11001 11010 11011 11100 11101 11110 11111 x X x x x x x Max X Max Max Def Max Def Max Def Min Def Max Def Min Min Max Def Max Def Min Def Min Min Timeslots assigned (Multislot capability) 3 4 5 6 1 Min Min 2 7 8
Confidential
ZTE choice
3GPP range
ZTE's WS
128
192
256
352
448
512
640
704
Contents
Chapter 1 Introduction to Coding Mode Adjustment Algorithms Chapter 2 Introduction to Link Quality Control Function Chapter 3 Introduction to UL TBF Access Mode Chapter 4 Introduction to Window in Data Transmission
Confidential
Chapter 5 Introduction to Functions, Timers and Counters Related to TBF Establishment & Release Chapter 6 Introduction to EDA and Algorithms of UL/DL Timeslot Allocation Decision Chapter 7 Introduction to Cell Reselection Algorithms Based on C1 & C2
Chapter 8 Introduction to BVC & MS Flow Control Algorithms

Chapter 9 Introduction to DTM & Paging Coordination Function Chapter 10 Introduction to NACC Function Chapter 11 Introduction to Suspend/Resume Functions Chapter 12 Introduction to Functions & Algorithms Influencing PDTCH Planning
Chapter 13 Introduction to Parameters of PDTCHTCH Conversion

Chapter 14 Introduction to PreemptiveTrans Bit Function Chapter 15 Introduction to CS Move Function Chapter 16 Introduction to Granularity for UL Block Allocation of GPRS Handset Chapter 17 Introduction to Parameters of Maximum UL/DL Users Allowed Chapter 18 Introduction to Relevant Poc Parameters Chapter 19 Quick Search for PS-related Radio Parameters
Introduction to Functions, Timers and Counters Related to TBF Establishment & Release
T3168
Confidential
Support TBF re-establishment flow

extended UL TBF UL delay time
DL release delay time

T3191/T3192/T3193 DrxTimeMax N3101/N3103/N3105/T3169/T3195 N3102 Related parameters
Confidential
T3168
Function: This timer is used for MS to decide when to stop waiting for the Packet UL Assignment message after it sends Packet Resource Request or PACKET CONTROL ACKNOWLEDGEMENT to apply for new TBF. Beginning: When applying for new TBF, MS sends PACKET RESOURCE REQUEST, which carries channel request message unit PACKET DOWNLINK ACK/NACK or PACKET CONTROL ACKNOWLEDGEMEN. The timer begins. Cessation: when PACKET UPLINK ASSIGNMENT is received, the timer ceases. Expiration: When Packet access flow is restarted or PACKET RESOURCE REQUEST / PACKET DOWNLINK ACK/NACK is retransmitted, the timer expires. At most 3 times of retransmission is allowed.
T3168 value has an impact on TBF establishment success rate. The smaller the value is set, the less time is left for TBF establishment, which means lower TBF establishment success rate, especially when radio environment is poor. Whereas, larger timer value leads to longer period for MS to judge TBF establishment failure, which means longer delay of packet access and lower system performance. Its suggested to set the timer a value between 1000ms2000ms according to the radio environment in the cells.
Confidential
Initial TBF Establishment is supported
Initial TBF establishment means : When uplink TBF is released, the CTRL_ACK in the last Packet Control Acknowledgement will indicate whether a new uplink TBF needs to be established immediately. Theoretically, enabling this function can avoid the situation that uplink TBF must be released before resource allocation requests are initiated again to establish uplink TBF. Thus, uplink throughput can be improved. As most MSs (BlackBerry, and fake phones)are not completely compatible with this function, those that do not fully support initial TBF establishment may not access network. It is not recommended to enable this function in versions before iBSC V6.20.200f.p005; As this function might be enabled in the field by mistake, it has been disabled on OMCR for iBSC V6.20.200f.p005 and later versions, but it can still be seen on OMCR.
Extended uplink TBF

MS Packet UL Data Block(CV=1) PCU
Confidential
The function of extended uplink TBF is to immediate enable data transmission again, if new data needs to be transmitted when the countdown process starts. Otherwise, new uplink TBF can only be established after the present TBF is totally released. Besides, it helps to maintain the establishment of uplink TBF when the last block (CV=0) has been acknowledged by the network. In this way, this function helps to speed up the transmission of uplink data, the establishment of downlink TBF. According to data or signaling, the extended uplink TBF can be configured separately. It is suggested that both are enabled so as to improve uplink/downlink throughput capacity.
Packet UL Data Block(CV=0) Timer Packet Uplink Dummy Control Block Packet UL Data Block(CV=0xff) Packet UL Data Block(CV=0xff) Stop Timer
When no payload is contained in Uplink Data block the PCU starts the timer
PCU receive UL data block with payload before timer expired, Stop timer and return to normal transfer mode.
Packet UL Data Block(CV=0) Timer Packet Uplink Dummy Control Block When no payload is contained in Uplink Data block the PCU starts the timer again
Packet Uplink Dummy Control Block
Packet Uplink Dummy Control Block
Expiry
Packet UL Ack/Nack( FAI=1 ) Packet Control ACK
PCU releases the TBF when Timer expired.
Rel
Rel
Confidential
Uplink delay time

MS Packet UL Data Block(CV=1) Packet UL Data Block(CV=0) Timer Packet downlink assignment When Receive Dl LLC Frame When no DL TBF PCU
Expiry Packet uplink ack/nack(FAI=1)) Packet Control ACK Rel Rel PCU release the TBF when Timer expired.
With uplink TBF, when the data block CV=0 is received, if there is no downlink TBF, then uplink delay time occurs. At this time, if there is no transmission of downlink data, downlink is established on PACCH, and uplink TBD is released. In other words, it does not need Polling or Paging to establish downlink TBF. When the uplink delay time is out according to the timer, the uplink TBF should be released. If the terminal and the system support extended uplink TBF, the timer ceases to be effective. So only one of the two functions can be chosen.
The configuration of time is relatively long, which helps to establish downlink TBF when there is no transmission of uplink data. However, this function is not as good as extended uplink TBF. That is, even if it is needed to transmit the uplink data during this time, the transmission will not happen until the Timer expires and the uplink TBF is newly established. This situation affects the uplink throughput. In summary, it is suggested that the default value of this parameter should be 1000ms.
Confidential
Release time of downlink delay time

MS
To avoid the repetitive release and re-establishment of downlink TBF, when downlink data TBF is established, the timer for downlink delay time is added. In this way, during the downlink delay time, if LLC frame of the upper layer needs to be transmitted, the downlink data is still transmitted by the original TBF, and it does not need to re-establish TBF. Therefore, the establishment of downlink TBF needs less time.
Re l
Packet DL Data Block Packet DL Data Block(FBI = 0) Packet DL Ack/Nack Packet DL Data Block(LLC DUMMY) Packet DL Ack/Nack
PC U
Tim er
When no LLC data will be sent starts the timer
Packet DL Data Block(FBI = 1) Packet DL Ack/Nack(FAI=1)
Expir y
TBF is released when the timer expired.
Re l
The bigger the parameter is configured, the longer TBF related resources (including TFI and timeslot) is reserved. If the configuration of the parameter is not big enough, it is not good for the discontinuous transmission of downlink data. Therefore, the configuration of this data should take the service load of the cell into full consideration. Under the circumstance that network resources are rich, the configuration of the time should be longer so as to reduce the time for establishing TBF and enhance the transmission data of downlink data.
Confidential
T3191/T3192/T3193
Timer
Function
T3191 is used to calculate the time before network can use the TFI again after it sends the final RLC data block. This timer helps the network side to confirm that the resources allocated to MS are invalid so as to reuse the TFI.
Start
After network sends a RLC data block whose Final Block Identifier (FBI) domain is 1
1.
Stop
T3191
T3192
T3193
When the final PACKET DOWNLINK ACK/NACK or PACKET CONTROL ACKNOWLEDGEMENT message is received; 2. It is restarted when network sends an RLC data block whose FBI=1. T3192 initializes the release of 1. In acknowledged mode, the 1.It restarts when the MS sends downlink TBF after the final data MS sends PACKET DOWNLINK ACK/NACK message block is received. PACKET DOWNLINK whose FBI domain is 1. This timer is used when MS receives ACK/NACK message 2. In unacknowledged mode, it restarts when all RLC data blocks. whose FBI domain is 1. MS sends PACKET CONTROL ACK message 2. In unacknowledged mode, MS as the response for the final RLC data block. sends the 3. It stops when MS receives PACKET DOWN PACKET CONTROL LINK ASSIGNMENT message. ACKNOWLEDGE 4. It stops when MS receives PACKET message as the TIME SLOT RECONFIGURE response for the final RLC data block. After network receives the final The final PACKET PACKET DOWN- LINK DOWNLINK ACK/NACK or 1. The network establishes a new downlink ACK/NACK from MS, the timer PACKET CONTROL TBF calculates the time before network ACKNOWLEDGE message is 2. It is restarted when the final PACKET reuses TFI. This timer helps the received. DOWNLINK ACK/NACK or PACKET network side to confirm that T3192 CONTROL ACKNOWLEDGEMENT message expires so as to reuse the TFI. is received
The higher the value of T3192, the longer time TBF resources will be reserved (including TFI and timeslot); lower value of T3192 will hinder the discontinuous transmission of downlink data. If T3192 has expired, but there is new downlink data in network, network will need to initiate paging or immediate assignment (if MS is in ready state), thus, downlink TBF establish will take a longer time. However, if T3192 does not expire when there is downlink data in network, network can send packet downlink assignment message to establish a new downlink TBF and shorten the time for TBF establishment. Therefore, the traffic of the current cell should be taken into full account for the setting of T3192/T3193, which should be set to a higher value when there is sufficient network resource, so as to shorten the time for TBF establishment and to improve data transmission rate. T3193 should be set to a higher value than T3192 In many sites, BlackBerry mobiles and some fake mobiles do not completely support T3192/T3193. Sometimes, network connection of these mobiles will be interrupted, or they can not access network, in this case, please set a lower value to T3192/T3193.
Confidential
Protection time under DRX mode
Parameter Name (CN)
Parameter Name Parameter (EN) code

DrxTimeMax
Range & Unit
ZTE Default
DRX DRX mode holding time
0, 1, 2, 4, 8, 16, 32, 64, s 2
Definition: It configures the maximum duration for MS to implement non-DRX mode when MS enters packet idle mode from packet transmission mode. When MS enters packet idle mode from packet transmission mode, it needs to keep nonDRX mode for a period of time. When TBF is released, with the non-DRX mode, MS will monitor all the CCCH blocks and PCU will reserve the context related to MS. When PCCCH channel is not configured for the network, with the non-DRX mode, the Immediate assignment command can be sent on all PCH and AGCH channels and the process only lasts for dozens of ms. However, with the DRX mode,
MS can only monitor the paging messages within the paging group it belongs to. Then the message of immediate
assignment message is received by all the paging blocks and AGCH reserved blocks. Besides, the process for receiving the paging message lasts for a relatively long time (It is related to the configuration of some parameters like the number of multiframes of paging channel and the number of reserved blocks of AGCH). However, with the non-DRX mode, the power consumption of the battery is increased. In general, it is suggested that the configuration of the parameter should be larger, for example, 4 6s.
Confidential
N3101/N3103/N3105/T3169/T3195
MS
USF=n USF=n
BS S
MS
CV=0 CV=0 PACKET UPLINK ACK/NACK
BS S
MS
Data BlockRRBP Data BlockRRBP
BS S
. .
USF=n
N3101max
. .
. .
N3103max
Data BlockRRBP PACK DLLINK ACK/NACK
N3105max
RlacMac_T3169
PACKET UPLINK ACK/NACK PACKET CONTROL ACK
RlcMac_T3195
RlcMac_T3169
Release USF and TFI
Release USF and TFI
Release TFI
Counter N3101
N3103
Description of functions For a USF, if the network receives correct data form a specified uplink block, N3101 clears for that TBF. If the number of losses in specified uplink block exceeds N3101(N3101max), then T3169 timer starts. The network uses the TFI and USF resources when T3169 stops. When the last PACKET UPLINK ACK/NACK message (FAI=1) of a TBF is sent, N 3103 is reset. If the PACKET CONTROL ACKNOWLEDGEMENT message is not received by the specified block of the network side, N3103 will have an increment and sent the PACKET UPLINK ACK/NACK again. If the counter N3103 exceed the limiting N3103max, the network will start T3169. The network uses TFI and USF resources when T3169 stops.
N3105
During the packet downlink transmission, BSS will configure RRBP domain on downlink RLC data block at set intervals so as to notify MS to send the RLC/MAC control message on corresponding uplink blocks (e.g., packet downlink confirmation message and the like). For a TBF, if the number of losses of RLC/MAC control message in specified uplink block exceeds N3105 (N3105max), T3195 starts. The network uses TFI resources when T3195 stops.
According to the definitions of N3101/N3103/N3105, it can be seen that if the configuration of these counters and Timers is a bit larger than the default value, TBF failure rate can be reduced to some extent.
Confidential
N3102
Parameter Name (CN)
N3102 N3102 N3102

N3102 decrease step N3102 increase step N3102 Max PanDec PanInc PanMax
Range & Unit
ZTE Default
48121620242832 4 48121620242832 8 48121620242832 32
When MS detects the stall condition of the window (V(S) = V(A) + WS), MS will start T3182. When PACKET UPLINK ACK/NACK is received, which enables V(S) < V(A) + WS, T3182 stops. When T3182 expires, MS will subtract PanDec from N3102 , and will implement the abnormal release of the TBF and make it accessed and have a retry. When MS receives the PACKET UPLINK ACK/NACK message from the network which allows the increase of V(S) or V(A), MS will add PanInc to N3102. However, N3102 can not exceed the value defined by PanMax. When N31020, MS will implement the abnormal release of the TBF, and will trigger the cell reselection. If the configuration of PanDecPanInc and PanMax is 0, N3102 is invalid. The configuration of T3182 is fixed, that is 5s, and it can be changed.
In summary, the addition of PanInc and PanMax, or the subtraction of PanDec can make it less possible that when
MS does not receive Packet Uplink Ack, TBF is released in an abnormal way and the cell is reselected. On the other hand, when the send window stops, and can not send data, MS will occupy the radio resources for a relatively long time. In this way, the utilization ratio of resources is not high. If possible, it is suggested that it should be avoided that TBF is released in an abnormal way and the cell is reselected. Besides, the default value should be reserved.
Confidential
T3142/T3172
Timer Function Start Stop Timeout
Initiate new packet access request.
Wait for the time to initiate The timer is used during The timer expires new packet access after packet access on CCCH, after IMMEDIATE the receipt of an IMMEDIATE
T3142
ASSIGNMENT REJECT
ASSIGNMENT REJECT message.
T3172
Before T3172 expires, MS shall not initiate new packet access attempt in the same cell. It could attempt packet assess in the new cell after cell reselection succeeds.
The timer is started after the PACKET UPLINK MS returns to idle packet receipt of the PACFKET ASSIGNMENT message is mode. The packet access in ACCESS REJECT message, this cell is prohibited no more. received. which corresponds to one of But Channel Request message the latest three packet channel could not be sent as the paging request messages response before the receipt of Paging request message.
This is realized in V6.20.100e. The T3122 value is used in previous versions. Too high the setting may influence the overall access performance into the network, affecting customers satisfaction. Too low the setting tends to block further the channels when the radio channel is heavily loaded. ZTE default value is recommended.
Confidential
Single Block Assignment Offset
Parameter Parameter Parameter Name (EN) Name (CN) Code

Single Block Assign Offset SBAssOffset
Range & Unit

6~12,block
ZTE Default
10
In V6.20.100e and later versions, this parameter, which is fixed in the system of previous versions, is visible on the EMS interface. The ZTE default value 10 is used when this parameter is not enabled; It is used to define the single block assignment offset allowed in the first single block assignment in two phase access.
Confidential
POLLING Retry Time
Parameter Name Parameter Name Parameter (CN) (EN) Code

POLLING Polling Retry Time PollingRetryTime
Range & Unit

3~12
ZTE Default
7
In V6.20.100e and later versions, this parameter, which is fixed in the system of previous versions, is visible on the EMS interface. The ZTE default value 7 is used when this parameter is not enabled; In some versions before V2, this parameter was enabled sometimes; It defines, when polling has not been received by MS after it was sent out by network, the maximum number of sending pollings This parameter should be set a higher value in order to improve the abnormal TBF failure rate.
Confidential
Relevant parameters
Category Parameter Name (CN) Parameter Name (EN)
BSC level BSC level BSC level BSC level BSC level BSC level BSC level BSC level BSC level Support signal extended uplink TBF TBF TBF release time of downlink transmission TBF TBF release timer MAX allowed number of continuous losses of uplink data blocks / Times of packet uplink ACK/NACK retries TFIUSF TFI and USF release timer MAX allowed number of RLC/MAC continuous losses of uplink RLC/MAC control message TBF TBF protect time when radio link failure Support TBF establish TBF Is the cell support TBF extendable uplink TBF Downlink delay time TBF Extend uplink TBF time
Parameter Code
Range & Unit
ZTE Default
No 51 500 10 10 500 10 500 No
SIGNAL_EUTBF Yes/No T3193 T3191 N3101 N3103 T3169 N3105 T3195 TBF_EST 0 ~ 65535, 10ms 0 ~ 65535, 10ms 9 ~ 255 0 ~ 255 0 ~ 65535, 10ms 0 ~ 255 0 ~ 65535, 10ms Yes/No
Cell level
Cell level Cell level
EXT_UTBF
DLDelaytime ExtULTBFTime
Yes/No
500 ~ 4000, ms 0 ~ 3000, ms
Yes
2000 1500
Confidential
Relevant parameters
Parameter Name (CN) Parameter Name (EN)
N3102 decrease step
Category
Parameter code
PanDec
Range & Unit
ZTE Default
Cell level N3102 Cell level N3102 Cell level N3102 Cell level
N3102 increase step PanInc N3102 Max PanMax
4812162024 4 2832 4812162024 8 2832 4812162024 32 2832
DRX DRX mode holding time T3192 Uplink delay time T3168
DrxTimeMax 0, 1, 2, 4, 8, 16, 32, 64, s 2 T3192 500, 1000, 1500, 0, 80, 120, 160, 200ms 500 1000 4
Cell level T3192 Cell level Cell level T3168
ULDelayTime 0 ~ 4000, ms T3168 0.5 ~ 4.0,0.5s
Contents Chapter 1 Introduction to Coding Mode Adjustment Algorithms

Chapter 2 Introduction to Link Quality Control Function Chapter 3 Introduction to UL TBF Access Mode Chapter 4 Introduction to Window in Data Transmission
Confidential
Chapter 5 Introduction to Functions, Timers and Counters Related to TBF Establishment & Release Chapter 6 Introduction to EDA and Algorithms of UL/DL Timeslot Allocation Decision Chapter 7 Introduction to Cell Reselection Algorithms Based on C1 & C2 Chapter 8 Introduction to BVC & MS Flow Control Algorithms Chapter 9 Introduction to DTM & Paging Coordination Function Chapter 10 Introduction to NACC Function Chapter 11 Introduction to Suspend/Resume Functions Chapter 12 Introduction to Functions & Algorithms Influencing PDTCH Planning Chapter 13 Introduction to Parameters of PDTCHTCH Conversion Chapter 14 Introduction to PreemptiveTrans Bit Function Chapter 15 Introduction to CS Move Function Chapter 16 Introduction to Granularity for UL Block Allocation of GPRS Handset Chapter 17 Introduction to Parameters of Maximum UL/DL Users Allowed Chapter 18 Introduction to Relevant Poc Parameters Chapter 19 Quick Search for PS-related Radio Parameters
Introduction to EDA and Algorithms of UL/DL Timeslot Allocation Decision
Confidential
Introduction to EDA functions

Introduction to algorithms of uplink/downlink timeslot allocation decision
Relevant parameters
Confidential
Advantages of EDA
DL PDC H0 PDC H1 PDC H2 PDC H3 PDC H4 PDC H5 PDC H6 PDC H7
USF
USF
UL
PDC H0
PDC H1
PDC H2
PDC H3
PDC H4
PDC H5
PDC H6
PDC H7
Dynamic Allocation
DL
PDC H0
PDC H1 USF
PDC H2
PDC H3
PDC H4
PDC H5
PDC H6
PDC H7
UL
PDC H0
PDC H1
PDC H2
PDC H3
PDC H4
PDC H5
PDC H6
PDC H7
As to dynamic allocation, each uplink PDCH should have a corresponding downlink PDCH to schedule it. Therefore, the number of uplink PDCH should be no more than that of downlink PDCH. In this case, some defects exist for those services which mainly center around uplink services (e.g., uploading, sending EMAIL and so on). It is supported by extend dynamic allocation that one downlink PDCH can schedule several uplink PDCH. In this case, it can better support the services which center around uplink services. It is suggested that this function should be enabled.
Extend Dynamic Allocation
Note: It is only supported by terminals of R4 or higher.
Confidential
Introduction to algorithms of UL/DL timeslot allocation decision

In V6.20.100f, the parameter Initial Downlink Allocation by Multislot Class 1 is added. If,
This parameter is set as No, PDTCH will be allocated according to the actual Multislot class supported by MS. If this parameter is set as Yes, PDTCH will be allocated according to Multislot Class 1 in priority. Then, the UL/DL resources will be allocated according to the relevant parameter Resource adjust threshold. It is recommended to set this parameter as No to improve downlink speed.
In versions before V6.20.100f, only the algorithm involved in parameter Resource adjust threshold is available. This will be dealt with in the next page.
Confidential
Introduction to algorithms of UL/DL timeslot allocation decision

Adjust Criteria (UL: UL data flow; DL: DL data flow) initial TS allocated( for Non PFC MS) UL + DL > = TH |UL DL| < TH/4 UL&DL TS: Balance Sum TS: Max DL - UL >= TH/4 DL TS: Max Sum TS: Max UL + DL < TH -
UL - DL >=TH/4 UL TS: Max Sum TS: Max
Principle Example: multislot class 12 (4d + 4u < 5 Sum) EDA enabled Example: multislot class 12 (4d + 4u < 5 Sum) EDA disabled
1d + 1u
no adjust
1d + 1u
1d + 4u
3d + 2u
4d + 1u
no adjust
1d + 1u
3d + 2u
3d + 2u
4d + 1u
no adjust
Adjust opportunities
The periodic check is once per 5s. At present, when the link of TBF is set up, the uplink/downlink only have one chance to be adjusted. 5KBytes is easy to be satisfied, so it is suggested that the configuration of this parameter should be 5KBytes.
Confidential
Relevant parameters
Parameter Name (CN) Parameter Name (EN)
Parame ter Range & Unit Code
ExUpDynS Yes/No upport No
ZTE Default
Support extended uplink dynamic allocation (Cell Level) Resource adjust threshold Support extended uplink dynamic allocation (BSC Level)
Resource 200 ~ 5000,Byte() 2000 AdjustThs ExUpDynS Yes/No upport
No
The following parameter is already invalid: Parameter Name (CN)
Parameter Name Parameter (EN) Code

Extend dynamic allot supported ExtDynAssign
Range & Unit
ZTE Default
0: support;1:not 0 support.
Contents
Confidential
Chapter 3 Introduction to UL TBF Access Mode Chapter 4 Introduction to Window in Data Transmission
Introduction to cell reselection algorithms based on c1 & c2
Confidential
Introduction to algorithms of cell reselection
decision before and after the ready state

Introduction to attached reselection parameter
indication
Relevant parameters
Confidential
Introduction to algorithms of cell reselection decision before and after the ready state
=RXLEV-RXLEV_ACCESS_MINMAX(MS_TXPWR_MAX_CCHP,O)+CRO-TEO*H(PT-T)+CRH When PT<640 or =RXLEV-RXLEV_ACCESS_MINMAX(MS_TXPWR_MAX_CCHP,O)-CRO+CRH When PT=640
Cell reselection threshold =C2+CRH
=C1+CRO-TEO*H(PTT)+CRH When PT<640 or =C1-CRO+CRH When PT=640
For terminals which are not at ready state (that is at standby state of CS), under the same LA, reselection will not be triggered until C2 of the non-serving cell surpasses C2 of the serving cell for 5 seconds. After one reselection, if another reselection is needed within 15 seconds, C2 of the new cell should be larger than C2 of the serving cell by 5dB for 5 seconds. For terminals at ready state, reselection will not be triggered unless C2 of the new cell is at least larger than C2 of the serving cell CELL_RESELECT_ HYSTERESIS dB for 5 seconds. In these two situations, after the cell reselection, MS will not return to the original cell in the following 5 seconds.
Confidential
Introduction to added reselection parameter indicator

This paramter defines whether C2 related parameters are broadcast on SI4 or SI7/8. SI7/8 can only be broadcast on extended BCCH. Some terminals do not support SI7/8. If this function is enabled, some terminals can not have the network access. In general, if C2 needs to be enabled, the configuration of CellReselPI should be YES, and the configuration of AdditionReselPI should still be NO.
Confidential
Relevant parameters
Parameter Name (CN)
Range & Unit
ZTE Default
No No 0 4 1 0
attached reselection parameter indication Cell reselection parameter indication Reselection offset Cell reselecting hysteresis level Temporary offset Penalty time
No:use parameters in SI AdditionReselP 4;Yes:use parameters in I SI7/8 CellReselPI Yes/No
ReselOffset 0~63, 2db ReselHysteresi 0~7, 2db s TemporaryOffse 0~7, 10db t PenaltyTime 0~31, 20s
Contents
Confidential
Introduction to BVC & MS Flow Control Algorithms
The relation between BVC and MS flow control Introduction to flow control algorithm Introduction to flow control mode Relevant parameters
Confidential
The relation between BVC and MS flow control

PS flow control is conducted at Gb interface from SGSN to BSS and controls only downlink. It is implemented by SGSN through control parameters provided by BSS, aiming to avoid the possibility that a BVC on BSS discards some LLC data because packet channel is too busy (too many buffer LLC frames) or the possibility that downlink LLC data is discarded as a result of memory resource limitation.
The transmission of downlink BSSGP DL_UNITDATA PDU from SGSN is controlled by BSS, which uses flow control to adjust leak bucket so that the memory data in it will be reduced to the maximum without interrupting downlink TBF transmission. More memory data in leak bucket consumes resource and will be discarded when the life circle of this memory data expires, which is informed to SGSN by LLC_DISCARDED PDU and will trigger off data retransmission at Gb interface. An LLC PDU could be sent out, only after MS flow control and BVC flow control are implemented by SGSN. BVC leakage ratio is the sum of all MS leakage ratios within the cell. It is recommended that MS flow control and BVC flow control be enabled simultaneously.
Confidential
Introduction to flow control algorithm

LLC PDU p with length Lp reaches at time Tc yes
B*=B+L(p)-(Tc-Tp)R
B*<Lp?
B=L(p)
no no B=B* Tp=Tc
B*>Bmax?
yes
Delay LLC PDU
Pass LLC PDU
Confidential
Introduction to flow control mode

Mode 1: report flow control parameter according to the actual radio interface traffic statistics taken at BSC side. Mode 2: report flow control parameters according to the maximum traffic that could be provided in a cell. Mode 3: reserved. When mode 1 is selected, BSC will report flow control parameter according to the actual radio interface traffic statistics. In practical use, as the actual statistics may be a little low as a result of radio interface retransmission and TBF failure, when BSC reports flow control parameter, the actual traffic will be multiplied by a certain times defined by the parameter, and parameter flow control mode 1 is used to define this times. If flow control mode 1 is adopted, it is recommended to set flow control mode 1 as about 3~5. When flow control mode 2 is adopted, BSC will report flow control parameter according to the maximum traffic available in a cell. The maximum traffic is based on the number of channels allocated, the calculation formula is: number of channels X the maximum traffic available in each channel. Parameter flow control mode 1 is used to define this speed, to which the unit is 100bps. If flow control mode 2 is adopted and EDGE is enabled, this parameter should be set as 592 or above. Attention: for MOTO and HW SGSN, mode 2 should be adopted.
Confidential
Relevant parameters
Parameter Parameter ZTE Parameter Name (EN) Range & Unit Name (CN) Code Default
BVC MS BVC MS BVC flow control period MS flow control period BVC flow control supported MS flow control supported Flow control mode Parameter of Flow control 1 mode 1 Parameter of Flow control 2 mode 2 BVC flow control R MIN BVCR value CellFcPer 0 ~ 65535, 10ms MsFcPer 0 ~ 65535, 10ms BVCFlowCtrl Yes/No MSFlowCtrl Yes/No FlowCtrlMode 1 ~ 3 FlowCtrlMode1P 1 ~ 100 ara FlowCtrlMode2P 10 ~ 1000, ara 100bps BVCFlowCtrlRM 10 ~ 300, 100bps in MSFlowCtrlRMi MSR MS flow control R MIN value 10 ~ 300, 100bps n 3000 3000 Yes No 1 1 214 80
80
The following two parameters have been invalid:

Parameter Name (CN)
BVC MS
Parameter Name (EN)
Parameter ZTE Range & Unit Code Default

1 ~ 100, % 1 ~ 100, % 80 80
BVC flow control threshold CellFcThs MS flow control threshold MsFcThs
Contents
Introduction to DTM & Paging Coordination Function
Confidential
Introduction to DTM function
How to make MS support CS when it is transmitting data?

Relevant parameters
Confidential
Introduction to DTM function
Supported by DTM function, both CS and PS could be conducted simultaneously in MS type A. DTM function consists of two modes: GTTP and TBF. In CS, if there is few PS signaling needs to be transmitted, it will be transmitted in GTTP message on SACCH. If there is a large amount of packet data, it will need to establish TBF and allocated packet channel to carry out transmission. Maximum number of GTTP Lapdm frame: it defines the maximum number of GTTP Lapdm frames when the TCH allocated in CS finishes PS signaling interaction service; the value 3 could satisfy common data services such as RAU, and ATTACH, and etc.; if it is set too high, user perception will be influenced a little. For requirements that could not be met by maximum number of GTTP Lapdm, TBF is the only way out. In current V6.20 series version (001 series and 100 series), handover between data service and CS under DTM mode has been possible, so DTM function could be enabled.
Confidential
How to make MS support CS when it is transmitting data?
If there is no Gs interface, MS type B will not monitor CCCH when it is in data. In this case, if paging coordination function is enabled, BSC will check whether this MS is in PS service when it receives CS paging messages from A interface. If the MS is in PS service, it will send the CS paging message to MS on the PDTCH the MS is transmitting data so as to make the MS responds to the paging and suspend the ongoing data service to conduct CS. For MS type A, DTM function could be enabled so that PS and CS could be conducted simultaneously.
Confidential
Relevant parameters
Parameter Name Parameter Name (EN) (CN)

DTM Support DTM BSCCS BSC support page coordination GTTP Lapdm Max number of GTTP Lapdm frame
Parameter Code
DTMSupport PagCoordination GttpLapdmNum
Range & ZTE Unit Default

Yes/No Yes/No 0~7 No No 3
Contents
Confidential
Introduction to NACC Function

Introduction to advantages of NACC function Introduction to parameters related to NACC switch Introduction to CCN mode Introduction to (P)SI Status NACC signaling flow Comparison between the signaling flow of MScontrolled cell retransmission and that under NACC Introduction to Timers and Counters related to obtaining inter-BSC NACC neighbor cell (P)SI Introduction to network control order
Confidential
Introduction to advantages of NACC function

NACC allows BSC to aid the GPRS/EDGE MS under Packet Transfer mode to conduct cell update. The time delay in cell reselection is due mainly to the time consumed to collect the whole set of system messages (SI1, 3, 13), so NACC is expected mainly to reduce the time used to wait for SI. When MS needs reselection, it will send Packet Cell Change Notification to inform system about the BCCH/BSIC of the target cell, without interrupting data transmission. System will send the system message of the target cell to MS through Packet Neighbor Cell Data message in packet transmission, reducing the time of transmission interruption caused by receiving system message.
NACCs outside and inside of BSC function the same, both aim to speed up the access to new cells when MS makes cell reselection. This is realized through the method that MSC sends MS system message of the new cell in the original cell before MS makes cell reselection, saving the time that MS spends to receive system message after reselected the new cell. On the contrary, the NACC outside of BSC needs SGSN and RAN Information ManagementRIM process to obtain the system information of the cells outside of BSC.
Outside NACC is applicable to V6.20.100e and above. LLC frame transfer function in the same CMP module is applicable to V6.20.200e and above. LLC frame transfer function in different CMP modules is not supported temporarily.
Confidential
Introduction to parameters related to NACC switch

Parameters in versions below V6.20.100e:
Parameter Name (CN)
Parameter Paramete Name(EN) r code
Range
ZTE Default
Not support NACC No
NACC supported RIM RIM support
Not Support NACC;Support NACC, not NACCSuppor LLC Frame Transfer;Support NACC and t LLC Frame Transfer RIMSupport Yes/No
Parameters in V6.20.200e and above:
Parameter Name (CN)

LLC RIM
Parameter Paramete Name(EN) r code

NACC supported LLC frame rerouting RIM support NACCSuppor Yes/No t LLCTRANSU Yes/No PPORT RIMSupport Yes/No
Range
ZTE Default
No No No
Confidential
Introduction to CCN mode

CCN mode is cell change notification, which is broadcasted to MS through system message. When CCN is allowed in BSS, if MS in NC0 and NC1 mode needs cell reselection, a PACKET CELL CHANGE NOTIFICATION will be sent to BSS. After BSS receives this message and obtains system messages of the neighbor cells, it will send certain system messages of candidate cells. Only after BSS receives PACKET CELL CHANGE NOTIFICATION will it send the required system message to MS, i.e. NACC is enabled only in CCN mode.
Parameter Name (CN)

CCN
Parameter Paramete Name (EN) r Code

CCN is allowed CCNActive
Range & Unit

Yes/No
ZTE Defaul t
No
Confidential
Introduction to (P)SI Status

The system message of the reselected cells sent from service cell is not the whole set of system message, instead, it is only a part, which contains the parameters MS should acquire in order to access the reselected cell. However, this part of system messages could not guarantee the immediate access of MS to the reselected cell, to which the precondition is the reselected cell supports PSI Status (PBCCH has been allocated) or SI Status. If PSI Status or SI Status is supported in the reselected cell, it could be guaranteed that MS receive the whole set of system messages under packet transmission. In this case, MS will be able to enter into packet transmission in the reselected cell immediately, without spending extra time in monitoring system messages. After accessed the reselected cell, MS will send PSI(SI)Status message to network side on PACCH. After received this, BSC will send Packet Serving Cell SI as indicated so that MS could acquire more system messages needed without going back PBCCH (BCCH) for monitoring, reducing the time of service interruption. If PSI(SI) Status is not supported in the reselected cell, MS need try to receive the whole set of system messages at least once after entering the reselected cell, therefore, packet service needs to be interrupted for a longer time. Use PSI Status message if PBCCH is allocated, otherwise, use SI Status message.
Parameter Name (CN)

PSI
Parameter Name(EN)
PSI status supported
Parameter code
PsiStatInd
Range
Yes/No Yes/No
ZTE Default
No No
SI Status indication SIStatusInd
Confidential
NACC signaling flow
When MS meets the condition for cell reselections, and supports CCN mode, it will transmit on PACCH the PACKET CELL CHANGE NOTIFICATION message, which contains BCCH and BSIC of the target cell for cell reselection. After received this message, BSC will send PACKET NEIGHBOUR CELL DATA message, which contains system message in the needed target cell during cell reselection. Then, BSC will send PACKET CELL CHANGE CONTINUE message to inform MS to continue cell reselection.
Confidential
Comparison between the signaling flow of MScontrolled cell retransmission and that under NACC
According to the above figure, after NACC is enabled, in data transmission mode, network provides the SI1SI3 and SI13 of the target cell of MS on PACCH, so as to reduce the procedures for MS to monitor these system messages of the target cell in cell reselection process (NC0 mode). Thus, the time of interrupted data transmission caused by cell reselection is reduced.
Confidential
Introduction to Timers and Counters related to obtaining inter-BSC NACC neighbor cell (P)SI
TRIR: this timer is started when service BSC requires system message from target BSC, and is stopped when service BSC receives system message from target BSC. If this timer expires, message request flow will be regarded as failed, and service BSC will initiate another message request; TRI: this timer is started when target BSC waits for ACK response after it sends system message to service BSC, and is stopped when target BSC receives the ACK response from service BSC. TRIAE: this timer is started when service BSC waits for ACK response, after it initiates RAN Information Application Error flow when receiving incorrect system message. It is stopped when service BSC receives ACK response from target BSC.
As the minimum value for these three Timers is 5s, even though the maximum RIMRetryTimes is set as 1, the reselection process will cost a long time; therefore, it would be better for MS to restart cell reselection when it discovers another suitable candidate cell that satisfy the condition for cell reselection after the above timer expires. This helps to select the best candidate cell. RIMRetryTimes is recommended to be set as 0.
Parameter Name (CN)

RIM RIR RI RIAE
Parameter Name(EN)
RIM Retry times RIR timer RI timer RIAE timer
Parameter code
RIMRetryTimes TRIR TRI TRIAE 0~3
Range
50 ~ 300,100ms 50 ~ 300,100ms 50 ~ 300,100ms
ZTE Default
0 50 50 50
Confidential
Introduction to network control order

NC0MS reselects cells automatically NC1MS reports measurement report, and reselects cell automatically NC2 MS reports measurement report, and network controls cell reselection
Parameter Name (CN)
Parameter Name(EN)
Paramete r code
Range
NC0, NC1, NC2
ZTE Default
NC0
Network control order CtrlOrder
Contents
Introduction to Suspend/Resume Functions
Confidential
The signaling flow of data service resumption through RAU The signaling flow of data service resumption through Resume Advantages of Suspend/Resume Functions and their implementation methods in ZTE Relevant Parameters
The signaling flow of data service resumption through RAU

Suspend GPRS service Resume GPRS service
After CM service is ended, system sends channel release to MS. It could be learnt from the specific RR cause that the RR CAUSE is Normal event because system does not support RESUME function. MS needs to initiate route update to request for continuing FTP process. After MS receives the channel release, to which the RR cause is normal event, it will initiate uplink channel request to establish TBF to continue GPRS service through route update.
Confidential
In the FTP downloading process, MS initiates CM service request, which is reflected in MS sending short messages MS initiates GPRSSuspension request. From the specific suspension cause, it could be learnt that the suspension is caused by MS initiating short message service.
The signaling flow of data service resumption through Resume

Suspend GPRS service Resume GPRS service
Confidential
In the FTP downloading process, MS initiates CM service request, which is reflected in MS sending short messages
MS initiates GPRSSuspension request. It could be learnt from the specific suspension cause that the suspension is caused by MS initiating short message service.
After MS receives the channel release, to which the RR cause is GPRSResumption, it will initiate uplink channel request to establish TBG and resume GPRS service.
After CM service is ended, system will sends channel release to MS. It could be learnt from the specific RR cause that the resume from PCU to SGSM has been responded normally. And system will inform MS to conduct GPRS resume through channel release.
Confidential
Advantages of Suspend/Resume Functions and their implementation methods in ZTE

There are obvious advantages in using RESUME function, reflected mainly in: 1. Reducing PCU load: RAU will generate large amount of signaling and PS traffic, increasing both SGSN load and TBF reuse rate; the number of TBFs needed to be maintained by PCU and the number of GPRS channel will also increase, leading to heavier PCU load. 2. Shortening PS interruption: compared with RESUME, RAU consumes longer time, in this case, the time of PS interruption will be longer. But, the implementation method adopted in ZTE differs from what is stipulated in GSM protocol, which is detailed as follows: 1. If the ResumeSetOpt of RESUME is set as Open, BSC side will send SUSPEND to SGSN but not send RESUME to MS, and MS will conduct RAU automatically; 2. If the ResumeSetOpt of RESUME is set as Close, BSC side will not send SUSPEND to SGSN but will send back RESUME to MS, in this case, MS will not trigger off RAU. It could be learnt from the above that, if the ResumeSetOpt of RESUME is set as Open, MS will trigger off RAU after CS is ended; if RAU fails or costs too long time, the test KPIs of CS will be affected greatly. It is recommended to set this option as Close in CS test, or set MS as ATTACH only when necessary.
Confidential
Relevant parameters
Parameter Name (CN)

RESUME
Parameter Name (EN)

MAX times of suspend retry
Parameter ZTE Range & Unit Code Default

SuspendMax 0 ~ 10 0 ~ 10 1 ~ 100, 100ms 1 ~ 100, 100ms Open/Close 3 3 30 30 Open
MAX times of resume retry ResumeMax Suspend retry time Resume retry time Resume set option BssgpT3 BssgpT4 ResumeSetOpt
Contents
Confidential
Introduction to Functions & Algorithms Influencing PDTCH Planning
TCH allocation strategy

PDCHPrecedence function Ps Service Preference property function The function of conversion from static TCH/F to HR and SDCCH Introduction to PDTCH allocation algorithm based on the idle threshold of TRX
Relevant parameters
Confidential
TCH allocation strategy-from the two ends to the middle according to timeslot number
For V6.00.100a series, all sub-versions of 6.10, and all sub-versions of 6.20, one algorithm is added for the allocation strategy of TCH. According to this algorithm, TCH is allocated on basis of the timeslot number from high to low, that is, 0/7>1/6>2/5>3/4. TSID TsChannelComb TSID Group B TsChannelComb TSID Group C TsChannelComb Group A 0 14 0 0 0 0 1 14 1 0 1 0 2 0 2 0 2 0 3 0 3 0 3 14 4 0 4 0 4 14 5 0 5 0 5 0 6 0 6 14 6 0 7 0 7 14 7 0
If this algorithm is added, it can be seen that strategy C is the best among the three planning methods of PDTCH, that is, A, B, and C. The reasons for this are as follows
For strategy A, when the voice service occupies the third or fourth timeslot, the data service can not occupy 4 continuous Tsl. For strategy B, when the voice service occupies the third or fourth timeslot, the data service can not occupy 4 continuous Tsl. For strategy C, when the voice service occupies the fifth timeslot, the data service can not occupy 4 continuous Tsl.
Confidential
PDCHPrecedence function
If there is the parameter of PDCHPrecedence in timeslot parameters, it indicates that the function of absolute preference of PS service is added to this version. If this parameter is enabled (The configuration is Yes.), data service can compete for the channel which is being used for voice service. However, it is not the other way round. At present, all GSM networks give priority to voice service, so this funciton has not been used in the work field yet. However, some aspects need to be paid attention to when static PDTCH is configured or static PDTCH is changed into dynamic PDTCH: If the parameter TsChannelComb of timeslot level is manually modified as the type of PDTCH+PACCH+PTCCH, the parameter of PDCHPrecedence will be automatically modified as Yes. However, if it is modified by batch operation or the Template (NetworkPlan) is used to import directly, PDCHPrecedence of the static PDTCH channel must be configured as Yes.
If the dynamic channel is not configured as absolute preference for PS service, PDCHPrecedence
must be configred as No when static PDTCH is changed into dynamic channel. The purpose for this is to give absolute priority to CS service.
Confidential
Ps Service Preference property function

If there is the parameter of priority attribute of packet service channel in timeslot parameters, it indicates that this version is added the priority attribute of packet service channel. This parameter defines 4 types of PDTCH channel, that is, GPRS preference channel, EDGE preference channel, EDGE exclusion channel, and non-preference channel. The adoption of this function is to reduce or avoid the possibility that subscribers of GPRS and EDGE share PDTCH so as to improve the subscriber perception. If this function is used, the following aspects needs special attention: GPRS preference channel or EDGE preference channel are only relative concepts. They will not be effective unless some groups of PDTCH are defined as GPRS preference channel, and some groups of PDTCH are defined as EDGE preference channel. EDGE exclusion channel is only for subscribers of EDGE service. On the one hand, it can improve the perception of EDGE subscribers, on the other hand, it will waste some resources. At present, ZTE equipment can reuse the modulation mode of GMSK and 8PSK at Block level.
PDCH type Static Dynamic
EDGE exclusion(EE)
EDGE preference(EP)
Non GPRS preference(NP) preference(GP)
Confidential
Ps Service Preference property function
Note: The following figure is supposed to help to understand these 2 parameters, and it does not take into consideration the multislot processing capability of MS.
1. EDGE service occupy EDGE prior PDCH as EDGE user quotas is below V1.
2. EDGE service occupy GPRS prior PDCH as EDGE user quotas is over V1.
3. EDGE service move back to EDGE prior PDCH as GPRS user quotas is over V2. V1= SfPreferBusyThs; V2=OpPreferBusyThs
Confidential
The function of conversion from static TCH/F to HR and SDCCH

If there is HRTsPercentage in cell parameters, it means that the function of conversion from static TCH/F to HR and SDCCH is available. On the other hand, if this function exists, it means that there is no constraint that dynamic PDTCH and dynamic HR need to share the switch. Besides, there is no need to configure most of the service channels of the cell as dynamic channels for sake of dynamic HR. Notes:
For SDR, the capacity planning for each BSC HR should not exceed 15000Erl.
The default value of HRTsPercentage is smaller than 50%, which limits the largest usage ratio of HR. So it should be adjusted flexibly according to the actual application of HR.
Confidential
Introduction to PDTCH allocation algorithm based on the idle threshold of a TRX

Objective
During the application of PDTCH resource, subscribers should be gathered on idler TRXs as much as possible so as to avoid meaningless expansion; When the calculated idle threshold of TRX is lower than the value of TrxPSBusyThs, PS service should be balanced among different TRXs. Select in priority other idler TRXs for allocation, in order to increase subscribers rate.
Formula to calculate the idle threshold of a TRX (at timeslot level)

The limit in all useable PS times on a TRX (value:0~16)* Abis bandwidth (EDGE:4; GPRS: 2)*100/(number of PS subscribers on a TRX+1)/number of useable timeslots
Points for attention in setting TrxPSBusyThs

Only the idle threshold of downlink TRX is calculated currently; Sequence of application: TRXs on which busy threshold is lower than this threshold idle TRXs TRXs on which busy threshold is higher than this threshold; In field application, the value of this parameter should be increased gradually to reduce the reuse rate of PS users. This is more effective in improving the speed during the throughput test to cells with busy PS service.
Confidential
Relevant parameters
Parameter Name (CN)
PSCS PDCH
Parameter Name (EN)

Support PS Prmp CS Dynamic ts Ps Service Preference property
Parameter Code
PSPrmpCSSupport
Range & Unit ZTE Default

Yes/No No Yes/No Yes No preference, GPRS preference, EDGE No preference preference, EDGE specialty Yes/No No Yes/No Yes
PDCH Priority Support of subscriber occupying other preference channel Support of PS subscriber moving out of other preference channel Congeneric service threshold for PS-moving Un-congeneric service threshold for PS-moving PS
PDCHPrecedence HybridOccuSupp
AllowPsMove
Yes/No
No
SfPreferBusyThs OpPreferBusyThs
0~100, %() 0~100, %() 1 ~ 6400
100 0 900
TRX PS busy threshold TrxPSBusyThs(<)
Contents
Confidential
Introduction to Parameters of PDTCHTCH Conversion
Confidential
Parameter Name (CN)

CS
Parameter Name (EN)
Parameter Code
Range & Unit

0 ~ 255()
ZTE Default
2
Minimal number of CsChansThs idle CS channel PSRelDelay
PS PS channel delay release timer
200 ~ 600, 100ms
300
For cells of small sites, if the static PDTCH is not configured, CsChansThs should be configured as 0, if possible. In this way, it can be avoided that the normal data service can not carry on when the voice service is busy. As to PSRelDelay, if possible, the dynamic channel should keep the type of TCH since priority is given to the voice service. Besides, since the minimum value of this Timer is 20s, it is suggested that 20s should be the minimum value.
Contents
Confidential
Confidential
Introduction to PreemptiveTrans Bit Function
Parameter Name (CN)
Parameter Name ZTE Parameter Code Range & Unit (EN) Default
Take "Preemptivetrans bit" function PreemptiveRans Yes/No No
If this function is supported by the cell, through the field of PRE_EMPTIVE_TRANSMISSION
of
PACKET UPLINK ACK/NACK message, the network can indicate whether the handset can send the RLC data of PENDING-ACK when there are no NACK state data and no new RLC data blocks need to be sent, or when the send window is full. If the function of preemptiveTrans bit is enabled, the throughput can be improved to some extent.
Contents
Confidential
Chapter 5 Introduction to Functions, Timers and Counters Related to TBF Establishment & Release
Chapter 6 Introduction to EDA and Algorithms of UL/DL Timeslot Allocation Decision Chapter 7 Introduction to Cell Reselection Algorithms Based on C1 & C2
Chapter 8 Introduction to BVC & MS Flow Control Algorithms Chapter 9 Introduction to DTM & Paging Coordination Function Chapter 10 Introduction to NACC Function Chapter 11 Introduction to Suspend/Resume Functions Chapter 12 Introduction to Functions & Algorithms Influencing PDTCH Planning Chapter 13 Introduction to Parameters of PDTCHTCH Conversion Chapter 14 Introduction to PreemptiveTrans Bit Function Chapter 15 Introduction to CS Move Function Chapter 16 Introduction to Granularity for UL Block Allocation of GPRS Handset Chapter 17 Introduction to Parameters of Maximum UL/DL Users Allowed Chapter 18 Introduction to Relevant Poc Parameters Chapter 19 Quick Search for PS-related Radio Parameters
Confidential
Introduction to CS Move Function
Parameter Parameter Parameter Name (EN) Name (CN) Code

CS Support of CS subscriber moving Access Persist Level AllowCsMove
Range & Unit

Yes/No
ZTE Default
No
In theory, if this function is enabled, it can largely prevent subscribers of voice service from occupying the dynamic PDTCH channel. However, at present, if this function is enabled, the indicators like handover and call drop will be greatly influenced. So it is suggested that it should not be enabled.
Contents
Confidential
Chapter 5 Introduction to Functions, Timers and Counters Related to TBF Establishment & Release Chapter 6 Introduction to EDA and Algorithms of UL/DL Timeslot Allocation Decision Chapter 7 Introduction to Cell Reselection Algorithms Based on C1 & C2 Chapter 8 Introduction to BVC & MS Flow Control Algorithms Chapter 9 Introduction to DTM & Paging Coordination Function
Chapter 10 Introduction to NACC Function Chapter 11 Introduction to Suspend/Resume Functions

Chapter 12 Introduction to Functions & Algorithms Influencing PDTCH Planning Chapter 13 Introduction to Parameters of PDTCHTCH Conversion Chapter 14 Introduction to PreemptiveTrans Bit Function Chapter 15 Introduction to CS Move Function Chapter 16 Introduction to Granularity for UL Block Allocation of GPRS Handset Chapter 17 Introduction to Parameters of Maximum UL/DL Users Allowed Chapter 18 Introduction to Relevant Poc Parameters Chapter 19 Quick Search for PS-related Radio Parameters
Confidential
Introduction to Granularity for UL Block Allocation of GPRS Handset
Parameter Name (CN)
Parameter Parameter Name (EN) Code
Range & Unit
ZTE Defaul t
GPRS Selective granularity
0~1 USFGranularit (0: uplink block allocation 0 y granularity is 1; 1: uplink block allocation granularity is 4)
It is sent to the handset in PACKET UPLINK ASSIGNMENT message. It indicates that when the cell adopts the media control method of dynamic allocation, the network will allocate uplink block granularity to the GPRS handset. A smaller configuration can avoid the waste of resources. A smaller configuration can make the allocation of resources more flexible. If 4 granularities, which are not continuous, are chosen to be allocated at one time, the allocation will fail. Therefore, it is suggested that the configuration of this parameter should be 0, and each time one granularity should be allocated to subscribers.
Contents
Confidential
Chapter 5 Introduction to Functions, Timers and Counters Related to TBF Establishment & Release Chapter 6 Introduction to EDA and Algorithms of UL/DL Timeslot Allocation Decision Chapter 7 Introduction to Cell Reselection Algorithms Based on C1 & C2 Chapter 8 Introduction to BVC & MS Flow Control Algorithms Chapter 9 Introduction to DTM & Paging Coordination Function
Chapter 10 Introduction to NACC Function Chapter 11 Introduction to Suspend/Resume Functions

Chapter 12 Introduction to Functions & Algorithms Influencing PDTCH Planning Chapter 13 Introduction to Parameters of PDTCHTCH Conversion Chapter 14 Introduction to PreemptiveTrans Bit Function Chapter 15 Introduction to CS Move Function Chapter 16 Introduction to Granularity for UL Block Allocation of GPRS Handset Chapter 17 Introduction to Parameters of Maximum UL/DL Users Allowed Chapter 18 Introduction to Relevant Poc Parameters Chapter 19 Quick Search for PS-related Radio Parameters
Confidential
Introduction to Parameters of Maximum UL/DL Users Allowed

Parameter Name (CN) Parameter Name (EN) Parameter Code
MaxPsUserPerTs_0
Range & Unit

2~8
ZTE Default
4
Maximum PS uplink PS user per ts Maximum PS PS downlink user per ts
MaxPsUserPerTs_1
2 ~ 16
To guarantee that there is no artificial constraint on USF high limit and TFI high limit on a PDCH. So these two parameters are open. A low rate can be allowed. However, it can not be allowed that resources are available but subscribers can not have the access because of human factors. It is suggested that the configuration of uplink is 7, and the configuration of downlink is 16 or a little bit lower.
Contents
Confidential
Confidential
Introduction to Relevant Poc Parameters

The parameter Optimized PoC service support is used to control the following five parameters: PSCAPATHS_UL, PSCAPATHS_DL, PocAttSelt_0, PocAttSelt_1, and PocSrcThs. Only when it is set as Yes could relevant Poc optimization parameters work. The parameters Maximal users of POC service on shared PS channel 0 and Maximal users of POC service on shared PS channel 1 are used to define maximum number of users of the Poc service on
shared UL/DL Poc channel;

The parameters Highest coding scheme of POC service in GPRS and Highest coding scheme of POC service in EGPRS are used to define the highest coding scheme that could be used in Poc service; The parameters Maximal resource for POC service defines the percentage of current PS resource that could be occupied in Poc service. Note: 1) the number when the database obtained PDTCH should be used as the basis for calculation; 2) if fraction occurs, the calculation results should be rounded down; 3) this part of resources will be allocated to Poc users; only this part of resources could be used for Poc service, i.e. this is the only resource that could be used by Poc service.
Confidential
Relevant parameters
Category Parameter Name (CN) Parameter Name (EN) Parameter code Range & Unit ZTE Default
BSC level
PoC POC PoC
BSC level
BSC level
POC PoC GPRSPOC EDGEPOC POC
BSC level
BSC level Cell level
Optimized PoC POCSUPPORT Yes/No service support Maximal users of POC service on PSCAPATHS_U 26 shared PS channel L 0 Maximal users of POC service on PSCAPATHS_D 26 shared PS channel L 1 Highest coding CS1CS2CS3 scheme of POC PocAttSelt_0 CS4 service in GPRS Highest coding scheme of POC PocAttSelt_1 MCS1 ~ MCS9 service in EGPRS Maximal resource POCSrcThs 0~100,% for POC service
No
CS3
MCS6 50
Contents
Confidential
Confidential
A fast check of radio parameters related to PS service

GSM Training Materials For Special Subjects - Optimization of PS Radio Parameters - R2

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

GSM Training Materials For Special Subjects - Optimization of PS Radio Parameters - R2

Загружено:

Авторское право:

Доступные форматы

Optimization of PS Radio Parameters

Feng Xiaoying Lu Yan Wang Hangyan

Relevant PS parameters of V6.20.100 series are added.

Feng Xiaoying Lu Yan Wang Hangyan

Introduction to Coding Mode Adjustment Algorithms

EGPRS phone quality measure mode

Classifications of coding mode

FEC Code Rate

User bit Rate Family bits/20ms (bps)

Initial coding mode and its dynamic adjustment

Parameter Name Parameter Paramete (CN) Name (EN) r Code

Range & Unit

MCS2MCS5 MCS6 MCS6

Parameter Name (CN)

Parameter Name (EN)

Range & Unit

EGPRS phone quality measure mode

Range & Unit

Interval number of Packet Downlink/Uplink Ack/Nack

Parameter Name (CN)

Average filter period for BEP

Parameter Name (CN)

Parameter Parameter Name (EN) Code

Range & Unit

Average filter BEP period for uplink BEP

Average filter BEPperiodDo BEP period for downlink 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10 wn BEP

Uplink measure report period

Parameter Name (CN)

Parameter Name (EN)

Range & Unit

Uplink measure report period

Introduction to Link Quality Control Function

LQC: link quality control

Link adaptation (GPRS, EGPRS)

Lower performance Lower memory required

Higher performance Higher memory required Soft combining

MCS9 for Example

Introduction to selection algorithm of MCS based on Confidential BEP

Introduction to MCS selection algorithm during transmission under LA function

Last MCS = MCS9 Example Command MCS = MCS5 Re-trans = MCS3

Introduction to MCS selection algorithm during transmission under IR function

Last MCS = MCS9 Example

Re-trans = MCS6 Command MCS = MCS5

Introduction to MCS selection algorithm during transmission without LA or IR

MCS9 data block

MS returns MEAN_BEP=31 and CV_BEP= 7 in DL ack/nack

MCS9 data block

MS returns MEAN_BEP=20 and CV_BEP=5 in DL ack/nack

Introduction to IR-LA conversion algorithm

Parameter Name (CN)

Parameter Name Parameter Range & Unit (EN) Code

LA+IR Support uplink LA+IR IrSupportUp quality control

Contents Chapter 1 Introduction to Coding Mode Adjustment Algorithms

Chapter 3 Introduction to UL TBF Access Mode

Introduction to UL TBF access mode

Comparison between one-phase and two-phase access

Time reduce 200ms

DATA BLOCK PDTCH

Introduction to EGPRS Packet Channel Request on CCCH

MS is required to be able to support this signaling;

Introduction to selection of access mode (two-phase Confidential access is not forced)

EGPRS PACKET CHANNEL REQUEST supported in the cell