Automatic Neighbor Relation For LTE

No further reproduction or networking is permitted. Distributed by Nokia.
Copyrighted material licensed to adil.nabi@bt.com on 13-03-2023.

Single RAN Features, Rel. SRAN
22R2, Operating Documentation,
Issue 05
Automatic Neighbor Relation for

LTE
DN280034679
Issue 02
Approved on 2022-04-07
© 2022 Nokia. Nokia Condential Information
Use subject to agreed restrictions on disclosure and use.

Automatic Neighbor Relation for LTE

Nokia is committed to diversity and inclusion. We are continuously reviewing our customer
documentation and consulting with standards bodies to ensure that terminology is inclusive
and aligned with the industry. Our future customer documentation will be updated
accordingly.
This document includes Nokia proprietary and condential information, which may not be
distributed or disclosed to any third parties without the prior written consent of Nokia. This
document is intended for use by Nokia’s customers (“You”/”Your”) in connection with a
product purchased or licensed from any company within Nokia Group of Companies. Use this
document as agreed. You agree to notify Nokia of any errors you may nd in this document;
however, should you elect to use this document for any purpose(s) for which it is not
intended, You understand and warrant that any determinations You may make or actions
You may take will be based upon Your independent judgment and analysis of the content of
this document.
Nokia reserves the right to make changes to this document without notice. At all times, the
controlling version is the one available on Nokia’s site.
No part of this document may be modied.
NO WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO
ANY WARRANTY OF AVAILABILITY, ACCURACY, RELIABILITY, TITLE, NON-INFRINGEMENT,
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, IS MADE IN RELATION TO THE
CONTENT OF THIS DOCUMENT. IN NO EVENT WILL NOKIA BE LIABLE FOR ANY DAMAGES,
INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR
CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT,
REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA THAT MAY ARISE
FROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN IT, EVEN IN THE CASE OF
ERRORS IN OR OMISSIONS FROM THIS DOCUMENT OR ITS CONTENT.
Copyright and trademark: Nokia is a registered trademark of Nokia Corporation. Other

product names mentioned in this document may be trademarks of their respective owners.
© 2022 Nokia.
2 © 2022 Nokia. Nokia Confidential Information Issue 02


Table of Contents
Automatic neighbor relation for LTE summary of changes .................................................... 6
1 Overview and benefits of automatic neighbor relation for LTE ............................................ 7
2 Requirements for automatic neighbor relation for LTE .......................................................... 9
3 Automatic neighbor relation for LTE system impact ............................................................ 11

Automatic neighbor relation features interdependencies ........................................... 11
4 Automatic neighbor relation (ANR) overview .......................................................................... 12
5 LTE intra- and inter-frequency automatic neighbor relations ............................................ 14

5.1 Neighbor cell configuration through X2 initiated by camping UE ............................ 22
5.2 X2 link management ....................................................................................................... 22
5.3 ANR modes ....................................................................................................................... 25
5.4 UE measurements and detection of unknown cells ................................................... 27
5.5 Limiting and blacklisting neighbors .............................................................................. 29
6 Autonomous removal of LTE neighbors .................................................................................. 31

6.1 LTE NRs revalidation ....................................................................................................... 33
7 Reference data related to automatic neighbor relation ....................................................... 36

7.1 Faults and alarms related to automatic neighbor relation for LTE ......................... 36
7.2 Measurements, counters, and KPIs related to automatic neighbor relation for LTE
............................................................................................................................................ 37
7.3 Parameters related to automatic neighbor relation for LTE .................................... 38
8 Activating and deactivating automatic neighbor relation for LTE ....................................... 43

8.1 Activating automatic neighbor relation ....................................................................... 43
8.2 Activating fully UE-based automatic neighbor relation ............................................. 44
8.3 Activating UE-based automatic neighbor relation for inter-frequency LTE ........... 45
8.4 Activating autonomous LTE neighbor removal ........................................................... 47
8.5 Deactivating automatic neighbor relation ................................................................... 49
8.6 Deactivating fully UE-based automatic neighbor relation ........................................ 50
8.7 Deactivating UE-based automatic neighbor relation for inter-frequency LTE ...... 51
8.8 Deactivating autonomous LTE neighbor removal ...................................................... 52
Issue 02. © 2022 Nokia. Nokia Confidential Information 3


List of Figures
Figure 1 ANR principle ................................................................................................................ 13
Figure 2 Automatic establishment of an inter-frequency NR .............................................. 17
Figure 3 Intra-BTS neighbor cells at different frequencies and fully overlap .................... 21
Figure 4 Inter-BTS neighbor cells at different frequency bands, of different type and fully
overlap ............................................................................................................................. 21
Figure 5 ANR Intra-LTE, Inter-frequency UE Based neighbor discovery: RF part .............. 28
Figure 6 PCI confusion ............................................................................................................... 33


List of Tables
Table 1 Automatic neighbor relation for LTE availability ........................................................ 9
Table 2 Resulting ANR method toward target frequency F2 ............................................... 20
Table 3 Parameters related to active/passive ANR ............................................................... 26
Table 4 BTS faults introduced by automatic neighbor relation for LTE features in SRAN21A
........................................................................................................................................... 36
Table 5 BTS faults related to automatic neighbor relation for LTE .................................... 36
Table 6 Counters introduced by automatic neighbor relation for LTE features in SRAN21A
........................................................................................................................................... 37
Table 7 Key performance indicators introduced by automatic neighbor relation for LTE
features in SRAN21A ...................................................................................................... 38
Table 8 Key performance indicators related to automatic neighbor relation for LTE
features ........................................................................................................................... 38
Table 9 Parameters introduced by automatic neighbor relation features for LTE
........................................................................................................................................... 38
Table 10 Parameters related to automatic neighbor relation for LTE ............................... 42


Automatic neighbor relation for LTE summary of changes
Find list of changes between document issues. You can navigate to respective changed
topics.
Changes between issues 01 (2021-07-30) and 02 (2022-04-07, 21A)
Deactivating fully UE-based automatic neighbor relation
A note has been added.
Deactivating UE-based automatic neighbor relation for inter-frequency LTE
A note has been added.


1. Overview and benefits of automatic neighbor relation
for LTE
In the LTE networks, the UE mobility relies on the information given by neighbor cell, such
as their availability and configuration. An automatic mechanism is implemented to
discover the unknown cells. The main benefit introduced with the automatic neighbor
relation mechanism is the simplified site management, as the unknown cells or site are
automatically detected and configured.
LTE539: Central ANR

The LTE539: Central ANR feature is the first implementation of the automated neighbor
relation (ANR) for LTE cells with the same frequency, and was later substituted by newer
features.
LTE724: LTE Automatic Neighbor Cell Configuration

The LTE724: LTE Automatic Neighbor Cell Configuration feature supported manual
configuration of the LTE neighbors for all cells of the target and source BTSs, and was later
substituted by newer features.
LTE492: ANR
The LTE492: Automatic Neighbor Relation (ANR) feature is a basic feature for ANR detection.
With the LTE492 feature, NetAct resolves IP addresses of neighbour BTS based on physical
cell ID (PCI). The feature is based on mobility measurements activated for each UE. The
feature allows manual neighbor configuration.
LTE556: ANR Intra-LTE, Inter- Frequency-UE Based

The LTE556: ANR Intra-LTE, Inter-frequency - UE Based feature enables new neighbor
relations to be established between LTE cells with different frequencies.
LTE771: Optimization of Intra-LTE Neighbor Relations

The LTE771: Optimization of Intra-LTE Neighbor Relations feature increases the quality of
service for the end user by maintaining it while performing mobility procedures. It was


replaced with EdenNet implementation.
For more information about EdenNet for LTE ANR, see EdenNet/EdenNet Operating
Documentation/Module Guides/LTE Automatic Neighbor Relations Guide.
LTE782: ANR Fully UE Based

The LTE782: ANR Fully UE Based feature covers automatic neighbor relation configuration
(UE-based ANR) between LTE cells working on the same frequencies.
LTE1685: Neighbor Relation Robustness

The LTE1685: Neighbor Relation Robustness feature enhances the maintenance of the LTE
neighbor relations with an autonomous cleanup of unused LTE neighbors, PCI re-validation,
and warning messages to help adjust configuration conflicts.
LTE1821: Neighbor Detection Optimization for HetNet

The LTE1821: Neighbor Detection Optimization for HetNet feature enhances the LTE neighbor
detection in a multi-layer heterogeneous network (HetNet) environment. It calculates and
uses estimated cell-specific ranges for the source cell and the potential target cells. The
feature provides a precise detection of neighbor cells in a multi-layer HetNet environment,
and it was replaced with EdenNet implementation.
LTE1823: Neighbor Prioritization Optimization for HetNet

The LTE1823: Neighbor Prioritization Optimization for HetNet feature enhances LTE neighbor
detection in multi-layer HetNet environment. It introduces a new algorithm that optimizes
the priority set for the neighbor cells generated during pre-planning or during auto-
configuration, and it was replaced with EdenNet implementation.


2. Requirements for automatic neighbor relation for LTE
Hardware, software, and license requirements
Equipment preconditions
Table 1: Automatic neighbor relation for LTE availability
Feature Available since
LTE492: ANR RL20/RL15TD
LTE782: ANR Fully UE Based RL30/RL25TD
LTE556: ANR Intra-LTE, Inter-Frequency-UE based RL60/RL45TD
LTE1685: Neighbor Relation Robustness RL70/RL55TD
For 5G supported hardware and software, see Reference Documentation/Compatibility matrix

and Operating Documentation/5G Features/List of Features and Documents in 5G Operating
Documentation.
For SRAN supported hardware and software, see Operating Documentation/Single RAN
Features/List of Features and Documents in Single RAN Operating Documentation.
For ASiR System 5G supported hardware and software, see Operating

Documentation/AirScale Indoor Radio System 5G/ASiR System 5G Features/List of Features
Supported in ASiR System 5G in AirScale Indoor Radio System 5G Operating Documentation.
For ASiR System supported hardware and software, see Operating Documentation/AirScale
Indoor Radio System/ASiR System Features/List of Features in ASiR System in AirScale Indoor
Radio System Operating Documentation.
Sales information
For 5G licenses information, see Operating Documentation/Single RAN System/Licenses.
For SRAN licenses information, see Operating Documentation/Single RAN System/Licenses.
For ASiR System 5G licenses information, see Operating Documentation/AirScale Indoor Radio
System 5G/ASiR System 5G Features/List of Features Supported in ASiR System 5G.
For ASiR System licenses information, see Operating Documentation/AirScale Indoor Radio


System/ASiR System Features/List of Features in ASiR System.


3. Automatic neighbor relation for LTE system impact
The automatic neighbor relation for LTE has no impact on interfaces, network
management tools, and system performance and capacity.
Automatic neighbor relation features interdependencies

List of correlations between automatic neighbor relation features and other features
The interactions are grouped by the specific automatic neighbor relation for LTE features.
The LTE55: Inter-frequency HO feature must be activated before activating the LTE556: ANR
Intra-LTE, Inter-frequency - UE based feature.
The LTE782: ANR Fully UE Based feature impacts theLTE42: Support of DRX in RRC
Connected Mode feature.
The LTE782 feature uses the DRX functionalities provided by the LTE42 feature. DRX needs
to be set up in the UE in order to allow Cell Global Identity (CGI) measurements.


4. Automatic neighbor relation (ANR) overview
The LTE neighbor cells are discovered and added automatically or manually, depending on
the ANR features configuration.
In order to perform handover, the BTS needs configuration information about the neighbor
cells from the neighbor BTS. The neighbor cells are reported in measurement reports from
UE as potential target cells for mobility procedures. Without this functionality, the
information about the neighbor cells is kept and maintained through BTS configuration,
requiring manual planning, maintenance, and subsequently leading to possible human errors
from the process.
The following information must be configured for each neighbor LTE cell:
Cell Global Identity (CGI)
Public land mobile network identity (PLMN ID)
Transport Admission Control (TAC)
Physical cell ID (PCI)
Downlink E-UTRA Absolute Radio Frequency Channel Number (EARFCN)
The 3GPP solution for ANR is to learn the neighbor cell configuration information using the
UE, so that you don't have to manually pre-configure the information of LTE neighbor cells
in the BTS.
The ANR function automates and optimizes that handover process with real-time
information exchange between the source cell and target cell.
The prerequisites are as follows:

You have to ensure that the LTE cell blacklists don't contain the PCIs of the neighbor cell.
The neighboring BTSs have IP connectivity to establish an X2 link.
All the neighbor BTSs have the LTE492: ANR feature or the LTE782: ANR Fully UE Based
feature activated.


Figure 1: ANR principle


5. LTE intra- and inter-frequency automatic neighbor
relations
The LTE492: Automatic Neighbor Relation (ANR) feature is applicable to both intra- and
inter-frequency scenario. The LTE782: ANR Fully UE Based feature allows automatic
establishment of new neighbor relations (NRs) between LTE cells with the same
frequencies, while the LTE556: ANR Intra-LTE Inter-frequency UE Based feature allows
this mechanism between LTE cells with different frequencies. NRs are evaluated and
created based on the information obtained only from UE measurements.
During the operation of the BTS, the mobility measurements are activated for each UE. If
the UE measurement reports show physical cell ID (PCI) values without existing
configuration, the BTS searches the PCI values in the mapping table.
The target BTS supports the LTE492 feature, and accepts incoming X2 link setup from the
other BTS. The feature allows also manual neighbor configuration.
The neighbor cell configuration through X2 is initiated by the UE-measurements of a

connected UE. Only the connected UE reports this measurements during mobility
procedure.
The UE reports all detected/strongest cells above a given threshold. Therefore, it can report
strong cells whose PCI is currently not yet known to the BTS. The BTS checks in the A3/A5
measurement when there are more PCI reported, if the unknown PCI is the only target to be
selected. In this case, the BTS maps the control plane (C-plane) IP address of the relevant
neighbor BTS, hosting the unknown cell. The BTS uses only the strongest unknown PCI for
this and only if there is no other known PCI that could be selected for handover preparation.
If the BTS successfully maps the IP address, the X2 signalling connectivity is set up, and an
IPsec tunnel that is used for S1 traffic is also used for the X2 traffic as configured, if network
domain security is applied. The X2 user plane (X2-U) interface is set up during the first
handover event between a pair of BTSs, including IPsec tunnel over S1 interface, if network
domain security is applied.
Note:
The ANR supports IPsec star topology configurations where an IPsec tunnel that is
used for S1 traffic is also used for X2 traffic as configured.
IPsec meshed topology configurations aren't supported.


The resolution of PCI to IP address is done by means of a PCI/RF/IP address mapping table
stored at the BTS.
The PCI/RF/IP address mapping table provides a mapping of PCI assigned to a neighbor cell.
The table includes information about relation of the cell PCI identification at a certain RF-
carrier to the C-plane IP address of the Flexi BTS serving that cell.
Note:
The PCI values of neighbor cells are unique for the given center frequency (RF-carrier)
and the geo-location area of the cells.
The LTE492 feature supports finding the neighbor on the same (common) center frequency
as the actual cell. It's known that all cells are assigned to the same center frequency.
Therefore, in the PCI/IP address table, all PCI values usually have the same RF-carrier.
The selection inside the NetAct is based on the geo-data and collects in a typical two center
frequency network the potential neighbor cells from either center frequency. This allows you
to assign the cells later on to different center frequencies without updating the BTS PCI/IP
address table.
Note:
It's not recommended to use the LTE492 feature in a network deployment with three
center frequencies and/or with huge difference in the cell sizes on each center
frequency, for example for 800 and 2600 MHz bands, as in those cases some RF
carriers can have less potential candidates prepared than required.
The neighbor relation and the neighbor cell information is persistently stored. This allows S1
handover, if X2 link isn't running. The neighbor cell relation is only generated if the PCI is
reported by a UE connected to this cell. The cell-specific relation allows to detect the
relevant neighbor cells, while all known cells at the BTS level are available for handover.
The new neighbors found by the LTE492 feature are created as LNADJ instance and set the
parameter LNADJ C-Plane IP address control (cPlaneIpAddrCtrl) to
enbControled and all neighbor data from the X2 link among them LNADJL Physical
cell ID of cell served by neighbor eNB (phyCellId). After each X2 link drop
one of the persistent configured phyCellId is used to map the IP address again. This
behavior requires to have an up-to-date IP address/PCI mapping table. The PCI update at
the neighbor cell is informed to the neighbors connected through X2, but the PCI/IP address
table isn't updated.


The LTE782 feature covers LTE intra-frequency automatic neighbor relation configuration
(UE-based ANR). If the BTS gets a measurement report from a UE with a PCI that it doesn't
recognize, it commands the UE to report the E-UTRAN Cell Global Identifier (ECGI) associated
with the PCI. The BTS uses the ECGI and PCI to obtain the X2 C-plane (X2-C) IP address of
the newly discovered LTE neighboring cell through the S1 interface, using the self-
organizing network (SON) information exchange procedure.
Once the X2-C IP address is obtained, the BTS attempts to establish an X2 connection with
the newly discovered neighbor. The new neighbor information is persistently stored at the
BTS for further use by the mobility management subsystem at the BTS.
Note:
If the X2-C IP address isn't obtained through the S1 interface, the BTS still attempts
handovers to the unknown neighbor through S1 handovers.
For all cells on the BTS, the persistent neighboring cell information allows the S1 handover,
while the X2 handover is preferred if the X2 link is active.
Whenever one camping UE sees one of these known neighboring cells and this neighbor is
selected as handover target then, within this cell, a neighboring cell relation is established.
The LTE782: ANR Fully UE Based feature doesn't require additional support from the
NetAct. However, the BTS updates the NetAct with the newly discovered neighbor
information.
The LTE492 and LTE782 features can run in parallel. To determine the configuration
information of unknown UE reported cell, the BTS can apply either the LTE492 or LTE782
procedure.
If a new PCI on a certain RF is found and the PCI/EARFCN/IP address mapping table contains
the mapping information for this PCI and RF, then the information in the PCI/EARFCN/IP
address mapping table is applied. If the new PCI and RF isn't included in the PCI/RF/IP
address mapping table, then the mechanism from the LTE782 feature is applied to detect
the required information.
With the LTE556: ANR Intra-LTE Inter-frequency UE Based feature, the BTS automatically
establishes the dedicated LTE inter-frequency neighbor relations (NRs) for its cells. The
feature considers that geographically-separated BTS cells can detect LTE inter-frequency
neighbors that have different CGI with the same physical identity (PCI and EARFCN). The cells
of distributed sites are geographically separated, so there are no conflicting neighbors. You
only configure the carrier frequencies (and other parameters if needed) that are used by the
BTS for the automatic NR detection. The BTS informs you when new NRs are automatically


created.
A mechanism is implemented to discover unknown cells based on UE measurements. With

this mechanism, a complete pre-planning of the neighbor cell configurations isn't needed
for the automatic configuration and update of LTE inter-frequency neighbor cells.
The LTE492 feature is needed, if inter-frequency LTE neighbor cells need to be resolved.
The operator configures the required inter-frequency measurement configuration for the
known center frequency. This measurement configuration supports neighbor finding as well
as the preparation for the handover to these neighbors.
The LTE556: ANR Intra-LTE Inter-frequency UE Based feature enables the BTS to
automatically establish its NRs at LTE inter-carrier frequencies with the support of UE
measurements.
You need to configure, using ANR profiles, the LTE carrier frequencies that are used for
automatic neighbor cell detection. The BTS then activates, for these carrier frequencies, the
relevant measurements at the connected UEs. At the purpose, inter-frequency-specific ANR
measurements are required.
Before adding a UE-resolved LTE inter-frequency neighbor to the relevant BTS cell, at least
one handover preparation must be attempted to that cell from the respective BTS cell.
The BTS informs you through Network Element Manager and the NetAct when a new NR has
to be modeled.
The Automatic establishment of an inter-frequency NR figure shows the affected network

entities and interfaces, for a successful case of NR establishment according to the LTE556:
ANR Intra-LTE Inter-frequency UE Based feature.
Figure 2: Automatic establishment of an inter-frequency NR


LTE ANR method towards target frequency dependent on feature

configuration
The LTE556: ANR Intra-LTE Inter-frequency UE Based feature is enabled by setting the
LNBTS Activate UE-based ANR for intra-Frequency LTE
(actUeBasedAnrIntraFreqLte) parameter to true. Also, you need create the ANR
profile and enables it for UE-based ANR for the target carrier frequency.


Note:
The BTS establishes an enbControlled X2 link only if at least one of the features
LTE782: ANR Fully UE based or LTE492: ANR is activated (that is, either the LNBTS
actUeBasedAnrIntraFreqLte or LNBTS Activate ANR support for LTE
with OAM extension (anrOmExtEnable) parameter is set to true). Setting the
ANR Maximum number of eNB-controlled incoming X2-links
(maxNumX2LinksIn) and the ANR Maximum number of eNB-controlled
outgoing X2-links (maxNumX2LinksOut) parameters values to 0 is the only way
to disable accepting/establishing of the enbControlled X2 links.
The Resulting ANR method toward target frequency F2 table shows the ANR method
towards a target frequency dependent on the cell frequency and the feature configuration
(feature activation parameter, ANR profile configuration).


Table 2: Resulting ANR method toward target frequency F2
Inter-frequency Activated feature(s) No dedicated ANR Dedicated ANR

profile for F2 profile for F2
Cell Target LTE492: LTE782: LTE556: Default Default UE- UE-

frequen frequen ANR ANR ANR profile profile based based
cy cy Fully UE Intra- UE- UE- ANR ANR
Based LTE, based based deactiv activate
Inter- ANR ANR ated d
frequen deactiv activate
cy - UE ated d
based
F1 F2 – – – – – – –
F1 F2 – – X – LTE556 – LTE556
F1 F2 – X – – – – –
F1 F2 – X X – LTE556 – LTE556
F1 F2 X – – LTE492 LTE492 LTE492 LTE492
F1 F2 X – X LTE492 LTE556 LTE492 LTE556
F1 F2 X X – LTE492 LTE492 LTE492 LTE492
F1 F2 X X X LTE492 LTE556 LTE492 LTE556
The LTE556: ANR Intra-LTE Inter-frequency UE Based feature supports the following
scenarios:
The establishment of NRs between the cells of one BTS operating at different carrier
frequencies
The carrier frequencies belonging to different or the same frequency bands
The cells at different carrier frequencies fully/partially overlap
The carrier frequencies can be used paired for providing carrier aggregation (CA)


Figure 3: Intra-BTS neighbor cells at different frequencies and fully overlap
The establishment of NRs between cells of different BTSs operating at different carrier
frequencies
The carrier frequencies of different BTSs belonging to different or the same frequency
bands
The inter-frequency cells of different BTSs fully/partially overlap
The inter-frequency cells of different BTSs are of the same/different types (for
example, macro and pico)
Figure 4: Inter-BTS neighbor cells at different frequency bands, of different type and fully
overlap


5.1 Neighbor cell configuration through X2 initiated by
camping UE
The initiation of the X2 connectivity between the UE and neighbor cell begins with the UE
reporting detection of the strongest cells above a given threshold.
The UE reports strong cells whose physical cell IDs (PCIs) are currently not known to the BTS.
In this case, the BTS can send a measurement request to the UE to discover and report the
E-UTRAN Cell Global Identifier (ECGI) for the previously reported unknown PCI. After the ECGI
resolution, the configuration of neighbor cell and neighbor relation (NR) is stored. The cell is
available for S1 handover.
If there is no X2-link available and the X2-link establishment isn't forbidden by the operator
(through X2 neighbor blacklisting), the BTS retrieves the IP address serving the resolved
neighbor cell and sets up the X2 connectivity. The X2 connectivity is set up including
establishment of the IPsec layer if the network domain security is applied followed by the
Stream Control Transmission Protocol (SCTP) connection setup.
Note:
The BTS can't establish an X2 link when it has already set up maximum number of X2
connections or when the target BTS is in the operator blacklist for X2 link connection
(but not for S1)
If the maximum number of the X2 links is reached, then the link can’t be established
and needs to be rejected through the SCTP abort.
On the X2 application layer, the BTS exchanges a list of served cells and subsequent
configuration parameters with the new neighbor. The exchanged cell information covers all
served cells of a site and is stored in the configuration databases of both sites.
When the new neighbors are successfully included into the local configuration data, the BTS
sends a configuration change notification to the NetAct to inform you about the new cell
configurations.
5.2 X2 link management

The automatic neighbor relation (ANR) features allow to re-establish the X2 connectivity
with the LTE neighboring cell configuration data stored at the BTS.
According to the activated ANR features, the X2 link can be re-established after each link


drop based on:
oamControlled: the IP address
enbControlled and the LTE492: Automatic Neighbor Relation (ANR) feature is
activated: the PCI/IP address table with any physical cell ID (PCI) of a child LNADJ object
enbControlled and the LTE782: ANR Fully UE Based feature activated: the S1-MME
interface based IP address resolution from global BTS ID. In case LTE492: Automatic
Neighbor Relation (ANR) is also activated, the BTS first tries to check the PCI/IP address
table.
Two different types of X2 links are distinguished using the LNADJ C-Plane IP address
control (cPlaneIpAddrCtrl) parameter:
oamControlled X2 link. The BTS establishes the X2-link using the IP address provided
using the plan file (no ANR mechanisms to determine IP address are used by the BTS).
enbControlled X2 link. The ANR mechanisms to establish and maintain the X2 link are
applied by the BTS (this includes the retrieval of the IP address for X2 link establishment).
The modification of the X2 link type (cPlaneIpAddrCtrl) using plan file is allowed and the
new LNADJ X2 link status (x2LinkStatus) read-only parameter provides information
whether the link is available or unavailable. NetAct and Network Element Manager are
informed about any change of X2 link configuration and status information.
Nokia BTS ANR functions rely on the fact that other-vendor neighbor BTSs inform the BTS
during X2 setup about all its served cells, especially about all cells that are On air. Non-
compliance of other-vendor neighbor BTSs on this can considerably impact ANR functions in
the BTS.
oamControlled
The oamControlled X2 links have the following basic properties:
The IP address to be used for the establishment of the oamControlled X2 link is
provided by the operator in the LNADJ object instance. It's the responsibility of the
operator to cater for correct configuration of the IP address of the oamControlled X2
link.
The BTS automatically triggers the establishment of the oamControlled X2 link
configured by the operator (for example if startup of the BTS occurs). No further
conditions are checked by the BTS.
Establishment of the oamControlled X2 link has priority over establishment of the
enbControlled X2 link.
If the establishment of the oamControlled X2 link fails, fault 6203 Transport
layer connection failure in X2 interface is raised by the BTS.


If the establishment of new link fails isn't possible because the maximum limit of links is
reached, fault 6265 Maximum number of neighbor eNBs/cells exceeded is
raised by the BTS.
To avoid inconsistencies regarding the establishment/re-establishment behavior, it's

recommended to configure the same X2 link type at both sides of the X2 link (that is if the
X2 link is configured as oamControlled in BTS, then, it's also configured as
oamControlled in the peer BTS).
enbControlled
The enbControlled X2 links have the following basic properties:
All X2 links that are automatically established by the ANR functions are labelled as the
enbControlled X2 links. The activation of at least one of the ANR features (either
LTE492: Automatic Neighbor Relation (ANR) or LTE782: ANR Fully UE Based) is a pre-
condition for the establishment of the enbControlled X2 link.
The ANR functions of the BTS trigger the automatic establishment of the
enbControlled X2 link, if the BTS detects that handover procedures to cells of the
neighbor BTS have to be performed.
The IP-address needed for the X2 link establishment is automatically determined by the
BTS
Establishment of the enbControlled X2 link to some neighbor BTS can be forbidden by
the operator through X2 link blacklisting.
If the establishment of the enbControlled X2 link fails, no fault is raised by the BTS.
If the establishment of new link fails isn't possible because the maximum limit of links is
reached, fault 6265 Maximum number of neighbor eNBs/cells exceeded is
raised by the BTS.
Regarding the re-establishment of enbControlled X2 links, the BTS behaves as described

in Outgoing enbControlled X2 link (establishment triggered by the BTS) and Incoming
enbControlled X2 link (establishment triggered by neighbor BTS).
Outgoing enbControlled X2 link (establishment triggered by the BTS)

The BTS triggers (re-)establishment of the enbControlled X2 link if all of the following
conditions are met:
The BTS has seen that cells of the neighbor BTS are necessary as targets for handover (in
this case, the LNREL/LNADJL object pairs are available associated with the neighbor
BTS).


The operator didn't forbidden the establishment of the enbControlled X2 link through
X2 link blacklisting.
The number of X2 links is still smaller than the ANR Maximum number of eNB-
controlled outgoing X2-links (maxNumX2LinksOut) parameter.
The maximum number of X2 links, that can be established by the BTS, isn't reached yet.
Incoming enbControlled X2 link (establishment triggered by neighbor BTS)

The BTS accepts the establishment request of the enbControlled X2 from the neighbor
BTS if all of the following conditions are met:
The operator didn't forbidden the establishment of the enbControlled X2 link through
X2 link blacklisting.
The number of X2 links is still smaller than the ANR Maximum number of eNB-
controlled incoming X2-links (maxNumX2LinksIn) parameter.
The maximum number of X2 links that can be established by the BTS is not reached yet.
Note:
The BTS attempts to retrieve IP-address through S1 interface, if the LTE492:

Automatic Neighbor Relation feature is deactivated, or if the IP-address cannot be
found in the PCI/IP address mapping table.
The LTE492: Automatic Neighbor Relation and the LTE782: ANR Fully UE Based features can
be activated concurrently in the BTS. In this case, to resolve the IP address, the mapping
table has precedence before the mobility management entity (MME) look-up. In case of X2
link drop, the re-connection of the X2 link for enbControled IP address is resolved using
the mapping table first. If no suitable PCI value is found, then the MME procedure is applied.
Depending on PCI or IP address changes, it's possible that a different BTS is finally selected
as neighbor. A work around is to set the IP address to oamControled, if the IP address is
still the same, see if the BTS sets up the X2 link correctly, and then change to
enbControled again. This can help updating the PCI values in LNADJL so that there is a
valid resolution next time.
5.3 ANR modes

The automatic neighbor relation (ANR) mechanisms allow the BTS to operate in active
ANR or passive ANR modes based on performance measurements.


To reduce the probability of call drops, the BTS detects and configures any unknown
neighbor cell as early as possible and not at the time when the first handover, to a newly
detected cell, is triggered. This kind of operational mode of ANR is further referred to as
active ANR.
Active ANR
If active ANR handling is started, the BTS pro-actively scans for unknown intra-frequency
LTE cells.
The operator can reduce the number of unknown neighbor cells detected through active
ANR mode by setting a high value for the ANRPRL ANR power level threshold for
neighbor cells (anrThresRSRPNbCell) threshold parameter defined in the ANR
profile.
Passive ANR
If no unknown cells need to be detected anymore, ANR operates as a background task. For
example, the BTS doesn't configure ANR-specific measurements, but uses normal
measurement reports (as received for handover) for the detection of unknown cells.
Table 3: Parameters related to active/passive ANR
MO and full name Parameter Related to Active/Passive ANR
ANRPRL ANR power level anrThresRSR Active ANR

threshold for neighbor PNbCell
cells
ANRPRL ANR power level anrThresRSR Passive ANR

threshold for mobility PNbCellMobE
events v
ANRPRL ANR quality anrThresRSR

threshold for neighbor QNbCell Active and passive ANR
cells It determines the criterion to order UE
to derive E-UTRAN Cell Global Identifier
(ECGI) of certain unknown PCI. The
higher (towards -3 dB) the value of this
parameter, the more stringent criterion
to trigger the ECGI derivation.
After new neighbor cell relations have been successfully included into the local configuration


data, the BTS sends a configuration change notification to the NetAct to inform the
operator about the new neighbor cell configurations.
5.4 UE measurements and detection of unknown cells

The LTE BTS supports the detection of unknown cells reported in A3/A4/A5 event-based
inter-frequency measurements and inter-frequency reportStrongestCells (RSC)
periodic measurements.
The following UE measurements are used:

RSC - to actively detect unknown physical cell IDs (PCIs) at a LTE carrier frequency. To
perform this measurement, the UE generally requires the configuration of measurement
gaps. This searching method for unknown cells is named active ANR.
ReportCGI - to resolve the cell identities (Cell Global Identity (CGI), Transport Admission
Control (TAC)) of a detected unknown PCI at the indicated LTE carrier frequency. To
perform this measurement, the UE always requires the configuration of a suited
discontinuous reception (DRX) profile.
Note:
There are important interactions with DRX and the latency reaction timer that need
to be considered when using the inter-frequency automatic neighbor relation (ANR).
The UE reports CGI when the LNCEL DRX inactivity timer (drxInactivityT)
and the LNBTS Uplink improved latency reaction timer
(ilReacTimerUl) parameters are set as follows:
The drxInactivityT parameter: suggested default value is 20 ms or 10 ms.

The latency reaction timer feature must be disabled for reliable CGI measurement
results in all RF scenarios. If the ilReacTimerUl parameter is set to a value other
than zero, the ReportCGI can fail, depending on whether the UE sends ping
messages at the ANR point.
The detection of unknown cells can also be done using LTE inter-frequency mobility events
through an A3, A4, or A5 measurement report. This searching method for unknown PCIs is
passive ANR.


Figure 5: ANR Intra-LTE, Inter-frequency UE Based neighbor discovery: RF part
The detection of unknown neighbor cells happens during event-triggered inter-frequency

measurements or during periodic measurements activated by the Flexi Multiradio BTS for
ANR-capable UEs. Upon the detection of an unknown cell, Flexi Multiradio BTS tries to
resolve the corresponding ECGI. This is done by ordering ECGI measurement at the UE, if
supported by the UE, or through any other information locally available (for example, from
X2 interface).
The detection of unknown cells using reportStrongestCells measurements stops as

soon as the pre-configured maximum number of automatically created NRs is achieved.
There are two scenarios for triggering the CGI measurements:

If the Attach1 RSC measurement report fulfill reference signal received power (RSRP) is
greater than, or equal to the ANRPRL ANR power level threshold for neighbor
cells (anrThresRSRPNbCell) parameter value, the PCI/Frequency pair is added into
the PciToResolveByAnyUeInCell list.
If the Attach2 RSC measurement report fulfill reference signal received quality (RSRQ) is
greater than, or equal to the ANRPRL ANR quality threshold for neighbor
cells (anrThresRSRQNbCell) parameter value and the PCI/Frequency pair is already
in the PciToResolveByAnyUeInCell list, then CGI measurement is triggered.


Note:
Attach1 and Attach2 could be the same UE in different attach attempts.

Attach1 and Attach2 could be same UE in one attach attempt, however, in this
case RSRP and RSRQ need to fulfill both thresholds.
Attach1 and Attach2 could be different UEs in different attach attempts.
5.5 Limiting and blacklisting neighbors

The automatic neighbor relation (ANR) intra-frequency mechanism (either with the
LTE782: ANR Fully UE Based or LTE492: Automatic Neighbor Relation feature) allows to
automatically disable handover and mobility service across LTE neighbor relations based
on their performance and necessity.
Limiting the addition of new neighbors

With the automatic neighbor relation (ANR) intra-frequency mechanism (either with the
LTE782: ANR Fully UE Based or LTE492: Automatic Neighbor Relation feature) it is possible
to limit the addition of new neighbors.
For passive ANR, the addition of new neighbors is limited to the following cases:
Accept the strongest unknown physical cell ID (PCI) in A3/A5 as candidate for ANR only if
no other handover targets are available.
In addition to the existing conditions, accept unknown physical cell ID (PCI) in
reportStrongestCells (RSC) as candidate for ANR only if it's the strongest PCI
included in RSC.
If neither stronger nor any other known handover target cells for handover preparation are
available, then consider the strongest unknown PCI in A3/A5 as candidate for ANR. The
addition of neighbors is allowed only up to a maximum amount that can be specified by the
operator.
The BTS limits creation of new neighbor relations (NRs) by using the ANRPRL Neighbor
relation limit intra-frequency (nrLimitIntraFreq) and Neighbor relation
limit inter-frequency (nrLimitInterFreq) parameters. When the number of LTE
intra-/inter-frequency NRs of the BTS cell reaches the nrLimitIntraFreq and
nrLimitInterFreq parameter values, the BTS stops autonomous learning of new
neighbor cells using ANR.


Note:
If the limits for the amount of neighbor relation are already exceeded in the BTS
database, no action is triggered in the BTS.
If an unknown PCI is accepted as a candidate for ANR, then the BTS resolves the
neighbor information (using CGI measurement or X2) and stores the related
LNADJ/LNADJL objects.
Blacklisting
PCIs blacklisting:
The LTE782 feature uses PCI blacklisting for handover. The PCIs that are blacklisted for
handover are also blacklisted for intra-LTE ANR. For example, if such a PCI is received in a
measurement report from UE, this PCI is ignored by the ANR functionality in the BTS.
X2 link blacklisting:
X2 blacklisting is based on the global BTS ID. A new plan file-configured LNBTS Global
eNB id X2-link blacklist (glbNbEnbIdX2LinkBlacklist) parameter for X2
blacklisting has been introduced. Up to 64 list entries are supported. The X2 link
blacklisting applies to all BTS-controlled X2 links.
X2 blacklisting doesn't depend on ANR feature activation.
The NetAct and Network Element Manager are informed about any change of blacklisting
information.
Note:
If the glbNbEnbIdX2LinkBlacklist parameter is omitted in an X2 blacklisting

entry, then all BTSs of the set public land mobile network (PLMN) are X2-blacklisted.
This can be used for foreign public land mobile network (PLMN), that don't allow the
X2 setup.


6. Autonomous removal of LTE neighbors
The LTE1685: Neighbor Relation Robustness feature enhances the maintenance of the
LTE neighbor relations (NRs) with a mechanism for autonomous removal of unused LTE
neighbors.
Autonomous removal of unused LTE NRs

When the feature is disabled, the ANR Activate autonomous removal of LTE
neighbours (actAutoLteNeighRemoval) activation parameter is set to false and the
operator has to manually delete the neighbor objects (LNREL, LNADJ, LNADJL).
When the feature is enabled, the actAutoLteNeighRemoval activation parameter is set

to true and the BTS decides at the end of every hour if any objects need to be removed.
Note:
You can also delete the NRs manually through NetAct or Network Element Manager.
The are following methods to remove the unused LTE neighbor relations:
The removal of NRs

The BTS can autonomously remove the NR related to the LNREL object if all of the
following conditions are met:
There is no handover preparation (X2, S1, or intra-BTS) to the neighbor cell observed
for longer than the configurable time (the ANR Idle Time Threshold for LTE
Neighbour Relations (idleTimeThresLteNR parameter).
The LNREL Remove allowed (removeAllowed) parameter is set to true.
Closing the X2 links
The BTS autonomously closes an available X2 link if:
There is no incoming X2 handover for longer than the configurable time (the ANR
Idle Time Threshold for X2 links (idleTimeThresX2) parameter).
There are no NRs (LNREL objects) associated with the X2 link.
The X2 link has an enbControlled C-plane IP Address.
If the X2 link is closed, the LNADJ X2 link status (x2LinkStatus) parameter
becomes unavailable.
The removal of the neighbor BTS (LNADJ object) and the neighbor cell (LNADJL object)
information
If the BTS (BTS1) stores the configuration information for the neighbor BTS and its
served cells, the BTS1 observes the configuration information of the neighbor BTS and its


cells. The BTS1 checks if this configuration information is used for a handover. The BTS1
also checks if the incoming X2 handover requests are received on a related link. If neither
the neighbor BTS, nor any of the neighbor cells is used for longer than the configurable
waiting time, the BTS1 removes the configuration information of the neighbor BTSs and
their cells.
If no associated NRs or an X2 link is available for longer than the configurable time, the
LNADJ and the LNADJL objects are removed from the BTS database. Only the LNADJ
objects with the C-Plane IP address control (cPlaneIpAddrCtrl) parameter
set to enbControlled are considered.
Note:
To delete the LNADJ and LNADJL objects of the remote BTS, the LTE1685 feature
must be enabled in the remote BTS as well, with the same idle time parameters
(Idle Time Threshold for LTE Neighbor Relations
(idleTimeThresLteNR) and Idle Time Threshold for X2 links
(idleTimeThresX2)). Thus, the conditions of the removal are fulfilled.
Autonomous neighbor exchange

For the UE-based ANR, if the maximum number of neighbor BTSs (that is, the maximum
number of LNADJ objects) that can be stored in the BTS database is reached, the BTS
can still learn new NRs. If the maximum number of LNADJ objects is reached (128 for
FSMr2 and 256 for FSMr3) and the Cell Global Identity (CGI) measurement provides a new
neighbor BTS (LNADJ), then the BTS selects the already existing LNADJ object which
hasn't been used for the longest time. This selection is based on the outgoing X2 and S1
traffic from the BTS. After that, the BTS deletes it and its associated LNADJL/LNREL
object, and creates a new LNADJ object which holds the newly detected neighbor BTS
and neighbor cell in its database.
In this way, the old LTE neighbor is replaced with a new one. The BTS database includes
the newly detected neighbor BTS and the neighbor cell connected to this neighbor BTS.
Warning of PCI confusion

A re-validation of the NR for the physical cell ID (PCI) and frequency leads to a toggling of
the NR assigned to this PCI and frequency. The BTS concludes if these NRs can be subject to
a PCI confusion. If a PCI is suspected of confusion, as shown in the figure below, the BTS
raises a PCI warning to the operator.


Figure 6: PCI confusion
6.1 LTE NRs revalidation

To revalidate a neighbor relation (NR) through a Cell Global Identity (CGI) measurement,
the BTS starts an active automatic neighbor relation (ANR) mode (CGI measurement isn't
retrieved from the UE that requests the handover).
When the physical cell ID (PCI), CGI, Global BTS ID, or public land mobile network (PLMN) ID
values are modified, the BTS updates the new information through the CGI measurement.
The BTS can detect these changes and perform the updates accordingly by revalidating the
NR.
The NRs revalidation is triggered in the following cases:
For a certain NR, a configurable number of consecutive handover execution failures has
been observed.
The handover preparation is started for an NR, and since the last validation of the NR, the
configurable time has passed (the ANR S1 periodical revalidation wait timer
(s1PrdRevalWaitTmr) ANR timer for NRs without an associated X2 link available, and
the ANR X2 periodical revalidation wait timer (x2PrdRevalWaitTmr) ANR
timer for NRs with an associated X2 link available).
The revalidation is needed to cover the following cases:

Misleading CGI measurements
The BTS can store a wrong NR because of misleading or wrong measurements. An
incorrect CGI value can be reported in the following cases:
A malicious UE reports an incorrect CGI value.
The CGI value isn't measured correctly.
The UE located in an airplane can report the CGI of a far-distant cell (as it has free line
of sight to it), and the earth-bound UEs detect another neighbor cell using the same
PCI and frequency.


While performing an NR revalidation, the BTS checks the NR by repeating the CGI
measurement for the PCI and frequency of the neighbor BTS. When this PCI and
frequency are associated with another neighbor cell which is not stored by the BTS, the
BTS replaces the wrong NR with a correct one. As a result, the correct NR is used for a
handover.
PCI and frequency modification
If the operator modifies the PCI and frequency values of the neighbor cells, the BTS
adapts autonomously to these configuration changes, even if there is no X2 link available.
The BTS observes if a handover to the neighbor cells is successful. If not, the BTS
performs the revalidation of NRs (the BTS checks NRs through repetition of the CGI
measurement). The BTS recognizes the correct PCI values and updates the NRs. After
this, the handover is triggered using the correct NR.
If the operator modifies the PCI and frequency values and there is an X2 link available to
the neighbor BTS, the BTS is informed about configuration changes through this X2 link.
The revalidation can be helpful in the following cases:

Neighbor cell replacement
If the operator replaces one neighbor cell with another neighbor cell, using the same PCI
and frequency, the BTS adapts autonomously to this configuration change. It happens
even if there is no X2 link available.
The BTS stores the PCI and frequency of the NR and performs a handover procedure to
the NR. If the operator modified the network in such a way that the PCI and frequency are
correct for another neighbor cell, the handover procedure to the first NR isn't successful.
The BTS checks this NR through the revalidation of NR, and it recognizes that the first NR
isn't valid. The BTS replaces the first NR with a correct one, associated with the second
neighbor cell. The BTS autonomously adapts its stored NRs to the changed network
environment. The handover procedures for the PCI and frequency are triggered towards
the correct (second) neighbor cell.
The first neighbor cell, whose PCI and frequency were moved to the second cell, can be
completely removed, or it can no longer be visible as an NR of the BTS cell.
Neighbor BTS replacement
The identity of a neighbor BTS is given by the Global BTS ID value. If the operator
modifies the Global BTS ID of a neighbor BTS, the BTS perceives this as a replacement of
the neighbor BTS with another neighbor BTS.
If the operator switches one neighbor BTS off and replaces it with another neighbor BTS
that supports cells with the same PCI and frequency values as the cells of the old
neighbor BTS, the BTS autonomously adapts to this configuration change.
After the configuration change, the BTS observes that a handover to the NR isn't
successful. Next, the BTS performs the revalidation of the NR. The BTS recognizes that


the first NR isn't valid. The BTS replaces this NR with another, corrected one, which points
to the correct neighbor cell served by the second neighbor BTS. The handover
procedures for the PCI and frequency are triggered towards the correct neighbor cell,
which is indicated by the second NR.


7. Reference data related to automatic neighbor relation
List of management data related to the automatic neighbor relation features: alarms,
faults, measurements, counters, KPIs, and parameters
For reference data descriptions, see Reference Documentation/Reference document.
7.1 Faults and alarms related to automatic neighbor

relation for LTE
List of management data related to the automatic neighbor relation for LTE features:
alarms and faults
BTS faults and reported alarms
Table 4: BTS faults introduced by automatic neighbor relation for LTE features in SRAN21A
Related Fault ID Fault name Reported alarms

Feature
LTE492 6260 Automatic neighbor 7652 BASE STATION

relation failure NOTIFICATION
LTE782, 6265 Maximum number of 7652 BASE STATION

LTE1685 neighbor eNBs/cells NOTIFICATION
exceeded
LTE1685 6279 PCI confusion detected 7655 CELL NOTIFICATION
Table 5: BTS faults related to automatic neighbor relation for LTE
Related Fault ID Fault name Reported alarms

Feature
LTE1685 6274 Neighbor cell ambiguity 7655 CELL NOTIFICATION

detected


7.2 Measurements, counters, and KPIs related to
automatic neighbor relation for LTE
measurements, counters, and KPIs
Measurements and counters
Table 6: Counters introduced by automatic neighbor relation for LTE features in SRAN21A
Related Counter ID Counter name Measurement

Feature
LTE782, M8000C37 Number of successful X2 IP LTE S1AP

LTE556 address retrievals via S1
LTE782, M8000C38 Number of attempted X2 IP LTE S1AP

LTE556 address retrievals via S1
LTE782, M8008C10 Number of Report CGI LTE RRC

LTE556, Requests
LTE1685
LTE782, M8008C11 Number of successful CGI LTE RRC

LTE556, Reports
LTE1685
LTE782, M8022C0 Number of X2 Setup attempts LTE X2AP

LTE556
LTE782, M8022C1 Number of failed X2 Setup LTE X2AP

LTE556 attempts
Key performance indicators


Table 7: Key performance indicators introduced by automatic neighbor relation for LTE features
in SRAN21A
Related KPI ID KPI name

feature
LTE782 LTE_5003a E-UTRAN Data Radio Bearer Setup Success

Ratio
LTE782 LTE_5405a E-UTRAN CGI reports for E-UTRAN Success

Ratio
Table 8: Key performance indicators related to automatic neighbor relation for LTE features
Related KPI ID KPI name

feature
LTE1685 LTE_5004a E-UTRAN Radio Bearer Drop Ratio
LTE1685 LTE_5025d E-UTRAN E-RAB Drop Ratio, RAN View
LTE1685 LTE_5048b E-UTRAN HO Success Ratio, Inter eNB X2

based
7.3 Parameters related to automatic neighbor relation for

LTE
parameters
Parameters
Table 9: Parameters introduced by automatic neighbor relation features for LTE
Related Full name Abbreviated name Path

Feature
LTE492 Activate ANR anrOmExtEnable MRBTS/LNBTS

support for LTE
with OAM extension


Feature
LTE556 Activate UE-based actUeBasedAnrInte MRBTS/LNBTS

ANR for Inter- rFreqLte
frequency LTE
LTE782 Activate UE-based actUeBasedAnrIntr MRBTS/LNBTS

ANR for intra- aFreqLte
Frequency LTE
LTE782 ANR LTE intra-freq anrLTEIntraRscRep MRBTS/LNBTS

reportStrongestCell ortAmount
s reportAmount
LTE782 ANR LTE intra-freq anrLTEIntraRscRep MRBTS/LNBTS

reportStrongestCell ortInterval
s reportInterval
LTE782 Wait time for waitTimeEstCtrlX2 MRBTS/LNBTS

establishment of Lnk
eNB controlled X2
links
LTE1685 Activate autonomous actAutoLteNeighRe MRBTS/LNBTS/ANR

removal of LTE moval
neighbors
LTE1685 ANR Idle Time anrIdleTimeThresL MRBTS/LNBTS/ANR

Thresholds for LTE te
LTE1685 Idle Time Threshold idleTimeThresLteN MRBTS/LNBTS/ANR/AN

for LTE Neighbor R R Idle Time Thresholds
Relations for LTE
(anrIdleTimeThresLte)
LTE1685 Idle Time Threshold idleTimeThresNbeN MRBTS/LNBTS/ANR/AN

for Neighbor eNBs B R Idle Time Thresholds
for LTE
LTE1685 Idle Time Threshold idleTimeThresNbEn MRBTS/LNBTS/ANR/AN

for Neighbor eNB bExch R Idle Time Thresholds
Exchange for LTE


Feature
LTE1685 Idle Time Threshold idleTimeThresX2 MRBTS/LNBTS/ANR/AN

for X2 links R Idle Time Thresholds
for LTE
LTE1685 Neighbor eNB nbEnbExchWaitTmr MRBTS/LNBTS/ANR/AN

Exchange Wait Timer R Idle Time Thresholds
for LTE
LTE556 ANR interfrequency anrIfTRSC MRBTS/LNBTS/ANR

RSC timer
LTE1685 Consecutive consecHoFailThres MRBTS/LNBTS/ANR

handover execution
failure re-
validation TH
LTE782 Global eNB id X2- glbNbEnbIdX2LinkB MRBTS/LNBTS/ANR

link blacklist lacklist
LTE556 Maximum number of maxNumX2LinksIn MRBTS/LNBTS/ANR

eNB-controlled
incoming X2-links
LTE556 Maximum number of maxNumX2LinksOut MRBTS/LNBTS/ANR

eNB-controlled
outgoing X2-links
LTE782 Minimum not minNotActivatedUt MRBTS/LNBTS/ANR

activated UTRA raRSCFS
reportStrongestCell
sForSon
LTE1685 S1 periodical s1PrdRevalWaitTmr MRBTS/LNBTS/ANR

revalidation wait
timer
LTE1685 X2 periodical x2PrdRevalWaitTmr MRBTS/LNBTS/ANR

revalidation wait
timer
LTE492, PCI-IP address pciIpAdrMap MRBTS/LNBTS/ANR

LTE782 mapping table


Feature
LTE492 PCI-IP map primary mncLength MRBTS/LNBTS/ANR/PCI

MNC length -IP address mapping
table (pciIpAdrMap)
LTE492 PCI-IP map PCI pci MRBTS/LNBTS/ANR/PCI

-IP address mapping
table (pciIpAdrMap)
LTE492 PCI-IP map downlink dlEarfcn MRBTS/LNBTS/ANR/PCI

EARFCN -IP address mapping
table (pciIpAdrMap)
LTE492 PCI-IP map eNB ID enbId MRBTS/LNBTS/ANR/PCI

-IP address mapping
table (pciIpAdrMap)
LTE492 PCI-IP map ipAdr MRBTS/LNBTS/ANR/PCI

IPv4/IPv6 address -IP address mapping
table (pciIpAdrMap)
LTE492 PCI-IP map primary mcc MRBTS/LNBTS/ANR/PCI

MCC -IP address mapping
table (pciIpAdrMap)
LTE1685 Remove allowed removeAllowed MRBTS/LNBTS/LNCEL/L

NREL


Table 10: Parameters related to automatic neighbor relation for LTE

Feature
LTE1685 ANR robustness anrRobLevel MRBTS/LNBTS/ANR

level
LTE782 ANR power level anrThresRSRPNbC MRBTS/LNBTS/ANRPRL

threshold for ell
neighbor cells
LTE556, ANR quality anrThresRSRQNbC MRBTS/LNBTS/ANRPRL

LTE782 threshold for ell
neighbor cells
LTE782 Neighbor relation nrLimitIntraFre MRBTS/LNBTS/ANRPRL

limit intra- q
frequency
LTE782 Neighbor relation nrLimitInterFre MRBTS/LNBTS/ANRPRL

limit inter- q
frequency
LTE556 Target Carrier targetCarrierFr MRBTS/LNBTS/ANRPRL

frequency eq
LTE1685 Neighbor relation nrStatus MRBTS/LNBTS/LNCEL/LNREL

status


8. Activating and deactivating automatic neighbor relation
for LTE
Instructions to activate or deactivate automatic neighbor relation for LTE in the network
8.1 Activating automatic neighbor relation

Instructions to activate the LTE492: ANR feature
Before you start
See Configuring Features with BTS Site Manager for general management tool
instructions.
See Configuring Features with Web Element Manager for general management tool
instructions.
Check if the BTS is commissioned and operational.
Check if BTS elements are detected and configured.
Modifying the settings of the parameters used in this procedure doesn't interrupt service
availability.
Procedure
1 Start the WebEM / BTS SM application.
2 Go to Parameter Editor.
Select from the available options

Go to Configuration ► Configuration Management ► Parameter
Editor.
Use the PE keyboard shortcut.
Click the Parameter Editor icon in the top menu.
3 Go to the LNBTS object.
Object path: MRBTS ► LNBTS
4 Set the Activate ANR support for LTE with OAM extension
(anrOmExtEnable) parameter to true.


8.2 Activating fully UE-based automatic neighbor relation
Instructions to activate the LTE782: ANR Fully UE Based feature
Before you start
instructions.
instructions.
availability.
Procedure

Editor.
4 Set the Activate UE-based ANR for Inter-frequency LTE

(actUeBasedAnrInterFreqLte) parameter to true.


8.3 Activating UE-based automatic neighbor relation for
inter-frequency LTE
Instructions to activate the LTE556: ANR Intra-LTE, Inter-frequency – UE Based feature
Before you start
instructions.
instructions.
availability.
The LTE782: ANR Fully UE Based feature must be activated.
Procedure

Editor.
4 Set the Enable interFrequency handover (actIfHo) parameter to enabled.
5 Create and configure the ANR object.
Object path: MRBTS ► LNBTS ► ANR
6 Go to the DRX object.
Object path: MRBTS ► LNBTS ► LNCEL ► DRX


7 Configure the DRX profile 103 (drxProfile103) structure and set the required
parameter values.
8 Create and configure the ANRPRL parameters.
Object path: MRBTS ► LNBTS ► ANRPRL
Note:
In addition to the default profile, one or more ANRPRL profiles for dedicated
target carrier frequencies can be created.
Configure the following parameters:

Activate also for UE-based ANR (actAlsoForUeBasedANR)
ANR profile for LTE identifier (anrPrLId)
ANR power level threshold for neighbor cells
(anrThresRSRPNbCell)
ANR power level threshold for mobility events
(anrThresRSRPNbCellMobEv)
ANR quality threshold for neighbor cells (anrThresRSRQNbCell)
Neighbor relation limit inter-frequency (nrLimitInterFreq)
Neighbor relation limit intra-frequency (nrLimitIntraFreq)
Target carrier frequency (targetCarrierFreq)
Note:
When the anrPrLId parameter is set to 0, the targetCarrierFreq parameter

must be empty.
When the anrPrLId parameter is different than 0, then the

targetCarrierFreq parameter must be configured.
9 Create and configure the LNHOIF object.
Object path: MRBTS ► LNBTS ► LNCEL ► LNHOIF


Note:
For each targetCarrierFreq parameter, there must be a dedicated LNHOIF

instance with the Eutra carrier info (eutraCarrierInfo) parameter
equal to the targetCarrierFreq parameter, within all LNCEL instances in
which the LTE inter-frequency ANR is active.
8.4 Activating autonomous LTE neighbor removal

Instructions to activate the LTE1685: Neighbor Relation Robustness feature
Before you start
instructions.
instructions.
availability.
To activate intra and/or inter-frequency PCI revalidation, the LTE556: ANR Intra-LTE, Inter-
frequency - UE Based and/or LTE782: ANR Fully UE Based features must be activated, that is
the LNBTS Activate UE-based ANR for Inter-frequency LTE
(actUeBasedAnrInterFreqLte) parameter is set to true.
Procedure

Editor.


3 Go to the ANR object.
4 Set the Activate autonomous removal of LTE neighbours

(actAutoLteNeighRemoval) parameter to true.
5 Set the Consecutive handover execution failure re-validation TH

(consecHoFailThres) parameter to a value greater then 0 to activate PCI
revalidation after consecutive handover execution failures.
6 Set the S1 periodical revalidation wait timer (s1PrdRevalWaitTmr)

parameter to a value greater than 0 to activate PCI periodical revalidation after the
S1 handover preparation.
7 Set the X2 periodical revalidation wait timer (x2PrdRevalWaitTmr)

parameter to a value is greater than 0 to activate PCI periodical revalidation after the
X2 handover preparation.
8 Optional, create the LNREL object and configure the mandatory parameters.
Object path: MRBTS ► LNBTS ► LNCEL ► LNREL
9 Set the Remove allowed (removeAllowed) parameter.
11 Set the ANR robustness level (anrRobLevel) parameter.
12 Configure the ANR Idle Time Thresholds for LTE (anrIdleTimeThresLte)

parameter structure:
12.1 Set the Idle Time Threshold for LTE Neighbour Relations
(idleTimeThresLteNR) parameter.
12.2 Set the Idle Time Threshold for Neighbour eNBs

(idleTimeThresNbeNB) parameter.
12.3 Set the Idle Time Threshold for Neighbour eNB Exchange
(idleTimeThresNbEnbExch) parameter.


12.4 Set the Idle Time Threshold for X2 links (idleTimeThresX2)
parameter.
12.5 Set the Neighbour eNB Exchange Wait Timer (nbEnbExchWaitTmr)

parameter.
8.5 Deactivating automatic neighbor relation

Instructions to deactivate the LTE492: ANR feature
Before you start
instructions.
instructions.
Check if all BTS elements are detected and configured.
availability.
Procedure

Editor.
4 Set the Activate ANR support for LTE with OAM extension


(anrOmExtEnable) parameter to false.
8.6 Deactivating fully UE-based automatic neighbor

relation
Instructions to deactivate the LTE782: ANR Fully UE Based feature.
Before you start
instructions.
instructions.
availability.
Note:
Deactivation of UE-based ANR doesn't impact creation of neighbor relations (LNREL)

towards cells known by the BTS. This functionality is always active and can't be
disabled.
Procedure

Editor.



(actUeBasedAnrInterFreqLte) parameter to false.
8.7 Deactivating UE-based automatic neighbor relation

for inter-frequency LTE
Instructions to deactivate the LTE556: ANR Intra-LTE, Inter-frequency - UE Based feature.
Before you start
instructions.
instructions.
availability.
Note:
Deactivation of UE-based ANR doesn't impact creation of neighbor relations (LNREL)

towards cells known by the BTS. This functionality is always active and can't be
disabled.
Procedure

Editor.



(actUeBasedAnrInterFreqLte) parameter to false.
Note:
It's also possible to deactivate ANR for a certain LTE carrier frequency or to
restrict ANR to a set of cells. Deactivating the LTE556: ANR Intra-LTE, Inter-
frequency - UE Based feature on a given carrier frequency requires that the ANR
profile has been disabled for UE-based ANR for that target carrier frequency.
8.8 Deactivating autonomous LTE neighbor removal

Instructions to deactivate the LTE1685: Neighbor Relation Robustness feature
Before you start
instructions.
instructions.
availability.
Procedure

Editor.


4 Set the Activate autonomous removal of LTE neighbours

(actAutoLteNeighRemoval) parameter to false.
5 Set the Consecutive handover execution failure re-validation TH

(consecHoFailThres) parameter to 0, to deactivate PCI revalidation after
consecutive handover execution failures.
6 Set the S1 periodical revalidation wait timer (s1PrdRevalWaitTmr)

parameter to 0min, to deactivate PCI periodical revalidation after the S1 handover
preparation.
7 Set the X2 periodical revalidation wait timer (x2PrdRevalWaitTmr)

parameter to 0min, to deactivate PCI periodical revalidation after the X2 handover
preparation.

Automatic Neighbor Relation For LTE

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Automatic Neighbor Relation For LTE

Uploaded by

Copyright:

Available Formats

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to adil.nabi@bt.com on 13-03-2023.