Internal Use Only

(E)GPRS Radio Network Optimization

Work Guidebook

Version: 1.0

Released by:

GSM Network Planning & Optimization Dept.

Engineering Service Division
ZTE Corporation

This document contains proprietary information of ZTE Corporation and is not to be disclosed or used
except in accordance with applicable agreements.

Internal Use Only

Guidebook
for GSM Networking Planning & Optimization

Version Introduction
Version
V1.0

Date

Writer

2008-11-15

Bo Zongjun

Assessor
Hou Shuai

Amendment record
None

This document contains proprietary information of ZTE Corporation and is not to be disclosed or used
except in accordance with applicable agreements.

Internal Use Only

Contents
1

Introduction..........................................................................................................................................1

Overview of Optimization...................................................................................................................2
2.1

(E)GPRS network structure...............................................................................................................2

2.2

Features of data optimization............................................................................................................3

Optimization Flow...............................................................................................................................6
3.1

3.2

Network evaluation...........................................................................................................................6
3.1.1

Set up service mode.................................................................................................................7

3.1.2

Check warning system.............................................................................................................9

3.1.3

Check data and settings...........................................................................................................9

3.1.4

Load evaluation.....................................................................................................................12

3.1.5

On-site test.............................................................................................................................15

Network optimization......................................................................................................................15
3.2.1

Optimization flow..................................................................................................................15

3.2.2

System optimization..............................................................................................................16

3.2.3

On-site test optimization.......................................................................................................27

Work Plan of GSM Packet Service Team& Field Feedback.........................................................38

This document contains proprietary information of ZTE Corporation and is not to be disclosed or used
except in accordance with applicable agreements.

Internal Use Only

1 Introduction
As data services are continually developing, network operators have gradually raised
higher requirements on data network. In the real network optimization, we have started
to encounter needs of (E) GPRS optimization. With the aim to meet new requirements
and help engineers grasp thoughts of data optimization and improve their skills and
abilities to solve related problems on the basis of their mastering GSM optimization
knowledge, in this guidebook mainly introduced is regular data optimization
knowledge.

This document contains proprietary information of ZTE Corporation and is not to be disclosed or used
except in accordance with applicable agreements.
1

Internal Use Only

2 Overview of Optimization
2.1 (E)GPRS network structure

Picture 2-1 EGPRS network structure

(E)GPRS network is based on GSM network, and their operating mechanism is

basically the same in terms of UM interface and BSS:

At UM gateway, BTU of (E)GPRS is wireless data block, and each block is made
up of four TDMA frames. TCH frame, which transmits voice service, consists of
26 TSMA frames; PDCH frame, which transmits data service, consists of 52
TDMA frames. (E)GPRS just reorganizes the TDMA frames with different coding
and modulation/demodulation methods. As for protocols, (E)GPRS follows the
low layer protocols of voice service.

At BSS in (E) GPRS, two modules are added on the basis of GSM network, which
are CCU(channel coding unit) and PCU(packet control unit). CCU is integrated in
BTS and PCU in BSC. In fact, PCU is equivalent to BSC in voice service; and air
interface data is transmitted transparently before it reaches PCU.

(E)GPRS follows the low layer protocols of voice service. Packet service owns a
set of independent system (including parameters, signaling flow, logic channels,

This document contains proprietary information of ZTE Corporation and is not to be disclosed or used
except in accordance with applicable agreements.
2

Internal Use Only

etc..), but its current reselection algorithm is very much alike that of circuit
service, and it shares CCCH with circuit service.
In sum, data optimization is similar to voice optimization to a great degree, so its
very easy to master data optimization with the basis of voice service optimization
ability. The differences between them are focused in this guidebook.

2.2 Features of data optimization

Compared with voice service, data service owns the following features:

Higher requirements on radio environment: for all networks, radio

environment quality can never be good enough, as it were; and for (E)GPRS,
higher requirement on radio environment is more obvious;

This document contains proprietary information of ZTE Corporation and is not to be disclosed or used
except in accordance with applicable agreements.
3

Internal Use Only

Picture 2-2 Relational graph of EDGE carrier-to-interference ratio and throughput

Picture 2-3 Relational graph of GPRS carrier-to-interference ratio and throughput

Higher demand on resources: that subscribers enjoy high-speed data service and
one subscriber can use more than one channel at the same time is desirable, but it
inevitably means further improvement in the whole system resources and a series
of problems accompanying with the huge improvement project. At air interface,
the lack of frequency resource has seriously tied the development of (E)GPRS.
Besides, data service brings new signaling traffic. Therefore, reasonable
distribution of resources and avoiding contest of channels between data service
and voice service has become a new subject to be cracked.

This document contains proprietary information of ZTE Corporation and is not to be disclosed or used
except in accordance with applicable agreements.
4

Internal Use Only

More complicated mechanism: because data service adopts packet transmission

mechanism, one subscriber can use more than one channel and one channel can be
used by more than one subscriber. The flexible resource management method
results in lower operability. What's more, different radio environments take along
different band width, plus the defects in measurement report, it is rather difficult
to get the actual on-site situations from OMCR.

Terrible reselection mechanism: because of the immanent defects in GSM

system, for data service with cell reselection but handovers, its inevitable that
transmission breaks off at each time of cell reselection, which has serious
influence on Drive Test.

Radio side is inclined to be affected by CN and external network: the essence

of data network is to connect MS with Internet or other networks like WAP
through GSM. Once something goes wrong with the external network or CN,
radio side will be affected greatly.
From the aspects listed above, we can see that optimization of data service is more

complicated that that of voice service. The development time of data service is not
long, its system and mechanism are not perfect, and its subscribers are not as stable as
those of voice service, so well definitely meet much more difficulties in the
optimization of data service. But, from its development trend, we can see data service
will play an important role in mobile communication market. Hope the optimization
methods of data service will gradually be completed through our efforts.

This document contains proprietary information of ZTE Corporation and is not to be disclosed or used
except in accordance with applicable agreements.
5

Internal Use Only

3 Optimization Flow
Flow of (E)GPRS optimization is the same as that of voice service, as shown bellow:

Network
evaluation

Network
optimization

Inspection &
acceptance

3.1 Network evaluation

Compared with voice optimization, network evaluation is of great importance in data
optimization, reasons for which are as follows:

Compared with voice service, the mode of data service is more complicated and
unstable. Poor grasp of its features will result in bad effects on its optimization.

Most network operators are not familiar with data service optimization, and there
tend to be deviation in settings of basic parameters. If the deviations can not be
adjusted in time, unfavorable effects will occur in the following optimization
work.

The work load of data service test is heavy, and requirements on test quality are
higher, thus we should make detailed test plans, so as to lay a good foundation for
the following optimization work.

Concrete contents of network evaluation are as follows:

Network evaluation

Service mode setup

Warning checking

Load evaluation

On-site testing

3.1.1 Set up service mode

Setup of packet service mode falls into the following parts:
This document contains proprietary information of ZTE Corporation and is not to be disclosed or used
except in accordance with applicable agreements.
6

Internal Use Only

3.1.1.1

Define busy hours

As for PS service, there may exist two busy hour periods in the system: busy hour of
TBF set-up times and busy hour of data traffic. The reason for this situation is that
currently there are not many subscribers of PS service, and most of TBF set-up is for
routing location update but data traffic. Therefore, because of heavier call traffic and
faster subscriber movement, great number of TBF without subscriber data traffic will
set up in busy hours; while due to great number of multimedia message subscribers,
TBF doesnt set up many times at night, but the data traffic is high. As for access KPI,
its examination time period shall be the busy hours of TBF set-up; as for KPIs, such as
retransmission rate, etc., its examination time period shall be the busy hours of data
traffic.
Some operators will propose precise time periods for examination of different KPIs,
which varies in different locations.
Reference indicators:
Indicator

UL TBF Establishment
times

iBSC
C100010159+C100010160+C1000101

C70042+ C70055+ C70069

61+C100010168+C100010163+C100010
164+C100010165+C100010166

UL TBF Establishment
times

3.1.1.2

v2BSC

C100010141+C100010142+C1000101
C70043+ C70057+ C70071

43+C100010144+C100010145+C100010
146+C100010147+C100010148

UL data throughput

C70050

C100010057

DL data throughput

C70049

C100010056

Define busy areas

Distribution of PS is unbalanced not only in terms of time, but also in areas. Currently,
the main subscriber groups and areas of PS are: students, high-class office buildings
and hotels, and airports, etc., which we can tell from data traffic, therefore, we should
pay more attention to these key areas.
Reference indicators:
Indicator

v2BSC

iBSC

UL data throughput

C70050

C100010057

DL data throughput

C70049

C100010056

This document contains proprietary information of ZTE Corporation and is not to be disclosed or used
except in accordance with applicable agreements.
7

Internal Use Only

3.1.1.3

Observe developing trend of business volume

Service volume and data traffic may change dramatically even increase over times
along with the development in PS, which will have influence upon TBF set-up success
rate, network band width and retransmission rate. Complete understanding of historical
data will contribute to a precise evaluation of the following optimization work.
Reference indicators:
Indicator

v2BSC

iBSC

UL data throughput

C70065+ C70079

C100010062+ C100010070

DL data throughput

C70067+ C70081

C100010064+ C100010072

3.1.1.4

Define EDGE penetration rate

EDGE penetration rate is of great importance in EDGE optimization. Proportion of
EDGE subscribers varies in different areas, and this proportion may change along with
market development, which shall be taken into consideration when we adjusting EDGE
parameters.
EDGE penetration rate is defined as proportion of MS supporting EDGE. The defining
method is as follows:
Indicators

v2BSC

iBSC
C100010164+C100010165+C1000101

UL

EDGE

TBF

establishment rate

66/
C70069/( C70055+ C70069)

(C100010159+C100010160+C10001016
1+C100010163+C100010164+C1000101
65+C100010166+C100010168)
C100010145+C100010146+C1000101

DL

EDGE

TBF

establishment rate

47+C100010148/
C70071/( C70057+ C70071)

(C100010141+C100010142+C10001014
3+C100010144+C100010145+C1000101
46+C100010147+C100010148)

UL GPRS Data TBF

Share
DL GPRS Data TBF
Share

C70079/(C70065+ C70079)
C70081/(C70067+ C70081)

C100010070/(C100010062+
C100010070)
C100010072/(C100010064+
C100010072)

This document contains proprietary information of ZTE Corporation and is not to be disclosed or used
except in accordance with applicable agreements.
8

Internal Use Only

3.1.2 Check warning system
Check warnings and notices of all equipment before optimization. As for PS, we shall
make primary observation of BVC restoration and obstruction in addition to normal
checking. Make sure that all warnings and notices are cleared before optimization.
Checking and notification method of warning is illustrated in the attachment:

Checking &
notification method of warning.doc

3.1.3 Check data and settings

Check if parameter of CS subscriber movement( AllowCSMove) is closed;

CS subscriber movement ( AllowCSMove) is to switch some CS subscribers to other

timeslots through in-cell handovers, so as to centralize PS timeslots and improve usage
rate of PS resource. While currently this parameter can not function yet, so it has to be
closed.

Check if all cells keep GPRS function open(PsSupprt supported in V2;

PSSupport supported in V3)

Measurement report mode of EGPRS LinkQuaMeaModehas to

be set 0 and be reported according to TBF, or MS wont report
MEAN_BEP and CV_BEP values;

EDGE MS has two report modes:

report per timeslot

Parameters reported per timeslot by EGPRS MS include:

MEAN_BEP_TNx0-7and I_LEVEL_TN0-7

report per TBF

Parameters reported per TBF by EGPRS MS include:

MEAN_BEP and CV_BEP
In report mode, 0 means report per TBF, 1~3 means report per timeslot. Currently in
report per timeslot, omission of report occurs at some terminals, which seriously affects
adjustment of coding mode, so it is suggested that the two report modes be applied
simultaneously.
This document contains proprietary information of ZTE Corporation and is not to be disclosed or used
except in accordance with applicable agreements.
9

Internal Use Only

Each cell must be configured with at least one static PDCH; and complete
dynamic configuration is not allowed;

We shall try to make PDCHs in one cell consecutive, since its stipulated in
relevant protocol that the multi channels occupied by MS must be consecutive. If
channels are not consecutive, MS may not be able to take them even when there
are enough channels. Currently, multi-timeslot ability of MS mainly falls into
4+1 and 4+2 modes, so when assigning channels, we should try to make 4
consecutive channels as a unit. If 8 channels are to be assigned, a complete TRX is
to be occupied; or we can assign them on two TRXs in the mode of 4+4. Try to
avoid 6+2 or 7+1.

TSC of all PDCH timeslots in one cell must be the same as BCC, including
dynamic and static channels;

The ordering function must be open, if there are dynamic PDCHs (MSC needs to
support and open line-up function of TCH assignment; and value of timer at BSC
should be smaller than that of timer at MSC), therefore we can prevent TCH from
seizing dynamic PDCH.

Checking method
of channel configuration.doc

Flow control mode (BSC level)

BVC flow control proceeds at the Gb gateway between SGSN and BSS, and the control
is carried out only on DL by SGSN with parameters provided by BSS; it is used to
avoid one BVC busy with classifying channels (too much cache memory of LLC
frame), which will result in abandonment of some LLC data (data stored in cache
memory beyond a certain time will be abandoned), and to avoid restriction on memory
(cache memory of LLC frame overflows), which will abandon DL LLC data.
BSSGP at BSS periodically counts the current BVC leak rate and anticipates the
funnel size needed for transmitting new data; if the anticipated funnel size exceeds the
max allowed by BSC, flow control shall be started.
Flow control can keep network operating normally in congestion period and prevent
loss of LLC and retransmission caused by congestion, so it shall be kept open.

This document contains proprietary information of ZTE Corporation and is not to be disclosed or used
except in accordance with applicable agreements.
10

Internal Use Only

As for the BVC of SGSN equipment manufactured by HuaWei and Motorola, their
flow control mode must be 2; as for those from other suppliers, there is no restriction
(usually the BVC is 1).
Here is a sectional drawing of flow control parameters:

Flow control
paramters.doc

DL polling times (BSC level)

DL polling timesPollTimemust be 7.
The system makes TA update in PS through polling. If MS fails to respond to polling
with certain times, abnormal TBF release will be resulted.
PollTime is the max retransmission times of DL polling. It is related to paging period.
After Packet Polling Request is sent, network will release DL assignment information
regardless whether MS makes response or not. DL assignment is sent on paging
module of CCCH; normally the paging period is 5, which means there is only one
chance of sending assignment information for 5 continuous 51 multi-frames. The max
waiting time is 5*51*4.615=1176ms, which is about 6 times of polling.
Note: DL PollTime is only applicable to V2BSC; it is fixed to be 7 in IBSC, and it is
the same as that in V2BSC.

Number of frame number adjustment (cell level)

There are two main reasons for frame number adjustment

1. Faults with Abis link or the interconnection equipment at link ends need to be
cleared out;
2. Channels without frame numbers resulted from wrong connection information.
This can be solved through restoring the connection equipment between BTS (and
BSC) and T network.
Reference indicators:
Indicator
Total number of UL packet channel
frame number adjustment
Total number of DL packet channel

v2BSC

iBSC

C70038

C100110006

C70039

C100110007

This document contains proprietary information of ZTE Corporation and is not to be disclosed or used
except in accordance with applicable agreements.
11

Internal Use Only

frame number adjustment

3.1.4 Load evaluation

3.1.4.1

Radio channel evaluation

3.1.4.1.1 Step 1: PS channel planning based on Campbell algorithm

1Input cell configuration information-EGPRS template data.
EGPRS template is as follows:

Cell
configuration(EGPRS) template.xls

General cares for filling in template:

1)

The number of cell service channels is the sum of voice

service channels and data service channels.

2)

CS1 usage rate is the rate of CS1 data traffic at busy hours
to total data traffic; the rate value shall be >0, but <1. Usage
rates of CS2CS4MCS1MCS9 are defined in the same way.

3)

Sum of the usage rates of CS1CS4MCS1MCS9 shall be 1.

4)

The Excel table format for filling usage rates of CS1CS4MCS1

MCS9 and retransmission rate shall be suitable for numerical
values, in case of program misreading.

5)

Operators can fill in the template referring to the demonstration

data.

2: Open http://tools.cmdi.chinamobile.com/campell, after registration

enter EGPRS radio channel configuration software, select EGPRS radio
channel calculation, and fill in it step by step, then export PS
channel planning result.
3.1.4.1.2 Step 2: PS channel optimization based on max UL&DL TBF number
Take PS basic measurement of 7*24 hours, and take the max UL&DL
TBF number in it, and calculate the biggest value of max TBF using CI
as index, then respectively get divided by PS channel planning result
(obtained through Campbell algorithm in Step 1) to get the max TBF
number per channel of the same time. Its suggested that this value
is smaller than 2TBF/PDTCH; if it goes beyond 2TBF/PDTCH, after

This document contains proprietary information of ZTE Corporation and is not to be disclosed or used
except in accordance with applicable agreements.
12

Internal Use Only

confirming there is no burst situations within some 15 minutes,
optimize PS channels as per channel owning max TBF/2.
3.1.4.1.3 Step 3: Re-optimization of PS channel in TCH-congested cells
As for BTSs lacking of PS resources caused by TCH congestion, make
traffic sharing for cells suitable for it; for cells taking no traffic
sharing, open HR or re-plan the cells PS channels according to Step
1.
3.1.4.2

PCU load evaluation

V2BSC

One BRP board can process 40 PDCHs (dynamic+static), and one EBRP board can
process 160 PDCHs (dynamic+static), and usually its usage rate is 5075%.

iBSC

Operator processing unit, which is made up of UPPB board.

Each UPPB board consists of 14 DSPs, and each DSP can maximumly configure for 80
cells and process 160 Abis timeslots of 16kbps; number of PDTCH processed depends
on nature of the channels:
160 channels, which only support CS1CS2 (each channel uses one 16kbps Abis
timeslot);
80 channels, which support CS3CS4 (each channel uses two 16kbps Abis timeslots);
40 channels, which support MCS9 (each channel uses four 16kbps Abis timeslots);
When access by IP Abis, number of channels is the same as those listed above.
Precise evaluation methods are shown bellow:

PCU load
PCU load
IBSC&UPPB
calculation-iBSC.doc
calculation-2BSC.doc
configuration.doc

3.1.4.3

Abis timeslot assignment

Coding speed

Theoretical application layer throughputkps

Number Abis timeslots needed

CS1

CS2

12

This document contains proprietary information of ZTE Corporation and is not to be disclosed or used
except in accordance with applicable agreements.
13

Internal Use Only

CS3

14.4

CS4

20

MCS1

8.8

MCS2

11.2

MCS3

14.8

MCS4

17.6

MCS5

22.4

MCS6

29.6

MCS7

44.8

MCS8

54.4

MCS9

59.2

V2BSC-5
IBSC-4
V2BSC-5
IBSC-4

With adoption of dynamic auxiliary timeslot number, the total number of timeslots in a
BTS can be adjusted appropriately according to actual situations. Given that cells under
one BTS wont bear high load simultaneously, the following suggestions can be
referred to.
No. of cells under

Total timeslots

BTS
1

Number of timeslots needed in a cell

Total number of timeslots needed in

all cells*0.8

Total number of timeslots needed in

all cells*0.6

3.1.5 On-site test

PS test task is heavy and there are more issues deserving our attention. In order to
ensure the validity of data collected through the evaluation test, please read the related
materials in 5.1 Training\GPRS service test on the FTP server of Test Dept.

Try to conduct test at busy hours;

If its EDGE test, please clearly examine the model of test phone, because mobile
phones vary in their supportive ability to new functions of EDGE. SAGEM
OT498 is recommended for the test, which supports the latest protocol R4 and
owns ability to test UL TBF espansion and other new features like NACC.

This document contains proprietary information of ZTE Corporation and is not to be disclosed or used
except in accordance with applicable agreements.
14

Internal Use Only

Operators approval for test software must be obtained, because different kinds of
test software will bring different test results (FLASHGET is recommended for
testing FTP).

Before DT starts, make sure test vehicle speed in urban is no faster than 40km/h,
and on highway no slower than 70km/h; and try to keep the speed in retest the
same as in the first test.

Before test starts, choose a stable FTP server and WAP webpage, and keep using
them thereafter (change the download file if the webpage changes);

Before test starts, close all irrelevant software in case of influence on band width
(eg. Windows firewall, auto-update, and other software which may take band
width).

Try to use test software's own FTP download software. If its not available, we
recommend cute FTP.

3.2 Network optimization

3.2.1 Optimization flow
Main optimization flow:

Data
collection

Data
analysis

Data
adjustment
The basic optimization flow of GPRS is almost the same as that of CS. Currently the
difference between the two is that PS service mode is not stable, which requires
collection of enough data and more careful analysis. Besides, radio side of PS will
receive interference from CN and external networks like internet, so we need to
exclude external factors through analysis when judging problems.
This document contains proprietary information of ZTE Corporation and is not to be disclosed or used
except in accordance with applicable agreements.
15

Internal Use Only

3.2.2 System optimization
Compared with CS optimization, PS optimization involves fewer KPIs, which are as
follows:
3.2.2.1

UL/DL TBF link establishment success rate

3.2.2.1.1 Formula
iBSC UL TBF link establishment success rate=
(C100010025+C100010033+C100010026+C100010034)*100%/
(C100010159+C100010160+C100010161+C100010168+C100010163+C100010164+
C100010165+C100010166)
v2BSC UL TBF link establishment success rate = C70042+C70055+C70069 /
C70040100
iBSC DL TBF link establishment success rate =
(C100010007+C100010015+C100010008+C100010016)*100%/
(C100010141+C100010142+C100010143+C100010144+C100010145+C100010146+
C100010147+C100010148)
v2BSC DL TBF link establishment success rate = C70043+C70057+C70071 /
C70041100
3.2.2.1.2 Illustration on judgment
Judgment on bad cell:
If
UL/DL TBF setup success rate<80%;
and whole network UL/DL TBF setup success rate>90%;
we judge the cell is good.
Note: UL/DL TBF setup request shall be no less than 50 times. If the request times is
too few, we can prolong the statistical time period or add statistical times.
Main influence factors:
Terrible radio environment, including weak coverage and interference; we can optimize
the radio environment accordingly.

This document contains proprietary information of ZTE Corporation and is not to be disclosed or used
except in accordance with applicable agreements.
16

Internal Use Only

Settings of parameters, such as parameter T3168, line-up parameter is on/off, setting of
UL/DL TBF per channel is correct/incorrect.
Stability of equipment and transmission, like frequent breaks caused by high
transmission code error rate or unstable link.
Usability of data service functions, such as halt of single board CPU caused by burst
traffic volume.
When TBF link setup rate >10%, main causes of failure link setup may be: bad radio
environment, serious interference, link code error, frame number adjustment.
When TBF link setup rate <10%, main causes of failure link setup may be: link fault,
communication fault between boards, abnormal channels.
3.2.2.1.3 Adjustment methods

Observe channel status

Before starting analysis, check PDCH status in dynamic management. If PDCH is

found closed, take the following procedures:
1. close PDCH manually, open BVC;
2. restore EBRP/BRP or UPPB;
3. if the above doesnt work, deliver the recorded and printed signaling to technical
support for solution.

About frame number adjustment

This frame is PCU frame, which is the frame structure transmitted at Abis. Usually
problems happen to Abis link and the interconnection equipment of link ends.
Moderate frame number adjustment is normal, which may be caused by link code error
or sliding poise. If large quantity of adjustment is found, take the following procedures:
1. check if transmission warning exists;
2. restore EBRP or UPPB.

About channel without frame number (V2BSC)

During the check within 1 minute, if Ebrp hasnt received any UL data from bts or
it hasnt send any data, this is regarded as channel without frame number.
To handle channel without frame number, collect the following data:
This document contains proprietary information of ZTE Corporation and is not to be disclosed or used
except in accordance with applicable agreements.
17

Internal Use Only

1. whether its accompanied by other blockings;
2. whether the channel without frame number can automatically recover; usually
automatic recovery time is about 2 minutes; if it doesnt recover in 5 minutes, we
can basically confirm it's not able to recover automatically;
3. find out the unrecoverable channel without frame number is of BSC level or cell
level or channel level;
4. find out the unrecoverable channel without frame number is on ebrp or brp;
5. whether the channel without frame number can recover the next day.
Handle the unrecoverable channel without frame number according to the following
principles:
1. Conduct the following examination, if no data is received;
Problem with bts: check the link;
Connection problem: compare data in OMCR and BSC;
Hardware problem: check if single board in abnormal condition
2. Conduct the following examination, if DL transmission fails.
Any problems with dsp reading/writing at hpi?
Any connection errors?
3. Change channel type; transpose the master and standby of cmm; restore brp and
puc. Try to make these changes in service-idle hours.

Check if GB link has problems

Check NS layer signaling. Check if Gb interface is unobstructed. If PCU hasnt

received SGSN acknowledgement message, we need to further check physical link at
Gb interface and SGSN data configuration.

Confirm channel resource is enough before analysis

Refer to 3.1.4.1

Radio environment optimization

Judge radio environment according to the following methods:

Quality handover rate in voice service;

This document contains proprietary information of ZTE Corporation and is not to be disclosed or used
except in accordance with applicable agreements.
18

Internal Use Only

Retransmission rate;

Rate of data throughput of each code to total data throughput;

Trace measurement report of PACKET UL/DL ACK at UM interface through

signaling

TBF setup failure resulted from overmany TBF setup times

Adjust CRH and CRO. If adjustment fails, re-plan RAC and LAC.
Adjustment on CRO and CRH is shown bellow
As for PS, slow reselection tend to result in bad radio environment and cause
reselection times to increase and coding speed to decrease. MS releases TBF and resetups link each time of reselection, and traffic is 0 during this process; if there are too
many times of reselection, PS performance will be influenced. Adjustment on CRO and
CRH shall be focused on reselection times. A balance point between radio environment
and reselection times shall be reached.
Because CRO's influence on CS is more powerful, currently we focus on adjustment on
CRH. Suggested value of CRH is 8-14.

CS cell
reselection mechanism.doc

Boundary division of LAC shall be in accordance with the following principles:

1.

Try NOT to set location area boundaries in urban center where call traffic volume
is high. Set the boundaries in suburb or plants where call traffic volume is low and
low-end subscribers are more. In these areas there are fewer cells and MS location
changes in a smaller scope, and the burden to network caused by cross-boundary
location change is relatively smaller. When busy urban area is unavoidable, try to
set location boundaries in residential quarters or areas where MS moves less.

2.

Set location boundaries vertical or in skew intersection with roads, try to avoid
overlapped location areas in high MS-mobility regions, so as to avoid large
quantity of Pingpong location changes and Pingpong handovers as MS crossing
location areas. If the location boundaries are not set correct, there will be great
impact on the system.

This document contains proprietary information of ZTE Corporation and is not to be disclosed or used
except in accordance with applicable agreements.
19

Internal Use Only

3.

Try to avoid setting several location boundaries in a small area, which will help
reduce MS location changes and handovers among several location areas.

4.

When setting location area boundaries, we also need to consider the trend of
traffic increase. In designing location area paging capacity and traffic capacity, we
shall consider certain amount of expansion margin, so as to avoid frequent
division of location areas.

T3168

Description: T3168 is used to set the time length of MS waiting for packet UL
assignment information. After sending out PACKET RESOURCE REQUEST, MS
enters PACKET UPLINK ASSIGNMENT; or when MS sends out PACKET
CONTROL ACKNOWLEDGEMENT applying for new TBF, T3168 starts. T3168
decides when to stop waiting for packet UL assignment information. When the timer
overtimes,

MS

restarts

packet

access

process

until

PACKET CONTROL

ACKNOWLEDGEMENT has been sent four times and TBF setup is shown as failure,
report to upper layer the RLC/MAC errors.
Value: 07
Explanation: Value of T3168 can affect TBF setup success rate. The smaller it is, the
less time is provided for TBF setup, and the lower TBF setup success rate will be,
especially when radio environment is bad; the larger it is, the longer period MS will
need to judge TBF setup failure, and time delay of packet access will be longer, and
system performance will decrease accordingly. When setting T3168 value, we must
consider radio environment, which is BLER. Usually we can take the following as
reference:

BLER<2%, excellent radio environmentT3168 can be set 500ms

2%<BLER<5%good radio environmentT3168 can be set 1000ms

5<BLER<10%bad radio environmentT3168 can be set 2000ms

Open CS line-up function

When CS is busy, it is possible that CS grabs dynamic PDCH, which will result in
forced abruption of service on dynamic PDCH. CS line-up function can greatly reduce
the possibility of this problem.

This document contains proprietary information of ZTE Corporation and is not to be disclosed or used
except in accordance with applicable agreements.
20

Internal Use Only

In the meantime, check if the line-up function at BSC and MSC is open; and if the
line-up time at MSC is shorter than that at BSC, we take that at MSC as criterion.

Max number of UL/DL subscribers taken by single radio timeslot

(MaxPsUserPerTs_0/1)

Maximumly, PS can support 7 UL subscribers, 6 DL subscribers. The UL default value

of PS subscribers taken by single radio timeslot is 4, DL 6. Increase in max number of
subscribers can improve access performance. But when there are many subscribers on
one timeslot, the speed for all of them will be extremely slow. Therefore, the optimum
value of the two parameters shall be the minimum one on the premise that access is
ensured. Usually they are set slightly larger than the default values. We suggest UL 7,
DL 12, but the minimum shall not be smaller than the default value.
3.2.2.2

Retransmission rate

3.2.2.2.1 Formula
v2BSC
C70066/ C70065100

GPRS RLC UL block retransmission rate;

C70068/ C70067100

GPRS RLC DL block retransmission rate;

C70080/ C70079100

EGPRS RLC UL block retransmission rate;

C70082/ C70081100

EGPRS RLC DL block retransmission rate;

iBSC
C100010063*100%/C100010062 GPRS RLC UL block retransmission rate;
C100010065*100%/C100010064 GPRS RLC DL block retransmission rate;
C100010071*100%/C100010070 EGPRS RLC UL block retransmission rate;
C100010073*100%/C100010072 EGPRS RLC DL block retransmission rate;
3.2.2.2.2 Explanation on judgment
Judgment of bad cells:
GPRS retransmission rate >10%
EGPRS retransmission rate >10%
Main influence factors:
This document contains proprietary information of ZTE Corporation and is not to be disclosed or used
except in accordance with applicable agreements.
21

Internal Use Only

Terrible radio environment, including weak coverage and interference; need to
optimize radio environment.
Stability of equipment and transmission, like abrupt discontinuity caused by high
transmission code error rate or unstable link.
About bad cells: print and analyze if adjustment of frame number and abnormal frame
number happen frequently; get warning record and analyze each link code error; check
notices of code error and sliding poise in warning record; check if the binding post
earthed; check clock synchronization mode; if its BTS transmission is based on
satellite, observe Abis link; if the whole BSC is abnormal, check link between BSC
boards; if the link is in normal condition, the problem may be at UM interface, then go
to the BSC and test cell coverage.
3.2.2.2.3 Adjustment methods
In PS, retransmission rate is an important KPI to indicate radio environment quality,
but its not easy to define its threshold. Provided radio environment remains the same,
then higher coding speed brings higher retransmission rate, which doesn't mean lower
throughput. In field test, we are inclined to increase throughput regardless
retransmission. Therefore, we recommend using retransmission rate as a reference
indicator of radio environment rather than evaluation indicator.
In practical use, we suggest inspecting retransmission rate against different coding
mode. With the same coding mode, higher retransmission rate brings worse radio
environment quality. This is more of reference value. Specific COUTNERS are shown
bellow:
V2BSC

IBSC

UL CS1 retransmission rate

C60037/C60011

C900040102/C900040098

DL CS1 retransmission rate

C60041/C60024

C900040089/C900040085

UL CS2 retransmission rate

C60038/C60012

C900040103/C900040099

DL CS2 retransmission rate

C60042/C60025

C900040090/C900040086

UL CS3 retransmission rate

C60039/C60013

C900040104/C900040100

DL CS3 retransmission rate

C60043/C60026

C900040091/C900040087

UL CS4 retransmission rate

C60040/C60014

C900040105/C900040101

DL CS4 retransmission rate

C60044/C60027

C900040092/C900040088

UL MCS1 retransmission rate

C60045/C60015

C900040208/C900040217

DL MCS1 retransmission rate

C60054/C60028

C900040181/C900040190

UL MCS2 retransmission rate

C60046/C60016

C900040209/C900040218

This document contains proprietary information of ZTE Corporation and is not to be disclosed or used
except in accordance with applicable agreements.
22

Internal Use Only

DL MCS2 retransmission rate

C60055/C60029

C900040182/C900040191

UL MCS3 retransmission rate

C60047/C60017

C900040210/C900040219

DL MCS3 retransmission rate

C60056/C60030

C900040183/C900040192

UL MCS4 retransmission rate

C60048/C60018

C900040211/C900040220

DL MCS4 retransmission rate

C60057/C60031

C900040184/C900040193

UL MCS5 retransmission rate

C60049/C60019

C900040212/C900040221

DL MCS5retransmission rate

C60058/C60032

C900040185/C900040194

UL MCS6 retransmission rate

C60050/C60020

C900040213/C900040222

DL MCS6 retransmission rate

C60059/C60033

C900040186/C900040195

UL MCS7 retransmission rate

C60051/C60021

C900040214/C900040223

DL MCS7 retransmission rate

C60060/C60034

C900040187/C900040196

UL MCS8 retransmission rate

C60052/C60022

C900040215/C900040224

DL MCS8 retransmission rate

C60061/C60035

C900040188/C900040197

UL MCS9 retransmission rate

C60053/C60023

C900040216/C900040225

DL MCS9 retransmission rate

C60062/C60036

C900040189/C900040198

Radio environment optimization

Radio environment includes addition of new BTSs, adjustment of direction angle and
down-tilt, amendment of frequency points, etc.;

About frame number adjustment

Refer to 3.2.2.1.3 for details;

About channel without frame numberabout V2BSC

Refer to 3.2.2.1.3 for details;

Lower initial coding speed

When radio environment is bad, we can appropriately lower initial coding speed to
avoid large amount of retransmission.
We have to take system indicators, CQT and DT into consideration when adjusting
initial coding speed.

As for system indicator, we can bring down initial coding speed to reduce
retransmission rate;

CQT is often conducted at locations with better radio environment, so we hope for
higher initial coding speed to improve performance;

This document contains proprietary information of ZTE Corporation and is not to be disclosed or used
except in accordance with applicable agreements.
23

Internal Use Only

Radio environment fluctuates in DT process, so we shall comprehensively

consider data transmission speed and radio environment quality. Initial coding
speed can be neither too high nor too low.

The commonly recommended DL initial coding speed is CS2/MCS6, which also needs
adjustment based on actual situations.

Cn/Nn/Xn optimization

Changed to:
In GPRS service, fluctuation of coding mode is decided through Cn/Nn/Xn algorithm.
As for v2BSC:
When the number of data blocks correctly transmitted by TBF (DL/UL) [using channel
coding mode CSn 1n3 ] exceeds the preset parameter Cn[n-1], upgrade
transmission coding mode by one rank; among Nn n-2data blocks transmitted by
TBF (UL/DL) [using channel coding mode CSn 2n4 ], if Xn[n-2]% are lost
consecutively, degrade transmission coding mode by one rank.
Currently,

the

existing

networks

adopt

these

default

values:

Cn=10 Nn=20 Xn=80 which means to degrade coding mode when consecutive
loss of data blocks reaches 80%. Requirements on degrading coding mode are strict.
We can appropriately lower requirements to match with real situations. We can judge
whether it matches with real situation through related retransmission rate.
As for iBSC
Among Nn n-2 data blocks transmitted by TBF (UL/DL) [using channel coding
mode CSn1n3], if Cn[n-1]% are transmitted successfully, upgrade transmission
coding mode by one rank.
Among Nn n-2 data blocks transmitted by TBF (UL/DL) [using channel coding
mode CSn 2n4 ], if Xn[n-2]% are lost consecutively, degrade transmission
coding mode by one rank.
Default values: Cn=85Nn=20Xn=25
3.2.2.3

UL/DL signaling/ data TBF failure rate

3.2.2.3.1 Formula
v2BSC
This document contains proprietary information of ZTE Corporation and is not to be disclosed or used
except in accordance with applicable agreements.
24

Internal Use Only

Counter

Meaning

Related counter

C70531

UL signaling TBF failure rate

C70093/ C70042100

C70532

UL GPRS data TBF failure rate

C70094/ C70055100

C70533

UL EGPRS data TBF failure rate

C70095/ C70069100

C70534

DL signaling TBF failure rate

C70096/ C70043100

C70535

DL GPRS data TBF failure rate

C70097/ C70057100

C70536

DL EGPRS data TBF failure rate

C70098/ C70071100

iBSC
Indicator

Formula
(C100010037+C100010038+C100010039+C100010040+C100010041+C1000

UL signaling TBF failure rate

10042+C100010043+C100010044+C100010045+C100010046)*100%/
(C100010025+C100010033)
(C100010149+C100010150+C100010151+C100010152+C100010153+C1000

DL signaling TBF failure rate

10154+C100010155+C100010156+C100010157+C100010158)*100%/
(C100010007+C100010015)
((C100010020+C100010021+C100010022+C100010023+C100010024)-

UL GPRS data TBF failure rate

(C100010037+C100010038+C100010039+C100010040+C100010041))/
( C100010026)
((C100010002+C100010003+C100010004+C100010005+C100010006

DL GPRS data TBF failure rate

)-

(C100010149+C100010150+C100010151+C100010152+C100010153))/
( C100010008)
((C100010028+C100010029+C100010030+C100010031+C100010032)-

UL EGPRS data TBF failure rate

(C100010042+C100010043+C100010044+C100010045+C100010046))/
( C100010026)
((C100010010+C100010011+C100010012+C100010013+C100010014

DL EGPRS data TBF failure rate

)-

(C100010154+C100010155+C100010156+C100010157+C100010158))/
( C100010016)

3.2.2.3.2 Illustration on judgment

Judgment of bad cells:
TBF failure rate>20%
Influence factors:
The percentage of abnormally-released TBF after DL signaling TBF setup succeeded.
Through this indicator, we can judge there may be problems like interference, lost
packets, wrong parameters and unstable links in the network.
Interference: internal interference, external interference;
This document contains proprietary information of ZTE Corporation and is not to be disclosed or used
except in accordance with applicable agreements.
25

Internal Use Only

Wrong parameters: wrong settings of Timer or other functional parameters;
Stability of equipment and transmission: high transmission code error, abrupt
discontinuity caused by unstable links;
Usability of data service functions: such as halted single-board CPU resulted from
burst of traffic.
3.2.2.3.3 Adjustment methods

N3101/N3103/N3105

N3101 allowed max number of consecutively-lost UL data blocks

N3103 number of retry times of packet UL acknowledge/non-acknowledge
N3105 allowed max number of consecutively-lost UL RLC/MAC Control message
These counters are influenced by radio environment. When the counters overtime, TBF
will be released by force, which means the radio environment is bad.
Default values of the three counters: 10

T3191

Timer T3191 of RLC/MAC layer on BRP: in packet DL transmission process, if the

BSN of RLC data block (to be sent out) is the biggest (ie. the last DL data block), the
network will send out an RLC data block (with FBI as 1 and including an effective
RRBP) to initialize release of TBF. In the mean time, network starts T3191.

Default value: 500 (5 sec )is recommended.

This document contains proprietary information of ZTE Corporation and is not to be disclosed or used
except in accordance with applicable agreements.
26

Internal Use Only

3.2.3 On-site test optimization
3.2.3.1

KPI analysis

EDGE Reference indicators:

Indicator requirements

Test items

Kh

Kl

Average Attach times)

Attach success rate (%)

100.00%

92.00%

PDP activation time(s)

2.5

test

PDP activation success rate(%)

100.00%

92.00%

Ping Test 500k

Average time delay(s)

1.5

byte

Success rate (%)

100.00%

92.00%

6.5

15

99.50%

80.00%

12

99.50%

80.00%

60

40

99.50%

80.00%

99.50%

80.00%

99.50%

80.00%

120

80

97.50%

80.00%

Attach test
PDP

activation

Average

WAP

homepage

display time (s)

WAP homepage login success
rate(%)
WAP page refresh time (s)

WAP test

WAP page refresh success rate

(%)
WAP download speed
Data

WAP download success rate

service

Average

CQT

success rate (%)

KJAVA test

Success

KJAVA
rate

download
of

online

application access (%)

Single

song

download speed

Single song download speed

Average success rate of Single
song download (%)

FTP test

Average file download speed

120

80

Email

Average file upload speed

40

20

Average file download speed

120

80

End-to-end success rate(%)

99.50%

90.00%

99.50%

90.00%

6.5

15

upload/download
test

PUSH SMS sending success

MMS test

rate (%)
Average time delay of PUSH
SMS sending(s)

Data

Coverage rate

100.00%

92.00%

service

Call drop rate

0.00%

2.00%

DT

Average WAP homepage display time (s)

8.5

20

This document contains proprietary information of ZTE Corporation and is not to be disclosed or used
except in accordance with applicable agreements.
27

Internal Use Only

WAP homepage login success rate(%)

99.50%

80.00%

WAP page refresh time (s)

15

WAP page refresh success rate (%)

99.50%

80.00%

WAP download speed

40

20

WAP download success rate

99.50%

80.00%

FTP download speed

80

40

Note: Listed in the above form are China Mobile (Zhejiang)s indicators of 2007. Test
conditions are: mobile phone occupies 4 TRXs and supports EDGE, highest code is
MCS9. For reference only.
GPRS Reference indicators:

Average GPRS Attach time (s)

1.7

Acceptable
value
3.00

GPRS Attach success rate (%)

98%

90.00%

1.50

PDP activation success rate (%)

99%

90.00%

Average WAP homepage display time (s)

6.5

10.00

98.00%

90.00%

Items
Attach test
PDP activation test
Website login test
WAP test
Webpage refresh test
Ring, picture download test
Ping test
Kjava test
MMS test

Indicators

PDP activation time(s)

WAP homepage login success rate(%)

Average WAP page refresh time (s)

8.00

WAP page refresh success rate (%)

98.00%

90.00%

Download success rate

98.00%

90.00%

20

10.00

Average download speedkbit/s

Average time delay(s)

1.50

2.00

Success rate

98%

90.00%

Download success rate

98.00%

90.00%

MMS end-to-end success rate

98.00%

90.00%

MMS push information success rate

98.00%

90.00%

6.5

12.00

SMS end-to-end success rate

99.00%

95.00%

Average SMS end-to-end time

4.50

8.00

Average file download speed(KB/S)

3.75

2.00

Average upload speed

1.25

0.80

Average download speed

Success rate of using online Treasure Case

3.75

2.00

98.00%

90.00%

98.00%

90.00%

Average time delay of MMS push information

SMS test
FTP test
WEB upload/download speed

DT test

WAP test

Best value

WAP login success rate

WAP homepage display time(s)

8.50

12.00

WAP page refresh success rate

98.00%

90.00%

8.00

98.00%
1.6

0.90
100.00%

WAP page refresh time(s)

Success rate of downloading WAP ring, picture
Average speed of downloading WAP ring, picture
KB/s)

This document contains proprietary information of ZTE Corporation and is not to be disclosed or used
except in accordance with applicable agreements.
28

Internal Use Only

Coverage rate

99%

95.00%

Call drop rate

1.00%

3.00%

2.80

1.50

Average application layer throughput (KB/s)

Note: test conditions are: mobile phone occupies 4TRXs, highest code is CS4. For
reference only.
3.2.3.1.1 Attach and PDP test
Both attach and PDP activation are signaling protocol flow, which includes only upper
layer signaling and small amount of data and displays time delay in system. These two
tests are the basis of all other tests, which will be affected if the two indicators are bad.
Adjustment methods

Optimize radio environment;

Avoid cell reselection;

Delay release of TBF;

Note: Its stipulated in related regulations that cell reselection is not allowed over 4
times. Usually no cell reselection is required in tests.
3.2.3.1.2 WAP-type tests
These tests include WAP test, KJAVA test and download test of picture/ring. Data
amount of WAP webpage is not large, normally within 100K even in downloading, so
its test of small amount of data.
Adjustment methods:

Optimize radio environment;

Avoid frequent cell reselection;

Delay release of TBF;

Select fixed webpage for WAP refresh; mobile phone is permitted to refresh
random webpage; they are not comparable;

Reset mobile phones memory each time before WAP refreshes;

Improve initial coding speed (taking into consideration DT data to make isostatic
adjustment).

This document contains proprietary information of ZTE Corporation and is not to be disclosed or used
except in accordance with applicable agreements.
29

Internal Use Only

3.2.3.1.3 Net-type tests
These tests include download of PING/FTP, main internet gateways. The FTP test is
test of large amount of data.
Adjustment methods:

Optimize radio environment;

Avoid frequent cell reselection;

Delay release of TBF;

Allocate enough resources, including PDCH and auxiliary timeslots.

3.2.3.1.4 MMS test

This test is mainly to connect MMS center. It is test of small amount of data.
Adjustment methods:

Optimize radio environment;

Avoid frequent cell reselection;

Delay release of TBF;

Improve initial coding speed (taking into consideration DT data to make isostatic
adjustment).

3.2.3.2

Illustration on main adjustment methods

3.2.3.2.1 Radio environment optimization

Optimization content of data service radio environment is the same as that of voice
service, so its not repeated here. Mainly introduced here is judgment of radio
environment.

Carrier-to-interference ratio

C/I ratio is the most direct method to evaluate radio environment. MCS9 requires C/I
ratio >20.

MEAN_BEP and CV_BEP

MEAN_BEP and CV_BEP are used to decide which coding speed (LA) is to be
adopted in EDGE. Different modulation methods have their corresponding

This document contains proprietary information of ZTE Corporation and is not to be disclosed or used
except in accordance with applicable agreements.
30

Internal Use Only

MEAN_BEP and CV_BEP. The tables bellow display the corresponding relation
between coding methods and the values of MEAN_BEP and CV_BEP.
8PSK_CV_BEP
8
P
S
K

M
E
A
N

B
E
P

1
2
3
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

GMSK_CV_BEP

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

MCS_4
MCS_4
MCS_4
MCS_4
MCS_4
MCS_4
MCS_5
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

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_8
MCS_9
MCS_9
MCS_9
MCS_9

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_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_8
MCS_9
MCS_9
MCS_9
MCS_9

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_6
MCS_7
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_8
MCS_9
MCS_9
MCS_9
MCS_9

MCS_4
MCS_4
MCS_4
MCS_5
MCS_5
MCS_5
MCS_5
MCS_6
MCS_6
MCS_6
MCS_6
MCS_6
MCS_7
MCS_7
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_8
MCS_9
MCS_9
MCS_9
MCS_9

MCS_4
MCS_4
MCS_4
MCS_5
MCS_5
MCS_5
MCS_6
MCS_6
MCS_6
MCS_6
MCS_6
MCS_7
MCS_7
MCS_7
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_8
MCS_9
MCS_9
MCS_9
MCS_9

MCS_4
MCS_4
MCS_4
MCS_5
MCS_5
MCS_6
MCS_6
MCS_6
MCS_6
MCS_6
MCS_7
MCS_7
MCS_7
MCS_7
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_8
MCS_9
MCS_9
MCS_9
MCS_9

G
M
S
K

M
E
A
N

B
E
P

1
2
3
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

MCS_1
MCS_1
MCS_1
MCS_1
MCS_1
MCS_1
MCS_1
MCS_1
MCS_1
MCS_1
MCS_1
MCS_2
MCS_2
MCS_2
MCS_2
MCS_3
MCS_3
MCS_3
MCS_3
MCS_3
MCS_3
MCS_3
MCS_4
MCS_4
MCS_4
MCS_4
MCS_4
MCS_4
MCS_4
MCS_5
MCS_5
MCS_5

MCS_1
MCS_1
MCS_1
MCS_1
MCS_1
MCS_1
MCS_1
MCS_1
MCS_1
MCS_1
MCS_1
MCS_2
MCS_2
MCS_2
MCS_2
MCS_3
MCS_3
MCS_3
MCS_3
MCS_3
MCS_3
MCS_3
MCS_4
MCS_4
MCS_4
MCS_4
MCS_4
MCS_4
MCS_4
MCS_5
MCS_5
MCS_5

MCS_1
MCS_1
MCS_1
MCS_1
MCS_1
MCS_1
MCS_1
MCS_1
MCS_1
MCS_1
MCS_2
MCS_2
MCS_2
MCS_2
MCS_3
MCS_3
MCS_3
MCS_3
MCS_3
MCS_3
MCS_3
MCS_4
MCS_4
MCS_4
MCS_4
MCS_4
MCS_4
MCS_4
MCS_5
MCS_5
MCS_5
MCS_5

MCS_1
MCS_1
MCS_1
MCS_1
MCS_1
MCS_1
MCS_1
MCS_1
MCS_1
MCS_2
MCS_2
MCS_2
MCS_2
MCS_2
MCS_3
MCS_3
MCS_3
MCS_3
MCS_3
MCS_3
MCS_3
MCS_4
MCS_4
MCS_4
MCS_4
MCS_4
MCS_4
MCS_5
MCS_5
MCS_5
MCS_5
MCS_5

MCS_1
MCS_1
MCS_1
MCS_1
MCS_1
MCS_1
MCS_1
MCS_1
MCS_2
MCS_2
MCS_2
MCS_2
MCS_2
MCS_3
MCS_3
MCS_3
MCS_3
MCS_3
MCS_3
MCS_3
MCS_3
MCS_4
MCS_4
MCS_4
MCS_4
MCS_4
MCS_4
MCS_5
MCS_5
MCS_5
MCS_5
MCS_5

MCS_1
MCS_1
MCS_1
MCS_1
MCS_1
MCS_1
MCS_1
MCS_2
MCS_2
MCS_2
MCS_2
MCS_2
MCS_3
MCS_3
MCS_3
MCS_3
MCS_3
MCS_3
MCS_3
MCS_3
MCS_3
MCS_4
MCS_4
MCS_4
MCS_4
MCS_4
MCS_5
MCS_5
MCS_5
MCS_5
MCS_5
MCS_5

MCS_1
MCS_1
MCS_1
MCS_1
MCS_1
MCS_1
MCS_2
MCS_2
MCS_2
MCS_2
MCS_2
MCS_3
MCS_3
MCS_3
MCS_3
MCS_3
MCS_3
MCS_3
MCS_3
MCS_3
MCS_3
MCS_4
MCS_4
MCS_4
MCS_4
MCS_4
MCS_5
MCS_5
MCS_5
MCS_5
MCS_5
MCS_5

MCS_1
MCS_1
MCS_1
MCS_1
MCS_1
MCS_2
MCS_2
MCS_2
MCS_2
MCS_2
MCS_3
MCS_3
MCS_3
MCS_3
MCS_3
MCS_3
MCS_3
MCS_3
MCS_3
MCS_3
MCS_3
MCS_4
MCS_4
MCS_4
MCS_4
MCS_5
MCS_5
MCS_5
MCS_5
MCS_5
MCS_5
MCS_5

Radio measurement report

The radio measurement reports of GPRS and EDGE are both transmitted in packet DL
confirm/non-confirm messages. The report of GPRS is transmitted once every 480ms,
which can not satisfy the requirements of inconstant radio environment; while the
report of EDGE can be transmitted once every 20ms; and C value and
MEAN_BEP/CV_BEP are included in the report.
Related parameters:
Average period of UL/DL BEP filtration: value of forgetting factor can be changed
through adjustment of this parameter.
Value of forgetting factor(e):

This document contains proprietary information of ZTE Corporation and is not to be disclosed or used
except in accordance with applicable agreements.
31

Internal Use Only

Each value of MEAN_BEP and CV_BEP can be obtained through calculation with e.

For detailed formula, please refer to 10.2.3.2.1 in regulation 05.08.

UL response dispatch intervals of EDGE mobile phone: this parameter defines how
many UL data blocks need to be received for sending DL acknowledge message once.
3.2.3.2.2 Avoid frequent cell reselection
There is no handover mechanism in data service, but data transmission will be
interrupted each time of cell reselection, so to avoid frequent cell reselection is of great
importance.

CRO/PT/TO

Usage of these parameters is the same as in voice service. Because they can affect data
service and voice service at the same time, its rather difficult make adjustment about
data service on condition that voice service is ensured.
Besides, CS and PS traffic will be changed after adjustment on CRO, which may result
in new congestion problems, so we need to carryout observation and retest after
adjustment.

CRH

As for data service, under READY condition, cell reselection formula is changed to be:
C2adjacent cell>C2serving cell+CRH
Note: For details, please refer to 3.2.2.1.3
Therefore, cell reselection can be delayed through adjusting CRH, and there is no
influence on idle MS. Please note to observe CS indicators when adjusting CRH at
LAC boundaries.
3.2.3.2.3 Delay release of TBF
On condition of existing TBF available to MS, flow of new TBF setup is much faster
than setting up TBF with no existing ones available. In actual service, one operation is
This document contains proprietary information of ZTE Corporation and is not to be disclosed or used
except in accordance with applicable agreements.
32

Internal Use Only

often accompanied by many times of TBF setup and release. During FTP downloading
process, large amount of UL TBF will be setup and released. To delay the release of
TBF can accelerate the average speed and reduce time delay.
Relevant parameters are shown bellow:

T3192/T3193 optimization

Timer T3192 is to set time duration that MS has to wait for TBF release after it has
received the final data block. When MS sends PACKET DOWNLINK ACK/NACK
message, whose final acknowledge identity (FAI) is 1, start T3192; or when
PACKET CONTROL ACK is sent in non-acknowledgement mode as response to the
final data block, MS starts T3192; within time set on T3192, when starting
requirements

are

satisfied,

PACKET DOWNLINK

T3192

can

ASSIGNMENT

be

restarted;

message

or

when
PACKET

MS

receives

TIMESLOT

RECONFIGURE message sent by PCU, stop T3192; if T3192 overtimes, MS will

release TBF resource and start to monitor paging channels.
The larger T3192 value is, the longer TBF resource (including TFI and timeslot) will
be kept, and transmission time of TBF will be longer, which will cause congestion
easily. When T3192 value is smaller, MS will quickly release TBF resource; if there are
new DL data arriving at network, the network will start paging or immediate
assignment flow (provided MS stays ready), setup time of DL TBF will be longer as
well. If T3192 doesnt overtime when new DL data arrive at network, then the network
can directly send PACKET DOWNLINK ASSIGNMENT message to setup a new DL
TBF and shorten TBF setup time. Try to take into consideration the cells service load,
service model when setting T3192. Given rich network resource, try to set T3192 a
larger value to reduce setup time of new TBF and improve data transmission speed.
T3193 is the corresponding timer at network , which must be larger than T3192.
Currently, default value of T3192 in existing network is 500ms. Its suggested to set it
1500ms, and T3192, 1520ms.

DrxTimerMax optimization

When MS enters Idle Mode from Packet Transmission Mode, Timer DRX sets the max
time value of MS staying in non-DRX mode.
When MS enters Packet Idle Mode from Packet Transmission Mode, it needs to stay in
non-DRX mode for a while. After TBF release and during non-DRX mode, MS
This document contains proprietary information of ZTE Corporation and is not to be disclosed or used
except in accordance with applicable agreements.
33

Internal Use Only

monitors all CCCH blocks, and in the meantime, PCU retains the contexts related to
MS. The retaining time is decided by the minimum value of DRX_Timer_Max and
NON_DRX_TIMER (non-DRX mode timer).
When network is not configured with PCCCH, in non-DRX mode, Immediate
assignment command can be transmitted on all PCHs and AGCHs, the transmission
takes about 40ms, which is much faster than transmitting it in DRX mode; thus during
this non-DRX period, TBF setup time is short. In DRX mode, MS can only monitor
paging message on specific paging block, then receive Immediate assignment order
on all paging blocks and AGCH reserved blocks. The process of receiving paging
message is comparatively long. The average time length is about half of paging
multiframe period; when BS_PA_MFRMS is 2, its about 235ms.
However, in non-DRX mode, power consumption of MS increases. When
DRX_Timer_Max is set a big value, TBF setup time can be reduced, but power
consumption of MS increases; while DRX_Timer_Max is set a small value, MS can be
saved; but paging flow is added in DRX mode and signaling load is increased, and time
delay of data transmission will be increased as well. Currently in existing network,
DrxTimerMax is set 2s, but we suggest 4s.

Expanded UL TBF

When expanded UL TBF is NOT supported, and when UL TBF is transmitting the final
RLC block, set CV=0. If MS still has UL data to be transmitted thereafter, new UL
TBF needs to be setup for transmission. When expanded UL TBF is supported, and
after UL TBF has transmitted the final RLC block, the existing TBF is not released
right away; if MS still has UL data to be transmitted, directly use the existing TBF for
transmission; there is no need to setup new TBF, and the time for setting up new TBF is
saved.
Expanded UL TBF is very useful for reducing time delay, and it has positive effect on
Ping packet.
Expanded UL TBF needs support from MS. Commonly used mobile phones are sagem
490nokia 6230inokia5700nokiaN72. If expanded UL TBF is supported, usually
we can see packet uplink dummy controlin RLC/MAC signaling trace; if the
mobile phone doesnt support expanded UL TBF, we can often find channel request in
DL response in signaling, which requests for establishment of UL TBF (through
Packet UL Assignment or Packet Timeslot Reassignment messages ).
This document contains proprietary information of ZTE Corporation and is not to be disclosed or used
except in accordance with applicable agreements.
34

Internal Use Only

3.2.3.2.4 Other issues

parameter configuration under flow control mode 2

Flow control is proceeded at Gb gateway, which is between SGSN and BSS, and it
only works on DL. BSS uses flow control to adjust the capacity of BVC funnel and MS
funnel. Try to make buffer memory of the funnels small without breaking down
transmission of DL TBF. If there are too many buffer memory data in the funnel, its a
waste of resource and processors load will be increased, and when life cycle of the
buffer memory data becomes overflown, the data will be abandoned, and SGSN will be
notified about this through LLC_DISCARDED PDU, which may result in data
retransmission at Gb gateway. Therefore, we should set flow control parameter
reasonably; its not that the larger the better, but the more suitable the better.
Theoretical parameter configuration of flow control mode 2 corresponding to each
coding method under EDGE:
Coding scheme

Data speed per timeslot

Parameter configuration under flow control mode 2

MCS-1

8.8 kbps

88

MCS-2

11.2 kbps

112

MCS-3

14.8 kbps

148

MCS-4

17.6 kbps

176

MCS-5

22.4 kbps

224

MCS-6

29.6 kbps

296

MCS-7

44.8 kbps

448

MCS-8

56.4 kbps

564

MCS-9

59.2 kbps

592

Parameter configuration of flow control mode 2 corresponding to each coding method

under GPRS:
Coding scheme

Data speed per

Pparameter configuration under flow control mode

timeslot

CS-1

9.05 kbps

90

CS-2

13.4 kbps

134

CS-3

15.6 kbps

156

CS-4

21.4 kbps

214

This document contains proprietary information of ZTE Corporation and is not to be disclosed or used
except in accordance with applicable agreements.
35

Internal Use Only

When setting this parameter, we dont need to consider number of packet channels, for
the number of packet channels (including dynamic channels) configured in the cell will
be multiplied when flow control message is sent out.

Decision values of PanDecPanIncPanMax

Description: They are MS parameters and belong to GPRS cell parameters. They are
broadcasted to MS in PSI1PSI13 and SI13 messages, indicating values of PAN_DEC
PAN_INC and PAN_MAX. Each time after cell reselection, MS will set the initial
value of counter N3102 to be PanMax. (1) When MS receives PACKET UPLINK
ACK/NACK message, which makes V(S) move forward, add PanInc to N3102
(PanIncPanMax). (2) When MS detects stall condition (V(S) = V(A) + W(S ),
timer T3182 will be started. After MS receives PACKET UPLINK ACK/NACK
message which makes V(S) < V(A) + W(S), T3182 stops. If T3182 overtimes, MS will
deduct N3102 by PanDec. When N3102< 0, MS takes cell reselection as abnormal
release. When any of PanDecPanInc and PanMax is 0, N3102 is invalid.
Reference valuePanDec=4PanInc=8PanMax=32

This document contains proprietary information of ZTE Corporation and is not to be disclosed or used
except in accordance with applicable agreements.
36

Internal Use Only

4 Work Plan of GSM Packet Service Team&

Field Feedback
As for feedback and disposal of problems, whats important is to record them and give
feedback.
Feedback principles:
1. The information must be in-time and accurate;
2. Record the information first, then consider how to restore it, because the recording
process is very short and its a thorough solution.
Feedback content:
Step 1: When problems occur, the first thing is to confirm the location of cell and
EBRP single board, record EBRP, EFRP printing, trace signaling (record duration is
usually above 5 mins), refresh dynamic data management and check if UL/DL is
occupied by MS, and grab screen graph. Take down time points at OMCR.
Step 2: Dispose field problems.
Step 3: Obtain PS basic measurement statistics, warnings, notifications, MP log file,
front stage zdb form, cell packet radio parameters in radio data management, BSC
packet radio parameters; feedback MP EBRP information, and describer problems in
details.
Field feedback content sheet:

Field feedback
content sheet.xls

Its a must to present field feedback content sheet when handling problems. As for the
missed content, there must be relevant explanation, which shall be complemented
ASAP. The feedback sheet is a key to solve the problems

This document contains proprietary information of ZTE Corporation and is not to be disclosed or used
except in accordance with applicable agreements.
37

This document contains proprietary information of ZTE Corporation and is not to be disclosed or used
except in accordance with applicable agreements.
38