Академический Документы
Профессиональный Документы
Культура Документы
eRAN3.0
Issue
06
Date
2013-02-27
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 the warranty of any kind, express or implied.
Website:
http://www.huawei.com
Email:
support@huawei.com
eRAN
ANR Management
Contents
Contents
1 Introduction ................................................................................................................................1-1
1.1 Scope ............................................................................................................................................ 1-1
1.2 Intended Audience......................................................................................................................... 1-1
1.3 Change History.............................................................................................................................. 1-1
Issue 06 (2013-02-27)
eRAN
ANR Management
Contents
8 X2 Self-Setup..............................................................................................................................8-1
8.1 Overview ....................................................................................................................................... 8-1
8.2 X2 Self-Setup in X2 over S1 Mode ............................................................................................... 8-2
8.3 X2 Self-Setup in X2 over M2000 Mode ......................................................................................... 8-4
11 Engineering Guidelines.......................................................................................................11-1
11.1 When to Use ANR ..................................................................................................................... 11-1
11.1.1 Intra-RAT ANR .................................................................................................................. 11-1
Issue 06 (2013-02-27)
ii
eRAN
ANR Management
Contents
Issue 06 (2013-02-27)
iii
eRAN
ANR Management
Contents
12 Parameters .............................................................................................................................12-1
13 Counters..................................................................................................................................13-1
14 Glossary ..................................................................................................................................14-1
15 Reference Documents .........................................................................................................15-1
Issue 06 (2013-02-27)
iv
eRAN
ANR Management
1 Introduction
1 Introduction
1.1 Scope
This document describes the Automatic Neighbor Relation (ANR) management feature in terms of
implementation principles, parameter adjustments, feature dependencies, network impact, and
engineering guidelines.
The ANR management feature involves the following optional features:
Any managed objects (MOs), parameters, alarms, or counters described in this document correspond to
the software release delivered with this document. In the event of updates, the updates will be described
in the product documentation delivered with the latest software release.
Personnel who work with Huawei Long Term Evolution (LTE) products
Feature change: refers to a change in the ANR management feature of a specific product version.
Editorial change: refers to a change in wording or the addition of information that was not described in
the earlier version.
Document Issues
The document issues are as follows:
06 (2013-02-27)
05 (2012-12-29)
04 (2012-09-20)
03 (2012-06-30)
02 (2012-05-11)
01 (2012-03-30)
Draft A (2012-01-10)
06 (2013-02-27)
Compared with issue 05 (2012-12-29) of eRAN3.0, issue 06 (2013-02-27) of eRAN3.0 includes the
following changes.
Change Type
Change Description
Parameter Change
Feature change
None
None
Issue 06 (2013-02-27)
1-1
eRAN
ANR Management
1 Introduction
Change Type
Change Description
Parameter Change
Editorial change
05 (2012-12-29)
Compared with issue 04 (2012-09-20) of eRAN3.0, issue 05 (2012-12-29) of eRAN3.0 includes the
following changes.
Change Type
Change Description
Feature change
Editorial change
Parameter Change
None
04 (2012-09-20)
Compared with issue 03 (2012-06-30) of eRAN3.0, issue 04 (2012-09-20) of eRAN3.0 includes the
following changes.
Change Type
Change Description
Parameter Change
Feature change
None
None
Editorial change
03 (2012-06-30)
Compared with issue 02 (2012-05-11) of eRAN3.0, issue 03 (2012-06-30) of eRAN3.0 includes the
following changes.
Issue 06 (2013-02-27)
1-2
eRAN
ANR Management
1 Introduction
Change Type
Change Description
Feature change
Parameter Change
Added the
ENodeBAlgoSwitch.RanSharingAnrSwitch
For details about the principles, see parameter.
chapter 6 "ANR with Shared Cells."
For details about the impact on the
network, see section 10.3 "ANR with
Shared Cells."
For details about engineering
guidelines, see chapter 11
"Engineering Guidelines."
Revised some descriptions. For
None
details, see section 7.3.1 "Configuring
an HO Blacklist."
Editorial change
02 (2012-05-11)
Compared with issue 01 (2012-03-30) of eRAN3.0, issue 02 (2012-05-11) of eRAN3.0 includes the
following changes.
Change Type
Change Description
Parameter Change
Feature change
None
None
Editorial change
None
01 (2012-03-30)
This is the first official release.
Compared with draft A (2012-01-10) of eRAN3.0, issue01 (2012-03-30) of eRAN3.0 includes the
following changes.
Change Type
Change Description
Parameter Change
Feature change
None
None
Editorial change
None
Draft A (2012-01-10)
Compared with draft A (2011-07-15) of eRAN2.2, draft A (2012-01-10) of eRAN3.0 includes the following
changes.
Change Type
Change Description
Parameter Change
Feature change
Removed TempNRTs.
None
Issue 06 (2013-02-27)
1-3
eRAN
ANR Management
Change Type
1 Introduction
Change Description
Parameter Change
ANR.StatisticPeriodForNRTDel
ANR.StatisticNumForNRTDel
Editorial change
None
None
Issue 06 (2013-02-27)
1-4
eRAN
ANR Management
2 Overview of ANR
2 Overview of ANR
Operation and maintenance (OM) of the radio access network has become increasingly complex,
difficult, and costly because of the large number of network elements, the implementation of different
system standards, and the coexistence of different equipment vendors and telecom operators. To
address this situation, the self-organizing network (SON) concept is proposed. The main functions of
SON are self-configuration, self-optimization, and self-healing.
ANR is a self-optimization function. It automatically maintains the integrity and effectiveness of neighbor
cell lists (NCLs) and neighbor relation tables (NRTs) to increase handover success rates and improve
network performance. In addition, ANR does not require manual intervention, which reduces the costs of
network planning and optimization.
Neighbor relations are classified as normal and abnormal. Abnormal neighbor relations exist in the
cases of missing neighboring cells, physical cell identifier (PCI) conflicts, abnormal neighboring cell
coverage, and unstable neighbor relations. ANR automatically detects missing neighboring cells, PCI
conflicts, and abnormal neighboring cell coverage, and maintains neighbor relations.
Based on neighbor relations, ANR is classified into intra-RAT ANR and inter-RAT ANR. Based on the
methods of measuring neighboring cells, ANR is classified into event-triggered ANR and fast ANR (also
known as periodic ANR). RAT is short for radio access technology. Figure 2-1 shows ANR
classifications.
Figure 2-1 ANR classifications
Intra-RAT ANR handles neighbor relations with E-UTRAN cells, while inter-RAT ANR handles neighbor
relations with GERAN, UTRAN, and CDMA2000 cells. Here, UTRAN, E-UTRAN, GERAN, and
CDMA2000 are short for universal terrestrial radio access network, evolved UTRAN, GSM/EDGE radio
access network, and code division multiple access 2000, respectively.
To implement ANR, the eNodeB collaborates with UEs and the M2000.
Issue 06 (2013-02-27)
2-1
eRAN
ANR Management
3.2 NCL
The NCLs of an eNodeB contain information about the external cells of the eNodeB. The external cells of
an eNodeB are provided by base stations other than the eNodeB.
NCLs are classified into intra-RAT NCLs and inter-RAT NCLs. Each eNodeB has one intra-RAT NCL and
multiple inter-RAT NCLs.
The intra-RAT NCL records the ECGIs, PCIs, and E-UTRA absolute radio frequency channel numbers
(EARFCNs) of the external E-UTRAN cells.
The GERAN NCL records the cell IDs, base transceiver station identity codes (BSICs), and ARFCNs
of the external GERAN cells.
The UTRAN NCL records the cell IDs, scrambling codes, and UTRA ARFCNs (UARFCNs) of the
external UTRAN cells.
The CDMA2000 NCL records the cell IDs, frequencies, and PCIs of the external CDMA2000 cells.
NCLs are used as a basis for creating neighbor relations. The eNodeB adds newly detected external
cells to NCLs. External cells can be automatically managed (for example, added, deleted, or modified)
by ANR.
3.3 NRT
The NRTs of a cell contain information about the neighbor relations between a cell and its neighboring
cells. NRTs are classified into intra-RAT NRTs and inter-RAT NRTs. Each cell has one intra-RAT
intra-frequency NRT, one intra-RAT inter-frequency NRT, and multiple inter-RAT NRTs. The intra-RAT
intra-frequency NRT and intra-RAT inter-frequency NRT are referred to as the intra-RAT NRT in this
document.
Table 3-1 shows an example of the NRT. The information in this table is for reference only.
Table 3-1 An example of the NRT
SN
LCI
eNodeB ID
Cell ID
LCI#1
46001
eNodeB ID#1
Cell ID#1
Prohibited
Prohibited
LCI#1
46001
eNodeB ID#2
Cell ID#2
Allowed
Allowed
LCI#1
46001
eNodeB ID#3
Cell ID#3
Prohibited
Prohibited
NOTE
For details about the NRT, see 3GPP TS 36.300. Huawei NRT does not include the attribute that controls whether to allow
X2 setup.
NRT structures are the same for intra- and inter-eNodeB neighbor relations. Intra-eNodeB neighbor relations only exist in
NRTs, not in NCLs.
Issue 06 (2013-02-27)
3-1
eRAN
ANR Management
The NRT in Table 3-1 is an intra-RAT NRT. An inter-RAT NRT differs greatly from an intra-RAT NRT.
The NRT contains the following information, which can be updated automatically or manually:
Local cell identifier (LCI): uniquely identifies the source cell in a neighbor relation. This attribute is
defined by Cell.LocalCellId.
Target cell PLMN: identifies the PLMN of the operator that owns the target cell.
eNodeB ID: identifies the eNodeB that provides the target cell.
Removal control: indicates whether a neighbor relation can be removed from the NRT by ANR. By
default, this attribute is set to allow removal. It can also be set to prohibit removal.
Handover control: indicates whether this neighbor relation can be used for a handover. By default, this
attribute is set to allow handover. It can also be set to prohibit removal.
NRTs can be managed (for example, added, deleted, or modified) automatically by ANR.
NOTE
eRAN3.0 eNodeBs maintain only NRTs, whereas eNodeBs of earlier versions maintain both NRTs and TempNRTs.
3.4 Blacklists
3.4.1 HO Blacklist
An HO blacklist contains the information about neighbor relations that cannot be used for a handover or
removed automatically from the NRT by ANR. The neighbor relations in the HO blacklist must meet the
following conditions:
A neighbor relation can be added to the HO blacklist manually. For details, see 3GPP TS 32.511.
3.4.2 X2 Blacklist
An X2 blacklist contains information about the neighboring eNodeBs with which the local eNodeB is not
allowed to set up X2 interfaces. If an X2 interface has been set up between the local eNodeB and a
neighboring eNodeB on the X2 blacklist, the interface will be removed automatically.
NOTE
To remove an X2 interface, the eNodeB removes the X2 logical connection but retains the configuration data for the X2
interface. This ensures that the configuration data is not lost due to exceptions such as misoperations.
3.5 Whitelist
3.5.1 HO Whitelist
An HO whitelist contains the information about neighbor relations that can be used for a handover but
cannot be removed automatically from the NRT by ANR. The neighbor relations in the HO whitelist must
meet the following conditions:
Issue 06 (2013-02-27)
3-2
eRAN
ANR Management
A neighbor relation can be added to the HO whitelist manually. For details, see 3GPP TS 32.511.
3.5.2 X2 Whitelist
An X2 whitelist contains information about the neighboring eNodeBs with which the local eNodeB has
set up X2 interfaces. These X2 interfaces cannot be removed automatically.
The coverage of neighboring cells may be abnormal in any of the following scenarios:
The antenna tilt or orientation changes because of improper installation or a natural phenomenon such
as strong wind.
In mountainous terrain, the signals of the umbrella cell cover lower cells.
Issue 06 (2013-02-27)
Applicability
Yes
3-3
eRAN
ANR Management
Indicator
Index
16
N/A
Applicability
Yes
NOTE
17
18
19
NOTE
In the preceding table, if an Applicability cell is marked with Yes, the functions mentioned in the Supported Functions
(When the Indicator Is Set to 1) cell have been implemented and successfully tested on the eNodeB.
Issue 06 (2013-02-27)
3-4
eRAN
ANR Management
4 Intra-RAT ANR
4 Intra-RAT ANR
4.1 Overview
This chapter describes the optional feature LOFD-002001 Automatic Neighbour Relation (ANR).
Intra-RAT ANR is classified into intra-RAT event-triggered ANR and intra-RAT fast ANR. Intra-RAT
event-triggered ANR detects missing neighboring cells by using event-triggered UE measurements or
UE history information. In addition, it detects abnormal neighboring cell coverage and maintains
neighbor relations. For details, see section 4.2 "Intra-RAT Event-triggered ANR".
Based on the reporting of periodic UE measurements, intra-RAT fast ANR obtains information about all
possible intra-RAT neighboring cells before a handover is performed. This reduces the negative effects
of event-triggered UE measurements on handover performance. For details, see section 4.3 "Intra-RAT
Fast ANR."
PCI
ECGI
Cell A
17
Cell B
19
Issue 06 (2013-02-27)
4-1
eRAN
ANR Management
4 Intra-RAT ANR
Figure 4-1 shows how the eNodeB detects cell B by using event-triggered UE measurements.
Figure 4-1 Procedure for detecting a missing intra-RAT neighboring cell by using event-triggered UE
measurements
The UE performs intra-frequency neighboring cell measurements by default. When a UE establishes radio bearers, the
eNodeB delivers by default the intra-frequency neighboring cell measurement configuration to the UE by using the RRC
Connection Reconfiguration message. Therefore, if the UE needs to perform inter-frequency neighboring cell
measurements, the eNodeB must deliver the inter-frequency neighboring cell measurement configuration to the UE and
activate the measurement gap mode. For details about intra- and inter-frequency handover measurements, see Mobility
Management in Connected Mode Feature Parameter Feature.
2. The UE detects that the PCI of cell B meets the measurement requirements, and reports the PCI to
the source eNodeB. Note that the UE does not report the PCIs of the neighboring cells in the RRC
blacklist to the eNodeB.
3. The source eNodeB checks whether its intra-RAT NCL includes the PCI of cell B. If so, the procedure
ends. If not, the source eNodeB sends the measurement configuration to the UE, instructing the UE
to read the ECGI, tracking area code (TAC), and PLMN ID list of cell B.
4. The source eNodeB allows the UE to read these parameters over the broadcast channel (BCH).
NOTE
The maximum time that a UE can spend on ECGI reading is controlled by timer T321. The following table defines T321 as
quoted directly from 3GPP TS 36.331.
Issue 06 (2013-02-27)
4-2
eRAN
ANR Management
4 Intra-RAT ANR
Timer
Start
Stop
At Expiry
T321
UE history information defined in 3GPP TS 36.413 is the information about the cells that provided services for the UE. The
information contains:
Figure 4-2 Procedure for detecting a missing neighboring cell based on UE history information
Issue 06 (2013-02-27)
4-3
eRAN
ANR Management
4 Intra-RAT ANR
4. The M2000 queries the PCI, TAC, and PLMN ID list of cell A based on the reported ECGI and sends
the parameters to the target eNodeB.
The target eNodeB adds cell A to the intra-RAT NCL of the target eNodeB.
NOTE
eRAN3.0 eNodeBs do not manage TempNRTs. Therefore, upon detecting a missing neighboring cell by using
event-triggered UE measurements or using UE history information, an eRAN3.0 eNodeB adds this neighbor relation
directly to the NRT. For details about how NRTs are maintained, see section 4.2.2 "Automatic Maintenance of NCLs and
NRTs."
During intra-RAT neighbor relation addition through ANR, attributes that cannot be obtained through measurement reports
or UE history information use default values.
The eNodeB automatically adds a cell to an NCL in either of the following cases:
The
The
The eNodeB automatically removes an external cell from an NCL if the following conditions are all met:
The
The
measurement period, which equals four times the value of ANR.StatisticPeriodForNRTDel, has
elapsed.
The
NRTs of all cells under the local eNodeB do not contain any neighbor relations with this external
cell.
No
X2 interface has been set up between the local eNodeB and the eNodeB of this external cell.
The eNodeB automatically adds a neighbor relation to an NRT if the eNodeB detects a missing
neighboring cell based on UE measurements, receives information about this cell, and adds this
information to the NCL.
Issue 06 (2013-02-27)
4-4
eRAN
ANR Management
4 Intra-RAT ANR
The eNodeB automatically removes a neighbor relation (for example, with cell A) from an NRT if the
IntraRatAnrAutoDelSwitch check box under the ENodeBAlgoSwitch.AnrSwitch parameter is
selected, the removal control flag is set to allow removal, and either of the following criteria is met:
Criterion 1, which includes the following two conditions:
Within
In
the same measurement period, cell A's PCI has never been included in any handover
measurement reports in the same measurement period.
In
the same measurement period, the handover success rate is less than or equal to the value of
ANR.DelCellThd.
Note that when conditions in criterion 2 are met, not only is the neighbor relation with cell A removed
from the NRT, but also information about cell A is removed from the NCL.
The algorithm for automatically detecting abnormal neighboring cell coverage requires that the longitudes and latitudes of
the associated eNodeBs and sectors be accurately set and that the settings have taken effect. If the longitudes and
latitudes are not set or the settings do not meet the requirement, the detection results may not be accurate.
4-5
eRAN
ANR Management
4 Intra-RAT ANR
Issue 06 (2013-02-27)
4-6
eRAN
ANR Management
4 Intra-RAT ANR
Process
Figure 4-3 shows an intra-RAT fast ANR process.
Figure 4-3 Intra-RAT fast ANR process
Issue 06 (2013-02-27)
4-7
eRAN
ANR Management
4 Intra-RAT ANR
cells.
The
number
of
UEs
that
can
ANR.FastAnrIntraRatMeasUeNum parameter.
be
selected
is
specified
by
the
the PCI of an unknown cell is reported, the eNodeB adds the information of this cell to the NCL,
sets the number of UEs that have performed measurements in the check period to 0, and then
selects UEs to perform measurements. The number of UEs that can be selected is also specified by
the ANR.FastAnrIntraRatMeasUeNum parameter. Fast ANR does not select VoIP users to perform
fast ANR measurements.
If
no PCI is reported, the eNodeB proceeds to the end of the check period.
3. At the end of each check period, the eNodeB performs the following operations:
If
the total number of UEs involved in intra- and inter-frequency measurements exceeds the value of
ANR.FastAnrIntraRatUeNumThd, the eNodeB enters the monitoring state. In this state, the
eNodeB monitors whether the PCI of an unknown cell is reported in an event-triggered ANR
measurement report. If an unknown PCI is reported during the monitoring state, the eNodeB starts
fast ANR measurements again.
If
the total number of UEs involved in intra- and inter-frequency measurements is less than or equal
to the value of ANR.FastAnrIntraRatUeNumThd, the eNodeB directly starts the next round of fast
ANR measurements.
During a fast ANR procedure, after a UE reports the PCI of an unknown cell, the eNodeB will instruct the
UE to read the ECGI of the cell. After the UE reports the ECGI of the cell, the eNodeB adds the
information about this cell to the NCL. Then, after a successful handover from the serving cell to this cell,
the eNodeB adds the neighbor relation to the NRT. For details about automatic maintenance of NCLs
and NRTs, see section 4.2.2 "Automatic Maintenance of NCLs and NRTs."
respect to intra-frequency fast ANR, this process does not impact UE throughput, because the
UE does not need to listen to extra frequencies to perform intra-frequency measurements.
With
respect to inter-frequency or inter-RAT fast ANR, this process impacts UE throughput because
gap-assisted measurements are used. Two measurement gap patterns are defined in 3GPP TS
36.133: pattern 0 and pattern 1. They are described in Table 4-2. To accelerate measurements, patter
0 is used by default.
Gap Repetition
Period (Unit: ms)
Target RAT
40
FDD UTRAN
GERAN
CDMA2000 HRPD
CDMA2000 1X
Issue 06 (2013-02-27)
4-8
eRAN
ANR Management
4 Intra-RAT ANR
Measurement
Gap Pattern
Gap Repetition
Period (Unit: ms)
Target RAT
80
FDD UTRAN
GERAN
TDD LCR
CDMA2000 HRPD
CDMA2000 1X
CGI reading
This process impacts all fast ANR processes. To read the CGI of an unknown cell, the UE needs to
listen to system information block type 1 (SIB1) of the unknown cell to obtain the PLMN ID, CGI, and
TAC of the cell. After obtaining this information, the UE must report it to the local eNodeB. The reading
and reporting processes decrease UE throughput.
With respect to intra-frequency fast ANR, periodical PCI reporting does not impact system
performance, whereas CGI reading interrupts UE services.
With respect to inter-frequency and inter-RAT fast ANR, periodical PCI reporting impacts UE
throughput, and CGI reading interrupts UE services.
NOTE
For details about the process in which a UE reads the ECGI of a neighboring cell, see "Detecting Missing Neighboring
Cells by Using Event-triggered UE Measurements" in section 4.2.1 "Automatic Detection of Missing Neighboring Cells."
Issue 06 (2013-02-27)
4-9
eRAN
ANR Management
5 Inter-RAT ANR
5 Inter-RAT ANR
5.1 Overview
This chapter describes the optional feature LOFD-002002 Inter-RAT ANR.
Inter-RAT ANR is classified into inter-RAT event-triggered ANR and inter-RAT fast ANR.
Inter-RAT event-triggered ANR automatically detects missing neighboring inter-RAT cells by means of
event-triggered UE measurements. Inter-RAT fast ANR automatically detects missing neighboring cells
by instructing UEs to perform periodic measurements. Inter-RAT fast ANR enables eNodeBs to collect
neighboring cell information before handovers. This, to some degree, protects handover performance
from the adverse effects of inter-RAT event-triggered ANR measurements by UEs during handovers.
Information about neighboring CDMA cells can be collected only by inter-RAT fast ANR. CDMA cells include CDMA2000
High Rate Packet Data (HRPD) cells and CDMA2000 1x Radio Transmission Technology (CDMA2000 1xRTT) cells.
Inter-RAT ANR does not check for PCI conflicts and abnormal neighboring cell coverage because of the following
reasons:
The E-UTRAN has only a small number of standardized interfaces with other RATs.
Issue 06 (2013-02-27)
5-1
eRAN
ANR Management
5 Inter-RAT ANR
Figure 5-1 Procedure for detecting a missing inter-RAT neighboring cell by using event-triggered UE
measurements
For details about inter-RAT handover measurements, see Mobility Management in Connected Mode Feature Parameter
Feature.
2. The UE detects that cell B meets the measurement requirements and reports its scrambling code to
cell A. If the NCL of the source eNodeB includes the scrambling code of cell B, the procedure ends. If
the NCL of cell A does not include the scrambling code of cell B, the source eNodeB proceeds to the
next step.
3. The source eNodeB requests the UE to read the parameters of cell B. If cell B is a GERAN or UTRAN
cell, the parameters to be read are the CGI, location area code (LAC), and routing area code (RAC).
4. The source eNodeB schedules appropriate call gapping to allow the UE to read the CGI and other
parameters of cell B over the BCH.
5. The UE reports the CGI and other parameters of cell B to the source eNodeB.
The source eNodeB adds the newly detected neighboring cell to its inter-RAT NCL and adds the
neighbor relation to the inter-RAT NRT.
Issue 06 (2013-02-27)
5-2
eRAN
ANR Management
5 Inter-RAT ANR
To enable automatic removal of neighbor relations with UTRAN, GERAN, or CDMA2000, select the
UtranAutoNrtDeleteSwitch, GeranAutoNrtDeleteSwitch, or CdmaAutoNrtDeleteSwitch check box
under the ENodeBAlgoSwitch.AnrSwitch parameter. When a network is unstable or in the early stage
of deployment, you are advised to disable automatic removal by clearing these check boxes. The
purpose of disabling automatic removal is to prevent frequent NCL/NRT updates so the collection of
neighbor relations can be completed as quickly as possible. Information about the external cells of a RAT
can be removed from the NCL and neighbor relations with the RAT can be automatically removed from
the NRT only when the corresponding check box is selected.
NOTE
The eNodeB adds a detected external neighboring cell to an NCL if the eNodeB detects a missing
neighboring cell based on UE measurements and receives information about this cell (including the
CGI).
The eNodeB automatically removes an external cell from an NCL if all of the following conditions are
met:
The
The
measurement period, which equals four times the value of ANR.StatisticPeriodForNRTDel, has
elapsed.
The
NRTs of all cells under the local eNodeB do not contain any neighbor relations with this external
cell.
The eNodeB automatically adds a neighbor relation to an NRT if the eNodeB detects a missing
neighboring cell based on UE measurements, receives information about this cell, and adds this
information to the NCL.
The eNodeB automatically removes a neighbor relation from an NRT when the corresponding check
box under the ENodeBAlgoSwitch.AnrSwitch parameter is selected and all of the following
conditions are met:
The
number of neighbor relations in the NRT has reached the maximum specification and a new
neighbor relation is to be added to the NRT.
Within
Automatic removal of neighbor relations with CDMA2000 is not yet a requirement; therefore, it is not implemented in
eRAN3.0.
Issue 06 (2013-02-27)
5-3
eRAN
ANR Management
5 Inter-RAT ANR
The signal quality threshold used to determine whether to periodically report a neighboring cell's PCI is
determined by the ANR.FastAnrRsrpThd parameter in intra-RAT fast ANR and by the following
parameters in inter-RAT fast ANR.
Target RAT
UTRAN
ANR.FastAnrRscpThd
GERAN
ANR.FastAnrRssiThd
CDMA2000 1xRTT
ANR.FastAnrCdma1xrttPilotThd
CDMA2000 HRPD
ANR.FastAnrCdmahrpdPilotThd
The upper limit on the number of concurrent UEs involved in fast ANR measurements is specified by
the ANR.FastAnrInterRatMeasUeNum parameter in inter-RAT fast ANR and by the
ANR.FastAnrIntraRatMeasUeNum parameter in intra-RAT fast ANR.
The upper limit on the total number of concurrent UEs involved in fast ANR measurements is specified
by the ANR.FastAnrInterRatUeNumThd parameter in inter-RAT fast ANR and by the
ANR.FastAnrIntraRatUeNumThd parameter in intra-RAT fast ANR.
Inter-RAT fast ANR has the same impact on network performance as intra-RAT fast ANR. For details,
see section 4.3 "Intra-RAT Fast ANR."
Issue 06 (2013-02-27)
5-4
eRAN
ANR Management
eRAN3.0 does not support ANR with shared UTRAN or GERAN cells.
Issue 06 (2013-02-27)
6-1
eRAN
ANR Management
Figure 6-1 Procedure for detecting a missing neighboring cell based on UE history information
NOTE
If serving cells and neighboring cells are not managed by the same the NMS, the PLMN round function and ANR functions
are mutually exclusive when ENodeBSharingMode.EnodeBSharingMode is set to SHARED_FREQ.
If the UE reports the PLMN list of the neighboring cell, the serving eNodeB starts a normal ANR
procedure.
After the UE reports the CGI and PLMN list to the serving eNodeB, the serving eNodeB adds the
information about the missing neighboring cell to the intra-RAT NCL and NRT and adds the PLMN
information to the PLMN list configurations.
If the UE does not report the PLMN list of the neighboring cell, the serving eNodeB adds the
information about the missing neighboring cell to the intra-RAT NCL and NRT and reports the CGI
obtained by the UE to the M2000. The M2000 queries the PLMN list of the neighboring cell and sends
the query result to the serving eNodeB. The serving eNodeB adds the PLMN information to the PLMN
list configurations.
If the eNodeB detects a missing neighboring cell based on the UE history information, the eNodeB adds
the neighboring cell according to the same procedure described in section 6.1 "Shared Neighboring Cell
Broadcasting PLMN List in an RR Manner."
Issue 06 (2013-02-27)
6-2
eRAN
ANR Management
EutranIntraFreqNCell
EutranInterFreqNCell
UTRAN cell
UtranNCell
GERAN cell
GeranNcell
Cdma20001XRTTNcell
Cdma2000HrpdNcell
For details, see Mobility Management in Connected Mode Feature Parameter Description.
If ANR is activated, neighbor relations are added or removed automatically.
Issue 06 (2013-02-27)
7-1
eRAN
ANR Management
Step 4 Set both Deletion Prohibited and Handover Prohibited to TRUE in the displayed Set dialog
box.
----End
Alternatively, to blacklist a neighbor relation, you can set the EutranInterFreqNCell.NoHoFlag
parameter to FORBID_HO_ENUM and the EutranInterFreqNCell.NoRmvFlag parameter to
FORBID_RMV_ENUM. Depending on the neighbor relation type, these two parameters belong to
different MOs:
For a neighbor relation with an intra-frequency E-UTRAN cell, they belong to the
EutranIntraFreqNCell MO.
For a neighbor relation with an inter-frequency E-UTRAN cell, they belong to the
EutranInterFreqNCell MO.
For a neighbor relation with a UTRAN cell, they belong to the UtranNCell MO.
For a neighbor relation with a GERAN cell, they belong to the GeranNcell MO.
For a neighbor relation with a CDMA2000 HRPD cell, they belong to the Cdma2000HrpdNCell MO.
For a neighbor relation with a CDMA2000 1xRTT cell, they belong to the Cdma20001XRTTNCell MO.
To remove an X2 interface, the eNodeB removes the X2 logical connection but retains the configuration data for the X2
interface. This ensures that the configuration data is not lost due to exceptions such as misoperations.
X2 blacklists can be configured as required by operators. For example, X2 setup between different base
station models is prohibited.
To configure an X2 blacklist, perform the following steps:
Step 1 Log in to the M2000.
Step 2 Choose Configuration > LTE Self Optimization > ANR Management.
Step 3 Click the X2 Management tab on the ANR Management tab page.
----End
Alternatively, you can use the X2BlackWhiteList MO to configure an X2 blacklist.
Issue 06 (2013-02-27)
7-2
eRAN
ANR Management
For a neighbor relation with an intra-frequency E-UTRAN cell, they belong to the
EutranIntraFreqNCell MO.
For a neighbor relation with an inter-frequency E-UTRAN cell, they belong to the
EutranInterFreqNCell MO.
For a neighbor relation with a UTRAN cell, they belong to the UtranNCell MO.
For a neighbor relation with a GERAN cell, they belong to the GeranNcell MO.
For a neighbor relation with a CDMA2000 HRPD cell, they belong to the Cdma2000HrpdNCell MO.
For a neighbor relation with a CDMA2000 1xRTT cell, they belong to the Cdma20001XRTTNCell MO.
Issue 06 (2013-02-27)
7-3
eRAN
ANR Management
Step 3 Click the X2 Management tab on the ANR Management tab page.
----End
Alternatively, you can use the X2BlackWhiteList MO to configure an X2 whitelist.
Issue 06 (2013-02-27)
7-4
eRAN
ANR Management
8 X2 Self-Setup
8 X2 Self-Setup
8.1 Overview
This chapter describes the principles of X2 self-setup, which is implemented by the optional feature
LOFD-002004 Self-configuration.
In E-UTRAN, X2 interfaces exist between neighboring eNodeBs. The X2 interfaces allow some
messages to be directly exchanged between neighboring eNodeBs, which meets the requirements of a
flat LTE network architecture.
An X2 interface can be set up in either link configuration mode or end point configuration mode. Figure
8-1 shows the classifications of X2 setup modes.
Figure 8-1 X2 setup modes
The eNodeB can set up an X2 interface based on the X2eNodeB MO. One X2eNodeB MO is used
to set up one X2 interface; therefore, multiple X2eNodeB MOs are required to set up multiple X2
interfaces.
X2
If X2eNodeB is not manually configured, the eNodeB can set up an X2 interface in X2 over S1 or X2
over M2000 mode. The mode is specified by the GlobalProcSwitch.X2SonLinkSetupType
parameter.
Issue 06 (2013-02-27)
8-1
eRAN
ANR Management
8 X2 Self-Setup
Both self-setup modes require that neighboring cell information be configured and that the X2
self-setup switch (specified by the GlobalProcSwitch.X2SonSetupSwitch parameter) be set to
ON(On). After a handover is triggered, the source eNodeB and target eNodeB can obtain the
configuration information about each other. Based on the information, the X2 interface between the
two eNodeBs is automatically set up.
NOTE
X2 self-setup reduces configuration operations by users. Users need only to configure the local IP addresses of each
eNodeB. An eNodeB automatically obtains the IP addresses of the peer eNodeB and sets up an X2 interface to the peer
eNodeB. This document describes two X2 self-setup modes: X2 over S1 and X2 over M2000. For details about other
modes, see S1/X2/OM Channel Management Feature Parameter Description, which also includes descriptions about X2
self-setup in IPSec-enabled scenarios.
When ENodeBSharingMode.ENodeBSharingMode is set to SHARED_FREQ, the neighboring eNodeB PLMN over the
X2 interface is the primary operator PLMN of the neighboring eNodeB.
When ENodeBSharingMode.ENodeBSharingMode is set to SEPARATED_FREQ, the neighboring eNodeB PLMN over
the X2 interface is the same as the PLMN when ENodeBSharingMode.ENodeBSharingMode is set to INDEPENDENT.
Issue 06 (2013-02-27)
8-2
eRAN
ANR Management
8 X2 Self-Setup
If
the X2 interface is unavailable, an S1-based handover is performed. At the same time, the source
eNodeB triggers X2 self-setup in X2 over S1 mode. The procedure goes to step 2.
2. The source eNodeB sends an eNodeB Configuration Transfer message to the MME. The message
contains the following information:
Source
eNodeB ID, which consists of the global eNodeB ID and the selected tracking area identifier
(TAI)
Target
eNodeB ID, which consists of the global eNodeB ID and the selected TAI
Control-plane
Issue 06 (2013-02-27)
8-3
eRAN
ANR Management
8 X2 Self-Setup
3. The MME sends an MME Configuration Transfer message to the target eNodeB. This message
contains information about the source eNodeB. (For details about contents in the message, see
3GPP TS 36.413.)
4. After receiving the control-plane and user-plane IP addresses of the source eNodeB, the target
eNodeB uses these IP addresses and its own control-plane and user-plane IP addresses to
configure an X2eNodeB MO and sets up control-plane and user-plane bearers for the X2 interface.
Then, the target eNodeB responds to the MME with an eNodeB Configuration Transfer message,
which contains the control-plane and user-plane IP addresses of the target eNodeB.
5. The MME sends an MME Configuration Transfer message to the source eNodeB. This message
contains the control-plane and user-plane IP addresses of the target eNodeB.
6. After receiving the control-plane and user-plane IP addresses of the target eNodeB, the source
eNodeB uses these IP addresses and its own control-plane and user-plane IP addresses to
configure an X2eNodeB MO and sets up control-plane and user-plane bearers for the X2 interface.
7. After signaling exchange over the S1 interface is complete, the source eNodeB sends an X2 setup
request to the target eNodeB and the target eNodeB responds to the request. An X2 interface is
automatically set up.
8. If a handover between the two eNodeBs is triggered after the X2 setup, the handover will be
performed through the X2 interface.
NOTE
In RAN sharing with dedicated carriers mode, control-plane and user-plane IP addresses are configured separately for
each operator, and therefore X2Interface and X2eNodeB MOs must also be separately configured for each operator.
In RAN sharing with common carriers mode, only one X2Interface MO needs to be configured, corresponding to the
primary operator. If the primary and secondary operators share user-plane IP addresses, only one X2eNodeB MO needs
to be configured. If the primary and secondary operators use different user-plane IP addresses, one X2eNodeB MO must
be configured for each operator.
Issue 06 (2013-02-27)
8-4
eRAN
ANR Management
8 X2 Self-Setup
If
the X2 interface is unavailable, an S1-based handover is performed. At the same time, the source
eNodeB triggers X2 self-setup in X2 over M2000 mode. The procedure goes to step 2.
2. The source eNodeB sends an X2 self-setup request to the M2000. The request message contains
the PLMN IDs and eNodeB IDs of the source and target eNodeBs.
3. After receiving the request, the M2000 searches for the configuration information (such as the X2
control-plane IP addresses and X2 user-plane IP addresses) about the source and target eNodeBs.
Based on the configuration information, the M2000 configures two X2eNodeB MOs.
4. The M2000 sends the X2eNodeB MO configurations to the source and target eNodeBs.
Issue 06 (2013-02-27)
8-5
eRAN
ANR Management
8 X2 Self-Setup
5. The source and target eNodeBs set up an SCTP link between them. The control plane on the X2
interface is set up.
6. After an X2-based handover is triggered, the source and target eNodeBs set up an IP path between
them. The user plane on the X2 interface is set up.
NOTE
The X2 over M2000 mode can be used only if the source and target eNodeBs are managed by the same M2000.
Issue 06 (2013-02-27)
8-6
eRAN
ANR Management
9 Related Features
9 Related Features
9.1 Intra-RAT ANR
9.1.1 Required Features
Intra-RAT ANR depends on the feature LBFD-002017 DRX. If ANR measurements need to be performed,
a temporary dedicated DRX cycle needs to be configured for the UE. During this cycle, the UE obtains
the CGIs of neighboring cells in sleep time. For details about DRX, see DRX Feature Parameter
Description.
9.3 X2 Self-Setup
9.3.1 Required Features
None
Issue 06 (2013-02-27)
9-1
eRAN
ANR Management
The UE throughput is unaffected during the process that the UE periodically measures intra-frequency
neighboring cells and reports the PCI of the neighboring cell with the highest signal quality.
UE reads the CGI and other information about an unknown cell during DRX periods. This drop
occurs because the UE cannot be scheduled during DRX periods.
The
Generally, the influence that fast ANR exerts over network performance is controllable and acceptable,
because of the upper limits on the number of UEs involved in fast ANR per cell and on the number of
periodic measurement reports by a UE within each period.
Intra-RAT ANR optimizes and manages intra-RAT neighbor relations, thereby reducing service drops
and handover failures caused by inappropriate neighbor relations. The gain that ANR brings to the
handover success rate and service drop rate cannot be provided here because many factors, such as
the number and distribution of ANR-capable UEs, will affect the handover success rate and service drop
rate.
The handover success rate and service drop rate are reflected by the following counters:
Issue 06 (2013-02-27)
10-1
eRAN
ANR Management
10.4 X2 Self-Setup
10.4.1 Impact on System Capacity
X2 self-setup has no impact on system capacity.
Issue 06 (2013-02-27)
10-2
eRAN
ANR Management
11 Engineering Guidelines
11 Engineering Guidelines
11.1 When to Use ANR
11.1.1 Intra-RAT ANR
Intra-RAT ANR consists of intra-RAT event-triggered ANR and intra-RAT fast ANR.
Use intra-RAT fast ANR when quick detection of neighbor relations is required, for example, in the early
stage of deployment or during network capacity expansion. Use intra-RAT event-triggered ANR to
supplement and optimize neighbor relations.
Network
capacity expansion or eNodeB relocation has occurred. In this situation, cells or eNodeBs
are removed from one place and added to another, which causes changes to neighbor relations.
Intra-RAT event-triggered ANR can effectively deal with these types of changes and achieve
optimization.
Intra-RAT
fast ANR is enabled. The neighboring cells detected using fast ANR are added to NCLs. To
use these neighboring cells for handovers, intra-RAT event-triggered ANR is required.
In the early stage of deployment, disable automatic removal of neighbor relations. This can prevent
stable neighbor relations from being removed simply because only a few handovers have been
performed.
Intra-RAT event-triggered ANR is not recommended if users want to manually manage neighbor
relations. In this situation, disable both intra-RAT event-triggered ANR and intra-RAT fast ANR.
Network
capacity expansion or eNodeB relocation has occurred. In this situation, cells or eNodeBs
are removed from one place and added to another, which causes changes to neighbor relations.
Intra-RAT fast ANR can effectively deal with these types of changes and achieve optimization.
network is well constructed and serves a moderate number of UEs, and basic neighbor relations
are configured.
Users
Issue 06 (2013-02-27)
11-1
eRAN
ANR Management
11 Engineering Guidelines
NOTE
If both event-triggered ANR and fast ANR are enabled, they separately detect missing neighboring cells by using their own
mechanisms.
Disable the function of ANR with shared cells under either of the following conditions:
The neighboring cells are shared by PLMNs, but the operators prefer manual maintenance of neighbor
relations to ANR.
In this situation, disable intra-RAT event-triggered ANR, intra-RAT fast ANR, and ANR with shared
cells.
11.1.4 X2 Self-Setup
X2 self-setup can be implemented in X2 over S1 or X2 over M2000 mode.
The operator has not planned X2 interfaces and hopes to use the X2 self-setup function to
automatically set up X2 interfaces.
You are advised to disable X2 self-setup in X2 over S1 mode when the operator prefers to manually
maintain X2 interfaces.
The operator has not planned X2 interfaces and hopes to use the X2 self-setup function to
automatically set up X2 interfaces.
You are advised to disable X2 self-setup in X2 over M2000 mode in the following cases:
Issue 06 (2013-02-27)
11-2
eRAN
ANR Management
11 Engineering Guidelines
Proportion and distribution of UEs that support intra-RAT ANR in the network
A UE supports intra-RAT ANR if it supports intra- or inter-frequency ANR.
Proportion and distribution of UEs that support inter-RAT ANR in the network
RAT (UTRAN, GERAN, or CDMA2000) that constructs inter-RAT networking with the E-UTRAN
Network configuration: whether RAN sharing and PLMN list broadcast in an RR manner are to be
enabled
For details about the network configuration, see RAN Sharing Feature Parameter Description.
Proportion and distribution of UEs that support intra-RAT ANR in the network
A UE supports intra-RAT ANR if it supports intra- or inter-frequency ANR.
11.2.4 X2 Self-Setup
Check whether the EPC or M2000 supports X2 self-setup.
Issue 06 (2013-02-27)
11-3
eRAN
ANR Management
11 Engineering Guidelines
UEs on the network support ANR-related measurements on intra- or inter-frequency neighboring cells
and are DRX-capable.
The intra-RAT measurement information (including frequencies to be measured) has been configured.
For details, see Mobility Management in Connected Mode Feature Parameter Description.
Operators have purchased and activated the license pertaining to intra-RAT ANR. Table 11-1 provides
the license control item.
Parameter ID
Source
Setting Description
Network plan
(negotiation not
required)
IntraRatEventAnrSwitch
IntraRatFastAnrSwitch
IntraRatAnrAutoDelSwitch
(Optional) The following table describes the parameters that must be set in the X2BlackWhiteList MO
to configure an X2 blacklist. Configure this MO based on operator requirements.
Parameter Parameter ID
Name
Source
Setting Description
Mobile
network
code
Network plan
This parameter specifies the mobile country code
(negotiation not (MCC) of the neighboring eNodeB at the other end
of this X2 interface.
X2BlackWhiteList. required)
Mcc
This parameter references the corresponding
parameter in the eNodeB MO on the neighboring
eNodeB.
Mobile
network
code
Network plan
This parameter specifies the mobile network code
(negotiation not (MNC) of the neighboring eNodeB at the other end
of this X2 interface.
X2BlackWhiteList. required)
Mnc
This parameter references the corresponding
parameter in the eNodeB MO on the neighboring
eNodeB.
Issue 06 (2013-02-27)
11-4
eRAN
ANR Management
Parameter Parameter ID
Name
eNodeB
identity
11 Engineering Guidelines
Source
Setting Description
Network plan
This parameter specifies the ID of the neighboring
(negotiation not eNodeB at the other end of this X2 interface. This
ID uniquely identifies an eNodeB in a network.
X2BlackWhiteList. required)
ENodeBId
This parameter references the corresponding
parameter in the eNodeB MO on the neighboring
eNodeB.
Network plan
This parameter specifies whether this X2 interface
X2 Black or
X2BlackWhiteList. (negotiation not is to be whitelisted or blacklisted.
White List
X2ListType
required)
Type
Set this parameter to X2_BLACK_LIST_TYPE.
11.5.4 Precautions
None
In the Object Group pane, find MOs in the navigation tree. This method applies to users who are
familiar with the navigation tree.
In the Search pane, search for an MO. This method applies to users who are unfamiliar with the
navigation tree.
Issue 06 (2013-02-27)
11-5
eRAN
ANR Management
11 Engineering Guidelines
For descriptions of the user-defined template and summary data file and also the detailed procedure for
configuring eNodeBs in batches, see eNodeB Initial Configuration Guide.
A user-defined template is recommended. The following table lists the recommended distribution of the
parameters in the template.
MO
Parameter
ENODEBALGOSWITCH
ENodeBAlgoSwitch
X2BLACKWHITELIST
X2BlackWhiteList
Signaling Tracing
Start a Uu interface tracing task on the M2000 client. Remove the configurations of some neighbor
relations so that there are missing neighboring cells within the network. If a UE reports an ECGI during
an intra-RAT handover according to the traced signaling, intra-RAT ANR has been activated.
Figure 11-1 Uu tracing result during activation observation for intra-RAT ANR
Issue 06 (2013-02-27)
11-6
eRAN
ANR Management
11 Engineering Guidelines
Step 1 On the M2000 client, choose Configuration > LTE Self Optimization > Query SON Log.
Select ANR Log from the Log Category drop-down list.
Step 2 In the Event Name list, select ANR Switch Setting, Add Neighbour Cell, Delete Neighbour
Cell, Add External Cell, and Delete External Cell one at a time to check different types of ANR
operations, as shown in Figure 11-2.
Figure 11-2 SON logs on the M2000 client
----End
MML Commands
The procedure for activation observation using MML commands is as follows:
Step 1 Run the LST EUTRANINTRAFREQNCELL command and the LST
EUTRANINTERFREQNCELL command to list parameters of neighbor relations with intra- and
inter-frequency E-UTRAN cells, respectively.
Step 2 In the command outputs, check the value of ANR flag.
----End
11.5.8 Reconfiguration
None
11.5.9 Deactivation
Step 1 Run the MOD ENODEBALGOSWITCH command to disable intra-RAT ANR.
Step 2 (Optional) Run the RMV X2BLACKWHITELIST command to remove an X2 blacklist or whitelist.
----End
Issue 06 (2013-02-27)
11-7
eRAN
ANR Management
11 Engineering Guidelines
UEs on the network support ANR-related measurements on inter-RAT neighboring cells and are
DRX-capable.
The inter-RAT measurement information (including frequencies to be measured) has been configured.
For details, see Mobility Management in Connected Mode Feature Parameter Description.
Operators have purchased and activated the license pertaining to inter-RAT ANR. Table 11-2 provides
the license control item.
Inter-RAT ANR
Parameter ID
Source
ANR
algorithm
switch
AnrSwitch
Setting Description
UtranFastAnrSwitch
UtranAutoNrtDeleteSwitch
GeranEventAnrSwitch
GeranFastAnrSwitch
GeranAutoNrtDeleteSwitch
CdmaFastAnrSwitch
CdmaAutoNrtDeleteSwitch
The following table describes the parameter that must be set in the DRX MO to configure the long DRX
cycle that is specific for inter-RAT ANR.
Issue 06 (2013-02-27)
11-8
eRAN
ANR Management
Parameter
Name
Parameter ID
11 Engineering Guidelines
Source
Setting Description
Long DRX
LongDRXCyclefo Network plan Set this parameter based on the networking mode
Cycle for
rIRatAnr
(negotiation not collected in section 11.2 "Information to Be
Inter-RAT ANR
required)
Collected".
11.6.4 Precautions
None
In the Object Group pane, find MOs in the navigation tree. This method applies to users who are
familiar with the navigation tree.
In the Search pane, search for an MO. This method applies to users who are unfamiliar with the
navigation tree.
Issue 06 (2013-02-27)
11-9
eRAN
ANR Management
11 Engineering Guidelines
For descriptions of the user-defined template and summary data file and also the detailed procedure for
configuring eNodeBs in batches, see eNodeB Initial Configuration Guide.
A user-defined template is required. The following table lists the recommended distribution of the
parameters in the template.
MO
Parameter
ENODEBALGOSWITCH
ENodeBAlgoSwitch
11.6.8 Reconfiguration
None
11.6.9 Deactivation
Run the MOD ENODEBALGOSWITCH command to disable inter-RAT ANR.
UEs on the network support ANR-related measurements on intra- or inter-frequency neighboring cells
and are DRX-capable.
The intra-RAT measurement information (including frequencies to be measured) has been configured.
For details, see Mobility Management in Connected Mode Feature Parameter Description.
Issue 06 (2013-02-27)
11-10
eRAN
ANR Management
11 Engineering Guidelines
Source
Setting Description
ANR Under RAN ENodeBAlgoSwitc Network plan Set the following switches under the
Sharing Algorithm h.RanSharingAnrS (negotiation not ENodeBAlgoSwitch.RanSharingAnrSwitch
Switch
witch
required)
parameter:
NBSLTEPLMNRoundSwitch
NBSLTERANSharingSwitch
11.7.4 Precautions
None
In the Object Group pane, find MOs in the navigation tree. This method applies to users who are
familiar with the navigation tree.
In the Search pane, search for an MO. This method applies to users who are unfamiliar with the
navigation tree.
Fill in the summary data file with the name of the user-defined template.
The parameter settings in the user-defined template will be applied to the eNodeBs after you import
the summary data file into the CME.
----End
For descriptions of the user-defined template and summary data file and also the detailed procedure for
configuring eNodeBs in batches, see eNodeB Initial Configuration Guide.
Issue 06 (2013-02-27)
11-11
eRAN
ANR Management
11 Engineering Guidelines
A user-defined template is recommended. The following table lists the recommended distribution of the
parameters in the template.
MO
Parameter
ENodeBAlgoSwitch
ENodeBAlgoSwitch
11.7.8 Reconfiguration
None
11.7.9 Deactivation
Run the MOD ENODEBALGOSWITCH command to disable ANR with shared cells.
LOFD-002004 Self-configuration
Self-configuration
Issue 06 (2013-02-27)
11-12
eRAN
ANR Management
11 Engineering Guidelines
11.8.4 Precautions
None
Signaling Tracing
Signaling tracing can be used to check whether X2 self-setup in X2 over S1 mode has been activated.
Start an S1 interface tracing task on the M2000 client. If information about the source and target
eNodeBs (such as the PLMN IDs, eNodeB IDs, and IP addresses) is exchanged over the S1 interface,
then the self-setup has been activated. Figure 11-3 shows an example of S1 interface tracing related to
X2 self-setup.
Issue 06 (2013-02-27)
11-13
eRAN
ANR Management
11 Engineering Guidelines
----End
Issue 06 (2013-02-27)
11-14
eRAN
ANR Management
11 Engineering Guidelines
11.8.8 Reconfiguration
None
11.8.9 Deactivation
Run the MOD GLOBALPROCSWITCH command to deactivate X2 self-setup.
Monitoring
The current eRAN version has no performance counter related to intra-RAT ANR. Using intra-RAT ANR
decreases the probability that the configurations of neighboring cells are missing or incorrect, thereby
increasing the intra-RAT handover success rate and decreasing the service drop rate. To monitor the
performance of intra-RAT ANR, you can check the performance counters related to handovers and
service drops.
Parameter Optimization
The following parameters may need to be modified after intra-RAT ANR is activated.
Parameter
Name
Parameter ID
Setting Description
Issue 06 (2013-02-27)
11-15
eRAN
ANR Management
11 Engineering Guidelines
Parameter
Name
Parameter ID
Setting Description
Statistic cycle
ANR.StatisticPeriod
ANR.FastAnrRprtAmount
Issue 06 (2013-02-27)
11-16
eRAN
ANR Management
11 Engineering Guidelines
Parameter
Name
Parameter ID
Setting Description
ANR.FastAnrRprtInterval
ANR.FastAnrCheckPeriod
Fast ANR
checking period
ANR.FastAnrRsrpThd
Fast ANR
measurement
RSRP threshold
IntraRat Fast
ANR
measurement
UE number
IntraRat Fast
ANR.FastAnrIntraRatUeNumTh This parameter specifies the upper limit for the total
number of UEs involved in intra-RAT periodic
ANR valid
d
measurements. A larger parameter value results in
measurement
more UEs that are involved in intra-RAT periodic
min UE number
measurements. In this situation, the UEs involved
can be distributed more randomly throughout the
network, reducing the risk of the likelihood of missing
neighboring cells. However, a large parameter value
affects the service quality for these UEs and the
uplink throughput of the network.
Issue 06 (2013-02-27)
11-17
eRAN
ANR Management
11 Engineering Guidelines
Parameter
Name
Parameter ID
Setting Description
Optimization
Mode
ANR.OptMode
Monitoring
The current eRAN version has no performance counter related to inter-RAT ANR. Using inter-RAT ANR
decreases the probability that the configurations of neighboring cells are missing or incorrect, thereby
increasing the inter-RAT handover success rate and decreasing the service drop rate. To monitor the
performance of inter-RAT ANR, you can check the performance counters related to handovers and
service drops.
Parameter Optimization
The parameters that may require modification after inter-RAT ANR is used are almost the same as those
after intra-RAT ANR is used. The following table describes only the parameters that differ from those
used for intra-RAT ANR and are specifically used for inter-RAT ANR.
Parameter
Name
Parameter ID
InterRat Fast
ANR
measurement
UE number
Setting Description
InterRat Fast
ANR.FastAnrInterRatUeNumTh This parameter specifies the upper limit for the total
number of UEs involved in inter-RAT periodic
ANR valid
d
measurements. A larger parameter value results in
measurement
more UEs being involved in inter-RAT periodic
min UE number
measurements. In this situation, the UEs involved
can be distributed more randomly throughout the
network, reducing the risk of the likelihood of missing
neighboring cells. However, this affects the service
quality for these UEs and the uplink throughput of
the network.
Issue 06 (2013-02-27)
11-18
eRAN
ANR Management
11 Engineering Guidelines
Parameter
Name
Parameter ID
Setting Description
UTRAN Fast
ANR RSCP
threshold
ANR.FastAnrRscpThd
GERAN Fast
ANR RSSI
threshold
ANR.FastAnrRssiThd
CDMA2000
1XRTT Fast
ANR Pilot
threshold
CDMA2000
HRPD Fast
ANR Pilot
threshold
Issue 06 (2013-02-27)
11-19
eRAN
ANR Management
11 Engineering Guidelines
Monitoring
The current eRAN version has no performance counter related to ANR in sharing mode. Using ANR with
shared cells decreases the probability that the configurations of neighboring cells are missing or
incorrect, thereby increasing the intra-RAT handover success rate and decreasing the service drop rate.
To monitor the performance of ANR with shared cells, you can check the performance counters related
to handovers and service drops.
Parameter Optimization
None
11.9.4 X2 Self-Setup
This section describes how to optimize the performance of X2 self-setup.
Monitoring
The performance of X2 self-setup and X2-based handover can be monitored using counters, SON logs,
and alarms.
Counters
The following table lists the counters related to the X2 setup success rates and percentage of X2-based
handovers.
Counter ID
Counter Name
Description
1526727202
L.Sig.X2.SendSetup.Att
1526727204
L.Sig.X2.RecvSetup.Att
1526727203
L.Sig.X2.SendSetup.Succ
1526727205
L.Sig.X2.RecvSetup.Succ
1526727265
L.HHO.X2.IntraFreq.ExecAttOut
1526727268
L.HHO.X2.InterFreq.ExecAttOut
1526727002
1526727005
Issue 06 (2013-02-27)
11-20
eRAN
ANR Management
11 Engineering Guidelines
Counter ID
Counter Name
Description
1526727294
L.HHO.NCell.ExecAttOut
NOTE
For the detailed definitions of the counters, see eNodeB Performance Counter Reference.
SON Logs
The X2 control- and user-plane bearer self-setup events are automatically recorded in SON logs. The
SON logs can be exported using the M2000. The recorded information includes the setup time, the
PLMN IDs and eNodeB IDs of the local and peer eNodeBs, the link number of the peer eNodeB, and the
IP addresses of the peer eNodeB. If the X2 self-setup fails, the cause value is recorded in SON logs for
further analysis.
The following table lists the common cause values and solutions to setup failures.
Cause Values in the SON
Logs
Description
Solution
Issue 06 (2013-02-27)
11-21
eRAN
ANR Management
11 Engineering Guidelines
Description
Solution
The CnOperator MO
referenced by the
CnOperatorId parameter
has not been configured.
Alarms
The following table lists the alarms related to X2 interfaces. For details about the alarms, see eNodeB
Alarm Reference.
Alarm ID
Alarm Name
Severity
29204
X2 Interface Fault
Major
29205
Major
25886
IP Path Fault
Major
25888
Major
The following part in this section describes how to use the counters, SON logs, and alarms to monitor
the performance of X2 self-setup and X2-based handovers.
Analyzing Causes for X2 Self-Setup Failures
Step 1 Monitor the X2 self-setup success rates based on counters.
Export counters whose IDs are 1526727202, 1526727204, 1526727203, and 1526727205. Calculate
the X2 setup success rates as follows:
Issue 06 (2013-02-27)
11-22
eRAN
ANR Management
11 Engineering Guidelines
Based on the X2 setup success rates at the local eNodeB and peer eNodeB, identify the top N eNodeBs
with low X2 setup success rates for further analysis.
Step 2 Run the LST GLOBALPROCSWITCH command to check the settings of the X2 self-setup
switch and self-setup mode.
Step 3 Check the configurations of the control-plane and user-plane IP addresses.
1. Run the LST X2SIGIP command to check the control-plane IP address configuration of the local
eNodeB. Note that if the X2 over S1 mode is used, the default port numbers must be used. The
number of the port where the control-plane IP address is configured must be 36422.
2. Run the LST X2SERVIP command to check the user-plane IP address configuration of the local
eNodeB.
Step 4 Check whether alarms related to X2 interfaces are generated for the top N eNodeBs. If related
alarms are generated, clear the alarms.
Step 5 On the M2000, export X2 self-setup SON logs for the top N eNodeBs. For details about how to
export SON logs, see section 11.8.7 "Activation Observation."
The Event Source Object field records the MCC, MNC, and ID of the local eNodeB and can be used
to filter the logs for the top N eNodeBs.
The Event Description field records information such as MCC, MNC, ID, and IP address of the peer
eNodeB and can be used to identify the peer eNodeB.
The Result field records whether the X2 control plane or user plane has been successfully set up.
Filter for failure records for further analysis.
The Failure Cause field records the causes. Figure 11-5 shows an example of the SON logs.
----End
Analyzing Whether X2 Interfaces Are Frequently Used
Step 1 Export counters whose IDs are 526727265, 1526727268, 1526727002, and 1526727005.
Step 2 Use the counter values to calculate the percentage of X2-based outgoing handovers for an
eNodeB.
The calculation formula is as follows:
Percentage of performed X2-based outgoing handovers = (L.HHO.X2.IntraFreq.ExecAttOut +
L.HHO.X2.InterFreq.ExecAttOut)/(L.HHO.IntereNB.IntraFreq.ExecAttOut +
L.HHO.IntereNB.InterFreq.ExecAttOut) x 100%
When X2 interfaces are available between an eNodeB and its neighboring eNodeBs, X2-based
handovers are preferentially performed. If the percentage of performed X2-based outgoing handovers is
less than 100%, S1-based handovers are performed because no X2 interface has been set up between
the local eNodeB and some of its neighboring eNodeBs.
Issue 06 (2013-02-27)
11-23
eRAN
ANR Management
11 Engineering Guidelines
Filter for the top N eNodeBs with low percentages of X2-based outgoing handovers.
Step 3 Check the X2 interface configuration of the top N eNodeBs to identify the peer eNodeBs with
which X2 interfaces have been set up.
The DSP X2INTERFACE command can be used to check the PLMN IDs and eNodeB IDs of all peer
eNodeBs with which X2 interfaces have been set up.
Step 4 Use counters to calculate the number of outgoing handovers from a top N eNodeB to each peer
eNodeB.
Export the counter whose ID is 1526727294. This counter is a cell-level counter. Calculate the sum of
the counter values of the source cells to obtain the number of eNodeB-level X2-based outgoing
handovers. The following is an example.
Assume that cell a and cell b are provided by the source eNodeB, cell c and cell d are provided by the
target eNodeB, and the counter values are as listed in the following table.
Source Cell
Target Cell
Cell a
Cell c
Cell b
Cell d
Cell a
Cell d
Cell b
Cell c
The total number of outgoing handovers from the source eNodeB to the target eNodeB is the sum of X, Y,
Z, and W.
Step 5 Based on the X2 interface configuration information obtained in Step 3, analyze the results
obtained in Step 4.
If an X2 interface has been set up between the source eNodeB and a target eNodeB but none or a
small number of handovers are performed over the X2 interface, the priority of the X2 interface is low.
When the number of configured X2 interfaces has reached the maximum, the low-priority X2 interface
can be removed for the setup of another X2 interface.
If an X2 interface has not been set up between the source eNodeB and a target eNodeB but a large
number of handovers are performed from the source eNodeB to this target eNodeB, an X2 interface
needs to be set up between the two eNodeBs. You can remove a low-priority X2 interface to ensure
that an X2 interface can be set up between these two eNodeBs.
----End
Adjusting the X2 Interface Configuration After eNodeB IP Address Modification
If eNodeB IP addresses are changed, run the RMV X2ENODEB command to remove the X2 interface at
both the local and neighboring eNodeBs. The X2 self-setup function will set up a new X2 interface
between the two eNodeBs.
You can find out the destination IP addresses based on the X2 interface configuration at the local
eNodeB. The method is as follows:
1. Obtain the value of the X2eNodeB.FIRSTSIGIP parameter from the X2eNodeB MO to be removed
from the local eNodeB. The eNodeB whose first X2 control-plane IP address (specified by the
Issue 06 (2013-02-27)
11-24
eRAN
ANR Management
11 Engineering Guidelines
The X2SigIP.LOCIP parameter indicates the first X2 control-plane IP address of the local eNodeB. The
X2eNodeB.FIRSTSIGIP parameter indicates the first X2 control-plane IP address of the neighboring eNodeB.
Parameter Optimization
None
11.10 Troubleshooting
11.10.1 Intra-RAT ANR
Fault Description
An intra- or inter-frequency handover fails.
Fault Handling
Perform the following steps to check whether this handover failure is caused by an incorrect ANR
configuration:
Step 1 Start a Uu interface tracing task on the M2000 client, and check whether the eNodeB has
delivered a handover command. A handover command is delivered if the RRC_CONN_RECFG
message contains the IE mobilityControlInfo.
If the eNodeB has delivered the handover command, contact Huawei engineers.
Step 2 Run the following commands to check whether external cells, intra-frequency neighbor relations,
and inter-frequency neighbor relations have been configured: LST EUTRANEXTERNALCELL,
LST EUTRANINTRAFREQNCELL, and LST EUTRANINTERFREQNCELL.
Issue 06 (2013-02-27)
11-25
eRAN
ANR Management
11 Engineering Guidelines
NOTE
In RAN sharing with common carriers mode, if the UE is subscribed to a secondary operator, you also need to check
whether the PLMN ID has been configured for the secondary operator. If no PLMN ID has been configured for the
secondary operator, configure one PLMN ID for the secondary operator.
Step 3 Check whether the switch for intra-RAT event-triggered ANR has been turned on.
If the switch has not been turned on, turn on the switch.
Step 4 Check whether the UE supports intra-RAT ANR by referring to section 3.7 "ANR Capabilities of
UEs." Intra-RAT neighbor relations can be automatically found only if the UE supports intra-RAT
ANR.
If the UE supports intra-RAT ANR, the handover failure is not caused by incorrect ANR configuration.
Contact Huawei engineers.
----End
Fault Handling
Perform the following steps to check whether this handover failure is caused by an incorrect ANR
configuration:
Step 1 Start a Uu interface tracing task on the M2000 client, and check whether the eNodeB has
delivered a handover command. A handover command is delivered if the
RRC_MOBIL_FROM_EUTRA_CMD message contains the IE mobilityFromEUTRACommand.
If the eNodeB has delivered the handover command, contact Huawei engineers.
Step 2 Run the LST UTRANEXTERNALCELL command to check whether external cells have been
configured. Run the LST UTRANNCELL command to check whether the neighbor relations with
UTRAN have been configured.
In RAN sharing with common carriers mode, if the UE is subscribed to a secondary operator, you also need to check
whether the PLMN ID has been configured for the secondary operator. If no PLMN ID has been configured for the
secondary operator, configure one PLMN ID for the secondary operator.
Step 3 Check whether the switch for event-triggered ANR with UTRAN has been turned on.
If the switch has not been turned on, turn on the switch.
Issue 06 (2013-02-27)
11-26
eRAN
ANR Management
11 Engineering Guidelines
Fault Handling
Perform the following steps to check whether this handover failure is caused by an incorrect ANR
configuration:
Step 1 Start a Uu interface tracing task on the M2000 client, and check whether the eNodeB has
delivered a handover command. A handover command is delivered if the RRC_CONN_RECFG
message contains the IE mobilityControlInfo.
If the eNodeB has delivered the handover command, contact Huawei engineers.
Step 2 Run the following commands to check whether external cells, intra-frequency neighbor relations,
inter-frequency neighbor relations, and the PLMN list of external cells have been configured:
LST EUTRANEXTERNALCELL, LST EUTRANINTRAFREQNCELL, LST
EUTRANINTERFREQNCELL, and LST EUTRANEXTERNALCELLPLMN.
Step 3 Check whether the switch for intra-RAT event-triggered ANR and that for RAN sharing
supporting by neighboring eNodeBs have been turned on.
If any of the switches has not been turned on, turn on the switch.
Step 4 Check whether the UE supports intra-RAT ANR by referring to section 3.7 "ANR Capabilities of
UEs."
11.10.4 X2 Self-Setup
None
Issue 06 (2013-02-27)
11-27
eRAN
ANR Management
12 Parameters
12 Parameters
Table 12-1 Parameter description
MO
Parameter ID
ENodeBAlg AnrSwitch
oSwitch
Issue 06 (2013-02-27)
MML
Command
Feature
ID
Feature Description
Name
MOD
LOFD-002 Automati Meaning:Indicates the ANR
ENODEBALGO 001 /
c
algorithm switch. Switches related to
SWITCH
TDLOFD- Neighbou ANR are described as follows:
002001
r Relation IntraRatEventAnrSwitch: If this
LST
(ANR)
switch is turned on, intra-RAT
ENODEBALGO LOFD-002
event-triggered ANR is enabled to
SWITCH
002 /
Inter-RAT construct and optimize intra-RAT
TDLOFD- ANR
neighboring relations by triggering
002002
intra-RAT handover events.
IntraRatFastAnrSwitch: If this switch
is turned on, intra-RAT fast ANR is
enabled to construct and optimize
intra-RAT neighboring relations by
performing periodic intra-RAT
measurements.
IntraRatAnrAutoDelSwitch: If both
IntraRatEventAnrSwitch and this
switch are turned on and No
Remove of an intra-RAT neighboring
relation (a flag in the neighboring
relation table) is set to False,
automatic removal of the intra-RAT
neighboring relation is allowed. If this
switch is turned off, automatic
removal of the intra-RAT neighboring
relation is prohibited.
UtranEventAnrSwitch: If this switch
is turned on, event-triggered ANR
with UTRAN is enabled to construct
and optimize inter-RAT neighboring
relations with UTRAN cells by
triggering events for inter-RAT
handovers to UTRAN.
GeranEventAnrSwitch: If this switch
is turned on, event-triggered ANR
with GERAN is enabled to construct
and optimize inter-RAT neighboring
relations with GERAN cells by
triggering events for inter-RAT
handovers to GERAN.
UtranFastAnrSwitch: If this switch is
turned on, fast ANR with UTRAN is
enabled to construct and optimize
inter-RAT neighboring relations with
UTRAN cells by performing periodic
inter-RAT measurements on
UTRAN. The eNodeB does not
deliver information about external
12-1
eRAN
ANR Management
MO
Parameter ID
12 Parameters
MML
Command
Feature
ID
Feature Description
Name
UTRAN cells in the measurement
configuration to UEs and the UEs
measure only neighboring UTRAN
cells contained in the measurement
configuration. Therefore, if you want
external UTRAN cells added by fast
ANR with UTRAN to be measured in
handovers, you are advised to turn
on UtranEventAnrSwitch as well.
GeranFastAnrSwitch: If this switch is
turned on, fast ANR with GERAN is
enabled to construct and optimize
inter-RAT neighboring relations with
GERAN cells by performing periodic
inter-RAT measurements on
GERAN. CdmaFastAnrSwitch: If this
switch is turned on, fast ANR with
CDMA2000 is enabled to construct
and optimize inter-RAT neighboring
relations with CDMA2000 cells by
performing periodic intra-RAT
measurements on CDMA2000
networks.
UtranAutoNrtDeleteSwitch: If both
UtranEventAnrSwitch and this switch
are turned on and No Remove of the
inter-RAT neighboring relation with a
UTRAN cell (a flag in the neighbor
relations table) is set to False,
automatic removal of the inter-RAT
neighboring relation is allowed. If this
switch is turned off, automatic
removal of the inter-RAT neighboring
relation is prohibited.
GeranAutoNrtDeleteSwitch: If both
GeranEventAnrSwitch and this
switch are turned on and No
Remove of the inter-RAT
neighboring relation with a GERAN
cell (a flag in the neighboring relation
table) is set to False, automatic
removal of the inter-RAT neighboring
relation is allowed. If this switch is
turned off, automatic removal of the
inter-RAT neighboring relation is
prohibited.
CdmaAutoNrtDeleteSwitch: If this
switch is turned on and No Remove
of the inter-RAT neighboring relation
with a CDMA2000 cell (a flag in the
neighboring relation table) is set to
False, automatic removal of the
Issue 06 (2013-02-27)
12-2
eRAN
ANR Management
MO
Parameter ID
12 Parameters
MML
Command
Feature
ID
Feature Description
Name
inter-RAT neighboring relation is
allowed. If this switch is turned off,
automatic removal of the inter-RAT
neighboring relation is prohibited.
ExtendIntraRatAnrSwitch: This
switch is used to specify whether
unknown cells corresponding to the
detected PCIs can be configured as
external cells of the eNodeB by
using the eCoordinator. If this switch
is turned on, unknown cells
corresponding to the detected PCIs
can be configured as external cells
of the eNodeB by using the
eCoordinator in any of the following
scenarios: When PCIs of unknown
cells are detected by triggering
intra-RAT handover events,
IntraRatEventAnrSwitch is turned off
or the UE is incapable of measuring
CGIs. When PCIs of unknown cells
are detected by performing periodic
intra-RAT measurements, the UE is
incapable of measuring CGIs. If this
switch is turned off, unknown cells
corresponding to the detected PCIs
cannot be configured as external
cells of the eNodeB by using the
eCoordinator.
GUI Value
Range:IntraRatEventAnrSwitch,
IntraRatFastAnrSwitch,
IntraRatAnrAutoDelSwitch,
UtranEventAnrSwitch,
GeranEventAnrSwitch,
UtranFastAnrSwitch,
GeranFastAnrSwitch,
CdmaFastAnrSwitch,
UtranAutoNrtDeleteSwitch,
GeranAutoNrtDeleteSwitch,
CdmaAutoNrtDeleteSwitch,
ExtendIntraRatAnrSwitch
Unit:None
Actual Value
Range:IntraRatEventAnrSwitch,
IntraRatFastAnrSwitch,
IntraRatAnrAutoDelSwitch,
UtranEventAnrSwitch,
GeranEventAnrSwitch,
UtranFastAnrSwitch,
Issue 06 (2013-02-27)
12-3
eRAN
ANR Management
MO
Parameter ID
12 Parameters
MML
Command
Feature
ID
Feature Description
Name
GeranFastAnrSwitch,
CdmaFastAnrSwitch,
UtranAutoNrtDeleteSwitch,
GeranAutoNrtDeleteSwitch,
CdmaAutoNrtDeleteSwitch,
ExtendIntraRatAnrSwitch
Default
Value:IntraRatEventAnrSwitch:Off,
IntraRatFastAnrSwitch:Off,
IntraRatAnrAutoDelSwitch:On,
UtranEventAnrSwitch:Off,
GeranEventAnrSwitch:Off,
UtranFastAnrSwitch:Off,
GeranFastAnrSwitch:Off,
CdmaFastAnrSwitch:Off,
UtranAutoNrtDeleteSwitch:On,
GeranAutoNrtDeleteSwitch:On,
CdmaAutoNrtDeleteSwitch:On,
ExtendIntraRatAnrSwitch:Off
ANR
DelCellThd
MOD ANR
LST ANR
X2BlackWhi ENodeBId
Issue 06 (2013-02-27)
ADD
12-4
eRAN
ANR Management
MO
Parameter ID
teList
12 Parameters
MML
Command
Feature
ID
Feature Description
Name
X2BLACKWHIT 004 /
guration neighboring eNodeB to be added to
ELIST
TDLOFDthe list.
Automati
002004
RMV
c
GUI Value Range:0~1048575
X2BLACKWHIT LOFD-002 Neighbou
ELIST
001 /
r Relation Unit:None
TDLOFD- (ANR)
Actual Value Range:0~1048575
LST
002001
X2BLACKWHIT
Default Value:None
ELIST
ANR
ANR
Issue 06 (2013-02-27)
12-5
eRAN
ANR Management
MO
12 Parameters
Parameter ID
MML
Command
Feature
ID
Feature Description
Name
pdPilotThd
LST ANR
ANR
ANR
ANR
Issue 06 (2013-02-27)
12-6
eRAN
ANR Management
MO
Parameter ID
12 Parameters
MML
Command
Feature
ID
Feature Description
Name
GUI Value Range:1~10000
Unit:None
Actual Value Range:1~10000
Default Value:20
ANR
ANR
ANR
Issue 06 (2013-02-27)
12-7
eRAN
ANR Management
12 Parameters
MML
Command
MO
Parameter ID
ANR
Feature
ID
Feature Description
Name
ANR
ANR
ANR
Issue 06 (2013-02-27)
12-8
eRAN
ANR Management
MO
Parameter ID
12 Parameters
MML
Command
Feature
ID
LST ANR
002001
Feature Description
Name
X2eNodeB FIRSTSIGIP
ADD
X2ENODEB
MOD
X2ENODEB
LST
X2ENODEB
Cell
LocalCellId
ACT CELL
None
None
ADD CELL
BLK CELL
DEA CELL
Unit:None
DSP CELL
LST CELL
Default Value:None
MOD CELL
RMV CELL
STR
CELLRFLOOPB
ACK
STR
CELLSELFTES
T
UBL CELL
X2SigIP
LOCIP
Issue 06 (2013-02-27)
ADD X2SIGIP
12-9
eRAN
ANR Management
MO
Parameter ID
12 Parameters
MML
Command
Feature
ID
Feature Description
Name
eNodeB, which is to be used as the
first local IP address for an
automatically set up SCTP link on an
X2 interface.
GUI Value Range:Valid IP address
Unit:None
Actual Value Range:Valid IP address
Default Value:None
X2BlackWhi Mcc
teList
ADD
LOFD-002 Self-confi Meaning:Indicates the mobile
X2BLACKWHIT 004 /
guration country code of the neighboring
ELIST
TDLOFDeNodeB to be added to the list. The
Automati value of this parameter is a string of
002004
RMV
c
three characters, each of which must
X2BLACKWHIT LOFD-002 Neighbou be a digit in the range of 0 to 9.
ELIST
001 /
r Relation
TDLOFD- (ANR)
GUI Value Range:3 characters
LST
002001
X2BLACKWHIT
Unit:None
ELIST
Actual Value Range:000~999
Default Value:None
X2BlackWhi Mnc
teList
ADD
LOFD-002 Self-confi Meaning:Indicates the mobile
X2BLACKWHIT 004 /
guration network code of the neighboring
ELIST
TDLOFDeNodeB to be added to the list. The
Automati value of this parameter is a string of
002004
RMV
c
two or three characters, each of
X2BLACKWHIT LOFD-002 Neighbou which must be a digit in the range of
ELIST
001 /
r Relation 0 to 9.
TDLOFD- (ANR)
LST
002001
GUI Value Range:2~3 characters
X2BLACKWHIT
ELIST
Unit:None
Actual Value Range:00~99,000~999
Default Value:None
ANR
Issue 06 (2013-02-27)
12-10
eRAN
ANR Management
MO
Parameter ID
12 Parameters
MML
Command
Feature
ID
Feature Description
Name
Actual Value Range:1~10000
Default Value:200
EutranInter NoHoFlag
FreqNCell
ADD
LBFD-002 Coverage Meaning:Indicates whether
EUTRANINTER 01802 /
Based
handovers of UEs to the neighboring
FREQNCELL TDLBFD-0 Inter-freq cell are prohibited.
0201802 uency
MOD
Handover GUI Value
EUTRANINTER LOFD-002
Range:PERMIT_HO_ENUM(Permit
FREQNCELL 001 /
Automati Ho), FORBID_HO_ENUM(Forbid
TDLOFD- c
Ho)
LST
002001
Neighbou
EUTRANINTER
r Relation Unit:None
FREQNCELL
(ANR)
Actual Value
Range:PERMIT_HO_ENUM,
FORBID_HO_ENUM
Default
Value:PERMIT_HO_ENUM(Permit
Ho)
EutranInter NoRmvFlag
FreqNCell
ADD
LOFD-002 Automati Meaning:Indicates whether to permit
EUTRANINTER 001 /
c
or prohibit removal of the
FREQNCELL TDLOFD- Neighbou neighboring relationship by ANR.
002001
r Relation
MOD
GUI Value
(ANR)
EUTRANINTER
Range:PERMIT_RMV_ENUM(Permi
FREQNCELL
t ANR Remove),
FORBID_RMV_ENUM(Forbid ANR
LST
Remove)
EUTRANINTER
FREQNCELL
Unit:None
Actual Value
Range:PERMIT_RMV_ENUM,
FORBID_RMV_ENUM
Default
Value:PERMIT_RMV_ENUM(Permit
ANR Remove)
ANR
OptMode
MOD ANR
LST ANR
Issue 06 (2013-02-27)
12-11
eRAN
ANR Management
MO
Parameter ID
12 Parameters
MML
Command
Feature
ID
Feature Description
Name
CONTROLLED(CONTROLLED)
Unit:None
Actual Value Range:FREE,
CONTROLLED
Default Value:FREE(FREE)
DEVIP
PT
ADD DEVIP
RMV DEVIP
DSP DEVIP
LST DEVIP
None
None
12-12
eRAN
ANR Management
MO
Parameter ID
12 Parameters
MML
Command
Feature
ID
Feature Description
Name
reports the CGI of the cell during
ANR measurements.
If both NBSLTEPLMNRoundSwitch
and NBSLTERANSharingSwitch are
turned on,
NBSLTEPLMNRoundSwitch
overrides
NBSLTERANSharingSwitch.
GUI Value
Range:NBSLTEPLMNRoundSwitch(
NBSLTEPLMNRoundSwitch),
NBSLTERANSharingSwitch(NBSLT
ERANSharingSwitch)
Unit:None
Actual Value
Range:NBSLTEPLMNRoundSwitch,
NBSLTERANSharingSwitch
Default
Value:NBSLTEPLMNRoundSwitch:O
ff, NBSLTERANSharingSwitch:Off
ANR
ANR
Issue 06 (2013-02-27)
12-13
eRAN
ANR Management
MO
Parameter ID
12 Parameters
MML
Command
Feature
ID
Feature Description
Name
GUI Value Range:1~10080
Unit:min
Actual Value Range:1~10080
Default Value:1440
ANR
X2BlackWhi X2ListType
teList
ADD
LOFD-002 Self-confi Meaning:Indicates whether the list is
X2BLACKWHIT 004 /
guration a blacklist or whitelist.If the peer
ELIST
TDLOFDeNodeB is in the X2 blacklist, the X2
Automati interface between the two eNodeBs
002004
LST
c
cannot be manually or automatically
X2BLACKWHIT LOFD-002 Neighbou set up. If the peer eNodeB is in the
ELIST
001 /
r Relation X2 whitelist, the X2 interface
TDLOFD- (ANR)
between the two eNodeBs cannot be
002001
automatically removed.
GUI Value
Range:X2_BLACK_LIST_TYPE(X2
Black List Type),
X2_WHITE_LIST_TYPE(X2 White
List Type)
Unit:None
Actual Value
Range:X2_BLACK_LIST_TYPE,
X2_WHITE_LIST_TYPE
Default
Value:X2_BLACK_LIST_TYPE(X2
Black List Type)
Issue 06 (2013-02-27)
12-14
eRAN
ANR Management
12 Parameters
MO
Parameter ID
MML
Command
Feature
ID
Feature Description
Name
X2ServIP
X2SERVIP
Issue 06 (2013-02-27)
12-15
eRAN
ANR Management
Issue 06 (2013-02-27)
12 Parameters
12-16
eRAN
ANR Management
13 Counters
13 Counters
There are no specific counters associated with this feature.
Issue 06 (2013-02-27)
13-1
eRAN
ANR Management
14 Glossary
14 Glossary
For the acronyms, abbreviations, terms, and definitions, see Glossary.
Issue 06 (2013-02-27)
14-1
eRAN
ANR Management
15 Reference Documents
15 Reference Documents
This chapter lists the reference documents related to the ANR management feature:
[1] 3GPP TS 32.511, "Automatic Neighbor Relation (ANR) management; Concepts and requirements"
[2] 3GPP TS 36.300, "E-UTRAN Overall description"
[3] 3GPP TS 36.331, "RRC Protocol specification"
[4] 3GPP TS 36.413, "E-UTRAN S1 Application Protocol (S1AP)"
[5] eNodeB MO Reference
[6] eNodeB MML Command Reference
[7] eNodeB Alarm Reference
[8] eNodeB Performance Counter Reference
[9] DRX Feature Parameter Description
[10] Mobility Management in Connected Mode Feature Parameter Description
[11] S1/X2/OM Channel Management Feature Parameter Description
Issue 06 (2013-02-27)
15-1