You are on page 1of 19

UMTS Radio Parameter Planning

Technical Guide


Version: v1.0













Release 2008-3-21 Implementation 2008-3-21
Released by UMTS Radio Planning & Optimization Dept., ZTE Corp.

Internal Use Only
This document contains proprietary information of ZTE Corporation and is not to be disclosed or used except
in accordance with applicable agreements.
1
Modification Record
File No.
Drafter /
Modifier
Major Points Modified
Update
Date
Version
Reason for
modification
1 WU Yuanjiang 2008-3-21 V1.0 Guide
establishment



























Internal Use Only
This document contains proprietary information of ZTE Corporation and is not to be disclosed or used except
in accordance with applicable agreements.
2
Contents
1 PURPOSE OF THE GUIDE...........................................................................................................................4
2 RADIO PARAMETER OF WCDMA NEWLY-CONSTRUCTED NETWORK.......................................4
2.1 CELL RADIO PARAMETERS CONTROLLED BY ONE RNC.............................................................................4
2.1.1 MCC..................................................................................................................................................6
2.1.2 MNC..................................................................................................................................................6
2.1.3 RNCId................................................................................................................................................6
2.1.4 NodeB No..........................................................................................................................................6
2.1.5 SectorId.............................................................................................................................................6
2.1.6 Cid.....................................................................................................................................................6
2.1.7 LAC...................................................................................................................................................7
2.1.8 SACPC...............................................................................................................................................7
2.1.9 SACB.................................................................................................................................................7
2.1.10 SACBPre.......................................................................................................................................8
2.1.11 RAC...............................................................................................................................................8
2.1.12 LCId..............................................................................................................................................8
2.1.13 LCGId............................................................................................................................................8
2.1.14 TCell..............................................................................................................................................8
2.1.15 UUARFCH....................................................................................................................................8
2.1.16 DUARFCH....................................................................................................................................8
2.1.17 PrimscraCode...............................................................................................................................8
2.1.18 URAnum........................................................................................................................................9
2.1.19 URA...............................................................................................................................................9
2.2 NEIGHBOR CELL CONFIGURATION WITHIN THE SYSTEM.............................................................................9
2.3 NEIGHBOR CELL CONFIGURATION BEYOND THE SYSTEM.........................................................................13
2.4 NEIGHBOR CELL CONFIGURATION CONTROLLED BY OTHER RNC...........................................................14
2.5 GSM CELL CONFIGURATION....................................................................................................................16
3 RADIO PARAMETERS REQUIRE TO BE CONFIGURED IN GSM SYSTEM IN MUTUAL
OPERATION BETWEEN 2G AND 3G SYSTEM..............................................................................................16
3.1 REQUIRED 3G NEIGHBOR CELL INFORMATION CONFIGURED IN GSM SYSTEM........................................17

Internal Use Only
This document contains proprietary information of ZTE Corporation and is not to be disclosed or used except
in accordance with applicable agreements.
3
3.2 INFORMATION NEEDS TO CONFIGURED FOR RESELECTION FROM 2G SYSTEM TO 3G SYSTEM.................17
4 ATTACHMENT: INPUT TEMPLATE OF RADIO PARAMETER CONFIGURATION FOR
WCDMA NEWLY CONSTRUCTED NETWORK ............................................................................................18


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

1 Purpose of the Guide
Initial radio parameters need to be configured and data need to be planned by engineers from Customer
Service Department for the newly established or capacity expanded network before commissioning and
debugging. The document mainly introduces detailed principles and methods for radio parameters planning
in newly established network, including cells basic information, such as cells ID, scrambling codes,
neighbor cells, etc.
2 Radio Parameter of WCDMA Newly-constructed Network
Radio parameters mentioned here represent some parameters in each practical network that need to be
set according to practical situation, such as network number, NodeB number, cell number, routing area code,
etc.; some commonly used parameters such as cell handover parameter and reselection parameter can be
generally set as default and wont be described here. These configured parameters need to be set in OMC by
engineers from Customer Service Department, some need to be set in NodeB, such as cell number. Because
there are numerous data in large networks, data batch input can be realized in OMC for convenient
configuration; each parameter owns input template.
2.1 Cell Radio Parameters Controlled by One RNC
Attachment 1 is a detailed example and also a configuration template, including parameters need to be
configured in WCDMA system. All cell radio parameters that need to be configured are listed in the
following table, mainly in sky-blue part, which will be introduced one by one as follows.
What need to be noticed is that the parameters input in template mode for configuring are controlled by
one RNC; if parameters are controlled by several RNC, they need to be configured for several times by the
same configuration method.
Table 1 Cell Parameter Description
Parameter Description Value scope
MCC Mobile Country Code 0..999
MNC Mobile Network Code 0..999
RncId RNC Identity 0..4095
NodebNo NodeB Number 065535
SectorId Sector Identity 16
CId Cell Identity 0.. 65535
LAC Location Area Code 1..0xfffd, 0xffff
SACPC Serving area code belong to CS+PS domain 1..0xfffd, 0xffff
SACBPre SACB Configuration Tag 0:False 1:True
SACB Serving area code belong to BC domain 0...65535
RAC Routing area code 0...255
LCId Local Cell Identity 0.. 65535
LCGId Local Cell Group ID 0.. 65535

Internal Use Only
This document contains proprietary information of ZTE Corporation and is not to be disclosed or used except
in accordance with applicable agreements.
5
TCell T_Cell (09*256)chip step:256chip
UUARFCN UUARFCN 9612..9888 or 9262..9538
DUARFCN DUARFCN 10562..10838 or 9662..9938
PrimScraCode Cell Primary Scrambling Code 0511
URANum URA Number 1.. 4
URA URA identity 0..65535
In3G2GEdge Is at the edge of 3G and 2G
0False 1True
CellIndivOffset Cell individual offset
-10..10dB step 0.5
UseOfHCS Use of HCS
1Not used 2used
HcsPrio HCS_PRIO 0..7
CellDescripType Cell Description Type 0: Center Point with Altitude
and Cell Radius1: Polygon
2: Arc
PolygonPointNum Polygon Point Number 3.. 15
PolyLatitudeSign Polygon Point Latitude Sign 0: North 1: South
PolyLatitude Degree of Polygon Point Latitude (0.. 90)step 1 second
PolyLongitude Degrees of Polygon Point Longitude (-180.. 180) step 1 second
LatitudeSign Latitude Sign for Cell Center 0: North 1: South
Latitude Degree of Latitude for Cell Center (0.. 90)step 1 second
Longitude Degrees Of Longitude for Cell Center (-180.. 180)step 1 second
Altitude Cell Altitude for Cell Center (0..2^15-1)m
AltitudeDir Direction of Altitude for Cell Center 0: Height 1: Depth
AltitudeAcc Altitude Accurary (0...990)m
Confidence Confidence
0..100%
CellRadius Cell Radius
0..1806627m
AnteType Antenna Type
0Omni Antenna 1Beam
Antenna
AnteLatitudeSign Antenna Latitude Sign 0: North 1: South
AnteLatitude Degree of Antenna Latitude (0.. 90)step 1 second

Internal Use Only
This document contains proprietary information of ZTE Corporation and is not to be disclosed or used except
in accordance with applicable agreements.
6
AnteLongitude Degrees of Antenna Longitude (-180.. 180)step 1 second
AnteAltitude Antenna Altitude (0..2^15-1)m
AnteAltitudeDir Direction of Antenna Altitude 0: Height 1:Depth
OffsetAngle Offset angle (0..360)
InnerAngle Inner Angle (0..360)
2.1.1 MCC
MCC is Mobile Country Code for uniquely identifying countries in which mobile subscriber (or
system) is located; it is allocated internationally and the code for China is 460, while the code for other
countries can be searched out on Google website.
2.1.2 MNC
MNC is Mobile Network Code for uniquely identifying a specific PLMN in a certain country
(determined by MCC), it is provided by operators such as China Mobile and China Unicom.
2.1.3 RNCId
RNCId is for uniquely identifying RNC in a specific PLMN in one country (determined by MCC).
If there is only one RNC, RNCId can be set randomly; its default value is 1. If the network
dimension is so large that many RNC are used, then RNCId shall be set flexibly and differentiated by
different construction period, different cities, different NodeB model (R99/HSDPA), etc.
2.1.4 NodeB No
NODEB number is valid only to RNC; its value is from 0 to 65535 and is usually restricted by RNC
capacity and practical network dimension. There will not be too many NodeB controlled by one RNC, so
different value range can be used to identify different NodeB.
If the sites number shall be the same with that in GSM system, we use GSM numbering.
NodeB is classified by phase, for instance, 1XXX represents phase one, 2XXX represents phase two,
etc.
NodeB number can also be used for differentiating RNC boundary, cities (for instance, 1XX
represents city one, 2XX represents city two, etc.), site types (macro-site/micro-site, R99/HSDPA, etc.)
as well as other features.
2.1.5 SectorId
Sector Identity is only valid in Node B; its value scope is from 1 to 6. Sectors are named 1, 2, 3
clockwise from the North. Generally the site with one carrier and three sectors is in common use, so
sector identity value is usually from 1 to 3.
2.1.6 Cid
Cell Identitys scope is from 0 to 65535, uniquely for identifying cell in RNC. When the network
dimension is relatively small, Cid is represented as NodeB NoSectorId that limits the maximum

Internal Use Only
This document contains proprietary information of ZTE Corporation and is not to be disclosed or used except
in accordance with applicable agreements.
7
NodeB number to 9999; but this isnt compulsory, Cid can be set flexibly according to network actual
situation. Generally the last digit of Cid is used to identify sector or carrier; as to 1C3S, the last digit of
Cid is 1, 2, 3; as to 2C3S, the last digit of Cid is successively 4, 5, 6; as to 3C3S, the last digit of Cid is
successively 7, 8, 9. What needs to be noticed is that when site is omni-site or owns 2 sectors, the left ID
in the same group (3 identities comprise a group) will be abandoned, and new cell will be identified
again, the demonstration is as follows.
Table 2 Cid Demonstration
Site
Number
Site
Type
Sector
Number
Carrier
Number
Cid
Demonstration
101 3C3S 1 1 1011
101 3C3S 2 1 1012
101 3C3S 3 1 1013
101 3C3S 1 2 1014
101 3C3S 2 2 1015
101 3C3S 3 2 1016
101 3C3S 1 3 1017
101 3C3S 2 3 1018
101 3C3S 3 3 1019
102 2C2S 1 1 1021
102 2C2S 2 1 1022
102 2C2S 1 2 1024
102 2C2S 2 2 1025
103 1C1S 1 1 1031
104 2C1S 1 1 1041
104 2C1S 1 2 1044
2.1.7 LAC
LAC is Location Area Code. For locating MS, each covering area in PLMN has been divided into
several location areas; location area code is to identify different location areas. LAC is a part of LAI
(LAI = MCC + MNC + LAC). LAI is Location Area Identity. One location area is composed by several
cells.
Cell number set in location area is mainly determined by paging capacity, frequency update and
traffic distribution. Paging capacity determines the maximum cell number; too frequent frequency update
may cause low call success rate and limits the minimum site number. LAC boundary shall be located in
the place where traffic is low. Detailed LAC planning please refer to WCDMA LAC Planning
Instruction.
2.1.8 SACPC
SAC is Serving Area Code, uniquely identifies one cell or several cells in one location area. It is used
to locate UE for CN.
One cell has one or two SAC, one belongs to CS +PS domain, and another belongs to BC domain.
One cell has to own one SAC belongs to CS +PS domain, which is SACPC.
The value of cells serving area code belongs to CS+PS domain is corresponding to RAC.
2.1.9 SACB
SACB is Serving Area Code belong to BC domain; its default value is 0.

Internal Use Only
This document contains proprietary information of ZTE Corporation and is not to be disclosed or used except
in accordance with applicable agreements.
8
2.1.10 SACBPre
SACB Configuration Tag represents whether SACB is configured; its present default value is 0.
2.1.11 RAC
RAC is Route Area Code that identifies a route area in location area in GSM-MAP PLMN for packet
service. RAC is a part of RAI (RAI = PLMN-ID + LAC + RAC). RAC is set by operator through O&M
in RNC. Now RAC value is usually the same with that of LAC, or refers to GPRS/EDGE value. We need
to pay attention that site number shall not exceed its scope in route area.
2.1.12 LCId
LCId is Local Cell Identity. Local cell means resource of NodeB that can be configured as one
certain cell; it is used for identifying corresponding cell resource when information exchange between
CRNC and NodeB as well as when there is no certain cell has been established. Notice: local cell
identity has to be confirmed according to NodeB, the value of LCId has to be the same with the value of
established logical cell identity, and otherwise cell establishment is failed.
2.1.13 LCGId
LCGId is Local Cell Group ID. Cells can share BP resource only when they are in the same local cell
group.
2.1.14 TCell
TCell is used for defining the time delay of a cell of a NodeB relative to the NodeB BFN. It
determines the time delay between start time of cell SCH, CPICH, downlink PSC and BFN.
The parameter is mainly used in Cell setup Request message for establishing cell. The function of the
parameter is to avoid inter-cell interference; for instance, SCH transmitting time varies with cells that
facilitates UE to carry out cell synchronization and avoids interference.
We suggest that TCell of geographically adjacent cells that belong to the same NodeB shall not be
the same. Now the default settings are 256*0, 256*2 and 256*4 for 3 sectors successively.
2.1.15 UUARFCH
UUARFCH is uplink utter radio frequency channel number, corresponding to the central frequency
of cell uplink channel carrier. Its value is frequency*5.
2.1.16 DUARFCH
DUARFCH is downlink utter radio frequency channel number, corresponding to the central
frequency of cell downlink channel carrier. Its value is frequency*5.
2.1.17 PrimscraCode
Cell primary scrambling code is used for distinguishing cell; UTRAN system has totally 512
downlink primary scrambling codes. Cell primary scrambling code number is informed to NodeB
through CELL SETUP REQUEST message when cell is established; it can not be modified in cell
reconfiguration; if it has to be modified, we can only delete the cell and reset a new one.
Scrambling code multiplexing distance is mainly considered in scrambling code planning;

Internal Use Only
This document contains proprietary information of ZTE Corporation and is not to be disclosed or used except
in accordance with applicable agreements.
9
meanwhile, reservation of boundary area and indoor coverage shall also be noticed. Detailed planning
methods please refer to WCDMA Cell Scrambling Code Planning Instruction (v1.0).
Presently, there are two types of scrambling code planning. One is planning successively in 1, 2, 3
order. Another is planning with the interval of 8. If customer hasnt chosen which type of planning, we
use the successive planning. Three scrambling codes are set as a group. For instance, if all of the
surrounding sites have 3 sectors except one site owns 2 sectors, then the left third scrambling code isnt
used in the 2-sector site and the next scrambling code group is used in the next site.
Generally, we use network planning and simulation software to plan scrambling code; set Atoll as an
example, it can plan cell/site/site cluster separately, and enable different carriers to use same scrambling
code, or even introduce neighbor cell relationship as a restraint condition. The detailed operation please
refers to related instructions.
2.1.18 URAnum
URAnum is the number of UTRAN registration area, also the number of URA that cells belong to.
One cell can belong to at most 4 URAs; UE that stays in the cell can belong to different URAs, but UE
in URA_PCH status can only belong to one of the URAs. The default value of URAnum is 1.
2.1.19 URA
URA is UTRAN Registration Area, which is for avoiding too frequent signaling; when using
multi-layer structure to carry out cell planning, as to UE that moving in high speed, we can use
macro-beehive with low priority to decrease cell reselection times. According to the same principle,
URA update is lower than Cell update, so we can control when making UE stay in Cell_URA status
through calculating UEs cell update times; or counting by ourselves and make UE status change
automatically from Cell_PCH to URA_PCH when cell reselection times exceeds a certain number
during a period of time. Adjacent cells in different URAs can be configured to belong to many URAs for
avoiding frequent URA update.
2.2 Neighbor Cell Configuration within the System
For insuring UEs mobility, handover can only be carried out when neighbor cells are configured in
neighbor cell list by OMC. The following table is the input template of neighbor cell configuration, and these
in sky-blue parts are ones require configuration.
Notice: in neighbor cell configuration, cells are identified through Cid.
Table 3 Parameter Description in Neighbor Cell List Configuration
Parameter Description Scope
MCC Mobile Country Code 0..999
MNC Mobile Network Code 0..999
RncId RNC Identity 0..4095
CId Cell Identity 0.. 65535
NMCC
Mobile Country Code of Neighboring
cell
0..999

Internal Use Only
This document contains proprietary information of ZTE Corporation and is not to be disclosed or used except
in accordance with applicable agreements.
10
NMNC
Mobile Network Code of Neighboring
cell
0..999
NRncId RNC identity of Neighboring cell 0..4095
NCId Neighboring Cell ID 0.. 65535
MeasPrio
Measurement Priority of Neighboring
cell
0..2
ShareCover Share Cover Indication
0:Neighbor; 1:Overlap;
2:Covers; 3:Contained in
CellIndivOffset Cell individual offset (-10..10)dB step 0.5dB
FbdCellInd FbdCellInd 0:False 1:True
ReadSFNInd Read SFN indicator 0:False 1:True
UseOfHCS Use of HCS 1: Not used 2: used
Qoffset1SNSib11 Qoffset1
s,n
in SIB11 (-50..50)dB
Qoffset2SN Sib11 Qoffset2
s,n
in SIB11 (-50..50)dB
QhcsEcN0Sib11 Qhcs for CPICH Ec/No in SIB11 (-24..0)dB, step:0.5dB
QhcsRscpSib11 Qhcs for CPICH RSCP in SIB11 (-115..-26)dBm
QhcsEcN0Sib12 Qhcs for CPICH Ec/No in SIB12 (-24..0)dB, step:0.5dB
QhcsRscpSib12 Qhcs for CPICH RSCP in SIB12 (-115..-26)dBm
PenaltyTime
Sib11
penalty time in SIB11
(Not Used, 10, 20, 30, 40, 50,
60 )s
TempOffset1Sib11 Temporary_offset1 in SIB11
3, 6, 9, 12, 15, 18, 21, inf
dB
TempOffset2Sib11 Temporary_offset2 in SIB11
2, 3, 4, 6, 8, 10, 12, infdB
Qoffset1SNSib12 Qoffset1
s,n
in SIB12 (-50..50)dB
Qoffset2SN Sib12 Qoffset2
s,n
in SIB12 (-50..50)dB
PenaltyTime
Sib12
penalty time in SIB12
(Not Used, 10, 20, 30, 40, 50,
60 )s
TempOffset1Sib12 Temporary_offset1 in SIB12
3, 6, 9, 12, 15, 18, 21, inf
dB

Internal Use Only
This document contains proprietary information of ZTE Corporation and is not to be disclosed or used except
in accordance with applicable agreements.
11
TempOffset2Sib12 Temporary_offset2 in SIB12
2, 3, 4, 6, 8, 10, 12, infdB
The meaning of each parameter is understandable, so we mainly introduce method and principle of
neighbor cell configuration.
Principle of neighbor cell configuration mainly includes neighbor cell number, geographic topological
structure, coverage interference, etc.
Because the maximum number of neighbor cell list within a system is regulated as 31 in protocol,
neighbor cell lists will be combined in soft handover status; we need to control neighbor cell number in
configuration and try to minimize it as much as possible in the precondition of insuring the successful
handover.
Now all of the network planning and simulation software can be used for neighbor cell planning; for
instance, the already existed neighbor cell relationship can be input in Atoll. But the accuracy of the present
planning result of network planning and simulation software still needs to be improved; the situation of too
many configured neighbor cells or missing out neighbor cell configuration happens, therefore we can use
RNA to carry out manual checking and neighbor cell planning if the sites scale isnt large.
Whether neighbor cell list setting is reasonable impacts handover between sites; the initial neighbor cell
list formed in system design phase is set according to the following mode, then neighbor cell list will be
adjusted according to handover times after system is commissioned.
Cells of one same site have to be set as each others neighbor cell; the first layer and the second layer
cells can be chosen as the present cells neighbor cell according to present cells coverage (shown in the
following figure). The second layer cells on the same direction of the present sector are set as its neighbor
cells, the first layer cells on the opposite direction of the present sector are also set as its neighbor cells.
The following is an example of neighbor cell setting shown in figure 1.
The red one is the present cell whose scrambling codes are set as 4, 8 and 12; those cells formed in
boldfaced broken lines are present sectors neighbor cells. Pink ones are the first layer cells; blue ones are
the second layer cells.

Internal Use Only
This document contains proprietary information of ZTE Corporation and is not to be disclosed or used except
in accordance with applicable agreements.
12
1
9
6
2
0
0
2
0
4
4
8
1
2
1
0
0
1
0
4
1
0
8
1
2
4
1
2
8
1
3
2
1
6
2
0
2
4
8
8
9
2
9
6
2
2
0
2
2
4
2
2
8
7
6
8
0
8
4
1
1
2
1
1
6
1
2
0
2
0
8
2
1
2
2
1
6
6
4
6
8
7
2
1
6
0
1
6
4
1
6
8
1
4
8
1
5
2
1
5
6
5
2
5
6
6
0
1
7
2
1
7
6
1
8
0
4
0
4
4
4
8
2
8
3
2
3
6
1
3
6
1
4
0
1
4
4
1
8
4
1
8
8
1
9
2

Figure 1 Illustration of Neighbor Cell Configuration

The present cells neighbor cell can be set as follows:
Table 4 Demonstration of Neighbor Cell List Configuration
Sector
number
Scrambling
code
number
Neighbor cell list
1-1 4
8(1-1)12(1-2)32(3-2)48(4-3)88(8-1)92(8-2)100(9-1)108(9-3)
112(10-1)128(11-2)140(12-2)144(12-3)156(13-3)196(17-1)
200(17-2)204(17-3)208(18-1)220(19-1)
Adjust neighbor cells according to each cells configured neighbor cell number as well as the situation
whether cells are set as mutual neighbor cells. We try to realize neighbor cell mutual configuration; in
principle, neighbor cell number shall not exceed 18, neighbor cell mutual configuration rate has to be higher
than 90%. The adjustment order is firstly the second layer cells that arent on the direction of the present cell,
and secondly the second layer cells that are on the direction of the present cell.

Internal Use Only
This document contains proprietary information of ZTE Corporation and is not to be disclosed or used except
in accordance with applicable agreements.
13
2.3 Neighbor Cell Configuration beyond the System
When constructing network with other system, such as GSM system, on the coverage edge of WCDMA
system, UE can continuously enjoy services through handover to GSM system due to GSM systems
long-time construction and perfect coverage. Therefore, neighbor cells among systems need to be configured
for handover or reselection. The following table shows template parameters in neighbor cell configuration
among systems.
Table 5 Parameter Table for Neighbor Cell Configuration among Systems
ModInd Modify Indicator A:Add D:Delete
M:Modify
MCC Mobile Country Code 0..999
MNC Mobile Network Code 0..999
RncId RNC Identity 0..4095
CId Cell Identity 0.. 65535
NMCC Mobile Country Code of Neighboring
cell
0..999
NMNC Mobile Network Code of Neighboring
cell
0..999
LAC Location Area Code of Neighboring cell 1..0xfffd, 0xffff
CI GSM Neighboring Cell Identifier 0.. 65535
GsmShareCover Share Cover Indication 0:Neighbor; 1:Overlap;
2:Covers; 3:Contained
in
MeasPrio Measurement Priority of Neighboring
cell
0..2
UseOfHCS Use of HCS 1: Not used 2: used
Qoffset1SNSib11 Qoffset1
s,n
in SIB11 (-50..50)dB
QhcsSib11 Qhcs in SIB11 (-110..-37)dBm
PenaltyTime Sib11 penalty time in SIB11 (Not Used, 10, 20, 30, 40,
50, 60 )s
TempOffset1Sib11 Temporary_offset1 in SIB11
3, 6, 9, 12, 15, 18, 21,
inf dB
Qoffset1SNSib12 Qoffset1s,n in SIB12 (-50..50)dB
QhcsSib12 Qhcs in SIB12 (-110..-37)dBm
PenaltyTime Sib12 penalty time in SIB12 (Not Used, 10, 20, 30, 40,
50, 60 )s

Internal Use Only
This document contains proprietary information of ZTE Corporation and is not to be disclosed or used except
in accordance with applicable agreements.
14
TempOffset1Sib12 Temporary_offset1 in SIB12
3, 6, 9, 12, 15, 18, 21,
inf dB
The meaning of each parameter is understandable, what requires attention is that GSM cell is identified
through LAC+CI. The method of neighbor cell configuration is generally the same with that in the system.
There are two types of common mutual operations between 2G and 3G system. One is handover within
GSM system on the coverage edge of WCDMA system; another is the whole WCDMA network is handed
over in GSM system.
When WCDMA network realizes continuous coverage, WCDMA system is only handed over in 2G
system on its coverage edge, so only sites on the coverage edge need to be configured with neighbor cells.
The following principles are mainly taken into account.
1 Co-sited cells with the same direction are configured as neighbor cells;
2 GSM900 cells own the priority to be chosen as neighbor cells;
3 Try not to configure congested GSM cells as neighbor cells as much as possible.
When WCDMA network cannot realize continuous coverage, the mutual operation between the whole
WCDMA network and 2G network shall be taken into account. The 2G neighbor cell configuration method
in the whole WCDMA network is the same with WCDMA neighbor cell configuration method in WCDMA
system, but the situation of neighbor cell traffic congestion shall also be considered at the same time.

2.4 Neighbor Cell Configuration Controlled by Other RNC
Inter-RNC handover is hard handover; besides neighbor cell needs to be configured, corresponding cell
information shall also be configured. Neighbor cell information table is shown as follows; parameter
meaning is the same with that controlled by one RNC.
Table 6 Neighbor Cell Information Table Controlled by One RNC
ModInd Modify Indicator A:Add D:Delete M:Modify
MCC Mobile Country Code of Neighboring cell 0..999
MNC Mobile Network Code of Neighboring cell 0..999
RncId RNC identity of Neighboring cell 0..4095
CId Neighboring Cell ID 0.. 65535
LAC Location Area Code of Neighboring cell 1..0xfffd, 0xffff
SACPC Serving area code belong to CS+PS domain of
Neighboring cell
1..0xfffd, 0xffff
SACBPre SACB Configuration Tag 0:False 1:True
SACB Serving area code belong to BC domain of
Neighboring cell
0...65535
RAC Routing area code of Neighboring cell 0...255

Internal Use Only
This document contains proprietary information of ZTE Corporation and is not to be disclosed or used except
in accordance with applicable agreements.
15
URANum URA Number 1.. 4
URA URA identity 0..65535
UUARFCN UUARFCN 9612..9888 or 9262..9538
DUARFCN DUARFCN 10562..10838 or 9662..9938
PrimScraCode Cell Primary Scrambling Code 0511
HcsPrio HCS_PRIO 0..7
QqualMinSib11 Qqualmin in SIB11
-24..0dB
QrxLevMinSib11 Qrxlevmin in SIB11 (-115..-25)dB step 2dB
QqualMinSib12 Qqualmin in SIB12
-24..0dB
QrxLevMinSib12 Qrxlevmin in SIB12 (-115..-25)dB step 2dB
MaxRACHTxPwr RACH Maximum Allowed UL TX Power (-50..33)dBm
PcpichPwr Primary CPICH Power (-10..50)dBm
CellDescripType Cell Description Type 0: Center Point with Altitude
and Cell Radius 1:Polygon
2:Arc
PolygonPointNum Polygon Point Number 3.. 15
PolyLatitudeSign Polygon Point Latitude Sign 0: North 1: South
PolyLatitude Degree of Polygon Point Latitude (0.. 90)step 1 second
PolyLongitude Degrees of Polygon Point Longitude (-180.. 180) step 1 second
LatitudeSign Latitude Sign for Cell Center 0: North 1: South
Latitude Degree of Latitude for Cell Center (0.. 90)step 1 second
Longitude Degrees Of Longitude for Cell Center (-180.. 180)step 1 second
Altitude Cell Altitude for Cell Center (0..2^15-1)m
AltitudeDir Direction ofAltitude for Cell Center 0:Height 1: Depth
AltitudeAcc Altitude Accurary (0...990)m
Confidence Confidence
0..100%
CellRadius Cell Radius
0..1806627m
AnteType Antenna Type
0 Omni Antenna 1 Beam
Antenna
AnteLatitudeSign Antenna Latitude Sign 0: North 1: South

Internal Use Only
This document contains proprietary information of ZTE Corporation and is not to be disclosed or used except
in accordance with applicable agreements.
16
AnteLatitude Degree of Antenna Latitude (0.. 90)step 1 second
AnteLongitude Degrees of Antenna Longitude (-180.. 180)step 1 second
AnteAltitude Antenna Altitude (0..2^15-1)m
AnteAltitudeDir Direction of Antenna Altitude 0: Height 1:Depth
OffsetAngle Offset angle (0..360)
InnerAngle Inner Angle (0..360)

2.5 GSM Cell Configuration
When doing mutual operation between 2G and 3G system, for instance, handover/reselection from 3G
system to 2G system, besides neighbor cell needs to configured, GSM cell information shall also be
configured in WCDMA system, which is shown in the following table.
Table 7 GSM Cell Parameter Configuration Table
Parameter Description Scope
LAC Location Area Code 1..0xfffd, 0xffff
CI Cell Identifier 065535
NCC Network Color Code 0..7
BCC Base Station Color Code 0..7
Bandindicator Band indicator
0DCS 1800 band used
1PCS 1900 band used
2GSM 900 band used
BCCHARFCN BCCH ARFCN 0..124 and 975.. 1023 or
512..885
MaxULTxPwr Maximum Allowed UL TX Power (-50..33)dBm
HcsPrio HCS_PRIO 0..7
QrxLevMinSib11 Qrxlevmin in SIB11 (-115..-25)dB step 2dB
QrxLevMinSib12 Qrxlevmin in SIB12 (-115..-25)dB step 2dB
CellIndivOffset Cell individual offset (-50..50)dB step 1dB
GSM cell parameter configuration table can be obtained from GSM staff.

3 Radio Parameters Require to be Configured in GSM System in Mutual Operation between 2G
and 3G System
In mutual operation between 2G and 3G system, besides configuring GSM cell information in WCDMA

Internal Use Only
This document contains proprietary information of ZTE Corporation and is not to be disclosed or used except
in accordance with applicable agreements.
17
system, WCDMA cell information and neighbor cell information shall also be configured in GSM system
that requires cooperation with GSM equipment manufacturer. Provided parameters vary with manufacturers;
this chapter mainly introduces parameter configuration template for ZTE GSM system. Parameter
configuration template please refers to Attachment 2.

3.1 Required 3G Neighbor Cell Information Configured in GSM System
Required 3G cell information is shown in the following table.
Table 8 Neighbor Cell Parameter Configuration Table in GSM System
Parameter Description Scope
CI_G 2G GSM cell ID 0.. 65535
NCI_W Neighbor cell
WCDMA cell ID
0.. 65535
EcID External cell ID 0..65535
CI WCDMA cell id 0.. 65535
MCC
Mobile country
code
0..99
MNC
Mobile network
code
0..99
LAC Location area code 1..0xfffd, 0xffff
PSC Scrambling code 0..511
RNCID RNC ID 0..4095
FREQ
Downlink
frequency number
Central frequency*5
BANDWIDCH
3G
Band width
5NN is the number
of frequency
EcID is external cell identity, can be set from 1; different cells own different identities. We
suggest keeping EcID the same with CI, or using CI as EcID directly.

3.2 Information Needs to Configured for Reselection from 2G System to 3G System
Required 3G cell information is shown in the following table.
Table 9 Neighbor Cell Parameter Configuration Table in GSM System
Parameter Description Scope
BSCID GSM BSC identity
SITEID GSM site identity
BTSID BTS identity
2G_CI
2G
GSM cell identity
Refer to GSM criterion
C_ID
3G WCDMA cell 0..65535

Internal Use Only
This document contains proprietary information of ZTE Corporation and is not to be disclosed or used except
in accordance with applicable agreements.
18
identity
Site Name WCDMA site name 0..999
MCC
Mobile country
code
0..999
MNC
Mobile network
code
0..999
RNC_ID RNC identity 0..4095
C_ID
WCDMA cell
identity
0..65535
LAC Location area code 1..0xfffd, 0xffff
FDDARFCN
Downlink
frequency number
Central frequency*5
SCRAMBLINGCODE
Scrambling code 0..511
4 Attachment: Input Template of Radio Parameter Configuration for WCDMA Newly Constructed
Network
Attachment 1: ZXWR OMC network planning and optimization batch input template, each table can be
input separately.
ZXWR
OMC. xl s

Attachment 2: neighbor cell data template configured in GSM system.
GSM
. r ar

You might also like