For internal use only!!!

RL30/RL25TD Network Engineering Information

ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782)

Krystian Krysmalski
Network Engineering
NWS LTE RA NetEng GSM & LTE Migration
November 2011

Please always use the latest version of the materials that can be found under the link:
https://sharenet-ims.inside.nokiasiemensnetworks.com/Open/432955256

For internal use only

1 © Nokia Siemens Networks ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782) / Network Engineering
ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782)

Revision History

Author: Krystian Krysmalski

Issue
Date of Issue Reason for Update
Number
0.1 20.06.2011 1st draft version – for NetEng internal review
0.2 05.10.2011 NetEng internal review completed; ready for external review
1.0 07.11.2011 External review comments incorporated

1.1 18.01.2012 PKDB link added

1.2 10.02.2012 Update acc. to CRL634; update of mapping rule for RSRQ threshold

1.3 17.02.2012 PKDB link updated

1.4 04.04.2012 Comment on LTE570 added; further updates acc. to CRL634;

1.5 15.02.2013 Update acc. to CRL678 (RL40)

For internal use only

2 © Nokia Siemens Networks ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782) / Network Engineering
ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782)

Open items

Item
Open item description Status/Comments
Number

For internal use only

3 © Nokia Siemens Networks ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782) / Network Engineering
ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782)

Contents
 Introduction
Motivation & Feature Overview
 Features Details
Functionality & eNB Implementation
 Configuration Aspects
Parameters & O&M
 Expected Benefits
Gains & Performance Aspects Analysis
 Dimensioning Aspects
Impact on Capacity & Link Budget
Modeling in Dimensioning Tools
 Application Aspects
Use Cases & Application Scenarios
 Performance Measurement Aspects
Feature Monitoring (Counters & KPIs)

For internal use only

4 © Nokia Siemens Networks ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782) / Network Engineering
ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782)

Contents

 Introduction
 Features Details
 Configuration Aspects
 Expected Benefits
 Dimensioning Aspects
 Application Aspects
 Performance Measurement Aspects

For internal use only

5 © Nokia Siemens Networks ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782) / Network Engineering
ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782)
Introduction – before RL30/RL25TD (1/4)
 LTE Automatic Neighbor Cell Configuration (LTE724)
 neighbour site and cell relations are created
automatically upon start-up of Flexi Multiradio
BTS
 all necessary neighbour site (MOC LNADJ) and
neighbour cells (MOC LNADJL) information is
derived and updated via automatically
established X2 connections
 according to 3GPP TS 36.423, upon setup of X2
connection, each eNB provides information about
its served cells to the peer eNB – bidirectional data
exchange
 the prerequisite for X2 connection setup is the
list of C-plane IP addresses of adjacent eNB
(MOC ADIPNO)
 such a list must be provided for each eNB in the
pre-planning phase
 IP@s (and eNB Ids if provided) must be
appropriately configured at both ends of X2
connection to be established – eNB does not
accept the X2 connection setup request from IP@
that is not listed in MOC ADIPNO
 Central ANR (LTE539) – NetAct feature for
For internal useautomatic
only preparation of MOC ADIPNO (see slide
6 © Nokia Siemens Networks ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782) / Network Engineering
notes)
ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782)
Introduction – before RL30/RL25TD (2/4)
 LTE Automatic Neighbor Cell Configuration (LTE724)
 for each cell, neighbour cell information list (in
MOC LNCEL) is automatically created and
populated with all cells of the parent eNB and all
cells for which the parent eNB has received
configuration information from neighbour eNB
(via X2 connection)

 cells belonging to eNB-B that is not on the IP@

list in MOC ADIPNO of eNB-A cannot be added to
the neighbouring cell information list of cells of
eNB-A
 pre-planning of IP@ lists is crucial for automatic
neighbour cell configuration with LTE724 feature
and consequently for mobility management
procedures
 cells measured and reported by UE but not being on
automatically created neighbour cell information list
are not regarded as potential targets for HO – no
mechanisms for identification of unknown UE-
reported neighbour cells

For internal use only

7 © Nokia Siemens Networks ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782) / Network Engineering
ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782)
Introduction – before RL30/RL25TD (3/4)
 ANR support for LTE with OAM extension (LTE492)
 new mechanism allowing for identification of
unknown UE-reported intra- and inter-
frequency neighbour cells
 X2 connection setup (for configuration info
retrieval) procedure is triggered by UE
measurement reports containing PCI that is
not known to eNB as a neighbour cell but is
listed in PCI/RF/IP@ mapping table
 each newly activated Flexi Multiradio BTS is
provided with table that maps Physical Cell Id
& DL EARFCN of adjacent cells to C-plane IP
address of their parent eNBs
 in RL30 the global eNB ID is added
 PCI/RF/IP@ mapping tables are generated by
NetAct based on the neighbour site relations
analysis and downloaded to BTS during auto-
configuration procedure
 based on PCI/RF/IP@ mapping table, eNB is able to determine IP@ of the adjacent
eNB hosting unknown cells
 neighbour site and neighbour cell configuration information is derived from the
For internal use only
8 adjacent
© Nokia SiemenseNodeB
Networks via X2 connection as in –case
ANR – Intra-LTE, Intra-frequency of LTE724
Fully UE based feature
(LTE782) / Network Engineering
ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782)
Introduction – before RL30/RL25TD (4/4)

 ANR support for LTE with OAM extension (LTE492)

 X2 connection setup procedure is triggered by
UE measurement reports containing PCI that is
not known to eNB as a neighbour cell but is
listed in PCI/RF/IP@ mapping table

 target eNB accepts incoming X2 connection

setup requests from a source eNB even if no IP-
address of the source eNB is configured on the
target site
 no need for configuration of IP@s at both ends of
the X2 connection as it was with LTE724

For internal use only

9 © Nokia Siemens Networks ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782) / Network Engineering
ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782)
Introduction – in RL30/RL25TD
 ANR - Intra-LTE, Intra-frequency - Fully UE based (LTE782)
 for unknown UE-reported cells (PCI
unknown to eNB) operating on the
same frequency as the serving cell,
the corresponding EUTRAN Cell
Global ID (ECGI) is derived with the
help of the UE measurements
 UE must support decoding and delivery
of ECGI on request coming from eNB
 derived ECGI is used as input to an
IP@ resolution procedure over S1 IF
 eNB retrieves, with the help of MME, C-
plane IP@ needed to setup X2
connection towards the neighbour eNB
parenting the UE-reported cells
 no need for predefined PCI-to-IP@
mapping tables

 Feature benefits
 automated detection and configuration of unknown intra-frequency neighbour cells
without operator involvement and planning efforts - no neighbour relation
information has to be provided by the operator via O&M
For internal use only
10 © Nokia Siemens Networks ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782) / Network Engineering
ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782)
Introduction – in RL30/RL25TD
 Related features in RL30/RL25TD:
 Optimization of intra-LTE neighbour relations (LTE771)
 blacklisting of underperforming intra-LTE cells from HO success rate viewpoint
 ANR InterRAT UTRAN (LTE783) and ANR InterRAT GERAN (LTE784)
 automated planning of UTRAN and GERAN neighbour relations with the help of NetAct
Optimizer and Configurator
 inter-RAT neighbour relations are to be created in NetAct based on configuration data
retrieved from 3G/2G network configuration management database
 Synchronization of InterRAT neighbours (LTE510)
 keeping inter-RAT neighbour relations up-to-date

 Plans beyond RL30/RL25TD:

 ANR – Intra-LTE, Inter-frequency – Fully UE based (LTE556)
 ANR InterRAT UTRAN – Fully UE based (LTE908)
 ANR InterRAT GERAN – Fully UE based (LTE460)
 Inter-Rat Auto Setup and Scheduled Optimization (LTE1222)
 InterRAT Neighbour Relation Optimization (LTE507)
 ANR InterRAT HRPD (LTE880)

For internal use only

11 © Nokia Siemens Networks ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782) / Network Engineering
ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782)

Contents

 Introduction
 Features Details
 Configuration Aspects
 Expected Benefits
 Dimensioning Aspects
 Application Aspects
 Performance Measurement Aspects

For internal use only

12 © Nokia Siemens Networks ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782) / Network Engineering
ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782)
Feature details
Dependency table

FD-LTE RL release eNB NetAct

Release/version RL30 LBTS3.0 OSS5.3 CD3

TD-LTE TD LTE release eNB (TD LTE) NetAct (TD LTE)

Release/version RL25TD TD-LBTS2.0 OSS5.3 CD3

HW
HW & IOT MME SAE GW UE
requirements

Release/version FSM R2, FSM R3 no

NS2.2 ANR support required
dependency

For internal use only

13 © Nokia Siemens Networks ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782) / Network Engineering
 ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782)
Feature details
Neighbour relations database structure in RL20
LNBTS (1..1) * LTE492 specific
lnBtsId, …, pciIpAdrMap (dlEarfcn, ipAdr, pci)*, … …

LNADLP (0..32):
LNADJ (0..32):

LNADJG (0..32)
LNCEL:  lnAdlpId

LNADJW (0..32)
 lnCelId  lnAdjId  adjPhyCellIdOp
LNCEL: 1…3  adjEnbId
 adjCelInfoL  adjEgciOp
 lnCelId  plmnId
eutraCelId_1 …
 adjCelInfoL …  …
eutraCelId_1 eutraCelId_130
…  phyCellId
eutraCelId_130
 eutraCelId ADIPNO (1..1):
 phyCellId
 lcrId  AdIpNoId
 eutraCelId
 adjWInfList  adjEnbIpAddressMap
 lcrId
 adjGInfList …
 adjGInfList LTE724
… LNADJL (1..3):
 adjWInfList
 lnAdjlId
…
 lnAdlpInf
 phyCellId
 adjEutraCelId
 ecgiPlmnId
…

Ecgi = plmnId + eutraCelId

eutraCelId
For internal use=only
EnbId + lcrId
14 © Nokia Siemens Networks ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782) / Network Engineering
 ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782)
Feature details
Neighbour relations database structure in RL30
LNBTS (1..1) * LTE492 specific
lnBtsId, …, actUeBasedAnrIntraFreqLte, glbNbEnbIdX2LinkBlacklist, pciIpAdrMap (dlEarfcn, ipAdr, pci, eNbId)*, … …

LNADLP (0..32):
LNCEL: LNADJ (0..64):

LNADJG (0..32)
 lnAdlpId

LNADJW (0..32)
LNCEL:  lnCelId  lnAdjId  adjPhyCellIdOp
 lnCelId 1…6  adjCelInfoL  adjEnbId  adjEgciOp
 adjCelInfoL eutraCelId_1  plmnId …
eutraCelId_1 …
 …
… eutraCelId_130
 cPlaneIpAddr
eutraCelId_130  phyCellId ADIPNO (1..1):
 phyCellId  cPlaneIpAddCtrl
 eutraCelId  AdIpNoId
 eutraCelId  x2LinkStatus
 lcrId  adjEnbIpAddressMap
 lcrId  adjWInfList …
 adjGInfList  adjGInfList
 adjWInfList  anrThresNbCell
 anrThresNbCell  drxProfile101 LNADJL (1..6):
 drxProfile101  nLTEIntraNeigh  lnAdjlId
 nLTEIntraNeigh bours  lnAdlpInf
bours …  phyCellId
…  adjEutraCelId
LNREL (0..389): LNREL (0..389):
 ecgiPlmnId
 lnRelId  lnRelId
ecgiAdjEnbId
 ecgiAdjEnbId  ecgiAdjEnbId
ecgiLcrId
 ecgiLcrId  ecgiLcrId
sourceOfData
For internal use only  ecgiPlmnId  ecgiPlmnId
validityOfData
15 …
© Nokia Siemens Networks ANR – Intra-LTE, Intra-frequency
… – Fully UE based (LTE782) / Network Engineering
 …
ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782)
Feature details
Overview (1/2)
 LTE782 introduces two new mechanisms allowing for fully automatic detection and
configuration of intra-LTE intra-frequency neighbour cell relations

 unknown cell detection

and its EUTRAN Cell
Global Id (ECGI) derivation
 if UE measurement report
(either event-triggered or
periodic) contains an
unknown intra-frequency cell
(reported Physical Cell Id is
not known to eNB), eNB
requests (if some
preconditions are fulfilled) a
UE to retrieve and report
ECGI, Tracking Area Code
(TAC) and PLMN(s) of that
cell
 derived ECGI, TAC &
PLMN(s) are used by eNB to
retrieve (via S1 IF) the X2 C-
plane IP@ of eNB hosting
considered neighbour cell

For internal use only

16 © Nokia Siemens Networks ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782) / Network Engineering
ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782)
Feature details
Overview (2/2)
 LTE782 introduces two new mechanisms allowing for fully automatic detection and
configuration of intra-LTE intra-frequency neighbour cell relations

 X2 C-plane IP@ resolution

via S1 IF
 SON Information Exchange
procedure is used to derive
X2 C-plane IP@ of eNB that is
a parent of the cell towards
which neighbour relation is to
be established
 having retrieved C-plane IP@,
eNB triggers establishment of
X2 connection for
configuration information
exchange
 upon successful retrieval of
necessary configuration
information the
corresponding neighbour cell
relation can be finally defined
and previously unknown cell
can be regarded as potential
target for intra-frequency X2
For internal use only
17 ©handover
Nokia Siemens Networks ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782) / Network Engineering
ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782)
Feature details
Detection of unknown cells (1/3)
 There are two different modes for detection of unknown cells
 passive mode – based on A3 and A5 event
triggered measurement reports
 active mode – based on
ReportStrongestCells measurements
(periodic measurements)
 UE is requested to measure and report PCI of the
strongest cells detected at the serving cell
carrier frequency
 ReportStrongestCell measurement handling
does not affect event-triggered measurements so
that handover execution is not impacted
 No ReportStrongestCells measurement are
requested if the UE has inter-frequency or inter-
RAT measurements activated
 ReportStrongestCell measurements are
requested only from UEs that indicate their ANR
capability to eNB
 RRC:UECapabilityinformation: UE-EUTRA-Capability: featureGroupIndicators:
BIT17 - Periodical measurement reporting for SON / ANR and ANR related intra-frequency
For internal use only
18 measurement reportingANR
© Nokia Siemens Networks events
– Intra-LTE, Intra-frequency – Fully UE based (LTE782) / Network Engineering
ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782)
Feature details
Detection of unknown cells (2/3)
 ANR active mode is applied in a cell as long as
 the number of consecutive measurement reports
(event triggered and ReportStrongestCells)
without unknown intra-frequency PCI has not
reached the value of maxMRnoIntraPciToResolve
(MOC LNBTS) and
 the number of defined LTE intra-frequency
neighbour relations for a cell is lower than
nLTEintraNeighbours (MOC LNCEL)
 ReportStrongestCells measurement are
controlled with the following parameters
 anrLTEIntraRscReportInterval (MOC LNBTS) –
defines regular time intervals of reports delivery
by a UE
 anrLTEIntraRscReportAmount (MOC LNBTS) –
defines the number of reports to be provided by a
UE as a result of single request
 if Periodic UE measurements (LTE570) are
activated, reportInterval (MOC LNCEL:
periodicUeMeas) and reportAmount (MOC
LNCEL:periodicUeMeas)
For internal use only
19 © Nokia Siemens Networks ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782) / Network Engineering
ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782)
Feature details
Detection of unknown cells (3/3) – ReportStrongestCells
 Measurement configuration for ReportStrongestCells
 the same measurement object as for the own serving cell
 Report configuration for ReportStrongestCells
 ReportStrongestCells measurement report

For internal use only

20 © Nokia Siemens Networks ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782) / Network Engineering
ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782)
Feature details
ECGI derivation (1/4)
 If PCI & DL-EARFCN of a cell reported (in either A3/A5 event-triggered or
ReportStrongestCells report) do not correspond to any known LTE neighbour cell (MOC
LNADJL), eNodeB classifies such a cell as a candidate for ECGI derivation
 ECGI is derived with the help of UEs
 new type of measurements has been
introduced – ReportCGI measurements
 UE may be requested to decode and report
the ECGI, TAC & PLMN(s) of LTE intra-
frequency cell reported previously within
either A3 /A5 event-triggered or
ReportStrongestCells measurement report
 to request a UE to perform ReportCGI
measurements some preconditions must be met
(see next slide)
 eNB requests a UE to report a ECGI only for
PCIs that it has previously reported
 each unknown cell needs separate
ReportCGI measurements configuration
 UE can be configured with only one ReportCGI measurements at a time
For internal use only
21 © Nokia Siemens Networks ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782) / Network Engineering
ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782)
Feature details
ECGI derivation (2/4)
 ReportCGI measurements can be requested if the following conditions are met:

 the UE is ANR capable and indicates it

capability to the eNB
 RRC:UECapabilityinformation: UE-EUTRA-
Capability:featureGroupIndicators:
BIT17 - Periodical measurement reporting for
SON / ANR and ANR related intra-frequency
measurement reporting events
 no inter-frequency or inter-RAT
measurements are activated at the UE
 current bearer configuration allows for
ANR specific DRX profile
 ReportCGI measurements require long DRX
cycle profile since MIB and SIB1 messages of
indicated cell must be decoded by the UE
 DRX profile is used by the UE only for the time
of executing ReportCGI measurements
 DRX profile is configurable via drxProfile101
parameters (MOC LNCEL)
For internal use only
22 © Nokia Siemens Networks ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782) / Network Engineering
ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782)
Feature details
ECGI derivation (3/4)
 If unknown PCI has been discovered based on A3 or A5 event-triggered
measurement report, ReportCGI can be requested from the UE only for the
strongest unknown PCI and only if no other HO targets are available and the
number of already created LNRELs is smaller than MaxNb=f(nLTEintraNeighbours)
(acc. to CRL678);
 If unknown PCI has been discovered based on
ReportStrongestCells measurement report,
ReportCGI can be requested only if:
 RSRP of reported cell is higher than the configured
threshold anrThresNbCell (MOC LNCEL) and

 RSRQ of reported cell is higher than or equal to the

configured threshold
anrLTEIntraNbCellRSRQThres (MOC LNBTS) and

 the number of already created LNRELs is smaller

than nLTEintraNeighbours (acc. to CRL634)

 ReportCGI measurements are controlled by the timer

anrLTEIntraTReportCGI (MOC LNBTS) – if it expires,
eNB stops ReportCGI measurements by releasing
ANR DRX profile for given UE
For internal use only
23 © Nokia Siemens Networks ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782) / Network Engineering
ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782)
Feature details
ECGI derivation (4/4) - ReportCGI
 Measurement configuration for ReportCGI
 includes PCI for which ECGI is to be decoded
 Report configuration for ReportCGI
 ReportCGI measurement report

For internal use only

24 © Nokia Siemens Networks ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782) / Network Engineering
ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782)
Feature details
Procedure flow (1/4)
 Upon switching to active mode RRC Connection
Reconfiguration procedure is executed to configure
periodic ReportStrongestCell measurements
 in passive mode unknown PCI detection is based on
A3 or A5 event-triggered measurements
 If UE Measurement Report contains an unknown cell
(operating on the same DL EARFCN as serving cell)
and the criteria from slide #23, the RRC Connection
Reconfiguration procedure is executed to configure the
ReportCGI measurements for the unknown PCI
(including DRX profile setup)
 if anrLTEIntraTReportCGI timer expires, eNB stops
ReportCGI measurements by releasing ANR DRX
profile for the UE
 Upon receiving ReportCGI measurement containing
requested CGI information (ECGI, TAC & PLMN), eNB
creates corresponding LNADJ, LNADJL instances (acc.
to CRL634/678 no LNREL is created at this stage) with
info retrieved from ReportCGI measurement report
 eNB indicates changes towards O&M (NetAct and BTS
Site Manager)
 If DRX profile configured on the purpose of ReportCGI
For internal use only
25
measurements need to be changed, RRC Connection
ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782) / Network Engineering
© Nokia Siemens Networks
Reconfiguration procedure is applied
ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782)
Feature details
Procedure flow (2/4)
 Having derived ECGI of investigated cell, the
serving eNB initiates the procedure of X2 C-
plane IP@ resolution via S1 IF involving MME
and S1AP: Configuration Transfer procedure
 SON Information Exchange procedure (according
to 3GPP TS 36.413) is used
 serving eNB addresses eNB of which X2 IP@ is to
be retrieved by Global eNB Id being part of
previously decoded ECGI

 Having retrieved X2 C-plane IP@, the serving

eNB attempts X2 link establishment
 target eNB accepts incoming X2 connection setup
requests from a source eNB even if no IP-address
of the source eNB is configured on the target site
 retrieved X2 C-plane IP@ is stored in cPlaneIpAddr
attribute of MOC LNADJ

For internal use only

26 © Nokia Siemens Networks ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782) / Network Engineering
ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782)
Feature details
Procedure flow (3/4)
 Once X2 connection is successfully established,
source and target eNBs exchange configuration
information necessary to fill in MOCs LNADJ and
LNADJL
 neighbour cells configuration data exchange
process is bidirectional – each eNB retrieves and
stores in LNADJ and LNADJL info on all cells
belonging to the peer eNB (not only on the
unknown cell that triggered the procedure)
 LNREL is not created at this stage – it can be
created only if based on A3/A5 certain cell is
selected as HO candidate (acc. to CRL634)
 eNB knows all cells of the neighboring eNB by PCI
and IP address - if cell being reported within A3/A5
report is selected by eNB as HO candidate (acc. to
CRL634) and is not in LNREL yet, the eNB just
needs to create LNREL and does not trigger ANR
procedure again
 for cells reported in ReportStrongestCell and
ReportCGI measurements, no LNRELs are
created (acc to. CRL634)

For internal use only

27 © Nokia Siemens Networks ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782) / Network Engineering
ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782)
Feature details
Procedure flow (4/4)
 Once X2 connection is successfully established,
source and target eNBs exchange configuration
information necessary to fill in MOCs LNADJ and
LNADJL
 x2LinkStatus in MOC LNADJ is set to ‘available’ so
that X2 handovers towards corresponding cells are
possible
 sourceOfData of corresponding LNADJL objects is
set to ‘X2’
 NetAct and BTS Site Manager are notified about
changed configuration
 until X2 link is successfully setup, cells being
already defined in LNADJL can be regarded as
targets for S1 HO (if feature is enabled)

For internal use only

28 © Nokia Siemens Networks ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782) / Network Engineering
ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782)
Feature details
Features interdependencies (1/2)
 LTE Automatic Neighbor Cell Configuration (LTE724)
 LTE724 may be applied by operator in parallel to LTE782 without any restrictions
 both X2-links provided by operator in accordance with feature LTE724 and X2-links established
via ANR mechanisms can be used simultaneously by eNB
 ANR support for LTE with OAM extension (LTE492)
 LTE492 can run in parallel to LTE782
 to determine the configuration information on unknown UE reported cell, eNB may apply either
LTE782 or LTE492 procedures
 if unknown PCI is present in the PCI/RF/IP@ mapping table (provided via O&M), eNB triggers
LTE492 specific procedures (to establish X2 link and retrieve neighbour cell information) in
parallel to triggering UE measurements for CGI derivation
 IP@ retrieval via S1 IF is applied only if the LTE492 cannot be used due to lack of PCI in
PCI/RF/IP@ mapping table
 LTE492 is applicable to both intra- and inter-frequency scenarios
 LTE782 applies to intra-frequency cases only
 X2-link Blacklist handling introduced with LTE782 is also applied to LTE492
 PCI/RF/IP@ mapping table has been extended with global eNB Ids to provide means for
consistent X2 blacklisting
 if feature LTE492 is activated and if X2 blacklisting shall be used it is recommended to update
the PCI/RF/IP@ mapping table (pciIpAdrMap in MOC LNBTS ) with global eNB Ids via plan file
download/activation
For internal use only
29 © Nokia Siemens Networks ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782) / Network Engineering
ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782)
Feature details
Features interdependencies (2/2)
 DRX in RRC Connected mode (LTE42) and Extended DRX settings (LTE473)
 LTE782 exploits the functionality of LTE42 and LTE473 without the need for explicit activation of
these features
 ECGI derivation (ReportCGI measurements) requires UE to enter DRX mode
 new – ANR specific – trigger for DRX activation/reconfiguration has been introduced
 existing DRX triggers are not affected and runs in parallel to ANR specific activities
 decision whether ANR specific DRX profile can be applied on top of normal DRX profile
depends on priorities assigned to particular profiles

 Periodic UE measurements (LTE570)

 LTE570 can run in parallel to LTE782 but LTE570 is not a prerequisite for LTE782 activation
 if both LTE782 and LTE570 are activated the ReportStrongestCells measurements follow the
rules and setting defined for LTE570

 Blacklisting
 cells that are blacklisted for handover (blacklistHOL in MOC LNCEL) are automatically regarded
as blacklisted for ANR procedure so that for such a cell ECGI derivation is not attempted

 Inter-frequency/inter-RAT measurements
 ReportCGI measurements are not activated for the UE that is already in inter-frequency or inter-
RAT measurement mode
For internal use only
30  ReportCGI measurements are
ANRaborted
© Nokia Siemens Networks upon start
– Intra-LTE, Intra-frequency – Fullyof
UE inter-frequency or inter-RAT measurement
based (LTE782) / Network Engineering
ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782)

Contents

 Introduction
 Features Details
 Configuration Aspects
 Expected Benefits
 Dimensioning Aspects
 Application Aspects
 Performance Measurement Aspects

For internal use only

31 © Nokia Siemens Networks ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782) / Network Engineering
ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782)
Configuration Management
New parameters (1/14)
 Description of parameters related to the LTE782 feature can be find also in PKDB
under the following link:
http://pkdb1.emea.nsn-
net.net:8080/pkdbWebToolLTE/#ProxyPlace:IjIwMjEi@0@ke5UIRZ3CSvUTKzV$70rZvPWY$M=!D
ETAILS

actUeBasedAnrIntraFreqLte Activate UE-based ANR for intra-Frequency LTE

object: LNBTS This parameter controls the status of the feature in the BTS.
unit: - Default value of the parameter disables the feature in the BTS.
range: 0 (false), 1 (true) Feature activation prerequisites:
step: - - feature license is active
default: - Note: Feature activation/deactivation does not require eNB restart.
multiplicity: 1

For internal use only

32 © Nokia Siemens Networks ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782) / Network Engineering
ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782)
Configuration Management
New parameters (2/14)

maxMRnoIntraPciToResolve Max consecutive meas.reports w/o unknown PCIs

object: LNBTS This parameter defines the number of consecutive measurement
unit: - reports (event triggered and ReportsStrongestCells) w/o LTE intra-
frequency unknown PCIs that the eNB cell must receive before
range: 1 (30), 2 (50), disabling Active ANR.
3 (100), 4 (200)
This parameter, together with nLTEintraNeighbours (LNCEL),
step: - determines the criteria for switching between ANR active and passive
default: 2 (50) mode: ANR active mode is left when the number of consecutive
multiplicity: 1 measurement reports (A3/A5 event-triggered and ReportStrongestCells)
without unknown intra-frequency PCI reaches the value of
maxMRnoIntraPciToResolve (MOC LNBTS) and the number of LTE
intra-frequency neighbour relations known to a cell is greater than or
equal to nLTEintraNeighbours (MOC LNCEL).

Note: this is hidden parameter and its modification requires BTS restart.

Rule: the higher the value of this parameter, the longer the ANR active
mode is sustained in cells belonging to the eNB.

For internal use only

33 © Nokia Siemens Networks ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782) / Network Engineering
ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782)
Configuration Management
New parameters (3/14)
anrLTEIntraNbCellRSRQThres ANR LTE intra-freq neighbour cell RSRQ threshold
object: LNBTS This parameter defines the minimum RSRQ level measured by the
unit: dB mapping rule UE from a neighbour cell required for ordering its CGI decoding.
range: 0…34 This parameter together with anrThresNbCell parameter (MOC
LNCEL) determines the criterion for ordering UE to derive ECGI of
step: 1 certain cell.
default: 16 Note: this is hidden parameter and its modification requires BTS
multiplicity: 1 restart.
Rule: the higher the value of this parameter the more stringent criterion
to trigger ECGI derivation. ‘Too low’ values may result in forcing ECGI
derivation for cells that will never be sufficient candidate for handover
and in poor ECGI derivation success rate.
Mapping rule:
RSRQ_00 -> RSRQ  -19.5dB
RSRQ_01 -> -19.5dB  RSRQ < -19dB
RSRQ_02 -> -19dB  RSRQ < -18.5dB
…
RSRQ_16 -> - 12 RSRQ< -11.5dB
…
RSRQ_32 -> -4dB  RSRQ < -3.5dB
RSRQ_33 -> -3.5dB  RSRQ < -3dB
RSRQ_34 -> -3dB  RSRQ
For internal use only
34 © Nokia Siemens Networks ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782) / Network Engineering
ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782)
Configuration Management
New parameters (4/14)

anrLTEIntraRscReportInterval ANR LTE intra-freq reportStrongestCells report interval

object: LNBTS This parameter defines the time interval for
unit: - ReportStrongestCells measurement reports configured in the
UE.
range: 1 (120ms), 2 (240ms),
3 (480ms), 4 (1024ms), This parameter together with anrLTEIntraRscReportAmount
5 (2048ms), 6 (5120ms), parameter influences the number of ReportStrongestCells reports
7 (10240ms), 8 (1min), received from UEs and consequently the unknown PCI discovery
9 (6min), 10 (12min), rate.
11 (30min), 12 (60min) Note1: this is hidden parameter and its modification requires BTS
step: - restart.
default: 4 (1024ms) Note2: if both LTE782 and LTE570 are activated the
ReportStrongestCells measurements follow the rules and setting
multiplicity: 1 defined for LTE570.
Rule: the higher the value of this parameter, the more seldom
ReportStrongestCells reports will be delivered by single UE and
hence some neighbour cells may be not discovered. In scenarios
characterized by high mobility, lower values may increase the
number of unknown PCI discovered based on reports of single UE. In
low mobility scenarios, ‘too short’ (wrt. UE speed) intervals may result
in lots of reports with the same neighbour cells. Setting of this
parameter should be coordinated with setting of
anrLTEIntraRscReportAmount.
For internal use only
35 © Nokia Siemens Networks ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782) / Network Engineering
ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782)
Configuration Management
New parameters (5/14)
anrLTEIntraRscReportAmount ANR LTE intra-freq reportStrongestCells report amount
object: LNBTS This parameter defines the number of periodic
unit: - ReportStrongestCells measurement reports configured in the UE
with single request.
range: 1 (1), 2 (2), 3 (4), 4 (8),
5 (16), 6 (32), 7 (64), This parameter together with nrLTEIntraRscReportInterval parameter
influences the number of ReportStrongestCells reports received from
8 (Infinity) UEs and consequently the unknown PCI discovery rate.
step: - Note1: this is hidden parameter and its modification requires BTS
default: 2 restart.
multiplicity: 1 Note2: if both LTE782 and LTE570 are activated the
ReportStrongestCells measurements follow the rules and setting
defined for LTE570.

Rule: the higher the value of this parameter, the more

ReportStrongestCells reports will be delivered by single UE as a result
of single request from eNB. In scenarios characterized by high mobility,
higher values may increase the number of unknown PCI discovered
based on reports of single UE. Having this parameter set to high
values in low mobility scenarios may bring lots of reports containing the
same neighbour cells (especially if nrLTEIntraRscReportInterval is set
to small values). Setting of this parameter should be coordinated with
setting of nrLTEIntraRscReportInterval.

For internal use only

36 © Nokia Siemens Networks ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782) / Network Engineering
ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782)
Configuration Management
New parameters (6/14)

anrLTEIntraTReportCGI ANR LTE intra-frequency reportCGI timer

object: LNBTS This parameter defines the supervision timer for ReportCGI
unit: ms measurements.
range: 1 (1050), 2 (1090), It defines the maximum time at the eNB for receiving the ReportCGI
3 (1200) measurement results from a UE configured to perform such
measurement. Upon expiry of this timer eNB deactivates the
step: - ReportCGI measurement by releasing ANR DRX profile for the UE.
default: 3 (1200) Note: This is hidden parameter and its modification requires BTS
multiplicity: 1 restart.

For internal use only

37 © Nokia Siemens Networks ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782) / Network Engineering
ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782)
Configuration Management
New parameters (7/14)
glbNbEnbIdX2LinkBlacklist Global eNB id X2-link blacklist
object: LNBTS This parameter provides means for blacklisting the X2 IF eNB
unit: - neighbour relations (eNB does not establish or accept X2
connections to/from eNBs which are contained in this list).
range: -
This list includes the Global eNB IDs of those neighbour eNBs for which
step: - the X2-link establishment is forbidden by the operator.
default: - Note1: this is optional and online modifiable parameter.
multiplicity: 64 Note2: X2 blacklisting is independent from LTE782 status.

waitTimeEstCtrlX2Lnk Wait time for establishment of eNB controlled X2 links

object: LNBTS This parameter defines contribution of the eNB RNL to time the eNB
unit: sec shall wait before repeating the an eNB Controlled X2-link
establishment attempt.
range: 0 (5), 1 (10),
2 (30), 3 (60),
4 (90), 5 (120), Note1: to obtain the total wait time the additional contribution from eNB
6 (150), 7 (240), TNL given by 'MaxTimeSctpSetup' has to be added.
8 (360), 9 (480), Note2: this is hidden parameter and not modifiable.
10 (600)
step: -
default: 6 (150)
multiplicity: 1
For internal use only
38 © Nokia Siemens Networks ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782) / Network Engineering
ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782)
Configuration Management
New parameters (8/14)

anrThresNbCell ANR measurement threshold for neighbour cells

object: LNCEL This parameter defines the threshold for RSRP of a neighbour cell
unit: dBm mapping rule included in ReportStrongestCells measurement report that triggers
CGI derivation.
range: 0…97
If reported RSRP is greater than the value of this parameter, then the cell
step: 1 is accepted by eNB as a neighbour cell for which ECGI is to be derived.
default: 40 Rule: the higher the value of this parameter, the more stringent criterion
multiplicity: 1 to trigger ECGI derivation; “too high” values may result in avoiding ECGI
derivation until A3 event.
Recommendation: the value of this parameter should be about 5 dB
above the RSRP value at the cell edge. The current default value is
calculated for -115 dBm at cell edge (note: this corresponds to a 'Reported
Value' of 35dB as defined in [3GPP 36.133]).
Mapping rule: value_in_dBm = -140+anrThresNbCell

For internal use only

39 © Nokia Siemens Networks ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782) / Network Engineering
 ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782)
Configuration Management
New parameters (9/14)
nLTEIntraNeighbours Number LTE intraFrequency neighbours
object: LNCEL This parameter defines the minimum number of LTE intra-frequency
unit: - neighbour relations (LNREL objects) created in a given cell required
for leaving the ANR Active mode in this cell.
range: 1 (0), 2 (6), 3 (12),
4 (18), 5 (Infinity) This parameter together with maxMRnoIntraPciToResolve (LNBTS)
determines the criteria for switching between ANR active and passive
step: - mode: ANR active mode is left when the number of consecutive
default: 3 (12) measurement reports (A3/A5 event triggered and ReportStrongestCells)
multiplicity: 1 without unknown intra-frequency PCI reaches the value of
maxMRnoIntraPciToResolve (MOC LNBTS) and the number of LTE intra-
frequency neighbour relations known to the eNB cell is greater than or
equal to nLTEintraNeighbours (MOC LNCEL).
Note1: if unknown PCI is reported within ReportStrongestCells (e.g.
Periodic UE measurements - LTE570) when the number of created
LNRELs is equal or higher than this parameter, no CGI derivation
procedure is attempted for this PCI (acc. to CRL634)
Note2: if unknown PCI is reported within A3/A5 report when the number of
created LNRELs is equal or higher than maxNb being defined via this
parameter, no CGI derivation procedure is attempted for this PCI (acc. to
CRL678); maxNb = 1 (16); 2 (32); 3 (48); 4 (64); 5 (infinity);
Rule: the higher the value of this parameter, the longer ANR active mode
is kept in a cell and more neighbour relations are to be created. Setting of
this parameter should be adjusted according to the network layout.
For internal use only
40 © Nokia Siemens Networks ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782) / Network Engineering
ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782)
Configuration Management
New parameters (10/14)

drxProfile101 DRX profile 101

object: LNCEL This parameter defines DRX profile for LTE intra-frequency ANR
unit: - measurements (ReportCGI measurements).
range: …, … This is the structure containing the following attributes:
step: - - drxProfileIndex: identity of DRX profile = 101
default: - - drxInactivityT: the Inactivity Timer for DRX (the number of
consecutive PDCCH-subframes for which the UE
multiplicity: 1 monitors the PDCCH after decoding an UL or DL
resource assignment on PDCCH for an initial data
transmission)
- drxLongCycle: the long DRX cycle (the periodic repetition of the DRX
On Duration)
- drxOnDuratT: the On Duration Timer for DRX (the number of
consecutive PDCCH-subframes at the beginning of a
DRX cycle during which the UE monitors the PDCCH)
-drxProfilePriority: DRX profile priority (determines applicability of DRX
profile in the context of established bearers)
- drxRetransT : Retransmission Timer for DRX (the maximum number
of PDCCH-subframes a UE monitors the PDCCH as
soon as a retransmission in DL is expected by the UE)
Note: There is no need to explicitly activate the DRX feature . If not
explicitly activated, DRX will apply only for ANR specific measurements
For internal use only
41 © Nokia Siemens Networks
but not for power saving.
ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782) / Network Engineering
ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782)
Configuration Management
New parameters (11/14)

cPlaneIpAddr C-Plane IP address of neighbor eNB

object: LNADJ This parameter replaces the former ADIPNO parameter
unit: - adjEnbCPlaneIpAddress. It holds the C-Plane IP address of an
adjacent eNB.
range: 7…15 characters
The format of this parameter allows for an IPv4 IP@ in the dotted decimal
step: - form. Value ‘0.0.0.0’ means the Control plane IP address is not defined.
default: - This is online modifiable parameter. It is configurable via plan file or ANR
multiplicity: 1 related procedures.
IP@ information from ADIPNO is automatically migrated to the new model.
Note:
- cPlaneIpAddr must be unique within all LNADJ objects (except for empty
values)
- cPlaneIpAddr is mandatory if cPlaneIpAddrCtrl is set to ‘oamControlled’
- if cPlaneIpAddr is not configured adjEnbId parameter must be specified
- the maximum number of established X2 links is 32, even if the number of
LNADJ instances is higher.
- If there are 32 oamControlled IP@, LTE782 is not possible and hence at
least one IP@ should be left for eNBControlled
-
For internal use only
42 © Nokia Siemens Networks ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782) / Network Engineering
ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782)
Configuration Management
New parameters (12/14)
cPlaneIpAddrCtrl C-Plane IP address control
object: LNADJ This parameter determines whether the C-Plane IP address of the
unit: - neighbour eNB (X2 link) is statically configured via plan file
(‘oamControlled’) or whether eNB is allowed to update the IP address
range: 0 (oamControlled), based on information provided by ANR procedures (‘enbControlled’).
1 (enbControlled)
Note:
step: -
- the maximum number of LNADJ instances with cPlaneIpAddrCtrl set to
default: 0 (oamControlled) ‘oamControlled’ is 32
multiplicity: 1 - in terms of the limitation to maximum of 32 X2 links, the ‘oamControlled’
links have priority over ‘enbControlled’ -> new ‘oamControlled’ link can
drop existing enbControlled’
- if parameter set to ‘oamControlled’, the operator is responsible for correct
configuration of the cPlaneIpAddr
- if the parameter is set to ‘enbControlled’ the IP@ is maintained by ANR
procedures if ANR features are activated. Moreover, plmnId and adjEnbId
must be configured. ‘enbControlled’ is the default value for neighbor eNBs
which have been learnt via ANR procedures.
- Reconfigurations of this parameter (‘enbControlled’<-> ‘oamControlled’)
can be done by the operator. Modification from 'enbControlled' to
'oamControlled' is rejected if the limit of maximum 32 'oamControlled' X2
links would be exceeded. Modification to ‘oamControlled’ is allowed only if
the IP@ is already configured or is provided in parallel within the delta
plan file.
For internal use only - In RL30, all new neigbours found by LTE492 or LTE782 are established
ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782) / Network Engineering
43 © Nokia Siemens Networks
as ‘eNBControlled’
ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782)
Configuration Management
New parameters (13/14)

x2LinkStatus X2 link status

object: LNADJ This parameter provides information whether the X2 link has been
unit: - established successfully (‘available’) or not (‘unavailable’).
range: 0 (unavailable), This is read only parameter.
1 (available)
step: -
default: -
multiplicity: 1

For internal use only

44 © Nokia Siemens Networks ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782) / Network Engineering
ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782)
Configuration Management
New parameters (14/14)

sourceOfData Source of data

object: LNADJL This parameter provides information whether the LNADJL object
unit: - creation or latest update was based on plan file data (OM), X2
information (X2) or UE specific ANR measurements (UE).
range: 0 (OM), 1 (UE), 2 (X2)
This is read only parameter.
step: -
default: -
multiplicity: 1

validityOfData Validity of configuration data

object: LNADJL This parameter indicates if PCI&EARFCN duplication has been
unit: - detected by eNB.
range: 0 (false), (true) If the same PCI&EARFCN combination is already in use (other LNADJL
or LNCEL object), this parameter is set to 'false'. If the flag is set to
step: - 'false' the LNADJL object is ignored by eNB procedures.
default: - This is read only parameter.
multiplicity: 1

For internal use only

45 © Nokia Siemens Networks ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782) / Network Engineering
ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782)

Contents

 Introduction
 Features Details
 Configuration Aspects Please refer to comments in section
Performance Measurement Aspects.
 Expected Benefits
 Dimensioning Aspects
 Application Aspects
 Performance Measurement Aspects

For internal use only

46 © Nokia Siemens Networks ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782) / Network Engineering
ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782)

Contents

 Introduction
 Features Details
 Configuration Aspects
 Expected Benefits No contents for this section as this feature
has no impact on dimensioning
 Dimensioning Aspects
 Application Aspects
 Performance Measurement Aspects

For internal use only

47 © Nokia Siemens Networks ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782) / Network Engineering
ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782)

Contents

 Introduction
 Features Details
 Configuration Aspects
 Expected Benefits
 Dimensioning Aspects
 Application Aspects
 Performance Measurement Aspects

For internal use only

48 © Nokia Siemens Networks ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782) / Network Engineering
ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782)
Application aspects
LNADJ object management in RL30/RL25TD
 LNADJ object can be created either via plan file or automatically by eNB
 to avoid ID conflicts in case of in-parallel-creation of LNADJ via plan file and by the
eNB, in plan file the lowest free LNADJ instance ID should be used (eNB uses the
highest free LNADJ instance ID in automatic creation procedure)
 if a pure S1 HO target cell is to be configured, the parameter cPlaneIpAddr should be
left empty and cPlaneIpAddrCtrl shall be set to ‘enbControlled’
 to prohibit X2 connection establishment, the neighbour eNB needs to be blacklisted via
glbNbEnbIdX2LinkBlacklist (MOC LNBTS)

 for static X2 IF configuration, cPlaneIpAddr must be set with the C-Plane IP@ of the
neighbour eNB and cPlaneIpAddrCtrl should be set to ‘oamControlled’ (default value)
 until the X2 connection is successfully established the x2LinkStatus is kept set to ‘unavailable’
 LNADJ can be modified or deleted via plan file
 setting of cPlaneIpAddrCtrl can be modified via plan file with the restriction that
changing to ‘oamControlled’ is allowed only if the IP@ (cPlaneIpAddr) is already
configured or provided in parallel within the delta plan file and the maximum (32)
number of ‘oamControlled’ links is not exceeded.
 to delete the neighbour eNB information persistently the neighbour eNB must be
49
blacklisted (MOC LNBTS:ANRglbNbEnbIdX2LinkBlacklist)
For internal use only
© Nokia Siemens Networks – Intra-LTE, Intra-frequency – Fully UE based (LTE782) / Network Engineering
ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782)
Application aspects
LNADJL object management in RL30/RL25TD

 LNADJL object can be created either via plan file or automatically by eNB
 to avoid ID conflicts in case of in-parallel-creation of LNADJL via plan file and by the
eNB, in plan file the lowest free LNADJL instance ID should be used (eNB uses the
highest free LNADJL instance ID in automatic creation procedure)

 LNADJL can be modified or deleted via plan file

 modification of LNADJL parameters via plan file make sense only if no X2 link is
configured or if the X2 link is unavailable – otherwise eNB would implicitly trigger
X2 link setup to ensure data consistency

 when deleting LNADJL the corresponding LNREL object is kept – unused LNREL(s)
may be deleted manually via plan file

For internal use only

50 © Nokia Siemens Networks ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782) / Network Engineering
ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782)
Application aspects
LNREL object management in RL30/RL25TD
 LNREL object can be created either via plan file or automatically by eNB
 to avoid ID conflicts in case of in-parallel-creation of LNREL via plan file and by the eNB, in plan
file the lowest free LNREL instance ID subordinate to the given LNCEL object should used (eNB
uses the highest free LNREL instance ID in automatic creation procedure)
 LNREL objects can be created together with the related LNADJL object in one delta plan file
 LNREL objects are created automatically by eNB for given PCI only if corresponding LNADJL
already exists and the PCI it is not blacklisted (MOC LNCEL: blacklistHOL) and it has been
selected by eNB as HO candidate based on A3/A5 event
 LNREL is not created for cells from A3/A5 report that have not been selected as HO
candidate and is not created for cells reported in reportStrongestCells and ReportCGI
measurement reports (acc. to CRL634/678)
 LNREL objects are kept even if related LNADJL or LNCEL instance is deleted
 such “dummy” objects are not regarded as valid HO targets
 LNREL becomes effective if corresponding LNADJL is learnt or configured
 LNREL objects can be modified or deleted via plan file

 LNREL object management is independent from the status of LTE782 and LTE492
 if neither LTE782 nor LTE492 is activated LNREL objects are created by eNB if corresponding
LNADJL object already exist and certain PCI is reported by UE within A3/A5 event and is
selected by eNB as HO candidate

For internal use only

51 © Nokia Siemens Networks ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782) / Network Engineering
ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782)

Contents

 Introduction
 Features Details
 Configuration Aspects
 Expected Benefits
 Dimensioning Aspects
 Application Aspects
 Performance Measurement Aspects

For internal use only

52 © Nokia Siemens Networks ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782) / Network Engineering
ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782)
Performance measurement aspects
New counters (1)

Counter name Description

X2_IP_RETR_VIA_S1_ATT This counter provides the number of attempted neighbour eNB X2
(M8000C38) IP@ retrievals via S1 IF
(S1AP measurements) Trigger event: eNB sends S1AP:ENB CONFIGURATION
TRANSFER message including ‘SON Information Request’ for 'X2
TNL Configuration Info' to the MME.
Use case:
- X2_IP@_RETRIEVAL_SUCCESS_RATE = M8000C37/M8000C38
X2_IP_RETR_VIA_S1_SUCC This counter provides the number of successful neighbour eNB X2
(M8000C37) IP@ retrievals via S1 IF.
(S1AP measurements) Trigger event: eNB receives from the MME the S1AP:MME
CONFIGURATION TRANSFER message including 'SON Information
Reply' with 'X2 TNL Configuration Info' and C-Plane IP@ of neighbor
eNB.
Use case:
- X2_IP@_RETRIEVAL_SUCCESS_RATE = M8000C37/M8000C38

For internal use only

53 © Nokia Siemens Networks ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782) / Network Engineering
ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782)
Performance measurement aspects
New counters (2)

Counter name Description

X2_SETUP_ATT (M8022C0) This counter provides the number of X2 setup attempts triggered by eNB
(X2AP measurements) Trigger event: eNB sends X2AP: X2 SETUP REQUEST message to the
neighbour eNB
Use case:
- X2_SETUP_SUCCESS_RATE = 1 – (M8022C1/M8022C0)
X2_SETUP_ATT_FAIL This counter provides the number of failed X2 setup attempts
(M8022C1) Trigger event: eNB receives X2AP: X2 SETUP FAILURE message from
(X2AP measurement) the neighbor eNB towards which X2AP: X2 SETUP REQUEST message
had been sent previously or TimerX2SetupWaitForResponse timer
expires (MOC LNBTS: x2SetupRspTmr ).
Use case:
- X2_SETUP_SUCCESS_RATE = 1 – (M8022C1/M8022C0)

For internal use only

54 © Nokia Siemens Networks ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782) / Network Engineering
ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782)
Performance measurement aspects
New counters (3)

Counter name Description

REPORT_CGI_REQ This counter provides the number of attempts to retrieve the CGI of a
(M8008C10) neighbour cell with the help of a UE.
(RRC measurements) Trigger event: eNB sends RRCConnectionReconfiguration
including 'reportCGI' measurement configuration to the UE
Use case:
- CGI_DERIVATION_SUCCESS_RATE = M8008C11/M8008C10
SUCC_CGI_REPORTS This counter provides the number of CGI measurement reports received
(M8008C11) from UE.
(RRC measurements) Trigger event: eNB receives RRC: Measurement Report message
including a 'reportCGI' measurement result for requested PCI.
Use case:
- CGI_DERIVATION_SUCCESS_RATE = M8008C11/M8008C10

For internal use only

55 © Nokia Siemens Networks ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782) / Network Engineering
ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782)
Performance measurement aspects
Feature performance monitoring

Feature performance indicator How to measure

 Number of CGI derivation requests Counters:
 REPORT_CGI_REQ (M8008C10)
 CGI derivation success rate KPIs:
 CGI_DERIVATION_SUCCESS_RATE =
M8008C11/M8008C10
 Number of X2 IP@ retrieval requests Counters:
 X2_IP_RETR_VIA_S1_ATT (M8000C38)
 X2 IP@ retrieval success rate KPIs:
 X2_IP@_RETRIEVAL_SUCCESS_RATE =
M8000C37/M8000C38
 Number of X2 setup attempts Counters:
 X2_SETUP_ATT (M8022C0)
 X2 setup success rate KPIs:
 X2_SETUP_SUCCESS_RATE = 1 – (M8022C1/M8022C0)

For internal use only

56 © Nokia Siemens Networks ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782) / Network Engineering
ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782)
Performance measurement aspects
Impact on overall network performance

 Although the main argument behind LTE782 introduction is to reduce the manual pre-
planning efforts, activation of this feature may influence the overall network
performance in terms of inter-eNB handover statistics
 this feature increases the probability of having complete neighbour cell relations what in turn
may be reflected in better performance of inter-cell HOs
 without LTE782, in case of incomplete O&M-controlled cPlaneIpAddr in MOC LNADJ
(LTE724&LTE539) or PCI/RF/IP@ mapping table in MOC LNBTS (LTE492) some adjacent cells
may be missed in the neighbour cell information leading to non-optimal HO performance

Feature impact How to measure

Higher X2-based inter-eNB HO KPIs:
Success Ratio  inter eNB E-UTRAN tot HO SR X2 (LTE_5058b)
 inter eNB E-UTRAN HO SR X2 (LTE_5048b)
Lower X2-based inter-eNB HO KPIs:
Failure Ratio  inter eNB E-UTRAN HO FR X2 (LTE_5055b)

The feature impact highly depends on the completeness of neighbour cell information before
feature activation – in case of appropriately defined O&M-controlled cPlaneIpAddr in MOC LNADJ
and/or PCI/RF/IP@ mapping table in MOC LNBTS (based on which neighbour cell information is
retrieved), there may be no impact of LTE782 feature activation on network performance.

For internal use only

57 © Nokia Siemens Networks ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782) / Network Engineering
 Thank you
for your attention!

For internal use only

58 © Nokia Siemens Networks ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782) / Network Engineering
 Backup

For internal use only

59 © Nokia Siemens Networks ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782) / Network Engineering
ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782)
CRL634

For internal use only

60 © Nokia Siemens Networks ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782) / Network Engineering
ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782)
Feature details
LNBTS (1..1) * LTE492 specific
lnBtsId, …, actUeBasedAnrIntraFreqLte, glbNbEnbIdX2LinkBlacklist,
pciIpAdrMap (dlEarfcn, ipAdr, pci, eNbId)*, … …

LNCEL: LNADJ (0..64):

LNADJG (0..32)
LNADJW (0..32)
LNCEL:  lnCelId  lnAdjId
 lnCelId 1…6  phyCellId  adjEnbId
 phyCellId  eutraCelId  plmnId
 eutraCelId  lcrId  …
 lcrId  adjWInfList  cPlaneIpAddr
 adjGInfList  adjGInfList  cPlaneIpAddCtrl
 adjWInfList  anrThresNbCell  x2LinkStatus
 anrThresNbCell  drxProfile101  …
 drxProfile101  nLTEIntraNeigh
 nLTEIntraNeigh bours
bours …
… LNADJL (1..6):
 lnAdjlId
 phyCellId
 adjEutraCelId
 ecgiPlmnId
LNREL (0..389): LNREL (0..389):  ecgiAdjEnbId
 lnRelId  lnRelId  ecgiLcrId
 ecgiAdjEnbId  ecgiAdjEnbId  sourceOfData
 ecgiLcrId  ecgiLcrId  validityOfData
 ecgiPlmnId  ecgiPlmnId …
For internal use only …  …
61 © Nokia Siemens Networks ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782) / Network Engineering
RL10, RL20, RL15TD Intra system adjacency
LTE724 LTE Automatic Neighbor Cell Configuration
LNADJ creation is started when X2
connection has been set up
successfully. 2
For each cell served by neighbouring
BTS an instance of LNADJL is created. 1
Parameters for LNADJ and LNADJL are
copied automatically from target.
PLMN
Operator configures only C-Plane IP
addess of neighbouring eNB in ADIPNO
for automatic LTE intra system
Target eNB
MRBTS adjacency (LNADJ, LNADJL) creation.
Source eNB
1..1
X2
LNBTS LNBTS

1..1
0..32 Adjacent eNB configuration map
LNCEL ADIPNO (adjEnbIpAddressMap)
LNADJ 1..3 multiplicity: 32
adj eNB list
- Adjacent eNB C-plane IP address
LNCEL
1..3
0..98
adjCellnfoL
LNADJL

Neighbouring LTE BTS cell Neighbouring LTE BTS Neighbouring cell

object represents neighbouring object contains Information list
LTE cell which is served by its information about Global Parameter for List of
parent LNADJ instance. This MOC eNB ID [SIG.1389] of neigbouring cell’s
contains served cell information of neighbouring eNB and Unique E-UTRAN cell
neighbouring cell received during other neighbouring eNB identifiers, multiplicity:
X2 establishment. related parameters. 98 (=32*3+2).
Object/parameter created/modified/deleted by eNB

Object/parameter created/modified/deleted by user

For internal use only
62 © Nokia Siemens Networks ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782) / Network Engineering
RL30, RL25TD Intra system adjacency
LTE724 LTE Automatic Neighbor Cell Configuration
LTE54 Intra-LTE handover management via S1
Target eNB
When X2 link cannot be LNADJ and LNADJL used for
for S1 successfully established, both X2 and S1 HO. Operator
LNADJ is used for S1 HO. can create LNADJ and LNADJL.
LNBTS
S1 Information in LNADJ X2 Link LTE54: LNADLP removed.
Status parameter that is set by
MME system. LTE724: ADIPNO no longer
LNCEL PLMN used. But operator can create
via plan LNADJ and LNADJL.
S1 adjCellInfoL no longer
Target eNB supported.
MRBTS
for X2 LTE782: New object LNREL.
1..1 Source
X2 eNB
LNBTS LNBTS

1..1 0..16
LNCEL 0..64
ADIPNO LNADLP
LNADJ 1..6
adj eNB list

1..6
LNCEL
adjCellnfoL LTE Neighbor Relation
LNADJL
A new MOC LNREL is
introduced which represents
properties of LTE neighbour
0…389
relations. Max: 6*64 + 5 = 389.

LNREL LNREL objects are created

automatically by eNB
Object/parameter created/modified/deleted by user
Object/parameter created/modified/deleted by eNB
For internal use only
63 © Nokia Siemens Networks ANR
Presentation – Intra-LTE,
/ Author / DateIntra-frequency – Fully UE based (LTE782) / Network Engineering
ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782)
Feature details
Measurement Configuration IE

For internal use only

64 © Nokia Siemens Networks ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782) / Network Engineering
 ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782)
Feature details
Alarms and warnings
 Related alarms
 Maximum number of Neighbour eNBs/cells
is exceeded
 Neighbour Cell Information Inconsistency
Alarm Name Maximum number of Neighbour eNBs/cells exceeded
Scenario description The alarm is raised if an LTE neighbour cell, which is
reported by an UE via ANR specific measurements could not
be stored because the maximum number of LNADJ or
LNADJL instances is reached.
Trigger description A new LTE neighbour cell is reported by an UE due to Alarm Name Neighbour cell info inconsistency
activated ANR feature(s) but cannot be stored because the Scenario description If inconsistencies in neighbour cell
maximum number of LNADJ objects or LNADJL objects is information are detected, the alarm is raised
already reached. to inform the network operator about the
Alarm Text A neighbour cell which is reported by an UE due to activated error condition which has occurred.
ANR feature(s) could not be stored because the maximum Please note that this is only warning.
number of neighbour eNBs or neighbour cells is reached. Trigger description Inconsistency error for Neighbouring Cell
Neighbour cell information needs be cleaned up manually by Information occured during creation of cell or
the operator via plan file. neighbour cell information.
Probable Cause - Inconsistent configuration for neighbouring
Alarm Text
Alarm Severity Warning cells was detected
Additional Info ECGI of the reported cell, which could not be stored Probable Cause -
MOC (alarm object) LNBTS Alarm Severity Warning
Alarm clearance condition not applicable Additional Info affected LNADJL/LNCEL instances including
Alarm correlation description - PCI value and frequency
MOC (alarm object) LNADJ
Alarm clearance condition Not applicable
Alarm correlation description -

For internal use only

65 © Nokia Siemens Networks ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782) / Network Engineering