ANR Management (ERAN3.0 - 08)

ANR Management
eRAN3.0
Feature Parameter Description
Issue 08
Date 2013-05-20
HUAWEI TECHNOLOGIES CO., LTD.

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

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: http://www.huawei.com
Email: support@huawei.com
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
2 Overview of ANR .......................................................................................................................2-1

2.1 Introduction.................................................................................................................................... 2-1
2.2 Benefits ......................................................................................................................................... 2-1
2.3 Architecture ................................................................................................................................... 2-1
3 Concepts Related to ANR .......................................................................................................3-1

3.1 Overview ....................................................................................................................................... 3-1
3.2 NCL ............................................................................................................................................... 3-1
3.3 NRT ............................................................................................................................................... 3-1
3.4 Blacklists ....................................................................................................................................... 3-2
3.4.1 HO Blacklist .......................................................................................................................... 3-2
3.4.2 X2 Blacklist ........................................................................................................................... 3-2
3.4.3 RRC Blacklist ........................................................................................................................ 3-2
3.5 Whitelist ......................................................................................................................................... 3-3
3.5.1 HO Whitelist .......................................................................................................................... 3-3
3.5.2 X2 Whitelist ........................................................................................................................... 3-3
3.6 Abnormal Neighboring Cell Coverage ........................................................................................... 3-3
3.7 ANR Capabilities of UEs ............................................................................................................... 3-3
4 Intra-RAT ANR ............................................................................................................................4-1

4.1 Overview ....................................................................................................................................... 4-1
4.2 Intra-RAT Event-triggered ANR ..................................................................................................... 4-1
4.2.1 Automatic Detection of Missing Neighboring Cells ............................................................... 4-1
4.2.2 Automatic Maintenance of NCLs and NRTs ......................................................................... 4-4
4.2.3 Automatic Detection of Abnormal Neighboring Cell Coverage ............................................. 4-5
4.3 Intra-RAT Fast ANR ....................................................................................................................... 4-6
5 Inter-RAT ANR ............................................................................................................................5-1

5.1 Overview ....................................................................................................................................... 5-1
5.2 Inter-RAT Event-triggered ANR ..................................................................................................... 5-1
5.2.1 Automatic Detection of Missing Neighboring Cells ............................................................... 5-1
5.2.2 Automatic Maintenance of NCLs and NRTs ......................................................................... 5-3
5.3 Inter-RAT Fast ANR ....................................................................................................................... 5-4
6 ANR with Shared Cells ............................................................................................................6-1

6.1 Shared Neighboring Cell Broadcasting PLMN List in an RR Manner ........................................... 6-1
6.2 Shared Neighboring Cell Not Broadcasting PLMN List in an RR Manner .................................... 6-2
Issue 08 (2013-05-20) Huawei Proprietary and Confidential i

Copyright © Huawei Technologies Co., Ltd.
eRAN
7 Manual Management of Neighbor Relations .....................................................................7-1

7.1 Overview ....................................................................................................................................... 7-1
7.2 Adding or Removing a Neighbor Relation ..................................................................................... 7-1
7.3 Blacklisting a Neighbor Relation ................................................................................................... 7-1
7.3.1 Configuring an HO Blacklist ................................................................................................. 7-1
7.3.2 Configuring an X2 Blacklist................................................................................................... 7-2
7.3.3 Configuring an RRC Blacklist ............................................................................................... 7-2
7.4 Whitelisting a Neighbor Relation ................................................................................................... 7-3
7.4.1 Configuring an HO Whitelist ................................................................................................. 7-3
7.4.2 Configuring an X2 Whitelist .................................................................................................. 7-3
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
8.4 eNodeB Configuration Update Based on X2 Messages ............................................................... 8-6
9 Related Features .......................................................................................................................9-1

9.1 Intra-RAT ANR ............................................................................................................................... 9-1
9.1.1 Required Features ................................................................................................................ 9-1
9.1.2 Mutually Exclusive Features ................................................................................................. 9-1
9.1.3 Affected Features ................................................................................................................. 9-1
9.2 Inter-RAT ANR ............................................................................................................................... 9-1
9.3 X2 Self-Setup ................................................................................................................................ 9-1
10 Impact on the Network ........................................................................................................10-1

10.1 Intra-RAT ANR ........................................................................................................................... 10-1
10.1.1 Impact on System Capacity .............................................................................................. 10-1
10.1.2 Impact on Network Performance ...................................................................................... 10-1
10.2 Inter-RAT ANR ........................................................................................................................... 10-1
10.3 ANR with Shared Cells .............................................................................................................. 10-2
10.4 X2 Self-Setup ............................................................................................................................ 10-2
Issue 08 (2013-05-20) Huawei Proprietary and Confidential ii

eRAN
11 Engineering Guidelines for Intra-RAT ANR....................................................................11-1

11.1 When to Use ANR ..................................................................................................................... 11-1
11.2 Information to Be Collected ....................................................................................................... 11-2
11.3 Network Planning ...................................................................................................................... 11-2
11.4 Overall Deployment Procedure ................................................................................................. 11-2
11.5 Deploying Intra-RAT ANR .......................................................................................................... 11-2
11.5.1 Deployment Procedure ..................................................................................................... 11-2
11.5.2 Deployment Requirements ............................................................................................... 11-2
11.5.3 Data Preparation ............................................................................................................... 11-2
11.5.4 Precautions ....................................................................................................................... 11-3
11.5.5 Hardware Adjustment ....................................................................................................... 11-3
11.5.6 Feature Activation ............................................................................................................. 11-4
11.5.7 Activation Observation ...................................................................................................... 11-5
11.5.8 Reconfiguration ................................................................................................................. 11-6
11.5.9 Deactivation ...................................................................................................................... 11-6
11.6 Monitoring .................................................................................................................................. 11-6
11.7 Parameter Optimization ............................................................................................................. 11-6
11.8 Troubleshooting ......................................................................................................................... 11-9
12 Engineering Guidelines for Inter-RAT ANR ...................................................................12-1

12.1 When to Use ANR ..................................................................................................................... 12-1
12.5 NoneDeploying Inter-RAT ANR ................................................................................................. 12-1
12.5.3 Data Preparation .............................................................................................................. 12-1
12.5.4 Precautions ....................................................................................................................... 12-2
12.5.8 Reconfiguration ................................................................................................................ 12-3
12.5.9 Deactivation ...................................................................................................................... 12-3
12.6 Performance Optimization ......................................................................................................... 12-4
13 Engineering Guidelines for ANR with Shared Cells ....................................................13-1

13.1 When to Use ANR ..................................................................................................................... 13-1
Issue 08 (2013-05-20) Huawei Proprietary and Confidential iii

eRAN
13.5 Deploying ANR with Shared Cells ............................................................................................. 13-1

13.5.4 Precautions ....................................................................................................................... 13-2
13.5.9 Deactivation ...................................................................................................................... 13-3
13.6 Performance Optimization ......................................................................................................... 13-3
14 Engineering Guidelines X2 Automatic Management ..................................................14-1

14.5 Deploying X2 Self-Setup ........................................................................................................... 14-1
14.5.4 Precautions ....................................................................................................................... 14-2
14.5.9 Deactivation ...................................................................................................................... 14-4
14.6 Monitoring .................................................................................................................................. 14-4
14.7 Parameter Optimization ............................................................................................................ 14-8
15 Parameters .............................................................................................................................15-1
16 Counters..................................................................................................................................16-1
17 Glossary ..................................................................................................................................17-1
18 Reference Documents .........................................................................................................18-1
Issue 08 (2013-05-20) Huawei Proprietary and Confidential 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:
 LOFD-002001 Automatic Neighbour Relation (ANR)
 LOFD-002002 Inter-RAT ANR
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.
1.2 Intended Audience

This document is intended for:
 Personnel who need to understand ANR management
 Personnel who work with Huawei Long Term Evolution (LTE) products
1.3 Change History

This section provides information about the changes in different document versions.
There are two types of changes, which are defined as follows:
 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:
 08 (2013-05-20)
 07 (2013-03-15)
 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)
08 (2013-05-20)
Compared with issue 07 (2013-03-15) of eRAN3.0, issue 08 (2013-05-20) of eRAN3.0 includes the
following changes.
Issue 08 (2013-05-20) Huawei Proprietary and Confidential 1-1

eRAN
Change Type Change Description Parameter Change

Feature None None
change
Editorial Revised descriptions of the procedure for detecting None
change missing neighboring cells by using UE history
information. For details, see "Detecting Missing
Neighboring Cells by Using UE History Information" in
section 4.2.1 "Automatic Detection of Missing
Neighboring Cells."
Added descriptions of using the DRX mechanism to read None
ECGIs or CGIs of neighboring cells during intra-RAT or
inter-RAT ANR measurements. For details, see
"Detecting Missing Neighboring Cells by Using
Event-triggered UE Measurements" in section 4.2.1
"Automatic Detection of Missing Neighboring Cells" and
section 5.2.1 "Automatic Detection of Missing
Neighboring Cells."
Deleted descriptions of DRX being required for intra-RAT None
and inter-RAT ANR. For details, see sections 9.1.1
"Required Features" and 9.2.1 "Required Features."
(During intra-RAT and inter-RAT ANR measurements,
reading CGIs of neighboring cells using the DRX
mechanism does not require the activation of the DRX
feature.)
Added the section 8.4 "eNodeB Configuration Update None
Based on X2 Messages."
07 (2013-03-15)
following changes.

Feature change None None
Editorial change  Modified the flow chat for X2 self-setup. None
For details, see Figure 8-2 and Figure
8-3.
 Added the description that both the
source and target eNodeBs can send the
X2 Setup Request message during X2
self-setup. For details, see section 8.2
"X2 Self-Setup in X2 over S1 Mode" and
section 8.3 "X2 Self-Setup in X2 over
M2000 Mode."

eRAN
06 (2013-02-27)
following changes.

Editorial change Revised descriptions in chapter 6 None
"ANR with Shared Cells."
05 (2012-12-29)
following changes.

Feature change Added X2 self-setup. For details, Added the following parameters:
see the following chapters or  GlobalProcSwitch.X2SonLinkSetupType
sections:
 GlobalProcSwitch.X2SonSetupSwitch
 8 "X2 Self-Setup"
 X2SigIP.LOCIP
 9.3 "X2 Self-Setup"
 X2eNodeB.FIRSTSIGIP
 10.4 "X2 Self-Setup"
 14 "Engineering Guidelines X2
Automatic Management"
Editorial change Moved the license control ID. None
04 (2012-09-20)
following changes.

Editorial change Revised some descriptions. For details, see sections None
11.5.6 "Feature Activation", 12.5.6 "Feature Activation"
and13 "Engineering Guidelines for ANR with Shared
Cells."
03 (2012-06-30)
following changes.

eRAN

Feature change Added the function of ANR with Added the
shared cells. 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."
Editorial change Revised some descriptions. For None
details, see section 7.3.1 "Configuring
an HO Blacklist."
02 (2012-05-11)
following changes.

Editorial change Revised some descriptions in the document. 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.

Editorial change Revised the engineering guidelines. For details, None
see chapter 11 "Engineering Guidelines."
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.

Feature change Removed TempNRTs. None

eRAN

Modified the mechanism for adding a Deleted the AddCellThd parameter.
newly detected external neighboring cell to
an NCL.
Modified the mechanism for adding a
neighbor relation to an NRT.
For details, see "Automatic Maintenance of
NCLs" and "Automatic Maintenance of
NRTs" in section 4.2.2 "Automatic
Maintenance of NCLs and NRTs."
Modified the mechanism for removing an Changed the default value of the
external cell from an NCL. ANR.DelCellThd parameter.
Modified the mechanism for removing a Added the following parameters:
neighbor relation from an NRT.  ANR.StatisticPeriodForNRTDel
For details, see "Automatic Maintenance of  ANR.StatisticNumForNRTDel

NCLs" and "Automatic Maintenance of
NRTs" in section 4.2.2 "Automatic
Maintenance of NCLs and NRTs."
Modified the conditions for starting fast Changed the default value of the
ANR. ANR.FastAnrRprtInterval parameter.
Editorial change Optimized the engineering guidelines. None
Moved the information about PCI conflict None
detection to a new document named PCI
Conflict Detection and Self-Optimization.

eRAN
ANR Management 2 Overview of ANR
2 Overview of ANR
2.1 Introduction
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
2.2 Benefits
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.
2.3 Architecture
To implement ANR, the eNodeB collaborates with UEs and the M2000.

eRAN
ANR Management 3 Concepts Related to ANR
3 Concepts Related to ANR

3.1 Overview
This chapter describes basic ANR-related concepts, which include NCL, NRT, HO blacklist, X2 blacklist,
HO whitelist, X2 whitelist, radio resource control (RRC) blacklist, and abnormal neighboring cell
coverage.
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 Target Cell PLMN eNodeB ID Cell ID Removal Control Handover
Control
1 LCI#1 46001 eNodeB ID#1 Cell ID#1 Prohibited Prohibited
2 LCI#1 46001 eNodeB ID#2 Cell ID#2 Allowed Allowed
3 LCI#1 46001 eNodeB ID#3 Cell ID#3 Prohibited Prohibited
NOTE
For details about the NRT, see section 22.3.2a in 3GPP TS 36.300 V10.3.0 (2011-03). 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.

eRAN
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.
 Cell ID: identifies 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:
 Removal control = prohibited
 Handover control = prohibited
A neighbor relation can be added to the HO blacklist manually. For details, see section 5.2 in 3GPP TS
32.511 V10.0.0 (2011-03).
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.4.3 RRC Blacklist

An RRC blacklist contains the neighboring E-UTRAN cells whose information will not be measured and
reported to the eNodeB by UEs. You can manually add an intra- or inter-frequency neighboring cell to an
RRC blacklist.

eRAN
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:
 Removal control = prohibited
 Handover control = allowed
A neighbor relation can be added to the HO whitelist manually. For details, see section 5.2 in 3GPP TS
32.511 V10.0.0 (2011-03).
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.
3.6 Abnormal Neighboring Cell Coverage

Abnormal neighboring cell coverage may exist between intra-frequency E-UTRAN cells. As shown in
Figure 3-1, assume UEs in cell A detect signals from cell B. Then, ANR considers cell B to be a
neighboring cell of cell A and adds related information to an NCL or NRT. However, from a topology
perspective, the two cells do not meet the requirements for neighbor relations. In this situation, the
coverage of cell B is regarded as abnormal. This type of coverage is also called coverage overlap.
Figure 3-1 Abnormal neighboring cell coverage
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.
3.7 ANR Capabilities of UEs

The ANR capabilities of a UE refer to the ability of the UE to read the ECGIs of neighboring cells.
According to section B.1 in 3GPP TS 36.331 V10.1.0 (2011-03), the Feature Group Indicators bit string
contained in the UE Capability Information message indicates the ANR capability of the UE. Table 3-2
provides the definitions and setting descriptions of the ANR-related indicators.

eRAN
Table 3-2 Definitions and setting descriptions of the ANR-related indicators

Indicator Supported Functions (When the Indicator Remarks Applicability
Index Is Set to 1)
5  Long discontinuous reception (DRX) cycle N/A Yes
 DRX command Media Access Control
(MAC) element
16  Reporting of non-ANR-related periodical N/A Yes
intra-frequency measurements
 Reporting of non-ANR-related periodical
inter-frequency measurements is supported
if indicator 25 is also set to 1
 Reporting of non-ANR-related periodical
measurements of the UTRAN, GERAN,
CDMA2000 1xRTT, or CDMA2000 HRPD is
supported if indicator 22, 23, 24, or 26 is
also set to 1
NOTE
Non-ANR-related periodical measurements are the
measurements with trigger type and purpose set
to periodical and reportStrongestCells,
respectively. Event-triggered periodical
measurements are the measurements with trigger
type and reportAmount set to event and a value
greater than 1, respectively. Reporting of
event-triggered periodical measurements is a
mandatory function of event-triggered reporting
and therefore is not denoted by this indicator.
17  Reporting of SON-related or ANR-related This indicator can only Yes

periodical measurements be set to 1 when
 Reporting of ANR-related intra-frequency indicator 5 is set to 1.
events
18 Reporting of ANR-related inter-frequency This indicator can only Yes (unless the UE
events be set to 1 when only supports band
indicator 5 is set to 1. 13)
19 Reporting of ANR-related inter-RAT events This indicator can only N/A
be set to 1 when
indicator 5 is set to 1.
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.

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."
4.2 Intra-RAT Event-triggered ANR

Intra-RAT event-triggered ANR is controlled by the IntraRatEventAnrSwitch check box under the
ENodeBAlgoSwitch.AnrSwitch parameter. The intra-RAT event-triggered ANR function is activated
when the IntraRatEventAnrSwitch check box is selected.
Intra-RAT event-triggered ANR detects missing intra-RAT neighboring cells and abnormal neighboring
cell coverage, and maintains neighbor relations. For details, see the following sections in this chapter.
4.2.1 Automatic Detection of Missing Neighboring Cells

The procedure for using event-triggered UE measurements to detect missing neighboring cells is
defined in section 22.3.2a in 3GPP TS 36.300 V10.3.0 (2011-03).
ANR can detect missing neighboring cells by using UE history information in addition to even-triggered
UE measurements.
Detecting Missing Neighboring Cells by Using Event-triggered UE

Measurements
Intra-RAT event-triggered ANR detects cells with unknown PCIs based on the intra- and inter-frequency
measurement reports that contain information about cells meeting the handover requirements.
Assume that cell A and cell B are involved in a handover. The UE is under the coverage of cell A of the
source eNodeB, and cell B is a neighboring cell of cell A.
Table 4-1 lists the identification information about cell A and cell B.
Table 4-1 Identification information about cell A and cell B
Cell PCI ECGI
Cell A 3 17
Cell B 5 19

eRAN
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 procedure is described as follows:

1. The source eNodeB delivers the inter-frequency measurement configuration to the UE, instructing
the UE to measure inter-frequency neighboring cells that work on the frequencies specified in the
measurement configuration.
NOTE
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
During intra-RAT ANR measurement, the eNodeB sends a set of temporary DRX parameters to a UE. Then, both the
eNodeB and UE enter the DRX state. During sleep time, the UE reads the ECGIs of neighboring cells. Then, the eNodeB
and UE exit the DRX state. Note that reading ECGIs of neighboring cells using the DRX mechanism does not require the
DRX feature to be activated. For details about how DRX is used in intra-RAT ANR measurements, see DRX Feature
Parameter Description.

eRAN
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 section 7.3 in 3GPP TS 36.331 V10.1.0 (2011-03).
Timer Start Stop At Expiry

T321 Upon receiving measConfig Upon acquiring the information Initiate the measurement
including a reportConfig with needed to set all fields of reporting procedure, stop
the purpose set to reportCGI cellGlobalId for the requested cell, performing the related
upon receiving measConfig that measurements and
includes removal of the remove the
reportConfig with the purpose set to corresponding measId
reportCGI
5. The UE reports the parameter values to the source eNodeB.

The source eNodeB adds the newly detected neighboring cell (cell B) to the intra-RAT NCL and adds the
neighbor relation to the intra-RAT NRT of cell A.
Detecting Missing Neighboring Cells by Using UE History Information

During a handover, the source eNodeB sends UE history information to the target eNodeB. Figure 4-2
shows the procedure for detecting a missing intra-RAT neighboring cell by using UE history information.
NOTE
UE history information consists of information about all the cells that have provided services for the UE. Defined in section
9.2.1.42 of 3GPP TS 36.413 V10.1.0 (2011-03) and section 9.2.38 of 3GPP TS 36.423 V10.1.0 (2011-03), this information
includes:
 ECGI of the last visited cell
 Type of the last visited cell
 Duration of the UE for camping on the cell
Figure 4-2 Procedure for detecting a missing neighboring cell based on UE history information

1. The source eNodeB sends a Handover Request message to the target eNodeB.

eRAN
2. The target eNodeB obtains the UE history information from the message. The target eNodeB checks
whether the ECGI of the last visited cell (in this case, cell A, the source cell) is in the NCL of the target
eNodeB and then proceeds as follows:
 If the ECGI is in the NCL but is not in the NRT, the target eNodeB adds the neighbor relation to the
NRT and the procedure ends.
 If the ECGI is not in the NCL, the target eNodeB reports the ECGI of cell A to the M2000. The
procedure goes to step 3.
3. 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.
4. The target eNodeB adds cell A to its intra-RAT NCL.
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."
4.2.2 Automatic Maintenance of NCLs and NRTs

Automatic maintenance of NCLs and NRTs ensures the effectiveness of neighbor relations and therefore
significantly improves network performance.
To enable automatic removal of intra-RAT neighbor relations, select the IntraRatAnrAutoDelSwitch
check box under the ENodeBAlgoSwitch.AnrSwitch parameter.
When a network is unstable or in the early stage of deployment, you are advised to disable this
automatic removal by clearing the IntraRatAnrAutoDelSwitch check box. The purpose is to prevent
frequent NCL/NRT updating and to complete the collection of neighbor relations as soon as possible.
NOTE
During intra-RAT neighbor relation addition through ANR, attributes that cannot be obtained through measurement reports
or UE history information use default values.
Automatic Maintenance of NCLs

During automatic maintenance of NCLs, the eNodeB can automatically add a newly detected external
neighboring cell to or remove an external cell from an NCL:
 The eNodeB automatically adds a cell to an NCL in either of the following cases:
− The eNodeB detects a missing neighboring cell based on UE measurements and receives
information about this cell, including the ECGI, TAC, and PLMN ID list.
− The eNodeB detects a missing intra-RAT neighboring cell based on UE history information
 The eNodeB automatically removes an external cell from an NCL if the following conditions are all met:
− TheIntraRatAnrAutoDelSwitch check box under the ENodeBAlgoSwitch.AnrSwitch parameter is
selected. External cells can be automatically removed from NCLs only when this check box is
selected.
− Themeasurement 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.

eRAN
Automatic Maintenance of NRTs

During automatic maintenance of NRTs, the eNodeB can automatically add a neighbor relation to or
remove a neighbor relation from an NRT:
 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 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:
− Withina measurement period specified by the ANR.StatisticPeriodForNRTDel parameter, the total
number of all types of handover from the local cell to its neighboring cells is greater than or equal to
the value of ANR.StatisticNumForNRTDel.
− In
the same measurement period, cell A's PCI has never been included in any handover
measurement reports in the same measurement period.
Criterion 2, which includes the following two conditions:
− Within
a measurement period specified by the ANR.StatisticPeriod parameter, the number of
handovers from each of the cells under the eNodeB to cell A is greater than or equal to the value of
ANR.NcellHoStatNum.
− 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.
4.2.3 Automatic Detection of Abnormal Neighboring Cell Coverage

Abnormal neighboring cell coverage may exist between intra-frequency E-UTRAN cells. Abnormal
neighboring cell coverage decreases the handover success rate because of the abnormal neighbor
relations it causes. Therefore, detecting and eliminating abnormal neighboring cell coverage plays an
important role in network optimization.
If the IntraRatEventAnrSwitch check box is selected, automatic detection of abnormal neighboring cell
coverage is activated. When the M2000 receives an operator's request to query the information about
abnormal neighboring cell coverage, it triggers the algorithm for detecting abnormal neighboring cell
coverage and listing abnormal neighboring cells.
The M2000 checks for abnormal neighboring cell coverage based on the latitudes and longitudes of the
serving cell and its neighboring cells. Then, the M2000 collects statistics about abnormal neighboring
cell coverage and generates a list of abnormal neighboring cells for the serving cell.
NOTE
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.
To view abnormal neighboring cells, perform the following steps:

Step 1 Log in to the M2000.
Step 2 Choose Configuration > LTE Self Optimization > ANR Management.
Step 3 On the Neighbor Cell Management tab page, view abnormal neighboring cells in the Query
Cross-Coverage Cell pane.

eRAN
----End
4.3 Intra-RAT Fast ANR

Intra-RAT fast ANR enables the eNodeB to quickly obtain information about all qualified neighboring
cells based on periodic UE measurements. This reduces the adverse impact of event-triggered UE
measurements on handover performance.
Intra-RAT fast ANR is enabled if the IntraRatFastAnrSwitch check box is selected.
Before UEs perform handovers, they periodically send measurement reports so that the eNodeB learns
about all neighboring cells whose reference signal received power (RSRP) values are greater than or
equal to the value of ANR.FastAnrRsrpThd.
After intra-RAT fast ANR is enabled, the eNodeB randomly selects fast-ANR-capable UEs to perform
intra- and inter-frequency measurements. After receiving periodic measurement reports from these UEs,
the eNodeB adds missing neighboring cells to NCLs. The procedure for detecting a missing neighboring
cell using fast ANR is the same as that using event-triggered ANR based on UE measurements, which is
detailed in "Detecting Missing Neighboring Cells by Using Event-triggered UE Measurements" in section
4.2.1 "Automatic Detection of Missing Neighboring Cells." However, after 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
ANR.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. This is repeated until the eNodeB
deactivates intra-RAT fast ANR. The upper limit is specified by the ANR.FastAnrRprtAmount
parameter. The interval for UEs to report periodic measurements is specified by the
ANR.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. At a regular interval,
specified by the ANR.FastAnrCheckPeriod parameter, the eNodeB checks whether the total number of
involved UEs is greater than the upper limit. The upper limit is specified by the
ANR.FastAnrIntraRatUeNumThd parameter. If yes, the eNodeB automatically deactivates intra-RAT
fast ANR. If no, periodic UE measurements continue.

eRAN
Process
Figure 4-3 shows an intra-RAT fast ANR process.
Figure 4-3 Intra-RAT fast ANR process
In summary, an intra-RAT fast ANR process is as follows:

1. After intra-RAT fast ANR is activated, the eNodeB starts a check period (ANR.FastAnrCheckPeriod)
and selects UEs to perform intra- and inter-frequency measurements to detect the PCIs of unknown

eRAN
cells. The number of UEs that can be selected is specified by the

ANR.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 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."
Impact on System Performance

Generalized from intra-RAT fast ANR, fast ANR includes two UE-performed processes: periodical PCI
reporting and CGI reading. In the periodical PCI reporting process, the UE periodically reports the PCI of
the neighboring cell with the best signal quality. In the CGI reading process, the UE reads the CGIs of
unknown cells.
 Periodical PCI reporting
− With
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.
− Withrespect 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 section 8.1.2 of
3GPP TS 36.133 V10.2.0 (2011-04): pattern 0 and pattern 1. They are described in Table 4-2. To
accelerate measurements, patter 0 is used by default.
Table 4-2 Gap patterns
Measurement Gap Width (Unit: ms) Gap Repetition Target RAT
Gap Pattern Period (Unit: ms)
0 6 40  Inter-Frequency FDD E-UTRAN
 Inter-Frequency TDD E-UTRAN
 FDD UTRAN
 GERAN
 TDD low chip rate (LCR)
 CDMA2000 HRPD
 CDMA2000 1X

eRAN
Measurement Gap Width (Unit: ms) Gap Repetition Target RAT

Gap Pattern Period (Unit: ms)
1 6 80  Inter-Frequency FDD E-UTRAN
 Inter-Frequency TDD E-UTRAN
 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.
In conclusion, fast ANR impacts system performance as follows:
 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."

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.
5.2 Inter-RAT Event-triggered ANR

Inter-RAT event-triggered ANR is enabled if the GeranEventAnrSwitch or UtranEventAnrSwitch
check box under the ENodeBAlgoSwitch.AnrSwitch parameter is selected.
After inter-RAT event-triggered ANR is activated, the eNodeB delivers inter-RAT measurement
configurations to the UE and instructs the UE to perform periodic measurements on neighboring GERAN
or UTRAN cells.
NOTE
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.
 It is complex for the E-UTRAN to detect anomalies in other RATs.
5.2.1 Automatic Detection of Missing Neighboring Cells

This section describes how inter-RAT event-triggered ANR detects a missing neighboring UTRAN cell.
Assume that cell A is an E-UTRAN cell and cell B is a UTRAN cell. The UE is under the coverage of cell
A, and cell B is an inter-RAT neighboring cell of cell A.
Figure 5-1 shows how the eNodeB detects cell B by using event-triggered UE measurements.

eRAN
Figure 5-1 Procedure for detecting a missing inter-RAT neighboring cell by using event-triggered UE
measurements

1. The source eNodeB delivers the inter-RAT measurement configuration (including target RATs and
ARFCNs) to the UE, activates the measurement gap mode, and instructs the UE to measure the
neighboring cells that meet the measurement requirements.
NOTE
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.
NOTE
During inter-RAT ANR measurement, the eNodeB sends a set of temporary DRX parameters to a UE. Then, both the
eNodeB and UE enter the DRX state. During sleep time, the UE reads the CGIs of neighboring cells. Then, the eNodeB
and UE exit the DRX state. Note that reading CGIs of neighboring cells using the DRX mechanism does not require the
DRX feature to be activated. For details about how DRX is used in inter-RAT ANR measurements, see DRX Feature
The source eNodeB adds the newly detected neighboring cell to its inter-RAT NCL and adds the
neighbor relation to the inter-RAT NRT.

eRAN
5.2.2 Automatic Maintenance of NCLs and NRTs

Automatic maintenance of NCLs and NRTs ensures the effectiveness of neighbor relations, which
improves network performance.
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 UtranAutoNrtDeleteSwitch, GeranAutoNrtDeleteSwitch, and CdmaAutoNrtDeleteSwitch check

boxes under the ENodeBAlgoSwitch.AnrSwitch parameter control the automatic removal of neighbor relations with
UTRAN, GERAN, and CDMA2000, respectively.
During inter-RAT neighbor relation addition through ANR, attributes that cannot be obtained through measurement reports
or UE history information use default values.
Automatic Maintenance of NCLs

During automatic maintenance of NCLs, the eNodeB can automatically add a newly detected external
neighboring cell to or remove an external cell from an NCL:
 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:
− TheUtranAutoNrtDeleteSwitch, GeranAutoNrtDeleteSwitch, or CdmaAutoNrtDeleteSwitch
check box under the ENodeBAlgoSwitch.AnrSwitch parameter is selected.
− Themeasurement 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.
Automatic Maintenance of NRTs

During automatic maintenance of NRTs, the eNodeB can automatically add a neighbor relation to or
remove a neighbor relation from an NRT:
 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:
− Thenumber of neighbor relations in the NRT has reached the maximum specification and a new
neighbor relation is to be added to the NRT.
− Withina measurement period specified by the ANR.StatisticPeriodForNRTDel parameter, the
number of handovers from the local cell to its inter-RAT neighboring cells is greater than or equal to
the value of ANR.StatisticNumForNRTDel. A group of neighboring cells that have the removal

eRAN
control flag set to allow removal have never been measured as the target cell of these handovers. In
this case, the eNodeB randomly removes a neighboring cell in this group from the NRT.
NOTE
Automatic removal of neighbor relations with CDMA2000 is not yet a requirement; therefore, it is not implemented in
eRAN3.0.
5.3 Inter-RAT Fast ANR

Inter-RAT fast ANR is enabled if the GeranFastAnrSwitch, UtranFastAnrSwitch, or
CdmaFastAnrSwitch check box under the ENodeBAlgoSwitch.AnrSwitch parameter is selected.
After inter-RAT fast ANR is activated, the eNodeB delivers inter-RAT measurement configurations to the
UE and instructs the UE to perform periodic measurements on neighboring GERAN, UTRAN, and CDMA
cells.
The principles of inter-RAT fast ANR are almost the same as those of intra-RAT fast ANR. For details
about the principles and relevant parameter settings, see section 4.3 "Intra-RAT Fast ANR."
For fast ANR with UTRAN and CDMA2000, the information element (IE) reportStrongestCellsForSON is
configured on the eNodeB for fast ANR measurements. According to section 6.3.5 in 3GPP TS 36.331
V10.1.0 (2011-03), when the measurement type is set to reportStrongestCellsForSON, reportAmount
can only be set to 1, which means that the UE sends only one measurement report to the eNodeB at one
time. In this case, the user-defined measurement period does not take effect. For the UE to periodically
transmit measurement reports, the fast ANR algorithm sets and sends reportStrongestCellsForSON to
the UE at an unconfigurable period.
In terms of parameters, inter-RAT fast ANR differs from intra-RAT fast ANR in the following ways:
 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 Parameter Determining the Signal Quality Threshold
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."

eRAN
ANR Management 6 ANR with Shared Cells
6 ANR with Shared Cells

Currently, the ANR with shared cells function automatically sets up neighbor relations with E-UTRAN
cells that are shared by PLMNs. In this chapter, neighboring cells refer to neighboring E-UTRAN cells
unless otherwise stated.
If a neighboring cell is shared by PLMNs and broadcasts its PLMN list in a round robin (RR) manner, a
UE in its serving cell might not be able to obtain the correct serving PLMN list of the neighboring cell. If
the shared neighboring cell does not broadcast its PLMN list in an RR manner, a UE in its serving cell
might not report a complete PLMN list of the neighboring cell to the serving cell. As a result of either case,
neighbor relations cannot be correctly added. To solve this problem, the serving cell can request that the
M2000 send the serving PLMN list of the neighboring cell. This solution works if the serving and
neighboring cells are managed by the same M2000, which stores the configuration data and status
information about the neighboring cell.
NOTE
eRAN3.0 does not support ANR with shared UTRAN or GERAN cells.
6.1 Shared Neighboring Cell Broadcasting PLMN List in an RR

Manner
ANR with shared cells that broadcast PLMN lists in an RR manner requires that
NBSLTEPLMNRoundSwitch under the ENodeBAlgoSwitch.RanSharingAnrSwitch parameter be
turned on.
If NBSLTEPLMNRoundSwitch is turned on and the serving eNodeB of a UE receives a measurement
report containing the CGI (PLMN ID+eNodeB ID+cell ID) of a neighboring cell, the serving eNodeB
reports the PCI and CGI obtained by the UE to the M2000. The M2000 queries the primary PLMN and
serving PLMN list of the neighboring cell based on the PCI, eNodeB ID, and cell ID. The M2000 then
sends the query result to the serving eNodeB. The serving eNodeB adds the PLMN information to the
external cell configuration and PLMN list configuration corresponding to the neighboring cell.
In a handover procedure, as shown in Figure 6-1, if cell A (the source cell) is shared by PLMNs and the
target eNodeB providing cell B detects from UE history information that cell A has not been configured as
a neighboring cell of cell B, the target eNodeB adds the information about cell A to the intra-RAT NCL.
The target eNodeB also adds the information about the secondary operators of cell A to the PLMN list
configurations of the external cell for cell B.

eRAN
ANR Management 6 ANR with Shared Cells
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.
6.2 Shared Neighboring Cell Not Broadcasting PLMN List in an

RR Manner
ANR with shared cells that do not broadcast PLMN lists in an RR manner requires that
NBSLTERANSharingSwitch under the ENodeBAlgoSwitch.RanSharingAnrSwitch parameter be
turned on.
If NBSLTERANSharingSwitch is turned on and NBSLTEPLMNRoundSwitch is turned off, and if the
serving eNodeB of a UE receives a measurement report containing the CGI of a neighboring cell, the
serving eNodeB takes one of the following actions:
 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."

eRAN
ANR Management 7 Manual Management of Neighbor Relations
7 Manual Management of Neighbor Relations

7.1 Overview
Generally, neighbor relations are managed by ANR automatically. In some cases, they need to be
managed manually.
The manual management tasks are as follows:
 Adding or removing a neighbor relation
 Blacklisting a neighbor relation
 Whitelisting a neighbor relation
The latest manually maintained neighbor relations are kept in NRTs.
7.2 Adding or Removing a Neighbor Relation

To manually add or remove a neighbor relation, configure the corresponding managed objects (MOs), as
listed in the following table.
To Add or Remove a Neighbor Relation with... Configure the MO...

Intra-frequency E-UTRAN cell EutranIntraFreqNCell
Inter-frequency E-UTRAN cell EutranInterFreqNCell
UTRAN cell UtranNCell
GERAN cell GeranNcell
CDMA2000 1xRTT cell Cdma20001XRTTNcell
CDMA2000 HRPD cell Cdma2000HrpdNcell
For details, see Mobility Management in Connected Mode Feature Parameter Description.
If ANR is activated, neighbor relations are added or removed automatically.
7.3 Blacklisting a Neighbor Relation

7.3.1 Configuring an HO Blacklist
HO blacklists can only be configured manually. If an NRT contains a neighbor relation that has been
included in an HO blacklist, this neighbor relation cannot be automatically removed from the NRT.
A neighbor relation needs to be added to an HO blacklist in some special cases, for example, if the
neighbor relation causes coverage overlap and leads to unstable handovers.
To blacklist a neighbor relation, perform the following steps:
Step 3 On the Neighbor Cell Management tab page, select a neighbor relation to be blacklisted in the
Neighboring Cell pane.

eRAN
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.
7.3.2 Configuring an X2 Blacklist

X2 blacklists can only be configured manually.
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.
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 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.
7.3.3 Configuring an RRC Blacklist

UEs are not allowed to measure or be handed over to the cells contained in RRC blacklists. To configure
intra- or inter-frequency RRC blacklists, configure the IntraFreqBlkCell and InterFreqBlkCell MOs.

eRAN
7.4 Whitelisting a Neighbor Relation

7.4.1 Configuring an HO Whitelist
HO whitelists can only be configured manually. If an NRT contains a neighbor relation that has been
included in an HO whitelist, this neighbor relation cannot be automatically removed from the NRT for a
handover.
HO whitelists are especially useful in the early phase of network construction. In this phase, there are
usually a small number of UEs. Therefore, the best practice to collect neighbor relation information as
soon as possible is to prohibit ANR from automatically removing neighbor relations.
To whitelist a neighbor relation, perform the following steps:
Step 3 On the Neighbor Cell Management tab page, select a neighbor relation to be whitelisted in the
Neighboring Cell pane.
Step 4 Set Deletion Prohibited to TRUE and Handover Prohibited to FALSE in the displayed Set
dialog box.
----End
Alternatively, to whitelist a neighbor relation, you can set the EutranInterFreqNCell.NoHoFlag

parameter to PERMIT_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.
7.4.2 Configuring an X2 Whitelist

X2 whitelists can only be configured manually.
An X2 whitelist is especially useful when it takes a long time to maintain an eNodeB. During the
maintenance, the eNodeB cannot provide any services, and the NRTs of this eNodeB and its
surrounding eNodeBs may change. To avoid this situation, you can add the associated eNodeBs to the
X2 whitelist.
To configure an X2 whitelist, perform the following steps:

eRAN
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.

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 X2 setup modes are described as follows:

 Link configuration mode
Users configure control-plane bearers (SCTP links) and user-plane bearers (IP paths) and negotiate
port information about the local eNodeB and peer eNodeB.
 End point configuration mode (also called self-setup mode)
After users configure ports, the eNodeBs automatically set up control-plane bearers (SCTP links) and
user-plane bearers (IP paths) for the X2 interface between the eNodeBs.
In end point configuration mode, the X2 self-setup procedure varies depending on whether the
neighboring eNodeB has been manually configured using an X2eNodeB MO.
− X2 self-setup with X2eNodeB manually configured
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 self-setup with X2eNodeB automatically configured

eRAN
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.
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.
8.2 X2 Self-Setup in X2 over S1 Mode

In X2 over S1 mode, the MME collects the configuration information about neighboring eNodeBs. Figure
8-2 shows the setup procedure.

eRAN
Figure 8-2 Procedure for X2 self-setup in X2 over S1 mode
The procedure is as follows:

1. When a handover is triggered, the source eNodeB checks whether an X2 interface is available
between the source eNodeB and the target eNodeB.
− If the X2 interface is available, an X2-based handover is performed.
− 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 and user-plane IP addresses of the source eNodeB

eRAN
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. When signaling exchange over the S1 interface is complete, an eNodeB sends an X2 setup request
to the peer eNodeB and the peer eNodeB responds to the request. An X2 interface is automatically
set up. Note that before receiving an X2 Setup Request message, both the source eNodeB and the
target eNodeB can send the X2 Setup Request message to and receive the X2 Setup Response
message from the peer end.
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.
8.3 X2 Self-Setup in X2 over M2000 Mode

In X2 over M2000 mode, the M2000 collects the configuration information about neighboring eNodeBs.
Figure 8-3 shows the setup procedure.

eRAN
Figure 8-3 Procedure for X2 self-setup in X2 over M2000 mode
The procedure is as follows:

1. When a handover is triggered, the source eNodeB checks whether an X2 interface is available
between the source eNodeB and the target eNodeB.
− If the X2 interface is available, an X2-based handover is performed.
− 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.

eRAN
5. The source and target eNodeBs set up an SCTP link between them. The control plane on the X2
interface is set up. Note that before receiving an X2 Setup Request message, both the source
eNodeB and the target eNodeB can send the X2 Setup Request message to and receive the X2
Setup Response message from the peer end.
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.
8.4 eNodeB Configuration Update Based on X2 Messages

If an X2 interface is configured between two eNodeBs, the eNodeB information is exchanged through
the X2 interface during an X2 setup and eNodeB configuration updates. For details on the messages
transmitted during X2 setups and eNodeB configuration updates, see section 8.3 in 3GPP TS 36.423
V10.0.0 (2010-12).
After an X2 interface is configured between two eNodeBs, the eNodeB information is updated, as
outlined in Figure 8-4.
Figure 8-4 X2 setup
1. After receiving an X2 Setup Request message from eNodeB 1, eNodeB 2 adds all cells under
eNodeB 1 to the NCL of eNodeB 2 if GlobalProcSwitch.X2BasedUptENodeBCfgSwitch is set to
ON for eNodeB 2.
2. eNodeB 2 responds with an X2 Setup Response message. After receiving this message, eNodeB 1
adds all cells under eNodeB 2 to the NCL of eNodeB 1 if
GlobalProcSwitch.X2BasedUptENodeBCfgSwitch is set to ON for eNodeB 1.
After the configuration of an eNodeB is updated, the configuration is updated in the peer eNodeB, as
outlined in Figure 8-5.
Figure 8-5 eNodeB configuration update

eRAN
1. When the local cell or neighboring cell configuration changes in eNodeB 1, eNodeB 1 sends an
eNodeB Configuration Update message to eNodeB 2.
After eNodeB 2 receives the message, it performs the following operations if

GlobalProcSwitch.X2BasedUptENodeBCfgSwitch is set to ON:
 If the NCL of eNodeB 2 does not contain the cell in the message, eNodeB 2 adds the cell to its NCL.
 If the NCL of eNodeB 2 contains the cell in the message, eNodeB 2 updates its NCL and NRTs. The updated
information includes the operating frequency, PCI, ECGI, TAC, and PLMN list.
If no active cell exists under eNodeB 1, the configuration change information cannot be sent to eNodeB 2 through X2
messages.
2. eNodeB 2 responds with an eNodeB Configuration Update Acknowledge message.
Before modifying eNodeB configuration data (such as eNodeBId, CellId, LocalCellId, CnOperator,
CnOperatorTa, CellOp, PhyCellId, or DlEarfcn) on a CME, set
GlobalProcSwitch.X2BasedUptENodeBCfgSwitch to OFF. This ensures that configuration data will
not be automatically updated based on X2 messages when configuration data is modified through the
CME, avoiding the conflict between the two data modification procedures.

eRAN
ANR Management 9 Related Features
9 Related Features
9.1 Intra-RAT ANR
9.1.1 Required Features
None
9.1.2 Mutually Exclusive Features

None
9.1.3 Affected Features

Intra-RAT ANR has an impact on LOFD-002007 PCI Collision Detection & Self-Optimization.
When neighboring cell information changes because of intra-RAT ANR, PCI conflict detection is
triggered.
9.2 Inter-RAT ANR

None

None

None
9.3 X2 Self-Setup
None

None

None

eRAN
ANR Management 10 Impact on the Network
10 Impact on the Network

10.1 Intra-RAT ANR
10.1.1 Impact on System Capacity
N/A
10.1.2 Impact on Network Performance

Intra-RAT event-triggered ANR introduces extra delays in handovers of the UEs that meet the handover
conditions but are still performing ANR periodic measurements. In addition, it affects the UE throughput
because UEs cannot be scheduled when they are reading the CGI and other information about an
unknown cell during DRX periods.
Intra-RAT fast ANR has the following influence on network performance:
 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.
 The UE throughput drops when:
− TheUE 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 UE performs gap-assisted measurements on inter-frequency or inter-RAT neighboring cells.
 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:
 Intra-frequency Handover Out Success Rate
 Inter-frequency Handover Out Success Rate
 Service Drop Rate
Service Drop Rate = (L.E-RAB.AbnormRel/L.E-RAB.NormRel + L.E-RAB.AbnormRel) x 100%
Where, L.E-RAB.AbnormRel provides the number of abnormally released E-RABs and
L.E-RAB.NormRel provides the number of normally released E-RABs.
10.2 Inter-RAT ANR

N/A

Inter-RAT ANR has basically the same influence on network performance as intra-RAT ANR does. The
difference is that inter-RAT ANR has an impact on the following KPIs:

eRAN
ANR Management 10 Impact on the Network
 Inter-RAT Handover Out Success Rate (LTE to CDMA)

 Inter-RAT Handover Out Success Rate (LTE to WCDMA)
 Inter-RAT Handover Out Success Rate (LTE to GSM)
10.3 ANR with Shared Cells

N/A

If the switch for ANR with shared cells (specified by the ENodeBAlgoSwitch.RanSharingAnrSwitch
parameter) is turned on, the serving eNodeB of a UE may query the M2000 for the neighboring cell
information. The query time is long and therefore might affect the handover. If no other neighboring cells
are available for the handover, a service drop may occur. However, after the serving eNodeB obtains the
neighboring cell information from the M2000, the information can be used in subsequent handovers to
the neighboring cell.
ANR with shared cells decreases the service drop rate and increases the handover success rate. The
related KPIs are as follows:
 Intra-frequency Handover Out Success Rate
 Inter-frequency Handover Out Success Rate
 Handover In Success Rate
 Service Drop Rate
10.4 X2 Self-Setup
X2 self-setup has no impact on system capacity.

X2 self-setup reduces the workload required for manually planning and configuring X2 interfaces. In
addition, after X2 self-setup is complete, X2-based handovers take less time than S1-based handovers.

eRAN
ANR Management 11 Engineering Guidelines for Intra-RAT ANR
11 Engineering Guidelines for Intra-RAT ANR

11.1 When to Use 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.
Intra-RAT Event-triggered ANR

Consider the following when determining whether to use intra-RAT event-triggered ANR:
 The prerequisites for using intra-RAT event-triggered ANR are as follows:
Operators have deployed ANR-capable UEs on the network.
 Intra-RAT event-triggered ANR is enabled in any of the following cases:
− Network construction is in progress. The purpose is to complete and optimize existing 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-RATfast 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.
Intra-RAT Fast ANR

Consider the following when determining whether to use intra-RAT fast ANR.
 The prerequisites for using intra-RAT fast ANR are as follows:
Operators have deployed ANR-capable UEs on the network.
 Intra-RAT fast ANR is enabled in any of the following cases:
− Network construction is at an early stage. The purpose is to quickly collect neighbor relations.
− Networkcapacity 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.
 Intra-RAT event-triggered ANR is not recommended in either of the following cases:
− The network is well constructed and serves a moderate number of UEs, and basic neighbor relations
are configured.
− Users want to manually manage neighbor relations.
NOTE
If both event-triggered ANR and fast ANR are enabled, they separately detect missing neighboring cells by using their own
mechanisms.

eRAN
11.2 Information to Be Collected

Collect the following information:
 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.
 Networking mode (intra- or inter-frequency networking)
11.3 Network Planning

N/A
11.4 Overall Deployment Procedure

None
11.5 Deploying Intra-RAT ANR

This section describes the process of deploying intra-RAT ANR.
11.5.1 Deployment Procedure

None
11.5.2 Deployment Requirements

 UEs on the network support ANR-related measurements on intra- or inter-frequency neighboring cells
and are DRX-capable.
 An M2000 of iManager M2000 V200R012C00 or later is used.
 The intra-RAT measurement information (including frequencies to be measured) has been configured.
 Operators have purchased and activated the license pertaining to intra-RAT ANR. Table 11-1 provides
the license control item.
Table 11-1 License control items related to intra-RAT ANR
Feature License Control Item Name
LOFD-002001 Automatic Neighbour Relation (ANR) Automatic Neighbour Relation (ANR)
11.5.3 Data Preparation

The following table describes the parameter that must be set in the EnodeBAlgoSwitch MO to
configure eNodeB-level algorithm switches.

eRAN
Parameter Parameter ID Source Setting Description

Name
ANR algorithm AnrSwitch Network plan Select or clear the following check boxes by
switch (negotiation not referring to section 11.1 "When to Use ANR."
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.

Name
Network plan This parameter specifies the mobile country code
(negotiation not (MCC) of the neighboring eNodeB at the other end
Mobile
X2BlackWhiteList. required) of this X2 interface.
network
Mcc This parameter references the corresponding
code
parameter in the eNodeB MO on the neighboring
eNodeB.
Network plan This parameter specifies the mobile network code
(negotiation not (MNC) of the neighboring eNodeB at the other end
Mobile
X2BlackWhiteList. required) of this X2 interface.
network
Mnc This parameter references the corresponding
code
eNodeB.
Network plan This parameter specifies the ID of the neighboring
(negotiation not eNodeB at the other end of this X2 interface. This
eNodeB X2BlackWhiteList. required) ID uniquely identifies an eNodeB in a network.
identity ENodeBId This parameter references the corresponding
eNodeB.
X2 Black or Network plan This parameter specifies whether this X2 interface

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
11.5.5 Hardware Adjustment

N/A

eRAN
11.5.6 Feature Activation

Configuring a Single eNodeB Using the GUI
Configure a single eNodeB in the general configuration window on the Configuration Management
Express (CME) based on the MO and parameters as described in section 11.5.3 "Data Preparation."
See the M2000 Help for more information about operations in the general configuration window. Press
F1 to launch M2000 Help. Navigate to Introduction to the LTE General Configuration Window and
refer to the generic procedure for setting parameters using the CME graphical user interface (GUI).
To find MOs in the planned area, use either of the following methods:
 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.
Configuring eNodeBs in Batches

To configure eNodeBs in batches, perform the following steps:
Step 1 On the GUI, set the parameters listed in the table for a specific scenario in this section, and save
the parameter settings as a user-defined template.
The parameters are the same as those described in section 11.5.3 "Data Preparation."
Step 2 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 Group Name Parameter

ENODEBALGOSWITCH ENodeBAlgoSwitch ANR algorithm switch
X2BLACKWHITELIST X2BlackWhiteList Mcc, Mnc, EnodeBId, X2ListType
Configuring a Single eNodeB Using MML Commands

Step 1 Run the MOD ENODEBALGOSWITCH command to enable intra-RAT ANR.
Step 2 (Optional) Run the ADD X2BLACKWHITELIST command to add an X2 blacklist or whitelist.
----End

eRAN
11.5.7 Activation Observation

By using signaling tracing, SON logs on the M2000 client, or MML commands, you can check whether
intra-RAT ANR has been activated.
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
SON Logs on the M2000 Client

The procedure for activation observation by checking SON logs on the M2000 client is as follows:
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

eRAN
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.
 If ANR flag is True, the intra-RAT neighbor relation is configured by ANR.
 If ANR flag is False, the intra-RAT neighbor relation is manually configured.
----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
11.6 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.
11.7 Parameter Optimization

The following parameters may need to be modified after intra-RAT ANR is activated.
Parameter Parameter ID Setting Description

Name
ANR delete cell ANR.DelCellThd This parameter specifies the handover success rate threshold,
threshold which is used in the evaluation for removing a neighbor relation
from the intra-RAT NRT based on the handover success rate. A
larger parameter value results in a higher probability of removing a
neighbor relation from this NRT.
The default value is 0 so that it is difficult to remove a neighbor
relation.

eRAN

Name
Least Handover ANR.NcellHoStatN This parameter specifies the threshold for the number of handovers
Num for Statistic um to neighboring cells, which is used in the evaluation for removing a
neighbor relation from the intra-RAT NRT based on the handover
success rate. A larger parameter value results in more stable
neighbor relations in the intra-RAT NRT; however, updates to this
NRT take longer. If only a small number of UEs are involved in
periodic measurements on the live network, reduce this parameter
value to accelerate NRT updates.
Statistic cycle ANR.StatisticPerio This parameter specifies the measurement period, which is used in
d the evaluation for removing a neighbor relation from the intra-RAT
NRT based on the handover success rate. At the end of this period,
the eNodeB automatically analyzes neighbor relations. A larger
parameter value may result in more UE handover requests;
however, updates to the intra-RAT NRT take longer. Tune this
parameter based on the total number of daily handover requests on
the live network. If many UEs are involved in periodic
measurements, reduce this parameter value to accelerate NRT
updates.
Statistic Number ANR.StatisticNum This parameter specifies the threshold for the number of handovers
For Delete NRT ForNRTDel to neighboring cells, which is used in the evaluation for removing a
neighbor relation from the intra-RAT NRT based on the outgoing
handovers. It is used in the automatic analysis of neighbor
relations. A larger parameter value results in more stable neighbor
relations in the intra-RAT NRT; however, updates to this NRT take
longer. If only a small number of UEs are involved in periodic
measurements on the live network, reduce this parameter value to
accelerate NRT updates.
Statistic Cycle ANR.StatisticPerio This parameter specifies the measurement period, which is used in
For Delete NRT dForNRTDel the evaluation for removing a neighbor relation from the intra-RAT
NRT based on the outgoing handovers. At the end of this period,
the eNodeB automatically analyzes neighbor relations. A larger
parameter value may result in more UE handover requests;
however, updates to the intra-RAT NRT take longer. Tune this
parameter based on the total number of daily handover requests on
the live network. If many UEs are involved in periodic
measurements, reduce this parameter value to accelerate NRT
updates.
Fast ANR PCI ANR.FastAnrRprt This parameter specifies the maximum number of periodic
report amount Amount measurement reports sent by a UE during each ANR procedure. It
implies the total measurement amount.
If only a small number of UEs are involved in periodic
measurements, increase this parameter value. Otherwise, reduce
it.
If services on most of the UEs have relatively high QoS class
identifiers (QCIs), reduce this parameter value to ensure service
quality and reduce power consumption of the UEs.

eRAN

Name
Fast ANR PCI ANR.FastAnrRprtI This parameter specifies the interval at which a UE sends periodic
report interval nterval measurement reports. A larger parameter value results in a shorter
interval. Tune this parameter based on the moving speed of most
UEs involved. If most of the UEs move quickly through a constantly
changing set of neighboring cells, reduce the parameter value to
shorten this interval. Otherwise, increase it.
Fast ANR ANR.FastAnrChec This parameter specifies the interval at which the eNodeB checks
checking period kPeriod whether the total number of UEs involved in periodic
measurements reaches the upper limit. If only a few UEs
participate in fast ANR, increase this parameter value. Otherwise,
reduce it.
If services on most of the UEs have relatively high QoS class
identifiers (QCIs), reduce this parameter value to ensure service
quality and reduce power consumption of the UEs.
Fast ANR ANR.FastAnrRsrp This parameter specifies the RSRP requirement for adding a
measurement Thd neighboring cell to the NCL. A larger parameter value results in a
RSRP threshold higher RSRP requirement; therefore the neighboring cells in the
NCL have higher signal quality. In urban areas with densely
distributed cells, increase this parameter value to ensure that only
high-quality neighboring cells are added to the NCL. In contrast, in
sparsely populated areas, reduce the parameter value to add to the
NCL the neighboring cells that cover the partial cell edge with low
RSRP values.
IntraRat Fast ANR.FastAnrIntra This parameter specifies the maximum number of UEs that are
ANR RatMeasUeNum concurrently involved in intra-RAT periodic measurements. A larger
measurement parameter value results in more UEs that can concurrently perform
UE number periodic measurements. In this situation, neighboring cells can be
quickly detected. However, this affects the service quality for these
UEs and the uplink throughput of the network.
IntraRat Fast ANR.FastAnrIntra This parameter specifies the upper limit for the total number of UEs
ANR valid RatUeNumThd involved in intra-RAT periodic measurements. A larger parameter
measurement value results in 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.
Optimization ANR.OptMode This parameter specifies the mode for optimizing neighbor
Mode relations. If users require ANR to automatically optimize neighbor
relations, set this parameter to FREE(FREE). If users require
manual confirmation on the M2000 before neighbor relations are
optimized, set this parameter to CONTROLLED(CONTROLLED).
ter Optimization
None

eRAN
11.8 Troubleshooting
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 not delivered the handover command, go to step 2.

 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.
 If they have not been configured, go to step 3.
 If they have been configured, contact Huawei engineers.
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.
 If the switch has been turned on, contact Huawei engineers.
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.

eRAN
 If the UE does not support intra-RAT ANR, no further action is required.

----End

eRAN
ANR Management 12 Engineering Guidelines for Inter-RAT ANR
12 Engineering Guidelines for Inter-RAT ANR

Inter-RAT ANR consists of inter-RAT event-triggered ANR and inter-RAT fast ANR. The same
considerations should be made when determining whether to use inter-RAT ANR as when determining
whether to use intra-RAT ANR. For details, see section 11.1 "When to Use 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

N/A

12.5 NoneDeploying Inter-RAT ANR
This section describes the process of deploying inter-RAT ANR.

None

 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.
 Operators have purchased and activated the license pertaining to inter-RAT ANR. Table 12-1 provides
the license control item.
Table 12-1 License control items related to inter-RAT ANR
LOFD-002002 Inter-RAT ANR Inter-RAT ANR

The following table describes the parameter that must be set in the EnodeBAlgoSwitch MO to
configure eNodeB-level algorithm switches.

eRAN

Name
ANR AnrSwitch Network plan Select or clear the following check boxes by
algorithm (negotiation not referring to section 12.1 "When to Use ANR":
switch 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.

Name
Long DRX LongDRXCyclef Network plan Set this parameter based on the networking mode
Cycle for orIRatAnr (negotiation not collected in section 11.2 "Information to Be
Inter-RAT ANR required) Collected".
 If a neighboring UTRAN exists, set this parameter
to SF1280, which is the default value.
 If a neighboring GERAN exists, set this parameter
to SF2560.
 If both exist, set this parameter to SF2560.
12.5.4 Precautions
None

N/A

Configure a single eNodeB in the general configuration window on the CME based on the MO and
parameters as described in section 12.5.3 "Data Preparation"
refer to the generic procedure for setting parameters using the CME GUI.

eRAN
navigation tree.

To configure eNodeBs in batches, perform the following steps:
Step 1 On the GUI, set the parameters listed in the table for a specific scenario in this section, and save
the parameter settings as a user-defined template.
The parameters are the same as those described in section 12.5.3 "Data Preparation."
----End
A user-defined template is required. The following table lists the recommended distribution of the

ENODEBALGOSWITCH ENodeBAlgoSwitch ANR algorithm switch

Run the MOD ENODEBALGOSWITCH command to enable inter-RAT ANR.

The procedure for observing the activation of inter-RAT ANR is similar to that of intra-RAT ANR. For
details, see section 11.5.7 "Activation Observation."
The commands used to list parameters of neighbor relations with UTRAN cells, GERAN cells,
CDMA2000 1xRTT cells, and CDMA2000 HRPD cells are LST UTRANNCELL, LST GERANNCELL,
LST CDMA20001XRTTNCELL, and LST CDMA2000HRPDNCELL, respectively.
The command output of each command includes the ANR flag field. If ANR flag is True, the inter-RAT
neighbor relation is configured by ANR. If ANR flag is False, the inter-RAT neighbor relation is manually
configured.
None
12.5.9 Deactivation
Run the MOD ENODEBALGOSWITCH command to disable inter-RAT ANR.

eRAN
12.6 Performance Optimization

This section describes how to optimize the performance of inter-RAT ANR.
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.

Name
InterRat Fast ANR.FastAnrInterR This parameter specifies the maximum number of UEs that are
ANR atMeasUeNum concurrently involved in inter-RAT periodic measurements. A
measurement larger parameter value indicates that more UEs can concurrently
UE number perform periodic measurements. In this situation, neighboring
cells can be quickly detected. However, this affects the service
quality for these UEs and the uplink throughput of the network.
InterRat Fast ANR.FastAnrInterR This parameter specifies the upper limit for the total number of
ANR valid atUeNumThd UEs involved in inter-RAT periodic measurements. A larger
measurement parameter value results in more UEs being involved in inter-RAT
min UE number 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.
UTRAN Fast ANR.FastAnrRscpT This parameter specifies the RSCP requirement for adding a
ANR RSCP hd neighboring cell to the NCL. A larger parameter value results in a
threshold higher RSCP requirement; therefore the neighboring cells in the
NCL have higher signal quality. In urban areas with densely
distributed cells, increase this parameter value to ensure that only
neighboring cells with high signal quality are added to the NCL. In
contrast, in sparsely populated areas, reduce this parameter
value to add as many neighboring cells as possible to the NCL.
GERAN Fast ANR.FastAnrRssiT This parameter specifies the received signal strength indicator
ANR RSSI hd (RSSI) requirement for adding a neighboring cell to the NCL. A
threshold larger parameter value results in a higher RSSI requirement;
therefore the neighboring cells in the NCL have higher signal
quality. In urban areas with densely distributed cells, increase this
parameter value to ensure that only neighboring cells with high
signal quality are added to the NCL. In contrast, in sparsely
populated areas, reduce this parameter value to add as many
neighboring cells as possible to the NCL.

eRAN

Name
CDMA2000 ANR.FastAnrCdma This parameter specifies the pilot strength requirement for adding
1XRTT Fast 1xrttPilotThd a neighboring CDMA2000 1xRTT cell to the NCL. A larger
ANR Pilot parameter value results in a higher pilot strength requirement;
threshold therefore the neighboring cells in the NCL have higher signal
CDMA2000 ANR.FastAnrCdma This parameter specifies the pilot strength requirement for adding
HRPD Fast hrpdPilotThd a neighboring CDMA2000 HRPD cell to the NCL. A larger
ANR Pilot parameter value results in a higher pilot strength requirement;
threshold therefore the neighboring cells in the NCL have higher signal
Fault Description
A coverage-based handover from E-UTRAN to UTRAN fails.
Fault Handling
configuration:
delivered a handover command. A handover command is delivered if the
RRC_MOBIL_FROM_EUTRA_CMD message contains the IE mobilityFromEUTRACommand.
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.
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 event-triggered ANR with UTRAN has been turned on.
 If the switch has not been turned on, turn on the switch.

eRAN
 If the switch has been turned on, go to step 4.

Step 4 Check whether the UE supports ANR with UTRAN.
 If the UE supports ANR with UTRAN, contact Huawei engineers.
----End

eRAN 13 Engineering Guidelines for ANR with Shared
ANR Management Cells
13 Engineering Guidelines for ANR with Shared Cells

Enable the ANR with shared cells function when all the following conditions are met:
 The neighboring cells are shared by multiple PLMNs.
If the shared neighboring cells broadcast the PLMN lists in an RR manner, turn on
NBSLTEPLMNRoundSwitch under the ENodeBAlgoSwitch.RanSharingAnrSwitch parameter.
If the shared neighboring cells do not broadcast the PLMN lists in an RR manner, turn off
NBSLTEPLMNRoundSwitch and turn on NBSLTERANSharingSwitch under the
ENodeBAlgoSwitch.RanSharingAnrSwitch parameter.
 Some ANR-supporting UEs are used in the network.
 IntraRatEventAnrSwitch under the ENodeBAlgoSwitch.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 not shared by PLMNs.
 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.

 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.
 Networking mode (intra- or inter-frequency networking)

N/A

None
13.5 Deploying ANR with Shared Cells

This section describes the process of deploying the function of ANR with shared cells.

None


 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.

The following table describes the parameter that must be set in the EnodeBAlgoSwitch MO to set
switches for ANR with shared cells.
Parameter Name Parameter ID 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
For details about how to set the switches, see
section 13.1 "When to Use ANR."
13.5.4 Precautions
None

N/A

Configure a single eNodeB in the general configuration window on the CME based on the MO and
parameters as described in section 13.5.3 "Data Preparation."
refer to the generic procedure for setting parameters using the CME GUI.
navigation tree.


Step 1 On the GUI, set the parameters listed in the table for a specific scenario in this section, and
save the parameter settings as a user-defined template.
The parameters are the same as those described in section 13.5.3 "Data Preparation. "
----End
A user-defined template is recommended. The following table lists the recommended distribution of the

ENodeBAlgoSwitch ENodeBAlgoSwitch ANR Under RAN Sharing Algorithm Switch

Run the MOD ENODEBALGOSWITCH command to enable ANR with shared cells.

The procedure for observing the activation of ANR with shared cells is similar to that of intra-RAT ANR.
For details, see "SON Logs on the M2000 client" in section 11.5.7 "Activation Observation."
None
13.5.9 Deactivation
Run the MOD ENODEBALGOSWITCH command to disable ANR with shared cells.
13.6 Performance Optimization

This section describes how to optimize the performance of ANR with shared cells.
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

Fault Description
In RAN sharing mode, the UE subscribed to a secondary operator fails in an intra-RAT handover.
Fault Handling
configuration:
delivered a handover command. A handover command is delivered if the RRC_CONN_RECFG
message contains the IE mobilityControlInfo.
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.
 If the switches have been turned on, go to step 4.
Step 4 Check whether the UE supports intra-RAT ANR by referring to section 3.7 "ANR Capabilities of
UEs."
 If the UE supports intra-RAT ANR, contact Huawei engineers.
----End

eRAN 14 Engineering Guidelines X2 Automatic
ANR Management Management
14 Engineering Guidelines X2 Automatic Management

X2 self-setup can be implemented in X2 over S1 or X2 over M2000 mode.
X2 Self-Setup in X2 over S1 Mode

You are advised to enable X2 self-setup in X2 over S1 mode in the following cases:
 The operator has not planned X2 interfaces and hopes to use the X2 self-setup function to
automatically set up X2 interfaces.
 The eNodeBs are not managed by the same M2000.
You are advised to disable X2 self-setup in X2 over S1 mode when the operator prefers to manually
maintain X2 interfaces.
X2 Self-Setup in X2 over M2000 Mode

You are advised to enable X2 self-setup in X2 over M2000 mode in the following cases:
 The eNodeBs are managed by the same M2000.
 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:
 The eNodeBs are not managed by the same M2000.
 The operator prefers to manually maintain X2 interfaces.

Check whether the EPC or M2000 supports X2 self-setup.

N/A

None
14.5 Deploying X2 Self-Setup

This section describes the process of deploying X2 self-setup.

None

Requirements for the Operating Environment
The X2 over S1 mode requires that the EPC support X2 SON.
The X2 over M2000 mode requires that the M2000 support X2 SON.

Requirements for Transmission Networking

For details, see S1/X2/OM Channel Management Feature Parameter Description.
Requirements for Licenses

LOFD-002004 Self-configuration Self-configuration

For details about how to configure the GlobalProcSwitch, X2ServIP, and X2SigIP MOs, see the
engineering guidelines for deploying an X2 interface in S1/X2/OM Channel Management Feature
14.5.4 Precautions
None

None

See the engineering guidelines for deploying an X2 interface in S1/X2/OM Channel Management
Feature Parameter Description.

By using signaling tracing or checking SON logs on the M2000 client, you can check whether X2
self-setup has been activated.
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 14-1 shows an example of S1 interface tracing related to
X2 self-setup.

Figure 14-1 Example of S1 interface tracing related to X2 self-setup
SON Logs on the M2000 Client

The procedure for activation observation by checking SON logs on the M2000 client is as follows:
Step 1 On the M2000 client, choose Configuration > LTE Self Optimization > Query SON Log.
Select X2 Link Log from the Log Category drop-down list.
Step 2 In the Event Name list, select one at a time Automatically Establish Signaling Link and
Automatically Establish Service Link to check different types of X2 self-setup operations, as shown in
Figure 14-2.
Figure 14-2 SON logs on the M2000 client
----End

None
14.5.9 Deactivation
Run the MOD GLOBALPROCSWITCH command to deactivate X2 self-setup.
14.6 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 Number of X2 link setup attempts at the local
eNodeB
1526727204 L.Sig.X2.RecvSetup.Att Number of X2 link setup attempts at the peer
eNodeB
1526727203 L.Sig.X2.SendSetup.Succ Number of successful X2 link setups at the local
eNodeB
1526727205 L.Sig.X2.RecvSetup.Succ Number of successful X2 link setups at the peer
eNodeB
1526727265 L.HHO.X2.IntraFreq.ExecAttOut Number of performed inter-eNodeB
intra-frequency outgoing handovers over the X2
interface
1526727268 L.HHO.X2.InterFreq.ExecAttOut Number of performed inter-eNodeB
inter-frequency outgoing handovers over the X2
interface
1526727002 L.HHO.IntereNB.IntraFreq.ExecAttOut Number of performed inter-eNodeB
intra-frequency outgoing handovers in a cell
1526727005 L.HHO.IntereNB.InterFreq.ExecAttOut Number of performed inter-eNodeB
inter-frequency outgoing handovers in a cell
1526727294 L.HHO.NCell.ExecAttOut Number of performed inter-specific cell outgoing
handovers
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 Description Solution

Logs
Plus the SCTPLNK objects to The number of configured Run the LST SCTPLNK command to
be automatically set up, the SCTPLNK MOs has check the configuration of SCTP links.
total number of SCTPLNK reached the maximum Remove unnecessary SCTP links.
objects will exceed the If no SCTP link can be removed, no
maximum specifications. additional SCTPLNK MOs can be
configured.
Plus the IPPATH objects to be The number of configured Run the LST IPPATH command to check
automatically set up, the total IPPATH MOs has reached the configuration of IP paths. Remove
number of IPPath objects will the maximum. unnecessary IP paths.
exceed the maximum If no IP path can be removed, no additional
specifications. IPPATH MOs can be configured.
The record of the X2Interface is The number of configured Run the DSP X2INTERFACE command to
full. X2Interface MOs has query information about X2 interfaces.
reached the maximum. Remove unnecessary X2 interfaces.
If no X2 interface can be removed, no
additional X2Interface MOs can be
configured.
If the PT parameter in the If the DEVIP.PT parameter  If a device IP address on the same
DEVIP object associated with in the DEVIP MO associated network segment is not available, run the
the X2SERVIP parameter in an with the ADD DEVIP command to add the device
X2ServIP object is set to X2ServIP.X2SERVIP IP address.
LOOPINT, the X2ServIP object parameter is set to  If an IP route to the service IP address is
and each service IP address in LOOPINT, a device IP unavailable, run the ADD IPRT
the X2eNodeB object must address on the same command to add the IP route.
meet the following condition: A network segment as a
device IP address on the same service IP address in the
network segment as a service X2eNodeB MO or an IP
IP address in the X2eNodeB route to this service IP
object or an IP route to this address must be configured
service IP address is on the board where the
configured on the board where X2ServIP MO resides.
the X2ServIP object resides.
The CnOperator object on The CnOperator MO The operator information about the peer
which the CNOPERATORID referenced by the eNodeB has not been configured on the
parameter depends is not CnOperatorId parameter local eNodeB.
configured. has not been configured. Run the ADD CNOPERATOR command
to add the operator information.
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 X2 Interface Configuration Update Failed Major
25886 IP Path Fault Major
25888 SCTP Link Fault 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:
 X2 setup success rate at the local eNodeB = L.Sig.X2.SendSetup.Succ/L.Sig.X2.SendSetup.Att x
100%
 X2 setup success rate at the peer eNodeB = L.Sig.X2.RecvSetup.Succ/L.Sig.X2.RecvSetup.Att x
100%
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 14.5.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 14-3 shows an example of the SON logs.

Figure 14-3 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.
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 Number of Handovers (Counter Value)

Cell a Cell c X
Cell b Cell d Y
Cell a Cell d Z
Cell b Cell c W

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
X2SigIP.LOCIP parameter) is the same as the value of the X2eNodeB.FIRSTSIGIP parameter is a
neighboring eNodeB with which an X2 interface has been set up.
2. Check the X2eNodeB MO configurations at the neighboring eNodeB. Find and remove the
X2eNodeB MO in which the value of the X2eNodeB.FIRSTSIGIP parameter is the same as the
value of the X2SigIP.LOCIP parameter configured for the local eNodeB.
NOTE
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.
14.7 Parameter Optimization

None
None

eRAN
ANR Management 15 Parameters
15 Parameters
Table 15-1 Parameter description
MO Parameter ID MML Feature Feature Description
Command ID Name
ENodeBAlg AnrSwitch MOD LOFD-002 Automati Meaning:Indicates the ANR

oSwitch 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
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
inter-RAT neighboring relations with
UTRAN cells by performing periodic
inter-RAT measurements on
UTRAN. The eNodeB does not
deliver information about external

eRAN

Command ID 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
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
relations with CDMA2000 cells by
performing periodic intra-RAT
measurements on CDMA2000
networks.
UtranAutoNrtDeleteSwitch: If both
UtranEventAnrSwitch and this
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
GeranAutoNrtDeleteSwitch: If both
GeranEventAnrSwitch and this
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
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

eRAN

Command ID Name
False, automatic removal of the
inter-RAT neighboring relation is
allowed. If this switch is turned off,
automatic removal of the inter-RAT
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,

eRAN

Command ID Name
UtranFastAnrSwitch,
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 LOFD-002 Automati Meaning:Indicates the threshold for
001 / c removing a neighbor relationship
LST ANR TDLOFD- Neighbou with a cell by ANR based on the
002001 r Relation handover success rate. The
(ANR) threshold is the percentage of the
number of successful handovers to
the total number of handovers from
the local cell to the neighboring cell.
For example, an external cell is
configured as a neighboring cell for
all cells under an eNodeB, and this
neighboring cell permits automatic
removal of the neighboring
relationship by ANR. If the success
rate of handovers from each cell
under the eNodeB to this
neighboring cell is lower than or
equal to this threshold after a
measurement period, the
corresponding external cell and the
neighbor relationship with this cell
are automatically removed.
GUI Value Range:0~100
Unit:%
Actual Value Range:0~100
Default Value:0

eRAN

Command ID Name
X2BlackWh ENodeBId ADD LOFD-002 Self-confi Meaning:Indicates the ID of the

iteList X2BLACKWHIT 004 / guration neighboring eNodeB to be added to
ELIST TDLOFD- the list.
002004 Automati
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
ENodeBSh ENodeBSharing MOD LOFD-001 RAN Meaning:Indicates the eNodeB

aringMode Mode ENODEBSHAR 036 / Sharing sharing mode, which can be
INGMODE TDLOFD- with independent Operator Mode,
001036 Common Shared Frequency Sharing Mode, or
LST Carrier Separate Frequency Sharing Mode.
ENODEBSHAR LOFD-001
INGMODE 037 / RAN GUI Value
TDLOFD- Sharing Range:INDEPENDENT(Independen
001037 with t Operator Mode),
Dedicate SHARED_FREQ(Shared Frequency
d Carrier Sharing Mode),
SEPARATED_FREQ(Separate
Frequency Sharing Mode)
Unit:None
Actual Value
Range:INDEPENDENT,
SHARED_FREQ,
SEPARATED_FREQ
Default
Value:INDEPENDENT(Independent
Operator Mode)
ANR FastAnrCdma1xr MOD ANR LOFD-002 Automati Meaning:Indicates the pilot strength
ttPilotThd 001 / c threshold for fast ANR with
LST ANR TDLOFD- Neighbou CDMA2000 1xRTT. If the signal
002001 r Relation quality in a neighboring CDMA2000
(ANR) 1xRTT cell reported by the UE is
LOFD-002 lower than the threshold, the cell is
002 / Inter-RAT not automatically added as an
TDLOFD- ANR external cell of the eNodeB.
002002
GUI Value Range:-63~0
Unit:0.5dB
Actual Value Range:-31.5~0,
step:0.5
Default Value:-30

eRAN

Command ID Name
ANR FastAnrCdmahrp MOD ANR LOFD-002 Automati Meaning:Indicates the pilot strength
dPilotThd 001 / c threshold for fast ANR with
LST ANR TDLOFD- Neighbou CDMA2000 HRPD. If the signal
002001 r Relation quality in a neighboring CDMA2000
(ANR) HRPD cell reported by the UE is
002002
GUI Value Range:-63~0
Unit:0.5dB
Actual Value Range:-31.5~0,
step:0.5
Default Value:-16
ANR FastAnrCheckPe MOD ANR LOFD-002 Automati Meaning:Indicates the fast ANR
riod 001 / c checking timer. When the timer is
LST ANR TDLOFD- Neighbou expired, the eNodeB automatically
002001 r Relation checks whether to disable fast ANR.
(ANR)
LOFD-002 GUI Value Range:1~10080
002 / Inter-RAT
TDLOFD- ANR Unit:min
002002 Actual Value Range:1~10080
Default Value:60
ANR FastAnrInterRat MOD ANR LOFD-002 Inter-RAT Meaning:Indicates the maximum

MeasUeNum 002 / ANR allowed number of UEs that perform
LST ANR TDLOFD- inter-RAT measurements for fast
002002 ANR. After the number of UEs
performing inter-RAT measurements
for fast ANR reaches the maximum
number, inter-RAT measurements
for fast ANR will not be performed
on other UEs.
Unit:None
Default Value:5
ANR FastAnrInterRat MOD ANR LOFD-002 Inter-RAT Meaning:Indicates the threshold

UeNumThd 002 / ANR above which the eNodeB enters the
LST ANR TDLOFD- monitoring state for inter-RAT fast
002002 ANR. The threshold is expressed as
the number of UEs that have
performed measurements for

eRAN

Command ID Name
inter-RAT fast ANR.
Unit:None
Default Value:20
ANR FastAnrIntraRat MOD ANR LOFD-002 Automati Meaning:Indicates the maximum

MeasUeNum 001 / c allowed number of UEs that perform
LST ANR TDLOFD- Neighbou intra-RAT measurements for fast
002001 r Relation ANR. After the number of UEs
(ANR) performing intra-RAT measurements
for fast ANR reaches the maximum
number, intra-RAT measurements
for fast ANR will not be performed
on other UEs.
Unit:None
Default Value:5
ANR FastAnrIntraRat MOD ANR LOFD-002 Automati Meaning:Indicates the threshold

UeNumThd 001 / c above which the eNodeB enters the
LST ANR TDLOFD- Neighbou monitoring state for intra-RAT fast
002001 r Relation ANR. The threshold is expressed as
(ANR) the number of UEs that have
performed measurements for
intra-RAT fast ANR.
Unit:None
Default Value:20
ANR FastAnrRprtAmo MOD ANR LOFD-002 Automati Meaning:Indicates the number of

unt 001 / c periodic measurement reports sent
LST ANR TDLOFD- Neighbou for fast ANR.
002001 r Relation
(ANR) GUI Value Range:r1(1), r2(2), r4(4),
LOFD-002 r8(8), r16(16), r32(32), r64(64),
002 / Inter-RAT Infinity(Infinity)
TDLOFD- ANR
002002 Unit:None
Actual Value Range:r1, r2, r4, r8,
r16, r32, r64, Infinity

eRAN

Command ID Name
Default Value:r64(64)
ANR FastAnrRprtInter MOD ANR LOFD-002 Automati Meaning:Indicates the interval at

val 001 / c which periodic measurement reports
LST ANR TDLOFD- Neighbou are sent for fast ANR.
002001 r Relation
(ANR) GUI Value Range:120ms, 240ms,
LOFD-002 480ms, 640ms, 1024ms, 2048ms,
002 / Inter-RAT 5120ms, 10240ms, 1min, 6min,
TDLOFD- ANR 12min, 30min, 60min
002002
Unit:None
Actual Value Range:120ms, 240ms,
480ms, 640ms, 1024ms, 2048ms,
5120ms, 10240ms, 1min, 6min,
12min, 30min, 60min
Default Value:5120ms
ANR FastAnrRscpThd MOD ANR LOFD-002 Automati Meaning:Indicates the received

001 / c signal code power (RSCP) threshold
LST ANR TDLOFD- Neighbou for fast ANR with UTRAN. If the
002001 r Relation signal quality in a neighboring
(ANR) UTRAN cell reported by the UE is
002 Inter-RAT not automatically added as an
ANR external cell of the eNodeB.
GUI Value Range:-120~-25
Unit:dBm
Actual Value Range:-120~-25
Default Value:-106
ANR FastAnrRsrpThd MOD ANR LOFD-002 Automati Meaning:Indicates the reference

001 / c signal received power (RSRP)
LST ANR TDLOFD- Neighbou threshold for intra-RAT fast ANR. If
002001 r Relation the signal quality in a neighboring
(ANR) E-UTRAN cell reported by the UE is
002002
Unit:dBm
Default Value:-102

eRAN

Command ID Name
ANR FastAnrRssiThd MOD ANR LOFD-002 Automati Meaning:Indicates the received

001 / c signal strength indicator (RSSI)
LST ANR TDLOFD- Neighbou threshold for fast ANR with GERAN.
002001 r Relation If the signal quality in a neighboring
(ANR) GERAN cell reported by the UE is
002002
Unit:dBm
Default Value:-103
X2eNodeB FIRSTSIGIP ADD LOFD-002 Self-confi Meaning:Indicates the first signaling

X2ENODEB 004 / guration IP address of the neighboring
TDLOFD- eNodeB, which is to be used as the
MOD 002004 first peer IP address for an
X2ENODEB automatically set up SCTP link on
LST the X2 interface.
X2ENODEB GUI Value Range:Valid IP address
Unit:None
Actual Value Range:Valid IP address
Default Value:None
Cell LocalCellId ACT CELL None None Meaning:Indicates the local ID of the
cell. It uniquely identifies a cell within
ADD CELL a BS.
BLK CELL GUI Value Range:0~17
DEA CELL Unit:None
DSP CELL Actual Value Range:0~17
LST CELL Default Value:None
MOD CELL
RMV CELL
STR
CELLRFLOOP
BACK
STR
CELLSELFTES
T

eRAN

Command ID Name
UBL CELL
X2SigIP LOCIP ADD X2SIGIP LOFD-002 Self-confi Meaning:Indicates the first X2

004 / guration signaling IP address of the local
MOD X2SIGIP TDLOFD- eNodeB, which is to be used as the
LST X2SIGIP 002004 first local IP address for an
automatically set up SCTP link on
an X2 interface.
GUI Value Range:Valid IP address
Unit:None
Default Value:None
Drx LongDRXCyclef MOD DRX LBFD-002 DRX Meaning:Indicates the long DRX
orIRatAnr 017 / cycle for inter-RAT ANR. If inter-RAT
LST DRX TDLBFD-0 ANR is enabled, this parameter is
02017 valid regardless of whether DRX is
enabled.
GUI Value Range:SF128(128
subframes), SF160(160 subframes),
SF256(256 subframes), SF320(320
subframes), SF512(512 subframes),
SF640(640 subframes),
SF2560(2560 subframes)
Unit:subframe
Actual Value Range:SF128, SF160,
SF256, SF320, SF512, SF640,
SF1024, SF1280, SF2048, SF2560
Default Value:SF1280(1280
subframes)
X2BlackWh Mcc ADD LOFD-002 Self-confi Meaning:Indicates the mobile

iteList X2BLACKWHIT 004 / guration country code of the neighboring
ELIST TDLOFD- eNodeB to be added to the list. The
002004 Automati value of this parameter is a string of
RMV c three characters, each of which
X2BLACKWHIT LOFD-002 Neighbou must 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

eRAN

Command ID Name
Default Value:None
X2BlackWh Mnc ADD LOFD-002 Self-confi Meaning:Indicates the mobile

iteList X2BLACKWHIT 004 / guration network code of the neighboring
ELIST TDLOFD- eNodeB to be added to the list. The
002004 Automati value of this parameter is a string of
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 NcellHoStatNum MOD ANR LOFD-002 Automati Meaning:Indicates the threshold for
001 / c the total number of handovers to an
LST ANR TDLOFD- Neighbou intra-RAT neighboring cell, above
002001 r Relation which ANR begins to evaluate the
(ANR) removal of the neighboring relation
in the case of a low handover
success rate.
Unit:None
Default Value:200
EutranInter NoHoFlag ADD LBFD-002 Coverag Meaning:Indicates whether

FreqNCell EUTRANINTER 01802 / e Based handovers of UEs to the neighboring
FREQNCELL TDLBFD-0 Inter-freq cell are prohibited.
0201802 uency
MOD Handove GUI Value
EUTRANINTER LOFD-002 r Range:PERMIT_HO_ENUM(Permit
FREQNCELL 001 / Ho), FORBID_HO_ENUM(Forbid
TDLOFD- Automati Ho)
LST 002001 c
EUTRANINTER Neighbou Unit:None
FREQNCELL r Relation Actual Value
(ANR) Range:PERMIT_HO_ENUM,
FORBID_HO_ENUM
Default
Value:PERMIT_HO_ENUM(Permit
Ho)
EutranInter NoRmvFlag ADD LOFD-002 Automati Meaning:Indicates whether to permit

EUTRANINTER 001 / c or prohibit removal of the

eRAN

Command ID Name
FreqNCell FREQNCELL TDLOFD- Neighbou neighboring relationship by ANR.
002001 r Relation
MOD (ANR) GUI Value
EUTRANINTER Range:PERMIT_RMV_ENUM(Perm
FREQNCELL it 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 LOFD-002 Automati Meaning:Indicates the mode for
001 / c optimizing neighboring relations. If
LST ANR TDLOFD- Neighbou this parameter is set to FREE,
002001 r Relation neighboring relations are optimized
(ANR) automatically by ANR. If this
parameter is set to CONTROLLED,
neighboring relations to be added or
removed are reported to the M2000
and then subject to manual
processing for optimization.
GUI Value Range:FREE(FREE),
CONTROLLED(CONTROLLED)
Unit:None
Actual Value Range:FREE,
CONTROLLED
Default Value:FREE(FREE)
DEVIP PT ADD DEVIP None None Meaning:Indicates the port type.

RMV DEVIP GUI Value Range:PPP(PPP Link),
MPGRP(Multi-link PPP Group),
DSP DEVIP ETH(Ethernet Port),
LST DEVIP ETHTRK(Ethernet Trunk),
LOOPINT(Loopback Interface)
Unit:None
Actual Value Range:PPP, MPGRP,
ETH, ETHTRK, LOOPINT
Default Value:None
ENodeBAlg RanSharingAnrS MOD LOFD-002 Automati Meaning:Indicates the ANR

eRAN

Command ID Name
oSwitch witch ENODEBALGO 001 / c algorithm switch in RAN sharing
SWITCH TDLOFD- Neighbou mode. Related switches are
002001 r Relation described as follows:
LST (ANR)
ENODEBALGO LOFD-002 NBSLTEPLMNRoundSwitch: If this
SWITCH 002 / Inter-RAT switch is turned on, some
TDLOFD- ANR neighboring eNodeBs provide cells
002002 that work in RAN sharing mode and
broadcast their PLMN lists in a
round robin (RR) manner. In this
situation, if IntraRatEventAnrSwitch
or IntraRatFastAnrSwitch is turned
on for the local eNodeB, the local
eNodeB will ask the M2000 for the
actual cell global identifier (CGI) and
PLMN list for a cell broadcasting
PLMN IDs in an RR manner after the
UE reports the CGI of the cell during
ANR measurements.
NBSLTERANSharingSwitch: If this
switch is turned on, some
neighboring eNodeBs provide cells
that work in RAN sharing mode. In
this situation, if
IntraRatEventAnrSwitch or
IntraRatFastAnrSwitch is turned on
for the local eNodeB, the local
eNodeB will ask the M2000 for the
PLMN list for a cell after the UE
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:

eRAN

Command ID Name
Off, NBSLTERANSharingSwitch:Off
ANR StatisticNumFor MOD ANR LOFD-002 Automati Meaning:Indicates the number of

NRTDel 001 / c handovers above which neighboring
LST ANR TDLOFD- Neighbou relations are to be removed from a
002001 r Relation neighbor relation table (NRT). In a
(ANR) measurement period for neighboring
LOFD-002 relation removal, when the total
002 / Inter-RAT number of handovers from a cell
TDLOFD- ANR exceeds the value of this parameter,
002002 the neighboring cells that are not
detected by UEs are removed from
the NRT.
Unit:None
Default Value:200
ANR StatisticPeriod MOD ANR LOFD-002 Automati Meaning:Indicates the period during
001 / c which the total number of handovers
LST ANR TDLOFD- Neighbou to an intra-RAT neighboring cell is
002001 r Relation measured by ANR to evaluate the
(ANR) removal of the neighboring relation
in the case of a low handover
success rate.
Unit:min
Default Value:1440
ANR StatisticPeriodFo MOD ANR LOFD-002 Automati Meaning:Indicates the period during
rNRTDel 001 / c which the number of handovers are
LST ANR TDLOFD- Neighbou measured for neighboring relation
002001 r Relation removal from a neighbor relation
(ANR) table (NRT). In a measurement
LOFD-002 period for neighboring relation
002 / Inter-RAT removal, when the total number of
TDLOFD- ANR handovers from a cell exceeds the
002002 threshold for neighboring relation
removal, the neighboring cells that
are not detected by UEs are
removed from the NRT.
Unit:min

eRAN

Command ID Name
Default Value:10080
GlobalProc X2BasedUptENo MOD None None Meaning:Indicates whether the

Switch deBCfgSwitch GLOBALPROC eNodeB automatically updates the
SWITCH configuration of neighboring cells
based on the messages received
LST over the X2 interface. The
GLOBALPROC messages include X2 SETUP
SWITCH REQUEST, X2 SETUP RESPONSE,
and ENB CONFIGURATION
UPDATE.
When this switch is turned on, the
local eNodeB automatically updates
its configuration of neighboring cells
based on the messages received
over the X2 interface if any of the
following parameters of a
neighboring eNodeB is modified:
eNodeBId, CellId, LocalCellId,
CnOperator, CnOperatorTa, CellOp,
PhyCellId, and DlEarfcn. If the
eNodeB configuration data on a
network is to be modified by using
the interlocking modification function
on the CME, it is recommended that
this switch be turned off for all
eNodeBs on the network to disable
the automatic update over the X2
interface. Otherwise, the
configuration data may be lost or
become abnormal during the
automatic update.
This switch must be turned on if the
interlocking modification function on
the CME is not used and the
eNodeB configuration data on a
network is to be modified by using
the automatic update over the X2
interface.
GUI Value Range:OFF(Off), ON(On)
Unit:None
Actual Value Range:OFF, ON
Default Value:OFF(Off)
X2BlackWh X2ListType ADD LOFD-002 Self-confi Meaning:Indicates whether the list is

X2BLACKWHIT 004 / a blacklist or whitelist.If the peer

eRAN

Command ID Name
iteList ELIST TDLOFD- guration eNodeB is in the X2 blacklist, the X2
002004 interface between the two eNodeBs
LST Automati cannot be manually or automatically
X2BLACKWHIT LOFD-002 c set up. If the peer eNodeB is in the
ELIST 001 / Neighbou X2 whitelist, the X2 interface
TDLOFD- r Relation between the two eNodeBs cannot
002001 (ANR) be 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)
X2ServIP X2SERVIP ADD X2SERVIP LOFD-002 Self-confi Meaning:Indicates the X2 service IP

004 / guration address of the local eNodeB, which
MOD TDLOFD- is to be used as the local IP address
X2SERVIP 002004 for an automatically set up IP path
LST X2SERVIP on an X2 interface.
GUI Value Range:Valid IP address
Unit:None
Default Value:None
GlobalProc X2SonLinkSetup MOD LBFD-002 Mobility Meaning:Indicates the method of X2

Switch Type GLOBALPROC 018 / Manage setup by SON, that is, the method of
SWITCH TDLBFD-0 ment automatically setting up X2
02018 interfaces. The value
LST Coverag X2_OVER_M2000 can be set only
GLOBALPROC LBFD-002 e Based for Huawei eNodeBs, and the value
SWITCH 01801 / Intra-freq X2_OVER_S1 can be set for any
TDLBFD-0 uency eNodeB.
0201801 Handove
r GUI Value
LBFD-002 Range:X2_OVER_M2000(X2SonLin
01802 / Coverag k is set up over M2000),
TDLBFD-0 e Based X2_OVER_S1(X2SonLink is set up
0201802 Inter-freq over S1)
uency
Handove Unit:None

eRAN

Command ID Name
r Actual Value
Range:X2_OVER_M2000,
X2_OVER_S1
Default
Value:X2_OVER_M2000(X2SonLin
k is set up over M2000)
GlobalProc X2SonSetupSwit MOD LBFD-002 Mobility Meaning:Indicates whether to

Switch ch GLOBALPROC 018 / Manage enable or disable X2 setup by SON.
SWITCH TDLBFD-0 ment
02018 GUI Value Range:OFF(Off), ON(On)
LST Coverag
GLOBALPROC LBFD-002 e Based Unit:None
SWITCH 01801 / Intra-freq Actual Value Range:OFF, ON
TDLBFD-0 uency
0201801 Handove Default Value:ON(On)
r
LBFD-002
01802 / Coverag
TDLBFD-0 e Based
0201802 Inter-freq
uency
Handove
r

eRAN
ANR Management 16 Counters
16 Counters
There are no specific counters associated with this feature.

eRAN
ANR Management 17 Glossary
17 Glossary
For the acronyms, abbreviations, terms, and definitions, see Glossary.

eRAN
ANR Management 18 Reference Documents
18 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


ANR Management (ERAN3.0 - 08)

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

ANR Management (ERAN3.0 - 08)

Uploaded by

Copyright:

Available Formats

ANR Management

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

2 Overview of ANR .......................................................................................................................2-1

3 Concepts Related to ANR .......................................................................................................3-1

4 Intra-RAT ANR ............................................................................................................................4-1

5 Inter-RAT ANR ............................................................................................................................5-1

6 ANR with Shared Cells ............................................................................................................6-1

Issue 08 (2013-05-20) Huawei Proprietary and Confidential i

7 Manual Management of Neighbor Relations .....................................................................7-1

9 Related Features .......................................................................................................................9-1

10 Impact on the Network ........................................................................................................10-1

Issue 08 (2013-05-20) Huawei Proprietary and Confidential ii

10.4.2 Impact on Network Performance ...................................................................................... 10-2

11 Engineering Guidelines for Intra-RAT ANR....................................................................11-1

12 Engineering Guidelines for Inter-RAT ANR ...................................................................12-1

13 Engineering Guidelines for ANR with Shared Cells ....................................................13-1

Issue 08 (2013-05-20) Huawei Proprietary and Confidential iii

13.5 Deploying ANR with Shared Cells ............................................................................................. 13-1

14 Engineering Guidelines X2 Automatic Management ..................................................14-1

Issue 08 (2013-05-20) Huawei Proprietary and Confidential iv

1.2 Intended Audience

1.3 Change History

Issue 08 (2013-05-20) Huawei Proprietary and Confidential 1-1

Change Type Change Description Parameter Change

Change Type Change Description Parameter Change

Issue 08 (2013-05-20) Huawei Proprietary and Confidential 1-2

Change Type Change Description Parameter Change

Change Type Change Description Parameter Change

Change Type Change Description Parameter Change

Issue 08 (2013-05-20) Huawei Proprietary and Confidential 1-3

Change Type Change Description Parameter Change

Change Type Change Description Parameter Change

Change Type Change Description Parameter Change

Change Type Change Description Parameter Change

Issue 08 (2013-05-20) Huawei Proprietary and Confidential 1-4

Change Type Change Description Parameter Change

For details, see "Automatic Maintenance of  ANR.StatisticNumForNRTDel

Issue 08 (2013-05-20) Huawei Proprietary and Confidential 1-5

Issue 08 (2013-05-20) Huawei Proprietary and Confidential 2-1

3 Concepts Related to ANR

Issue 08 (2013-05-20) Huawei Proprietary and Confidential 3-1

3.4.3 RRC Blacklist

Issue 08 (2013-05-20) Huawei Proprietary and Confidential 3-2

3.6 Abnormal Neighboring Cell Coverage

3.7 ANR Capabilities of UEs

Issue 08 (2013-05-20) Huawei Proprietary and Confidential 3-3

Table 3-2 Definitions and setting descriptions of the ANR-related indicators

17  Reporting of SON-related or ANR-related This indicator can only Yes

Issue 08 (2013-05-20) Huawei Proprietary and Confidential 3-4

4.2 Intra-RAT Event-triggered ANR

4.2.1 Automatic Detection of Missing Neighboring Cells

Detecting Missing Neighboring Cells by Using Event-triggered UE

Issue 08 (2013-05-20) Huawei Proprietary and Confidential 4-1

The procedure is described as follows:

Issue 08 (2013-05-20) Huawei Proprietary and Confidential 4-2

Timer Start Stop At Expiry

5. The UE reports the parameter values to the source eNodeB.

Detecting Missing Neighboring Cells by Using UE History Information

The procedure is described as follows:

Issue 08 (2013-05-20) Huawei Proprietary and Confidential 4-3

4.2.2 Automatic Maintenance of NCLs and NRTs