Sie sind auf Seite 1von 144

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.

1)

Huawei Technologies Co., Ltd.

Document

Wireless Planning & Design Dept.,

Number

Product Version

Level
3.1

International Technical Support

Product Name: GSM900/1800

Division

Confidential

secret
149 pages

GSM900/1800 BSS&PCU Network Planning


Data Configuration Specification
(Version 3.1)

(For Internal Use Only)


Written by:

Technical Support
Group Wireless Planning
and Design Dept.

Reviewed
by:
Reviewed
by:
Approved
by:

Date:

2002/3/14

Date:
Date:
Date:

Huawei Technologies Co., Ltd.


All Rights Reserved
_______________________________________________________________________________________
2002-2-25
All rights reserved
Page 1of 147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

Revision Record
Date

Revised version

Description

Author

2000/9/10

1.00

Draft completed

Hequn, Zhao Yinghe. Tao Maodi and Xing


Lijin etc.

2000/10/10

2.00

First revision

2000/10/20

2.00

Revision completed; ready to

Zeng Shuhui and Li Yunzi etc.

Zhao Qiyong

issue
2001/1/2

2.10

Revision completed; ready to

Zeng Shuhui and Zhao Qiyong

issue
2001/3/8

2.20

Revision

Zeng Shuhui

2001/7/25

3.00

Revision

Si Fazhong, Zeng Shuhui and Chen Jing

2001/12/20

3.10

Revision

Chen Jing, Si Fajing, Li Xia and Bai Xiaobin

_______________________________________________________________________________________
2002-2-25
All Rights Reserved
Page 1 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

1. Foreword...................................................................................................................................... 5
1.1 Types of wireless parameter adjustment..............................................................................6
1.2. Prerequisites for wireless parameter adjustment................................................................6
1.3.Points for attention in wireless parameter adjustment..........................................................7
II. Data configuration....................................................................................................................... 7
2.1 Local office........................................................................................................................... 7
2.2 Sites................................................................................................................................... 11
2.3 Cells................................................................................................................................... 13
2.4 Handover............................................................................................................................ 54
2.5 Power control..................................................................................................................... 82
2.6 Channels.......................................................................................................................... 101
III. GPRS (PCU) network planning data configuration specifications (draft)..........................111
IV.Accessories............................................................................................................................. 121
4.1The channel description format and cell frequency configuration......................................121
4.2 Location area classification basic principle.......................................................................124
4.2.1 LAC concept.......................................................................................................... 124
4.2.2 Principles in location area classification.................................................................124
4.3 34 Tables (BSC) of Network Planning Data......................................................................126
4.4 Description of parameter configuration and main check-points for Phase XX network
planning of the XX mobile network......................................................................................... 128
4.5 Description of flow control (based on the 06.0520 version and the current 01.07.0520
version).................................................................................................................................. 130
4.5.1 BSC internal flow control.......................................................................................130
4.5.2 Cell traffic level maintenance and processing at different traffic levels..................135
4.5.3 About TCH flow control.......................................................................................... 138
4.6 Newly added functions in new version.............................................................................138
4.7. Description Manual of Key Specifications in Various Versions of GSM BSC32 Traffic
Statistics................................................................................................................................. 142
4.7.1 Overview................................................................................................................ 142
4.7.2 Traffic statistics modification of various versions...................................................142
4.8 Description of data configuration for BCCH participation in frequency hopping...............145

_______________________________________________________________________________________
2002-2-25
All Rights Reserved
Page 1 of 147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

GSM900/1800 BSS&PCU Network Planning Data


Configuration Specification
(Version 3.0, Dec 20, 2001)

Key words: BSS function applications


Abstract: this article describes the specifications and the points for attention that should
be followed in the process of GSM900/1800 BSS network planning data preparation and
optimization. On basis of the first edition, related functions and parameters of BSC0520
version and BTS3.X are added. Network Planning Data refer to all functions and
algorithm parameters related to the wireless network quality (voice, data, etc.) in the BSS
system. With the perfection of the BSS system and the application of GPRS and next
generation system, more functions and algorithm parameters will be continuously added.
So, when the Central R&D Division of Huawei adds or improves any functions and
algorithm to the BSS system, please inform our department in time so that we can
participate in the evaluation and discussions. Besides, the personnel in charge of network
planning of this project also has the final say in on-site modification of such data.
Research into wireless network parameters and improvement of algorithms and functions
must also forecast hidden hazardous factors in wireless networks (e.g., large traffic and
user abnormal behavior), and should not narrow down to existing small networks.
Otherwise, it will cost a more dear price for compensations when problems pop up during
construction of larger networks.
Moreover, no parameters stand alone. Many problems and phenomena on the network
result from the joint action of function algorithms and the way of organizing the wireless
networking. For such complicated phenomena, we should integrate our theoretical study
with practical experience, and make comprehensive and profound case studies, from all
aspects such as MSC, BSC, and BTS as well as wireless network characteristics. Our
analysis should involve perfect suggestions for device function algorithms, application
suggestions for function algorithms in actual networking, and guide to problem analysis.
This is even more urgent while Huawei devices are getting more and more reliable, but
the wireless network is getting more and more complex, and traffic and capacity are
getting greater and greater. As a result, it gets more and more complicated to make
comprehensive use of such parameters in consideration of wireless network features.
Thus, This needs the participation of all of us
Some topics worthy of further research have also been mentioned in the article.

List of abbreviations:
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 2 of 147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

List of Reference Documents


Name
First
version
specifications

Autho Cod Issuing date Reference location


r
e
of

the

2000/8

GSM related protocols


Central R&D documents
Technical documents of other
manufacturers
Others
Revision Description:
1).This revision is made on basis of Version 2.2. It includes some updating of part of
original parameters, and addition of new BSC concentric functions, channel
generation II distribution algorithms, flow control functions, extended cells, and
BCCH parameter configuration and introduction that participate in the frequency
hopping function. Moreover, it also lists the main functions of Huaweis mainstream
BTS, BSC and traffic statistics. Meanwhile, it has also briefly described part of
GPRS parameters in PCU. Parameter setting is on basis of thoroughly understanding
the algorithms behind the parameters. Only in this way, can we arrive at correct
applications for different circumstances. The recommended values are for reference
only. Please come up with better and more mature ideas and suggestions in the
implementation process.
2) The module number and cell number in the cell, handover, and power control
menus act as indexes of a cell in a BSC. The module number must start with 1 and
must correspond to the BM code; the cell number falls in the value range 0 127,
and must be unique in a module. In earlier versions, these codes must be continuous.
The base station codes have a value range of 0 63, and must also be unique in a
module. For easier extended and workload reduction during network optimization,
each base station is assigned three cell numbers; if there are enough device resources,
each cell that has extended potential can be assigned with more carrier numbers, e.g.,
all single carrier sectors are configured into 2 carrier sectors.
3) Based on the two points above, the data setting center should please work out
corresponding modifying plans.

______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 3 of 147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

1. Foreword
The 900/1800MHzTDMA digital cellular mobile communication system (GSM) is an
integrated system that integrates such fields as network technology, digital SPC switching
technology, all types of transmission technologies and wireless technologies. Normally,
the GSM system can be divided into three parts analyzed from the physical structure of
the network, i.e., the network can be divided into the network subsystem (NSS), the base
station subsystem (BSS), and the mobile station (MS). But analyzed from the signaling
structure, the GSM system largely consists of the MAP interface, the A interface
(interface between MSC and BSC), the Abis interface (interface between BSC and BTS)
and the Um interface (interface between BTS and MS, which is normally called the air
interface). All these entities and interfaces have plenty of configuration parameters and
performance parameters, some of which are already determined during the device
developing and manufacturing stage, but most of which are determined by the network
operators according to the actual network requirements and actual running. But the
setting and adjustment of those parameters have considerable influence on the operation
of the whole GSM network. So, GSM optimization is in a certain sense, the process of
optimization setting and adjustment of all types of parameters in the network.
As a mobile communications system, the GSM network has parameters related to
wireless devices and interfaces that are most sensitive to the influence of network service
performance. The wireless parameters in the GSM network refer to parameters related to
wireless devices and wireless resources. These parameters have vital impact on the cell
coverage in the network, the distribution of signaling flow and the service performance of
the network. As a result, reasonable adjustment of wireless parameters is an important
part of GSM network optimization. Normally, the GSM wireless parameters can be
divided into two types according to the service targets of the wireless parameters in the
network, i.e., project parameters, and resources (cell) parameters. The project parameters
refer to those related to project design, installation and commissioning, e.g., antenna
height, antenna direction, antenna gain, antenna declination angle and cable attenuation.
These parameters must be determined during network design, as they can hardly be
modified during network operation. The resources (cell) parameters refer to those related
to the configuration and usage of wireless resources. They are normally transmitted on
wireless interfaces (Um) to keep the consistency between the base station and mobile
stations. Another important feature of resources parameters is that most resources
parameters can be dynamically adjusted during network running at some man machine
interfaces. The wireless parameters involved in this text are mainly wireless resources
parameters (unless otherwise particularly specified, the wireless parameters described
here actually refer to wireless resources parameters).
When a service carrier starts to construct a mobile communications network, he must first
make system project design according to such parameters as wireless channel features
obtained from the geographic environment of a specific area, and the service forecasting
and testing. The design should include network topology design, base station addressing
and frequency planning. But compared with a fixed system, as user terminals are mobile
in mobile communication, so, mobility, spontaneity, and randomness are obvious features
of not only service flow, but also signaling flow, and other characteristic network
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 4 of 147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

parameters. Such features explain why there is some big difference between the design of
mobile communication systems and their actual applications in such aspects as the traffic
model and signaling flow. So, after the network starts running, the carrier needs to adjust
the various types of structures, configurations and parameters of the network, so that the
network can work more reasonably. The is an important part in the whole network
optimization process.
Wireless parameter optimization adjustment is a process of enhancing the communication
quality, improve the average network service performance and increase the device
utilization rate of a running system according to the actual wireless channel features,
traffic features, and signaling flow bearing, and by adjusting the partial or global network
wireless parameters. In fact, the basic principle of wireless parameter adjustment is to
make full use of existing wireless resources, average and smoothen the global service
flow and signaling flow through load-sharing, so as to reach the goal of enhancing the
average network service level.

1.1 Types of wireless parameter adjustment


There are two types of such adjustment according to the property of problems to be
solved through wireless parameter adjustment. The first type is to solve static problems,
i.e., modify the traffic model adopted in system design according to the actual average
traffic flow and signaling flow tested on site in various areas in the network, so as to
solve the rampant problems in the long run. The other type of adjustment is used to solve
problems of traffic overloading and channel congestion in certain areas within a time
segment due to some spontaneous or random events.
For the first type of adjustment, the carrier only has to make periodic tests and reports on
the actual running of the network, and on this basis, make appropriate adjustment of
global or partial network parameters and configurations. But the second type of
adjustment means that the network operator should adjust part of the real-time wireless
parameters according to the data obtained by the testing personnel. However, no matter
what type of wireless parameter adjustment is used, it means the same for the parameters
themselves. So, this manual starts from parameters, and makes analysis of the impact of
parameter adjustment range and adjustment result on the whole network. It does not
involve the real time issue during adjustment.

1.2. Prerequisites for wireless parameter adjustment


The network operator must first have a thorough understanding of the meaning of each
wireless parameter, the adjustment mode and adjustment result, and should be very
experienced with the wireless parameter types involved in problems that occur in the
network. This is a necessary condition for effective wireless parameter adjustment. On
the other hand, the adjustment of wireless parameters will depend on plenty of actual
testing data obtained during actual network operation. Normally, these parameters can be
obtained in two ways. First, the statistic parameters can be obtained from the operation
maintenance center (OMC) of the network, or the operation maintenance center (OMC
R) in the radio segment, e.g., the bearing of CCCH channels, RACH channels and the
signaling bearing of other channels (including wired and wireless channels). Second,
other parameters, including cell coverage, mobile station communication quality, etc.,
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 5 of 147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

should be obtained from actual measurements and tests. So if the carrier wishes to
effectively adjust wireless parameters, they must make frequent and long-term
measurements of the various network features.

1.3.Points for attention in wireless parameter adjustment


In the GSM system, plenty of wireless parameters are set on basis of cells and regional
areas. But inter-region parameters are often strongly interrelated. So, during parameter
adjustment, consideration must be made to the impact of regional parameter adjustment
on other areas, especially adjacent areas. Otherwise, parameter adjustment will bring
about diverse consequences.
Besides, when regional problems occur in the network, first we should determine whether
they are caused by device faults (including connection failure). Only when it is confirmed
that network problems are caused by service causes, can we make wireless parameter
adjustment. The wireless parameter adjustment modes recommended in this manual are
put forward on condition that no device problems exist.

II. Data configuration


2.1 Local office
BSC cell table
Cell system type: Huawei M900/M1800 BSC supports both the independent and hybrid
networking of both 900M and 1800M. The setting here can be either "GSM900" or
"GSM1800" according to the band configuration selected for the cell or the network.
Sub cell type and cell level: to determine the location of a cell in the layered and
hierarchical structure, used mainly for dual-band networking, so as to differentiate macrocell, micro-cell, and better realizing load-sharing and handover. The setting here is
"normal" and "superior" during the construction of a new network.
BCC and NCC: NCC and BCC form BSIC.
Value range: 07
BCC is a base station color code used to distinguish adjacenting cells with the same
BCCH frequencys; in frequency hopping cells, the TSC in the frequency hopping data
table must be configured to be consistent with BCC in the cell.
Note: after dynamic modification of cell BSIC, TSC in the frequency hopping data table
must be modified accordingly.

______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 6 of 147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

The NCC is a network color code used to distinguish networks in different areas. It is
coded in a uniform way over the whole country.
Value range: 07
Cell Global Identifier: CGI, must be capitalized; notice that the classification of LAC has
a very important effect on increasing signaling load and call completion rate.
For the basic principles of LAC classification, refer to the appendices.
Supporting GPRS
Value range: Yes, No
Unit: None
Content: indicating whether the GPRS function is supported. The GPRS function needs
the support from the base station.
Recommended value: to be determined according to the actual circumstances. For base
station versions that don't support the GPRS function and cells where the GPRS service is
not commissioned yet, the value must be set to No; otherwise, it might make it
impossible for part of the mobile phones to access the Internet.
Frequency hopping data table
Frequency hopping index number: internal index number, provides an association
between the wireless channel configuration table and the frequency hopping data table.
MA: the MA is a set of frequency hopping points formed by a maximum of 64
frequencys; the frequencys must be those within the cell distribution table. At present,
when carrier frequencies hop in the radio frequencies, MA can not contain the frequencys
on the BCCH channel; BTS3X after the 03.0529 version supports BCCH participation in
frequency hopping (baseband and time slot frequency hopping). Thus, except the time
slot 0 of hopping carrier frequencies (when extended BCCH is configured, the time slots
corresponding to the extended BCCH should be also excepted), MA in other time slots
can contain the BCCH frequency; in actual use, note that only BSC08.0520B and
subsequent versions support BCCH participation in frequency hopping.
The data configuration method of BCCH participation in baseband time slot frequency
hopping, refer to the appendix (4.8 Description of data when BCCH participates in
frequency hopping)

______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 7 of 147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

Hopping frequency offset MAIO: during frame frequency hopping, MAIO is


recommended to the same in all channels of a TRX, in the same cell, the MAIO of a
different TRX is different, and the rule of the thumb here is to guarantee that the MAIO
in the same time slot of TRX of the same HSN and MA in synchronized cells are not the
same, so as to avoid clash between the same frequency. During time slot frequency
hopping, the MAIO of various channels of the same TRX can be configured differently.
Note: BTS2.X supports radio frequency frame hopping; all versions of BTS3.X support
baseband frequency hopping and radio frequency hopping frequency, including time slot
frequency hopping and frame frequency hopping; but only BTS3.X after version 03.0529
supports BCCH participation in frequency hopping (baseband and time slot frequency
hopping)
Hopping serial number HSN: the HSN of all channels in the same cell is recommended to
be the same; and it is specified that HSN can not be "0". For part of the 30 base station
versions, if HSN is configured to be "0", it will cause base station to be unable to
properly operate.
Training serial code TSC: when frequency hopping in a cell, TSC must be set to be
identical with the BCC in the cell, otherwise, the TCH carrier channels in the cell cannot
be properly seized.
Note: for frequency hopping algorithms, refer to Protocol 0502
Wireless channel configuration table
Channel type: indicating the channel type and function of every time slot of all carrier
frequencies in a cell.
Every cell is configured a BCCH carrier; normally, the TRX corresponding to a BCCH
frequency is fixed to be the smallest TRX number in the cell. Listed below are the
common channel combinations of BCCH carrier frequencies:
Combination BCCH7TCH
Main BCCHSDCCH/8+6TCH
Main BCCH2SDCCH/8+5TCH
Main BCCHSDCCH/8+ extended BCCH(BCH)+5TCH
Main BCCHSDCCH/8+ extended BCCH(BCH)+TCH+ extended
BCCH(BCH)+3TCH
Note: the configuration of BCCH in a cell should be done appropriately according to the
channel number in the cell and the paging capability in the location area.
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 8 of 147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

The main BCCH and combined BCCH are configured in time slot 0, and extended BCCH
channel can be configured only in time slots 2, 4, and 6. After extended BCCH channels
are configured, the CCCH configuration parameters in the system message data table
should be configured accordingly. For example, if an extended BCCH is configured in
time slot 2, then, in the system message data table, CCCH should be configured into 2
non-combined CCCHs.
All versions of BTS3.0 base station running on the network at present support extended
BCCH, but only version 05.0420 and those after of BTS2.0 base station support extended
BCCH.
If there is the cell broadcasting function, SDCCH8 can be modified into SDCCH
CBCH. At present, devices support only one CBCH channel in each cell, with the
channel type of SDCCHCBCH, but they don't support BCH+CBCH. In practice, traffic
statistics must be continuously made so as to monitor the seizure of each channel and
make timely adjustments in order to reach the maximum utilization of channels.
Recommended value: for 1 to 2 TRXs, one SDCCH/8 is configured; for 3 to 4 TRXs, 2
SDCCH/8s are configured; for 5 to 6 TRXs, 3 SDCCH/8s are configured. Meanwhile,
start the dynamic SDCCH distribution function to guarantee ideal operation.
flow control parameter table:
At present, the on-line BSC versions all support flow control. The flow control parameter
table at the data management console is a hidden form. To set corresponding parameters,
please refer to the flow control guidebook of corresponding versions (with permission of
version administrators).
Take the 01.07.0520B version as example, the operation is as follows:
Enter the data management console. Press CTRL+SHIFT+F12, open the "flow control
parameter table", and confirm the following information:
"Internal flow control permission" configured as: "Yes"
"Message queue initial overload threshold" configured as: "70"
"Message queue severe overload threshold" configured as: "60"
"Inter-module messages allowed within a cycle" configured as: "15"
"Observation cycle (unit: tick)" configured as: "25"
Note:
1. Starting from G3BSC32.1010X.06.0520B, flow control table 2 under the configuration
menu and flow control table 1 under the local office menu are integrated into one and is
put under the configuration menu, with some new fields added; meanwhile, flow control
table 1 under the local office menu is deleted.
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 9 of 147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

2. G2BSC32.1010X.03.0520B X=1, 2, and 3, able to start the flow control function;


3. G3BSC32.10102.04.0520B can start the flow control function;
4. G3BSC32.1010X.06.0520B X=0, 1, and 2, able to start the flow control function;
5. 00.07.0520B cannot be used temporarily;
6. 01.07.0520B and subsequent versions can start the flow control function.

2.2 Sites
carrier configuration table
Power level: "0" power level shows that power is in its maximum.
1. In BTS version:
The 0407 version of BTS30 base station supports static power level setting of levels 0
6, and the 0529 version supports the static power level setting of levels 010, and in the
04.0529 version, the down-tuning function by 30dB (in maximum) is added, for
debugging before cutover (operated on the base station maintenance station);
All on-line versions of BTS20 base station support the static power setting of levels 0
10;
The Micro cellular base stations support the static power setting of levels 013.
Note:
1. Cells can be enabled to sufficiently absorb traffic by setting the "power level"
parameters; but when antennas are too tall that result in serious cross-cell overlapping,
the first solution should be lowering the antenna height and increasing the antenna
declination angle. Also note that lowering base station transmitting power will deteriorate
indoor coverage.
2. The available frequencys must be the subset of the CA table
3. Normally, for cells with the same priority in the network, their power level setting
should guarantee that the EIRP of every cell is basically the same.
4. During power level setting, note that for different carrier frequencies in a cell, different
combining modes will arrive at different loss.
5. In case there is no frequency hopping, among all the available frequencys of all carrier
frequencies in the carrier configuration table, only the first frequency is valid, and no
others have any impact.
carrier power type
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 10 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

Value range: "40W", "60W", "default"


Default value: "default"
Content: for configuration of the carrier type; and after the launch of 60W TRX, this
parameter should be used to distinguish carrier frequencies with different power.
Concentric property
Value range: internal circle, external circle, none
Default value: none
Content: to indicate whether carrier frequencies should be configured on the internal or
external circle of a concentric circle.
TRX priority class
Value range: level 0level 7
Default value: "level 0"
Content: used in Huawei channel II distribution algorithm to designate the priority of
TRX.
Feeder configuration table
Whether there is tower amplifier
Value range: with tower amplifier, without tower amplifier
Power attenuation factor
Value range: 0255
Recommended value: to be reasonably configured according to the feeder length, the
method of which is shown as follows.
Use BTS base station (including 2.0 and 3.0 base stations) of the CDU system to adjust
the gain of CDU according to the two parameters described above.
In systems where BTS2.x base station adopts the combiner/divider mode (no CDU
mode), this has been fixed at 10.
Uplink: according to actual tower amplifier circumstances:
Data

With or without tower

Power attenuation

Description

______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 11 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

configuration

amplifier

factor

With
tower
amplifier

With tower amplifier

Tower amplifier gain


-feeder loss =12-4=8
(i.e., CDU attenuation
of 8dB)

Triplex tower amplifier


has a gain of 12.
Duplex tower amplifier
has a gain of 14
Simplex tower amplifier
has a gain of 14
Assuming that feeder
loss is 4dB

No tower
amplifier

No tower amplifier

Downlink: no tower amplifier, and power attenuation factor is set to be 255 (no impact)

2.3 Cells
System message data table
System message used
Value range: this is a multi-option item including system messages 1 12. 2bis, 2ter,
5bis, 5ter and 10bis
Unit: None
Content: System Information Used, used to determine whether to send a certain type of
system message. A system message is one sent from the network side to a mobile station
in the broadcast mode. It informs all mobile stations of information about a location area,
a cell, available carrier frequencies, available frequency hopping sequences, channel
distribution and random access control, so as to help mobile stations to locate network
resources quickly and accurately. In the pull-down check-box, select the system message
type supported by BSC system. If one is selected, it means that it is supported, indicated
by "1"; otherwise it is "0". From top to bottom, the system message types are: 10bis, 5ter,
5bis, 2ter, 2bis, 12. , 1. For example: 10000000000000000 indicates that only the
system message type 10bis is supported. Besides, the system message types 2bis and 5bis
are used for the 1800 network, and the system message types 2ter and 5ter are used for
the 900/1800 dual-band network. For detailed system message definitions, refer to
Protocol 0408 and system message training materials.
Recommended value: select system messages: 16. 2bis, 2ter, 5bis, 5ter
Note: versions after G2BSC3203.0520B send the following system messages in default:
1, 2, 2ter, 3, 4, 5, 5ter, and 6; for some new system messages (e.g., messages 7 and 8),
some mobile phones do not recognize them, which can easily cause automatic resetting or
other abnormal occurrences. So care is requested during data configuration. Moreover,
after dynamic system message modification, we must reset the baseband processing
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 12 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

board at BTS2.X base station (including the 22C microcell), but BTS3.X base station
does not need to be reset.
Timed sending
Value range: Yes, No
Unit: None
Content: showing whether BSC periodically updates the system message content sent
from BTS. If it is set as "Yes", BSC will send system messages to BTS periodically
(interval to be determined by the sending interval), otherwise, manual sending is
requested.
Recommended value: Yes
Timed sending interval
Value range: 0255
Unit: minute
Content: specifying the interval BSC sends system messages periodically to BTS.
Recommended value: 10
Maximum MS re-transmitting times
Value range: 1, 2, 4, 7
Unit: times
Content: MAX retrains, the upper limit of times MS is allowed to send the "Channel
Request" message in the same immediate assignment process. After MS initiates the
immediate assignment process, it will keep monitoring BCCH and all public control
channel messages belonging to the CCCH group to which it belongs. If the network side
does not send an Immediate Assignment or Immediate Assignment Extend message, MS
will keep re-sending the channel request message after a certain interval. The greater this
parameter is set to be, the higher the success trial call rate, and the high the call
completion rate, but also the greater the load on the RACH channel and the SDCCH
channel. Refer to Protocol 0408.
Recommended value:
For areas where cells have the radius more than 3 kilometers but with less service traffic
(normally the suburbs or rural areas), M can be set as 11 (i.e., the maximum re-sending
times is 7) so as to raise the mobile station access success rate.
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 13 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

For areas where cells have the radius less than 3 kilometers but with average service
traffic (normally the urban areas where traffic is not so busy), M can be set as 10 (i.e., the
maximum re-sending times is 4).
For microcells, M is recommended to be set as 01 (i.e., the maximum re-sending times is
2).
For microcell areas and obviously congested cells M is recommended to be set as 00 (i.e.,
the maximum re-sending times is 1).
It is recommended to set satellite transmission base stations as 4 or greater.
Note: when the downlink quality is poor, it will cause a mobile phone to send SABM to
BTS multiple times.
Common access control level
Value range: multi option item, including level 0 barred, , level 9 barred
Content: used for load control, allowing or inhibiting network access to some users at the
common access level. "1" indicates that access is barred, and "0" indicates that access is
allowed. For example: 1000000000 means to allow network access to users except those
at level 0. During base station installation and commissioning or during maintenance
testing of some cells, it can be set as "1" for all, so as to compulsorily inhibit access of
different users, and to reduce impact on installation or maintenance; in cells with a heavy
service traffic, congestion will occur in busy hours, indicated by a higher RACH clash
frequency, AGCH flow overloading, and Abis interface flow overloading. Setting the
level of some users as "1" can reduce the service traffic in the cell.
Recommended value: all set to "0"
Special access control level
Value range: multi option item, including level 11 barring, , level 15 barring
Content: used for load control, allowing or inhibiting network access to users at certain
some special access level. "1" indicates access barred, and "0" indicates access allowed.
in cells with a heavy service traffic, congestion will occur in busy hours, indicated by a
higher RACH clash frequency, AGCH flow overloading, and Abis interface flow
overloading. Setting the level of some users as "1" can reduce the service traffic in the
cell.
Recommended value: all set to "0"
Cell channel description format
Value range: bitmap, 1024, 512, 256, 128. variable-length
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 14 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

Content: the message element is in fact a list of available absolute carrier numbers in a
service cell, with the length of 17 bytes. To be specific, there are altogether 124 bits
starting from the D3 bit of the second byte in the cell channel description to the D0 bit in
the 17th byte, recorded respectively as carrier frequencies No. 124, 123, 122......3, 2, and
1. If the Nth bit is 1, then this Nth carrier belongs to this cell. At present, this parameter
does not function in the system.
Attach/detach allowed
Value range: Yes, No
Content: Attach-detach allowed, ATT. For different cells in the same location area, ATT
must be set to be the same. When it is set to "Yes", it will facilitate the network no longer
to process the called connections of this user when the MS switches off, thus, saving the
network processing time and resources.
Recommended value: Yes
Power control allowed
Value range: Yes, No
Unit: None
Content: indicating whether MS should remove the level received from BCCH carrier
time slots when it calculates the average receiving level grade value, if BCCH carrier
time slots participate in frequency hopping.
Recommended value: Yes
Discrete transmitting indication
Value range: can be used, must be used, must not be used
Unit: None
Content: indicating the discontinuous uplink transmission of MS in the past measuring
cycle; refer to Protocol 0508.
Recommended value: must be used
Note: versions starting from version G3BSC32.10101.01.1120A support control as to
whether to activate the downlink DTX function in BSC; for parameter setting, refer to
"Whether to use downlink DTX" in the cell property table.
Cell access allowed
Value range: Yes (0), No (1)
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 15 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

Unit: None
Content: cell access barred (CELL BAR ACCESS); refer to Protocol 0408. It can be used
together with CBQ to determine the priority of cells.
Recommended value: Yes
Cell barring allowed
Value range: Yes (1), No (0)
Unit: None
Content: CBQ (Cell Bar Qualify). CBQ affects only cell selection, and does not affect
cell reselect. Together with CBA, it forms the cell priority. Refer to Protocol 0408.
Cell barring Cell access
allowed
allowed

and Cell
priority

selection Cell
priority

No

Yes

Normal

Normal

No

No

Barred

Barred

Yes

Yes

Low

Normal

Yes

No

Low

Normal

reselect

Recommended value: None


Emergency call allow
Value range: Yes, No
Unit: None
Content: EC (Emergency call). For MS at access level 0 9, EC set to "Yes" indicates
Emergency call allowed; for MS at access level 11 15, only when the corresponding
access control bit and EC are both set to 0, is Emergency call barred.
Recommended value: Yes
Call re-construction allowed
Value range: Yes, No
Content: RE. The network determines by setting RE whether to allow call re-set up. As
sudden interferences or high buildings can cause "blind points" that result in call
disconnections caused by wireless link faults, MS can start the call re-set up process to
restore the call. Allowing call re-set up can reduce the average calldrop rate, but it also
takes a longer time. This applies to suburbs or urban areas with a bad coverage.
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 16 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

Recommended value: Yes


Nation color code NCC allowed
Value range: multi option item, including allowed selections 07
Content: NCC allowed, sent in system messages 2 and 6. It lists the combinations of cell
NCC codes MS should measure. For measuring reports where the parameter is "1", MS
will report it to the base station.
Note: as MS cannot report adjacent area information in networks where NCC is set to 0,
if this parameter is set impropriety, it will cause MS unable to initiate normal call
handover in the calling status, which results in cross-cell calldrop. Refer to Protocol
0508.
CCCH configuration
Value range: 1 non-combined CCCH, 1 combined CCCH, 2 non-combined CCCHs, 3
non-combined CCCHs, 4 non-combined CCCHs; in a corresponding BCCH multi frame,
number of CCCH message blocks: 9, 18, 27, and 36. CCCH configuration determines the
capacity of PCH, AGCH, and RACH. In particular, the capacity of PCH should be
considered with care. Normally, the PCH capacity of all cells in a LAC should be
guaranteed consistent, or, at least the cell with the least PCH capacity should bear more
carrier frequencies than the sum of all carrier frequencies under LAC.
Unit: None
Recommended value: for cells with one carrier, it is recommended to configure 1
combined CCCH (in a system in the location area with few call messages); for the rest,
determine the CCCH configuration according to the carrier number. For extended BCCH
(including the main B and expanded BCCH), if several BCCH channels are configured,
we should then configure several non-combined CCCH.

Extended transmission time slot number:


Value range: 312, 14, 16, 20, 25, 32, and 50
Unit: RACH time slot number (corresponding to a TDMA frame, 4.615ms)
Content: the Tx-integer, used to calculate the time slot number during each interval of
sending when MS continuously sends multiple channel request messages. It is set to
reduce the number of clashes on the RACH channel, and it mainly affects the execution
efficiency of immediate assignment processes. The value of this parameter is related to
the CCCH configuration mode, as they two together determine the parameter S.
Tx-integer

______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 17 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

CCCH not sharing with CCCH


SDCCH
SDCCH
3. 8. 14. 50

55

41

4. 9. 16

76

52

5. 10. 20

109

58

6. 11. 25

163

86

7. 12. 32

217

115

sharing

with

The time slot number between the time when MS starts the immediate assignment
process and the time when the first channel request message is sent (don't includes the
time slot of sending message) is a random value in the set {0, 1. , MAX(T, 8)1};
The time slot number in the interval between any two adjacent channel request messages
interval (not including the time slots sending the messages) is a random value in the set
{S, S1. , ST1} .The greater T gets, the greater the variation range of the interval
for MS to send channel request messages, but the less the RACH clashes. The greater S
gets, the greater the interval for MS to send channel request messages, the less the clashes
on the RACH channel, and the higher the availability rate of AGCH and SDCCH
channels. But the increase of the two will lengthen MS access time, which leads to drop
in the access performance of the whole network. So normally, T should be chosen to
make S as small as possible (so as to reduce MS access time), but we must guarantee that
no overloading occurs on the AGCH and SDCCH channels.
Recommended value: 20 (it can be greater if the cell immediate assignment has a low
success rate) (32 for satellite transmission, so as to reduce impact of satellite
transmission delay)
Note: in case of a heavy network traffic, the less the S+T value, the lower the immediate
assignment success rate in the cell access performance measuring task; in this case, we
can adjust the T value so that S+T is greater.
Access allowed reserved blocks
Value range: 02 (1 combined CCCH), 07 (others)
Unit: Block
Content: the BS-AG-BLKS-RES, indicating how many message blocks in the CCCH
channels are reserved specifically for access allowed channels. After CCCH
configuration is done, this value actually shows the seizure rate of AGCH and PCH
assigned on CCCH. The setting of this parameter will affect the time MS responds to
paging and system service performance.
Recommended value: 2 (non combined CCCH), 1 (combined CCCH)
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 18 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

Note: the AGCH processing process of BTS30 program is the same with BTS20. When
the AGCH channels are all seized, if the PCH channel is idle, it can be used to issue
immediate assignment commands. If the reserved AGCH blocks are configured 0, then
immediate assignment can be sent only on idle call channels; so, some fixed capacity
should be assigned to AGCH.
Coding of frames between the same calls
Value range: 29
Unit: multi frame per cycle
Content: BS-PA-MFRMS, meaning how many multi frames are taken as a cycle for a
paging sub-channel. In fact, this parameter determines how many paging sub-channels
are paging channels in a cell divided. In an actual network, MS monitors only its paging
sub-channels and ignore the content of other paging sub-channels. Refer to Protocol
0502, 0508. The greater the parameter MFR, the more paging sub-channels in a cell, and
correspondingly the less the users belonging to each paging sub-channel (refer to the
05.02 paging group calculation mode in the GSM specifications), which can lengthen the
average MS batteries time. But the greater the MFR, the greater the delay of paging
messages on the air segment, and the lower the average system service performance. The
selection of this value is based on the principle of guaranteeing that no overloading
occurs on this paging channel, and on this basis, the parameter can be as small as
possible. In the running network, we should measure the overloading of paging channels,
and take this as the basis to appropriately adjust the MFR value. Because any paging
message in the same location area (with the same LAC) must be sent in all cells in this
location area, so the capacity of each paging channel in this location area should be made
the same or as close as possible (i.e., the paging sub channels in each cell calculated
finally).
Recommended value: BTS3X 2
For BTS2X, reference the following recommendation
MFR is set to 6 or 7 (i.e., with 6 or 7 multi frames taken as the cycle of paging groups)
for areas with an average or great paging channel load (usually in location areas with
medium or great traffic); for areas with a small paging channel load (usually areas with a
small traffic), MFR is set to 4 or 5 (i.e., 4 or 5 multi frames are taken as the cycle of
paging groups); normally, it is set to 2.
Note:
1. A call block (four continuous CCCH time slots) can bear 2 IMSI calls or 4
TMSI calls or a AGCH immediate assignment message.
2. The downlink signaling link fault When IDLE
The downlink fault rule is based on the downlink signaling link fault timer DSC. When a
mobile phone sits in a cell, DSC is initialized into an integer closest to 90/N (N is
BS_PA_MFRMS frames between the same calls, with the Value range: 2~9). So,
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 19 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

each time when a mobile phone tries to decode messages on a call sub-channel, DSC is
increased by with each successful decoding of a message, but it should not exceed the
initially set value; if message decoding fails, DSC will be decreased by 4. If DSC<=0,
downlink signaling link fault will occur. downlink signaling link fault will lead to cell
reselect.
Cycle location updating time limit value
Value range: 0255
Unit: 6 minutes
Content: T3212. Timeout value. It defines the location updating cycle length. In VLR,
there is a parameter called the cycle location updating cycle. The shorter the cycle
location updating time limit, the better the overall network service performance, but also
the greater the network signaling flow, which will lower the wireless resources
availability rate. Besides, this will increase the MS power consumption, so that the
average ready-for-service time of MS in the system is greatly shortened. So, during the
setting of this parameter, consideration should be given to the processing ability of MSC
and BSC, the A interface, Abis interface, and the Um interface, as well as the HLR and
VLR flow. Normally, the continuous urban coverage area is set larger, while the setting in
the suburbs, rural, or blind areas is smaller.
Recommended value: 2030 (urban), 1020 (suburb), 810 (mountains)
It is normally recommended to select a greater T3212 (e.g., 16 hours, 20 hours, and even
25 hours) in areas with a large service traffic and signaling flow, but a smaller T_3212
(e.g., 3 hours or 2 hours) in areas with a smaller service traffic and signaling flow. To set
the T3212 appropriately, comprehensive and long-term measurements should be made on
the processing ability and flow of all entities of the system in the running network (e.g.,
the processing ability of the MSC, BSC, A interface, Abis interface, Um interface, HLR
and VLR). When overloading occurs to any of the above, the T3212 value can be
increased. Flexible use of the two parameters, i.e., the cycle location updating cycle in
VLR and the cycle location updating time limit value in BSC can improve the system call
completion rate and increase the LAC capacity by reducing ineffective calls.
Note: the cycle location updating cycle set in MSC must be greater than the set value of
this parameter; otherwise, it might occur that the user is not in the service area.
Wireless link timeout timer
Value range: 464, with a step-length of 4
Unit: SACCH cycle (480ms)
Content: RLINKT (Radio Link Timeout). Refer to Protocol 0408 and 0508. This
parameter is used by MS to determine when to disconnect the call when SACCH
decoding fails. Once MS is assigned specific channels, it will turn on the timer S, every
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 20 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

time a SACCH message is unable to decode, S decreases by 1; and each time a SACCH
message is correctly decoded, S increases by 2. This way guarantees that the connections
the voice /data quality of which has dropped to an intolerable level and cannot be
improved through power control or channel switching are either reconstructed, or
released. But if the parameter is set too small, it will cause calldrop due to wireless link
faults; when it is set too big, mobile phones will not clear the line for too long a time,
lowering the resources availability rate (this parameter functions in the downlink).
Recommended value:
In areas with spare services (e.g., remote areas), it is recommended to set the parameter
between 5264.
In areas with a small service traffic but a large coverage radius (e.g., suburbs or rural
areas), it is recommended to set the parameter between 3648.
In areas with a large service traffic (normally urban areas), it is recommended to set the
parameter between 2032.
In areas with a very large service traffic (normally covered with micro-cells), it is
recommended to set the parameter between 4~16.
For cells with obvious blind points or with serious mobile calldrop or interruptions, it is
recommended to set the parameter appropriately larger so that there are chances that the
calls can be restored.
The maximum MS transmitting power control level
Value range: 020; according to the protocol:
For cells of GSM900 and GSM1800 respectively, the dBm values corresponding to the
control level should be different. The 32 maximum transmitting power control levels
corresponding to GSM900 are:
{39, 39, 39, 37, 35, 33, 31, 29, 27, 25, 23, 21, 19, 17, 15, 13, 11, 9, 7, 5, 5, 5, 5, 5, 5, 5, 5,
5,5, 5, 5, 5}
The 32 maximum transmitting power control levels corresponding to GSM1800 are:
{30,28, 26, 24, 22, 20, 18, 16, 14, 12, 10, 8, 6, 4, 2, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 36,
34, 32}
Unit: level
Content: MS-TXPWR-MAX-CCH, it is sent in the BCCH system message; it affects
mobile phone behavior in the idle mode, and is used to calculate C1 and C2 values, and
determine cell selection and cell reselect.
C1 = RLA_C - RXLEV_ACCESS_MIN- MAX((MS_TXPWR_MAX_CCH- P), 0)
RLA_C: average mobile station receiving level,
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 21 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

RXLEV_ACCESS_MIN: the minimum receiving level allowed for the access of the
mobile station,
MS_TXPWR_MAX_CCH: control channel the maximum power level (MS the
maximum of transmitting power control level);
P: the maximum transmitting power level of the mobile station itself.
This parameter determines the power output adopted by an MS when it first accesses a
cell but has not received the power command. Refer to Protocol 0508. The smaller it is
set, the greater the MS output power. But MS near the base station will cause great
adjacent channel interference to this cell, and affect the quality of access and
communication of other MSs; the greater it is set, the less the MS output power, and this
will lower the access success rate of MS at the edge of the cell.
Recommended value: 5(900M), 0(1800M)
Note: at present, BSC version supports only the value range 0 20, which does not
confirm with the protocol (the protocol specified range is 0 31). If the maximum MS
transmitting power control level grade value exceeds 20, it won't affect 900M, but it
cause power control abnormality to 1800M.

Minimum MS receiving signal level


Value range: 063
1Unit: level grade value
Content: RXLEV-ACCESS-MIN. Refer to Protocol 0508. It indicates the minimum
receiving signal level MS requests to access the system.
Recommended value: 8 (corresponding level grade value 102dBm)
Note: this parameter is set too low, having too low a requirement on access signal level,
causing too many MS to try to sit inside this cell, thus adding to cell load and calldrop
possibility. So, it should be set reasonably according to the good uplink/downlink
balance.
Half rate support
Value range: Yes, No
Unit: None
Content: the network informs MS whether the area supports half rate services.
1Recommended value: No
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 22 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

Cell reselect hysteresis parameter (CRH)


Value range: 014; step-length is 2
Unit: dB
Content: Cell Selection Hysteresis, a parameter used when deciding whether to reselect
when crossing a location area. For its functions, refer to the description about the cell
reselect hysteresis parameter. The setting of the parameter is to prevent the increase of
network signaling flow due to frequent location updating and to lower call message loss.
If the parameter is set too small, it will lead to the location updating "ping-pong" effect,
and thus add to signaling load on SDCCH; besides, as MS during location updating
cannot respond to a call, this will further lower the system call completion rate. If it is set
too large, when MS enters a new location area, maybe the cells sitting in the cell for the
longest time are not the best.
Recommended value: 810 (urban dual-band networking, not sharing the location area),
6 (normally)
CBCH channel description
Content: CBCH Channel Description, occurring only when short message cell
broadcasting is already commissioned in the cell; it is an optional item in system message
4, and it consists of 6 bytes: 1. The first byte is channel description IEI; 2. The second
byte consists of the channel type and TDMA offset +TN (time slot number); 3. The third
and fourth bytes contain the information of MAIO (most significant bit) during frequency
hopping (H=1) and ARFCN (most significant bit) not during frequency hopping (H=0),
with TSC information also included; 4. The information of MAIO (least significant bit)
and HSN is included; 5. ARFCN least significant bit information.
CBCH mobile configuration
Content: CBCH Mobile Allocation. If it is designated in CBCH channel description that
frequency hopping is used, then this parameter must be set. If the No.i bit of the value is
"1", it indicates that the No. i carrier in the cell distribution frequency list belongs to the
mobile distribution list.
Additional reselection parameter indication
Value range: Yes, No
Unit: None
Content: ACS (Additional Reselect Param Indication), it is used to inform MS where to
pick up the related cell reselection parameter during cell reselect. In system message 3, it
is not meaningless, so ACS=0. In system message 4, ACS=0 shows that MS should pick
up the parameter PI related to cell reselect from the remaining bytes of system message 4
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 23 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

and calculate C2 related parameters; when ACS=1, shows that MS should pick up the
parameter PI related to cell reselect from the remaining bytes of system message 7 or 8
and calculate C2 related parameters.
Recommended value: No
Cell reselection parameter indication
Value range: Yes (1), No (0)
Unit: None
Content: Cell Reselect parameter indication (PI), sent on the broadcast channel of the
cell. It is the symbol to determine whether "cell reselect offset", "cell reselect temporary
offset" and "cell reselect penalty time" exist. In fact, it notifies MS whether to adopt C2
as the cell reselect standard. Refer to Protocol 0408 and 0508. Each time the cell reselect
caused by parameter C2 has at least an interval of 5s, and this is to avoid frequent MS
activation of the cell reselect process.
Recommended value: Yes
Note: at least for every 5s, the mobile phone will calculate C1 and C2 of the service cell.
When necessary, it will re-calculate C1 and C2 values of all non-service cells (adjacent
areas). The mobile phone constantly checks the following conditions:
1) Whether the path loss (C1) of the current service cell drops to below 0 within 5s. If
yes, it shows too big a path loss in this cell.
2) The C2 value of a suitable non-service cell always exceeds that of service cells in 5s,
and meets the following conditions:
a) If a new cell is in a different location area, the C2 value of this new cell minus the cell
reselect hysteresis (CELL_RESELECT_HYSTERESIS, broadcast in system messages 3
and 4 on the BCCH channel in a service cell) constantly exceeds the C2 value of the
service cell within the 5s period;
b) If a cell reselect has occurred within a previous 15s, then the C2 value of the new cell
minus 5dB constantly exceeds the C2 value of the service cell within 5s.
A new cell that meets the conditions above is a better cell. When a better cell exists, the
mobile phone will have cell reselect. After a better cell is found, and cell reselect occurs,
no reselect should occur within 5s to the previously seated cell.
Cell reselect offset
Value range: 063. Corresponding level grade value: 0126db. step-length =2dB.
Unit: None

______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 24 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

Content: CRO (Cell Reselect Offset), standing for the manually corrected C2 value.
Reason setting of the parameter can reduce the handover times, and help assignment to a
better cell. The greater CRO gets, the greater the repelling to the cell. Usually, there is no
such setting as CRO>25db. This is because too big a CRO will bring uncertainty to the
network. Normally, for cells in a network that have the same priority, CRO is basically
the same. Refer to Protocol 0508 and 0408. The setting of this parameter affects only
GSM PhaseII mobile phones.
Recommended value: 0
Note: the final setting of RXLEV-ACCESS-MIN and CRO should guarantee that cells
make the same offset to mobile phone with the same priority from the actual received
level to C2 calculation, otherwise, something abnormal will occur.
Cell reselect temporary offset
Value range: 07. The corresponding value: 060db. and 7 corresponds to "infinite"
Unit: None
Content: TO (Cell Reselect Temporary Offset), indicating the temporary corrected value
of C2. It functions only in the "cell reselect penalty time" cycle. Refer to Protocol 0508
and 0408. The setting of the parameter affects only the GSM PhaseII mobile phones.
Recommended value: 0
Cell reselect penalty time
Value range: 031. The corresponding time is 20620s, where 31 is a reserved value
used to change the function direction of the CRO on C2.
Unit: None
Content: PT (Cell Reselect Penalty Time), a parameter to ensure the safety and validity of
cell reselect; its main function is to avoid too frequent MS cell reselect. Refer to Protocol
0508 and 0408. The setting of this parameter affects only the GSM PhaseII mobile
phones.
Recommended value: 0
Note:
After the mobile phone completes cell selection, it will go through cell reselection
process in the standby status in order to select a more suitable service cell. The parameter
that determines cell reselect is C2. The principle of mobile phone reselect: select the cell
with the maximum C2 as the service cell. C2 is determined by the following factors:
C2=C1+CRO-TO*H(PT-T)(PT <31)
C2=C1-CRO (PT = 31)
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 25 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

Where CRO is the cell reselect offset, the size of which value affects the difficulty of cell
reselect; TO is the temporary offset, which functions within the penalty time; and PT is
the penalty time.
CRO values can be 0, 1. ...63. The unit is a level grade value, corresponding to 00dB; 1
2dB; ...63126dB.
TO: temporary offset
Values can be 0, 1. ...7
00dB; 110dB; ...660dB; 7Infinite
H()=0

if PT-T<0

H()=1

if PT-T>0

PT: penalty timing time.


Value 0, 1. ...31
0---20s; 1---40s; ...30---620s
This shows that C1 reflects the wireless channel quality. The greater the C1, the better the
channel quality. But the C2 value is manually corrected. and it can be adjusted by CRO.
Thus, the C2 value can be calculated according to CRO, TO, and PT, so as to determine
the cell reselected by a mobile phone. That is to say, we can set such parameters as CRO
that affect the C2 value so that the C2 value of GSM1800 is greater than that in GSM900.
So, even in cases where the signal strength in the GSM1800 cell is lower than that in
GSM900, we can still enable mobile phones to reselect to GSM1800 cells through
parameter setting.
Flexible use of various parameters in cell selection and reselection can control mobile
phones in their selection to the GSM1800 network according to network plan
requirements, so that mobile phones can set up calls on the GSM1800 network, thus,
share the load on the GSM900 network.
ECSC
Value range: Yes, No
Unit: None
Content: early class mark sending control, showing whether SM in a certain cell uses
early class mark sending. Refer to Protocol 0408. After receiving the class mark change
information, MS will send additional class mark information to the network as soon as
possible. CM3 (class mark 3) information includes the power messages of various
frequency bands in a multi-frequency MS. In the handover between different frequency
bands, the power level must be described correctly. Calling and sending the BA2 table
between different frequency bands must know the CM3 message.
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 26 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

Recommended value: No
Note: ECSC is largely for dual-band mobile phones, and it is invalid forsingle-band
mobile phones. For dual-band mobile phones, when ECSC is not used, after the mobile
phone reports EST IND,MSC will still initiate the CLASSMARK REQUEST message,
and MS reports a CLASSMARK UPDATE message, and other functions are not affected.
After it is modified into "NO" at the Bayin site in Gansu Province, tests show that the
connection time from MS to MS reduces from the ordinary 9s to about 6.5s, i.e., the
connection is obviously speeded up. Forsingle-band mobile phones, if the connection
time is too long, they are included here. The specific reason is still under investigation.
And this also has to do with our lack of knowledge about mobile phone behaviour.
Power offset indication
Value range: Yes, No
Unit: None
Content: determining whether to calculate the use power of class 3 mobile phones of
DCS1800.
Recommended value: No
Power offset
Value range: 03. The corresponding values: 0db. 2db. 4db. 6dB
Unit: None
Content: after random access, if it has not received the original power command, the
power used by class 3 mobile phones of DCS1800 is the maximum MS transmitting
power level plus the power offset. Refer to Protocol 0508.
Recommended value: 1
Multi frequency report
Value range: 03
Unit: None
Content: it is used to notify MS to report on adjacent areas of multi frequency bands, and
is sent in system messages 2ter and 5ter. When its value is "0", MS reports the test results
of 6 strongest adjacent areas, no matter which frequency band they are in; when its value
is "1", MS reports on the test results of one adjacent area with the strongest signal on
each frequency band, and the remaining location is used to report the adjacent areas of all
frequency bands in the current service cell. If there are still remaining locations, they are
used to report on reaming adjacent areas; when its value is "2", MS reports on the test
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 27 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

results of two adjacent areas with the strongest signal on each frequency band, and the
remaining location is used to report the adjacent areas of all used frequency bands in the
current service cell. If there are still remaining locations, they are used to report on
reaming adjacent areas; when its value is "3", MS reports on the test results of three
adjacent areas with the strongest signal on each frequency band, and the remaining
location is used to report the adjacent areas of all used frequency bands in the current
service cell. If there are still remaining locations, they are used to report on reaming
adjacent areas. Refer to Protocol 0508. When the service in each frequency band is
basically the same, with no special requirements on the frequency band, it is set to "0";
when the service in each frequency band is obviously different, and if MS is expected to
access a certain frequency band in priority, it is set to "3"; in cases between these two, it
is set to "1" or "2".
Cell configuration data table
Data service configuration
Value range: multi-option item, including: NT 12K FULL RATe, NT 12K HALF RATE,
NT 12K, NT 6K, T 9.6K, T 4.8K, T 2.4K, T 1.2K, T 600 BITS and T 1200/75
Unit: None
Content: indicating which data service to support. When it is set to "0100000000", it
means only to support the NT 12K HALF RATE data service. The specific value should
be set according to the actual circumstances.
Recommended value: 0000000000
Voice version
Value range: multi-option item, including supporting full rate version 1 supporting full
rate version 3, supporting half rate version 1and supporting half rate version 3
Unit: None
Content: it shows which type of voice version to support. When it is set to"111000", it
shows to support full rate version 13, but not half rate version 13.
Recommended value: 111000
& Description:
1. The distinction between voice versions: full rate voice version 1 is FR (at the rate of
13kb/s), full rate voice version 2 is EFR (improved full rate voice coding, at the rate of
12.2kb/s), and the voice version 3 is not provided at present.
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 28 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

2. EFR function is normally supported by all dual-band mobile phones, at the same time
it need corresponding FTC board versions (FTC13 of BSC) to support EFR.
3. Selection of voice version should note the circuit pool No. at the A interface.
4. The half rate is not supported at present.
Voice version priority selection
Value range: supporting the full rate version 1 supporting the full rate version 3,
supporting the half rate version 1 supporting the half rate version 3
Unit: None
Content: it is used to select the voice version supported in priority.
Recommended value: support full rate version 1
Note: the two parameters of voice version and voice version priority select do not
function at present. In fact, BSC host determines the voice version to be used according
to the circuit pool function select in the cell call control table and the circuit pool in the
trunk circuit table. But during data configuration, it is requested to make the
configuration as specified, so as to avoid unpredictable problems brought about by
version changes.
Encryption algorithm setting
Value range: multi-option item, including: not support encryption, A5/1A5/7
Unit: None
Content: it determines the supported encryption algorithm. This should not be all 0s. At
present, domestic GSM communication systems adopt the non-encryption mode, so
"1000000" is selected. In case the system supports (BTS3.X 04. 0529), we can select an
encryption algorithm type. Currently, the 0520B series versions all support encryption
algorithms. In the G3BSC32.10101.08.0520B version, several problems during the
Thailand encryption tests on coordination with products of other manufacturers are
solved. When encryption is requested, it is recommended to use the
G3BSC32.10101.08.0520B version.
Recommended value: 10000000
Note: encryption related setting at both the BSS side and the NSS side must be set
identical.
& Description:
Whether the system needs encryption and what encryption algorithm to select should first
be described in the MAP function flow of MSC. And which encryption algorithm the
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 29 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

system will finally adopt should also depend on BSC data setting and mobile phone
capacity (indicated in the CLASSMARK ENCRYPTION ALGORITHM).
Cell BCCH Mutual Aid allowed
Value range: Yes, No
Unit: None
Content: BCCH Mutual Aid means that when the main BCCH in a cell fails, some other
TRX in the cell will be used to replace the defective TRX, so that it temporarily performs
the functions of the main BCCH by data exchange, and the cell can continue to work.
This parameter indicates whether to use the BCCH Mutual Aid function. This function
can be used flexibly. For example, during expansion or optimization, when the original
BCCH carrier is not installed or seizure failure is too frequent, this function can be used
to let an installed or some other better carrier board to act properly as the BCCH. This
function does not work simultaneously with the function of BCCH participating in
frequency hopping.
Recommended value: Yes
Frequency hopping mode
Value range: no frequency hopping, baseband frequency hopping, radio frequency
hopping
Unit: None
Content: it determines whether frequency hopping is used, and the used frequency
hopping mode. If "no frequency hopping" is selected here, then even if the frequency
hopping data table is configured, this cell will have no frequency hopping. What
frequency hopping can obtain is interference average and frequency diversity.
Recommended value: when the frequency hopping function is activated, device support
to frequency hopping must be checked first.
Note: BTS2.X supports radio frequency frame hopping, and all versions of BTS3.X
support baseband frequency hopping and radio frequency hopping, including time slot
frequency hopping and frame frequency hopping.
1
Supporting DRX Mode or Not
Value range: Yes, No
Unit: None
Content: specifying whether to support the discontinuous receiving mode. DRX means
specifically the discontinuous receiving of cell broadcast short messages by the mobile
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 30 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

station. Mobile stations supporting the DRX specially refers to the mobile station's
discontinuous reception of cell broadcasting short message .Mobile stations that support
DRX mode can receive the broadcasting short message that users are interested in at less
electricity consumption, so that the mobile stations can sustain longer working time. BSC
that support the DRX mode should send scheduling messages so as to meet the needs of
discontinuous receiving by mobile stations. A scheduling message contains the
information of many broadcast short messages to be sent consequently in a cell. The
scheduling cycle seized by the broadcast short messages contained in a scheduling
message is called the scheduling cycle. The scheduling message contains the description
of short message according to the sending sequence, and also indicates the location of the
message in the scheduling cycle. By reading the scheduling messages, the mobile station
can obtain the broadcast short messages it is interested in even shorter a time, so as to
reduce power consumption.
Recommended value: if the cell broadcast messages are opened, it is set to "Yes";
otherwise, it is set to "No".
Support downlink DTX Mode or Not
Value range: Yes, No
Unit: None
Content: It indicates whether to use downlink DTX in a cell; the DTX switch in MSC still
functions; when MSC clearly indicates the barring of downlink DTX, then downlink
DTX cannot be used no matter how the cell switches in BSC are set.
Note: this parameter is provided only in the G3BSC32.10101.01.1120A version and
subsequent versions, and needs the support of the OMC version.
Cell BCCH Mutual Aid Changeover Selection
Value range: changeback during resources check, immediate changeback, no changeback
Unit: None
Content: it indicates that when the cell BCCH mutual aid function is activated, if the
carrier of the faulty BCCH returns to normal, the cell main BCCH will return to the
originally configured state, and this is called BCCH Mutual Aid changeback. The time of
changeback is determined by the parameter. If it is configured as immediate changeback,
then, once the main BCCH recovers, immediate changeback is performed. If it is
configured as changeback during resources check, then changeback is done only during
resources check.
Recommended value: in frequency hopping cells (including radio frequency hopping and
baseband frequency hopping), use "changeback during resources check"; in nonfrequency hopping cells, use "immediate changeback".
Note: this function can be set dynamically, with no command word.
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 31 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

Baseband frequency hopping TRX fault changeover allowed


Value range: Yes, No
Content: this indicates whether to activate the changeover function when the TRX that
participates in baseband frequency hopping fails. When this function is used, if a
baseband frequency hopping TRX in the cell fails, the base station will report the TRX
fault. When the base station management module receives the fault report, it will
automatically adjust the frequency hopping parameter, and remove this TRX from
corresponding hopping frequencies in the cell, and make configuration again for the
whole cell, so as to configure this TRX as a non-hopping TRX, while other TRX still
participate in baseband frequency hopping.
Recommended value: Yes (during baseband frequency hopping), No (no frequency
hopping)
Baseband frequency hopping TRX fault recovery changeback selection
Value range: changeback during resources check, immediate changeback, no changeback
Content: indicating the changeback mode adopted when the originally failed TRX that
participated in baseband frequency hopping is now recovered. When the parameter is set
to "no changeback", this TRX can provide services for non-hopping TRX.
Recommended value: in non-hopping cells, use "immediate changeback"; in frequency
hopping cells (including radio frequency hopping and baseband frequency hopping), use
"changeback during resources check".
Note: this function can be set dynamically, with no command word.
Cell distribution table
That is, the CA table. The CA table mainly configures the valid (available) frequency of
designated cells, and at most 63 value ranges can be configured; the actually configured
value ranges are configured according to the carrier number in the cell from front to back,
with no idle space in between. For example, if a certain base station is configured S5/5/5,
its cell distribution table is as follows:
Module
number

Cell
number

Available
frequency
0

Available
frequency
1

Available
frequency
2

Available
frequency
3

Available
frequency
4

Available
frequency

51

45

59

68

77

86

Not filled

52

49

62

71

80

89

53

53

92

65

74

83

BSC sends the cell CA to mobile phones in system messages.


______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 32 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

Considering the data making standard, it is recommended to set the available frequency 0
as BCCH.
CA table is sent in the form of a bitmap, and different bitmaps support frequency sets
differently, as shown in the appendix: "Cell Channel Description Format and Cell
frequency Configuration".
BA1 (BCCH) table
It mainly records the adjacent cell list used by mobile phones for retrieval in the idle
state, and it is sent in system messages 2, 2bis, and 2ter. For sake of convenience, if the
BCCH frequency is a private frequency, we can fill all BCCH frequencys (better
excluding the point itself) into the BA1 table in the ascending order, so as to improve data
preparation efficiency, and reduce the risks during on-site dynamic data modification.
BA2(SACCH) table
It mainly records the adjacent cell list used by mobile phones for retrieval in the calling
state, and it is sent in system messages 5, 5bis, and 5ter. For sake of convenience, if the
BCCH frequency is a private frequency, we can fill all BCCH frequencys (better
excluding the point itself) into the BA2 table in the ascending order, so as to improve data
preparation efficiency, and reduce the risks during on-site dynamic data modification.
Note: during network optimizing, we can consider putting all BCCH frequencys in the
network into the BA2 table, so as to use the performance measuring function of the
undefined adjacent cells in the traffic statistics station to find out the adjacent cells
missed.
Cell property table
Interference band threshold 05
Value range: 11085
Unit: dBm
Content: BSS measures the uplink features of the wireless channels seized by MS it is
serving, calculates and reports the channel interference of the Idle channel, and provides
judgment basis for BSC to make channel assignment. Interference is manually classified
into 6 levels according to the interference signal strength. The amount of the level used to
classify these levels is called the interference band threshold. BTS determines at which
level the current interfering signal strength is according to these interfere band thresholds,
and uses the wireless resources indication messages to report to BSC. BSC determines
whether handover is requested after comparing the busy and idle channel resources
reported in the measuring reports and wireless resources indication messages. The
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 33 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

statistics of interfere band results can provide analysis for the setting of various
thresholds and interference analysis. Refer to Protocol 0808, 0858, 1221.
Recommended value: 110 (interfere band threshold 0, which must be equal to 110), 105
(interfere band threshold 1), 98 (interfere band threshold 2), 90 (interfere band threshold
3), 87 (interfere band threshold 4), 85 (interfere band threshold 5, which must be equal to
85).
Average interfering cycle
Value range: 131
Unit: SACCH cycle (480ms)
Content: the interfering level on the Idle channel is averaged before wireless resources
indication messages are sent, and the averaged result is used to classify the interfering
level on the Idle channel within 5 interfere bands. This parameter is the time used to
average the interfering level. Refer to Protocol 0808, 0858, and 1221.
Recommended value: 20
SACCH multiframe Number
Value range: 0255
Unit: SACCH cycle (480ms)
Content: it is used for BTS to notify BSC of wireless link connection failure. BSS side
will identify the wireless link failures according to the bit error ratio of SACCH in the up
link. Refer to Protocol 0508, 0858, and 0408. The bit error rate on SACCH is used to
determine if wireless links fail. When it is impossible to correctly decode the SACCH
message within the time set by this parameter, BTS sends a connection failure indication
message to BSC. The SACCH multiframe number and wireless link invalid counter in the
system message respectively define the wireless link connection failure time on both the
uplink and the downlink, and the judgment standard for both cases is whether able to
decode the SACCH message correctly. If up link and its wireless environment is bad and
high bit error rate results in difficult connection or serious call drop, the parameter value
can be increased a little to solve the problem.
Recommended value: BTS3X 14 (31 is recommended for versions after 05.0529)
BTS2X 31
Note: In versions before BTS3X 04.0529 version, the SACCH multi frame number is
restricted within 16 (inclusive). Though BTS3X (04.0529) can be modified, serious
hidden hazard exists (which can cause system collapse when the base station version is
rolled back). SACCH multi frame number supported by BTS3X (after 05.0529) and
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 34 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

BTS2X is <=31. Both microcells and micro base stations support SACCH multi frame
number <=31.
Wireless resources reporting cycle
Value range: 0255
Unit: second
Content: this parameter is used for BTS to notify BSC of the interference level
experienced by channels on one TRX in the Idle state. Refer to Protocol 0858 and 0808.
In the wireless resources indication message, the TRX reports the interference level every
Idle channel undergoes in the whole measuring cycle. This parameter specifies the
interval while sending wireless resources indication messages.
Recommended value: 10 (BTS2.X), which does not function in BTS3.X; instead,
"average interfering cycle" is used.
CCCH load indication cycle
Value range: 0255
Unit: Second
Content: the setting of the parameter is for BTS to inform BSC of the load on a specific
CCCH time slot. Refer to Protocol 0858. If the load on a specific CCCH time slot
exceeds the CCCH load threshold, BTS periodically sends CCCH overloading
information to BSC, which can be specifically grouped into two types: overloading on
random access channel RACH of an uplink and overloading on the paging channel PCH
of a downlink. This parameter specifies the interval for sending overloading information.
If it is set too small, signaling flow at the Abis interface will increase, thus adding to
system burden; if it is set too large, BSC cannot timely handle BTS abnormality.
Recommended value: 15
CCCH load threshold
Value range: 0100
Unit:
Content: his parameter is applied for BTS to inform BSC of the load in a specific CCCH timeslot.
See Protocol 0858. If the load in a specific CCCH timeslot exceeds this CCCH load threshold, BTS
will send CCCH overload information to BSC at intervals. The interval of overload information
sending is called CCCH Load Indication Cycle. Low settings of this threshold will make BTS report
overload information too frequently, thus the exploitation rate of system resources will be lowered,
and even the normal MS access will become difficult. High settings will lead to the situation that BTS
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 35 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

wont report overload information to BSC until the access of many MSs to the network makes system
resources insufficient. This situation tends to induce system malfunction.

Recommended value: 80
Maximum Repeat Times of Physical Information
Value range: 1255
Unit: times
Content: during asynchronous handover, the mobile phone will continuously send to the
network a handover access Burst (normally the timer T3124 lasts 320ms). When BTS
detects the handover access Burst of the mobile phone, BTS will send back a physical
message to the mobile phone on the main DCCH channel, and start timer T3105, as well
as sending the MSG_ABIS_HO_DETECT message to BSC. The physical information
message contains related information on different physical layers so as to guarantee the
correct transfer of MS. If the timer fails before receiving the SAMB frame from MS, BTS
will re-send physical information messages to MS, and this parameter designates the
maximum times Ny1 for sending physical information. If the re-sending times exceed
Ny1, and BTS still has not got any correct SAMB frame from MS, BTS will send the
connection failure message (including handover failure information) to BSC. After BSC
receives this, it will release the newly assigned special channel and stop timer T3105.
Refer to Protocol 0858 and 0408. When the clock or bad transmission causes handover to
be slow or the handover success rate to drop, consideration can be made to increase this
parameter.
Recommended value: 100
Note: only when: maximum physical information re-send times * wireless link
connection timer >EST IND~HO DETECT interval (120~180ms), can the mobile phone
handover be possibly done. Otherwise, handover must fail.
Wireless link connection timer (10ms)
Value range: 0255
Unit: 10ms
Content: timer T3105. Refer to Protocol 0408, 0858. When sending physical information,
the network starts timer T3105. If the timer fails before receiving any correct frame from
MS, the network will resend the physical information message and restart the timer, but
the maximum repeating times is Ny1. As Physical Information is sent on FACCH, each
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 36 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

time every four TDMA frames is sent on FACCH, it takes about 18.0ms, but if they are
sent in exactly 18ms, the previous FACCH might be still in the sending process, so, we
set it as 20ms, so as to guarantee that it is sent out. So, 20ms is the recommended value to
guarantee Physical Information can be continuously sent at the fastest speed.
Recommended value: 2
Note: the benefit of such setting is to reduce the asynchronous handover speed of part of
the mobile phones.
Overloading interval
Value range: 0255
Unit: second
Content: this parameter specifies the interval at which BTS sends the overloading
information to BSC. Overloading includes TRX processor overloading, downlink CCCH
overloading and AGCH overloading. Refer to Protocol 0858.
Recommended value: 15
RACH busy threshold
Value range: 0255
Unit: level grade value
Content: this value is dealt with differently in Huawei BTS20 and BTS30 base station
systems, as shown in the table below:
Parameter

BTS20

BTS30

Rach Slot Count

System configuration

System configuration

Number of RACH greater than


the
busy
threshold
and
demodulated successfully

Number of RACH greater than


the busy threshold

Number of RACH greater than


the busy threshold and accessed
successfully

Number of RACH greater than


the busy threshold and accessed
successfully,
without
considering how high the
access level is

(total statistic time slot)


Rach Busy Count
(RACH busy time slots)
Rach Access Count
(the RACH time slot is
demodulated successful)

1. In BTS20: it indicates the level threshold the system judges MS random access. When
the level of a burst time slot of a received RACH is greater than the threshold, BTS takes
this time slot as a busy time slot. This parameter should be set according to the actual
base station sensitivity and the minimum mobile phone access level, so as to guarantee
the uplink/downlink balance; besides, attention should be given to the difference brought
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 37 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

about by the calculate mode of different BTS base station software version RSSI: field
strength indication RSSI calculated in all BTS20 versions is greater by 56db for M900,
and by 8 9db for M1800. This parameter also affects the handover access of RACH
BURST during asynchronous handover.
2. In BTS30: the RACH busy threshold does not affect mobile phone access, but only the
reporting of CCCH_LOAD_IND. At the network side, if the received level grade value
on BCCH is greater than the RACH busy threshold, it will be regarded as one valid
CCCH_LOAD_IND statistics no matter whether decoding is successful. Besides, the
RACH of successful decoding but lower than the busy threshold value is also included in
the statistics. The statistics cycle is the average RACH load time slot. If the parameter is
set too low, BTS can easily judge the RACH time slot as busy, so as to easily report an
overloading message to BSC; if it is set too high, BTS will not be able to correctly
determine the status of the RACH time slot.
Minimum access level of RACH
Value range: 0255
Unit: level grade value
Content: The "minimum RACH access level" of BTS3X after the 03.0529 version will
affect mobile phone access, indicating the level threshold at which the system determines
MS random access. When the level of a burst time slot of a received RACH is greater
than the threshold, BTS will regard this time slot as a busy time slot. This parameter
should be set according to the actual base station sensitivity and the minimum mobile
phone access level, so as to guarantee the uplink/downlink balance. But in BTS3X, the
"RACH busy threshold" does not affect mobile phone access.
Recommended value:
1. In BTS2.X:
It is recommended to set it as 510. Besides, consideration should also be given so that
RSSI calculation is not too high. If this parameter is set too high, it will affect the
successful handover rate of the 20 base station; if it is set too low, it will bring about too
high a calldrop rate.
DC offset threshold (affecting only BTS2.X base station)
If the CDU system has a tower amplifier, the combiner and divider system is set to 0
When the CDU system has no tower amplifier, it can be set to 3 (to compensate for the
radio frequency channel gain by 3dB when without a tower amplifier)
2. In BTS3.X:
At present, the parameter "RACH busy threshold" recovers its original meaning, i.e.,
making statistics about the busy status of the RACH channel, and acting as one trigger
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 38 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

condition for BSC to make flow control, but having no restriction over mobile phone
uplink access. The value of RACH busy threshold is set according to the bottom noise of
the wireless environment, frequency multiplexing, and the interfere band statistics result.
Normally, it is set above 16 (-94dBm).
In order to control uplink access (call, paging response and handover) and to balance
between the coverage and calldrop rate, the parameter "the minimum access level of
RACH" is added. This parameter is used in BTS3X 0529 version and subsequent
versions. The parameter can be increased progressively from -110dBm, so as to handle
mobile phone uplink access, and does not restrict the handover access threshold. But the
parameter might affect the calldrop rate and access range (coverage). It needs support
from version BSC04.0520 and its subsequent versions.
Moreover, the RACH busy threshold must be higher than the minimum access level of
RACH.
Average RACH Load Time Slot
Value range: 065535
Unit: time slot number
Content: indicating the interval the system judges the RACH time slot as busy, i.e., the
number of RACH burst time slots during one RACH load measurement. Refer to
Protocol 0858. If this threshold is set too low, BTS can easily report overloading
messages to BSC, so that the system resources availability rate is lowered, and normal
MS access gets more difficult; if it is set too high, only when many MS access the
network and cause a tension in system resources, will BTS report overloading messages
to BSC, thus easily bringing about system failure.
Recommended value: 5000
RF Maximum Power Reduce
Value range: 0255
Unit: level, step-length 2dB
Content: it specifies the level of BTS radio frequency power that can be reduced in
maximum. In BTS2.X, it is screened, so it is not used at BTS3.X base station.
T200
The T200 timer (Timer200) is an important timer at the Um interface data link layer
LAPDm. And because LAPDm has different channels such as SDCCH, FACCH and
SACCH, and as different channels have different transmission rates, so we should set
different timer values. The T200+ channel type indicates the T200 value on the channel.
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 39 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

The T200 timer is one that prevents dead lock during data transfer on the data link layer,
and the function of the data link layer is to turn easily erring physical links into sequential
and error-free data links. And the communication entities at both ends of such data links
adopt the re-send acknowledging mechanism. That is to say, each time message is sent,
the opposite side is requested to acknowledge the reception. If this message is lost for
unknown reasons, it will occur that both sides are waiting, leading to system dead lock.
So, a timer must be set at the sending side, so that when the timer gets timeout, the
sending side thinks that the receiving side has not received the message, and will send it
again.
T200 SDCCH (5ms)
Value range: 50100
Unit: 5ms
Content: specifying the T200 value on the SDCCH channel.
Recommended value: at present, it is screened at BTS2.X base station; but at BTS3.X
base station, it is set to "60".
T200 FACCH/ full rate (5ms)
Value range: 40100
Unit: 5ms
Content: specifying the T200 value on the FACCH/ full rate channel.
Recommended value: at present, it is screened at BTS2.X base station; but at BTS3.X
base station, it is set to "50".
T200 FACCH/ half rate (5ms)
Value range: 40100
Unit: 5ms
Content: specifying the T200 value on the FACCH/ half rate channel.
Recommended value: at present, it is screened at BTS2.X base station; and at BTS3.X
base station, it is set to "50".
T200 SACCH TCH SAPI0 (10ms)
Value range: 120200
Unit: 10ms
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 40 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

Content: specifying the T200 value on the TCH SAPI0 channel.


Recommended value: at present, it is screened at BTS2.X base station; and at BTS3.X
base station, it is set to "150".
T200 SACCH TCH SAPI3 (10ms)
Value range: 120200
Unit: 10ms
Content: specifying the T200 value on the TCH SAPI3 channel.
Recommended value: at present, it is screened at BTS2.X base station; and at BTS3.X
base station, it is set to "200".
T200 SACCH SDCCH (10ms)
Value range: 50100
Unit: 10ms
Content: specifying the T200 value on the SACCH and SDCCH channels.
Recommended value: at present, at BTS2.X base station, it is screened; and at BTS3.X
base station, it is set to "60".
T200 SDCCH SAPI3 (10ms)
Value range: 50100
Unit: 10ms
Content: specifying the T200 value on the SACCH SAPI3 channel.
Recommended value: at present, at BTS2.X base station, it is screened; and at BTS3.X
base station, it is set to "60".
The maximum time advance
Value range: 0127 (where TA=127 means there is no time advance)
Unit: bit cycle, 1 bit cycle corresponds to 0.55km
Recommended value: 63
Content: this parameter determines the actual service range of the base station cell. When
BTS receives the channel request message or handover access information, it determines
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 41 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

whether channel distribution or handover should take place in the local cell by comparing
the TA and the parameter set value.
Note: in single time slot extended cells, the maximum TA in normal cells can only be set
to 62. As Huawei processes all TA with a distance greater than 35 kilometers to 63, this
causes mobile phones unable to normally reselect external circles farther away than 35
kilometers.
Frame starting time
Value: 65535
Content: it indicates the initial base station time slot frame number for synchronization
between BTS and MS after base station re-initialization. At present, this parameter is not
used.
Paging times
Value range: 0255
Unit: times
Content: at BTS2.X base station, this parameter is used for BTS to determine paging resending. It controls the paging re-sending times jointly with the paging times configured
in MSC. The total paging times approximate the multiplication of the two. At present,
MSC fixes the paging re-send times at 4 in the program. BSC has no re-send
mechanisms, so it processes a paging message each time it receives one. BTS2.X base
station has a re-send mechanism, but BTS3.X base station has no re-send mechanism.
At present, the MSC call re-send strategy is as follows:
MSC6.0 can re-send paging at most 4 times, and the re-send intervals are 3 seconds, 3
seconds, 2 seconds, and 2 seconds respectively. 2 seconds after the last paging is sent,
i.e., 12 seconds after the first paging is sent, if there is no paging response reported, MSC
will take it as paging responding timeout, and will send a voice prompt that the user is not
in the service area. MSC can adopt two types of paging modes, i.e., TMSI and IMSI. The
G3MSC33.00100.01.0109P version can have flexible setting in whether to adopt TMSI or
IMSI paging, the maximum paging times, call re-send interval, and giving up paging if it
determines that the user is not in the service area, so as to improve LAC capacity, paging
response time (connection time) and whether the network is practical.
Recommended value: 1(BTS2.X), and fixed as "1" in BTS3.X base station program
Random access error threshold
Value range: 0255
Unit: None
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 42 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

Content: the GSM protocol stipulates that we can determine whether a received signal is
an MS random access signal (and also used to calculate the TA value) by judging the
correlation of the training sequence (41bit). This parameter defines the correlation of the
training sequence. If the parameter is set too small, there will be a high random access
signal error tolerance, so that MS random access will be easy but the error report rate will
also be high; if it is set too large, the MS error report rate will be low, but normal access
is hard to report. Refer to Protocol 0408, 0502. In versions before BTS3.X06.0529, the
correlation of the training sequence is fixed in the program, but starting from the 06.0529
version, this parameter, like the 20 base station, can be adjusted on the data management
console.
Recommended value: 180200.
Power level
Content: the parameter does not function at either BTS2.X or BTS3.X base station.
Saturation threshold
Content: the parameter does not function at either BTS2.X or BTS3.X base station.
DC voltage offset threshold
Content: at BTS2.X base station, the true meaning of the current DC offset threshold is to
compensate for the RSSI difference whether the system has tower amplifiers, so as to
guarantee the correctness of the RSSI value in case with no tower amplifier. The DC
offset threshold is 3 greater with no tower amplifier than with a tower amplifier; but this
parameter is not used at BTS3.X base station.
Recommended value: 0 (with tower amplifier), 3 (with no tower amplifier, where RSSI is
regarded as accurate)
Cell extension type
Value range: normal cell, single time slot extended cell, dual time slot extended cell
Unit: None
Content: indicating whether a cell is an extended cell and the way of realizing an
extended cell. Single time slot extended cells correspond to fixed delay extension, and
dual time slot extended cells correspond to classic solution extension. Single time slot
extended cells are overlapped in a ring to obtain a large-scale coverage. For each ring
extended cell (difference between inner and outer radius not over 35Km), BTS will
increase fixed time delay between the cell downlink transmission and uplink receive time
slots, and provide normal TA value for the mobile station and BTS, so as for normal
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 43 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

processing. Huawei BSS subsystem can support extended cells of 70Km. At present, it
supports only normal cells and single time slot extended cells, and the version supporting
double time slot extended cells will soon be launched; it has the version No.:
03.08.0520T.
Note: BTS22 version base stations do not support extended cell functions, nor does the
G2BTS32.3000X.0X.0407
version
of
BTS3X,
but
the
versions
of
BTS23.20000.03.0420a and BTS3.X 0529 version do.
Cell extension offset
Value range: 035
Unit: Km
Content: as the GSM time advance has a limit of 63 bits, so the radius of a cell cannot
exceed 35Km. This parameter indicates the smallest distance between cells and the base
station.
Recommended value: 0 (normal cell), 34 (single time slot extended cell, better set
according to actual circumstances)
Note: for single time slot extended cells, the actual cell extended offset should not be set
exactly as 34. To guarantee continuous coverage between normal cells and extended cells
that provide coverage in the same direction, it is necessary to measure the coverage
distance of normal cells in the actual user environment, and then use this measured value
to set the extended offset for extended cells. This value should also be given some
allowance during setting, so that there is certain overlapping between normal cells and
extended cells.
Cell alarm threshold table
Power output error threshold
Value range: 09, indicating 10dB1dB respectively
Content: used by BTSM. When the output power of a transmitter carrier is lower than
certain a fixed level, errors will occur. The power output error threshold and the power
output reduce threshold give two threshold values of the error. The greater the value, the
less the error.
Recommended value: 2
power output reduce threshold
Recommended value: 2
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 44 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

VSWR transceiver error threshold


Value range: 018
Recommended value: 2
VSWR transceiver incorrected threshold
Value range: 018
Recommended value: 2
Cell call control table
Immediate assignment TCH
Value range: Yes, No
Unit: None
Content: option "Yes" means that TCH channel can be immediately assigned during
analysis of access application when SDCCH has no available resources. The option "No"
means that only SDCCH channels can be distributed.
Recommended value: No
Description: this function can be dynamically set in the 0520B version, Command word:
"configure call control data", parameter: cell number.
Immediate assignment optimization
Value range: Yes, No
Unit: None
Content: option "Yes" means it is allowed to optimize channels activated by BTS when
multiple MS access applications occur, so as to guarantee network response speed.
Recommended value: No
Note: for versions after G2BSC32 0520B, this function is used mainly for "satellite
transmission", i.e., during satellite transmission, "immediate assignment optimization"
must be "Yes", so as to reduce the effects of satellite transmission time delay; for ground
transmission, the recommended value is "No". In the 0520B version, the function can be
set dynamically, Command word: "configure call control data", parameter: cell number.
Immediate assignment to non-random access cell
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 45 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

Value range: Yes, No


Unit: None
Content: after the mobile phone initiates random access in a cell, other cells are all "nonrandom cells". The option "Yes" means that it is allowed to make channel distribution
between cells during analysis of MS access applications. After SDCCH distribution
during random access, when TCH are distributed, they are immediately assigned to nonrandom cells (already synchronized). The program does not have this function.
Recommended value: No
Assignment to cells outside the service cell
Value range: Yes, No
Unit: None
Content: the option "Yes" means it is allowed to make ground link distribution during
assignment, and to assign them to cells outside the service cell when TCH are seized
(already synchronized). This function does not exist in the program.
Recommended value: Yes
TCH assignment re-attempt
Value range: Yes, No
Unit: None
Content: the option "Yes" means that re-attempts are allowed during TCH channel
assignment, if assignment fails. This function does not exist in the program.
Recommended value: No
Handover from SDCCH to TCH in the cell
Value range: Yes, No
Unit: None
Content: the option "Yes" means to allow MS handover to the TCH channel of the local
cell during the use of SDCCH. This function does not exist in the program.
Recommended value: Yes
Handover from SDCCH to TCH between BSC cells
Value range: Yes, No
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 46 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

Unit: None
Content: "Yes" means allowing the MS handover to the TCH channel of other cells
during use of SDCCH. This function does not exist in the program.
Recommended value: Yes
OM initiates inter-channel handover in the same cell
Value range: Yes, No
Unit: None
Content: this indicates whether to support the compulsory inter-channel handover in the
same cell originated at the operation maintenance management console. This function is
default in the program, but the parameter is not used.
Recommended value: Yes
OM initiates inter-cell handover in the same BSC
Value range: Yes, No
Unit: None
Content: this indicates whether to support the compulsory inter-cell handover in the same
BSC originated at the operation maintenance management console. This function is
default in the program, but the parameter is not used.
Recommended value: Yes
OM initiates inter-cell handover in different BSC
Value range: Yes, No
Unit: None
Content: this indicates whether to support the compulsory inter-cell handover in different
BSC originated at the operation maintenance management console. This function is
default in the program, but the parameter is not used.
Recommended value: Yes
Handover re-attempt
Value range: Yes, No
Unit: None
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 47 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

Content: indicating whether to allow re-attempt after handover failure. This function is
default in the program, but the parameter is not used.
Recommended value: Yes
Radio frequency channel release abnormal re-attempt
Value range: Yes, No
Unit: None
Content: indicating whether to allow re-attempt when BTS wireless channel release is
abnormal. In default, one re-attempt is allowed in the program, but the parameter is not
used.
Recommended value: Yes
Random access overloading control
Value range: Yes, No
Unit: None
Content: indicating whether to allow flow control on the RACH channel. In BSC0520
version, there is no such parameter.
Recommended value: No
TCH flow start
Value range: Yes, No
Unit: None
Content: indicating whether to allow to make flow control for the TCH channel.
Recommended value: No
Circuit pool function selection
Value range: selecting circuit pool function, not selecting circuit pool function, system
automatic selection
Unit: None
Content: circuit pool is a circuit property; starting the circuit pool function can enable
BSC to check MSC assigned circuits and supported services. The circuit pool largely
classifies circuits according to circuit bearing ability and service type. If the circuit pool
in which the MSC assigned circuits fall does not match with the assigned service, it will
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 48 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

cause assignment failure. For example, the MSC assigned circuit is in the No.1 circuit
pool, but the voice coding algorithm is EFR, which will lead to mis-matching of circuit
pools and assignment failure. But the circuit pool function should coordinate with BSC
and MSC. If the circuit pool function is not activated on the MSC side, it is meaningless
to activate this function alone on BSC side. To use the EFR function, we must select the
circuit pool function.
Recommended value: selecting circuit pool function
Description: this function can be dynamically set in the 0520B version; Command word:
"configure call control data", parameter: cell number.
Allow direct re-attempt
Value range: Yes, No
Unit: None
Content: TCH direct re-attempt adopts the handover flow to handover to an adjacent cell.
Accordingly, signaling channel handover data should be set in coordination (largely
related to such parameters as signaling channel handover time, filter length, etc., but not
related to whether signaling channel handover allow is activated). Direct re-attempt
chiefly acts as an emergent measure during abnormal high traffic in some regional
wireless network, but not as the main solution to traffic congestion; if a regional area in
the network always makes direct re-attempt, consideration should be made as to adjust
the base station sector carrier configuration and network layout.
Recommended value: Yes
Description: in the 0520B version, this function can be set dynamically, Command word:
"configure call control data", parameter: cell number.
Cell call processing parameter table
Immediate assignment of TCH idle rate threshold
Value range: 0100
Unit:
Content: in the Huawei system, only when SDCCH are used up, but when the TCH idle
rate reaches a threshold, is immediate TCH assignment allowed. The system adopts the
default value, and the parameter is invalid.
Recommended value: 80
Immediate assignment of TCH call re-set up success rate threshold
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 49 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

Value range: 0100


Unit:
Content: when the historically recorded TCH call re-set up success rate reaches a certain
percentage, immediate TCH assignment is allowed.
Recommended value: 80
Assign re-attempt TCH idle rate threshold
Value range: 0100
Unit:
Content: when the TCH idle rate reaches a certain percentage, assignment re-attempt is
allowed. There is no such parameter in BSC0520 version.
Recommended value: 80
TCH flow control start idle threshold
Value range: 07 (fixed in the program)
Unit: idle TCH time slots in this cell
Content: only when the number of idle TCH time slots in this cell is less than a set idle
threshold value, can cell TCH flow control be started.
Recommended value: 2
Description: in the 0520B version, the function can be set dynamically, Command word:
configure call control data", parameter: cell number.
Assign maximum re-attempt times
Value range: 03
Unit: times
Content: the parameter is valid when the TCH assignment re-attempt selection is "Yes".
In the 0520B version, this parameter is not used.
Recommended value: 2
Maximum handover re-attempt times
Value range: 03
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 50 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

Unit: times
Content: the parameter is valid when handover re-attempt selection is "Yes". In the
0520B version, the parameter is not used.
Recommended value: 2
TCH idle rate threshold during SDCCH-to-TCH automatic handover
Value range: 0100
Unit:
Content: when the idle rate of TCH reaches a certain percentage, MS is allowed to
directly handover from SDCCH to TCH. The parameter is valid when SDCCH-to-TCH
handover in the cell is "Yes". In the 0520B version, the parameter is not used.
Recommended value: 80
maximum re-attempt times during abnormal radio frequency channel release
Value range: 03
Unit: times
Content: indicating the maximum times of allowed re-attempt during abnormal radio
frequency channel release due to wireless link disconnection. In the program, the default
is 1. This parameter is not used.
Recommended value: 1
Service request type during SDCCH-to-TCH automatic handover
Value range: MSC service request, location updating request, paging response, MSC
service re-set up request, unknown
Unit: None
Content: the parameter is not used at the moment.
Recommended value: MSC service request
interval for re-sending outgoing handover request indication
Value range: 015
Unit: second
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 51 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

Content: the parameter is valid when handover re-attempt selection is "Yes". In the
0520B version, the parameter uses the default value 10. The parameter is not used.
Recommended value: 10
Maximum re-sending times of outgoing handover request indication
Value range: 03
Unit: times
Content: the parameter is valid when handover re-attempt selection is "Yes". In the
0520B version, this parameter uses the default value 2. The parameter is not used.
Recommended value: 2
System delay absolute frame No. adjustment value
Recommended value: 0
Description: in the 0520B version, the parameter is no longer used.
Response request selection
Value range: Yes, No
Unit: None
Content: deciding whether to make response to a request. For example, when the
parameter is set as "No", then, after BSC sends a handover request, if MSC finds it
impossible to distribute wireless channels, or ground links, it does not have to return a
handover rejection to BSC. So, in traffic statistics, we can see more handover requests
than the sum of successful handovers and handover failures.
Recommended value: Yes
Description: in the 0520B version, the function can be set dynamically, Command word:
configure call control data", parameter: cell number.
Cell module information table
Content: cell global identification code and module number.
Note: improper configuration of the table will lead to handover failure.
Note: the following main points should be considered during configuration of tables
undercell handover :
1. Making full use of the 1800 network to absorb traffic
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 52 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

2. Enhancing mobile phone call completion rate, to guarantee call quality


3. Reducing unnecessary handover and calldrop
4. Cutting down load of the BSS and NSS systems
5. Enlarging coverage

2.4 Handover
Due to RSSI calculation reasons, (at present, it is average 5 8db higher in BTS2X. In
version BTS3X 06.0529 and subsequent versions, it is 2 4dB higher) the previous
settings of various up thresholds do not reflect the absolute values, and in the measuring
reports, the reported receiving level grade values are higher than they are;
The various threshold setting values given below are the recommended valued on
condition that the measuring reports are accurate.
What follows is the 16 Bit rule in BSC handover algorithm used to assort candidate
handover cells, and candidate cells are selected finally according to handover type and
cell sorting result.
16

15

14

13

12

11

10

Bits No. 1-3: sorting according to the cell downlink receiving level (combining the
receiving level and corresponding penalty).
Bit No. 4: handover hysteresis comparison bit between cells on the same layer. The fourth
4 bit for service cell is always 0; for adjacent cells, it is set to 0, if the receiving level
minus the receiving level in the service cells is higher than the inter-cell handover
hysteresis; and it is set to 1, if the receiving level of an adjacent cell minus the receiving
level in the service cell is lower than the inter-cell handover hysteresis.
Bits No. 5-10: layered and hierarchical bits, altogether 6 bits, which can be grouped into
64 priority class. When the receiving level in an adjacent cell or service cell is lower than
the inter-layer handover threshold and hysteresis, they are screened, and all set to 0.
Bit No. 11: load adjustment bit, used for service cells. When the load is more than or
equal to the load handover start threshold, it is set to 1, otherwise, to 0; when the
candidate cell is an adjacent cell, and the load is more than or equal to the load handover
receive threshold, it is set to 1, otherwise, to 0. For the load handover start threshold and
the receiving threshold, refer to the load handover data table.
Bit No. 12: co-BSC adjustment bit, controlled by parameter co-BSC/MSC adjustment
allowed. When this parameter is set to "Yes", in-BSC handover is done in priority. When
the level in an adjacent area or service area is lower than the inter-layer handover
threshold and hysteresis relationship, it is screened, and set to 0.
Bit No. 13: co-MSC adjustment bit, controlled by parameter co-BSC/MSC adjustment
allowed. When the parameter is set to "Yes", in-MSC handover is done in priority. When
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 53 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

the level in an adjacent area or service area is lower than the inter-layer handover
threshold and hysteresis relationship, it is screened, and set to 0.
Bit No. 14: inter-layer handover hysteresis bit. When the receiving level in an adjacent
cell is higher than the inter-layer handover threshold +hysteresis, and that in the service
cell is higher than the inter-layer handover threshold -hysteresis, it is set to 0; otherwise,
it is set to 1.
Bit No. 15: cell type adjustment bit (largely suitable for 70KM single time slot extended
cells); for extended cells, this bit is 1. For normal cells, it is 0.
Bit No. 16: reserved bit
Handover control data table
Handover algorithm type
Value range: Huawei handover algorithm, GSM0508 handover algorithm
Unit: None
Content: to select the used handover algorithm; Huawei handover algorithm, which
supports the handover of complicated layout of networks such as hierarchical networks,
is the only selected handover algorithm at present.
Recommended value: Huawei handover algorithm
Minimum interval of service channel handover
Value range: 160
Unit: second
Content: when a new TCH channel is assigned, a timer should be turned on, and
handover is allowed only when this timer is overflow. This parameter is the timing time
of this timer. It is the protection time used to avoid wrong handover due to inaccurate
measuring reports at the start of call setup. When the measuring report is processed at
BTS side, the parameter can be set smaller; when it is processed at BSC side, the set
parameter can have a longer interval.
Recommended value: 6
Minimum interval of signaling channel handover
Value range: 160
Unit: second

______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 54 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

Content: when a new SDCCH channel is assigned, a timer should be turned on, and
handover is allowed only when this timer is overflow. This parameter is the timing time
of this timer. It is the set protection time used to avoid wrong handover due to inaccurate
measuring reports at the start of call setup. When the measuring report is processed at
BTS side, the parameter can be set smaller; when it is processed at BSC side, the set
parameter can have a longer interval.
Recommended value: 2
Minimum interval for continuous handover
Value range: 160
Unit: second
Content: a timer should be started after a handover command is sent, and handover
judgment is made only when the timer is overflow. This parameter is the timing time of
this timer. This is to prevent continuous frequency changes from causing the deterioration
of the global network quality and adding to processor load.
Recommended value: 6
Minimum interval of new emergent handover
Value range: 160
Unit: second
Content: the timing time to start an emergent handover barring timer after completion of
an emergency handover or failure of an emergency handover attempt.
Recommended value: 6
Co-BSC/MSC adjustment allowed
Value range: Yes, No
Unit: None
Content: indicating whether to adjust candidate cell array so that handover takes place in
the same BSC/MSC in priority.
Recommended value: Yes
Signaling channel handover allowed
Value range: Yes, No
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 55 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

Unit: None
Content: determining whether to hand over signaling channel.
Recommended value: No
Penalty processing allowed
Value range: Yes, No
Unit: None
Content: determining whether penalty is allowed to target cells in which handover has
failed, or to the original service cell that did handover with too large a time advance or
bad quality. That is to say, when the target cell congestion causes handover failure, to
prevent the system from another handover to that cell, some penalty should be rendered
to the target cell; in the same way, when handover is caused by too large a time advance
or damaged channel, it can easily result in a "ping-pong" handover; in this case, penalty
should be given to the original service cell. Those penalty measures can be used in cells
in the same BSC and in external cells as well.
Recommended value: Yes
In-cell handover allowed
Value range: Yes, No
Unit: None
Content: determining whether in-cell handover is allowed. In-cell handover includes time
slot change and handover to another carrier. bad transmission quality due to "Rayleigh"
fading or co-frequency interference can be improved through in-cell handover, but it can
not distinguish temporary interference from time dispersal on. So when time dispersal
exists, in-cell handover does not have any significance. This parameter does not affect
concentric handover.
Recommended value: No
Load handover allowed
Value range: Yes, No
Unit: None
Content: determining whether to make traffic load sharing handover. Load sharing can
lower the channel assignment failure rate due to cell congestion, so that services are more
evenly distributed in all cells, the cell congestion rate is lowered, so as to improve
network performance. It works only in the same BSC or in cells on the same layer, and
mainly for TCH channels. Load handover largely acts as the emergent measure for
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 56 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

abnormally high traffic in some regional wireless networks, but not as the main solution
to traffic congestion. If load handover occurs always in that part of a network,
consideration should be made to adjust the base station sector carrier configuration and
network layout.
Recommended value: Yes
Note: extra interference might result from intense frequency multiplexing.
Fast moving micro cell handover algorithm allowed
Value range: Yes, No
Unit: None
Content: deciding whether to use this algorithm to process fast moving MS. It can be
used to hand over fast moving MS to a macro cell, so as to reduce the handover times. It
is recommended that it is only used in special areas (e.g., highways), so as to reduce CPU
load. This algorithm can be used only when suitable conditions are selected. Normally, it
is not activated.
Recommended value: No
Emergent handover algorithm during fast receiving level drop allowed
Value range: Yes, No
Unit: None
Content: this shows whether to use the emergency handover algorithm during fast
receiving level drop. It is used to make mobile phone handover before calldrop due to fast
receiving level fast drop so as to avoid calldrop. This algorithm can be used only when
suitable conditions are selected. Normally, it is not activated. To activate this handover
algorithm, it is required that there should be original measuring reports in BSC.
Recommended value: No
PBGT handover algorithm allowed
Value range: Yes, No
Unit: None
Content: indicating whether to use the PBGT handover algorithm. PBGT handover is
processed on the LAPD board at present. To avoid ping-pong handover, PBGT handover
occurs only between cells at the same level and at the same layer, and can only be
triggered on the TCH channel, not allowed on the SDCCH channel. Flexible use of the
PBGT handover algorithm can effectively avoid co-frequency interference from the
adjacent cells.
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 57 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

Recommended value: Yes


After-handover power budget allowed
Value range: Yes, No
Unit: None
Content: indicating whether MS is allowed to be connected to new channels with
optimized power instead of max. This can reduce system interference, and improve
service quality (this parameter functions in BSC).
Recommended value: No
BTS measuring report preprocessing
Value range: Yes, No
Unit: None
Content: indicating whether to make measuring report preprocessing in BTS. When its
value is "No", it means that preprocessing occurs in BSC. In this case, the two parameters
"transmitting original measuring report" and "transmitting BS/MS power level" no longer
function; when it is "Yes", it reduces Abis interface signaling and BSC load, and
improves response time and network performance. This switch determines where power
control occurs. When it is set to "Yes", the power control is made at BTS side, and when
it is set to "No", BSC side will handle power control. The setting of this parameter must
consider whether BTS supports the set power control algorithm.
Recommended value: No
Note:
1. It must be set to "Yes" under the configuration of 15: 1, otherwise, the link rate might
not be enough.
2. The measuring report pre-processing and power control test conclusion of BTS22C
0110 version (micro cell 0110) are POK (most part of the test results are correct); so at
the base station of this version, the parameter must be set to "No".
3. When the parameter is set to "Yes", BTS3.X 0407 version supports only generation I
power control; versions after BTS3.X 03.0529 version support both generation I and
generation II power control, but need the support of versions BSC07.0520 and 1120
accordingly; wrong setting will cause sites to fail running.
4. No matter what data configuration looks like, BSC 01.06.0520b and BSC 01.06.0520c
both will issue generation I power control data, and the algorithm selection is also
generation I power control;

______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 58 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

5. Versions after BTS3X 00.0529 and BSC 00.07.0520B can support the down-shift of
generation II power control, but in this case preprocessing should be activated so as to set
generation II power control data.
7. Versions before BTS3X 0407 version and BSC 06.0520 version (inclusive) don't
support generation II power control down-shift;
8. BTS2X (including all versions of BTS23, BTS24, and BTS22C) and online versions
all support generation I power control, but not generation II power control down-shift.
Transmitting original measuring reports
Value range: Yes, No
1Unit: None
Content: indicating whether to send original measuring reports to BSC after measuring
report preprocessing on BTS. When the parameter is set to "Yes", BTS transmits to BSC
not only the processed measuring reports, but also the original reports.
Recommended value: No
Note: under the configuration of 15: 1, when the SDCCH/8 number is more than 2, it
must be set to "No".
Transmitting BS/MS power level
Value range: Yes, No
Unit: None
Content: indicating whether to transmit the BS/MS power level from BTS to BSC.
Sending BS/MS power level is to observe the effect of power control on BTS;
meanwhile, after preprocessing is activated, if BS/MS power level is not reported, it will
affect the uplink/downlink balance measuring results; besides, handover types such as
PBGT handover and concentric handover that needs power compensation will be
abnormal.
Recommended value: Yes
Note: starting from the 01.1120A version, the default value of this parameter changes
from "No" to "Yes".
Preprocessed measuring report reporting frequency
Value range: no reporting, twice every second, once every second, once every 2 seconds,
and once every 4 seconds.
Unit: None
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 59 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

Content: indicating the interval when measuring report preprocessing occurs at the BTS
side and preprocessing measuring reports are sent to BSC
Recommended value: twice every second
once every second (in data configuration of 15: 1)
Note: as the program processes the statistics time and duration involved in handover
algorithms into number of measuring reports (e.g., 4 seconds correspond to 8 measuring
reports), so when measuring reports are reported less than twice a second, it will affect
the handover speed, causing handover hysteresis.
Cell description data table
Cell layer
Value range: 1 4, which correspond respectively to the PICO layer, MICRO layer,
MACRO layer, and UMBRELLA layer
Unit: layer
Content: the whole network designed by Huawei takes the 4-layer network as the basic
frame, respectively the layers of Umbrella, Macro, Micro, and Pico. Each layer can be set
with 16 priority class. This provides the service carrier with sufficient network planning
space so as to fit various complex networking environments. Among them, the Macro
layer is the major 900 layer, Micro is the major 1800 layer, and Pico is the 900 and 1800
micro cell layer. The smaller the layer value, the higher the priority.
Recommended value: 3
Cell priority
Value range: 116
Unit: level
Content: refer to the description of "cell layer ", which is used to control the handover
priority between cells on the same layer; normally, the priority of cells on the same layer
is set the same. For cells on the same layer, the smaller the priority value, the higher the
priority.
Recommended value: 1
Inter-layer handover threshold
Value range: 063
Unit: level grade value
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 60 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

Content: a bit in handover priority, which affects cell sorting; when the downlink level of
a cell is lower than inter-layer handover threshold, this cell participates in candidate cell
sorting only with its level, and it sits at a lower priority in comprehensive sorting; layered
and hierarchical handover and load handover all require that the target cell be higher than
the inter-layer handover threshold (as determined in the program), otherwise, handover
might occur from the high load (high priority) and high level cells to lower load (lower
priority) and low level cells, thus causing calldrop; inter-layer handover threshold should
be set to >= edge handover threshold inter cell handover hysteresis.
Recommended value: 25
Inter layer handover hysteresis
Value range: 063
Unit: level grade value
Content: hysteresis value during handover between cells on different layers or between
different priority class (inter-layer handover threshold in service cells = configured inter
layer handover threshold - inter-layer handover hysteresis; and adjacent cell inter-layer
handover threshold = configured inter-layer handover threshold + inter layer handover
hysteresis), so as to restrict inter-layer ping-pong handover.
Recommended value: 3
Speed penalty value
Value range: 063
Unit: level grade value
Content: it is the level penalty value to adjacent cells when MS fast moves; it is only
allowed for the umbrella layer to render penalty to cells at the other 3 layers, and not to
other layers. This parameter functions only within the speed penalty time.
Recommended value: 30
Speed penalty time
Value range: 0255
Unit: second
Content: indicating that the penalty to adjacent cells to which a fast moving MS moves
within this period of time is valid.
Recommended value: 40
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 61 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

Minimum downlink power in candidate cell handover


Value range: 063
Unit: level grade value
Content: minimum downlink receiving level requirement for all handover candidate cells.
Recommended value: 15
Note: notice the influence of this value on handover success rate.
Maximum MS transmitting power level
Normal Value range: 020, not prepared according to protocol specification, according
to which, the dBm values corresponding to the control level for GSM900 and GSM1800
cells are not same. The 32 maximum transmitting power control levels corresponding to
GSM900 are:
{39, 39, 39, 37, 35, 33, 31, 29, 27, 25, 23, 21, 19, 17, 15, 13, 11, 9, 7, 5, 5, 5, 5, 5, 5, 5, 5,
5, 5, 5, 5}
The 32 maximum transmitting power control levels corresponding to GSM1800 are:
{30, 28, 26, 24, 22, 20, 18, 16, 14, 12, 10, 8, 6, 4, 2, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
36, 34, 32}
Unit: Control level
Content: this parameter is mainly used for the judgment of the M rule for mobile phones
in the private mode. The M rule is the minimum rule to determine if an adjacent cell of
MS can become a candidate adjacent cell. Its judgment is similar to the C1 rule during
cell selection: M="MS actual receiving level" "handover candidate cell minimum
downlink power" MAX(("MS maximum transmitting power level" "MS maximum
transmitting power"), 0)"minimum access level offset". Only when M0, can an MS
adjacent cell become a candidate adjacent cell.
Recommended value: 5(900M); 0(1800M)
Optimal uplink receiving level
Value range: 063
Unit: level grade value
Content: uplink receiving level to be obtained on a new channel during mobile phone
handover. It is used for after-handover power predicting algorithm. In generation I power
control, it is configured according to the "expected stable signal strength" in the "MS
power control data table"; in the generation II power control algorithm, it keeps
consistent with the "uplink signal strength upper threshold".
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 62 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

Cell type
Value range: normal cell, concentric cell
Default value: normal cell
External cell description data table
Same as above
Cell adjacency relationship table
Adjacent cell number
Index value of this adjacent cell, which can be in two cases: Case one: if adjacent cell
module number is not an external cell, the adjacent cell number value range is within 0
255; Case two: if adjacent cell module number is an external cell, then the adjacent cell
number value range is between 0799.
PBGT handover threshold
Value range: 0127, corresponding to 6463dB
Unit: None
Content: indicating that handover to PBGT in an adjacent cell can be made only when the
difference between the downlink level of an adjacent cell and the downlink level in the
service cell is greater than the PBGT handover threshold. When PBGT handover is
activated, and when "inter-cell handover hysteresis" "PBGT handover threshold
(corresponding dB value)", the "inter-cell handover hysteresis" acts instead of the "PBGT
handover threshold". The threshold should also be adjusted according to the handover
performance statistics result and the actual network.
Recommended value: the value is about 68 in populous urban areas; but in suburbs, the
value is about 72.
Inter-cell handover hysteresis
Value range: 063
Unit: level grade value
Content: indicating the handover hysteresis between adjacent cells on the same layer. The
purpose of setting this parameter is to reduce the "ping-pong" effect. But if cells are not
on the same layer, the value is invalid. Hysteresis should also be adjusted according to the
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 63 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

handover performance statistic results and the actual network. Flexible setting of this
value can offer effective guide to the handover and traffic between two adjacent cells.
Recommended value: in populous urban areas, the value is about 4; but in suburbs, the
value is about 8.

Minimum access level offset


Value range: 063
Unit: level grade value
Content: this offset is based on the "handover candidate cell minimum downlink power".
For different adjacent cells, different offsets can be defined. For a corresponding adjacent
cell to enter a candidate queue, it must be greater than the sum of the "handover candidate
cell minimum downlink power" and this offset.
Recommended value: 0
Filter data table
number of measuring reports allowed to lose in complementary calculations
Value range: 032
Unit: number of measuring reports
Content: it indicates the number of continuous measuring reports allowed to lose during
complementary calculations. If the number of measuring reports lost continuously is less
than this value, then based on the values of two successively received measuring reports,
the lost measuring report value is a linear inserted value. Otherwise, the previous
measuring reports are discarded, and calculations are made again when new measuring
reports arrive.
Recommended value: 4
Voice/data channel signal strength filter length
Value range: 132
Unit: None
Content: indicating the number of forward fetched values during mean calculation of
voice /data channel signal strength during measuring reports mean calculation. This can
avoid the swift drop of signal level due to "Rayleigh" attenuation, as well as partial
analysis as to whether handover is needed. When the filtering window is set too large, as
impact from bursts will be weaker but system response will slow down, so that some
effective measures (e.g., handover) cannot be timely implemented, thus resulting in a
drop of the global network quality.
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 64 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

Recommended value: 6
Voice /data channel signal quality filter length
Value range: 132
Unit: None
Content: indicating the number of forward fetched values during mean calculation of
voice /data channel quality during measuring reports mean calculation.
Recommended value: 6
Signaling channel signal strength filter length
Value range: 132
Unit: None
Content: indicating the number of forward fetched values during mean calculation of
signaling channel signal strength during measuring reports mean calculation. As MS stays
on signaling channels shorter than on traffic channels, the value should be
correspondingly smaller.
Recommended value: 3
Signaling channel signal quality filter length
Value range: 132
Unit: None
Content: indicating the number of forward fetched values during mean calculation of
signaling channel quality during measuring reports mean calculation. As MS stays on
signaling channels shorter than on traffic channels, the value should be correspondingly
smaller.
Recommended value: 3
Adjacent cell filter length
Value range: 132
Unit: None
Content: indicating the number of forward fetched values during mean calculation of
signal strength in adjacent cells during measuring reports mean calculation. This can
avoid the swift drop of signal level due to "Rayleigh" attenuation, as well as partial
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 65 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

analysis as to whether handover is needed. When the filtering window is set too large, as
impact from bursts will be weaker but system response will slow down, so that some
effective measures (e.g., handover) cannot be timely implemented, thus resulting in a
drop of the global network quality.
Recommended value: 6
TA filter length
Value range: 132
Unit: None
Content: indicating the number of forward fetched values during mean calculation of time
advance in measuring reports mean calculation.
Recommended value: 6
Penalty data table
Cell signal strength penalty during handover failure
Value range: 063
Unit: level grade value
Content: indicating the signal level grade value for target cell penalty in order to prevent
re-attempt of the system to hand over to the target cell again when it causes handover
failure due to reasons such as congestion. This value is valid only within the handover
failure penalty duration.
Recommended value: 30
Handover failure penalty duration
Value range: 060
Unit: second
Content: indicating the time of penalty to corresponding target cells during handover
failure.
Recommended value: 10
Cell signal strength penalty during handover failure due to bad quality
Value range: 063
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 66 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

Unit: level grade value


Content: signal strength value at which penalty is given to the original service cell after
emergency handover due to bad quality so as to avoid "ping-pong" handover; it is valid
only during handover penalty duration due to bad quality.
Recommended value: 63
Handover penalty duration due to bad quality
Value range: 060
Unit: second
Content: indicating the time of penalty to the original service cell after emergency
handover due to bad quality.
Recommended value: 10
Signal strength penalty for time advance handover
Value range: 063
Unit: level grade value
Content: signal strength penalty value to the original service cell after emergency
handover due to a time advance, so as to avoid "ping-pong" handover; it is valid during
the penalty duration for handover due to a time advance.
Recommended value: 63
Penalty duration for handover due to a time advance
Value range: 060
Unit: second
Content: indicating penalty duration to the original service cell after emergency handover
due to a time advance.
Recommended value: 10
Concentric handover failure penalty time
Value range: 016
Unit: second
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 67 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

Content: the time (i.e., the set value of this parameter) during which a call is barred from
reinitiating concentric handover after a concentric handover failure (no matter it is
handover from big circle to small, or from a small circle to a big one).
Recommended value: 10
Emergency handover data table
Note: optimal cells are selected to speed up system response only according to the current
cell sorting sequence but not the PN sorting result in the HW II handover algorithm in
emergency handover (TA handover, handover due to bad quality, interference handover
and handover due to fast level drop)
Emergency handover TA restriction
Value range: 063
Unit: bit cycle
Content: when time advance this value, emergency handover is triggered
Recommended value: 63
downlink quality restriction during emergency handover
Value range: 070, corresponding to RQ (quality level 07)10
Unit: None
Content: indicating the downlink receives quality threshold for triggering emergency
handover. After frequency hopping or DTX is turned on, RQ will deteriorate (normal
phenomenon), so this value should be tuned to 70. This should also be adjusted according
to the current network quality and handover statistics. When emergency handover is
triggered, what is first selected is outgoing cell handover, and in-cell handover is
triggered only when in-cell handover is activated and when there are no other candidate
cells.
Recommended value: 60
uplink quality restriction during emergency handover
Value range: 070, corresponding to RQ (quality level 07)10
Unit: None
Content: uplink receives quality threshold for triggering emergency handover. After
frequency hopping or DTX is turned on, RQ will deteriorate (normal phenomenon), so
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 68 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

this value should be tuned to 70. This should also be adjusted according to the current
network quality and handover statistics. When emergency handover is triggered, what is
first selected is outgoing cell handover, and in-cell handover is triggered only when incell handover is activated and when there are no other candidate cells.
Recommended value: 60
interference handover uplink quality threshold
Value range: 070, corresponding to RQ (quality level 07)10
Unit: None
Content: service cell uplink receives quality threshold for triggering interference
handover. After frequency hopping or DTX is turned on, RQ will deteriorate (normal
phenomenon), so this value should be tuned to 60. This should also be adjusted according
to the current network quality and handover statistics. During interference handover
triggering, cells are selected according to normal sorting results made once. If the local
cell is arranged in the first place and its in-cell handover is activated, the local cell is
selected; otherwise, the second candidate cell is selected.
Recommended value: 50
downlink quality threshold for interference handover
Value range: 070, corresponding to RQ (quality level 07)10
Unit: None
Content: downlink receives quality threshold for triggering interference handover. After
frequency hopping or DTX is turned on, RQ will deteriorate (normal phenomenon), so
this value should be tuned to 60. This should also be adjusted according to the current
network quality and handover statistics. During interference handover triggering, cells are
selected according to normal sorting results made once. If the local cell is arranged in
first place and its in-cell handover is activated, the local cell is selected; otherwise, the
second candidate cell is selected.
Recommended value: 50
Note: interference handover quality must be higher than emergency handover quality
uplink receive power threshold for interference handover
Value range: 063
Unit: level grade value
Content: it is the minimum uplink receiving power threshold that a service cell is required
to reach during interference handover triggering due to uplink quality reasons, and only
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 69 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

in such cases, is it judged as uplink interference. During interference handover triggering,


cells are selected according to normal sorting results made once. If the local cell is
arranged in first place and its in-cell handover is activated, the local cell is selected;
otherwise, the second candidate cell is selected
Recommended value: 25
downlink receive power threshold during interference handover
Value range: 063
Unit: level grade value
Content: it is the minimum downlink receiving power threshold that a service cell is
required to reach during interference handover triggering due to downlink quality
reasons, and only in such cases, is it judged as downlink interference. During interference
handover triggering, cells are selected according to normal sorting results made once. If
the local cell is arranged in first place and its in-cell handover is activated, the local cell is
selected; otherwise, the second candidate cell is selected.
Recommended value: 30
uplink level short term filter length
Content: a short-term uplink level filter length, usually having the default value 3. This
parameter is not used.
Filter parameters A1A8
Value range: 020
Unit: None
Recommended value: 10
Content: used for fast dropping filter configuration, altogether 9 parameters for the filter
together with parameter B. The corresponding formula is (in the program, A1 A8 are
the configuration values minus 10, and B is the negative of the configuration value):
C1(nt)=A1C(nt)A2C(ntt)A3C(nt2t) A8C(nt7t), where C(nt) is
the receive signal level in the uplink measuring report of the service cell at the moment
nt. If C1(nt)B, and C(nt) is below the edge handover threshold, then the signal level is
considered to be fast dropping.
Filter parameter B
Value range: 0255
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 70 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

Unit: None
Recommended value: 0
Content: used for parameter configuration of the fast dropping filter; refer to the
explanation of filters A1A8.
Listed below are the error code rates corresponding to the quality grades:
Quality grade

Actual BER range

Less than 0. 2%

0.2% to 0.4%

0.4% to 0.8%

0.8% to 1.6%

1.6% to 3.2%

3.2% to 6.4%

6.4% to 12.8%

Greater than 12.8%

Minimum time advance


Value range: 063
Unit: bit cycle
Content: the minimum TA value in which MS is handed over from the external ring
extended cell to an internal ring normal cell in case of extended cells.
Recommended value: 0
Load handover data table
Load handover allowing system traffic level threshold
Value range: 0, 811; its corresponding values: 0, 70, 80, 90, 95
Unit: system traffic level
Content: load handover is allowed only when system flow (signaling flow) is lower than
this threshold value. Handover above the maximum threshold will bring about
unimaginable consequences to the system, so the value should not be set too high.
Recommended value: 10
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 71 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

Load handover starting threshold


Value range: 07. Its corresponding values: 0, 50, 60, 70, 75, 80, 85, 90
Unit: cell load level
Content: starting load handover when cell load is higher than this threshold value, i.e.,
load handover is started when the seized TCH in a cell reach the corresponding
percentage.
Recommended value: 5
Load handover receive threshold
Value range: 07. Its corresponding values: 0, 50, 60, 70, 75, 80, 85. 90
Unit: cell load level
Content: when the cell load is lower than this threshold, the cell is able to receive users
handed over from other cells due to load, i.e., this cell refuses to accept users handed over
due to load from other cells if the cell in the Idle mode has TCH lower than a
corresponding percentage.
Recommended value: 2
Load handover bandwidth
Value range: 063
Unit: level grade value
Content: the setting of this value is related to that of the edge handover threshold. The
edge handover threshold acts as the threshold for allowing load handover. Only when the
receiving level of the user in the service cell falls within the range of {edge handover
threshold, edge handover threshold + load handover bandwidth }, is load handover
allowed.
Recommended value: 25
Hierarchical load handover cycle
Value range: 160
Unit: second
Content: when a certain cell reaches the conditions of load handover, all calls taking it as
their service cell will send a handover request at the same time, causing a sudden increase
in processor load, which will cause calldrop due to target cell congestion in certain cases.
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 72 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

So, the algorithm of hierarchical load handover is used to control handover number. This
cycle refers to the time required for handover at each level.
Recommended value: 10
Hierarchical load handover step-length
Value range: 163
Unit: level grade value
Content: during hierarchical load handover, the load handover band starts from the
handover threshold; each handover increases the width by one step-length.
Recommended value: 5
Normal handover data table
Uplink edge handover threshold
Value range: 063
Unit: level grade value
Content: within a certain statistic time, edge handover will occur if the uplink receiving
level remains lower than the value for a certain period of time. After PBGT handover is
activated, the corresponding edge handover threshold will drop. When without PBGT
handover, if the edge handover threshold is inappropriately set, it will easily cause crosscell coverage and adjacent co-frequency interference. The threshold should also adjusted
according to the handover performance statistic results and the actual network so as to
reach a basic uplink/downlink balance.
Recommended value: 25 (with no PBGT handover, urban); 15 (stand-alone sites in
suburban counties); and 15 (activating PBGT handover, urban)
downlink edge handover threshold
Value range: 063
Unit: level grade value
Content: within a certain statistic time, edge handover will occur if the downlink
receiving level remains lower than the value for a certain period of time. After PBGT
handover is activated, the corresponding edge handover threshold will drop. When
without PBGT handover, if the edge handover threshold is inappropriately set, it will
easily cause cross-cell coverage and adjacent co-frequency interference. The threshold
should also adjusted according to the handover performance statistic results and the
actual network so as to reach a basic uplink/downlink balance.
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 73 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

Recommended value: 30 (with no PBGT handover, urban); 20 (stand-alone sites in


suburban counties); and 20 (activating PBGT handover, urban)
Note: (uplink) downlink edge handover threshold <(uplink) downlink signal strength
lower threshold
Edge handover statistic time
Value range: 116
Unit: second
Content: making statistics of the uplink and downlink receiving level within this time
range, so as to determine whether it is edge handover.
Recommended value: 5
Note: in the program, the set value is processed into the corresponding number of
measuring reports (MR); 5 means 10 MR, and 4 means 8 MR.
After the measuring report preprocessing switch is turned on, the measuring report
frequency will affect the handover speed.
Edge handover duration
Value range: 116
Unit: second
Content: the duration length during which the receiving level of the uplink or downlink
remains lower than the edge handover threshold within the edge handover statistics time
when edge handover judgment is made.
Recommended value: 4
PBGT handover statistics time
Value range: 116
Unit: second
Content: time during which path loss statistics is made on adjacent cells, so as to see
whether PBGT handover should be triggered.
Recommended value: 5
PBGT handover duration
Value range: 116
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 74 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

Unit: second
Content: time length during which adjacent cells should meet the PBGT handover
conditions while PBGT handover is judged during the statistics time.
Recommended value: 4
Inter-layer handover statistics time (second)
Value range: 116
Unit: second
Content: time used to make sorting statistics on the candidate cells when better cells than
the current service cell exist.
Recommended value: 5
Inter layer handover duration (second)
Value range: 016
Unit: second
Content: during the whole statistics time, if a cell remains in first position among all
candidate cells during this period, it is judged as the best cell.
Recommended value: 4
Fast moving handover data table
Fast moving cell statistics number
Value range: 110
Unit:
Content: statistics of MS to see whether it is the sum P of fast moving cells. If this value
is too large, it will lead to the sudden increase of system flow, but if it is too small, it will
lead to inaccurate judgment of fast moving MS.
Recommended value: 3
Actual number of cells fast past
Value range: 110
Unit: piece
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 75 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

Content: total N of cells MS actually fast passes, i.e., when N cells among all P cells that
MS has currently passed are those passed quickly, the fast moving micro cell handover
algorithm is started.
Recommended value: 2
Fast moving time threshold
Value range: 0255
Unit: second
Content: time threshold (2r/v) determined according to cell radius (r) and moving speed
(v). If the time MS uses to pass this cell is less than the threshold, it means that MS
passes this cell fast.
Recommended value: 15
In-cell continuous handover control table
Maximum number of continuous handover
Value range: 120
Unit: times
Content: when two in-cell handovers occur below a time threshold, the two in-cell
handovers are regarded continuous. After occurrence of multiple continuous in-cell
handovers, in-cell handover will be barred within a certain period of time; this parameter
is the times of continuous in-cell handover allowed in the cell.
Recommended value: 3
Barring time after maximum occurrence of continuous handover
Value range: 1200
Unit: second
Content: an in-cell handover barring timer will be started after the occurrence of a
maximum number of continuous in-cell handover, and its timing time is called the
"barring time after maximum occurrence of continuous handover".
Recommended value: 20
interval to regard handover as continuous
Value range: 1200
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 76 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

Unit: second
Content: indicating the interval in which two internal handovers are regarded as
continuous.
Recommended value: 6
GSM0508 handover data table
The GSM0508 handover algorithm is not recommended, and this table is not configured.
Concentric handover data table
Strength difference between Internal and external circle signals
Value range: 063
Unit: dB
Content: internal and external circle power difference will lead to different signal strength
mobile phone receives from internal and external circles. This parameter indicates the
power compensation to the internal circle, normally the sum of the internal/external
power amplification power difference, the combiner loss difference, the path loss caused
by different antennas, and the path loss caused by different frequency selectivity. As can
be seen from actual measurements, multi-point measurements should be done when
internal/external circles use different antennas.
Recommended value: None, to be determined according to actual circumstances.
Receiving level threshold
Value range: 063
Unit: level
Content: determining the internal/external circle area together with the receiving level
hysteresis, TA threshold, and TA hysteresis; it must be greater than the edge handover
threshold value.
Recommended value: edge handover threshold +internal/external circle signal strength
difference; set temporarily to 25.
Receiving level hysteresis
Value range: 063
Unit: dB
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 77 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

Content: determining the internal/external circle area together with the receiving level
threshold, TA threshold, and TA hysteresis
Recommended value: 5
TA threshold
Value range: 063
Unit: bit cycle. 1 bit cycle corresponds to 0.55km
Content: determining the internal/external circle area together with the receiving level
threshold, receiving level hysteresis, and TA hysteresis; it must be greater than the TA
emergency handover threshold value.
TA hysteresis
Value range: 063
Unit: bit cycle, 1 bit cycle corresponding 0.55km
Content: determining the internal/external circle area together with the receiving level
threshold, receiving level hysteresis, and TA threshold
Note: the above 4 parameters determine the coverage range of internal and external
circles.
Internal circle area can be indicated as follows:
Receiving level >= receiving level threshold + receiving level hysteresis and TA < TA
threshold - TA hysteresis
External circle area can be indicated as follows:
Receiving level <= receiving level threshold - receiving level hysteresis or TA > =TA
threshold + TA hysteresis
The internal circle and external presented in the formula has a "blank" stripe in between,
i.e.,
Receiving level threshold - receiving level hysteresis <= receiving level <= receiving
level threshold + receiving level
Hysteresis and TA threshold - TA hysteresis <= TA < TA threshold + TA hysteresis
The field is the hysteresis stripe of concentric circles, and its function is to prevent pingpong handover.
When the TA threshold has the value 63, and the TA hysteresis has the value 0, the
boundary of the internal circle is completely determined by the receiving level parameter;
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 78 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

when the receiving level threshold has the value 63 and the receiving level hysteresis is 0,
the internal circle boundary is determined completely by the TA parameter.
Concentric handover statistics time
Value range: 016
Unit: second
Recommended value: 5
Concentric handover duration
Value range: 016
Unit: second
Recommended value: 4
Assign optimal layer
Value range: system optimized, external circle and internal circle not optimized
Content: in concentric cells, TCH assignment can be in the following modes: selection
can be made to assign the priority service layer based on system judgment according to
measuring reports on SDCCH; select external circle in priority to make TCH
assignment; select internal circle in priority to make assignment; no special
processing.
Recommended value: system optimization
Assign optimal level threshold
Value range: 063
Unit: dBm
Content: after selection of assigning optimal layer as "system optimization", the current
SDCCH level grade value can be estimated (inserted, filtered) with the uplink measured
value in the previous SDCCH measuring report; furthermore, comparison can be made
with "assign optimal level threshold" to assign the external circle or internal circle
channels.
Recommended value: if SDCCH is on an external circle: edge handover threshold
+internal/external circle signal strength difference + balanced uplink/downlink margin +
SDCCH and TCH differential margin; if SDCCH is on an internal circle: edge handover
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 79 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

threshold + uplink/downlink balanced margin + SDCCHand TCH differential margin,


which is temporarily 25.
In-BSC into-cell handover optimal algorithm allowed
Value range: Yes, No
Content: when a cell is configured as a concentric cell, the two processing methods of
into-cell handover requests in BSC are: channel distribution undergoes no special
processing; providing cell judgment to concentric cells by increasing the BCCH
measurement values in the handover request messages between cells in BSC, comparing
with the receiving level threshold, without considering the receiving level hysteresis, so
as to select the service layer distributed in priority.
Recommended value: Yes
Incoming handover optimal layer
Value range: external circle, internal circle, none
Content: determining the layer on which the channel falls that is selected in priority
during incoming handover
Recommended value: none, to be determined by actual networking. For example, in
common networking, inter-BSC handover is triggered at the cell edge, in which case,
external circle channels can be selected in priority; in dual-band networking, most
900/1800 networks are constructed by sharing the sites, in which case incoming handover
is more frequent, and is not usually triggered at the cell edge, so, internal circle channels
are selected in priority.
Points for attention in configuration:
1. BCCH carrier frequencies must be configured in the external circle
2. SDCCH is configured in the external circle
3. If the receiving level threshold and the receiving level hysteresis are configured to 63
and 63, or, if the TA threshold and the TA hysteresis should be configured to 63 and 63,
handover between internal/external circle will be barred

2.5 Power control


Power control selection table
Power control algorithm selection
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 80 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

Value range: GSM_0508. HW_1. HW_2


Unit: None
Content: selecting the used power control algorithm
Recommended value: HW_2
Note: in the BTS3.X base station and the G2BTS32.30000.00.0529A base station
versions, the generation II power control down-shift base station is supported. When
BTS2X selects the HW_2 algorithm, power control must be performed at the BSC side.
When activating measuring report pre-processing, if we select the Huawei generation II
power control algorithm, even if we set all uplink/downlink power controls to off, some
individual BTS20 versions will meet the base station initialization failure problem.
1Uplink power control allowed
Value range: Yes, No
Unit: None
Content: whether to allow mobile phone power adjustment
Recommended value: Yes
Downlink power control allowed
Value range: Yes, No
Unit: None
Content: whether to allow mobile phone power adjustment
Recommended value: Yes
Normal cell power control data table
Note: it is the 0508 power control algorithm, not recommended, and need not be
configured. The table is hidden starting from the 1120A version.
Uplink power increasing receiving level threshold
Value range: 063
Unit: level grade value
Content: indicating that when the receiving signal level of an uplink is less than the set
value of this parameter, the power of MS can be increased by one level.
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 81 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

Recommended value: 20
Downlink power increasing receiving level threshold
Value range: 063
Unit: level grade value
Content: indicating that when the receiving signal level of an downlink is less than the set
value of this parameter, the power of BTS can be increased by one level.
Recommended value: 20
P1
Value range: 132
Unit: None
Content: making statistics for the receiving signal level of uplink or downlinks, so as to
determine the total measuring reports for the upward adjustment of uplink or downlink
power.
Recommended value: 12
N1
Value range: 132
Unit: None
Content: among P1 measuring reports in the statistics, if the receiving signal level in N1
reports meets the condition that it is lower than the receiving signal level threshold of
uplink or downlinks, MS or BTS power upward adjustment is triggered.
Recommended value: 10
Receiving level threshold for uplink power decrease
Value range: 063
Unit: level grade value
Content: indicating that when the receiving signal level of an uplink is higher than the set
value of this parameter, the power of MS drops by one level.
Recommended value: 40
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 82 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

Receiving level threshold for downlink power decrease


Value range: 063
Unit: level grade value Value range: 063
Content: indicating that when the receiving signal level of a downlink is higher than the
set value of this parameter, the power of BTS drops by one level.
Recommended value: 40
P2
Value range: 132
Unit: None
Content: making statistics for the receiving signal level of uplink or downlinks, so as to
determine the total measuring reports for the downward adjustment of uplink or downlink
power.
Recommended value: 20
N2
Value range: 132
Unit: None
Content: among P2 measuring reports in the statistics, if the receiving signal level in N2
reports meets the condition that it is higher than the receiving signal level threshold of
uplink or downlinks, MS or BTS power downward adjustment is triggered.
Recommended value: 19
Uplink power increasing receiving quality threshold
Value range: 07
Unit: level
Content: indicating that when the receiving signal level of an uplink is less than the set
value of this parameter, the power of MS can be increased by one level.
Recommended value: 5
Downlink power increasing receiving quality threshold
Value range: 07
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 83 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

Unit: level
Content: indicating that when the receiving signal level of a downlink is less than the set
value of this parameter, the power of BTS can be increased by one level.
Recommended value: 5
P3
Value range: 132
Unit: None
Content: making statistics for the receiving signal level of uplink or downlinks, so as to
determine the total measuring reports for the upward adjustment of uplink or downlink
power.
Recommended value: 7
N3
Value range: 132
Unit: None
Content: among P3 measuring reports in the statistics, if the receiving signal quality in
N3 reports meets the condition that it is lower than the receiving signal quality threshold
of uplink or downlinks, MS or BTS power upward adjustment is triggered.
Recommended value: 5
Uplink power decreasing receiving quality threshold
Value range: 07
Unit: level
Content: indicating that when the receiving signal quality of an uplink is less than the set
value of this parameter, the power of MS can drop by one level
Recommended value: 1
Downlink power decreasing receiving quality threshold
Value range: 07
Unit: level
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 84 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

Content: indicating that when the receiving signal quality of a downlink is greater than
the set value of this parameter, the power of BTS can drop by one level
Recommended value: 1
P4
Value range: 132
Unit: None
Content: making statistics for the receiving signal quality of uplink or downlinks, so as to
determine the total measuring reports for the downward adjustment of uplink or downlink
power
Recommended value: 18
N4
Value range: 132
Unit: None
Content: among P4 measuring reports in the statistics, if the receiving signal quality in
N4 reports meets the condition that it is higher than the receiving signal quality threshold
of uplink or downlinks, MS or BTS power downward adjustment is triggered.
1Recommended value: 15
BTS power control data table
Note: it is the generation I power control algorithm
Power control adjustment cycle
Value range: 110
Unit: SACCH cycle (480ms)
Content: the minimum time between two continuous power control commands.
Recommended value: 5
Expected stable downlink signal strength
Value range: 063
Unit: level grade value
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 85 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

Content: it defines the signal strength value expected to obtain at MS in a stable state.
Expected stable downlink signal strengthdownlink edge handover threshold (handover
parameter), otherwise, it will cause ping-pong handover due to power control.
Recommended value: 35
Downlink signal strength filter length
Value range: 132
Unit: None
Content: indicating the number of measuring reports in which the average of signal
strength of downlinks is taken in a stable state before BTS power adjustment. The
purpose of setting this parameter is to remove influence of mutation factors, so that
analysis of whether to make power adjustment is not too partial. When the filtering
window is too long, the influence due to mutation will be weakened, but the BTS power
adjustment is not timely; if the window is too short, BTS power adjustment will not be
accurate enough.
Recommended value: 5
Downlink path loss compensating factor
Value range: 0100
Unit:
Content: each time, the power adjustment range will change along with the variation of
the difference between the actual receiving level and the expected level. The downlink
compensating factor acts as the weighting coefficient of such different values. When the
difference is fixed, the greater the compensating factor, the greater the BTS power
adjustment.
Recommended value: 80
Expected downlink quality
Value range: 07
Unit: level
Content: the expected signal quality received at MS in a stable state, showing the power
adjustment direction.
Recommended value: 1

______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 86 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

Downlink quality filter length


Value range: 132
Unit: None
Content: indicating the number of measuring reports in which the average of signal
strength of downlinks is taken in a stable state before BTS power adjustment. The
purpose of setting this parameter is to remove influence of mutation factors, so that
analysis of whether to make power adjustment is not too partial. When the filtering
window is too long, the influence due to mutation will be weakened, but the BTS power
adjustment is not timely; if the window is too short, BTS power adjustment will not be
accurate enough.
Recommended value: 5
Downlink quality compensating factor
Value range: 0100
Unit:
Content: each time, the power adjustment range will change along with the variation of
the difference between the actual downlink quality and the expected downlink quality.
The downlink compensating factor acts as the weighting coefficient of such different
values. When the difference is fixed, the greater the compensating factor, the greater the
BTS power adjustment
Recommended value: 20
Minimum base station transmitting power
Value range: 036
Unit: dBm
Content: indicating the minimum transmitting power allowed by the base station. No
matter how big is the original base station power and the how many levels it can be
down-tuned, the transmitting power of the base station cannot be lower than this value.
Recommended value: 4
Maximum power control adjustment step-length
Value range: 116
Unit: level, 2dB at each level
Content: defining the maximum range of BTS power adjustment each time.
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 87 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

Recommended value: 8
Maximum base station transmitting power
Value range: 158
Unit: dBm
Content: indicating the maximum base station transmitting power, which is related to the
setting of power level in the carrier configuration table. The minimum value of the two is
taken as the maximum base station transmitting power. And the power adjustment cannot
exceed this range.
Recommended value: 46(macro cell), 36(22C), 39(3001C)
Base station power control level
Value range: 116. corresponding to 0dB30dB
Unit: level, every level corresponding to 2dB
Content: indicating the maximum level the base station dynamic power can be adjusted.
Recommended value: 16
Base station power control
MS power control data table
Note: it is a generation I power control algorithm
Registering cycle
Value range: 130
Unit: SACCH cycle (480ms)
Content: the minimum time between 2 continuous power control commands.
Recommended value: 5
Expected initial signal strength
Value range: 063
Unit: level grade value
Content: signal strength expected at the BTS receiver at the initial stage. The specific
value can be determined in reference to the actual cell planning, and the cell geographical
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 88 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

environment; but normally, its value should be greater than the signal strength in a stable
state.
Recommended value: 30
Filter length at the initial adjustment phase
Value range: 132
Unit: None
Content: indicating the number of measuring reports in which the average of signal
strength of uplinks is taken before MS power adjustment at the initial stage. The purpose
of setting this parameter is to remove influence of mutation factors, so that analysis of
whether to make power adjustment is not too partial. When the filtering window is too
long, the influence due to mutation will be weakened, but the MS power adjustment is
not timely; if the window is too short, MS power adjustment will not be accurate enough.
At the initial stage, the power adjustment of MS depends only on the receiving signal
level but considering no receiving signal quality. To lower MS transmitting power as
soon as possible, normally the value should be less than the filter length at the stable
stage.
Recommended value: 2
Expected stable state signal strength
Value range: 063
Unit: level grade value
Content: signal strength (normally the signal level at the edge of the adjusted area)
expected at the BTS receiver in the stable state. The expected stable state signal strength
uplink edge handover threshold (handover parameter), otherwise, it will cause pingpong handover due to power control.
Recommended value: 30
Stable stage signal filter length
Value range: 132
Unit: None
Content: indicating the number of measuring reports in which the average of signal
strength of uplinks is taken before MS power adjustment at the stable stage. The purpose
of setting this parameter is to remove influence of mutation factors, so that analysis of
whether to make power adjustment is not too partial. When the filtering window is too
long, the influence due to mutation will be weakened, but the MS power adjustment is
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 89 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

not timely; if the window is too short, MS power adjustment will not be accurate enough.
At the stable stage, the power adjustment of MS depends on the receiving signal level and
quality. Power adjustment in the stable state is started once the expected stable filtering
window is fall, no matter whether initialization adjustment is executed.
Recommended value: 5
Uplink compensating factor
Value range: 1100
Unit:
Content: a parameter required to calculate power adjustment, indicating the weighting
value of the difference between the actual receiving level and the expected receiving level
grade value on the MS transmitting power.
Recommended value: 80 (indicating that when the difference between the current level
and the ideal level is 5dB, power is adjusted by 4 dB. i.e., 5*80/100)
Expected uplink quality
Value range: 07
Unit: level
Content: indicating the signal quality received at the BTS receiver in the expected stable
state.
Recommended value: 1
Quality filter length at stable stage
Value range: 130
Unit: None
Content: indicating the number of measuring reports in which the average of uplink
quality is taken before MS power adjustment in the stable state. The purpose of setting
this parameter is to remove influence of mutation factors, so that analysis of whether to
make power adjustment is not too partial. When the filtering window is too long, the
influence due to mutation will be weakened, but the MS power adjustment is not timely;
if the window is too short, MS power adjustment will not be accurate enough.
Recommended value: 6
Uplink quality compensating factor
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 90 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

Value range: 0100


Unit:
Content: each time, power adjustment range will change along with the difference
between the actual uplink quality and the expected uplink quality. The uplink quality
compensating factor acts as the weighting coefficient of this difference; so when the
difference is fixed, the greater the compensating factor, the greater the MS required
power adjustment.
Recommended value: 20 (indicating that the difference between the current quality and
the ideal quality is 1 level, and power is adjusted by 2 dB. i.e., (1*20/100)*10)
Power raising range after handover failure
Value range: 04
Unit: level, every level corresponding to 2dB
Content: indicating the power level grade value raised when returning to the original
channel after handover failure to avoid calldrop. It is the mobile phone power raising
value after handover failure, so as to further raise handover power.
Recommended value: 2
Maximum power control adjusting step-length
Value range: 116
Unit: level, every level is 2dB
Content: indicating the maximum level by which the MS power can be dynamically
adjusted.
Recommended value: 8
In Huawei generation I power control algorithms, the transmitting power to be currently
adjusted = (expected stable state signal strength - current actual receiving signal strength)
* uplink (downlink) link compensating factor + (current actual receiving uplink
(downlink) link quality - expected uplink (downlink) link quality) *10* uplink
(downlink) quality compensating factor. The final power adjustment level should not
exceed the maximum power control step-length.
To determine the power level to be adjusted, we should find the error tolerance table
according to the current transmitting power level, and the final power adjustment level is
not allowed to exceed the specified value in the error tolerance table. The error tolerance
tables of 900M and 1800M are as follows:
1800M:
Level

10

11

12

13

14

15

16

17

______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 91 of
147

18

19

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

Error
2
tolerance

Error
2
tolerance

10

11 12

13

14

15 16

17

18 19

900M
1Level

HW generation II power control data table


Power control adjustment cycle
Value range: 130
Unit: SACCH cycle (480ms)
Content: specifying the minimum time between 2 continuous power control commands.
Recommended value: 5
Uplink level filter length
Value range: 120
Unit: None
Content: indicating the number of measuring reports in which the average of uplink
signal strength is taken before MS power adjustment.
Recommended value: 6
Downlink level filter length
Value range: 120
Unit: None
Content: indicating the number of measuring reports in which the average of downlink
signal strength is taken before BTS power adjustment.
Recommended value: 6
Uplink quality filter length
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 92 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

Value range: 120


Unit: None
Content: indicating the number of measuring reports in which the average of uplink
signal quality is taken before MS power adjustment
Recommended value: 6
Downlink quality filter length
Value range: 120
Unit: None
Content: indicating the number of measuring reports in which the average of downlink
signal quality is taken before MS power adjustment.
Recommended value: 6
Measuring report compensation switch
Value range: Yes, No
Unit: None
Content: after the switch is turned on, the currently received measuring reports should be
put into the measuring reports compensation queue. Next, the transmitting power change
information should be recorded according to the MS and BTS power values in the
measuring reports, so that after insertion of values into the measuring reports,
compensations should be made to the receiving level grade values in the historical
measuring reports according to the power change information.
Recommended value: Yes
Number of predicted uplink measuring reports
Value range: 03
Unit: number of measuring reports
Content: when generation II power control algorithms are adopted, no average filtering
values of the historical measuring reports are used for power control judgment, but rather,
predicting functions are added into filtering waves so as to cancel the hysteresis of power
adjustment. This parameter specifies the number of uplink measuring reports for
prediction.
Recommended value: 2
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 93 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

Number of predicted downlink measuring reports


Value range: 03
Unit: number of measuring reports
Content: when generation II power control algorithms are adopted, no average filtering
values of the historical measuring reports are used for power control judgment, but rather,
predicting functions are added into filtering waves so as to cancel the hysteresis of power
adjustment. This parameter specifies the number of downlink measuring reports for
prediction.
Recommended value: 2
Uplink signal strength upper threshold
Value range: 063
Unit: level grade value
Content: during calculation of power control step according to signal level, signal level
has both upper and lower thresholds. Signals between these two thresholds are not
adjusted, and power control is invoked only when the signal level gets out of these upper
and lower thresholds. The distance between these two thresholds should not be too large,
otherwise, power control will not be so sensitive to the change of receiving level, and the
fluctuation of receiving level will be too large. But it should not be too smaller either,
otherwise, power control will be too sensitive to the change of receiving level, so as to
result in power control oscillation. Besides, it can over-restrict the receiving quality
difference so as to raise the transmitting power and improve the receiving space. This
parameter specifies the upper threshold of uplink signals for power control. When the
signal level exceeds the above range, a power increment value ( sum of upper and
lower thresholds/2receiving level) is calculated, and this increment value together with
the maximum allowed adjustment step-length of the quality band at which the receiving
signal quality falls determines the actual step-length for the power adjustment.
Recommended value: 35
Uplink signal strength lower threshold
Value range: 063
Unit: level grade value
Content: during calculation of power control step according to signal level, signal level
has both upper and lower thresholds. Signals between these two thresholds are not
adjusted, and power control is invoked only when the signal level gets out of these upper
and lower thresholds. This parameter specifies the lower threshold of uplink signals for
power control. When the signal level exceeds the above range, a power decrease value
(receiving level sum of upper and lower threshold/2) is calculated. And this decrease
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 94 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

value together with the maximum allowed adjustment step-length of the quality band at
which the receiving signal quality falls determines the actual step-length for the power
adjustment
Recommended value: 25
Uplink signal good quality threshold
Value range: 07
Unit: level grade value
Content: during calculation of power control step according to signal quality, receiving
signal quality has both upper and lower thresholds. Power control is invoked only when
the signal quality gets out of these upper and lower thresholds signal quality. This
parameter specifies the uplink good quality threshold for power control.
Recommended value: 0
Uplink signal bad quality threshold
Value range: 07
Unit: level grade value
Content: during calculation of power control step according to signal quality, receiving
signal quality has both upper and lower thresholds. Power control is invoked only when
the signal quality gets out of these upper and lower thresholds of signal quality. This
parameter specifies the uplink bad quality threshold for power control.
Recommended value: 2
Downlink signal strength upper threshold
Value range: 063
Unit: level grade value
Content: during calculation of power control step according to signal level, signal level
has both upper and lower thresholds. Signals between these two thresholds are not
adjusted, and power control is invoked only when the signal level gets out of these upper
and lower thresholds. The space between these two thresholds should not be too large,
otherwise, power control will not be so sensitive to the change of receiving level, and the
fluctuation of receiving level will be too large. But it should not be too smaller either,
otherwise, power control will be too sensitive to the change of receiving level, so as to
result in power control oscillation. Besides, it can over-restrict the adjusted space while
receiving signal bad quality so as to raise the transmitting power. This parameter specifies
the upper threshold of downlink signals level for power control. When the signal level
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 95 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

exceeds the upper range, a power increment value ( sum of upper and lower
thresholds/2 receiving level) is calculated, and this increment value together with the
maximum allowed adjustment step-length of the quality band at which the receiving
signal quality falls determines the actual step-length for the power adjustment
Recommended value: 40
Downlink signal strength lower threshold
Value range: 063
Unit: level grade value
Content: during calculation of power control step according to signal level, signal level
has both upper and lower thresholds. Signals between these two thresholds are not
adjusted, and power control is invoked only when the signal level gets out of these upper
and lower thresholds. This parameter specifies the lower threshold of downlink signals
for power control. When the signal level exceeds the lower threshold, a power decrease
value (receiving level sum of upper and lower threshold/2) is calculated. And this
decrease value together with the maximum allowed adjustment step-length of the quality
band at which the receiving signal quality falls determines the actual step-length for the
power adjustment.
Recommended value: 30
Downlink signal good quality threshold
Value range: 07
Unit: level grade value
Content: during calculation of power control step according to signal quality, receiving
signal quality has both upper and lower thresholds. Power control is invoked only when
the signal quality gets out of these upper and lower thresholds of signal quality. This
parameter specifies the downlink good quality threshold for power control
Recommended value: 0
Downlink signal bad quality threshold
Value range: 07
Unit: level grade value
Content: during calculation of power control step according to signal quality, receiving
signal quality has both upper and lower thresholds. Power control is invoked only when
the signal quality gets out of these upper and lower thresholds of signal quality. This
parameter specifies the downlink bad quality threshold for power control
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 96 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

Recommended value: 2
Maximum allowed adjustment step-length in quality band 0
Value range: 030
Unit: dB
Content: Huawei generation II power control algorithms classify received signal quality
(RQ value) into three quality bands (0, 1 2, 3), and in every quality band is set
different maximum allowed power adjustment step-length. In this way, during power
adjustment according to level, different receiving quality is allowed different maximum
step-length adjustment. If the allowed maximum step-length adjustment is set too small,
the algorithm will not reach the purpose of fast power control; if it is set too large, it will
reduce the effectiveness of power control. This parameter specifies the maximum allowed
power step-length when RQ value is 0.
Recommended value: 16
Maximum allowed adjustment step-length in quality band 1
Value range: 030
Unit: dB
Content: This parameter specifies the maximum allowed power step-length when RQ
value is between (0, 1).
Recommended value: 8
Maximum allowed adjustment step-length in quality band 2
Value range: 030
Unit: dB
Content: This parameter specifies the maximum allowed power step-length adjustment
when RQ value3 during power adjustment according to level.
Recommended value: 4
Allowed adjustment step-length for power control according to quality
Value range: 04
Unit: dB
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 97 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

Content: specifying the allowed adjustment step-length during power control according to
received signal quality.
Recommended value: 4
Note: in Huawei generation II power control algorithm, first the power adjustment
request is given according to the received signal level and quality, then the power control
adjustment direction and step-length are obtained by integrating the two as follows:
Receiving level
control adjustment

power

Receiving quality
control adjustment

power

Level and quality integration


power control adjustment

AdjStep_Lev

AdjStep_Qul

maxAdjStep_Lev,AdjStep_Qul)

AdjStep_Lev

AdjStep_Qul

No action

AdjStep_Lev

No action

AdjStep_Lev

AdjStep_Lev

AdjStep_Qul

AdjStep_Lev

AdjStep_Lev

AdjStep_Qul

max(AdjStep_Lev,AdjStep_Qul)

AdjStep_Lev

No action

AdjStep_Lev

No action

AdjStep_Qul

AdjStep_Qul

No action

AdjStep_Qul

AdjStep_Qul

No action

No action

No action

Minimum allowed power of MS


Value range: 020
Unit: power level
Content: the lower limit of MS transmitting power when power control is turned on.
Recommended value: 19(900M), 15(1800M)
Maximum allowed power of MS
Value range: 020
Unit: level
Content: indicating the maximum allowed transmitting power of MS.
Recommended value: 5(900M), 0(1800M)
Maximum transmitting power of base station
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 98 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

Value range: 158


Unit: dBm
Content: indicating the maximum power that can be transmitted by a base station, which
is related to the power level setting in the carrier configuration table. The minimum value
of the two is taken as the maximum transmitting power of the base station. But power
adjustment cannot exceed this range.
Recommended value: 46 (macro cell), 36(22C), 39(3001C)
Level number of base station power control
Value range: 116; corresponding to 0dB30dB
Unit: level
Content: this indicates the maximum level number that a base station can be down-tuned
from the static power level.
Recommended value: 16

2.6 Channels
Wireless channel management control table
Channel distribution algorithm selection
Value range: Huawei generation I algorithms and Huawei generation II algorithms
Unit: None
Content: specifying channel distribution algorithm used in the cell. Huawei generation I
algorithms distribute channels in sequence; Huawei generation II algorithms select
priority distributed channels to distribute. To efficiently distribute channels, "Huawei
generation I algorithms" are recommended; to distribute optimal channels, "Huawei
generation II algorithms" are recommended.
Recommended value: Huawei generation I algorithms
Note: in version BSC1120 and subsequent versions, Huawei generation II algorithms are
recommended.
interference band pre-processing switch
Value range: Yes, No
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 99 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

Unit: None
Content: it determines whether channel management preprocesses interference bands.
Recommended value: No
Initial length of interference band filtering
Value range: 07
Unit: None
Content: If the local cell starts bad channel management, the configuration of this data is
valid. The initial length of interference band filtering means the number of reports of
radio frequency resources indication messages that start to be preprocessed.
Recommended value: 3
Length of averaged interference band
Value range: 031
Unit: None
Content: If the cell starts bad channel management, the configuration of this data is valid.
This parameter refers to the number of radio frequency resources indication message
reports in which the average of received interference band levels is calculated.
Recommended value: 6
The three parameters above are actually not used, and will not be available starting from
version OMC 01.1120A.
Whether SDCCH is dynamically distributed
Value range: Yes, No
Unit: None
Content: whether SDCCH is dynamically distributed.
Recommended value: Yes
Description: in the 0520B version, this function can be set dynamically. Command word:
configure channel management data, parameter: cell number. For the current 03.0529
base station version of BTS3X, when SDCCH dynamic distribution is turned on,
assignment failure and single-connection might occur, but this is already solved in the
05.0529 version of BTS3X.

______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 100 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

The host version G3BSC32.10100.07.0520B and subsequent versions all support force
recovery of SDCCH channels. When whether SDCCH are dynamically distributed is set
to "No" at the data management console, all SDCCH channels adjusted from TCH are
immediately recovered to TCH channels. In this case, all calls set up on this TCH channel
will be lost.
Idle SDCCH channel threshold
Content: when idle SDCCH channels in the cell are less than or equal to the set value of
this parameter, try to find an available TCH to convert to SDCCH channels. Initiating the
conversion flow from TCH to SDCCH, needs two more conditions besides that idle
SDCCH channels must be less than or equal to N1: the current idle TCH channels in the
cell are more than 4 or more than the number of TRXs; the number of current SDCCH
channels in the cell is less than the allowed maximum number of MaxSDCCH.
Recommended value: 2
Description: in the 0520B version, this item can be set dynamically. Command word:
configure channel management data, parameter: cell number.
The maximum number of SDCCH channel in the cell
Content: specifying the maximum number of SDCCH in the cell.
Recommended value: configured SDCCH in the cell + 8 (too big a value will not be good
for system recovery during abnormality)
Description: the value must be larger than the maximum number of SDCCH configured
in the cell, otherwise, dynamic SDCCH adjustment cannot occur. In the 0520B version,
the item can be set dynamically. Command word: configure channel management data,
parameter: cell number.
Note:
1. The processing flow of recovering SDCCH into TCH is as follows: every cell is set a
timer Count. Each time a TCH channel is converted into a SDCCH channel, the Counter
is set as ResTime. Every 3 seconds, Count is adjusted once. If the current idle SDCCH
channels > 8 + N1, then Count is subtracted by 3; if the current idle SDCCH channels < 8
+ N1, then add 12 to Count, but it must not exceed ResTime; if the current idle SDCCH
channels 8 + N1, then Count remains unchanged. After the adjustment, if Count <= 0,
then recover one TCH channel. This is the so-called "bucket" algorithm.
2. Due to TRX hardware processing capability restriction, every TRX can have at most 2
time slots configured as SDCCH. During initiating of converting TCH to SDCCH, if
there are calls on the selected TCH channel, the calls are handed over to other idle TCH
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 101 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

channels in the cell. During dynamic SDCCH channel distribution, each time only one
TCH is converted into SDCCH; when recovering SDCCH into TCH, each time only one
TCH channel is recovered.
3. During conversion from TCH to SDCCH, TCH channels on TRX where BCCH are
located should not be selected.
Minimum TCH recovery time (second)
Value range: 603600
Unit: second
Content: the minimum time during which TCH are converted into SDCCH and then
recovered into TCH.
Recommended value: 600
Description: in the 0520B version, this item can be set dynamically. Command word:
configure channel management data, parameter: cell number.
Idle TCH channel threshold N1
Value range: 0cell TCH time slot number
Unit: None
Recommended value: 2
TCH judgment application cycle T (minute)
Value range: 0~65535
Unit: minute
Recommended value: 10
Note:
1. The usage of "idle TCH channel threshold N1", "TCH judgment application cycle T
(minute)": setting parameters for the opportunity of mutual conversion between TCH and
dynamic PDCH.
2. Dynamic PDCH in default are TCH; dynamic PDCH can be converted into SDCCH
(when they are used as TCH); and dynamic PDCH can be converted into PDCH (even
though they are used as SDCCH);

______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 102 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

3. There are two supposes of dynamic PDCH control: to determine when BSC requests
PCU for TCH; to determine whether BSC refuses PCU channel requests.
4. A timer Count is set in every cell, initialized to 0. Count value range is TT. Count
is adjusted once every minute. If the current idle TCH channels > N1, then Count is
increased by 1, but it should not exceed T; if the current idle TCH channels <= N1, Count
is decreased by 1, but it still should not be less than -T. After adjustment, if Count < -T/2,
and if available dynamic PDCH channels are greater than 0, then BSC requests PCU for
TCH channels. When BSC receives channel request messages from PCU, it first check
Count value, and if Count < T/2, then BSC unconditionally refuses PCU channel
requests; in contrary, it will determine the response to PCU according to the PCU
requirements and current channel use.
Bad channel management control table
Bad channel management switch
Value range: Yes, No
Unit: None
Recommended value: No
Content: indicating whether bad channel management is made. At present, it is not used.
Bad channel definition threshold
Value range: 315
Unit: None
Content: definition value for a channel to change into a bad channel; it is now not used. A
bad channel is defined as a channel outside 5 interference bands.
Recommended value: 4
Bad channel alarming threshold
Value range: 115
Unit: None
Content: the parameter determines the number of bad channels required to make bad
channel alarming in a cell.
Recommended value: 10
Note: the table has been deleted in the OMC version that matches with the host version
01.1120A. No subsequent versions will include this table.
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 103 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

Channel distribution generation II algorithm data table


Note: to support channel distribution generation II algorithms, the BSC host software
should be upgraded to version G3BSC32.10100.01.1120A and versions above; LAPD
should be upgraded to version G3LAPV4.0.2000.11.20 and versions above; and OMC
should also be upgraded to a related version.
SDCCH channel optimal distribution allow ed
Value range: Yes, No
Unit: None
Recommended value: Yes
Content: if this data is "No", then SDCCH channel distribution adopts the polling mode;
if this data item is "Yes", then SDCCH channel distribution adopts optimal mechanisms.
Note: the parameter can be dynamically set, command word is "configure channel
management data", and the parameter is cell number
Use interfering priority allowed
Value range: Yes, No
Unit: None
Recommended value: Yes
Content: if this data item is "Yes", then the interfering priority in channel priority is valid;
otherwise, the interfering priority is invalid.
Seize channel interfering measuring allowed
Value range: Yes, No
Unit: None
Content: if this data item is "No", then judgment is made without seizing channel
interfering, nor sending interfering indication; otherwise, judgment will be made
according to the interference circumstances about the seized channel.
Recommended value: Yes
Use TRX priority allowed
Value range: Yes, No
Unit: None
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 104 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

Content: if this data item is "Yes", then the TRX priority in channel priority is valid;
otherwise, the TRX priority is invalid.
Recommended value: Yes
Using history records priority allowed
Value range: Yes, No
Unit: None
Content: if this data item is "Yes", then the history record priority in channel priority is
valid; otherwise, the history record priority is invalid
Recommended value: Yes
Balancing channel traffic distribution allowed
Value range: Yes, No
Unit: None
Content: if this data item is "Yes", then the initial value range of random channel ranging
is selected; otherwise, the next channel after the previously distributed channel is taken as
the start point of channel ranging
Recommended value: Yes
Uplink interfering level threshold
Value range: 0~63
Unit: level grade value
Content: if uplink level of a channel is greater than this threshold, and if the uplink
channel quality is greater than or equal to the uplink interference quality threshold, then
uplink interference occurs
Recommended value: 31
Uplink interfering quality threshold
Value range: 0~70
Unit: quality grade value
Content: if uplink level of a channel is greater than or equal to the uplink interference
level threshold, and if the uplink channel quality is greater than or equal to this threshold,
then uplink interference occurs
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 105 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

Recommended value: 40
Downlink interfering level threshold
Value range: 0~63
Unit: level grade value
Content: if downlink level of a channel is greater than or equal to this threshold, and if
the downlink channel quality is greater than or equal to the downlink interference quality
threshold, then downlink interference occurs
Recommended value: 31
Downlink interfering quality threshold
Value range: 0~70
Unit: quality grade value
Content: if downlink level of a channel is greater than or equal to this downlink
interference level threshold, and if the downlink channel quality is greater than or equal
to this threshold, then downlink interference occurs.
Recommended value: 40
Voice /data channel signal strength filter length
Value range: 132
Unit: None
Content: to filter the voice /data channel level with this parameter
Recommended value: 6
Voice /data channel signal quality filter length
Value range: 1~32
Unit: None
Content: to filter the voice /data channel quality with this parameter
Recommended value: 6
Signaling channel signal strength filter length
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 106 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

Value range: 1~32


Unit: None
Content: to filter the signaling channel level with this parameter
Recommended value: 2
Signaling channel signal quality filter length
Value range: 1~32
Unit: None
Content: to filter the signaling channel quality with this parameter.
Recommended value: 2
Channel-seizing history record refreshing cycle
Value range: 1~1,440
Unit: minute
Content: in the minute task, when the time exceeds the channel history record refreshing
cycle, the history record refreshing flow is started, i.e., every time the interval set by this
parameter is reached, the historical record of every channel is subtracted by the set value
of the "channel seizure history record refreshing range", so as to improve channel
priority. This parameter together with the "channel seizure history record refreshing
range" acts to prevention channel inability to distribute after deterioration for a period of
time.
Recommended value: 30
Channel seizure history record refreshing range
Value range: 063
Unit: None
Content: while refreshing history record priority, if the history record priority is higher
than this range, then refresh related history record priority.
Recommended value: 2

______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 107 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

III. GPRS (PCU) network planning data


configuration specifications (draft)
In GPRS, data configuration is done in form of command lines. So, exact forms as in
GSM do not exist; besides, it is also not clearly defined which data in GPRS should be
configured during network optimization. But the related parameters in the "forms" below
should be familiar during network optimization. Moreover, forms such as PRACH,
PCCCH, and NEIGBOUR InUse are not listed in this draft because current devices do
not support them, or they need not be configured at present.
Meanings of the command words:
Attr

Add a record in attribute table

Csdc

Add a record in CSDC table

Pwrctrlconfig
Measconfig
Pdchpara
Pwpar
Servpar

Add a record in power control algorithm table


Add a record in measurement configuration table
Add a record in PDCH parameter table
Add a record in power control table
Add a record in service parameter table

What follows is an item by item description of the above command words and
parameters:
GPRS cell identification parameter configuration
Command word: pcu add attr <LCNo> <CGI> <BSC> <RA> <SGPRS> <PrimRPPU>
<SecRPPU> <in use> <LCName>
Parameter Description: the GPRS cell identifier indicates the cells of GPRS services
supported by the PCU system, the GPRS cell identification configuration means actually
to define the various parameters required in a GPRS cell. That is to say, to define a GPRS
cell, we must know the CGI, BSC code, Ra, RPPU boards, etc. Only when these
parameters are completed, is the definition of the GPRS cell complete.
PCU and BSC cooperate to provide packet and circuit services simultaneously to related
cells. For cells that support GPRS services, data should be configured in the PCU system,
and corresponding data should also be configured in the BSC system.
The main data configuration parameters involved are:

______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 108 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

Logical cell number (LCNo): a logical cell number logically identifies a corresponding
cell. It is a code uniformly made under PCU, and every cell is identified uniquely with
one logical cell number. Value range: 0 ~ 65534
Global cell identifier (CGI): cell CGI number. The CGI configured to PCU that supports
GPRS service cells should be the same as the correspondingly configured cell CGI
number at the BSC side. Besides, this cell should have related data correctly configured
in BSC (refer to the operation manual of BSC). Note: in GPRS, the cell CGI is the BCD
code, 13 bits.
BSC code (BSC): the BSC code identifies the BSC that processes cell services. One PCU
can be connected to multiple BSCs, and corresponding BSC are coded uniformly under
PCU. Every BSC is identified by a BSC code.
Value range: 0~255
Route area code (RA): it identifies the route area of a cell.
Value range: hexadecimal code, 00~FF.
Whether to support the GPRS service (SGPRS): this data item indicates whether a cell
supports GPRS services. At present, this data item is invalid, and can be configured as
YES.
RPPU board number (RPPUNO): the RPPU board number identifies the number of the
RPPU board that processes cell services. It is unformly coded under PCU. Every RPPU
board is identified with a unique RPPU board number. Value range: 0 ~ 5, 10 ~ 15
Note: in the PCU33b version, this parameter is changed into the following two
parameters: PrimRPPU and SecRPPU, which are basically the same, and they are both
configured with a pair of activate/standby RPPU board numbers.
Whether cell configuration is in use: Value range: "true" or "false"; this parameter begins
to be used in PCU33b.
Logical cell number: character string
BCCH frequency (BCCH): BCCH frequency identifies the absolute frequency ARFCN of
the main BCCH in a cell. It must be the same as the BCCH frequency configured for a
corresponding cell in BSC. It exists in the PCU33a version, but is canceled in pcu33b.
CS change control data configuration
Command word:
<UlCsChgThd0>

pcu

add

csdc

<LCNo>

<Isallowed>

<MinMeaRptNum>

<UlCsChgThd1> <UlCsChgThd2> <UlUpHys0> <UlUpHys1>


<UlUpHys2> <UlDownHys0> <UlDownHys1> <UlDownHys2>
<MinTimeGap> <DlCsChgThd0> <DlCsChgThd1> <DlCsChgThd2>
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 109 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

Parameter Description: in the GPRS system, the channel codes can adopt 4 types of
coding modes: CS-1, CS-2, CS-3, and CS-4. The tighter the coding level, the higher the
transmission rate, and the higher the requirements for channel quality. The PCU system
can perform dynamic CS change according to such factors as channel quality, so as to
find the optimal mode. CS change parameters relates to data configuration setting and CS
dynamical change algorithm. It mainly includes the following parameters:
LCNoRange: a logical cell number identifies one GPRS cell in PCU, i.e., making data
configuration for adjacent cells against this GPRS cell. Value range: 0 ~ 65534
IsCsDcallowed: whether CS dynamic change is allowed sets whether PCU performs the
CS dynamic change function. If PCU supports CS dynamic change, the parameter is set
to TRUE; if PCU does not support CS dynamic change, the parameter is set to FALSE.
Value range: TRUE or FALSE
MinMeasRptNumForCsdc: CSDC minimum report number sets the minimum number of
measurement reports that performs CS dynamic change, i.e., the number of measurement
reports for which the average is obtained. Value range: 0 ~ 255
UlCS changeQualThreshold0: uplink TBF CS change threshold 0 sets the threshold
reference value of channel quality to judge the CS-1 and CS-2 dynamic change of uplink
TBF. Value range: 0 ~ 70
UlCS changeQualThreshold1: uplink TBF CS change threshold 1 sets the threshold
reference value of channel quality to judge the CS-2 and CS-3 dynamic change of uplink
TBF.Value range: 0 ~ 70
UlCS changeQualThreshold2: uplink TBF CS change threshold 2 sets the threshold
reference value of channel quality to judge the CS-3 and CS-4 dynamic change of uplink
TBF. Value range: 0 ~ 70
UluplinkCsdcQual Hysteresis0: uplink TBF CS change uplink hysteresis 0 sets the
hysteresis value for uplink TBF to change again from CS-1 to CS-2. Value range: 0 ~ 70
UluplinkCsdcQual Hysteresis1: uplink TBF CS change uplink hysteresis 1 sets the
hysteresis value for uplink TBF to change again from CS-2 to CS-3. Value range: 0 ~ 70
UluplinkCsdcQual Hysteresis2: uplink TBF CS change uplink hysteresis 2 sets the
hysteresis value for uplink TBF to change again from CS-3 to CS-4. Value range: 0 ~ 70
UldownlinkCsdcQual Hysteresis0: uplink TBF CS change downlink hysteresis 0 sets the
hysteresis value for uplink TBF to change again from CS-2 to CS-1. Value range: 0 ~ 70
UldownlinkCsdcQual Hysteresis1: uplink TBF CS change downlink hysteresis 1 sets the
hysteresis value for uplink TBF to change again from CS-3 to CS-2. Value range: 0 ~ 70
DownlinkCsdcQual Hysteresis2: uplink TBF CS change downlink hysteresis 2 sets the
hysteresis value for uplink TBF to change again from CS-4 to CS-3. Value range: 0 ~ 70
MinCSchangeTimeGap: the uplink TBF CS change time threshold sets the timeout length
for uplink TBF changes again from a CS to another CS in the same direction. Value
range: 0 ~ 65535
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 110 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

DlCS changeILevelThreshold0: downlink TBF CS change threshold 0 sets the interfering


level threshold value when downlink TBF changes between CS-1 and CS-2. Value range:
0 ~ 30
DlCS changeILevelThreshold1: downlink TBF CS change threshold 1 sets the interfering
level threshold value when downlink TBF changes between CS-2 and CS-3. Value range:
0 ~ 30
DlCS changeILevelThreshold2: downlink TBF CS change threshold 2 sets the interfering
level threshold value when downlink TBF changes between CS-3 and CS-4. Value range:
0 ~ 30
Power control data configuration
Command word: pcu add pwrctrlconfig <LCNo> <IsUlPcPmt> <IsDlPcPmt>
<MinMeaRptNum>
<IdealRxQual> <RxQualThd> <GammaChgTime> <GammaChgStep>
Parameter Description: power control data sets parameters related to power control, e.g.,
conditions to start power control. It mainly includes the following parameters: Logical
cell number (LCNoRange): logical cell number identifies a GPRS cell under PCU, i.e.,
data configuration for adjacent cells against this GPRS cell.
Value range: 0 ~ 65534
IsUlPcallowed: uplink power control allowed sets whether to execute uplink power
control. If uplink power control is allowed, then it is set to TRUE; if it is not allowed,
then it is set to FALSE.
IsDlPcallowed: downlink power control allowed sets whether to execute downlink power
control. If downlink power control is allowed, then it is set to TRUE; if it is not allowed,
then it is set to FALSE.
MinRptNumForGammaCh: number of measurement reports threshold sets the minimum
number of valid measurement reports PCU must receive during power algorithm
execution. Value range: 0 ~ 255
IdealRxQual: ideal receive quality sets the expected ideal receive quality. Receive quality
corresponds to channel bit error rate. Value range: 0 ~ 70
RxQualTolerance: receive quality tolerance sets the tolerance value to perform power
control functions; it is an offset value in contrast to ideal receive quality. Value range: 0 ~
70
GammaChChangeTime: GammaCh change time threshold sets the time value when
GammaCh should change, and its receive quality (RxQual) must satisfy and maintain
certain conditions.
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 111 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

Value range: 0 ~ 65535


GammaChChangeStep: GammaCh change step-length sets the step-length for each
change when GammaCh changes dynamically. Value range: 0 ~ 15
Measuring result preprocessing data configuration
Command word: PCU add MeasConfig <LCNo> <RptForInsert> <MaxRptNumGap>
<MaxRptTimeGap>
<SsbFilterLength> <SsbFilterUpTolerance> <SsbFilterDownTolerance>
<BerFilterUpTolerance> <BerFilterDownTolerance>
Parameter Description: the PCU system can perform the MS power control function.
After receiving measuring reports from MS, PCU needs to preprocess measuring reports,
so as to realize power control. The measuring result pre-processing data configuration
mainly includes the following parameters:
LCNoRange: logical cell number identifies a GPRS cell under PCU, i.e., making data
configurations for adjacent cells against this GPRS cell. Value range: 0 ~ 65534
RptForInsert: measuring report insertion number threshold sets the minimum number of
measuring reports PCU must receive before PCU allows insertion to measuring reports.
Value range: 0 ~ 255
MaxRptNumGap: measuring report insertion code tolerance sets a tolerance value, and
only when the code interval is less than or equal to this value, is measuring report
insertion allowed.
Value range: 0 ~ 255
MaxRptTimeGap: measuring report insertion time tolerance sets the insertion time
tolerance value; if the time between the previous report and this report exceeds this
value , then the measuring reports received previously are discarded. Value range: 0 ~
65535
SsbFilterLength: measuring report filter length sets a number of measuring reports used
for power control, i.e., how many previous measurements are used to obtain the average.
Value range: 0 ~ 255
SsbFilterUpTolerance: Ssb filtering upper tolerance sets the upper limit of the difference
between the valid value and the average value of the BTS receive signal power. Value
range: 0 ~ 64
SsbFilterDownTolerance: Ssb filtering lower tolerance sets the lower limit of the
difference between the valid value and the average value of the BTS receive signal
power.Value range: 0 ~ 64
BerFilterUpTolerance: Ber filtering upper tolerance sets the upper limit of the difference
between the valid value and the average used by the bit error rate filter. Value range: 0 ~
255
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 112 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

BerFilterDownTolerance: Ber filtering lower tolerance sets the lower limit of the
difference between the valid value and the average used by the bit error rate filter. Value
range: 0 ~ 255
3.5 Power control parameters
Command word: pcu add pwpar <LCNo> <ALPHA> <TAVGW> <TAVGT> <PB>
<PCMeasChan>
<MeasChAvail> <NAVGI>
Parameter Description: power control parameters are used by MS to determine its TX
power level. It mainly includes the following parameters:
LCNoRange: logical cell number identifies a GPRS cell under PCU, i.e., making data
configuration against this GPRS cell. Value range: 0 ~ 65534
ALPHA: the ALPHA parameter is used by MS to calculate the output power value PCH of
its uplink PDCH.
Value range: 0.0~1.0, Note: this is an interesting parameter, with which MS can make its
own power control; this parameter is issued in the SI13. At present, it is not supported by
the GSM mobile phones.
(TAVGW: the T_AVG_W parameter sets the signal strength filtering cycle of MS in the
packet idle mode. MS measures the downlink signal strength in the packet idle mode, and
is used to calculate the C value.Value range: 025
(TAVGT: the T_AVG_T parameter sets the signal strength filtering cycle of MS in the
packet transferring mode. MS measures the downlink signal strength in the packet
transferring mode, and is used to calculate the C value. Value range: 025
PB: the PB parameter sets the power attenuation value of BTS on the PBCCH board. It
has the values: "0dB", "-2dB", "-4dB", ..., "-30dB"
PCMeasChan: power control measuring channel sets on which channel MS measures the
receive power level used for uplink power control. If the parameter is set to BCCH, it
shows that downlink power control measuring is realized on BCCH; if it is set to PDCH,
it means that downlink power control measuring is realized on PDCH. Value range:
"bcch" or "pdch"
Interference measuring channel indication (IntMeasChAvail): this parameter indicates
whether the cell broadcasts optional PSI4 messages. It should be set to NO.
NAVGI: the N_AVG_I parameter sets the interference signal strength filter for power
control. Value range: 015
3.6 PDCH channel configuration parameter setting
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 113 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

Command word: pcu add pdchpara <LCNo> <MaxUlHighLd> <MaxDlHighLd>


<MaxUlLowLd>
<MaxDlLowLd>

(PCU33b newly added)

Parameter Description:
LCNoRange: value range: 0 ~ 65534
MaxUlHighLd: 17
MaxDlHighLd: value range: 116
MaxUlLowLd: value range: 17
MaxDlLowLd: value range: 116
3.7 Service cell property
Command word:
<RxLevAccMin>

pcu

add

servpar

<LCNo>

<CellBarAccess2>

<ExcAcc>

<MsTxPwrMax> <PriorClass> <GPRSHCSThr> <MultiBandRep>


Parameter Description: service cell property sets some cell selection parameters of the
GPRS cell. It mainly includes the following parameters:
LCNoRange: value range: 0 ~ 65534
CellBarAccess2: the cell access barring indication parameter combines the system
parameter CELL_BAR_ACCESS and CELL_BAR_QUALIFY; it indicates the state of
cell reselection. If the parameter is set as Permit, it shows that the cell reselection state is
normal; if the parameter is set as NoPermit, it shows that cell reselection is barred.
ExcAcc: the exclusive access mode sets the system parameter EXC_ACC. It is used to
prevent MS with no exclusive access authority to remain in the cell. When the parameter
is set to Exclusive, it shows that the cell is used for exclusive SoSLA access; when the
parameter is set to NoExclusive, it means that the cell is not used for exclusive SoSLA
access.
Option: "exclusive" or "noexclusive"
GPRSRxLevAccMin: this parameter sets the minimum receive power level required by
the MS access in the cell. It is used by MS to calculate the C1 value. Value range: 0 ~ 63
GPRSMsTxPwrMaxCCH: the parameter sets the maximum TX power level used by MS
to access a packet control channel. Value range: 0 ~ 31
GPRSPriorityClass: the GPRS priority class sets the HCS priority of the GPRS cell.
Option: 0 ~ 7."nouse"

______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 114 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

GPRSHCSThr: the HCS threshold sets the HCS signal strength threshold. Option: "110dB", "-108dB", "-106dB",...,"-48dB", "nouse"
MultiBandRep same as the multi frequency band indication in GSM.
3.8 Others (SI13)
The GPRS system message data configuration contains the content of multiple parts, but
as Huawei (including other manufacturers) do not support the CCCH and PBCCH
channels, so, many parameters, e.g., access control parameters and cell reselection
parameters, and are using the same GSM parameters. So, for the meainings of those
parameters, refer to GSM.
But system message SI13 is exclusive for GPRS, and is issued by PCU to BSC, and BSC
relay it. Here, meanings of the SI13 part parameters are listed as follows. SI13 contains
many segments, and is configured with multiple commands, e.g., the power control
command word, and the service cell command word. The content of the following
command word is all for the content of SI13 .
pcu add gprs <LCNo> <NMO> <T3168> <T3192> <DRXTimerMax>
<AccBurst> <CtrlAckType> <BsCvMax> <PanDec> <PanInc>
<PanMax> <EGPRSSupport>
OPTIONS
LCNo Logical cell number, range: 0 ~ 65534
NMO Network Mode of Operation
0 - Network Mode of Operation I
1 - Network Mode of Operation II
2 - Network Mode of Operation III
3 - Reserved
T3168 Timeout value of T3168. range: "500ms", "1000ms"
"1500ms",...,"4000ms"
T3192 Timeout value of T3192. range: "500ms", "1000ms"
"1500ms",...,"4000ms"
DRXTimerMax Maximum duration of DRX
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 115 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

"no" - no Non-DRX mode after transfer state


"1s" - 1 second
"2s" - 2 seconds
"4s" - 4 seconds
...
"64s" - 64 seconds
AccBurst Indicates whether 8 or 11 bits burst shall be used on
PRACH, range: "8bit", "11bit"
CtrlAckType Default format of the PACKET CONTROL ACKNOWLEDGMENT
message
range:
0 - default format is four access bursts
1 - default format is RLC/MAC control block
BsCvMax,

range: 0 ~ 15

PanDec

range: 0 ~ 7. "nouse"

PanInc

range: 0 ~ 7. "nouse"

PanMax

range: 4. 8...., 32."nouse"

EGPRSSuppot Support improved GPRS or not, option: "yes" or "no"


LCNoRange: the logical cell number identifies a GPRS cell under PCU, so that can
configure this GPRS cell.
NMO: network operation mode is related to the system adopted paging channels type,
which can be divided into three types of mode: network operation mode III, network
operation mode II and network operation mode II. When the system has the Gs interface,
mode I should be configured; when the system is not configured with the Gs interface,
nor packet public control channels (PCCCH), mode II should be configured; when the
system is not configured with the Gs interface, but with packet public control channels
(PCCCH), mode III should be configured. Meanwhile, in cells of same route segment, the
network operation mode should be same.
T3168: timer T3168 is used to set the time duration for MS to wait for packet uplink
assignment messages. After sending packet resources request messages, MS starts to wait
for packet uplink assignment messages, T3168 decides when to stop waiting. The
parameter is configured in step of 500ms.
T3192: timer T3192 is used to set the time duration for MS to wait for TBF release after
receiving the last data block. After MS receives the last RLC data blocks, timer T3192 is
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 116 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

started. If T3192 times out, MS will release TBF and start monitoring paging channels.
This parameter is configured in units of 500ms.
DRXTimerMax: The DRX timer maximum value sets the maximum time duration of
executing the non-DRX mode after MS changes from the packet transmission mode into
the packet idle mode. The parameter is configured in unit of seconds.
AccBurstType: the access pulse type sets the access pulse type MS uses in PRACH,
PTCCH/U, and packet control acknowledgment messages. This parameter's option is of 8
bits or 11 bits.
CtrlAckType: sets the format of MS used in controlling acknowledgment messages.
Option 0 stands for 4 access pulses, and option 1 stands for RLC/MAC control blocks.
BsCvMax: maximum countdown value sets the MS countdown parameter
BS_CV_MAX; it is a parameter used by MS to calculate the Countdown Value (CV).
PanDec: the parameter sets the value of the parameter PAN_DEC used by the N3102
timer of MS. When T3182 of MS times out, N3102 reduces the value of PAN_DEC.
PanInc: the parameter sets the value of the parameter PAN_INC used by the N3102 timer
of MS. When MS starts timer T3182 and receives the packet uplink acknowledgment
message, N3102 increases the value of PAN_INC.
PanMax: the parameter sets the value of PAN_MAX of the N3102 timer of MS, i.e., the
maximum value of N3102.
EGPRSSupport: the parameter sets the GPRS cell supports EGPRS services or not. At
present, PCU does not support EGPRS, and this parameter is fixed as No.

IV.Accessories
4.1The channel description format and cell frequency configuration
Now, the cell frequency configuration supported by BSC (0520 version) can reach
64. Due to the restriction of cell channel description format, actual cell frequencys cannot
be configured freely.
Let's see the cell channel description format. The "System Message Data Table" at
the BSC data management console has this item. The BSC program actually does not use
this item, but actual frequency configurations use different cell channel description
formats.
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 117 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

There are the following types of cell channel description formats, determined
respectively by the second byte Format ID (bit8, bit7, bit4, bit3, and bit2) in the Cell
Channel Description.
Bit Bit Bit Bit Bit format notation
87432
0 0 X X X bit map 0 (0bitmap)
1 0 0 X X 1024 range (1024 range format)
1 0 1 0 0 512 range (512 range format)
1 0 1 0 1 256 range (256 range format)
1 0 1 1 0 128 range (128 range format)
1 0 1 1 1 variable bit map (variable-length bitmap)
The above cell channel description formats correspond to different number of absolute
frequency point which can be configured in the cell. If the number of absolute frequency
ponit in the cell is n (except and invalid cases), use arfcn(i) (i=1. ...,n) to represent
corresponding radio frequency points. Then, the frequency points can be configured in
every channel description formats are:
1. 0 Bitmap format
The 0 bitmap format is used for the frequencys of M900, and frequencys that can be
actually configured in the cell can reach 64, and the frequencys can be arbitrary, only
limited to 1 arfcn(i) 124.
2. 1024 range format
In this format, frequency number that can be actually configured in the cell is n
16. But frequency points are not limited; for M900, 1 arfcn(i) 124; and for M1800,
512 arfcn(i) 885.
3. 512 range format
In this format, frequency point number that can be actually configured in the cell is n
18. Besides, the following condition should also be met: in the configured frequency
points, if the maximum skip between two frequency points is m, then m < 512. actually,
M900 and M1800 frequency points cannot be configured together. In fact, for M900 and
M1800 alone, it is free.
4. 256 range format
In this format, frequency point quantity that can be actually configured in the cell n
22. Besides, the following condition should also be met: in the configured frequency
points, if the maximum skip between two frequency points is m, then m < 256. For
example, in this format, frequency points 512 and 812 cannot be configured
simultaneously.
______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 118 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

5. 128 range format


In this format, frequency number that can be actually configured in the cell n 29.
Besides, the following condition should also be met: in the configured frequency points,
if the maximum skip between two frequency points is m, then m < 128. For example, in
this format, frequency points 512 and 712 cannot be configured simultaneously.
6. Variable-length bitmap
In this format, frequency number that can be actually configured in the cell can also
reach 64. But the following condition must be met: in the configured frequency points, if
the maximum distance between two frequency points is m, then we must have 1 m
111. For example, if a total of 64 frequency points are configured, e.g., 512, 513, 514....,
575 (incrementing by 1), this is feasible. But if a total of 64 frequency points are
configured, e.g., 512, 514, 516...., 638 (incrementing by 2), problems will occur.
Description:
1. The above frequency restrictions are mainly for the M1800 frequency points, and
the M900 frequency points are not restricted [because M900 frequency points can always
use the "0 bitmap" format]
2. In the program, the judgement priority levels are as follows:
a. 0 bitmap format
B. Variable-length bitmap format
c. 1024 range format
d. 512 range format
e. 256 range format
f. 128 range format
Only when current bitmap format does not meet the requirement, is the next bitmap
format judgement is performed.
If none of the above formats meet the requirement, the program in default will use the
"1024 range format".
3. The above mainly affect the "radio frequency hopping" multi-frequency
configurations; for non-frequency hopping cases, for example: S 12/12/12 configuration,
attention is also required to frequency configuration. Otherwise, it might cause some
problem.
4. No matter how frequencys are configured, they can all be issued to base stations;
but due to protocol restrictions, some frequencys might be impossible to issue to mobile
phones, causing assignment failure.

______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 119 of
147

GSM9001800 BSS&PCU Network Planning Data Configuration Specification(V3.1)

______________________________________________________________________________________
_
2002-2-25
All Rights Reserved
Page 120 of
147

GSM
Network

900/1800
Planning

BSS

Version 3.1

Data

4.2 Location area classification basic principle


4.2.1 LAC concept
To determine a mobile station location, the coverage area of every GSM PLMN can
be divided into many location areas. The location area code (LAC) is used to identify
different location areas.
The location area code (LAC) is contained in LAI, consisting of two bytes, coded in
hexadecimal digits. The available range is 1 65535 (decimal). One location area can
contain one or more cells. At present, according to our experience, the quantity of carrier
under one LAC is not exceed 400; of course, at the beginning of network construction,
this value can be set appropriately larger as the traffic is not so heavy, or due to LAC.
LAC is broadcast in system messages on the broadcast channels of every cell. A
mobile station updates its LAC by IMSI attachment (IMSIAttach) or location updating
during switch-on, inserting an SIM card or finding out the LAC of current cell does not
match with the originally stored. The network stores the location area of every mobile
station, and uses it as the location information for paging this mobile station in the future.
Every country specifies its own LAC coding modes. China Mobile also has its clear
specifications over the LAC coding modes on its proprietary GSM networks (refer to
related GSM systems and specifications promulgated by the Chinese Ministry of Posts
and Telecommunications). Normally, in the initial phase of network construction, LAC
distribution and coding are already determined, and are seldom changed during network
running. The size of a location area (LAC) (i.e., the range size covered by a location area
code (LAC)) is a key factor in the system. If the LAC coverage area is too small, the
mobile station location updating processes will be frequently, and cause the system more
signaling traffic. On the contrary, if the location area coverage area is too big, then, when
the network pages a mobile station, the same paging message will be sent to many cells,
which leads to too heavy a load on the PCH channel, and at the same time causes the
heavy signaling traffic on the Abis interface. As mobility and paroxysmal are mobile
communications, the location area size adjustment has no uniform standards. Therefore,
according to the long-term statistics of the PCH load in various areas, and the signaling
link load to determine whether or not adjust the location area size. If the former problem
is too serious, we can appropriately adjust the location area smaller; otherwise, we can
adjust the location area appropriately greater.
4.2.2 Principles in location area classification
During the process of network planning and optimization, the key points of concern
are: 1. How to set appropriate paging traffic, and how to set PCH load and SDCCH
signaling load reasonable; 2. How to let mobile phones update their locations timely and
efficiently, and reduce phenomena with obvious signal but not in the service area. For the
relationships between PCH and SDCCH signaling load and location areas, refer to related
documents. Based on the above principles, manufacturers such as NOKIA are very
careful in location area classification (especially in big cities):

2002-03-15

Copy rights reserved, violations subject to penalty

Page 121

GSM
Network

900/1800
Planning

BSS

Version 3.1

Data

1. When coverage between urban and the urban area proper is not continuous, it
might occur that mobile phones cannot update their locations in periodic location
updating moments. When the protection time is over (which is normally set in MSC), the
system regards IMSI recessive detachment, so if a mobile phone enters a city at this time,
the LAC in the urban and suburb areas is the same. In this case, some mobile phones
cannot immediately make normal location updating, resulting in the phenomenon of
having signals but appearing not in the service area. So, in location area distribution,
normally suburbs use an independent location area, and the location area distribution in
such cases is similar to a concentric ring, so as to avoid the above phenomenon.
2. In a city with a heavy traffic, one location area is not enough. In case of multiple
location areas, attention should be given to the control of location area boundaries, so as
to keep them as much as possible not parallel or overlapping with streets, or in places
with a heavy traffic (such as supermarkets). On the one hand, during reselection of cells
between location areas, the cell reselection hysteresis will act, causing the user to feel
signal instability. On the other hand, location area boundaries parallel to or overlapping
with streets in heavy traffic areas will lead to frequent location updating, increasing
signaling load, and causing SDCCH congestion in some cells. So, location area
boundaries normally are not parallel or vertical to street, but rather diagonal.

2002-03-15

Copy rights reserved, violations subject to penalty

Page 122

GSM

900/1800

Network

Planning

BSS

Version 3.1

Data

4.3 34 Tables (BSC) of Network Planning Data


The Network Planning Department need 34 tables to prepare network planning data,
distributed under such menus as local office, site, cell, handover, power, and channel.
Reference of dbf file and BSC tables
Serial No.

OMC tables

Dbf file

BSC cell table

Bsc cell

Frequency hopping data table

Hop data

Wireless channel configuration table

abiscir

carrier configuration table

rccfg

System message data table

symgdatl

Cell configuration data table

cellcfg

Cell distribution table

cealotl

BA1 table

ba1

BA2 table

ba2

10

Cell property table

cellattr

11

Cell alarming threshold table

cellala

12

Cell call control table

callctrl

13

Cell call processing parameter table

celcalmp

14

Cell module information table

cgitbl

15

Handover control data table

swctrl

16

Cell description data table

celldesc

17

External cell description data table

extcell

18

Cell adjacency relationship table

nebcell

19

Filter data table

filterd

20

Penalty data table

penalty

21

Emergency handover data table

urgedat

22

Load handover data table

clsdata

23

Normal handover data table

nordata

24

Fast moving handover data table

Move data

25

In-cell continuous handover data table

intraho

26

GSM0508 handover data table

cellho2

2002-03-15

Copy rights reserved, violations subject to penalty

Remarks

The

table

is

Page 126

GSM
Network

900/1800
Planning

BSS

Version 3.1

Data
empty

27

Power control selection table

pwrctls

28

Normal cell power control data table

cellpwrc

29

BTS power control data table

btspwrc

30

MS power control data table

mspwrc

31

Wireless channel management control table

idlechpr

32

Bad channel management control table

badchcfg

Deleted
in
version 1120A
and subsequent
versions

33

Traffic control parameter table

flowctl

Two tables are


combined into
one

34

Channel distribution generation II algorithm


data table

chanall.dbf

2002-03-15

Copy rights reserved, violations subject to penalty

Page 127

GSM
Network

900/1800
Planning

BSS

Version 3.1

Data

4.4 Description of parameter configuration and main check-points for Phase


XX network planning of the XX mobile network
Outline: try to achieve the purpose of first check by filling out and auditing this
description.

Network carrier in this phase; base station ; maximum site type;


Available bandwidth of frequency band:
BCCH used frequency range: , total;
BSC hardware version:

host software version:

Base station type 1, board (TRX, FPU, HPA) software version:

Base station type 2, board (TMU, TRX, CDU) software version:

LAC1 code, area, and number of carrier:


LAC2 code, area, and number of carrier:
LAC3 code, area, and number of carrier:

Pay attention to the difference between decimal and hexadecimal and case sensitivity
CI coding principle:
Pay attention to the difference between decimal and hexadecimal and case sensitivity.

Correspondence relationship between BCCH frequencys and BSIC (NCC+BCC):


Check the CA table, carrier configuration table, BSC cell table, cell description data
table, wireless channel configuration table, and frequency hopping data table

Power budget description


Notice the difference between different combiners

Dynamic distribution of SDCCH(); SDCCH distribution principle:


Checking the wireless channel management control table and wireless channel
configuration table
BCCH carrier load-sharing ();

2002-03-15

Copy rights reserved, violations subject to penalty

Page 128

GSM

900/1800

Network

Planning

BSS

Version 3.1

Data

Checking the cell configuration data table


flow control ()
Checking the internal flow control permit table
BA table and adjacent cell configuration principle:
Checking the BA1 table, BA2 table, cell adjacency relationship table and cell description
data table

Principle and area for frequency hopping:


Checking the CA table, carrier configuration table, frequency hopping data table,
wireless channel configuration table and cell configuration data table

Uplink DTX(), downlink DTX():


System message data table, checking and verifying data tables at the MSC side whether
downlink DTX is used

Power control algorithms generation 1 (), generation 2 ();


uplink(), expected threshold: ; downlink (), expected threshold.

Handover algorithm:
Statistics time:

duration:

PBGT(), PBGT handover threshold;


Inter-layer handover threshold:
Uplink edge handover level threshold: ; downlink edge handover level threshold;
Load handover (); inra-cell handover (); directional re-attempt (); others:

RACH busy threshold:


Other descriptions

2002-03-15

Copy rights reserved, violations subject to penalty

Page 129

GSM900/1800 BSS&PCU Network Planning Data Configuration Specification

Version 3.1

4.5 Description of flow control (based on the 06.0520 version and the current
01.07.0520 version)
4.5.1 BSC internal flow control
4.5.1.1 Internal flow control processing flow

MPU processor overloading:


1. Set system internal flow control level according to current MPU processor load and
with the traffic level set algorithm;
2. Set the corresponding control parameters according to the internal flow control level;
3. Make corresponding flow control in various related modules according to the current
flow control level and related control parameters.
Paging message overload:
1. Protect the normal communication and BM stable running with many paging message
broadcast through the A interface by setting the number of paging messages at the A
interface in each cycle of BM in BSC.
4.5.1.2 Internal traffic level maintenance algorithms

The BSC internal flow control level as level 11, using a second timing task to monitor the
CPU load, control the timer status (control with timer default T3 10s) according to the
internal traffic, and start the BSC internal flow control algorithm. When the CPU load
exceeds the CPU overload initial threshold (set to 70 in default), the internal traffic
level rises. When the CPU load is lower than the CPU overload terminal threshold (set to
60 in default), the internal traffic level drops.
When the BSC internal traffic level changes, the alarming of BSC internal traffic level
change occurs. When the BSC internal traffic level is 0, the alarming of BSC internal flow
control ending occurs.
If BSC detects that CPU load exceeds the CPU overloading initial threshold (set to 70in
default) in each second, it will send the OVERLOAD message send to MSC, with the
cause value of PROCESSOR_OVERLOAD

2002-2-25

All Rights Reserved

Page 130

GSM900/1800 BSS&PCU Network Planning Data Configuration Specification

Internal flow control level


maintenance processing flow

Version 3.1

Start
N

Is internal flow control


permitted?

Return

Obtain current MPU message array load

When load exceeds threshold,


send OVERLOAD to MSC
N

Does flow control exist?

Is Timer T3 time reached?

Smoothening of MPU message array load

Y
Is it overloaded?

Smoothening of MPU message array load

N
Return

Is it overloaded?

Return

Set initial flow level


Raise by 1 level

Lowever by 1 level

Produce flow control alarming

Set corresponding control parameters

Send flow control message to related module

Invoke interface function of corresponding module

2002-2-25

Return

All Rights Reserved

Page 131

GSM900/1800 BSS&PCU Network Planning Data Configuration Specification

Version 3.1

Control operations at different internal traffic levels:


Control processing under internal flow control levels
interfere
band

Interface
pre-tracking

processing

barred

cycle
Control level-

Channel

Channel

Packet

SDCCH

TCH_REQ

distribution contention

paging

dynamic

initiated

waiting

message

adjustment

PCU

forbarred

queuing

barred

Barred

Barred

Barred

Barred

Barred

Barred

Barred

Barred

Barred

Barred

Barred

Barred

Barred

Barred

Barred

Barred

No queuing Barred

Barred

Barred

Barred

Barred

No queuing Barred

Barred

Barred

Barred

Barred

No queuing Barred

Barred

Barred

Barred

Barred

No queuing Barred

Barred

Barred

Barred

Barred

No queuing Barred

Barred

Barred

Barred

Barred

No queuing Barred

Barred

Barred

Barred

Barred

No queuing Barred

Barred

Barred

Barred

0
Control levelNo
1

processing

Control levelNo
2

processing

Control levelNo
3

processing

Control levelNo
4

processing

Control levelNo
5

processing

Control levelNo
6

processing

Control levelNo
7

processing

Control levelNo
8

processing

Control levelNo
9

processing

Control levelNo
10

processing

Control levelNo
11

processing

Others: when flow control is at different levels, part of BTSM operations are barred:
Traffic levels 0-4: normal running, not barred
2002-2-25

All Rights Reserved

Page 132

by

GSM900/1800 BSS&PCU Network Planning Data Configuration Specification

Version 3.1

Traffic level 5: the following operations are barred:


Transparent message transmission;
Base station log message reporting;
Traffic levels 6 and 7: the following operations are barred:
Operations barred for traffic level 5;
Background software loading;
Traffic levels 8 and 9: the following operations are barred:
Operations barred for traffic level 5, 6, 7;
Alarming processing;
Background change management state;
Base station request change management state;
Traffic levels 10 and 11: the following operations are barred:
Operations barred for traffic level 5, 6, 7, 8, 9;
Base station initialization;
State modification reports;
Board resetting operation;
Base station resetting;
Resetting TRX;
Base station board active/standby changeover;
4.5.1.3 Paging message overloading:

By setting the quantity of paging messages at the A interface in each BM cycle of BM in


BSC, protect the BM stable running and normal communication of A interface links when
large quantities of paging messages are broadcast.
Set the detecting cycle as: 25tick, number of paging messages to be processed: 15
PAGING messages.
When more than 15 paging messages are received within the detection cycle, the extra
message are automatically discarded, and BSC no longer processes them. When CPU load
is too heavy, the number of paging messages allowed for processing (15) is dynamically
adjusted. When CPU load is 75, 80, 85, and 90, the number of paging messages allowed
for processing are respectively adjusted: 3/4, 1/2, 1/4, and 1/8. When CPU load return to
normal, the number of paging messages allowed for processing (15) is restored to the
original by multiplying with 2.
2002-2-25

All Rights Reserved

Page 133

GSM900/1800 BSS&PCU Network Planning Data Configuration Specification

Version 3.1

4.5.1.4 Abis interface traffic control:

BSC cell traffic control in no way handles PCH overload. Besides, PCH overloading is
reported in form of an OVERLOAD message (CCCH overloading) to MSC. CCCH
overloading in other cases (DEL_IND and RACH overloading) will no longer be reported
to MSC. Instead, cell flow control processing is activated to restrict mobile phone access
by system message modification of C1/C2.
4.5.1.5 Processing of DEL_IND message reported by BTS

When BSC receives the DEL_IND message reported by BTS, it directly starts the cell
flow control, and adjusts traffic level according to the timer T1/T2.
4.5.1.6. Processing of CCCH_LOAD_IND message reported by BTS

Uplink channel overloading (RACH): start flow control in the cell, and adjusts traffic level
according to the timer T1/T2.
Downlink channel overloading (PCH): the overloading message OVERLOAD is reported
to MSC with the reason of CCCH OVERLOAD.
4.5.1.7 Processing of OVERLOAD message reported by BTS

The cause is CCCH OVERLOAD, and BSC does not process it.
When the cause is PROCESS OVERLOAD, first overloading protection is activated: for 1
minute. If, within the overloading protection time, the PROCESS OVERLOAD message
is received again, the TRX channel distribution protection is activated (for a default
duration of 2 minutes, which can be set at the data management console)), and within this
protection time, channels on this TRX are not assigned. If within this protection time, the
PROCESS OVERLOAD message is received again, the TRX protection time is refreshed
into the default duration. In this algorithm, the system minute timer is used to clear the
detecting TRX protection mark.
Meanwhile, if this TRX is the TRX where BCCH is located, flow control of this cell is
started, and traffic level is adjusted according to timer T1/T2.

4.5.2 Cell traffic level maintenance and processing at different traffic levels
Traffic level maintenance
The traffic level maintenance algorithm uses the maintenance algorithms of the T1 and T2
timers, as shown in the following figure:

2002-2-25

All Rights Reserved

Page 134

GSM900/1800 BSS&PCU Network Planning Data Configuration Specification

ABIS flow control level


maintenance processing flow

Version 3.1

Start
Is ABIS flow control
permitted?
Y
N

Does flow control exist


in this cell?
Y

Set initial cell flow control

Is it within the T1
timed period?
N
Raise flow control level in this cell

Start timer(T1)

Reset timer (T1)

Set timer identifier


Set corresponding control parameters
Invoke system message sending control function
Timer (T2) timeout processing flow
Return

Start
Lower flow control level in the cell

Timer (T1) timeout processing flow

Start
Set time(T2-T1)

Set timer identifier


Return

Is level 0?
Reset timer (T2)

Recover corresponding
control parameters

Set timer identifier

Set corresponding control parameters


Invoke system message sending control function
Return

2002-2-25

All Rights Reserved

Page 135

GSM900/1800 BSS&PCU Network Planning Data Configuration Specification

Version 3.1

For cell flow control, the following content is added:


Alarming for cell flow control itself: cell start/recover flow control
Traffic statistics items for overloading indication: CCCH_LOAD_IND (RACH
overloading), CCCH_LOAD_IND(PCH overloading), DEL_INd. OVERLOAD (CCCH
overloading), OVERLOAD(TRX overloading).
Dynamic setting of controlling timer T1/T2 duration
4.5.2.1 Traffic control processing at different levels

When the traffic level is 1, BSC performs no flow control operations, and with the rise of
the traffic level, the minimum access level and cell reselection offset level is adjusted 4
steps (4dbm) for each level.
RXLEV_ACCESS_MIN in system messages is adjusted according to different levels.
Cell flow control level
Cell selection parameter RXLEV_ACCESS_MIN
added control amount added (L)
Control level 0

Control level 1

Control level 2

Control level 3

Control level 4

Control level 5

Control level 6

12

Control level 7

16

Control level 8

20

Control level 9

24

Control level 10

28

Control level 11

32

When cell traffic changes, the cell immediately updates and sends cell system messages.
When the cell sends system messages, RXLEV_ACCESS_MIN of the cell is calculated as
follows:
RXLEV_ACCESS_MIN(new) = RXLEV_ACCESS_MIN + added control amount (L)
When 0 < RXLEV_ACCESS_MIN (new)< | ( 63 - RXLEV_ACCESS_MIN) / 2 |
RXLEV_ACCESS_MIN(new)= 0

2002-2-25

All Rights Reserved

Page 136

GSM900/1800 BSS&PCU Network Planning Data Configuration Specification

Version 3.1

When RXLEV_ACCESS_MIN (new) <= 0


RXLEV_ACCESS_MIN(new)= | ( 63 - RXLEV_ACCESS_MIN) / 2 |
When RXLEV_ACCESS_MIN(new)>= | ( 63 - RXLEV_ACCESS_MIN) / 2 |
Cancel the following formerly operations in BSC cell flow control are cancel:
The access restriction for different CHAN_REQ at different levels; meanwhile, cancel
the access delay time for the mobile phone.
The access barring of the polling modes of different types of mobile phones in system
messages.
The barring setting of CBA in system messages when flow control is at the highest level.
Consideration to cases where all TCH channels in the cell are busy
About load indication reported by BSC
If it is detected that all TCH channels in the cell are busy during the period check every 5
seconds in the cell. The LOAD IND message will be reported to MSC, and this message
will cause MSC to generate alarm: BSC load indication; meanwhile, MSC will send this
message to the BSC where the adjacent cells of this congested cell are located. When BSC
receives the LOAD_IND message issued from MSC, it will send this message to the
handover judging module (which is LAPD at present), restricting handover to the
congested cell.
Traffic index item: LOAD_IND of the overload indicating is added.
4.5.3 About TCH flow control
When BSC distributes TCH traffic channels, if available TCH channels in the cell exceed
this threshold, flow control in this cell is activated, to adjust traffic level according to the
timer T1/T2, so as to restrict call access. When TCH flow control starts, alarming is
already given.

4.6 Newly added functions in new version


erial

Version name

Newly added functions

G2BTS32.30000.07.0407B

1. Supporting BTS312; 2. Supporting TES transmission;

version

3. Supporting the BCCH carrier load-sharing; 4.

No.
BTS3X
1

Supporting the Abis interface 15: 1 multiplexing; 5.


Supporting PMU board management; 6. For the TRX
static power, the value in the carrier configuration table is
used, not the maximum radio frequency power
descending configuration; 7. Alarming processing level

2002-2-25

All Rights Reserved

Page 137

GSM900/1800 BSS&PCU Network Planning Data Configuration Specification

Version 3.1

drop: DBUS is changed into prompt alarming; 8.


alarming screen function; 9. Alarming reporting function;
10. shutting off BCCH carrier power after locking the
cell; 11. Supporting 64 frequency point frequency
hopping; 12. Supporting work log reporting function.
0

G3BTS32.30000.03.0529A

1. Supporting TMU board hardware version number

version

reporting; 2. Base station system message check; 3.


BTS30 phase lock loop load-sharing ; 4. BTS30 uplink
frequency scanning function; 5. TTMU supports 8031
external synchronized clock processing, supports 8031
automatic reporting of DA and phase authentication; 6.
BTS30 adds "no mains" alarming, two BTS30A alarms,
"serious standing wave ratio" alarming and power
amplifier turning-off function, and controls processing of
the times of TRX resetting; 7. Supporting the GPRS
function; 8. Support encrypting/decrypting functions; 9.
Supporting

satellite

Supporting

remote

transmission
sending

functions;

self-defining

10.

message

functions; 11. Supporting BCCH frequency participation


in baseband frequency hopping; 12. Supporting Huawei
generation II power control algorithm down-shifting; 13.
Supporting 10-level static power; 14. Supporting PMU
resources query and parameter setting; 15. Supporting
TMU self-checking crystal oscillator central frequency;
16. Supporting memory check function (including TRX
and DPRAM); 17. Supporting cell frequency scanning;
18. Supporting system message request; 19. Supporting
downlink statistics; 20. Supporting 70KM cells; 21.
Supporting clock capturing mode; 22. Supporting
BTS30A function.
3

G3BTS32.30000.04.0529A

1. Lowering power level before cutover; 2. Supporting

version

2E1. S10/10/10 three synchronous cells, and 30 TRX


sites; 3. Increasing power attenuation before cutover so
as to reduce radiation; 4. Modifying SACCH multi frame
number parameter; 5. Supporting idle BURST test
function; 6. Realizing EDU new requirements; 7. Adding
E1 remote error code detecting function; 8. Adding a

2002-2-25

All Rights Reserved

Page 138

GSM900/1800 BSS&PCU Network Planning Data Configuration Specification

Version 3.1

self-defining demand, used to perform phase lock loop


changeover or designated use; 9. BTS30 rack TRB
backplate bit switch correcting function; 10. Connection
time; 11. Wireless link alarming; 12. TMU log clearing.
4

G3BTS32.30000.05.0529A

1. PBU board function support 2. Local check of channel

version

state 3. Modifying version rollback mechanism 4. After


the TMU software downloading and modification of the
version rollback mechanism, to guarantee software
downloading reliability, the CRC check function is
added; 5. In modification of late assignment, the
encryption flow fails 6. Paging fails during dynamic
replacing of BCCH and combined BCCH 7. Supporting
SACCH with more than 16 multi frames, i.e., SACCH
multi frames have a value range of (0-31)

G3BSC32.10101.06.0520B

1. Supporting the GM13MPU board.

version
2

G3BSC32.10102.06.0520B

1. Supporting the 2001 annual report function.

version
3

G3BSC32.10100.07.0520B

1. A interface protocol reforming; 2. Traffic statistics

version

optimization function development; 3. GPRS traffic


statistics support; 4. TFO function support; 5. power
control generation II algorithm down-shift BTS (; 6.
BTS3001C base station support; 7. PBU power amplifier
board support; 8. EDU board function support; 9. base
station level 4 resetting function perfection; 10. base
station added with resetting alarming function; 11. Multiworkstation transparent message transfer; 12. LCS
function.

G3BSC32.10101.07.0520B

1. Concentric functions.

version
5
6

2002-2-25

G3BSC32.10101.08.0520B

1. BCCH frequency participation in baseband frequency

version

hopping

G3BSC32.10103.08.0520T

1. Dual time slot extended cell

All Rights Reserved

Page 139

GSM900/1800 BSS&PCU Network Planning Data Configuration Specification

Version 3.1

version
7

G3BSC32.10101.01.1120A

1. Channel distribution algorithm generation II

version
OMC

G3OMC32.00X01.07.0520

Supporting automatic data configuration console system,

the synchronous modification problem still exists during


parameter modification with common command lines; at
present, it can be used only at the center generated data +
automatic data configuration console; but note that these
two methods cannot be used in mixture.

2002-2-25

All Rights Reserved

Page 140

GSM900/1800 BSS&PCU Network Planning Data Configuration Specification

Version 3.1

4.7. Description Manual of Key Specifications in Various Versions of GSM


BSC32 Traffic Statistics
4.7.1 Overview
The description manual describes the key index modification of all versions of traffics
statistics starting from the version G2BSC32.10100.04.0520B. Those aspects not
mentioned here are the same as in the G2BSC32.10100.03.0520B version.
4.7.2 Traffic statistics modification of various versions
4.7.2.1 G2BSC32.10100.04.0520B/G3BSC32.10100.04.0520B version((compared with the
G2BSC32.10100.03.0520 version)

Modification Description:
a. "Times of TCH seizure failure (all)" is added with the statistics of CONN_FAIL
messages received during inter-cell handover, whether channel activation is responded,
channel activation timeout or waiting for handover detection timeout.
b. "Times of TCH seizure failure during into-cell handover in BSC (due to congestion)" is
added with the statistics of CONN_FAIL messages received during inter-cell handover,
whether channel activation is responded, channel activation timeout or waiting for
handover detection timeout (here it should not be added).
c. Software parameter switches are added to control whether to make statistics of calldrop
during the handover process. For detailed operations, refer to the software parameter
setting guidebook.
d. CLEAR_CMD of MSC received during outgoing BSC handover is turned into outgoing
BSC handover success in the statistics.
e. CLEAR_CMD of MSC received during incoming BSC handover is turned into
incoming BSC handover success in the statistics.

4.7.2.2 G3BSC32.10101.04.0520B version (compared with G3BSC32.10100.04.0520)


Modification description:

a. Statistics points of uplink short message are modified ( BUG modification in the 04
version).
b. CLEAR_CMD received during the outgoing BSC handover process are put in the
statistics according to causes. For those with the causes of CALL_CTRL and HO_SUCC,
the statistics is reflected as outgoing BSC handover success, otherwise, as outgoing BSC
handover failure

2002-2-25

All Rights Reserved

Page 141

GSM900/1800 BSS&PCU Network Planning Data Configuration Specification

Version 3.1

c. Those received during incoming BSC handover with the cause CLEAR_CMD of
CALL_CTRL are counted in the statistics as incoming BSC handover success, otherwise,
as failure in the statistics
d. Traffic statistics is optimized. For detailed settings, refer to the traffic statistics
optimization setting guidebook.
e. The "Times of TCH seizure failure during into-cell handover in BSC (due to
congestion)" is modified (so that statistics of only cases without channel distribution)
f. "Times of TCH seizure failure (all)" is added with the new channel seizure failure
statistics in handover failure.

4.7.2.3 G3BSC32.10102.04.0520B version (compared with the G3BSC32.10100.04.0520


version)

Modification Description:
a. CLEAR_CMD received during the outgoing BSC handover process are put in the
statistics according to causes. For those with the causes of CALL_CTRL and HO_SUCC,
the statistics is reflected as outgoing BSC handover success, otherwise, as outgoing BSC
handover failure
b. Those received during incoming BSC handover with the cause CLEAR_CMD of
CALL_CTRL are counted in the statistics as incoming BSC handover success, otherwise,
as failure in the statistics
c. Traffic statistics is optimized. For detailed settings, refer to the traffic statistics
optimization setting guidebook
d. The "Times of TCH seizure failure during into-cell handover in BSC (due to
congestion)" is modified (so that statistics of only cases without channel distribution is
made)
e. "Times of TCH seizure failure (all)" is added with the new channel seizure failure
statistics in handover failure
f. The report indexes meet the Mobile 2001 Annual Report Requirements: congestion has
statistics of only assignment failure, and calldrop has statistics of only CLEAR_REQ and
ERR_IND.

4.7.2.4 G3BSC32.10100.06.0520B version (compared with the G3BSC32.10100.04.0520


version)

Modification Description:
a. CLEAR_CMD received during outgoing BSC handover are put in the statistics
according to status. For those before receiving HO_SUCC, the statistics is reflected as

2002-2-25

All Rights Reserved

Page 142

GSM900/1800 BSS&PCU Network Planning Data Configuration Specification

Version 3.1

outgoing BSC handover failure, For those after receiving HO_SUCC, the statistics is
reflected as outgoing BSC handover success
b. The "Times of TCH seizure failure during into-cell handover in BSC (due to
congestion)" is modified (so that statistics of only cases without channel distribution is
made)
c. "Times of TCH seizure failure (all)" is added with the new channel seizure failure
statistics in handover failure

4.7.2.5
G3BSC32.10101.06.0520B
features
version
G3BSC32.10100.06.0520)Modification Description:

(compared

with

the

a. CLEAR_CMD received during the outgoing BSC handover process are put in the
statistics according to causes. For those with the causes of CALL_CTRL and HO_SUCC,
the statistics is reflected as outgoing BSC handover success, otherwise, as outgoing BSC
handover failure
b. Those received during incoming BSC handover with the cause CLEAR_CMD of
CALL_CTRL are counted in the statistics as incoming BSC handover success, otherwise,
as failure in the statistics

4.7.2.6G3BSC32.10101.06.0520C
features
version
G3BSC32.10100.06.0520)Modification description:

(compared

with

the

a. CLEAR_CMD received during the outgoing BSC handover process are put in the
statistics according to causes. For those with the causes of CALL_CTRL and HO_SUCC,
the statistics is reflected as outgoing BSC handover success, otherwise, as outgoing BSC
handover failure
b. Those received during incoming BSC handover with the cause CLEAR_CMD of
CALL_CTRL are counted in the statistics as incoming BSC handover success, otherwise,
as failure in the statistics

4.7.2.7
G3BSC32.10102.06.0520B
features
version
G3BSC32.10100.06.0520)Modification Description:

(compared

with

the

a. CLEAR_CMD received during the outgoing BSC handover process are put in the
statistics according to causes. For those with the causes of CALL_CTRL and HO_SUCC,
the statistics is reflected as outgoing BSC handover success, otherwise, as outgoing BSC
handover failure
b. Those received during incoming BSC handover with the cause CLEAR_CMD of
CALL_CTRL are counted in the statistics as incoming BSC handover success, otherwise,
as failure in the statistics

2002-2-25

All Rights Reserved

Page 143

GSM900/1800 BSS&PCU Network Planning Data Configuration Specification

Version 3.1

c. Traffic statistics of the year 2001 is met, with one switch added to meet the requirement
of Mobile 2001 Annual Reports that the "Times of TCH seizure success (all)" be the same
as in assignment completion messages. For specific details, refer to the software parameter
setting guidebook.

4.7.2.8 G3BSC32.10100.07.0520B versions (compared with the G3BSC32.10100.06.0520)


Modification Description:

a. CLEAR_CMD received during the outgoing BSC handover process are put in the
statistics according to causes. For those with the causes of CALL_CTRL and HO_SUCC,
the statistics is reflected as outgoing BSC handover success, otherwise, as outgoing BSC
handover failure
b. Those received during incoming BSC handover with the cause CLEAR_CMD of
CALL_CTRL are counted in the statistics as incoming BSC handover success, otherwise,
as failure in the statistics
c. Traffic statistics of the year 2001 is met, with one switch added to meet the requirement
of Mobile 2001 Annual Reports that the "Times of TCH seizure success (all)" be the same
as in assignment completion messages. For specific details, refer to the software parameter
setting guidebook.
d. Traffic statistics is optimized. For specific settings, refer to the traffic statistics
optimization setting guidebook.
e. The report indexes meet the Mobile 2001 Annual Report Requirements: congestion has
statistics of only assignment failure, and calldrop has statistics of only CLEAR_REQ and
ERR_IND

4.8 Description of data configuration for BCCH participation in frequency


hopping
1. Versions providing this function: BTS3.0 base station 0529 series.
2. Requirements on data configuration
a. The type of BCCH participates in frequency hopping can only be baseband
frequency hopping.
Frequency hopping data should be configured according to the baseband frequency
hopping data panel.
b. Selection of frequency hopping sequences should be as follows:
Selected 3 groups frequency hopping sequences. Suppose a cell has N carries. Then
the frequencys are f1, f2...., fn. Therefore, in the local office frequency hopping data
table, two groups of frequency hopping sets should be configured as follows respectively:

2002-2-25

All Rights Reserved

Page 144

GSM900/1800 BSS&PCU Network Planning Data Configuration Specification

Version 3.1

{{f2. f3...., fn}, {f1. f2...., fn}. The HSN in the two groups of data can be selected
arbitrarily, but they must be the same.
In the local office wireless channel configuration table, the configurations of all
channels are as shown below (TRX0 being BCCH). Note here that the MAIO of each
TRX is different, but must be the same in the same TRX. It must be specifically pointed
out here that the frequency hopping index value of TS0 in TRX0 should be 0, so as to
indicate that it has only one frequency, and no frequency hopping occurs at TS0.
TRX0 channel configuration TRX1 channel configuration

TRX2 channel configuration

TS0

f0

f1. f2 HSN=? MAIO=0

f1. f2 HSN=? MAIO=1

TS1

f0,f1. f2 HSN=? MAIO=0

f0,f1. f2 HSN=? MAIO=1

f0,f1. f2 HSN=? MAIO=2

TS2

f0,f1. f2 HSN=? MAIO=0

f0,f1. f2 HSN=? MAIO=1

f0,f1. f2 HSN=? MAIO=2

TS3

f0,f1. f2 HSN=? MAIO=0

f0,f1. f2 HSN=? MAIO=1

f0,f1. f2 HSN=? MAIO=2

TS4

f0,f1. f2 HSN=? MAIO=0

f0,f1. f2 HSN=? MAIO=1

f0,f1. f2 HSN=? MAIO=2

TS5

f0,f1. f2 HSN=? MAIO=0

f0,f1. f2 HSN=? MAIO=1

f0,f1. f2 HSN=? MAIO=2

TS6

f0,f1. f2 HSN=? MAIO=0

f0,f1. f2 HSN=? MAIO=1

f0,f1. f2 HSN=? MAIO=2

TS7

f0,f1. f2 HSN=? MAIO=0

f0,f1. f2 HSN=? MAIO=1

f0,f1. f2 HSN=? MAIO=2

c. Other places are configured in the same way as the baseband frequency hopping.

2002-2-25

All Rights Reserved

Page 145

Das könnte Ihnen auch gefallen