anr management(eran6.0_03).pdf
TRANSCRIPT
eRAN eRAN6.0
ANR Management Feature Parameter Description
Issue 03
Date 2013-11-10
HUAWEI TECHNOLOGIES CO., LTD.
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd. i
Copyright © Huawei Technologies Co., Ltd. 2013. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior
written consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and
the customer. All or part of the products, services and features described in this document may not be
within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements,
information, and recommendations in this document are provided "AS IS" without warranties, guarantees or
representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.
Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: http://www.huawei.com
Email: [email protected]
eRAN
ANR Management Feature Parameter Description Contents
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
ii
Contents
1 About This Document .................................................................................................................. 1
1.1 Scope ............................................................................................................................................................................ 1
1.2 Intended Audience ........................................................................................................................................................ 1
1.3 Change History ............................................................................................................................................................. 1
2 Overview ......................................................................................................................................... 4
2.1 Introduction .................................................................................................................................................................. 4
2.2 Benefits ......................................................................................................................................................................... 5
2.3 Architecture .................................................................................................................................................................. 5
3 Concepts Related to ANR ............................................................................................................ 6
3.1 Overview ...................................................................................................................................................................... 6
3.2 NCL .............................................................................................................................................................................. 6
3.3 NRT .............................................................................................................................................................................. 6
3.4 Blacklists ...................................................................................................................................................................... 8
3.5 Whitelists ...................................................................................................................................................................... 8
3.6 Abnormal Neighboring Cell Coverage ......................................................................................................................... 9
3.7 ANR Capabilities of UEs .............................................................................................................................................. 9
4 Intra-RAT ANR ........................................................................................................................... 11
4.1 Overview .................................................................................................................................................................... 11
4.2 Intra-RAT Event-triggered ANR ................................................................................................................................. 11
4.2.1 Automatic Detection of Missing Neighboring Cells ................................................................................................ 11
4.2.2 Automatic Maintenance of NCLs and NRTs ............................................................................................................ 14
4.2.3 Automatic Detection of Abnormal Neighboring Cell Coverage .............................................................................. 16
4.3 Intra-RAT Fast ANR ................................................................................................................................................... 17
5 Inter-RAT ANR ........................................................................................................................... 22
5.1 Overview .................................................................................................................................................................... 22
5.2 Inter-RAT Event-triggered ANR ................................................................................................................................. 22
5.2.1 Automatic Detection of Missing Neighboring Cells ................................................................................................ 22
5.2.2 Automatic Maintenance of NCLs and NRTs ............................................................................................................ 24
5.3 Inter-RAT Fast ANR ................................................................................................................................................... 25
6 ANR with Shared Cells .............................................................................................................. 27
6.1 Overview .................................................................................................................................................................... 27
eRAN
ANR Management Feature Parameter Description Contents
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
iii
6.2 Scenarios ..................................................................................................................................................................... 27
6.2.1 Shared Neighboring E-UTRAN Cell Broadcasting Its PLMN List in an RR Manner ............................................ 27
6.2.2 Shared Neighboring E-UTRAN Cell Not Broadcasting Its PLMN List in an RR Manner...................................... 28
6.2.3 Shared Neighboring UTRAN Cell Broadcasting Its PLMN List in an RR Manner ................................................ 29
6.2.4 Shared Neighboring GERAN Cell Broadcasting Its PLMN List in an RR Manner ................................................ 29
7 Manual Management of Neighbor Relations ........................................................................ 30
7.1 Overview .................................................................................................................................................................... 30
7.2 Adding or Removing a Neighbor Relation ................................................................................................................. 30
7.3 Blacklisting a Neighbor Relation ................................................................................................................................ 30
7.3.1 Configuring an HO Blacklist ................................................................................................................................... 30
7.3.2 Configuring an X2 Blacklist .................................................................................................................................... 31
7.3.3 Configuring an RRC Blacklist ................................................................................................................................. 31
7.4 Whitelisting a Neighbor Relation ............................................................................................................................... 31
7.4.1 Configuring an HO Whitelist ................................................................................................................................... 31
7.4.2 Configuring an X2 Whitelist .................................................................................................................................... 32
8 X2 Automatic Management ....................................................................................................... 33
8.1 Overview .................................................................................................................................................................... 33
8.2 X2 Self-Setup ............................................................................................................................................................. 33
8.2.1 X2 Self-Setup in X2 over S1 Mode ......................................................................................................................... 34
8.2.2 X2 Self-Setup in X2 over M2000 Mode .................................................................................................................. 35
8.3 X2 Automatic Removal .............................................................................................................................................. 37
8.4 eNodeB Configuration Update Based on X2 Messages ............................................................................................. 37
9 Related Features .......................................................................................................................... 39
9.1 Features Related to TDLOFD-002001 Automatic Neighbour Relation (ANR) .......................................................... 39
9.2 Features Related to TDLOFD-002002 Inter-RAT ANR ............................................................................................. 39
9.3 Features Related to TDLOFD-002004 Self-configuration .......................................................................................... 40
10 Network Impact ......................................................................................................................... 41
10.1 Intra-RAT ANR ......................................................................................................................................................... 41
10.2 Inter-RAT ANR ......................................................................................................................................................... 42
10.3 ANR with Shared Cells ............................................................................................................................................. 43
10.4 X2 Automatic Management ...................................................................................................................................... 43
11 Engineering Guidelines for Intra-RAT ANR ...................................................................... 44
11.1 When to Use Intra-RAT ANR ................................................................................................................................... 44
11.2 Required Information ................................................................................................................................................ 45
11.3 Deployment ............................................................................................................................................................... 45
11.3.1 Process ................................................................................................................................................................... 45
11.3.2 Requirements ......................................................................................................................................................... 45
11.3.3 Data Preparation..................................................................................................................................................... 46
11.3.4 Precautions ............................................................................................................................................................. 46
11.3.5 Hardware Adjustment ............................................................................................................................................ 46
eRAN
ANR Management Feature Parameter Description Contents
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
iv
11.3.6 Activation ............................................................................................................................................................... 46
11.3.7 Activation Observation .......................................................................................................................................... 49
11.3.8 Reconfiguration ..................................................................................................................................................... 50
11.3.9 Deactivation ........................................................................................................................................................... 50
11.4 Performance Monitoring ........................................................................................................................................... 51
11.5 Parameter Optimization ............................................................................................................................................ 52
11.6 Troubleshooting ........................................................................................................................................................ 54
12 Engineering Guidelines for Inter-RAT ANR ...................................................................... 56
12.1 When to Use Inter-RAT ANR ................................................................................................................................... 56
12.2 Required Information ................................................................................................................................................ 56
12.3 Deployment .............................................................................................................................................................. 56
12.3.1 Process ................................................................................................................................................................... 56
12.3.2 Requirements ......................................................................................................................................................... 56
12.3.3 Data Preparation .................................................................................................................................................... 57
12.3.4 Precautions ............................................................................................................................................................. 58
12.3.5 Hardware Adjustment ............................................................................................................................................ 58
12.3.6 Activation ............................................................................................................................................................... 58
12.3.7 Activation Observation .......................................................................................................................................... 61
12.3.8 Reconfiguration ..................................................................................................................................................... 61
12.3.9 Deactivation ........................................................................................................................................................... 61
12.4 Performance Monitoring ........................................................................................................................................... 63
12.5 Parameter Optimization ............................................................................................................................................ 63
12.6 Troubleshooting ........................................................................................................................................................ 65
13 Engineering Guidelines for ANR with Shared Cells ........................................................ 66
13.1 When to Use ANR with Shared Cells ....................................................................................................................... 66
13.2 Required Information ................................................................................................................................................ 67
13.3 Deployment .............................................................................................................................................................. 67
13.3.1 Process ................................................................................................................................................................... 67
13.3.2 Requirements ......................................................................................................................................................... 67
13.3.3 Data Preparation .................................................................................................................................................... 68
13.3.4 Precautions ............................................................................................................................................................. 68
13.3.5 Hardware Adjustment ............................................................................................................................................ 68
13.3.6 Activation ............................................................................................................................................................... 68
13.3.7 Activation Observation .......................................................................................................................................... 71
13.3.8 Reconfiguration ..................................................................................................................................................... 71
13.3.9 Deactivation ........................................................................................................................................................... 71
13.4 Performance Monitoring ........................................................................................................................................... 72
13.5 Parameter Optimization ............................................................................................................................................ 72
13.6 Troubleshooting ........................................................................................................................................................ 72
14 Engineering Guidelines for X2 Automatic Management .................................................. 74
14.1 When to Use X2 Automatic Management ................................................................................................................ 74
eRAN
ANR Management Feature Parameter Description Contents
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
v
14.2 Required Information ................................................................................................................................................ 75
14.3 Deployment .............................................................................................................................................................. 75
14.3.1 Process ................................................................................................................................................................... 75
14.3.2 Requirements ......................................................................................................................................................... 75
14.3.3 Data Preparation .................................................................................................................................................... 75
14.3.4 Precautions ............................................................................................................................................................. 76
14.3.5 Hardware Adjustment ............................................................................................................................................ 77
14.3.6 Activation ............................................................................................................................................................... 77
14.3.7 Activation Observation .......................................................................................................................................... 79
14.3.8 Reconfiguration ..................................................................................................................................................... 82
14.3.9 Deactivation ........................................................................................................................................................... 82
14.4 Performance Monitoring ........................................................................................................................................... 83
14.5 Parameter Optimization ............................................................................................................................................ 85
14.6 Troubleshooting ........................................................................................................................................................ 85
15 Parameters .................................................................................................................................. 87
16 Counters .................................................................................................................................... 132
17 Glossary .................................................................................................................................... 133
18 Reference Documents............................................................................................................. 134
eRAN
ANR Management Feature Parameter Description 1 About This Document
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
1
1 About This Document
1.1 Scope
This document describes the Automatic Neighbor Relation (ANR) feature, including
implementation principles, parameter adjustments, feature dependencies, network impact, and
engineering guidelines.
The ANR feature involves the following optional features:
TDLOFD-002001 Automatic Neighbour Relation (ANR)
TDLOFD-002002 Inter-RAT ANR
TDLOFD-002004 Self-configuration
Any managed objects (MOs), parameters, alarms, or counters described below correspond to
the software release delivered with this document. Any future updates will be described in the
product documentation delivered with the latest software release.
This document applies only to LTE TDD. Any "L" or "LTE" in this document refers to LTE
TDD, "eNodeB" refers to LTE TDD eNodeB,and "eRAN" refers to LTE TDD eRAN.
1.2 Intended Audience
This document is intended for personnel who:
Need to understand ANR
Work with Huawei LTE products
1.3 Change History
This section provides information about the changes in different document versions. There are
two types of changes, which are defined as follows:
Feature change: refers to a change in the ANR feature of a specific product version.
Editorial change: refers to a change in wording or the addition of information that was
not described in the earlier version.
eRAN
ANR Management Feature Parameter Description 1 About This Document
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
2
Document Versions
The document version is
03 (2013-11-10)
02 (2013-06-20)
01 (2013-05-10)
Draft A (2013-03-01)
03 (2013-11-10)
Compared with Issue 02 (2013-06-20) , Issue 03 (2013-11-10) of eRAN6.0 includes the
following changes:
Change Type
Change Description Parameter Change
Feature
change
Added descriptions about using event ANR with the
ReportStrongestCellsForSON IE to detect missing UTRAN
neighboring cells, for details see 5.2.1 Automatic Detection of
Missing Neighboring Cells.
None
Editorial
change
None None
02 (2013-06-20)
Compared with Issue 01 (2013-05-10) , Issue 02 (2013-06-20) of eRAN6.0 includes the
following changes:
Change Type
Change Description Parameter Change
Feature
change
Added MlbBasedEventAnrSwitch,see 11.3.3
Data Preparation and 12.3.3 Data Preparation.
Added parameter:
FastAnrMode
Changed the navigation path for batch
configuration on the CME.
Added the steps for exporting and activating
incremental scripts on the planned area of the
M2000 client.
For details, see Using the CME to Perform Batch
Configuration for Existing eNodeBs.
None
Editorial
change
None None
01 (2013-05-10)
This is the first official release.
eRAN
ANR Management Feature Parameter Description 1 About This Document
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
3
Compared with Draft A (2013-03-01) of eRAN 6.0, Issue 01 (2013-05-10) of eRAN 6.0
includes the following changes:
Change Type
Change Description Parameter Change
Feature
change
None None
Editorial
change
Revised the document structure. None
Draft A(2013-03-01)
This is a draft of eRAN6.0.
Compared with Draft A (2012-11-30) of eRAN3.1, Draft A (2013-03-01) of eRAN6.0
includes the following changes.
Change Type
Change Description Parameter Change
Feature
change
Added the description of Intra-RAT
event-triggered ANR,see Detecting Missing
Neighboring Cells by Using Event-triggered
UE Measurements.
None
Editorial
change
Revised the document structure. None
eRAN
ANR Management Feature Parameter Description 2 Overview
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
4
2 Overview
2.1 Introduction
Operation and maintenance (OM) of radio access networks has become increasingly
complicated, difficult, and costly because of the large number of network elements,
implementation of different system standards, and coexistence of different equipment vendors
and telecom operators. These issues can be addressed by 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-optimization function of SON.
Neighbor relations are classified as being either normal or abnormal. In most cases, abnormal
neighbor relations are characterized by missing neighbor cells, physical cell identifier (PCI)
conflicts, and abnormal neighboring cell coverage. ANR automatically detects missing
neighboring cells and maintains neighbor relations to resolve problems caused by abnormal
neighbor relations.
Based on radio access technologies (RATs), ANR is classified into intra-RAT ANR and
inter-RAT ANR. Based on the methods of measuring neighboring cells, ANR is classified into
event-triggered ANR and fast ANR (also known as periodic ANR). Figure 2-1 shows ANR
classifications.
Figure 2-1 ANR classifications
eRAN
ANR Management Feature Parameter Description 2 Overview
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
5
2.2 Benefits
ANR minimizes the probabilities of missing neighboring cells, PCI conflicts, and abnormal
neighboring cell coverage so as to increase handover success rates.
Intra-RAT ANR handles neighbor relations between E-UTRAN cells, while inter-RAT ANR
handles neighbor relations of E-UTRAN cells with GERAN and UTRAN cells. ANR
automatically maintains the completeness and validity of neighbor cell lists (NCLs) and
neighbor relation tables (NRTs) to increase handover success rates and improve network
performance. In addition, ANR reduces manual intervention and, therefore, the costs of
network planning and optimization.
2.3 Architecture
The eNodeB works together with UEs and the M2000 to implement ANR.
eRAN
ANR Management Feature Parameter Description 3 Concepts Related to ANR
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
6
3 Concepts Related to ANR
3.1 Overview
This chapter describes basic ANR-related concepts, which include NCL, NRT, HO blacklist,
HO whitelist, X2 blacklist, X2 whitelist, radio resource control (RRC) blacklist, and abnormal
neighboring cell coverage.
3.2 NCL
The NCLs of an eNodeB contain information about the external cells of the eNodeB, which
belong to other base stations. NCLs are classified as intra-RAT NCLs and inter-RAT NCLs.
Each eNodeB has one intra-RAT NCL and multiple inter-RAT NCLs.
The intra-RAT NCL records information such as the E-UTRAN cell global identifiers
(ECGIs), PCIs and E-UTRA absolute radio frequency channel numbers (EARFCNs) of the
external E-UTRAN cells. The GERAN NCL records information such as the cell IDs, base
transceiver station identity codes (BSICs) and ARFCNs of the external GERAN cells. The
UTRAN NCL records information such as the cell IDs, base transceiver station identity codes
(BSICs) and UTRA ARFCNs (UARFCNs) of the external UTRAN cells. NCLs are used as
the basis for creating neighbor relations. ANR can automatically add or remove external cells
from NCLs.
3.3 NRT
The NRTs of a cell contain information about the neighbor relations of the cell with its
adjacent cells. NRTs are classified into intra-RAT NRTs and inter-RAT NRTs. Each cell has
one intra-RAT intra-frequency NRT, one intra-RAT inter-frequency NRT, and multiple
inter-RAT NRTs. In this document, the intra-RAT intra-frequency NRT and intra-RAT
inter-frequency NRT are collectively referred to as the intra-RAT NRT. Table 3-1 shows an
example of the intra-RAT NRT. The information in this table is for reference only.
eRAN
ANR Management Feature Parameter Description 3 Concepts Related to ANR
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
7
Table 3-1 Intra-RAT NRT example
SN LCI Target Cell PLMN
eNodeB ID Cell ID No Remove
No HO
1 LCI#1 46001 eNodeB ID#1 Cell ID#1 FORBID_
RMV
FORBID_
HO
2 LCI#1 46001 eNodeB ID#2 Cell ID#2 PERMIT_
RMV
PERMIT_
HO
3 LCI#1 46001 eNodeB ID#3 Cell ID#3 FORBID_
RMV
FORBID_
HO
For details about the NRT, see section 22.3.2a in 3GPP TS 36.300 V10.3.0 (2011-04). Huawei NRT
does not include the No X2 attribute.
The NRT in the preceding table is an intra-RAT NRT, which differ greatly from an inter-RAT NRT.
For macro eNodeBs, NRT structures are the same for intra- and inter-eNodeB neighbor relationships.
There is no NCL for intra-eNodeB neighbor relationships. For micro eNodeBs, only one cell exists
under each eNodeB, and therefore, there are no intra-eNodeB neighbor relations.
The intra-RAT NRT contains the following information, which can be updated automatically
or manually:
Local cell identifier (LCI): uniquely identifies the local cell of a neighbor relation. This
attribute is defined by LocalCellId.
Target cell PLMN: identifies the public land mobile network (PLMN) of the operator
that owns the target cell.
eNodeB ID: identifies the eNodeB to which the target cell belongs.
Cell ID: identifies the target cell.
No Remove: indicates whether ANR can remove a neighbor relation from the NRT. By
default, this attribute is set to permit removals.
− When NO Remove is set to FORBID_RMV, the eNodeB is not allowed to remove
the neighbor relation from the NRT by using ANR.
− When NO Remove is set to PERMIT_RMV, the eNodeB is allowed to remove the
neighbor relation from the NRT by using ANR.
No HO: indicates whether this neighbor relation can be used for a handover. By default,
this attribute is set to permit handovers.
− When NO HO is set to FORBID_HO, the eNodeB is not allowed to use the
neighbor relation for handovers.
− When NO HO is set to PERMIT_HO, the eNodeB is allowed to use the neighbor
relation for handovers.
NRTs can be managed (for example, added or removed) automatically by ANR.
eRAN
ANR Management Feature Parameter Description 3 Concepts Related to ANR
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
8
3.4 Blacklists
HO Blacklist
An HO blacklist contains the information about neighbor relations that cannot be used for a
handover or removed automatically from the NRT by ANR. The neighbor relations in the HO
blacklist must meet both of the following conditions:
No Remove is set to prohibit removals.
No HO is set to prohibit handovers.
You can manually add neighbor relations to the HO blacklist. For details, see section 5.2 in
3GPP TS32.511 V10.0.0 (2011-04).
X2 Blacklist
An X2 blacklist contains information about the neighboring eNodeBs with which the local
eNodeB is not permitted to set up X2 interfaces. If an X2 interface has been set up between
the local eNodeB and a neighboring eNodeB in the X2 blacklist, this X2 interface is removed
automatically.
When removing an X2 interface, the eNodeB removes the X2 logical connection but retains the
configuration data for the X2 interface. This mechanism prevents configuration data loss due to
misoperations.
RRC Blacklist
An RRC blacklist contains the neighboring E-UTRAN cells whose information will not be
measured or reported to the eNodeB by UEs. You can manually add an intra- or
inter-frequency neighboring cell to an RRC blacklist.
3.5 Whitelists
HO Whitelist
An HO whitelist contains the information about neighbor relations that can be used for a
handover but cannot be removed automatically from the NRT by ANR. The neighbor relations
in the HO whitelist must meet both of the following conditions:
No Remove is set to prohibit removals.
No HO is set to permit handovers.
You can manually add neighbor relations to the HO whitelist. For details, see section 5.2 in
3GPP TS32.511 V10.0.0 (2011-04).
X2 Whitelist
An X2 whitelist contains information about the neighboring eNodeBs with which the local
eNodeB has set up X2 interfaces. These X2 interfaces cannot be removed automatically.
eRAN
ANR Management Feature Parameter Description 3 Concepts Related to ANR
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
9
3.6 Abnormal Neighboring Cell Coverage
Abnormal neighboring cell coverage may exist between intra-frequency E-UTRAN cells. As
shown in Figure 3-1, if UEs in cell A detect signals from cell B, the ANR considers cell B to
be a neighboring cell of cell A, and ANR adds related information to an NCL and NRT.
However, from a topology perspective, the two cells do not meet the requirements for
neighbor relations. In this situation, the coverage of cell B is regarded as being abnormal. This
type of coverage is also called overshoot coverage.
Figure 3-1 Abnormal neighboring cell coverage
The coverage of neighboring cells may be abnormal in any of the following scenarios:
The antenna tilt or azimuth changes because of improper installation or a natural
phenomenon, such as strong winds.
In mountains, the signals of the umbrella cell cover the lower cells.
3.7 ANR Capabilities of UEs
The ANR capabilities of a UE are represented by the ability of the UE to read the CGIs of
neighboring cells. According to section B.1 in 3GPP TS 36.331 V10.1.0 (2011-03), the
Feature Group Indicators field contained in the UE Capability Information message indicates
the ANR capability of the UE. Table 3-2 provides the definitions and setting descriptions of
the ANR-related indicators.
Table 3-2 Definitions and setting descriptions of ANR-related indicators
Indicator Index
Definition Remarks Applicable
5 Long discontinuous reception (DRX) cycle
DRX command media access control (MAC)
element
N/A Yes
eRAN
ANR Management Feature Parameter Description 3 Concepts Related to ANR
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
10
Indicator Index
Definition Remarks Applicable
16 Periodic reporting of non-ANR-related
intra-frequency measurements
Periodic reporting of non-ANR-related
inter-frequency measurements, if the UE sets
indicator 25 to 1
Periodic reporting of non-ANR-related
measurements of the UTRAN, GERAN,
CDMA2000 1xRTT, or CDMA2000 HRPD,
if the UE sets indicator 22, 23, 24, or 26 to 1,
respectively.
NOTE
Periodic reporting of non-ANR-related
measurements corresponds only to periodical
trigger type with purpose set to
reportStrongestCells. Event-triggered periodic
reporting corresponds to the event trigger type
with reportAmount set to a value greater than 1.
This type of reporting is a mandatory function of
event-triggered reporting and therefore does not
pertain this indicator.
N/A Yes
17 Periodic measurement reporting for
SON/ANR
Reporting of ANR-related intra-frequency
events
This indicator
can only be set
to 1 if the UE
sets indicator 5
to 1.
Yes
18 Reporting of ANR-related inter-frequency
events
This indicator
can only be set
to 1 if the UE
sets indicator 5
to 1.
Yes (unless the
UE supports
only band 13)
19 Reporting of ANR-related inter-RAT events This indicator
can only be set
to 1 if the UE
sets indicator 5
to 1.
N/A
eRAN
ANR Management Feature Parameter Description 4 Intra-RAT ANR
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
11
4 Intra-RAT ANR
4.1 Overview
This chapter describes optional TDLOFD-002001 Automatic Neighbor Relation (ANR),
which is specific for intra-RAT ANR. Intra-RAT ANR is classified into intra-RAT
event-triggered ANR and intra-RAT fast ANR. Intra-RAT event-triggered ANR uses
event-triggered UE measurements or UE history information to detect missing neighboring
cells. In addition, it detects abnormal neighboring cell coverage and maintains neighbor
relations. Intra-RAT fast ANR is also known as periodic intra-RAT ANR. Based on the
periodic reporting of UE measurements, intra-RAT fast ANR obtains information about all
possible intra-RAT neighboring cells before a handover is performed. This type of ANR
reduces the adverse impact of event-triggered ANR measurements on handover performance.
4.2 Intra-RAT Event-triggered ANR
Intra-RAT event-triggered ANR is activated when the IntraRatEventAnrSwitch check box
is selected under the AnrSwitch parameter.
Intra-RAT event-triggered ANR detects missing intra-RAT neighboring cells and abnormal
neighboring cell coverage, and maintains neighbor relations.
4.2.1 Automatic Detection of Missing Neighboring Cells
The procedure for using event-triggered UE measurements to detect missing neighboring cells
is defined in section 22.3.2a in 3GPP TS 36.300 V10.3.0 (2011-04).
ANR can detect missing neighboring cells by using event-triggered UE measurements.
ANR can detect missing neighboring cells by using UE history information.
Detecting Missing Neighboring Cells by Using Event-triggered UE Measurements
Intra-RAT event-triggered ANR detects cells with unknown PCIs based on the intra- and
inter-frequency measurement reports that contain information about cells that meet handover
requirements.
eRAN
ANR Management Feature Parameter Description 4 Intra-RAT ANR
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
12
Intra-RAT event-triggered ANR is triggered only by coverage-based handover measurements or
inter-frequency mobility load balancing (MLB) measurements.
inter-frequency MLB measurements based intra-RAT event-triggered ANR is enabled only when both
IntraRatEventAnrSwitch and MlbBasedEventAnrSwitch are turned on.
For example, cell A and cell B are involved in a handover. The UE is under the coverage of
cell A of the source eNodeB, and cell B is a neighboring cell of cell A. Figure 4-1 shows how
the eNodeB uses event-triggered UE measurements to detect cell B.
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 neighboring cells as specified in the measurement configuration.
The UE performs intra-frequency measurements by default. When a UE establishes radio bearers, by
default, the eNodeB delivers the intra-frequency measurement configuration to the UE in an RRC
Connection Reconfiguration message. When inter-frequency measurements are required, the eNodeB
must deliver the inter-frequency measurement configuration to the UE and set up inter-frequency
measurement gaps. For details about intra- and inter-frequency handover measurements, see Mobility
Management in Connected Mode Feature Parameter Description.
2. The UE detects that cell B meets the measurement requirements, and it reports the PCI of
cell B to the source eNodeB. Note that the UE does not report the PCIs of the
neighboring cells in the RRC blacklist to the eNodeB.
3. The source eNodeB checks whether its intra-RAT NCL includes the PCI of cell B. If the
NCL includes this PCI, the ANR procedure ends. If the NCL does not include this PCI,
the source eNodeB sends the measurement configuration to the UE, instructing the UE to
read the ECGI, tracking area code (TAC), and PLMN ID list of cell B.
eRAN
ANR Management Feature Parameter Description 4 Intra-RAT ANR
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
13
4. The source eNodeB enables the UE to read these parameters over the broadcast channel
(BCH).
Timer T321 controls the maximum amount of time a UE can spend reading ECGIs. The following table
defines T321 and is quoted directly from section 7.3 in 3GPP TS 36.331 V10.1.0 (2011-03). The
following table briefly describes Timer T321.
Timer Start Stop At Expiry
T321 Upon receiving
measConfig including
a reportConfig with
the purpose set to
reportCGI
Upon acquiring the information
needed to set all fields of
cellGlobalId for the requested cell,
upon receiving measConfig that
includes removal of the
reportConfig with the purpose set to
reportCGI
Initiate the
measurement
reporting
procedure, stop
performing the
related
measurements
and remove the
corresponding
measId
5. The UE reports the obtained parameter values to the source eNodeB.
The source eNodeB adds the newly detected neighboring cell (cell B) to its intra-RAT NCL
and adds the neighbor relation to the intra-RAT NRT of cell A.
Detecting Missing Neighboring Cells by Using UE History Information
During a handover, the source eNodeB sends UE history information to the target eNodeB.
Figure 4-2 shows the procedure for using UE history information to detect a missing
intra-RAT neighboring cell.
UE history information is the information about the cells that provided services for the UE. Defined in
section 9.2.1.42 of 3GPP TS 36.413 V10.1.0 (2011-03) and section 9.2.38 of 3GPP TS 36.423 V10.1.O
(2011-03), this information includes: ECGI and type of the last visited cell and duration of the time the
UE stayed in the cell.
eRAN
ANR Management Feature Parameter Description 4 Intra-RAT ANR
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
14
Figure 4-2 Procedure for detecting a missing neighboring cell by using UE history information
1. The source eNodeB sends a Handover Request message to the target eNodeB.
2. The target eNodeB obtains the UE history information from the message. The target
eNodeB checks whether the ECGI of the last visited cell (in this case, cell A, the source
cell) exists in the NCL of the target eNodeB and then proceeds as follows:
a. If the ECGI exists in the NCL but does not exist in the NRT, the target eNodeB adds
the neighbor relation to the NRT. The procedure ends.
b. If the ECGI does not exist in the NCL, the target eNodeB reports the ECGI of cell A
to the M2000 and proceeds to step 3.
3. The M2000 queries the PCI, TAC, and PLMN ID list of cell A based on the reported
ECGI and sends the parameters to the target eNodeB.
4. The target eNodeB adds cell A to its intra-RAT NCL.
eNodeBs of eRAN3.0 or later versions do not maintain TempNRTs. The eNodeB adds the neighbor
relation to the NRT after detecting the missing neighboring cell based on event-triggered UE
measurements and UE history information. For details about how to maintain NRTs, see 4.2.2 Automatic
Maintenance of NCLs and NRTs.
4.2.2 Automatic Maintenance of NCLs and NRTs
Automatic maintenance of NCLs and NRTs ensures the validity of neighbor relations and
therefore improves network performance.
Automatic removal of intra-RAT neighbor relations is controlled by
IntraRatAnrAutoDelSwitch under the AnrSwitch parameter. When a network is unstable or
in an early stage of deployment, you are advised to disable automatic removals. This action
prevents frequent NCL/NRT updates so that neighbor relations can be collected as quickly as
possible.
When the IntraRatAnrAutoDelSwitch check box is not selected, intra-RAT neighbor
relations cannot be removed automatically by ANR.
When the IntraRatAnrAutoDelSwitch check box is selected, intra-RAT neighbor
relations whose CtrlMode is AUTO_MODE can be removed automatically by ANR.
− Neighbor relations whose CtrlMode is AUTO_MODE can be modified or removed
manually by users or automatically by ANR.
eRAN
ANR Management Feature Parameter Description 4 Intra-RAT ANR
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
15
− Neighbor relations whose CtrlMode is MANUAL_MODE can be modified or
removed only manually by users.
− The CtrlMode is set to AUTO_MODE for neighbor relations that are automatically
created during SON operations. The CtrlMode can be set to AUTO_MODE or
MANUAL_MODE for neighbor relations that are manually created.
− When ANR automatically adds an intra-RAT neighbor relation, it uses the default
values for parameters whose values cannot be obtained from UE measurements or
UE history information.
The CtrlMode for each object is as follows:
EutranExternalCell.CtrlMode specifies the CtrlMode for external E-UTRAN cells.
EutranIntraFreqNCell.CtrlMode specifies the CtrlMode for intra-frequency
E-UTRAN cell.
EutranInterFreqNCell.CtrlMode specifies the CtrlMode for inter-frequency
E-UTRAN cell.
EutranInterNFreq.CtrlMode specifies the CtrlMode for neighboring E-UTRAN
frequencies.
Automatic Maintenance of NCLs
During NCL automatic maintenance, the eNodeB can automatically add a newly detected
external cell to or remove an external cell from an NCL.
The eNodeB automatically adds an external cell to an NCL in either of the following
cases:
− The eNodeB detects a missing neighboring cell based on UE measurements and
receives information about this cell, including the ECGI, TAC, and PLMN ID list.
− The eNodeB detects a missing intra-RAT neighboring cell based on UE history
information.
The eNodeB automatically removes an external cell from an NCL if all of the following
conditions are met:
− The IntraRatAnrAutoDelSwitch check box under the AnrSwitch parameter is
selected. External cells can be automatically removed from NCLs only when this
check box is selected.
− The measurement period, which equals four times the value of
StatisticPeriodForNRTDel, has elapsed. The measurement period specified by
StatisticPeriodForNRTDel starts when any event-triggered ANR switch is turned on
for E-UTRAN, UTRAN, GERAN, or CDMA2000.
− The NRTs of all cells under the local eNodeB do not contain any neighbor relations
with this external cell.
− No X2 interface has been set up between the local eNodeB and the eNodeB to which
this external cell belongs.
− CTRLMODE is set to AUTO_MODE for the neighbor relation with the external
cell.
Automatic Maintenance of NRTs
During NRT automatic maintenance, the eNodeB can automatically add a neighbor relation to
or remove a neighbor relation from an NRT.
eRAN
ANR Management Feature Parameter Description 4 Intra-RAT ANR
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
16
The eNodeB automatically adds a neighbor relation to an NRT in either of the following
cases:
− The eNodeB detects a missing neighboring cell based on UE measurements, receives
information (such as the ECGI, TAC, and PLMN list) about this cell, and adds this
information to the NCL. If the detected cell already exists in the NCL, the eNodeB
directly adds the neighbor relation to the NRT.
− The eNodeB detects a missing neighboring cell based on UE history information in a
handover request message and finds that the ECGI of the last visited cell exists in the
NCL of the target eNodeB but does not exist in the NRT of the target cell.
The eNodeB automatically removes a neighbor relation (for example, with cell A) from
an NRT if the IntraRatAnrAutoDelSwitch check box under the AnrSwitch parameter
is selected, and either of the following conditions is met:
− When the number of neighbor relations in an intra-RAT intra-frequency or
inter-frequency NRT has reached the maximum number 64, a new neighbor relation
needs to be added through ANR.
Within the last measurement period specified by the StatisticPeriodForNRTDel
parameter, the total number of handovers from the local cell to its neighboring cells is
greater than or equal to the value of StatisticNumForNRTDel. A group of
neighboring cells have never been included in handover measurement reports. For
these cells, the No Remove attribute is set to permit removals, and the CtrlMode
parameter is set to AUTO_MODE. In this case, the eNodeB randomly removes a
neighboring cell in this group from the NRT.
− Within a measurement period specified by the StatisticPeriod parameter, the number
of handovers from all cells under the eNodeB to cell A is greater than or equal to the
value of NcellHoStatNum, the handover success rate for each cell is less than or
equal to the value of DelCellThd, No Remove is set to PERMIT_RMV, and the
CtrlMode parameter is set to AUTO_MODE. Note that in this case, the neighbor
relation with cell A is removed from the NRT, and information about cell A is also
removed from the NCL. If No Remove is set to FORBID_RMV, the neighbor
relation with cell A is not removed from the NRT, or information about cell A is not
removed from the NCL, either.
The measurement period specified by StatisticPeriodForNRTDel starts when any event-triggered ANR
switch is turned on for E-UTRAN, UTRAN, GERAN, or CDMA2000.
The measurement period specified by StatisticPeriod starts when the switch for intra-RAT
event-triggered ANR is turned on.
4.2.3 Automatic Detection of Abnormal Neighboring Cell Coverage
Abnormal neighboring cell coverage may exist between intra-frequency E-UTRAN cells. It
decreases the handover success rate because of the abnormal neighbor relations it causes.
Therefore, detecting and eliminating abnormal neighboring cell coverage plays an important
role in network optimization.
If the IntraRatEventAnrSwitch(IntraRatEventAnrSwitch) check box under the
AnrSwitch parameter is selected, the M2000 triggers the algorithm for detecting abnormal
neighboring cell coverage and listing abnormal neighboring cells when the M2000 receives an
operator's request to query information about abnormal neighboring cell coverage. The
M2000 checks for abnormal neighboring cell coverage based on the latitudes and longitudes
of the serving cell and its neighboring cells. Then, the M2000 collects statistics about
abnormal neighboring cell coverage and generates a list of abnormal neighboring cells for the serving cell.
eRAN
ANR Management Feature Parameter Description 4 Intra-RAT ANR
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
17
The algorithm for automatically detecting neighboring cell coverage requires that the longitudes and
latitudes of the associated eNodeBs and sectors be accurately set and that the settings take effect. If the
longitudes and latitudes are not set or incorrectly set, the detection results may not be accurate.
To view abnormal neighboring cells, perform the following steps: Log in to the M2000 client.
Choose Configuration > LTE Self Optimization > ANR Management. On the
Neighboring Cell Management tab page, view abnormal neighboring cells in the Query
Cross-Coverage Cell pane.
4.3 Intra-RAT Fast ANR
Intra-RAT event-triggered ANR is activated when the IntraRatFastAnrSwitch check box is
selected under the AnrSwitch parameter.
Before UEs perform handovers, they periodically send measurement reports so that the
eNodeB learns about all neighboring cells whose reference signal received power (RSRP)
values are greater than or equal to the value of FastAnrRsrpThd. This type of ANR reduces
the adverse impact of event-triggered ANR measurements on handover performance.
Periodic UE measurements negatively affect the uplink throughput of the network. To reduce
this adverse impact, intra-RAT fast ANR restricts the number of UEs that can concurrently
perform periodic intra-RAT measurements. When the number of UEs concurrently performing
periodic intra-RAT measurements reaches the maximum, the eNodeB does not select a new
UE for periodic measurements until another UE stops these measurements. The maximum
number is specified by the FastAnrIntraRatMeasUeNum parameter.
Periodic UE measurements also increase the power consumption of UEs. To save UE power
and enable more UEs to perform measurements, intra-RAT fast ANR restricts the number of
periodic measurement reports that each UE can send. When the number of periodic
measurement reports that a UE sends reaches the maximum, the UE stops periodic
measurements so that the eNodeB can select another UE for periodic measurements. The
maximum number is specified by the FastAnrRprtAmount parameter. The interval for UEs to
report periodic measurements is specified by FastAnrRprtInterval. The total number of
neighboring cells that the RSRP requirement of intra-RAT fast ANR is limited, and periodic
UE measurements negatively affect the uplink throughput of the network. To prevent
unnecessary measurements and reduce this adverse impact, intra-RAT fast ANR applies a
threshold (specified by the FastAnrIntraRatUeNumThd parameter) for the total cumulative
number of UEs involved in intra-RAT periodic measurements. The eNodeB checks whether
the total number of UEs that have performed intra-RAT periodic measurements reaches or
exceeds the threshold at a regular interval, which is specified by the FastAnrCheckPeriod
parameter. If the total number of UEs reaches or exceeds the threshold, the eNodeB enters the
monitoring state.
Process
Figure 4-3 shows an intra-RAT fast ANR process.
eRAN
ANR Management Feature Parameter Description 4 Intra-RAT ANR
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
18
Figure 4-3 Intra-RAT fast ANR process
eRAN
ANR Management Feature Parameter Description 4 Intra-RAT ANR
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
19
eRAN
ANR Management Feature Parameter Description 4 Intra-RAT ANR
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
20
In summary, an intra-RAT fast ANR process is as follows:
After intra-RAT fast ANR is activated, the eNodeB starts a check period and selects UEs to
perform intra-frequency and inter-frequency measurements to detect the PCIs of unknown
cells. The maximum number of UEs that can be selected is specified by the
FastAnrIntraRatMeasUeNum parameter. During the check period, the eNodeB operates as
follows: If the PCI of an unknown cell is reported, the eNodeB sets the number of UEs that
have performed measurements in the check period (FastAnrCheckPeriod) to 0 and then
selects UEs to perform intra- and inter-frequency measurements. The maximum number of
UEs that can be selected is specified by the FastAnrIntraRatMeasUeNum parameter. The
eNodeB does not select voice over IP (VoIP) UEs to perform fast ANR measurements.
At the end of each check period, the eNodeB performs the following operators: If the total
number of UEs that have performed intra-frequency and inter-frequency measurements is less
than the value of FastAnrIntraRatUeNumThd, the eNodeB directly starts the next round of
fast ANR measurements. If the total number of UEs that have performed intra-frequency and
inter-frequency measurements reaches or exceeds the value of FastAnrIntraRatUeNumThd,
the eNodeB enters the monitoring state to monitor whether the PCI of an unknown cell is
reported in an event-triggered ANR measurement report. If an unknown PCI is reported, the
eNodeB starts fast ANR measurements again.
During a fast ANR procedure, after a UE reports the PCI of an unknown cell, the eNodeB
instructs the UE to read the ECGI of the cell. In intra-frequency scenarios, the eNodeB adds
the information about the detected cell to the NCL. In inter-frequency scenarios, when
FastAnrMode is configured to NCL_NRT_MODE, the eNodeB adds the information about
the strongest detected cell to the NCL and NRT and adds the information about the next
strongest cell only to the NCL; when FastAnrMode is configured to NCL _MODE, the
eNodeB adds the information about both the strongest and next strongest detected cell to the
NCL.
Impact on System Performance
Derived from intra-RAT fast ANR, fast ANR includes two UE processes: periodic PCI
reporting and cell global identification (CGI) reading. In the periodic PCI reporting process,
the UE periodically reports the PCI of the neighboring cell with the best signal quality. In the
CGI reading process, the UE reads the CGIs of unknown cells.
Periodic PCI reporting
− With respect to intra-frequency fast ANR, this process does not affect UE throughput
because the UE does not need to measure other frequencies during intra-frequency
measurements.
− With respect to inter-frequency or inter-RAT fast ANR, this process negatively affects
UE throughput because gap-assisted measurements are used. Two measurement gap
patterns are defined in section 8.1.2 of 3GPP TS 36.133 V10.2.0 (2011-04): pattern 0
and pattern 1. To speed up these measurements, pattern 0 is used by default.
Table 4-1 Gap patterns
Measurement Gap Pattern
Gap Width (Unit: ms)
Gap Repetition Period (Unit: ms)
Target RAT
0 6 40 Inter-Frequency E-UTRAN
FDD and TDD, UTRAN
eRAN
ANR Management Feature Parameter Description 4 Intra-RAT ANR
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
21
Measurement Gap Pattern
Gap Width (Unit: ms)
Gap Repetition Period (Unit: ms)
Target RAT
FDD, GERAN, LCR TDD,
HRPD, CDMA2000 1x
1 6 80 Inter-Frequency E-UTRAN
FDD and TDD, UTRAN
FDD, GERAN, LCR TDD,
HRPD, CDMA2000 1x
CGI reading
To read the CGI of an unknown cell, the UE uses the system information block type 1
(SIB1) of the unknown cell to obtain the PLMN IDs, CGI, and TAC of the cell. After
obtaining this information, the UE reports it to the source eNodeB. The reading and
reporting processes decrease UE throughput.
In conclusion, fast ANR affects system performance as follows:
With respect to intra-frequency fast ANR, periodic PCI reporting does not affect system
performance, but CGI reading interrupts UE services.
With respect to inter-frequency and inter-RAT fast ANR, periodic PCI reporting
negatively affects UE throughput, and CGI reading interrupts UE services.
eRAN
ANR Management Feature Parameter Description 5 Inter-RAT ANR
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
22
5 Inter-RAT ANR
5.1 Overview
This chapter describes optional TDLOFD-002002 Inter-RAT ANR, which is specific for
inter-RAT ANR. Inter-RAT ANR is classified into inter-RAT event-triggered ANR and
inter-RAT fast ANR. Inter-RAT event-triggered ANR uses event-triggered UE measurements
to automatically detect missing inter-RAT neighboring cells. Inter-RAT fast ANR instructs
UEs to perform periodic measurements to automatically detect missing neighboring cells.
Inter-RAT fast ANR enables eNodeBs to collect neighboring cell information before any
handovers. This type of ANR reduces the adverse impact of inter-RAT event-triggered ANR
measurements on handover performance.
5.2 Inter-RAT Event-triggered ANR
The GeranEventAnrSwitch(GeranEventAnrSwitch) and
UtranEventAnrSwitch(UtranEventAnrSwitch) check boxes under the AnrSwitch
parameter control inter-RAT event-triggered ANR. The inter-RAT event-triggered ANR
function is activated when the corresponding check box is selected.
After inter-RAT event-triggered ANR is activated, the eNodeB delivers inter-RAT
measurement configurations to the UE and instructs it to perform event-triggered ANR
measurements on neighboring GERAN or UTRAN cells.
Inter-RAT ANR does not check for PCI conflicts and abnormal neighboring cell coverage based on the
following: The E-UTRAN has only a small number of standardized interfaces with other RATs. The
E-UTRAN has difficulty detecting anomalies in other RATs.
5.2.1 Automatic Detection of Missing Neighboring Cells
Inter-RAT event-triggered ANR detects missing inter-RAT neighboring cells based on the list
of cells that are contained in inter-RAT measurement reports for coverage-based handovers.
This section describes how inter-RAT event-triggered ANR detects a missing neighboring
UTRAN cell. For example, cell A is an E-UTRAN cell and cell B is a UTRAN cell. The UE is
under the coverage of cell A and cell B is an inter-RAT neighboring cell of cell A.
eRAN
ANR Management Feature Parameter Description 5 Inter-RAT ANR
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
23
Due to protocol limitations, unknown neighboring UTRAN cells cannot be reported using the B1/B2
event measurement report during UTRAN measurements. Instead, the SON-specific measurement report
with the ReportStrongestCellsForSON IE must be used.
During GERAN measurements, unknown neighboring GERAN cells can be reported using the B1/B2
event measurement report.
Figure 5-1 shows how the eNodeB uses event-triggered UE measurements to detect cell B.
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 (including target
RATs and frequencies) to the UE, sets up measurement gaps, and instructs the UE to
measure neighboring cells as specified in the measurement configuration.
For details about inter-RAT handover measurements, see Mobility Management in Connected Mode
Feature Parameter Description.
In the current version, inter-RAT event-triggered ANR is triggered only by coverage-based handover
measurements or MLB measurements.
UTRAN MLB measurements based inter-RAT event-triggered ANR is enabled when both
UtranEventAnrSwitch and MlbBasedEventAnrSwitch are turned on.
GERAN MLB measurements based inter-RAT event-triggered ANR is enabled when both
GeranEventAnrSwitch and MlbBasedEventAnrSwitch are turned on.
2. The UE detects that cell B meets the measurement requirements and reports the primary
scrambling code (PSC) of cell B to cell A. If the NCL of the source eNodeB includes the
PSC of cell B, the ANR procedure ends. If the NCL does not include the PSC of cell B,
the source eNodeB proceeds to the next step.
3. The source eNodeB requests the UE to read the parameters of cell B.
eRAN
ANR Management Feature Parameter Description 5 Inter-RAT ANR
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
24
If cell B is a GERAN or UTRAN cell, the parameters to be read are the CGI, location
area code (LAC), and routing area code (RAC).
4. The source eNodeB schedules appropriate idle time to allow the UE to read the CGI,
LAC, and RAC of cell B over the BCH.
5. The UE reports the CGI, LAC, and RAC of cell B to the source eNodeB.
The source eNodeB adds the newly detected neighboring cell to its inter-RAT NCL and adds
the neighbor relation to the inter-RAT NRT of cell A.
5.2.2 Automatic Maintenance of NCLs and NRTs
Automatic maintenance of NCLs and NRTs ensures the validity of neighbor relations and
therefore improves network performance.
Automatic removal of neighbor relations with UTRAN or GERAN is controlled by the
UtranAutoNrtDeleteSwitch or GeranAutoNrtDeleteSwitch option, respectively, under the
AnrSwitch parameter. When a network is unstable or in an early stage of deployment, you are
advised to disable automatic removals. This action prevents frequent NCL/NRT updates so
that neighbor relations can be collected as quickly as possible.
When the UtranAutoNrtDeleteSwitch or GeranAutoNrtDeleteSwitch option is not
selected, inter-RAT neighbor relations cannot be removed automatically by ANR.
When the UtranAutoNrtDeleteSwitch or GeranAutoNrtDeleteSwitch option is
selected, inter-RAT neighbor relations whose CtrlMode is AUTO_MODE can be
removed automatically by ANR.
− Neighbor relations whose CtrlMode is AUTO_MODE can be modified or removed
manually by users or automatically by ANR.
− Neighbor relations whose CtrlMode is MANUAL_MODE can be modified or
removed only manually by users.
− The CtrlMode is set to AUTO_MODE for neighbor relations that are automatically
created during SON operations. The CtrlMode can be set to AUTO_MODE or
MANUAL_MODE for neighbor relations that are manually created.
− Parameters in different modes are separately configured.
− When ANR automatically adds an inter-RAT neighbor relation, it uses the default
values for parameters whose values cannot be obtained from UE measurements or
UE history information.
The CtrlMode for each object is as follows:
UtranExternalCell.CtrlMode specifies the CtrlMode for external UTRAN cells.
UtranNCell.CtrlMode specifies the CtrlMode for neighboring UTRAN cells.
GeranExternalCell.CtrlMode specifies the CtrlMode for external GERAN cells.
GeranNcell.CtrlMode specifies the CtrlMode for neighboring GERAN cells.
Automatic Maintenance of NCLs
During NCL automatic maintenance, the eNodeB can automatically add a newly detected
external cell to or remove an external cell from an NCL.
The eNodeB adds an external cell to an NCL
if the eNodeB detects a missing neighboring cell based on UE measurements and
receives information about this cell, including the CGI.
eRAN
ANR Management Feature Parameter Description 5 Inter-RAT ANR
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
25
The eNodeB automatically removes an external cell from an NCL if all of the following
conditions are met:
− The UtranAutoNrtDeleteSwitch or GeranFastAnrSwitch option under the
AnrSwitch parameter is selected.
− The measurement period, which equals four times the value of
StatisticPeriodForNRTDel, has elapsed.
− The NRTs of all cells under the local eNodeB do not contain any neighbor relations
with this external cell.
− CtrlMode is set to AUTO_MODE for the neighbor relation with the external cell.
The measurement period specified by StatisticPeriodForNRTDel starts when any event-triggered ANR
switch is turned on for E-UTRAN, UTRAN, GERAN, or CDMA2000.
Automatic Maintenance of NRTs
During NRT automatic maintenance, the eNodeB can automatically add a neighbor relation to
or remove a neighbor relation from an NRT.
The eNodeB automatically adds a neighbor relation to an NRT
after the eNodeB detects a missing neighboring cell based on UE measurements,
receives information about this cell, and adds this information to the NCL.
The eNodeB automatically removes a neighbor relation from an NRT when all the
following conditions are met:
− The corresponding option UtranAutoNrtDeleteSwitch(UtranAutoNrtDeleteSwitch)
or GeranAutoNrtDeleteSwitch(GeranAutoNrtDeleteSwitch) under the AnrSwitch
parameter is selected.
− When the number of neighbor relations in the NRT has reached the maximum, a new
neighbor relation needs to be added through ANR.
− Within the last measurement period specified by the StatisticPeriodForNRTDel
parameter, the total number of handovers from the local cell to its neighboring
UTRAN or GERAN cells is greater than or equal to the value of
StatisticNumForNRTDel. A group of neighboring cells have never been included in
handover measurement reports. For these cells, the No Remove attribute is set to
permit removals, and the CtrlMode parameter is set to AUTO_MODE. In this case,
the eNodeB randomly removes a neighboring cell in this group from the NRT.
The measurement period specified by StatisticPeriodForNRTDel starts when any event-triggered ANR
switch is turned on for E-UTRAN, UTRAN, GERAN, or CDMA2000.
5.3 Inter-RAT Fast ANR
The GeranFastAnrSwitch(GeranFastAnrSwitch) and
UtranFastAnrSwitch(UtranFastAnrSwitch) options under the AnrSwitch parameter
control inter-RAT fast ANR. The inter-RAT fast ANR function is activated when the
corresponding options are selected.
After inter-RAT fast ANR is activated, the eNodeB delivers inter-RAT measurement
configurations to the UE and instructs the UE to perform periodic measurements on
neighboring GERAN and UTRAN cells.
eRAN
ANR Management Feature Parameter Description 5 Inter-RAT ANR
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
26
The principles of inter-RAT fast ANR are almost the same as those of intra-RAT fast ANR.
For details, see 4.3 Intra-RAT Fast ANR. Compared with intra-RAT fast ANR, inter-RAT fast
ANR incorporates the following differences:
For fast ANR with UTRAN, the reportStrongestCellsForSON option is configured on
the eNodeB for fast ANR measurements. According to section 6.3.5 in 3GPP TS 36.331
V10.1.0 (2011-03), when the information element (IE) purpose is set to
reportStrongestCellsForSON, the reportAmount IE can only be set to 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 UE to send periodic measurement reports, the fast ANR algorithm sets and sends
reportStrongestCellsForSON to the UE at an unconfigurable interval.
When a user subscribes to inter-RAT fast ANR measurement reporting events on the
eCoordinator, inter-RAT fast ANR is restarted if the eNodeB enters the monitoring state
for inter-RAT fast ANR.
During fast ANR, after a UE reports an unknown cell, the eNodeB instructs the UE to
read the CGI of the cell. In fast ANR with GERAN, when FastAnrMode is configured to
NCL_NRT_MODE, the eNodeB adds the information about the detected strongest
GERAN cell to the NCL and NRT and adds the information about the next strongest
GERAN cell only to the NCL; when FastAnrMode is configured to NCL _MODE, the
eNodeB adds the information about both the strongest and next strongest detected cell to
the NCL. In fast ANR with UTRAN, the eNodeB adds the information about the
detected strongest UTRAN cell to the NCL and NRT; when FastAnrMode is configured
to NCL _MODE, the eNodeB adds the information about both the strongest and next
strongest detected cell to the NCL.
The following describes parameter differences between intra- and inter-RAT fast ANR.
− The signal quality threshold used in the evaluation of whether to periodically report a
neighboring cell's PCI is specified by the FastAnrRsrpThd parameter in intra-RAT
fast ANR and specified by the following parameters in inter-RAT fast ANR:
FastAnrRscpThd and FastAnrRssiThd specify UTRAN and GERAN, respectively.
− For the maximum number of UEs that can concurrently perform fast ANR
measurements, FastAnrInterRatMeasUeNum and FastAnrIntraRatMeasUeNum
specify inter-RAT fast ANR and intra-RAT fast ANR, respectively.
− For the minimum number of UEs that have performed measurements for fast ANR,
FastAnrInterRatUeNumThd and FastAnrIntraRatUeNumThd specify inter-RAT
fast ANR and intra-RAT fast ANR, respectively.
For details about the impact on network performance brought by inter-RAT fast ANR, see 4.3
Intra-RAT Fast ANR.
eRAN
ANR Management Feature Parameter Description 6 ANR with Shared Cells
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
27
6 ANR with Shared Cells
6.1 Overview
If a neighboring E-UTRAN cell is shared by PLMNs and broadcasts its PLMN list in a round
robin (RR) manner, a UE in its serving cell might not be able to obtain the correct serving
PLMN list of the neighboring E-UTRAN cell. If the shared neighboring E-UTRAN cell does
not broadcast its PLMN list in an RR manner, a UE in its serving cell might not report a
complete PLMN list of the neighboring E-UTRAN cell to the serving cell. As a result of
either case, neighbor relations cannot be correctly added. To solve this problem, the serving
cell can request that the M2000 send the serving PLMN list of the neighboring E-UTRAN cell.
This solution works only if the serving and neighboring cells are managed by the same
M2000, which stores the configuration data and status information about the neighboring cell.
This solution also applies to the following inter-RAT ANR scenarios in which neighbor
relations cannot be added.
If the shared neighboring cell is a UTRAN cell, a UE in its serving cell might not report a
complete PLMN list of the neighboring UTRAN cell to the serving cell.
If the shared neighboring cell is a GERAN cell, a UE in its serving cell does not report the
PLMN list of the neighboring GERAN cell to the serving cell.
6.2 Scenarios
6.2.1 Shared Neighboring E-UTRAN Cell Broadcasting Its PLMN List in an RR Manner
ANR with shared E-UTRAN cells that broadcast PLMN lists in an RR manner requires that
NBSLTEPLMNRoundSwitch(NBSLTEPLMNRoundSwitch) under the
RanSharingAnrSwitch parameter be turned on.
If NBSLTEPLMNRoundSwitch(NBSLTEPLMNRoundSwitch) is turned on and the
serving eNodeB of a UE receives a measurement report containing the CGI (PLMN
ID+eNodeB ID+cell ID) of a neighboring E-UTRAN cell, the serving eNodeB reports the PCI
and CGI obtained by the UE to the M2000. The M2000 queries the primary PLMN and
serving PLMN list of the neighboring E-UTRAN cell based on the PCI, eNodeB ID, and cell
ID because the PLMN ID in the CGI may be the ID of a secondary PLMN. The M2000 then
sends the query result to the serving eNodeB. The serving eNodeB adds the PLMN
eRAN
ANR Management Feature Parameter Description 6 ANR with Shared Cells
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
28
information to the external-cell and PLMN-list configurations corresponding to the
neighboring E-UTRAN cell.
In a handover procedure, as shown in Figure 6-1, if cell A (the source cell) is shared by
PLMNs and the target eNodeB providing cell B detects from UE history information that cell
A has not been configured as a neighboring cell of cell B, the target eNodeB adds the
information about cell A to the intra-RAT NCL. The target eNodeB also adds information
about the secondary operators of cell A to the PLMN list configurations of the external cell for
cell B.
Figure 6-1 Procedure for detecting a missing neighboring cell by using UE history information
If the serving cell and neighboring cell are not managed by the same M2000, the ANR function cannot
be used with the function of broadcasting the PLMN list in an RR manner, which is provided in
TDLOFD-001036 RAN Sharing with Common Carrier.
6.2.2 Shared Neighboring E-UTRAN Cell Not Broadcasting Its PLMN List in an RR Manner
ANR with shared neighboring E-UTRAN cells that do not broadcast PLMN lists in an RR
manner requires that NBSLTERANSharingSwitch(NBSLTERANSharingSwitch) under the
RanSharingAnrSwitch parameter be turned on.
If NBSLTERANSharingSwitch(NBSLTERANSharingSwitch) is turned on and
NBSLTEPLMNRoundSwitch(NBSLTEPLMNRoundSwitch) is turned off, and the serving
eNodeB of a UE receives a measurement report containing the CGI of a neighboring
E-UTRAN cell, the serving eNodeB takes one of the following actions:
If the UE does not report the PLMN list of the neighboring E-UTRAN cell, the serving
eNodeB adds the information about the missing neighboring E-UTRAN cell to the
intra-RAT NCL and NRT and reports the CGI obtained by the UE to the M2000. The
M2000 queries the PLMN list of the neighboring E-UTRAN cell and sends the query
result to the serving eNodeB. The serving eNodeB adds the PLMN information to the
PLMN list configurations.
If the UE reports the PLMN list of the neighboring E-UTRAN cell, the serving eNodeB
starts a normal ANR procedure. After the UE reports the CGI and PLMN list to the
serving eNodeB, the serving eNodeB adds the information about the missing
eRAN
ANR Management Feature Parameter Description 6 ANR with Shared Cells
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
29
neighboring E-UTRAN cell to the intra-RAT NCL and NRT and adds the PLMN
information to the PLMN list configurations.
The procedure for detecting a missing neighboring cell based on UE history information is the
same as that described in Detecting Missing Neighboring Cells by Using UE History
Information.
6.2.3 Shared Neighboring UTRAN Cell Broadcasting Its PLMN List in an RR Manner
ANR with shared UTRAN cells that broadcast PLMN lists in an RR manner requires that
NBSUTRANRANSharingSwitch(NBSUTRANRANSharingSwitch) under the
RanSharingAnrSwitch parameter be turned on.
If NBSUTRANRANSharingSwitch(NBSUTRANRANSharingSwitch) is turned on and the
serving eNodeB of a UE receives a measurement report containing the GCI of a neighboring
UTRAN cell, the serving eNodeB takes one of the following actions:
If the UE reports the PLMN list of the neighboring UTRAN cell, the serving eNodeB
starts a normal ANR procedure. After the UE reports the CGI and PLMN list to the
serving eNodeB, the serving eNodeB adds the information about the missing
neighboring UTRAN cell to the NCL and NRT and adds the PLMN information to the
PLMN list configurations.
If the UE does not report the PLMN list of the neighboring UTRAN cell, the serving
eNodeB adds the information about the missing neighboring UTRAN cell to the NCL
and NRT and reports the CGI obtained by the UE to the M2000. The M2000 queries the
PLMN list of the neighboring UTRAN cell and sends the query result to the serving
eNodeB. The serving eNodeB adds the PLMN information to the PLMN list
configurations.
6.2.4 Shared Neighboring GERAN Cell Broadcasting Its PLMN List in an RR Manner
ANR with shared GERAN cells that broadcast PLMN lists in an RR manner requires that
NBSGERANRANSharingSwitch(NBSGERANRANSharingSwitch) under the
RanSharingAnrSwitch parameter be turned on.
If NBSGERANRANSharingSwitch(NBSGERANRANSharingSwitch) is turned on and the
serving eNodeB of a UE receives a measurement report containing CGI of a neighboring
GERAN cell, the serving eNodeB adds the information about the missing neighboring
GERAN cell to the NCL and NRT. Then it reports the CGI obtained by the UE to the M2000.
The M2000 queries the PLMN list of the neighboring GERAN cell and sends the query result
to the serving eNodeB. The serving eNodeB adds the PLMN information to the PLMN list
configurations.
eRAN
ANR Management Feature Parameter Description 7 Manual Management of Neighbor Relations
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
30
7 Manual Management of Neighbor Relations
7.1 Overview
Generally, ANR automatically manages neighbor relations. In some cases, they need to be
managed manually. The manual management tasks are as follows: Adding or removing a
neighbor relation, blacklisting a neighbor relation, and whitelisting a neighbor relation. The
most recent manually or automatically maintained neighbor relations are kept in NRTs.
7.2 Adding or Removing a Neighbor Relation
Configure the EutranIntraFreqNCell, EutranInterFreqNCell, UTRANNCELL, and
GeranNcell MOs to add or remove a neighbor relation with intra-frequency E-UTRAN cells,
inter-frequency E-UTRAN cells, UTRAN cells, and GERAN cells, respectively. For details,
see Mobility Management in Connected Mode Feature Parameter Description. If ANR is
activated (recommended), neighbor relations are added or removed automatically.
7.3 Blacklisting a Neighbor Relation
7.3.1 Configuring an HO Blacklist
HO blacklists can only be configured manually. If an NRT contains a neighbor relation that
has been included in an HO blacklist, this neighbor relation cannot be automatically removed
from the NRT, an the corresponding neighboring cell cannot be selected as the handover
target cell.
A neighbor relation needs to be added to an HO blacklist in some special cases, for example,
if the neighbor relation causes overshoot coverage and leads to unstable handover success
rates. To blacklist a neighbor relation, perform the following steps:
Log in to the M2000 client. Choose Configuration > LTE Self Optimization > ANR
Management. On the Neighbor Cell Management tab page, select a neighbor relation to be
blacklisted in the Neighboring Cell pane. Set both Handover Prohibited and Deletion
Prohibited to TRUE in the displayed Set dialog box.
eRAN
ANR Management Feature Parameter Description 7 Manual Management of Neighbor Relations
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
31
Alternatively, you can set NoHoFlag to FORBID_HO_ENUM(Forbid Ho) and
NoRmvFlag to FORBID_RMV_ENUM(Forbid ANR Remove) to blacklist a neighbor
relation. Depending on the neighbor relation type, these two parameters belong to different
MOs:
For a neighbor relation with an intra-frequency E-UTRAN cell, they belong to the
NoHoFlag and NoRmvFlag parameters.
For a neighbor relation with an inter-frequency E-UTRAN cell, they belong to the
NoHoFlag and NoRmvFlag parameters.
For a neighbor relation with a UTRAN cell, they belong to the NoHoFlag and
NoRmvFlag parameters.
For a neighbor relation with a GERAN cell, they belong to the NoHoFlag and
NoRmvFlag parameters.
7.3.2 Configuring an X2 Blacklist
X2 blacklists can only be configured manually. An X2 blacklist contains information about
the neighboring eNodeBs with which the local eNodeB is not permitted to set up X2
interfaces. If an X2 interface has been set up between the local eNodeB and a neighboring
eNodeB in the X2 blacklist, this X2 interface is removed automatically.
When removing an X2 interface, the eNodeB removes the X2 logical connection but retains the
configuration data for the X2 interface. This mechanism prevents configuration data loss due to
misoperations.
X2 blacklists can be configured as required by operators. For example, operators may require
that X2 interfaces not be set up between different base station models. To configure an X2
blacklist, perform the following steps:
Log in to the M2000 client. Choose Configuration > LTE Self Optimization > ANR
Management. On the ANR Management tab page, add an X2 interface to the X2 blacklist.
You can also query the X2 blacklist on this tab page. Alternatively, you can use the
X2BlackWhiteList MO to configure an X2 blacklist.
7.3.3 Configuring an RRC Blacklist
UEs are not permitted to measure or be handed over to the cells contained in RRC blacklists.
To configure intra-frequency or inter-frequency RRC blacklist, configure the
IntraFreqBlkCell or
InterFreqBlkCell MO, respectively.
7.4 Whitelisting a Neighbor Relation
7.4.1 Configuring an HO Whitelist
HO whitelists can only be configured manually. If an NRT contains a neighbor relation that
has been included in an HO whitelist, this neighbor relation cannot be automatically removed
from the NRT, and the corresponding neighboring cell can be selected as the handover target
cell.
eRAN
ANR Management Feature Parameter Description 7 Manual Management of Neighbor Relations
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
32
HO whitelists are especially useful in an early phase of network construction, where usually
only a small number of UEs exist. Therefore, the best practice for collecting neighbor relation
information quickly is to prohibit ANR from automatically removing neighbor relations.
To whitelist a neighbor relation, perform the following steps: Log in to the M2000 client.
Choose Configuration > LTE Self Optimization > ANR Management. On the Neighbor
Cell Management tab page, select a neighbor relation to be whitelisted in the Neighboring
Cell pane. Set Deletion Prohibited to TRUE and Handover Prohibited to FALSE in the
displayed Set dialog box.
Alternatively, you can set NoHoFlag to PERMIT_HO_ENUM(Permit Ho) and
NoRmvFlag to FORBID_RMV_ENUM(Forbid ANR Remove) to whitelist a neighbor
relation.
For a neighbor relation with an intra-frequency E-UTRAN cell, they belong to the
NoHoFlag and NoRmvFlag parameters.
For a neighbor relation with an inter-frequency E-UTRAN cell, they belong to the
NoHoFlag and NoRmvFlag parameters.
For a neighbor relation with a UTRAN cell, they belong to the NoHoFlag and
NoRmvFlag parameters.
For a neighbor relation with a GERAN cell, they belong to the NoHoFlag and
NoRmvFlag parameters.
7.4.2 Configuring an X2 Whitelist
X2 whitelists can only be configured manually.
An X2 whitelist is especially useful when it needs a long time to maintain an eNodeB. During
maintenance, the eNodeB cannot provide any services, and the NRTs of this eNodeB and its
surrounding eNodeBs may change. To prevent these changes, you can add associated
eNodeBs to the X2 whitelist. To configure an X2 whitelist, perform the following steps:
Log in to the M2000 client. Choose Configuration > LTE Self Optimization > ANR
Management. On the X2 Mangement tab page, add an X2 interface to the X2 whitelist. You
can also query the X2 whitelist on this tab page. Alternatively, you can use the
X2BlackWhiteList MO to configure an X2 whitelist.
eRAN
ANR Management Feature Parameter Description 8 X2 Automatic Management
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
33
8 X2 Automatic Management
8.1 Overview
This chapter describes X2 automatic management, which is involved in TDLOFD-002004
Self-configuration and TDLOFD-002001 Automatic Neighbour Relation (ANR).
X2 automatic management involves self-setup and self-removal of X2 interfaces. It also
involves automatic eNodeB configuration updates based on X2 messages.
8.2 X2 Self-Setup
X2 self-setup is divided into X2-C self-setup and X2-U self-setup, where X2-C and X2-U
refer to X2 control plane and X2 user plane, respectively. An X2 interface can be configured
in link configuration mode or end point configuration mode (also called self-setup mode). For
details on the two modes, see S1/X2/OM Channel Management Feature Parameter Description.
Depending on whether the SctpPeer (control-plane peer) and UserPlanePeer (user-plane
peer) MOs are manually configured, eNodeBs support the following methods of X2 self-setup
in generic scenarios:
X2 self-setup with SctpPeer and UserPlanePeer manually configured: The eNodeB
directly sets up an X2 interface based on the SctpPeer and UserPlanePeer MOs. One
SctpPeer and one UserPlanePeer is used to set up one X2 interface. Therefore, multiple
SctpPeer and UserPlanePeer MOs are required to set up multiple X2 interfaces.
X2 self-setup with SctpPeer and UserPlanePeer automatically configured: An X2
interface can be automatically set up in two modes: X2 over M2000 and X2 over S1, as
specified by the X2SonLinkSetupType parameter. Both modes require that neighboring
cell information (which can be collected by ANR or manually configured) be available
and the X2 self-setup switch (specified by the X2SonSetupSwitch parameter) be set to
ON(On). After a handover is triggered, the serving eNodeB can obtain the configuration
information about the neighboring eNodeB. Based on this information, the X2 interface
between the two eNodeBs is automatically set up.
X2 self-setup reduces configuration operations by users. Users need only to configure the local IP
addresses of each eNodeB. An eNodeB automatically obtains the IP addresses of a peer eNodeB and sets
up an X2 interface to the peer eNodeB. This document describes two X2 self-setup modes: X2 over S1
and X2 over M2000. For details about other modes, see S1X2OM Channel Management Feature
Parameter Description, which also provides descriptions of X2 self-setup in IPSec-enabled scenarios.
eRAN
ANR Management Feature Parameter Description 8 X2 Automatic Management
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
34
8.2.1 X2 Self-Setup in X2 over S1 Mode
X2 self-setup in X2 over S1 mode is enabled when the X2SonLinkSetupType parameter in
the GlobalProcSwitch MO is set to X2_OVER_S1. In this mode, the MME collects the
configuration information about neighboring eNodeBs. This mode is recommended because
there is no restriction on operators or mobile element management system (EMS). To enable
this function, the MME must support this function. The procedure is shown as follows:
Figure 8-1 Procedure for X2 self-setup in X2 over S1 mode
1. When a handover is triggered, the source eNodeB checks whether an X2 interface is
available between the source eNodeB and the target eNodeB. If the X2 interface is
available, an X2-based handover is performed. If the X2 interface is unavailable, an X2
self-setup in X2 over S1 mode.
2. The source eNodeB sends an eNodeB Configuration Transfer message to the MME. The
message contains the following information:
eRAN
ANR Management Feature Parameter Description 8 X2 Automatic Management
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
35
− Source eNB ID IE, which consists of the Global eNB ID and Selected TAI IEs
− Target eNB ID IE, which consists of the Global eNB ID and Selected TAI IEs
− Control-plane and user-plane IP addresses of the source eNodeB
3. The MME sends an MME Configuration Transfer message to the target eNodeB. This
message contains information about the source eNodeB. For details about the message,
see 3GPP TS 36.413.
4. After receiving the control-plane and user-plane IP addresses of the source eNodeB, the
target eNodeB uses these IP addresses and its own control-plane and user-plane IP
addresses to set up control-plane and user-plane bearers for the X2 interface. Then, the
target eNodeB responds to the MME with an eNodeB Configuration Transfer message,
which contains the control-plane and user-plane IP addresses of the target eNodeB.
5. The MME sends an MME Configuration Transfer message to the source eNodeB.
6. After receiving the control-plane and user-plane IP addresses of the target eNodeB, the
source eNodeB uses these IP addresses and its own control-plane and user-plane IP
addresses to set up control-plane and user-plane bearers for the X2 interface.
7. When signaling exchange over the S1 interface is complete, the source eNodeB responds
to the request. The X2 interface is automatically set up.
8. If a handover between the two eNodeBs is triggered after the X2 setup, the handover will
be performed through the X2 interface.
8.2.2 X2 Self-Setup in X2 over M2000 Mode
X2 self-setup in X2 over M2000 mode is enabled when the X2SonLinkSetupType parameter
in the GLOBALPROCSWITCH MO is set to X2_OVER_M2000. In this mode, the M2000
collects the configuration information about neighboring eNodeBs. This mode applies when
the source eNodeB and the target eNodeB are managed by the same M2000. The procedure is
shown as follows:
eRAN
ANR Management Feature Parameter Description 8 X2 Automatic Management
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
36
Figure 8-2 Procedure for X2 self-setup in X2 over M2000 mode
1. When a handover is triggered, the source eNodeB checks whether an X2 interface is
available between the source eNodeB and the target eNodeB. If the X2 interface is
available, an X2-based handover is performed. If the X2 interface is unavailable, an
S1-based handover is performed. At the same time, the source eNodeB triggers an X2
self-setup in X2 over M2000 mode. The procedure goes to step 2.
2. The source eNodeB sends a Configuration_transfer message to the M2000. The message
contains the X2-related parameters (such as the control-plane IP address, user-plane IP
address, and PLMN ID) of the source eNodeB.
3. After receiving the message, the M2000 transfers the message to the target eNodeB
identified by the target eNodeB ID.
4. The target eNodeB sends a Configuration_transfer message to the M2000, which
contains the control-plane and user-plane IP addresses of the target eNodeB.
5. Then, the M2000 forwards this message to the source eNodeB.
6. The source eNodeB automatically sets up an SCTP link and an IP path to the target
eNodeB based on the control-plane and user-plane IP addresses of the target eNodeB
contained in the Configuration_transfer message. The X2 interface is now set up.
eRAN
ANR Management Feature Parameter Description 8 X2 Automatic Management
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
37
8.3 X2 Automatic Removal
If the NRTs of two eNodeBs do not contain any neighbor relations between cells under the
two eNodeBs, the X2 interface between them will be automatically removed when the timer
specified by X2SonDeleteTimer expires. The X2 automatic removal function takes effect only
for X2-related MOs whose control mode is AUTO_MODE.
The following is a brief procedure for automatically removing an X2 interface:
1. The local eNodeB obtains the neighbor relations with the cells under each peer eNodeB
through 3GPP defined messages over X2 interfaces. Each time the local eNodeB
receives an X2 message, it updates the neighbor relations that it stores.
2. If the NRTs of the local eNodeB do not contain any neighbor relations with the cells
under a peer eNodeB, and the local eNodeB detects that the peer eNodeB's NRTs also do
not contain any neighbor relations with the cells under the local eNodeB, then the local
eNodeB starts the timer specified by X2SonDeleteTimer.
3. When the X2SonDeleteTimer expires, the local eNodeB checks whether the peer
eNodeB is a Huawei eNodeB. If yes, the procedure goes to step 4.
4. The local eNodeB sends a private message to the peer eNodeB. The message contains all
neighbor relations of the cells under the local eNodeB. In addition, the local eNodeB
requests the peer eNodeB to send back the neighbor relations of the cells under the peer
eNodeB. If no neighbor relation is configured between the cells under the local and peer
eNodeBs, the local eNodeB removes the X2 interface.
If the X2SonDeleteTimer parameter is set to 0, the X2 automatic removal function is disabled.
The X2 automatic removal function has the following special treatment:
X2 automatic removal is not triggered for a faulty X2 interface over which the neighbor
relation configurations of the eNodeBs cannot be exchanged.
If the local and peer eNodeBs have different X2SonDeleteTimer settings, the timer that
expires earlier takes effect.
If the value of the X2SonDeleteTimer parameter is 0 in the local eNodeB but not 0 in the
peer eNodeB, the peer eNodeB can remove the X2 interface between the two eNodeBs
but the local eNodeB cannot.
8.4 eNodeB Configuration Update Based on X2 Messages
If an X2 interface is configured between two eNodeBs, the eNodeB information is exchanged
through the X2 interface during an X2 setup and eNodeB configuration updates. For details
on the messages transmitted during X2 setups and eNodeB configuration updates, see section
8.3 in 3GPP TS 36.423 V10.0.0 (2010-12).
Figure 8-3 X2 setup
eRAN
ANR Management Feature Parameter Description 8 X2 Automatic Management
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
38
eNodeB 1 sends an X2 Setup Request message containing information about the local cell and
neighboring cell to eNodeB 2. eNodeB 2 responds with an X2 Setup Response message
containing information about the local cell and neighboring cell to eNodeB 1.
Figure 8-4 eNodeB configuration update
When the local cell or neighboring cell configuration changes in eNodeB 1, eNodeB 1 sends
an eNodeB Configuration Update message to eNodeB 2.
After the source or target eNodeB receives the message, it updates its configuration based on
the following principles:
When eNodeB 2 receives the X2 Setup Request message from eNodeB 1, and the
X2BasedUptENodeBCfgSwitch is set to ON(On), eNodeB 2 adds all the cells related to
eNodeB 1 to its NCL.
When eNodeB 1 receives the X2 Setup Response message from eNodeB 2, and the
X2BasedUptENodeBCfgSwitch is set to ON(On), eNodeB 1 adds all the cells related to
eNodeB 2 to its NCL.
After eNodeB 2 receives the eNodeB Configuration Update message from eNodeB 1, it
updates its NCL and NRTs if the X2BasedUptENodeBCfgSwitch is set to ON(On), and the
CtrlMode parameter of the corresponding neighbor relation is AUTO_MODE. The updated
information includes the operating frequency, PCI, ECGI, TAC, and PLMN list.
eRAN
ANR Management Feature Parameter Description 9 Related Features
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
39
9 Related Features
9.1 Features Related to TDLOFD-002001 Automatic Neighbour Relation (ANR)
Prerequisite Features
Intra-RAT ANR requires TDLBFD-002017 DRX. If ANR measurements need to be
performed, a temporary dedicated DRX cycle needs to be configured for the UE. During this
cycle, the UE obtains the CGIs of neighboring cells in sleep time. For details about DRX, see
DRX Feature Parameter Description.
Mutually Exclusive Features
If the serving cell and neighboring cell are not managed by the same M2000, the ANR
function cannot be used with the function of broadcasting the PLMN list in an RR manner,
which is provided in TDLOFD-001036 RAN Sharing with Common Carrier.
Impacted Features
Intra-RAT ANR affects TDLOFD-002007 PCI Collision Detection & Self-Optimization.
When neighboring cell information changes because of intra-RAT ANR, PCI conflict
detection is triggered.
Currently, Huawei eNodeB selects only non-CA UEs to perform ANR measurement. In the
early stage of network construction, there are few CA UEs in networks, and therefore
selecting only non-CA UEs does not affect ANR performance.
9.2 Features Related to TDLOFD-002002 Inter-RAT ANR
Prerequisite Features
Inter-RAT ANR requires TDLBFD-002017 DRX. If ANR measurements need to be
performed, a temporary dedicated DRX cycle needs to be configured for the UE. For details
about DRX, see DRX Feature Parameter Description.
eRAN
ANR Management Feature Parameter Description 9 Related Features
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
40
Mutually Exclusive Features
None
Impacted Features
Currently, Huawei eNodeB selects only non-CA UEs to perform ANR measurement. In the
early stage of network construction, there are few CA UEs in networks, and therefore
selecting only non-CA UEs does not affect ANR performance.
9.3 Features Related to TDLOFD-002004 Self-configuration
Prerequisite Features
Self-configuration requires TDLOFD-002001 Automatic Neighbour Relation (ANR).
Mutually Exclusive Features
None
Impacted Features
None
eRAN
ANR Management Feature Parameter Description 10 Network Impact
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
41
10 Network Impact
10.1 Intra-RAT ANR
System Capacity
No impact.
Network Performance
Intra-RAT event-triggered ANR introduces extra delays in the handovers of the UEs that meet
the handover conditions but are still performing periodic ANR measurements. In addition, this
function affects the UE throughput because UEs cannot be scheduled while reading the CGI
of an unknown cell during DRX periods.
Intra-RAT fast ANR has the following impact on network performance.
The UE throughput is unaffected during the process in which the UE periodically
measures intra-frequency neighboring cells and reports the PCI of the strongest
neighboring cell. The UE throughput drops when: The UE performs gap-assisted
measurements on inter-frequency neighboring cells.
The UE reads the CGI of an unknown cell during DRX periods. This drop occurs
because the UE cannot be scheduled during DRX periods.
The overall impact that fast ANR exerts over network performance is controllable and
acceptable because of the upper limits on the number of UEs involved in fast ANR per
cell and the number of periodic measurement reports by a UE within each period.
Intra-RAT ANR reduces service drops and handover failures caused by inappropriately
configured neighbor relations. As a result, the service drop rate decreases and the
intra-RAT handover success rates increase. Since many factors affect the handover
success rate and service drop rate, gains brought about by ANR cannot be measured.
Factors such as the number of UEs supporting ANR and UE distribution affect detection
of unknown neighboring cells when ANR is enabled.
The following key performance indicators (KPIs) are involved:
Intra-frequency Handover Success Rate
Inter-frequency Handover Success Rate
Service Drop Rate=(L.E-RAB.AbnormRel/L.E-RAB.NormRel + L.E-RAB.AbnormRel)
x 100%
eRAN
ANR Management Feature Parameter Description 10 Network Impact
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
42
Table 10-1 Intra-RAT ANR counters
Counter Name Counter Description
Intra-frequency Handover Success Rate Intra-frequency handover success rate
Inter-frequency Handover Success Rate Inter-frequency handover success rate
L.E-RAB.AbnormRel Total number of abnormal E-UTRA radio
access bearer (E-RAB) releases by the
eNodeB
L.E-RAB.NormRel Total number of normal E-RAB releases by
the eNodeB
10.2 Inter-RAT ANR
System Capacity
No impact.
Network Performance
Inter-RAT ANR has almost the same impact on network performance as intra-RAT ANR. The
difference is that inter-RAT ANR raises the following KPIs:
Inter-RAT Handover Out Success Rate (LTE to WCDMA) =
(L.IRATHO.E2W.ExecSuccOut/L.IRATHO.E2W.ExecAttOut) x 100%
Inter-RAT Handover Out Success Rate (LTE toTD-SCDMA) =
(L.IRATHO.E2T.ExecSuccOut/L.IRATHO.E2T.ExecAttOut) x 100%
Inter-RAT Handover Out Success Rate (LTE to GSM) =
(L.IRATHO.E2G.ExecSuccOut/L.IRATHO.E2G.ExecAttOut) x 100%
Table 10-2 Inter-RAT ANR counters
Counter Name Counter Description
L.IRATHO.E2W.ExecSuccOut Number of Successful Outgoing Handovers from
E-UTRAN to UTRAN
L.IRATHO.E2W.ExecAttOut Number of Performed Outgoing Handovers from
E-UTRAN to UTRAN
L.IRATHO.E2T.ExecSuccOut Number of Successful Outgoing Handovers from
E-UTRAN to TD-SCDMA
L.IRATHO.E2T.ExecAttOut Number of Performed Outgoing Handovers from
E-UTRAN to TD-SCDMA
L.IRATHO.E2G.ExecSuccOut Number of Successful Outgoing Handovers from
E-UTRAN to GERAN
L.IRATHO.E2G.ExecAttOut Number of Performed Outgoing Handovers from
eRAN
ANR Management Feature Parameter Description 10 Network Impact
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
43
Counter Name Counter Description
E-UTRAN to GERAN
10.3 ANR with Shared Cells
System Capacity
No impact.
Network Performance
If the switch for ANR with shared cells (specified by the RanSharingAnrSwitch parameter)
is turned on, the serving eNodeB of a UE may query the M2000 for the neighboring cell
information. The query time is long and, therefore, might affect the handover. If no other
neighboring cells are available for the handover, a service drop may occur. After the serving
eNodeB obtains the neighboring cell information from the M2000, the information can be
used in subsequent handovers to the neighboring cell.
ANR with shared cells decreases the service drop rate and increases handover success rates.
The related KPIs are as follows:
Intra-frequency Handover Out Success Rate
Inter-frequency Handover Out Success Rate
Handover In Success Rate
Service Drop Rate
Inter-RAT Handover Out Success Rate (LTE to WCDMA)
Inter-RAT Handover Out Success Rate (LTE to GSM)
10.4 X2 Automatic Management
System Capacity
No impact.
Network Performance
X2 self-setup reduces the workload required for manually planning and configuring X2
interfaces. In addition, after X2 self-setup is completed, X2-based handovers take less time
than S1-based handovers. X2 automatic removal enables X2 interface configurations to be
automatically updated. eNodeB configuration update based on X2 messages prevents
handover failures due to inconsistent configurations between two eNodeBs.
eRAN
ANR Management Feature Parameter Description 11 Engineering Guidelines for Intra-RAT ANR
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
44
11 Engineering Guidelines for Intra-RAT ANR
This chapter describes the process of deploying intra-RAT ANR.
11.1 When to Use Intra-RAT ANR
Intra-RAT ANR is classified into intra-RAT event-triggered ANR and intra-RAT fast ANR.
Use intra-RAT fast ANR when quick detection of neighbor relations is required, for example,
in the early stage of deployment or during network capacity expansion. Use intra-RAT
event-triggered ANR to supplement and optimize neighbor relations.
Intra-RAT Event-triggered ANR
A prerequisite for using intra-RAT event-triggered ANR is that operators have deployed
ANR-capable UEs on the network.
Intra-RAT event-triggered ANR is recommended in any of the following cases:
Network construction is in progress. The purpose is to complete and optimize existing
neighbor relations.
Network capacity expansion or eNodeB relocation has occurred. In this situation, cells or
eNodeBs are removed from one place and added to another, which causes changes to
neighbor relations. Intra-RAT event-triggered ANR can effectively deal with these types
of changes and achieve optimization.
Intra-RAT fast ANR is enabled. The neighboring cells detected using fast ANR are added
to NCLs in some scenarios. To use these neighboring cells for handovers, intra-RAT
event-triggered ANR is required.
Intra-RAT event-triggered ANR is not recommended if users want to manually manage
neighbor relations. In this situation, disable both intra-RAT event-triggered ANR and
intra-RAT fast ANR.
Consider automatic removal of neighbor relations as follows:
Automatic removal of neighbor relations is a function of intra-RAT event-triggered ANR.
This function takes effect when intra-RAT event-triggered ANR is enabled and
IntraRatAnrAutoDelSwitch is turned on. Enable this function if users want to use ANR to
automatically remove incorrect or redundant neighbor relations. Disable this function in an
eRAN
ANR Management Feature Parameter Description 11 Engineering Guidelines for Intra-RAT ANR
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
45
early stage of network deployment to prevent stable neighbor relations from being mistakenly
removed.
Intra-RAT Fast ANR
The following describes when to use intra-RAT fast ANR:
Enable intra-RAT fast ANR in the following scenarios:
− Operators have deployed ANR-capable UEs on the network.
− Network construction is at an early stage. The purpose is to quickly collect neighbor
relations.
− Network capacity expansion or eNodeB relocation has occurred. In this situation,
cells or eNodeBs are removed from one place and added to another, which causes
changes to neighbor relations. Intra-RAT fast ANR can effectively deal with these
types of changes and achieve optimization.
Disable intra-RAT event-triggered ANR in either of the following cases:
− The network is well constructed and serves a moderate number of UEs, and basic
neighbor relations have been configured.
− Users want to manually manage neighbor relations.
If both event-triggered ANR and fast ANR are enabled, the eNodeB detects missing neighboring cells
using both event-based and periodic measurements.
11.2 Required Information Proportion and distribution of UEs that support intra-RAT intra- or inter-frequency ANR
in the network
Networking mode: intra-frequency or inter-frequency
11.3 Deployment
11.3.1 Process
None
11.3.2 Requirements
UEs on the network support ANR-related measurements on intra- or inter-frequency
neighboring cells and are DRX-capable. The eNodeB is not required to support DRX.
For details about DRX, see DRX and Signaling Control Feature Parameter Description.
iManager M2000 V200R013C00 or later is used.
The intra-RAT measurement information (including frequencies to be measured) has
been configured. For details, see Mobility Management in Connected Mode Feature Parameter Description.
Operators have purchased and activated the license for the feature listed in Table 11-1.
eRAN
ANR Management Feature Parameter Description 11 Engineering Guidelines for Intra-RAT ANR
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
46
Table 11-1 License information for intra-RAT ANR
Feature ID Feature Name License Control Item NE Sales Unit
TDLOFD-00
2001
Automatic Neighbor
Relation (ANR)
Automatic Neighbour
Relation(ANR)(TDD)
eNodeB per cell
11.3.3 Data Preparation
There are three types of data sources:
Network plan (negotiation required): parameter values planned by the operator and
negotiated with the EPC or peer transmission equipment
Network plan (negotiation not required): parameter values planned and set by the
operator
User-defined: parameter values set by users
The following table describes the parameter that must be set to configure intra-RAT ANR.
Parameter Name
Parameter ID
Setting Notes Data Source
ANR
algorithm
switch
AnrSwitc
h
Select or clear the following check boxes
by referring to 11.1 When to Use
Intra-RAT ANR:
IntraRatEventAnrSwitch
IntraRatFastAnrSwitch
MlbBasedEventAnrSwitch
IntraRatAnrAutoDelSwitch
Network plan
(negotiation not
required)
11.3.4 Precautions
None
11.3.5 Hardware Adjustment
N/A
11.3.6 Activation
Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs
Enter the values of the parameters listed in Table 11-2 in a summary data file, which also
contains other data for the new eNodeBs to be deployed. Then, import the summary data file
into the Configuration Management Express (CME) for batch configuration. For detailed
instructions, see section "Creating eNodeBs in Batches" in the initial configuration guide for
the eNodeB.
eRAN
ANR Management Feature Parameter Description 11 Engineering Guidelines for Intra-RAT ANR
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
47
The summary data file may be a scenario-specific file provided by the CME or a customized
file, depending on the following conditions:
The managed objects (MOs) in Table 11-2 are contained in a scenario-specific summary
data file. In this situation, set the parameters in the MOs, and then verify and save the
file.
Some MOs in Table 11-2 are not contained in a scenario-specific summary data file. In
this situation, customize a summary data file to include the MOs before you can set the
parameters.
Table 11-2 Intra-RAT ANR parameter
MO Sheet in the Summary Data File
Parameter Group Remarks
ENodeB
AlgoSwit
ch
User-defined sheet.
ENodeBAlgoSwitch is
recommended.
ANR algorithm
switch
N/A
Using the CME to Perform Batch Configuration for Existing eNodeBs
Batch reconfiguration using the CME is the recommended method to activate a feature on
existing eNodeBs. This method reconfigures all data, except neighbor relationships, for
multiple eNodeBs in a single procedure. The procedure is as follows:
Step 1 Choose CME > Advanced > Customize Summary Data File from the main menu of an
M2000/DOMC920 client, or choose Advanced > Customize Summary Data File from the
main menu of a CME client, to customize a summary data file for batch reconfiguration.
For context-sensitive help on a current task in the client, press F1.
Step 2 Choose CME > LTE Application > Export Data >Export Base Station Bulk
Configuration Data from the main menu of the M2000/DOMC920 client, or choose LTE
Application > Export Data >Export Base Station Bulk Configuration Data from the main
menu of the CME client, to export the eNodeB data stored on the CME into the customized
summary data file.
Step 3 In the summary data file, set the parameters in the MOs listed in "Using the CME to Perform
Batch Configuration for Newly Deployed eNodeBs" and close the file.
Step 4 Choose CME > LTE Application > Import Data > Import Base Station Bulk
Configuration Data from the main menu of the M2000/DOMC920 client, or choose LTE
Application> Import Data > Import Base Station Bulk Configuration Data from the main
menu of the CME client, to import the summary data file into the CME.
Step 5 Choose CME > Planned Area > Export Incremental Scripts from the main menu of the
M2000/DOMC920 client, or choose Area Management > Planned Area > Export
Incremental Scripts from the main menu of the CME client, to export and activate the
incremental scripts.
----End
eRAN
ANR Management Feature Parameter Description 11 Engineering Guidelines for Intra-RAT ANR
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
48
Using the CME to Perform Single Configuration
On the CME, set the parameters listed in the "Data Preparation" section for a single eNodeB.
The procedure is as follows:
Step 1 In the planned data area, click Base Station in the upper left corner of the configuration
window.
Step 2 In area 1 shown in Figure 11-1, select the eNodeB to which the MOs belong.
Figure 11-1 MO search and configuration window
Step 3 On the Search tab page in area 2, enter an MO name, for example, CELL.
Step 4 In area 3, double-click the MO in the Object Name column. All parameters in this MO are
displayed in area 4.
Step 5 Set the parameters in area 4 or 5.
Step 6 Choose CME > Planned Area > Export Incremental Scripts (M2000/DOMC920 client
mode), or choose Area Management > Planned Area > Export Incremental Scripts (CME
client mode), to export and activate the incremental scripts.
----End
Using MML Commands Activating Intra-RAT Event-triggered ANR
Run the MOD ENODEBALGOSWITCH command with the
IntraRatEventAnrSwitch(IntraRatEventAnrSwitch) check box selected under the
ANR algorithm switch parameter.
Command:
eRAN
ANR Management Feature Parameter Description 11 Engineering Guidelines for Intra-RAT ANR
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
49
MOD ENODEBALGOSWITCH:AnrSwitch=IntraRatEventAnrSwitch-1;
Activating Automatic Removal of Neighbor Relations for Intra-RAT ANR
Run the MOD ENODEBALGOSWITCH command with both the
IntraRatAnrAutoDelSwitch(IntraRatAnrAutoDelSwitch) and
IntraRatEventAnrSwitch(IntraRatEventAnrSwitch) check boxes selected under the
ANR algorithm switch parameter.
Command:
MOD
ENODEBALGOSWITCH:AnrSwitch=IntraRatEventAnrSwitch-1&IntraRatAnrAutoDel
Switch-1;
Activating Intra-RAT Fast ANR
Run the MOD ENODEBALGOSWITCH command with the
IntraRatFastAnrSwitch(IntraRatFastAnrSwitch) check box selected under the ANR
algorithm switch parameter.
Command:
MOD ENODEBALGOSWITCH:AnrSwitch=IntraRatFastAnrSwitch-1;
11.3.7 Activation Observation
By using signaling tracing, checking SON logs on the M2000 client, or running an MML
command, you can check whether intra-RAT ANR has been activated.
Signaling Tracing
Create and start a Uu interface tracing task. Remove the configurations of some neighbor
relations so that there are missing neighboring cells within the network. If a UE reports an
ECGI during an intra-RAT handover as indicated in the traced signaling, intra-RAT ANR has
been activated.
Figure 11-2 Uu tracing result for intra-RAT ANR observation
eRAN
ANR Management Feature Parameter Description 11 Engineering Guidelines for Intra-RAT ANR
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
50
SON Logs on the M2000 Client
To use SON logs to verify whether intra-RAT ANR takes effect, perform the following steps:
Step 1 On the M2000 client, choose SON>SON Log. On the Query SON Log tab page, select LTE
ANR Log from the Log Category drop-down list in the upper left corner.
Step 2 In the Event Name area, select items such as Set ANR Switch, Add Neighboring Cell,
Delete Neighboring Cell, Add External Cell, and Delete External Cell one at a time to
check different types of ANR operations.
----End
MML Commands
To use man-machine language (MML) commands to verify whether intra-RAT ANR takes
effect, do as follows:
Run the LST EUTRANINTRAFREQNCELL command and the LST
EUTRANINTERFREQNCELL command to list parameters of neighbor relations with
intra- and inter-frequency E-UTRAN cells, respectively. In the command outputs, check the
value of ANR flag. If ANR flag is True, the intra-RAT neighbor relation is configured by
ANR. If ANR flag is False, the intra-RAT neighbor relation is manually configured.
11.3.8 Reconfiguration
None
11.3.9 Deactivation
Using the CME to Perform Batch Configuration
Batch reconfiguration using the CME is the recommended method to deactivate a feature on
eNodeBs. This method reconfigures all data, except neighbor relationships, for multiple
eNodeBs in a single procedure. The procedure for feature deactivation is similar to that for
feature activation described in Using the CME to Perform Batch Configuration for Existing
eNodeBs. In the procedure, modify parameters according to Table 11-3.
Table 11-3 Intra-RAT ANR parameter
MO Sheet in the Summary Data File
Parameter Group
Setting Notes
ENodeBAlgoSwit
ch
User-defined sheet ANR
algorithm
switch
Turn off :
IntraRatEventAnrSwitch
IntraRatFastAnrSwitch
MlbBasedEventAnrSwitch
IntraRatAnrAutoDelSwitch
eRAN
ANR Management Feature Parameter Description 11 Engineering Guidelines for Intra-RAT ANR
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
51
Using the CME to Perform Single Configuration
On the CME, set parameters according to Table 11-3. For detailed instructions, see 11.3.6
Activation described for feature activation.
Using MML Commands Deactivating Intra-RAT Event-triggered ANR
Run the MOD ENODEBALGOSWITCH command with the
IntraRatEventAnrSwitch(IntraRatEventAnrSwitch) check box cleared under the
ANR algorithm switch parameter.
Example:
MOD ENODEBALGOSWITCH: AnrSwitch=IntraRatEventAnrSwitch-0;
Clear only the IntraRatAnrAutoDelSwitch(IntraRatAnrAutoDelSwitch) check box if
you disable only automatic removal of neighbor relations for intra-RAT ANR.
Example:
MOD ENODEBALGOSWITCH: AnrSwitch=IntraRatAnrAutoDelSwitch-0;
Deactivating Intra-RAT Fast ANR
Run the MOD ENODEBALGOSWITCH command with the
IntraRatFastAnrSwitch(IntraRatFastAnrSwitch) check box cleared under the ANR
algorithm switch parameter.
Example:
MOD ENODEBALGOSWITCH: AnrSwitch=IntraRatFastAnrSwitch-0;
11.4 Performance 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 following table lists the performance counters that reflect the network performance after
intra-RAT ANR is enabled.
Counter Name Description
L.IntraFreqHO.NoNRT Number of intra-frequency handover initiation failures due to
the target cell not being configured as a neighboring cell for
the source cell
L.InterFreqHO.NoNRT Number of inter-frequency handover initiation failures due to
the target cell not being configured as a neighboring cell for
the source cell
After intra-RAT neighbor relations are configured, the values of these counters decrease.
eRAN
ANR Management Feature Parameter Description 11 Engineering Guidelines for Intra-RAT ANR
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
52
11.5 Parameter Optimization
The following parameters may need to be modified after intra-RAT ANR is activated.
Parameter Name Parameter ID Setting Notes
ANR delete cell
threshold DelCellThd This parameter specifies the handover success
rate threshold, which is used in the evaluation for
removing a neighbor relation from the intra-RAT
NRT. A larger parameter value results in a
higher probability of removing a neighbor
relation from this NRT. The default value is 0 so
that it is difficult to remove a neighbor relation.
Least Handover
Num for Statistic
NcellHoStatNu
m
This parameter specifies the threshold for the
number of handovers to neighboring cells, which
is used in the evaluation for removing a neighbor
relation from the intra-RAT NRT based on the
handover success rate. A larger parameter value
results in more stable neighbor relations in the
intra-RAT NRT; however, updates to this NRT
take longer. If only a small number of UEs are
involved in periodic measurements on the live
network, decrease this parameter value to
accelerate NRT updates.
Statistic cycle StatisticPeriod This parameter specifies the measurement
period, which is used in the evaluation for
removing a neighbor relation from the intra-RAT
NRT based on the handover success rate. At the
end of this period, the eNodeB automatically
analyzes neighbor relations. A larger parameter
value may result in more UE handover requests;
however, updates to the intra-RAT NRT take
longer. Tune this parameter based on the total
number of daily handover requests on the live
network. If many UEs are involved in periodic
measurements, decrease this parameter value to
accelerate NRT updates.
Statistic Number
For Delete NRT
StatisticNumFo
rNRTDel
This parameter indicates the number of
handovers above which a neighbor relationship
is to be removed from an NRT when the number
of neighbor relationships in the NRT has reached
the maximum specification and a new neighbor
relationship is to be added to the NRT by ANR.
A larger parameter value indicates a stricter
removal condition.
Statistic Cycle For
Delete NRT
StatisticPeriodF
orNRTDel
This parameter indicates the period during which
the number of handovers are measured for
neighbor relationship removal from an NRT
when the number of neighbor relationships in the
NRT has reached the maximum specification and
a new neighbor relationship is to be added to the
NRT by ANR. A larger parameter value
eRAN
ANR Management Feature Parameter Description 11 Engineering Guidelines for Intra-RAT ANR
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
53
Parameter Name Parameter ID Setting Notes
indicates a stricter removal condition.
Fast ANR PCI
report amount
FastAnrRprtAm
ount
This parameter specifies the maximum number
of periodic measurement reports sent by a UE
during each fast ANR procedure. It indirectly
determines the total time period during which a
UE sends periodic reports.
If only a small number of UEs are involved in
periodic measurements, increase the parameter
value. Otherwise, decrease it.
If services on most of the UEs have relatively
high priorities according to QoS class identifiers
(QCIs), decrease this parameter value to ensure
service quality and reduce power consumption of
the UEs.
Fast ANR PCI
report interval
FastAnrRprtInt
erval
This parameter specifies the interval at which a
UE sends periodic measurement reports. A
smaller parameter value indicates a shorter
interval. Tune this parameter based on the
movement speed of most UEs involved. If most
of the UEs move quickly through a constantly
changing set of neighboring cells, decrease the
parameter value to shorten this interval.
Otherwise, increase the parameter value.
Fast ANR checking
period
FastAnrCheckP
eriod
This parameter specifies the interval at which the
eNodeB checks whether the total number of UEs
involved in periodic measurements reaches the
upper limit. If only a few UEs participate in fast
ANR, increase this parameter value. Otherwise,
decrease it.
If services on most of the UEs have relatively
high priorities according to QCIs, decrease this
parameter value to ensure service quality and
reduce power consumption of the UEs.
Fast ANR
measurement RSRP
threshold
FastAnrRsrpTh
d
This parameter specifies the RSRP requirement
for adding a neighboring cell to the NCL. A
larger parameter value results in a higher RSRP
requirement, and therefore the neighboring cells
in the NCL have higher RSRP quality. In urban
areas with densely distributed cells, increase the
parameter value to ensure that only high-quality
neighboring cells are added to the NCL. In
contrast, in sparsely populated areas, decrease
this parameter value to add the neighboring cells
with low cell-edge RSRP to the NCL.
IntraRat Fast ANR
measurement UE
number
FastAnrIntraRa
tMeasUeNum
This parameter specifies the maximum number
of UEs that can be concurrently involved in
measurements for intra-RAT fast ANR. A larger
parameter value results in more UEs that can
concurrently perform fast ANR measurements.
eRAN
ANR Management Feature Parameter Description 11 Engineering Guidelines for Intra-RAT ANR
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
54
Parameter Name Parameter ID Setting Notes
In this situation, neighboring cells can be quickly
detected. However, this affects the service
quality for these UEs and network throughput.
IntraRat Fast ANR
valid measurement
min UE number
FastAnrIntraRa
tUeNumThd
This parameter specifies the threshold for
entering the monitoring state for fast ANR. This
threshold is expressed as the number of UEs that
have performed measurements for fast ANR. A
larger parameter value results in a larger total
number of UEs that are involved in
measurements for intra-RAT fast ANR. In this
situation, the UEs involved can be distributed
more randomly throughout the network, reducing
the probability of missing neighboring cells.
However, a larger parameter value affects the
service quality for these UEs and network
throughput.
Optimization Mode OptMode This parameter specifies the mode for optimizing
neighbor relations. If users allow ANR to
automatically optimize neighbor relations, set
this parameter to FREE(FREE). If users require
manual confirmation on the M2000 client before
neighbor relations are optimized, set this
parameter to
CONTROLLED(CONTROLLED).
11.6 Troubleshooting
Fault Description
An intra- or inter-frequency handover fails.
Fault Handling
Perform the following steps to check whether this handover failure is caused by incorrect
ANR configuration:
Step 1 Start a Uu interface tracing task for the source cell on the M2000 client. In the tracing result,
check whether the eNodeB has delivered a handover command. A handover command was
delivered if the RRC_CONN_RECFG message contains the IE mobilityControlInfo, as
shown in the following figure.
eRAN
ANR Management Feature Parameter Description 11 Engineering Guidelines for Intra-RAT ANR
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
55
If the eNodeB has not delivered the handover command, go to Step 2.
If the eNodeB has delivered the handover command, contact Huawei technical support.
Step 2 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 relation between the source and target
cells has been configured on the source cell.
If they have not been configured, go to Step 3.
If they have been configured, contact Huawei technical support.
In RAN sharing with common carriers mode, if the UE is subscribed to a secondary operator, you also
need to check whether the PLMN ID of the secondary operator has been configured. If the PLMN ID
has not been configured, configure it.
Step 3 Check whether the switch for intra-RAT event-triggered ANR has been turned on.
If the switch is turned off, turn it on.
If the switch is turned on, go to Step 4.
Step 4 Check whether the UE supports intra-RAT ANR by referring to 3.7 ANR Capabilities of UEs.
If the UE supports intra-RAT ANR, contact Huawei technical support.
If the UE does not support intra-RAT ANR, no further action is required.
----End
eRAN
ANR Management Feature Parameter Description 12 Engineering Guidelines for Inter-RAT ANR
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
56
12 Engineering Guidelines for Inter-RAT ANR
This chapter describes the process of deploying inter-RAT ANR.
12.1 When to Use Inter-RAT ANR
Inter-RAT ANR is classified into inter-RAT event-triggered ANR and inter-RAT fast ANR.
Make the same considerations when determining whether to use inter-RAT ANR as when
determining whether to use intra-RAT ANR. For details, see 11.1 When to Use Intra-RAT
ANR.
12.2 Required Information Proportion and distribution of UEs that support inter-RAT ANR in the network
RAT (UTRAN or GERAN) that constructs inter-RAT networking with the E-UTRAN
12.3 Deployment
12.3.1 Process
None
12.3.2 Requirements
UEs on the network support ANR-related measurements on inter-RAT neighboring cells
and are DRX-capable. The eNodeB is not required to support DRX. For details about
DRX, see DRX and Signaling Control Feature Parameter Description.
iManager M2000 V200R013C00 or later is used.
The inter-RAT measurement information (including frequencies to be measured) has
been configured. For details, see Mobility Management in Connected Mode Feature
Parameter Description.
Operators have purchased and activated the license for the feature listed in Table 12-1.
eRAN
ANR Management Feature Parameter Description 12 Engineering Guidelines for Inter-RAT ANR
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
57
Table 12-1 License information for inter-RAT ANR
Feature ID
Feature Name License Control Item NE Sales Unit
TDLOFD-
002002
Inter-RAT ANR Inter-RAT ANR eNodeB per cell
12.3.3 Data Preparation
There are three types of data sources:
Network plan (negotiation required): parameter values planned by the operator and
negotiated with the EPC or peer transmission equipment
Network plan (negotiation not required): parameter values planned and set by the
operator
User-defined: parameter values set by users
The following table describes the parameter that must be set in the EnodeBAlgoSwitch MO
to enable inter-RAT ANR.
Parameter Name
Parameter ID
Setting Notes Data Source
ANR
algorithm
switch
AnrSwitc
h
Select or clear the following check boxes by
referring to 12.1 When to Use Inter-RAT
ANR:
UtranEventAnrSwitch
UtranFastAnrSwitch
UtranAutoNrtDeleteSwitch
GeranEventAnrSwitch
GeranFastAnrSwitch
GeranAutoNrtDeleteSwitch
MlbBasedEventAnrSwitch
Network plan
(negotiation not
required)
The following table describes the parameter that must be set in the DRX MO to configure the
long DRX cycle that is specific for inter-RAT ANR.
Parameter Name
Parameter ID
Setting Notes Data Source
Long
DRX
Cycle for
Inter-RAT
ANR
LongDR
XCyclefo
rIRatAnr
Set this parameter based on the networking
mode collected in 12.2 Required Information:
If a neighboring UTRAN exists, set this
parameter to SF1280(1280 subframes),
which is the default value.
If a neighboring GERAN exists, set this
parameter to SF2560(2560 subframes).
If both exist, set this parameter to
Network plan
(negotiation
not required)
eRAN
ANR Management Feature Parameter Description 12 Engineering Guidelines for Inter-RAT ANR
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
58
Parameter Name
Parameter ID
Setting Notes Data Source
SF2560(2560 subframes).
12.3.4 Precautions
None
12.3.5 Hardware Adjustment
N/A
12.3.6 Activation
Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs
Enter the values of the parameters listed in Table 12-2 in a summary data file, which also
contains other data for the new eNodeBs to be deployed. Then, import the summary data file
into the Configuration Management Express (CME) for batch configuration. For detailed
instructions, see section "Creating eNodeBs in Batches" in the initial configuration guide for
the eNodeB.
The summary data file may be a scenario-specific file provided by the CME or a customized
file, depending on the following conditions:
The managed objects (MOs) in Table 12-2 are contained in a scenario-specific summary
data file. In this situation, set the parameters in the MOs, and then verify and save the
file.
Some MOs in Table 12-2 are not contained in a scenario-specific summary data file. In
this situation, customize a summary data file to include the MOs before you can set the
parameters.
Table 12-2 Parameters related to inter-RAT ANR
MO Sheet in the Summary Data File
Parameter Group Remarks
ENodeBAlgoS
witch ENodeBAlgoSwitch ANR algorithm switch User-defined
sheet
Using the CME to Perform Batch Configuration for Existing eNodeBs
Batch reconfiguration using the CME is the recommended method to activate a feature on
existing eNodeBs. This method reconfigures all data, except neighbor relationships, for
multiple eNodeBs in a single procedure. The procedure is as follows:
Step 1 Choose CME > Advanced > Customize Summary Data File from the main menu of an
M2000/DOMC920 client, or choose Advanced > Customize Summary Data File from the
main menu of a CME client, to customize a summary data file for batch reconfiguration.
eRAN
ANR Management Feature Parameter Description 12 Engineering Guidelines for Inter-RAT ANR
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
59
For context-sensitive help on a current task in the client, press F1.
Step 2 Choose CME > LTE Application > Export Data >Export Base Station Bulk
Configuration Data from the main menu of the M2000/DOMC920 client, or choose LTE
Application > Export Data >Export Base Station Bulk Configuration Data from the main
menu of the CME client, to export the eNodeB data stored on the CME into the customized
summary data file.
Step 3 In the summary data file, set the parameters in the MOs listed in "Using the CME to Perform
Batch Configuration for Newly Deployed eNodeBs" and close the file.
Step 4 Choose CME > LTE Application > Import Data > Import Base Station Bulk
Configuration Data from the main menu of the M2000/DOMC920 client, or choose LTE
Application> Import Data > Import Base Station Bulk Configuration Data from the main
menu of the CME client, to import the summary data file into the CME.
Step 5 Choose CME > Planned Area > Export Incremental Scripts from the main menu of the
M2000/DOMC920 client, or choose Area Management > Planned Area > Export
Incremental Scripts from the main menu of the CME client, to export and activate the
incremental scripts.
----End
Using the CME to Perform Single Configuration
On the CME, set the parameters listed in the "Data Preparation" section for a single eNodeB.
The procedure is as follows:
Step 1 In the planned data area, click Base Station in the upper left corner of the configuration
window.
Step 2 In area 1 shown in Figure 12-1, select the eNodeB to which the MOs belong.
eRAN
ANR Management Feature Parameter Description 12 Engineering Guidelines for Inter-RAT ANR
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
60
Figure 12-1 MO search and configuration window
Step 3 On the Search tab page in area 2, enter an MO name, for example, CELL.
Step 4 In area 3, double-click the MO in the Object Name column. All parameters in this MO are
displayed in area 4.
Step 5 Set the parameters in area 4 or 5.
Step 6 Choose CME > Planned Area > Export Incremental Scripts (M2000/DOMC920 client
mode), or choose Area Management > Planned Area > Export Incremental Scripts (CME
client mode), to export and activate the incremental scripts.
----End
Using MML Commands Activating Event-triggered ANR with UTRAN
Run the MOD ENODEBALGOSWITCH command with the
UtranEventAnrSwitch(UtranEventAnrSwitch) check box selected under the ANR
algorithm switch parameter. To enable automatic removal of neighbor relations with
UTRAN cells, also select the UtranAutoNrtDeleteSwitch(UtranAutoNrtDeleteSwitch)
check box under the ANR algorithm switch parameter.
Example:
MOD ENODEBALGOSWITCH: AnrSwitch=UtranEventAnrSwitch-1;
Activating Fast ANR with UTRAN
Run the MOD ENODEBALGOSWITCH command with the
UtranFastAnrSwitch(UtranFastAnrSwitch) check box selected under the ANR
algorithm switch parameter.
Command:
eRAN
ANR Management Feature Parameter Description 12 Engineering Guidelines for Inter-RAT ANR
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
61
MOD ENODEBALGOSWITCH: AnrSwitch=UtranFastAnrSwitch-1;
Activating Event-triggered ANR with GERAN
Run the MOD ENODEBALGOSWITCH command with the
GeranEventAnrSwitch(GeranEventAnrSwitch) check box selected under the ANR
algorithm switch parameter. To enable automatic removal of neighbor relations with
GERAN cells, also select the
GeranAutoNrtDeleteSwitch(GeranAutoNrtDeleteSwitch) check box under the ANR
algorithm switch parameter.
Example:
MOD ENODEBALGOSWITCH: AnrSwitch=GeranEventAnrSwitch-1;
Activating Fast ANR with GERAN
Run the MOD ENODEBALGOSWITCH command with the
GeranFastAnrSwitch(GeranFastAnrSwitch) check box selected under the ANR
algorithm switch parameter.
Command:
MOD ENODEBALGOSWITCH: AnrSwitch=GeranFastAnrSwitch-1;
12.3.7 Activation Observation
The procedure for observing the activation of inter-RAT ANR is similar to that of intra-RAT
ANR. For details, see 11.3.7 Activation Observation.
The commands used to list parameters of neighbor relations with UTRAN cells and GERAN
cells are LST UTRANNCELL and LST GERANNCELL, respectively. The command
output of each command includes the ANR flag field. If ANR flag is True, the inter-RAT
neighbor relation is configured by ANR. If ANR flag is False, the inter-RAT neighbor
relation is manually configured.
12.3.8 Reconfiguration
None
12.3.9 Deactivation
Using the CME to Perform Batch Configuration
Batch reconfiguration using the CME is the recommended method to deactivate a feature on
eNodeBs. This method reconfigures all data, except neighbor relationships, for multiple
eNodeBs in a single procedure. The procedure for feature deactivation is similar to that for
feature activation described in Using the CME to Perform Batch Configuration for Existing
eNodeBs. In the procedure, modify parameters according to Table 12-3.
Table 12-3 Parameters related to inter-RAT ANR
MO Sheet in the Summary Data File
Parameter Group
Setting Notes
ENodeBAlg
oSwitch
User-defined sheet ANR algorithm
switch
Turn off the corresponding
switches:
UtranEventAnrSwitch
GeranEventAnrSwitch
eRAN
ANR Management Feature Parameter Description 12 Engineering Guidelines for Inter-RAT ANR
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
62
MO Sheet in the Summary Data File
Parameter Group
Setting Notes
UtranFastAnrSwitch
GeranFastAnrSwitch
UtranAutoNrtDeleteSwitch
GeranAutoNrtDeleteSwitch
MlbBasedEventAnrSwitch
Using the CME to Perform Single Configuration
On the CME, set parameters according to Table 12-3. For detailed instructions, see 13.3.6
Activation described for feature activation.
Using MML Commands Deactivating Event-triggered ANR with UTRAN
Run the MOD ENODEBALGOSWITCH command to turn off
UtranEventAnrSwitch(UtranEventAnrSwitch) under the ANR algorithm switch
parameter. Turn off only UtranAutoNrtDeleteSwitch(UtranAutoNrtDeleteSwitch) if
you disable only automatic removal of neighbor relations with UTRAN cells.
Example:
MOD ENODEBALGOSWITCH: AnrSwitch=UtranEventAnrSwitch-0;
Deactivating Fast ANR with UTRAN
Run the MOD ENODEBALGOSWITCH command to turn off
UtranFastAnrSwitch(UtranFastAnrSwitch) under the ANR algorithm switch
parameter.
Command:
MOD ENODEBALGOSWITCH: AnrSwitch=UtranFastAnrSwitch-0;
Deactivating Event-triggered ANR with GERAN
Run the MOD ENODEBALGOSWITCH command to turn off
GeranEventAnrSwitch(GeranEventAnrSwitch) under the ANR algorithm switch
parameter. Turn off only GeranAutoNrtDeleteSwitch(GeranAutoNrtDeleteSwitch) if
you disable only automatic removal of neighbor relations with GERAN cells.
Example:
MOD ENODEBALGOSWITCH: AnrSwitch=GeranEventAnrSwitch-0;
Deactivating Fast ANR with GERAN
Run the MOD ENODEBALGOSWITCH command to turn off
GeranFastAnrSwitch(GeranFastAnrSwitch) under the ANR algorithm switch
parameter.
Command:
MOD ENODEBALGOSWITCH: AnrSwitch=GeranFastAnrSwitch-0;
eRAN
ANR Management Feature Parameter Description 12 Engineering Guidelines for Inter-RAT ANR
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
63
12.4 Performance Monitoring
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.
The following table lists the counters that reflect the network performance after inter-RAT
ANR is enabled.
Counter Name Description
L.IRATHO.E2W.NoNRT Number of handover initiation failures from E-UTRAN to
WCDMA networks due to the target cell not being
configured as a neighboring cell for the source cell
L.IRATHO.E2T.NoNRT Number of handover initiation failures from E-UTRAN to
TD-SCDMA networks due to the target cell not being
configured as a neighboring cell for the source cell
L.IRATHO.E2G.NoNRT Number of handover initiation failures from E-UTRAN to
GERAN due to the target cell not being configured as a
neighboring cell for the source cell
After inter-RAT neighbor relations are configured, the values of these counters decrease.
12.5 Parameter Optimization
The parameters that may require modification after inter-RAT ANR is used are almost the
same as those after intra-RAT ANR is used. The following table describes only the parameters
that differ from those used for intra-RAT ANR and are specifically used for inter-RAT ANR.
Parameter Name Parameter ID Setting Notes
InterRat Fast ANR
measurement UE
number
FastAnrInterRat
MeasUeNum
This parameter specifies the maximum number
of UEs that can be concurrently involved in
measurements for inter-RAT fast ANR. A larger
parameter value results in more UEs that can
concurrently perform fast ANR measurements.
In this situation, neighboring cells can be
quickly detected. However, this affects the
service quality for these UEs and the uplink
throughput of the network.
InterRat Fast ANR
valid measurement
min UE number
FastAnrInterRat
UeNumThd
This parameter specifies the threshold for
entering the monitoring state for fast ANR. This
threshold is expressed as the number of UEs that
have performed measurements for fast ANR. A
larger parameter value results in a larger total
number of UEs that are involved in
measurements for inter-RAT fast ANR. In this
situation, the UEs involved can be distributed
eRAN
ANR Management Feature Parameter Description 12 Engineering Guidelines for Inter-RAT ANR
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
64
Parameter Name Parameter ID Setting Notes
more randomly throughout the network,
reducing the probability of missing neighboring
cells. However, this affects the service quality
for these UEs and the uplink throughput of the
network.
UTRAN Fast ANR
RSCP threshold FastAnrRscpThd This parameter specifies the RSCP requirement
for adding a neighboring cell to the NCL. A
larger parameter value results in a higher RSCP
requirement, and therefore the neighboring cells
in the NCL have higher RSCP quality. In urban
areas with densely distributed cells, increase the
parameter value to ensure that only high-quality
neighboring cells are added to the NCL. In
contrast, in sparsely populated areas, decrease
this parameter value to add the neighboring cells
with low cell-edge RSCP to the NCL.
GERAN Fast ANR
RSSI threshold FastAnrRssiThd This parameter specifies the received signal
strength indicator (RSSI) requirement for adding
a neighboring cell to the NCL. A larger
parameter value results in a higher RSSI
requirement, and therefore the neighboring cells
in the NCL have higher RSSI quality. In urban
areas with densely distributed cells, increase this
parameter value to ensure that only neighboring
cells with high RSSI are added to the NCL. In
contrast, in sparsely populated areas, decrease
this parameter value to add the neighboring cells
with low cell-edge RSSI to the NCL.
CDMA2000
1xRTT Fast ANR
Pilot threshold
FastAnrCdma1x
rttPilotThd
This parameter specifies the pilot strength
requirement for adding a neighboring
CDMA2000 1XRTT cell to the NCL. A larger
parameter value results in a higher pilot strength
requirement; therefore the neighboring cells in
the NCL have higher signal quality. In urban
areas with densely distributed cells, increase this
parameter value to ensure that only neighboring
cells with high signal quality are added to the
NCL. In contrast, in sparsely populated areas,
decrease this parameter value to add the
neighboring cells with low cell-edge signal
quality to the NCL.
CDMA2000 HRPD
Fast ANR Pilot
threshold
FastAnrCdmahr
pdPilotThd
This parameter specifies the pilot strength
requirement for adding a neighboring
CDMA2000 HRPD cell to the NCL. A larger
parameter value results in a higher pilot strength
requirement; therefore the neighboring cells in
the NCL have higher signal quality. In urban
areas with densely distributed cells, increase this
parameter value to ensure that only neighboring cells with high signal quality are added to the
eRAN
ANR Management Feature Parameter Description 12 Engineering Guidelines for Inter-RAT ANR
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
65
Parameter Name Parameter ID Setting Notes
NCL. In contrast, in sparsely populated areas,
decrease this parameter value to add the
neighboring cells with low cell-edge signal
quality to the NCL.
12.6 Troubleshooting
Fault Description
A coverage-based handover from E-UTRAN to UTRAN fails.
Fault Handling
Perform the following steps to check whether this handover failure is caused by incorrect
ANR configuration:
Step 1 Start a Uu interface tracing task for the source cell on the M2000 client. In the tracing result,
check whether the eNodeB has delivered a handover command. A handover command was
delivered if the RRC_MOBIL_FROM_EUTRA_CMD message contains the IE
mobilityFromEUTRACommand.
If the eNodeB has not delivered the handover command, go to Step 2.
If the eNodeB has delivered the handover command, contact Huawei technical support.
Step 2 Run the LST UTRANEXTERNALCELL command to check whether the target cell has
been configured as an external cell on the source eNodeB. Run the LST UTRANNCELL
command to check whether the neighbor relation between the source and target cells has been
configured on the source cell.
If they have not been configured, go to Step 3.
If the NRT and NCL are configured, contact Huawei technical support.
In RAN sharing with common carriers mode, if the UE is subscribed to a secondary operator, you also
need to check whether the PLMN ID of the secondary operator has been configured. If the PLMN ID
has not been configured, configure it.
Step 3 Check whether the switch for event-triggered ANR with UTRAN has been turned on.
If the switch is turned off, turn it on.
If the switch is turned on, go to Step 4.
Step 4 Check whether the UE supports ANR with UTRAN.
If the UE supports ANR with UTRAN, contact Huawei technical support.
If the UE does not support ANR with UTRAN, no further action is required.
----End
eRAN
ANR Management Feature Parameter Description 13 Engineering Guidelines for ANR with Shared Cells
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
66
13 Engineering Guidelines for ANR with Shared Cells
This chapter describes the process of deploying the function of ANR with shared cells.
13.1 When to Use ANR with Shared Cells
ANR with Shared E-UTRAN Cells
Enable ANR with shared E-UTRAN cells when all the following conditions are met:
Neighboring E-UTRAN cells are shared by multiple PLMNs.
− If the shared neighboring cells broadcast the PLMN lists in an RR manner, turn on
NBSLTEPLMNRoundSwitch under the RanSharingAnrSwitchparameter.
− If the shared neighboring cells do not broadcast the PLMN lists in an RR manner,
turn off NBSLTEPLMNRoundSwitch and turn on NBSLTERANSharingSwitch
under the RanSharingAnrSwitch parameter.
ANR-capable UEs are used in the network.
IntraRatEventAnrSwitch under the AnrSwitch parameter is turned on for UEs to read
ECGIs over the radio interface.
Disable ANR with shared E-UTRAN cells when one of the following conditions is met:
The neighboring E-UTRAN cells are not shared by PLMNs.
The neighboring cells are shared by PLMNs, but the operators prefer manual
maintenance of neighbor relations to ANR. In this situation, disable intra-RAT
event-triggered ANR, intra-RAT fast ANR, and ANR with shared E-UTRAN cells.
ANR with Shared UTRAN Cells
Enable ANR with shared UTRAN cells when all the following conditions are met:
Neighboring UTRAN cells are shared by multiple PLMNs.
In this case, turn on NBSUTRANRANSharingSwitch under the RanSharingAnrSwitch
parameter.
Some UEs in the network support ANR of E-UTRAN with UTRAN.
eRAN
ANR Management Feature Parameter Description 13 Engineering Guidelines for ANR with Shared Cells
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
67
UtranEventAnrSwitch under the AnrSwitch parameter is turned on for UEs to read
CGIs over the radio interface.
Disable ANR with shared UTRAN cells when one of the following conditions is met:
The neighboring UTRAN cells are not shared by PLMNs.
The neighboring cells are shared by PLMNs, but the operators prefer manual
maintenance of neighbor relations to ANR. In this situation, disable event-triggered ANR
with UTRAN, fast ANR with UTRAN, and ANR with shared UTRAN cells.
ANR with Shared GERAN Cells
Enable ANR with shared GERAN cells when all the following conditions are met:
Neighboring GERAN cells are shared by multiple PLMNs.In this case, turn on
NBSGERANRANSharingSwitch under the RanSharingAnrSwitch parameter.
Some UEs in the network support ANR of E-UTRAN with GERAN.
GeranEventAnrSwitch under the ANRSWITCH parameter is turned on for UEs to read
CGIs over the radio interface.
Disable ANR with shared GERAN cells when one of the following conditions is met:
The neighboring GERAN cells are not shared by PLMNs.
The neighboring cells are shared by PLMNs, but the operators prefer manual
maintenance of neighbor relations to ANR. In this situation, disable event-triggered ANR
with GERAN, fast ANR with GERAN, and ANR with shared GERAN cells.
13.2 Required Information
Collect the following information:
Network configuration: whether RAN sharing and PLMN list broadcast in an RR manner
are to be enabled
For details about the network configuration, see RAN Sharing Feature Parameter
Description.
Proportion and distribution of UEs that support intra-frequency, inter-frequency, and
inter-RAT ANR in the network
Networking mode: intra-frequency, inter-frequency, or inter-RAT
13.3 Deployment
13.3.1 Process
None
13.3.2 Requirements
UEs on the network support ANR-related measurements on
intra-frequency/inter-frequency/inter-RAT neighboring cells and are DRX-capable. The
eRAN
ANR Management Feature Parameter Description 13 Engineering Guidelines for ANR with Shared Cells
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
68
eNodeB is not required to support DRX. For details about DRX, see DRX and Signaling Control Feature Parameter Description.
iManager M2000 V200R013C00 or later is used.
The intra-RAT measurement information (including frequencies to be measured) has
been configured. For details, see Mobility Management in Connected Mode Feature Parameter Description.
13.3.3 Data Preparation
There are three types of data sources:
Network plan (negotiation required): parameter values planned by the operator and
negotiated with the EPC or peer transmission equipment
Network plan (negotiation not required): parameter values planned and set by the
operator
User-defined: parameter values set by users
The following table describes the parameter that must be set in the EnodeBAlgoSwitch MO
to enable ANR with shared cells.
Parameter Name
Parameter ID Setting Notes Data Source
ANR
Under
RAN
Sharing
Algorithm
Switch
RanSharingAnr
Switch
Set the following switches under this
parameter:
NBSLTEPLMNRoundSwitch
NBSLTERANSharingSwitch
NBSUTRANRANSharingSwitch
NBSGERANRANSharingSwitch
For details about how to set the switches,
see 13.1 When to Use ANR with Shared
Cells.
Network
plan
(negotiation
not required)
13.3.4 Precautions
None
13.3.5 Hardware Adjustment
N/A
13.3.6 Activation
Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs
Enter the values of the parameters listed in Table 13-1 in a summary data file, which also
contains other data for the new eNodeBs to be deployed. Then, import the summary data file
into the Configuration Management Express (CME) for batch configuration. For detailed
instructions, see section "Creating eNodeBs in Batches" in the initial configuration guide for
the eNodeB.
eRAN
ANR Management Feature Parameter Description 13 Engineering Guidelines for ANR with Shared Cells
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
69
The summary data file may be a scenario-specific file provided by the CME or a customized
file, depending on the following conditions:
The managed objects (MOs) in Table 13-1 are contained in a scenario-specific summary
data file. In this situation, set the parameters in the MOs, and then verify and save the
file.
Some MOs in Table 13-1 are not contained in a scenario-specific summary data file. In
this situation, customize a summary data file to include the MOs before you can set the
parameters.
Table 13-1 Parameters related to ANR with shared cells
MO Sheet in the Summary Data File
Parameter Group Remarks
ENodeBAl
goSwitch
ENodeBAlgoSwitch ANR Under RAN Sharing
Algorithm Switch
User-defined sheet
Using the CME to Perform Batch Configuration for Existing eNodeBs
Batch reconfiguration using the CME is the recommended method to activate a feature on
existing eNodeBs. This method reconfigures all data, except neighbor relationships, for
multiple eNodeBs in a single procedure. The procedure is as follows:
Step 1 Choose CME > Advanced > Customize Summary Data File from the main menu of an
M2000/DOMC920 client, or choose Advanced > Customize Summary Data File from the
main menu of a CME client, to customize a summary data file for batch reconfiguration.
For context-sensitive help on a current task in the client, press F1.
Step 2 Choose CME > LTE Application > Export Data >Export Base Station Bulk
Configuration Data from the main menu of the M2000/DOMC920 client, or choose LTE
Application > Export Data >Export Base Station Bulk Configuration Data from the main
menu of the CME client, to export the eNodeB data stored on the CME into the customized
summary data file.
Step 3 In the summary data file, set the parameters in the MOs listed in "Using the CME to Perform
Batch Configuration for Newly Deployed eNodeBs" and close the file.
Step 4 Choose CME > LTE Application > Import Data > Import Base Station Bulk
Configuration Data from the main menu of the M2000/DOMC920 client, or choose LTE
Application> Import Data > Import Base Station Bulk Configuration Data from the main
menu of the CME client, to import the summary data file into the CME.
Step 5 Choose CME > Planned Area > Export Incremental Scripts from the main menu of the
M2000/DOMC920 client, or choose Area Management > Planned Area > Export
Incremental Scripts from the main menu of the CME client, to export and activate the
incremental scripts.
----End
eRAN
ANR Management Feature Parameter Description 13 Engineering Guidelines for ANR with Shared Cells
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
70
Using the CME to Perform Single Configuration
On the CME, set the parameters listed in the "Data Preparation" section for a single eNodeB.
The procedure is as follows:
Step 1 In the planned data area, click Base Station in the upper left corner of the configuration
window.
Step 2 In area 1 shown in Figure 13-1, select the eNodeB to which the MOs belong.
Figure 13-1 MO search and configuration window
Step 3 On the Search tab page in area 2, enter an MO name, for example, CELL.
Step 4 In area 3, double-click the MO in the Object Name column. All parameters in this MO are
displayed in area 4.
Step 5 Set the parameters in area 4 or 5.
Step 6 Choose CME > Planned Area > Export Incremental Scripts (M2000/DOMC920 client
mode), or choose Area Management > Planned Area > Export Incremental Scripts (CME
client mode), to export and activate the incremental scripts.
----End
Using MML Commands Activating ANR with Shared E-UTRAN Cells That Broadcast PLMN Lists in an RR
Manner
Run the MOD ENODEBALGOSWITCH command with the
NBSLTEPLMNRoundSwitch(NBSLTEPLMNRoundSwitch) check box selected
under the ANR Under RAN Sharing Algorithm Switch parameter.
eRAN
ANR Management Feature Parameter Description 13 Engineering Guidelines for ANR with Shared Cells
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
71
Example:
MOD ENODEBALGOSWITCH: AnrSwitch=IntraRatEventAnrSwitch-1,
RanSharingAnrSwitch=NBSLTEPLMNRoundSwitch-1;
Activating ANR with Shared E-UTRAN Cells That Do Not Broadcast PLMN Lists in an
RR Manner
Run the MOD ENODEBALGOSWITCH command with the
NBSLTERANSharingSwitch(NBSLTERANSharingSwitch) check box selected under
the ANR Under RAN Sharing Algorithm Switch parameter.
Example:
MOD ENODEBALGOSWITCH: AnrSwitch=IntraRatEventAnrSwitch-1,
RanSharingAnrSwitch=NBSLTERANSharingSwitch-1;
Activating ANR with Shared UTRAN Cells
Run the MOD ENODEBALGOSWITCH command with the
NBSUTRANRANSharingSwitch(NBSUTRANRANSharingSwitch) check box
selected under the ANR Under RAN Sharing Algorithm Switch parameter.
Example:
MOD ENODEBALGOSWITCH: AnrSwitch=IntraRatEventAnrSwitch-1,
RanSharingAnrSwitch=NBSUTRANRANSharingSwitch-1;
Activating ANR with Shared GERAN Cells
Run the MOD ENODEBALGOSWITCH command with the
NBSGERANRANSharingSwitch(NBSGERANRANSharingSwitch) check box
selected under the ANR Under RAN Sharing Algorithm Switch parameter.
Example:
MOD ENODEBALGOSWITCH: AnrSwitch=IntraRatEventAnrSwitch-1,
RanSharingAnrSwitch=NBSGERANRANSharingSwitch-1;
13.3.7 Activation Observation
The procedure for observing the activation of ANR with shared cells is similar to that of
intra-RAT ANR. For details, see 11.3.7 Activation Observation.
13.3.8 Reconfiguration
None
13.3.9 Deactivation
Using the CME to Perform Batch Configuration
Batch reconfiguration using the CME is the recommended method to deactivate a feature on
eNodeBs. This method reconfigures all data, except neighbor relationships, for multiple
eNodeBs in a single procedure. The procedure for feature deactivation is similar to that for
feature activation described in Using the CME to Perform Batch Configuration for Existing
eNodeBs. In the procedure, modify parameters according to Table 13-2.
eRAN
ANR Management Feature Parameter Description 13 Engineering Guidelines for ANR with Shared Cells
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
72
Table 13-2 Parameters related to ANR with shared cells
MO Sheet in the Summary Data File
Parameter Group
Setting Notes
ENodeBAl
goSwitch
User-defined sheet RanSharing
AnrSwitch
Turn off the following switches:
NBSLTEPLMNRoundSwitch
NBSLTERANSharingSwitch
NBSUTRANRANSharingSwit
ch
NBSGERANRANSharingSwit
ch
Using the CME to Perform Single Configuration
On the CME, set the parameter according to Table 13-2. For detailed instructions, see 13.3.6
Activation described for feature activation.
Using MML Commands
Run the MOD ENODEBALGOSWITCH command to turn on the switches for ANR with
shared cells.
The following example command is used to deactivate ANR with shared E-UTRAN cells that
broadcast PLMN lists in an RR manner:
MOD ENODEBALGOSWITCH: RanSharingAnrSwitch=NBSLTEPLMNRoundSwitch-0;
13.4 Performance Monitoring
Using ANR with shared cells decreases the probability that the configurations of neighboring
cells are missing or incorrect, thereby increasing the handover success rate and decreasing the
service drop rate. To monitor the performance of ANR with shared cells, you can check the
performance counters related to handovers and service drops. In addition, you can check the
counters for intra- or inter-RAT ANR for reference.
13.5 Parameter Optimization
None
13.6 Troubleshooting
Fault Description
In an E-UTRAN shared by PLMNs, an intra-RAT handover of a UE subscribed to a
secondary operator fails.
eRAN
ANR Management Feature Parameter Description 13 Engineering Guidelines for ANR with Shared Cells
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
73
Fault Handling
Perform the following steps to check whether this handover failure is caused by incorrect
ANR configuration:
Step 1 Start a Uu interface tracing task for the source cell on the M2000 client. In the tracing result,
check whether the 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 2.
If the eNodeB has delivered the handover command, contact Huawei technical support.
Step 2 Run the following commands to check whether the external cell, neighbor relation, and
PLMN list configurations of the target cell have been set on the source side: LST
EUTRANEXTERNALCELL, LST EUTRANINTRAFREQNCELL/LST
EUTRANINTERFREQNCELL, and LST EUTRANEXTERNALCELLPLMN.
If they have not been set, go to Step 3.
If they have been set, contact Huawei technical support.
Step 3 Check whether the switch for intra-RAT event-triggered ANR and the switch for RAN
sharing at the target cell have been turned on at the source side.
If any of the switches has not been turned on, turn on the switch.
If the switches have been turned on, go to Step 4.
Step 4 Check whether the UE supports intra-RAT ANR.
If the UE supports intra-RAT ANR, contact Huawei technical support.
If the UE does not support intra-RAT ANR, no further action is required.
----End
eRAN
ANR Management Feature Parameter Description
14 Engineering Guidelines for X2 Automatic
Management
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
74
14 Engineering Guidelines for X2 Automatic Management
This chapter describes the process of deploying X2 automatic management.
14.1 When to Use X2 Automatic Management
X2 Self-Setup
X2 self-setup can be implemented in X2 over S1 or X2 over M2000 mode.
X2 Self-Setup in X2 over S1 Mode
This mode has no requirement on whether the eNodeBs are managed by the same M2000, and
therefore this mode is recommended for X2 self-setup.
Enable X2 self-setup in X2 over S1 mode when the operator has not planned X2 interfaces
and hopes to use the X2 self-setup function to automatically set up X2 interfaces.
Disable X2 self-setup in X2 over S1 mode when the operator prefers to manually maintain X2
interfaces.
X2 Self-Setup in X2 over M2000 Mode
This mode can be used only when the eNodeBs are managed by the same M2000.
Enable X2 self-setup in X2 over M2000 mode when the operator has not planned X2
interfaces and hopes to use the X2 self-setup function to automatically set up X2 interfaces.
Disable X2 self-setup in X2 over M2000 mode in one of the following cases:
The operator prefers to manually maintain X2 interfaces.
The eNodeBs are not managed by the same M2000.
X2 Automatic Removal
Enable X2 automatic removal when redundant X2 configurations exist due to network
reconfiguration and the operator hopes to use the X2 automatic removal function to
automatically remove redundant X2 interfaces.
eRAN
ANR Management Feature Parameter Description
14 Engineering Guidelines for X2 Automatic
Management
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
75
Disable X2 automatic removal if the operator prefers to manually maintain X2 interface
configurations.
eNodeB Configuration Update Based on X2 Messages
Enable eNodeB configuration update based on X2 messages when the operator hopes to use
this function to automatically maintain eNodeB configurations.
Disable eNodeB configuration update based on X2 messages when the operator prefers to
manually maintain eNodeB configurations.
14.2 Required Information
Check whether the EPC or M2000 supports X2 self-setup.
14.3 Deployment
14.3.1 Process
For details on the deployment process of X2 self-setup, see section "Deploying an X2
Interface" in S1X2OM Channel Management Feature Parameter Description.
14.3.2 Requirements
For details on the deployment requirements of X2 self-setup, see section "Deploying an X2
Interface" in S1X2OM Channel Management Feature Parameter Description.
14.3.3 Data Preparation
For details on the data preparation for deploying X2 self-setup, see section "Deploying an X2
Interface" in S1X2OM Channel Management Feature Parameter Description.
There are three types of data sources:
Network plan (negotiation required): parameter values planned by the operator and
negotiated with the EPC or peer transmission equipment
Network plan (negotiation not required): parameter values planned and set by the
operator
User-defined: parameter values set by users
(Optional) The following table describes the parameters that can be set in the
X2BlackWhiteList MO to configure an X2 blacklist or whitelist. Configure this MO based
on operator requirements.
Parameter Name
Parameter ID
Setting Notes Data Source
Mobile
country
code
Mcc This parameter specifies the mobile country code
(MCC) of the neighboring eNodeB at the other end
of an X2 interface.
This parameter references the corresponding
Network
plan
(negotiation not
eRAN
ANR Management Feature Parameter Description
14 Engineering Guidelines for X2 Automatic
Management
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
76
Parameter Name
Parameter ID
Setting Notes Data Source
parameter in the CNOPERATOR MO on the
neighboring eNodeB.
required)
Mobile
network
code
Mnc This parameter specifies the mobile network code
(MNC) of the neighboring eNodeB.
This parameter references the corresponding
parameter in the CNOPERATOR MO on the
neighboring eNodeB.
Network
plan
(negotiati
on not
required)
eNodeB
identity
ENodeBI
d
This parameter specifies the ID of the neighboring
eNodeB. This ID uniquely identifies an eNodeB in a
network.
This parameter references the corresponding
parameter in the ENODEBFUNCTION MO on the
neighboring eNodeB.
Network
plan
(negotiati
on not
required)
X2 Black
or White
List Type
X2ListTy
pe
This parameter specifies whether to blacklist or
whitelist the X2 interface.
Set this parameter to
X2_BLACK_LIST_TYPE(X2 Black List Type) or
X2_WHITE_LIST_TYPE(X2 White List Type).
Network
plan
(negotiati
on not
required)
The following table describes the parameter that must be set in the GlobalProcSwitch MO
for X2 automatic removal.
Parameter Name Parameter ID Setting Notes Data Source
The Timer of X2
delete by SON X2SonDeleteTimer Set this parameter by
referring to 14.1 When
to Use X2 Automatic
Management.
Network plan
(negotiation not
required)
The following table describes the parameter that must be set in the GlobalProcSwitch MO
for eNodeB configuration update based on X2 messages.
Parameter Name Parameter ID Setting Notes Data Source
Update eNB
Configuration Via
X2 Switch
X2BasedUptENode
BCfgSwitch
Set this parameter by
referring to 14.1 When to
Use X2 Automatic
Management.
Network plan
(negotiation
not required)
14.3.4 Precautions
None
eRAN
ANR Management Feature Parameter Description
14 Engineering Guidelines for X2 Automatic
Management
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
77
14.3.5 Hardware Adjustment
N/A
14.3.6 Activation
For details on the activation of X2 self-setup, see section "Deploying an X2 Interface" in
S1X2OM Channel Management Feature Parameter Description.
This section describes how to activate X2 automatic removal and eNodeB configuration
update based on X2 messages.
Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs
Enter the values of the parameters listed in Table 14-1 in a summary data file, which also
contains other data for the new eNodeBs to be deployed. Then, import the summary data file
into the Configuration Management Express (CME) for batch configuration. For detailed
instructions, see section "Creating eNodeBs in Batches" in the initial configuration guide for
the eNodeB.
The summary data file may be a scenario-specific file provided by the CME or a customized
file, depending on the following conditions:
The managed objects (MOs) in Table 14-1 are contained in a scenario-specific summary
data file. In this situation, set the parameters in the MOs, and then verify and save the
file.
Some MOs in Table 14-1 are not contained in a scenario-specific summary data file. In
this situation, customize a summary data file to include the MOs before you can set the
parameters.
Table 14-1 Parameters related to X2 automatic removal and eNodeB configuration update based
on X2 messages
MO Sheet in the Summary Data File
Parameter Group Remarks
GLOBAL
PROCS
WITCH
User-defined sheet.
GLOBALPROCSWITCH is
recommended.
X2SonSetupSwitch,
X2SonDeleteTimer,
X2BasedUptENodeBCfgSwitch
N/A
Using the CME to Perform Batch Configuration for Existing eNodeBs
Batch reconfiguration using the CME is the recommended method to activate a feature on
existing eNodeBs. This method reconfigures all data, except neighbor relationships, for
multiple eNodeBs in a single procedure. The procedure is as follows:
Step 1 Choose CME > Advanced > Customize Summary Data File from the main menu of an
M2000/DOMC920 client, or choose Advanced > Customize Summary Data File from the
main menu of a CME client, to customize a summary data file for batch reconfiguration.
For context-sensitive help on a current task in the client, press F1.
eRAN
ANR Management Feature Parameter Description
14 Engineering Guidelines for X2 Automatic
Management
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
78
Step 2 Choose CME > LTE Application > Export Data >Export Base Station Bulk
Configuration Data from the main menu of the M2000/DOMC920 client, or choose LTE
Application > Export Data >Export Base Station Bulk Configuration Data from the main
menu of the CME client, to export the eNodeB data stored on the CME into the customized
summary data file.
Step 3 In the summary data file, set the parameters in the MOs listed in "Using the CME to Perform
Batch Configuration for Newly Deployed eNodeBs" and close the file.
Step 4 Choose CME > LTE Application > Import Data > Import Base Station Bulk
Configuration Data from the main menu of the M2000/DOMC920 client, or choose LTE
Application> Import Data > Import Base Station Bulk Configuration Data from the main
menu of the CME client, to import the summary data file into the CME.
Step 5 Choose CME > Planned Area > Export Incremental Scripts from the main menu of the
M2000/DOMC920 client, or choose Area Management > Planned Area > Export
Incremental Scripts from the main menu of the CME client, to export and activate the
incremental scripts.
----End
Using the CME to Perform Single Configuration
On the CME, set the parameters listed in the "Data Preparation" section for a single eNodeB.
The procedure is as follows:
Step 1 In the planned data area, click Base Station in the upper left corner of the configuration
window.
Step 2 In area 1 shown in Figure 14-1, select the eNodeB to which the MOs belong.
Figure 14-1 MO search and configuration window
eRAN
ANR Management Feature Parameter Description
14 Engineering Guidelines for X2 Automatic
Management
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
79
Step 3 On the Search tab page in area 2, enter an MO name, for example, CELL.
Step 4 In area 3, double-click the MO in the Object Name column. All parameters in this MO are
displayed in area 4.
Step 5 Set the parameters in area 4 or 5.
Step 6 Choose CME > Planned Area > Export Incremental Scripts (M2000/DOMC920 client
mode), or choose Area Management > Planned Area > Export Incremental Scripts (CME
client mode), to export and activate the incremental scripts.
----End
Using MML Commands Activating X2 Self-Setup
Run the MOD GLOBALPROCSWITCH command with The Switch of X2 setup by
SON set to ON(On).
MOD GLOBALPROCSWITCH: X2SonSetupSwitch=ON;
Activating X2 Automatic Removal
Run the MOD GLOBALPROCSWITCH command with The Timer of X2 delete by
SON set to a value other than 0.
MOD GLOBALPROCSWITCH: X2SonDeleteTimer=1440;
Activating eNodeB Configuration Update Based on X2 Messages
Run the MOD GLOBALPROCSWITCH command with Update eNB Configuration
Via X2 Switch set to ON(On).
MOD GLOBALPROCSWITCH: X2BasedUptENodeBCfgSwitch=ON;
14.3.7 Activation Observation
X2 Self-Setup
By using signaling tracing or checking SON logs on the M2000 client, you can check whether
X2 self-setup has been activated.
Signaling Tracing
Signaling tracing can be used to check whether X2 self-setup in X2 over S1 mode has been
activated.
Perform signaling tracing as follows:
Step 1 Log in to the M2000 client, and choose Monitor > Signaling Trace > Signaling Trace
Management.
Step 2 In the navigation tree on the left of the Signaling Trace Management tab page, choose
LTE > Application Layer > S1 Interface Trace.
Step 3 Create and start an S1 interface tracing task.
Step 4 Check the tracing result.
If information about the source and target eNodeBs (such as the PLMN IDs, eNodeB IDs, and
IP addresses) is exchanged over the S1 interface, X2 self-setup in X2 over S1 mode has been
activated. Figure 14-2 shows an example of traced S1 messages related to X2 self-setup.
eRAN
ANR Management Feature Parameter Description
14 Engineering Guidelines for X2 Automatic
Management
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
80
Figure 14-2 Example of traced S1 messages related to X2 self-setup
----End
SON Logs on the M2000 Client
The procedure for activation observation by checking SON logs on the M2000 client is as
follows:
Step 1 On the M2000 client, choose SON > SON Log.
Step 2 On the Query SON Log tab page, select X2 Link Log from the Log Category drop-down
list in the upper left corner.
Step 3 In the Event Name area, select Automatically Establish Signaling Link and Automatically
Establish Service Link one at a time to check different types of X2 self-setup operations.
Figure 14-3 shows an example of SON logs.
Figure 14-3 Example of SON logs
----End
eRAN
ANR Management Feature Parameter Description
14 Engineering Guidelines for X2 Automatic
Management
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
81
X2 Automatic Removal
You can view SON logs on the M2000 client to check whether X2 automatic removal has
been activated. The procedure is as follows:
Step 1 On the M2000 client, choose SON > SON Log.
Step 2 On the Query SON Log tab page, select X2 Link Log from the Log Category drop-down
list in the upper left corner.
Step 3 In the Event Name area, select Automatically Delete Signaling Link Deleted and
Automatically Delete Service Link one at a time to check different types of X2 automatic
removal operations.
----End
eNodeB Configuration Update Based on X2 Messages
You can view X2 messages to check whether the function of eNodeB configuration update
based on X2 messages has been activated. The procedure is as follows:
Step 1 On the M2000 client, choose Monitor > Signaling Trace > Signaling Trace Management.
Step 2 In the navigation tree on the left of the Signaling Trace Management tab page, choose
LTE > Application Layer > X2 Interface Trace.
Step 3 Create and start an X2 interface tracing task.
Step 4 Check the tracing result.
If the X2_SETUP_REQUEST or ENB_CONFIGURATION_UPDATE message (as shown in
Figure 14-4) shows that the local eNodeB sends its configurations to the peer eNodeB, this
function has been activated. The peer eNodeB then updates the configuration based on the
messages.
eRAN
ANR Management Feature Parameter Description
14 Engineering Guidelines for X2 Automatic
Management
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
82
Figure 14-4 Example of X2_SETUP_REQUEST or ENB_CONFIGURATION_UPDATE
message
----End
14.3.8 Reconfiguration
None
14.3.9 Deactivation
Using the CME to Perform Batch Configuration
Batch reconfiguration using the CME is the recommended method to deactivate a feature on
eNodeBs. This method reconfigures all data, except neighbor relationships, for multiple
eNodeBs in a single procedure. The procedure for feature deactivation is similar to that for
feature activation described in Using the CME to Perform Batch Configuration for Existing
eNodeBs. In the procedure, modify parameters according to Table 14-2.
eRAN
ANR Management Feature Parameter Description
14 Engineering Guidelines for X2 Automatic
Management
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
83
Table 14-2 Parameters related to X2 automatic management
MO Sheet in the Summary Data File
Parameter Group Setting Notes
GlobalPro
cSwitch
User-defined sheet.
GlobalProcSwitch is
recommended.
X2SonSetupSwitch,
X2SonDeleteTimer,
X2BasedUptENode
BCfgSwitch
Set X2SonSetupSwitch to
OFF.
Set X2SonDeleteTimer to 0.
Set
X2BasedUptENodeBCfgSw
itch to OFF.
Using the CME to Perform Single Configuration
On the CME, set the parameter according to Table 14-2. For detailed instructions, see Using
the CME to Perform Single Configuration described for feature activation.
Using MML Commands Deactivating X2 Self-Setup
Run the MOD GLOBALPROCSWITCH command with The Switch of X2 setup by
SON set to OFF(Off).
MOD GLOBALPROCSWITCH:X2SONSETUPSWITCH=OFF;
Deactivating X2 Automatic Removal
Run the MOD GLOBALPROCSWITCH command with The Timer of X2 delete by
SON set to 0.
MOD GLOBALPROCSWITCH: X2SonDeleteTimer=0;
Deactivating eNodeB Configuration Update Based on X2 Messages
Run the MOD GLOBALPROCSWITCH command with Update eNB Configuration
Via X2 Switch set to OFF(Off).
MOD GLOBALPROCSWITCH:X2BASEDUPTENODEBCFGSWITCH=OFF;
14.4 Performance Monitoring
X2 Self-Setup
The performance of X2 self-setups and X2-based handovers can be monitored using counters,
SON logs, and alarms.
Counters
The following table lists the counters related to the X2 setup success rates and
percentage of X2-based handovers.
Counter ID
Counter Name Description
152672720
2 L.Sig.X2.SendSetup.Att Number of X2 setup attempts initiated
by the local eNodeB
eRAN
ANR Management Feature Parameter Description
14 Engineering Guidelines for X2 Automatic
Management
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
84
Counter ID
Counter Name Description
152672720
4
L.Sig.X2.RecvSetup.Att Number of X2 setup attempts initiated
by peer eNodeBs
152672720
3
L.Sig.X2.SendSetup.Succ Number of successful X2 setups
initiated by the local eNodeB
152672720
5
L.Sig.X2.RecvSetup.Succ Number of successful X2 setups
initiated by peer eNodeBs
152672726
5
L.HHO.X2.IntraFreq.ExecAttOut Number of executed outgoing
X2-based inter-eNodeB
intra-frequency handovers in a cell
152672726
8
L.HHO.X2.InterFreq.ExecAttOut Number of executed outgoing
X2-based inter-eNodeB
inter-frequency handovers in a cell
152672700
2
L.HHO.IntereNB.IntraFreq.ExecAtt
Out
Number of executed outgoing
inter-eNodeB intra-frequency
handovers in a cell
152672700
5
L.HHO.IntereNB.InterFreq.ExecAtt
Out
Number of executed outgoing
inter-eNodeB inter-frequency
handovers in a cell
152672729
4
L.HHO.NCell.ExecAttOut Number of executed outgoing
handovers between two specific cells
For the detailed definitions of the counters, see eNodeB Performance Counter Reference.
SON logs
The X2 control- and user-plane bearer self-setup events are automatically recorded in
SON logs. The SON logs can be exported using the M2000. The recorded information
includes the setup time, the PLMN IDs and eNodeB IDs of the local and peer eNodeBs,
the link number of the peer eNodeB, and the IP addresses of the peer eNodeB. If an X2
self-setup fails, the cause value is recorded in SON logs for further analysis.
Alarms
The following table lists the alarms related to X2 interfaces. For details about the alarms,
see eNodeB Alarm Reference.
Alarm ID Alarm Name Severity
29204 X2 Interface Fault Major
29205 X2 Interface Configuration
Update Failed
Major
25886 IP Path Fault Major
25888 SCTP Link Fault Major
eRAN
ANR Management Feature Parameter Description
14 Engineering Guidelines for X2 Automatic
Management
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
85
X2 Automatic Removal
The performance of X2 automatic removal can be monitored using SON logs. The X2
control- and user-plane bearer automatic removal events are automatically recorded in SON
logs. The SON logs can be exported using the M2000. The recorded information includes the
removal time, the PLMN IDs and eNodeB IDs of the local and peer eNodeBs, the link
number of the peer eNodeB, and the IP addresses of the peer eNodeB. If an X2 removal fails,
the cause value is recorded in SON logs for further analysis.
eNodeB Configuration Update Based on X2 Messages
Using the function of eNodeB configuration update based on X2 messages decreases the
probability that the configurations of neighboring cells are missing or incorrect, thereby
increasing the handover success rate and decreasing the service drop rate. To monitor the
performance of eNodeB configuration update based on X2 messages, you can check the
performance counters related to handovers and service drops. In addition, you can check the
counters for intra-RAT ANR for reference.
14.5 Parameter Optimization
None
14.6 Troubleshooting
Fault Description
X2 self-setups fail.
Fault Handling
Perform the following steps:
Step 1 Calculate the X2 self-setup success rates based on counters.
Export the following counters: 1526727202, 1526727204, 1526727203, and 1526727205.
Then, calculate the X2 self-setup success rates by using the following formulas:
Success rate of X2 self-setups initiated by the local eNodeB = Number of successful X2
setups initiated by the local eNodeB (1526727203)/Number of X2 setup attempts
initiated by the local eNodeB (1526727202) x 100%
Success rate of X2 self-setups initiated by peer eNodeBs = Number of successful X2
setups initiated by peer eNodeBs (1526727205)/Number of X2 setup attempts initiated
by peer eNodeBs (1526727204) x 100%
Based on the X2 setup success rates, identify the top N eNodeBs with low X2 setup success
rates for further analysis.
Step 2 Run the LST GLOBALPROCSWITCH command to check whether the settings of the X2
self-setup switch and self-setup method are correct.
If yes, go to Step 3.
If no, correct the settings.
eRAN
ANR Management Feature Parameter Description
14 Engineering Guidelines for X2 Automatic
Management
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
86
Step 3 Check whether the control-plane and user-plane IP addresses are correctly configured.
If yes, go to Step 4.
If no, correct the configuration.
Step 4 Check whether alarms related to X2 interfaces are generated for the top N eNodeBs.
If yes, handle the alarms.
If no, go to Step 5.
Step 5 On the M2000, export X2 self-setup SON logs for the top N eNodeBs. The logs can be
exported in an EXCEL file.
----End
eRAN
ANR Management Feature Parameter Description 15 Parameters
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
87
15 Parameters
Table 15-1 Parameter description
MO Parameter ID MML Command
Feature ID Feature Name Description
Cell LocalCellId ACT CELL
ADD CELL
ADD
CELLBAND
BLK CELL
DEA CELL
DSP CELL
DSP
CELLULCOM
PCLUSTER
DSP
PRIBBPADJUS
T
LST CELL
LST
CELLBAND
MOD CELL
RMV CELL
RMV
CELLBAND
STR
CELLRFLOOP
BACK
STR
CELLSELFTES
T
UBL CELL
None None Meaning:Indicat
es the local ID
of the cell. It
uniquely
identifies a cell
within a BS.
GUI Value
Range:0~17
Actual Value
Range:0~17
Default
Value:None
Unit:None
ENodeBAlgoS
witch AnrSwitch MOD
ENODEBALG
LOFD-002001 /
TDLOFD-0020
Automatic
Neighbour
Meaning:Indicat
es the automatic
eRAN
ANR Management Feature Parameter Description 15 Parameters
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
88
MO Parameter ID MML Command
Feature ID Feature Name Description
OSWITCH
LST
ENODEBALG
OSWITCH
01
LOFD-002002
Relation (ANR)
Inter-RAT ANR
neighbor
relation (ANR)
algorithm
switch.
Switches related
to ANR are
described as
follows:
IntraRatEventA
nrSwitch: If this
switch is turned
on, intra-RAT
event-triggered
ANR is enabled
to construct and
optimize
intra-RAT
neighboring
relations by
triggering
intra-RAT
coverage-based
handover
events.
IntraRatFastAnr
Switch: If this
switch is turned
on, intra-RAT
fast ANR is
enabled to
construct and
optimize
intra-RAT
neighboring
relations by
performing
periodic
intra-RAT
measurements.
IntraRatAnrAut
oDelSwitch: If
this switch is
turned on,
IntraRatEventA
nrSwitch is
turned on, and
No Remove (a
flag in the
neighboring
relation table)
of an intra-RAT neighboring cell
eRAN
ANR Management Feature Parameter Description 15 Parameters
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
89
MO Parameter ID MML Command
Feature ID Feature Name Description
is set to False,
automatic
removal of the
intra-RAT
neighboring
relation is
allowed. If
IntraRatAnrAut
oDelSwitch is
turned off,
automatic
removal of the
intra-RAT
neighboring
relation is not
allowed.
UtranEventAnr
Switch: If this
switch is turned
on,
event-triggered
ANR with
UTRAN is
enabled to
construct and
optimize
inter-RAT
neighboring
relations with
UTRAN cells
by triggering
events for
inter-RAT
coverage-based
handovers to
UTRAN.
GeranEventAnr
Switch: If this
switch is turned
on,
event-triggered
ANR with
GERAN is
enabled to
construct and
optimize
inter-RAT
neighboring
relations with
GERAN cells
by triggering events for
eRAN
ANR Management Feature Parameter Description 15 Parameters
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
90
MO Parameter ID MML Command
Feature ID Feature Name Description
inter-RAT
coverage-based
handovers to
GERAN.
UtranFastAnrS
witch: If this
switch is turned
on, fast ANR
with UTRAN is
enabled to
construct and
optimize
inter-RAT
neighboring
relations with
UTRAN cells
based on
periodic UE
measurements
on UTRAN.
The eNodeB
does not deliver
information
about external
UTRAN cells in
the
measurement
configuration to
UEs and the
UEs measure
only
neighboring
cells contained
in the
measurement
configuration.
Therefore, if
you want
external
UTRAN cells
added by fast
ANR with
UTRAN to be
measured in
handovers, you
are advised to
turn on
UtranEventAnr
Switch as well.
GeranFastAnrS
witch: If this switch is turned
eRAN
ANR Management Feature Parameter Description 15 Parameters
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
91
MO Parameter ID MML Command
Feature ID Feature Name Description
on, fast ANR
with GERAN is
enabled to
construct and
optimize
inter-RAT
neighboring
relations with
GERAN cells
by performing
periodic
inter-RAT
measurements
on GERAN.
CdmaFastAnrS
witch: If this
switch is turned
on, fast ANR
with
CDMA2000 is
enabled to
construct and
optimize
inter-RAT
neighboring
relations with
CDMA2000
cells by
performing
periodic
inter-RAT
measurements
on CDMA2000
networks.
UtranAutoNrtD
eleteSwitch: If
this switch is
turned on,
UtranEventAnr
Switch is turned
on, and No
Remove (a flag
in the
neighboring
relation table)
of a neighboring
GERAN cell is
set to False,
automatic
removal of the
inter-RAT neighboring
eRAN
ANR Management Feature Parameter Description 15 Parameters
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
92
MO Parameter ID MML Command
Feature ID Feature Name Description
relation is
allowed. If
UtranAutoNrtD
eleteSwitch is
turned off,
automatic
removal of the
inter-RAT
neighboring
relation is not
allowed.
GeranAutoNrtD
eleteSwitch: If
this switch is
turned on,
GeranEventAnr
Switch is turned
on, and No
Remove (a flag
in the
neighboring
relation table)
of a neighboring
GERAN cell is
set to False,
automatic
removal of the
inter-RAT
neighboring
relation is
allowed. If
GeranAutoNrtD
eleteSwitch is
turned off,
automatic
removal of the
inter-RAT
neighboring
relation is not
allowed.
CdmaAutoNrtD
eleteSwitch: If
this switch is
turned on,
CdmaEventAnr
Switch is turned
on, and No
Remove (a flag
in the
neighboring
relation table) of a neighboring
eRAN
ANR Management Feature Parameter Description 15 Parameters
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
93
MO Parameter ID MML Command
Feature ID Feature Name Description
CDMA2000
cell is set to
False, automatic
removal of the
inter-RAT
neighboring
relation is
allowed. If this
switch is turned
off, automatic
removal of the
inter-RAT
neighboring
relation is not
allowed.
ExtendIntraRat
AnrSwitch:
This switch is
used to control
whether cells
with unknown
physical cell
identifiers
(PCIs) can be
configured as
external cells of
the eNodeB by
using the
eCoordinator. If
this switch is
turned on, cells
with unknown
PCIs can be
configured as
external cells of
the eNodeB by
using the
eCoordinator in
any of the
following
scenarios: (1)
When unknown
PCIs are
detected by
triggering
handover
events,
IntraRatEventA
nrSwitch is
turned off or the
UE is incapable of measuring
eRAN
ANR Management Feature Parameter Description 15 Parameters
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
94
MO Parameter ID MML Command
Feature ID Feature Name Description
cell global
identifications
(CGIs). (2)
When unknown
PCIs are
detected by
performing
periodic
intra-RAT
measurements,
the UE is
incapable of
measuring
CGIs. This
parameter will
be removed in
later versions.
In this version,
the setting of
this parameter is
still
synchronized
between the
M2000 and the
eNodeB, but it
is no longer
used internally.
Therefore,
avoid using this
parameter.
CdmaEventAnr
Switch: If this
switch is turned
on,
event-triggered
ANR with
CDMA2000 is
enabled to
construct and
optimize
inter-RAT
neighbor
relations with
CDMA2000
cells by
triggering
events for
inter-RAT
handovers to
CDMA2000.
GUI Value
Range:IntraRat
eRAN
ANR Management Feature Parameter Description 15 Parameters
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
95
MO Parameter ID MML Command
Feature ID Feature Name Description
EventAnrSwitc
h(IntraRatEvent
AnrSwitch),
IntraRatFastAnr
Switch(IntraRat
FastAnrSwitch),
IntraRatAnrAut
oDelSwitch(Intr
aRatAnrAutoDe
lSwitch),
UtranEventAnr
Switch(UtranEv
entAnrSwitch),
GeranEventAnr
Switch(GeranE
ventAnrSwitch)
,
UtranFastAnrS
witch(UtranFast
AnrSwitch),
GeranFastAnrS
witch(GeranFas
tAnrSwitch),
CdmaFastAnrS
witch(CdmaFast
AnrSwitch),
UtranAutoNrtD
eleteSwitch(Utr
anAutoNrtDelet
eSwitch),
GeranAutoNrtD
eleteSwitch(Ger
anAutoNrtDelet
eSwitch),
CdmaAutoNrtD
eleteSwitch(Cd
maAutoNrtDele
teSwitch),
ExtendIntraRat
AnrSwitch(Exte
ndIntraRatAnrS
witch),
CdmaEventAnr
Switch(CdmaEv
entAnrSwitch)
Actual Value
Range:IntraRat
EventAnrSwitc
h,
IntraRatFastAnr
Switch,
IntraRatAnrAut
eRAN
ANR Management Feature Parameter Description 15 Parameters
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
96
MO Parameter ID MML Command
Feature ID Feature Name Description
oDelSwitch,
UtranEventAnr
Switch,
GeranEventAnr
Switch,
UtranFastAnrS
witch,
GeranFastAnrS
witch,
CdmaFastAnrS
witch,
UtranAutoNrtD
eleteSwitch,
GeranAutoNrtD
eleteSwitch,
CdmaAutoNrtD
eleteSwitch,
ExtendIntraRat
AnrSwitch,
CdmaEventAnr
Switch
Default
Value:IntraRatE
ventAnrSwitch:
Off,
IntraRatFastAnr
Switch:Off,
IntraRatAnrAut
oDelSwitch:On,
UtranEventAnr
Switch:Off,
GeranEventAnr
Switch:Off,
UtranFastAnrS
witch:Off,
GeranFastAnrS
witch:Off,
CdmaFastAnrS
witch:Off,
UtranAutoNrtD
eleteSwitch:On,
GeranAutoNrtD
eleteSwitch:On,
CdmaAutoNrtD
eleteSwitch:On,
ExtendIntraRat
AnrSwitch:Off,
CdmaEventAnr
Switch:Off
Unit:None
eRAN
ANR Management Feature Parameter Description 15 Parameters
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
97
MO Parameter ID MML Command
Feature ID Feature Name Description
ACL CTRLMODE ADD ACL
MOD ACL
LST ACL
None None Meaning:Indicat
es whether the
object can be
modified or
deleted by the
system. The
value
MANUAL_MO
DE means that
only the user
can modify or
delete the
object. The
value
AUTO_MODE
means that both
the system and
the user can
modify or delete
the object.
GUI Value
Range:MANUA
L_MODE(Man
ual Mode),
AUTO_MODE(
Auto Mode)
Actual Value
Range:MANUA
L_MODE,
AUTO_MODE
Default
Value:MANUA
L_MODE(Man
ual Mode)
Unit:None
ANR StatisticPeriodF
orNRTDel
MOD ANR
LST ANR
LOFD-002001 /
TDLOFD-0020
01
Automatic
Neighbour
Relation (ANR)
Meaning:Indicat
es the period
during which
the number of
handovers are
measured for
neighbor
relationship
removal from a
neighbor
relation table
(NRT) when the
number of
neighbor
relationships in
eRAN
ANR Management Feature Parameter Description 15 Parameters
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
98
MO Parameter ID MML Command
Feature ID Feature Name Description
the NRT has
reached the
maximum
specification
and a new
neighbor
relationship is
to be added to
the NRT by
ANR. This
parameter is
also used to
determine
external cell
removal from a
neighboring cell
list (NCL).
Within four
consecutive
measurement
periods, if an
external cell is
not added to the
NRT as a
neighboring
cell, and the
local eNodeB is
not configured
with an X2
interface with
the peer
eNodeB
providing this
external cell,
this external cell
is removed from
the NCL.
GUI Value
Range:1~50400
Actual Value
Range:1~50400
Default
Value:10080
Unit:min
ANR StatisticNumFor
NRTDel
MOD ANR
LST ANR
LOFD-002001 /
TDLOFD-0020
01
Automatic
Neighbour
Relation (ANR)
Meaning:Indicat
es the number
of handovers
above which a
neighbor relationship is
eRAN
ANR Management Feature Parameter Description 15 Parameters
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
99
MO Parameter ID MML Command
Feature ID Feature Name Description
to be removed
from a neighbor
relation table
(NRT) when the
number of
neighbor
relationships in
the NRT has
reached the
maximum
specification
and a new
neighbor
relationship is
to be added to
the NRT by
ANR. In the
latest
measurement
period for
neighbor
relationship
removal, if the
total number of
handovers from
the local cell
exceeds the
value of this
parameter, a
neighboring cell
that is not
detected by UEs
is removed from
the NRT.
GUI Value
Range:1~10000
Actual Value
Range:1~10000
Default
Value:200
Unit:None
ANR StatisticPeriod MOD ANR
LST ANR
LOFD-002001 /
TDLOFD-0020
01
Automatic
Neighbour
Relation (ANR)
Meaning:Indicat
es the period
during which
the total number
of handovers to
an intra-RAT
neighboring cell
is measured by ANR to
eRAN
ANR Management Feature Parameter Description 15 Parameters
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
100
MO Parameter ID MML Command
Feature ID Feature Name Description
evaluate the
removal of the
neighboring
relation in the
case of a low
handover
success rate.
GUI Value
Range:1~10080
Actual Value
Range:1~10080
Default
Value:1440
Unit:min
ANR NcellHoStatNu
m
MOD ANR
LST ANR
LOFD-002001 /
TDLOFD-0020
01
Automatic
Neighbour
Relation (ANR)
Meaning:Indicat
es the threshold
for the total
number of
handovers to an
intra-RAT
neighboring
cell, above
which ANR
begins to
evaluate the
removal of the
neighboring
relation in the
case of a low
handover
success rate.
GUI Value
Range:1~10000
Actual Value
Range:1~10000
Default
Value:200
Unit:None
ANR DelCellThd MOD ANR
LST ANR
LOFD-002001 /
TDLOFD-0020
01
Automatic
Neighbour
Relation (ANR)
Meaning:Indicat
es the threshold
for removing a
neighbor
relationship
with a cell by
ANR based on
the handover
success rate. The threshold is
eRAN
ANR Management Feature Parameter Description 15 Parameters
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
101
MO Parameter ID MML Command
Feature ID Feature Name Description
the percentage
of the number
of successful
handovers to the
total number of
handovers from
the local cell to
the neighboring
cell. For
example, an
external cell is
configured as a
neighboring cell
for all cells
under an
eNodeB, and
this neighboring
cell permits
automatic
removal of the
neighboring
relationship by
ANR. If the
success rate of
handovers from
each cell under
the eNodeB to
this neighboring
cell is lower
than or equal to
this threshold
after a
measurement
period, the
corresponding
external cell and
the neighbor
relationship
with this cell
are
automatically
removed.
GUI Value
Range:0~100
Actual Value
Range:0~100
Default Value:0
Unit:%
ANR FastAnrRsrpTh
d MOD ANR LOFD-002001 /
TDLOFD-0020
Automatic
Neighbour
Meaning:Indicat
es the reference
eRAN
ANR Management Feature Parameter Description 15 Parameters
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
102
MO Parameter ID MML Command
Feature ID Feature Name Description
LST ANR 01
LOFD-002002
Relation (ANR)
Inter-RAT ANR
signal received
power (RSRP)
threshold for
intra-RAT fast
ANR. If the
signal quality in
a neighboring
E-UTRAN cell
reported by the
UE is lower
than the
threshold, the
cell is not
automatically
added as an
external cell of
the eNodeB.
GUI Value
Range:-130~-70
Actual Value
Range:-130~-70
Default
Value:-102
Unit:dBm
ANR FastAnrIntraRat
MeasUeNum
MOD ANR
LST ANR
LOFD-002001 /
TDLOFD-0020
01
Automatic
Neighbour
Relation (ANR)
Meaning:Indicat
es the maximum
allowed number
of UEs that
perform
intra-RAT
measurements
for fast ANR.
After the
number of UEs
performing
intra-RAT
measurements
for fast ANR
reaches the
maximum
number,
intra-RAT
measurements
for fast ANR
will not be
performed on
other UEs.
GUI Value
Range:1~200
eRAN
ANR Management Feature Parameter Description 15 Parameters
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
103
MO Parameter ID MML Command
Feature ID Feature Name Description
Actual Value
Range:1~200
Default Value:5
Unit:None
ANR FastAnrRprtAm
ount
MOD ANR
LST ANR
LOFD-002001 /
TDLOFD-0020
01
Automatic
Neighbour
Relation (ANR)
Meaning:Indicat
es the number
of periodic
measurement
reports sent for
fast ANR.
GUI Value
Range:r1(1),
r2(2), r4(4),
r8(8), r16(16),
r32(32),
r64(64),
Infinity(Infinity
)
Actual Value
Range:r1, r2, r4,
r8, r16, r32, r64,
Infinity
Default
Value:r4(4)
Unit:None
ANR FastAnrRprtInte
rval
MOD ANR
LST ANR
LOFD-002001 /
TDLOFD-0020
01
Automatic
Neighbour
Relation (ANR)
Meaning:Indicat
es the interval at
which periodic
measurement
reports are sent
for fast ANR.
GUI Value
Range:120ms,
240ms, 480ms,
640ms, 1024ms,
2048ms,
5120ms,
10240ms, 1min,
6min, 12min,
30min, 60min
Actual Value
Range:120ms,
240ms, 480ms,
640ms, 1024ms,
2048ms,
5120ms,
10240ms, 1min, 6min, 12min,
eRAN
ANR Management Feature Parameter Description 15 Parameters
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
104
MO Parameter ID MML Command
Feature ID Feature Name Description
30min, 60min
Default
Value:5120ms
Unit:None
ANR FastAnrIntraRat
UeNumThd
MOD ANR
LST ANR
LOFD-002001 /
TDLOFD-0020
01
Automatic
Neighbour
Relation (ANR)
Meaning:Indicat
es the threshold
above which the
eNodeB enters
the monitoring
state for
intra-RAT fast
ANR. The
threshold is
expressed as the
number of UEs
that have
performed
measurements
for intra-RAT
fast ANR.
GUI Value
Range:1~10000
Actual Value
Range:1~10000
Default
Value:20
Unit:None
ANR FastAnrCheckP
eriod
MOD ANR
LST ANR
LOFD-002001 /
TDLOFD-0020
01
LOFD-002002
Automatic
Neighbour
Relation (ANR)
Inter-RAT ANR
Meaning:Indicat
es the fast ANR
checking timer.
When the timer
is expired, the
eNodeB
automatically
checks whether
to disable fast
ANR.
GUI Value
Range:1~10080
Actual Value
Range:1~10080
Default
Value:60
Unit:min
UtranExternalC
ell
CtrlMode ADD
UTRANEXTE
LOFD-002001 /
TDLOFD-0020
Automatic
Neighbour
Meaning:Indicat
es the control policy on
eRAN
ANR Management Feature Parameter Description 15 Parameters
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
105
MO Parameter ID MML Command
Feature ID Feature Name Description
RNALCELL
MOD
UTRANEXTE
RNALCELL
LST
UTRANEXTE
RNALCELL
01 Relation (ANR) ANR-related
MOs, which can
be defined by
the user or be
based on
Automatic
Neighbor
Relation (ANR)
algorithm.
When this
parameter is set
to
MANUAL_MO
DE, the
ANR-related
MOs can be
modified or
removed by
only the user. A
failure message
is displayed
when the user
adds an existed
MO. When this
parameter is set
to
AUTO_MODE,
the
ANR-related
MOs can be
modified or
removed by the
user or based on
the ANR
algorithm. The
MO removal is
successful even
if the MO does
not exist. An
MO can be
added both by
the user and
based on the
ANR algorithm.
If an existed
MO is to be
added, the MO
is modified
when the user
performs the
addition, but it cannot be added
eRAN
ANR Management Feature Parameter Description 15 Parameters
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
106
MO Parameter ID MML Command
Feature ID Feature Name Description
based on the
ANR algorithm.
The preceding
control policy
also applies to
the
UtranExternalC
ellPlmn MO,
which is a child
MO of the
UtranExternalC
ell MO. When
the
ANR-related
MOs are
automatically
added based on
the ANR
algorithm, this
parameter is set
to
AUTO_MODE
by default.
When the
ANR-related
MOs are added
by the user, this
parameter can
be set to
AUTO_MODE
or
MANUAL_MO
DE.
GUI Value
Range:AUTO_
MODE(Auto
Mode),
MANUAL_MO
DE(Manual
Mode)
Actual Value
Range:AUTO_
MODE,
MANUAL_MO
DE
Default
Value:AUTO_
MODE(Auto
Mode)
Unit:None
eRAN
ANR Management Feature Parameter Description 15 Parameters
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
107
MO Parameter ID MML Command
Feature ID Feature Name Description
UtranNCell CtrlMode ADD
UTRANNCEL
L
MOD
UTRANNCEL
L
LST
UTRANNCEL
L
LOFD-002001 /
TDLOFD-0020
01
Automatic
Neighbour
Relation (ANR)
Meaning:Indicat
es the control
policy on
ANR-related
MOs, which can
be defined by
the user or be
based on
ANR(Automati
c Neighbor
Relation)
algorithm.
When this
parameter is set
to
MANUAL_MO
DE, the
ANR-related
MOs can be
modified or
removed by
only the user. A
failure message
is displayed
when the user
adds an existed
MO. When this
parameter is set
to
AUTO_MODE,
the
ANR-related
MOs can be
modified or
removed by the
user or based on
the ANR
algorithm. The
MO removal is
successful even
if the MO does
not exist. An
MO can be
added both by
the user and
based on the
ANR algorithm.
If an existed
MO is to be
added, the MO
is modified
when the user
eRAN
ANR Management Feature Parameter Description 15 Parameters
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
108
MO Parameter ID MML Command
Feature ID Feature Name Description
performs the
addition, but it
cannot be added
based on the
ANR algorithm.
When the
ANR-related
MOs are
automatically
added based on
the ANR
algorithm, this
parameter is set
to
AUTO_MODE
by default.
When the
ANR-related
MOs are added
by the user, this
parameter can
be set to
AUTO_MODE
or
MANUAL_MO
DE.
GUI Value
Range:AUTO_
MODE(Auto
Mode),
MANUAL_MO
DE(Manual
Mode)
Actual Value
Range:AUTO_
MODE,
MANUAL_MO
DE
Default
Value:AUTO_
MODE(Auto
Mode)
Unit:None
GeranExternalC
ell
CtrlMode ADD
GERANEXTE
RNALCELL
MOD
GERANEXTE
RNALCELL
LOFD-002001 /
TDLOFD-0020
01
Automatic
Neighbour
Relation (ANR)
Meaning:Indicat
es the control
policy on
ANR-related
MOs, which can
be defined by the user or be
eRAN
ANR Management Feature Parameter Description 15 Parameters
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
109
MO Parameter ID MML Command
Feature ID Feature Name Description
LST
GERANEXTE
RNALCELL
based on
Automatic
Neighbor
Relation (ANR)
algorithm.
When this
parameter is set
to
MANUAL_MO
DE, the
ANR-related
MOs can be
modified or
removed by
only the user. A
failure message
is displayed
when the user
adds an existed
MO. When this
parameter is set
to
AUTO_MODE,
the
ANR-related
MOs can be
modified or
removed by the
user or based on
the ANR
algorithm. The
MO removal is
successful even
if the MO does
not exist. An
MO can be
added both by
the user and
based on the
ANR algorithm.
If an existed
MO is to be
added, the MO
is modified
when the user
performs the
addition, but it
cannot be added
based on the
ANR algorithm.
The preceding control policy
eRAN
ANR Management Feature Parameter Description 15 Parameters
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
110
MO Parameter ID MML Command
Feature ID Feature Name Description
also applies to
the
GeranExternalC
ellPlmn MO,
which is a child
MO of the
GeranExternalC
ell MO. When
the
ANR-related
MOs are
automatically
added based on
the ANR
algorithm, this
parameter is set
to
AUTO_MODE
by default.
When the
ANR-related
MOs are added
by the user, this
parameter can
be set to
AUTO_MODE
or
MANUAL_MO
DE.
GUI Value
Range:AUTO_
MODE(Auto
Mode),
MANUAL_MO
DE(Manual
Mode)
Actual Value
Range:AUTO_
MODE,
MANUAL_MO
DE
Default
Value:AUTO_
MODE(Auto
Mode)
Unit:None
GeranNcell CtrlMode ADD
GERANNCEL
L
MOD
LOFD-002001 /
TDLOFD-0020
01
Automatic
Neighbour
Relation (ANR)
Meaning:Indicat
es the control
policy on ANR-related
eRAN
ANR Management Feature Parameter Description 15 Parameters
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
111
MO Parameter ID MML Command
Feature ID Feature Name Description
GERANNCEL
L
LST
GERANNCEL
L
MOs, which can
be defined by
the user or be
based on
ANR(Automati
c Neighbor
Relation)
algorithm.
When this
parameter is set
to
MANUAL_MO
DE, the
ANR-related
MOs can be
modified or
removed by
only the user. A
failure message
is displayed
when the user
adds an existed
MO. When this
parameter is set
to
AUTO_MODE,
the
ANR-related
MOs can be
modified or
removed by the
user or based on
the ANR
algorithm. The
MO removal is
successful even
if the MO does
not exist. An
MO can be
added both by
the user and
based on the
ANR algorithm.
If an existed
MO is to be
added, the MO
is modified
when the user
performs the
addition, but it
cannot be added based on the
eRAN
ANR Management Feature Parameter Description 15 Parameters
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
112
MO Parameter ID MML Command
Feature ID Feature Name Description
ANR algorithm.
When the
ANR-related
MOs are
automatically
added based on
the ANR
algorithm, this
parameter is set
to
AUTO_MODE
by default.
When the
ANR-related
MOs are added
by the user, this
parameter can
be set to
AUTO_MODE
or
MANUAL_MO
DE.
GUI Value
Range:AUTO_
MODE(Auto
Mode),
MANUAL_MO
DE(Manual
Mode)
Actual Value
Range:AUTO_
MODE,
MANUAL_MO
DE
Default
Value:AUTO_
MODE(Auto
Mode)
Unit:None
ANR FastAnrRscpTh
d
MOD ANR
LST ANR
LOFD-002001 /
TDLOFD-0020
01
LOFD-002002
Automatic
Neighbour
Relation (ANR)
Inter-RAT ANR
Meaning:Indicat
es the received
signal code
power (RSCP)
threshold for
fast ANR with
UTRAN. If the
signal quality in
a neighboring
UTRAN cell reported by the
eRAN
ANR Management Feature Parameter Description 15 Parameters
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
113
MO Parameter ID MML Command
Feature ID Feature Name Description
UE is lower
than the
threshold, the
cell is not
automatically
added as an
external cell of
the eNodeB.
GUI Value
Range:-120~-25
Actual Value
Range:-120~-25
Default
Value:-106
Unit:dBm
ANR FastAnrRssiThd MOD ANR
LST ANR
LOFD-002001 /
TDLOFD-0020
01
LOFD-002002
Automatic
Neighbour
Relation (ANR)
Inter-RAT ANR
Meaning:Indicat
es the received
signal strength
indicator (RSSI)
threshold for
fast ANR with
GERAN. If the
signal quality in
a neighboring
GERAN cell
reported by the
UE is lower
than the
threshold, the
cell is not
automatically
added as an
external cell of
the eNodeB.
GUI Value
Range:-110~-48
Actual Value
Range:-110~-48
Default
Value:-103
Unit:dBm
ANR FastAnrInterRat
MeasUeNum
MOD ANR
LST ANR
LOFD-002002 Inter-RAT ANR Meaning:Indicat
es the maximum
allowed number
of UEs that
perform
inter-RAT measurements
eRAN
ANR Management Feature Parameter Description 15 Parameters
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
114
MO Parameter ID MML Command
Feature ID Feature Name Description
for fast ANR.
After the
number of UEs
performing
inter-RAT
measurements
for fast ANR
reaches the
maximum
number,
inter-RAT
measurements
for fast ANR
will not be
performed on
other UEs.
GUI Value
Range:1~200
Actual Value
Range:1~200
Default Value:5
Unit:None
ANR FastAnrInterRat
UeNumThd
MOD ANR
LST ANR
LOFD-002002 Inter-RAT ANR Meaning:Indicat
es the threshold
above which the
eNodeB enters
the monitoring
state for
inter-RAT fast
ANR. The
threshold is
expressed as the
number of UEs
that have
performed
measurements
for inter-RAT
fast ANR.
GUI Value
Range:1~10000
Actual Value
Range:1~10000
Default
Value:20
Unit:None
ENodeBAlgoS
witch
RanSharingAnr
Switch
MOD
ENODEBALGOSWITCH
LOFD-002001 /
TDLOFD-002001
Automatic
Neighbour Relation (ANR)
Meaning:Indicat
es the ANR algorithm
eRAN
ANR Management Feature Parameter Description 15 Parameters
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
115
MO Parameter ID MML Command
Feature ID Feature Name Description
LST
ENODEBALG
OSWITCH
LOFD-002002 /
TDLOFD-0020
02
Inter-RAT ANR switch in eRAN
sharing mode.
Related
switches are
described as
follows:
NBSLTEPLMN
RoundSwitch:
If this switch is
turned on, some
neighboring
eNodeBs
provide cells
that work in
eRAN sharing
mode and
broadcast their
PLMN lists in a
round robin
(RR) manner. In
this situation, if
IntraRatEventA
nrSwitch or
IntraRatFastAnr
Switch is turned
on for the local
eNodeB, the
local eNodeB
will ask the
M2000 for the
actual cell
global identifier
(CGI) and
PLMN list for a
cell
broadcasting
PLMNs in an
RR manner
after the UE
reports the CGI
of the cell
during ANR
measurements.
If both
NBSLTEPLMN
RoundSwitch
and
NBSLTERANS
haringSwitch
are turned on,
NBSLTEPLMNRoundSwitch
eRAN
ANR Management Feature Parameter Description 15 Parameters
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
116
MO Parameter ID MML Command
Feature ID Feature Name Description
overrides
NBSLTERANS
haringSwitch.
NBSLTERANS
haringSwitch: If
this switch is
turned on, some
neighboring
eNodeBs
provide cells
that work in
eRAN sharing
mode. In this
situation, if
IntraRatEventA
nrSwitch or
IntraRatFastAnr
Switch is turned
on for the local
eNodeB, the
local eNodeB
will ask the
M2000 for the
PLMN list for a
cell after the UE
reports the CGI
of the cell
during ANR
measurements.
If the UE has
reported the
PLMNlist, the
local eNodeB
will not ask the
M2000 for the
PLMN list.
NBSUTRANR
ANSharingSwit
ch: If this
switch is turned
on, some
neighboring
NodeBs provide
cells that work
in UTRAN
sharing mode.
In this situation,
if
UtranEventAnr
Switch or
UtranFastAnrSwitch is turned
eRAN
ANR Management Feature Parameter Description 15 Parameters
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
117
MO Parameter ID MML Command
Feature ID Feature Name Description
on for the local
eNodeB, the
local eNodeB
will ask the
M2000 for the
PLMN list for a
cell after the UE
reports the CGI
of the cell
during ANR
measurements.
If the UE has
reported the
PLMNlist, the
local eNodeB
will not ask the
M2000 for the
PLMN list.
NBSGERANR
ANSharingSwit
ch: If this
switch is turned
on, some
neighboring
BTSs provide
cells that work
in GERAN
sharing mode.
In this situation,
if
GeranEventAnr
Switch or
GeranFastAnrS
witch is turned
on for the local
eNodeB, the
local eNodeB
will ask the
M2000 for the
PLMN list for a
cell after the UE
reports the CGI
of the cell
during ANR
measurements.
GUI Value
Range:NBSLTE
PLMNRoundS
witch(NBSLTE
PLMNRoundS
witch),
NBSLTERANS
eRAN
ANR Management Feature Parameter Description 15 Parameters
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
118
MO Parameter ID MML Command
Feature ID Feature Name Description
haringSwitch(N
BSLTERANSh
aringSwitch),
NBSUTRANR
ANSharingSwit
ch(NBSUTRA
NRANSharingS
witch),
NBSGERANR
ANSharingSwit
ch(NBSGERA
NRANSharingS
witch)
Actual Value
Range:NBSLTE
PLMNRoundS
witch,
NBSLTERANS
haringSwitch,
NBSUTRANR
ANSharingSwit
ch,
NBSGERANR
ANSharingSwit
ch
Default
Value:NBSLTE
PLMNRoundS
witch:Off,
NBSLTERANS
haringSwitch:O
ff,
NBSUTRANR
ANSharingSwit
ch:Off,
NBSGERANR
ANSharingSwit
ch:Off
Unit:None
EutranInterFreq
NCell NoHoFlag ADD
EUTRANINTE
RFREQNCELL
MOD
EUTRANINTE
RFREQNCELL
LST
EUTRANINTE
RFREQNCELL
LBFD-0020180
2 /
TDLBFD-0020
1802
LOFD-002001 /
TDLOFD-0020
01
Coverage Based
Inter-frequency
Handover
Automatic
Neighbour
Relation (ANR)
Meaning:Indicat
es whether
handovers of
UEs to the
neighboring cell
are prohibited.
GUI Value
Range:PERMIT
_HO_ENUM(P
ermit Ho), FORBID_HO_
eRAN
ANR Management Feature Parameter Description 15 Parameters
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
119
MO Parameter ID MML Command
Feature ID Feature Name Description
ENUM(Forbid
Ho)
Actual Value
Range:PERMIT
_HO_ENUM,
FORBID_HO_
ENUM
Default
Value:PERMIT
_HO_ENUM(P
ermit Ho)
Unit:None
EutranIntraFreq
NCell
NoRmvFlag ADD
EUTRANINTR
AFREQNCELL
MOD
EUTRANINTR
AFREQNCELL
LST
EUTRANINTR
AFREQNCELL
LOFD-002001 /
TDLOFD-0020
01
Automatic
Neighbour
Relation (ANR)
Meaning:Indicat
es whether to
permit or
prohibit
removal of the
neighboring
relationship by
ANR.
GUI Value
Range:PERMIT
_RMV_ENUM(
Permit ANR
Remove),
FORBID_RMV
_ENUM(Forbid
ANR Remove)
Actual Value
Range:PERMIT
_RMV_ENUM,
FORBID_RMV
_ENUM
Default
Value:PERMIT
_RMV_ENUM(
Permit ANR
Remove)
Unit:None
EutranIntraFreq
NCell
NoHoFlag ADD
EUTRANINTR
AFREQNCELL
MOD
EUTRANINTR
AFREQNCELL
LST
EUTRANINTR
LBFD-0020180
1 /
TDLBFD-0020
1801
LOFD-002001 /
TDLOFD-0020
01
Coverage Based
Intra-frequency
Handover
Automatic
Neighbour
Relation (ANR)
Meaning:Indicat
es whether
handovers of
UEs to the
neighboring cell
are prohibited.
GUI Value
Range:PERMIT_HO_ENUM(P
eRAN
ANR Management Feature Parameter Description 15 Parameters
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
120
MO Parameter ID MML Command
Feature ID Feature Name Description
AFREQNCELL ermit Ho),
FORBID_HO_
ENUM(Forbid
Ho)
Actual Value
Range:PERMIT
_HO_ENUM,
FORBID_HO_
ENUM
Default
Value:PERMIT
_HO_ENUM(P
ermit Ho)
Unit:None
EutranInterFreq
NCell
NoRmvFlag ADD
EUTRANINTE
RFREQNCELL
MOD
EUTRANINTE
RFREQNCELL
LST
EUTRANINTE
RFREQNCELL
LOFD-002001 /
TDLOFD-0020
01
Automatic
Neighbour
Relation (ANR)
Meaning:Indicat
es whether to
permit or
prohibit
removal of the
neighboring
relationship by
ANR.
GUI Value
Range:PERMIT
_RMV_ENUM(
Permit ANR
Remove),
FORBID_RMV
_ENUM(Forbid
ANR Remove)
Actual Value
Range:PERMIT
_RMV_ENUM,
FORBID_RMV
_ENUM
Default
Value:PERMIT
_RMV_ENUM(
Permit ANR
Remove)
Unit:None
UtranNCell NoHoFlag ADD
UTRANNCEL
L
MOD
UTRANNCEL
L
LST
LOFD-001019 /
TDLOFD-0010
19
LOFD-002002
PS Inter-RAT
Mobility
between
E-UTRAN and
UTRAN
Inter-RAT ANR
Meaning:Indicat
es whether to
allow handover
of UEs to the
neighboring cell
that is
determined by
eRAN
ANR Management Feature Parameter Description 15 Parameters
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
121
MO Parameter ID MML Command
Feature ID Feature Name Description
UTRANNCEL
L
the neighboring
relation.
GUI Value
Range:PERMIT
_HO_ENUM(P
ermit Ho),
FORBID_HO_
ENUM(Forbid
Ho)
Actual Value
Range:PERMIT
_HO_ENUM,
FORBID_HO_
ENUM
Default
Value:PERMIT
_HO_ENUM(P
ermit Ho)
Unit:None
UtranNCell NoRmvFlag ADD
UTRANNCEL
L
MOD
UTRANNCEL
L
LST
UTRANNCEL
L
LOFD-002001 /
TDLOFD-0020
01
LOFD-002002
Automatic
Neighbour
Relation (ANR)
Inter-RAT ANR
Meaning:Indicat
es whether to
permit or
prohibit
removal of the
neighboring
relationship by
ANR.
GUI Value
Range:PERMIT
_RMV_ENUM(
Permit ANR
Remove),
FORBID_RMV
_ENUM(Forbid
ANR Remove)
Actual Value
Range:PERMIT
_RMV_ENUM,
FORBID_RMV
_ENUM
Default
Value:PERMIT
_RMV_ENUM(
Permit ANR
Remove)
Unit:None
GeranNcell NoHoFlag ADD
GERANNCELLOFD-002002 Inter-RAT ANR Meaning:Indicat
es whether
eRAN
ANR Management Feature Parameter Description 15 Parameters
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
122
MO Parameter ID MML Command
Feature ID Feature Name Description
L
MOD
GERANNCEL
L
LST
GERANNCEL
L
handovers of
UEs to the
neighboring cell
are prohibited.
GUI Value
Range:PERMIT
_HO_ENUM(P
ermit Ho),
FORBID_HO_
ENUM(Forbid
Ho)
Actual Value
Range:PERMIT
_HO_ENUM,
FORBID_HO_
ENUM
Default
Value:PERMIT
_HO_ENUM(P
ermit Ho)
Unit:None
GeranNcell NoRmvFlag ADD
GERANNCEL
L
MOD
GERANNCEL
L
LST
GERANNCEL
L
LOFD-002001 /
TDLOFD-0020
01
LOFD-002002
Automatic
Neighbour
Relation (ANR)
Inter-RAT ANR
Meaning:Indicat
es whether to
permit or
prohibit
removal of the
neighboring
relationship by
ANR.
GUI Value
Range:PERMIT
_RMV_ENUM(
Permit ANR
Remove),
FORBID_RMV
_ENUM(Forbid
ANR Remove)
Actual Value
Range:PERMIT
_RMV_ENUM,
FORBID_RMV
_ENUM
Default
Value:PERMIT
_RMV_ENUM(
Permit ANR
Remove)
Unit:None
eRAN
ANR Management Feature Parameter Description 15 Parameters
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
123
MO Parameter ID MML Command
Feature ID Feature Name Description
GlobalProcSwit
ch
X2SonDeleteTi
mer
MOD
GLOBALPRO
CSWITCH
LST
GLOBALPRO
CSWITCH
LOFD-002001 /
TDLBFD-0020
01
Automatic
Neighbour
Relation (ANR)
Meaning:Indicat
es the time
during which
the X2 interface
configuration is
retained for a
local eNodeB
and a peer
eNodeB when
the two
eNodeBs do not
have a neighbor
relationship
with each other.
If the local
eNodeB
determines that
a neighbor
relationship is
not configured
for the local and
peer eNodeBs,
the local
eNodeB starts
the timer and
removes the X2
interface
configuration
when the timer
expires. If this
parameter is set
to 0, the
function of
automatic X2
interface
configuration
removal is
disabled.
GUI Value
Range:0~50400
Actual Value
Range:0~50400
Default Value:0
Unit:min
ANR OptMode MOD ANR
LST ANR
LOFD-002001 /
TDLOFD-0020
01
Automatic
Neighbour
Relation (ANR)
Meaning:Indicat
es the mode for
optimizing
neighboring
relations. If this
parameter is set
eRAN
ANR Management Feature Parameter Description 15 Parameters
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
124
MO Parameter ID MML Command
Feature ID Feature Name Description
to FREE,
neighboring
relations are
optimized
automatically
by ANR. If this
parameter is set
to
CONTROLLE
D, neighboring
relations to be
added or
removed are
reported to the
M2000 and then
subject to
manual
processing for
optimization.
GUI Value
Range:FREE(F
REE),
CONTROLLE
D(CONTROLL
ED)
Actual Value
Range:FREE,
CONTROLLE
D
Default
Value:FREE(F
REE)
Unit:None
Drx LongDRXCycle
forIRatAnr
MOD DRX
LST DRX
LBFD-002017 /
TDLBFD-0020
17
DRX Meaning:Indicat
es the long
DRX cycle for
inter-RAT
ANR. If
inter-RAT ANR
is enabled, this
parameter is
valid regardless
of whether
DRX is
enabled. If there
are multiple
inter-RAT
systems, and all
of them require inter-RAT ANR
eRAN
ANR Management Feature Parameter Description 15 Parameters
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
125
MO Parameter ID MML Command
Feature ID Feature Name Description
measurements,
it is
recommended
that this
parameter be set
to the maximum
value of the
long DRX cycle
configured for
inter-RAT ANR
measurements.
Otherwise, the
success rate for
inter-RAT ANR
measurements
may be
affected.
GUI Value
Range:SF128(1
28 subframes),
SF160(160
subframes),
SF256(256
subframes),
SF320(320
subframes),
SF512(512
subframes),
SF640(640
subframes),
SF1024(1024
subframes),
SF1280(1280
subframes),
SF2048(2048
subframes),
SF2560(2560
subframes)
Actual Value
Range:SF128,
SF160, SF256,
SF320, SF512,
SF640, SF1024,
SF1280,
SF2048,
SF2560
Default
Value:SF1280(1
280 subframes)
Unit:subframe
eRAN
ANR Management Feature Parameter Description 15 Parameters
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
126
MO Parameter ID MML Command
Feature ID Feature Name Description
ANR FastAnrCdma1x
rttPilotThd
MOD ANR
LST ANR
LOFD-002001 /
TDLOFD-0020
01
LOFD-002002
Automatic
Neighbour
Relation (ANR)
Inter-RAT ANR
Meaning:Indicat
es the pilot
strength
threshold for
fast ANR with
CDMA2000
1xRTT. If the
signal quality in
a neighboring
CDMA2000
1xRTT cell
reported by the
UE is lower
than the
threshold, the
cell is not
automatically
added as an
external cell of
the eNodeB.
GUI Value
Range:-63~0
Actual Value
Range:-31.5~0,
step:0.5
Default
Value:-30
Unit:0.5dB
ANR FastAnrCdmahr
pdPilotThd
MOD ANR
LST ANR
LOFD-002001 /
TDLOFD-0020
01
LOFD-002002
Automatic
Neighbour
Relation (ANR)
Inter-RAT ANR
Meaning:Indicat
es the pilot
strength
threshold for
fast ANR with
CDMA2000
HRPD. If the
signal quality in
a neighboring
CDMA2000
HRPD cell
reported by the
UE is lower
than the
threshold, the
cell is not
automatically
added as an
external cell of
the eNodeB.
GUI Value
eRAN
ANR Management Feature Parameter Description 15 Parameters
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
127
MO Parameter ID MML Command
Feature ID Feature Name Description
Range:-63~0
Actual Value
Range:-31.5~0,
step:0.5
Default
Value:-16
Unit:0.5dB
X2BlackWhiteL
ist
Mcc ADD
X2BLACKWHI
TELIST
RMV
X2BLACKWHI
TELIST
LST
X2BLACKWHI
TELIST
None None Meaning:Indicat
es the mobile
country code of
the neighboring
eNodeB to be
added to the list.
The value of
this parameter is
a string of three
characters, each
of which must
be a digit in the
range of 0 to 9.
GUI Value
Range:3
characters
Actual Value
Range:000~999
Default
Value:None
Unit:None
X2BlackWhiteL
ist
Mnc ADD
X2BLACKWHI
TELIST
RMV
X2BLACKWHI
TELIST
LST
X2BLACKWHI
TELIST
None None Meaning:Indicat
es the mobile
network code of
the neighboring
eNodeB to be
added to the list.
The value of
this parameter is
a string of two
or three
characters, each
of which must
be a digit in the
range of 0 to 9.
GUI Value
Range:2~3
characters
Actual Value
Range:00~99,0
eRAN
ANR Management Feature Parameter Description 15 Parameters
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
128
MO Parameter ID MML Command
Feature ID Feature Name Description
00~999
Default
Value:None
Unit:None
X2BlackWhiteL
ist
ENodeBId ADD
X2BLACKWHI
TELIST
RMV
X2BLACKWHI
TELIST
LST
X2BLACKWHI
TELIST
None None Meaning:Indicat
es the ID of the
neighboring
eNodeB to be
added to the list.
GUI Value
Range:0~10485
75
Actual Value
Range:0~10485
75
Default
Value:None
Unit:None
X2BlackWhiteL
ist
X2ListType ADD
X2BLACKWHI
TELIST
LST
X2BLACKWHI
TELIST
None None Meaning:Indicat
es whether the
X2 list is a
blacklist or
whitelist. If the
peer eNodeB is
in the X2
blacklist, the
status of the
manually
configured X2
interface
between the
local eNodeB
and this
neighboring
eNodeB is
abnormal and
this X2
interface cannot
be
automatically
set up. If the
peer eNodeB is
in the X2
whitelist, the
X2 interface
between the two
eNodeBs cannot
be automatically
eRAN
ANR Management Feature Parameter Description 15 Parameters
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
129
MO Parameter ID MML Command
Feature ID Feature Name Description
removed.
GUI Value
Range:X2_BLA
CK_LIST_TYP
E(X2 Black List
Type),
X2_WHITE_LI
ST_TYPE(X2
White List
Type)
Actual Value
Range:X2_BLA
CK_LIST_TYP
E,
X2_WHITE_LI
ST_TYPE
Default
Value:X2_BLA
CK_LIST_TYP
E(X2 Black List
Type)
Unit:None
GlobalProcSwit
ch
X2BasedUptEN
odeBCfgSwitch
MOD
GLOBALPRO
CSWITCH
LST
GLOBALPRO
CSWITCH
None None Meaning:Indicat
es whether the
eNodeB
automatically
updates the
configuration of
neighboring
cells based on
the messages
received over
the X2
interface. The
messages
include X2
SETUP
REQUEST, X2
SETUP
RESPONSE,
and ENB
CONFIGURAT
ION UPDATE.
Turn off the
switch if the
eNodeB
configuration
data on a
network is to be modified by
eRAN
ANR Management Feature Parameter Description 15 Parameters
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
130
MO Parameter ID MML Command
Feature ID Feature Name Description
using the
interlocking
modification
function on the
CME and
modifications to
the parameters
of a neighboring
eNodeB will be
updated on the
local eNodeB
through
messages over
the X2
interface. These
parameters
include
eNodeBId,
CellId,
LocalCellId,
CnOperator,
CnOperatorTa,
CellOp,
PhyCellId, and
DlEarfcn. This
prevents the
configuration
data from being
lost or abnormal
during the
automatic
update. This
switch must be
turned on if the
interlocking
modification
function on the
CME is not
used and the
eNodeB
configuration
data on a
network is to be
modified by
using the
automatic
eNodeB
configuration
update over the
X2 interface.
GUI Value
Range:OFF(Off
eRAN
ANR Management Feature Parameter Description 15 Parameters
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
131
MO Parameter ID MML Command
Feature ID Feature Name Description
), ON(On)
Actual Value
Range:OFF, ON
Default
Value:OFF(Off)
Unit:None
eRAN
ANR Management Feature Parameter Description 16 Counters
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
132
16 Counters
There are no specific counters associated with this feature.
eRAN
ANR Management Feature Parameter Description 17 Glossary
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
133
17 Glossary
For the acronyms, abbreviations, terms, and definitions, see Glossary.
eRAN
ANR Management Feature Parameter Description 18 Reference Documents
Issue 03 (2013-11-10) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
134
18 Reference Documents
This chapter lists the 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. eNodeB MO Reference
6. eNodeB MML Command Reference
7. eNodeB Alarm Reference
8. DRX and Signaling Control Feature Parameter Description
9. Mobility Management in Connected Mode Feature Parameter Description
10. S1X2OM Channel Management Feature Parameter Description
11. eNodeB Performance Counter Reference
12. RAN Sharing Feature Parameter Description