Professional Documents
Culture Documents
ANR Management (ERAN3.0 04)
ANR Management (ERAN3.0 04)
eRAN3.0
Issue
04
Date
2012-09-20
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 04 (2012-09-20)
eRAN
ANR Management
Contents
ii
eRAN
ANR Management
Contents
11 Parameters..............................................................................................................................11-1
12 Counters..................................................................................................................................12-1
13 Glossary ..................................................................................................................................13-1
14 Reference Documents .........................................................................................................14-1
Issue 04 (2012-09-20)
iii
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:
04 (2012-09-20)
03 (2012-06-30)
02 (2012-05-11)
01 (2012-03-30)
Draft A (2012-01-10)
04 (2012-09-20)
Compared with issue 03 (2012-06-30), issue 04 (2012-09-20) includes the following changes.
Change Type
Change Description
Parameter Change
Feature change
None
None
Editorial change
None
Issue 04 (2012-09-20)
1-1
eRAN
ANR Management
1 Introduction
03 (2012-06-30)
Compared with issue 02 (2012-05-11), issue 03 (2012-06-30) includes the following changes.
Change Type
Change Description
Parameter Change
Feature change
Added the
RanSharingAnrSwitch
parameter.
None
02 (2012-05-11)
Compared with issue 01 (2012-03-30), issue 02 (2012-05-11) 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
Removed TempNRTs.
None
Issue 04 (2012-09-20)
1-2
eRAN
ANR Management
1 Introduction
Change
Type
Change Description
Parameter Change
change
Editorial
change
StatisticPeriodForNRTDel
StatisticNumForNRTDel
None
None
Issue 04 (2012-09-20)
1-3
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 a huge amount of network elements, implementation of different system
standards, and coexistence of different equipment vendors and telecom operators. To overcome 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, and 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 04 (2012-09-20)
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 under 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
Removal
Control
Handover
Control
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 04 (2012-09-20)
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 of a neighbor relation is set to allow removal.
If
this attribute of a neighbor relation is set to prohibit removal, this neighbor relation cannot be
removed from the NRT by ANR.
If
this attribute of a neighbor relation is set to allow removal, this neighbor relation can be removed
from the NRT by ANR.
Handover control: indicates whether this neighbor relation can be used for a handover. By default, this
attribute of a neighbor relation is set to allow handover.
If
this attribute of a neighbor relation is set to prohibit handover, this neighbor relation cannot be used
for a handover.
If
this attribute of a neighbor relation is set to allow handover, this neighbor relation can be used for a
handover.
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 Blacklist
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 in the X2 blacklist, this X2 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.
Issue 04 (2012-09-20)
3-2
eRAN
ANR Management
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:
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.
Issue 04 (2012-09-20)
3-3
eRAN
ANR Management
Information message indicates the ANR capability of the UE. Table 3-2 provides the definitions and
setting descriptions of the ANR-related indicators.
Table 3-2 Definitions and setting descriptions of the ANR-related indicators
Indicator
Index
16
Remarks
Applicability
N/A
Yes
N/A
Yes
Yes
NOTE
17
18
19
N/A
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 04 (2012-09-20)
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 04 (2012-09-20)
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 the intra-frequency neighboring cell measurement configuration to the UE by using the RRC Connection
Reconfiguration message by default. 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-frequency handover measurements 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
and is quoted directly from 3GPP TS 36.331.
Issue 04 (2012-09-20)
4-2
eRAN
ANR Management
4 Intra-RAT ANR
Timer
Start
Stop
At Expiry
T321
Initiate the
measurement
reporting procedure,
stop performing the
related measurements
and remove the
corresponding measId
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 04 (2012-09-20)
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."
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 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.
The eNodeB automatically removes a neighbor relation (for example, with cell A) from an NRT if the
IntraRatAnrAutoDelSwitch check box under the AnrSwitch parameter is selected, the removal
control flag is set to allow removal, and either of the following criteria is met:
Criterion
Issue 04 (2012-09-20)
4-4
eRAN
ANR Management
4 Intra-RAT ANR
equal to the value of StatisticNumForNRTDel and cell A's PCI has never been included in any
handover measurement reports.
Criterion
The algorithm of 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 take 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
detecting a missing neighboring cell, the eNodeB operation differs. In fast ANR, this newly detected
neighboring cell is added immediately only to the NCL. The neighbor relation will be added to the NRT
only after a successful handover from the serving cell to this neighboring cell.
Periodic UE measurements negatively affect the uplink throughput of the network. Therefore, intra-RAT
fast ANR restricts the number of concurrent UEs involved in intra-RAT periodic measurements. When
the number of involved UEs reaches the upper limit, the eNodeB does not select a new UE for periodic
measurements until a UE stops periodic measurements. The upper limit is specified by the
FastAnrIntraRatMeasUeNum parameter.
Periodic UE measurements also increase the power consumption of a UE. Therefore, intra-RAT fast
ANR restricts the number of periodic measurement reports by each UE. When the number of periodic
measurement reports by a UE reaches the upper limit, the UE stops periodic measurements so that the
eNodeB can select another UE for periodic measurements until the eNodeB deactivates intra-RAT fast
ANR. The upper limit is specified by the FastAnrRprtAmount parameter. The interval for UEs to report
periodic measurements is specified by the FastAnrRprtInterval parameter.
The total number of neighboring cells that meet the RSRP requirement is limited, and periodic UE
measurements negatively affect the uplink throughput of the network. Therefore, intra-RAT fast ANR
restricts the total number of UEs involved in intra-RAT periodic measurements. The eNodeB checks
whether the total number of involved UEs is greater than the upper limit at a regular interval, which is
specified by the FastAnrCheckPeriod parameter. The upper limit is specified by the
FastAnrIntraRatUeNumThd parameter. If yes, the eNodeB automatically deactivates intra-RAT fast
ANR. If no, periodic UE measurements continue.
Issue 04 (2012-09-20)
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 04 (2012-09-20)
4-7
eRAN
ANR Management
4 Intra-RAT ANR
unknown cells. The number of UEs that can be selected is specified by the
FastAnrIntraRatMeasUeNum parameter.
2. During the check period, the eNodeB operates as follows:
If
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 FastAnrIntraRatMeasUeNum parameter.
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-frequency and inter-frequency measurements exceeds the
value of FastAnrIntraRatUeNumThd, the eNodeB enters the monitoring state to monitor 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-frequency and inter-frequency measurements is less than
or equal to the value of 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 04 (2012-09-20)
80
4-8
eRAN
ANR Management
Measurement
Gap Pattern
4 Intra-RAT ANR
Gap Repetition
Period (Unit: ms)
Target RAT
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, 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 04 (2012-09-20)
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 04 (2012-09-20)
10
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).
If
4. The source eNodeB schedules appropriate measurement gaps 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 04 (2012-09-20)
11
eRAN
ANR Management
5 Inter-RAT ANR
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 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 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
Issue 04 (2012-09-20)
12
eRAN
ANR Management
5 Inter-RAT ANR
NOTE
Automatic removal of neighbor relations with CDMA2000 is not yet a requirement; therefore, it is not implemented in
eRAN3.0.
The signal quality threshold used in the evaluation of whether to periodically report a neighboring cell's
PCI is specified by the FastAnrRsrpThd parameter in intra-RAT fast ANR and specified by the
following parameters in inter-RAT fast ANR.
Target RAT
UTRAN
FastAnrRscpThd
GERAN
FastAnrRssiThd
CDMA2000 1xRTT
FastAnrCdma1xrttPilotThd
CDMA2000 HRPD
FastAnrCdmahrpdPilotThd
The upper limit on the number of concurrent UEs involved in fast ANR measurements is specified by
the FastAnrInterRatMeasUeNum parameter in inter-RAT fast ANR and specified by the
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 FastAnrInterRatUeNumThd parameter in inter-RAT fast ANR and specified by the
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 04 (2012-09-20)
13
eRAN
ANR Management
eRAN3.0 does not support ANR with shared UTRAN or GERAN cells.
Issue 04 (2012-09-20)
6-1
eRAN
ANR Management
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 in the same procedure described in section 6.1 "Shared Neighboring Cell
Broadcasting PLMN List in an RR Manner."
Issue 04 (2012-09-20)
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 04 (2012-09-20)
7-1
eRAN
ANR Management
Step 4 Set both Deletion Prohibited and Handover Prohibited to TRUE in the displayed Set dialog
box.
----End
Alternatively, you can set the EUTRANINTERFREQNCELL.NoHoFlag parameter to
FORBID_HO_ENUM and the EutranInterFreqNCell.NoRmvFlag parameter to FORBID_RMV_ENUM
to blacklist a neighbor relation. 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 interfaces cannot be set up
between different base station models.
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 04 (2012-09-20)
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 04 (2012-09-20)
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 04 (2012-09-20)
7-4
eRAN
ANR Management
8 Related Features
8 Related Features
8.1 Intra-RAT ANR
8.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 dormancy periods. For details about DRX, see DRX Feature Parameter
Description.
Issue 04 (2012-09-20)
8-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
Overall, the influences that fast ANR exerts over network performance are 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 call drops and
handovers caused by inappropriate neighbor relations. As a result, the value of the Service Drop Rate
decreases and the values of the following key performance indicators (KPIs) increase:
Issue 04 (2012-09-20)
9-1
eRAN
ANR Management
Issue 04 (2012-09-20)
9-2
eRAN
ANR Management
10 Engineering Guidelines
10 Engineering Guidelines
10.1 When to Use ANR
10.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 04 (2012-09-20)
10-1
eRAN
ANR Management
10 Engineering Guidelines
NOTE
If both event-triggered ANR and fast ANR are enabled, they separately detect missing neighboring cells by using their own
mechanisms.
IntraRatEventAnrSwitch under the AnrSwitch parameter is turned on for UEs to read CGI over the
radio interface.
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.
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
Issue 04 (2012-09-20)
10-2
eRAN
ANR Management
10 Engineering Guidelines
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.
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 related to intra-RAT ANR. Table 10-1 provides
the license control item.
LOFD-002001 Automatic
Neighbour Relation (ANR)
LLT1ANR01
Issue 04 (2012-09-20)
10-3
eRAN
ANR Management
10 Engineering Guidelines
Parameter
Name
Parameter ID
Source
Setting Description
ANR
algorithm
switch
AnrSwitch
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 operators' requirements.
Parameter
Name
Mobile
network
code
Mobile
network
code
Parameter ID
X2BlackWhit
eList.Mcc
X2BlackWhit
eList.Mnc
eNodeB
identity
X2BlackWhit
eList.ENodeB
Id
X2 Black or
White List
Type
X2BlackWhit
eList.X2ListT
ype
Source
Setting Description
Network plan
(negotiation not
required)
Network plan
(negotiation not
required)
Network plan
(negotiation not
required)
Network plan
(negotiation not
required)
10.5.4 Precautions
None
Issue 04 (2012-09-20)
10-4
eRAN
ANR Management
10 Engineering Guidelines
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 an MO. This method applies to users who are unfamiliar with the
navigation tree.
Parameter
ENODEBALGOSWITCH
ENodeBAlgoSwitch
X2BLACKWHITELIST
X2BlackWhiteList
Issue 04 (2012-09-20)
10-5
eRAN
ANR Management
10 Engineering Guidelines
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 10-1 Uu tracing result during activation observation for intra-RAT ANR
----End
Issue 04 (2012-09-20)
10-6
eRAN
ANR Management
10 Engineering Guidelines
10.5.8 Reconfiguration
None
10.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
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 related to inter-RAT ANR. Table 10-2 provides
the license control item.
Inter-RAT ANR
LLT1IRA01
Issue 04 (2012-09-20)
10-7
eRAN
ANR Management
10 Engineering Guidelines
Parameter Name
Parameter ID
Source
Setting Description
ANR algorithm
switch
AnrSwitch
Network
plan
(negotiation
not required)
UtranEventAnrSwitch
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.
Parameter
Name
Parameter ID
Source
Setting Description
Long DRX
Cycle for
Inter-RAT
ANR
LongDRXCycle
forIRatAnr
Network plan
(negotiation
not required)
10.6.4 Precautions
None
Issue 04 (2012-09-20)
10-8
eRAN
ANR Management
10 Engineering Guidelines
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 an MO. This method applies to users who are unfamiliar with the
navigation tree.
Parameter
ENODEBALGOSWITCH
ENodeBAlgoSwitch
10.6.8 Reconfiguration
None
10.6.9 Deactivation
Run the MOD ENODEBALGOSWITCH command to disable inter-RAT ANR.
Issue 04 (2012-09-20)
10-9
eRAN
ANR Management
10 Engineering Guidelines
The intra-RAT measurement information (including frequencies to be measured) has been configured.
For details, see Mobility Management in Connected Mode Feature Parameter Description.
Parameter ID
Source
Setting Description
RanSharingAnrS
witch
Network plan
(negotiation
not required)
NBSLTEPLMNRoundSwitch
NBSLTERANSharingSwitch
10.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 an MO. This method applies to users who are unfamiliar with the
navigation tree.
Issue 04 (2012-09-20)
10-10
eRAN
ANR Management
10 Engineering Guidelines
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.
A user-defined template is recommended. The following table lists the recommended distribution of the
parameters in the template.
MO
Parameter
ENodeBAlgoSwitch
ENodeBAlgoSwitch
10.7.8 Reconfiguration
None
10.7.9 Deactivation
Run the MOD ENODEBALGOSWITCH command to disable ANR with shared cells.
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.
Issue 04 (2012-09-20)
10-11
eRAN
ANR Management
10 Engineering Guidelines
Parameter Optimization
The following parameters may need to be modified after intra-RAT ANR is activated.
Parameter
Name
Parameter ID
Setting Description
DelCellThd
Least Handover
Num for
Statistic
NcellHoStatN
um
Statistic cycle
StatisticPerio
d
Statistic
Number For
Delete NRT
StatisticNum
ForNRTDel
Statistic Cycle
For Delete NRT
StatisticPerio
dForNRTDel
Issue 04 (2012-09-20)
10-12
eRAN
ANR Management
10 Engineering Guidelines
Parameter
Name
Parameter ID
Setting Description
FastAnrRprt
Amount
FastAnrRprtI
nterval
Fast ANR
checking period
FastAnrChec
kPeriod
Fast ANR
measurement
RSRP
threshold
FastAnrRsrp
Thd
IntraRat Fast
ANR
measurement
UE number
FastAnrIntra
RatMeasUeN
um
IntraRat Fast
ANR valid
measurement
min UE number
FastAnrIntra
RatUeNumTh
d
This parameter specifies the upper limit for the total number of
UEs involved in intra-RAT periodic measurements. A larger
parameter value results in more UEs that are involved in intra-RAT
periodic 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 04 (2012-09-20)
10-13
eRAN
ANR Management
10 Engineering Guidelines
Parameter
Name
Parameter ID
Setting Description
Optimization
Mode
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 need to be modified 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
Setting Description
InterRat Fast
ANR
measurement
UE number
FastAnrInterRatM
easUeNum
InterRat Fast
ANR valid
measurement
min UE number
FastAnrInterRatU
eNumThd
This parameter specifies the upper limit for the total number
of UEs involved in inter-RAT periodic measurements. A
larger parameter value results in more UEs being involved in
inter-RAT periodic 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 04 (2012-09-20)
10-14
eRAN
ANR Management
10 Engineering Guidelines
Parameter
Name
Parameter ID
Setting Description
UTRAN Fast
ANR RSCP
threshold
FastAnrRscpThd
GERAN Fast
ANR RSSI
threshold
FastAnrRssiThd
CDMA2000
1XRTT Fast
ANR Pilot
threshold
FastAnrCdma1xrt
tPilotThd
CDMA2000
HRPD Fast ANR
Pilot threshold
FastAnrCdmahrp
dPilotThd
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
Issue 04 (2012-09-20)
10-15
eRAN
ANR Management
10 Engineering Guidelines
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
10.9 Troubleshooting
10.9.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 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.
In RAN sharing with common carriers mode, if the UE is subscribed to a secondary operator, you also need to check
whether additional PLMN IDs have been configured for the secondary operator. If no additional PLMN ID has been
configured for the secondary operator, configure one additional PLMN ID for the secondary operator.
Step 3 Check whether the switch for intra-RAT event-triggered ANR has been turned on.
Issue 04 (2012-09-20)
10-16
eRAN
ANR Management
10 Engineering Guidelines
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
Issue 04 (2012-09-20)
10-17
eRAN
ANR Management
11 Parameters
11 Parameters
Table 11-1 Parameter description
MO
Parameter ID
ENodeBAlg AnrSwitch
oSwitch
Issue 04 (2012-09-20)
MML
Command
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 UTRAN
cells in the measurement
11-1
eRAN
ANR Management
MO
Parameter ID
11 Parameters
MML
Command
Issue 04 (2012-09-20)
11-2
eRAN
ANR Management
MO
Parameter ID
11 Parameters
MML
Command
Issue 04 (2012-09-20)
11-3
eRAN
ANR Management
MO
Parameter ID
11 Parameters
MML
Command
ANR
DelCellThd
MOD ANR
LST ANR
X2BlackWh ENodeBId
iteList
Issue 04 (2012-09-20)
ADD
LOFD-002 Self-confi Meaning:Indicates the ID of the
X2BLACKWHIT 004 /
guration neighboring eNodeB to be added to
ELIST
TDLOFDthe list.
Automati
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
11-4
eRAN
ANR Management
MO
Parameter ID
11 Parameters
MML
Command
RMV
002004
c
GUI Value Range:0~1048575
X2BLACKWHIT
Neighbou
LOFD-002 r Relation Unit:None
ELIST
001 /
(ANR)
Actual Value Range:0~1048575
LST
TDLOFDX2BLACKWHIT 002001
Default Value:None
ELIST
ANR
ANR
ANR
Issue 04 (2012-09-20)
11-5
eRAN
ANR Management
MO
Parameter ID
11 Parameters
MML
Command
ANR
ANR
ANR
Issue 04 (2012-09-20)
11-6
eRAN
ANR Management
11 Parameters
MML
Command
MO
Parameter ID
ANR
ANR
ANR
ANR
Issue 04 (2012-09-20)
11-7
eRAN
ANR Management
MO
Parameter ID
11 Parameters
MML
Command
ANR
ANR
Cell
LocalCellId
Issue 04 (2012-09-20)
ACT CELL
None
None
ADD CELL
BLK CELL
DEA CELL
Unit:None
DSP CELL
LST CELL
Default Value:None
11-8
eRAN
ANR Management
MO
Parameter ID
11 Parameters
MML
Command
MOD CELL
RMV CELL
STR
CELLRFLOOPB
ACK
STR
CELLSELFTES
T
UBL CELL
X2BlackWh Mcc
iteList
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
X2BlackWh Mnc
iteList
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 04 (2012-09-20)
11-9
eRAN
ANR Management
MO
Parameter ID
11 Parameters
MML
Command
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 04 (2012-09-20)
11-10
eRAN
ANR Management
MO
Parameter ID
11 Parameters
MML
Command
11-11
eRAN
ANR Management
MO
Parameter ID
11 Parameters
MML
Command
ANR
ANR
ANR
Issue 04 (2012-09-20)
11-12
eRAN
ANR Management
MO
Parameter ID
11 Parameters
MML
Command
X2BlackWh X2ListType
iteList
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 04 (2012-09-20)
11-13
eRAN
ANR Management
12 Counters
12 Counters
There are no specific counters associated with this feature.
Issue 04 (2012-09-20)
12-1
eRAN
ANR Management
13 Glossary
13 Glossary
For the acronyms, abbreviations, terms, and definitions, see Glossary.
Issue 04 (2012-09-20)
13-1
eRAN
ANR Management
14 Reference Documents
14 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] DRX Feature Parameter Description
[9] Mobility Management in Connected Mode Feature Parameter Description
Issue 04 (2012-09-20)
14-1