ANR Management (ERAN15.1 08)

eRAN
ANR Management Feature

Parameter Description
Issue 08
Date 2020-08-05
HUAWEI TECHNOLOGIES CO., LTD.

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

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: https://www.huawei.com
Email: support@huawei.com
Issue 08 (2020-08-05) Copyright © Huawei Technologies Co., Ltd. i

eRAN
ANR Management Feature Parameter Description Contents
Contents
1 Change History.........................................................................................................................1
1.1 eRAN15.1 08 (2020-08-05)..................................................................................................................................................1
1.2 eRAN15.1 07 (2020-03-25)..................................................................................................................................................1
1.3 eRAN15.1 06 (2019-12-13)..................................................................................................................................................2
1.4 eRAN15.1 05 (2019-09-30)..................................................................................................................................................2
1.5 eRAN15.1 04 (2019-08-20)..................................................................................................................................................2
1.6 eRAN15.1 03 (2019-07-20)..................................................................................................................................................3
1.7 eRAN15.1 02 (2019-06-29)..................................................................................................................................................3
1.8 eRAN15.1 01 (2019-06-06)..................................................................................................................................................3
1.9 eRAN15.1 Draft C (2019-04-10)........................................................................................................................................ 4
1.10 eRAN15.1 Draft B (2019-03-18)...................................................................................................................................... 5
1.11 eRAN15.1 Draft A (2019-01-05)...................................................................................................................................... 5
2 About This Document.............................................................................................................8

2.1 General Statements................................................................................................................................................................ 8
2.2 Applicable RAT......................................................................................................................................................................... 9
2.3 Features in This Document.................................................................................................................................................. 9
2.4 Differences Between FDD and TDD............................................................................................................................... 10
3 Overview................................................................................................................................. 11
3.1 Introduction............................................................................................................................................................................ 11
3.2 Concepts Related to ANR................................................................................................................................................... 11
3.2.1 NCL......................................................................................................................................................................................... 12
3.2.2 NRT......................................................................................................................................................................................... 12
3.2.3 Blacklists and Whitelist....................................................................................................................................................14
3.2.4 Requirements of UEs for ANR....................................................................................................................................... 14
3.2.5 ANR Processing for Special UEs....................................................................................................................................16
4 Functions Related to Intra-RAT ANR................................................................................ 18

4.1 Intra-RAT ANR....................................................................................................................................................................... 18
4.1.1 Principles.............................................................................................................................................................................. 18
4.1.1.1 Intra-RAT NCL and NRT............................................................................................................................................... 18
4.1.1.1.1 NCL/NRT Control Mode............................................................................................................................................18
4.1.1.1.2 NRT Optimization Mode.......................................................................................................................................... 19
4.1.1.1.3 Method for NCL/NRT Management to Take Effect........................................................................................ 20
Issue 08 (2020-08-05) Copyright © Huawei Technologies Co., Ltd. ii

eRAN
4.1.1.2 Event-triggered ANR..................................................................................................................................................... 21

4.1.1.2.1 Automatic Detection and Addition of Missing Neighboring Cells.............................................................21
4.1.1.2.2 NCL Entry Modification............................................................................................................................................ 27
4.1.1.2.3 NCL/NRT Entry Removal.......................................................................................................................................... 28
4.1.1.2.4 Automatic Optimization of Neighbor Relationship Attributes................................................................... 33
4.1.1.2.5 Automatic Maintenance of Specified-Service Flags of External E-UTRAN Cells.................................. 35
4.1.1.3 Fast ANR............................................................................................................................................................................35
4.1.1.3.1 Automatic Detection and Addition of Missing Neighboring Cells.............................................................35
4.1.1.3.2 NCL Entry Modification............................................................................................................................................ 39
4.1.1.3.3 Automatic Maintenance of Specified-Service Flags of External E-UTRAN Cells.................................. 39
4.1.1.4 Backward ANR................................................................................................................................................................ 39
4.1.1.5 NCL/NRT Self-Management Based on X2 Messages.........................................................................................41
4.1.1.5.1 NCL/NRT Entry Addition and Update.................................................................................................................. 41
4.1.1.5.2 NCL/NRT Entry Removal.......................................................................................................................................... 44
4.1.1.6 NRT/NCL Entry Management Based on the eNodeB ID Blacklist.................................................................45
4.1.2 Network Analysis............................................................................................................................................................... 45
4.1.2.1 Benefits.............................................................................................................................................................................. 45
4.1.2.2 Impacts.............................................................................................................................................................................. 48
4.1.3 Requirements...................................................................................................................................................................... 52
4.1.3.1 Licenses.............................................................................................................................................................................. 52
4.1.3.2 Software............................................................................................................................................................................ 52
4.1.3.3 Hardware.......................................................................................................................................................................... 53
4.1.3.4 Networking...................................................................................................................................................................... 54
4.1.3.5 Others................................................................................................................................................................................ 54
4.1.4 Operation and Maintenance......................................................................................................................................... 54
4.1.4.1 Data Configuration........................................................................................................................................................ 54
4.1.4.1.1 Process............................................................................................................................................................................ 55
4.1.4.1.2 Data Preparation.........................................................................................................................................................59
4.1.4.1.3 Using MML Commands............................................................................................................................................ 74
4.1.4.1.4 Using the CME............................................................................................................................................................. 76
4.1.4.2 Activation Verification.................................................................................................................................................. 76
4.1.4.3 Network Monitoring..................................................................................................................................................... 81
4.1.4.4 Possible Issues................................................................................................................................................................. 82
4.2 Intra-RAT Neighbor Relationship Classification......................................................................................................... 86
4.2.1 Principles.............................................................................................................................................................................. 86
4.2.1.1 Neighbor Relationship Classification.......................................................................................................................87
4.2.1.2 Blacklisted Neighbor Relationship Management................................................................................................90
4.2.1.3 Differentiated Handling............................................................................................................................................... 94
4.2.2 Network Analysis............................................................................................................................................................... 96
4.2.2.1 Benefits.............................................................................................................................................................................. 96
4.2.2.2 Impacts.............................................................................................................................................................................. 96
4.2.3 Requirements...................................................................................................................................................................... 97
Issue 08 (2020-08-05) Copyright © Huawei Technologies Co., Ltd. iii

eRAN
4.2.3.1 Licenses.............................................................................................................................................................................. 97
4.2.3.2 Software............................................................................................................................................................................ 97
4.2.3.3 Hardware.......................................................................................................................................................................... 98
4.2.3.4 Networking...................................................................................................................................................................... 99
4.2.3.5 Others................................................................................................................................................................................ 99
4.2.4 Operation and Maintenance......................................................................................................................................... 99
4.2.4.1 Data Configuration........................................................................................................................................................ 99
4.2.4.1.1 Process............................................................................................................................................................................ 99
4.2.4.1.2 Data Preparation.........................................................................................................................................................99
4.2.4.1.3 Using MML Commands......................................................................................................................................... 101
4.2.4.1.4 Using the CME...........................................................................................................................................................102
4.2.4.2 Activation Verification................................................................................................................................................102
4.2.4.3 Network Monitoring................................................................................................................................................... 103
4.2.4.4 Possible Issues............................................................................................................................................................... 103
4.3 Specified PCI Group-based Neighboring Cell Management................................................................................103
4.3.1 Principles............................................................................................................................................................................ 103
4.3.1.1 Overview......................................................................................................................................................................... 104
4.3.1.2 Specified PCI Group-based ANR Management................................................................................................. 104
4.3.1.3 PCI Conflict Detection Based on the Specified PCI Group............................................................................. 106
4.3.2 Network Analysis............................................................................................................................................................ 106
4.3.2.1 Benefits............................................................................................................................................................................106
4.3.2.2 Impacts............................................................................................................................................................................ 107
4.3.3 Requirements.................................................................................................................................................................... 108
4.3.3.1 Licenses........................................................................................................................................................................... 108
4.3.3.2 Software.......................................................................................................................................................................... 108
4.3.3.3 Hardware........................................................................................................................................................................ 109
4.3.3.4 Networking.................................................................................................................................................................... 109
4.3.3.5 Others.............................................................................................................................................................................. 109
4.3.4 Operation and Maintenance....................................................................................................................................... 109
4.3.4.1 Data Configuration..................................................................................................................................................... 109
4.3.4.1.1 Process......................................................................................................................................................................... 109
4.3.4.1.2 Data Preparation...................................................................................................................................................... 110
4.3.4.1.4 Using the CME...........................................................................................................................................................112
4.3.4.4 Possible Issues............................................................................................................................................................... 114
4.4 Intra-RAT ANR with Shared Cells..................................................................................................................................114
4.4.1 Principles............................................................................................................................................................................ 114
4.4.1.1 Overview......................................................................................................................................................................... 115
4.4.1.2 Shared E-UTRAN Cell Broadcasting Its PLMN List in an RR Manner........................................................ 115
4.4.1.3 Shared E-UTRAN Cell Not Broadcasting Its PLMN List in an RR Manner............................................... 116
Issue 08 (2020-08-05) Copyright © Huawei Technologies Co., Ltd. iv

eRAN

4.4.2.1 Benefits............................................................................................................................................................................118
4.4.2.2 Impacts............................................................................................................................................................................ 118
4.4.3 Requirements.................................................................................................................................................................... 119
4.4.3.1 Licenses........................................................................................................................................................................... 119
4.4.3.2 Software.......................................................................................................................................................................... 119
4.4.3.3 Hardware........................................................................................................................................................................ 119
4.4.3.4 Networking.................................................................................................................................................................... 120
4.4.3.5 Others.............................................................................................................................................................................. 120
4.4.4.1.1 Process......................................................................................................................................................................... 120
4.4.4.1.4 Using the CME...........................................................................................................................................................122
4.4.4.4 Possible Issues............................................................................................................................................................... 122
4.5 Intra-RAT PLMN ID Management................................................................................................................................ 122
4.5.1 Principles............................................................................................................................................................................ 122
4.5.2.1 Benefits............................................................................................................................................................................124
4.5.2.2 Impacts............................................................................................................................................................................ 124
4.5.3 Requirements.................................................................................................................................................................... 125
4.5.3.1 Licenses........................................................................................................................................................................... 125
4.5.3.2 Software.......................................................................................................................................................................... 125
4.5.3.3 Hardware........................................................................................................................................................................ 125
4.5.3.4 Networking.................................................................................................................................................................... 125
4.5.3.5 Others.............................................................................................................................................................................. 126
4.5.4.1.1 Process......................................................................................................................................................................... 126
4.5.4.1.4 Using the CME...........................................................................................................................................................126
4.5.4.4 Possible Issues............................................................................................................................................................... 127
5 Functions Related to Inter-RAT ANR..............................................................................128

5.1 Inter-RAT ANR..................................................................................................................................................................... 128
5.1.1 Principles............................................................................................................................................................................ 128
5.1.1.1 Inter-RAT NCL and NRT.............................................................................................................................................128
Issue 08 (2020-08-05) Copyright © Huawei Technologies Co., Ltd. v

eRAN
5.1.1.1.1 NCL/NRT Control Mode......................................................................................................................................... 129

5.1.1.1.2 NRT Optimization Mode........................................................................................................................................129
5.1.1.1.3 Method for NCL/NRT Management to Take Effect......................................................................................131
5.1.1.2 Event-triggered ANR................................................................................................................................................... 133
5.1.1.2.1 Automatic Detection and Addition of Missing Neighboring Cells.......................................................... 133
5.1.1.2.2 NCL Entry Modification.......................................................................................................................................... 137
5.1.1.2.3 NCL/NRT Entry Removal........................................................................................................................................138
5.1.1.3 Fast ANR......................................................................................................................................................................... 142
5.1.1.3.1 Automatic Detection and Addition of Missing Neighboring Cells.......................................................... 142
5.1.1.3.2 NCL Entry Modification.......................................................................................................................................... 144
5.1.1.4 Automatic Optimization of Neighbor Relationship Attributes.................................................................... 145
5.1.1.4.1 Automatic Optimization of Blind Handover Priorities................................................................................ 145
5.1.1.4.2 Automatic Optimization of Measurement Priorities....................................................................................147
5.1.1.5 NG-RAN NCL/NRT Self-Management Based on EN-DC X2 Messages..................................................... 148
5.1.2.1 Benefits............................................................................................................................................................................151
5.1.2.2 Impacts............................................................................................................................................................................ 152
5.1.3 Requirements.................................................................................................................................................................... 154
5.1.3.1 Licenses........................................................................................................................................................................... 154
5.1.3.2 Software.......................................................................................................................................................................... 154
5.1.3.3 Hardware........................................................................................................................................................................ 155
5.1.3.4 Others.............................................................................................................................................................................. 156
5.1.4.1.1 Process......................................................................................................................................................................... 156
5.1.4.1.4 Using the CME...........................................................................................................................................................181
5.1.4.4 Possible Issues............................................................................................................................................................... 182
5.2 Inter-RAT Neighbor Relationship Classification....................................................................................................... 183
5.2.1 Principles............................................................................................................................................................................ 183
5.2.1.1 Neighbor Relationship Classification.................................................................................................................... 183
5.2.1.2 Blacklisted Neighbor Relationship Management............................................................................................. 184
5.2.2.1 Benefits............................................................................................................................................................................185
5.2.2.2 Impacts............................................................................................................................................................................ 185
5.2.3 Requirements.................................................................................................................................................................... 185
5.2.3.1 Licenses........................................................................................................................................................................... 185
5.2.3.2 Software.......................................................................................................................................................................... 186
5.2.3.3 Hardware........................................................................................................................................................................ 186
Issue 08 (2020-08-05) Copyright © Huawei Technologies Co., Ltd. vi

eRAN
5.2.3.4 Others.............................................................................................................................................................................. 186

5.2.4.1.1 Process......................................................................................................................................................................... 187
5.2.4.1.4 Using the CME...........................................................................................................................................................189
5.3 Inter-RAT ANR with Shared Cells.................................................................................................................................. 189
5.3.1 Principles............................................................................................................................................................................ 189
5.3.1.1 Shared GERAN Cell..................................................................................................................................................... 190
5.3.1.2 Shared UTRAN Cell..................................................................................................................................................... 191
5.3.2.1 Benefits............................................................................................................................................................................192
5.3.2.2 Impacts............................................................................................................................................................................ 193
5.3.3 Requirements.................................................................................................................................................................... 193
5.3.3.1 Licenses........................................................................................................................................................................... 193
5.3.3.2 Software.......................................................................................................................................................................... 193
5.3.3.3 Hardware........................................................................................................................................................................ 194
5.3.3.4 Others.............................................................................................................................................................................. 194
5.3.4.1.1 Process......................................................................................................................................................................... 194
5.3.4.1.4 Using the CME...........................................................................................................................................................196
5.4 Inter-RAT PLMN ID Management.................................................................................................................................196
5.4.1 Principles............................................................................................................................................................................ 196
5.4.2.1 Benefits............................................................................................................................................................................196
5.4.2.2 Impacts............................................................................................................................................................................ 196
5.4.3 Requirements.................................................................................................................................................................... 196
5.4.3.1 Licenses........................................................................................................................................................................... 196
5.4.3.2 Software.......................................................................................................................................................................... 197
5.4.3.3 Hardware........................................................................................................................................................................ 197
5.4.3.4 Others.............................................................................................................................................................................. 197
5.4.4.1.1 Process......................................................................................................................................................................... 197
Issue 08 (2020-08-05) Copyright © Huawei Technologies Co., Ltd. vii

eRAN

5.4.4.1.4 Using the CME...........................................................................................................................................................198
6 Parameters............................................................................................................................200
7 Counters................................................................................................................................ 201
8 Glossary................................................................................................................................. 202
9 Reference Documents........................................................................................................ 203
Issue 08 (2020-08-05) Copyright © Huawei Technologies Co., Ltd. viii

eRAN
ANR Management Feature Parameter Description 1 Change History
1 Change History
This chapter describes changes not included in the "Parameters", "Counters",

"Glossary", and "Reference Documents" chapters. These changes include:
● Technical changes
Changes in functions and their corresponding parameters
● Editorial changes
Improvements or revisions to the documentation
1.1 eRAN15.1 08 (2020-08-05)

This issue includes the following changes.
Technical Changes
None
Editorial Changes
● Added the statement that it is recommended that the
GlobalProcSwitch.X2ServedCellType parameter be set to
CONFIGURED_CELL in 4.1.1.5 NCL/NRT Self-Management Based on X2
Messages.
● Added a restriction on NRT entry removal in NG-RAN NCL/NRT self-
management based on EN-DC X2 messages. For details, see Effective
Conditions.
● Revised network analysis of inter-RAT neighbor relationship classification. For
details, see 5.2.2 Network Analysis.
● Revised descriptions and figures.
1.2 eRAN15.1 07 (2020-03-25)

Issue 08 (2020-08-05) Copyright © Huawei Technologies Co., Ltd. 1

eRAN
Technical Changes
None
Editorial Changes
● Revised descriptions of intra-RAT and inter-RAT NRT optimization mode. For
details, see 4.1.1.1.2 NRT Optimization Mode and 5.1.1.1.2 NRT
Optimization Mode.
● Revised descriptions in this document.
1.3 eRAN15.1 06 (2019-12-13)

Technical Changes
None
Editorial Changes
Revised descriptions of NRT optimization mode. For details, see 4.1.1.1.2 NRT
Optimization Mode and 5.1.1.1.2 NRT Optimization Mode.
1.4 eRAN15.1 05 (2019-09-30)

Technical Changes
None
Editorial Changes
Revised descriptions of automatic detection of missing neighboring cells. For
details, see 4.1.1.2.1 Automatic Detection and Addition of Missing Neighboring
Cells and 5.1.1.2.1 Automatic Detection and Addition of Missing Neighboring
Cells.
1.5 eRAN15.1 04 (2019-08-20)

Technical Changes
None
Editorial Changes
● Optimized MML command examples.

eRAN
1.6 eRAN15.1 03 (2019-07-20)

Technical Changes
None
Editorial Changes
● Optimized the MML configuration examples. For details, see 4.1.4.1.3 Using
MML Commands.
1.7 eRAN15.1 02 (2019-06-29)

Technical Changes
None
Editorial Changes
● Revised the description related to the optimization advice for adding the
neighbor relationship with a cell to an NRT based on event-triggered UE
measurements. For details, see 4.1.1.2.1 Automatic Detection and Addition
of Missing Neighboring Cells.
● Added a note for NCL/NRT entry removal in NG-RAN NCL/NRT self-
management based on E-UTRA-NR Dual Connectivity (EN-DC) X2 messages.
For details, see 5.1.1.5 NG-RAN NCL/NRT Self-Management Based on EN-
DC X2 Messages.
1.8 eRAN15.1 01 (2019-06-06)


eRAN
Technical Changes
Change Description Parameter Change RAT Base Station
Model
Added the determination None FDD ● 3900 and 5900

of UEs' capability of TDD series base
reading neighboring cells' stations
CGIs when the UEs are ● DBS3900
configured with EN-DC. LampSite and
For details, see 3.2.4 DBS5900
Requirements of UEs for LampSite
ANR.
● BTS3912E
● BTS3911E
Added support for None FDD ● 3900 and 5900

automatic update of TDD series base
architecture options for stations
external NG-RAN cells on ● DBS3900
the LTE side based on EN- LampSite and
DC X2 messages. For DBS5900
details, see 5.1.1.5 NG- LampSite
RAN NCL/NRT Self-
Management Based on ● BTS3912E
EN-DC X2 Messages and ● BTS3911E
5.1.4.1 Data
Configuration.
Editorial Changes
Added descriptions of the NG-RAN measurement in automatic detection of
missing neighboring cells. For details, see 5.1.1.2.1 Automatic Detection and
Addition of Missing Neighboring Cells.
1.9 eRAN15.1 Draft C (2019-04-10)

Technical Changes
None
Editorial Changes
● Revised the description of cell configuration changes in a gNodeB. For details,
see section 5.1.1.5 NG-RAN NCL/NRT Self-Management Based on EN-DC
X2 Messages.
● Revised descriptions in 3.2.2 NRT.
● Revised the document template.

eRAN
1.10 eRAN15.1 Draft B (2019-03-18)

Technical Changes
Model
Added UTRAN NCL/NRT Added the FDD ● 3900 and 5900

entry rectification. For UTRAN_NCELL_CORR TDD series base
details, see 5.3.4.1.2 Data ECTION_SW option to stations
Preparation. the ANR.NrtDelMode ● DBS3900
parameter. LampSite and
DBS5900
LampSite
● BTS3912E
● BTS3911E
Editorial Changes
● Revised the figure that illustrates the procedure for specification-based
removal. For details, see 4.1.1.2.3 NCL/NRT Entry Removal.
● Revised the MML command examples. For details, see 4.2.4.1.3 Using MML
Commands.
1.11 eRAN15.1 Draft A (2019-01-05)

This issue introduces the following changes to eRAN13.1 03 (2018-08-27).
Technical Changes
Model
Added the function of Added the FDD ● 3900 and 5900

filtering out UEs running LTE_EVENT_ANR_WIT TDD series base
QCI-1 services in intra- H_VOIP_MODE stations
RAT event-triggered ANR. option to the ● DBS3900
For details, see 3.2.5 ANR ANR.EventAnrWithV LampSite and
Processing for Special oipMode parameter. DBS5900
UEs. LampSite
● BTS3912E
● BTS3911E

eRAN

Model
Added ANR with NG-RAN. Added the following FDD ● 3900 and 5900
For details, see 5.1 Inter- options and TDD series base
RAT ANR. parameters: stations
● NrExternalCell.Ag ● DBS3900
gregationAttribut LampSite and
e DBS5900
● NrNRelationship.A LampSite
ggregationAttri- ● BTS3912E
bute ● BTS3911E
● NR_EVENT_ANR_S
W option of the
CellAlgoSwitch.An
rFunctionSwitch
parameter
● NrNFreq.Aggregat
ionAttribute
● ANR.NrFastAnrRsr
pThld
● NCellPlmnList.gN
BIdLength
● NR_DELREDUNDA
NCENCELL option
of the
ANR.NrtDelMode
parameter
Added NG-RAN NCL/NRT Added the following FDD ● 3900 and 5900
self-management based options: TDD series base
on E-UTRA-NR Dual ● MOD_NR_NCELL_ stations
Connectivity (EN-DC) X2 CFG_SW option of ● DBS3900
messages. For details, see the LampSite and
5.1.1.5 NG-RAN NCL/NRT GlobalProcSwitch. DBS5900
Self-Management Based X2BasedUptNcellC LampSite
on EN-DC X2 Messages. fgSwitch ● BTS3912E
parameter
● BTS3911E
● DEL_NR_NCELL_CF
G_SW option of
the
GlobalProcSwitch.
X2BasedUptNcellC
fgSwitch
parameter

eRAN

Model
Optimized the mechanism None FDD ● 3900 and 5900

for deleting inappropriate TDD series base
intra-RAT neighbor stations
relationships. For details, ● DBS3900
see 4.1.1.2.4 Automatic LampSite and
Optimization of DBS5900
Neighbor Relationship LampSite
Attributes.
● BTS3912E
● BTS3911E
Editorial Changes
None

eRAN
ANR Management Feature Parameter Description 2 About This Document
2 About This Document
2.1 General Statements

Purpose
This document is intended to acquaint readers with:
● The technical principles of features and their related parameters
● The scenarios where these features are used, the benefits they provide, and
the impact they have on networks and functions
● Requirements of the operating environment that must be met before feature
activation
● Parameter configuration required for feature activation, verification of feature
activation, and monitoring of feature performance
NOTE
This document only provides guidance for feature activation. Feature deployment and
feature gains depend on the specifics of the network scenario where the feature is
deployed. To achieve the desired gains, contact Huawei professional service engineers.
Software Interfaces
Any parameters, alarms, counters, or managed objects (MOs) described in this
document apply only to the corresponding software release. For future software
releases, refer to the corresponding updated product documentation.
Feature Differences Between RATs

The feature difference section only describes differences in switches or principles.
Unless otherwise stated, descriptions in this document apply to all RATs. If a
description does not apply to all RATs, the specific RAT that it does apply to will
be stated.
For example, in the statement "TDD cells are compatible with enhanced MU-
MIMO", "TDD cells" indicates that this function cannot be used in non-TDD cells.

eRAN
2.2 Applicable RAT

This document applies to FDD/TDD.
2.3 Features in This Document

This document describes the following FDD features.
Feature ID Feature Name Chapter/Section
LOFD-002001 Automatic Neighbour 4.1 Intra-RAT ANR

Relation (ANR)
LOFD-002002 Inter-RAT ANR 5.1 Inter-RAT ANR
LOFD-081225 Neighbor Cell Classification 4.2 Intra-RAT Neighbor

Management Relationship Classification
5.2 Inter-RAT Neighbor

Relationship Classification
LBFD-081102 PLMN ID Blacklist 4.5 Intra-RAT PLMN ID

Management
5.4 Inter-RAT PLMN ID

Management
LOFD-081207 Specified PCI Group-based 4.3 Specified PCI Group-

Neighboring Cell based Neighboring Cell
Management Management
This document describes the following TDD features.
Feature ID Feature Name Chapter/Section
TDLOFD-002001 Automatic Neighbour 4.1 Intra-RAT ANR

Relation (ANR)
TDLOFD-002002 Inter-RAT ANR 5.1 Inter-RAT ANR
TDLBFD-131125 PLMN ID Blacklist 4.5 Intra-RAT PLMN ID

Management
5.4 Inter-RAT PLMN ID

Management
TDLOFD-081201 Specified PCI Group-based 4.3 Specified PCI Group-

Neighboring Cell based Neighboring Cell

eRAN
2.4 Differences Between FDD and TDD

FDD Feature TDD Feature Difference Chapter/Section
LOFD-002001 TDLOFD-00200 None 4.1 Intra-RAT ANR

Automatic 1 Automatic
Neighbour Neighbour
Relation (ANR) Relation (ANR)
LOFD-002002 TDLOFD-00200 None 5.1 Inter-RAT ANR

Inter-RAT ANR 2 Inter-RAT
ANR
LOFD-081225 None This feature works 4.2 Intra-RAT

Neighbor Cell the same way in FDD Neighbor
Classification and TDD. Relationship
Management Classification
5.2 Inter-RAT
Neighbor
Relationship
Classification
LBFD-081102 TDLBFD-13112 None 4.5 Intra-RAT PLMN

PLMN ID 5 PLMN ID ID Management
Blacklist Blacklist 5.4 Inter-RAT PLMN
ID Management
LOFD-081207 TDLOFD-08120 None 4.3 Specified PCI

Specified PCI 1 Specified PCI Group-based
Group-based Group-based Neighboring Cell
Neighboring Neighboring Management
Cell Cell

eRAN
ANR Management Feature Parameter Description 3 Overview
3 Overview
3.1 Introduction
Operation and maintenance (OM) of radio access networks has become
increasingly complex, difficult, and costly because of the huge number of network
elements, the implementation of different radio access technologies (RATs), and
the coexistence of multiple equipment vendors and telecom operators. To address
this, 3GPP Release 8 introduces the self-organizing network (SON) solution. The
main functions of SON are self-configuration, self-optimization, and self-healing.
Automatic neighbor relation (ANR) is a self-configuration function, as shown in
Figure 3-1.
ANR maintains neighbor relationships of E-UTRAN cells with E-UTRAN, GERAN,
UTRAN, CDMA2000 (FDD), and NG-RAN cells.
Figure 3-1 ANR diagram
3.2 Concepts Related to ANR

This chapter describes the following basic ANR-related concepts:
● Neighboring cell list (NCL)
● Neighboring relation table (NRT)
● Blacklists and whitelist
– Handover (HO) blacklist

eRAN
– HO whitelist
– Radio resource control (RRC) blacklist
– Black neighboring relation table (BT) list
● Requirements of UEs for ANR
● ANR processing for special UEs
3.2.1 NCL
The NCLs of an eNodeB contain information about external cells, which are served
by surrounding base stations other than this eNodeB.
An eNodeB has an intra-RAT NCL and inter-RAT NCLs. An inter-RAT NCL can be a
GERAN NCL, UTRAN NCL, CDMA2000 NCL (FDD), or NG-RAN NCL.
● Intra-RAT NCL
E-UTRAN NCL: includes E-UTRAN cell global identifiers (ECGIs) of external E-
UTRAN cells, physical cell identifiers (PCIs), and E-UTRAN frequencies.
● Inter-RAT NCL
– GERAN NCL: includes cell global identifiers (CGIs) of external GERAN
cells, base transceiver station identity codes (BSICs), and GERAN
frequencies.
– UTRAN NCL: includes CGIs of external UTRAN cells, scrambling codes,
and UTRAN frequencies.
– NG-RAN NCL: includes CGIs of external NG-RAN cells, PCIs, and NG-RAN
frequencies.
– CDMA2000 NCL (FDD): includes CGIs of external CDMA2000 cells,
PnOffset, and CDMA2000 frequencies.
ANR can automatically add, remove, or update external cells.
NOTE
For details about all attributes in an NCL, see the MO and parameter reference.
3.2.2 NRT
The NRTs of a cell contain information about the neighbor relationships of the cell
with its adjacent cells.
A cell has intra- and inter-RAT NRTs. Intra-RAT NRTs contain an intra-frequency
NRT and an inter-frequency NRT.
The intra- and inter-RAT NRTs have different structures. Different from the intra-
RAT NRTs defined in section 22.3.2a "Automatic Neighbour Relation Function" in
3GPP TS 36.300 V10.3.0, Huawei-defined intra-RAT NRTs do not contain the No X2
attribute, as shown in Table 3-1. Besides 3GPP-defined attributes, Huawei-defined
intra-RAT NRTs support some special attributes used in Huawei-developed
features such as Blind handover Priority, Cell Measure Priority, and Neighbor
Cell Classification Flag. For details about these attributes, see the MO and
parameter reference.

eRAN
Table 3-1 Example of main information of an intra-RAT NRT
SN LCI Target eNodeB ID Cell ID No No HO

Cell Remove
PLMN
1 LCI#1 46001 eNodeB Cell ID#1 FORBID_R FORBID_H

ID#1 MV_ENUM O_ENUM
2 LCI#1 46001 eNodeB Cell ID#2 PERMIT_R PERMIT_H

ID#2 MV_ENUM O_ENUM
3 LCI#1 46001 eNodeB Cell ID#3 FORBID_R FORBID_H

ID#3 MV_ENUM O_ENUM
The following describes the items in Table 3-1:
● Local cell identifier (LCI): identifies the local cell.

● Target cell PLMN: identifies the public land mobile network (PLMN) of the
operator who owns the target cell.
● eNodeB ID: identifies the eNodeB that serves the target cell.
● Cell ID: identifies the target cell.
● No Remove: indicates whether ANR can remove a neighbor relationship from
the NRT. The No Remove attribute is specified by the No remove indicator
parameters on Huawei eNodeBs. The default value of these parameters is
PERMIT_RMV_ENUM.
– If the No remove indicator parameter is set to FORBID_RMV_ENUM for
a neighbor relationship, ANR cannot remove the neighbor relationship
from the NRT.
– If the No remove indicator parameter is set to PERMIT_RMV_ENUM for
a neighbor relationship, ANR can remove the neighbor relationship from
the NRT.
● No HO: indicates whether a neighbor relationship can be used for handovers.
The No HO attribute is specified by the No handover indicator parameters
on Huawei eNodeBs. The default value of these parameters is
PERMIT_HO_ENUM.
– If the No handover indicator parameter is set to FORBID_HO_ENUM for
a neighbor relationship, the neighbor relationship cannot be used for
handovers.
– If the No handover indicator parameter is set to PERMIT_HO_ENUM for
a neighbor relationship, the neighbor relationship can be used for
handovers.
ANR can automatically add, remove, and update neighbor relationships.
NOTE
In FDD, each E-UTRAN cell has a CDMA2000 1xRTT NRT and a CDMA2000 HRPD NRT.

eRAN
3.2.3 Blacklists and Whitelist

HO Blacklist
An HO blacklist includes neighbor relationships that meet both of the following
conditions:
● The No remove indicator parameter is set to FORBID_RMV_ENUM.
● The No handover indicator parameter is set to FORBID_HO_ENUM.
ANR cannot remove neighbor relationships in the HO blacklist.
Neighbor relationships can only be manually added to the HO blacklist by setting
the preceding parameters. For details about the HO blacklist, see section 5.2
"Specification level requirements" in 3GPP TS 32.511 V10.0.0.
HO Whitelist
An HO whitelist includes neighbor relationships that meet both of the following
conditions:
● The No remove indicator parameter is set to FORBID_RMV_ENUM.
● The No handover indicator parameter is set to PERMIT_HO_ENUM.
ANR cannot remove neighbor relationships in the HO whitelist.
The HO whitelist can only be configured manually. For details about the HO
whitelist, see section 5.2 "Specification level requirements" in 3GPP TS 32.511
V10.0.0.
RRC Blacklist
An RRC blacklist includes neighboring cells that UEs are not allowed to report.
ANR cannot automatically detect the neighboring cells in the RRC blacklist.
The RRC blacklist can only be configured manually.
BT List
A black neighboring relation table list (BT list) contains the neighboring cells that
UEs are allowed to measure but are not allowed to be handed over to. ANR
automatically detects the over-distant neighboring cells in the NRTs and adds
them to the BT list.
The BT list can also be configured manually.
eNodeBs support BT lists including blacklisted neighbor relationships with E-
UTRAN and UTRAN cells. The main information in the BT is LCIs, CGIs, and
automatic configuration flags of the blacklisted neighboring cells.
3.2.4 Requirements of UEs for ANR

ANR requires that a UE read the CGIs of neighboring cells.
In systems other than NG-RAN, the featureGroupIndicators (hereinafter referred to
as FGI) field in an RRC_UE_CAP_INFO message indicates the UE capability of

eRAN
reading the CGIs of neighboring cells. For details, see annex B.1 "Feature group
indicators" in 3GPP TS 36.331 V10.5.0. The UE_EUTRA_Capability IE includes fields
that indicate the UE capability of reading CGIs of neighboring cells after the UE is
configured with E-UTRA-NR Dual Connectivity (EN-DC).
In the NG-RAN, the UE_EUTRA_Capability IE includes fields that indicate the UE

capability.
Requirements of UEs for ANR are as follows:
● Intra-RAT ANR
– If the FGI bits 5 and 17 are set to 1, the UE supports intra-frequency ANR.
– If the FGI bits 5 and 18 are set to 1, the UE supports inter-frequency ANR.
– If the eutra-CGI-Reporting-ENDC field is included in the IE
UE_EUTRA_Capability, the UE supports intra-RAT ANR when it is
configured with EN-DC.
● Inter-RAT ANR
– If the RRC_UE_CAP_INFO message includes the R9 FGI field, then:
▪ (FDD) If the FGI bits 5 and 33 are set to 1, the UE supports ANR with
UTRAN FDD.
▪ (TDD) If the FGI bits 5 and 37 are set to 1, the UE supports ANR with
UTRAN TDD.
▪ If the FGI bits 5 and 34 are set to 1, the UE supports ANR with
GERAN.
CDMA2000 1xRTT.
CDMA2000 HRPD.
– If the RRC_UE_CAP_INFO message does not include the R9 FGI field, then:
▪ If the FGI bits 5, 19, and 22 are set to 1, the UE supports ANR with
UTRAN.
▪ If the FGI bits 5, 19, and 23 are set to 1, the UE supports ANR with
GERAN.
▪ (FDD) If the FGI bits 5, 19, and 24 are set to 1, the UE supports ANR
with CDMA2000 1xRTT.
▪ (FDD) If the FGI bits 5, 19, and 26 are set to 1, the UE supports ANR
with CDMA2000 HRPD.
– If the UE_EUTRA_Capability IE includes fields defined in 3GPP Release 15,
then:
▪ If the reportCGI_NR_EN_DC field is included in the IE, the UE

supports ANR with NG-RAN when EN-DC is configured.
▪ If the reportCGI_NR_NoEN_DC field is included in the IE, the UE

supports ANR with NG-RAN when EN-DC is not configured.

eRAN
▪ If the utra-GERAN-CGI-Reporting-ENDC field is included in the IE, the

UE supports ANR with UTRAN and ANR with GERAN when it is
configured with EN-DC.
NOTE
Since 3GPP TS 36.331 V10.5.0, the size of the FGI field has been changed from 32 bits to 64
bits. The leftmost indicator is set to 1.
UEs read CGIs in the following methods:

● DRX-based CGI reading
As defined in 3GPP specifications, an eNodeB sends a set of temporary DRX
parameters to a UE for ANR measurements. The UE reads the CGIs of
neighboring cells when both the eNodeB and the UE enter DRX mode. After
the UE acquires the CGIs, both the eNodeB and the UE exit DRX mode. This
process does not require the DRX feature to be activated.
The ANR-dedicated long DRX cycles for intra- and inter-RAT ANR
measurements are specified by the
CellDrxSpecialPara.LongDrxCycleForIntraRatAnr and
CellDrxSpecialPara.LongDrxCycleForInterRatAnr parameters, respectively.
The ANR-dedicated DRX inactivity timer is specified by the
CellDrxSpecialPara.FddAnrDrxInactivityTimer (FDD)/
CellDrxSpecialPara.TddAnrDrxInactivityTimer (TDD) parameter. For details
about how DRX works in ANR measurements, see DRX and Signaling Control.
● CGI reading using autonomous gaps
3GPP Release 9 defines CGI reading using autonomous gaps for UEs capable
of autonomous gaps. When the LTE_AUTON_GAP_CGI_SW option of the
CellAlgoSwitch.AnrAlgoSwitch parameter is selected, the eNodeB instructs
UEs to read CGIs of only intra-RAT neighboring cells using autonomous gaps.
Smart preallocation takes effect during CGI reading if the
ANR.SmartPreallocationMode parameter is set to ENABLE and the
SmartPreAllocationSwitch option of the CellAlgoSwitch.UlSchSwitch parameter
is selected. Smart preallocation does not take effect during CGI reading if the
ANR.SmartPreallocationMode parameter is set to DISABLE. For details about
smart preallocation, see Scheduling.
3.2.5 ANR Processing for Special UEs

A live network may have some abnormal UEs, for example, UEs that report FGI
indicators inconsistent with their capabilities or UEs that report incorrect CGIs. To
prevent the negative impact of ANR measurements on such UEs and the network,
the eNodeB does not instruct these UEs to perform ANR measurements. For
details, see Terminal Awareness Differentiation.
The ANR.EventAnrWithVoipMode parameter specifies whether UEs running
VoLTE services can be selected to perform measurements for event-triggered ANR.
● The eNodeB selects UEs running QCI-1 services for measurements related to
event-triggered intra-RAT ANR only if the
LTE_EVENT_ANR_WITH_VOIP_MODE option of this parameter is selected.
event-triggered ANR with UTRAN only if the

eRAN
UTRAN_EVENT_ANR_WITH_VOIP_MODE option of this parameter is

selected.
event-triggered ANR with GERAN only if the
GERAN_EVENT_ANR_WITH_VOIP_MODE option of this parameter is
selected.
event-triggered ANR with CDMA2000 only if the
CDMA_EVENT_ANR_WITH_VOIP_MODE option of this parameter is selected
During the detection of missing neighboring cells, the eNodeB determines the
type of CA UEs to be selected for CGI reading based on the ANR.CaUeChoseMode
parameter setting:
● If this parameter is set to CA_UE_CAP, the eNodeB selects UEs for which CA
does not take effect in the local cell.
● If this parameter is set to CA_UE_CARRIER_NUM, the eNodeB selects the UEs
that are each served by one carrier.
● If this parameter is set to ANR_UE_CAP, the eNodeB selects ANR-capable CA
UEs.

eRAN
ANR Management Feature Parameter Description 4 Functions Related to Intra-RAT ANR
4 Functions Related to Intra-RAT ANR
4.1 Intra-RAT ANR
4.1.1 Principles
Intra-RAT ANR includes the following functions:
● Intra-RAT NCL and NRT
● Event-triggered ANR
● Fast ANR
● Backward ANR
● NCL/NRT self-management based on X2 messages
● NCL/NRT management based on the eNodeB ID blacklist
Among the preceding functions:
● Event-triggered ANR and fast ANR can be enabled simultaneously. If both are
enabled, UEs perform both event-triggered measurements and periodic
measurements. eNodeBs detect missing neighboring cells based on either
event-triggered or periodic measurement reports.
● When the CPU usage of the main control board exceeds 80%, the eNodeB
does not handle unknown CGIs or perform backward ANR to prevent system
overload.
4.1.1.1 Intra-RAT NCL and NRT
4.1.1.1.1 NCL/NRT Control Mode

External cells and neighbor relationships can be manually or automatically added
to NCLs and NRTs, respectively. Table 4-1 lists the parameters that specify the
control mode for external cells in NCLs and neighbor relationships in NRTs.
● The Control Mode parameter can be set to AUTO_MODE or
MANUAL_MODE for an external cell or a neighbor relationship that is
manually added.

eRAN
● The Control Mode parameter is automatically set to AUTO_MODE for an

external cell or a neighbor relationship that is automatically added by ANR.
External cells and neighbor relationships for which the Control Mode
parameter is set to AUTO_MODE can be maintained automatically by ANR.
Table 4-1 Control mode parameters

NCL/NRT Parameter
External E-UTRAN EutranExternalCell.CtrlMode

cell
Intra-frequency EutranIntraFreqNCell.CtrlMode
neighbor
relationship
Inter-frequency EutranInterFreqNCell.CtrlMode
neighbor
relationship
Blacklisted EutranBlkNCell.CtrlMode
neighboring E-
UTRAN cell
4.1.1.1.2 NRT Optimization Mode

Intra-RAT NRT optimization mode specifies whether the following types of
optimization advice automatically take effect or require manual confirmation:
● NRT optimization advice automatically generated by the eNodeB triggered by
event-triggered ANR
fast ANR
automatic optimization of neighbor relationship attributes
● BT optimization advice automatically generated by the eNodeB triggered by
ANR
The ANR.OptMode parameter specifies how the preceding types of optimization
advice take effect.
● When the ANR.OptMode parameter is set to FREE, the NRT optimization
advice and BT optimization advice take effect directly.
● When the ANR.OptMode parameter is set to CONTROLLED and the
NCellParaCfg.RatType parameter is set to EUTRAN, the
NCellParaCfg.CellAnrOptMode parameter specifies whether the E-UTRAN
optimization advice needs to be reported to the U2020.
– When the NCellParaCfg.CellAnrOptMode parameter is set to
CONTROLLED, then:
▪ The NRT optimization advice for a local cell generated by the

eNodeB triggered by event-triggered ANR, fast ANR, or automatic
optimization of neighbor relationship attributes needs to be reported

eRAN
to the U2020. The optimization is subject to the manual confirmation

on the U2020.
▪ ANR cannot trigger the eNodeB to automatically generate BT

optimization advice or report the BT optimization advice on neighbor
relationships with E-UTRAN cells to the U2020.
– When the NCellParaCfg.CellAnrOptMode parameter is set to FREE,
then:
▪ The NRT optimization advice for the local cell generated by the
eNodeB triggered by event-triggered ANR, fast ANR, or automatic
optimization of neighbor relationship attributes is automatically
handled by the eNodeB.
▪ The BT optimization advice for a local cell generated by the eNodeB

triggered by ANR needs to be reported to the U2020. The
optimization is subject to the manual confirmation on the U2020.
When the ANR.OptMode parameter is set to CONTROLLED, the collaboration
between adding neighboring cells and performing intra-RAT handovers is as
follows:
● When the ANR.AnrControlledHoStrategy parameter is set to PERMIT_HO,
the eNodeB performs the handovers after receiving handover measurement
reports from UEs, regardless of whether maintenance personnel have
confirmed the advice on the U2020 to add the neighbor relationships with the
target cells to the NRTs.
● When the ANR.AnrControlledHoStrategy parameter is set to FORBID_HO,
the eNodeB does not perform the handovers after receiving handover
measurement reports from UEs if maintenance personnel have not confirmed
the advice on the U2020. Therefore, if this parameter is set to FORBID_HO,
maintenance personnel must confirm the optimization advice in a timely
manner to ensure handovers of the UEs to the target cells. If the handovers
cannot be performed, RRC connection reestablishments or service drops occur.
NOTE
NCLs are not controlled by the ANR.OptMode parameter, and the eNodeB cannot generate
NCL optimization advice. The eNodeB automatically adds external cells to NCLs, removes
external cells from NCLs, and updates the information about the external cells in NCLs even
if this parameter is set to CONTROLLED.
4.1.1.1.3 Method for NCL/NRT Management to Take Effect

Neighbor relationship management of ANR refers to detect and modify external
cells or neighbor relationships in NCLs or NRTs, and delete them from NCLs or
NRTs based on the Uu measurement results or handover statistics.
Neighbor relationship management of ANR takes effect on a per base station, cell,
or frequency basis, each controlled by base-station-, cell-, or frequency-specific
ANR parameters listed in Table 4-2.
● Base-station-specific ANR parameters must be set to implement intra-RAT
ANR.
● Cell-specific ANR parameters must be set to implement intra-RAT ANR for a
local cell after base-station-specific parameters are set.

eRAN
● Frequency-specific ANR parameters control whether ANR takes effect for

external cells on a specific neighboring frequency of the local cell and
neighbor relationships with these cells after cell-specific parameters are set.
Table 4-2 Base-station-, cell-, and frequency-specific intra-RAT ANR parameters

Base-Station-Specific Cell-Specific Frequency-Specific
Parameters Parameters Parameters
Event-triggered ANR: INTRA_RAT_ANR_SW Intra-frequency neighbor

IntraRatEventAnrSwitch option of the relationships and
option of the CellAlgoSwitch.AnrFunc external cells:
ENodeBAlgoSwitch.Anr tionSwitch parameter Cell.IntraFreqAnrInd
Switch parameter Inter-frequency neighbor
Fast ANR: relationships and
IntraRatFastAnrSwitch external cells:
option of the EutranInterNFreq.AnrIn
ENodeBAlgoSwitch.Anr d
Switch parameter
NOTE
NCLs are configured on a per base station basis. A base station adheres to the following
rules when configuring NCLs:
● External cells are added to an NCL based on the frequency indicators of the source cells.
● External cells can be directly removed from NCLs if each cell served by the base station
does not have neighbor relationships with the external cells.
4.1.1.2 Event-triggered ANR

Event-triggered ANR includes detection of intra-RAT missing neighboring cells by
using event-triggered UE measurements and UE history information and
automatic maintenance of intra-RAT NCLs and NRTs. This function takes effect on
a per base station, cell, or frequency basis. For details, see 4.1.1.1.3 Method for
NCL/NRT Management to Take Effect.
4.1.1.2.1 Automatic Detection and Addition of Missing Neighboring Cells
Automatic Detection of Missing Neighboring Cells

Intra-RAT event-triggered ANR detects missing intra-RAT neighboring cells based
on the cell lists in intra- and inter-frequency measurement reports. This type of
ANR is triggered by intra-RAT handover measurements.
Automatic detection of missing neighboring cell takes effect only after event-
triggered ANR is enabled. Table 4-3 lists types of handover measurements and
related eNodeB-specific parameters.

eRAN
Table 4-3 Types of intra-RAT handover measurements and related eNodeB-

specific parameters
Handover Measurement Type Parameters
Coverage-based handover None

measurements
Inter-frequency MLB measurements MlbBasedEventAnrSwitch option of

the ENodeBAlgoSwitch.AnrSwitch
parameter
Service-based handover measurements ServiceBasedEventAnrSwitch option

of the ENodeBAlgoSwitch.AnrSwitch
parameter
Service-request-based inter-frequency ● ServiceReqEventAnrSwitch option

handover measurements of the
ENodeBAlgoSwitch.AnrSwitch
parameter
● ServiceReqInterFreqHoSwitch
option of the
ENodeBAlgoSwitch.HoAlgoSwitch
parameter
Service-based inter-frequency ● ServiceBasedEventAnrSwitch

handover measurements option of the
parameter
● ServiceBasedInterFreqHoSwitch
option of the
ENodeBAlgoSwitch.HoAlgoSwitch
parameter
Other types of handover IntraRatEnhancedEventAnrSwitch

measurements option of the
parameter
CA measurements CaBasedEventAnrSwitch option of

the ENodeBAlgoSwitch.AnrSwitch
parameter
Auto neighbor group configuration InterFreqAngcAnrSwitch option of

(ANGC) measurements the ENodeBAlgoSwitch.AnrSwitch
parameter

eRAN
NOTE
● Other types of handovers include distance-based inter-frequency handover and uplink-

quality-based inter-frequency handover. For details about different types of handovers,
see Mobility Management in Connected Mode.
● CA measurements include measurements for PCC anchoring, SCell configuration, and
SCell change. For details, see Carrier Aggregation.
● For details about ANGC measurements, see Auto Neighbor Group Configuration.
Figure 4-1 shows the procedure for using event-triggered UE measurements to

detect a missing intra-RAT neighboring cell. Cell A (PCI = 3, ECGI = 17) served by
the source eNodeB is the serving cell of the UE. Cell B (PCI = 5, ECGI = 19) served
by the target eNodeB is a missing intra-RAT neighboring cell of cell A.
Figure 4-1 Procedure for using event-triggered UE measurements to detect a

missing intra-RAT neighboring cell
1. The source eNodeB delivers the measurement configuration to the UE,

instructing the UE to measure adjacent cells to detect missing neighboring
cells. By default, the UE performs intra-frequency measurements.
When a UE establishes radio bearers, the source eNodeB delivers the intra-
frequency measurement configuration to the UE in an RRC Connection
Reconfiguration message by default. When inter-frequency measurements are
required, the source eNodeB must deliver the inter-frequency measurement
configuration to the UE to enable gap-assisted measurements. For details
about intra-frequency and inter-frequency measurements, see Mobility
Management in Connected Mode.
2. The UE detects that cell B meets the measurement requirements, so the UE
reports the physical cell identifier (PCI) of cell B to the source eNodeB. Note
that the UE does not report the PCIs of the cells in an RRC blacklist to the
eNodeB.
3. The source eNodeB checks whether cell B has the strongest signal and
whether cell B is an unknown cell or a PCI-confusion neighboring cell.
The ANR.EventAnrMode parameter specifies how the source eNodeB checks
whether cell B is an unknown cell or a PCI-confusion neighboring cell.

eRAN
– When this parameter is set to NOT_BASED_NCL, the source eNodeB

proceeds to the next step if the combination of the operating frequency
and PCI of cell B does not exist in the NRT or is mapped to multiple
neighbor relationships in the NRT. Otherwise, the procedure ends.
– When this parameter is set to BASED_NCL, the source eNodeB proceeds
to the next step if the combination of the operating frequency and PCI of
cell B does not exist in the NCL or is mapped to multiple external cells in
the NCL. Otherwise, the procedure ends.
NOTE
If the ANR.EventAnrMode parameter is set to NOT_BASED_NCL, the ANR.OptMode

parameter is set to CONTROLLED, and the NCellParaCfg.CellAnrOptMode
parameter is set to CONTROLLED, then the optimization advice about adding the
neighbor relationship with a cell into an NRT is reported to the U2020. Maintenance
personnel determine whether to deliver the advice. Before maintenance personnel
confirm this optimization advice, the eNodeB instructs the UE to read the ECGI of the
cell again if the PCI contained in an intra-RAT measurement report does not exist in
the NRT. To prevent performance deterioration due to ECGI reading before handovers,
maintenance personnel are advised to handle the NRT optimization advice promptly
on the U2020.
4. The source eNodeB instructs the UE to read the ECGI, tracking area code
(TAC), and PLMN list of cell B over the BCH.
Timer T321 controls the maximum time a UE can spend reading ECGIs. The
following table describes information about timer T321. For the timer values,
see 5.5.2.3 "Measurement identity addition/modification" in 3GPP TS 36.331
V10.5.0.
Timer Start Stop At Expiry
T321 Upon receiving Upon acquiring Initiate the

measConfig cellGlobalId for the measurement
including a corresponding cell; reporting
reportConfig with alternatively, upon procedure,
the cause value receiving measConfig stop
reportCGI including a reportConfig performing
with the removal cause the related
value reportCGI measurement
s, and remove
the
corresponding
measId
NOTE
● The eNodeB does not process other measurement reports sent from the UE before
the UE finishes ECGI measurements or the T321 timer expires.
● The eNodeB instructs a UE in the EN-DC state to perform ECGI measurements of
intra-RAT neighboring cells only after the UE reports the "eutra-CGI-Reporting-
ENDC" field in the "UE_EUTRA_Capability" IE.
5. The UE reports the ECGI, TAC, and PLMN list of cell B to the source eNodeB.

eRAN
After detecting the missing neighboring cell, the source eNodeB adds and updates
the entries in the NCL or NRT. For details, see Automatic Addition of Missing
Neighboring Cells.
NOTE
If the neighbor relationship with a cell is automatically added by intra-RAT event-triggered

ANR based on inter-frequency MLB measurements, this neighboring cell is not selected as
the target cell for this load-based inter-frequency handover but will be selected as the
target cell for subsequent load-based inter-frequency handovers.
In some special networking scenarios (for example, a large number of micro

eNodeBs are deployed around macro eNodeBs), cells served by some specific
eNodeBs are allocated with PCIs in a specified PCI group and these cells may share
the PCI in the group. In this case, neighbor relationships with these cells need to
be specially managed.
Automatic Addition of Missing Neighboring Cells

When event-triggered ANR detects an intra-RAT missing neighboring cell by using
UE measurements, the eNodeB adds the detected cell to the NCL and the
neighbor relationship with the detected cell to the NRT based on the reported PCI
or ECGI of the cell in the intra-RAT handover measurement report and the
ANR.EventAnrMode parameter setting.
● When this parameter is set to NOT_BASED_NCL, the eNodeB adds the
neighbor relationship with this detected cell to the NRT according to the ECGI
reading result.
– If the reported ECGI of the detected cell is included in the NCL, the
eNodeB directly adds a neighbor relationship with the detected cell to the
NRT.
– If the reported ECGI of the detected cell is not included in the NCL, the
eNodeB adds the detected cell to the NCL of the eNodeB and adds the
neighbor relationship with the detected cell to the NRT of the local cell.
● When this parameter is set to BASED_NCL, the eNodeB performs the
following:
– If the reported PCI of the detected cell is included in the NCL, the eNodeB
adds the neighbor relationship with the detected cell to the NRT of the
local cell.
– If the reported PCI of the detected cell is not included in the NCL, the
eNodeB adds the detected cell to the NCL of the eNodeB and adds the
neighbor relationship with the detected cell to the NRT of the local cell
according to the ECGI reading result.
When event-triggered ANR detects a missing neighboring cell in one of the
following handover measurement scenarios, the source eNodeB selects this cell as
the target cell in the handover even if it has not added the detected cell to an NCL
or NRT.
● Coverage-based handover measurements
● Service-based handover measurements
● Service-request-based handover measurements
Figure 4-2 and Figure 4-3 illustrate the successful and unsuccessful operations of
adding a missing neighboring cell to an NCL of the source eNodeB and adding a

eRAN
neighbor relationship with the missing neighboring cell to an NRT of the source
cell, respectively. In the following figures, "eNodeB TMP ECGI/CGI" indicates the
internal temporary storage management module in the eNodeB and the dashed
line indicates an internal process in an eNodeB.
Figure 4-2 Successful operation of adding an NCL/NRT entry

eRAN
Figure 4-3 Unsuccessful operation of adding an NCL/NRT entry
1. A UE sends a measurement report to the eNodeB.

2. The eNodeB detects that the strongest cell (cell 1) contained in the
measurement report does not exist in the NCL.
3. The eNodeB instructs the UE to read the ECGI (or CGI) of cell 1.
4. The UE reports the ECGI (or CGI) of cell 1 to the eNodeB.
5. The eNodeB temporarily records the ECGI (or CGI).
6. The eNodeB attempts to add cell 1 to the NCL and add the neighbor
relationship with cell 1 to the NRT of the source cell.
– If the operation succeeds, the eNodeB selects cell 1 as the target cell for
the handover.
– If the operation fails, the eNodeB obtains the ECGI (or CGI) of cell 1 from
the temporary records and then selects cell 1 as the target cell for the
handover.
NOTE
The temporarily recorded ECGI (or CGI) is used only for the current handover
determination.
4.1.1.2.2 NCL Entry Modification

After a UE reports the CGI of a missing neighboring cell to an eNodeB, the
eNodeB checks whether the reported information about the detected cell is
consistent with the external cell information in the NCL. If the reported

eRAN
information is inconsistent with the external cell information, the eNodeB

automatically synchronizes the NCL with the reported information. The reported
information includes the downlink E-UTRA absolute radio frequency channel
number (EARFCN), PCI, TAC, PLMN list, and secondary frequency band.
4.1.1.2.3 NCL/NRT Entry Removal

When an NCL or NRT has an inappropriate or redundant entry or the number of
NCL or NRT entries reaches its maximum, event-triggered ANR can automatically
remove an external cell or neighbor relationship if the following conditions are
met:
● The Control Mode parameter is set to AUTO_MODE.

● The No remove indicator parameter is set to PERMIT_RMV_ENUM.
Table 4-4 lists the related options controlling three types of automatic removal.
Table 4-4 Options controlling the automatic removal functions
Scenario Option
Specificatio ● Removal of neighbor relationships from an NRT is enabled if

n-based the IntraRatAnrAutoDelSwitch option of the
removal ENodeBAlgoSwitch.AnrSwitch parameter is selected.
● Removal of external cells from an NCL is not under switch
control.
Removal of This function is enabled if both of the following options are

inappropriat selected:
e NCL/NRT ● IntraRatAnrAutoDelSwitch option of the
entries ENodeBAlgoSwitch.AnrSwitch parameter
● EUTRAN_DELCELLERRORNCELL option of the
ANR.NrtDelMode parameter
Removal of This function is enabled if both of the following options are

redundant selected:
NCL/NRT ● IntraRatAnrAutoDelSwitch option of the
entries ENodeBAlgoSwitch.AnrSwitch parameter
● EUTRAN_DELREDUNDANCENCELL option of the
ANR.NrtDelMode parameter
NOTE
For details about the maximum number of external cells in an NCL and the maximum
number of neighbor relationships in an NRT, see the following commands in the MML
command reference:
● ADD EUTRANEXTERNALCELL
● ADD EUTRANINTRAFREQNCELL
● ADD EUTRANINTERFREQNCELL

eRAN
Removal of Neighbor Relationships from an NRT

● Specification-based removal
ANR removes a certain neighbor relationship when the number of entries in
the intra- or inter-frequency NRT of a cell or the total number of entries in
intra- or inter-frequency NRTs of an eNodeB has reached its maximum.
Specification-based removal is triggered when ANR attempts to add a new
neighbor relationship in the preceding scenario.
– When the number of entries in the NRT of the cell has reached its
maximum, ANR removes a certain neighbor relationship before it adds a
new neighbor relationship to the NRT. Figure 4-4 describes the
procedure.
– When the total number of entries in the NRTs of the eNodeB but not the
number of entries in the NRT of the cell has reached its maximum, the
eNodeB first checks whether there is a neighbor relationship of the cell
that can be removed by specification-based removal before it adds a new
neighbor relationship. If not, the eNodeB has a chance to randomly select
other intra-eNodeB cells with candidate to-be-removed neighbor
relationships and perform specification-based removal. Figure 4-4
describes the procedure.
After intra-RAT event-triggered ANR is enabled, a measurement period
specified by the ANR.StatisticPeriodForNRTDel parameter starts.
Figure 4-4 shows the specification-based removal procedure.

eRAN
Figure 4-4 Specification-based removal

eRAN
The descriptions of the parameters in Figure 4-4 are as follows:

Parameter 1: ANR.StatisticNumForNRTDel, which specifies the threshold of
the total number of handover attempts from the local cell to all its
neighboring E-UTRAN cells
Parameter 2: ANR.NcellHoForNRTDelThd, which specifies the threshold of
the number of handover attempts from the local cell to a neighboring cell
Parameter 3: ANR.NcellCaThdForNRTDel, which specifies the threshold of
the number of times the neighboring cell is successfully configured as an
SCell for UEs in the local cell
Parameter 4: NCellParaCfg.NcellNumForAnr or
EutranInterNFreq.NcellNumForAnr, which specifies the number of required
intra- or inter-frequency neighboring cells, respectively
During specification-based removal, the eNodeB preferentially removes a
neighbor relationship for which the No handover indicator parameter is set
to PERMIT_HO_ENUM from the candidate neighbor relationships.
NOTE
When specification-based removal is enabled, this function can remove neighbor

relationships after statistics are collected for two consecutive measurement periods.
The measurement period is defined by ANR.StatisticPeriodForNRTDel.
● Removal of inappropriate neighbor relationships
If the number of handover attempts from a cell (for example, cell A) served
by the local eNodeB to a neighboring cell (for example, cell B) reaches
ANR.NcellHoStatNum, and the handover success rate is less than or equal to
ANR.DelCellThd within a measurement period specified by
ANR.StatisticPeriod, the local eNodeB removes the neighbor relationship of
cell A with cell B. When the ANR.OptMode parameter is set to
CONTROLLED, the eNodeB reports the optimization advice to the U2020, and
operators determine whether to take the advice. When the parameter is set to
FREE, the eNodeB also removes cell B from the NCL if cell B has no
neighboring cell.
NOTE
The handover success rate used in this document is calculated based on the number of
successful actual handovers from a source cell to a target cell, excluding the number
of RRC connection reestablishments to the target cell.
● Removal of redundant neighbor relationships
This removal function takes effect on intra-RAT neighbor relationships only
when the local cell is configured with more than the minimum number of
neighboring cells. The minimum number of intra-frequency neighboring cells
is specified by the NCellParaCfg.NcellNumForAnr parameter. The minimum
number of inter-frequency neighboring cells is specified by the
EutranInterNFreq.NcellNumForAnr parameter.
A neighbor relationship is redundant if the following conditions are met
within each of ANR.StatPeriodCoeff consecutive measurement periods
defined by ANR.StatisticPeriodForNRTDel:
– The total number of handover attempts from the local cell to all its
neighboring E-UTRAN cells is greater than or equal to the
ANR.StatisticNumForNRTDel parameter value.

eRAN
– The number of handover attempts from the local cell to this neighboring
cell is 0.
– The neighboring cell is not configured as an SCell for any UE in the local
cell.
This removal function does not apply to the neighboring cells that meet any
of the following conditions:
– The blind-handover priority is set to a non-zero value.
– The Overlap Indicator parameter is set to YES.
– The No handover indicator parameter is set to FORBID_HO_ENUM.
– The Plmn List Type parameter is set to GREY_LIST.
NOTE
Adding neighboring cells at the PLMN borders to a greylist prevents the UEs from
repeatedly reading the CGIs of inter-PLMN neighboring cells and therefore reduces UE
power consumption. This also helps detect possible PCI conflicts, which affect
handovers.
● Penalty on removed neighbor relationships
When a neighbor relationship with an E-UTRAN cell is automatically removed
by ANR, penalty on removed neighbor relationships can prevent this neighbor
relationship from being added back to the NRT within a short period. When a
neighbor relationship with an E-UTRAN cell is automatically removed by ANR,
the eNodeB stores the neighbor relationship in an eNodeB-maintained
temporary list. If the number of times the neighbor relationship is required to
be added to the intra-RAT NRT is greater than or equal to the
ANR.EutranNcellDelPunNum parameter value within a measurement period
specified by the ANR.NcellDelPunishPeriod parameter, the eNodeB re-adds
the neighbor relationship to the NRT. Otherwise, the eNodeB does not re-add
the neighbor relationship to the NRT.
NOTE
Removed neighbor relationships under penalty are stored on a temporary list in the
eNodeB. The list is cleared if the eNodeB resets. The list can be regenerated after the
penalty mechanism evaluates neighbor relationships again. Therefore, if the penalty
mechanism is active, the number of neighbor relationships may increase after the
eNodeB is reset. The number can be restored by using the penalty mechanism.
Operators can check the traced Uu messages for the number of attempts to add back
the removed neighbor relationships during the penalty period.
● Removal of neighbor relationships with special flags
During automatic removal of neighbor relationships, the eNodeB does not
remove a neighbor relationship if one of the following conditions is met:
– The MLB_DELNCELCTRL option of the ANR.NrtDelMode parameter is
selected, and the OverlapInd parameter is set to YES for the neighbor
relationship.
– The CA_DELNCELCTRL option of the ANR.NrtDelMode parameter is
selected and the neighboring cell performing CA services has been
configured in the CaGroupSCellCfg MO with SCellBlindCfgFlag set to
TRUE.
– The BLINDHO_DELNCELCTRL option of the ANR.NrtDelMode parameter
is selected and the Blind handover Priority parameter is set to a non-
zero value for the neighbor relationship.

eRAN
Removal of External Cells from an NCL

The eNodeB removes from an NCL an external cell for which the Control Mode
parameter is set to AUTO_MODE in the following scenarios.
● Specification-based external cell removal

A new external cell may be added by ANR when the number of external cells
in an NCL has reached its maximum. If no cells served by the local eNodeB
have a neighbor relationship or a blacklisted neighbor relationship with an
external cell, the eNodeB removes the external cell from the NCL.
This operation is not parameter-controlled.
● Removal of redundant external cells
After the intra-RAT event-triggered ANR and neighbor relationship removal
functions are enabled, a measurement period specified by the
ANR.StatisticPeriodForNRTDel parameter starts. At the end of four
consecutive measurement periods defined by ANR.StatisticPeriodForNRTDel,
the eNodeB removes the external cell that meets certain conditions.
In intra-RAT event-triggered ANR, the eNodeB removes the external cell that
meets both of the following conditions:
– No cells served by the local eNodeB have a neighbor relationship with
the external cell.
– No X2 interface is set up between the local eNodeB and the eNodeB that
serves the external cell if the ADD_NCELL_CFG_SW option of the
GlobalProcSwitch.X2BasedUptNcellCfgSwitch parameter is selected.
4.1.1.2.4 Automatic Optimization of Neighbor Relationship Attributes

ANR identifies neighbor relationships with cells for which the handover statistics
are abnormal and handles the inappropriate neighbor relationships. This function
prevents handover failures due to inappropriate neighbor relationships and
maintains a stable handover success rate. This function is supported only by intra-
RAT event-triggered ANR.
This function is controlled by the IntraRatNoHoSetAnrSwitch option of the

ENodeBAlgoSwitch.AnrSwitch parameter, given that event-triggered ANR has
been enabled.
With this function enabled, ANR works as follows based on the

ANR.NoHoSetMode parameter setting:
● If the ANR.NoHoSetMode parameter is set to NO_CHECK, ANR automatically

sets the No handover indicator parameter to FORBID_HO_ENUM for a
neighbor relationship that meets all the following conditions within a period
defined by ANR.StatisticPeriod:
– The number of handovers from the local cell to the neighboring cell
reaches the ANR.NcellHoStatNum parameter value.
– The success rate of handovers from the local cell to the neighboring cell
is less than or equal to the ANR.NoHoSetThd parameter value.
– The Control Mode parameter for the neighbor relationship is set to
AUTO_MODE.
Otherwise, the No handover indicator parameter value remains unchanged.

eRAN
● If the ANR.NoHoSetMode parameter is set to PCI_CHECK:

If all of the following conditions are met within the measurement period
defined by ANR.StatisticPeriod, the eNodeB instructs the UE to read the ECGI
of this neighboring cell, after the UE sends a measurement report for an
intra-RAT handover containing the EARFCN and PCI of that cell within the
next measurement period. If this cell is an unknown cell, the eNodeB adds
this cell to the NCL and adds the neighbor relationship with this cell to an
NRT.
AUTO_MODE.
is less than or equal to the ANR.HoSucRateForCgiRead parameter value.
NOTE
If the ANR.NoHoSetMode parameter is set to PCI_CHECK, it is recommended that the

ANR.HoSucRateForCgiRead parameter be set to a value greater than or equal to the
ANR.NoHoSetThd parameter value. If the ANR.HoSucRateForCgiRead parameter
value is less than the ANR.NoHoSetThd parameter value, the eNodeB and UE may
not execute the ECGI reading procedure. For example, if the success rate of handovers
to a neighboring cell is greater than the ANR.HoSucRateForCgiRead parameter value
but less than or equal to the ANR.NoHoSetThd parameter value, the eNodeB sets the
No handover indicator to FORBID_HO_ENUM for the neighbor relationship without
instructing the UE to perform ECGI reading.
If ECGI reading is not triggered, the eNodeB performs the following
operations within the current measurement period: If all of the following
conditions are met, the eNodeB automatically sets the No handover
indicator parameter to FORBID_HO_ENUM for the neighbor relationship. If
ECGI reading is triggered but the cell is not considered as an unknown cell,
the eNodeB performs the following operations within the next measurement
period: If all of the following conditions are met, the eNodeB automatically
sets the No handover indicator parameter to FORBID_HO_ENUM for the
neighbor relationship.
is less than or equal to the ANR.NoHoSetThd parameter value.
AUTO_MODE.
Otherwise, the No handover indicator parameter value remains unchanged.
After ANR sets the No handover indicator parameter to FORBID_HO_ENUM for
a neighbor relationship, ANR no longer automatically sets this parameter to
PERMIT_HO_ENUM. Operators should manually optimize or remove this neighbor
relationship. If the relationship is optimized, operators should manually set the No
handover indicator parameter to PERMIT_HO_ENUM.

eRAN
NOTE
● If both the IntraRatAnrAutoDelSwitch and IntraRatNoHoSetAnrSwitch options of the

ENodeBAlgoSwitch.AnrSwitch parameter are selected, it is recommended that the
ANR.DelCellThd parameter be set to a value less than or equal to that of the
ANR.NoHoSetThd parameter. In this case, if the success rate of handovers to a
neighboring cell is less than or equal to ANR.DelCellThd, the eNodeB does not remove
the neighbor relationship with this cell and automatically sets the No handover
indicator parameter to FORBID_HO_ENUM for this neighbor relationship.
● If all of the following options are selected and a neighbor relationship meets both the
conditions of removal of inappropriate neighbor relationships and automatic setting of
the no handover indicator, the eNodeB preferentially performs automatic setting of the
no handover indicator for the neighbor relationship.
● IntraRatAnrAutoDelSwitch option of the ENodeBAlgoSwitch.AnrSwitch
parameter
● IntraRatNoHoSetAnrSwitch option of the ENodeBAlgoSwitch.AnrSwitch
parameter
● EUTRAN_DELCELLERRORNCELL option of the ANR.NrtDelMode parameter
4.1.1.2.5 Automatic Maintenance of Specified-Service Flags of External E-UTRAN

Cells
The specified-service flag of an external E-UTRAN cell, specified by the
EutranExternalCell.SpecifiedCellFlag parameter, indicates whether the external
cell is a specified-service cell. ANR maintains the flags.
If the SPEC_CELL_FLAG_QUERY_SW option of the ANR.SpecServiceCellQuerySw
parameter is selected, the eNodeB queries the specified-service flags of inter-
eNodeB intra- and inter-frequency neighboring cells from the U2020 when adding
an external E-UTRAN cell. Based on the query result, the eNodeB maintains the
flags.
This function is not supported when an external E-UTRAN cell is added based on
the X2 interface.
4.1.1.3 Fast ANR

Fast ANR is also known as periodic ANR. It detects missing intra-RAT neighboring
cells based on periodic UE measurement reports and adds the missing neighboring
cells. This function takes effect on a per base station, cell, or frequency basis. For
details, see 4.1.1.1.3 Method for NCL/NRT Management to Take Effect.

Figure 4-5 illustrates the procedure for using fast ANR to detect missing
neighboring cells.

eRAN
Figure 4-5 Procedure for using fast ANR to detect missing neighboring cells

eRAN
The procedure is as follows:

1. An eNodeB starts a fast ANR check period specified by the
ANR.FastAnrCheckPeriod parameter and selects a number of UEs to
simultaneously perform fast ANR measurements. The maximum number of
UEs is specified by the ANR.FastAnrIntraRatMeasUeNum parameter.
UEs performing voice over IP (VoIP) services do not perform fast ANR
measurements. If a UE initiates a VoIP service and sets up QCI-1 bearers after
being selected to perform fast ANR measurements, the eNodeB takes
different actions on the measurement configuration delivered to the UE
depending on the setting of the GlobalProcSwitch.VoipWithGapMode
parameter.
– If this parameter is set to ENABLE, the eNodeB does not delete the fast-
ANR-related measurement configuration.
– If this parameter is set to DISABLE, the eNodeB delivers an RRC
Connection Reconfiguration message to delete the fast-ANR-related
measurement configuration.
When inter-frequency measurements are required, the source eNodeB must
deliver the inter-frequency measurement configuration to the UE and activate
gap mode. Two gap patterns are defined in section 8.1.2 "Requirements" of
3GPP TS 36.133 V10.2.0: pattern 0 and pattern 1. To speed up the
measurements, the eNodeB uses pattern 0 by default. In pattern 0, the
measurement gap length is 6 ms, and the repetition period is 40 ms.
2. The UEs send measurement reports at an interval specified by the
ANR.FastAnrRprtInterval parameter to the eNodeB. The measurement
reports contain neighboring cells whose signal quality is higher than or equal
to the corresponding threshold. The maximum number of periodic
measurement reports that a UE can send is specified by the
ANR.FastAnrRprtAmount parameter. The E-UTRAN signal quality threshold is
defined by the ANR.FastAnrRsrpThd parameter.
If intra-RAT fast ANR is enabled, it is recommended that the
ANR.FastAnrRprtAmount parameter not be set to r1. This is because a UE
may report only the serving cell information in the first measurement report
during intra-RAT fast ANR. According to section 5.5.4.1 "General" in 3GPP TS
36.331 V10.1.0, if purpose is set to reportStrongestCells, the UE sends the
first measurement report immediately after the quantity to be reported
becomes available for at least either the serving cell or one of the adjacent
cells. Therefore, this IE might include the information only about the serving
cell.
The UE can report information about multiple adjacent E-UTRAN cells at a
time.
3. Based on check results in a fast ANR check period, the eNodeB performs the
following:
– If an unknown cell is reported, the eNodeB sets the number of UEs that
have performed measurements in the check period to 0 and then selects
a number of UEs specified by the ANR.FastAnrIntraRatMeasUeNum
parameter to perform measurements. If a UE reports multiple adjacent E-
UTRAN cells, the eNodeB instructs the UE to read the ECGI of the
strongest cell. Then, the eNodeB adds the detected cell to an NCL and
NRT. For details about the policies for adding the cell to the NCL and
NRT, see Automatic Addition of Missing Neighboring Cells.

eRAN
– If no unknown cell is reported, the check period ends. The eNodeB checks
the total number of UEs that have performed measurements. If the total
number is less than the ANR.FastAnrIntraRatUeNumThd parameter
value, the eNodeB starts the next round of fast ANR measurements. If the
total number is greater than or equal to the
ANR.FastAnrIntraRatUeNumThd parameter value, the eNodeB enters
the monitoring state.
Before the monitoring state period defined by
ANR.FastAnrMonitorStatePeriod elapses, the eNodeB does not select
UEs for fast ANR measurements and monitors whether event-triggered
ANR measurement reports contain the PCI of an unknown cell.
▪ The eNodeB exits the monitoring state when it receives a

measurement report that contains the PCI of an unknown cell. When
the eNodeB exits the monitoring state, it starts measurements again.
▪ Otherwise, the eNodeB stays in the monitoring state.

When the monitoring state period defined by
ANR.FastAnrMonitorStatePeriod elapses, the eNodeB automatically
exits the monitoring state and enters the next round of fast ANR.

After detecting a missing intra-RAT neighboring cell based on UE measurements,
the eNodeB handles the missing neighboring cell differently, depending on
whether the neighboring cell is an intra-frequency neighboring cell or inter-
frequency neighboring cell. In addition, the handling varies with the setting of the
ANR.FastAnrMode parameter and adn the fact that the strongest or second
strongest unknown neighboring cell is or not an intra-eNodeB cell of the serving
cell.
Table 4-5 and Table 4-6 describes the handling of a missing intra-frequency
neighboring cell and a missing inter-frequency neighboring cell, respectively.
Table 4-5 Handing of a missing intra-frequency neighboring cell
Intra- NCL_NRT_MODE NCL_MODE NRT_MODE

Site
Neighb
oring
Cell
Yes The cell is added to the NRT. No action is The UE is instructed

taken. to report the ECGI
and the cell is added
to the NRT.
No The cell is added to the NCL The cell is The UE is instructed

and NRT. added to to report the ECGI
the NCL. and the cell is added
to the NCL and NRT.

eRAN
Table 4-6 Handing of a missing inter-frequency neighboring cell
Intra- NCL_NRT_MODE NCL_MODE NRT_MODE

Site
Neighb
oring
Cell
Yes ● If the cell is the strongest No action is The UE is instructed

neighboring cell, it is added taken. to report the ECGI
to the NRT. and the cell is added
● If the cell is the second to the NRT.
strongest neighboring cell,
no action is taken.
No ● If the cell is the strongest The cell is The UE is instructed

neighboring cell, it is added added to to report the ECGI
to the NCL and NRT. the NCL. and the cell is added
● If the cell is the strongest to the NCL and NRT.
neighboring cell, it is added
to the NCL.

For details, see 4.1.1.2.2 NCL Entry Modification.
4.1.1.3.3 Automatic Maintenance of Specified-Service Flags of External E-UTRAN

Cells
For details, see 4.1.1.2.5 Automatic Maintenance of Specified-Service Flags of
External E-UTRAN Cells.
4.1.1.4 Backward ANR

In backward ANR, the target cell can add the source cell to an NCL and NRT after
obtaining the information about the source cell. Intra-RAT backward ANR adds a
neighbor relationship of a target cell with a source cell in a handover.
When intra-RAT event-triggered ANR or fast ANR is enabled, intra-RAT backward

ANR is controlled by the BACKWARD_ANR_SW option of the
CellAlgoSwitch.AnrAlgoSwitch parameter.
If the neighbor relationship with an inter-eNodeB cell has been added to the NRT
of the local cell, the neighbor relationship with the local cell can be added to the
NRT of the inter-eNodeB cell based on UE history information. According to
section 9.2.1.42 "UE History Information" of 3GPP TS 36.413 V10.1.0 and section
9.2.38 "UE History Information" of 3GPP TS 36.423 V10.1.0, the "UE History
Information" contains information about cells that a UE has been served by prior
to the target cell. The information includes the ECGI, cell type, and duration of
stay.

eRAN
Figure 4-6 illustrates the procedure for using UE history information to detect a
missing intra-RAT neighboring cell. This procedure is triggered by an intra-RAT
handover.
Figure 4-6 Procedure for using UE history information to detect a missing intra-
RAT neighboring cell
1. The source eNodeB sends a handover request message to the target eNodeB.
2. After obtaining the UE history information from the message, the target
eNodeB checks whether the ECGI of the last visited cell (in this example, the
source cell) exists in the intra-RAT NCL and an intra-RAT NRT of the target
eNodeB.
– If the ECGI exists in the NCL but does not exist in the NRT, the target
eNodeB adds the neighbor relationship with the source cell to the NRT
and the procedure ends.
– If the ECGI does not exist in the NCL, the target eNodeB proceeds to 3.
3. The target eNodeB reports the ECGI of the source cell to the U2020.
4. The U2020 queries the PCI, TAC, and PLMN list of the source cell identified by
the reported ECGI and sends the results to the target eNodeB. Then, the
target eNodeB adds the missing neighboring cell to an NCL and the missing
neighbor relationship to the NRT, and the procedures ends. If the target and
source cells are managed by different U2020s, the U2020s support the
function of cross-U2020 neighboring cell information query. For details, see
4.1.3.3 Hardware.
If a neighbor relationship with an intra-eNodeB cell is added to the NRT of a
serving cell or the serving cell successfully performs a handover to the intra-
eNodeB neighboring cell, the serving eNodeB adds the neighbor relationship with
the serving cell to the NRT of the intra-eNodeB cell.

eRAN
NOTE
When the CPU usage of the main control board exceeds 80%, the eNodeB does not handle
unknown CGIs or perform backward ANR to prevent system overload.
If the eNodeB serving the target cell is provided by another vendor, the eNodeB cannot
obtain information about the target cell from the U2020. In this case, NRT entry addition
may fail.
It takes a period of time to query information about the source cell such as PCI, TAC, and
PLMN list on the U2020. Therefore, there is a latency of adding neighbor relationships
through backward ANR.
4.1.1.5 NCL/NRT Self-Management Based on X2 Messages

When an X2 interface is set up or eNodeB configurations change, the local and
peer eNodeBs exchange information over the X2 interface to update NCLs and
NRTs. For details about the messages transmitted during X2 setups and eNodeB
configuration updates, see section 8.3 "Global Procedures" in 3GPP TS 36.423
V10.0.0.
NCL/NRT self-management based on X2 messages manages only external cells

and neighbor relationships for which the Control Mode parameter is set to
AUTO_MODE. For details about the Control Mode parameter, see 4.1.1.1.1
NCL/NRT Control Mode.
If the GlobalProcSwitch.X2ServedCellType parameter is set to

CONFIGURED_CELL, the X2 message sent by the local eNodeB includes all active
and inactive cells. The local eNodeB sends an ENB CONFIGURATION UPDATE
message carrying the IE Served Cells To Delete to the peer eNodeB only if a cell
served by the local eNodeB is removed.
If the GlobalProcSwitch.X2ServedCellType parameter is set to ACTIVE_CELL, the

X2 message sent by the local eNodeB includes only active cells. The local eNodeB
sends the peer eNodeB an ENB CONFIGURATION UPDATE message carrying the
IE Served Cells To Delete when a cell served by the local eNodeB is manually
deactivated or the S1 interface is faulty. After receiving this message, the peer
eNodeB incorrectly removes the cell from its NCL and NRTs. If no active cells exist,
configuration update cannot be delivered to the peer eNodeB by using X2
message.
NOTICE
It is recommended that the GlobalProcSwitch.X2ServedCellType parameter be

set to CONFIGURED_CELL. This prevents peer eNodeBs from removing neighbor
relationships with cells served by the local eNodeB when the cells are deactivated
for reasons such as local eNodeB upgrade.
4.1.1.5.1 NCL/NRT Entry Addition and Update
NCL Entry Addition Based on X2 Messages

Figure 4-7 illustrates the signaling procedure of X2 setup.

eRAN
Figure 4-7 Procedure for adding external cells based on X2 messages.
1. When an X2 interface between eNodeB 1 and eNodeB 2 is set up, the eNodeB
1 informs eNodeB 2 by sending an X2 SETUP REQUEST message.
2. After receiving the message, eNodeB 2 adds all cells served by eNodeB 1 to
the NCL of eNodeB 2 only if the ADD_NCELL_CFG_SW option of the
GlobalProcSwitch.X2BasedUptNcellCfgSwitch parameter is selected for
eNodeB 2.
3. eNodeB 2 responds to eNodeB 1 with an ENB X2 SETUP RESPONSE message.
4. After receiving the ENB X2 SETUP RESPONSE message from eNodeB 2,
eNodeB 1 adds all cells served by eNodeB 2 to the NCL of eNodeB 1 only if
the ADD_NCELL_CFG_SW option of the
eNodeB 1.
NCL Entry Addition and NCL/NRT Update Based on eNodeB Configuration

Update Messages
If a cell is added to the local eNodeB or the cell configuration (downlink EARFCN,
PCI, ECGI, TAC, or PLMN list) of the local eNodeB changes, the local eNodeB sends
an ENB CONFIGURATION UPDATE message to the peer eNodeB over the X2
interface to inform the peer eNodeB of the change. The peer eNodeB
automatically adds the new cell to its NCL or updates the cell configuration in its
NCL and NRT based on the types of IEs contained in the message.
Figure 4-8 illustrates the signaling procedure of eNodeB configuration update.

eRAN
Figure 4-8 Procedure for adding external cells or updating external cells and
neighbor relationships based on eNodeB configuration update messages
1. When a cell is added to or modified in eNodeB 1, eNodeB 1 sends an ENB

CONFIGURATION UPDATE message to eNodeB 2.
2. eNodeB 2 performs one of the following operations:
– If the NCL of eNodeB 2 does not contain the cell and the
ADD_NCELL_CFG_SW option of the
eNodeB 2, eNodeB 2 adds the cell to its NCL.
– If the following conditions are met, eNodeB 2 updates the NCL and NRT
entry with the new downlink EARFCN, PCI, ECGI, TAC, or PLMN list:
▪ The NCL of eNodeB 2 contains the cell.
▪ The Control Mode parameter for the NCL/NRT entry is set to

AUTO_MODE.
▪ The MOD_NCELL_CFG_SW option of the

GlobalProcSwitch.X2BasedUptNcellCfgSwitch parameter is
selected for eNodeB 2.
3. eNodeB 2 responds to eNodeB 1 with an ENB CONFIGURATION UPDATE
ACKNOWLEDGE message.
Before modifying eNodeB configuration data (such as parameters

eNodeBFunction.eNodeBId, Cell.CellId, Cell.LocalCellId, Cell.PhyCellId, and
Cell.DlEarfcn, and parameters in the MOs CnOperator, CnOperatorTa, and
CellOp) using the CME, you are advised to deselect the ADD_NCELL_CFG_SW and
MOD_NCELL_CFG_SW options of the
GlobalProcSwitch.X2BasedUptNcellCfgSwitch parameter. If one of the options is
selected, the eNodeB may experience conflicts between modified configuration
data delivered from the CME and the NCL/NRT update based on X2 messages,
thereby causing configuration data loss or abnormality. Deselecting these options
ensures that NCLs/NRTs will not be automatically updated based on X2 messages.
Instead, NCL/NRT data is modified using the CME. If operators directly deliver the
configuration database using the CME to modify the eNodeB configuration, no X2
update messages are generated. In this case, NCLs and NRTs cannot be updated.

eRAN
Neighboring Frequency Addition Based on X2 Messages and eNodeB

Configuration Update Messages
If the ADD_FREQ_CFG_SW option of the
GlobalProcSwitch.X2BasedUptNcellCfgSwitch parameter is selected, the local
eNodeB can automatically synchronize neighboring frequencies of cells served by
it with neighboring frequencies of cells served by the peer eNodeB using X2
messages. X2 messages include X2 SETUP REQUEST, X2 SETUP RESPONSE, and
ENB CONFIGURATION UPDATE messages.
When an eNodeB adds a neighboring frequency based on X2 messages, the

FreqAddCtrl option of the GlobalProcSwitch.X2BasedUptENodeBPolicy
parameter specifies whether the eNodeB filters frequencies based on the operator
information. If this option is selected, the local eNodeB does not filter frequencies
but directly configures the operating frequencies of cells served by the peer
eNodeB as neighboring frequencies of the local cell. If this option is deselected,
the local eNodeB filters frequencies. It checks whether the operator information of
the local cell and that of cells served by the peer eNodeB are the same. The local
eNodeB configures a frequency as a neighboring frequency only if the frequency
has the same operator information as the local cell.

If a cell under the local eNodeB is removed, the local eNodeB sends an ENB
CONFIGURATION UPDATE message to the peer eNodeB through the X2 interface
to inform the peer eNodeB of the change. The peer eNodeB automatically
removes the cell from its NCL and removes the neighbor relationship with the cell
from its NRT. NCL/NRT entry removal based on X2 messages is controlled by the
DEL_NCELL_CFG_SW option of the
GlobalProcSwitch.X2BasedUptNcellCfgSwitch parameter.
Figure 4-9 illustrates the procedure of for removing external cells and neighbor
relationships.
Figure 4-9 Procedure for removing external cells and neighbor relationships
1. When a cell served by eNodeB 1 is removed, eNodeB 1 sends eNodeB 2 an

ENB CONFIGURATION UPDATE message that contains the IE Served Cells To
Delete.

eRAN
2. Considering the ECGI in the IE Served Cells To Delete, eNodeB 2 performs one
of the following operations:
– eNodeB 2 removes the external cell and the neighbor relationships if the
following conditions are met:
▪ The ECGI is included in both an NCL and an NRT of eNodeB 2.
▪ The No remove indicator parameter is set to PERMIT_RMV_ENUM

for the neighbor relationship with the cell identified by the ECGI.
▪ The Control Mode parameter is set to AUTO_MODE for the external

cell and neighbor relationship.
– If the ECGI is included in the NCL but not any NRT of eNodeB 2, eNodeB
2 removes the external cell identified by the ECGI from the NCL.
3. eNodeB 2 responds to eNodeB 1 with an ENB CONFIGURATION UPDATE
ACKNOWLEDGE message.
NOTE
If the GlobalProcSwitch.X2ServedCellType parameter is set to ACTIVE_CELL for a local

eNodeB, the ADD_NCELL_CFG_SW, MOD_NCELL_CFG_SW, and DEL_NCELL_CFG_SW
options of the GlobalProcSwitch.X2BasedUptNcellCfgSwitch parameter must be selected
for the peer eNodeB to ensure cell configuration updating when the modification of the
downlink EARFCN, PCI, or ECGI in the local eNodeB causes cell reestablishment.
In NCL/NRT entry removal based on X2 messages, the optimization advice needs to be
reported to the U2020 if all of the following conditions are met. The NRT entry removal is
subject to the manual confirmation on the U2020. After an NRT entry is removed, the
removal of redundant NCL/NRT entries function determines whether to remove the
corresponding NCL entry.
● The ANR.OptMode parameter is set to CONTROLLED.
● The NCellParaCfg.RatType parameter is set to EUTRAN.
● The NCellParaCfg.CellAnrOptMode parameter is set to CONTROLLED.
4.1.1.6 NRT/NCL Entry Management Based on the eNodeB ID Blacklist

In NRT/NCL entry management based on the eNodeB ID blacklist, the eNodeB
detects and performs differentiated management of neighboring cells with
abnormal eNodeB IDs when adding unknown neighboring cells.
The eNodeB adds a specific eNodeB ID to the blacklist based on the setting of the
EnodebIdBlacklist.EnodebId parameter. At the same time, if there is an external
cell or neighbor relationship with a cell having the corresponding eNodeB ID, the
external cell or neighbor relationship should be removed. If an unknown
neighboring cell to be added has a blacklisted eNodeB ID, the source eNodeB
neither initiates handovers to this cell nor adds this cell to the NCL and NRT.
4.1.2 Network Analysis
4.1.2.1 Benefits
Intra-RAT ANR handles neighbor relationships of E-UTRAN cells with other E-
UTRAN cells. It automatically maintains the completeness, validity, and correctness
of the neighbor relationships to improve network performance. In addition, intra-

eRAN
RAT ANR automatically optimizes the attributes of neighbor relationships,

reducing manual intervention while decreasing the costs of network planning,
network optimization, and O&M.
Event-triggered ANR and fast ANR
● Event-triggered ANR and fast ANR can optimize intra-RAT neighbor
relationships and reduce service drops and handover failures caused by
neighbor relationship problems. This decreases the service drop rate and
increases the intra-RAT handover success rate. However, the gain produced by
ANR cannot be quantified. The number and distribution of ANR-capable UEs
affect how fast ANR can detect missing neighboring cells.
● Neighboring cells with overshoot coverage exist on the live network. If UEs
report such types of unknown neighboring cells based on measurements and
initiate handovers to the neighboring cells, the service drop rate increases or
the intra-RAT handover success rate fluctuates. In this case, you need to
optimize the network coverage configuration and it is recommended that
blacklisted neighbor relationship management be enabled.
The following describes the application scenarios of intra-RAT ANR where
maximum gains can be provided in different stages of network deployment.
New Deployment
● Intra-RAT event-triggered ANR
It is recommended that removal of redundant neighbor relationships with E-
UTRAN cells be disabled. Otherwise, neighbor relationships may be
unexpectedly removed because the number of UEs in handovers is small.
● (Optional) Intra-RAT fast ANR
It is recommended that intra-RAT fast ANR be enabled only when the
network serves a small number of commercial UEs or engineering
optimization (for example, downtilt adjustment and power adjustment) does
not finish. It is recommended that this function be disabled when the network
serves a large number of commercial UEs and engineering optimization
finishes.
● (Optional) Intra-RAT backward ANR
If handovers between cells on all frequencies are bidirectional, it is
recommended that this function be enabled. Otherwise, it is recommended
that this function be disabled to avoid unnecessary neighbor relationships
from being added to NRTs.
● Automatic optimization of neighbor relationships with cells having abnormal
intra-RAT handover success rates
This function includes two sub-functions. It is recommended that PCI
confusion detection based on the handover success rate be enabled to avoid
PCI confusions from affecting the handover success rate. It is recommended
that automatic setting of the no handover indicator based on the handover
success rate be enabled based on the actual requirements. If this sub-function
is enabled, the No handover indicator parameter is automatically set to
FORBID_HO_ENUM for neighbor relationships.
● NCL/NRT self-management based on X2 messages
NCL entry addition based on X2 messages: It is recommended that this
function be disabled to avoid redundant NCL entries. Especially when cells are

eRAN
not geographically adjacent, this function causes a large number of redundant

NCL entries.
NCL/NRT entry update based on X2 messages: It is recommended that this
function be enabled if an X2 interface is configured between the local and
peer eNodeBs and operators do not use the CME to modify the eNodeB
configurations that affect neighbor relationships. If the function is enabled in
this situation, inappropriate neighbor relationships can be avoided. Examples
of the configuration data are parameters eNodeBFunction.eNodeBId,
Cell.CellId, Cell.LocalCellId, Cell.PhyCellId, and Cell.DlEarfcn, as well as the
parameters in the MOs CnOperator, CnOperatorTa, and CellOp. If either of
the preceding conditions is not met, it is recommended that this function be
disabled.
NCL/NRT entry removal based on X2 messages: It is recommended that this
function be enabled if an X2 interface is configured between the local and
peer eNodeBs and operators do not use the CME to modify the eNodeB
configurations that affect neighbor relationships. If this function is enabled in
this situation, inappropriate or redundant neighbor relationships can be
removed. If either of the preceding conditions is not met, it is recommended
that this function be disabled.
If NCL/NRT entry update or removal based on X2 messages is enabled, you
are advised to set the GlobalProcSwitch.X2ServedCellType parameter to
CONFIGURED_CELL to prevent neighbor relationship configuration loss due
to the modification of ECGIs or PCIs.
● (Optional) HO blacklist
Operators can configure a HO blacklist in some special cases. For example, if
UEs in indoor cells on high floors can detect outdoor neighboring cells and
users do not want UEs to initiate handovers to such outdoor neighboring
cells, it is recommended that the neighbor relationships with such outdoor
cells be added to the blacklists.
HO blacklists are configured by operators.
● (Optional) HO whitelist
Operators can configure a HO whitelist in some special cases. For example,
the traffic volumes of cells are uneven in the places, such as sports stadiums
or venues. These cells have traffic volumes only in special occasions. If the
neighbor relationships with the cells around are not added to the HO
whitelists, ANR may determine these neighbor relationships as redundant
neighbor relationships and removes them from the NRTs. In this case, you are
advised to add the neighbor relationships with the cells around the areas
whose traffic volume is uneven to the HO whitelists. This prevents ANR from
mistakenly removing them from the NRTs.
HO whitelists are configured by operators.
● (Optional) RRC blacklist
Operators can configure an RRC blacklist in some special cases. For example,
if cells in the network edge area of an operator operate on the same
frequency but do not share PCIs, operators can add the PCI range used by
another operator to the RRC blacklists. This prevents the UEs served by cells
of the operator from reporting cells of another operator.
When adding a cell to an RRC blacklist, ensure that the cell does not share
the same PCI with other intra-frequency neighboring cells. For example, if
neighboring cells A and B operate on the same frequency and share the same

eRAN
PCI and neighboring cell A is not an expected target cell for handovers and
redirections, you are advised not to add this PCI to the RRC blacklist. This is
because the RRC blacklist is set based on PCIs of cells operating on the same
frequency. If the operating frequency and PCI of neighboring cell A are
blacklisted, neighboring cell B cannot be the target cell for handovers and
redirections as well.
NOTE
In service steering scenarios, if an E-UTRA frequency is deployed for providing only

VoIP services, initial planning and configuration of the neighbor relationships of cells
on this frequency is recommended.
Site Expansion or Migration

It is recommended that the following functions be enabled during site expansion
and migration. Enable other functions according to operators' policies.
It is recommended that removal of inappropriate neighbor relationships,
specification-based removal, and removal of redundant neighbor relationships
be enabled.
● (Optional) Intra-RAT backward ANR
Enable this function based on the policies applied to frequencies on the
network.
● Automatic optimization of neighbor relationships with cells having abnormal
intra-RAT handover success rates
It is recommended that this function be enabled.
● (Optional) NCL/NRT self-management based on X2 messages
It is recommended that NCL/NRT self-management based on X2 messages be
enabled.
4.1.2.2 Impacts
Network Impacts
– Event-triggered ANR prolongs the delay in the handover of a UE that
meets the handover conditions but is still performing ANR measurements
to detect an unknown cell. After the neighbor relationship with the cell is
added, ANR measurements are not triggered during subsequent
handovers to the cell and therefore the delay in handovers to the cell is
no longer prolonged.
– Event-triggered ANR negatively affects the UE throughput because UEs
cannot be scheduled while they are reading the CGI of an unknown cell
in the DRX state. On commercial networks, UEs are usually not fully
buffered, and therefore the impact on the UE throughput is limited. After
the neighbor relationship with the cell is added, the throughput is no
longer affected when UEs are handed over to the cell.
– UEs read CGIs in sleep time during DRX. The sleep time stops when a
data packet arrives. This has an impact on the CGI reading success rate.
This success rate is even lower at UEs running VoLTE services, which are

eRAN
scheduled at a fixed interval and encounter a higher probability that the

sleep time stops. After a CGI is acquired, the identified cell is
automatically configured as a neighboring cell and UEs are no longer
instructed to read the CGI.
● Intra-RAT fast ANR
– Periodic reporting of the PCIs of the strongest cells may affect network
performance.
LTE measurements are performed on a per frequency basis. Periodic
reporting of the PCIs of the strongest intra-frequency cells does not affect
UE throughput. Inter-frequency ANR requires gap-assisted measurements,
which negatively affect UE throughput.
– CGI reading affects network performance as follows:
▪ To read the CGI of an unknown cell, the UE must be synchronized

with the cell. The UE acquires the PLMN ID, CGI, and TAC of the cell
from the system information and then reports the information to the
source eNodeB. This process negatively affects UE throughput.
▪ To read the CGI of an unknown cell, the UE enters sleep time in the
DRX state. During sleep time, the UE cannot be scheduled, and
therefore UE throughput is negatively affected.
– The overall impact of fast ANR on network performance is controllable.
This is because there are upper limits on the number of UEs involved in
fast ANR per cell and on the number of periodic measurement reports
from a UE within each period.
– A larger number of periodic measurement reports from a UE results in
more power consumption of the UE.
Related KPIs include:
● Intra-frequency Handover Out Success Rate

● Inter-frequency Handover Out Success Rate
● Service Drop Rate, which is represented by L.E-RAB.AbnormRel/(L.E-
RAB.NormRel + L.E-RAB.AbnormRel) x 100%
Counter ID Counter Name
1526726995 L.HHO.IntraeNB.IntraFreq.PrepAttOut
1526726996 L.HHO.IntraeNB.IntraFreq.ExecAttOut
1526726997 L.HHO.IntraeNB.IntraFreq.ExecSuccOut
1526727001 L.HHO.IntereNB.IntraFreq.PrepAttOut
1526727002 L.HHO.IntereNB.IntraFreq.ExecAttOut
1526727003 L.HHO.IntereNB.IntraFreq.ExecSuccOut
1526726998 L.HHO.IntraeNB.InterFreq.PrepAttOut
1526726999 L.HHO.IntraeNB.InterFreq.ExecAttOut
1526727000 L.HHO.IntraeNB.InterFreq.ExecSuccOut

eRAN
1526727004 L.HHO.IntereNB.InterFreq.PrepAttOut
1526727005 L.HHO.IntereNB.InterFreq.ExecAttOut
1526727006 L.HHO.IntereNB.InterFreq.ExecSuccOut
1526727546 L.E-RAB.AbnormRel
1526727547 L.E-RAB.NormRel
Function Impacts
RAT Function Function Referenc Description
Name Switch e
FDD PCI ENodeBAlgoS PCI PCI conflict detection is

TDD conflict witch.PciConf Conflict triggered when intra-RAT ANR
detection lictDetectSwi Detection changes neighboring cell
and self- tch and Self- information.
optimizati Optimizat
on ion
FDD CA cell None Carrier Currently, if the E-UTRAN
TDD Aggregati supports CA (included in LTE-A
on Introduction) according to
eNodeB configurations and UE
capabilities, the eNodeB does
not select certain CA UEs to
perform measurements for
intra-RAT event-triggered ANR
or intra-RAT fast ANR. The CA
UE selection rule is specified
by the ANR.CaUeChoseMode
parameter.
FDD Handover None Mobility ECGI reading is triggered if a

TDD Managem handover is required when PCI
ent in confusion occurs and ANR is
Connecte enabled.
d Mode

eRAN

Name Switch e
FDD Cell None Cell After an outage cell is

TDD outage Outage detected, cell outage detection
detection Detection and compensation adjusts the
and and values of the
compensa Compens EutranInterFreqN-
tion ation Cell.NoHoFlag and
EutranInterFreqN-
Cell.NoRmvFlag parameters
to:
● Prevent ANR from
removing an outage cell
from the NRT and adding
the outage cell to the
handover blacklist.
● Prohibit UEs from being
handed over to the outage
cell.
FDD eMTC EMTC_SWITC eMTC eMTC UEs do not support

TDD introducti H option of ANR.
on the eMTC-only cells do not
CellEmtcAlgo support ANR.
.EmtcAlgoSw
itch
parameter
FDD Specified Cell.Specified WBB ● If the operations support

TDD service CellFlag system (OSS) does not
carrier support eNodeB's query
about attributes of new
external cells, neighboring
non-common cells
automatically added by
ANR are configured as
common cells. In this case,
you need to check and
manually correct their
carrier attributes.
● If the OSS supports
eNodeB's query about
attributes of new external
cells, correct carrier
attributes are configured
for automatically added
neighboring non-common
cells. In this case, ANR has
no impact on the specified
service carrier function.

eRAN
4.1.3 Requirements
4.1.3.1 Licenses
RAT Feature ID Feature Model Sales Unit
Name
FDD LOFD-002001 Automatic LT1S000ANR00 Per Cell

Neighbour
Relation
(ANR)
TDD TDLOFD-0020 Automatic LT1ST00ANR00 Per Cell

01 Neighbour
Relation
(ANR)
4.1.3.2 Software
Before activating this function, ensure that its prerequisite functions have been
activated and mutually exclusive functions have been deactivated. For detailed
operations, see the relevant feature documents.
Prerequisite Functions
Name Switch e
FDD Automati None None This is a function of the

TDD c U2020.
Neighbor
Relation
Optimizat
ion - LTE

eRAN

Name Switch e
FDD Service- ENodeBAlgoS Mobility Event-triggered ANR triggered

TDD based witch.HoAlgo Managem by service-request-based inter-
inter- Switch ent in frequency handover
frequency Connecte measurements requires that
handover d Mode service-request-based inter-
frequency handover be
enabled (controlled by the
ServiceReqInterFreqHoS-
witch option of the
ENodeBAlgoSwitch.HoAlgoS
witch parameter). Event-
triggered ANR triggered by
service-based inter-frequency
handover measurements
requires that service-based
inter-frequency handover be
enabled (controlled by the
ServiceBasedInterFreqHoS-
witch option of the
ENodeBAlgoSwitch.HoAlgoS
witch parameter).
Mutually Exclusive Functions

Name Switch e
FDD RAN ENodeBShari RAN If the serving cell and

TDD sharing ngMode.ENo Sharing neighboring cells are managed
with deBSharingM by different OSSs, intra-RAT
common ode ANR does not work when the
carrier PLMN ID at the top of the
PLMN list is rotated.
FDD Hybrid ENodeBShari RAN If the serving cell and

TDD RAN ngMode.ENo Sharing neighboring cells are managed
sharing deBSharingM by different OSSs, intra-RAT
ode ANR does not work when the
PLMN ID at the top of the
PLMN list is rotated.
4.1.3.3 Hardware
Base Station Models

No requirements

eRAN
Boards
No requirements
RF Modules
No requirements
Cells
● In automatic detection of missing neighboring cells using UE history
information, if the serving cell and neighboring cell are not managed by the
same U2020, the U2020s must support the function of cross-U2020
neighboring cell information query.
● The intra-RAT ANR measurement information (including frequencies to be
measured) has been configured in the EutranInterNFreq MOs. For details,
see Mobility Management in Connected Mode.
4.1.3.4 Networking
Before deploying a large number of micro eNodeBs and LampSite eNodeBs, re-
plan the PCI group of cells served by the macro eNodeBs and that of cells served
by micro eNodeBs and LampSite eNodeBs as follows:
1. The PCI group of cells served by the macro eNodeBs must be different from
that of cells served by the micro eNodeBs and LampSite eNodeBs.
2. The PCI and neighboring cell configurations of the cells served by the macro
eNodeBs are adjusted based on the planning result.
3. After the adjustment, the micro eNodeBs and LampSite eNodeBs are deployed
and PCIs in the specified group are allocated to cells served by the micro
eNodeBs and LampSite eNodeBs.
In FDD, before enabling super combined cell, re-plan the PCI groups of regular
cells and super combined cells as follows:
1. The PCI group of the regular cells must be different from that of the super
combined cells.
2. The PCI and neighboring cell configurations of the regular cells are adjusted
based on the planning result.
3. After the adjustment, the super combined cells are deployed and PCIs in the
specified group are allocated to the super combined cells.
In TDD, there are no requirements.
4.1.3.5 Others
Intra-RAT ANR requires that UEs on the network be DRX-capable and support
intra- and inter-frequency measurements for ANR.
4.1.4 Operation and Maintenance
4.1.4.1 Data Configuration

eRAN
4.1.4.1.1 Process
The deployment process for intra-RAT ANR varies with network deployment
stages.
eNodeB Deployment
Figure 4-10 illustrates the deployment process for intra-RAT ANR during eNodeB
deployment.

eRAN
Figure 4-10 Deployment process for intra-RAT ANR

eRAN

Figure 4-11 illustrates the deployment process for intra-RAT ANR during site
expansion or migration.

eRAN
Figure 4-11 Deployment process for intra-RAT ANR

eRAN
4.1.4.1.2 Data Preparation
NCL/NRT Control Mode

Table 4-7 describes the parameters used for function activation.
Table 4-7 Parameters used for activation

Parameter Parameter ID Setting Notes
Name
Control Mode EutranExternalCe None

ll.CtrlMode
Control Mode EutranIntraFreqN None

Cell.CtrlMode
Control Mode EutranInterFreqN None

Cell.CtrlMode
Control Mode EutranBlkNCell.C None

trlMode
NRT Optimization Mode


Name
Optimization ANR.OptMode Set this parameter to FREE or

Mode CONTROLLED based on the operator's
policy.
Cell ANR NCellParaCfg.Cel None

Optimization lAnrOptMode
Mode
Method for NCL/NRT Management to Take Effect

Table 4-9 and Table 4-10 describe the parameters used for function activation
and optimization, respectively.

eRAN

Parameter Parameter ID Option Setting Notes
Name
IntraFreq ANR Cell.IntraFreqAnr None Set this parameter to

Indication Ind NOT_ALLOWED or
ALLOWED based on
the operator's policy.
ANR EutranInterNFreq None Set this parameter to

Indication .AnrInd NOT_ALLOWED or
ALLOWED based on
ANR Function CellAlgoSwitch.A INTRA_RAT_ANR To enable the

Switch nrFunctionSwitc _SW following functions,
h you are advised to
select the
INTRA_RAT_ANR_SW
option.
● Neighbor
relationship
addition in intra-
RAT event-
triggered ANR
● Removal of
inappropriate
NCL/NRT entries in
intra-RAT ANR
● Specification-based
removal in intra-
RAT ANR
● Removal of
redundant
NCL/NRT entries in
intra-RAT ANR
● Intra-RAT fast ANR
ANR CellAlgoSwitch.A LTE_AUTON_GAP To enable CGI reading

Algorithm nrAlgoSwitch _CGI_SW using autonomous
Switch gaps, select the
LTE_AUTON_GAP_CGI
_SW option.

eRAN
Table 4-10 Parameters used for optimization

Name
CA UE Chose ANR.CaUeChose This parameter specifies the policy based

Mode Mode on which the eNodeB selects CA UEs to
perform ANR measurements.
● If the CA UE penetration rate is low in
the network, the recommended value is
CA_UE_CARRIER_NUM.
● If the CA UE penetration rate is high in
the network, the recommended value is
ANR_UE_CAP.
● It is not recommended that this
parameter be set to CA_UE_CAP. This is
because this value presents a strict UE
selection condition, affecting the
efficiency of ANR.
Smart ANR.SmartPreall This parameter specifies whether to enable

Preallocation ocationMode smart preallocation during CGI reading.
Mode ● If this parameter is set to ENABLE,
smart preallocation takes effect during
CGI reading when smart preallocation is
enabled. In this case, uplink scheduling
delay becomes shorter but the DRX
sleep time that UEs stay in becomes
shorter, decreasing the success rate of
CGI reading. In addition, in PCI
confusion scenarios, the service drop
rate may increase.
● If this parameter is set to DISABLE,
smart preallocation does not take effect
during CGI reading even when smart
preallocation is enabled. In this case,
uplink scheduling delay becomes longer
but the DRX sleep time that UEs stay in
becomes longer, increasing the success
rate of CGI reading. In addition, in PCI
confusion scenarios, the service drop
rate may decrease.
Long DRX CellDrxSpecialPa This parameter specifies the long DRX

Cycle for ra.LongDrxCycleF cycle for intra-RAT ANR.
Intra-RAT orIntraRatAnr A larger value of this parameter results in
ANR a longer duration for UEs to perform CGI
reading and a longer system delay.
To ensure the CGI reading success rate, you
are advised to set the long DRX cycle to a
time period greater than or equal to 256
ms.

eRAN

Name
DRX Inactivity CellDrxSpecialPa ● A smaller value of this parameter

Timer For ra.FddAnrDrxInac results in a longer DRX sleep time for
FDD ANR tivityTimer UEs during CGI reading, a higher CGI
DRX Inactivity CellDrxSpecialPa reading success rate, a longer delay of
Timer for ra.TddAnrDrxInac data scheduling.
TDD ANR tivityTimer ● A larger value of this parameter results
in the opposite effects.
Event-Triggered ANR

Name
ANR ENodeBAlgoSwit IntraRatEventAnr To enable neighbor

algorithm ch.AnrSwitch Switch relationship addition
switch MlbBasedEventA by intra-RAT event-
nrSwitch triggered ANR, you
are advised to select
ServiceBasedEve the following options:
ntAnrSwitch
● IntraRatEventAnrS
IntraRatEnhance- witch
dEventAnrSwitch
● MlbBasedEventAn
IntraRatNoHoSet rSwitch
AnrSwitch
● ServiceBasedEven-
CaBasedEventAnr tAnrSwitch
Switch
● IntraRatEnhance-
InterFreqAngcAn dEventAnrSwitch
rSwitch
● IntraRatNoHoSetA
ServiceReqEvent nrSwitch
AnrSwitch
● CaBasedEventAnr
IntraRatEventAnr Switch
Switch
● InterFreqAngcAnr
Switch
● ServiceReqEventA
nrSwitch

eRAN

Name
Event ANR ANR.EventAnrMo None This parameter

Mode de specifies the policy
based on which the
eNodeB adds a
neighbor relationship
into an NRT in event-
triggered ANR based
on coverage-based
intra- or inter-
frequency handover
measurements and in
event-triggered ANR
based on MLB-based
inter-frequency
measurements. If
adjacent cells of an
eNodeB share PCIs,
you are advised to set
this parameter to
NOT_BASED_NCL to
prevent inappropriate
neighbor relationships
from being added to
NRTs. With this
parameter setting, the
eNodeB does not add
a neighbor
relationship to an NRT
based on the
neighboring cell
information in the
NCL but based on the
reported ECGI.
If the ANR.OptMode
parameter is set to
CONTROLLED and
the
ENodeBAlgoSwitch.E
utranVoipSupportS-
witch parameter is set
to ON, this parameter
must be set to
BASED_NCL.

eRAN

Name
No Handover ANR.NoHoSetMo None To configure

Set Mode de automatic
optimization of
with cells having
abnormal intra-RAT
handover success
rates, set this
parameter to its
recommended value.
Set not ANR.NOHOSetTh None To configure

handover d automatic
attribute optimization of
threshold neighbor relationships
with cells having
abnormal intra-RAT
handover success
rates, set this
parameter to its
recommended value.
A larger value of this
parameter results in a
higher probability of
setting the No
handover indicator
parameter to
FORBID_HO_ENUM.
A smaller value of this
lower probability.
If the
ANR.NoHoSetMode
parameter is set to
PCI_CHECK, it is
recommended that
the threshold
parameter be set to a
value less than 80.

eRAN

Name
Handover ANR.HoSucRateF This parameter specifies the handover

Success Rate orCgiRead success rate threshold for triggering CGI
for CGI reading. If the success rate of handovers to
Reading a neighboring cell is less than or equal to
the parameter value, the eNodeB instructs
UEs to perform CGI reading for automatic
setting the No handover indicator
parameter value for the neighboring cell. A
larger value of this parameter results in a
lower probability of triggering CGI reading
based on the handover success rate.
NCL/NRT Entry Removal


Name
ANR ENodeBAlgoSwit IntraRatEventAnr To enable the

algorithm ch.AnrSwitch Switch following functions,
switch IntraRatAnrAuto- you are advised to
DelSwitch select the
IntraRatEventAnrS-
witch and
IntraRatAnrAuto-
DelSwitch options.
● Removal of
inappropriate
NCL/NRT entries in
intra-RAT ANR
● Specification-based
removal in intra-
RAT ANR
● Removal of
redundant
NCL/NRT entries in
intra-RAT ANR

eRAN

Name
NRT Delete ANR.NrtDelMode EUTRAN_DELCEL ● To enable removal

Mode LERRORNCELL of inappropriate
EUTRAN_DELRED NCL/NRT entries in
UNDANCENCELL intra-RAT ANR, you
are advised to
select the
EUTRAN_DELCELL
ERRORNCELL
option.
● To configure
removal of
redundant
NCL/NRT entries in
intra-RAT ANR, you
are advised to
select the
EUTRAN_DELRED
UNDANCENCELL
option.

eRAN

Name
Handover ANR.NcellHoFor None In specification-based

threshold for NRTDelThd removal:
delete NRT ● If this parameter is
set to a non-zero
value and the
number of
neighbor
relationships in an
NRT has reached
its maximum value,
the eNodeB
determines
whether to remove
a neighbor
relationship with a
neighboring cell
based on the
number of
measurement
reports that include
the neighboring
cell and the
number of
handovers from
the local cell to the
neighboring cell.
When there are
several candidate
neighbor
relationships that
meet certain
conditions, ANR
removes the
lowest-priority
neighbor
relationship. The
priority is
determined by the
number of
handovers.
● If this parameter is
set to 0 and the
number of
neighbor
relationships in an
NRT has reached
its maximum value,
the eNodeB

eRAN

Name
determines
whether to remove
a neighbor
relationship with a
neighboring cell
based on the
number of
measurement
reports that include
the neighboring
cell.
CA Threshold ANR.NcellCaThdF None This parameter

for NRT orNRTDel indicates the
Deletion threshold (expressed
as a number of times
a cell has been
configured as an
SCell) used for
removal when the
number of NRT
entries has reached its
maximum and a new
needs to be added by
ANR.
Neighbor Cell ANR.NcellDelPun None When configuring

Deletion ishPeriod penalty on removed
Punish Period intra-RAT neighbor
relationships, you are
advised to set this
parameter to 10080
in the unit of min.
EUTRAN ANR.EutranNcell None If this parameter is set

Neighbor Cell DelPunNum to 1, the penalty
Deletion function does not take
Punish effect. If this
Number parameter is set to a
value greater than 1,
this function takes
effect.
Set this parameter to
its recommended
value.

eRAN

Name
ANR delete ANR.DelCellThd A larger value of this parameter results in

cell threshold a higher probability of removing neighbor
relationships from NRTs.
Least ANR.NcellHoStat A larger value of this parameter results in

Handover Num more stable neighbor relationships in NRTs
Num for but a longer delay in removing neighbor
Statistic relationships from NRTs.
If only a few UEs are involved in ANR
measurements on the live network, reduce
the value of this parameter to accelerate
NRT updates.
Statistic cycle ANR.StatisticPeri A larger value of this parameter results in

od more accurate neighbor relationships
added to NRTs but a longer delay in
updating NRTs.
Statistic ANR.StatisticNu A larger value of this parameter results in

Number For mForNRTDel a lower probability of removing neighbor
Delete NRT relationships from NRTs.
Statistic Cycle ANR.StatisticPeri A larger value of this parameter results in

For Delete odForNRTDel a lower probability of removing neighbor
NRT relationships from NRTs.
Statistic Cycle ANR.StatPeriodC A larger value of this parameter results in

Coefficient oeff a longer time to remove a redundant
neighbor relationship from the NRT.
Neighbouring NCellParaCfg.Nc This parameter specifies the minimum

Cell Number ellNumForAnr number of intra-RAT neighboring cells on
for ANR EutranInterNFreq a frequency in specification-based removal.
.NcellNumForAnr ● A smaller value results in a smaller
number of neighboring cells on this
frequency.
● A larger value results in a larger
number of neighboring cells on this
frequency.
Fast ANR

eRAN

Name
ANR ENodeBAlgoSwit IntraRatFastAnrS To enable intra-RAT

algorithm ch.AnrSwitch witch fast ANR, you are
switch advised to select the
IntraRatFastAnrS-
witch option.
Fast ANR PCI ANR.FastAnrRprt None If only a few UEs are

report Amount on the network,
amount increase the value of
this parameter.
Otherwise, reduce it.
Fast ANR ANR.FastAnrMon None Set the parameter to

Monitoring itorStatePeriod its recommended
State Period value.
Fast ANR ANR.FastAnrMod None This parameter

Mode e specifies the policy for
adding neighboring
cells by fast ANR.
Currently, fast ANR
adds only the
with the strongest
inter-frequency,
UTRAN, and GERAN
cells to NRTs. It does
not add the neighbor
relationships with the
strongest intra-
frequency cells to
NRTs. The NCL mode
always takes effect for
the detected intra-
frequency cells,
irrespective of the
parameter setting.

Name
Fast ANR PCI ANR.FastAnrRprt If UEs move in the high mobility state,
report interval Interval reduce the value of this parameter.
Otherwise, increase it.

eRAN

Name
Fast ANR ANR.FastAnrChec If only a few UEs are on the network,

checking kPeriod increase the value of this parameter.
period Otherwise, reduce it.
Fast ANR ANR.FastAnrRsrp A larger value of this parameter results in

measurement Thd a higher RSRP requirement and therefore
RSRP higher RSRP of the neighboring cells in the
threshold NCL.
● In densely populated urban areas,
increase the value of this parameter to
reduce the probability of adding
neighboring cells with low RSRP to the
NCL.
● In sparsely populated areas, reduce the
value of this parameter to increase the
probability of adding neighboring cells
with low RSRP to the NCL.
IntraRat Fast ANR.FastAnrIntra A larger value of this parameter results in

ANR RatMeasUeNum more accurate NCL/NRT entry addition but
measurement a greater negative impact on quality of
UE number service and network throughput.
IntraRat Fast ANR.FastAnrIntra A larger value of this parameter results in

ANR valid RatUeNumThd more accurate NCL/NRT entry addition but
measurement a greater negative impact on quality of
min UE service and network throughput.
number
VoIP With GlobalProcSwitc This parameter specifies whether a UE

Gap Mode h.VoipWithGapM running VoIP services can enter gap mode
ode to perform periodic measurements.
If a UE initiates a VoIP service and sets up
QCI-1 bearers after being selected to
perform fast ANR measurements, the
eNodeB takes different actions on the
measurement configuration delivered to
the UE depending on the parameter
settings.
● If this parameter is set to ENABLE, the
eNodeB does not delete the fast-ANR-
related measurement configuration.
● If this parameter is set to DISABLE, the
eNodeB delivers the RRC connection
reconfiguration to the UE and deletes
the fast-ANR-related measurement
configuration.

eRAN
Backward ANR

Name
ANR CellAlgoSwitch.A BACKWARD_ANR To enable intra-RAT

Algorithm nrAlgoSwitch _SW backward ANR, select
Switch the
BACKWARD_ANR_S
W option.
NCL/NRT Self-Management Based on X2 Messages


Name
X2-based GlobalProcSwitc ADD_NCELL_CFG To enable NCL/NRT

Neighboring h.X2BasedUptNc _SW self-management
Cell ellCfgSwitch MOD_NCELL_CFG based on X2
Configuration _SW messages, select the
Update following options:
Switch DEL_NCELL_CFG_
SW ● ADD_NCELL_CFG_
SW
ADD_FREQ_CFG_
SW ● MOD_NCELL_CFG_
SW
● DEL_NCELL_CFG_S
W
● ADD_FREQ_CFG_S
W

eRAN

Name
Update eNB GlobalProcSwitc You are advised to set the FreqAddCtrl

Configuration h.X2BasedUptEN option based on the operator's frequency
Via X2 Policy odeBPolicy configuration policy. If an eNodeB adds
neighboring frequencies based on X2
messages, select this option only if you
intend to enable the eNodeB to filter
frequencies based on operator information.
NRT/NCL Entry Management Based on the eNodeB ID Blacklist


Name
eNodeB ID EnodebIdBlacklis None

t.EnodebId
Blacklists and Whitelist


Name
No handover EutranIntraFreqN ● Set this parameter to

indicator Cell.NoHoFlag FORBID_HO_ENUM when configuring
an HO blacklist.
● Set this parameter to
PERMIT_HO_ENUM when configuring
an HO whitelist.
No remove EutranIntraFreqN Set this parameter to

indicator Cell.NoRmvFlag FORBID_RMV_ENUM when configuring an
HO whitelist or blacklist.

eRAN

Name
No handover EutranInterFreqN ● Set this parameter to

indicator Cell.NoHoFlag FORBID_HO_ENUM when configuring
an HO blacklist.
● Set this parameter to
PERMIT_HO_ENUM when configuring
an HO whitelist.
No remove EutranInterFreqN Set this parameter to

indicator Cell.NoRmvFlag FORBID_RMV_ENUM when configuring an
HO whitelist or blacklist.
Local cell ID IntraFreqBlkCell. None

LocalCellId
Start physical IntraFreqBlkCell. None
cell ID PhyCellId
Local cell ID InterFreqBlkCell. None
LocalCellId
Downlink InterFreqBlkCell. None
EARFCN DlEarfcn
Start physical InterFreqBlkCell. None
cell ID PhyCellId
4.1.4.1.3 Using MML Commands
Activation Command Examples

//Activating frequency-specific ANR
MOD CELL: LocalCellId=xx, IntraFreqAnrInd=ALLOWED;
MOD EUTRANINTERNFREQ: LocalCellId=xx, DlEarfcn=xx, AnrInd=ALLOWED;
//Activating neighbor relationship addition in intra-RAT event-triggered ANR

MOD ENODEBALGOSWITCH: AnrSwitch=IntraRatEventAnrSwitch-1;
MOD CELLALGOSWITCH: LocalCellId=xx, AnrFunctionSwitch=INTRA_RAT_ANR_SW-1;
MOD ENODEBALGOSWITCH:
AnrSwitch=MlbBasedEventAnrSwitch-1&ServiceBasedEventAnrSwitch-1&ServiceReqEventAnrSwitch-1&IntraR
atEnhancedEventAnrSwitch-1&InterFreqAngcAnrSwitch-1&CaBasedEventAnrSwitch-1;
//(Optional) Configuring event-triggered ANR
MOD ANR: EventAnrMode=NOT_BASED_NCL;
//Activating specification-based removal in intra-RAT ANR under the condition that intra-RAT event-
triggered ANR is activated
MOD ENODEBALGOSWITCH: AnrSwitch=IntraRatAnrAutoDelSwitch-1;
MOD ANR: NcellHoForNRTDelThd=xx;
//Activating removal of inappropriate NCL/NRT entries in intra-RAT ANR

MOD ANR: NrtDelMode=EUTRAN_DELCELLERRORNCELL-1;
//Activating removal of redundant NCL/NRT entries in intra-RAT ANR

MOD ANR: NrtDelMode=EUTRAN_DELREDUNDANCENCELL-1;
//Activating penalty on removed neighbor relationships with E-UTRAN cells

eRAN
MOD ANR: NcellDelPunishPeriod=xx, EutranNcellDelPunNum=xx;
//Activating intra-RAT fast ANR

MOD ENODEBALGOSWITCH: AnrSwitch=IntraRatFastAnrSwitch-1;
MOD ANR: FastAnrRprtAmount=r4;
MOD ANR: FastAnrMonitorStatePeriod=xx;
//Activating intra-RAT backward ANR

MOD CELLALGOSWITCH: LocalCellId=xx,AnrAlgoSwitch=BACKWARD_ANR_SW-1;
//Activating automatic optimization of neighbor relationships with cells having abnormal intra-RAT
handover success rates
MOD ENODEBALGOSWITCH: AnrSwitch=IntraRatNoHoSetAnrSwitch-1;
//(Optional) Configuring the NoHoSetMode and NoHoSetThd parameters
MOD ANR: NoHoSetMode=PCI_CHECK;
MOD ANR: NoHoSetThd=0;
//Activating NCL/NRT self-management based on X2 messages

MOD GLOBALPROCSWITCH:
X2BasedUptNcellCfgSwitch=ADD_NCELL_CFG_SW-1&MOD_NCELL_CFG_SW-1&DEL_NCELL_CFG_SW-1&ADD
_FREQ_CFG_SW-1;
//Configuring the eNodeB ID blacklist

ADD ENODEBIDBLACKLIST: EnodebId=400013;
//Configuring HO blacklists and HO whitelists

ADD EUTRANINTRAFREQNCELL: LocalCellId=0, Mcc="460", Mnc="00", eNodeBId=123, CellId=0,
NoHoFlag=FORBID_HO_ENUM, NoRmvFlag=FORBID_RMV_ENUM;
ADD EUTRANINTRAFREQNCELL: LocalCellId=0, Mcc="460", Mnc="00", eNodeBId=123, CellId=0,
NoHoFlag=PERMIT_HO_ENUM, NoRmvFlag=FORBID_RMV_ENUM;
ADD EUTRANINTERFREQNCELL: LocalCellId=0, Mcc="460", Mnc="00", eNodeBId=123, CellId=0,
ADD EUTRANINTERFREQNCELL: LocalCellId=0, Mcc="460", Mnc="00", eNodeBId=123, CellId=0,
//Configuring RRC blacklists

ADD INTRAFREQBLKCELL: LocalCellId=0, PhyCellId=1, PhyCellIdRange=n4;
ADD INTERFREQBLKCELL: LocalCellId=0, DlEarfcn=0, PhyCellId=1, PhyCellIdRange=n4;
//Configuring CGI reading using autonomous gaps

MOD CELLALGOSWITCH: LocalCellId=xx, AnrAlgoSwitch=LTE_AUTON_GAP_CGI_SW-1;
Optimization Command Examples

Optimize parameters related to intra-RAT ANR according to the setting notes in
4.1.4.1.2 Data Preparation.
Deactivation Command Examples

//Deactivating frequency-specific ANR
MOD CELL: LocalCellId=xx, IntraFreqAnrInd=NOT_ALLOWED;
MOD EUTRANINTERNFREQ: LocalCellId=xx, DlEarfcn=xx, AnrInd=NOT_ALLOWED;
//Deactivating neighbor relationship addition in intra-RAT event-triggered ANR

MOD ENODEBALGOSWITCH: AnrSwitch=IntraRatEventAnrSwitch-0;
AnrSwitch=MlbBasedEventAnrSwitch-0&ServiceBasedEventAnrSwitch-0&IntraRatEnhancedEventAnrSwitch-0
&ServiceReqEventAnrSwitch-0&InterFreqAngcAnrSwitch-0&CaBasedEventAnrSwitch-0;
//Deactivating removal of inappropriate NCL/NRT entries and specification-based removal in intra-RAT ANR
MOD ENODEBALGOSWITCH: AnrSwitch=IntraRatAnrAutoDelSwitch-0;
//Deactivating removal of redundant NCL/NRT entries in intra-RAT ANR

MOD ANR: NrtDelMode=EUTRAN_DELREDUNDANCENCELL-0;

eRAN
//Deactivating penalty on removed neighbor relationships with E-UTRAN cells

MOD ANR: EutranNcellDelPunNum=1;
//Deactivating intra-RAT fast ANR

MOD ENODEBALGOSWITCH: AnrSwitch=IntraRatFastAnrSwitch-0;
//Deactivating intra-RAT backward ANR

MOD CELLALGOSWITCH: LocalCellId=xx,AnrAlgoSwitch=BACKWARD_ANR_SW-0;
//Deactivating automatic optimization of neighbor relationships with cells having abnormal intra-RAT
handover success rates
MOD ENODEBALGOSWITCH: AnrSwitch=IntraRatNoHoSetAnrSwitch-0;
//Deactivating NCL/NRT self-management based on X2 messages

MOD GLOBALPROCSWITCH:
X2BasedUptNcellCfgSwitch=ADD_NCELL_CFG_SW-0&MOD_NCELL_CFG_SW-0&DEL_NCELL_CFG_SW-0&ADD
_FREQ_CFG_SW-0;
//Removing an eNodeB ID blacklist

RMV ENODEBIDBLACKLIST: EnodebId=400013;
//Disabling CGI reading using autonomous gaps

4.1.4.1.4 Using the CME

For detailed operations, see CME-based Feature Configuration.
4.1.4.2 Activation Verification
Addition and Removal of Intra-RAT NRT Entries

● Signaling tracing
To use signaling tracing to verify whether intra-RAT ANR has taken effect,
perform the following steps:
Step 1 On the U2020 client, choose Monitor > Signaling Trace > Signaling Trace
Management.
Step 2 In the navigation tree on the left of the Signaling Trace Management tab page,
double-click Uu Interface Trace under LTE > Application Layer.
Step 3 Create and start a Uu interface tracing task.
Step 4 Remove some neighbor relationships so that there are missing neighboring cells in
the network. If a UE reports an ECGI during an intra-RAT handover to a missing
neighboring cell as indicated in a traced message, intra-RAT ANR has taken effect.
Figure 4-12 shows an example of the tracing result.

eRAN
Figure 4-12 Uu tracing result for intra-RAT ANR observation
Step 5 Check whether intra-RAT backward ANR takes effect.
After the ECGI reading result is reported and the neighbor relationship of the
source cell (cell A) with the target cell (cell B) is added in Step 4, cell A initiates
an X2- or S1-based handover to cell B. After the handover completes, check the
neighboring cell configuration in cell B. If the neighbor relationship of cell B with
cell A is added, backward ANR has taken effect.
----End
● SON logs on the U2020 client

To use SON logs to verify whether this function has taken effect, perform the
following steps:
Step 1 (Optional) Deliver optimization advice. This step is required when the
Optimization Mode parameter is set to CONTROLLED. The advice selection
operation varies depending on the advice type:
● Optimization advice of adding or removing neighbor relationships: On the
U2020 client, choose SON > LTE ANR. In the Neighboring Cell Relationship
to Be Handled pane of the Neighboring Cell Management tab page, select
the optimization advice to be delivered.
● Optimization advice on blind handover priorities: On the U2020 client, choose
SON > LTE Blind Neighboring Cell Optimization. On the Parameter
Optimization Advice tab page, select the optimization advice to be delivered.
Step 2 On the U2020 client, choose SON > SON Log.
Step 3 On the Query SON Log tab page, click LTE ANR Log in the Log Category drop-
down list in the upper left corner.
Step 4 In the Event Name area, select items such as Set ANR Switch, Add Neighboring
Cell, Delete Neighboring Cell, Add External Cell, Delete External Cell, SET
handover Blacklist & Whitelist, and Automatically Disable Handover one at a
time to check different types of ANR operations.
----End

eRAN
NOTE
If there are several SON-related operations at the same time and one of the operations is
incorrectly executed, all SON-related operations are rolled back. In this situation, only one
error code is displayed in the SON log, and other failed operations have the same error
code.
● LTE ANR management on the U2020 client

To use the LTE ANR management function to view configured neighbor
relationships, perform the following steps:
Step 1 On the U2020 client, choose SON > LTE ANR.
Step 2 In the Neighboring Cell area on the Neighboring Cell Management tab page,
check all neighbor relationships of the specific source cell. The Creation Mode
attribute indicates whether a neighbor relationship is added by ANR. NON-ANR
indicates that the neighbor relationship is not added by ANR. ANR indicates that
the neighbor relationship is added by ANR. This function can be used to view all
configured neighbor relationships, even if the ANR feature is disabled.
----End
● MML commands
To use MML commands to verify whether intra-RAT ANR has taken effect,
Step 1 Run the LST EUTRANINTRAFREQNCELL and LST EUTRANINTERFREQNCELL

commands to list the configurations of neighbor relationships with intra- and
inter-frequency E-UTRAN cells, respectively.
Step 2 In the command output, check the value of the ANR flag parameter.
● If the value is True, the intra-RAT neighbor relationship is automatically
configured by ANR.
● If the value is False, the intra-RAT neighbor relationship is manually
configured.
----End
Automatic Optimization of Neighbor Relationships with Cells Having

Abnormal Intra-RAT Handover Success Rates
following steps:
Step 3 In the Event Name area, select the item Automatically Disable Handover to
check whether this function takes effect.
----End

eRAN
NCL/NRT Self-Management Based on X2 Messages

To check whether NCL/NRT self-management based on X2 messages has taken
effect, perform the following steps:
Step 1 Log in to the U2020 client, and choose Monitor > Signaling Trace > Signaling
Trace Management.
double-click X2 Interface Trace under LTE > Application Layer.
Step 3 Create and start an X2 interface tracing task.
Step 4 Check the tracing result.
If the X2_SETUP_REQUEST message (as shown in Figure 4-13) or
ENB_CONFIGURATION_UPDATE message (as shown in Figure 4-14) indicates that
the local eNodeB sends its configurations to the peer eNodeB, which then updates
the configuration based on the messages, this function has taken effect.
Figure 4-13 Example of X2_SETUP_REQUEST message
Figure 4-14 Example 1 of ENB_CONFIGURATION_UPDATE message
If the ENB_CONFIGURATION_UPDATE message (as shown in Figure 4-15)

contains the IE Served Cell to Delete, the peer eNodeB removes the neighbor

eRAN
relationships with the removed cells. The NCL/NRT entry removal function has
taken effect.
Figure 4-15 Example 2 of ENB_CONFIGURATION_UPDATE message
----End
eNodeB ID Blacklist
To use MML commands to verify whether the eNodeB ID blacklist configuration
has taken effect, perform the following steps:
Step 1 Run the LST ENODEBIDBLACKLIST command to view the eNodeB ID blacklist.
Step 2 Run the LST EUTRANINTRAFREQNCELL or LST EUTRANINTERFREQNCELL

command to check whether ANR adds neighbor relationships with cells of the
corresponding eNodeB IDs to the NRTs.
ANR does not add cells having blacklisted eNodeB IDs to the NRTs.
----End
HO Blacklist and HO Whitelist

To use SON logs to verify whether the functions have taken effect, perform the
following steps:
Step 3 In the Event Name area, select the item SET handover Blacklist & Whitelist to
check the ANR operation of configuring HO blacklists and whitelists.
Step 4 The HO blacklist function takes effect if the cells in the blacklist can be detected
by UEs, no handovers to these cells are performed, and configuration data shows
that the neighbor relationships with these cells cannot be removed automatically.
The HO whitelist function takes effect if the cells in the whitelist can be detected
by UEs, handovers to these cells can be performed, and configuration data shows
that the neighbor relationships with these cells cannot be removed automatically.
----End

eRAN
NOTE
The SON logs under the item SET handover Blacklist & Whitelist record the modification of
No remove indicator and No handover indicator by operators.
RRC Blacklist
To use signaling tracing to verify whether this function has taken effect, perform
the following steps:
Step 1 Log in to the U2020 client, and choose Monitor > Signaling Trace > Signaling
Trace Management.
choose LTE > Application Layer > Uu Interface Trace.
Step 4 Check the tracing result.
The RRC blacklist is included in the SIB4, SIB5, and measurement objects. If the Uu
messages include the RRC blacklist, this function has taken effect.
----End
4.1.4.3 Network Monitoring

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.
The handover performance counters listed in Table 4-22 can reflect the network
performance after intra-RAT ANR is enabled. As intra-RAT neighbor relationships
are configured, the values of these counters decrease.
Table 4-22 Counters related to intra-RAT ANR

1526728398 L.IntraFreqHO.NoNRT
1526728399 L.InterFreqHO.NoNRT
1526741657 L.IntraRat.CgiReadAtt
1526741658 L.IntraRat.CgiReadSucc
1526747658 L.IntraFreqHO.DelPunish
1526747659 L.InterFreqHO.DelPunish
NCL/NRT self-management based on X2 messages decreases the probability of

missing or incorrect neighbor relationship configurations. This increases the
handover success rate and decreases the service drop rate. To monitor the self-

eRAN
management performance, check the performance counters related to handovers

and service drops.
Collect the performance counters related to the intra-frequency handover success
rate, inter-frequency handover success rate, and E-RAB, listed in the table below.
Then, use the following formula to calculate the service drop rate:
Service Drop Rate = L.E-RAB.AbnormRel/(L.E-RAB.NormRel + L.E-RAB.AbnormRel)
x 100%
1526726995 L.HHO.IntraeNB.IntraFreq.PrepAttOut
1526726996 L.HHO.IntraeNB.IntraFreq.ExecAttOut
1526726997 L.HHO.IntraeNB.IntraFreq.ExecSuccOut
1526727001 L.HHO.IntereNB.IntraFreq.PrepAttOut
1526727002 L.HHO.IntereNB.IntraFreq.ExecAttOut
1526727003 L.HHO.IntereNB.IntraFreq.ExecSuccOut
1526726998 L.HHO.IntraeNB.InterFreq.PrepAttOut
1526726999 L.HHO.IntraeNB.InterFreq.ExecAttOut
1526727000 L.HHO.IntraeNB.InterFreq.ExecSuccOut
1526727004 L.HHO.IntereNB.InterFreq.PrepAttOut
1526727005 L.HHO.IntereNB.InterFreq.ExecAttOut
1526727006 L.HHO.IntereNB.InterFreq.ExecSuccOut
1526727546 L.E-RAB.AbnormRel
1526727547 L.E-RAB.NormRel
4.1.4.4 Possible Issues
Fault Description 1
An intra- or inter-frequency handover fails.
Fault Handling 1
To check whether this handover failure is caused by an incorrect neighbor
relationship configuration, perform the following steps:
Step 1 On the U2020 client, start a Uu interface tracing task for the source cell.
Choose Monitor > Signaling Trace > Signaling Trace Management. In the
navigation tree on the left of the Signaling Trace Management tab page, double-
click Uu Interface Trace under LTE > Application Layer. Create and start a Uu
interface tracing task.

eRAN
Step 2 In the tracing result, check whether the source eNodeB has delivered a handover
command. A handover command was delivered if the RRC_CONN_RECFG message
contains the IE mobilityControlInfo.
● If the eNodeB has not delivered the handover command, go to Step 3.
● If the eNodeB has delivered the handover command, contact Huawei
technical support.
Step 3 Run the LST EUTRANEXTERNALCELL command to check whether the target cell
has been configured as an external cell on the source eNodeB. Run the LST
EUTRANINTRAFREQNCELL or LST EUTRANINTERFREQNCELL command to
check whether the intra- or inter-frequency neighbor relationship between the
source and target cells has been configured on the source cell.
● If they have not been configured, go to Step 4.
● If they have been configured, contact Huawei technical support.
NOTE
In RAN sharing with common carrier mode, if the UE subscribes to a secondary

operator, query the EutranExternalCellPlmn MO to check whether the PLMN list has
been configured. Configure the PLMN list if it has not been configured.
Step 4 Check whether the switch for intra-RAT event-triggered ANR has been set to on.
● If the switch is off, set it to on.
● If the switch is on, go to Step 5.
Step 5 Check whether the UE supports intra-RAT ANR. For details, see 3.2.4
Requirements of UEs for ANR.
● If the UE supports this function, contact Huawei technical support.
● If the UE does not support this function, no further action is required.
----End
Fault Description 2
When an E-UTRAN cell is shared by operators, a UE that subscribes to a secondary
operator experiences a failure of an intra-RAT handover to the cell.
Fault Handling 2
1. Choose Monitor > Signaling Trace > Signaling Trace Management.
2. In the navigation tree on the left of the Signaling Trace Management tab
page, double-click Uu Interface Trace under LTE > Application Layer. Create
and start a Uu interface tracing task.
Step 2 In the tracing result, check whether the source eNodeB has delivered a handover
command. A handover command was delivered if the RRC_CONN_RECFG message
contains the IE mobilityControlInfo.

eRAN

technical support.
Step 3 Run the LST EUTRANEXTERNALCELL command to check whether the target cell
EUTRANINTRAFREQNCELL or LST EUTRANINTERFREQNCELL command to
check whether the intra- or inter-frequency neighbor relationship between the
source and target cells has been configured on the source cell. Run the LST
EUTRANEXTERNALCELLPLMN command to check whether the PLMN list has
been configured for the external cell.
Step 4 Check whether the source and target eNodeBs are managed by the same U2020.
● If they are, go to Step 5.
● If they are not, contact Huawei technical support.
Step 5 Check whether the switch for intra-RAT event-triggered ANR and the switch for
ANR with shared cells have been set to on.
● If the switches are off, set them to on.
Step 6 Check whether the UE supports intra-RAT ANR.

----End
Fault Description 3
NCL/NRT entries cannot be added, updated, or removed based on X2 messages.
Fault Handling 3
To handle the fault, perform the following steps:
Step 1 Run the LST GLOBALPROCSWITCH command to check the switch settings.
If NCL/NRT entries cannot be added or updated, check the setting of the Update
eNB Configuration Via X2 Switch parameter.
If NCL/NRT entries cannot be removed, check the settings of the Update eNB
Configuration Via X2 Switch and Delete Ncell Configuration Via X2 Switch
parameters.
● If a value is Off, set the parameter to ON.

● If the values are On, go to Step 2.
Management. In the navigation tree on the left of the Signaling Trace
Management tab page, double-click X2 Interface Trace under LTE > Application
Layer. Create and start an X2 interface tracing task for the source cell.

eRAN
Step 3 Modify or remove the configuration of a cell served by an eNodeB. Check the
tracing result to determine whether the eNodeB has sent an ENB
CONFIGURATION UPDATE message to inform the peer eNodeB of the change.
● If the eNodeB has sent the message, contact Huawei technical support.
● If the eNodeB did not send the message, go to Step 4.
Step 4 Run the DSP X2INTERFACE command to check whether the X2 interface is
configured and works normally.
● If the X2 interface is normal, contact Huawei technical support.
● If the X2 interface is abnormal, see S1 and X2 Self-Management for details
about how to handle the fault.
----End
Fault Description 4
The result of the LST EUTRANINTRAFREQNCELL or LST
EUTRANINTERFREQNCELL command shows configured neighbor relationships.
However, the result of the DSP EUTRANINTRAFREQNCELL or DSP
EUTRANINTERFREQNCELL command does not show any configured neighbor
relationship.
Fault Handling 4
Perform the following steps for troubleshooting:
command to check the Neighbor Cell Classification Label parameter value.
Step 2 If the Neighbor Cell Classification Label parameter value for a neighboring cell
in the result is EXTENDED, set the Neighbor Cell Classification Flag parameter
to EXTENDED or ALL when running the DSP EUTRANINTRAFREQNCELL
command to query the information of the neighboring cell. If the Neighbor Cell
Classification Label parameter value for a neighboring cell in the result is
FORMAL, set the Neighbor Cell Classification Flag parameter to FORMAL or
ALL when running the DSP EUTRANINTRAFREQNCELL command to query the
information of the neighboring cell.
Run the DSP EUTRANINTRAFREQNCELL or DSP EUTRANINTERFREQNCELL
command, the information of neighboring cells for which the Neighbor Cell
Classification Label parameter is set to FORMAL is displayed, by default.
----End
Fault Description 5
There is a neighbor relationship with a cell of an invalid PLMN in an intra-RAT
NRT, causing handover failures.
Fault Handling 5
Step 1 Check the SON logs to verify whether such a neighbor relationship is added by
ANR. If yes, UEs report the invalid PLMN.

eRAN
Step 2 Set the Plmn List Type parameter in the NCellPlmnList MO to BLACK_LIST for
the PLMN.
Step 3 Manually remove such a neighbor relationship from the NRT or use the ANR
function to remove it.
----End
Fault Description 6
A handover from a regular cell to a specified-PCI cell fails.
Fault Handling 6
On the U2020 client, choose Monitor > Signaling Trace > Signaling Trace
Management. In the navigation tree on the left of the Signaling Trace
Management tab page, choose LTE > Application Layer > Uu Interface Trace to
create and start a Uu interface tracing task.
Step 2 Check whether the source cell sends the RRC_CONN_RECFG message to instruct
the UE to perform ECGI reading.
● If no, go to Step 3.
● If yes, contact Huawei technical support.
Step 3 Run the LST EUTRANSPEPCICELL command to check whether the specified PCI
group is configured and whether the PCI of the target cell is in the PCI group.
● If the PCI of the target cell is in the specified PCI group, go to Step 4.
● If the specified PCI group is not configured, configure the specified PCI group
by following the steps in 4.1.4.1 Data Configuration.
Step 4 Check whether the IntraRatEventAnrSwitch option of the ANR algorithm switch
parameter and the IntraAnrPolicySwitch option of the
CellAlgoSwitch.SpePCIBasedPolicySw parameter are selected.
● If either of the two options is not selected, select the option.
● If both options are selected, go to Step 5.
Step 5 Check whether the UE supports intra-RAT ANR.
----End
4.2 Intra-RAT Neighbor Relationship Classification
4.2.1 Principles
The intra-RAT neighbor relationship classification function classifies intra-RAT
neighbor relationships based on the handover statistics and provides differentiated

eRAN
management of the neighbor relationships based on the classification, improving

O&M experience.
4.2.1.1 Neighbor Relationship Classification

Intra-RAT neighbor relationship classification is controlled by the
INTRA_RAT_NCELL_CLASS_SW option of the CellAlgoSwitch.NCellClassMgtSw
parameter. This function requires that event-triggered ANR or fast ANR be
enabled.
Intra-RAT neighbor relationships can be formal neighbor relationships or extended
neighbor relationships, as shown in Table 4-23. When ANR is enabled, the source
cell starts a measurement period specified by the
NCellClassMgt.StatPeriodForNCellClass parameter.
Table 4-23 Formal and extended neighbor relationships

Neighbor Formal Neighbor Relationship Extended Neighbor
Relations Relationship
hip Type
Required If either of the following conditions are If both of the following

Conditio met within a measurement period, the conditions are met within
n eNodeB sets the Neighbor Cell four consecutive
Classification Flag parametera to measurement periods, the
FORMAL for a neighbor relationship: eNodeB sets the
● The number of handover attempts Neighbor Cell
from the local cell to a neighboring Classification Flag
cell is greater than or equal to the parametera to EXTENDED
NCellClassMgt.HoAttemptThd for a neighbor
parameter value, and the number relationship:
of successful handovers is greater ● The number of
than or equal to the handover attempts
NCellClassMgt.HoSuccThd from the local cell to a
parameter value. neighboring cell is less
● The number of times the than the
neighboring cell is successfully NCellClassMgt.HoAtte
configured as an SCell for CA UEs is mptThd parameter
greater than or equal to the value, or the number of
NCellClassMgt.CaSCellCfgThd successful handovers is
parameter value. less than the
NCellClassMgt.HoSucc
Thd parameter value.
● The number of times
the neighboring cell is
successfully configured
as an SCell for CA UEs
is less than the
NCellClassMgt.CaSCel
lCfgThd parameter
value.

eRAN
Descripti In the following scenarios, the None

on Neighbor Cell Classification Label
parameter is automatically set to
FORMAL and this parameter cannot
be set to EXTENDED for a neighbor
relationship:
● The EutranIntraFreqN-
Cell.AttachCellSwitch parameter is
set to ON for intra-RAT intra-
frequency neighbor relationships.
● Any of the following conditions is
met for intra-RAT inter-frequency
neighbor relationships:
– The EutranInterFreqN-
Cell.BlindHoPriority parameter
is not set to 0.
– The EutranInterFreqN-
Cell.OverlapInd parameter is set
to YES.
– The
CaGroupSCellCfg.SCellBlindCfg
Flag parameter is set to TRUE.
● The Control Mode parameter is set
to MANUAL_MODE.
a: The Neighbor Cell Classification Flag parameter refers to

EutranIntraFreqNCell.NCellClassLabel for an intra-frequency neighbor
relationship and EutranInterFreqNCell.NCellClassLabel for an inter-frequency
neighbor relationship.
Extended neighbor relationships can be stored in the configuration database or

eNodeB memory. The storage place can be changed, as shown in Table 4-24.
Table 4-24 Storage of extended neighbor relationships
Storage Configuration Database eNodeB Memory

Place
Required ● If the If the

Conditio NCellClassMgt.IntraRatNcellMgt- NCellClassMgt.IntraRatN
n Mode parameter is set to cellMgtMode parameter
CONFIGURATION_MODE, the is set to
extended neighbor relationships are INTERNAL_STORAGE_MO
stored in the configuration DE, the extended neighbor
database. relationships are stored in
● The No remove indicator the eNodeB memory.
parameter is set to
FORBID_RMV_ENUM.

eRAN
Change When the value of the If a certain condition is

of NCellClassMgt.IntraRatNcellMgt- meta and the
Storage Mode parameter is changed from EXTENDED_NCELL_MNG_
Places CONFIGURATION_MODE to SW option of the
INTERNAL_STORAGE_MODE, the CellAlgoSwitch.NCellClas
eNodeB moves the extended neighbor sMgtSw parameter is
relationships in the configuration selected, the eNodeB
database to the eNodeB memory at writes extended neighbor
the end of a measurement period relationships stored in the
specified by the memory into the
NCellClassMgt.StatPeriodForNCell- configuration database.
Class parameter.
Descripti If an unknown or formal neighbor If the
on relationship is changed to an extended EXTENDED_NCELL_MNG_
neighbor relationship, the eNodeB SW option of the
changes the value of the Neighbor CellAlgoSwitch.NCellClas
Cell Classification Label parameter sMgtSw parameter is
for this neighbor relationship in the deselected, the eNodeB
configuration database. If neighbor removes the extended
relationship classification does not neighbor relationships
take effect, the existing parameter from the memory.
value will not change.
a: One of the following conditions is met:

● The value of the NCellClassMgt.IntraRatNcellMgtMode parameter is
changed from INTERNAL_STORAGE_MODE to CONFIGURATION_MODE.
● The ANR.OptMode parameter is set to CONTROLLED and the
NCellParaCfg.CellAnrOptMode parameter is set to CONTROLLED.
● The IntraRatEventAnrSwitch and IntraRatFastAnrSwitch options of the
ENodeBAlgoSwitch.AnrSwitch parameter are deselected.
● The INTRA_RAT_NCELL_CLASS_SW option of the
CellAlgoSwitch.NCellClassMgtSw parameter is deselected.
● The INTRA_RAT_ANR_SW option of the CellAlgoSwitch.AnrFunctionSwitch
parameter is deselected.
● The corresponding frequency-specific ANR indicator is set to NOT_ALLOWED.

eRAN
NOTE
The value range of the NCellClassMgt.StatPeriodForNCellClass parameter is 1 to 50400.

Set this parameter based on the traffic fluctuation of the network. If the traffic volume of
the local cell fluctuates greatly, set this parameter to a large value, for example, 10080
(one week). If the traffic volume of the local cell does not fluctuate greatly, the default
value (for example, 1440) is recommended.
If the NRT optimization mode works in controlled mode, the unknown neighbor
relationships to be added or removed will be reported to the U2020 for manual
confirmation. In this case, neighbor relationship classification will not be performed. In
other words, when the ANR.OptMode parameter is set to CONTROLLED and the
NCellParaCfg.CellAnrOptMode parameter is set to CONTROLLED, neighbor relationship
classification does not take effect.
Moving extended neighbor relationships from the memory to the configuration database
prevents neighbor relationship loss and consequent KPI fluctuations after an upgrade. This
operation will increase CPU usage and system load within a short period of time. You are
advised to perform this operation during off-peak hours. This function provides best effort
protection. If CPU flow control is implemented or the number of neighbor relationships in
the configuration database has reached its maximum, the eNodeB directly removes the
excessive extended neighbor relationships.
4.2.1.2 Blacklisted Neighbor Relationship Management

ANR automatically detects the over-distant neighboring cells in the NRTs and adds
them to the BT list. An over-distant neighboring cell is a neighboring cell far away
from a local cell. The U2020 regards an over-distant cell as an overshooting cell.
This function prevents over-distant neighboring cells from being added to the NRT,
improving neighbor relationship management efficiency.
For formal neighbor relationships, the blacklisted neighbor relationship
management function manages the E-UTRAN neighbor relationship blacklist
(specified by the EutranBlkNCell MO). For extended neighbor relationships, this
function manages the E-UTRAN neighbor relationship blacklist, or the over
distance flags and no handover indicators.
Table 4-25 Blacklisted neighbor relationship management
Function Name Application Prerequisite Parameter

Scenario
Blacklisted Intra-RAT event- ● The intra-RAT INTRA_RAT_OVE

neighbor triggered ANR or neighbor RDISTANCE_SW
relationship fast ANR relationship option of the
management classification CellAlgoSwitch.A
function is nrAlgoSwitch
enabled. parameter
● The intra-RAT
neighbor
relationship
classification
function is in
eNodeB
memory mode.

eRAN
Topology-based Management
This function performs topology check for neighbor relationships reported to the
U2020 and handles them accordingly at the end of a measurement period
specified by the NCellClassMgt.StatPeriodForNCellClass parameter.
If the check result meets all specified conditions, the eNodeB adds formal
neighbor relationships to the neighboring E-UTRAN cell blacklist (specified by the
EutranBlkNCell MO) or sets the Over Distance Flag parameter to
BOOLEAN_TRUE and the No handover indicator parameter to
FORBID_HO_ENUM for extended neighbor relationships.
If the check result does not meet all specified conditions, the eNodeB removes
formal neighbor relationships from the neighboring E-UTRAN cell blacklist
(specified by the EutranBlkNCell MO) or sets the Over Distance Flag parameter
to BOOLEAN_FALSE for extended neighbor relationships.
● The conditions for neighbor relationships without any special indicators are as
follows:
– The blind-handover priority is set to 0.
– The Overlap Indicator parameter is set to NO.
– The Control Mode parameter is set to AUTO_MODE.
– The No remove indicator parameter is set to PERMIT_RMV_ENUM.
– The Attach Cell Switch parameter is set to OFF.
– This neighboring cell is not one of the neighboring cells of a single
frequency network (SFN) cell specified by the SfnEdgeRruRelation MO.
– The CaGroupSCellCfg.SCellBlindCfgFlag parameter is set to FALSE or
this neighboring cell is not a candidate SCell specified by the
CaGroupSCellCfg MO.
● The number of handover attempts is less than the value of the
NCellParaCfg.HoStatThd parameter or the handover success rate is less than
the value of the NCellParaCfg.HoSuccThd parameter within each of four
consecutive measurement periods specified by the
NCellClassMgt.StatPeriodForNCellClass parameter.
● The U2020 obtains the latitude and longitude information from the eNodeB
configurations or the engineering parameters on the CME. Then, the U2020
calculates the distances between the serving cell and its neighboring cell to
determine whether the neighboring cell is an over-distant neighboring cell.
– When the NCellParaCfg.NCellOdDisThd parameter is set to a non-zero
value (a value twice greater than the Cell.CellRadius parameter value is
recommended), a neighboring cell is determined as an over-distant
neighboring cell if the distance between the serving cell and the
neighboring cell is greater than this threshold.
NOTE
It is recommended that the NCellParaCfg.NCellOdDisThd parameter be set to

1000 in a pole site scenario. For macro base stations, set this parameter based on
the average actual coverage radius. For details about the configuration principles,
contact Huawei engineers.
– When the NCellParaCfg.NCellOdDisThd parameter is set to 0, a
neighboring cell is determined as an over-distant neighboring cell if the

eRAN
distance between the serving cell and the neighboring cell is greater than
the sum of the actual access radii of the two cells. The eNodeB can
detect over-distant neighboring cells served only by Huawei eNodeBs.
(The actual access radius indicates the maximum distance between a UE
and an eNodeB in case that the UE can access the eNodeB.)
NOTE
To check blacklisted neighbor relationships, log in to the U2020 client and choose SON >
LTE Neighbouring Cell Blacklist Management.
Different from blacklisted neighbor relationship management, the U2020 supports
abnormal coverage evaluation of neighboring cells based on topology and only presents the
evaluation result. To view neighboring cells with abnormal coverage, log in to the U2020
client and choose SON > LTE ANR. On the Neighboring Cell Management tab page, view
the neighboring cells in the Query Cross-Coverage Cell pane.
Statistics-based Management
This function calculates the number of times a neighboring cell is included in a
measurement report for all neighbor relationships (including blacklisted neighbor
relationships). At the end of a measurement period specified by the
NCellClassMgt.StatPeriodForNCellClass parameter, the eNodeB adds neighbor
relationships that meet the following conditions to the neighboring E-UTRAN cell
blacklist (specified by the EutranBlkNCell MO):
● The neighbor relationship is an extended neighbor relationship.
● The Neighbor Cell Plmn Label parameter is set to GREY.
● The number of CGI reading times is greater than the
NCellClassMgt.HoAttemptThd parameter value.
If an extended neighbor relationship for which the Over Distance Flag parameter
is BOOLEAN_TRUE or a blacklisted neighbor relationship meets the following
conditions, this neighbor relationship will be removed.
● The measurement decrease rate is greater than 80% or the neighboring cell is
never included in any measurement reports within each of four consecutive
measurement periods. The decrease rate is calculated using the following
formula: (A – B)/A
where,
A denotes the maximum number of times the neighboring cell is included in
measurement reports with any previous period.
B denotes the number of times the neighboring cell is included in
measurement reports in the current measurement period.
● The Control Mode for the blacklisted neighbor relationship is set to
AUTO_MODE.

eRAN
NOTE
● The calculation of the access radius is based on the parameters Cell.CellRadius,

Cell.HighSpeedFlag, and Cell.PreambleFmt. For details, see descriptions about the
random access procedure in 3GPP TS 36.211 V12.0.0.
● The topology-based blacklisted neighbor relationship management function checks each
neighboring cell only once to prevent frequent invalid queries. If engineering parameters
or thresholds of a cell are changed, you are advised to restart the blacklisted neighbor
relationship management function.
● If a multi-RRU cell or SFN cell has multiple latitudes and longitudes, the minimum
distance is used for determination.
Detection of a New Neighboring Cell Whose PCI Is the Same as That of an

Over-Distant Neighboring Cell
If the PCIs contained in the intra-RAT handover measurement reports sent by UEs
are the same as those of the extended neighboring cells that meet any of the
following conditions, then from the time specified by ANR.StartTime to the time
specified by ANR.StopTime, the eNodeB instructs UEs to perform CGI reading. If a
new neighboring cell is detected, the eNodeB adds the detected cell to the NCL
and the neighbor relationship with this cell to the NRT.
● The No handover indicator parameter for the extended neighboring cell is
set to FORBID_HO_ENUM.
● The Neighbor Cell Plmn Label parameter for the extended neighboring cell
is set to GREY.
Controlled-Mode-based Neighboring Cell Distance Check

In controlled mode, when a UE reports unknown neighboring cells, the eNodeB
reports the optimization advice on the neighbor relationships to the U2020, and
operators determine whether to take the advice on the U2020.
NOTE
For details about controlled mode, see 4.1.1.1.2 NRT Optimization Mode.
If the Overshooting Check parameter is set to ON on the U2020, the U2020

automatically performs overshooting check for neighboring cells which are
included in the NRT optimization advice on adding neighbor relationships. For
details about the policy and thresholds for overshooting check, see Topology-
based Management. However, the difference between the two functions is that in
controlled-mode-based neighboring cell distance check, the U2020 obtains the
information about latitudes and longitudes from the CME engineering parameter
table and then calculates the actual distance between the serving cell and every
neighboring cell.
When checking whether to deliver the optimization device, operators can filter the
optimization advice based on the distance between the serving cell and every
neighboring cell or the overshooting check results.

eRAN
NOTE
● When the Overshooting Check parameter is set to ON and operators check a massive
scale of NRT optimization advice, it takes a long time to finish the check.
● If data in the CME engineering parameter table is inaccurate, the calculation result of
the actual distance between the serving cell and a neighboring is inaccurate.
4.2.1.3 Differentiated Handling

An eNodeB performs differentiated handling on different types of neighbor
relationships. The differentiation handling includes the following functions.
Target Cell Selection for Handovers

This function requires that event-triggered ANR is enabled and is controlled by the
NCELL_CLASS_HO_POLICY_SW option of the CellAlgoSwitch.NCellClassMgtSw
parameter.
If this option is selected, the eNodeB performs differential handling as follows
during target cell selection for handovers:
● If the Neighbor Cell Classification Label parameter value is FORMAL for a
neighboring cell contained in the measurement report, the eNodeB selects the
target cell using the NRTs.
● If the Neighbor Cell Classification Label parameter value is EXTENDED for a
neighboring cell contained in the measurement report, the eNodeB instructs
the UE to perform ECGI reading. Based on the ECGI reading results, the
eNodeB determines the target cell.
If this option is deselected, the eNodeB does not instruct the UE to perform ECGI
reading for extended neighbor relationships before a handover. Instead, the
normal target cell selection procedure is adopted for both formal and extended
neighbor relationships.
Neighbor Relationship Handling in PCI Confusion Scenarios

PCI conflict detection is controlled by the
ENodeBAlgoSwitch.PciConflictAlmSwitch parameter and the
CONFUSION_DETECT_SWITCH option of the
ENodeBAlgoSwitch.PciConflictDetectSwitch parameter.
After PCI conflict detection is activated, the eNodeB obtains neighboring cell pairs
that have the same PCI and operating frequency and handles the neighboring cells
as shown in Table 4-26.

eRAN
Table 4-26 Handling of PCI-confused neighboring cells

Neighbor Handling of Neighbor Relationships
Relationship Pair
Type
One extended ● If the extended neighbor relationship is stored in the

neighbor relationship eNodeB memory, the eNodeB does not check and
and one formal report PCI confusion.
neighbor relationship ● If the extended neighbor relationship is stored in the
One extended configuration database, the eNodeB checks and
neighbor relationship reports PCI confusion.
and one blacklisted At the end of a measurement period defined by
neighbor relationship NCellClassMgt.StatPeriodForNCellClass, the eNodeB
removes the extended neighbor relationship if the ratio
of the number of times the ECGI of the formal or
blacklisted neighboring cell is read to the maximum
number of times the ECGI of an extended neighboring
cell is read is greater than or equal to 10.
Two extended ● If the extended neighbor relationship is stored in the

neighbor relationships memory, the eNodeB does not check and report PCI
confusion.
● If the extended neighbor relationship is stored in the
configuration database, the following are true: If the
NCELL_CLASS_PCI_CONFLICT_SW option of the
CellAlgoSwitch.NCellClassMgtSw parameter is
deselected, the eNodeB checks and reports PCI
confusion; otherwise, the eNodeB does not check
and report PCI confusion.
Two formal neighbor The eNodeB checks and reports PCI confusion.
relationships
One formal neighbor

relationship and one
blacklisted neighbor
relationship
Two blacklisted
For details about the definitions and principles of PCI confusion, see PCI Conflict
Detection and Self-Optimization.
Neighbor Relationship Query/Manual Removal

You can run the DSP EUTRANINTRAFREQNCELL or DSP
EUTRANINTERFREQNCELL command to query different types of neighbor
relationships with the Neighbor Cell Classification Flag parameter set to
FORMAL, EXTENDED, or ALL. Formal neighbor relationships are displayed in the
command output by default.

eRAN
You can run the DSP EUTRANEXTENDEDNCELL command to query the neighbor
relationships when the Intra-RAT Neighbor Cell Management Mode parameter
value is INTERNAL_STORAGE_MODE.
You can run the RMV EUTRANEXTENDEDNCELL command to remove extended
neighbor relationships stored in the memory.
You can run the RMV EUTRANINTRAFREQNCELL or RMV
EUTRANINTERFREQNCELL command to remove neighbor relationships with
intra-frequency or inter-frequency E-UTRAN cells.
4.2.2.1 Benefits
If the Neighbor Cell Classification Label parameter is set to EXTENDED for a
neighboring cell and the NCELL_CLASS_HO_POLICY_SW option of the
CellAlgoSwitch.NCellClassMgtSw parameter is selected, the eNodeB instructs a
UE to perform ECGI reading before handing the UE over to this neighboring cell.
This can detect possible PCI confusion, increasing the handover success rate and
decreasing the service drop rate.
The following describes the application scenarios where maximum gains can be
provided.
● New deployment
It is recommended that the INTRA_RAT_NCELL_CLASS_SW and
NCELL_CLASS_PCI_CONFLICT_SW options be selected and the
NCELL_CLASS_HO_POLICY_SW option be deselected. Deselecting the
NCELL_CLASS_HO_POLICY_SW option reduces the number of times of CGI
reading before handovers are executed. It is recommended that the Intra-RAT
Neighbor Cell Management Mode parameter be set to
INTERNAL_STORAGE_MODE to reduce the number of configured
neighboring cells and improve the OM experience.
It is recommended that the INTRA_RAT_OVERDISTANCE_SW option be
selected for the blacklisted neighbor relationship management. This setting
identifies over-distant neighboring cells to which UEs are seldom handed over
or that have low handover success rates so that the eNodeB applies
differentiated handling of these neighboring cells to reduce the number of
handovers to over-distant neighboring cells.
● Site expansion or migration
It is recommended that the intra-RAT neighbor relationship classification and
blacklisted neighbor relationship management functions be enabled.
4.2.2.2 Impacts
Network Impacts
If the Neighbor Cell Classification Label parameter is set to EXTENDED for a
neighboring cell and the NCELL_CLASS_HO_POLICY_SW option of the
CellAlgoSwitch.NCellClassMgtSw parameter is selected, the eNodeB instructs a
UE to perform CGI reading before handing the UE over to this neighboring cell.

eRAN
This increases the handover delay of the UE and decreases the UE throughput. If
CGI reading fails, there is a possibility that UE may experience a service drop.
Function Impacts
None
4.2.3 Requirements
4.2.3.1 Licenses
The following are FDD license requirements.

Name
FDD LOFD-081225 Neighbor Cell LT1S00NCCM00 Per Cell

Classification
Management
There are no TDD license requirements.
4.2.3.2 Software
Name Switch e
FDD Intra-RAT Following ANR None

TDD ANR options of the Managem
ENodeBAlgoS ent
witch.AnrSwi
tch
parameter:
IntraRatEven
tAnrSwitch
IntraRatFast
AnrSwitch

eRAN

Name Switch e
FDD Inter-RAT Following ANR None

TDD ANR options of the Managem
ENodeBAlgoS ent
witch.AnrSwi
tch
parameter:
GeranEventA
nrSwitch
UtranEventA
nrSwitch
GeranFastAn
rSwitch
UtranFastAnr
Switch
FDD PCI ENodeBAlgoS PCI None

TDD conflict witch.PciConf Conflict
detection lictDetectSwi Detection
and self- tch and Self-
optimizati Optimizat
on ion
FDD Neighbori None None This is a function of the
TDD ng cell U2020.
distance
and
overshoot
ing
detection

None
4.2.3.3 Hardware
Base Station Models

No requirements
Boards
No requirements
RF Modules
No requirements

eRAN
4.2.3.4 Networking
For details, see 4.1.3.4 Networking.
4.2.3.5 Others
The configurations in the CME engineering parameter table are correct when the
blacklisted neighbor relationship management function is enabled. The following
are required in the CME engineering parameter table:
● For a non-multi-RRU cell, the CGI (comprised of eNodeB ID, MCC, MNC, and
Cell ID), latitude, and longitude information about the cell is specified on the
LTE sheet.
● For a multi-RRU cell, the CGI information about the cell and the latitude and
longitude information about any RRU of the cell are specified on the LTE
sheet. The "REPEATERRRU" field is set to Yes, indicating that multiple RRUs
exist and the latitude and longitude of each RRU need to be specified. On the
REPEATER sheet, the CGI, RAT (RATTYPE=LTE), RRU name (RepeaterName),
latitude, and longitude information about the cell are specified. Multiple rows
with the same CGI but different latitudes and longitudes are specified for a
multi-RRU cell.
4.2.4.1.1 Process
For details, see 4.1.4.1.1 Process.


Name
Neighbor Cell CellAlgoSwitch.N INTRA_RAT_NCE Select the following

Classification CellClassMgtSw LL_CLASS_SW options:
Mgt Switch NCELL_CLASS_PC ● INTRA_RAT_NCEL
I_CONFLICT_SW L_CLASS_SW
EXTENDED_NCEL ● NCELL_CLASS_PCI_
L_MNG_SW CONFLICT_SW
● EXTENDED_NCELL
_MNG_SW

eRAN

Name
Statistic NCellClassMgt.St None Set the parameter to

Period For atPeriodForNCell its recommended
Neighbor Cell Class value.
Classification
Handover NCellClassMgt.H None Set the parameter to

Attempt oAttemptThd its recommended
Threshold value.
Handover NCellClassMgt.H None Set the parameter to

Success oSuccThd its recommended
Threshold value.
Threshold of NCellClassMgt.C None Set the parameter to

SCell aSCellCfgThd its recommended
Configured value.
Intra-RAT NCellClassMgt.In None The recommended

Neighbor Cell traRatNcellMgtM value is
Management ode INTERNAL_STORAGE
Mode _MODE.
ANR CellAlgoSwitch.A INTRA_RAT_OVE It is recommended

Algorithm nrAlgoSwitch RDISTANCE_SW that the
Switch INTRA_RAT_OVERDIS
TANCE_SW option be
selected.
Handover NCellParaCfg.Ho None Set the parameter to

Statistic StatThd its recommended
Threshold value.

Success Rat SuccThd its recommended
Threshold value.
Neighboring NCellParaCfg.NC None Set the parameter to

Cell Distance ellOdDisThd its recommended
Threshold value.

eRAN

Name
Statistic NCellClassMgt.St A larger value of this parameter results in

Period For atPeriodForNCell higher stability of the neighbor
Neighbor Cell Class relationship classification labeling but
Classification lower timeliness of the classification
results.
A smaller value of this parameter results in
lower stability of both the neighbor
relationship classification labeling and the
neighbor relationship classification
algorithm.

//Activating intra-RAT neighbor relationship classification
//Method 1:
MOD CELLALGOSWITCH: LocalCellId=xx,
NCELLCLASSMGTSW=INTRA_RAT_NCELL_CLASS_SW-1&NCELL_CLASS_HO_POLICY_SW-0&NCELL_CLASS_PCI
_CONFLICT_SW-1&EXTENDED_NCELL_MNG_SW-0;
MOD NCELLCLASSMGT: IntraRatNcellMgtMode=INTERNAL_STORAGE_MODE;
MOD ANR: OptMode=FREE;
//Method 2:
_CONFLICT_SW-1&EXTENDED_NCELL_MNG_SW-0;
MOD ANR: OptMode=CONTROLLED;
MOD NCELLPARACFG: LocalCellId=xx, CellAnrOptMode=FREE;
//Activating intra-RAT blacklisted neighbor relationship management

//Method 1:
MOD CELLALGOSWITCH: LocalCellId=xx, AnrAlgoSwitch=INTRA_RAT_OVERDISTANCE_SW-1;
//Method 2:

Optimize parameters related to intra-RAT ANR according to the setting notes in
Table 4-28.

//Deactivating intra-RAT neighbor relationship classification
_CONFLICT_SW-0;

eRAN
//Activating intra-RAT blacklisted neighbor relationship management


Intra-RAT Neighbor Relationship Classification

You can use SON logs to verify whether this function has taken effect.
To verify whether neighbor relationship classification in configuration mode has

taken effect, perform the following steps:
Step 2 On the Query SON Log tab page, click LTE Neighbor cell Classification
Management Log in the Log Category drop-down list in the upper left corner.
Step 3 Click Set Neighbor Cell Classified Identity in the Custom list under Event Name.
Then click Query to query SON logs of neighbor relationship classification.
----End
To verify whether neighbor relationship classification in eNodeB memory mode

Step 3 Click Add Neighboring Cell and Delete Neighboring Cell in the Custom list
under Event Name. Then click Query to query SON logs of neighbor relationship
classification.
----End
To verify whether classification for extended neighbor relationships has taken

effect, perform the following step:
Step 1 On the U2020 client, choose SON > LTE ANR > Neighboring Cell Management >
Extended Neighbor Relationship.
----End
● MML commands
Run the LST EUTRANINTRAFREQNCELL or LST EUTRANINTERFREQNCELL
to check the Neighbor Cell Classification Label parameter value in
configuration mode. If the parameter value for a neighboring cell is FORMAL
or EXTENDED, this function has taken effect.
Run the DSP EUTRANEXTENDEDNCELL command to check the extended
neighbor relationships in eNodeB memory mode.

eRAN
Intra-RAT Blacklisted Neighbor Relationship Management

You can use SON logs to verify whether this function has taken effect. To
verify whether neighbor relationship classification in eNodeB memory mode

Step 2 On the Query SON Log tab page, click LTE Neighbor cell Classification
Management Log in the Log Category drop-down list in the upper left corner.
Step 3 Click Set Neighbor Cell Classified Identity, Delete Black Neighbor Cell, and
Reject Black Neighbor Cell Request in the Custom list under Event Name. Then,
click Query to query SON logs of neighbor relationship classification.
----End
● MML commands
Run the LST EUTRANBLKNCELL to check the Neighbor Cell Classification
Label parameter value in configuration mode. If the parameter value for a
neighboring cell is FORMAL or EXTENDED, this function has taken effect.
Run the DSP EUTRANEXTENDEDNCELL command to query extended
neighbor relationships with over-distant neighboring cells in eNodeB memory
mode.

Neighbor relationship classification can reduce repeated addition and removal of
neighboring cells. When neighboring cell management in PCI confusion scenarios
takes effect, the number of times UEs read CGIs when PCI confusion occurs is
reduced. The CGI-related performance counters listed in Table 4-22 can reflect the
network performance after intra-RAT ANR is enabled.
After blacklisted neighbor relationship management is enabled, the handover-
related KPIs will improve because the number of handovers to over-distant
neighboring cells decreases.
For details about intra- and inter-frequency handover success rates and E-RAB-
related counters, see 4.1.4.3 Network Monitoring.

For details, see 4.1.4.4 Possible Issues.
4.3 Specified PCI Group-based Neighboring Cell

Management
4.3.1 Principles
In an E-UTRAN, cells on the same frequency may share one PCI. A PCI conflict can
occur between cells on the same frequency. To address this, Huawei eNodeBs

eRAN
introduce a specified PCI group and deploy different management policies for
neighboring cells based on PCI ranges.
This section takes the following application scenarios as examples.
● In FDD, this function can be used in the following scenarios:
– A large number of micro eNodeBs and LampSite eNodeBs are deployed
within the coverage area of a macro eNodeB, and the operator needs to
allocate specified PCI groups for cells served by the micro eNodeBs and
LampSite eNodeBs.
– In a macro eNodeB, super combined cell is enabled, and the operator
needs to allocate a specified PCI group for super combined cells. For
details about super combined cell, see Super Combined Cell (FDD).
● In TDD, this function can be used when a large number of micro eNodeBs and
LampSite eNodeBs are deployed within the coverage area of a macro eNodeB
and the operator needs to allocate specified PCI groups for cells served by the
micro eNodeBs and LampSite eNodeBs.
4.3.1.1 Overview
When a large number of micro eNodeBs and LampSite eNodeBs are deployed
around a macro eNodeB, adjacent cells around the macro eNodeB may share one
PCI since the total number of PCIs is limited. If a cell is configured with intra-
frequency neighboring cells sharing the same PCI, the target cell cannot be
determined in a handover. In this case, UEs cannot be handed over and service
drops occur. To address this, operators can reserve specified PCI groups for cells
served by micro eNodeBs and LampSite eNodeBs and these cells share PCIs in the
groups. During a handover from a macro cell to a micro cell or LampSite cell, the
source eNodeB can identify the target cell based on the ECGI reading result.
In FDD, when super combined cell is enabled, adjacent SFN cells share one PCI but
different ECGIs. This may result that the source eNodeB cannot identify the target
cell based on the reported PCI in a handover from a regular cell to a super
combined cell. Similarly, the Specified PCI Group-based Neighboring Cell
Management feature allows the eNodeB to identify the target cell based on the
ECGI reading result. For details about SFN, see SFN.
Operators need to configure the specified PCI group in the EutranSpePciCell MO
on all eNodeBs using this function. The EutranSpePciCell.StaPhyCellId and
EutranSpePciCell.SpePhyCellIdRange parameters specify the start PCI of the PCI
group and the number of PCIs in the group, respectively.
In this document, a cell allocated with a PCI in the group is called a specified-PCI
cell, and a cell allocated with a PCI that is not in the group is called a regular cell.
4.3.1.2 Specified PCI Group-based ANR Management
Procedure of Event-triggered ANR Based on the Specified PCI Group

This function is controlled by the IntraRatEventAnrSwitch option of the
ENodeBAlgoSwitch.AnrSwitch parameter and the IntraAnrPolicySwitch option
of the CellAlgoSwitch.SpePCIBasedPolicySw parameter.
Event-triggered ANR works differently for regular cells and specified-PCI cells.

eRAN
● In receiving a measurement report from a UE for an intra-RAT handover, a

regular cell (cell A) checks whether the PCIs of neighboring cells contained in
the measurement report are in the specified PCI group which is configured in
the EutranSpePciCell MO.
– If yes, cell A identifies these neighboring cells as specified-PCI cells and
then instructs the UE to read the ECGIs of these neighboring cells. Based
on the ECGI reading results, cell A determines a target cell and initiates
the handover. If the UE reports the ECGI of an unknown cell (cell B), the
eNodeB that serves cell A adds cell B to its NCL and adds the neighbor
relationship with cell B to an intra-RAT NRT of cell A.
– If no, cell A identifies these neighboring cells as regular cells and a
common event-triggered ANR procedure is performed.
● When a specified-PCI cell receives a measurement report from a UE for an
intra-RAT handover, a common event-triggered ANR procedure is performed.
● If the NCellAddProhibitPolicySwitch option of the
CellAlgoSwitch.SpePCIBasedPolicySw parameter is selected for a specified-
PCI cell, the eNodeB does not add the specified-PCI cell to an NRT or NCL.
● If the NO_HO_BASED_X2_AUTO_SETUP_SW option of the
EutranSpePciCell.SpecPciGroupPolicySw parameter is selected for a
specified-PCI cell, the local eNodeB is not allowed to trigger a handover-
induced self-setup procedure for an X2 interface with the eNodeB that serves
the specified-PCI cell.
Procedure of Fast ANR Based on the Specified PCI Group

This function is controlled by the IntraRatFastAnrSwitch option of the
ENodeBAlgoSwitch.AnrSwitch parameter and the IntraAnrPolicySwitch option
of the CellAlgoSwitch.SpePCIBasedPolicySw parameter.
Fast ANR works differently for regular cells and specified-PCI cells.
● When a regular cell (cell C) receives a fast-ANR-related measurement report
from a UE, cell C checks whether the PCIs of neighboring cells contained in
the measurement report are in the specified PCI group which is configured in
the EutranSpePciCell MO.
– If yes, cell C identifies these neighboring cells as specified-PCI cells and
then instructs the UE to read the ECGIs of these neighboring cells. If the
UE reports the ECGI of an unknown cell (cell D), the eNodeB that serves
cell C adds cell D to its NCL and adds the neighbor relationship with cell
D to an intra-RAT NRT of cell C according to policies of fast ANR.
– If no, cell C identifies these neighboring cells as regular cells and a
common fast ANR procedure is performed.
● When a specified-PCI cell receives a fast-ANR-related measurement report
from a UE, a common fast ANR procedure is performed.
If the NCellAddProhibitPolicySwitch option of the
CellAlgoSwitch.SpePCIBasedPolicySw parameter is selected for a specified-PCI
cell, the eNodeB does not add the specified-PCI cell to an NRT or NCL.

eRAN
NOTE
When fast ANR based on the specified PCI group is enabled, you are advised to set the
ANR.FastAnrRprtAmount parameter to r2. This prevents a regular cell from frequently
instructing UEs to perform fast ANR measurements on specified-PCI cells, reducing the
impact on UE throughput.
4.3.1.3 PCI Conflict Detection Based on the Specified PCI Group

This function is controlled by the PciConflictDetectPolicySwitch option of the
CellAlgoSwitch.SpePCIBasedPolicySw parameter and the
CONFUSION_DETECT_SWITCH option of the
ENodeBAlgoSwitch.PciConflictDetectSwitch parameter.
This section describes only the procedure of PCI conflict detection based on the
specified PCI group. For details about the principles of PCI conflict detection, see
PCI Conflict Detection and Self-Optimization.
PCI conflict detection works differently for regular cells and specified-PCI cells.
● When a regular cell initiates a PCI conflict detection procedure, it checks
whether the PCIs of neighboring cells are in the specified PCI group which is
configured in the EutranSpePciCell MO.
– If yes, the regular cell identifies these neighboring cells as specified-PCI
cells and does not initiate a PCI confusion detection and reporting
procedure.
– If no, the regular cell identifies these neighboring cells as regular cells
and a common PCI conflict detection procedure is performed.
● When a specified-PCI cell initiates a PCI conflict detection procedure, a
common PCI conflict detection procedure is performed.
4.3.2.1 Benefits
Specified PCI group-based neighboring cell management reduces manual PCI
planning for eNodeBs that serve specified-PCI cells, reduces the operating expense
(OPEX), and ensures handovers from eNodeBs that serve regular cells to eNodeBs
that serve specified-PCI cells.
provided.
● New Deployment
Use this function when:
A large number of micro eNodeBs and LampSite eNodeBs are deployed within
the coverage area of a macro eNodeB. As a result, some neighboring cells of a
macro cell share one PCI.
Super combined cell (FDD) is enabled.
It is recommended that specified PCI group-based neighboring cell
management be enabled.

eRAN
4.3.2.2 Impacts
Network Impacts
● Before UEs in a regular cell are handed over to a specified-PCI cell, the regular
cell will instruct UEs to perform ECGI reading to select a target cell. ECGI
reading prolongs the delay in handovers, and therefore the serving cell may
not be able to select a target cell, affecting the handover success rate and the
service drop rate.
● UEs read ECGIs in the sleep time during DRX. The traffic volume of UEs
affects the mechanism of ECGI reading during the sleep time. Timer T321
controls the maximum time a UE can spend reading ECGIs. For the timer
values, see 5.5.2.3 "Measurement identity addition/modification" in 3GPP TS
36.331 V10.5.0.
● The sleep time stops when a data packet arrives. This has an impact on the
ECGI reading success rate. This success rate is even lower if UEs are
performing VoLTE services, which are scheduled at a fixed interval and
encounter a higher probability that the sleep time stops.
● ECGI reading during the sleep time affects the UE throughput. This is because
UEs cannot be scheduled while they are reading the ECGI of an unknown cell
in the DRX state. In a commercial network, the impact on UEs depends on the
types of services that UEs are performing.
Function Impacts
Name Switch e
FDD Functions None None With this function enabled,

TDD that the eNodeB that serves a
cannot regular cell may add a
identify neighbor relationship with a
cells with specified-PCI cell to an intra-
the same RAT NRT of the regular cell.
PCI The specified-PCI cell operates
on the same frequency and
uses the same PCI as another
neighboring cell in the NRT.
This addition in the NRT
affects features that cannot
identify intra-frequency cells
with the same PCI.
FDD User- InterFreqMlb Intra-RAT If an intra-RAT NRT of a

TDD number- Switch and Mobility regular cell contains neighbor
based InterFreqBlin Load relationships with cells that
mobility dMlbSwitch Balancing operate on the same
load options of the frequency and share one
balancing CellAlgoSwit specified PCI, these MLB
(MLB) ch.MlbAlgoS functions cannot transfer load
witch from the normal cell to these
parameter cells.

eRAN

Name Switch e
FDD Super CellAlgoSwit Super When a super combined cell

combined ch.SfnAlgoSw Combined cooperates with common cells
cell itch Cell (in non-high-speed railway
(FDD) coverage scenarios), specified
PCI group-based neighboring
cell management must be
enabled for the common cells
and the PCI of the super
combined cell must be set in
the special PCI range of these
cells. Otherwise, handover
may fail when a UE is handed
over from a common cell to
the super combined cell.
4.3.3 Requirements
4.3.3.1 Licenses
Name
FDD LOFD-081207 Specified PCI LT1SSPGNCM00 Per Cell

Group-based
Neighboring
Cell
Management
TDD TDLOFD-0812 Specified PCI LT1SSPGNCM02 Per Cell

01 Group-based
Neighboring
Cell
Management
4.3.3.2 Software

eRAN
RAT Function Name Function Switch Reference
FDD Intra-RAT ANR Following options of the ANR

TDD ENodeBAlgoSwitch.AnrS Management
witch parameter:
IntraRatEventAnrSwitch
IntraRatFastAnrSwitch
FDD PCI conflict detection ENodeBAlgoSwitch.PciCo PCI Conflict

TDD and self-optimization nflictDetectSwitch Detection and
Self-Optimization

None
4.3.3.3 Hardware
Base Station Models

No requirements
Boards
No requirements
RF Modules
No requirements
4.3.3.4 Networking
4.3.3.5 Others
None
4.3.4.1.1 Process

eRAN


Name
Downlink EutranSpePciCell. None Specify the downlink

EARFCN DlEarfcn E-UTRA absolute radio
frequency channel
number (EARFCN) of
E-UTRAN cells with
the specified PCI
according to the
network plan.
Start Physical EutranSpePciCell. None Specify the start PCI

Cell ID StaPhyCellId of the specified PCI
group according to
the network plan.
Specified EutranSpePciCell. None Specify the number of

Physical Cell SpePhyCellIdRan PCIs in the specified
ID Range ge PCI group according
to the network plan.
Specified PCI EutranSpePciCell. NO_HO_BASED_X Select the

Group Policy SpecPciGroupPoli 2_AUTO_SETUP_S NO_HO_BASED_X2_A
Switch cySw W UTO_SETUP_SW
option based on the
network plan.
Specified PCI CellAlgoSwitch.S IntraAnrPolicySw Select the following

Based Policy pePCIBasedPolicy itch options based on the
Switch Sw PciConflictDetect network plan:
PolicySwitch ● IntraAnrPolicySwi
NCellAddProhibit tch
PolicySwitch ● PciConflictDetect-
PolicySwitch
● NCellAddProhibit-
PolicySwitch
Fast ANR PCI ANR.FastAnrRprt None Setting this parameter

report Amount to a small value, for
amount example r2, prevents
the serving cell from
frequently instructing
UEs to perform fast
ANR measurements
on specified-PCI cells,
reducing the impact
on UE throughput.

eRAN

Name
PCI conflict ENodeBAlgoSwit None It is recommended

alarm switch ch.PciConflictAlm that this parameter be
Switch set to ON. Operators
can evaluate whether
this function has
taken effect based on
whether PCI conflict
alarms are reported.
If this parameter is set
to ON, then:
● If the PCI conflict
occurs between
cells with a PCI in
the specified group,
the PCI conflict will
not be reported.
● Otherwise, the
alarm will be
reported.

//Activating specified PCI group-based neighboring cell management
//Configuring the specified PCI group
ADD EUTRANSPEPCICELL: DlEarfcn=x, StaPhyCellId=1, SpePhyCellIdRange=2;
//(Optional) Configuring the policy for the specified PCI group

MOD EUTRANSPEPCICELL: DlEarfcn=3000, StaPhyCellId=25,
SpecPciGroupPolicySw=NO_HO_BASED_X2_AUTO_SETUP_SW-1;
//Activating specified PCI group-based neighboring cell management

MOD CELLALGOSWITCH: LocalCellId=0,
SpePCIBasedPolicySW=IntraAnrPolicySwitch-1&PciConflictDetectPolicySwitch-1&NCellAddProhibitPolicySwitc
h-1;
//(Optional) Setting the number of periodic PCI measurement reports for fast ANR
MOD ANR: FastAnrRprtAmount=r2;
//(Optional) Activating PCI conflict alarm reporting

MOD ENODEBALGOSWITCH: PCICONFLICTALMSWITCH=ON;

//Deactivating specified PCI group-based neighboring cell management
MOD CELLALGOSWITCH: LocalCellId=0,
SpePCIBasedPolicySW=IntraAnrPolicySwitch-0&PciConflictDetectPolicySwitch-0&NCellAddProhibitPolicySwitc
h-0;
//(Optional) Disabling the policy for the specified PCI group

MOD EUTRANSPEPCICELL: DlEarfcn=3000, StaPhyCellId=25,
SpecPciGroupPolicySw=NO_HO_BASED_X2_AUTO_SETUP_SW-0;

eRAN
//(Optional) Deactivating PCI conflict alarm reporting

MOD ENODEBALGOSWITCH: PCICONFLICTALMSWITCH=OFF;

● Fast batch activation
This function can be batch activated using the Feature Operation and
Maintenance function of the CME. For detailed operations, see the following
section in the CME product documentation or online help: CME Management
> CME Guidelines > Enhanced Feature Management > Feature Operation
and Maintenance.
● Single/Batch configuration
This function can be activated for a single base station or a batch of base
stations on the CME. For detailed operations, see CME-based Feature
Configuration.

To use signaling trace to verify whether specified PCI group-based neighboring cell
management has taken effect, perform the following steps:
Management.
choose LTE > Application Layer > Uu Interface Trace.
Step 4 Add the neighbor relationship with a specified-PCI cell to an NRT of a regular cell,
and move a UE from the regular cell to the specified-PCI cell to trigger a
handover.
Step 5 Check whether the UE performs ECGI reading. Specified PCI group-based
neighboring cell management has taken effect if the UE performs ECGI reading as
indicated in the tracing result.
Figure 4-16 shows an example of the tracing result of ECGI reading. When the
source cell receives a measurement report that contains the ECGI, the source cell
sends an RRC Connection Reconfiguration message to the UE and performs the
handover.

eRAN
Figure 4-16 Uu tracing result for ECGI reading observation

eRAN
----End

After specified PCI group-based neighboring cell management is enabled, counters
listed in the following table can be used to help evaluate performance of
handovers from and to specified-PCI cells.
1526746057 L.HHO.SpePciCell.PrepAttIn
1526746058 L.HHO.SpePciCell.ExecAttIn
1526746059 L.HHO.SpePciCell.ExecSuccIn
1526746054 L.HHO.SpePciCell.PrepAttOut
1526746055 L.HHO.SpePciCell.ExecAttOut
1526746056 L.HHO.SpePciCell.ExecSuccOut

4.4 Intra-RAT ANR with Shared Cells
4.4.1 Principles
ANR with shared cells consists of intra-RAT ANR with shared cells and inter-RAT
ANR with shared cells. This section describes intra-RAT ANR with shared cells.
In non-RAN-sharing scenarios, ANR maintains NCLs and NRTs. In RAN sharing
scenarios, ANR also maintains external-cell PLMN lists. Intra-RAT ANR maintains
the PLMN list of each external E-UTRAN cell, which is represented by the
EutranExternalCellPlmn MOs.

eRAN
If a neighboring cell is shared by operators, a UE may not report the PLMN IDs of
the secondary operators or report incorrect PLMN IDs of the primary and
secondary operators. In this case, the source eNodeB needs to obtain the PLMN
information about the neighboring cell from the U2020 to automatically maintain
the external-cell PLMN list.
● If the serving cell and neighboring cells are managed by the same U2020, the
source eNodeB can obtain the neighboring cell information directly from the
U2020.
● If the serving cell and neighboring cells are not managed by the same U2020,
the source eNodeB can obtain the neighboring cell information from the
U2020 that manages the serving cell only after the neighboring cell
information is imported into this U2020. Operators can import the
neighboring cell information into this U2020 by using the CME. If the
neighboring cell information is not imported into this U2020 in a timely
manner, the source eNodeB may not obtain the neighboring cell information
and ANR cannot add neighbor relationships with those cells to the NRTs.
4.4.1.1 Overview
An E-UTRAN cell may have the following types of shared intra-RAT neighboring
cells:
● E-UTRAN cell that broadcasts its PLMN list in a round robin (RR) manner
● E-UTRAN cell that does not broadcast its PLMN list in an RR manner
If PLMN information is changed for a shared E-UTRAN cell, the external-cell

PLMN list (specified by the EutranExternalCellPlmn MO) in each peer eNodeB
can be updated by intra-RAT ANR and can also be updated as follows:
● If the local and peer eNodeBs are connected through an X2 interface, the
local eNodeB sends X2 messages to the peer eNodeB to inform the peer
eNodeB of the change. The peer eNodeB then updates the external-cell PLMN
list based on the X2 messages.
● If the local and peer eNodeBs are not connected through an X2 interface, the
external-cell PLMN list can be updated in the peer eNodeB by manually
triggering either of the following CME functions:
– Association between serving and neighboring cell information
– Consistency check between external E-UTRAN cells and their source cells
4.4.1.2 Shared E-UTRAN Cell Broadcasting Its PLMN List in an RR Manner

If a shared neighboring E-UTRAN cell broadcasts its PLMN list in an RR manner,
the UE may fail to acquire the correct PLMN list of the cell. The neighboring cell
information is stored in the U2020.
The eNodeB can obtain the information from the U2020 depending on the
settings of the NBSLTEPLMNRoundSwitch option of the
ENodeBAlgoSwitch.RanSharingAnrSwitch parameter and the frequency RAN
sharing indicator of neighboring cells.
If the NBSLTEPLMNRoundSwitch option is selected, the RAN sharing policy for

individual frequencies is as follows:

eRAN
● Intra-eNodeB intra- or inter-frequency neighboring cells

The eNodeB does not need to query the information about the neighboring
cells from the U2020.
● Inter-eNodeB intra- or inter-frequency neighboring cells
– If the Cell.IntraFreqRanSharingInd or
EutranInterNFreq.InterFreqRanSharingInd parameter is set to
BOOLEAN_TRUE, the eNodeB can obtain information about the
neighboring cells from the U2020.
BOOLEAN_FALSE, the eNodeB does not query the information about the
neighboring cells from the U2020 but directly adds the neighboring cells
based on CGI reading results.
In MOCN scenarios, the principles of adding external cells and neighbor
relationships by fast ANR vary with the ANR.FastAnrMode parameter setting:
● If this parameter is set to NCL_MODE or NCL_NRT_MODE, fast ANR adds
external cells to the NCL after obtaining related information from the OSS.
● If this parameter is set to NRT_MODE, fast ANR adds external cells to the
NCL and neighbor relationships to the NRTs after obtaining related
information from the OSS.
If intra-RAT event-triggered ANR detects a missing neighboring E-UTRAN cell by
using event-triggered UE measurements or intra-RAT fast ANR detects a missing
neighboring E-UTRAN cell, the source eNodeB automatically maintains the
external-cell PLMN list after receiving a measurement report that contains the
ECGI of the missing cell from the UE. The maintenance procedure is as follows:
1. The source eNodeB reports the PCI and ECGI acquired by the UE to the
U2020. The ECGI is comprised of the PLMN ID, eNodeB ID, and cell ID.
2. The U2020 queries the PLMN IDs of the primary and secondary operators that
share the cell identified by the PCI, eNodeB ID, and cell ID. The U2020 then
sends the query result to the source eNodeB.
3. The source eNodeB adds the PLMN information to the external-cell
configuration of the shared E-UTRAN cell.
NOTE
If a shared cell broadcasts its PLMN list in an RR manner, the source eNodeB must obtain
information about this cell from the U2020 before initiating handovers to this cell. UEs can
be handed over to a target cell only after the target cell has been added to the NCL of the
source eNodeB and the NRT of source cell and the external-cell PLMN list of the target cell
has been configured.
If the base station serving the target cell is provided by another vendor, the base station
cannot obtain information about the target cell from the U2020. In this case, the source
eNodeB does not add the target cell to the NCL and NRTs.
For details about RAN sharing, see RAN Sharing.
4.4.1.3 Shared E-UTRAN Cell Not Broadcasting Its PLMN List in an RR

Manner
If a shared neighboring E-UTRAN cell does not broadcast its PLMN list in an RR
manner, the UE may not acquire a complete PLMN list of the cell. As a result, the

eRAN
PLMN list is not included in the external-cell configuration. The neighboring cell
information is stored in the U2020.
The eNodeB can obtain the information from the U2020 depending on the
settings of the NBSLTERANSharingSwitch option of the
ENodeBAlgoSwitch.RanSharingAnrSwitch parameter and the frequency RAN
sharing indicator of neighboring cells.
If the NBSLTERANSharingSwitch option is selected, the RAN sharing policy for
individual frequencies is as follows:
● Intra-eNodeB intra- or inter-frequency neighboring cells
The eNodeB does not need to query the information about the neighboring
cells from the U2020.
● Inter-eNodeB intra- or inter-frequency neighboring cells
BOOLEAN_TRUE, the eNodeB can obtain information about the
neighboring cells from the U2020.
If the Cell.IntraFreqRanSharingInd or
BOOLEAN_FALSE, the eNodeB does not query the information about the
neighboring cells from the U2020 but directly adds the neighboring cells
based on CGI reading results.
For details about the principles of adding neighboring cells to the NCL and adding
neighbor relationships to NRTs in the preceding scenarios, see 4.4.1.2 Shared E-
UTRAN Cell Broadcasting Its PLMN List in an RR Manner.
If intra-RAT event-triggered ANR detects a missing neighboring E-UTRAN cell by
using event-triggered UE measurements or intra-RAT fast ANR detects a missing
neighboring E-UTRAN cell, the source eNodeB automatically maintains the
external-cell PLMN list after receiving a measurement report that contains the
ECGI of the cell from the UE. The maintenance procedure varies depending on
whether the UE reports the PLMN list:
● If the UE reports the PLMN list, the source eNodeB directly adds the PLMN
information to the external-cell configuration.
● If the UE does not report the PLMN list, the maintenance procedure is as
follows:
a. The source eNodeB reports the ECGI acquired by the UE to the U2020.
b. The U2020 queries the PLMN list of the cell and then sends the query
result to the source eNodeB.
c. The source eNodeB adds the PLMN information to the external-cell
configuration.

eRAN
NOTE
The system information delivered in cell B (a neighboring E-UTRAN cell of cell A) does not
include the PLMN IDs of these secondary operators if cell B is shared by multiple operators
(including two or more secondary operators) and the S1 interfaces of some secondary
operators of cell B are faulty. In this case, the PLMN list of cell B acquired by the UE is
incomplete, and cell A does not automatically add the PLMN IDs of these secondary
operators to the PLMN list configuration. After the S1 interfaces recover, operators must
manually add these PLMN IDs to the PLMN list configuration.
If a UE does not report the PLMN list of the target cell, the source eNodeB must obtain
information about this cell from the U2020. Before the target cell is added to the NCL of
the source eNodeB and the PLMN information is added to the external-cell configuration of
the source cell, UEs can be handed over to the primary-PLMN cell but not the secondary-
PLMN cell. If the base station serving the target cell is provided by another vendor, the base
station cannot obtain information about the target cell from the U2020. In this case, the
source eNodeB does not add the target cell to the NCL and NRTs.
4.4.2.1 Benefits
information about the neighboring cell from the U2020 and automatically
maintains the external-cell PLMN list.
It is recommended that ANR with shared E-UTRAN cells be enabled so that
maximum gains can be provided if both of the following conditions are met:
● Neighboring E-UTRAN cells are shared by operators.
If a neighboring E-UTRAN cell works in RAN sharing mode and broadcasts its
PLMN list with the top PLMN ID rotated, select the
NBSLTEPLMNRoundSwitch option of the
ENodeBAlgoSwitch.RanSharingAnrSwitch parameter. If a neighboring E-
UTRAN cell works in RAN sharing mode and broadcasts its PLMN list without
the top PLMN ID rotated, deselect the NBSLTEPLMNRoundSwitch option of
the ENodeBAlgoSwitch.RanSharingAnrSwitch parameter and select the
NBSLTERANSharingSwitch option of the same parameter.
● The serving and neighboring cells are managed by the same U2020, or the
configuration data of the neighboring cells has been imported into the U2020
that manages the serving cell.
It is recommended that ANR with shared E-UTRAN cells be disabled if either of
the preceding conditions is not met.
4.4.2.2 Impacts
Network Impacts
When ANR detects missing neighboring shared cells, the eNodeB queries the
U2020 for the cells. The query lasts for a maximum of 3 minutes and may affect
the handover. If no candidate target cell is available for the handover, a service
drop may occur.

eRAN
For details about related KPIs, see 4.1.2.2 Impacts.
Function Impacts
None
4.4.3 Requirements
4.4.3.1 Licenses
None
4.4.3.2 Software

witch parameter:

None
4.4.3.3 Hardware
Base Station Models

No requirements
Boards
No requirements
RF Modules
No requirements
Cells
If the serving cell and neighboring cell are managed by different U2020s, ANR
with shared cells requires cross-U2020 neighboring cell information query. In this

eRAN
case, operators must import the neighboring cell information into the U2020 that
manages the serving cell regularly.
Assume that the serving cell (cell A) is managed by U2020 A, and the neighboring
cell (cell B) is managed by U2020 B. The operations and requirements of
importing neighboring cell information to U2020 A are as follows:
● Set FTP server information on U2020 B for automatically uploading
neighboring cell information by FTP to U2020 A. In the CME NCCDM dialog
box, set parameters as follows:
– Set the Server IP parameter to the IP address of U2020 A.
– Set the Server Directory parameter to the file path where neighboring
cell information is to be stored.
For details, see "Setting a Server for Auto-Uploading Files Through the
FTP" in the Software and Hardware Management in the U2020 product
documentation.
● On U2020 B, use the CME to create a scheduled task of exporting neighboring
cell information with the task type set to Inter-System Neighboring Cell
Export. In the task interface, Export Inter-Rat ANR Data must be selected.
● On U2020 A, enable cross-U2020 neighboring cell information query by
selecting Enable cross-OSS neighboring cell optimization. Set the file path
to the value of Server Directory specified on U2020 B.
For details, see "Setting ANR Switches and Parameters" in SON Management
in the U2020 product documentation.
4.4.3.4 Networking
4.4.3.5 Others
None
4.4.4.1.1 Process


eRAN

Name
Intra Cell.IntraFreqRan None The recommended

Frequency SharingInd value is
RAN Sharing BOOLEAN_TRUE for
Indication the serving frequency
if an intra-frequency
neighboring cell is
shared by operators,
regardless of whether
the cell broadcasts its
PLMN list with the top
PLMN ID rotated in
RAN sharing
scenarios.
Inter EutranInterNFreq None The recommended

Frequency .InterFreqRanSha value is
RAN Sharing ringInd BOOLEAN_TRUE for a
Indication neighboring E-UTRA
frequency if an inter-
frequency neighboring
cell on the frequency
is shared by operators,
regardless of whether
the cell broadcasts its
PLMN list with the top
PLMN ID rotated in
RAN sharing
scenarios.
ANR Under ENodeBAlgoSwit NBSLTEPLMNRou Set the following

RAN Sharing ch.RanSharingAn ndSwitch options:
Algorithm rSwitch NBSLTERANShari ● NBSLTEPLMNRoun
Switch ngSwitch dSwitch
● NBSLTERANSharin
gSwitch

//Activating intra-RAT ANR with shared cells
MOD CELL: LocalCellId=xx, IntraFreqRanSharingInd=BOOLEAN_TRUE;
MOD EUTRANINTERNFREQ: LocalCellId=xx, DlEarfcn=xx, InterFreqRanSharingInd=BOOLEAN_TRUE;
//Enabling ANR with a shared neighboring E-UTRAN cell that broadcasts its PLMN list with the top PLMN
ID rotated
MOD ENODEBALGOSWITCH: RanSharingAnrSwitch=NBSLTEPLMNRoundSwitch-1;
//Enabling ANR with a shared neighboring E-UTRAN cell

eRAN
RanSharingAnrSwitch=NBSLTEPLMNRoundSwitch-0&NBSLTERANSharingSwitch-1;

//Deactivating intra-RAT ANR with shared cells
MOD CELL: LocalCellId=xx, IntraFreqRanSharingInd=BOOLEAN_FALSE;
MOD EUTRANINTERNFREQ: LocalCellId=xx, DlEarfcn=xx, InterFreqRanSharingInd=BOOLEAN_FALSE;
//Disabling ANR with a shared neighboring E-UTRAN cell that broadcasts its PLMN list with the top PLMN
ID rotated
MOD ENODEBALGOSWITCH: RanSharingAnrSwitch=NBSLTEPLMNRoundSwitch-0;
//Disabling ANR with a shared neighboring E-UTRAN cell

MOD ENODEBALGOSWITCH: RanSharingAnrSwitch=NBSLTERANSharingSwitch-0;


following steps:

Step 3 In the Event Name area, select items such as Add External Cell and Delete
External Cell to check ANR operation of adding or removing external-cell PLMN
lists.
----End
● MML commands
Run the LST EUTRANEXTERNALCELLPLMN command to list the external-cell
PLMN lists.

For details about related counters, see 4.1.4.3 Network Monitoring.

4.5 Intra-RAT PLMN ID Management
4.5.1 Principles
PLMN ID management enables an eNodeB to identify neighboring cells with
invalid PLMN IDs based on neighboring cells with invalid PLMN IDs detected and
reported by UEs and then perform differentiated management. This function

eRAN
applies to scenarios where neighboring cells are near the borders of different
PLMNs or abnormal UEs report invalid PLMN IDs.
Attributes of a PLMN are set manually in the NCellPlmnList MO. For each PLMN,
operators need to set the attributes by configuring the following parameters:
NCellPlmnList.Mcc, NCellPlmnList.Mnc, NCellPlmnList.RatType, and
NCellPlmnList.PlmnListType.
● The NCellPlmnList.Mcc and NCellPlmnList.Mnc parameters indicate the
mobile country code (MCC) and mobile network code (MNC), respectively. A
PLMN ID is composed of an MCC and an MNC.
● The NCellPlmnList.RatType parameter indicates the RAT of neighboring cells
of a PLMN. It can be set to EUTRAN, UTRAN, GERAN, or NR.
● The NCellPlmnList.PlmnListType parameter indicates the type of a PLMN.
– If this parameter is set to BLACK_LIST for a PLMN, the eNodeB cannot
add cells of the PLMN to NCLs or add neighbor relationships with these
cells to NRTs by ANR.
– If this parameter is set to GREY_LIST for a PLMN, the eNodeB can add
cells of the PLMN to NCLs and add neighbor relationships with these cells
to NRTs by ANR. In addition, ANR automatically sets the Neighbor Cell
Plmn Label parameter to GREY for these cells. The eNodeB does not
remove a neighbor relationship for which the Neighbor Cell Plmn Label
parameter is set to GREY from an NRT when removing redundant
neighbor relationships. This prevents such a neighbor relationship from
being repeatedly removed.
– If this parameter is set to WHITE_LIST for a PLMN, the eNodeB can add
cells of the PLMN to NCLs and add neighbor relationships with these cells
to NRTs by ANR. In addition, ANR automatically sets the Neighbor Cell
Plmn Label parameter to WHITE for these cells.
Operators can check the PLMN list labels of neighboring cells by running the
DSP EUTRANINTRAFREQNCELL, DSP EUTRANINTERFREQNCELL, DSP
UTRANNCELL, and DSP GERANNCELL commands. By default, the
information about whitelisted neighbor relationships is displayed in the
command output.
In addition, at most two types of PLMN can be manually configured for
neighboring cells of a RAT.
It is recommended that a whitelist and a greylist be configured for a PLMN. In
such a case, a PLMN with its type unspecified is in the blacklist, and neighboring
cells of this PLMN or corresponding external cells will not be added to any NRT or
NCL by ANR. If type of the master or any secondary PLMN of a neighboring cell
working in RAN sharing mode is not specified, this neighboring cell and the
corresponding external cell will not be added to any NRT or NCL by ANR.
For neighboring cells of an RAT, if operators set some PLMNs to one type and
leave other PLMNs' types undefined or leave all PLMNs' types undefined, the
eNodeB handles as follows:
● If operators have configured only blacklisted PLMNs, other type-undefined
PLMNs are regarded as whitelisted by default.
● If operators have configured only whitelisted PLMNs, other type-undefined
PLMNs are regarded as greylisted by default.

eRAN
● If operators have configured only greylisted PLMNs, other type-undefined

PLMNs are regarded as whitelisted by default.
● If operators have not defined the type of any PLMN, all PLMNs are regarded
as whitelisted by default.
In scenarios where abnormal UEs report neighboring cells with invalid PLMN IDs,
if the eNodeB adds such cells to NCLs and adds neighbor relationships with such
cells to NRTs, the addition of correct neighboring cells and neighbor relationships
is affected, as well as the target cell selection in handovers. Therefore, it is
recommended that the NCellPlmnList.PlmnListType parameter be set to
BLACK_LIST for the invalid PLMNs.
If neighboring cells are near the borders of different PLMNs, UEs can detect these
neighboring cells. If the neighboring cells are not added to NCLs and neighbor
relationships with these cells are not added to NRTs, UEs repeatedly read the CGIs
of these neighboring cells and target cells may be incorrectly selected during
handovers. Therefore, it is recommended that operators add neighboring PLMNs
to the PLMN greylist by setting the NCellPlmnList.PlmnListType parameter to
GREY_LIST.
4.5.2.1 Benefits
This function prevents neighbor relationships with cells that have abnormal PLMN
IDs from being added to NRTs, thereby increasing the handover success rate and
provided.
● New deployment
It is recommended that PLMN ID management be enabled if neighboring cells
are near the borders of PLMNs and when UEs report invalid PLMN IDs.
It is recommended that the NCellPlmnList.PlmnListType parameter be set to
WHITE_LIST for PLMNs of all operators that provide services and GREY_LIST
for a special PLMN.
If the SON logs indicate that no handovers occur between the eNodeB and
eNodeBs of another operator, it is recommended that the
NCellPlmnList.PlmnListType parameter be set to GREY_LIST for PLMNs of
the operator to reduce the number of times of CGI reading and obtain inter-
PLMN PCI alarms.
It is recommended that the PLMN ID management function be enabled.
4.5.2.2 Impacts
Network Impacts
None

eRAN
Function Impacts
None
4.5.3 Requirements
4.5.3.1 Licenses
None
4.5.3.2 Software

witch parameter:

None
4.5.3.3 Hardware
Base Station Models

No requirements
Boards
No requirements
RF Modules
No requirements
4.5.3.4 Networking
For details, see 4.1.4.3 Network Monitoring.

eRAN
4.5.3.5 Others
None
4.5.4.1.1 Process


Name
Mobile NCellPlmnList.M This parameter specifies the MCC of a

Country Code cc PLMN.
Mobile NCellPlmnList.M This parameter specifies the MNC of a

Network Code nc PLMN.
Rat Type NCellPlmnList.Ra This parameter specifies the RAT of a

tType PLMN.
Plmn List NCellPlmnList.Pl For invalid PLMN IDs reported by

Type mnListType abnormal UEs, the value BLACK_LIST is
recommended.
Near the borders of different PLMNs, the
value GREY_LIST is recommended.

//Activating PLMN ID management
ADD NCELLPLMNLIST: Mcc="xxx", Mnc="xx", RatType=EUTRAN, PlmnListType=WHITE_LIST;
ADD NCELLPLMNLIST: Mcc="460", Mnc="998", RatType=EUTRAN, PlmnListType=GREY_LIST;

//Deactivating PLMN ID management
RMV NCELLPLMNLIST: Mcc="xxx", Mnc="xx", RatType=EUTRAN;
RMV NCELLPLMNLIST: Mcc="460", Mnc="998", RatType=EUTRAN;


eRAN

To use MML commands to verify whether PLMN ID management has taken effect,

command to check whether ANR adds neighbor relationships with cells of the
relative PLMNs to the NRTs. If the Plmn List Type value is set to BLACK_LIST for a
PLMN, ANR does not add neighbor relationships with cells of the PLMN to NRTs.
Step 2 Run the DSP EUTRANINTRAFREQNCELL or DSP EUTRANINTERFREQNCELL
command to check the value of the Neighbor Cell Plmn Label parameter. If the
Plmn List Type parameter is set to GREY_LIST or WHITE_LIST for a PLMN, ANR
adds neighbor relationships with cells of the PLMN to NRTs and specifies the
PLMN type of the neighboring cell by setting the Neighbor Cell Plmn Label
parameter.
● If the parameter value is WHITE, the PLMN is valid.
● If the parameter is BLACK or GREY, the PLMN is invalid.
----End

For details about related counters, see 4.1.4.3 Network Monitoring.


eRAN
ANR Management Feature Parameter Description 5 Functions Related to Inter-RAT ANR
5 Functions Related to Inter-RAT ANR
5.1 Inter-RAT ANR
5.1.1 Principles
Inter-RAT ANR includes the following functions:
● Inter-RAT NCL and NRT

● Event-triggered ANR
● Fast ANR
● Automatic optimization of neighbor relationship attributes
● NG-RAN NCL/NRT self-management based on EN-DC X2 messages
Intra-ANR and inter-RAT ANR work in a similar way but differ in certain principles
and parameters.
NOTE
● To avoid overload, the eNodeB does not handle unknown CGIs, when the CPU usage of
the main control board exceeds 80%. The handling of unknown CGIs includes adding
and updating NCL and NRT entries. For details, see 5.1.1.2.1 Automatic Detection and
Addition of Missing Neighboring Cells and 5.1.1.2.2 NCL Entry Modification.
● CDMA2000 in this document includes CDMA2000 HRPD and CDMA2000 1xRTT.
● In FDD, ANR with CDMA2000 does not check for PnOffset conflicts and abnormal
neighboring cell coverage, because there are few standardized interfaces between LTE
and CDMA2000 and the E-UTRAN has difficulty detecting abnormal CDMA2000 cell
coverage.
● In FDD, eNodeBs support only event-triggered ANR with CDMA2000. Event-triggered
ANR with CDMA2000 supports automatic neighbor relationship addition and
specification-based removal.
● Automatic removal by ANR with NG-RAN supports only specification-based removal and
removal of redundant NCL/NRT entries.
5.1.1.1 Inter-RAT NCL and NRT

eRAN
5.1.1.1.1 NCL/NRT Control Mode

Table 5-1 lists the parameters that specify the control mode for external cells in
NCLs and neighbor relationships in NRTs for inter-RAT ANR. For details, see
4.1.1.1.1 NCL/NRT Control Mode.
Table 5-1 Control mode parameters

NCL/NRT Parameter
External UTRAN UtranExternalCell.CtrlMode

cell
Neighbor UtranNCell.CtrlMode
relationship with a
UTRAN cell
Blacklisted UtranBlkNCell.CtrlMode
neighboring
UTRAN cell
External GERAN GeranExternalCell.CtrlMode

cell
Neighbor GeranNcell.CtrlMode
relationship with a
GERAN cell
External NG-RAN CONTROL_MODE_FLAG option of the

cell NrExternalCell.AggregationAttribute parameter
Neighbor CONTROL_MODE_FLAG option of the

relationship with NrNRelationship.AggregationAttribute parameter
an NG-RAN cell
5.1.1.1.2 NRT Optimization Mode

Inter-RAT NRT optimization mode specifies whether the following types of
optimization advice automatically take effect or require manual confirmation:
● GERAN and UTRAN optimization advice on inter-RAT blind handover priorities
● GERAN, UTRAN, and NG-RAN NRT optimization advice
● UTRAN BT optimization advice
The GERAN and UTRAN optimization advice on inter-RAT blind handover priorities
is controlled by the BlindNcellOpt.OptMode parameter.
● When this parameter is set to FREE, the optimization advice takes effect
directly.
● When this parameter is set to CONTROLLED, the optimization advice needs
to be reported to the U2020. The optimization is subject to the manual
confirmation on the U2020.
The NRT optimization advice takes effect in manners varying with different RATs.
The NRT optimization advice and BT optimization advice take effect as follows:

eRAN
● The GERAN and UTRAN NRT optimization advice and UTRAN BT optimization
advice are controlled by the ANR.OptMode parameter.
– When the ANR.OptMode parameter is set to FREE, the NRT optimization
advice and BT optimization advice optimization advice take effect directly.
– When the ANR.OptMode parameter is set to CONTROLLED and the
NCellParaCfg.RatType parameter is set to UTRAN or GERAN, the
NCellParaCfg.CellAnrOptMode parameter specifies whether the UTRAN
or GERAN optimization advice needs to be reported to the U2020.
▪ For NRT optimization advice:

○ When the NCellParaCfg.CellAnrOptMode parameter is set to
FREE, the optimization advice on neighbor relationships with
UTRAN or GERAN cells takes effect on the eNodeB directly.
CONTROLLED, the optimization advice on neighbor
relationships with UTRAN or GERAN cells needs to be reported
to the U2020. The optimization is subject to the manual
confirmation on the U2020.
▪ For BT optimization advice:

FREE, the BT optimization advice on neighbor relationships with
UTRAN cells needs to be reported to the U2020. The
optimization is subject to the manual confirmation on the
U2020.
CONTROLLED, the eNodeB does not generate the BT
optimization advice or report the BT optimization advice on
neighbor relationships with UTRAN cells to the U2020.
● The NCellParaCfg.CellAnrOptMode parameter specifies the delivery mode
for NG-RAN NRT optimization advice.
When the NCellParaCfg.RatType parameter is set to NR, the
NCellParaCfg.CellAnrOptMode parameter specifies whether the NG-RAN
optimization advice needs to be reported to the U2020.
– When the NCellParaCfg.CellAnrOptMode parameter is set to
CONTROLLED, the NRT optimization advice needs to be reported to the
U2020. The optimization is subject to the manual confirmation on U2020.
– When the NCellParaCfg.CellAnrOptMode parameter is set to FREE, the
NRT optimization advice takes effect directly.
When the ANR.OptMode parameter is set to CONTROLLED, the collaboration
between adding neighboring cells and performing handovers varies depending on
the target RATs of handovers:
● Handovers to GERAN cells
For details, see the intra-RAT handover scenario described in 4.1.1.1.2 NRT
Optimization Mode.
● Handovers to UTRAN cells
The eNodeB must deliver handover measurement configurations including
information about neighboring UTRAN cells to UEs. Therefore, if maintenance

eRAN
personnel do not confirm the optimization advice about adding the neighbor
relationship with a UTRAN cell to the NRT, the eNodeB does not hand over
UEs to the UTRAN cell.
NOTE
● When the optimization advice on the blind handover priority for a neighbor relationship
is generated and the maintenance personnel do not deliver the optimization advice but
manually change the blind handover priority, the modification takes effect directly on
the eNodeB and the optimization advice is reserved on the U2020.
● NCLs are not controlled by the ANR.OptMode parameter, and the eNodeB cannot
generate NCL optimization advice. The eNodeB automatically adds external cells to
NCLs, removes external cells from NCLs, and updates the information about the external
cells in NCLs even if this parameter is set to CONTROLLED.
5.1.1.1.3 Method for NCL/NRT Management to Take Effect

Neighbor relationship management of inter-RAT ANR takes effect on a per base
station, cell, or frequency basis, each controlled by base-station-, cell-, or
frequency-specific ANR parameters. Table 5-2 lists the parameters.
● Base-station-specific ANR parameters: To implement inter-RAT ANR, operators
must turn on base-station-specific ANR switches.
● Cell-specific ANR parameters: To implement inter-RAT ANR for a local cell
after base-station-specific ANR switches are turned on, cell-specific switches
must be turned on for this cell.
● Frequency-specific ANR parameters: After cell-specific ANR takes effect for
the local cell, frequency-specific ANR parameters control whether ANR takes
effect for neighboring cells on a specific neighboring frequency of the local
cell.
Table 5-2 List of base-station-, cell-, and frequency-specific inter-RAT ANR

parameters
RAT Base-Station- Cell-Specific Parameters Frequency-
Specific Parameters Specific
Parameters
GERAN ● Event-triggered INTER_RAT_ANR_SW GeranNfreqGrou

ANR option of the p.AnrInd
GeranEventAnrS CellAlgoSwitch.AnrFuncti
witch option of onSwitch parameter
the
ENodeBAlgoSwit
ch.AnrSwitch
parameter
● Fast ANR
GeranFastAnrSw
itch option of the
ENodeBAlgoSwit
ch.AnrSwitch
parameter

eRAN
RAT Base-Station- Cell-Specific Parameters Frequency-

Specific Parameters Specific
Parameters
UTRAN ● Event-triggered INTER_RAT_ANR_SW UtranNFreq.AnrI

ANR option of the nd
UtranEventAnrS CellAlgoSwitch.AnrFuncti
witch option of onSwitch parameter
the
ENodeBAlgoSwit
ch.AnrSwitch
parameter
● Fast ANR
UtranFastAnrSwi
tch option of the
ENodeBAlgoSwit
ch.AnrSwitch
parameter
CDMA2 Event-triggered ANR INTER_RAT_ANR_SW None

000 CdmaEventAnrSwit option of the
(FDD) ch option of the CellAlgoSwitch.AnrFuncti
ENodeBAlgoSwitch. onSwitch parameter
AnrSwitch
parameter
NG- ● Event-triggered ● Event-triggered ANR ANR_INDICATIO

RAN ANR is not under NR_EVENT_ANR_SW N option of the
the control of option of the NrNFreq.Aggrega
base-station- CellAlgoSwitch.AnrFu tionAttribute
specific nctionSwitch parameter
parameters. parameter
● Fast ANR: ● Fast ANR
ANR.NrFastAnrR INTER_RAT_ANR_SW
srpThld option of the
– If this CellAlgoSwitch.AnrFu
parameter is nctionSwitch
set to 0, fast parameter
ANR does not
take effect.
– If this
parameter is
set to a value
other than 0,
fast ANR takes
effect.

eRAN
NOTE
● NCLs are configured on a per base station basis. A base station adheres to the following
rules when configuring NCLs:
● External cells are added to an NCL based on the frequency indicators of the source
cells.
● External cells can be directly removed from NCLs if each cell served by the base
station does not have neighbor relationships with the external cells.
● Before enabling inter-RAT ANR with NG-RAN, ensure that the
NCellPlmnList.gNBIdLength parameter has been set for the PLMNs whose attributes
meet the requirements for the PLMN whitelist or greylist. If this parameter has not been
set, this function does not take effect. As a result, corresponding external cells and
neighbor relationships cannot be added. For PLMNs whose attributes meet the
conditions for the PLMN blacklist, setting of the NCellPlmnList.gNBIdLength
parameter is not required. This is because the eNodeB does not add cells of blacklisted
PLMNs to an NRT or NCL. For details about PLMN attributes, see 4.5.1 Principles.
5.1.1.2 Event-triggered ANR

Inter-RAT event-triggered ANR includes detection of inter-RAT missing
neighboring cells by using event-triggered UE measurements and automatic
maintenance of inter-RAT NCLs and NRTs. This function takes effect on a per
eNodeB, cell, or frequency basis. For details, see 5.1.1.1.3 Method for NCL/NRT
Management to Take Effect.

Inter-RAT event-triggered ANR detects missing inter-RAT neighboring cells based
on the cell lists in inter-RAT measurement reports. This type of ANR is triggered by
inter-RAT mobility measurements.
Automatic detection of missing neighboring cell takes effect only after event-
triggered ANR is enabled. Table 5-3 lists types of handover measurements and
related eNodeB-specific parameters.
● Event-triggered ANR with GERAN or UTRAN can be triggered only by
coverage-based handover measurements, service-based inter-RAT handover
measurements (applicable only to ANR with UTRAN) (TDD), or inter-RAT
MLB measurements.
● Event-triggered ANR with NG-RAN can be triggered by NSA DC
measurements or measurements related to LTE-to-NR handover based on
NG-RAN coverage.
● Other types of measurements cannot trigger event-triggered inter-RAT ANR.

eRAN
Table 5-3 Types of inter-RAT handover measurements and related base-station-

specific parameters
Handover Parameter for ANR Parameter for Parameter
Measurement with UTRAN ANR with GERAN for ANR with
Type NG-RAN
Coverage-based None None N/A

mobility
measurements
Inter-RAT MLB MlbBasedEventAnrS- MlbBasedEventA N/A

measurements witch option of the nrSwitch option
ENodeBAlgoSwitch.A of the
nrSwitch parameter ENodeBAlgoSwit
ch.AnrSwitch
parameter
Service-based ServiceBasedEven- N/A N/A

inter-RAT tAnrSwitch option of
handover the
measurements ENodeBAlgoSwitch.A
(applicable only nrSwitch parameter
to ANR with
UTRAN) (TDD)
NSA-DC-based N/A N/A None

measurements
Coverage-based N/A N/A None

LTE-to-NR
handover
measurements
This section uses the procedure for detecting a missing neighboring UTRAN cell to
illustrate how inter-RAT event-triggered ANR detects missing inter-RAT
neighboring cells. Assume that a UE is served by cell A of the source eNodeB and
that cell B is an adjacent UTRAN cell of cell A. Figure 5-1 illustrates how the
eNodeB uses event-triggered UE measurements to detect cell B.
NOTE
If the neighbor relationship with a cell is automatically added by inter-RAT event-triggered

ANR based on inter-RAT MLB measurements, this neighboring cell is not selected as the
target cell for this load-based inter-RAT handover but will be selected as the target cell for
subsequent load-based inter-RAT handovers.

eRAN
Figure 5-1 Procedure for using event-triggered UE measurements to detect a

missing inter-RAT neighboring cell
1. The source eNodeB delivers the inter-RAT measurement configuration to the

UE, activates gap mode, and instructs the UE to measure the specified UTRAN
frequencies and cells.
2. The UE detects that cell B meets the measurement requirements, so the UE
reports the scrambling code of cell B to cell A.
3. The source eNodeB checks whether its UTRAN NCL includes the scrambling
code of cell B.
– If the NCL includes the scrambling code, the ANR procedure ends.
– If the NCL does not include the scrambling code, cell B is a missing inter-
RAT neighboring cell of cell A. The procedure continues.
4. The source eNodeB instructs the UE to read information such as the CGI,
location area code (LAC), and routing area code (RAC) of cell B.
NOTE
● The eNodeB does not process other measurement reports sent from the UE before
the UE finishes CGI measurements or the T321 timer expires.
● The eNodeB instructs a UE in the EN-DC state to perform ECGI measurements of
neighboring UTRAN or GERAN cells only after the UE reports the "utra-GERAN-
CGI-Reporting-ENDC" field in the "UE_EUTRA_Capability" IE.
5. The UE reports the CGI, LAC, and RAC of cell B to the source eNodeB.
After detecting the missing neighboring cell, the source eNodeB adds and updates
the entries in the NCL or NRT. For details, see Automatic Addition of Missing
Neighboring Cells.
● UTRAN measurement

eRAN
According to 3GPP specifications, UEs cannot report missing neighboring

UTRAN cells by sending B1- or B2-related measurement reports to eNodeBs.
Instead, eNodeBs use SON-dedicated measurements (with purpose set to
ReportStrongestCellsForSON) to instruct UEs to report missing neighboring
UTRAN cells.
According to 3GPP TS 36.331 of versions earlier than V10.12.0, if the eNodeB
delivers the ANR-related measurement configuration of a UTRAN frequency
where 32 cells operate, certain UEs cannot send measurement reports of the
UTRAN frequency for ANR. However, 3GPP TS 36.331 V10.12.0 and later
versions have been modified. In the measurement configuration for ANR, the
maximum number of adjacent cells is equal to the protocol-defined value
minus one. The McUtranNcellNumOptSwtich option of the
ENodeBAlgoSwitch.HoSignalingOptSwitch parameter specifies whether the
modification takes effect.
The length of time in which UEs perform CGI reading for event-triggered ANR
with UTRAN is specified by the ANR.UtranEventAnrCgiTimer parameter. If a
UE fails to read the CGI of an adjacent cell within the length of time, the
eNodeB removes the measurement configuration related to CGI reading.
● GERAN measurement
UEs can report missing neighboring GERAN cells by sending B1- or B2-related
measurement reports to eNodeBs. According to 3GPP TS 36.331 V11.6.0, if the
eNodeB includes the IE cellForWhichToReportCGI in the measurement
configuration, the IE MeasObjectGERAN includes only one GERAN ARFCN.
Before the modification, the IE MeasObjectGERAN can include multiple
GERAN ARFCNs. If the IE includes multiple GERAN ARFCNs, some UEs may
not report CGIs. To address this, the number of GERAN ARFCNs that can be
included is modified in the 3GPP specifications. The GeranAnrMcOptSwitch
option of the GlobalProcSwitch.ProtocolMsgOptSwitch parameter specifies
whether the modification takes effect.
The length of time in which UEs perform CGI reading for event-triggered ANR
with GERAN is specified by the ANR.GeranEventAnrCgiTimer parameter. If a
UE fails to read the CGI of an adjacent cell within the length of time, the
eNodeB removes the measurement configuration related to CGI reading.
● NG-RAN measurement
When a UE detects that an NG-RAN cell meets the measurement
requirements, it reports the PCI of the cell to the source eNodeB. The source
eNodeB needs to check whether the NG-RAN cell has the strongest signal and
whether the NG-RAN cell is an unknown cell or a PCI-confusion neighboring
cell.
The ANR.EventAnrMode parameter specifies how the source eNodeB checks
whether a cell is an unknown cell or a PCI-confusion neighboring cell.
– When this parameter is set to NOT_BASED_NCL, the source eNodeB
proceeds to the next step if the combination of the operating frequency
and PCI of the NG-RAN cell does not exist in the NRT or is mapped to
multiple neighbor relationships in the NRT. Otherwise, the procedure
ends.
– When this parameter is set to BASED_NCL, the source eNodeB proceeds
to the next step if the combination of the operating frequency and PCI of
the NG-RAN cell does not exist in the NCL or is mapped to multiple
external cells in the NCL. Otherwise, the procedure ends.

eRAN
NOTE
If the ANR.EventAnrMode parameter is set to NOT_BASED_NCL, the ANR.OptMode

parameter is set to CONTROLLED, and the NCellParaCfg.CellAnrOptMode
parameter is set to CONTROLLED, then the optimization advice about adding the
neighbor relationship with a cell into an NRT is reported to the U2020. Maintenance
personnel determine whether to deliver the advice. Before maintenance personnel
confirm this optimization advice, the eNodeB instructs the UE to read the CGI of the
cell again if the PCI contained in an intra-RAT measurement report does not exist in
the NRT. To prevent performance deterioration due to CGI reading before handovers,
maintenance personnel are advised to handle the NRT optimization advice promptly
on the U2020.

If event-triggered ANR with UTRAN, GERAN, or NG-RAN detects a missing
neighboring cell, the eNodeB considers the settings of the following parameters to
add the detected cell to an NCL and to add the neighbor relationship with the
detected cell to an NRT of the source cell. The principle is the same as that for
intra-RAT event-triggered ANR.
● UTRAN: ANR.UtranEventAnrMode
● GERAN: ANR.GeranEventAnrMode
● NG-RAN: ANR.EventAnrMode
NOTE
According to the description of the trackingAreaCode field in section 6.3.2 "Radio

resource control information elements" in 3GPP TS 38.331 V15.7.0, an NG-RAN cell
supports only NSA if SIB1 does not contain a TAC. Therefore, if the CGI report sent by
the UE does not contain a TAC, the eNodeB sets the TAC to 4294967295 and the NR
architecture option to NSA when adding a cell to the NCL.

After a UE reports the CGI of a missing neighboring cell to an eNodeB, the
eNodeB checks whether the reported information about the detected cell is
consistent with the external cell information in the NCL. If they are inconsistent,
the eNodeB automatically synchronizes the NCL with the reported information.
The reported information varies with RATs.
● For a neighboring UTRAN cell, the information includes the downlink
UARFCN, scrambling code, LAC, RAC, PLMN list, and secondary frequency
band.
● For a neighboring GERAN cell, the information includes the BSIC, RAC, ARFCN,
and band indicator.
● For a neighboring NG-RAN cell, the information includes the downlink NR
Absolute Radio Frequency Channel Number (NR-ARFCN), PCI, and TAC.
In an NSA NG-RAN in NSA networking, the TAC is not broadcast in system
information. In this scenario, the UE does not report the TAC, and the eNodeB
does not automatically update the TAC.
The eNodeB checks whether inter-RAT external cells of the strongest intra-RAT cell
contained in the measurement report are configured with RACs when the
UtranUpdateRacSwitch or GeranUpdateRacSwitch option of the
ENodeBAlgoSwitch.AnrSwitch parameter is selected. If no, the eNodeB instructs

eRAN
the UE to perform CGI reading to re-obtain the RACs and updates the external cell
configurations.

The NCL/NRT entry removal function takes effect only after event-triggered ANR
is enabled. When an NCL or NRT has an inappropriate or redundant entry or the
number of NCL or NRT entries reaches its maximum, event-triggered ANR can
automatically remove an external cell or neighbor relationship if the following
conditions are met:
● For systems other than NG-RAN:
– The Control Mode parameter is set to AUTO_MODE.
– The No remove indicator parameter is set to PERMIT_RMV_ENUM.
● For NG-RAN:
– The CONTROL_MODE_FLAG option of the Aggregation Attribute
parameter is selected for the corresponding external cell.
– The CONTROL_MODE_FLAG and NO_REMOVE_FLAG options of the
Aggregation Attribute parameter are selected and deselected,
respectively, for the corresponding neighbor relationship.
Table 5-4 lists the parameters controlling the automatic removal functions.
Table 5-4 Parameters controlling the automatic removal functions

Function Specification-based Removal of Removal of
Removal Inappropriate Redundant Neighbor
Neighbor Relationships
Relationships
Inter-RAT UtranAutoNrtDele- ● UtranAutoNrt ● UtranAutoNrtDele

ANR with teSwitch option of DeleteSwitch teSwitch option of
UTRAN the option of the the
ENodeBAlgoSwitch. ENodeBAlgoS ENodeBAlgoSwitc
AnrSwitch witch.AnrSwit h.AnrSwitch
parameter ch parameter parameter
● UTRAN_DELER ● UTRAN_DELREDU
RORNCELL NDANCENCELL
option of the option of the
ANR.NrtDelM ANR.NrtDelMode
ode parameter parameter

eRAN
Function Specification-based Removal of Removal of

Removal Inappropriate Redundant Neighbor
Neighbor Relationships
Relationships
Inter-RAT GeranAutoNrtDele- ● GeranAutoNrt ● GeranAutoNrtDel

ANR with teSwitch option of DeleteSwitch eteSwitch option
GERAN the option of the of the
ENodeBAlgoSwitch. ENodeBAlgoS ENodeBAlgoSwitc
AnrSwitch witch.AnrSwit h.AnrSwitch
parameter ch parameter parameter
● GERAN_DELER ● GERAN_DELREDU
RORNCELL NDANCENCELL
option of the option of the
ANR.NrtDelM ANR.NrtDelMode
ode parameter parameter
Inter-RAT CdmaAutoNrtDele- Not supported Not supported

ANR with teSwitch option of
CDMA2000 the
(FDD) ENodeBAlgoSwitch.
AnrSwitch
parameter
Inter-RAT None Not supported NR_DELREDUNDANC

ANR with ENCELL option of the
NG-RAN ANR.NrtDelMode
parameter
NOTE
For details about the maximum number of external cells in an NCL and the maximum
number of neighbor relationships in an NRT, see the following commands in the MML
command reference.
● ADD GERANEXTERNALCELL
● ADD GERANNCELL
● ADD UTRANEXTERNALCELL
● ADD UTRANNCELL
● ADD CDMA20001XRTTEXTCELL (FDD)
● ADD CDMA2000HRPDEXTCELL (FDD)
● ADD CDMA20001XRTTNCELL (FDD)
● ADD CDMA2000HRPDNCELL (FDD)
● ADD NREXTERNALCELL
● ADD NRNRELATIONSHIP
Removal of Neighbor Relationships from an NRT

Removal of NCL/NRT entries by inter-RAT ANR is similar to that by intra-RAT ANR.
This section only describes the differences.

eRAN
● Specification-based removal
If event-triggered ANR with UTRAN, GERAN, CDMA2000, or NG-RAN is
enabled, a measurement period specified by the
ANR.StaPeriodForIRatNRTDel parameter starts.
The procedure for specification-based removal in inter-RAT ANR with UTRAN,
GERAN, and CDMA2000 is similar to that in intra-RAT ANR, as shown in
4.1.1.2.3 NCL/NRT Entry Removal.
At the end of a measurement period, the eNodeB generates a list of
candidate cells based on the following parameter settings after collecting
statistics of the period.
Parameter 1: ANR.StaNumForIRatNRTDel, which specifies the threshold of
the total number of handover attempts from the local cell to all its
neighboring cells of an RAT.
Parameter 2: ANR.UtranNcellHoForNRTDelThd or
ANR.GeranNcellHoForNRTDelThd, which specifies the threshold of the
number of handover attempts from the local cell to a neighboring cell
Figure 5-2 shows the specification-based removal procedure in ANR with NG-
RAN. The threshold is ANR.StaNumForIRatNRTDel.
Figure 5-2 Specification-based removal by ANR with NG-RAN
The algorithm of specification-based removal in inter-RAT ANR is the same as

that in intra-RAT event-triggered ANR, except that inter-RAT ANR does not
support the restriction on the number of neighboring cells on a frequency.
● Removal of inappropriate NCL/NRT entries
After the GeranAutoNrtDeleteSwitch or UtranAutoNrtDeleteSwitch option
is selected, event-triggered ANR with GERAN or UTRAN also requires that the

eRAN
GERAN_DELERRORNCELL or UTRAN_DELERRORNCELL option of the

ANR.NrtDelMode parameter be selected. If the number of handovers from a
cell (for example, cell A) served by the local eNodeB to a neighboring cell (for
example, cell B) reaches ANR.NcellHoStatNum and the handover success
rate is less than or equal to ANR.DelCellThd within a measurement period
specified by ANR.StatisticPeriod, the local eNodeB removes the neighbor
relationship of cell A with cell B. When the ANR.OptMode parameter is set to
CONTROLLED, the eNodeB reports the optimization advice to the U2020, and
operators determine whether to take the advice. When the parameter is set to
FREE, the eNodeB also removes cell B from the NCL if cell B has no
neighboring cell.
● Removal of redundant UTRAN, GERAN, or NG-RAN neighbor relationships
A neighbor relationship is redundant if the following conditions are met
within each of ANR.StatPeriodCoeff consecutive measurement periods
defined by ANR.StaPeriodForIRatNRTDel:
– The total number of times all inter-RAT neighboring cells are measured
by UEs in the local cell is greater than or equal to
ANR.StaNumForIRatNRTDel.
– The number of handovers from the local cell to this neighboring cell is 0.
– This neighboring cell has never been included in any measurement
report.
– At least one neighboring cell on the frequency of this neighboring cell is
included in a measurement report.
This removal function does not apply to the neighboring cells that meet any
of the following conditions:
– The blind-handover priority is set to a non-zero value.
– The Overlap Indicator parameter is set to YES.
– The No handover indicator parameter is set to FORBID_HO_ENUM.
– The Plmn List Type parameter is set to GREY_LIST.
– The Blind Configuration Indicator is set to TRUE.
NOTE
● The blind-handover priority, the Overlap Indicator parameter, and the Plmn List
Type parameter are inapplicable to NG-RAN.
● The Blind Configuration Indicator parameter is applicable to NG-RAN only.
● Penalty on removed neighbor relationships
When a neighbor relationship with a UTRAN or NG-RAN cell is automatically
removed by ANR, penalty on removed neighbor relationships can prevent this
neighbor relationship from being added back to the NRT within a short
period.
– The penalty mechanism is the same as that for removed neighbor
relationships with E-UTRAN cells. If the number of times a neighbor
relationship is required to be added to the NRT is greater than or equal
to ANR.UtranNcellDelPunNum within a measurement period defined by
ANR.NcellDelPunishPeriod, the eNodeB re-adds the neighbor
relationship to the NRT. Otherwise, the eNodeB does not re-add the
neighbor relationship to the NRT.

eRAN
– The penalty mechanism for removed neighbor relationships with NG-RAN

cells is the same as that for removed neighbor relationships with E-
UTRAN cells. For details, see 4.1.1.2.3 NCL/NRT Entry Removal.
Removal of External Cells from an NCL

After the inter-RAT event-triggered ANR with UTRAN, GERAN, NG-RAN and
neighbor relationship removal functions are enabled, a measurement period
specified by the ANR.StaPeriodForIRatNRTDel parameter starts. At the end of
four consecutive measurement periods (each specified by the
ANR.StaPeriodForIRatNRTDel parameter), the eNodeB removes the external cell
that has no neighbor relationships with any of the cells served by the local
eNodeB.
5.1.1.3 Fast ANR

Inter-RAT fast ANR is also known as inter-RAT periodic ANR. It detects missing
inter-RAT neighboring cells based on periodic UE measurement reports and adds
the missing neighboring cells. This function takes effect on a per base station, cell,
or frequency basis. For details, see 5.1.1.1.3 Method for NCL/NRT Management
to Take Effect.

Automatic detection of missing neighboring cells by inter-RAT ANR is similar to
that by intra-RAT ANR. This section only describes the differences. For details
about the similarities, see 4.1.1.3.1 Automatic Detection and Addition of
Missing Neighboring Cells.
The eNodeB selects a number of UEs to simultaneously perform fast ANR
measurements within a fast ANR check period. The maximum number of UEs is
specified by the ANR.FastAnrInterRatMeasUeNum parameter.
The following table lists the signal quality thresholds for the UTRAN, GERAN, and
NG-RAN.
RAT Signal Quality Threshold
UTRAN Received signal code power (RSCP) threshold,

specified by the ANR.FastAnrRscpThd
parameter
GERAN Received signal strength indicator (RSSI)

threshold, specified by the ANR.FastAnrRssiThd
parameter
NG-RAN Reference signal received power (RSRP)

threshold, specified by the
ANR.NrFastAnrRsrpThld parameter
If fast ANR with GERAN is enabled, it is recommended that the

ANR.FastAnrRprtAmount parameter not be set to r1. This is because a UE may

eRAN
report only the serving cell information in the first measurement report during
intra-RAT fast ANR and fast ANR with GERAN. According to section 5.5.4.1
"General" in 3GPP TS 36.331 V10.1.0, if purpose is set to reportStrongestCells,
the UE sends the first measurement report immediately after the quantity to be
reported becomes available for at least either the serving cell or one of the
adjacent cells. Therefore, this IE might include the information only about the
serving cell. A measurement report can contain multiple adjacent GERAN cells.
For fast ANR with UTRAN, the eNodeB sets purpose to

reportStrongestCellsForSON for fast ANR measurements. According to section
6.3.5 "Measurement information elements" of 3GPP TS 36.331 V10.1.0, when
purpose is set to reportStrongestCellsForSON, reportAmount takes the only value
1, which means that the UE sends only one measurement report to the eNodeB
when the reporting condition is met. In this case, the user-defined reporting
interval does not take effect. For the UEs to send periodic measurement reports,
the fast ANR algorithm reconfigures measurement IEs with purpose set to
reportStrongestCellsForSON for the UEs at a fixed interval of 5s. A measurement
report contains only one UTRAN cell.
Based on check results in a fast ANR check period, the eNodeB performs the
following:
● If an unknown cell is reported, the eNodeB sets the number of UEs that have
performed measurements in the check period to 0 and then selects a number
of UEs specified by the ANR.FastAnrInterRatMeasUeNum parameter to
perform measurements. If a UE reports multiple adjacent GERAN or NG-RAN
cells, the eNodeB instructs the UE to read the CGI of only the first cell. Then,
the eNodeB adds the detected cell to an NCL and NRT. For details about the
policies for adding the cell to the NCL and NRT, see Automatic Addition of
Missing Neighboring Cells.
● If no unknown cell is reported, the check period ends. The eNodeB checks the
total number of UEs that have performed measurements. If the total number
is less than the ANR.FastAnrInterRatUeNumThd parameter value, the
eNodeB starts the next round of fast ANR measurements. If the total number
is greater than or equal to the ANR.FastAnrInterRatUeNumThd parameter
value, the eNodeB enters the monitoring state.
Before the monitoring state period defined by
ANR.FastAnrMonitorStatePeriod elapses, the eNodeB does not select UEs for
fast ANR measurements but monitors whether event-triggered ANR
measurement reports contain the scrambling code, BSIC, or PCI of an
unknown UTRAN, GERAN, or NG-RAN cell, respectively. The eNodeB stays in
the monitoring state until it receives a measurement report that contains the
scrambling code, BSIC, or PCI of an unknown UTRAN, GERAN, or NG-RAN cell,
respectively. When the eNodeB exits the monitoring state, it starts fast ANR
measurements again. When the monitoring state period defined by
ANR.FastAnrMonitorStatePeriod elapses, the eNodeB automatically exits the
monitoring state.

When fast ANR detects a missing neighboring cell, the eNodeB adds this
neighboring cell to the NCL and the neighbor relationship with this cell to the
NRT.

eRAN
● Fast ANR with GERAN

– When the ANR.FastAnrMode parameter is set to NCL_NRT_MODE, the
eNodeB adds the strongest unknown neighboring GERAN cell to the NCL
and the neighbor relationship with this cell to the NRT. The eNodeB also
adds the second strongest unknown neighboring GERAN cell to the NCL.
– When the ANR.FastAnrMode parameter is set to NCL_MODE, the
eNodeB adds the strongest and second strongest unknown neighboring
GERAN cells to the NCL.
– When the ANR.FastAnrMode parameter is set to NRT_MODE, the
eNodeB instructs UEs to perform CGI reading and adds the strongest and
second strongest unknown neighboring GERAN cells to the NCL and the
neighbor relationships with these cells to the NRT based on the CGI
reading results instead of the information in the NCL.
NOTE
If the strongest neighboring cell is unknown, the eNodeB instructs UEs to read the CGI
of the strongest neighboring cell. If the strongest neighboring cell is already known,
the eNodeB instructs UEs to read the CGI of the second strongest neighboring cell.
● Fast ANR with UTRAN
eNodeB adds the strongest unknown neighboring UTRAN cell to the NCL
and NRT.
eNodeB adds the strongest unknown neighboring UTRAN cell to the NCL.
eNodeB instructs UEs to perform CGI reading and adds the strongest
unknown neighboring UTRAN cell to the NCL and the neighbor
relationship with the cell to the NRT based on the CGI reading results
instead of the information in the NCL.
● Fast ANR with NG-RAN
eNodeB adds the strongest unknown neighboring NG-RAN cell to the
NCL. In addition, it adds the neighbor relationship with this cell to the
NRT based on the NCL if this cell meets certain conditions.
eNodeB only adds the strongest unknown neighboring NG-RAN cell to
the NCL.
eNodeB instructs UEs to perform CGI reading and adds the strongest
unknown neighboring NG-RAN cell to the NCL and the neighbor
relationship with the cell to the NRT based on the CGI reading results
instead of the information in the NCL.

The eNodeB checks whether inter-RAT external cells of the strongest intra-RAT cell
contained in the measurement report are configured with RACs when the
UtranUpdateRacSwitch or GeranUpdateRacSwitch option of the
ENodeBAlgoSwitch.AnrSwitch parameter is selected. If no, the eNodeB instructs
the UE to perform CGI reading to re-obtain the RACs and updates the external cell
configurations.

eRAN
For details about other information, see 4.1.1.2.2 NCL Entry Modification.
5.1.1.4 Automatic Optimization of Neighbor Relationship Attributes

ANR automatically optimizes certain attributes of inter-RAT neighbor relationships
based on inter-RAT handover statistics. This function takes effect after event-
triggered ANR with UTRAN or GERAN is enabled.
5.1.1.4.1 Automatic Optimization of Blind Handover Priorities
Overview
ANR optimizes the UtranNCell.BlindHoPriority and GeranNcell.BlindHoPriority
parameter settings for neighbor relationships with UTRAN and GERAN cells,
respectively, based on inter-RAT handover statistics.
NOTE
For details about the definitions and usage of the blind handover priorities for neighbor
relationships with UTRAN and GERAN cells, see Mobility Management in Connected Mode.
This automatic optimization function includes the following:

● ANR automatically identifies the neighboring UTRAN or GERAN cells that
cover E-UTRAN cells and changes the blind handover priority for the neighbor
relationships with these UTRAN or GERAN cells from 0 to 1. Figure 5-3 shows
an example, in which the coverage area of a UTRAN or GERAN cell includes
that of an E-UTRAN cell. In this example, the UTRAN or GERAN cell can be
configured as the target cell for blind handovers from the E-UTRAN cell.
Therefore, ANR sets the blind handover priority to 1 for the neighbor
relationship of the E-UTRAN cell with the UTRAN or GERAN cell.
● After the network topology changes, the existing blind handover priorities
may become inappropriate, causing network performance deterioration. For
example, the blind handover success rate is low. In this case, ANR
automatically changes the blind handover priorities from a non-zero value to
0.
Figure 5-3 E-UTRAN cell in UTRAN/GERAN coverage
Automatic optimization of blind handover priorities for neighbor relationships with

UTRAN or GERAN cells is activated if the UtranBlindNcellOptSwitch or
GeranBlindNcellOptSwitch option of the
ENodeBAlgoSwitch.BlindNcellOptSwitch parameter is selected.
The optimization advice can be automatically delivered or requires manual
confirmation. For details, see 5.1.1.1.2 NRT Optimization Mode.

eRAN
Inter-RAT Handover Statistics Collection

After this automatic optimization function is enabled, a measurement period
specified by the BlindNcellOpt.StatisticPeriod parameter starts. Within the
measurement period, the eNodeB collects the performance counters related to
inter-RAT handovers to UTRAN or GERAN. For details, see 5.1.4.3 Network
Monitoring. The values of these performance counters are used as an input to
generate optimization advice.
The collection procedure is as follows:
1. Within a measurement period, the eNodeB counts the following data:

– Number of measurement-based handovers for circuit switched fallback
(CSFB) from the source E-UTRAN cell to each individual UTRAN
frequency or to each individual GERAN frequency group
– Number of measurement-based handovers for CSFB from the source E-
UTRAN cell to each individual neighboring UTRAN or GERAN cell
– Number of blind handover attempts from the source E-UTRAN cell to
each individual neighboring UTRAN or GERAN cell and number of
successful blind handovers among these attempts
– Number of measurement-based handover attempts from the source E-
UTRAN cell to each individual neighboring UTRAN or GERAN cell and
number of successful handovers among these attempts
2. At the end of the measurement period, the eNodeB calculates the following
data based on the preceding measurement values:
– Proportion of the number of measurement-based handovers for CSFB
from the source E-UTRAN cell to each individual neighboring UTRAN or
GERAN cell to the number of such handovers from the source E-UTRAN
cell to the operating UTRAN frequency or GERAN frequency group of the
neighboring cell, respectively
– Success rate of measurement-based handovers from the source E-UTRAN
cell to each individual neighboring UTRAN or GERAN cell
– Success rate of blind handovers from the source E-UTRAN cell to each
individual neighboring UTRAN or GERAN cell
NOTE
All the preceding data is measured on a per cell basis. The data is not operator-
specific in RAN sharing scenarios.
Generation of Optimization Advice for Blind Handover Priorities

● Changing the priority from 0 to 1
ANR changes the blind handover priority from 0 to 1 for a neighboring
UTRAN or GERAN cell that meets all the following conditions. For details
about related counters, see 5.1.4.3 Network Monitoring.
– The UtranNFreq.ContinuCoverageIndication or
GeranNfreqGroup.ContinuCoverageIndication parameter is set to
CONTINUOUS.
– Within the current measurement period, the number of measurement-
based handovers for CSFB from the source E-UTRAN cell to the operating

eRAN
UTRAN frequency or GERAN frequency group of the neighboring cell is

greater than the BlindNcellOpt.SampleNumThd parameter value.
– Within the current measurement period, the proportion of the number of
handovers for CSFB from the source E-UTRAN cell to the neighboring cell
in the number of measurement-based handovers for CSFB from the
source E-UTRAN cell to the operating UTRAN frequency or GERAN
frequency group of the neighboring cell is greater than or equal to the
BlindNcellOpt.CsfbHoAttempRatioThd parameter value.
– Within the current measurement period, the success rate of
measurement-based handovers from the source E-UTRAN cell to the
neighboring UTRAN or GERAN cell is greater than or equal to the
BlindNcellOpt.HoSuccRateThd parameter value.
● Changing the priority from a non-zero value to 0
ANR changes the blind handover priority from a non-zero value to 0 for a
neighboring UTRAN or GERAN cell that meets both of the following
conditions. For details about related counters, see 5.1.4.3 Network
Monitoring.
– The number of blind handover attempts from the source E-UTRAN cell to
the neighboring UTRAN or GERAN cell is greater than the
BlindNcellOpt.SampleNumThd parameter value.
– The success rate of blind handovers from the source E-UTRAN cell to the
neighboring UTRAN or GERAN cell is less than or equal to the
BlindNcellOpt.BlindHoSuccRateThd parameter value.
5.1.1.4.2 Automatic Optimization of Measurement Priorities

ANR optimizes the UtranNCell.NCellMeasPriority and
GeranNcell.NCellMeasPriority parameter settings for neighbor relationships with
UTRAN and GERAN cells based on inter-RAT neighboring cell measurement
statistics, respectively. A larger parameter value indicates a higher measurement
priority.
NOTE
For details about the definitions and usage of the measurement priorities for neighbor
relationships with UTRAN and GERAN cells, see Mobility Management in Connected Mode
and CS Fallback.
Automatic optimization of measurement priorities for neighbor relationships with

UTRAN and GERAN cells is activated if the UTRAN_SWITCH and GERAN_SWITCH
options of the ENodeBAlgoSwitch.NCellRankingSwitch parameter are selected,
respectively.
After this automatic optimization function is enabled, a measurement period

specified by the ANR.PeriodForNCellRanking parameter starts.
1. Within the measurement period, the eNodeB counts the number of times
each neighboring UTRAN or GERAN cell is contained in measurement reports
for circuit switched fallback (CSFB), redirection, and handover.
2. At the end of the period, the eNodeB optimizes the measurement priorities
for the neighbor relationships with UTRAN or GERAN cells based on the
statistics.

eRAN
– If a neighboring cell is not contained in any measurement report, the

eNodeB sets the measurement priority for the neighbor relationship with
this cell to 0.
– For neighboring cells contained in at least one measurement report, the
eNodeB sorts these neighboring cells by the number of times a
neighboring cell is contained in the measurement reports in ascending
order. If some cells are contained in the measurement reports for the
same number of times, the eNodeB sorts them randomly. Then, the
eNodeB sets the priorities for the neighbor relationships with the
neighboring cells at the Nth place in the order to N.
NOTE
The UtranNCell.NCellMeasPriority and GeranNcell.NCellMeasPriority parameters can be

manually configured as required for neighbor relationships with UTRAN and GERAN cells,
respectively. To keep the measurement priority of a neighboring cell after the manual
configuration, set the Control Mode to MANUAL_MODE for the neighboring cell during
the manual configuration.
5.1.1.5 NG-RAN NCL/NRT Self-Management Based on EN-DC X2 Messages

NG-RAN NCL/NRT self-management based on E-UTRA-NR Dual Connectivity (EN-
DC) X2 messages updates and removes NCL and NRT entries. This function takes
effect only after the NCellPlmnList.gNBIdLength parameter is configured.
Signaling Procedures
This function updates and removes NCL and NRT entries based on the signaling
procedures listed in Table 5-5.
Table 5-5 Signaling procedures used for NG-RAN NCL/NRT self-management

based on EN-DC X2 messages
Function Involved Signaling Procedures
NCL and NRT entry update ● Signaling procedure based on X2 setup

● Signaling procedure based on configuration
update
NCL and NRT entry removal Signaling procedure based on configuration

update
● Signaling procedure based on X2 setup

This procedure, as shown in Figure 5-4, only involves NCL and NRT entry
update.

eRAN
Figure 5-4 Signaling procedure based on X2 setup
When receiving an EN-DC X2 SETUP RESPONSE message, then:

– The eNodeB is triggered to update the external cells and neighbor
relationships based on the information about the NG-RAN cells contained
in the message if the MOD_NR_NCELL_CFG_SW option of the
– The eNodeB is triggered to update the architecture options for external
NG-RAN cells based on the information about the NG-RAN cells
contained in the message if the UPT_NR_EXT_CELL_NW_OPT_CFG_SW
option of the GlobalProcSwitch.X2BasedUptNcellCfgSwitch parameter
is selected.
● Signaling procedure based on configuration update
This procedure, as shown in Figure 5-5, involves the update and removal of
NCL and NRT entries.
Figure 5-5 Signaling procedure based on configuration update
A gNodeB periodically monitors whether its cell configuration changes. Within

each 3-minute period:
– If no cell configuration changes, the gNodeB enters the next monitoring
period, and the eNodeB takes no action.
– If its cell configuration changes, then:
If an NG-RAN cell is added or the configuration of an NG-RAN cell, such
as the PLMN ID, PCI, or NR-ARFCN, is changed, the gNodeB sends an EN-
DC CONFIGURATION UPDATE message over the EN-DC X2 interface to
inform the eNodeB of the change.

eRAN
When receiving the message, then:
▪ The eNodeB is triggered to update the existing external cells and

neighbor relationships based on the information about the NG-RAN
cells contained in the message if the MOD_NR_NCELL_CFG_SW
option of the GlobalProcSwitch.X2BasedUptNcellCfgSwitch
parameter is selected.
▪ The eNodeB is triggered to update the architecture options for

external NG-RAN cells based on the information about the NG-RAN
cells contained in the message if the
UPT_NR_EXT_CELL_NW_OPT_CFG_SW option of the
GlobalProcSwitch.X2BasedUptNcellCfgSwitch parameter is
selected.
NOTE
This function does not add a newly configured NG-RAN cell to the NRTs and
NCL.
If an NG-RAN cell is removed or deactivated, the gNodeB sends an EN-
DC CONFIGURATION UPDATE message over the EN-DC X2 interface to
inform the eNodeB of the change. When receiving the message, the
eNodeB is triggered to remove the external cell and neighbor
relationships based on the information about the NG-RAN cell contained
in the message if the DEL_NR_NCELL_CFG_SW option of the
NOTE
An EN-DC CONFIGURATION UPDATE message sent by a gNodeB contains only

the activated cells. If an NG-RAN cell becomes unavailable due to reasons such
as cell reestablishment, the gNodeB sends the eNodeB an EN-DC
CONFIGURATION UPDATE message carrying the IE Served NR Cells To Delete. As
a result, the eNodeB mistakenly removes the neighbor relationships with this NG-
RAN cell and the corresponding external NG-RAN cell. If ANR with NG-RAN is
not enabled on the LTE network or the number of UEs that support CGI reading
of NG-RAN cells is small, these mistakenly removed neighbor relationships and
external cell cannot be automatically added. Therefore, you are advised to
deselect the DEL_NR_NCELL_CFG_SW option of the
GlobalProcSwitch.X2BasedUptNcellCfgSwitch parameter in this scenario.
Effective Conditions
When the removal or update of NCL and NRT entries is triggered based on the
procedures described in Signaling Procedures, the eNodeB removes or updates
NCL and NRT entries based on the following principles:
● NCL and NRT entry update

The eNodeB updates the NCL corresponding to an NG-RAN cell and neighbor
relationships with the NG-RAN cell when all of the following conditions are
met. The parameters to be updated include downlink NR-ARFCN, PCI, NR
architecture option, and others.
– The CONTROL_MODE_FLAG option of the
NrExternalCell.AggregationAttribute parameter is selected for the
corresponding external cell.

eRAN
– The CONTROL_MODE_FLAG option of the

NrNRelationship.AggregationAttribute parameter is selected for the
corresponding neighbor relationships.
● NCL and NRT entry removal
– The eNodeB removes the external cell corresponding to an NG-RAN cell
and neighbor relationships with the NG-RAN cell when all of the
following conditions are met:
▪ The information about the NG-RAN cell, which is contained in the

Served Cells To Delete IE of the EN-DC CONFIGURATION UPDATE
message, exists in both the NCL of the eNodeB and at least one NRT
of the eNodeB.
▪ The CONTROL_MODE_FLAG option of the

▪ The CONTROL_MODE_FLAG and NO_REMOVE_FLAG options of the

NrNRelationship.AggregationAttribute parameter are selected and
deselected, respectively, for the corresponding neighbor relationships.
– The eNodeB removes the neighbor relationships with an NG-RAN cell
when all of the following conditions are met:

message, exists in at least one NRT of the eNodeB.
▪ The CONTROL_MODE_FLAG and NO_REMOVE_FLAG options of the

NrNRelationship.AggregationAttribute parameter are selected and
deselected, respectively, for the corresponding neighbor relationships.
– The eNodeB removes the external cell corresponding to an NG-RAN cell
when all of the following conditions are met:

message, exists in the NCL of the eNodeB.
▪ The CONTROL_MODE_FLAG option of the

NOTE
If the information about an NG-RAN cell contained in the Served Cells To Delete IE of
the EN-DC CONFIGURATION UPDATE message exists in the NRTs of multiple cells
served by the eNodeB and at least one of the corresponding neighbor relationships
does not meet the preceding NRT entry removal condition, the eNodeB does not
remove any neighbor relationship with this NG-RAN cell.
5.1.2.1 Benefits
Inter-RAT ANR handles neighbor relationships of E-UTRAN cells with UTRAN,
GERAN, CDMA2000 (FDD), and NG-RAN cells. It automatically maintains the

eRAN
completeness, validity, and correctness of the neighbor relationships to improve

network performance. In addition, inter-RAT ANR automatically optimizes the
attributes of neighbor relationships, reducing manual intervention while
decreasing the costs of network planning, network optimization, and O&M.
Inter-RAT ANR has a similar impact on network performance as intra-RAT ANR.

The difference is that inter-RAT ANR increases the inter-RAT handover success
rates, involving the following KPIs:
● Inter-RAT Handover Out Success Rate (LTE to WCDMA)
● Inter-RAT Handover Out Success Rate (LTE to GSM)
provided.
● New deployment
– Inter-RAT event-triggered ANR
It is recommended that removal of redundant neighbor relationships with
inter-RAT cells be disabled. Otherwise, neighbor relationships may be
unexpectedly removed because the number of UEs in handovers is small.
– (Optional) Inter-RAT fast ANR
It is recommended that inter-RAT fast ANR be enabled only when the
network serves a small number of commercial UEs or engineering
optimization (for example, downtilt adjustment and power adjustment)
has not finished. It is recommended that this sub-function be disabled
when the network serves a large number of commercial UEs and
engineering optimization has finished.
– Automatic optimization of blind handover priorities for inter-RAT
It is recommended that this function be enabled in circuit switched
fallback (CSFB) based on PS handover scenarios to reduce manual
intervention in planning the blind handover priorities.
– It is recommended that automatic optimization of blind handover
priorities for inter-RAT neighbor relationships be enabled during site
expansion or migration. Enable other functions according to operators'
policies.
– It is recommended that automatic optimization of blind handover
priorities for inter-RAT neighbor relationships be enabled in CSFB based
on PS handover scenarios to reduce manual intervention in planning the
blind handover priorities.
5.1.2.2 Impacts
Network Impacts
● When the UtranUpdateRacSwitch or GeranUpdateRacSwitch option of the
ENodeBAlgoSwitch.AnrSwitch parameter is selected, UEs are instructed to
perform CGI reading if the UTRAN or GERAN cells are not configured with
RACs. This affects the service drop rate.

eRAN
NOTE
For ANR with UTRAN, if maintenance personnel do not confirm the optimization
advice about adding the neighbor relationship with a UTRAN cell reported to the
U2020, UEs cannot be handed over to the UTRAN cell. In this case, ANR with UTRAN
neither decreases the service drop rate nor increases the EUTRAN-to-UTRAN handover
success rate.
● Impacts on the NG-RAN are as follows:
During the detection of unknown neighboring cells, the eNodeB instructs UEs
that fulfill certain conditions to perform measurements for ANR. In Non-
Standalone (NSA) scenarios, this prolongs the delay on adding SCGs for UEs.
In SA scenarios, this prolongs the delay on redirections to NG-RAN cells. After
the neighbor relationships with the detected neighboring cells are added,
measurements for ANR are not triggered during subsequent SCG additions or
redirections for the UEs. Therefore, measurements for ANR do not result in a
long delay on SCG additions or redirections.
In FDD, this function also has the following impacts:
● ANR with CDMA2000 can optimize neighbor relationships with CDMA2000
cells and reduce service drops and handover failures caused by neighbor
relationship problems. This decreases the service drop rate and increases the
inter-RAT handover success rate. Related KPIs include:
– Inter-RAT Handover Out Success Rate (LTE to CDMA2000)
– Service Drop Rate
● ANR with CDMA2000 prolongs the delay in the handover of a UE that meets
the handover conditions but is still performing ANR measurements to detect
unknown cells. In addition, this function negatively affects UE throughput
because UEs in the DRX state cannot be scheduled while they are reading the
CGI of an unknown cell.
Function Impacts
Name Switch e
FDD CA cell None Carrier Currently, if the E-UTRAN

TDD Aggregati supports CA (included in LTE-A
on Introduction) according to
eNodeB configurations and UE
capabilities, the eNodeB does
not select certain CA UEs to
perform measurements for
inter-RAT event-triggered ANR
or fast ANR. The CA UE
selection rule is specified by
the ANR.CaUeChoseMode
parameter.

eRAN

Name Switch e
FDD SPID- INTER_FREQ_ Flexible SPID-based UMTS frequency

TDD based LIST_CTL_SW User filtering has been added to
camping and Steering UMTS measurement object
and L2U_FREQ_LI selection for event-triggered
handover ST_CTL_SW ANR.
options of the
CellAlgoSwit
ch.SpidSpecif
icHoSwitch
parameter
FDD UMTS UMTS_LTE_ZE UMTS A UMTS cell must be added as

and LTE RO_BUFFER_ and LTE a neighboring cell of an LTE
Zero ZONE_SW Zero cell in the buffer zone. When
Bufferzon option of the Bufferzon the inter-RAT ANR function is
e ULZeroBuffer e enabled, the neighboring
zone.ZeroBuf UMTS cells in the buffer zone
ZoneSwitch may be deleted if the number
parameter of neighboring UMTS cells of
the LTE cell reaches the
maximum. Therefore,
UtranNCell.NoRmvFlag must
be set to
FORBID_RMV_ENUM for
neighboring UMTS cells with
close interference.
5.1.3 Requirements
5.1.3.1 Licenses
Name
FDD LOFD-002002 Inter-RAT LT1S00IANR00 Per Cell

ANR
TDD TDLOFD-0020 Inter-RAT LT1STRTANR00 Per Cell

02 ANR
5.1.3.2 Software

eRAN
Name Switch e
FDD Inter-RAT None None This is a function of the

TDD Automati U2020.
c
Neighbor
Relation
Optimizat
ion - LTE
FDD DRX None DRX and ANR with CDMA2000 requires

Signaling LBFD-002017 DRX. To perform
Control ANR-related measurements,
each UE must be configured
with a temporary DRX
parameter dedicated to the
measurement. For details
about DRX and its
configuration, see DRX and
Signaling Control.

None
5.1.3.3 Hardware
Base Station Models

No requirements
Boards
The LMPT does not support this function.
RF Modules
No requirements
Cells
● The inter-RAT ANR measurement information (including frequencies to be
measured) has been configured. For ANR with UTRAN, the UtranNFreq MO
has been configured. For ANR with GERAN, the GeranNfreqGroup and
GeranNfreqGroupArfcn MOs have been configured. For ANR with NG-RAN,
the NrNFreq MO has been configured. For details, see Mobility Management
in Connected Mode.
● To use automatic optimization of blind handover priorities of inter-RAT
neighbor relationships, operators must enable the PS handover function and

eRAN
select the PS_HO option of the CSFallBackPolicyCfg.CsfbHoPolicyCfg

parameter. For details, see CS Fallback.
5.1.3.4 Others
Inter-RAT ANR requires that UEs on the network be DRX-capable and support
inter-RAT measurements for ANR.
ANR with NG-RAN requires NG-RAN cells to broadcast SIB1 in areas with ANR
enabled.
5.1.4.1.1 Process
The deployment process for inter-RAT ANR varies with network deployment
stages.
eNodeB Deployment
The deployment process for inter-RAT ANR during eNodeB deployment is
illustrated in Figure 5-6/Figure 5-7.

eRAN
Figure 5-6 Deployment process for inter-RAT ANR (FDD)

eRAN
Figure 5-7 Deployment process for inter-RAT ANR (TDD)

The deployment process for inter-RAT ANR during site expansion or migration is
illustrated in Figure 5-8/Figure 5-9.

eRAN
Figure 5-8 Deployment process for inter-RAT ANR (FDD)

eRAN
Figure 5-9 Deployment process for inter-RAT ANR (TDD)
NCL/NRT Control Mode


eRAN

Name
Control Mode UtranExternalCel None This parameter

l.CtrlMode specifies the control
mode of an external
UTRAN cell.
Control Mode UtranNCell.CtrlM None This parameter

ode specifies the control
mode of a
neighboring
relationship with a
UTRAN cell.
Control Mode UtranBlkNCell.Ct None This parameter

rlMode specifies the control
mode of a blacklisted
neighboring UTRAN
cell.
Control Mode GeranExternalCel None This parameter

l.CtrlMode specifies the control
mode of an external
GERAN cell.
Control Mode GeranNcell.CtrlM None This parameter

ode specifies the control
mode of a
neighboring
relationship with a
GERAN cell.
Aggregation NrExternalCell.A CONTROL_MODE The

Attribute ggregationAttri- _FLAG CONTROL_MODE_FL
bute AG option specifies
the control mode of
an external NG-RAN
cell.
Aggregation NrNRelationship. CONTROL_MODE The

Attribute AggregationAttri _FLAG CONTROL_MODE_FL
bute AG option specifies
the control mode of a
with an NG-RAN cell.
NRT Optimization Mode


eRAN

Name
Optimization ANR.OptMode Set this parameter to FREE or

Mode CONTROLLED based on the operator's
policy.
Cell ANR NCellParaCfg.Cel None

Optimization lAnrOptMode
Mode
Method for NCL/NRT Management to Take Effect


Name
ANR UtranNFreq.AnrI None Set this parameter to

Indication nd NOT_ALLOWED or
ALLOWED based on
ANR GeranNfreqGrou None Set this parameter to

Indication p.AnrInd NOT_ALLOWED or
ALLOWED based on

eRAN

Name
ANR Function CellAlgoSwitch.A INTER_RAT_ANR_ To enable the

Switch nrFunctionSwitc SW following functions,
h you are advised to
select the
INTER_RAT_ANR_SW
option:
● Neighbor
relationship
addition in event-
triggered ANR with
GERAN and UTRAN
● Removal of
inappropriate
NCL/NRT entries
and specification-
based removal in
inter-RAT ANR with
GERAN and UTRAN
● Fast ANR with
GERAN and UTRAN
● Fast ANR with NG-
RAN
ANR Function CellAlgoSwitch.A NR_EVENT_ANR_ To enable neighbor

Switch nrFunctionSwitc SW relationship addition
h by event-triggered
ANR with NG-RAN,
you are advised to
select the
NR_EVENT_ANR_SW
option.
ANR CellAlgoSwitch.A LTE_AUTON_GAP To enable CGI reading

Algorithm nrAlgoSwitch _CGI_SW using autonomous
Switch gaps, select the
LTE_AUTON_GAP_CGI
_SW option.
Aggregation NrNFreq.Aggrega ANR_INDICATIO Set the

Attribute tionAttribute N ANR_INDICATION
option based on the
operator's policy.

eRAN

Name
gNodeB ID NCellPlmnList.gN None This parameter must

Length BIdLength be set based on
network plan to
enable the following
functions: event-
triggered ANR with
NG-RAN, fast ANR
with NG-RAN, and
NG-RAN NCL/NRT
self-management
based on EN-DC X2
messages.
The parameter value
must be consistent
with the ID lengths of
all gNodeBs of a
PLMN in the NG-RAN.
Event-triggered ANR

Name
ANR ENodeBAlgoSwit UtranEventAnrS To enable neighbor

algorithm ch.AnrSwitch witch relationship addition
switch GeranEventAnrS by inter-RAT event-
witch triggered ANR, you
CdmaEventAnrS the following options:
witch (FDD)
● UtranEventAnrSwi
UtranUpdateRac tch
Switch
● GeranEventAnrSw
GeranUpdateRac itch
Switch
● CdmaEventAnrSwi
tch (FDD)
● UtranUpdateRacS-
witch
● GeranUpdateRacS
witch

eRAN

Name
Handover ENodeBAlgoSwit McUtranNcellNu To enable neighbor

Signaling ch.HoSignalingO mOptSwtich relationship addition
Optimized ptSwitch by event-triggered
Switch ANR with UTRAN, you
the
McUtranNcellNumO
ptSwtich option.
Protocol GlobalProcSwitc GeranAnrMcOptS To enable neighbor

Message h.ProtocolMsgOp witch relationship addition
Optimization tSwitch by event-triggered
Switch ANR with GERAN, you
the
GeranAnrMcOptSwit
ch option.
Utran Event ANR.UtranEvent None This parameter

ANR Mode AnrMode specifies the policy
based on which inter-
RAT event-triggered
ANR with UTRAN
adds a neighbor
relationship to an
NRT. If adjacent cells
of an eNodeB share
PSCs, you are advised
to set this parameter
to NOT_BASED_NCL
to prevent
inappropriate
from being added to
NRTs. With this
eNodeB does not add
a neighbor
based on the
neighboring cell
information in the
reported CGI.

eRAN

Name
Geran Event ANR.GeranEvent None This parameter

ANR Mode AnrMode specifies the policy
RAT event-triggered
ANR with GERAN
adds a neighbor
relationship to an
NRT. If adjacent cells
of an eNodeB share
PCIs, you are advised
to set this parameter
to NOT_BASED_NCL
to prevent
inappropriate
from being added to
NRTs. With this
eNodeB does not add
a neighbor
based on the
neighboring cell
information in the
reported CGI.
Event ANR ANR.EventAnrMo None This parameter

Mode de specifies the policy
RAT event-triggered
ANR with NG-RAN
adds a neighbor
relationship to an
NRT.
Long DRX CellDrxSpecialPa None ● If a UTRAN or

Cycle for ra.LongDrxCycleF CDMA2000
Inter-RAT orInterRatAnr network (FDD)
ANR exists, set this
parameter to
SF1280.
● If a GERAN exists,
set this parameter
to SF2560.
● If an NG-RAN
exists, set this
parameter to
SF1280.

eRAN

Name
Statistic Cycle ANR.StatPeriodC A larger value of this parameter results in

Coefficient oeff a longer time to remove a redundant
neighbor relationship from an NRT.
Event ANR ANR.EventAnrWi This parameter controls whether an

With VoIP thVoipMode eNodeB selects UEs with QCI-1 bearers to
Mode perform measurements for event-triggered
ANR with UTRAN or GERAN.
UTRAN Event ANR.UtranEvent A larger value of this parameter results in

ANR CGI AnrCgiTimer a longer time for UEs to perform CGI
Timer reading for event-triggered ANR with
UTRAN and a higher success rate of CGI
reading. However, a larger value of this
parameter results in a longer scheduling
delay, affecting user experience.
a shorter time for UEs to perform CGI
reading for event-triggered ANR with
UTRAN and a lower success rate of CGI
reading.
GERAN Event ANR.GeranEvent A larger value of this parameter results in

ANR CGI AnrCgiTimer a longer time for UEs to perform CGI
Timer reading for event-triggered ANR with
GERAN and a higher success rate of CGI
reading. However, a larger value of this
parameter results in a longer scheduling
delay, affecting user experience.
a shorter time for UEs to perform CGI
reading for event-triggered ANR with
GERAN and a lower success rate of CGI
reading.
NCL/NRT Entry Removal


eRAN

Name
ANR ENodeBAlgoSwit UtranAutoNrtDel To enable removal of

algorithm ch.AnrSwitch eteSwitch inappropriate
switch GeranAutoNrtDel NCL/NRT entries and
eteSwitch specification-based
removal in inter-RAT
CdmaAutoNrtDel ANR, select the
eteSwitch (FDD) following options:
● UtranAutoNrtDele
teSwitch
● GeranAutoNrtDel
eteSwitch
● CdmaAutoNrtDele
teSwitch (FDD)
NRT Delete ANR.NrtDelMode UTRAN_DELERR To enable removal of

Mode ORNCELL inappropriate
GERAN_DELERRO NCL/NRT entries and
RNCELL specification-based
removal in inter-RAT
ANR, select the
following options:
● UTRAN_DELERRO
RNCELL
● GERAN_DELERRO
RNCELL
NRT Delete ANR.NrtDelMode UTRAN_DELRED To enable removal of

Mode UNDANCENCELL redundant NCL/NRT
GERAN_DELREDU entries in inter-RAT
NDANCENCELL ANR, select the
following options:
NR_DELREDUND
ANCENCELL ● UTRAN_DELREDU
NDANCENCELL
● GERAN_DELREDU
NDANCENCELL
● NR_DELREDUNDA
NCENCELL
Neighbor Cell ANR.NcellDelPun None The recommended

Deletion ishPeriod value is 10080.
Punish Period

eRAN

Name
UTRAN ANR.UtranNcellD None If this parameter is set

Neighbor Cell elPunNum to 1, penalty on
Deletion removed neighbor
Punish relationships in ANR
Number with UTRAN does not
take effect. If this
parameter is set to a
this function takes
effect.
The recommended
value is 10.
EUTRAN ANR.EutranNcell None If this parameter is set

Neighbor Cell DelPunNum to 1, the penalty
Deletion function does not take
Punish effect. If this
Number parameter is set to a
this function takes
effect.
Set this option to its
recommended value.

Name
Neighbor Cell ANR.NcellDelPun A smaller value of this parameter indicates

Deletion ishPeriod a shorter penalty period of removed
Punish Period neighbor relationships and results in a
lower probability that removed neighbor
relationships can be re-added to NRTs by
ANR and more stable NRTs. A larger value
of this parameter results in the opposite
effects.
UTRAN ANR.UtranNcellD This parameter specifies the number of

Neighbor Cell elPunNum times penalty statistics about neighboring
Deletion UTRAN cell removal are collected. When a
Punish neighbor relationship with a UTRAN cell is
Number removed, it can be added to the NRT again
if the number of times additions of the
neighbor relationship are triggered is
greater than or equal to the value of this
parameter.

eRAN

Name
Long DRX CellDrxSpecialPa This parameter specifies the long DRX

Cycle for ra.LongDrxCycleF cycle for inter-RAT ANR.
Inter-RAT orInterRatAnr A larger value of this parameter results in
ANR a longer duration for UEs to perform CGI
reading and a longer system delay.
To ensure the CGI reading success rate, you
are advised to set the long DRX cycle to a
time period greater than or equal to 256
ms.
Fast ANR

Name
ANR ENodeBAlgoSwit UtranFastAnrSwi To configure fast ANR

algorithm ch.AnrSwitch tch with UTRAN and
switch GeranFastAnrSwi GERAN, you are
tch advised to select the
following options:
● UtranFastAnrSwit
ch
● GeranFastAnrSwit
ch

eRAN

Name
NR Fast ANR ANR.NrFastAnrRs None To configure fast ANR

RSRP rpThld with NG-RAN, set this
Threshold parameter to a non-
zero value.
A larger value of this
higher RSRP
requirement and
therefore higher RSRP
of the neighboring
cells in the NCL.
● In densely
populated urban
areas, increase the
value of this
parameter to
reduce the
probability of
adding neighboring
cells with low RSRP
to the NCL.
● In sparsely
populated areas,
reduce the value of
this parameter to
increase the
probability of
adding neighboring
cells with low RSRP
to the NCL.
Fast ANR PCI ANR.FastAnrRprt None Retain the default

report Amount value.
amount
Fast ANR ANR.FastAnrMon None Set the parameter to

Monitoring itorStatePeriod its recommended
State Period value.

eRAN

Name
InterRat Fast ANR.FastAnrInter A larger value of this parameter results in

ANR RatMeasUeNum more accurate NCL/NRT entry addition but
measurement a greater negative impact on UEs' QoS and
UE number uplink network traffic volume.
InterRat Fast ANR.FastAnrInter A larger value of this parameter results in

ANR valid RatUeNumThd more accurate NCL/NRT entry addition but
measurement a greater negative impact on UEs' QoS and
min UE uplink network traffic volume.
number
UTRAN Fast ANR.FastAnrRscp A larger value of this parameter results in

ANR RSCP Thd a higher RSCP requirement and therefore
threshold higher RSCP of the neighboring cells in the
NCL.
neighboring cells with low RSCP to the
NCL.
with low RSCP to the NCL.
GERAN Fast ANR.FastAnrRssi A larger value of this parameter results in

ANR RSSI Thd a higher RSSI requirement and therefore
threshold higher RSSI of the neighboring cells in the
NCL.
neighboring cells with low RSSI to the
NCL.
with low RSSI to the NCL.
Automatic Optimization of Neighbor Relationship Attributes


eRAN

Name
Blind Ncell ENodeBAlgoSwit GeranBlindNcell To enable automatic

Optimization ch.BlindNcellOpt OptSwitch optimization of blind
Switch Switch UtranBlindNcell handover priorities for
OptSwitch neighbor relationships
with inter-RAT cells,
select the following
options:
● GeranBlindNcellO
ptSwitch
● UtranBlindNcellO
ptSwitch
Neighboring ENodeBAlgoSwit GERAN_SWITCH To enable automatic

Cell Ranking ch.NCellRanking UTRAN_SWITCH optimization of
Switch Switch measurement
priorities for neighbor
relationships with
inter-RAT cells, select
the following options:
● GERAN_SWITCH
● UTRAN_SWITCH

Name
Period for ANR.PeriodForNC A larger value of this parameter results in

Neighboring ellRanking more samples.
Cell Ranking For a network that serves a large number
of UEs, reduce the value of this parameter
to accelerate measurement priority
updates.
Statistic BlindNcellOpt.St When operators configure automatic

Period atisticPeriod optimization of blind handover priorities, a
larger value of this parameter results in
more samples. For a network that serves a
large number of UEs, reduce the value of
this parameter to accelerate NRT updates.

eRAN

Name
Sample BlindNcellOpt.Sa When operators configure automatic

Number mpleNumThd optimization of blind handover priorities, a
Threshold larger value of this parameter results in a
larger number of required samples within
a measurement period and a lower
probability of optimizing blind handover
priorities.
Handover BlindNcellOpt.Ho When operators configure automatic

Success Ratio SuccRateThd optimization of blind handover priorities, a
Threshold larger value of this parameter results in a
lower probability of allowing blind
handovers to a neighboring cell.
It is recommended that this parameter be
set to a value of at least 98% to prevent
failures of handovers for CSFB.
CSFB BlindNcellOpt.Cs When operators configure automatic

Handover fbHoAttempRati optimization of blind handover priorities, a
Attemption oThd larger value of this parameter results in a
Ratio lower probability of allowing blind
Threshold handovers to a neighboring cell.
Blind BlindNcellOpt.Bli When operators configure automatic

Handover ndHoSuccRateTh optimization of blind handover priorities, a
Success Ratio d larger value of this parameter results in a
Threshold higher probability of prohibiting blind
handovers to a neighboring cell.
Blacklists and Whitelist


Name
No handover UtranNCell.NoHo None Set this parameter to

indicator Flag FORBID_HO_ENUM
when configuring an
HO blacklist.
PERMIT_HO_ENUM
when configuring an
HO whitelist.

eRAN

Name
No remove UtranNCell.NoR None Set this parameter to

indicator mvFlag FORBID_RMV_ENUM
when configuring an
HO whitelist or
blacklist.
No handover GeranNcell.NoHo None Set this parameter to

indicator Flag FORBID_HO_ENUM
when configuring an
HO blacklist.
PERMIT_HO_ENUM
when configuring an
HO whitelist.
No remove GeranNcell.NoR None Set this parameter to

indicator mvFlag FORBID_RMV_ENUM
when configuring an
HO whitelist or
blacklist.
Aggregation NrNRelationship. NO_REMOVE_FL Set this parameter to

Attribute AggregationAttri AG NO_REMOVE_FLAG
bute when configuring an
HO whitelist or
blacklist.
NG-RAN NCL/NRT Self-Management based on EN-DC X2 Messages


Name
X2-based GlobalProcSwitc MOD_NR_NCELL_ This option specifies

Neighboring h.X2BasedUptNc CFG_SW whether to modify
Cell ellCfgSwitch NG-RAN neighbor
Configuration relationships based on
Update EN-DC X2 messages.
Switch
X2-based GlobalProcSwitc UPT_NR_EXT_CEL This option specifies

Neighboring h.X2BasedUptNc L_NW_OPT_CFG_ whether to update the
Cell ellCfgSwitch SW architecture options
Configuration for external NG-RAN
Update cells based on EN-DC
Switch X2 messages.

eRAN

Name
X2-based GlobalProcSwitc DEL_NR_NCELL_C This option specifies

Neighboring h.X2BasedUptNc FG_SW whether to remove
Cell ellCfgSwitch NG-RAN neighbor
Configuration relationships based on
Update EN-DC X2 messages.
Switch
Activation Command Examples (FDD)

MOD UTRANNFREQ: LocalCellId=xx, UtranDlArfcn=xx, AnrInd=ALLOWED;
MOD GERANNFREQGROUP: LocalCellId=xx, BcchGroupId=xx, AnrInd=ALLOWED;
MOD NRNFREQ: LocalCellId=xx, DlArfcn=xx, AggregationAttribute=ANR_INDICATION-1;
//Activating neighbor relationship addition in inter-RAT event-triggered ANR with GERAN

MOD ENODEBALGOSWITCH: AnrSwitch=GeranEventAnrSwitch-1;
MOD CELLALGOSWITCH: LocalCellId=xx, AnrFunctionSwitch=INTER_RAT_ANR_SW-1;
MOD GLOBALPROCSWITCH: ProtocolMsgOptSwitch=GeranAnrMcOptSwitch-1;
MOD ANR: GeranEventAnrMode=NOT_BASED_NCL;
//Activating neighbor relationship addition in inter-RAT event-triggered ANR with UTRAN

MOD ENODEBALGOSWITCH: AnrSwitch=UtranEventAnrSwitch-1;
MOD ENODEBALGOSWITCH: HoSignalingOptSwitch=McUtranNcellNumOptSwtich-1;
MOD ANR: UtranEventAnrMode=NOT_BASED_NCL;
//Activating neighbor relationship addition in inter-RAT event-triggered ANR with CDMA2000

MOD ENODEBALGOSWITCH: AnrSwitch=CdmaEventAnrSwitch-1;
//Activating neighbor relationship addition in inter-RAT event-triggered ANR with NG-RAN

MOD CELLALGOSWITCH: LocalCellId=xx, AnrFunctionSwitch=NR_EVENT_ANR_SW-1;
ADD NCellPlmnList: Mcc="xx", Mnc="xx", RatType=NR, gNBIdLength=xx;
//Activating removal of inappropriate NCL/NRT entries and specification-based removal in inter-RAT ANR
MOD ENODEBALGOSWITCH: AnrSwitch=UtranAutoNrtDeleteSwitch-1;
MOD ANR: NrtDelMode=UTRAN_DELERRORNCELL-1;
MOD ENODEBALGOSWITCH: AnrSwitch=GeranAutoNrtDeleteSwitch-1;
MOD ANR: NrtDelMode=GERAN_DELERRORNCELL-1;
MOD ENODEBALGOSWITCH: AnrSwitch=CdmaAutoNrtDeleteSwitch-1;
//Activating removal of redundant NCL/NRT entries in intra-RAT ANR with NG-RAN

MOD ANR: NrtDelMode=NR_DELREDUNDANCENCELL-1;
//Deactivating removal of redundant NCL/NRT entries in inter-RAT ANR with UTRAN and GERAN
MOD ANR: NrtDelMode=UTRAN_DELREDUNDANCENCELL-0;
MOD ANR: NrtDelMode=GERAN_DELREDUNDANCENCELL-0;
//Activating penalty on removed neighbor relationships with UTRAN cells

MOD ANR: NcellDelPunishPeriod=xx, UtranNcellDelPunNum=xx;
//Activating penalty on removed neighbor relationships with NG-RAN cells


eRAN
//Activating inter-RAT fast ANR with GERAN

MOD ENODEBALGOSWITCH: AnrSwitch=GeranFastAnrSwitch-1;
//Activating inter-RAT fast ANR with UTRAN

MOD ENODEBALGOSWITCH: AnrSwitch=UtranFastAnrSwitch-1;
//Activating inter-RAT fast ANR with NG-RAN

MOD ANR: NrFastAnrRsrpThld=xx;
//Activating automatic optimization of blind handover priorities for inter-RAT neighbor relationships
MOD ENODEBALGOSWITCH: BlindNcellOptSwitch=UtranBlindNcellOptSwitch-1;
MOD ENODEBALGOSWITCH: BlindNcellOptSwitch=GeranBlindNcellOptSwitch-1;
//Activating automatic optimization of measurement priorities for inter-RAT neighbor relationships

MOD ENODEBALGOSWITCH: NCellRankingSwitch=UTRAN_SWITCH-1;
MOD ENODEBALGOSWITCH: NCellRankingSwitch=GERAN_SWITCH-1;

ADD UTRANNCELL: LocalCellId=0, Mcc="460", Mnc="00", RncId=123, CellId=0,
ADD GERANNCELL: LocalCellId=0, Mcc="460", Mnc="00", Lac=1, GeranCellId=0,
NoRmvFlag=FORBID_RMV_ENUM, NoHoFlag=FORBID_HO_ENUM;
NoRmvFlag=FORBID_RMV_ENUM, NoHoFlag=PERMIT_HO_ENUM;
//Activating inter-RAT RAC update

MOD ENODEBALGOSWITCH: AnrSwitch=UtranUpdateRacSwitch-1;
MOD ENODEBALGOSWITCH: AnrSwitch=GeranUpdateRacSwitch-1;

//Activating NG-RAN NCL/NRT self-management based on EN-DC X2 messages

MOD GLOBALPROCSWITCH: X2BasedUptNcellCfgSwitch=MOD_NR_NCELL_CFG_SW-1;
MOD GLOBALPROCSWITCH: X2BasedUptNcellCfgSwitch=UPT_NR_EXT_CELL_NW_OPT_CFG_SW-1;
MOD GLOBALPROCSWITCH: X2BasedUptNcellCfgSwitch=DEL_NR_NCELL_CFG_SW-1;
Activation Command Examples (TDD)

MOD UTRANNFREQ: LocalCellId=xx, UtranDlArfcn=xx, AnrInd=ALLOWED;
MOD GERANNFREQGROUP: LocalCellId=xx, BcchGroupId=xx, AnrInd=ALLOWED;
//Activating neighbor relationship addition in inter-RAT event-triggered ANR with GERAN

MOD ANR: GeranEventAnrMode=NOT_BASED_NCL;
//Activating neighbor relationship addition in inter-RAT event-triggered ANR with UTRAN

MOD ANR: UtranEventAnrMode=NOT_BASED_NCL;
//Activating neighbor relationship addition in inter-RAT event-triggered ANR with NG-RAN


eRAN
//Activating removal of inappropriate NCL/NRT entries and specification-based removal in inter-RAT ANR
//Activating removal of redundant NCL/NRT entries in intra-RAT ANR with NG-RAN

//Deactivating removal of redundant NCL/NRT entries in inter-RAT ANR with UTRAN and GERAN
//Activating penalty on removed neighbor relationships with UTRAN cells

MOD ANR: NcellDelPunishPeriod=xx, UtranNcellDelPunNum=xx;
//Activating penalty on removed neighbor relationships with NG-RAN cells

//Activating inter-RAT fast ANR with GERAN

//Activating inter-RAT fast ANR with UTRAN

//Activating inter-RAT fast ANR with NG-RAN

MOD ANR: NrFastAnrRsrpThld=xx;
//Activating automatic optimization of blind handover priorities for inter-RAT neighbor relationships
//Activating automatic optimization of measurement priorities for inter-RAT neighbor relationships


NoRmvFlag=FORBID_RMV_ENUM, NoHoFlag=FORBID_HO_ENUM;
NoRmvFlag=FORBID_RMV_ENUM, NoHoFlag=PERMIT_HO_ENUM;
//Activating inter-RAT RAC update


//Activating NG-RAN NCL/NRT self-management based on EN-DC X2 messages


eRAN

Optimize parameters related to inter-RAT ANR according to the setting notes in
5.1.4.1.2 Data Preparation.
Deactivation Command Examples (FDD)

MOD UTRANNFREQ: LocalCellId=xx, UtranDlArfcn=xx, AnrInd=NOT_ALLOWED;
MOD GERANNFREQGROUP: LocalCellId=xx, BcchGroupId=xx, AnrInd=NOT_ALLOWED;
//Deactivating neighbor relationship addition in inter-RAT event-triggered ANR with GERAN

//Deactivating neighbor relationship addition in inter-RAT event-triggered ANR with UTRAN

//Deactivating neighbor relationship addition in inter-RAT event-triggered ANR with CDMA2000

MOD ENODEBALGOSWITCH: AnrSwitch=CdmaEventAnrSwitch-0;
//Deactivating neighbor relationship addition in inter-RAT event-triggered ANR with NG-RAN

//Deactivating removal of inappropriate NCL/NRT entries and specification-based removal in inter-RAT ANR
MOD ENODEBALGOSWITCH: AnrSwitch=CdmaAutoNrtDeleteSwitch-0;
//Deactivating removal of redundant NCL/NRT entries in inter-RAT ANR

//Deactivating penalty on removed neighbor relationships with UTRAN cells

MOD ANR: UtranNcellDelPunNum=1;
//Deactivating penalty on removed neighbor relationships with NG-RAN cells

//Deactivating inter-RAT fast ANR

MOD ANR: NrFastAnrRsrpThld=0;
//Deactivating automatic optimization of blind handover priorities for inter-RAT neighbor relationships
//Deactivating automatic optimization of measurement priorities for inter-RAT neighbor relationships

//Deactivating inter-RAT RAC update



eRAN
//Deactivating NG-RAN NCL/NRT self-management based on EN-DC X2 messages

Deactivation Command Examples (TDD)

MOD UTRANNFREQ: LocalCellId=xx, UtranDlArfcn=xx, AnrInd=NOT_ALLOWED;
MOD GERANNFREQGROUP: LocalCellId=xx, BcchGroupId=xx, AnrInd=NOT_ALLOWED;
//Deactivating neighbor relationship addition in inter-RAT event-triggered ANR with GERAN

//Deactivating neighbor relationship addition in inter-RAT event-triggered ANR with UTRAN

//Deactivating neighbor relationship addition in inter-RAT event-triggered ANR with NG-RAN

//Deactivating removal of inappropriate NCL/NRT entries and specification-based removal in inter-RAT ANR
//Deactivating removal of redundant NCL/NRT entries in inter-RAT ANR

//Deactivating penalty on removed neighbor relationships with UTRAN cells

MOD ANR: UtranNcellDelPunNum=1;
//Deactivating penalty on removed neighbor relationships with NG-RAN cells

//Deactivating inter-RAT fast ANR

MOD ANR: NrFastAnrRsrpThld=0;
//Deactivating automatic optimization of blind handover priorities for inter-RAT neighbor relationships
//Deactivating automatic optimization of measurement priorities for inter-RAT neighbor relationships

//Deactivating inter-RAT RAC update


//Deactivating NG-RAN NCL/NRT self-management based on EN-DC X2 messages


eRAN


The procedure for observing the activation of inter-RAT ANR is similar to that of
intra-RAT ANR. For details, see corresponding sections in 4 Functions Related to
Intra-RAT ANR. The MML commands used to query inter-RAT neighboring cells
are different, which are listed as follows:
● LST UTRANNCELL
● LST GERANNCELL
● LST UTRANEXTERNALCELLPLMN
● LST GERANEXTERNALCELLPLMN
● DSP UTRANEXTENDEDNCELL
● DSP GERANEXTENDEDNCELL
● LST UTRANBLKNCELL
● LST CDMA20001XRTTNCELL (FDD)
● LST CDMA2000HRPDNCELL (FDD)
● LST NREXTERNALCELL
● LST NRNRELATIONSHIP

Using inter-RAT ANR decreases the probability that the configurations of inter-RAT
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.
Table 5-19 lists the performance counters that can reflect the network
performance after inter-RAT ANR is enabled. As inter-RAT neighbor relationships
are configured, the values of these counters converge.
Table 5-19 Counters related to inter-RAT ANR
1526728468 L.IRATHO.E2W.NoNRT
1526728470 L.IRATHO.E2G.NoNRT
1526728471 (FDD) L.IRATHO.E21xRTT.NoNRT
1526728472 (FDD) L.IRATHO.E2HRPD.NoNRT
1526741659 L.E2W.CgiReadAtt
1526741660 L.E2G.CgiReadAtt
1526749531 L.E2N.CgiReadAtt

eRAN
1526741662 L.E2W.CgiReadSucc
1526741663 L.E2G.CgiReadSucc
1526749532 L.E2N.CgiReadSucc
NOTE
For details about counters related to mobility management such as handover, see Mobility
Management in Connected Mode.
Fault Description
A coverage-based handover from an E-UTRAN cell to a UTRAN cell fails.
Fault Handling
Step 1 Start a Uu interface tracing task for the source cell on the U2020 client. In the
tracing result, check whether the eNodeB has delivered a handover command,
which carries the IE mobilityFromEUTRACommand.
technical support.
Step 2 Run the LST UTRANEXTERNALCELL command to check whether the target cell
UTRANNCELL command to check whether the neighbor relationship between the
source and target cells has been configured on the source cell.
NOTE
In RAN sharing with common carrier mode, if the UE subscribes to a secondary

operator, query the UtranExternalCellPlmn MO to check whether the PLMN list has
been configured. Configure the PLMN list if it has not been configured.
Step 3 Check whether the switch for event-triggered ANR with UTRAN has been set to
on.
● If the switch is off, set it to on.
Step 4 Check whether the UE supports ANR with UTRAN.

● If the UE supports ANR with UTRAN, contact Huawei technical support.

eRAN
● If the UE does not support ANR with UTRAN, no further action is required.
----End
5.2 Inter-RAT Neighbor Relationship Classification
5.2.1 Principles
The inter-RAT neighbor relationship classification function classifies inter-RAT
neighbor relationships based on the handover statistics and provides differentiated
management of the neighbor relationships based on the classification, improving
O&M experience.
5.2.1.1 Neighbor Relationship Classification

This function classifies neighbor relationships with GERAN and UTRAN cells.
The neighbor relationships in the inter-RAT NRT do not have neighbor relationship
classification labels. The eNodeB stores formal neighbor relationships in the
configuration database and extended neighbor relationships in the memory.
NOTE
If the NRT optimization mode works in controlled mode, the unknown neighbor
relationships to be added or removed will be reported to the U2020 for manual
confirmation. In this case, inter-RAT neighbor relationship classification will not be
performed. In other words, when the ANR.OptMode parameter is set to CONTROLLED and
the NCellParaCfg.CellAnrOptMode parameter is set to CONTROLLED, inter-RAT neighbor
relationship classification does not take effect.
Inter-RAT Neighbor Relationship Classification

Inter-RAT neighbor relationship classification is controlled by the
GERAN_NCELL_CLASS_SW or UTRAN_NCELL_CLASS_SW option of the
CellAlgoSwitch.NCellClassMgtSw parameter. This function requires that inter-
RAT event-triggered ANR or fast ANR be enabled.
When inter-RAT neighbor relationship classification is enabled and the
corresponding frequency-specific ANR indicator is set to ALLOWED, the source cell
with the IRATNCellClassMgt.RatType parameter set to GERAN or UTRAN starts
a measurement period specified by the
IRATNCellClassMgt.StatPeriodForNCellClass parameter.
If the number of times a neighboring GERAN or UTRAN cell is included in a
measurement report is greater than or equal to the
IRATNCellClassMgt.NCellMeasNumThd parameter value within a measurement
period defined by IRATNCellClassMgt.StatPeriodForNCellClass, the neighbor
relationship with this cell is stable. The eNodeB adds this neighbor relationship to
the NRT specified by the GeranNcell or UtranNcell MO.
If the following conditions are met for a neighboring GERAN or UTRAN cell within
each of four consecutive measurement periods defined by
IRATNCellClassMgt.StatPeriodForNCellClass, the neighbor relationship with this
cell is unstable. The eNodeB moves the neighbor relationship from the NRT
specified by the GeranNcell or UtranNcell MO to the memory.

eRAN
● The number of times a neighboring cell is included in measurement reports is

less than the IRATNCellClassMgt.NCellMeasNumThd parameter value.
● At least one neighboring cell on the frequency of this neighboring cell is
included in a measurement report.
If any of the following conditions are met, neighbor relationship classification does
not take effect. In this case, if the EXTENDED_NCELL_MNG_SW option of the
CellAlgoSwitch.NCellClassMgtSw parameter is selected, the eNodeB moves the
neighbor relationships from the memory to the configuration database.
● The GeranEventAnrSwitch and GeranFastAnrSwitch options of the
ENodeBAlgoSwitch.AnrSwitch parameter are deselected for GERAN. The
UtranEventAnrSwitch and UtranFastAnrSwitch options of the
ENodeBAlgoSwitch.AnrSwitch parameter are deselected for UTRAN.
● The INTER_RAT_ANR_SW option of the CellAlgoSwitch.AnrFunctionSwitch
parameter is deselected.
● The ANR.OptMode parameter is set to CONTROLLED and the
NCellParaCfg.CellAnrOptMode parameter is set to CONTROLLED.
● The GERAN_NCELL_CLASS_SW or UTRAN_NCELL_CLASS_SW option of the
CellAlgoSwitch.NCellClassMgtSw parameter is deselected.
● The corresponding frequency-specific ANR indicator is set to NOT_ALLOWED.
Neighbor Relationship Query/Manual Removal

You can run LST GERANNCELL or LST UTRANNCELL to list the configurations of
neighboring GERAN or UTRAN cells.
You can run the DSP GERANEXTENDEDNCELL or DSP UTRANEXTENDEDNCELL
command to query the neighbor relationships stored in the memory.
You can run the RMV GERANEXTENDEDNCELL or RMV UTRANEXTENDEDNCELL
command to remove one or more extended neighbor relationships stored in the
memory.
You can run the RMV GERANNCELL or RMV UTRANNCELL command to remove
one or more neighbor relationships with GERAN or UTRAN cells.
5.2.1.2 Blacklisted Neighbor Relationship Management

Management of blacklisted neighbor relationships with UTRAN cells is similar to
that of blacklisted neighbor relationships with E-UTRAN cells. Both functions
require that neighbor relationship classification be enabled. The following lists the
differences:
● The switch of management of blacklisted neighbor relationships with UTRAN
cells is specified by the UTRAN_OVERDISTANCE_SW option of the
CellAlgoSwitch.AnrAlgoSwitch parameter.
● The measurement period of management of blacklisted neighbor
relationships with UTRAN cells is specified by the
IRATNCellClassMgt.StatPeriodForNCellClass parameter.
● In topology-based management of inter-RAT blacklisted neighbor
relationships, the U2020 obtains the latitude and longitude information about
the serving cell and its neighboring cell. If the distance between the two cells

eRAN
is greater than the NCellParaCfg.NCellOdDisThd parameter value, the

neighboring cell is over-distant.
● In topology-based management of blacklisted neighbor relationships, the
latitude and longitude information about neighboring UTRAN cells can be
configured using the USMLCCELL MO or CME-provided engineering
parameters.
● In statistics-based management of inter-RAT blacklisted neighbor
relationships, the eNodeB cannot add neighbor relationships with UTRAN cells
to the BT list.
5.2.2.1 Benefits
Inter-RAT neighbor relationship classification classifies neighbor relationships in
NRTs based on the handover statistics and manages the neighbor relationships
based on the classification, improving the OM experience.
Management of blacklisted neighbor relationships with UTRAN cells enables the

base station to identify over-distant UTRAN neighboring cells to which UEs are
seldom handed over or that have low handover success rates and perform
differentiated handling for these neighboring cells, so as to reduce the number of
handovers to over-distant neighboring cells.
provided.
● New deployment
You are advised to turn on the switches that control classification of neighbor
relationship with UTRAN and GERAN cells and the over-distant neighboring
UTRAN cell detection switch.
None
5.2.2.2 Impacts
Network Impacts
None
Function Impacts
None
5.2.3 Requirements
5.2.3.1 Licenses
For details, see 4.2.3.1 Licenses.

eRAN
5.2.3.2 Software
For details, see 4.2.3.2 Software.

For details, see 4.2.3.2 Software.
5.2.3.3 Hardware
Base Station Models

No requirements
Boards
No requirements
RF Modules
No requirements
5.2.3.4 Others
The configurations in the CME engineering parameter table are correct when the
blacklisted neighbor relationship management function is enabled. The following
are required in the CME engineering parameter table:
● For a non-multi-RRU cell, the CGI (comprised of RNC ID, MCC, MNC, and cell
ID), latitude, and longitude information about the cell is specified on the
WCDMA or TDSCDMA sheet.
● For a multi-RRU cell, the CGI information about the cell and the latitude and
longitude information about any RRU of the cell are specified on the WCDMA
or TDSCDMA sheet. The "REPEATERRRU" field is set to Yes, indicating that
multiple RRUs exist and the latitude and longitude of each RRU need to be
specified. On the REPEATER sheet, the CGI, RAT (RATTYPE=LTE), RRU name
(RepeaterName), latitude, and longitude information about the cell are
specified. Multiple rows with the same CGI but different latitudes and
longitudes are specified for a multi-RRU cell.

eRAN
5.2.4.1.1 Process


Name
Neighbor Cell CellAlgoSwitch.N UTRAN_NCELL_C Select the following

Classification CellClassMgtSw LASS_SW options:
Mgt Switch GERAN_NCELL_C ● UTRAN_NCELL_CL
LASS_SW ASS_SW
EXTENDED_NCEL ● GERAN_NCELL_CL
L_MNG_SW ASS_SW
● EXTENDED_NCELL
_MNG_SW
Statistic IRATNCellClassM None Set the parameter to

Period For gt.StatPeriodFor its recommended
NCell Class NCellClass value.
NCell IRATNCellClassM None Set the parameter to

Measure gt.NCellMeasNu its recommended
Number mThd value.
Threshold
ANR CellAlgoSwitch.A UTRAN_OVERDIS It is recommended

Algorithm nrAlgoSwitch TANCE_SW that the
Switch UTRAN_OVERDISTAN
CE_SW option be
selected.

Statistic StatThd its recommended
Threshold value.

Success Rat SuccThd its recommended
Threshold value.
Neighboring NCellParaCfg.NC None Set the parameter to

Cell Distance ellOdDisThd its recommended
Threshold value.

eRAN

Name
Statistic IRATNCellClassM A larger value of this parameter results in

Period For gt.StatPeriodFor higher stability of the neighbor
NCell Class NCellClass relationship classification labeling but
lower timeliness of the classification
results.
lower stability of both the neighbor
relationship classification labeling and the
neighbor relationship classification
algorithm.
NCell IRATNCellClassM This parameter specifies the measurement

Measure gt.NCellMeasNu number threshold for inter-RAT neighbor
Number mThd relationship classification management. If
Threshold the number of times the target cell is
measured within the statistical period for
inter-RAT neighbor relationship
classification reaches this threshold, this
inter-RAT neighboring cell is a formal
neighboring cell. A smaller value of this
parameter results in a looser criteria for
deciding whether a neighboring cell is
formal. A larger value of this parameter
results in a stricter criteria for deciding
whether a neighboring cell is formal.

//Activating inter-RAT neighbor relationship classification
//Method 1: Classification of neighbor relationship with UTRAN cells
NCellClassMgtSw=UTRAN_NCELL_CLASS_SW-1&EXTENDED_NCELL_MNG_SW-0;
//Method 2: Classification of neighbor relationship with UTRAN cells

//Method 1: Classification of neighbor relationship with GERAN cells

NCELLCLASSMGTSW=GERAN_NCELL_CLASS_SW-1&EXTENDED_NCELL_MNG_SW-0;
//Method 2: Classification of neighbor relationship with GERAN cells


eRAN
//Activating inter-RAT blacklisted neighbor relationship management

//Method 1: Activating inter-RAT blacklisted neighbor relationship management
MOD CELLALGOSWITCH: LocalCellId=xx, AnrAlgoSwitch=UTRAN_OVERDISTANCE_SW-1;
//Method 2: Activating inter-RAT blacklisted neighbor relationship management


Optimize parameters related to inter-RAT ANR according to the setting notes in
Table 5-21.

//Deactivating inter-RAT neighbor relationship classification
NCELLCLASSMGTSW=UTRAN_NCELL_CLASS_SW-0&EXTENDED_NCELL_MNG_SW-0;
//Deactivating inter-RAT blacklisted neighbor relationship management



For details, see 5.1.4.2 Activation Verification.

After blacklisted neighbor relationship management is enabled, the handover-
related KPIs will improve because the number of handovers to over-distant
neighboring cells decreases.
For details about related counters, see Table 5-19.
5.3 Inter-RAT ANR with Shared Cells
5.3.1 Principles
ANR with shared cells consists of intra-RAT ANR with shared cells and inter-RAT
ANR with shared cells. This section describes inter-RAT ANR with shared cells.
If a neighboring cell is shared by operators, inter-RAT ANR maintains its PLMN list,
in addition to the NCL and NRT. The PLMN lists are configured using the
GeranExternalCellPlmn or UtranExternalCellPlmn MO, which represents the
PLMN list of each external GERAN or UTRAN cell, respectively.

eRAN
NOTE
In this version, ANR does not maintain the PLMN lists (configured by the
NrExternalCellPlmn MOs) of external NG-RAN cells.
This function requires the neighboring cell information obtained from the U2020
in the following methods:
● If the serving cell and neighboring cells are managed by the same U2020, the
source eNodeB can obtain the neighboring cell information directly from the
U2020.
● If the serving cell and neighboring cells are not managed by the same U2020,
the source eNodeB can obtain the neighboring cell information from the
U2020 that manages the serving cell only after the neighboring cell
information is imported into this U2020. Operators can import the
neighboring cell information into this U2020 by using the CME. If the
neighboring cell information is not imported into this U2020 in a timely
manner, the source eNodeB may not obtain the neighboring cell information
and ANR cannot add neighbor relationships with those cells to the NRTs.
information about the neighboring cell from the U2020 to automatically maintain
the external-cell PLMN list.
An E-UTRAN cell may have the following types of shared inter-RAT neighboring
cells:
● Shared UTRAN cell
● Shared GERAN cell
5.3.1.1 Shared GERAN Cell

If a neighboring GERAN cell is shared by operators, UEs do not report the PLMN
list of the cell. As a result, the PLMN list is not included in the external-cell
configuration.
The neighboring cell information is stored in the U2020. The eNodeB may obtain
the information from the U2020 depending on the settings of the
NBSGERANRANSharingSwitch option of the
ENodeBAlgoSwitch.RanSharingAnrSwitch parameter. On a network with more
than one GERAN frequency group, the GeranNFreqGroup.GeranRanSharingInd
parameter can be used to specify the RAN sharing policy for individual frequency
groups. The policy controls whether the eNodeB queries the U2020 for
neighboring cell information.
● If this parameter is set to BOOLEAN_TRUE, the source eNodeB can obtain the
neighboring cell information from the U2020.
The principles of adding external cells and neighbor relationships by event-
triggered ANR are the same as those without information query from the
U2020.
If the ANR.FastAnrMode parameter is set to NCL_NRT_MODE, the principles
of adding external cells and neighbor relationships by fast ANR are different
from those without information query from the U2020. The difference is that

eRAN
the eNodeB adds the strongest and second strongest unknown neighboring
cells to the NCL with the query from the U2020. If the ANR.FastAnrMode
parameter is set to values other than NCL_NRT_MODE, the principles of
adding external cells and neighbor relationships by fast ANR are the same as
those without information query from the U2020.
● If this parameter is set to BOOLEAN_FALSE, the source eNodeB does not
query the neighboring cell information from the U2020.
If ANR detects a missing neighboring GERAN cell, the eNodeB automatically
maintains the external-cell PLMN list after receiving a measurement report that
contains the CGI of the missing cell from the UE. The maintenance procedure is as
follows:
1. The eNodeB reports the CGI acquired by the UE to the U2020.
2. The U2020 queries the PLMN list of the cell and then sends the query result
to the eNodeB.
3. The eNodeB adds the PLMN information to the external-cell configuration.
NOTE
If a UE does not report the PLMN list of the target cell, the eNodeB must obtain
information about this cell from the U2020. Before the target cell is added to the NCL of
the eNodeB and the PLMN information is added to the external-cell configuration of the
source cell, UEs can be handed over to the primary-PLMN cell but not the secondary-PLMN
cell. If the base station serving the target cell is provided by another vendor, the base
station cannot obtain information about the target cell from the U2020. In this case, the
source eNodeB does not add the target cell to the NCL and NRTs.
5.3.1.2 Shared UTRAN Cell

If a neighboring UTRAN cell is shared by operators, the UE may not acquire a
complete PLMN list of the cell. As a result, the PLMN list is not included in the
external-cell configuration.
The neighboring cell information is stored in the U2020. The eNodeB may obtain
the information from the U2020 depending on the settings of the
NBSUTRANRANSharingSwitch option of the
ENodeBAlgoSwitch.RanSharingAnrSwitch parameter. On a network with more
than one UTRAN frequency, the UtranNFreq.UtranRanSharingInd parameter can
be used to specify the RAN sharing policy for individual frequencies. The policy
controls whether the eNodeB queries the U2020 for neighboring cell information.
● If this parameter is set to BOOLEAN_TRUE, the source eNodeB can obtain the
neighboring cell information from the U2020.
The principles of adding external cells and neighbor relationships by event-
triggered ANR are the same as those without information query from the
U2020.
If the ANR.FastAnrMode parameter is set to NCL_NRT_MODE, the principles
of adding external cells and neighbor relationships by fast ANR are different
from those without information query from the U2020. The difference is that
the eNodeB adds the strongest and second strongest unknown neighboring
cells to the NCL with the query from the U2020. If the ANR.FastAnrMode
parameter is set to values other than NCL_NRT_MODE, the principles of
adding external cells and neighbor relationships by fast ANR are the same as
those without information query from the U2020.

eRAN
● If this parameter is set to BOOLEAN_FALSE, the source eNodeB does not

query the neighboring cell information from the U2020.
If ANR detects a missing neighboring UTRAN cell, the eNodeB automatically

maintains the external-cell PLMN list after receiving a measurement report that
contains the CGI of the missing cell from the UE. The maintenance procedure
varies depending on whether the UE reports the PLMN list:
● If the UE reports the PLMN list, the eNodeB directly adds the PLMN
information to the external-cell configuration.
● If the UE does not report the PLMN list, the maintenance procedure is as
follows:
a. The eNodeB reports the CGI acquired by the UE to the U2020.
b. The U2020 queries the PLMN list of the cell and then sends the query
result to the eNodeB.
c. The eNodeB adds the PLMN information to the external-cell
configuration.
NOTE
If a UE does not report the PLMN list of the target cell, the eNodeB must obtain
information about this cell from the U2020. Before the target cell is added to the NCL
of the eNodeB and the PLMN information is added to the external-cell configuration
of the source cell, UEs can be handed over to the primary-PLMN cell but not the
secondary-PLMN cell. If the base station serving the target cell is provided by another
vendor, the base station cannot obtain information about the target cell from the
U2020. In this case, the source eNodeB does not add the target cell to the NCL and
NRTs.
5.3.2.1 Benefits
information about the neighboring cell from the U2020 and automatically
maintains the external-cell PLMN list.
provided.
● New deployment
It is recommended that ANR with shared UTRAN cells be enabled when both
of the following conditions are met:
– Neighboring UTRAN cells are shared by operators.
– The serving and neighboring cells are managed by the same U2020, or
the configuration data of the neighboring cells has been imported into
the U2020 that manages the serving cell.
It is recommended that ANR with shared GERAN cells be enabled when both
of the following conditions are met:
– Neighboring GERAN cells are shared by operators.

eRAN
– The serving and neighboring cells are managed by the same U2020, or
the configuration data of the neighboring cells has been imported into
the U2020 that manages the serving cell.
None
5.3.2.2 Impacts
Network Impacts
When ANR detects missing neighboring shared cells, the eNodeB queries the
U2020 for the cells. The query lasts for a maximum of 3 minutes and may affect
the handover. If no candidate target cell is available for the handover, a service
drop may occur.
Function Impacts
None
5.3.3 Requirements
5.3.3.1 Licenses
None
5.3.3.2 Software
FDD Inter-RAT ANR Following options of the ANR

witch parameter:
GeranEventAnrSwitch
UtranEventAnrSwitch
GeranFastAnrSwitch
UtranFastAnrSwitch

None

eRAN
5.3.3.3 Hardware
Base Station Models

No requirements
Boards
No requirements
RF Modules
No requirements
5.3.3.4 Others
None
5.3.4.1.1 Process


Name
UTRAN UtranNFreq.Utra None The recommended

Frequency nRanSharingInd value is
RAN Sharing BOOLEAN_TRUE for a
Indication neighboring UTRA
frequency if a
neighboring UTRAN
cell on the frequency
is shared by operators.

eRAN

Name
GERAN Freq GeranNfreqGrou None The recommended

Group RAN p.GeranRanShari value is
Sharing ngInd BOOLEAN_TRUE for a
Indication neighboring GERAN
frequency group if a
neighboring GERAN
cell on a frequency of
the group is shared by
operators.
ANR Under ENodeBAlgoSwit NBSUTRANRANS Select the following

RAN Sharing ch.RanSharingAn haringSwitch options:
Algorithm rSwitch NBSGERANRANS ● NBSUTRANRANSh
Switch haringSwitch aringSwitch
● NBSGERANRANSh
aringSwitch
NRT Delete ANR.NrtDelMode UTRAN_NCELL_C If ANR with UTRAN is

Mode ORRECTION_SW enabled in MOCN
scenarios and some
defective UEs report
incorrect primary and
secondary PLMN IDs,
it is recommended
that the
UTRAN_NCELL_CORR
ECTION_SW option
be selected to remove
incorrect external cells
and neighbor
relationships.

//Activating inter-RAT ANR with shared cells
MOD UTRANNFREQ: LocalCellId=xx, UtranDlArfcn=xx, UtranRanSharingInd=BOOLEAN_TRUE;
MOD ENODEBALGOSWITCH: RanSharingAnrSwitch=NBSUTRANRANSharingSwitch-1;
MOD GERANNFREQGROUP: LocalCellId=xx, BcchGroupId=xx, BandIndicator=xx,
GeranRanSharingInd=BOOLEAN_TRUE;
MOD ENODEBALGOSWITCH: RanSharingAnrSwitch=NBSGERANRANSharingSwitch-1;
//(Optional, recommended if ANR with UTRAN is enabled in MOCN scenarios and some defective UEs
report incorrect primary and secondary PLMN IDs) Activating UTRAN NCL/NRT entry rectification
MOD ANR: NrtDelMode=UTRAN_NCELL_CORRECTION_SW-1;

//Deactivating inter-RAT ANR with shared cells
MOD UTRANNFREQ: LocalCellId=xx, UtranDlArfcn=xx, UtranRanSharingInd=BOOLEAN_FALSE;
MOD ENODEBALGOSWITCH: RanSharingAnrSwitch=NBSUTRANRANSharingSwitch-0;

eRAN
MOD GERANNFREQGROUP: LocalCellId=xx, BcchGroupId=xx, BandIndicator=xx,

GeranRanSharingInd=BOOLEAN_FALSE;
MOD ENODEBALGOSWITCH: RanSharingAnrSwitch=NBSGERANRANSharingSwitch-0;
//(Optional, recommended if ANR with UTRAN is enabled in MOCN scenarios and some defective UEs
report incorrect primary and secondary PLMN IDs) Deactivating UTRAN NCL/NRT entry rectification
MOD ANR: NrtDelMode=UTRAN_NCELL_CORRECTION_SW-0;



5.4 Inter-RAT PLMN ID Management
5.4.1 Principles
For details about principles, see 4.5.1 Principles.
5.4.2.1 Benefits
This function prevents neighbor relationships with cells that have abnormal PLMN
IDs from being added to NRTs, thereby increasing the handover success rate and
5.4.2.2 Impacts
Network Impacts
None
Function Impacts
None
5.4.3 Requirements
5.4.3.1 Licenses
None

eRAN
5.4.3.2 Software
FDD Inter-RAT ANR Following options of the ANR

witch parameter:
GeranEventAnrSwitch
UtranEventAnrSwitch
GeranFastAnrSwitch
UtranFastAnrSwitch

None
5.4.3.3 Hardware
Base Station Models

No requirements
Boards
No requirements
RF Modules
No requirements
5.4.3.4 Others
None
5.4.4.1.1 Process

eRAN


Name
Mobile NCellPlmnList.M This parameter specifies the MCC of a

Country Code cc PLMN.
Mobile NCellPlmnList.M This parameter specifies the MNC of a

Network Code nc PLMN.
Rat Type NCellPlmnList.Ra This parameter specifies the RAT of a

tType PLMN.
gNodeB ID NCellPlmnList.gN If the NCellPlmnList.RatType parameter is

Length BIdLength set to NR, this parameter must be set for
the corresponding PLMN.
Plmn List NCellPlmnList.Pl For invalid PLMN IDs reported by

Type mnListType abnormal UEs, the value BLACK_LIST is
recommended.
Near the borders of different PLMNs, the
value GREY_LIST is recommended.

//Activating PLMN ID management
ADD NCELLPLMNLIST: Mcc="xxx", Mnc="xx", RatType=UTRAN, PlmnListType=WHITE_LIST;
ADD NCELLPLMNLIST: Mcc="460", Mnc="998", RatType=UTRAN, PlmnListType=GREY_LIST;
ADD NCELLPLMNLIST: Mcc="xxx", Mnc="xx", RatType=GERAN, PlmnListType=WHITE_LIST;
ADD NCELLPLMNLIST: Mcc="460", Mnc="998", RatType=GERAN, PlmnListType=GREY_LIST;
ADD NCELLPLMNLIST: Mcc="xxx", Mnc="xx", RatType=NR, gNBIdLength=xx, PlmnListType=WHITE_LIST;
ADD NCELLPLMNLIST: Mcc="460", Mnc="998", RatType=NR, gNBIdLength=xx, PlmnListType=GREY_LIST;

//Deactivating PLMN ID management
RMV NCELLPLMNLIST: Mcc="xxx", Mnc="xx", RatType=UTRAN;
RMV NCELLPLMNLIST: Mcc="460", Mnc="998", RatType=UTRAN;
RMV NCELLPLMNLIST: Mcc="xxx", Mnc="xx", RatType=GERAN;
RMV NCELLPLMNLIST: Mcc="460", Mnc="998", RatType=GERAN;



eRAN


eRAN
ANR Management Feature Parameter Description 6 Parameters
6 Parameters
The following hyperlinked EXCEL files of parameter documents match the

software version with which this document is released.
● Node Parameter Reference: contains device and transport parameters.

● eNodeBFunction Parameter Reference: contains all parameters related to
radio access functions, including air interface management, access control,
mobility control, and radio resource management.
● eNodeBFunction Used Reserved Parameter List: contains the reserved
parameters that are in use and those that have been disused.
NOTE
You can find the EXCEL files of parameter reference and used reserved parameter list for
the software version used on the live network from the product documentation delivered
with that version.
FAQ 1: How do I find the parameters related to a certain feature from

parameter reference?
Step 1 Open the EXCEL file of parameter reference.
Step 2 On the Parameter List sheet, filter the Feature ID column. Click Text Filters and
choose Contains. Enter the feature ID, for example, LOFD-001016 or
TDLOFD-001016.
Step 3 Click OK. All parameters related to the feature are displayed.
----End
FAQ 2: How do I find the information about a certain reserved parameter

from the used reserved parameter list?
Step 1 Open the EXCEL file of the used reserved parameter list.
Step 2 On the Used Reserved Parameter List sheet, use the MO, Parameter ID, and BIT
columns to locate the reserved parameter, which may be only a bit of a parameter.
View its information, including the meaning, values, impacts, and product version
in which it is activated for use.
----End

eRAN
ANR Management Feature Parameter Description 7 Counters
7 Counters
The following hyperlinked EXCEL files of performance counter reference match the
software version with which this document is released.
● Node Performance Counter Summary: contains device and transport counters.
● eNodeBFunction Performance Counter Summary: contains all counters related
to radio access functions, including air interface management, access control,
mobility control, and radio resource management.
NOTE
You can find the EXCEL files of performance counter reference for the software version used
on the live network from the product documentation delivered with that version.
FAQ: How do I find the counters related to a certain feature from

performance counter reference?
Step 1 Open the EXCEL file of performance counter reference.

Step 2 On the Counter Summary(En) sheet, filter the Feature ID column. Click Text
Filters and choose Contains. Enter the feature ID, for example, LOFD-001016 or
TDLOFD-001016.
Step 3 Click OK. All counters related to the feature are displayed.
----End

eRAN
ANR Management Feature Parameter Description 8 Glossary
8 Glossary
For the acronyms, abbreviations, terms, and definitions, see Glossary.

eRAN
ANR Management Feature Parameter Description 9 Reference Documents
9 Reference Documents
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. DRX and Signaling Control
6. Mobility Management in Connected Mode
7. S1 and X2 Self-Management
8. RAN Sharing
9. PCI Conflict Detection and Self-Optimization
10. Carrier Aggregation
11. Auto Neighbor Group Configuration
12. Terminal Awareness Differentiation
13. Scheduling
14. eMTC
15. Super Combined Cell (FDD)
16. SFN
17. Intra-RAT Mobility Load Balancing
18. Cell Outage Detection and Compensation
19. CS Fallback
20. Flexible User Steering
21. UMTS and LTE Zero Bufferzone
22. WBB
23. SON Management
24. Software and Hardware Management

ANR Management (ERAN15.1 08)

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

ANR Management (ERAN15.1 08)

Hochgeladen von

Copyright:

Verfügbare Formate

eRAN

ANR Management Feature

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 08 (2020-08-05) Copyright © Huawei Technologies Co., Ltd. i

2 About This Document.............................................................................................................8

4 Functions Related to Intra-RAT ANR................................................................................ 18

Issue 08 (2020-08-05) Copyright © Huawei Technologies Co., Ltd. ii

4.1.1.2 Event-triggered ANR..................................................................................................................................................... 21

Issue 08 (2020-08-05) Copyright © Huawei Technologies Co., Ltd. iii

Issue 08 (2020-08-05) Copyright © Huawei Technologies Co., Ltd. iv

4.4.2 Network Analysis............................................................................................................................................................ 118

5 Functions Related to Inter-RAT ANR..............................................................................128

Issue 08 (2020-08-05) Copyright © Huawei Technologies Co., Ltd. v

5.1.1.1.1 NCL/NRT Control Mode......................................................................................................................................... 129

Issue 08 (2020-08-05) Copyright © Huawei Technologies Co., Ltd. vi

5.2.3.4 Others.............................................................................................................................................................................. 186

Issue 08 (2020-08-05) Copyright © Huawei Technologies Co., Ltd. vii

5.4.4.1.2 Data Preparation...................................................................................................................................................... 198

Issue 08 (2020-08-05) Copyright © Huawei Technologies Co., Ltd. viii

This chapter describes changes not included in the "Parameters", "Counters",

1.1 eRAN15.1 08 (2020-08-05)

1.2 eRAN15.1 07 (2020-03-25)

Issue 08 (2020-08-05) Copyright © Huawei Technologies Co., Ltd. 1

1.3 eRAN15.1 06 (2019-12-13)

1.4 eRAN15.1 05 (2019-09-30)

1.5 eRAN15.1 04 (2019-08-20)

Issue 08 (2020-08-05) Copyright © Huawei Technologies Co., Ltd. 2

● Revised descriptions in this document.

1.6 eRAN15.1 03 (2019-07-20)

1.7 eRAN15.1 02 (2019-06-29)

1.8 eRAN15.1 01 (2019-06-06)

Issue 08 (2020-08-05) Copyright © Huawei Technologies Co., Ltd. 3

Added the determination None FDD ● 3900 and 5900

Added support for None FDD ● 3900 and 5900

1.9 eRAN15.1 Draft C (2019-04-10)

Issue 08 (2020-08-05) Copyright © Huawei Technologies Co., Ltd. 4

1.10 eRAN15.1 Draft B (2019-03-18)

Added UTRAN NCL/NRT Added the FDD ● 3900 and 5900

1.11 eRAN15.1 Draft A (2019-01-05)

Added the function of Added the FDD ● 3900 and 5900

Issue 08 (2020-08-05) Copyright © Huawei Technologies Co., Ltd. 5

Change Description Parameter Change RAT Base Station

Issue 08 (2020-08-05) Copyright © Huawei Technologies Co., Ltd. 6

Change Description Parameter Change RAT Base Station

Optimized the mechanism None FDD ● 3900 and 5900

Issue 08 (2020-08-05) Copyright © Huawei Technologies Co., Ltd. 7

2 About This Document

2.1 General Statements

Feature Differences Between RATs

Issue 08 (2020-08-05) Copyright © Huawei Technologies Co., Ltd. 8

2.2 Applicable RAT

2.3 Features in This Document

Feature ID Feature Name Chapter/Section

LOFD-002001 Automatic Neighbour 4.1 Intra-RAT ANR

LOFD-002002 Inter-RAT ANR 5.1 Inter-RAT ANR

LOFD-081225 Neighbor Cell Classification 4.2 Intra-RAT Neighbor

5.2 Inter-RAT Neighbor

LBFD-081102 PLMN ID Blacklist 4.5 Intra-RAT PLMN ID

5.4 Inter-RAT PLMN ID

LOFD-081207 Specified PCI Group-based 4.3 Specified PCI Group-

This document describes the following TDD features.