You are on page 1of 108

ANR for UTRAN -

Fully UE based
LTE908
Network Engineering Information
• Bartlomiej Bednarz
• 30-07-2015
• Ver 1.3
Please always check the latest version of this NEI slides!
1 © Nokia Solutions and Networks 2014
For internal use
Disclaimer

• Please note that the NEI materials are for internal use only. If they shall be used as a
source for the customer presentation, it is mandatory to align the contents with the
Product Management and/or local sales teams at first!
• The results of simulations shown in this presentation are examples only. They
demonstrate trends (not absolute values) expected after feature activation. The
presented simulations should be analyzed with respect to the assumptions taken.
They may differ from results achievable in real networks.
• This NEI slide deck reflects the state of the feature/solution as it is at the moment of
the NEI slide deck release and is being updated up to C5 (release available)
milestone.

2 © Nokia Solutions and Networks 2014


For internal use
Revision history and metadata
Please delete this slide if document is uncontrolled

Document ID: DXXXXXXXXX


Document location:
Organization:

Version Description of Changes Date Author Owner Status Reviewed by Reviewed Approver Approval
Date Date

0.1 For internal review (included: CRL2307, 12-02-2015 Bartlomiej DD-MM- DD-MM-
CRL2443) Bednarz YYYY YYYY

0.2 After internal review (comments from: 20-02-2015 Bartlomiej


Gay Calaranan, Marek Brylka, Krzysztof Bednarz
Golebiewski, Krzysztof Wascinski)

1.0 After external review (comments from: 25-02-2015 Bartlomiej


Tero Maaniitty, Maija Kaarre included) Bednarz

1.1 Minor update, 27-02-2015 Bartlomiej


LNHOW:maxNumCsfbTargets limitation Bednarz
added

1.2 NetAct requirements changed 20-04-2015 Bartlomiej


Bednarz

1.3 Inactivity timer issue added as open 30-07-2015 Bartlomiej


point (see on next slide). Additionaly, Bednarz
cooperation with MOCN (LTE4) is
described in ‘Interdependencies’ slides

Acknowledgements:
3 © Nokia Solutions and Networks 2014
-Big Data & NetEng: Marek Brylka, Gay Calaranan
For internal use
-Trials & Pilots: Otto Koch
Open Issues

Item Description Comments


When Inactivity timer (under LNCEL object) is changed from default value (30s) to value 10s or
less, then preparation of LNADJW object can not be finished and the handover to UTRAN is not
1 possible.
Correction plan: RL70 2.0, RL55 1.1
NA05804397

4 © Nokia Solutions and Networks 2014


For internal use
LTE908 ANR Inter-RAT UTRAN - Fully UE based
Table of contents

Introduction Technical Inter – Benefits and


Details dependencies Gains
Motivation and Feature Detailed Functionality Simulation, Lab and
Interdependencies with
Overview Description Field Findings
other features and Simulation, Lab
functions
1 and Field Findings

Configuration Deployment Performance Compliance


Management Aspects Aspects Aspects
Parameters and Activation, Configuration 3GPP, IETF, ETSI
Parameterization Counters and KPIs,
Examples, Fault Mgmt, Feature Impact Analysis
Scenarios Trial Area and Verification

5 © Nokia Solutions and Networks 2014


For internal use
LTE908 ANR Inter-RAT UTRAN - Fully UE based

Introduction

Table of contents

6 © Nokia Solutions and Networks 2014


For internal use
Introduction network
area
Before RL70/55TD LTE

LTE783/4 ANR Inter-RAT UTRAN/GERAN (RL30/35TD) -


NetAct features:
• Both features create (and delete) neighbor relations (NRs)
respectively
• NRs are determined with help of NetAct Optimizer,
Configurator and Operator user WCDMA
• Features are based on planning information (Geo-location of
cell’s antenna and antenna direction which have to be
manually entered by a user) from NetAct Configurator
• An uni-directional neighbor relationship is created – from LTE GERAN
towards GERAN or/and WCDMA
LTE cell/site with ANR enabled
LTE510 Synchronization of Inter-RAT Neighbors
• The feature is an enhancement of LTE783/LTE784 to keep Candidate for NR to WCDMA
automatically inter-RAT neighbor relations up-to-date
Candidate for NR to GERAN
Please refer to the NEI slides for details
7 © Nokia Solutions and Networks 2014
For internal use
Introduction
Before RL70/55TD
LNBTS (1..1)
lnBtsId, MCC, MNC,… …
LTE507 Inter-RAT Neighbor Relation Optimization (RL50/35TD)
– NetAct feature
LNADJx: LNCEL:
• The goal of the feature is to validate NR in the context of its stability and
reliability for a given mobility feature (e.g. Inter RAT PS HO, CSFB to • Neighboring • LTE (source)
UTRAN, SRVCC to GERAN, etc.) (target) WCDMA cell information
cell information
• This feature manages and optimizes the existing inter-RAT neighbor
relations between:
• LTE and WCDMA and/or LTE and GERAN for a defined set of mobility
LNRELx:
features
•…
• Optimizer user or automatic scheduler is able to use PM counters and
• csfbPsHoAllowed
KPIs to identify and blacklist various bad performing mobility features
• psHoAllowed
(e.g.blacklist Inter RAT PS HO with Success ratio < 90%)
„flexible blacklisting” • srvccAllowed
• Blacklisting is done in neighbor relation object LNRELx (means by Service ‘forbidden’. It •…
LNRELG/LNRELW/LNRELT) on mobility feature level is based on PM/KPIs,
thresholds and
nrControl condition.
Please refer to the NEI slides for details
8 © Nokia Solutions and Networks 2014
For internal use
Introduction
In RL70/55TD

LTE908 ANR for UTRAN - Fully UE based 0. UE Measurement Configuration


1. Measure the signal
(UTRAN, Frequency band) ( PSC x,
LTE eNB
• For unknown UE-reported WCDMA cell (PSC Center frequency Y)

unknown to eNB), the corresponding WCDMA 2. RRC measurement


report (PSC x, Center frequency Y, etc.)
Cell Global ID (CGI) is derived to the eNB with
the help of the UE measurements 3G BTS
3. Report request
to report CGI, RAC, LAC for PSC x 4. Read CGI, RAC,
• UTRAN carrier frequency must be defined in LAC from BCCH
5. Report CGI, RAC, LAC, PLMN-Ids
feature Profile
• UE decodes and delivers: CGI and LAC/RAC on CGI Cell Global Identifier
request coming from eNB RAC Routing Area Code
LAC Location Area Code
• eNB collects UTRA cell data, stores it in the BCCH Broadcast Channel
PSC Primary Scrambling Code
database, creates LNRELW/LNADJW and LTE908 supports NR adding
provides retrieved cell data to the NetAct towards WCDMA only
ANR Inter-RAT for TD-
•UE is triggered for UTRAN ANR measurement by: SCDMA is supported starting
• RRC Connection establishment/re-establishment or Incoming intra/inter-cell HO from TD-LTE 15A
• And when the UE context has been tagged for UTRAN ANR (case when LTE782 or/and LTE556 enabled as well
9
– see more in ‘Inter-dependencies’ part)
© Nokia Solutions and Networks 2014
For internal use
Introduction
Before & after

Before After
• Neighbor relations for UTRAN handovers must • Automatic detection and setup of neighbor cell
be defined manually, or relation from LTE towards WCDMA for
• With help of Optimizer while based on manually Connected Mode mobility purposes
entered geo-location data LTE • Candidate UTRAN cell signal strength/quality
• LTE783 works considering only is verified
distance between sites and
antenna direction • Activation via ANR Profiles
• If potential neighbor cell geo- • ANR Profile gives full flexibility in feature
location data is missing, NR configuration (e.g. activation, frequency band
will not be created signal quality/strength threshold, mobility
• Frequency band or candidate features blacklisting, NR limitation, …)
signal strength is not considered WCDMA • New PM counter for supervision of CGI
• As a result, NR performance might not be resolution (attempt, success, incomplete)
stable and reliable between cells
10 © Nokia Solutions and Networks 2014
For internal use
LTE908 ANR for UTRAN – Fully UE based

Technical Details

Table of contents

11 © Nokia Solutions and Networks 2014


For internal use
Technical Details
Dependency Table (LTE)

FDD LTE RL release eNodeB NetAct


Release/version RL70 LN7.0 NetAct 15.2 PP317

TDD LTE RL release eNodeB NetAct


Release/version RL55TD LNT5.0 NetAct 15.2 PP317

Flexi Zone Micro


RL release eNodeB NetAct
(FZM)
Release/version RL70/55FZ LNF7.0/LNZ5.0 NetAct 15.2 PP317
HW Specified by
HW & IOT MME SAE GW UE
requirements 3GPP
Specific FIGs
At least Rel’8
required*
12 © Nokia Solutions and Networks 2014
For internal use
* refers to slides #, #
Technical Details
Neighbor relation database structure in RL70/55TD
LNBTS (1..1)
lnBtsId, MCC, MNC,… …

ANRPRW(0..16): LNADJW(0..256): LNCEL(1..x): LNHOW(1..16):


• Definition of carrier specific • Neighboring • LTE (source) cell • Measurements and handover to
ANR profiles (target) WCDMA information UTRAN related information
• Target frequencies, cell information
dedicated thresholds and DRX Profile102
UFFIM(0..1):
limits are used for
searching new neighbor • Utran Frequency Idle Mode configuration
cells
REDRT(0..6):
Objects created by LTE783 or LTE908 • Parameters related to redirection

Objects created by LTE783 only LNRELW(0..256):


Objects created for LTE908 only • Indicates neighbor relationship to WCDMA

13 © Nokia Solutions and Networks 2014


For internal use
Searching of Detectability
Requirements Configuration CGI resolution NR update
unknown cell confirmation
Technical Details
LTE908 ANR for UTRAN - Fully UE based

Activation of LTE908:
• “ANR for UTRAN – Fully UE-based” [LNBTS:actUeBasedAnrUtran]
• UE’s reported UTRA capability must support ANR for UTRAN
• Definition of ANR profile(s) (for WCDMA frequency)

UE eNB NodeB MME NetAct

LNBTS:actUeBasedAnrUtran=true
ANRPRW – must be created for particular arfcn

RRC: UE UTRA Capability Enquiry


RRC: UE UTRA Capability Information

14 © Nokia Solutions and Networks 2014


For internal use
Searching of Detectability
Requirements Configuration CGI resolution NR update
unknown cell confirmation
Technical Details
LTE908 ANR for UTRAN - Fully UE based

UE Utra capability information (contains ANR-relevant information from UE):


• whether UTRA Measurements are supported
• if MeasGaps are needed to be setup
• which Utra bands are supported
• which FIGs are supported

Sample message:

15 © Nokia Solutions and Networks 2014


For internal use
Searching of Detectability
Requirements Configuration CGI resolution NR update
unknown cell confirmation
Technical Details
LTE908 ANR for UTRAN - Fully UE based

Feature Group Indicator #16, 19, 22 must be set by the Rel’8 UE for full LTE908 support:
FGI bit Description
5 - Long DRX cycle
NOTE: bit 5 is mandatory for bit 19
16 - Inter-RAT periodical measurement reporting where triggerType is set to periodical and purpose is set to
reportStrongestCells for UTRAN, GERAN, 1xRTT or HRPD, if the UE has set bit number 22, 23, 24 or 26 to 1,
respectively.
19 -Inter-RAT periodical measurement reporting where triggerType is set to periodical and purpose is set to
reportStrongestCellsForSON for UTRAN, 1xRTT or HRPD, if the UE has set bit number 22, 24 or 26 to 1,
respectively
- Inter-RAT periodical measurement reporting where triggerType is set to periodical and purpose is set to
reportCGI for UTRAN, GERAN, 1xRTT or HRPD, if the UE has set bit number 22, 23, 24 or 26 to 1, respectively
22 - UTRAN measurements, reporting and measurement reporting event B2 in E-UTRA connected mode

Rel’8 supports 32 FIG bits

16 © Nokia Solutions and Networks 2014


For internal use
Searching of Detectability
Requirements Configuration CGI resolution NR update
unknown cell confirmation
Technical Details
LTE908 ANR for UTRAN - Fully UE based

Feature Group Indicator #16, 22, 33 (optionally 114) must be set by the Rel’9 (Rel’10) UE
for full LTE908 support:
FGI bit Description
5 - Long DRX cycle
NOTE: bit 5 is mandatory for bit 33
16 - Inter-RAT periodical measurement reporting where triggerType is set to periodical and purpose is set to
reportStrongestCells for UTRAN, GERAN, 1xRTT or HRPD, if the UE has set bit number 22, 23, 24 or 26 to 1,
respectively.
22 - UTRAN measurements, reporting and measurement reporting event B2 in E-UTRA connected mode
33 -Inter-RAT periodical measurement reporting where triggerType is set to periodical and purpose is set to
reportStrongestCellsForSON
- Inter-RAT periodical measurement reporting where triggerType is set to periodical and purpose is set to
reportCGI
NOTE: can only be set to 1 if the UE has set bit number 5 and bit number 22 to 1.
(114) -Reporting of both UTRA CPICH RSCP and Ec/N0 in a Measurement Report
NOTE: - this bit can be set to 1 only if index 22 is set to 1. This FGI is present for UE with release >= “Rel’10”
17 © Nokia Solutions and Networks 2014 Rel’9 supports 64 FIG bits
For internal use
Rel’10 supports 128 FIG bits
Searching of Detectability
Requirements Configuration CGI resolution NR update
unknown cell confirmation
Technical Details
LTE908 ANR for UTRAN - Fully UE based

Utran ANR Profile


• Profile (MOC: ANRPRW) is defined by
an operator user
• It is carrier-specific, indicating which
arfcn must be scanned by UE for ANR
purpose
• There is no default Profile in the eNB
even if LTE908 activation flag is set to
true
• Without ANR Profile feature does not
BTS SM default view on ANRPRW with default
work – minimum one profile must be values
defined and enabled
• Profile determines minimum WCDMA cell RSCP level for considering particular cell as
candidate for NR and the minimum EcNo level for ordering CGI decoding
18 • More details about
© Nokia Solutions andANR
NetworksProfile
2014 setting in Technical Details and Deployment Aspects part
For internal use
Searching of Detectability
Requirements Configuration CGI resolution NR update
unknown cell confirmation
Technical Details
LTE908 ANR for UTRAN - Fully UE based

• LTE908 creates neighbor relations only (MOCs: LNRELW and LNADJW if needed)
• However for PS HO (LTE56 HO to WCDMA), CSFB via PSHO and SRVCC additionally
MOC LNHOW is required
• LNHOW can be created
manually or
• by LTE783 ANR Inter RAT
UTRAN (based on
predefined template)

19 © Nokia Solutions and Networks 2014


For internal use
Searching of Detectability
Requirements Configuration CGI resolution NR update
unknown cell confirmation
Technical Details
LTE908 ANR for UTRAN - Fully UE based

Detection of unknown cells – 1/3


• Following cell statuses are used in particular LTE908 steps

Cell status Description


Unknown Utran cell • An UTRAN cell (i.e. a PSC) on an UTRAN carrier frequency, is ‘unknown’ to the eNB if
it is not in the neighbor relation of the respective eNB cell
• Not blacklisted and above predefined threshold in ANR Profile

Detected Utran cell • An UTRAN cell (i.e. a PSC) on an UTRAN carrier frequency, is ‘detected’ by the eNB if
it is included in a UE measurement report (as a request for reportStrongestCells or/and
reportCGI) means that PSC is known for eNB cell and it is not yet in the neighbor
relation of the UE serving cell

Resolved Utran cell • eNB knows CGI, LAC/RAC, PSC, UARFCN of the neighboring NB cell; Secondary
PLMN ID is an optional

Blacklisted cell • Utran cell PSC which is defined in pscBlacklist


(ANRPRW: • If the UE reports any of these PSC (e.g. via ReportStrongestCellsForSon) eNB will not
20 pscBlacklist[psc;pscLast]) ask
© Nokia Solutions and Networks for its resolution
2014
For internal use • As a consequence, there is no NR towards blacklisted cell
Searching of Detectability
Requirements Configuration CGI resolution NR update
unknown cell confirmation
Technical Details
LTE908 ANR for UTRAN - Fully UE based

Detection of unknown cells – 2/3


• Typically ANR features work in two search modes:
• Active Search mode – triggered by RRC Connection establishment/re-establishment or Incoming intra/inter-cell HO
• Passive Search mode – triggered by event (e.g. A3, A4, A5 for LTE556)
• LTE908 does not support Passive Search mode (respectively triggered by events B1, B2)
• UE looks for unknown UTRAN neighbor cell only in Active Search mode
• Active Search mode is divided into two sub-modes:
• Active Fast Search mode
• Active Slow Search mode

21 © Nokia Solutions and Networks 2014


For internal use
Searching of Detectability
Requirements Configuration CGI resolution NR update
unknown cell confirmation
Technical Details
LTE908 ANR for UTRAN - Fully UE based
Active Slow Search mode
sub-mode
Detection of unknown cells – 3/3
• One UE in defined time period is requested to measure and
to report strongest cell (reportStrongestCellsForSon)
• Triggers for Active Slow Search:
• When number of consecutive ReportStrongestCellsForSon
Active Fast Search mode measurements w/o ‘unknown cells’ received on a given
sub-mode
UTRAN carrier frequency reaches 50
• Each UE is requested to measure and to report strongest • or the number of neighbor relations created at the respective
cell (reportStrongestCellsForSon) UTRAN carrier frequency is equal to or greater than the
• Triggers for Active Fast Search: corresponding ANRPRW:lnrelwLimitForAnr value
• Used after feature activation • LNBTS:minNotActivatedUtraRSCFS defines the
• Cell restart minimum frequency according which a UTRAN carrier
• An ‘unknown cell’ is reported by a UE at the respective frequency in Slow Search mode is scanned for potential new
UTRAN carrier frequency (RSCFS) neighbor cell detection
• 24h is a default value causing that one UE per 24h is
requested to look for ‘unknown cell’
• If value 0 is selected, the respective UTRAN carrier
frequency will always be in Fast Active search (each capable
22 © Nokia Solutions and Networks 2014 UE is asked)
For internal use
Searching of Detectability
Requirements Configuration CGI resolution NR update
unknown cell confirmation
Technical Details
LTE908 ANR for UTRAN - Fully UE based

InterRAT UTRAN measurement activation


• According to 3GPP 36.133, if the UE requires measurement gaps to identify and measure
inter-frequency or interRAT cells, the eNB must provide a single measurement gap pattern with
constant gap duration for concurrent monitoring of all frequency layers and RATs.

• During the measurement gaps, the UE: Gp0 corresponds to Gap Pattern ID 0

‒ does not transmit any data Measurement Gap Length 6 ms


‒ is not expected to tune its receiver Measurement Gap Repetition Period 40ms
on the E-UTRAN serving carrier Minimum available time for inter- 60ms
frequency. frequency during 480ms period (Tinter1)
 instead, it tunes to neighbor Measurement Purpose Inter-Frequency E-UTRAN FDD and
cell TDD, UTRAN FDD, GERAN, LCR
TDD,HRPD, CDMA2000 1x

23 © Nokia Solutions and Networks 2014


For internal use
Searching of Detectability CGI
Requirements Configuration NR update
unknown cell confirmation resolution
Technical Details
overview
LTE908 ANR for UTRAN - Fully UE based

Measurement used for LTE908 purpose – 1/5

Measurement Description
ReportStrongestCells • Up to one, the strongest Utran cell is reported (arfcn taken from ANR UTRAN Profile)
ForSon • PSC to be measured is not specified means that known or ‘unknown cell’ might be reported
• Needed UE support (FIG bits 22, 19 (Rel’8) or 33 (Rel’9), 114 (Rel’10))
• Measurement can take long (UE will scan the full carrier before reporting)

ReportStrongestCells • Up to 8 Utran cells can be reported (it cause that measurement can take longer or shorter
time)
• UE reports ‘unknown cells’ only so there is the need to explicitly configure in the respective
measurement object which unknown PSCs the UE should look for
• Needed UE support (FIG bits 22, 16, 114 (Rel’10))

reportCGI • Only one, ‘detected cell' is resolved by reportCGI


• Needed UE support (FIG bits 22, 19 (Rel’8) or 33 (Rel’9), 114 (Rel’10))
• Measurement can take long (synchronization to specifies frequency, read MIB, SIB1 and SIB3,
CGI resolution)
24 © Nokia Solutions and Networks 2014
For internal use
Searching of Detectability CGI
Requirements Configuration NR update
unknown cell confirmation resolution
Technical Details
overview
LTE908 ANR for UTRAN - Fully UE based
NB
CellB,
UE Fy, eNB NetAct
Measurement used for LTE908 PSCx CellA, Fx, PCI#1

purpose – 2/5 Searching of unknown


ANR UTRA cell
• Measurements appear 1) RRC Connection Reconfiguration (reportStrongestCellsForSON)
subsequently

• Each of them is related to


different part of LTE908
reporting 3) RRC Connection Reconfiguration (reportStrongestCells(„unknown cell(s)”))
• Searching of unknown
ANR UTRA cell PSC detectability
• PSC detectability confirmation
confirmation 5) RRC Connection Reconfiguration (reportCGI(„unknown cell”))
• CGI resolution
• ‘Unknown cell’ must be
! 25 processed© Nokia
by all these
measurementsSolutions and Networks 2014
requests to
For internal use CGI resolution
become a neighbor relation
Searching of Detectability
Requirements Configuration CGI resolution NR update
unknown cell confirmation
Technical Details
overview
LTE908 ANR for UTRAN - Fully UE based
NB
CellB,
UE Fy, eNB NetAct
Measurement used for LTE908 PSCx CellA, Fx, PCI#1

purpose – 3/5 Searching of unknown


ANR UTRA cell
• Measurements appear 1) RRC Connection Reconfiguration (reportStrongestCellsForSON)
subsequently Unknown PSCs for Fy CellA list:
-‘unknown PSCx’
• Each of them is related to -…

different part of LTE908


reporting
• Up to one, the strongest cell is reported by the UE for
3) RRC Connection Reconfiguration (reportStrongestCells(„unknown cell(s)”))
reportStrongestCellsforSon request
• Searching of unknown
ANR UTRA cell • When reported cell is ‘unknown’ for eNB CellA,PSC
Fy,detectability
then
• PSC detectability confirmation
goes to the eNB stored unknown PSCs for Fy, CellA list
confirmation 5) RRC Connection Reconfiguration (reportCGI(„unknown cell”))
• PSCx on that list is kept and then used in LTE908 further
• CGI resolution
procedures
• ‘Unknown cell’ must be
processed by all these • each eNB cell has that kind of list for each ANR Profile
26
measurements © Nokia Solutions and Networks 2014
requests to defined frequency
For internal use CGI resolution
become a neighbor relation
Searching of Detectability CGI
Requirements Configuration NR update
unknown cell confirmation resolution
Technical Details
overview
LTE908 ANR for UTRAN - Fully UE based
NB
CellB,
UE Fy, eNB NetAct
Measurement used for LTE908 PSCx CellA, Fx, PCI#1

purpose – 4/5 Searching of unknown


ANR UTRA cell
• Measurements appear • eNB
1) RRCrequests
Connection UE for up to(reportStrongestCellsForSON)
Reconfiguration eight ‘unknown cells’ (from
subsequently the list) measurement evaluation
• Each of them is related to • MR report provides information about EcNo and
different part of LTE908 RSCP of up to eight cells
reporting 3) RRC Connection Reconfiguration (reportStrongestCells(„unknown cell(s)”))
• Searching of unknown
ANR UTRA cell PSC detectability
• PSC detectability confirmation
confirmation 5) RRC Connection Reconfiguration (reportCGI(„unknown cell”))
• CGI resolution
• eNB selects the cell with the
• ‘Unknown cell’ must be best EcNo for CGI resolution
processed by all these
27 © Nokia Solutions and Networks 2014
measurements requests to
For internal use CGI resolution
become a neighbor relation
Searching of Detectability CGI
Requirements Configuration NR update
unknown cell confirmation resolution
Technical Details
overview
LTE908 ANR for UTRAN - Fully UE based
NB
CellB,
UE Fy, eNB NetAct
Measurement used for LTE908 PSCx CellA, Fx, PCI#1

purpose – 5/5 Searching of unknown


ANR UTRA cell
1) RRC Connection Reconfiguration (reportStrongestCellsForSON)
These two procedures are
separated UE scans Fy looking for the strongest PSC to report
2) Measurement Report (reportStrongestCellsForSON)

UE involved in Searching of Inactivity detection


unknown ANR UTRA cell may be 3) RRC Connection Reconfiguration (reportStrongestCells(„unknown cell(s)”))
different from the UE which is
UE scans Fy looking for the strongest PSC to report
involved in further procedures. eNB PSC detectability
stores information about unknown 4) Measurement Report (reportStrongestCells) confirmation
cell and then requests some UE for 5) RRC Connection Reconfiguration (reportCGI(„unknown cell”))
further procedures. It might be
UE scans Fy looking for the CGI to report
executed subsequently or in later
phase (some conditions decides 6) Measurement Report (reportCGI)
7) Report Neighbor Information
when further procedure starts)
28 © Nokia Solutions and Networks 2014 8) RRC Connection Reconfiguration
For internal use CGI resolution
Searching of Detectability
Requirements Configuration CGI resolution NR update
unknown cell confirmation
Technical Details
LTE908 ANR for UTRAN - Fully UE based

• Next slides presents the messages exchanged between the UE and the eNB,
when UE is requested to measure and report the strongest PSC that it can
detect on a given UTRAN carrier frequency
• The selected UTRAN carrier frequency can be in Fast or in Slow active search
mode

Message flow
available with details:

29 © Nokia Solutions and Networks 2014


For internal use
Searching of Detectability
Requirements Configuration CGI resolution NR update
unknown cell confirmation
Technical Details Measurement
LTE908 ANR for UTRAN - Fully UE based activation

NodeB UE eNB NetAct


CellB, Fy, PSCx CellA, Fx, PCI#1

UE is capable of InterRAT UTRAN ANR measurements eNB CellA operates at frequency Fx


(i.e. FIG bit#33 and #22 set) and it supports both LTE Fx UTRAN ANR Profile created & enabled for Fy for NodeB CellA
and UTRAN Fy frequency band LTE908 feature enabled

When requirements (shown on grey boxes) are fulfilled then RRC Connection Reconfiguration* triggers the LTE908
feature (explicitly measConfig where reportConfigInterRAT purpose is set to ReportStrongestCellsForSON)

1) RRC Connection Reconfiguration (reportStrongestCellsForSON)

RRC Connection Reconfiguration Complete

*RRC
30
Connection Reconfiguration which is a part of the following procedures
© Nokia Solutions and Networks 2014
only:
For internal use
• RRC Connection establishment/re-establishment
Searching of Detectability
Requirements Configuration CGI resolution NR update
unknown cell confirmation
Technical Details Measurement
LTE908 ANR for UTRAN - Fully UE based activation

UE eNB
CellA, Fx, PCI#1

1) RRC Connection Reconfiguration (purpose:


• ReportStrongesCellsForSon is activated
reportStrongestCellsForSon) when:
measGaps
10ms [4ms scheduling + • No ReportCGI measurement is currently
RRC Connection Reconfiguration Complete 6ms gap] running at the UE
anrUtraTRSCFS starts
UE scans Fy looking for the • No event based inter-frequency or inter-
- ANR timer for Utran RSCFS
strongest PSC to report - default: 5sec RAT measurements activated at the UE
(i.e. no inter-frequency A3/A5 or inter-RAT
2) Measurement Report B2; no inter-RAT B1; no inter-frequency A4)
MeasResult: MeasId ‘X’ with no unknown PSCx
reported

2) Measurement Report
MeasResult: MeasId ‘X’ with an unknown PSCx
reported

31 © Nokia Solutions and Networks 2014


For internal use Continuation on next slide…
Searching of Detectability
Requirements Configuration CGI resolution NR update
unknown cell confirmation
Technical Details Measurement
LTE908 ANR for UTRAN - Fully UE based configuration

UE eNB
CellA, Fx, PCI#1

1) RRC Connection Reconfiguration (purpose: • eNB builds measurement configuration (MeasId:


reportStrongestCellsForSon, measId ‘X’, s- measGaps
‘X’) for ReportStrongesCellsForSon:
measure: 0) 10ms [4ms scheduling + • measObjectUTRA with WCDMA carrier
6ms gap]
RRC Connection Reconfiguration Complete defined in ANR Profile
anrUtraTRSCFS starts (ANRPRW:utraCarrierFreq)
UE scans Fy looking for the - ANR timer for Utran RSCFS
strongest PSC to report - default: 5sec • The cellsToAddModListUTRA-FDD
can consist only of PSCs defined up
2) Measurement Report to now as neighboring cells
MeasResult: MeasId ‘X’ with no unknown PSCx • reportConfigInterRAT with purpose
reported reportStrongestCellsForSon
2) Measurement Report • eNB activates measurement gaps
MeasResult: MeasId ‘X’ with an unknown PSCx
reported
• S-measure is set to ‘0’ to enforce measure of
WCDMA cell regardless of serving E-UTRA
RSRP level
32 © Nokia Solutions and Networks 2014
For internal use Continuation on next slide…
Searching of Detectability
Requirements Configuration CGI resolution NR update
unknown cell confirmation
Technical Details Measurement
LTE908 ANR for UTRAN - Fully UE based result verification

NB
CellB,
Fy, UE eNB
PSCx CellA, Fx, PCI#1

1) RRC Connection Reconfiguration (purpose: • UE scans UTRAN carrier and then sends one
reportStrongestCellsForSon, measId ‘X’ , s- measGaps Measurement Report with the strongest PSC (if
measure: 0) 10ms [4ms scheduling found) for Fy
RRC Connection Reconfiguration Complete + 6ms gap]
anrUtraTRSCFS starts • Scanning starts after RRC Connection
UE scans Fy looking for the - ANR timer for Utran Reconfiguration Complete is sent and till
strongest PSC to report RSCFS LNBTS:anrUtraTRSCFS expires
- default: 5sec
2) Measurement Report • eNB considers a PSCx at Fy as ‘unknown’, if
MeasResult: MeasId ‘X’ no • it is not an LNRELW CellA,
unknown PSCx reported • it is not in the ‘unknown PSC list for Fy of CellA’,
or
• it has been detected by the UE above defined
2) Measurement Report threshold (ANRPRW:anrUtraRscpThres)
MeasResult: MeasId ‘X’ with an • it is not blacklisted in ANR Profile
unknown PSCx reported

33 © Nokia Solutions and Networks 2014


For internal use Continuation on next slide…
Searching of Detectability
Requirements Configuration CGI resolution NR update
unknown cell confirmation
Technical Details Measurement
LTE908 ANR for UTRAN - Fully UE based result verification

UE eNB
CellA, Fx, PCI#1 • Internal eNB counter is incremented when MR w/o
unknown PSCx for Fy in CellA is reported

2) Measurement Report
(separate counter exists for each LTE cell and each
defined Utran carrier in ANR Profile)
MeasResult: MeasId ‘X’ no unknown
PSCx reported • Counter value = 50 is used to trigger switching from
eNB increments counter of RSCFS meas.report Fast to Slow Search mode
w/o unknown PSC for Fy in CellA • No further action takes place with no ‘unknown’
or reported PSC

2) Measurement Report
• The eNB restarts the counter (regardless the
MeasResult: MeasId ‘X’ with an
current value is) as soon as an unknown PSCx is
unknown PSCx reported
reported in MR
eNB resets counter of RSCFS meas.report w/o
unknown PSC for Fy in CellA • When internal eNB counter is above 50 while an
unknown PSCx is reported, eNB begins to search
Unknown PSCs for Fy CellA list: from Slow to Fast mode again (each UE is
-‘unknown PSCx’ requested)
34 -…Networks 2014
© Nokia Solutions and
For internal use • If sill below 50, eNB continues to search in Fast
Continuation on next slide… Search mode
Searching of Detectability
Requirements Configuration CGI resolution NR update
unknown cell confirmation
Technical Details Setting
LTE908 ANR for UTRAN - Fully UE based releasing

UE eNB
CellA, Fx, PCI#1

… • If reported PSC is ‘an unknown’ then eNB keeps


2) Measurement Report it on an ‘unknown PCSs for Fy CellA’ list for
MeasResult: MeasId ‘X’ with no unknown
anrUtraTRSCFS is next steps - PSC detectability confirmation &
released
PSCx reported CGI resolution
eNB increments counter of RSCFS meas.report • eNB sends RRC Connection Reconfiguration
or w/o unknown PSC for Fy in CellA when:
• MR is received by eNB (timer is released)
2) Measurement Report
MeasResult: MeasId ‘X’ with an unknown PSCx
anrUtraTRSCFS is • or LNBTS:anrUtraTRSCFS expires
released
reported without MR receiving
eNB resets counter of RSCFS meas.report w/o • Purpose is to release measurement gaps (if
unknown PSC for Fy in CellA established) and to restore s-measure settings
RRC Connection Reconfiguration
anrUtraTRSCFS expires
measConfig: meas gaps, if setup, are
released, S-measure restored
35 RRC Connection
© NokiaReconfiguration Complete
Solutions and Networks 2014
For internal use
UTRA PSC detectability confirmation is a continuation of LTE908 process. See on next slide…
Searching of Detectability CGI
Requirements Configuration NR update
unknown cell confirmation resolution
Technical Details
LTE908 ANR for UTRAN - Fully UE based

• Next slides present the messages exchanged between the UE and the eNB when
UE is requested to measure and report the strongest UTRA PSC(s) that it can
detect on a given UTRAN carrier frequency
• PSCs selected by the eNB for the UE are those to be resolved (CGI resolution)

Message flow
available with details:

36 © Nokia Solutions and Networks 2014


For internal use
Searching of Detectability
Requirements Configuration CGI resolution NR update
unknown cell confirmation
Technical Details Measurement
LTE908 ANR for UTRAN - Fully UE based activation

UE eNB NodeB NetAct


CellA, Fx, PCI#1 CellB, Fy, PSCx

UE is capable of InterRAT UTRAN ANR measurements eNB CellA operates at frequency Fx


(i.e. FIG bit#33 and 22 set) and periodical UTRAN ANR Profile created & enabled for Fy for NodeB CellA
measurements (FIG bit#16 set) and it supports both LTE Unknown PSC list for Fy at CellA not empty
Fx and UTRAN Fy frequency band LTE908 feature enabled

RRC connected

3) RRC Connection Reconfiguration ReportStrongestCells is activated when:


(purpose: reportStrongestCells) • UE inactive for 5 sec time period in RRC
Connection state
• No event based inter-frequency/RAT running
• No ReportCGI and no
ReportStrongestCellForSon measurements
are currently running at the UE
37 © Nokia Solutions and Networks 2014
For internal use • There is at least one ‘unknown PSC’
Continuation on next slide…
Searching of Detectability
Requirements Configuration CGI resolution NR update
unknown cell confirmation
Technical Details Measurement
LTE908 ANR for UTRAN - Fully UE based configuration

UE eNB
CellA, Fx, PCI#1
Unknown PSCs for Fy CellA list: • eNB builds reportStrongestCells to measure
-‘unknown PSCx’
-… indicated PSCs (taken from the ‘unknown PSCs
list for Fy CellA’)
3) RRC Connection Reconfiguration
(purpose: reportStrongestCells) • A measObjectUTRA with the respective PSC(s)
measGaps to measure is provided for the selected UTRAN
MeasConfig: MeasIDs ‘X’ for RSC on Fy, 10ms [4ms scheduling +
6ms gap] carrier frequency
meas gaps setup if needed, s-
measure: 0 • The cellsToAddModListUTRA-FDD in
RRC Connection Reconfiguration Complete 2,5 sec. timer for the measurement object must be filled
Utran RSC starts with the ‘unknown PSC(s)’ collected so
UE scans Fy looking for the far from the respective UTRAN carrier
indicated PSCs to report frequency

4) Measurement Report • eNB activates measurement gaps


timer for Utran RSC is released
MeasResult: MeasId ‘X’ with an indicated PSC • S-measure is set to ‘0’ to enforce measure of
reported or WCDMA cell(s) regardless of serving E-UTRA
timer for Utran RSC expires RSRP level (similarly like for RSCFS)
38 © Nokia Solutions and Networks 2014
For internal use Continuation on next slide…
Searching of Detectability
Requirements Configuration CGI resolution NR update
unknown cell confirmation
Technical Details
Measuring
LTE908 ANR for UTRAN - Fully UE based

NB
CellB,
Fy, UE eNB
PSCx CellA, Fx, PCI#1
Unknown PSCs for Fy CellA list:
-‘unknown PSCx’
-…

3) RRC Connection Reconfiguration • UE scans UTRAN carrier. If indicated PSC(s) is


(purpose: reportStrongestCells) measGaps found then UE sends Measurement Report
MeasConfig: MeasIDs ‘X’ for RSC on Fy, 10ms [4ms scheduling +
meas gaps setup if needed s-measure: 0 6ms gap] • Scanning starts after RRC Connection
Reconfiguration Complete is sent
RRC Connection Reconfiguration Complete 2,5 sec. timer for
Utran RSC starts • Measurement Report must be sent till timer for
UE scans Fy looking for the Utran RSC (2,5 sec) expires. Otherwise, MR is
indicated PSCs to report ignored by the eNB and ‘detectability
confirmation’ starts from the beginning
4) Measurement Report (according to requirements from slide)
timer for Utran RSC is released
MeasResult: MeasId ‘X’ with an
or
indicated PSC(s) reported
timer for Utran RSC expires
39 © Nokia Solutions and Networks 2014
For internal use Continuation on next slide…
Searching of Detectability
Requirements Configuration CGI resolution NR update
unknown cell confirmation
Technical Details Measurement result
LTE908 ANR for UTRAN - Fully UE based verification and
settings releasing

NodeB
CellB,
Fy, UE eNB
PSCx CellA, Fx, PCI#1

UE scans Fy looking for the


indicated PSCs to report • From up to eight reported PSCs only one is
chosen by eNB for CGI resolution:
4) Measurement Report • PSC with the strongest EcNo (greater then or
timer for Utran RSC is released
MeasResult: MeasId ‘X’ with an equal to predefined ANRPRW:anrEcNoThres
indicated PSCs reported value). Else, when EcNo measurement is not
present, then eNB selects PSC having the
highest RSCP from the list of cells reported in
5) RRC Connection Reconfiguration RSC measurement whatever the value
(purpose: reportCGI) • It is not an LNRELW for CellA
(MeasConfig: ANR DRX#102 profile is setup and meas. Gaps • It is not blacklisted in ANR Profile
released if present, s-measure restored; MeasIDs ‘X’ for
ReportCGI for (PSCx;Fy) is activated) • MeasGaps releasing and S-measure restore take
place with request for reportCGI (GCI resolution)
and DRX setup

40 © Nokia Solutions and Networks 2014


For internal use Continuation on next slide…
Searching of Detectability CGI
Requirements Configuration NR update
unknown cell confirmation resolution
Technical Details
DRX configuration
LTE908 ANR for UTRAN - Fully UE based

UE eNB DRX Profile 102


CellA, Fx, PCI#1
• UE performs UL and DL traffic scheduling
5) RRC Connection Reconfiguration using a long DRX profile specific for Inter-
(purpose: reportCGI)
RAT UTRAN ANR measurements. This
(MeasConfig: ANR DRX#102 profile is setup and meas. gaps released occurs during the sleep mode (1280ms),
if present, MeasIDs ‘X’ for ReportCGI for (PSCx;Fy) is activated)
long enough for SIB reading

• Since this DRX profile is configured in cell-


level, each cell may have different child
parameter value

• LTE908 does not consider LTE42/473 as a


mandatory feature. Therefore, actDRX flag
does not need to be set to “true". If not
activated, DRX will be applied only for
ANR measurements, but not for power
LTE 473 - Extended DRX Technical Description / Krzysztof Golebiewski saving.
41 © Nokia Solutions and Networks 2014
For internal use
Searching of Detectability CGI
Requirements Configuration NR update
unknown cell confirmation resolution
Technical Details Measurement
LTE908 ANR for UTRAN - Fully UE based activation

UE eNB
CellA, Fx, PCI#1 • Measurement reportCGI is used to resolve CGI
5) RRC Connection Reconfiguration • Requirements for reportCGI measurement
(purpose: reportCGI) activation:
(MeasConfig: ANR DRX#102 profile is setup and meas. Gaps released if • Actual UE bearer configuration is compatible
present, s-measure restored; MeasIDs ‘X’ for ReportCGI for with DRX profile needed for UTRAN ANR
(PSCx;Fy) is activated)
8,2 sec. timer for Utran • No event based inter-RAT (B1/B2) or Inter-Freq
RRC Connection Reconfiguration Complete
Report CGI starts (A3/A4/A5) mobility measurement are currently
UE tries to synchronise with the active at the UE
UTRAN cell having (PSCx; Fy) and • No reportCGI measurement currently running at
to read its SIB1 and SIB3 the UE
6) Measurement Report
MeasResult: MeasId ‘X’ with CGI, LAC, RAC,
PLMN ID list reported

timer for Utran Report


CGI is stopped

42 © Nokia Solutions and Networks 2014


For internal use Continuation on next slide…
Searching of Detectability CGI
Requirements Configuration NR update
unknown cell confirmation resolution
Technical Details
Measuring
LTE908 ANR for UTRAN - Fully UE based

NodeB UE eNB
CellB, CellA, Fx, PCI#1
Fy,
PSCx
5) RRC Connection Reconfiguration • Timer for Utran Report CGI (8,2* sec.) defines
(purpose: reportCGI) time for synchronization to specifies frequency, read
(MeasConfig: ANR DRX#102 profile is setup and meas. Gaps released if MIB, SIB1 and SIB3, CGI resolution and sent
present, MeasIDs ‘X’ for ReportCGI for (PSCx;Fy) is activated) Measurement Report
RRC Connection Reconfiguration Complete
8,2 sec. timer for Utran • Measurement Report must be sent till 8,2 sec
Report CGI starts
expires. Otherwise, MR is ignored by eNB
UE tries to synchronize with the
UTRAN cell having (PSCx; Fy) and
• Following information must be taken from
to read its MIB, SIB1 and SIB3 WCDMA cell:
6) Measurement Report •PLMN (from MIB)
timer for Utran Report
CGI
CGI is released •Cell Id (i.e. LCID, from SIB3)
or
timer for Utran Report
•LAC (from SIB1 and RAC if contained)
CGI expires

43 © Nokia Solutions and Networks 2014 *ReportCGI is a periodical measurement reported by the UE only once, when the measurement
For internal use Continuation on next slide… result is available or T321 timer expires. T321 timer is defined by 3GPP with value set to “8”
second (see TS36.331 for more details). That is the reason that eNB waits 8,2 sec. for MR.
Searching of Detectability CGI
Requirements Configuration NR update
unknown cell confirmation resolution
Technical Details
Measuring
LTE908 ANR for UTRAN - Fully UE based

NodeB UE eNB NetAct


CellB, CellA, Fx, PCI#1
Fy,
PSCx
6) Measurement Report
timer for Utran Report • eNB receives Measurement Report with reportCGI
MeasResult: MeasId ‘X’ with CGI, LAC, CGI is released
RAC, PLMN ID list reported (optional) measurement results of the CellA of PSCx on Fy.
eNB removes PSCx from the respective unknown • eNB stores information about a neighbor UTRA cell
PSC list, creates LNRELW object for CellA if possible only when all mandatory results are completed –
and corresponding LNADJW object if not yet available
resolved cell (CGI, LAC and RAC if contained)
7) Report Neighbor information • When PSCx of Fy CellA is added as a NR then is
removed form the ‘Unknown PSCs for Fy CellA
list’
or
6) Measurement Report
timer for Utran Report
MeasResult: MeasId ‘X’ but no CGI CGI is released
If the Measurement Report results are not completed
and/or RAC is included (e.g. CGI or/and LAC/RAC is missing) then eNB
eNB discards the message discards the UE report. PSCx remains in the
timer for Utran Report respective unknown PSC list till next request for RSC
44 © Nokia Solutions and Networks 2014
CGI expires
For internal use Continuation on next slide…
Searching of Detectability CGI
Requirements Configuration NR update
unknown cell confirmation resolution
Technical Details Settings
LTE908 ANR for UTRAN - Fully UE based releasing

UE eNB NetAct
CellA, Fx, PCI#1

• eNB sends RRC Connection Reconfiguration


6) Measurement Report when:
timer for Utran Report
MeasResult: MeasId ‘X’ with CGI, LAC, RAC,
CGI is released
PLMN ID list reported (optional) • MR is received by eNB (timer is released)
eNB removes PSCx from the respective unknown • or timer for Utran Report CGI (8,2 sec.)
PSC list, creates LNRELW object for CellA if possible expires without MR receiving
and corresponding LNADJW object if not yet available

7) Report Neighbor information


• RRC Connection Reconfiguration releases DRX
profile#102

RRC Connection Reconfiguration


timer for Utran Report
measConfig: DRX profile#102 is CGI expires
released

RRC Connection Reconfiguration Complete


45 © Nokia Solutions and Networks 2014
For internal use
Searching of Detectability NR
Requirements Configuration CGI resolution
unknown cell confirmation update
Technical Details
LTE908 ANR for UTRAN - Fully UE based

NodeB UE eNB NetAct


CellB, CellA, Fx, PCI#1
Fy,
PSCx • Finally, the eNB communicates the newly resolved
6) Measurement Report UTRAN neighbor cell configuration information to the
timer for Utran Report CGI is
MeasResult: MeasId ‘X’ with CGI, LAC, RAC, stopped NetAct via Cell Change Notification (CCN)
PLMN ID list reported
• LNRELW and LNADJW (if not exists yet) are created
eNB removes PSCx from the respective unknown
PSC list, creates LNRELW object for CellA if possible • eNB includes in the CCN the context information for
and corresponding LNADJW object if not yet available SON report, i.e. the indication that LTE908 has been
the reason for the change (LNADJW:sourceOfData).
7) Report Neighbor information
• When limit of NR via ANR for Fy in CellA
(ANRPRW:lnRelWLimitForAnr) is reached then
LNRELW (and LNADJW if not exists yet) is not
RRC Connection Reconfiguration created
measConfig: DRX profile#102 is released
• The UE reported measurement result is
RRC Connection Reconfiguration Complete discarded, eNB rises an alarm and Active Slow
Search mode applies
46 © Nokia Solutions and Networks 2014
For internal use Continuation on next slide…
Searching of Detectability NR
Requirements Configuration CGI resolution
unknown cell confirmation update
Technical Details
LTE908 ANR for UTRAN - Fully UE based
CGI resolution for PSCs on Fy – 6/X LNBTS (1..1)
lnBtsId, MCC, MNC,… …

LNADJW(1..256): LNCEL(1..x):
 InAdjWId
 primaryPlmnId [mcc, mnc,
mnc Length]
Resolved CGI (as a  uTargetCid
response for reportCGI)  uTargetRncId
 secondaryPlmnId [mcc, LNRELW(1..256):
mnc, mnc Length]  lnRelWId
‘unknown PSC’   uTargetScFdd  plmnId
Carrier defined in Profile   uTargetFreq Resolved CGI (as a
 UTargetRncId
SRVCC setting from Profile   srvccHoInd response for reportCGI)
 UTargetCid
(default settings: PS and CS)  uTargetLac
 srvccAllowed
LAC and RAC delivered as  uTargetRac Taken from ANR Profile
 psHoAllowed
response for reportCGI (default setting is
 csfbPsHoAllowed
‘allowed’ for all of them)
47 © Nokia Solutions and Networks 2014  ...
For internal use
Searching of Detectability NR
Requirements Configuration CGI resolution
unknown cell confirmation update
Technical Details
LTE908 ANR for UTRAN - Fully UE based
CGI resolution for PSCs on Fy – 6/X LNBTS (1..1)
lnBtsId, MCC, MNC,… …

LNADJW(1..256): LNCEL(1..x):
• If the reported CGI points to an
 InAdjWId
 primaryPlmnId [mcc, mnc,
existing LNADJW but for a different
mnc Length] PSC and/or freq., then this LNADJW
 uTargetCid is updated (i.e. PSC and/or freq. set to
 uTargetRncId “PSCx” and “Fy”) and existing
 secondaryPlmnId [mcc, LNRELW(1..256):
mnc, mnc Length]  lnRelWId
LNRELW(s) in CellA or other eNB cells
 uTargetScFdd  plmnId pointing to that LNADJW are kept or
 uTargetFreq deleted depending on specific
 UTargetRncId
 srvccHoInd condition
 UTargetCid
 uTargetLac
 srvccAllowed
 uTargetRac
 psHoAllowed
 csfbPsHoAllowed
48 © Nokia Solutions and Networks 2014  ...
For internal use
Searching of Detectability CGI
Requirements Configuration NR update
unknown cell confirmation resolution
Technical Details
Inactivity timer
LTE908 ANR for UTRAN - Fully UE based

Does inactivity timer impact PSC detectability confirmation and CGI resolution?
• LNCEL:InactivityTimer is restarted in eNB by traffic on DRB (U-plane) only
• C-plane (e.g.: RRC Connection Reconfiguration) does not restart that timer
• For CGI resolution UE must stay in Connected Mode state till MR with resolved CGI is received
• Transition to Idle Mode (when inactivity expires) releases reportConfigInterRat ReportStrongestCells is
causing that MR will not be delivered activated when:
• For ANR UTRAN purpose, when: • UE inactive for 5 sec.time
period
UE inactive for 5 sec.time period + timer for Utran RSC (2,5 sec.) +
• No event based inter-
timer for Utran Report CGI (8,2 sec.) > inactivity timer frequency/RAT running
• Then inactivity timer is set to: 15,7 sec. (5+2,5+8,2) causing that UE • No ReportCGI and no
will be kept in Connected Mode till finish CGI resolution ReportStrongestCellForSon
measurements are currently
• Conclusion: no actions are needed whatever the inactivity timer running at the UE
value when LTE908 enabled • There is at least one ‘unknown
49 © Nokia Solutions and Networks 2014 PSC’
For internal use
Let’s have a short coffee break!

50 © Nokia Solutions and Networks 2014


For internal use
LTE908 ANR for UTRAN – Fully UE based

Interdependencies

Table of contents

51 © Nokia Solutions and Networks 2014


For internal use
Interdependencies

extensions LTE1342 Extended RNC identity (RL60)


CGI=PLMN + LCID (RNC-ID + UTRAN Cell ID)

standard or extension
• Standard: 12 bit RNC-ID (range 0..4095) and a 16 bit UTRAN Cell ID (range
0..65535)
• Extension made by LTE1342: 16 bit RNC-ID (range 0.. 65535) and a 12 bit UTRAN
Cell ID (range 0..4095)
• Extended RNC Id purpose is to support increased number of RNC Ids for I-HSPA
• The extended RNC ID IE is used within the S1AP:HandoverRequired message in case
that the RNC ID has a value larger than 4095
• Extended RNC ID is supported for WCDMA cells only (no TD-SCDMA)
• RNC coding must be defined in ANR Profile based on following parameters:
• ANRPRW:rncIdCoding [rncIdAllignment; rncIdType]
52 • A mix
© Nokia Solutions and Networks 2014 of ‘extended’ and 'normal' RNC IDs per carrier frequency is not supported.
For internal use
Interdependencies

extensions LTE783 ANR Inter-RAT UTRAN (O&M RL30/25TD)


LTE783 extends LTE908 by adding LNHOW, UFFIM and REDRT objects.
Handover, Idle Mode mobility and redirection are not possible without
these objects.

53 © Nokia Solutions and Networks 2014


For internal use
Interdependencies

extensions LTE56 Inter-RAT Handover to WCDMA


LTE736 CS Fallback to UTRAN
LTE872 SRVCC to WCDMA
• All these features require
neighbor relation to WCDMA
• NR might be done manually or
based on LTE783 or LTE908
• ANR Profile settings give
possibility to enable particular
mobility feature per NR
(LNRELW settings are taken
from the ANR Profile) however
activation flag setting (LNBTS
object) is independent
54 © Nokia Solutions and Networks 2014
For internal use
Interdependencies

extensions LTE507 Optimization of inter-RAT neighbors (O&M


RL50/35TD)
• LTE507 gives possibility
to verify NR
performance based on
aggregated PM data
• As a consequence poor
performing mobility
feature is blacklisted
(e.g.
srvccAllowed=forbidden)

LTE507 NEI slide set


55 © Nokia Solutions and Networks 2014
For internal use
Interdependencies

extensions LTE1043-B 3GPP baseline June 2012


•3GPP Rel’10 introduces FIG bits extension (Rel’9: up 64 bits;
Rel’10 up to 128 bits) For details please refer to ‘Technical
details’ part (link)
LTE1446 SON reports for decentral ANR features
•When NR is created via LTE908 and LTE1446 is enabled then
this particular NR is marked in NetAct as that autonomously
created via LTE908 (e.g.: 59: eNB - ANR UTRAN fully UE
based)

56 © Nokia Solutions and Networks 2014


For internal use
Interdependencies

limitations LTE556 Inter-frequency UE based ANR (RL60/45TD)


LTE782 LTE intra-frequency UE based ANR (RL30/25TD)
All these features can be configured with LTE908 simultaneously. This causes that intra/inter
cell incoming HO (either via RRC Connection reconfiguration or RC Connection
Reestablishment) or connection setup fulfils requirements enabling UE for ANR measurement:
Intra LTE, inter-frequency and inter-RAT Utran (of course UE must support specified FIGs for
each technology).
eNB enforces UE to perform UE based ANR measurements for one technology type
only (e.g. either LTE or UTRAN) during the life time of its RRC connection
eNB points on which technology to enable ANR measurements
• eNB stores for each technology type enabled to UE based ANR the information about when it
has been last time selected for a UE
• one having the oldest selection time is chosen for ANR measurement (RSCFS for UTRAN or
RSC for intra-frequency or inter-frequency)
• The starting position of the pointer is initialized to LTE when the eNB cell (re-)starts
57 © Nokia Solutions and Networks 2014
For internal use
Link to CRL2307 (jira)
Interdependencies

extension LTE42 DRX in RRC connected mode


•DRX mechanism is reused for ReportCGI measurement
however feature LTE42 does not need to be enabled
(LNBTS:actDRX flag does not need to be set to ‘true’)
• If LTE42 is deactivated, after CGI is reported or time for it expires DRX
is deactivated at all
•DRX settings are defined in drxProfile102 for LTE908

58 © Nokia Solutions and Networks 2014


For internal use
Interdependencies

extensions LTE4 RAN Sharing (MOCN)


LTE908 NR creation when RAN sharing with WCDMA is enabled
Configuration on 3G site:
- Common PLMN
- additional PLMN - 1
- additional PLMN – 2
- …
‘Common PLMN’ from WCDMA is located as a LNADJW: primaryPlmnId.
Others, additional PLMNs would be stored in Target secondary PLMN ID list
(up to 5) – LNADJW:secondaryPlmnIdL
LNRELW has option for one PLMN (Primary PLMN Id) only and it is ‘Common
PLMN’. The role of this PLMN in LNRELW is to identify from which LNCEL to
which WCDMA cell (LNADJW) neighbor relation exist (is created) as it is
presented here.
59 © Nokia Solutions and Networks 2014
For internal use
LTE908 ANR for UTRAN – Fully UE based

Benefits and Gains

Table of contents

60 © Nokia Solutions and Networks 2014


For internal use
Benefits and Gains
LTE908 ANR for UTRAN - Fully UE based

Automatic detection and No user/ Only relevant NR are


setup of neighbor relation from operator added
LTE towards WCDMA action is
needed for NR LTE908 based on signal quality
adding (defined in ANR Profile) during NR
candidates evaluation

Full flexibility in NR creation  user defines ANR profile New PM counter


dedicated to particular WCDMA frequency where: for supervision of CGI
resolution (attempt, success,
incomplete)
• specifies quality thresholds,
• Enables/disables particular mobility features per NR,
• limits new NR amount (if needed)

61 © Nokia Solutions and Networks 2014


For internal use
LTE908 ANR for UTRAN – Fully UE based

Configuration
Management
Table of contents

63 © Nokia Solutions and Networks 2014


For internal use
Configuration Management

Definition of terms and rules for parameter classification*


The ‘Basic Parameters’ category contains The ‘Advanced Parameters’ category contains
primary parameters which should be considered the parameters for network optimisation and fine
during cell deployment and must be adjusted to a tuning:
particular scenario:
• Decent network performance should be achieved without tuning
• Network Element (NE) identifiers these parameters
• Planning parameters, e.g. neighbour definitions, frequency, • Universal defaults ensuring decent network performance need to
scrambling codes, PCI, RA preambles be defined for all parameters of this category. If this is not
• Parameters that are the outcome from dimensioning, i.e. basic possible for a given parameter it must be put to the ‘Basic
parameters defining amount of resources Parameters’ category
• Basic parameters activating basic functionalities, e.g. power • Parameters requiring detailed system knowledge and broad
control, admission control, handovers experience unless rules for the ‘Basic Parameters’ category are
• Parameters defining operators’ strategy, e.g. traffic steering, violated
thresholds for power control, handovers, cell reselections, basic • All parameters (even without defaults) related to advanced and
parameters defining feature behaviour very complex features

* - purpose: categories of parameters have been defined to simplify network parameterization. Parameterization effort shall be focused mainly on parameters included in basic
category. Categorization is reflected in a ‘view’ definition in NetAct CM Editor (released in RL60/45TD) i.e. parameters will be displayed according to the category: either in the ‘Basic
parameters’ view or the ‘Advanced parameters’ view.

64 © Nokia Solutions and Networks 2014


For internal use
Configuration Management
New parameters Basic

Abbreviated name Full name PKDB link

LNBTS:actUeBasedAnrUtran Activate UE-based ANR for UTRAN

ANRPRW:anrPrWId ANR profile for WCDMA identifier

ANRPRW:utraCarrierFreq UTRAN carrier frequency

ANRPRW:anrUtraRscpThres ANR UTRA RSCP threshold

ANRPRW:rncIdCoding:rncIdAlign
Alignment within UTRAN CI
ment

ANRPRW:rncIdCoding:rncIdtype RNC ID type

65 © Nokia Solutions and Networks 2014


For internal use
Configuration Management
New parameters Advanced

Abbreviated name Full name PKDB link

ANRPRW:enableAnrProfile Enable ANR profile

ANRPRW:anrUtraEcNoThres ANR UTRA EcNo threshold

ANRPRW:cellsToApplyList Cells to apply list

ANRPRW:lnRelWDefaults:csfbPsHoAllo Circuit-switched fallback with


wed PS handover allowed

ANRPRW:lnRelWDefaults:PsHoAllowed PS handover allowed

Single radio Voice call


ANRPRW:lnRelWDefaults:srvccAllowed
continuity allowed

ANRPRW:srvccHoInd SRVCC HO indication


66 © Nokia Solutions and Networks 2014
For internal use
Configuration Management
New parameters Advanced

Abbreviated name Full name PKDB link


Limit for ANR created UTRAN
ANRPRW:lnRelWLimitForAnr
neighbor relations

ANRPRW:pscBlacklist:psc Primary scrambling code

Last primary scrambling code of


ANRPRW:pscBlacklist:pscLast
a range

LNADJW:sourceOfData Source of data

LNBTS:anrUtraTRSCFS ANR UTRA RSCFS timer

Minimum not activated UTRA


LNBTS:minNotActivatedUtraRSCFS
reportStrongestCellsForSon

67 © Nokia Solutions and Networks 2014


For internal use
Configuration Management
New parameters Advanced

Abbreviated name Full name PKDB link

LNCEL:drxprofile102:drxProfileIndex DRX profile index

LNCEL:drxprofile102:drxInactivityT DRX inactivity timer

LNCEL:drxprofile102:drxLongCycle DRX long cycle

LNCEL:drxprofile102:drxOnDuratT DRX on duration timer

LNCEL:drxprofile102:drxProfilePriority DRX profile priority

LNCEL:drxprofile102:drxRetransT DRX retransmission timer

68 © Nokia Solutions and Networks 2014


For internal use
Configuration Management
Related parameters

Abbreviated name Full name PKDB link

LNCEL:threshold2Wcdma Threshold th2 WCDMA for RSRP

LNCEL:inactivityTimer Inactivity timer

69 © Nokia Solutions and Networks 2014


For internal use
LTE908 ANR for UTRAN – Fully UE based

Deployment
Aspects
Network graphic boxes Network element boxes
Table of contents

70 © Nokia Solutions and Networks 2014


For internal use
BTS level Cell level
configuration configuration
Deployment Aspects
LTE908 ANR for UTRAN - Fully UE based

Activation and deactivation of this optional feature can be done in eNB level, through the
parameter:
• actUeBasedAnrUtran (deactivated by default)

71 © Nokia Solutions and Networks 2014


For internal use
BTS level Cell level
configuration configuration
Deployment Aspects
LTE908 ANR for UTRAN - Fully UE based

Define the maximum time that the eNB waits for WCDMA ReportStrongestCellsForSon
measurement report from UE:
• anrUtraTRSCFS (5 sec by default)

72 © Nokia Solutions and Networks 2014


For internal use
BTS level Cell level
configuration configuration
Deployment Aspects
LTE908 ANR for UTRAN - Fully UE based

Utran ANR Carrier Profile – 1/5


• There is no default Profile in the eNB
even LTE908 activation flag is set to true
• Without ANR Profile feature does not
work – minimum one profile must be
defined (ANRPRW:anrPrWId) and
enabled
(ANRPRW:enableAnrProfile=‘true’)

BTS SM default view on ANRPRW Properties


• Profile determines minimum WCDMA cell quality value for considering it
as ‘an unknown cell’:
• RSCP  ANRPRW:anrUtraRscpThres

73
• And the minimum EcNo level for ordering CGI decoding
© Nokia Solutions and Networks 2014

• EcNo  ANRPRW:anrUtraEcNoThres
For internal use
BTS level Cell level
configuration configuration
Deployment Aspects
LTE908 ANR for UTRAN - Fully UE based

Utran ANR Carrier Profile – 2/5


‒ Typically ANR profile must have unique target carrier frequency (ANRPRW:utraCarrierFreq)
• BTSSM checks profiles and will trigger an error* if duplicated frequency has been detected
• When feature is configured from NetAct, there are validation errors when provisioning the plan

*some exception on next slide


74 © Nokia Solutions and Networks 2014
For internal use
BTS level Cell level
configuration configuration
Deployment Aspects
LTE908 ANR for UTRAN - Fully UE based

Utran ANR Carrier Profile – 3/5


‒ RNC coding (RNC ID 3GPP 25.331)
Extended RNC Id purpose is to support
increased number of RNC Ids for I-HSPA
interworking
‒ ANRPRW:rncIdCoding:rncIdAlignment is
mandatory parameter

‒ LNRELW default values


(ANRPRW:lnRelWDefaults) gives possibility
to control (allowed/forbidden) CSFB, PS HO
and SRVCC from NR point of view

75 © Nokia Solutions and Networks 2014


For internal use
BTS level Cell level
configuration configuration
Deployment Aspects
LTE908 ANR for UTRAN - Fully UE based

Utran ANR Carrier Profile – 4/5


‒ optional structures:
‒ Cells to apply list (ANRPRW:cellsToApplyList) - parameter allows to restrict the Profile to
certain LTE cells that are identified by their LNCEL:lncelId
‒ CTAL gives possibility to use the same (ANRPRW:utraCarrierFreq) in different Profiles while each of
these Profiles must have different content of CTAL list (maximal of one ANRPRW instance with empty/
omitted cellsToApplyList allowed within the same utraCarrierFreq)
‒ As a consequence, several ANR Profiles with the same arfcn (ANRPRW:utraCarrierFreq) while dedicated
to different LTE cells (LNCEL:lncelId) are supported

76 © Nokia Solutions and Networks 2014


For internal use
BTS level Cell level
configuration configuration
Deployment Aspects
LTE908 ANR for UTRAN - Fully UE based

Utran ANR Carrier Profile – 5/5


‒ optional structures:
‒ List of blacklisted PSCs (ANRPRW:pscBlacklist[psc;pscLast]) - parameter specifies a list of
Primary Scrambling Codes (PSC) or code ranges that are excluded from ANR learning
‒ Psc is mandatory parameter in that optional structure.
‒ When pscLast is provided then all Scrambling Codes starting from psc to pscLast are blacklisted (NR is
created for these defined PSCs while mobility procedures have status ‘forbidden’)

77 © Nokia Solutions and Networks 2014


For internal use
Scenario 1 Scenario 2 Scenario 3 Scenario 4 Scenario 5 Scenario 6
Deployment Aspects
LTE908 ANR for UTRAN - Fully UE based

Scenarios – 1/13
• Scenario 1 – Typical scenario (UE is attaching to LTE cell, UE is in the overlapping area of the cells,
WCDMA measurement not started)
• Feature activation flag set to true, ANR Profile created

RSCP = -110 dBm = RSRP = -85dBm = Threshold


ANRPRW threshold “ANR 2 WCDMA for RSRP
UTRA RSCP threshold“
LTE eNB 3G BTS

ANR works properly

Typically threshold2WCDMA=-115 dBm while for


test purpose -85 dBm is considered
78 © Nokia Solutions and Networks 2014
For internal use
Trials & Pilots OAM test results, Otto Koch, SON.7015 LTE908 ANR Inter-RAT UTRAN – Fully UE based, V1.0 2014-11-10
Scenario 1 Scenario 2 Scenario 3 Scenario 4 Scenario 5 Scenario 6
Deployment Aspects
LTE908 ANR for UTRAN - Fully UE based

Scenarios – 2/13
• Scenario 1 – Typical scenario (UE is attaching to LTE cell, UE is in the overlapping area of the cells,
WCDMA measurement not started)

Attach complete
• During Attach procedure UE is
requested (via RRC
Connection Reconfiguration
message) for
reportStrongestCellsForSon
• A WCDMA cell is found
• UE sends MR – see picture
(anrUtraRscpThres fullfilled) rsrpResult 62  -140+62= [-79..-78) dBm

• This cell is considered as an


‘unknown cell’
Utra-RSCP 37  -120+5+37 = [-79..-78) dBm
79 © Nokia Solutions and Networks 2014
For internal use
Trials & Pilots OAM test results, Otto Koch, SON.7015 LTE908 ANR Inter-RAT UTRAN – Fully UE based, V1.0 2014-11-10
Scenario 1 Scenario 2 Scenario 3 Scenario 4 Scenario 5 Scenario 6
Deployment Aspects
LTE908 ANR for UTRAN - Fully UE based

Scenarios – 3/13
~ 107 seconds
• Scenario 1 – Typical scenario
Confirmation of strongest
(UE is attaching to LTE cell, UE unknown WCDMA neighbor cell
is in the overlapping area of the
cells, WCDMA measurement not
started) ~ 5 seconds

• UE is not used for any data during at


least 5 sec. (timer expires)
• UE is requested for
reportStrongestCells for that CGI resolution
‘unknown cell’ UTRA

• Nextly, CGI resolution for that ‘detected


cell’
• Cell is ‘resolved’
• LNADJW and LNRELW objects, for the
80WCDMA cell, are created
© Nokia inNetworks
Solutions and the eNB 2014
For internal use
Trials & Pilots OAM test results, Otto Koch, SON.7015 LTE908 ANR Inter-RAT UTRAN – Fully UE based, V1.0 2014-11-10
Scenario 1 Scenario 2 Scenario 3 Scenario 4 Scenario 5 Scenario 6
Deployment Aspects
LTE908 ANR for UTRAN - Fully UE based

Scenarios – 4/13
• Scenario 2 – A2 event (UE is attaching to LTE cell, UE is in the overlapping area of the cells, event
A2 condition reached – WCDMA measurement starts)
• Feature activation flag set to true, ANR Profile created

RSCP = -110 dBm = RSRP = -85dBm = Threshold


ANRPRW threshold “ANR 2 WCDMA for RSRP
UTRA RSCP threshold“
LTE eNB 3G BTS

ANR does not work

Typically threshold2WCDMA=-115 dBm while for


81 © Nokia Solutions and Networks 2014 test purpose -85 dBm is considered
For internal use
Trials & Pilots OAM test results, Otto Koch, SON.7015 LTE908 ANR Inter-RAT UTRAN – Fully UE based, V1.0 2014-11-10
Scenario 1 Scenario 2 Scenario 3 Scenario 4 Scenario 5 Scenario 6
Deployment Aspects
LTE908 ANR for UTRAN - Fully UE based

Scenarios – 5/13
• Scenario 2 – A2 event (UE is
attaching to LTE cell, UE is in the
overlapping area of the cells, event A2
condition reached – WCDMA
measurement starts)
• During Attach procedure UE is requested (via
RRC Connection Reconfiguration message) for
reportStrongestCellsForSon
• eNB receives MEASUREMENT REPORT with A2
event (threshold2Wcdma) satisfied
• eNB evaluates A2 event and performs intra-freq
RSRP(dBm) = X – 140=
rsrpResult 48  -140+48= [-93… -92) dBm
A3/A5 or inter-RAT B2 measurement activation in e.g 92dBm = 48 -140
UE
• eNB deactivates further ANR measurement
Utra-RSCP 38  -120+5+38= [- 78…-77) dBm
• i.e.:stops supervision timer, removes
82 RSCFS MeasId
© Nokia from
Solutions andUE, manages
Networks 2014
measGaps and DRX
For internal use
Trials & Pilots OAM test results, Otto Koch, SON.7015 LTE908 ANR Inter-RAT UTRAN – Fully UE based, V1.0 2014-11-10
Scenario 1 Scenario 2 Scenario 3 Scenario 4 Scenario 5 Scenario 6
Deployment Aspects
LTE908 ANR for UTRAN - Fully UE based

Scenarios – 6/13
• Scenario 3 – WCDMA cell signal level below Profile threshold (UE is attaching to LTE cell, UE is in
the overlapping area of the cells, WCDMA cell signal level below Profile threshold during attach
procedure)
• Feature activation flag set to true, ANR Profile created

RSCP = -110 dBm = RSRP = -85dBm = Threshold


ANRPRW threshold “ANR 2 WCDMA for RSRP
UTRA RSCP threshold“
LTE eNB 3G BTS

3. ANR does not work

1. Attach to LTE 2. Move mobile

Typically threshold2WCDMA=-115 dBm while for


83 © Nokia Solutions and Networks 2014 test purpose -85 dBm is considered
For internal use
Trials & Pilots OAM test results, Otto Koch, SON.7015 LTE908 ANR Inter-RAT UTRAN – Fully UE based, V1.0 2014-11-10
Scenario 1 Scenario 2 Scenario 3 Scenario 4 Scenario 5 Scenario 6
Deployment Aspects
LTE908 ANR for UTRAN - Fully UE based

Scenarios – 7/13
• Scenario 3 – WCDMA cell signal level below Profile threshold (UE is attaching to LTE cell, UE is
in the overlapping area of the cells, WCDMA cell signal level below Profile threshold during attach
procedure)
• Feature activation flag set to true, ANR Profile created

1. • During Attach procedure UE is requested (via RRC Connection


Reconfiguration message) for reportStrongestCellsForSon
• While Profile threshold is not satisfied (during attach procedure WCDMA
cell signal level is below anrUtraRscpThres) MR with unknown PSC is
discarded by eNB

2. • UE is moving to area where anrUtraRscpThres criterion is satisfy while LTE908 is not triggered (no attach, no HO, no
re-establishment).
3. • LTE908 is broken.

84 © Nokia Solutions and Networks 2014


For internal use
Trials & Pilots OAM test results, Otto Koch, SON.7015 LTE908 ANR Inter-RAT UTRAN – Fully UE based, V1.0 2014-11-10
Scenario 1 Scenario 2 Scenario 3 Scenario 4 Scenario 5 Scenario 6
Deployment Aspects
LTE908 ANR for UTRAN - Fully UE based

Scenarios – 8/13
• Scenario 4 – UE is attaching to LTE, moves to area with weak WCDMA cell signal level then
backs (UE attached to LTE cell, UE is in the overlapping area of the cells)
• Feature activation flag set to true, ANR Profile created

RSCP = -110 dBm = RSRP = -85dBm = Threshold


ANRPRW threshold “ANR 2 WCDMA for RSRP
UTRA RSCP threshold“
LTE eNB 3G BTS

2. Moved after 10 sec. 1. Attach to LTE

3. UE remains 5 minutes
4. ANR works
Typically threshold2WCDMA=-115 dBm while for
85 © Nokia Solutions and Networks 2014 test purpose -85 dBm is considered
For internal use
Trials & Pilots OAM test results, Otto Koch, SON.7015 LTE908 ANR Inter-RAT UTRAN – Fully UE based, V1.0 2014-11-10
Scenario 1 Scenario 2 Scenario 3 Scenario 4 Scenario 5 Scenario 6
Deployment Aspects
LTE908 ANR for UTRAN - Fully UE based

Scenarios – 9/13
• Scenario 4 – UE is attaching to LTE, moves to area with weak WCDMA cell signal level then
backs (UE attached to LTE cell, UE is in the overlapping area of the cells)

1. • During Attach procedure UE is requested (via RRC Connection Reconfiguration message) for reportStrongestCellsForSon
• Profile threshold satisfies (during attach procedure WCDMA cell signal level is above anrUtraRscpThres) MR with
unknown PSC is sent. eNB keeps unknown PSC in „Unknown PSCs list”
• UE is moving to area where anrUtraRscpThres criterion is not satisfied. This cause that even condition for RSC request
2. fulfils, eNB discard received MR with the reported strongest cell

3. • eNB still keeps delivered PSC in „Unknown PSCs list” waiting for UE which fulfills condition for UTRA PSC detectability
confirmation

4. • UE moved to area where anrUtraRscpThres criterion is satisfy


• Conditions to activate ReportStrongesCells reached (link)
• UTRA PSC detectability confirmation and then CGI resolution starts
• eNB removes PSCx from the respective „unknown PSC list”, creates LNRELW object for UTRAN CellA if possible
86(ANRPRW:lnRelWLimitForAnr not
© Nokia Solutions and Networks reach) and corresponding LNADJW object if not yet available
2014
For internal use
Trials & Pilots OAM test results, Otto Koch, SON.7015 LTE908 ANR Inter-RAT UTRAN – Fully UE based, V1.0 2014-11-10
Scenario 1 Scenario 2 Scenario 3 Scenario 4 Scenario 5 Scenario 6
Deployment Aspects
LTE908 ANR for UTRAN - Fully UE based

Scenarios – 10/13
• Scenario 5 – Typical scenario while additionally LTE556 configured on LTE f1 cell (UE#1 is attaching to
LTE f1 cell, then UE#2 handed over to eNB f1, nextly UE#3 attached to the network (eNB f1) ,UEs are in the
overlapping area of the: LTE f1 cell, LTE f2 (inter-frequency) cell and WCDMA cells, no neighboring relations
towards each of them)

ANR UTRA RSCP threshold Threshold 2 WCDMA for RSRP

LTE eNB f1 3G BTS

UE#3
UE#1
UE#2 History of the requests for LTE
ANR and UTRAN ANR
measurements determines for
which measurement UE would be
87 © Nokia Solutions and Networks 2014
For internal use asked here and now. See more
LTE eNB f2 on next slide
Scenario 1 Scenario 2 Scenario 3 Scenario 4 Scenario 5 Scenario 6
Deployment Aspects
LTE908 ANR for UTRAN - Fully UE based

Scenarios – 11/13
• Scenario 5 – Typical scenario while additionally LTE556 configured on LTE f1 cell (UE#1 attached to
LTE f1 cell, then UE#2 handed over to eNB f1, nextly UE#3 attached to the network (eNB f1) ,UEs are in
the overlapping area of the: LTE f1 cell, LTE f2 (inter-frequency) cell and WCDMA cells, no neighboring
relations towards each of them)
• Both features configured properly (ANRPRW defined for WCDMA and ANRPRL for f2 frequency, full FIGs support by
UEs)

Scenario 5 a) Scenario 5 b)
• History: • History:
•… •…
• UE#1 attached to the network (eNB f1) and requested • UE#1 attached to the network (eNB f1) and requested
for RSCFS (2015.02.10; 10:58) for RSCFS (2015.02.10; 10:58)
• UE#2 handed over to eNB f1 and requested for RSC • UE#2 handed over to eNB f1 and requested for
(2015.02.10; 11:15) RSCFS (2015.02.10; 11:15)
• Now: • Now:
88 • UE#3 ©attached to the
Nokia Solutions andnetwork (eNB
Networks 2014 f1) and requested • UE#3 attached to the network (eNB f1) and requested
for RSCFS
For internal use for RSC
Scenario 1 Scenario 2 Scenario 3 Scenario 4 Scenario 5 Scenario 6
Deployment Aspects
LTE908 ANR for UTRAN - Fully UE based

Scenarios – 12/13
• Scenario 6 – Rollout scenario with mobility dedicated MOCs creation (aim of this scenario is to
generate MOCs dedicated to connected and idle mode mobility from LTE towards WCDMA)
• Feature activation flag set to true, ANR Profile created

ANR UTRA RSCP threshold Threshold 2 WCDMA for RSRP

LTE eNB 3G BTS

ANR works properly

89 © Nokia Solutions and Networks 2014


For internal use
Scenario 1 Scenario 2 Scenario 3 Scenario 4 Scenario 5 Scenario 6
Deployment Aspects
LTE908 ANR for UTRAN - Fully UE based

Scenarios – 13/13
• Scenario 6 – Rollout scenario with mobility dedicated MOCs creation (aim of this scenario is to
generate connected and idle mode mobility MOCs from LTE towards WCDMA)
• To activate LTE783 on 1st eNB for mobility MOCs creation (i.e.: LNHOW, LNADJW, LNRELW, UFFIM, REDRT)
- To keep default settings
- To remove all LNRELW objects before new plan provisioning
• To activate LTE908 (activation flag set to true, ANR Profile defined for frequencies from LNHOW(s) and enabled)
- To keep default settings
- New LNRELW MOCs created (LNRELW created by LTE908 ensures better performing due to WCDMA signal
quality verification)
- Remove LNADJW(s) for which corresponding LNRELW(s) does not exist
• Enable mobility features (e.g. LTE56 HO to WCDMA)
• Activate (after 2-4 weeks) LTE507 for NR optimization – poor performing NR will be blacklisted
• To keep LTE908 and LTE507 activated till rollout finish
90 © Nokia Solutions and Networks 2014
• Repeat
For internal use procedure for all eNB in rollout area
Deployment Aspects
Faults

Fault name Maximum number of WCDMA neighbor relations per cell and carrier is exceeded
Fault ID and name 6270: EfaultId_MaximumNumberOfWcdmaNbRelsPerCellAndCarrierAl
Reported alarms 7652 BASE STATION NOTIFICATION
Unit status Working
LED display Stable Green
It has been detected that:
-the maximum number of LNRELW per cell and WCDMA carrier frequency has already been reached (is
Meaning greater than or equal to the lnRelWLimitForAnr parameter value (in ANPRW profile).
-or the maximum number of mobility parameters (either of: psHoAllowed, srvccAllowed) of LNRELW per
cell and WCDMA carrier frequency is greater than or equal to the limit in 3GPP 36.331 (32)
The WCDMA neighbor relation, which is reported by a UE because of activated ANR feature(s): 1) has
not been stored because the actual number of LNRELW per cell (LNCEL) per UTRAN carrier (in
Effect ANRPRW profile) is equal to or greater than the lnRelWLimitForAnr parameter value (in ANPRW profile)
or 2) has been stored but at least one of LNRELW's mobility parameters (psHoAllowed, srvccAllowed)
has been set to 'forbidden' because it has exceeded limit in 3GPP 36.331 (32).
check if there are LNRELW objects per cell and WCDMA carrier frequency that can be manually
Instructions deleted. This makes space for new LNRELW object per cell and WCDMA carrier frequency.

91 © Nokia Solutions and Networks 2014


For internal use
Deployment Aspects
Faults

Fault name Maximum number of WCDMA neighbor relations per cell and carrier is exceeded

LNRELW[200] ANR Profile settings:


LNRELW[201] srvccAllowed = allowed
maxCellMeas (3GPP 36.331) … psHoAllowed = allowed
… csfbPsHoAllowed = allowed*
Fault: Maximum number of WCDMA LNRELW[231]
neighbor relations per cell and carrier
is exceeded
LNRELW[232] srvccAllowed = forbidden
LNRELW[233]
ANRPRW: lnRelWLimitForAnr psHoAllowed = forbidden

csfbPsHoAllowed = forbidden
If the number of neighbor relations (LNRELW instances) exceeds the maximum number of WCDMA neighbor cells which might
be used by eNB in measurement configurations (limit in 3GPP 36.331,currently maxCellMeas=32) but the limit which is
configured with lnRelWLimitForAnr is not yet reached, then eNB will create new LNLRELW instances with xyzAllowed set to
'forbidden'.
92 This©isNokia
to ease further
Solutions manual
and Networks 2014 optimization of neighbor cell blacklisting
For internal use
*csfbPsHoAllowed=allowed is limited by LNHOW:maxNumCsfbTargets (max = 16)
Deployment Aspects
Faults

Fault name Maximum number of WCDMA neighbor relations is exceeded


Fault ID and name 6269: EfaultId_MaximumNumberOfWcdmaNbRelsAI
Reported alarms 7652 BASE STATION NOTIFICATION
Unit status Working
LED display Stable Green
This alarm indicates that a candidate for WCDMA neighbor, which is reported by a UE via ANR specific
measurements, could not be stored because the maximum number of neighbor relations per cell is
Meaning already reached. The additional alarm info holds the ECGI of the LTE cell and the UTRAN CGI of the
related WCDMA neighbor cell
LNRELW object with newly-learnt WCDMA neighbor relation configuration via ANR specific
Effect measurements is not stored in the eNB.
Check if the maximum number of LNRELW objects has been reached. If it has been, check if there are
Instructions LNRELW objects that can be manually deleted. This makes space for new LNRELW object.

93 © Nokia Solutions and Networks 2014


For internal use
Deployment Aspects
Faults

Fault name Maximum number of WCDMA neighbor cells is exceeded


Fault ID and name 6268: EfaultId_MaximumNumberOfWcdmaNbCellsAI
Reported alarms 7652 BASE STATION NOTIFICATION
Unit status Working
LED display Stable Green
This alarm indicates that a WCDMA neighbor cell, which is reported by an UE via ANR specific
measurements could not be stored because the maximum number of LNADJW instances is already
Meaning reached. The additional alarm info holds the UTRAN CGI of the reported WCDMA cell, which could not
be stored
LNADJW object with newly learnt WCDMA neighbor cell configuration via ANR specific measurements
Effect are not stored in eNB.
Check if maximum number of LNADJW was reached. If yes, check if there are LNADJW objects that can
Instructions be manually deleted. This makes space for new LNADJW object.

94 © Nokia Solutions and Networks 2014


For internal use
Please fill in a short survey
Your feedback is valuable to us!
KIND REQUEST TO YOU:
PLEASE FILL IN THE SURVEY NOW
SURVEY IN THE WEBEX PANEL

The certificate proving you attended this training session will be


available at NEDC:
(Training Center => Certifications => My Certifications)

95 © Nokia Solutions and Networks 2014


For internal use
LTE908 ANR for UTRAN – Fully UE based

Performance
Aspects
Table of contents

96 © Nokia Solutions and Networks 2014


For internal use
Performance Aspects
New counters
Feature LTE908 introduced 3 new counters

Counter name Description

UTRAN_REPORT_CGI_ATT This counter provides the total number of attempts to retrieve the CGI of a
(M8008C12) UTRAN neighbor cell from UE.
Trigger event: Transmission of RRCConnectionReconfiguration message
#LTE RRC including a "reportCGI" measurement configuration to the UE for a UTRAN cell
according to 3GPP TS 36.331.
UTRAN_REPORT_CGI_ATT (M8008C12) Use case: It is expected that number of new NR added to the network each day is
UTRAN_REPORT_CGI_SUCC (M8008C13)
decreasing (assumption: lack of WCDMA rollout)
UTRAN_REPORT_CGI_INCOMPL (M8008C14)

Monday Tuesday Wednesday

97 © Nokia Solutions and Networks 2014


Performance Aspects
New counters
Feature LTE908 introduced 3 new counters

Counter name Description

UTRAN_REPORT_CGI_SUCC This counter provides the number of CGI measurement reports received from
(M8008C13) UE containing LAC and RAC.

#LTE RRC Trigger event: Reception of RRC Measurement Report message including a
"reportCGI" measurement result for a UTRAN cell according to 3GPP TS 36.331.
The "reportCGI" measurement result contains all necessary IEs needed for a
UTRAN_REPORT_CGI_ATT (M8008C12) unique cell identification, which are: the CGI (PLMN, RNC ID Cell ID), the LAC
UTRAN_REPORT_CGI_SUCC (M8008C13)
and the RAC. KPI represents
success ratio of CGI
UTRAN_REPORT_CGI_INCOMPL (M8008C14)
E-UTRAN CGI reports UTRAN_REPORT_CGI_SUCC with full content
for UTRAN Success = ×100% (containing LAC
Ratio UTRAN_REPORT_CGI_ATT and RAC) received
by eNB. It is
expected that this
KPI is close to
Monday Tuesday Wednesday 100%
98 © Nokia Solutions and Networks 2014
Performance Aspects
New counters
Feature LTE908 introduced 3 new counters

Counter name Description

UTRAN_REPORT_CGI_INCOMP This counter provides the number of CGI measurement reports received from
L UE with missing LAC or RAC.
(M8008C14)
Trigger event: Reception of RRC Measurement Report message including a
#LTE RRC "reportCGI" measurement result for a UTRAN cell according to 3GPP TS 36.331.
The "reportCGI" measurement result does not contain the necessary IEs needed
UTRAN_REPORT_CGI_ATT (M8008C12) for a unique cell identification like the LAC or RAC.
UTRAN_REPORT_CGI_SUCC (M8008C13) Please note that a low number of failed CGI resolutions KPI represents
could be normal behavior (e.g. UE could not finish percentage of CGI
UTRAN_REPORT_CGI_INCOMPL (M8008C14)
without full content
detection in time) with no need of any further action of necessary IE
(missing LAC or
E-UTRAN CGI UTRAN_REPORT_CGI_INCOMPL RAC) received by
reports for UTRAN = ×100% eNB. It is expected
UTRAN_REPORT_CGI_ATT
Failure Ratio that this KPI is close
Monday Tuesday Wednesday to 0%
99 © Nokia Solutions and Networks 2014
Performance Aspects
Feature impact

Feature impact How to measure?


Increased number of mobility procedures Counters:
attempts to UTRAN • LTE562 CS Fallback attempts with redirection via RRC
Connection Release (M8016C11)
Note: as a result of new NBRs establishment overall
number of mobility procedures attempts in affected • LTE562 CS Fallback attempts (UE in Connected Mode) with
network should increase. redirection via RRC Connection Release (M8016C12)

• LTE56 Inter System Handover attempts (M8016C21)


• LTE56 Inter System Handover attempts per NBR (M8017C7)
• LTE872 Inter System Handover attempts to UTRAN with
SRVCC (M8016C29)

• LTE872 Inter System Handover attempts to UTRAN with


SRVCC per NBR (M8017C11)

10 © Nokia Solutions and Networks 2014


1 internal use
For
Performance Aspects
Feature impact

Feature impact How to measure?


Higher SRVCC Success Ratio (overall) KPI:
Note: as a result of increased number of NBRs, better • LTE872 E-UTRAN Inter RAT HO UTRAN with SRVCC
target cell might be available. It causes that HO Success Success Ratio (LTE_5564a)
Ratio may get improved.
Lower SRVCC Failure Ratio (overall) KPI:
Note: as a result of increased number of NBRs, better • LTE872 E-UTRAN Inter RAT HO UTRAN with SRVCC
target cell might be available. It causes that HO Failure Failure Ratio (LTE_5563a)
Ratio may get improved.
Higher PS-HO Success Ratio (overall) KPI:
Note: as a result of increased number of NBRs, better • LTE56 E-UTRAN Inter RAT HO Success Ratio (LTE_5195a)
target cell might be available. It causes that HO Success
Ratio may get improved.
Lower PS-HO Failure Ratio (overall) KPI:
Note: as a result of increased number of NBRs, better • LTE56 E-UTRAN Inter RAT HO Failure Ratio (LTE_5197a)
target cell might be available. It causes that HO Failure
Ratio may get improved.
10 © Nokia Solutions and Networks 2014
2 internal use
For
LTE908 ANR for UTRAN – Fully UE based

Compliance
Aspects
Table of contents

10 © Nokia Solutions and Networks 2014


3 internal use
For
Compliance Aspects
LTE908 ANR for UTRAN - Fully UE based

• At least Rel’8 UE is required with following FIG support:


- Feature Group Indicator #16,19, 22 must be set by the Rel’8 UE for full LTE908 support
- Feature Group Indicator #16, 22,33 must be set by the Rel’9 or higher UE for full LTE908 support
• Rel’10 with FIG #114 additionally measures UTRAN cell EcNo what is also evaluated by LTE908 feature

• LTE908 supports NBR adding to other vendors UTRAN cells


- Please remember to setup RNC ID settings correctly in ANR Profile
• 3GPP specifications:
- 3GPP TS 36.300: E-UTRA Overall Description, Stage 2
- 3GPP TS 36.331: E-UTRA RRC Protocol Specification
- 3GPP TS 36.133: E-UTRA Requirements for Support of Radio Resource Management
- 3GPP TS 25.331: UTRA RRC Protocol Specification

10 © Nokia Solutions and Networks 2014


4 internal use
For
References

Reference
CFAM LTE908 ANR for UTRAN – fully UE based, Rossella De Benedittis, version 9.0.0, 30.06.2014

NEI Complex Automatic Neighbour Relation (ANR) InterRATs with O&M, Bartlomiej Bednarz, version 4.1, 07.2014

Trials & Pilots OAM test results, Otto Koch, SON.7015 LTE908 ANR Inter-RAT UTRAN – Fully UE based, V1.0 2014-11-10

10 © Nokia Solutions and Networks 2014


5 internal use
For
10 © Nokia Solutions and Networks 2014
6 internal use
For
Copyright and confidentiality

The contents of this document are proprietary and Networks products and related specifications or other fitness for a particular purpose, are made in relation to
confidential property of Nokia Solutions and Networks. documentation. Accordingly, if the user of this the accuracy, reliability or contents of this document.
This document is provided subject to confidentiality document gives Nokia Solutions and Networks NOKIA SOLUTIONS AND NETWORKS SHALL NOT
obligations of the applicable agreement(s). Feedback on the contents of this document, Nokia BE RESPONSIBLE IN ANY EVENT FOR ERRORS IN
Solutions and Networks may freely use, disclose, THIS DOCUMENT or for any loss of data or income or
This document is intended for use of Nokia Solutions reproduce, license, distribute and otherwise any special, incidental, consequential, indirect or direct
and Networks customers and collaborators only for the commercialize the feedback in any Nokia Solutions and damages howsoever caused, that might arise from the
purpose for which this document is submitted by Nokia Networks product, technology, service, specification or use of this document or any contents of this document.
Solution and Networks. No part of this document may other documentation.
be reproduced or made available to the public or to any This document and the product(s) it describes are
third party in any form or means without the prior Nokia Solutions and Networks operates a policy of protected by copyright according to the
written permission of Nokia Solutions and Networks. ongoing development. Nokia Solutions and Networks applicable laws.
This document is to be used by properly trained reserves the right to make changes and improvements
professional personnel. Any use of the contents in this to any of the products and/or services described in this Nokia is a registered trademark of Nokia Corporation.
document is limited strictly to the use(s) specifically document or withdraw this document at any time Other product and company names mentioned herein
created in the applicable agreement(s) under which the without prior notice. may be trademarks or trade names of their respective
document is submitted. The user of this document may owners.
voluntarily provide suggestions, comments or other The contents of this document are provided "as is".
feedback to Nokia Solutions and Networks in respect of Except as required by applicable law, no warranties of © Nokia Solutions and Networks 2014
the contents of this document ("Feedback"). Such any kind, either express or implied, including, but not
Feedback may be used in Nokia Solutions and limited to, the implied warranties of merchantability and

10 © Nokia Solutions and Networks 2014


7 internal use
For
LTE1234 Whatever the feature name

Backup

10 © Nokia Solutions and Networks 2014


8 internal use
For
Configuration Management
New parameters Hidden!!!

Abbreviated name Full name PKDB link

LNBTS:anrUtraInactivityTimer UTRA ANR inactivity timer

LNBTS:anrUtraTRSC ANR UTRA RSC timer

LNBTS:anrUtraTRCGI ANR UTRA reportCGI timer

LNBTS:maxMRnoUtraPciToResol Maximum measurement reports


ve with no UTRA PCI (PSC) to resolve

10 © Nokia Solutions and Networks 2014


9 internal use
For
Searching of Detectability
Requirements Configuration CGI resolution NR update
unknown cell confirmation
Technical Details Measurement
LTE908 ANR for UTRAN - Fully UE based activation

UE eNB NodeB NetAct


CellA, Fx, PCI#1 CellB, Fy, PSCx

UE is capable of InterRAT UTRAN ANR measurements eNB CellA operates at frequency Fx


(i.e. FIG bit#33 and 22 set) and periodical UTRAN ANR Profile created & enabled for Fy for NodeB CellA
measurements (FIG bit#16 set) and it supports both LTE Unknown PSC list for Fy at CellA not empty
Fx and UTRAN Fy frequency band LTE908 feature enabled

RRC connected LNBTS: anrUtraInactivityTimer


3) RRC Connection Reconfiguration ReportStrongestCells is activated when:
(purpose: reportStrongestCells) • UE inactive for 5 sec time period in RRC
Connection state
• No event based inter-frequency/RAT running
• No ReportCGI and no
ReportStrongestCellForSon measurements
are currently running at the UE
11 © Nokia Solutions and Networks 2014
0 internal use
For • There is at least one ‘unknown PSC’
Continuation on next slide…