GSM Training Materials for Special Subjects--Optimization of PS Radio Parameters_R2

Optimization of PS Radio Parameters

Suitable for staff with P&O skill certificate IV

Issued by GSM Product Support Dept.

GSMGSM Training Materials forTraining Materials for Special Subjects Special Subjects

Confidential ▲

Version Introduction Version Date Writer Assessor Translator Amendment Records

V1.0 2009-06-30 Hou Shuai Zheng Hao None

V2.0 2009-11-13 Hou Shuai Zheng Hao Feng XiaoyingLu YanWang Hangyan

Relevant PS parameters of V6.20.100 series are added.

V3.0 2010-01-18 Hou Shuai Zheng Hao Feng XiaoyingLu YanWang 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.

V1.3 2010-03-31

Hou Shuai

Zheng Hao

Feng XiaoyingLu YanWang Hangyan

The optimization of ResourceAdjustThs is modified

V2.0 2010-07-21

Hou Shuai

Zheng Hao

Feng XiaoyingLu YanWang Hangyan

The optimization of Interval number of Packet Downlink/Uplink Ack/Nack, TBF_EST, and T3192/T3193 is

modified.

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!

Confidential ▲

Contents Chapter 1 Introduction to Coding Mode Adjustment AlgorithmsChapter 2 Introduction to Link Quality Control FunctionChapter 3 Introduction to UL TBF Access Mode Chapter 4 Introduction to Window in Data TransmissionChapter 5 Introduction to Functions, Timers and Counters Related to TBF Establishment & Release Chapter 6 Introduction to EDA and Algorithms of UL/DL Timeslot Allocation DecisionChapter 7 Introduction to Cell Reselection Algorithms Based on C1 & C2Chapter 8 Introduction to BVC & MS Flow Control AlgorithmsChapter 9 Introduction to DTM & Paging Coordination FunctionChapter 10 Introduction to NACC FunctionChapter 11 Introduction to Suspend/Resume FunctionsChapter 12 Introduction to Functions & Algorithms Influencing PDTCH PlanningChapter 13 Introduction to Parameters of PDTCH–TCH ConversionChapter 14 Introduction to PreemptiveTrans Bit FunctionChapter 15 Introduction to CS Move FunctionChapter 16 Introduction to Granularity for UL Block Allocation of GPRS HandsetChapter 17 Introduction to Parameters of Maximum UL/DL Users AllowedChapter 18 Introduction to Relevant Poc Parameters Chapter 19 Quick Search for PS-related Radio Parameters

Confidential ▲

Classifications of coding mode

Initial coding mode and its dynamic adjustment

EGPRS phone quality measure mode

Interval number of Packet Downlink/Uplink

Ack/Nack

Average filter period for BEP

Uplink measure report period

Introduction to Coding Mode Adjustment Algorithms

Confidential ▲

Classifications of coding mode

Modulative

Mode

Coding scheme

modulation

RLC Blks/Radio Blk

FEC Code Rate

User bits/20

ms

bit Rate (bps)

Family

GPRS

CS-1

GMSK

1 0.45 160 8,000 -CS-2 1 0.65 240 12,000 -CS-3 1 0.75 288 14,400 -CS-4 1 1 400 20,000 -

EGPRS

MCS-1 1 0.53 176 8,800 CMCS-2 1 0.66 224 11,200 BMCS-3 1 0.85 296 14,800 AMCS-4 1 1 352 17,600 CMCS-5

8-PSK

1 0.38 448 22,400 BMCS-6 1 0.49 592 29,600 AMCS-7 2 0.76 448+448 44,800 BMCS-8 2 0.92 544+544 54,400 AMCS-9 2 1 592+592 59,200 A

Confidential ▲

Initial coding mode and its dynamic adjustment (V6.20.100e and later versions)Parameter Name

(CN)Parameter Name (EN)

Parameter Code

Range & UnitZTE

Default编码进度模型的 Cn Cn Cn 100,%(>) 85编码进度模型的 Nn Nn Nn 0 ~ 255 20编码进度模型的 Xn Xn Xn 0 ~ 100,%(>) 25

GPRS 手机缺省编码 GPRS phone init coding

　1*16 kbps ： CS1 、 CS2 ；2~4*16 kbps ：CS1 、 CS2 、 CS3 、 CS4

CS2 ， CS2

GPRS 手机缺省编码可以动态改变

GPRS phones init code can be changed

InitAttachExch_0

Yes/No Yes

EGPRS 手机缺省编码 EGPRS Phone Init Coding

　

1×16 kbps ： MCS1 、 MCS2 ；2×16 kbps ：MCS1 、 MCS2 、 MCS3 、 MCS4、 MCS5 ；3×16 kbps ：MCS1 、 MCS2 、 MCS3 、 MCS4、 MCS5 、 MCS6 ；4×16 kbps ：MCS1 、 MCS2 、 MCS3 、 MCS4、 MCS5 、 MCS6 、 MCS7 、 MCS8 、 MCS9

MCS2 ， MCS5 ， MCS6 ，MCS6

EGPRS 手机缺省编码动态改变

EGPRS phones init code can be changed

InitAttachExch_1

Yes/No YesCn 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 these

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) to

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)

Parameter Name (EN)

Parameter Code

Range & Unit ZTE Default

信令 TBF 的最高编码方式

Highest coding scheme of signal

TBFSigTBFMaxCode MCS1 ~ MCS9 MCS6

EGPRS 手机缺省编码

EGPRS Phone Init Coding

EGPRSInitAttSelt0~8 （分别对应MCS1~MCS9 ） 5,5,8,8

GPRS 手机缺省编码

GPRS init attach select

GPRSInitAttSelt0~3 （分别对应

CS1~CS4 ） 1,1,3,3

Confidential ▲


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.

Parameter Name

(CN)

Parameter Name

(EN)

Parameter Code

Range & UnitZTE

Default

EGPRS 手机的测量上报模式


LinkQuameaMode

0 ： MEAN_BEP_TNx （ 0-7 ） and I_LEVEL_TN （ 0-7 ） will not reported （ which means TBFMEAN_BEP and CV_BEP of TBF will be reported ）；1 ： only I_LEVEL_TN （ 0-7 ） will be reported ；2 ： only MEAN_BEP_TNx （ 0-7 ） will be reported ；3 ： both MEAN_BEP_TNx （ 0-7 ） and I_LEVEL_TN （ 0-7 ） will be reported.

2

Confidential ▲

Interval number of Packet Downlink/Uplink Ack/Nack

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.

Parameter Name (CN)

Parameter Name (EN)Parameter

CodeRange &

Unit

ZTE Defaul

t下行 Gprs TBF 的 RRBP 间隔块数

Interval number of GPRS TBF downlink’s RRBP

GPRSDIRrbpInterVal

3 ~ 20 10

下行 Egprs TBF 的 RRBP间隔块数

Interval number of EGPRS TBF downlink’s RRBP

EGPRSDIRrbpInterVal

6 ~ 60 10

上行 Gprs TBF 的上行应答间隔块数

Interval number of GPRS TBF uplink’s ACK

GPRSUIAckInterVal

3 ~ 20 10

上行 Egprs TBF 的上行应答每信道间隔块数

Interval number of EGPRS TBF uplink’s ACK

EGPRSUIAckInterVal

3 ~ 20 8

Confidential ▲

Average filter period for BEP

Parameter Name (CN)

Parameter Name (EN)

Parameter Code

Range & UnitZTE

Default

上行 BEP 过滤平均周期

Average filter period for uplink BEP

BEPperiodUp0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13,14, 15

4

下行 BEP 过滤平均周期

Average filter period for downlink BEP

BEPperiodDown

0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10 4

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 ▲


Parameter Name (CN)

Parameter Name (EN)

Parameter Code Range & UnitZTE

Default

上行测量报告处理周期


Ulmeasureperiod 400 ~ 2000, ms 800

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

Chapter 1 Introduction to Coding Mode Adjustment AlgorithmsChapter 2 Introduction to Link Quality Control FunctionChapter 3 Introduction to UL TBF Access Mode Chapter 4 Introduction to Window in Data TransmissionChapter 5 Introduction to Functions, Timers and Counters Related to TBF Establishment & Release Chapter 6 Introduction to EDA and Algorithms of UL/DL Timeslot Allocation DecisionChapter 7 Introduction to Cell Reselection Algorithms Based on C1 & C2Chapter 8 Introduction to BVC & MS Flow Control AlgorithmsChapter 9 Introduction to DTM & Paging Coordination FunctionChapter 10 Introduction to NACC FunctionChapter 11 Introduction to Suspend/Resume FunctionsChapter 12 Introduction to Functions & Algorithms Influencing PDTCH PlanningChapter 13 Introduction to Parameters of PDTCH–TCH ConversionChapter 14 Introduction to PreemptiveTrans Bit FunctionChapter 15 Introduction to CS Move FunctionChapter 16 Introduction to Granularity for UL Block Allocation of GPRS HandsetChapter 17 Introduction to Parameters of Maximum UL/DL Users AllowedChapter 18 Introduction to Relevant Poc Parameters Chapter 19 Quick Search for PS-related Radio Parameters

Confidential ▲

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


under IR function


without LA or IR function

Cases of LA application

Cases of IR application

Introduction to conversion algorithm from IR to LA

Relevant parameters

Introduction to Link Quality Control Function

Confidential ▲

LQC: link quality control

Link adaptation(GPRS, EGPRS)

Incremental redundancyEGPRS only

Link Quality Control

•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

Confidential ▲Introduction to selection algorithm of MCS based on BEP0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7

0 MCS_4 MCS_4 MCS_4 MCS_4 MCS_4 MCS_4 MCS_4 MCS_4 0 MCS_1 MCS_1 MCS_1 MCS_1 MCS_1 MCS_1 MCS_1 MCS_11 MCS_4 MCS_4 MCS_4 MCS_4 MCS_4 MCS_4 MCS_4 MCS_4 1 MCS_1 MCS_1 MCS_1 MCS_1 MCS_1 MCS_1 MCS_1 MCS_12 MCS_4 MCS_4 MCS_4 MCS_4 MCS_4 MCS_4 MCS_4 MCS_4 2 MCS_1 MCS_1 MCS_1 MCS_1 MCS_1 MCS_1 MCS_1 MCS_13 MCS_4 MCS_4 MCS_4 MCS_4 MCS_4 MCS_5 MCS_5 MCS_5 3 MCS_1 MCS_1 MCS_1 MCS_1 MCS_1 MCS_1 MCS_1 MCS_14 MCS_4 MCS_4 MCS_4 MCS_4 MCS_5 MCS_5 MCS_5 MCS_5 4 MCS_1 MCS_1 MCS_1 MCS_1 MCS_1 MCS_1 MCS_1 MCS_15 MCS_4 MCS_4 MCS_4 MCS_5 MCS_5 MCS_5 MCS_5 MCS_6 5 MCS_1 MCS_1 MCS_1 MCS_1 MCS_1 MCS_1 MCS_1 MCS_26 MCS_4 MCS_5 MCS_5 MCS_5 MCS_5 MCS_5 MCS_6 MCS_6 6 MCS_1 MCS_1 MCS_1 MCS_1 MCS_1 MCS_1 MCS_2 MCS_27 MCS_5 MCS_5 MCS_5 MCS_5 MCS_5 MCS_6 MCS_6 MCS_6 7 MCS_1 MCS_1 MCS_1 MCS_1 MCS_1 MCS_2 MCS_2 MCS_28 MCS_5 MCS_5 MCS_5 MCS_5 MCS_6 MCS_6 MCS_6 MCS_6 8 MCS_1 MCS_1 MCS_1 MCS_1 MCS_2 MCS_2 MCS_2 MCS_29 MCS_5 MCS_5 MCS_5 MCS_6 MCS_6 MCS_6 MCS_6 MCS_6 9 MCS_1 MCS_1 MCS_1 MCS_2 MCS_2 MCS_2 MCS_2 MCS_2

10 MCS_5 MCS_5 MCS_6 MCS_6 MCS_6 MCS_6 MCS_6 MCS_7 10 MCS_1 MCS_1 MCS_2 MCS_2 MCS_2 MCS_2 MCS_2 MCS_311 MCS_6 MCS_6 MCS_6 MCS_6 MCS_6 MCS_6 MCS_7 MCS_7 11 MCS_2 MCS_2 MCS_2 MCS_2 MCS_2 MCS_2 MCS_3 MCS_312 MCS_6 MCS_6 MCS_6 MCS_6 MCS_6 MCS_7 MCS_7 MCS_7 12 MCS_2 MCS_2 MCS_2 MCS_2 MCS_2 MCS_3 MCS_3 MCS_313 MCS_6 MCS_6 MCS_6 MCS_6 MCS_7 MCS_7 MCS_7 MCS_7 13 MCS_2 MCS_2 MCS_2 MCS_2 MCS_3 MCS_3 MCS_3 MCS_314 MCS_6 MCS_6 MCS_7 MCS_7 MCS_7 MCS_7 MCS_7 MCS_7 14 MCS_2 MCS_2 MCS_3 MCS_3 MCS_3 MCS_3 MCS_3 MCS_315 MCS_7 MCS_7 MCS_7 MCS_7 MCS_7 MCS_7 MCS_7 MCS_7 15 MCS_3 MCS_3 MCS_3 MCS_3 MCS_3 MCS_3 MCS_3 MCS_316 MCS_7 MCS_7 MCS_7 MCS_7 MCS_7 MCS_7 MCS_7 MCS_7 16 MCS_3 MCS_3 MCS_3 MCS_3 MCS_3 MCS_3 MCS_3 MCS_317 MCS_7 MCS_7 MCS_7 MCS_7 MCS_7 MCS_7 MCS_7 MCS_7 17 MCS_3 MCS_3 MCS_3 MCS_3 MCS_3 MCS_3 MCS_3 MCS_318 MCS_7 MCS_7 MCS_7 MCS_7 MCS_7 MCS_7 MCS_7 MCS_7 18 MCS_3 MCS_3 MCS_3 MCS_3 MCS_3 MCS_3 MCS_3 MCS_319 MCS_7 MCS_7 MCS_7 MCS_7 MCS_7 MCS_7 MCS_7 MCS_7 19 MCS_3 MCS_3 MCS_3 MCS_3 MCS_3 MCS_3 MCS_3 MCS_320 MCS_7 MCS_7 MCS_7 MCS_7 MCS_7 MCS_7 MCS_7 MCS_7 20 MCS_3 MCS_3 MCS_3 MCS_3 MCS_3 MCS_3 MCS_3 MCS_321 MCS_7 MCS_7 MCS_8 MCS_8 MCS_8 MCS_8 MCS_8 MCS_8 21 MCS_3 MCS_3 MCS_4 MCS_4 MCS_4 MCS_4 MCS_4 MCS_422 MCS_8 MCS_8 MCS_8 MCS_8 MCS_8 MCS_8 MCS_8 MCS_8 22 MCS_4 MCS_4 MCS_4 MCS_4 MCS_4 MCS_4 MCS_4 MCS_423 MCS_8 MCS_8 MCS_8 MCS_8 MCS_8 MCS_8 MCS_8 MCS_8 23 MCS_4 MCS_4 MCS_4 MCS_4 MCS_4 MCS_4 MCS_4 MCS_424 MCS_8 MCS_8 MCS_8 MCS_8 MCS_8 MCS_8 MCS_8 MCS_8 24 MCS_4 MCS_4 MCS_4 MCS_4 MCS_4 MCS_4 MCS_4 MCS_425 MCS_8 MCS_8 MCS_8 MCS_8 MCS_8 MCS_8 MCS_8 MCS_8 25 MCS_4 MCS_4 MCS_4 MCS_4 MCS_4 MCS_4 MCS_4 MCS_526 MCS_8 MCS_8 MCS_8 MCS_8 MCS_8 MCS_8 MCS_8 MCS_8 26 MCS_4 MCS_4 MCS_4 MCS_4 MCS_4 MCS_5 MCS_5 MCS_527 MCS_8 MCS_8 MCS_8 MCS_8 MCS_8 MCS_8 MCS_8 MCS_8 27 MCS_4 MCS_4 MCS_4 MCS_5 MCS_5 MCS_5 MCS_5 MCS_528 MCS_9 MCS_9 MCS_9 MCS_9 MCS_9 MCS_9 MCS_9 MCS_9 28 MCS_4 MCS_4 MCS_5 MCS_5 MCS_5 MCS_5 MCS_5 MCS_529 MCS_9 MCS_9 MCS_9 MCS_9 MCS_9 MCS_9 MCS_9 MCS_9 29 MCS_5 MCS_5 MCS_5 MCS_5 MCS_5 MCS_5 MCS_5 MCS_530 MCS_9 MCS_9 MCS_9 MCS_9 MCS_9 MCS_9 MCS_9 MCS_9 30 MCS_5 MCS_5 MCS_5 MCS_5 MCS_5 MCS_5 MCS_5 MCS_531 MCS_9 MCS_9 MCS_9 MCS_9 MCS_9 MCS_9 MCS_9 MCS_9 31 MCS_5 MCS_5 MCS_5 MCS_5 MCS_5 MCS_5 MCS_5 MCS_5

GMSK_CV_BEP

GMSK

MEAN

BEP

8PSK_CV_BEP

8PSK

MEAN

BEP

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 Command MCS

MCS9 MCS8 MCS7 MCS6 MCS5 MCS4 MCS3 MCS2 MCS1

Last MCS

MCS9 MCS9 MCS6 MCS6 MCS6 MCS3 MCS3 MCS3 MCS3 MCS3

MCS8 MCS8 MCS8MCS6(Pad)

MCS6(Pad)

MCS3(Pad)

MCS3(Pad)

MCS3(Pad)

MCS3(Pad)

MCS3(Pad)








Last MCS = MCS9

Command MCS = MCS5Re-trans = MCS3Example

Confidential ▲

Introduction to MCS selection algorithm during transmission under IR function

IR Command MCS

MCS9 MCS8 MCS7 MCS6 MCS5 MCS4 MCS3 MCS2 MCS1

Last MCS


MCS8 MCS8 MCS8MCS6(Pad)

MCS6(Pad)

MCS6(Pad)

MCS6(Pad)

MCS6(Pad)

MCS6(Pad)

MCS6(Pad)








Last MCS = MCS9

Command MCS = MCS5Re-trans = MCS6Example

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

MCS9 data block

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

MCS9 data block

NACK

MCS6

ACK

MCS6

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

Last MSC = MCS9

command MSC =

MCS9 according to MEAN_BEP and CV_BEP

command MSC =

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 doesn’t 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 (EN)

Parameter Code

Range & UnitZTE

Default支持上行 LA+IR 质量控制方式

Support uplink “LA+IR” quality control

IrSupportUp Yes/No No

DL default: enabled; The UL switch is displayed on the interface, but the function can not be supported

yet; the codes are being written.

Confidential ▲

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

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 PDTCH–TCH 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 AllowedChapter 18 Introduction to Relevant Poc Parameters Chapter 19 Quick Search for PS-related Radio Parameters

Confidential ▲

One-phase access & two-phase access

Introduction to EGPRS Packet Channel Request

on CCCH

Introduction to selection of access mode (two-

phase access is not forced)

Related parameters

Introduction to UL TBF access mode

Confidential ▲

Comparison between one-phase and two-phase access MS PCU

RACH

AGCH

PDTCH

EGPRS_PACKET_CHANNEL_REQUEST

IMMEDATE_ASSIGNMENT_COMMAND

DATA BLOCK

PACCH

PACCH

PACKET_RESOURCE_REQUEST

PACKET_UPLINK_ASSIGNMENT

RACH

AGCH

PDTCH


DATA BLOCK

PACKET_UPLINK_ASSIGNMENT

MS PCU

Phase 2 access Phase 1 access

Time reduce 200ms

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

AGCH

PDTCH


PACKET UPLINK ASSIGNMENT

DATA BLOCK

MS is required to be able to support

this signaling;

Compared with the common Channel

requests, this signaling carries more

information about EGPRS support

ability.

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

Purpose of the packet access procedure

EGPRS PACKET CHANNEL REQUEST supported in the cell

EGPRS PACKET CHANNEL REQUEST not supported in the cell

User data transfer – requested RLC mode = unacknowledged

EGPRS PACKET CHANNEL REQUEST with access type = 'Two-phase access'

CHANNEL REQUEST with establishment cause = 'Single block packet access' for initiation of a two-phase access

User data transfer – requested RLC mode = acknowledged and number of RLC data blocks ≤ 8 (note 1)

EGPRS PACKET CHANNEL REQUEST with access type = 'Short Access' or 'One-phase access' or 'Two-phase access'


User data transfer – requested RLC mode = acknowledged and number of RLC data blocks > 8 (note 1)

EGPRS PACKET CHANNEL REQUEST with access type = 'One-phase access' or 'Two-phase access'


Upper layer signalling transfer (e.g. page response, cell update, MM signalling, etc)

EGPRS PACKET CHANNEL REQUEST with access type = 'signalling' or CHANNEL REQUEST with establishment cause 'one-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 message

CHANNEL REQUEST with establishment cause = 'Single block packet access' (note 2)

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 (CN)

Parameter Name (EN)Paramete

r CodeRange &

UnitZTE

Default

是否强制 MS 使用两步接入方式 Two phase access

TwoPhaseAccess

Yes/No Yes

支持 EGPRS 分组信道请求接入流程

Support EGPRS packet channel request access program

EgprsPacketChreq

Yes/No No

It’s 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”.

Confidential ▲

ContentsChapter 1 Introduction to Coding Mode Adjustment Algorithms


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













Confidential ▲

Introduction to the support ability of GPRS &

EDGE service windows

Introduction to the selection of windows for ZTE

EDGE service

Introduction to the window of data transmission

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

Confidential ▲Introduction to the selection of windows for ZTE EDGE service

1 2 3 4 5 6 7 8

64 0 Min

96 1 Min

128 10 Def

160 11 Min Min

192 100 Max Def

224 101 Min

256 110 Max Def

288 111

320 1000 Min

352 1001 Def Min

384 1010 Max

416 1011

448 1100 Def

480 1101

512 1110 Max Def Min

544 1111

576 10000

608 10001

640 10010 Max Def

672 10011

704 10100 Def

736 10101

768 10110 Max

800 10111

832 11000

864 11001

896 11010 Max

928 11011

960 11100

992 11101

1024 11110 Max

Reserved 11111 x X x x x x x X

ZTE's WS 128 192 256 352 448 512 640 704

Windowsize

Coding Timeslots assigned (Multislot capability)

3GPP range

ZTE choice

Confidential ▲





Chapter 5 Introduction to Functions, Timers and Counters Related to TBF

Establishment & Release













Confidential ▲

T3168

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

Introduction to Functions, Timers and Counters Related to TBF Establishment & Release

Confidential ▲

T3168Function: 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. It’s suggested to set the timer a value between 1000ms ～ 2000ms 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.

Confidential ▲Extended uplink TBF

Rel

PCUMS

Packet UL Data Block(CV=1)


Packet Uplink Dummy Control BlockTimer


Packet UL Data Block(CV=0xff)

Packet UL Ack/Nack( FAI=1 )

Packet Control ACK

Rel

Packet UL Data Block(CV=0xff)

Packet Uplink Dummy Control Block



Expiry

When no payload is containedin Uplink Data block the PCUstarts the timer

PCU receive UL data block with payload before timer expired, Stop timer and return to normal transfer mode.

Stop Timer

When no payload is containedin Uplink Data block the PCUstarts the timer again

Timer

PCU releases the TBF when Timer expired.

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.

Confidential ▲

Uplink delay time

Rel

PCUMS



Timer

Packet Control ACK

Rel

Expiry

When no DL TBF

When Receive Dl LLC Frame

PCU release the TBF when Timer expired.

Packet uplink ack/nack(FAI=1))

Packet downlink assignment

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

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. Rel

PCU

MS

Packet DL Data Block

Packet DL Data Block(FBI = 0)

Packet DL Ack/NackTimer

Packet DL Data Block(LLC DUMMY)

Rel

When no LLC data will be sentstarts the timer

TBF is released when the timer expired.

Expiry

Packet DL Ack/Nack

Packet DL Data Block(FBI = 1)Packet DL Ack/Nack(FAI=1)

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/T3193Timer Function Start Stop

T3191

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.

After network sends a RLC data block whose Final Block Identifier

(FBI) domain is 1

1. 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

T3192 initializes the release of downlink TBF after the final data block is received. This timer is used when MS receives all RLC data blocks.

1. In acknowledged mode, the MS sends

PACKET DOWNLINK ACK/NACK message

whose FBI domain is 1.

2. In unacknowledged mode, MS sends the

PACKET CONTROL ACKNOWLEDGE message as the response for the final RLC data block.

1.It restarts when the MS sends

PACKET DOWNLINK ACK/NACK message

whose FBI domain is 1.

2. In unacknowledged mode, it restarts when MS sends PACKET CONTROL ACK message as the response for the final RLC data block.

3. It stops when MS receives PACKET DOWN LINK ASSIGNMENT message.

4. It stops when MS receives PACKET TIME SLOT RECONFIGURE

T3193

After network receives the final PACKET DOWN- LINK ACK/NACK from MS, the timer calculates the time before network reuses TFI. This timer helps the network side to confirm that T3192 expires so as to reuse the TFI.

The final PACKET DOWNLINK ACK/NACK or PACKET CONTROL ACKNOWLEDGE message is received.

1. The network establishes a new downlink TBF2. It is restarted when the final PACKET DOWNLINK ACK/NACK or PACKET CONTROL ACKNOWLEDGEMENT

message 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 (EN)

Parameter code

Range & UnitZTE

DefaultDRX 模式保护时间 DRX mode holding time DrxTimeMax

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 non-

DRX 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/T3195MS

BSS

RlacMac_T3169

N3101max..

USF=n

Release USF and TFI

USF=n

USF=n

MS

CV=0

BSS

PACKET UPLINK ACK/NACK

PACKET UPLINK ACK/NACK

PACKET CONTROL ACK

RlcMac_T3169

N3103max

.

.

CV=0

Release USF and TFI

MSBSS

RlcMac_T3195

N3105max..

Data Block（RRBP）

Release TFI

Data Block（RRBP）

Data Block（RRBP）PACK DLLINK

ACK/NACK

Counter Description of functionsN3101 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.

N3103 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)

Parameter Name (EN)

Parameter code

Range & UnitZTE

Default

N3102 减步长 N3102 decrease step PanDec4 、 8 、 12 、 16 、 20 、 24 、28 、 32

4

N3102 增步长 N3102 increase step PanInc4 、 8 、 12 、 16 、 20 、 24 、28 、 32

8

N3102 最大值 N3102 Max PanMax4 、 8 、 12 、 16 、 20 、 24 、28 、 32

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 N3102≤0, MS will implement the abnormal release of the TBF, and will trigger the cell reselection. If the configuration of PanDec ， PanInc 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

T3142

Wait for the time to initiate new packet access after IMMEDIATE

ASSIGNMENT REJECT

The timer is used during packet access on CCCH, after the receipt of an IMMEDIATE

ASSIGNMENT REJECT message.

The timer expires Initiate new packet access request.

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 receipt of the PACFKET ACCESS REJECT message, which corresponds to one of the latest three packet channel request messages

PACKET UPLINK ASSIGNMENT message is received.

MS returns to idle packet mode. The packet access in this cell is prohibited no more. But Channel Request message could not be sent as the paging 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 Name (CN)


CodeRange &

UnitZTE Default

单块指派偏移 Single Block Assign Offset SBAssOffset 6~12,block 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 (CN)

Parameter Name (EN)

Parameter Code

Range & Unit

ZTE Default

POLLING 重试次数 Polling Retry Time PollingRetryTime 3~12 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

CategoryParameter Name

(CN)Parameter Name (EN)

Parameter Code

Range & UnitZTE

Default

BSC level 支持信令上行扩展 TBFSupport signal extended uplink TBF

SIGNAL_EUTBF Yes/No No

BSC level分组下行传时 TBF 释放定时器

TBF release time of downlink transmission

T3193 0 ~ 65535, 10ms 51

BSC level TBF 释放定时器 TBF release timer T3191 0 ~ 65535, 10ms 500

BSC level上行数据块连续丢失最大允许数

MAX allowed number of continuous losses of uplink data blocks

N3101 9 ~ 255 10

BSC level分组上行确认 / 非确认重试次数

Times of packet uplink ACK/NACK retries

N3103 0 ~ 255 10

BSC level TFI 和 USF 释放定时器 TFI and USF release timer T3169 0 ~ 65535, 10ms 500

BSC level上行 RLC/MAC 控制消息连续丢失最大允许数

MAX allowed number of continuous losses of uplink RLC/MAC control message

N3105 0 ~ 255 10

BSC level无线链路失败时 TBF 保护时间

TBF protect time when radio link failure

T3195 0 ~ 65535, 10ms 500

BSC level 支持 TBF 新建流程 Support TBF establish TBF_EST Yes/No No

Cell level 支持扩展上行 TBFIs the cell support extendable uplink TBF

EXT_UTBF Yes/No Yes

Cell level 下行延迟时间 Downlink delay time DLDelaytime 500 ~ 4000, ms 2000

Cell level 扩展上行定时器 Extend uplink TBF time ExtULTBFTime 0 ~ 3000, ms 1500

Confidential ▲

Relevant parameters

CategoryParameter Name (CN)

Parameter Name (EN)

Parameter code

Range & UnitZTE

Default

Cell level N3102 减步长 N3102 decrease step

PanDec4 、 8 、 12 、 16 、 20 、24 、 28 、 32

4

Cell level N3102 增步长 N3102 increase step PanInc4 、 8 、 12 、 16 、 20 、24 、 28 、 32

8

Cell level N3102 最大值 N3102 Max PanMax4 、 8 、 12 、 16 、 20 、24 、 28 、 32

32

Cell levelDRX 模式保护时间

DRX mode holding time

DrxTimeMax 0, 1, 2, 4, 8, 16, 32, 64, s 2

Cell level T3192 T3192 T3192500, 1000, 1500, 0, 80, 120, 160, 200 ， ms

500

Cell level 上行延迟时间 Uplink delay time ULDelayTime 0 ~ 4000, ms 1000

Cell level T3168 T3168 T3168 0.5 ~ 4.0,0.5s 4

Confidential ▲





Chapter 5 Introduction to Functions, Timers and Counters Related to TBF Establishment &

Release













Confidential ▲

Introduction to EDA functions

Introduction to algorithms of uplink/downlink

timeslot allocation decision

Relevant parameters

Introduction to EDA and Algorithms of UL/DL Timeslot Allocation Decision

Confidential ▲

Advantages of EDA

USF

USF

USF

PDCH1

PDCH2

PDCH3

PDCH4

PDCH5

PDCH6

PDCH7

PDCH0

PDCH0

PDCH1

PDCH2

PDCH3

PDCH4

PDCH5

PDCH6

PDCH7

PDCH0

PDCH1

PDCH2

PDCH3

PDCH4

PDCH5

PDCH6

PDCH7

PDCH0

PDCH1

PDCH2

PDCH3

PDCH4

PDCH5

PDCH6

PDCH7

DL

DL

UL

UL

Dynamic Allocation

Extend Dynamic Allocation

Note: It is only supported by terminals of R4 or higher.

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.

Confidential ▲

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.

Introduction to algorithms of UL/DL timeslot allocation decision

Confidential ▲

Introduction to algorithms of UL/DL timeslot allocation decision

　

initial TS allocated( for Non PFC

MS)

Adjust Criteria (UL: UL data flow; DL: DL data flow)

UL + DL > = THUL + DL < TH

UL - DL >=TH/4|UL – DL| < TH/4 DL - UL >=

TH/4-

Principle 1d + 1uUL TS: MaxSum TS: Max

UL&DL TS: BalanceSum TS: Max

DL TS: MaxSum TS: Max

no adjust

Example:multislot class 12(4d + 4u < 5 Sum)EDA enabled

1d + 1u 1d + 4u 3d + 2u 4d + 1u no adjust

Example:multislot class 12(4d + 4u < 5 Sum)EDA disabled

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)

Parameter

CodeRange & Unit

ZTE Default

支持扩展上行动态分配 (Cell Level)

Support extended uplink dynamic allocation

ExUpDynSupport

Yes/No No

分组资源调整门限值 Resource adjust thresholdResourceAdjustThs

200 ~ 5000,Byte(≥) 2000

支持扩展上行动态分配 (BSC Level)

Support extended uplink dynamic allocation

ExUpDynSupport

Yes/No No

Parameter Name (CN)

Parameter Name (EN)

Parameter Code

Range & Unit

ZTE Default

支持扩展动态分配 Extend dynamic allot supported

ExtDynAssign0: support;1:not support.

0

The following parameter is already invalid:

Confidential ▲






Release













Confidential ▲

Introduction to algorithms of cell reselection

decision before and after the ready state

Introduction to attached reselection parameter

indication

Relevant parameters

Introduction to cell reselection algorithms based on c1 & c2

Confidential ▲

Introduction to algorithms of cell reselection decision before and after the ready state

Cell reselection threshold

=C2+CRH

=C1+CRO-TEO*H(PT-T)+CRH When PT<640

or

=C1-CRO+CRH When PT=640

=RXLEV-RXLEV_ACCESS_MIN-MAX(MS_TXPWR_MAX_CCH-P,O)+CRO-TEO*H(PT-T)+CRH When PT<640 or=RXLEV-RXLEV_ACCESS_MIN-MAX(MS_TXPWR_MAX_CCH-P,O)-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)

Parameter Name (EN)

Parameter code

Range & UnitZTE

Default

附加重选参数指示 attached reselection parameter indication

AdditionReselPI

No:use parameters in SI 4;Yes:use parameters in SI7/8

No

重选参数指示 Cell reselection parameter indication

CellReselPI Yes/No No

重选偏置 Reselection offset ReselOffset 0~63, 2db 0

重选滞后电平值 Cell reselecting hysteresis level

ReselHysteresis

0~7, 2db 4

临时偏置 Temporary offsetTemporaryOffset

0~7, 10db 1

惩罚时间 Penalty time PenaltyTime 0~31, 20s 0

Confidential ▲


秘密▲

The relation between BVC and MS flow control

Introduction to flow control algorithm

Introduction to flow control mode

Relevant parameters

Introduction to BVC & MS Flow Control Algorithms

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

B*=B+L(p)-(Tc-Tp)×R

LLC PDU p with length Lp reaches at time Tc

B*<Lp?

B*>Bmax?

B=L(p)

Tp=TcB=B*

yes

no

no

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 Name (CN)

Parameter Name (EN)

Parameter Code

Range & UnitZTE

DefaultBVC 流控周期 BVC flow control period CellFcPer 0 ~ 65535, 10ms 3000MS 流控周期 MS flow control period MsFcPer 0 ~ 65535, 10ms 3000支持 BVC 流控 BVC flow control supported BVCFlowCtrl Yes/No Yes支持 MS 流控 MS flow control supported MSFlowCtrl Yes/No No流控模式 Flow control mode FlowCtrlMode 1 ~ 3 1

流控模式 1 参数 Parameter of Flow control mode 1

FlowCtrlMode1Para

1 ~ 100 1

流控模式 2 参数 Parameter of Flow control mode 2

FlowCtrlMode2Para

10 ~ 1000, 100bps

214

BVC 流控 R 最小值

BVC flow control R MIN value

BVCFlowCtrlRMin

10 ~ 300, 100bps 80

MS 流控 R 最小值 MS flow control R MIN value

MSFlowCtrlRMin

10 ~ 300, 100bps 80

Parameter Name (CN)

Parameter Name (EN)

Parameter Code

Range & UnitZTE

DefaultBVC 流控门限 BVC flow control threshold CellFcThs 1 ~ 100, % 80MS 流控门限 MS flow control threshold MsFcThs 1 ~ 100, % 80

The following two parameters have been invalid:

秘密▲Contents


Confidential ▲

Introduction to DTM function

How to make MS support CS when it is transmitting data?

Relevant parameters

Introduction to DTM & Paging Coordination Function

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 (CN)


CodeRange &

UnitZTE

Default

支持 DTM Support DTM DTMSupport Yes/No No

BSC 支持 CS 联合寻呼 BSC support page coordination PagCoordination Yes/No No

GTTP Lapdm 帧最大数 Max number of GTTP Lapdm frame

GttpLapdmNum 0 ~ 7 3

Confidential ▲


秘密▲

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 MS-

controlled 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

Introduction to NACC Function

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 Management （ RIM ） 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 Name(EN)

Parameter code

RangeZTE

Default

网络辅助小区重选 NACC supported

NACCSupport

Not Support NACC;Support NACC, not LLC Frame Transfer;Support NACC and LLC Frame Transfer

Not support NACC

支持 RIM RIM support RIMSupport Yes/No No

Parameters in V6.20.200e and above:

Parameter Name (CN)

Parameter Name(EN)

Parameter code

RangeZTE

Default

网络辅助小区重选 NACC supported

NACCSupport

Yes/No No

支持 LLC 帧转移 LLC frame rerouting

LLCTRANSUPPORT

Yes/No No

支持 RIM RIM support RIMSupport Yes/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)

Parameter Name (EN)

Parameter Code

Range & UnitZTE

Default

支持 CCN 模式 CCN is allowed CCNActive Yes/No No

Confidential ▲

Introduction to (P)SI Status

Parameter Name (CN)

Parameter Name(EN)

Parameter code

RangeZTE

Default

PSI 状态支持标记 PSI status supported

PsiStatInd Yes/No No

支持系统消息状态流程 SI Status indication SIStatusInd Yes/No No

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.

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 MS- controlled cell retransmission and that under NACC

According to the above figure, after NACC is enabled, in data transmission mode, network

provides the SI1 ， SI3 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)

Parameter Name(EN)

Parameter code

RangeZTE

DefaultRIM 重试次数 RIM Retry times RIMRetryTimes 0 ~ 3 0

RIR 定时器 RIR timer TRIR 50 ~ 300,100ms 50

RI 定时器 RI timer TRI 50 ~ 300,100ms 50

RIAE 定时器 RIAE timer TRIAE 50 ~ 300,100ms 50

Confidential ▲

Introduction to network control order

Parameter Name (CN)

Parameter Name(EN)

Parameter code

RangeZTE

Default

网络控制命令 Network control order CtrlOrder NC0, NC1, NC2 NC0

NC0—MS reselects cells automatically

NC1—MS reports measurement report, and reselects cell

automatically

NC2— MS reports measurement report, and network controls cell

reselection

秘密▲Contents


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

Introduction to Suspend/Resume Functions

Confidential ▲The signaling flow of data service resumption through RAU

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.

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.

Suspend GPRS service Resume GPRS service

Confidential ▲The signaling flow of data service resumption through Resume

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.

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.

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.

Suspend GPRS service Resume GPRS service

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 ▲

Parameter Name (CN)

Parameter Name (EN)

Parameter Code

Range & UnitZTE

Default

挂起重试最大次数 MAX times of suspend retry

SuspendMax 0 ~ 10 3

恢复重试最大次数 MAX times of resume retry ResumeMax 0 ~ 10 3

挂起重试时间 Suspend retry time BssgpT3 1 ~ 100, 100ms 30恢复重试时间 Resume retry time BssgpT4 1 ~ 100, 100ms 30RESUME 设置开关 Resume set option ResumeSetOpt Open/Close Open

Relevant parameters

Confidential ▲


秘密▲

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

Introduction to Functions & Algorithms Influencing PDTCH Planning

Confidential ▲

TCH allocation strategy-from the two ends to the middle according to timeslot number

Group ATSID 0 1 2 3 4 5 6 7TsChannelComb

14 14 0 0 0 0 0 0

Group B

TSID 0 1 2 3 4 5 6 7TsChannelComb

0 0 0 0 0 0 14 14

Group C

TSID 0 1 2 3 4 5 6 7TsChannelComb

0 0 0 14 14 0 0 0

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.

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 ▲


PDCH type EDGE exclusion(EE)

EDGE preference(EP)

Non preference(NP)

GPRS preference(GP)

Static √ √ √ √

Dynamic × √ √ √

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.

Confidential ▲


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

1

23

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.

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 TRXObjective

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)

Parameter Name (EN)

Parameter Code

Range & Unit ZTE Default

支持 PS 业务抢占 CS 业务 Support PS Prmp CS PSPrmpCSSupport Yes/No No

动态时隙 Dynamic ts 　 Yes/No Yes

信道分组业务优选属性 Ps Service Preference property

　

No preference, GPRS preference, EDGE preference, EDGE specialty

No preference

PDCH 优先属性 PDCH Priority PDCHPrecedence Yes/No No

支持用户占用非本类优选信道

Support of subscriber occupying other preference channel

HybridOccuSupp Yes/No Yes

支持用户迁移出非本类优选信道

Support of PS subscriber moving out of other preference channel

AllowPsMove Yes/No No

同类占用阈值 Congeneric service threshold for PS-moving

SfPreferBusyThs 0~100, %(≥ ) 100

异类占用阈值 Un-congeneric service threshold for PS-moving

OpPreferBusyThs 0~100, %(≥ ) 0

载频 PS 业务繁忙度阈值 TRX PS busy threshold TrxPSBusyThs(<) 1 ~ 6400 900

Confidential ▲






Release













Confidential ▲

Introduction to Parameters of PDTCH–TCH Conversion

Parameter Name (CN)

Parameter Name (EN)

Parameter Code

Range & UnitZTE

Default

空闲 CS 信道数门限

Minimal number of idle CS channel

CsChansThs 0 ~ 255(≥ ) 2

PS 信道延时回收释放定时器

PS channel delay release timer

PSRelDelay 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.

Confidential ▲






Release













Confidential ▲

Introduction to PreemptiveTrans Bit Function

Parameter Name (CN)

Parameter Name (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.

Confidential ▲






Release













Confidential ▲

Introduction to CS Move Function

Parameter Name (CN)


CodeRange & Unit

ZTE Default

支持 CS 用户迁移

Support of CS subscriber moving Access Persist Level

AllowCsMove Yes/No 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.

Confidential ▲






Release













Confidential ▲

Introduction to Granularity for UL Block Allocation of GPRS Handset

Parameter Name (CN)

Parameter Name (EN)

Parameter Code

Range & UnitZTE

Default

GPRS 手机上行块分配时选择的粒度

Selective granularity

USFGranularity

0 ~ 1(0: uplink block allocation granularity is 1; 1: uplink block allocation granularity is 4)

0

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.

Confidential ▲






Release













Confidential ▲

Introduction to Parameters of Maximum UL/DL Users Allowed

Parameter Name (CN)

Parameter Name (EN)


Default

单无线时隙最大容纳的PS 上行用户数

Maximum PS uplink user per ts

MaxPsUserPerTs_0 2 ~ 8 4

单无线时隙最大容纳的PS 下行用户数

Maximum PS downlink user per ts

MaxPsUserPerTs_1 2 ~ 16 6

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.

Confidential ▲






Release













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.

wanghangyan

Confidential ▲

Relevant parameters

Category Parameter Name (CN) Parameter Name (EN) Parameter code Range & Unit ZTE Default

BSC level 支持 PoC 业务优化 Optimized PoC service support

POCSUPPORT Yes/No No

BSC level共享上行 POC 信道PoC 业务用户数上限

Maximal users of POC service on

shared PS channel 0

PSCAPATHS_UL

2 ～ 6 3

BSC level共享下行 POC 信道PoC 业务用户数上限

Maximal users of POC service on

shared PS channel 1

PSCAPATHS_DL

2 ～ 6 3

BSC levelGPRS 下 POC 业务最

高编码方式

Highest coding scheme of POC

service in GPRS PocAttSelt_0

CS1 、 CS2 、 CS3、 CS4

CS3

BSC levelEDGE 下 POC 业务最

高编码方式

Highest coding scheme of POC

service in EGPRS PocAttSelt_1 MCS1 ~ MCS9 MCS6

Cell level POC 使用资源上限 Maximal resource for POC service

POCSrcThs 0~100,% 50

Confidential ▲






Release













Confidential ▲

A fast check of radio parameters related to PS service

A fast check of radio parameters related

Documents

GSM Training Materials for Special Subjects--Optimization of PS Radio Parameters_R2