Guide To LTE Neighboring Cell and X2 Interface Planning

Guide to LTE Neighboring Cell
and X2 Interface Planning
Issue
3.2
Date
2012-03-28
HUAWEI TECHNOLOGIES CO., LTD.
Copyright Huawei Technologies Co., Ltd. 2012. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means without prior
written consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and
the customer. All or part of the products, services and features described in this document may not be
within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements,
information, and recommendations in this document are provided "AS IS" without warranties, guarantees or
representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address:
Huawei Industrial Base

Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website:
http://www.huawei.com
Email:
support@huawei.com
2012-03-28
Huawei Proprietary and Confidential

Copyright Huawei Technologies Co., Ltd.
Guide to LTE Neighboring Cell and X2 Interface

Planning
About This Document
About This Document

Author
Prepared by
Sun Lecheng
Date
Reviewed by
Date
Reviewed by
Date
Approved by
Date
2010-08-27
Change History
Date
Issue
Description
Reviewed by
Prepared by
2010-08-27
1.0
Initial release.
Yang Shijie,
Wang Na
Sun Lecheng
2010-09-28
1.1
Deleted the algorithm of the dedicated tools for

Worldwide Interoperability for Microwave
Access (WiMAX) neighboring cell planning.
Yang Shijie,
Wang Na
Sun Lecheng,
Kong Gang
Yang Shijie,
Wang Na
Wang
Qingqing
Added preparation before neighboring cell

planning using the U-Net.
Added the example for X2 interface planning
results.
2011-02-20
2.0
Added Long Term Evolution (LTE) neighboring

cell planning principles.
Upgraded the eRAN2.0 X2, neighboring cell,
and external cell configuration.
Added the operation of using ID Get v1.0.xls to
extract IDs for X2 interface planning.
2011-07-15
3.0
Added script preparation and batch processing.
Yang Shijie
Added neighboring cell configuration in

RAN-sharing modes.
Changed the maximum number of
intra-frequency, inter-frequency, and intra-RAT
neighboring cells that can be configured.
2012-03-28

ii

Planning
About This Document
Date
Issue
Description
Reviewed by
Prepared by
2012-01-29
3.1
Added the description that the GENEX U-Net

V300R007C00SPC200 does not support multiple
modes.
Lin Jia
2012-02-07
3.2
Modified according to review comments.
Lin Jia
Added the example of neighboring cell planning

based on live network data.
2012-03-28

iii

Planning
Contents
Contents
About This Document .................................................................................................................... ii
1 Neighboring Cell Planning ......................................................................................................... 1
1.1 Neighboring Cell Planning Principle ............................................................................................................... 1
1.2 Intra-frequency Neighboring Cell Planning Analysis ...................................................................................... 2
1.3 Inter-frequency Neighboring Cell Planning Analysis ....................................................................................... 2
1.4 Inter-RAT Neighboring Cell Planning Analysis ............................................................................................... 2
2 Neighboring Cell Planning Solutions ...................................................................................... 3

2.1 Neighboring Cell Planning Based on Live Network Data................................................................................ 3
2.2 Neighboring Cell Planning Using Dedicated Tools.......................................................................................... 5
2.2.1 U-Net Neighboring Cell Planning Procedure .......................................................................................... 6
2.3 System Automatic Planning ........................................................................................................................... 13
3 X2 Interface Planning ................................................................................................................. 14

4 Script Preparation and Batch Processing ................................................................................ 16
4.1 Script Preparation for Intra-Frequency Neighboring Cells ............................................................................ 16
4.2 Script Preparation for Inter-Frequency Neighboring Cells............................................................................. 29
4.3 Script Preparation for Inter-RAT Neighboring Cells ...................................................................................... 50
4.3.1 UTRAN (UMTS/TD-SCDMA) ............................................................................................................ 50
4.3.2 GERAN (GSM/GPRS/EDGE) .............................................................................................................. 73
4.3.3 CDMA2000........................................................................................................................................... 89
4.4 Script Preparation in RAN-Sharing Mode ................................................................................................... 103
4.4.1 Neighboring Cell Configuration in RAN Sharing with Common Carrier ........................................... 103
4.4.2 Neighboring Cell Configuration in RAN Sharing with Dedicated Carrier ......................................... 116
4.5 Script Preparation for Neighboring Cells in Batches ................................................................................... 116
4.5.1 CME .................................................................................................................................................... 116
4.5.2 EXCEL................................................................................................................................................ 123
4.6 Script Execution in Batches on the M2000 .................................................................................................. 123
2012-03-28

iv

Planning
Guide to LTE Neighboring Cell and X2 Interface Planning

Key words:
LTE, neighboring cell planning, X2 interface planning
Abstract:
This document describes the neighboring cell planning and X2 interface planning, including
four neighboring cell planning solutions, the X2 interface planning solution, planning tools,
and related parameter configuration.
Acronyms and abbreviations:
2012-03-28
Acronym or Abbreviation
Full Name
ANR
automatic neighbor relation
CGI
cell global identifier
GERAN
GSM/EDGE radio access network
LTE
Long Term Evolution
MOCN
multi-operator core network
UTRAN
universal terrestrial radio access network


Planning
1 Neighboring Cell Planning
Neighboring Cell Planning
Neighboring cell planning affects network performance, and therefore it is critical during
radio network planning, especially for the networks requiring quick hard handovers.
Appropriate neighboring cell planning helps enhance LTE network performance. In addition,
LTE protocols define the automatic neighbor relation (ANR) function, and all Huawei LTE
products support ANR.
1.1 Neighboring Cell Planning Principle

To perform the ANR function, both the LTE network and the user equipment (UE) must
support this function. The effect of ANR is obvious when the traffic is heavy. However, most
UEs do not support ANR, and there are a few UEs at the initial deployment stage. Therefore,
the initial neighboring cell configuration must be performed by onsite engineers. In addition,
in the LTE network, handover measurement is performed by frequency, not by neighboring
cell list. After a UE measures cells on the frequency indicated in the measurement
configuration, it processes the measurement result to get a candidate handover cell list, and
then sends the list to the network. The network selects a cell and initiates a handover. The
function of the neighboring cell list is to provide information necessary for handovers, such as
the cell global identifier (CGI). Therefore, the number of neighboring cells does not affect the
measurement time and accuracy, and a large number of neighboring cells are recommended in
the LTE system. The following lists the principles of LTE neighboring cell planning.
2012-03-28
Geographically adjacent cells are used as neighboring cells.
In common scenarios, bidirectional neighboring relationship is configured. For example,

if sector B is the neighboring cell of sector A, sector A is also the neighboring cell of
sector B. In some special scenarios, for example, a UE moves at a high speed,
unidirectional neighboring relationship is configured. To implement a unidirectional
handover from sector A to sector B, you can add sector A to the black list of sector B.
The distance between E-UTRAN NodeBs (eNodeBs) is small (0.3 to 1.0 kilometers) in
urban areas, and therefore a large number of neighboring cells are recommended.
UTRAN refers to universal terrestrial radio access network. Huawei eNodeBs support a
maximum of 32 intra-frequency neighboring cells, 64 inter-frequency neighboring cells,
or 64 inter-RAT (UTRAN, GERAN, or CDMA2000) neighboring cells. GERAN refers
to GSM/EDGE radio access network. When configuring neighboring cells, you must
remove unrelated cells.
The distance between eNodeBs is large in suburban areas, and therefore adjacent cells
must be used as neighboring cells to ensure timely handovers.


Planning
1 Neighboring Cell Planning
The LTE neighboring cells are not in sequence, and the measurement period is short.
Therefore, all neighboring cells must be included. The neighboring cells can be
sequenced by signal strength or not.
If the adjacent cell of a cell in front of a lake, sea, or a wide road is also in front of the
lake, sea, or a wide road, the adjacent cell is configured as its neighboring cell.
1.2 Intra-frequency Neighboring Cell Planning Analysis

Intra-frequency neighboring cells are used for handovers in the LTE system. The eNodeB
sends the RRC Connection Reconfig message to deliver the intra-frequency measurement
configuration when initiates the radio bearer (RB) service. Intra-frequency handover is in a
high priority. In actual planning, possible intra-frequency neighboring cells can be put into the
neighboring cell list. After initiation, the eNodeB optimizes the neighboring cell relationship
based on the UE measurement.
1.3 Inter-frequency Neighboring Cell Planning Analysis

In the LTE system, different frequencies are used for capacity expansion, and therefore
inter-frequency neighboring cells must be configured.
In hierarchical cells, if inter-frequency neighboring cells are configured, the macro cells must
be configured as the inter-frequency neighboring cells of the micro cells.
In multi-frequency networking, possible inter-frequency neighboring cells can be put into the
neighboring cell list. After initiation, the eNodeB optimizes the neighboring cell relationship
based on the UE measurement.
Hierarchical cells: In heavy-traffic areas, micro cells or micro-micro cells are added to overlap with
macro cells to serve more subscribers by taking advantage of geographical areas.
1.4 Inter-RAT Neighboring Cell Planning Analysis

In the early stage or in the process of LTE networking, the Wideband Code Division Multiple
Access (WCDMA) network may coexist with the Global System for Mobile Communications
(GSM), CDMA2000, or Time Division Synchronous Code Division Multiple Access
(TD-SCDMA) network. Therefore, the LTE cell must be configured with inter-RAT
neighboring cells. The cell is configured as a neighboring cell of an inter-RAT cell.
Configuration of different handover parameters ensures continuous coverage and flexible
handovers. To make handovers performed only within the LTE network, add inter-RAT
neighboring cells to the black list.
In the initial deployment of the LTE network, the indoor areas or subways may be covered
only by inter-RAT neighboring cells. These cells must be configured as neighboring cells of
LTE cells to ensure continuous coverage.
2012-03-28


Planning
2 Neighboring Cell Planning Solutions
Neighboring Cell Planning Solutions
Neighboring cell planning includes four solutions: neighboring cell planning based on live
network data, neighboring cell planning using dedicated tools, neighboring cell planning
using pre-planning software, and automatic neighboring cell planning. The LTE neighboring
cell planning does not involve dedicated tools.
2.1 Neighboring Cell Planning Based on Live Network

Data
In actual planning, most operators have networks in other modes, such as the 2G network.
The LTE network usually shares one base station with other networks to reduce the cost. New
eNodeBs are added only in some special scenarios. In this case, the neighboring cell
relationship of previous base stations in other modes can be used to plan the LTE neighboring
cells.
Figure 2-1 shows the neighboring cell planning procedure based on live network data. The 2G
network is used as an example.
2012-03-28


Planning
Figure 2-1 Neighboring cell planning procedure based on live network data
Step 1 Complete the LTE cell planning.

Step 2 Determine whether the LTE cell and the existing 2G cell share the same base station and the
same antenna (or the cells use different antennas, but the antenna engineering parameters are
similar).
If yes, you can get the mapping between the LTE cell ID and the 2G cell ID based on the 2G
cell configuration:
2012-03-28
When the number of LTE cells equals the number of 2G cells, you can get the mapping
between the LTE cell ID and the 2G cell ID directly.


Planning
When the number of LTE cells is greater than the number of 2G cells, you can perform
the neighboring cell planning for the LTE cells without corresponding 2G cells based on
the coverage prediction or drive test result.
If not, you can perform the neighboring cell planning based on the coverage prediction or
drive test result, and get the neighboring cell planning result.
Step 3 Get the neighboring cell list of corresponding 2G cells based on the 2G cell configuration.
Step 4 Convert the 2G neighboring cell list to the LTE cell list based on the mapping between the
LTE cell ID and the 2G cell ID. Because the LTE cell list includes both intra-frequency cells
and inter-frequency cells, you need to perform the following actions:
If an intra-frequency neighboring cell list is required, remove all inter-frequency

neighboring cells.
If an inter-frequency neighboring cell list is required, remove all intra-frequency

neighboring cells.
If an inter-RAT neighboring cell list is required, configure all 2G neighboring cells as

inter-RAT neighboring cells. Then, get the initial LTE neighboring cell planning result.
Step 5 If a new eNodeB is deployed around or the coeNodeB cells cannot use the existing
neighboring cell data, configure neighboring cell relationships for these cells.
Step 6 If there are more than 32 initial neighboring cells, remove the neighboring cells that have few
handovers to the host cell based on the 2G cell handover data to ensure the number of
neighboring cells is not more than 32.
Following these steps, you can get the planning results of intra-frequency neighboring cells,
inter-frequency neighboring cells, and inter-RAT neighboring cells.
The 2G neighboring cell relationship can be converted to the LTE neighboring cell relationship
according to the following procedure:
a)
Open the neighboring cell relationship database and export the data of 2G neighboring cell
relationship to an .xls file.
b)
Replace the 2G cell ID with the corresponding LTE cell ID to get the initial LTE neighboring cell
relationship.
c)
Filter the intra-frequency, inter-frequency, or inter-RAT neighboring cells.
The bidirectional neighboring cell relationship must be configured for the following cells:
Cells of new eNodeBs
Co-eNodeB cells that cannot use the existing neighboring cell data
This neighboring cell planning solution applies to scenarios where new eNodeBs are deployed. If a
large number of cells do not share a base station, another neighboring cell planning solution is
needed, which makes the planning complicated. In this case, other neighboring cell planning
solutions are recommended.
2.2 Neighboring Cell Planning Using Dedicated Tools

Neighboring cell planning is performed using dedicated tools based on the following items:
2012-03-28
Engineering parameter table
Digital map
Cell coverage
Terrain feature


Planning
Propagation model
Neighboring planning algorithm
This solution applies to initial neighboring cell planning at the initial deployment stage. The
initial neighboring cell plan is optimized and adjusted based on the network performance in
following days.
The terrain feature information and the propagation model in the 3D digital map facilitate the
neighboring cell planning. Currently, Huawei uses the U-Net tool to plan neighboring cells.
The U-Net supports automatic neighboring cell planning. In addition, it also supports the
neighboring cell planning in scenarios where the repeater or remote radio unit (RRU) is used.
This ensures the planning reliability.
The U-Net plans the neighboring cells based on the following principles:
The cells that are served by the same eNodeB with the local cell are configured as the
neighboring cells of the local cell.
The candidate neighboring cells that have high scores are configured as the neighboring
cells of the local cell.
The existing neighboring cell relationship is reserved.
The bidirectional neighboring cell relationship is configured.
The U-Net neighboring cell planning is based on the topology or coverage prediction, or both
of them.
Neighboring cell planning algorithm based on the coverage prediction
Divide the space around the base station into multiple areas, forming a coverage matrix.
Calculate the counters at the matrix node, and plan neighboring cell relationship based on the
sequence of the counters.
Neighboring cell planning algorithm based on the topology
Use the cell to be planned as the center, calculate the angel and distance between the cell to be
planned and the candidate cells, and then plan the neighboring cell relationship.
Neighboring cell planning algorithm based on the coverage prediction and topology
Plan neighboring cell relationships based on the coverage prediction. If the neighboring cells
cannot be planned based on coverage prediction, plan neighboring cell relationships based on
the topology.
Neighboring cell planning using the GENEX U-Net V300R007C00SPC200 is used as an
example. The U-Net is used in following modes:
Code Division Multiple Access (CDMA), GSM, Universal Mobile Telecommunications

System (UMTS), LTE-TDD, or LTE-FDD
Co-eNodeB GSM, UMTS, and LTE-FDD
The CDMA or LTE-TDD mode supports only single-mode neighboring cell planning.
2.2.1 U-Net Neighboring Cell Planning Procedure

1.
Collecting data
1)
Digital map
The digital map is mandatory if the neighboring cell planning is to be performed based on the
coverage prediction. The digital map includes the terrain feature information about the site
2012-03-28


Planning
area, and provides the information about the wave transmission environment for the coverage
prediction. By setting a proper transmission mode, you can predict the path loss, and then
prepare the coverage prediction map and the neighboring cell planning result.
2)
Engineering parameter table
The engineering parameter table includes the base station geographic distribution information,
including the site latitude and longitude, antenna height, angel, and antenna length, which
affect the coverage and the handover area.
The digital map is not mandatory. If no digital map is available, you can import an engineering
parameter table to the U-Net, and perform prediction based on the site position, azimuth, tilt, and
antenna installation height. The engineering parameter table is not dedicated for the neighboring cell
planning. If the planning is not based on the digital map, the planning result is not accurate.
2.
Importing the new engineering and basic information
For details, see the Guide to U-Net-based LTE Simulation Operations.

3.
Automatic Neighboring Cell Planning
The following lists the procedure of automatic neighboring cell planning by using the U-Net.
2012-03-28
1)
Select the Operation tab in the browser window.
2)
Choose Neighbor Planning > LTE. Select Neighbor Automatic Allocation in the
shortcut menu. The LTE Neighbor Plan Setting is displayed, as shown in Figure 2-2.


Planning
Figure 2-2 LTE neighboring cell planning
3)
2012-03-28
Configure parameters in the General tab. Table 2-1 lists the parameters to be configured.


Planning
Table 2-1 Parameters for neighboring cell planning in the General tab
Parameter Name
Description
Methods Select
The following modes can be used for network

planning.
Default Value
Topology: The topology mode is selected for

neighboring cell planning.
Prediction: The coverage prediction mode is
selected for neighboring cell planning.
This mode applies only to outdoor base
stations.
Topology + Prediction: The topology +
prediction mode is selected for neighboring
cell planning.
This mode applies only to outdoor base
stations.
Max Neighbor
Distance
The maximum cell coverage radius is 40 km,

affecting the network planning speed. The
cells outside of the coverage are not planned
as neighboring cells.
Planning Neighbour
based on existed
neighbours
This parameter applies to ikebana-like

expansion scenario in the neighboring cell
planning of new eNodeBs.
Force Co-Site As
Neighbor
If this parameter is selected, co-site cells are

forcibly configured as neighboring cells.
Co-Site Distance(m)
If the distance between cells to be planned is

smaller than this parameter value, the
bidirectional neighboring relationship is
configured for the cells.
Force Using Co-site

2G/3G Neighbor for
Reference
This parameter indicates whether to use the

existing 2G/3G neighboring relationships as
reference for planning the neighboring cell
relationships on LTE networks.
Azimuth Difference
()
This parameter indicates the azimuth

difference between the cells to be planned and
the cells used for reference.
Min Signal
Level(dBm)
This parameter indicates the minimal signal

receive level.
-110 dBm
30 m
This parameter is valid when the neighboring

cell planning is based on coverage prediction.
Handover
Threshold(dB)
This parameter indicates the handover area

threshold.
6 dB

2012-03-28


Planning
Parameter Name
Description
Default Value
Handover Area
Percent(%)
This parameter indicates the handover area

proportion.
0.00

Compute Shadowing
This parameter indicates whether

shadow-fading margin is considered in the
calculation.
Cell Edge Coverage

Probability(%)
This parameter indicates the probability of the

cell edge coverage.
75%
This parameter is valid when shadow fading is

considered. If this parameter value is large,
the shadow fading value is large.
Compute Indoor Loss
If this parameter is selected, the penetration

loss is considered in the calculation.
This parameter indicates the planning area.
You can select any required areas or all areas
in the full map for neighboring cell planning.
Area
All Map
You can click Filter to select the cells

requiring neighboring cell configuration
manually.
Filter can memorize the cells that are planned
last time. Before planning neighboring cells,
verify that no cells are missed.
4)
Configure parameters in the Intra-Frequency tab. Table 2-2 lists the parameters to be
configured.
Table 2-2 Neighboring cell parameter setting in the Intra Frequency tab
Parameter Name
Description
Default Value
Max Neighbor
Number of Indoor
Cell
This parameter indicates the maximum

number of indoor intra-frequency
neighboring cells.
20
This parameter is valid when the

neighboring cell planning is based on the
topology mode.
2012-03-28

10

Planning
Parameter Name
Description
Default Value
Max Neighbor
Number of Outdoor
Cell

number of outdoor intra-frequency
neighboring cells.
20
Force Symmetry
This parameter indicates whether to

configure cells as bidirectional neighboring
cells forcibly.
If this parameter is selected in the capacity
expansion scenario, the previous
neighboring relation table is modified, and
the unidirectional neighboring relationship
is configured to bidirectional neighboring
relationship.
5)
Configure parameters in the Inter-Frequency tab. Table 2-3 lists the parameters to be
configured.
Table 2-3 Neighboring cell parameter setting in the Inter Frequency tab
Parameter Name
Description
Default Value
Max Neighbor Number of

Indoor Cell

number of indoor inter-frequency
neighboring cells.
20
This parameter is valid when the

neighboring cell planning is based on the
topology mode.
Max Neighbor Number of
Outdoor Cell

number of outdoor inter-frequency
neighboring cells.
Force Symmetry
This parameter indicates whether to

configure cells as bidirectional
neighboring cells forcibly.
20
If this parameter is selected in the capacity

expansion scenario, the previous
neighboring relation table is modified, and
the unidirectional neighboring relationship
is configured to bidirectional neighboring
relationship.
6)
2012-03-28
After setting parameters, click Run to plan neighboring cells. After planning the
neighboring cells, LTE Neighbor Display is displayed.

11

Planning
Figure 2-3 LTE neighboring cell planning results
7)
Follow-up procedure
Apply the neighboring cell planning result to each cell.
Right-click and choose Commit All in the LTE Neighbor Display window, apply the
neighboring cell planning results to each cell. Then, the new neighboring cell relationship
replaces the previous neighboring cell relationship and is saved in the U-Net system.
Export the neighboring cell planning result. Click Export in the LTE Neighbor Display.
The neighboring cell planning result is exported. The incremental export is to export
only the changed results after planning, which mainly applies to the ikebana-like
expansion scenarios. The full export is to export all planning results, and the full export
is used in most cases.
Remove neighboring cell relationships
Select cells that require neighboring cell relationship adjustment in the Cell area in the LTE
Neighbor Display dialog box. Clear Confirm in the right list corresponding to the cell.
2012-03-28
Modify the neighboring cell relationship.
a)
Select the host cell on the map.
b)
Press Ctrl and click other cells except the host cell, add or remove unidirectional
neighboring cell relationships.

12

Planning
c)
4.
Press Shift and click other cells except the host cell, add or remove bidirectional
neighboring cell relationships.
If a newly added neighboring cell relationship exists, change the Confirm status according to the
addition or deletion.
If a newly added neighboring cell relationship is not included in the existing neighboring cell
relationship, add new neighboring cell relationships. The Case list displays force.
Manual Neighboring Cell Planning
The manual neighboring cell planning can be performed in two methods:
Perform manual neighboring cell planning directly.
Perform automatic neighboring cell planning first, and then perform manual neighboring
cell planning to modify improper neighboring cells.
Before using the U-Net to plan neighboring cells manually, you must create an LTE project
file, and collect related data.
1)
Select cells to be planned.
a)
In the Network tab, right-click Transceiver and choose the cells to be planned. Select
Properties. The Transceiver Properties dialog box is displayed.
b)
Select the LTE Cell tab.
2)
Click the cell on the right side of the Neighbors list in the LTE Cell tab. The Neighbors
dialog box is displayed.
3)
Configure neighboring cell relationships.
a)
Configure intra-frequency neighboring cells in the Intra-frequency Neighbors dialog

box.
b)
Configure inter-frequency neighboring cells in the Inter-frequency Neighbors dialog

box.
c)
Configure inter-RAT neighboring cells in the Inter-technology Neighbors dialog box.
4)
After the configuration, click OK.
2.3 System Automatic Planning

In radio networks, the number of network elements (NEs) increases and the structure becomes
more complicated. Based on the self-organization network (SON), Huawei LTE products in
eRAN2.0 and later versions support ANR. The ANR function is to use UE measurement to
detect cells lack of neighboring cell relationship, which applies to the network with a large
number of UEs.
There are a few UEs at the initial deployment stage, and most UEs do not support ANR.
Therefore, the neighboring cell planning using tools is recommended.
2012-03-28

13

Planning
3 X2 Interface Planning
X2 Interface Planning
Based on the neighboring cell relationship, the X2 interface planning configures an X2 link
between two eNodeBs with handover relationships. An eNodeB can be configured with a
maximum of 32 X2 links, and the X2 link is bidirectional.
The X2 interface links two eNodeBs. Therefore, the eNodeB neighboring relation table is
provided by the network planners based on the neighboring cell relationships. The engineers
on the RAN side configure X2 links according to the following table.
Table 3-1 X2 interfaces between eNodeBs
Central eNodeB
2012-03-28
Neighbor eNodeB
Site name
eNodeB ID
Neighbor site name
eNodeB ID
eNB1_AKH227
101227
eNB1_AKH051
101051
eNB1_OSL246
100246
eNB1_OSL132
100132
eNB1_OSL246
100246
eNB1_OSL014
100014
eNB1_OSL049
100049
eNB1_OSL106
100106
eNB1_OSL313
100313
eNB1_OSL374
100374
eNB1_OSL140
100140
eNB1_OSL374
100374
eNB1_OSL374
100374
eNB1_OSL003
100003
eNB1_OSL037
100037
eNB1_OSL110
100110
eNB1_OSL132
100132
eNB1_OSL246
100246
eNB1_OSL014
100014
eNB1_OSL246
100246
eNB1_OSL106
100106
eNB1_OSL049
100049
eNB1_OSL374
100374
eNB1_OSL313
100313
eNB1_OSL374
100374
eNB1_OSL140
100140
eNB1_OSL003
100003
eNB1_OSL374
100374
eNB1_OSL110
100110
eNB1_OSL037
100037

14

Planning
3 X2 Interface Planning
In the N4M site, X2INTERFACEID, X2SCTPLINKID, SCTPNO, PATHID, and ANI use
numbers from 0 to 47 as the ID numbers. Parameters with ID numbers from 0 to 15 are
reserved for the core network, and those with ID numbers from 16 to 47 are reserved for the
X2 interface.
The X2 interface configuration is bidirectional, and therefore you must check the X2
relationships that are obtained from the neighboring cell list. If there is unidirectional X2
relationship, you must change it to bidirectional relationship. Then, use ID Get v1.0.xls to
extract the IDs. For details about the ID Get v1.0.xls, refer to the following website:
http://support.huawei.com/support/pages/kbcenter/view/product.do?actionFlag=detailCaseDo
c&web_doc_id=SC0000617191&doc_type=CaseDoc
2012-03-28

15

Planning
4 Script Preparation and Batch Processing
Script Preparation and Batch Processing
4.1 Script Preparation for Intra-Frequency Neighboring

Cells
Figure 4-1 shows the procedure for configuring an intra-frequency neighboring cell.
Figure 4-1 Procedure for configuring an intra-frequency neighboring cell
Configure an intra-frequency neighboring cell as follows:
2012-03-28
1.
Ensure that the following conditions are met before preparing scripts for intra-frequency
neighboring cells:
a)
The engineering parameter table is prepared based on the template (see the attachment in
section 4.5.1 CME) and the parameters in the table are complete and correct.
b)
Neighboring cell planning is completed, and the planning results are in the format as
shown in the following figure.

16

Planning
2.
In the neighboring cell configuration, LocalCellID for the local cell is used to search for CellID for
the neighboring cell. However, for tool-based neighboring cell configuration, CellID for the local
cell is used to search for CellID for the neighboring cell. To avoid confusion, the value of
LocalCellID is the same as that of CellID in actual planning.
NSiteName indicates the site name of a neighboring cell. N is short for neighbor, which has the
same meaning in NeNBID, NCellID, NPCI, and NTAC. The neighboring cell physical cell
identifier (PCI) and tracking area code (TAC) are provided because the information is necessary
when the neighboring cells of different eNodeBs are configured with external cells. When a local
cell and its intra-frequency neighboring cells are served by different eNodeBs, the corresponding
external evolved universal terrestrial radio access network (E-UTRAN) cells must be configured in
advance.
The downlink (DL) frequency of an external cell required by E-UTRAN intra-frequency

neighboring cells are the same as that of the local cells.
Each cell can be configured with a maximum of 32 E-UTRAN intra-frequency neighboring cells.
The PCI of an external cell that required by intra-frequency neighboring cells must be different from
that of the local cell.
Add an intra-eNodeB neighboring cell by running the following command:
ADD EUTRANINTRAFREQNCELL: LOCALCELLID=0, MCC="xxx", MNC="xx",

ENODEBID=101044, CELLID=1
Parameters in the command must be provided, and other parameters listed in Table 4-1 use
default values. Table 4-1 lists related parameters of intra-frequency neighboring cells.
Modify the configuration of intra-frequency neighboring cells by running MOD
EUTRANINTRAFREQNCELL.
Remove intra-frequency neighboring cells by running RMV
EUTRANINTRAFREQNCELL.
Query intra-frequency neighboring cells by running LST EUTRANINTRAFREQNCELL.
Table 4-1 Intra-frequency neighboring cell parameters
ID
Name
Description
LocalCellId
Local cell ID
Meaning: Indicates the cell ID of the local cell. It

uniquely identifies a cell within an eNodeB.
GUI Value Range: 0~17
Unit: None
Actual Value Range: 0~17
MML Default Value: None
Recommended Value: None
Parameter Relationship: None
Service Interrupted After Modification: Not involved
Impact on Radio Network Performance: None
Mcc
Mobile
country code
Meaning: Indicates the mobile country code of the

E-UTRAN neighboring cell.
The PLMN consists of the MCC and the MNC.
The MCC consists of three digits.
The MNC consists of two to three digits.
2012-03-28

17

Planning
ID
Name
Description
For example, MCC = 123, MNC = 45, PLMN = 12345.
GUI Value Range: 3 characters
Unit: None
Mnc
Mobile
network code
Meaning: Indicates the mobile network code of the

GUI Value Range: 2~3 characters
Unit: None
Actual Value Range: 00~99,000~999
eNodeBId
eNodeB ID
Meaning: Indicates the eNodeB identity of the

intra-frequency neighboring cell. It uniquely identifies an
eNodeB within a PLMN. The 28-bit E-UTRAN cell
identity is comprised of the cell identity and the eNodeB
identity (represented by the most significant 20 bits). The
cell global identity (CGI) of an E-UTRAN cell is
comprised of the E-UTRAN cell identity and the PLMN
ID. For details, see 3GPP TS 36.413.
Unit: None
CellId
2012-03-28
Cell ID
Meaning: Indicates the local identity of the

intra-frequency neighboring cell. It uniquely identifies a
cell within an eNodeB. The 28-bit E-UTRAN cell

18

Planning
ID
Name
Description
identity is comprised of the cell identity (represented by
the least significant eight bits) and the eNodeB identity.
The cell global identity (CGI) of an E-UTRAN cell is
Unit: None
CellIndividua
lOffset
Cell
individual
offset
Meaning: Indicates the cell-specific offset for the

intra-frequency neighboring cell. It affects the probability
of triggering intra-frequency measurement reports. A
larger value of this parameter indicates a higher
probability. For details, see 3GPP TS 36.331.
GUI Value Range: dB-24(-24dB), dB-22(-22dB),
dB-20(-20dB), dB-18(-18dB), dB-16(-16dB),
dB-14(-14dB), dB-12(-12dB), dB-10(-10dB),
dB-8(-8dB), dB-6(-6dB), dB-5(-5dB), dB-4(-4dB),
dB-3(-3dB), dB-2(-2dB), dB-1(-1dB), dB0(0dB),
dB1(1dB), dB2(2dB), dB3(3dB), dB4(4dB), dB5(5dB),
dB6(6dB), dB8(8dB), dB10(10dB), dB12(12dB),
dB22(22dB), dB24(24dB)
Unit: dB
Actual Value Range: dB-24, dB-22, dB-20, dB-18,
dB-16, dB-14, dB-12, dB-10, dB-8, dB-6, dB-5, dB-4,
dB-3, dB-2, dB-1, dB0, dB1, dB2, dB3, dB4, dB5, dB6,
dB8, dB10, dB12, dB14, dB16, dB18, dB20, dB22, dB24
MML Default Value: dB0(0dB)
Recommended Value: dB0(0dB)
Parameter Relationship: The smaller the value of this
parameter, the less probable that the UE camps on the
neighboring cell during reselection. The larger the value
of this parameter, the more probable that the UE camps
on the neighboring cell.
Service Interrupted After Modification: No (And no
impact on the UE in idle mode)
Impact on Radio Network Performance: A larger value of
this parameter leads to a higher probability of triggering
event A3 and handover. A smaller value of this parameter
leads to a lower probability.
CellQoffset
2012-03-28
Cell offset
Meaning: Indicates the cell specific offset between the

serving cell and the intra-frequency neighboring cell. A

19

Planning
ID
Name
Description
larger the value of this parameter results in a lower
probability of cell reselections. This parameter is
contained in SIB4. For details, see 3GPP TS 36.331.
dB-20(-20dB), dB-18(-18dB), dB-16(-16dB),
dB-14(-14dB), dB-12(-12dB), dB-10(-10dB),
dB22(22dB), dB24(24dB)
Unit: dB
dB8, dB10, dB12, dB14, dB16, dB18, dB20, dB22, dB24
Impact on Radio Network Performance: Increasing the
value of this parameter causes the cell edge to move
towards the neighboring cell, which leads to a lower
probability of cell reselection to the neighboring cell.
Decreasing the value of this parameter leads to an
opposite effect.
NoHoFlag
No handover
indicator
Meaning: Indicates whether handovers of UEs to the

neighboring cell are prohibited.
GUI Value Range: PERMIT_HO_ENUM(Permit Ho),
FORBID_HO_ENUM(Forbid Ho)
Unit: None
Actual Value Range: PERMIT_HO_ENUM,
FORBID_HO_ENUM
MML Default Value: PERMIT_HO_ENUM(Permit Ho)
Recommended Value: PERMIT_HO_ENUM(Permit Ho)
NoRmvFlag
No remove
indicator
Meaning: Indicates whether to permit or prohibit removal

of the neighboring relationship by ANR.
GUI Value Range: PERMIT_RMV_ENUM(Permit ANR
Remove), FORBID_RMV_ENUM(Forbid ANR
Remove)
2012-03-28

20

Planning
ID
Name
Description
Unit: None
Actual Value Range: PERMIT_RMV_ENUM,
FORBID_RMV_ENUM
MML Default Value: PERMIT_RMV_ENUM(Permit
ANR Remove)
Recommended Value: PERMIT_RMV_ENUM(Permit
ANR Remove)
LocalCellNa
me
Local cell
name
Meaning: Indicates the name of the local cell.

Unit: None
Actual Value Range: 0~99 characters
Parameter Relationship: In the EutranIntraFreqNCell
MO, the value of LocalCellName is a string of a
maximum of 99 characters. The string cannot be all null
characters or contain any of the following
characters:double quotation marks ("), commas (,),
semicolons (;), equal signs (=), single quotation marks ('),
three consecutive plus signs (+++), two or more
consecutive blanks, and two or more consecutive
percentage signs (%).
NeighbourCel
lName
Neighbour
cell name
Meaning: Indicates the name of the intra-frequency

neighboring E-UTRAN cell. The name is a string of a
characters or contain any of the following characters:
double quotation marks ("), commas (,), semicolons (;),
equal signs (=), single quotation marks ('), three
consecutive plus signs (+++), two or more consecutive
blanks, and two or more consecutive percentage signs
(%).
Unit: None
Parameter Relationship: In the EutranIntraFreqNCell
MO, the value of NeighbourCellName is a string of a
2012-03-28

21

Planning
ID
Name
Description
characters or contain any of the following characters:
double quotation marks ("), commas (,), semicolons (;),
equal signs (=), single quotation marks ('), three
consecutive plus signs (+++), two or more consecutive
blanks, and two or more consecutive percentage signs
(%).
3.
Add an intra-eNodeB neighboring cell.
a)
Add an external cell by running the following command:
ADD EUTRANEXTERNALCELL: MCC="xxx", MNC="xx", ENODEBID=100106,

CELLID=1, DLEARFCN=2850, ULEARFCNCFGIND=NOT_CFG, PHYCELLID=55,
TAC=2603
default values. Table 4-2 lists related parameters.
Each cell can be configured with a maximum of 1152 external E-UTRAN cells.
Table 4-2 Parameters for adding an external cell to an intra-frequency neighboring cell
ID
Name
Description
Mcc
Mobile
country
code
Meaning: Indicates the mobile country code of the external

E-UTRAN cell.
Unit: None
Mnc
Mobile
network
code
Meaning: Indicates the mobile network code of the external

E-UTRAN cell.
2012-03-28

22

Planning
ID
Name
Description
Unit: None
eNodeBId
eNodeB ID
Meaning: Indicates the eNodeB identity of the external

E-UTRAN cell. It uniquely identifies an eNodeB within a
PLMN. The 28-bit E-UTRAN cell identity is comprised of the
cell identity and the eNodeB identity (represented by the most
significant 20 bits). The cell global identity (CGI) of an
E-UTRAN cell is comprised of the E-UTRAN cell identity and
the PLMN ID. For details, see 3GPP TS 36.413.
Unit: None
CellId
Cell ID
Meaning: Indicates the cell identity of the external E-UTRAN

cell. It uniquely identifies a cell within an eNodeB. The 28-bit
E-UTRAN cell identity is comprised of the cell identity
(represented by the least significant eight bits) and the eNodeB
identity. The cell global identity (CGI) of an E-UTRAN cell is
comprised of the E-UTRAN cell identity and the PLMN ID.
For details, see 3GPP TS 36.413.
Unit: None
DlEarfcn
2012-03-28
Downlink
EARFCN
Meaning: Indicates the DL EARFCN of the external

E-UTRAN cell. The DL EARFCN is calculated by using the

23

Planning
ID
Name
Description
following formula:
DL carrier frequency (MHz) = Lowest frequency of the DL
operating band + 0.1 x (DL EARFCN - Offset used to
calculate the DL EARFCN). For example, if the DL EARFCN
is 3100 in band 7 for a cell, the DL carrier frequency of the
cell is calculated as 2620 + 0.1 x (3100 - 2750) = 2655 MHz.
Band 1: DL EARFCN range: 0 to 599, lowest frequency of the
DL operating band: 2110;
Band 2: DL EARFCN range: 600 to 1199, lowest frequency of
the DL operating band: 1930;
Band 3: DL EARFCN range: 1200 to 1949, lowest frequency
of the DL operating band: 1805;
of the DL operating band: 1844.9;
Band 32: DL EARFCN range: 17950 to 17999, lowest
frequency of the DL operating band: 1990;
2012-03-28

24

Planning
ID
Name
Description
Among the preceding bands, band 1 to band 32 are FDD
bands, and other bands are TDD bands. In addition, band 32
and band 64 are non-protocol-defined bands, and band 11 and
band 13 are different from protocol-defined bands. For details,
see 3GPP TS 36.104.
GUI Value Range: 0~45589,64436~65535
Unit: None
Service Interrupted After Modification: No (And no impact on
the UE in idle mode)
UlEarfcnC
fgInd
Uplink
EARFCN
indicator
Meaning: Indicates whether to set the UL EARFCN for the

external E-UTRAN cell. If this parameter is set to NOT_CFG,
the UL EARFCN is the DL EARFCN plus 18000 in FDD
mode and is the same as the DL EARFCN in TDD mode.
GUI Value Range: NOT_CFG(Not configure),
CFG(Configure)
Unit: None
2012-03-28

25

Planning
ID
Name
Description
Actual Value Range: NOT_CFG, CFG
MML Default Value: NOT_CFG(Not configure)
Recommended Value: NOT_CFG(Not configure)
UlEarfcn
Uplink
EARFCN
Meaning: Indicates the UL EARFCN of the external

E-UTRAN cell. For an FDD cell, if no UL EARFCN is
configured, the UL EARFCN equals the sum of the DL
EARFCN and 18000. For a TDD cell, the UL EARFCN is
calculated by using the following formula:
UL carrier frequency (MHz) = Lowest frequency of the UL
operating band + 0.1 x (UL EARFCN - Offset used to
calculate the UL EARFCN). For example, if the UL EARFCN
is 21100 in band 7 for a cell, the UL carrier frequency of the
cell is calculated as 2500 + 0.1 x (21100 - 20750) = 2535
MHz.
Band 1: UL EARFCN range: 18000 to 18599, lowest
frequency of the UL operating band: 1920;
frequency of the UL operating band: 1749.9;
2012-03-28

26

Planning
ID
Name
Description
Among the preceding bands, band 1 to band 32 are FDD
bands, and other bands are TDD bands. In addition, band 32
and band 64 are non-protocol-defined bands, and band 11 and
band 13 are different from protocol-defined bands. For details,
see 3GPP TS 36.104.
GUI Value Range: 18000~45589,64436~65535
Unit: None
MML Default Value: 18000
2012-03-28

27

Planning
ID
Name
Description
PhyCellId
Physical
cell ID
Meaning: Indicates the physical cell ID of the external

E-UTRAN cell. For details, see 3GPP TS 36.331.
Unit: None
Tac
Tracking
area code
Meaning: Indicates the tracking area code (TAC) of the

external E-UTRAN cell. Two TAC values 0x0000(0) and
0xFFFE(65534) are reserved according to the protocol and
will not be used in future versions. Therefore, do not use 0 or
65534 as a TAC value in TAC planning or configuration.
Unit: None
CellName
Cell name
Meaning: Indicates the name of the external E-UTRAN cell.

Unit: None
Parameter Relationship: In the EutranExternalCell MO, the
value of CellName is a string of a maximum of 99 characters.
The string cannot be all null characters or contain any of the
following characters:double quotation marks ("), commas (,),
three consecutive plus signs (+++), two or more consecutive
2012-03-28

28

Planning
ID
Name
Description
blanks, and two or more consecutive percentage signs (%).
b)
Add neighboring cells by running commands that used for adding intra-eNodeB
neighboring cells.
4.2 Script Preparation for Inter-Frequency Neighboring

Cells
Figure 4-2 shows the procedure for configuring an inter-frequency neighboring cell.
Figure 4-2 Procedure for configuring an inter-frequency neighboring cell
Configure an inter-frequency neighboring cell as follows:

1.
Add an inter-frequency neighboring frequency by running the following command:
ADD EUTRANINTERNFREQ: LocalCellId=0, DlEarfcn=2850, UlEarfcnCfgInd=CFG,

UlEarfcn=20850,CellReselPriorityCfgInd=CFG,CellReselPriority=3,SpeedDependSPCfg
Ind=CFG,TReselEutranSfMedium=0DOT5_ENUM,TReselEutranSfHigh=0DOT75_EN
2012-03-28

29

Planning
UM, MeasBandwidth=MBW75, QoffsetFreq=dB3, ThreshXhigh=2, ThreshXlow=30,

QRxlevmin=-63, PmaxCfgInd=CFG, Pmax=1,
PresenceAntennaPort1=BOOLEAN_TRUE
The DL frequency of an E-UTRAN inter-frequency neighboring cell must be different from the DL
frequency of a local cell.
Each cell can be configured with a maximum of 8 E-UTRAN inter-frequency neighboring

frequencies.
Table 4-3 Inter-frequency neighboring cell parameters

ID
Name
Description
LocalCellId
Local cell ID

Unit: None
DlEarfcn
Downlink
EARFCN
Meaning: Indicates the DL EARFCN of the neighboring

cell on the neighboring E-UTRAN frequency. The DL
EARFCN is calculated by using the following formula:
DL carrier frequency (MHz) = Lowest frequency of the
DL operating band + 0.1 x (DL EARFCN - Offset used
to calculate the DL EARFCN). For example, if the DL
EARFCN is 3100 in band 7 for a cell, the DL carrier
frequency of the cell is calculated as 2620 + 0.1 x (3100
- 2750) = 2655 MHz.
2012-03-28

30

Planning
ID
Name
Description
frequency of the DL operating band: 1844.9;
2012-03-28

31

Planning
ID
Name
Description
Among the preceding bands, band 1 to band 32 are
FDD bands, and other bands are TDD bands. In
addition, band 32 and band 64 are non-protocol-defined
bands, and band 11 and band 13 are different from
protocol-defined bands. For details, see 3GPP TS
36.104.
GUI Value Range: 0~45589,64436~65535
Unit: None
UlEarfcnCfgI
nd
Uplink
EARFCN
configure
indicator
Meaning: Indicates whether to set the UL EARFCN. If

this parameter is set to NOT_CFG, the UL EARFCN is
the DL EARFCN plus 18000 in FDD mode and is the
same as the DL EARFCN in TDD mode.
CFG(Configure)
Unit: None
UlEarfcn
Uplink
EARFCN
Meaning: Indicates the UL EARFCN of the neighboring

cell on the neighboring E-UTRAN frequency. For an
FDD cell, if no UL EARFCN is configured, the UL
EARFCN equals the sum of the DL EARFCN and
18000. For a TDD cell, the UL EARFCN is calculated
by using the following formula:
UL carrier frequency (MHz) = Lowest frequency of the
UL operating band + 0.1 x (UL EARFCN - Offset used
to calculate the UL EARFCN). For example, if the UL
EARFCN is 21100 in band 7 for a cell, the UL carrier
frequency of the cell is calculated as 2500 + 0.1 x
(21100 - 20750) = 2535 MHz.
2012-03-28

32

Planning
ID
Name
Description
2012-03-28

33

Planning
ID
Name
Description
Among the preceding bands, band 1 to band 32 are
FDD bands, and other bands are TDD bands. In
addition, band 32 and band 64 are non-protocol-defined
bands, and band 11 and band 13 are different from
protocol-defined bands. For details, see 3GPP TS
36.104.
GUI Value Range: 18000~45589,64436~65535
Unit: None
CellReselPrio
rityCfgInd
Inter frequency
cell resel
priority
configure
indicator
Meaning: Indicates whether to set the reselection

priority of the neighboring E-UTRAN frequency. If the
value of this parameter is not specified, the UE does not
reselect to neighboring cells on the frequency.
CFG(Configure)
Unit: None
Service Interrupted After Modification: No
(Modifications on this parameter would affect cell
2012-03-28

34

Planning
ID
Name
Description
reselection of the UE in idle mode.)
CellReselPrio
rity
Inter frequency
cell resel
priority
Meaning: Indicates the cell reselection priority of the

neighboring E-UTRAN frequency. It is contained in
system information block type 5 (SIB5).
The UE decides whether to reselect a neighboring cell
on the frequency based on the value of this parameter
and the absolute priority of the serving cell.
If the value of this parameter is larger than the absolute
priority of the serving cell, the UE starts measurements
on neighboring cells on the frequency; then if the signal
quality of some neighboring cells meets the related
conditions, the UE starts cell reselection.
If the value of this parameter is smaller than the
absolute priority of the serving cell, the UE starts the
measurements only when the signal quality of the
serving cell is poor; then if the signal quality of some
neighboring cells meets the related conditions, the UE
starts cell reselection. Frequencies used for different
RATs must be assigned different cell reselection
priorities. For details, see 3GPP TS 36.331.
Unit: None
Recommended Value: 1
Parameter Relationship: If CellReselPriorityCfgInd is
set to CFG, CellReselPriority must be set.
Impact on Radio Network Performance: A larger value
of this parameter leads to a higher probability of starting
measurements on cells on the neighboring E-UTRAN
frequency and also a higher probability of reselection to
a cell on the frequency.
EutranReselT
ime
EUTRAN
reselection time
Meaning: Indicates the time threshold for

inter-frequency cell reselection. A UE initiates a
reselection to the inter-frequency neighboring cell only
after the signal quality in the cell is better than that in
the serving cell for a period defined by this parameter
and, in addition, after the UE camps on the serving cell
for longer than 1s. This parameter is contained in SIB5.
Unit: s
2012-03-28

35

Planning
ID
Name
Description
SpeedDepend
SPCfgInd
Speed
dependent resel
parameter
configuring
indicator
Meaning: Indicates whether to set the speed-dependent

scaling parameters related to cell reselection.
If this parameter is set to NOT_CFG, speed-dependent
cell reselections are not supported by default.
CFG(Configure)
Unit: None
TReselEutran
SfMedium
Scaling factor
of treseleutra in
medium
mobility state
Meaning: Indicates the scaling factor applied to the cell

reselection duration for medium-mobility UEs. This
parameter is delivered in SIB5. For details, see 3GPP
TS 36.331.
GUI Value Range: 0DOT25_ENUM(0.25),
0DOT5_ENUM(0.5), 0DOT75_ENUM(0.75),
1DOT0_ENUM(1.0)
Unit: None
Actual Value Range: 0DOT25_ENUM,
0DOT5_ENUM, 0DOT75_ENUM, 1DOT0_ENUM
MML Default Value: 0DOT25_ENUM(0.25)
Parameter Relationship: If SpeedDependSPCfgInd is set
to CFG, TReselEutranSfMedium must be set.
Impact on Radio Network Performance: A smaller
value of this parameter results in a greater impact of the
UE mobility state on the cell reselection duration within
E-UTRAN, that is, results in a shorter duration. A larger
value leads to a smaller impact.
TReselEutran
2012-03-28
Scaling factor
Meaning: Indicates the scaling factor applied to the cell

36

Planning
ID
Name
Description
SfHigh
of treseleutra in
high mobility
state
reselection duration for high-mobility UEs. This

parameter is delivered in SIB5. For details, see 3GPP
TS 36.331.
GUI Value Range: 0DOT25_ENUM(0.25),
0DOT5_ENUM(0.5), 0DOT75_ENUM(0.75),
1DOT0_ENUM(1.0)
Unit: None
Actual Value Range: 0DOT25_ENUM,
0DOT5_ENUM, 0DOT75_ENUM, 1DOT0_ENUM
MML Default Value: 0DOT25_ENUM(0.25)
Parameter Relationship: If SpeedDependSPCfgInd is set
to CFG, TReselEutranSfHigh must be set.
Impact on Radio Network Performance: A smaller
value of this parameter results in a greater impact of the
UE mobility state on the cell reselection duration within
E-UTRAN, that is, results in a shorter duration. A larger
value leads to a smaller impact.
MeasBandWi
dth
Measurement
bandwidth
Meaning: Indicates the measurement bandwidth of the

inter-frequency neighboring cell on the frequency. The
setting of this parameter depends on the bandwidth
configuration of the cell. In E-UTRAN, a cell
bandwidth is also expressed in units of resource blocks
(RBs). Cell bandwidths 1.4 MHz, 3 MHz, 5 MHz, 10
MHz, 15 MHz, and 20 MHz correspond to 6 RBs, 15
RBs, 25 RBs, 50 RBs, 75 RBs, and 100 RBs,
respectively.
GUI Value Range: MBW6(1.4M), MBW15(3M),
MBW25(5M), MBW50(10M), MBW75(15M),
MBW100(20M)
Unit: MHz
Actual Value Range: MBW6, MBW15, MBW25,
MBW50, MBW75, MBW100
QoffsetFreq
2012-03-28
Frequency
offset
Meaning: Indicates the frequency offset of the

neighboring cell on the frequency. It is delivered in
system information block type 5 (SIB5). It is used in the
evaluation for cell reselection and for the triggering and

37

Planning
ID
Name
Description
stopping of event A4.
dB-20(-20dB), dB-18(-18dB), dB-16(-16dB),
dB-14(-14dB), dB-12(-12dB), dB-10(-10dB),
dB22(22dB), dB24(24dB)
Unit: dB
dB8, dB10, dB12, dB14, dB16, dB18, dB20, dB22,
dB24
Parameter Relationship: Not involved
of this parameter leads to a lower probability of
reselection to a neighboring cell on the frequency.
ThreshXhigh
Inter frequency
high priority
threshold
Meaning: Indicates the RX level required for a

neighboring cell on the frequency to become a
candidate for reselection if the priority of the frequency
is higher than that of the serving frequency. After
measurements are started for neighboring cells on the
frequency, the UE reselects to a neighboring cell on the
frequency only if the RX level of the cell is better than
the value specified by this parameter for a
time-to-trigger. For details, see 3GPP TS 36.331.
Unit: 2dB
Actual Value Range: 0~62, step:2
Impact on Radio Network Performance: With other
conditions unchanged, a larger value of this parameter
leads to a lower probability of reselection to the cell on
the higher-priority frequency, and a smaller value of
2012-03-28

38

Planning
ID
Name
Description
this parameter leads to a higher probability.
ThreshXlow
Inter frequency
lower priority
threshold
Meaning: Indicates the minimum RX level required for

a neighboring cell on the frequency to become a
candidate for reselection if the priority of the frequency
is lower than that of the serving frequency. After
frequency, the UE reselects to a neighboring cell on the
frequency only if the RX level of the serving cell is
lower than a specified threshold and that of the cell is
higher than the value specified by this parameter for a
Unit: 2dB
leads to a lower probability of reselection to a
neighboring cell on the lower-priority E-UTRAN
frequency, and a smaller value of this parameter leads to
a higher probability.
QRxLevMin
Minimum
required RX
level

neighboring cell on the frequency to become a suitable
cell for selection. It is included in criteria S and used in
the evaluation for cell selection. During the evaluation
for cell reselection, the UE performs the following
calculation: Srxlev = Measured RSRP value of a
neighboring cell on the frequency - Value of this
parameter - Compensated power. If Srxlev for a cell is
better than a threshold for a time-to-trigger, reselection
to the cell is started. For details, see 3GPP TS 36.304.
GUI Value Range: -70~-22
Unit: 2dBm
Actual Value Range: -140~-44, step:2
MML Default Value: -64
Recommended Value: -64
Parameter Relationship: A larger value of this
parameter leads to a lower probability of a cell meeting
criteria S and becoming a suitable cell for cell selection.
A smaller value of this parameter leads to a higher
probability. Set this parameter properly so that the
selected cell can provide signals that meet the quality
2012-03-28

39

Planning
ID
Name
Description
requirement of basic services.
of this parameter leads to a lower probability of a
neighboring cell on the frequency meeting criteria S and
becoming a suitable cell for selection. A smaller value
of this parameter leads to a higher probability. Set this
parameter properly so that the selected cell can provide
signals that meet the quality requirement of basic
services.
PmaxCfgInd
PMAX
configure
indicator
Meaning: Indicates whether to set the maximum power

that the UE can apply to transmission on the
neighboring E-UTRAN frequency. If the value of this
parameter is not specified, the maximum power is
subject to the UE capability. For details, see 3GPP TS
36.101.
CFG(Configure)
Unit: None
Pmax
PMAX
Meaning: Indicates the maximum power that the UE

can apply to transmission on the neighboring
E-UTRAN frequency. It is used in criteria S to calculate
the compensated power. If the value of this parameter is
not specified, the maximum power is subject to the UE
capability. For details, see 3GPP TS 36.101.
GUI Value Range: -30~33
Unit: dBm
Actual Value Range: -30~33
Parameter Relationship: If PmaxCfgInd is set to CFG,
Pmax must be set.
2012-03-28

40

Planning
ID
Name
Description
NeighCellCo
nfig
Neighbor cell
config
Meaning: Indicates the configuration information about

the intra-frequency neighboring cell of the serving cell.
BitString00: Indicates that certain neighboring cells
have the same MBSFN subframe.
BitString01: Indicates that all neighboring cells have the
same MBSFN subframe.
BitString10: Indicates that all neighboring cells have
mutually different MBSFN subframes.
BitString11: Indicates that the serving TDD cells have
neighboring cells of different UL-DL configurations.
GUI Value Range: BitString00(00), BitString01(01),
BitString10(10), BitString11(11)
Unit: None
Actual Value Range: BitString00, BitString01,
BitString10, BitString11
MML Default Value: BitString01(01)
Recommended Value: BitString01(01)
PresenceAnte
nnaPort1
Presence
antenna port1
Meaning: Indicates whether all inter-frequency

neighboring cells on this frequency are configured with
at least two antenna ports.
Set this parameter to TRUE if all inter-frequency
neighboring cells on this frequency are configured with
at least two antenna ports.
Set this parameter to FALSE if one inter-frequency
neighboring cell on this frequency is configured with
only one antenna port.
GUI Value Range: BOOLEAN_FALSE(False),
BOOLEAN_TRUE(True)
Unit: None
Actual Value Range: BOOLEAN_FALSE,
BOOLEAN_TRUE
MML Default Value: BOOLEAN_FALSE(False)
Recommended Value: BOOLEAN_FALSE(False)
InterFreqHoE
ventType
2012-03-28
Inter-Freq HO
trigger Event
Meaning: Indicates the event to trigger inter-frequency

handovers. This parameter can be set to EventA3,

41

Planning
ID
Name
Description
Type
EventA4, or EventA5. If the neighboring E-UTRAN

frequency and the serving frequency are in the same
frequency band, event A3 is recommended as it
provides better handover performance in this situation.
If the neighboring E-UTRAN frequency and the serving
frequency are in different frequency bands, event A4 is
used. Event A5 is not applied in the current version and
the parameter setting is reserved for future extension.
GUI Value Range: EventA3(EventA3),
EventA4(EventA4), EventA5(EventA5)
Unit: None
Actual Value Range: EventA3, EventA4, EventA5
MML Default Value: EventA4(EventA4)
Recommended Value: If the neighboring E-UTRAN
frequency and the serving frequency are in the same
frequency band, the value EventA3 is recommended.
If the neighboring E-UTRAN frequency and the serving
frequency are in different frequency bands, the value
EventA4 is recommended.
Impact on Radio Network Performance: Setting this
parameter to EventA3 improves the performance of
handovers to intra-band inter-frequency neighboring
cells in terms of timeliness and interference. Setting this
parameter to EventA4 reduces the number of inter-band
inter-frequency handovers.
ThreshXhigh
Q
Inter frequency
high priority
RSRQ
threshold
Meaning: Indicates the RSRQ-based minimum RX level

required for a neighboring cell on the frequency to
become a candidate for reselection if the RSRQ-based
priority of the frequency is higher than that of the
serving frequency.
After measurements are started for neighboring cells on
the neighboring E-UTRAN frequency, the UE reselects
to a neighboring cell on the frequency only if the
RSRQ-based RX level of the cell is higher than the
value specified by this parameter for a time-to-trigger.
Unit: dB
2012-03-28

42

Planning
ID
Name
Description
neighboring cell on the higher-priority E-UTRAN
ThreshXlow
Q
Inter frequency
low priority
RSRQ
threshold

required for a neighboring cell on the frequency to
become a candidate for reselection if the RSRQ-based
priority of the frequency is lower than that of the
serving frequency.
a frequency in the GERAN carrier frequency group, the
UE reselects to a neighboring cell on the frequency only
if the RSRQ-based RX level of the serving cell is lower
than a specified threshold and that of the cell is higher
than the value specified by this parameter for a
Unit: dB
neighboring cell on the lower-priority E-UTRAN
QqualMinCfg
Ind
Minimum RX
signal quality
configuration
indicator
Meaning: Indicates whether to set the minimum

required RX level.
CFG(Configure)
Unit: None
Parameter Relationship: If QqualMinCfgInd is set to
CFG, this parameter must be set.
If QqualMinCfgInd is set to NOT_CFG, this parameter
does not need to be set.
2012-03-28

43

Planning
ID
Name
Description
QqualMin
Minimum RX
signal quality
Meaning: Indicates the minimum RX level of an

inter-frequency neighboring cell, which is required for it
to become a candidate for cell reselection. It determines
the probability of triggering cell reselection to
inter-frequency neighboring cells on the frequency. The
value of this parameter is contained in SIB5. For details,
see 3GPP TS 36.331.
Unit: dB
Actual Value Range: -34~-3
of this parameter leads to lower probabilities of the cell
meeting criterion S and becoming a suitable cell
selected by a UE. A smaller value of this parameter
leads to higher probabilities. Set this parameter properly
so that the selected cell can provide signals that meet
the quality requirement of basic services.
2.
If the inter-frequency neighboring cells are served by different eNodeBs, add an external
cell.
If the inter-frequency neighboring cells are served by the same eNodeB, go to step 3. Add an
external cell by running commands that used for adding an external cell in section 4.1 Script
Preparation for Intra-Frequency Neighboring Cells.
If the external cell is in RAN sharing with common carrier, add the public land mobile
network (PLMN) list of corresponding external E-UTRAN cells.
3.
Add an inter-frequency neighboring cell by running the following command:
ADD EUTRANINTERFREQNCELL: LocalCellId=0, Mcc="460", Mnc="20",

eNodeBId=2, CellId=2, CellIndividualOffset=dB3, CellQoffset=dB4,
NoHoFlag=PERMIT_HO_ENUM, NoRmvFlag=FORBID_RMV_ENUM
2012-03-28

44

Planning
Each cell can be configured with a maximum of 64 E-UTRAN inter-frequency neighboring cells.
When inter-frequency neighboring cells and local cells are served by different eNodeBs, the
corresponding external E-UTRAN cells must be configured in advance.
The frequency of an external cell required by E-UTRAN inter-frequency neighboring cells must be
different from that of a local cell.
The frequencies of external cells required by E-UTRAN inter-frequency neighboring cells must be
configured in the E-UTRAN inter-frequencies.
Table 4-4 Inter-frequency neighboring cell parameters

ID
Name
Description
LocalCellId
Local cell
ID
Meaning: Indicates the cell ID of the local cell. It uniquely

identifies a cell within an eNodeB.
Unit: None
Mcc
Mobile
country
code

Unit: None
Mnc
Mobile
network
code

Unit: None
2012-03-28

45

Planning
ID
Name
Description
eNodeBId
eNodeB ID
Meaning: Indicates the eNodeB identity of the

inter-frequency neighboring cell. It uniquely identifies an
eNodeB within a PLMN. The 28-bit E-UTRAN cell
identity is comprised of the cell identity and the eNodeB
identity (represented by the most significant 20 bits). The
cell global identity (CGI) of an E-UTRAN cell is
Unit: None
CellId
Cell ID
Meaning: Indicates the cell ID of the neighboring

E-UTRAN cell. The combination of this parameter and
the eNodeB ID forms the E-UTRAN cell identity. The
combination of the E-UTRAN cell identity and the PLMN
identity forms the ECGI. For details, see 3GPP TS 36.413.
Unit: None
CellIndividual
Offset
Cell
individual
offset
Meaning: Indicates the cell-specific offset between the

serving cell and the inter-frequency neighboring cell. A
larger value of this parameter results in a higher
probability of reporting inter-frequency measurement
events. For details, see 3GPP TS 36.331.
dB-20(-20dB), dB-18(-18dB), dB-16(-16dB),
2012-03-28

46

Planning
ID
Name
Description
dB-2(-2dB), dB-1(-1dB), dB0(0dB), dB1(1dB),
dB24(24dB)
Unit: dB
Actual Value Range: dB-24, dB-22, dB-20, dB-18, dB-16,
dB-2, dB-1, dB0, dB1, dB2, dB3, dB4, dB5, dB6, dB8,
dB10, dB12, dB14, dB16, dB18, dB20, dB22, dB24
Parameter Relationship: The smaller the value of this
parameter, the less probable that the UE camps on the
neighboring cell during reselection. The larger the value
of this parameter, the more probable that the UE camps on
the neighboring cell.
this parameter results in lower probabilities of triggering
event A4 and therefore performing handovers. A smaller
value of this parameter results in an opposite effect.
CellQoffset
Cell offset
Meaning: Indicates the cell specific offset between the

serving cell and the inter-frequency neighboring cell. A
larger the value of this parameter results in a lower
probability of cell reselections. This parameter is
contained in SIB5. For details, see 3GPP TS 36.331.
dB-20(-20dB), dB-18(-18dB), dB-16(-16dB),
dB-2(-2dB), dB-1(-1dB), dB0(0dB), dB1(1dB),
dB24(24dB)
Unit: dB
Actual Value Range: dB-24, dB-22, dB-20, dB-18, dB-16,
dB-2, dB-1, dB0, dB1, dB2, dB3, dB4, dB5, dB6, dB8,
dB10, dB12, dB14, dB16, dB18, dB20, dB22, dB24
Impact on Radio Network Performance: Increasing the
2012-03-28

47

Planning
ID
Name
Description
value of this parameter causes the cell edge to move
towards the neighboring cell, which leads to a lower
probability of cell reselection to the neighboring cell.
Decreasing the value of this parameter leads to an
opposite effect.
NoHoFlag
No
handover
indicator

Unit: None
FORBID_HO_ENUM
NoRmvFlag
No remove
indicator

Remove), FORBID_RMV_ENUM(Forbid ANR Remove)
Unit: None
FORBID_RMV_ENUM
ANR Remove)
ANR Remove)
BlindHoPriorit
y
Blind
handover
Priority
Meaning: Indicates the priority of the neighboring cell

during blind handovers. Blind handover is a process in
which the eNodeB instructs a UE to hand over to a
specified neighboring cell without measurements. There
are 32 priorities in total. The priority has a positive
correlation with the value of this parameter. The value 0
indicates that blind handover is prohibited. Values 17 to
32 are designated for frequency-priority-based handover,
and values 1 to 16 are designated for other handover.
Unit: None
2012-03-28

48

Planning
ID
Name
Description
LocalCellName
Local cell
name

Unit: None
Parameter Relationship: In the EutranInterFreqNCell MO,
the value of LocalCellName is a string of a maximum of
99 characters. The string cannot be all null characters or
contain any of the following characters:double quotation
marks ("), commas (,), semicolons (;), equal signs (=),
single quotation marks ('), three consecutive plus signs
(+++), two or more consecutive blanks, and two or more
consecutive percentage signs (%).
NeighbourCell
Name
Neighbour
cell name
Meaning: Indicates the name of the inter-frequency

neighboring cell.
Unit: None
Parameter Relationship: In the EutranInterFreqNCell MO,
the value of NeighbourCellName is a string of a maximum
of 99 characters. The string cannot be all null characters or
2012-03-28

49

Planning
4.3 Script Preparation for Inter-RAT Neighboring Cells

4.3.1 UTRAN (UMTS/TD-SCDMA)
Figure 4-3 shows the procedure for configuring a UTRAN inter-RAT neighboring cell.
Figure 4-3 Procedure for configuring a UTRAN inter-RAT neighboring cell
Configure a UTRAN inter-RAT neighboring cell as follows:

1.
Add a UTRAN neighboring frequency by running the following command:
ADD UTRANNFREQ: LocalCellId=0, UtranDlArfcn=9700,

UtranFddTddType=UTRAN_FDD, UtranUlArfcnCfgInd=NOT_CFG,
CellReselPriorityCfgInd=NOT_CFG, OffsetFreq=1, QRxLevMin=-49, ThreshXHigh=2,
ThreshXLow=4
Each cell can be configured with a maximum of 16 E-UTRAN neighboring frequencies.
The frequency division duplex (FDD) or time division duplex (TDD) mode in a UTRAN system
must be the same as that in local cells.
The value of ThreshXHigh cannot be greater than the value of ThreshXLow.
Table 4-5 Parameters for adding a UTRAN neighboring frequency

ID
Name
Description
LocalCellId
Local cell
ID

2012-03-28

50

Planning
ID
Name
Description
Unit: None
UtranDlArfcn
Downlink
UARFCN
Meaning: Indicates the DL UARFCN of the neighboring

cell on the UTRAN frequency. The UARFCN range in
each FDD frequency band is shown as follows:
Band 1:
Normal UARFCNs: [10562-10838]
Special UARFCNs: none
Band 2:
Special UARFCNs:
(412,437,462,487,512,537,562,587,612,637,662,687)
Band 3:
Band 4:
Special UARFCNs: (1887, 1912, 1937, 1962, 1987, 2012,
2037, 2062, 2087)
Band 5:
Special UARFCNs: (1007, 1012, 1032, 1037, 1062, 1087)
Band 6:
Special UARFCNs: (1037, 1062)
Band 7:
Special UARFCNs: (2587, 2612, 2637, 2662, 2687, 2712,
2737, 2762, 2787, 2812, 2837, 2862, 2887, 2912)
Band 8:
Band 9:
The UARFCN range in each TDD frequency band is
2012-03-28

51

Planning
ID
Name
Description
shown as follows:
Band 1:
Normal UARFCNs: [9500-9600] and [10050-10125]
Band 2:
Band 3:
Band 4:
Special UARFCNs: (2112, 2137, 2162, 2187, 2212, 2237,
2262, 2287, 2312, 2337)
Band 5:
Band 6:
For details, see 3GPP TS 25.104 and 3GPP TS 25.105.
Unit: None
UtranVersion
UTRAN
version
Meaning: Indicates the working mode supported by the

UTRAN in the current UARFCN.
GUI Value Range: R99, HSDPA, HSUPA, HSPA
Unit: None
Actual Value Range: R99, HSDPA, HSUPA, HSPA
MML Default Value: HSUPA
Recommended Value: HSUPA
2012-03-28

52

Planning
ID
Name
Description
UtranFddTddT
ype
UTRAN
cell type
indicator
Meaning: Indicates the TDD/FDD mode of the inter-RAT

UTRAN.
GUI Value Range: UTRAN_FDD, UTRAN_TDD
Unit: None
Actual Value Range: UTRAN_FDD, UTRAN_TDD
MML Default Value: UTRAN_FDD
Recommended Value: UTRAN_FDD
UtranUlArfcnC
fgInd
Uplink
UARFCN
indicator
Meaning: Indicates whether to set the UL UARFCN of the

cell on the UTRAN frequency. If the value of this
parameter is not specified, the default UL UARFCN is
used. For a UTRAN FDD cell, the way to calculate the
default UL UARFCN varies depending on whether the DL
frequency is a normal or special one.
The default UL UARFCN is calculated as follows if the
DL frequency is a normal one:
Band 1: UL UARFCN = DL UARFCN - 950;
DL frequency is a special one:
For a TDD UTRAN cell, the UL UARFCN is the same as
the DL UARFCN. For details, see 3GPP TS 25.104 and
25.105.
CFG(Configure)
Unit: None
2012-03-28

53

Planning
ID
Name
Description
UtranUlArfcn
Uplink
UARFCN
Meaning: Indicates the UL UARFCN of the neighboring

cell on the UTRAN frequency. The UARFCN range in
each FDD frequency band is shown as follows:
Band 1:
Band 2:
Special UARFCNs: (12, 37, 62, 87, 112, 137, 162, 187,
212, 237, 262, 287)
Band 3:
Band 4:
Special UARFCNs: (1662, 1687, 1712, 1737, 1762, 1787,
1812, 1837, 1862)
Band 5:
Special UARFCNs: (782, 787, 807, 812, 837, 862)
Band 6:
Band 7:
Special UARFCNs: (2362, 2387, 2412, 2437, 2462, 2487,
2512, 2537, 2562, 2587, 2612, 2637, 2662, 2687)
Band 8:
Band 9:
shown as follows:
2012-03-28

54

Planning
ID
Name
Description
Band 1:
Band 2:
Band 3:
Band 4:
Special UARFCNs: (2112, 2137, 2162, 2187, 2212, 2237,
2262, 2287, 2312, 2337)
Band 5:
Band 6:
Unit: None
Parameter Relationship: 1. If UtranUlArfcnCfgInd is set to
CFG, UtranUlArfcn must be set.
2. The DL UARFCN and UL UARFCN must be in the
same frequency band.
CellReselPriorit
yCfgInd
Reselectio
n priority
configure
indicator
Meaning: Indicates whether to set the priority of a cell

assigned with the UARFCN used in cell reselection to
UTRAN.
CFG(Configure)
Unit: None
2012-03-28

55

Planning
ID
Name
Description
CellReselPriorit
y
Cell
reselection
priority
Meaning: The UE decides whether to reselect a

neighboring cell on the UTRAN frequency based on the
value of this parameter and the absolute priority of the
serving cell.
priority of the serving cell, the UE starts measurements on
neighboring cells on the UTRAN frequency; then if the
signal quality of some neighboring cells meets the related
conditions, the UE starts cell reselection.
If the value of this parameter is smaller than the absolute
priority of the serving cell, the UE starts the measurements
only when the signal quality of the serving cell is poor;
then if the signal quality of some neighboring cells meets
the related conditions, the UE starts cell reselection.
Frequencies used for different RATs must be assigned
different cell reselection priorities. For details, see 3GPP
TS 36.331.
Unit: None
Parameter Relationship: If CellReselPriorityCfgInd is set
to CFG, CellReselPriority must be set.
this parameter leads to a higher probability of starting
measurements on neighboring cells on the UTRAN
frequency and also a higher probability of reselection to a
neighboring cell on the frequency.
PmaxUtran
PMAX
Meaning: Indicates the maximum power that the UE can

apply to transmission on the UTRAN frequency. It is used
in criteria S to calculate the compensated power. For
details, see 3GPP TS 25.104.
Unit: dBm
2012-03-28

56

Planning
ID
Name
Description
OffsetFreq
Frequency
offset
Meaning: Indicates the frequency offset of the cell on the

UTRAN frequency. It determines the probability of
triggering measurement reports for event B1. For details,
see 3GPP TS 36.331.
Unit: dB
Impact on Radio Network Performance: The entering
condition of event B1 is as follows: Mn + Ofn - Hys >
Thresh. Where, Mn is the measurement value of
neighboring cells, Ofn is the frequency-specific offset of
the neighboring cell. Thresh is the threshold for event B1.
Hys is the hysteresis for event B1.
A smaller value of Ofn results in a lower probability of
triggering an event B1. This may delay the handover and
affect the user experience. A larger value of Ofn leads to a
higher probability of triggering an event B1, which may
cause handover decision errors and ping-pong handovers.
Qqualmin
Minimum
required
quality
level
Meaning: Indicates the minimum quality level required for

a cell on the UTRAN frequency to become a candidate for
reselection. This parameter is applied only to reselection
to UTRAN FDD cells. A neighboring cell on the UTRAN
frequency can become a candidate for reselection only
when the signal quality of the cell is better than the value
of this parameter.
Unit: dB
Parameter Relationship: Qqualmin must be set if
UtranFddTddType is set to UTRAN_FDD.
this parameter leads to a lower probability of the UTRAN
FDD cell to meet criterion S and become a suitable cell
selected by a UE. A smaller value of this parameter results
in a higher probability. Set this parameter properly so that
2012-03-28

57

Planning
ID
Name
Description
the selected cell can provide signals that meet the quality
QRxLevMin
Minimum
required
RX level

neighboring cell on the UTRAN frequency to become a
candidate for selection. It is included in criteria S and used
in the evaluation for cell selection. During the evaluation
for cell reselection, the UE performs the following
calculation: Srxlev = Measured RSRP value of a
neighboring cell on the frequency - Value of this
parameter - Compensated power. If Srxlev for a
neighboring cell is better than a threshold for a
time-to-trigger, reselection to the cell is started. For
Unit: 2dBm
this parameter leads to a lower probability of the UTRAN
cell to meet criterion S and become a suitable cell selected
by a UE. A smaller value of this parameter results in a
higher probability. Set this parameter properly so that the
ThreshXHigh
UTRAN
high
priority
threshold
Meaning: Indicates the minimum RX level required for a

candidate for reselection if the priority of the frequency is
higher than that of the serving frequency. After
UTRAN frequency, the UE reselects to a neighboring cell
on the frequency only if the RX level of the cell is higher
Unit: 2dB
2012-03-28

58

Planning
ID
Name
Description
leads to a lower probability of reselection to a neighboring
cell on the higher-priority UTRAN frequency, and a
smaller value of this parameter leads to a higher
probability.
UTRAN
lower
priority
threshold
ThreshXLow

candidate for reselection if the priority of the frequency is
lower than that of the serving frequency. After
UTRAN frequency, the UE reselects to a neighboring cell
on the frequency only if the RX level of the serving cell is
Unit: 2dB
cell on the lower-priority UTRAN frequency, and a
probability.
ThreshXHighQ
UTRAN
high
priority
RSRQ
threshold

required for a neighboring cell on the frequency to become
a candidate for reselection if the RSRQ-based priority of
the frequency is higher than that of the serving frequency.
the UTRAN frequency, the UE reselects to a neighboring
cell on the frequency only if the RSRQ-based RX level of
the cell is higher than the value specified by this parameter
for a time-to-trigger. For details, see 3GPP TS 36.331.
Unit: dB
Parameter Relationship: ThreshXHighQ must be set if
2012-03-28

59

Planning
ID
Name
Description
probability.
ThreshXLowQ
UTRAN
low
priority
RSRQ
threshold

required for a neighboring cell on the frequency to become
a candidate for reselection if the RSRQ-based priority of
the frequency is lower than that of the serving frequency.
the frequency, the UE reselects to a cell on the frequency
only if the RSRQ-based RX level of the serving cell is
Unit: dB
Parameter Relationship: ThreshXLowQ must be set if
probability.
PsPriority
PS service
priority
Meaning: Indicates the priority of the UTRAN frequency

for carrying PS services handed over from the local
E-UTRAN cell. The priorities of all neighboring UTRAN
frequencies constitute a priority hierarchy for PS services.
GUI Value Range: LOW_PRIORITY(Low Priority),
HIGH_PRIORITY(High Priority)
Unit: None
Actual Value Range: LOW_PRIORITY,
HIGH_PRIORITY
MML Default Value: HIGH_PRIORITY(High Priority)
Recommended Value: HIGH_PRIORITY(High Priority)
2012-03-28

60

Planning
ID
Name
Description
CsPriority
CS service
priority
Meaning: Indicates the priority of the UTRAN frequency

for carrying CS services handed over from the local
E-UTRAN cell. The priorities of all neighboring UTRAN
frequencies constitute a priority hierarchy for CS services.
GUI Value Range: LOW_PRIORITY(Low Priority),
HIGH_PRIORITY(High Priority)
Unit: None
Actual Value Range: LOW_PRIORITY,
HIGH_PRIORITY
MML Default Value: HIGH_PRIORITY(High Priority)
Recommended Value: HIGH_PRIORITY(High Priority)
2.
Add a UTRAN external cell by running the following command:
ADD UTRANEXTERNALCELL: Mcc="460", Mnc="20", UtranCellId=126,

UtranFddTddType=UTRAN_TDD, UtranDlArfcn=9700,
UtranUlArfcnCfgInd=NOT_CFG, RncId=48, RacCfgInd=NOT_CFG,
PScrambCode=124, Lac=33
Uplink (UL) and DL frequencies must be in the same frequency band.
The new frequency and scrambling code for an external cell must be different from existing ones.
Location area codes cannot be configured as 0000 or FFFE.
Each cell can be configured with a maximum of 768 external E-UTRAN cells.
Table 4-6 Parameters for adding a UTRAN external cell

ID
Name
Description
Mcc
Mobile
country
code

external UTRAN cell.
Unit: None
2012-03-28

61

Planning
ID
Name
Description
Mobile
network
code
Mnc

Unit: None
UTRAN
cell ID
UtranCellId
Meaning: Indicates the ID of the external UTRAN cell. It

uniquely identifies a UTRAN cell within a PLMN.
Unit: None
UtranFddTddT
ype
UTRAN
cell type
indicator
Meaning: Indicates the type of the UTRAN cell.

GUI Value Range: UTRAN_FDD, UTRAN_TDD
Unit: None
Actual Value Range: UTRAN_FDD, UTRAN_TDD
MML Default Value: UTRAN_FDD
Recommended Value: UTRAN_FDD
UtranDlArfcn
2012-03-28
Downlink
UARFCN
Meaning: Indicates the DL UARFCN of the external

UTRAN cell. The UARFCN range in each FDD

62

Planning
ID
Name
Description
frequency band is shown as follows:
Band 1:
Band 2:
Special UARFCNs:
(412,437,462,487,512,537,562,587,612,637,662,687)
Band 3:
Band 4:
Special UARFCNs: (1887, 1912, 1937, 1962, 1987, 2012,
2037, 2062, 2087)
Band 5:
Special UARFCNs: (1007, 1012, 1032, 1037, 1062, 1087)
Band 6:
Band 7:
Special UARFCNs: (2587, 2612, 2637, 2662, 2687, 2712,
2737, 2762, 2787, 2812, 2837, 2862, 2887, 2912)
Band 8:
Band 9:
shown as follows:
Band 1:
Band 2:
Band 3:
2012-03-28

63

Planning
ID
Name
Description
Band 4:
Special UARFCNs: (2112, 2137, 2162, 2187, 2212, 2237,
2262, 2287, 2312, 2337)
Band 5:
Band 6:
Unit: None
UtranUlArfcnC
fgInd
Uplink
UARFCN
configure
indicator
Meaning: Indicates whether to set the UL UARFCN for

the external UTRAN cell. If the value of this parameter is
not specified, the default DL UARFCN is used. For a
UTRAN FDD cell, the way to calculate the default UL
UARFCN varies depending on whether the DL frequency
is a normal or special one.
DL frequency is a normal one:
DL frequency is a special one:
2012-03-28

64

Planning
ID
Name
Description
For a TDD UTRAN cell, the UL UARFCN is the same as
the DL UARFCN. For details, see 3GPP TS 25.104 and
3GPP TS 25.105.
CFG(Configure)
Unit: None
Parameter Relationship: When UtranUlArfcnCfgInd is set
to CFG, UtranUlArfcn must be set.
If UtranUlArfcnCfgInd is set to NOT_CFG, UtranUlArfcn
does not need to be configured.
UtranUlArfcn
Uplink
UARFCN
Meaning: Indicates the UL UARFCN of the external

UTRAN cell. The UARFCN range in each FDD
frequency band is shown as follows:
Band 1:
Band 2:
Special UARFCNs: (12, 37, 62, 87, 112, 137, 162, 187,
212, 237, 262, 287)
Band 3:
Band 4:
Special UARFCNs: (1662, 1687, 1712, 1737, 1762, 1787,
1812, 1837, 1862)
Band 5:
Special UARFCNs: (782, 787, 807, 812, 837, 862)
Band 6:
2012-03-28

65

Planning
ID
Name
Description
Band 7:
Special UARFCNs: (2362, 2387, 2412, 2437, 2462, 2487,
2512, 2537, 2562, 2587, 2612, 2637, 2662, 2687)
Band 8:
Band 9:
shown as follows:
Band 1:
Band 2:
Band 3:
Band 4:
Special UARFCNs: (2112, 2137, 2162, 2187, 2212, 2237,
2262, 2287, 2312, 2337)
Band 5:
Band 6:
Unit: None
2012-03-28

66

Planning
ID
Name
Description
RncId
RNC ID
Meaning: This parameter will be removed in the later

versions. In this version, the setting of this parameter is
still synchronized between the M2000 and the eNodeB,
but it is no longer used internally. Therefore, avoid using
this parameter.
Unit: None
RacCfgInd
Routing
area code
configure
indicator
Meaning: Indicates whether to set the routing area code

(RAC) of the external UTRAN cell. This parameter must
be set to CFG if the external UTRAN cell supports packet
switched (PS) services.
CFG(Configure)
Unit: None
Rac
Routing
area code
Meaning: Indicates the routing area code.

Unit: None
Parameter Relationship: If RacCfgInd is set to CFG, this
parameter must be set.
PScrambCode
2012-03-28
Primary
scrambling
code
Meaning: Indicates the primary DL scrambles of the

external UTRAN cell. For details, see 3GPP TS 25.331.

67

Planning
ID
Name
Description
Unit: None
Lac
Location
area code
Meaning: Indicates the LAC of the external UTRAN cell.

GUI Value Range: 1~65533,65535
Unit: None
Actual Value Range: 1~65533,65535
CellName
Cell name
Meaning: Indicates the name of the external UTRAN cell.

Unit: None
Parameter Relationship: In the UtranExternalCell MO, the
value of CellName is a string of a maximum of 99
characters. The string cannot be all null characters or
CsPsHOInd
CS and PS
handover
indicator
Meaning: Indicates whether the external UTRAN cell

supports single radio voice call continuity (SRVCC) for
both CS and PS services. If this parameter is set to
BOOLEAN_FALSE, the cell supports only SRVCC for
CS services.
GUI Value Range: BOOLEAN_FALSE(False),
BOOLEAN_TRUE(True)
Unit: None
2012-03-28

68

Planning
ID
Name
Description
Actual Value Range: BOOLEAN_FALSE,
BOOLEAN_TRUE
MML Default Value: BOOLEAN_FALSE(False)
Recommended Value: BOOLEAN_FALSE(False)
Mobile
country
code
Mcc

Unit: None
3.
Add a UTRAN neighboring cell by running the following command:
ADD UTRANNCELL: LocalCellId=0, Mcc="460", Mnc="20", UtranCellId=126

The frequency of the external cell required by UTRAN inter-RAT neighboring cells must be
included in UTRAN frequencies.
The external cell corresponding to the UTRAN neighboring cell relationship must be configured in
advance.
Each cell can be configured with a maximum of 64 UTRAN neighboring cells.
When the blind handover priority is a non-zero value, no other values can be configured for the local
cell.
Table 4-7 Parameters for adding a UTRAN inter-RAT neighboring cell

ID
Name
Description
LocalCellId
Local cell ID

GUI value range: 0~11
2012-03-28

69

Planning
ID
Name
Description
Unit: None
Actual value range: 0~11
MML Default value: None
Recommended value: None
Mcc
Mobile
country code

neighboring UTRAN cell.
Unit: None
Mnc
Mobile
network code

neighboring UTRAN cell.
Unit: None
UtranCellId
UTRAN cell
ID
Meaning: Indicates the UTRAN cell ID. It uniquely

identifies a cell within a PLMN.
Unit: None
2012-03-28

70

Planning
ID
Name
Description
NoHoFlag
No handover
indicator
Meaning: Indicates whether to allow handover of UEs to

the neighboring cell that is determined by the neighboring
relation.
Unit: None
FORBID_HO_ENUM
NoRmvFlag
No remove
indicator

Unit: None
FORBID_RMV_ENUM
ANR Remove)
ANR Remove)
BlindHoPrio
rity
Blind
handover
priority

specified neighboring cell. There are 32 priorities
altogether. The priority has a positive correlation with the
value of this parameter. Note that the value 0 indicates
that blind handovers to the neighboring cell are not
allowed.
2012-03-28

71

Planning
ID
Name
Description
Unit: None
LocalCellNa
me
Local cell
name

Unit: None
Parameter Relationship: In the UtranNCell MO, the value
of LocalCellName is a string of a maximum of 99
NeighbourC
ellName
Neighbour cell
name
Meaning: Indicates the name of the UTRAN neighboring

cell.
Unit: None
Parameter Relationship: In the UtranNCell MO, the value
of NeighbourCellName is a string of a maximum of 99
2012-03-28

72

Planning
4.3.2 GERAN (GSM/GPRS/EDGE)

Figure 4-4 shows the procedure for configuring a GSM/EDGE radio access network (GERAN)
inter-RAT neighboring cell.
Figure 4-4 Procedure for configuring a GERAN inter-RAT neighboring cell
1.
Add a GERAN neighboring frequency group by running the following command:
ADD GERANNFREQGROUP: LocalCellId=0, BcchGroupId=1, GeranVersion=GSM,

StartingArfcn=0, BandIndicator=GSM_pcs1900, CellReselPriorityCfgInd=CFG,
CellReselPriority=3, PmaxGeranCfgInd=CFG
Each cell can be configured with a maximum of 16 GERAN neighboring frequency groups.
Table 4-8 Parameters for adding a GERAN neighboring frequency group

ID
Name
Description
LocalCellId
Local cell
ID

2012-03-28

73

Planning
ID
Name
Description
Unit: None
BcchGroupId
BCCH
group ID
Meaning: Indicates a GERAN carrier frequency group. In

the cell reselection procedure, the GERAN carrier
frequencies are organized in groups and the cell
reselection parameters are provided per group of GERAN
carrier frequencies.
Unit: None
GeranVersion
GERAN
version
Meaning: Indicates the standard that is supported by the

current carrier frequency group.
GUI Value Range: GSM, GPRS, EDGE
Unit: None
Actual Value Range: GSM, GPRS, EDGE
StartingArfcn
Starting
ARFCN
Meaning: Indicates the first ARFCN value in the GERAN

carrier frequency group. For details, see 3GPP TS 36.331.
Unit: None
2012-03-28

74

Planning
ID
Name
Description
Band
indicator
BandIndicator
Meaning: Indicates the GERAN band indicator. If the

GERAN ARFCN is a value in the range of 512 to 810, the
value of this parameter is used to indicate whether the
GERAN frequency is in the 1800 MHz band or the 1900
MHz band. For details, see 3GPP TS 36.331.
GUI Value Range: GSM_dcs1800, GSM_pcs1900
Unit: None
Actual Value Range: GSM_dcs1800, GSM_pcs1900
CellReselPriori
tyCfgInd
Cell
reselection
priority
configure
indicator
Meaning: Indicates whether to set the reselection priority

of the frequencies in the GERAN carrier frequency group.
If the value of this parameter is not specified, the UE does
not reselect to neighboring cells on the frequencies in the
GERAN carrier frequency group.
CFG(Configure)
Unit: None
CellReselPriori
ty
Cell
reselection
priority
Meaning: Indicates the cell reselection priority of the

GERAN carrier frequency group. It is contained in system
information block type 7 (SIB7). The UE decides whether
to reselect a neighboring cell on a frequency in the
GERAN carrier frequency group based on the value of
this parameter and the absolute priority of the serving cell.
priority of the serving cell, the UE starts measurements on
neighboring cells on the frequencies in the GERAN
carrier frequency group; then if the signal quality of some
neighboring cells meets the related conditions, the UE
starts cell reselection. If the value of this parameter is
smaller than the absolute priority of the serving cell, the
UE starts the measurements only when the signal quality
of the serving cell is poor; then if the signal quality of
2012-03-28

75

Planning
ID
Name
Description
some neighboring cells meets the related conditions, the
UE starts cell reselection. Frequencies used for different
RATs must be assigned different cell reselection
priorities. For details, see 3GPP TS 36.331.
Unit: None
Parameter Relationship: If CellReselPriorityCfgInd is set
to CFG, CellReselPriority must be set.
this parameter indicates a higher probability of a UE
camping on the cell on a frequency in the GERAN carrier
frequency group, and a smaller value indicates a lower
probability.
PmaxGeranCfg
Ind
PMAX
configure
indicator
Meaning: Indicates whether to set the maximum power

that the UE can apply to transmission on a frequency in
the GERAN carrier frequency group. It is used in criteria
S to calculate the compensated power. For details, see
3GPP TS 36.104.
CFG(Configure)
Unit: None
Parameter Relationship: If PmaxGeranCfgInd is set to
CFG, PmaxGeran must be set.
If PmaxGeranCfgInd is set to NOT_CFG, PmaxGeran
PmaxGeran
PMAX
Meaning: Indicates the maximum power that the UE can

apply to transmission on a frequency in the GERAN
carrier frequency group. For details, see 3GPP TS 36.331.
Unit: dBm
2012-03-28

76

Planning
ID
Name
Description
Parameter Relationship: If PmaxGeranCfgInd is set to
CFG, PmaxGeran must be set.
If PmaxGeranCfgInd is set to NOT_CFG, PmaxGeran
QRxLevMin
Minimum
required
RX level

neighboring cell on a frequency in the GERAN carrier
frequency group to become a candidate for selection. It is
included in criteria S and used in the evaluation for cell
selection. During the evaluation for cell reselection, the
UE performs the following calculation: Srxlev =
Measured RSSI value of a neighboring cell on a frequency
in the GERAN carrier frequency group - Value of this
parameter - Compensated power. If Srxlev for a
neighboring cell is better than a threshold for a
time-to-trigger, reselection to the cell is started. For
Unit: 2 dBm
this parameter leads to a lower probability of a
frequency group becoming a suitable cell for cell
selection. A smaller value of this parameter leads to a
higher probability. Set this parameter properly so that the
ThreshXHigh
High
priority
threshold

frequency group to become a candidate for reselection if
the priority of the frequency is higher than that of the
serving frequency.
After measurements are started for neighboring cells on a
frequency in the GERAN carrier frequency group, the UE
reselects to a cell on the frequency only if the RX level of
the cell is better than the value specified by this parameter
for a time-to-trigger. For details, see 3GPP TS 36.104.
Unit: 2 dB
2012-03-28

77

Planning
ID
Name
Description
Impact on Radio Network Performance: When other
cell on a frequency in the higher-priority carrier frequency
group, and a smaller value of this parameter leads to a
higher probability.
ThreshXLow
Lower
priority
threshold

frequency group to become a candidate for reselection if
the priority of the frequency is lower than that of the
serving frequency.
frequency in the GERAN carrier frequency group, the UE
reselects to a cell on the frequency only if the RX level of
the serving cell is lower than a specified threshold and that
of the cell is better than the value specified by this
parameter for a time-to-trigger. For details, see 3GPP TS
36.104.
Unit: 2 dB
cell on a frequency in the lower-priority carrier frequency
group, and a smaller value of this parameter leads to a
higher probability.
OffsetFreq
Frequency
offset
Meaning: Indicates the frequency specific offset of the

group of neighboring GERAN carrier frequencies. This
parameter is used in the decision of the UE to send
measurement reports for inter-RAT handovers. For
Unit: dB
2012-03-28

78

Planning
ID
Name
Description
Thresh.
Where, Mn is the measurement value of neighboring cells.
Ofn is the frequency-specific offset of the neighboring
cell, Thresh is the threshold for event B1, and Hys is the
hysteresis for event B1.
The smaller the value of Ofn is, the harder event B1 is
triggered, and the more slowly the handover is
implemented. This affects the user experience. The bigger
the value of Ofn is, the easier event B1 is triggered. This
also easily causes error decisions and ping-pong
handovers.
NccPermitted
NCC
monitoring
permitted
Meaning: Indicates whether a BCCH carrier with the

specific NCC is permitted for monitoring. For details, see
3GPP TS 36.331.
Unit: None
2.
Add a GERAN broadcast control channel (BCCH) neighboring frequency by running the
following command:
ADD GERANNFREQGROUPARFCN: LocalCellId=0, BcchGroupId=0, GeranArfcn=2

Table 4-9 lists related parameters.
2012-03-28

79

Planning
Each cell can be configured with a maximum of 31 GERAN BCCH neighboring frequencies.
Before configuring GERAN BCCH neighboring cells, you must configure corresponding BCCH
frequency groups.
The new frequencies cannot be the same as the existing ones.
Table 4-9 Parameters for adding a GERAN BCCH neighboring frequency

ID
Name
Description
LocalCellId
Local cell ID

Unit: None
BcchGroupId
BCCH group ID
Meaning: Indicates the index of the BCCH carrier

frequency group. It identifies a BCCH carrier
frequency group.
Unit: None
GeranArfcn
GERAN ARFCN
Meaning: Indicates the GERAN BCCH ARFCN. For

Unit: None
3.
2012-03-28
Add a GERAN external cell by running the following command:

80

Planning
ADD GERANEXTERNALCELL: Mcc="460", Mnc="20", GeranCellId=17, Lac=13,

RacCfgInd=CFG, Rac=16, BandIndicator=GSM_pcs1900, GeranArfcn=12,
NetworkColourCode=0, BaseStationColourCode=0
The LAC cannot be configured as 0000 or FFFE.
Each cell can be configured with a maximum of 768 GERAN external cells.
Table 4-10 Parameters for adding a GERAN external cell

ID
Name
Description
Mcc
Mobile country
code

external cell.
For example, MCC = 123, MNC = 45, PLMN =
12345.
Unit: None
Service Interrupted After Modification: Not
involved
Mnc
Mobile network
code

external cell.
For example, MCC = 123, MNC = 45, PLMN =
12345.
Unit: None
involved
2012-03-28

81

Planning
ID
Name
Description
GeranCellId
GERAN cell ID
Meaning: Indicates the cell ID of the external

GERAN cell. It uniquely identifies a GERAN cell
within the area specified by the location area
identity (LAI). An LAI consists of the MCC,
MNC, and LAC.
Unit: None
involved
Lac
Location area code
Meaning: Indicates the LAC of the external

GERAN cell. It uniquely identifies a location
within a PLMN.
Unit: None
involved
RacCfgInd
Routing area code

configure indicator
Meaning: Indicates whether to set the routing area

code (RAC) of the external GERAN cell. This
parameter is required if the external GERAN cell
supports packet switched (PS) services.
CFG(Configure)
Unit: None
Parameter Relationship: When RacCfgInd is set to
CFG, Rac must be set.
When RacCfgInd is set to NOT_CFG, Rac does
not need to be set.
Service Interrupted After Modification: No (And
no impact on the UE in idle mode)
2012-03-28

82

Planning
ID
Name
Description
Rac
Routing area code
Meaning: Indicates the routing area code.

Unit: None
BandIndicator
Band indicator
Meaning: Indicates the GERAN band indicator. If

the GERAN ARFCN is a value in the range of 512
to 810, the value of this parameter is used to
indicate whether the GERAN frequency is in the
1800 MHz band or the 1900 MHz band. For
GUI Value Range: GSM_dcs1800, GSM_pcs1900
Unit: None
Actual Value Range: GSM_dcs1800,
GSM_pcs1900
GeranArfcn
GERAN ARFCN
Meaning: Indicates the GERAN BCCH ARFCN.

Unit: None
NetworkColour
Code
Network color
code
Meaning: Indicates the network color code (NCC)

of GERAN. It is operator-specific and identifies a
network within the whole country.
The base transceiver station identity code (BSIC)
consists of the NCC and the base station color code
2012-03-28

83

Planning
ID
Name
Description
(BCC). For details, see 3GPP TS 23.003.
Unit: None
BaseStationCol
ourCode
Base station color

code
Meaning: Indicates the base station color code

(BCC) of the external GERAN cell. The base
transceiver station identity code (BSIC) consists of
the BCC and the network color code (NCC). For
Unit: None
DtmInd
DTM indication
Meaning: Indicates whether the cell supports the

dual transmission mode. If the cell supports the
dual transmission mode, both CS and PS services
can be handed over to the cell. Otherwise, only the
CS service or the PS service can be handed over to
the cell.
GUI Value Range: DTM_AVAILABLE,
DTM_NOT_AVAILABLE
Unit: None
Actual Value Range: DTM_AVAILABLE,
DTM_NOT_AVAILABLE
MML Default Value: DTM_NOT_AVAILABLE
Recommended Value: DTM_NOT_AVAILABLE
CellName
2012-03-28
Cell name
Meaning: Indicates the name of the external

GERAN cell.

84

Planning
ID
Name
Description
Unit: None
Parameter Relationship: In the GeranExternalCell
MO, the value of CellName is a string of a
maximum of 99 characters. The string cannot be
all null characters or contain any of the following
semicolons (;), equal signs (=), single quotation
marks ('), three consecutive plus signs (+++), two
or more consecutive blanks, and two or more
4.
Add a GERAN neighboring cell by running the following command:
ADD GERANNCELL: LocalCellId=0, Mcc="460", Mnc="20", Lac=13,

GeranCellId=17, NoRmvFlag=PERMIT_RMV_ENUM,
NoHoFlag=PERMIT_HO_ENUM
Before configuring GERAN inter-RAT neighboring cells, you must configure a GERAN inter-RAT
external cell.
The frequencies of the external cell required by GERAN inter-RAT neighboring cells must be
included in GERAN inter-RAT neighboring frequency groups.
Each cell can be configured with a maximum of 64 GERAN neighboring cells.
cell.
Table 4-11 Parameters for adding a GERAN inter-RAT neighboring cell

ID
Name
Description
LocalCellId
Local cell
ID

Unit: None
2012-03-28

85

Planning
ID
Name
Description
Mcc
Mobile
country
code

neighboring GERAN cell.
Unit: None
Mnc
Mobile
network
code

neighboring GERAN cell.
Unit: None
Lac
Location
area code
Meaning: Indicates the LAC of the GERAN neighboring

cell. It uniquely identifies a location within a PLMN.
Unit: None
2012-03-28

86

Planning
ID
Name
Description
GERAN
cell ID
GeranCellId
Meaning: Indicates the cell ID of the GERAN neighboring

cell. It uniquely identifies a GERAN cell within the area
specified by the location area identity (LAI). An LAI
consists of the MCC, MNC, and LAC.
Unit: None
No
remove
indicator
NoRmvFlag

Unit: None
FORBID_RMV_ENUM
ANR Remove)
ANR Remove)
No
handover
indicator
NoHoFlag

Unit: None
FORBID_HO_ENUM
BlindHoPriority
2012-03-28
Blind

87

Planning
ID
Name
Description
handover
priority

specified neighboring cell. There are 32 priorities
altogether. The priority has a positive correlation with the
value of this parameter. Note that the value 0 indicates
that blind handovers to the neighboring cell are not
allowed.
Unit: None
LocalCellName
Local cell
name

Unit: None
Parameter Relationship: In the GeranNcell MO, the value
of LocalCellName is a string of a maximum of 99
NeighbourCellN
ame
Neighbour
cell name
Meaning: Indicates the name of the GERAN neighboring

cell.
Unit: None
Parameter Relationship: In the GeranNcell MO, the value
of NeighbourCellName is a string of a maximum of 99
2012-03-28

88

Planning
ID
Name
Description
4.3.3 CDMA2000
Figure 4-5 shows the procedure for configuring a CDMA2000 inter-RAT neighboring cell.
Figure 4-5 Procedure for configuring a CDMA2000 inter-RAT neighboring cell
1.
Add a CDMA2000 frequency band by running the following command:
ADD CDMA2000BANDCLASS: LocalCellId=0, BandClass=bc0

2012-03-28

89

Planning
According to the protocol, band classes 0 to 17 are valid. Therefore, a maximum of 18 CDMA2000
band classes can be configured for an E-UTRAN cell.
Table 4-12 Parameters for adding a CDMA2000 frequency band

ID
Name
Description
LocalCellId
Local cell ID

Unit: None
BandClass
Band class
Meaning: Indicates the neighboring CDMA2000 band

class. Signals on a frequency within the band class can be
obtained by UEs. For details, see the
BandclassCDMA2000 IE defined in 3GPP 36.331.
GUI Value Range: bc0, bc1, bc2, bc3, bc4, bc5, bc6, bc7,
bc8, bc9, bc10, bc11, bc12, bc13, bc14, bc15, bc16, bc17
Unit: None
Actual Value Range: bc0, bc1, bc2, bc3, bc4, bc5, bc6,
bc7, bc8, bc9, bc10, bc11, bc12, bc13, bc14, bc15, bc16,
bc17
CellReselPrio
rity
Cell
reselection
priority
Meaning: Indicates the absolute priority of the

CDMA2000 band class to be used during cell reselection.
The value 0 indicates the lowest priority. Frequencies used
for different RATs must be assigned different cell
reselection priorities. The information is contained in
SIB8. For details, see 3GPP TS 36.331.
Unit: None
Parameter Relationship: The greater the parameter, the
2012-03-28

90

Planning
ID
Name
Description
greater the possibility for the UE to camp in this cell. The
smaller the parameter is, the smaller the possibility for the
UE to camp in this cell.
this parameter indicates a higher probability of a UE
camping on the cells assigned with the band class, and a
smaller value indicates a lower probability.
ThreshXHigh
High priority
threshold

neighboring cell on a frequency in the CDMA2000 band
class to become a candidate for reselection if the priority
of the frequency is higher than that of the serving
frequency.
frequency in the band class, the UE reselects to a
neighboring cell only if the RX level of the cell is higher
time-to-trigger. For details, see 3GPP TS 36.304 5.2.4.5.
Unit: dB
this parameter leads to a lower probability of a UE
camping on a cell on a frequency in the higher-priority
CDMA2000 band class, and a smaller value indicates a
higher probability.
ThreshXLow
Lower
priority
threshold

neighboring cell on a frequency in the CDMA2000 band
class to become a candidate for reselection if the priority
of the frequency is lower than that of the serving
frequency.
frequency in the band class, the UE reselects to a cell on
the frequency only if the RX level of the serving cell is
time-to-trigger. For details, see 3GPP TS 36.304 5.2.4.5.
Unit: dB
2012-03-28

91

Planning
ID
Name
Description
this parameter leads to a lower probability of a UE
camping on a cell on a frequency in the lower-priority
band class, and a smaller value leads to a higher
probability.
2.
Add a CDMA2000 frequency by running the following command:
ADD CDMA2000NFREQ: LocalCellId=0, BandClass=bc1, Frequency=20,

OffsetFreq=14, SearchWindowSizeCfgInd=NOT_CFG
Each cell can be configured with a maximum of 16 CDMA2000 frequencies on each frequency
band.
Before configuring CDMA2000 frequencies, you must configure corresponding CDMA2000

frequency bands.
Table 4-13 Parameters for adding a CDMA2000 frequency

ID
Name
Description
LocalCellId
Local cell ID

Unit: None
BandClass
Band class
Meaning: Indicates the neighboring CDMA2000 band

class. Signals on a frequency within the band class can be
obtained by UEs. For details, see the
BandclassCDMA2000 IE defined in 3GPP 36.331 6.3.4.
Unit: None
2012-03-28

92

Planning
ID
Name
Description
bc17
Frequency
Frequency
Meaning: Indicates the neighboring CDMA2000

frequency of the serving cell. For details, see the IE
CDMA2000-CarrierInfo in the 3GPP 36.331 6.3.4
protocol.
Unit: None
OffsetFreq
Frequency
offset
Meaning: Indicates the frequency-specific offset of the

local cell to the neighboring CDMA2000 cell on the
frequency. A larger value of this parameter leads to a
higher probability of triggering measurement reports. For
details, see the Q-OffsetRangeInterRAT IE defined in
3GPP 36.331 6.3.4.
Unit: dB
Thresh.
Where, Mn is the measurement value of neighboring cells.
Ofn is the frequency-specific offset of the neighboring
cell, Thresh is the threshold for this event, and Hys refers
to the hysteresis for this event.
The smaller the value of Ofn is, the harder event B1 is
triggered, and the more slowly the handover is
implemented. This affects the user experience. The bigger
the value of Ofn is, the easier event B1 is triggered. This
2012-03-28

93

Planning
ID
Name
Description
also easily causes error decisions and ping-pong
handovers.
SearchWindo
wSizeCfgInd
Search
window size
configure
indicator
Meaning: Indicates whether to set the size of the

CDMA2000 search window. If this parameter is set to
NOT_CFG, the default size (8) is used.
CFG(Configure)
Unit: None
SearchWindo
wSize
Search
window size
Meaning: Indicates the size of the CDMA2000 search

window. UEs search for pilots for neighboring
CDMA2000 cells within the time period specified by this
parameter. For details, see the MeasObjectCDMA2000 IE
defined in 3GPP TS 36.331.
Unit: None
Parameter Relationship: If SearchWindowSizeCfgInd is
set to CFG, SearchWindowSize must be set.
3.
Add a CDMA2000 external cell by running the following command:
ADD CDMA2000EXTERNALCELL: CellGlobalId="1000000000000002",

BandClass=bc1, Frequency=20, PnOffset=89, Mcc="460", Mnc="20"
Each cell can be configured with a maximum of 768 CDMA2000 external cells.
2012-03-28

94

Planning
Table 4-14 Parameters for adding a CDMA2000 external cell

ID
Name
Description
CellGlobalId
Cell global
ID
Meaning: Indicates the cell global ID of the external

CDMA2000 cell. It uniquely identifies a CDMA2000 cell
around the globe. For details, see the
CellGlobalIdCDMA2000 IE defined in 3GPP 36.331
6.3.4. The cell global ID of a CDMA2000 HRPD cell
consists of 16 decimal digits, and that of a CDMA2000
1xRTT cell consists of 6 decimal digits.
Unit: None
BandClass
Band class
Meaning: Indicates the band class on which the external

CDMA2000 cell operates. For details, see 3GPP TS
36.331.
Unit: None
bc17
Frequency
Frequency
Meaning: Indicates the frequency on which the external

CDMA2000 cell operates. For details, see 3GPP TS
36.331.
Unit: None
2012-03-28

95

Planning
ID
Name
Description
PnOffset
Physical cell
ID
Meaning: Indicates the scrambling code, which is used as

the physical cell identifier of the external CDMA2000
cell.
Unit: None
Cdma2000Ty
pe
CDMA2000
neighbor cell
type
Meaning: Indicates the type of the external CDMA2000

cell. By default, the cell is a CDMA2000 HRPD cell.
Note that the cell global identity of a CDMA2000 1xRTT
cell consists of 6 decimal digits, and that of a CDMA2000
HRPD cell consists of 16 decimal digits.
GUI Value Range:
CDMA2000_HRPD(CDMA2000_HRPD),
CDMA2000_1XRTT(CDMA2000_1XRTT)
Unit: None
Actual Value Range: CDMA2000_HRPD,
CDMA2000_1XRTT
MML Default Value:
CDMA2000_HRPD(CDMA2000_HRPD)
Recommended Value:
CDMA2000_HRPD(CDMA2000_HRPD)
Mcc
Mobile
country code

external cell.
A PLMN ID is comprised of an MCC and an MNC.
For example, if the MCC is 123 and the MNC is 45, then
the PLMN ID is 12345.
Unit: None
2012-03-28

96

Planning
ID
Name
Description
Mnc
Mobile
network code

external cell.
Unit: None
CellName
Cell name
Meaning: Indicates the name of the external CDMA2000

cell.
Unit: None
Parameter Relationship: In the Cdma2000ExternalCell
MO, the value of CellName is a string of a maximum of
4.
Add a CDMA2000 1XRTT neighboring cell by running the following command:
ADD CDMA20001XRTTNCELL: LocalCellId=0, CellGlobalId="123456",

BlindHoPriority=1
2012-03-28

97

Planning
The CDMA2000 1XRTT external cell must be configured in advance.
The frequency bands and frequencies of the external cell required by CDMA2000 1XRTT
neighboring cells must be included in the existing frequencies.
Each cell can be configured with a maximum of 32 CDMA2000 1XRTT neighboring cells.
cell.
Table 4-15 Parameters for adding a CDMA2000 1XRTT inter-RAT neighboring cell
ID
Name
Description
LocalCellId
Local cell
ID

Unit: None
CellGlobalId
Cell
global ID
Meaning: Indicates the cell global ID of the neighboring

cell. It uniquely identifies a CDMA2000 1xRTT cell
CellGlobalIdCDMA2000 IE defined in 3GPP 36.331
6.3.4.
Unit: None
NoHoFlag
No
handover
indicator

associated neighboring cell are prohibited.
Unit: None
FORBID_HO_ENUM
2012-03-28

98

Planning
ID
Name
Description
No
remove
indicator
NoRmvFlag

Unit: None
FORBID_RMV_ENUM
ANR Remove)
ANR Remove)
BlindHoPriority
Blind
handover
priority

are 32 priorities altogether. The priority has a positive
correlation with the value of this parameter. Note that the
value 0 indicates that blind handovers to the neighboring
cell are prohibited.
Unit: None
LocalCellName
Local cell
name

Unit: None
Parameter Relationship: In the Cdma20001XRTTNcell
2012-03-28

99

Planning
ID
Name
Description
MO, the value of LocalCellName is a string of a
NeighbourCellN
ame
Neighbour
cell name
Meaning: Indicates the name of the neighboring cell.

Unit: None
Parameter Relationship: In the Cdma20001XRTTNcell
MO, the value of NeighbourCellName is a string of a
5.
Add a CDMA2000 HRPD neighboring cell by running the following command:
ADD CDMA2000HRPDNCELL: LocalCellId=0, CellGlobalId="1234567890123456",

BlindHoPriority=0
2012-03-28

100

Planning
cell.
The CDMA2000 external cell must be configured in advance.
The frequency bands and frequencies of the external cell required by CDMA2000 HRPD
neighboring cells must be included in the existing frequencies.
Each cell can be configured with a maximum of 32 CDMA2000 HRPD neighboring cells.
Table 4-16 Parameters for adding a CDMA2000 HRPD inter-RAT neighboring cell
ID
Name
Description
LocalCellId
Local cell
ID

Unit: None
CellGlobalId
Cell
global ID
Meaning: Indicates the cell global ID of the neighboring

CDMA2000 HRPD cell. It uniquely identifies a
CDMA2000 HRPD cell around the globe. For details, see
the CellGlobalIdCDMA2000 IE defined in 3GPP 36.331
6.3.4.
Unit: None
NoHoFlag
No
handover
indicator

associated neighboring cell are prohibited.
Unit: None
FORBID_HO_ENUM
Parameter Relationship: LOFD-001021: PS Inter-RAT
Mobility between LTE and CDMA2000
2012-03-28

101

Planning
ID
Name
Description
No
remove
indicator
NoRmvFlag

Unit: None
FORBID_RMV_ENUM
ANR Remove)
ANR Remove)
BlindHoPriority
Blind
handover
priority

are 32 priorities altogether. The priority has a positive
correlation with the value of this parameter. Note that the
value 0 indicates that blind handovers to the neighboring
cell are prohibited.
Unit: None
LocalCellName
Local cell
name

Unit: None
Parameter Relationship: In the Cdma2000HrpdNcell MO,
the value of LocalCellName is a string of a maximum of
2012-03-28

102

Planning
ID
Name
Description
NeighbourCellN
ame
Neighbour
cell name
Meaning: Indicates the name of the neighboring

CDMA2000 HRPD cell.
Unit: None
Parameter Relationship: In the Cdma2000HrpdNcell MO,
the value of NeighbourCellName is a string of a maximum
of 99 characters. The string cannot be all null characters or
4.4 Script Preparation in RAN-Sharing Mode

In this document, the RAN-sharing mode includes RAN sharing with common carrier and
RAN sharing with dedicated carrier. In RAN sharing with common carrier, multiple operators
share eRAN resources that include carriers and eNodeB hardware. In RAN sharing with
dedicated carrier, different operators have their own carriers and share only eNodeB hardware.
The Multi-Operator Core Network (MOCN) uses the RAN sharing with common carrier.
4.4.1 Neighboring Cell Configuration in RAN Sharing with

Common Carrier
1.
Neighboring Cell Configuration in RAN Sharing with Common Carrier
Figure 4-6 shows the procedure for configuring an intra-frequency neighboring cell in RAN
sharing with common carrier.
2012-03-28

103

Planning
Figure 4-6 Procedure for configuring an intra-frequency neighboring cell in RAN sharing with
common carrier
For co-eNodeB neighboring cells, the configuration procedure is the same as that in
section 4.1 Script Preparation for Intra-Frequency Neighboring Cells.
For intra-eNodeB neighboring cells, if the target cell is in RAN sharing with common
carrier, the neighboring cells can be shared after the PLMN list of an external cell is
added.
The target cells not in RAN sharing with common carrier are separated based on the
E-UTRAN cell global identifier (ECGI) that includes MCC, MNC, eNodeBID and
CellID. The number of intra-frequency neighboring cells is 32 and is fixed.
Add the PLMN list of external E-UTRAN cells by running the following command:
ADD EUTRANEXTERNALCELLPLMN: Mcc="460", Mnc="20", eNodeBId=255,
CellId=1, ShareMcc="460", ShareMnc="01"
Before configuring the PLMN list of an external E-UTRAN cell, you must configure a
corresponding external E-UTRAN cell.
Each E-UTRAN external cell can be configured with three PLMN lists of an E-UTRAN external
cell.
Table 4-17 Parameters for adding the external cell PLMN list
2012-03-28
ID
Name
Description
Mcc
Mobile country

104

Planning
ID
Name
Description
code
external cell.
Unit: None
Mnc
Mobile network
code

external cell.
Unit: None
eNode
BId
eNodeB ID
Meaning: Indicates the eNodeB identity of the external

E-UTRAN cell. It uniquely identifies an eNodeB within a
PLMN. The 28-bit E-UTRAN cell identity is comprised of
the cell identity and the eNodeB identity (represented by
the most significant 20 bits). The cell global identity
(CGI) of an E-UTRAN cell is comprised of the E-UTRAN
cell identity and the PLMN ID. For details, see 3GPP TS
36.413.
Unit: None
2012-03-28

105

Planning
ID
Name
Description
CellId
Cell ID
Meaning: Indicates the cell identity of the external

E-UTRAN cell. It uniquely identifies a cell within an
eNodeB. The 28-bit E-UTRAN cell identity is comprised
of the cell identity (represented by the least significant
eight bits) and the eNodeB identity. The cell global
identity (CGI) of an E-UTRAN cell is comprised of the
E-UTRAN cell identity and the PLMN ID. For details, see
3GPP TS 36.413.
Unit: None
ShareM
cc
Share mobile
country code

external E-UTRAN cell that is shared among multiple
operators.
Unit: None
ShareM
nc
Share mobile
network code

external E-UTRAN cell that is shared among multiple
operators.
2012-03-28

106

Planning
ID
Name
Description
Unit: None
2.
Inter-Frequency Neighboring Cell Configuration in RAN Sharing with Common Carrier
Figure 4-7 shows the procedure for configuring an inter-frequency neighboring cell in RAN
sharing with common carrier.
Figure 4-7 Procedure for configuring an inter-frequency neighboring cell in RAN sharing with
common carrier
2012-03-28

107

Planning
If inter-frequency neighboring cells in RAN-sharing with common carrier are shared and
the operators are the same, the neighboring cells can be shared after the PLMN list of an
external cell is added. The commands are the same as those used for adding
intra-frequency neighboring cells.
If inter-frequency neighboring cells in RAN-sharing with common carrier are not shared,
the inter-frequency neighboring cells must be planned and configured. The number of
inter-frequency neighboring cells is fixed, and number of inter-frequency neighboring
cells configured for each operator depends on actual requirements. The number of
inter-frequency neighboring cells can be divided by the number of operators. For
example, a cell can be configured with a maximum of 64 inter-frequency neighboring
cells. If two operators share a network, each one is configured with 32 neighboring cells.
3.
Inter-RAT Neighboring Cell Configuration in RAN Sharing with Common Carrier
Configuring a UTRAN inter-RAT neighboring cell
Figure 4-8 shows the procedure for configuring a UTRAN inter-RAT neighboring cell in
RAN sharing with common carrier.
Figure 4-8 Procedure for configuring a UTRAN inter-RAT neighboring cell in RAN sharing with
common carrier
2012-03-28
Configuring a GERAN inter-RAT neighboring cell

108

Planning
Figure 4-9 shows the procedure for configuring a GERAN inter-RAT neighboring cell in
Figure 4-9 Procedure for configuring a GERAN inter-RAT neighboring cell in RAN sharing with
common carrier
Configuring a CDMA2000 inter-RAT neighboring cell
Figure 4-10 shows the procedure for configuring a CDMA2000 inter-RAT neighboring cell in
2012-03-28

109

Planning
Figure 4-10 Procedure for configuring a CDMA2000 inter-RAT neighboring cell in RAN sharing
with common carrier
If inter-RAT neighboring cells are shared and the operators are the same, the neighboring
cells can be shared after the PLMN list of an external cell is added.
If inter-RAT neighboring cells are shared, the inter-RAT neighboring cells must be
planned and configured separately. The number of inter-RAT neighboring cells is fixed,
and the configuration for each operator depends on actual requirements. The number of
inter-frequency neighboring cells can be divided by the number of operators. For
example, a cell can be configured with a maximum number of 64 Universal Mobile
Telecommunications System (UMTS) neighboring cells. If two operators share a
network, each one is configured with 32 neighboring cells.
Add the PLMN list of a UTRAN external cell by running the following command:
ADD UTRANEXTERNALCELLPLMN: UtranCellId=123, Mcc="460", Mnc="20",

ShareMcc="460", ShareMnc="01"
2012-03-28

110

Planning
Before configuring the PLMN list of a UTRAN external cell, you must configure the corresponding
UTRAN external cell.
Each UTRAN external cell can be configured with three PLMN lists of a UTRAN external cell.
UTRANCellId consists of the RNC ID (12 bits) and the Cell ID (16 bits). Therefore,
UTRANCellId is expressed in 28 bits.
Table 4-18 Parameters for adding the PLMN list of a UTRAN external cell
ID
Name
Description
UtranCel
lId
UTRAN cell ID
Meaning: Indicates the UTRAN cell ID. It uniquely

identifies a cell in a PLMN.
Unit: None
Mcc
Mobile country
code

UTRAN cell.
For example, if the MCC is 123 and the MNC is 45, then the
PLMN ID is 12345.
Unit: None
Mnc
Mobile network
code

UTRAN cell.
PLMN ID is 12345.
Unit: None
2012-03-28

111

Planning
ID
Name
Description
ShareMc
c
Share mobile
country code

UTRAN cell that is shared among multiple operators.
PLMN ID is 12345.
Unit: None
ShareMn
c
Share mobile
network code

UTRAN cell that is shared among multiple operators.
PLMN ID is 12345.
Unit: None
Add the PLMN list of a GERAN external cell by running the following command:
ADD GERANEXTERNALCELLPLMN: GeranCellId=15, Lac=12, Mcc="460",

Mnc="20", ShareMcc="460", ShareMnc="01"
2012-03-28

112

Planning
Before configuring the PLMN list of a GERAN external cell, you must configure the corresponding
GERAN external cell.
Each GERAN external cell can be configured with three PLMN lists of a GERAN external cell.
Table 4-19 Parameters for adding the PLMN list of a GERAN external cell
ID
Name
Description
GeranC
ellId
GERAN
cell ID
Meaning: Indicates the identity of the external GERAN cell. It

uniquely identifies a GERAN cell within a PLMN.
Unit: None
Lac
Location
area code
Meaning: Indicates the LAC of the external GERAN cell.

Unit: None
Mcc
Mobile
country
code
Meaning: Indicates the mobile country code of the external cell.

PLMN ID is 12345.
Unit: None
2012-03-28

113

Planning
ID
Name
Description
Mnc
Mobile
network
code
Meaning: Indicates the mobile network code of the external cell.

PLMN ID is 12345.
Unit: None
ShareM
cc
Share
mobile
country
code

GERAN cell that is shared among multiple operators.
PLMN ID is 12345.
Unit: None
ShareM
nc
Share
mobile
network
code

GERAN cell that is shared among multiple operators.
PLMN ID is 12345.
Unit: None
2012-03-28

114

Planning
ID
Name
Description
Add the PLMN list of a CDMA2000 external cell by running the following command:
ADD CDMA2000EXTERNALCELLPLMN: CellGlobalId="1234567890123456",

ShareMcc="460", ShareMnc="20"
Before configuring the PLMN list of a CDMA2000 external cell, you must configure a
corresponding CDMA2000 external cell.
Each CDMA2000 external cell can be configured with three PLMN lists of the CDMA2000 external
cell.
Table 4-20 Parameters for adding the PLMN list of a CDMA2000 external cell
ID
Name
Description
CellGloba
lId
Cell global ID
Meaning: Indicates the cell global ID of the external

CDMA2000 cell. It uniquely identifies a CDMA2000 cell
CellGlobalIdCDMA2000 IE defined in 3GPP 36.331 6.3.4.
Unit: None
ShareMcc
Share mobile
country code

CDMA2000 cell that is shared among multiple operators.
PLMN ID is 12345.
Unit: None
2012-03-28

115

Planning
ID
Name
Description
ShareMnc
Share mobile
network code

CDMA2000 cell that is shared among multiple operators.
PLMN ID is 12345.
Unit: None
4.4.2 Neighboring Cell Configuration in RAN Sharing with

Dedicated Carrier
The neighboring cell configuration in RAN sharing with dedicated carrier applies to the
scenario that operators use different frequencies and share only eNodeB hardware. The
neighboring cell configuration in RAN sharing with dedicated carrier does not affect
neighboring cell planning and configuration.
4.5 Script Preparation for Neighboring Cells in Batches

4.5.1 CME
At the initial deployment stage, provide data to radio network engineers based on the
Configuration Management Express (CME) Radio Network Planning (RNP) template
Configure neighboring cells when the site is deployed. For the inter-RAT neighboring cell
configuration, the CMEV200R011C00SPC200 supports only the GERAN network, and the
CMEV200R011C00SPC220 supports only the UTRAN network.
For details about the CME RNP template, see the following attachment.
2012-03-28

116

Planning
The template can be exported by using the CME according to the following steps.
1.
Enable the CME, and choose LTE Application > Export Data > Export Radio
Network Planing Data.
Figure 4-11 Exporting the RNP template (1)
2.
Select the appropriate network element (NE) version and corresponding NE, and put the
NE to the export area, as shown in the following figures.
2012-03-28

117

Planning
3.
2012-03-28
Select the NE or cell to be exported, and click Next, as shown in the following figure.

118

Planning
4.
2012-03-28
Select the items to be exported, and then click Next.

119

Planning
5.
2012-03-28
Select the file type and path.

120

Planning
6.
2012-03-28
The export is finished.

121

Planning
2012-03-28

122

Planning
4.5.2 EXCEL
At the optimization stage, when appropriate tools are unavailable, use Excel functions to
prepare the script. Use an ampersand (&) to put the contents together, as shown in the
following figure.
4.6 Script Execution in Batches on the M2000

Requirement of script preparation: Each script must be ended with two spaces, the site name
must be included in two braces, and the site name must be consistent with the site name on the
M2000. After completing the preparation, save the scripts in a .txt file, as shown in the
following figure.
The following steps show the procedure for executing scripts in batches on the M2000.
1.
2012-03-28
Choose Maintenance > Task Management.

123

Planning
Figure 4-17 Executing scripts in batches on the M2000 (1)
2.
Choose MML Script, enter a take name, and click Once.
3.
2012-03-28
Choose Run At Once, or choose the start time and then choose Run At Once.
124

Planning
4.
Find the prepared script, choose Reflect Result. An execution result is returned. You can
also choose Collateral or Serial to execute scripts.
2012-03-28

125

Planning
5.
Execute the script. An execution result is returned.
2012-03-28

126

Guide To LTE Neighboring Cell and X2 Interface Planning

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Guide To LTE Neighboring Cell and X2 Interface Planning

Transféré par

Droits d'auteur :

Formats disponibles

Guide to LTE Neighboring Cell

and X2 Interface Planning

HUAWEI TECHNOLOGIES CO., LTD.

Copyright Huawei Technologies Co., Ltd. 2012. All rights reserved.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Huawei Industrial Base

Huawei Proprietary and Confidential