RG301737

THIS FUNCTIONALITY IS FOR TRIAL PURPOSE

The latest version of this NEI can be found here

For internal use
Unique document identifier (ID) / Version number / Life cycle status
1 © Nokia Siemens Networks 2012 MBB CS Network Engineering/Dariusz Tomeczko/November 2012
Disclaimer

ATTENTION:

- NEI slides are reviewed by NetEng cooperation partners in R&D and other
organizations, but do not assume an 'approved' state.
Instead, NEI slides are 'living documents' , i.e. working documents that are
updated on-demand with new findings & experiences.

- Please note that NEI materials are FOR INTERNAL USE ONLY. If they shall be
used as source for customer consultation presentation, it is mandatory to align the
contents with Product Management or/and local Sales teams first!

For internal use

Unique document identifier (ID) / Version number / Life cycle status
2 © Nokia Siemens Networks 2012 MBB CS Network Engineering/Dariusz Tomeczko/November 2012
History and Acknowledgements Main Menu

History Open Issues

Versions Date Reason for Update Item Open Item Description Status / Comments

First version of the document (for so called Two cells with the same frequency put on
Limited functionality of LTE
test version). the NR list makes the content of SI2q
1.0 10.06.2011 1 System Information in case
References: coded in suboptimal way – topic handled
of introduction of IS- NCCR
- Requirement Specification: RG301737 by R&D, CR opportunity discussed

Version for the RG30 (commercial + test Currently, only up to 8 neighbours per all
Limited number of
1.1 16.12.2011 LTE frequencies (and one per TAC)
version merged, new specification) 2 neighbours for IS-NCCR
could be included in the DB, CR
feature
2.0 25.05.2012 Pre-P7 version opportunity discussed
Core network dependency related to
Limited performance gains
3.0 30.07.2012 Migration to the new NEI template Service based IS-NCCR functionality that
3 due to IS-NCCR
is NOT planned to be supported in NSN
introduction
4.0 20.09.2012 Version for the external review Core Network
Existence of check against
5.1 05.10.2012 Final version Under clarficaiton with R&D; no such
GERAN to E-UTRA support
4 check exists. Only LTE capability of the
in GERAN packet transfer
Additional corrections reflecting the mobile is checked
5.2 07.11.2012 mode field in MS RAC IE
implementation handling. Version for the P7

Acknowledgements
Matti Taponen – author of IS-NCCR for LTE, commercial version, Requirement Specification

For internal use

4 © Nokia Siemens Networks 2012 MBB CS Network Engineering/Dariusz Tomeczko/November 2012
 NEI Complex Introduction Main Menu
RG301737 – IS-NCCR for LTE, overview of GSM/LTE interworking functionalities

E-UTRA (RL40) LTE 873: SRVCC

GSM Connected
RRC_CONNECTED
GPRS
Packet
Transfer

LTE 562: CSFB redirect

LTE 423: redirect & LTE984
LTE 442: eNACC w/o RIM
(RL20) LTE 562: CSFB

(RG20) BSS21353: reselection

E-UTRA GSM Idle
RRC_IDLE (RL10) LTE 762: reselection GPRS Packet Idle

For internal use Please always check the latest RG/RU/RL roadmaps about current status of the feature set
5 © Nokia Siemens Networks 2012 MBB CS Network Engineering/Dariusz Tomeczko/November 2012
 RG301737 – IS-NCCR for LTE Main Menu

Table of Contents

Introduction Benefits and Gains

1 Motivation and Feature Overview 6 Simulation, Lab and Field Findings

Interdependencies Dimensioning Aspects

2 Interdependencies with Other Features and Functions 7 Dimensioning Impacts and Examples

Technical Details Performance Aspects

3 Functionality and Implementation, Message Flows 8 Counters and KPIs

Configuration Management Compliance Aspects

4 Parameters 9 3GPP, IETF, ETSI

Deployment Aspects End to End Operability

5 Feature Activation and Configuration Examples 10 OSS and Core Interworking

NEI Contact: Dariusz Tomeczko

For internal use
Unique document identifier (ID) / Version number / Life cycle status
6 © Nokia Siemens Networks 2012 MBB CS Network Engineering/Dariusz Tomeczko/November 2012
 Introduction Table of Contents Main Menu
RG301737 – IS-NCCR for LTE

 Features supplements interworking between LTE and GSM

 Thanks to IS-NCCR functionality LTE capable mobiles could be moved from GSM to
LTE with the help of network controlled cell reselection instead of mobile
autonomous inter-system cell reselection

LTE coverage
area

GSM coverage area GSM/LTE capable UE

THIS FUNCTIONALITY IS FOR TRIAL PURPOSE

For internal use
7 © Nokia Siemens Networks 2012 MBB CS Network Engineering/Dariusz Tomeczko/November 2012
 With and without IS-NCCR Table of Contents Main Menu
RG301737 – IS-NCCR for LTE

 Before RG30 the only way to  With the help of RG301737

RG301737 change the RAT from GSM to Network Controlled Cell RG301737
Not activated Activated
LTE is to utilize mobile Reselection to LTE is introduced
autonomous cell reselection  RG301737 now covers so called
algorithm that are based on test and commercial (pre-RG30
absolute priorities (according nomenclature) version of this
to 3GPP Rel. 8 specifications). functionality where both
 For further details please refer
 coverage and
to NEI on LTE System
Information (BSS 21353)  service based IS-NCCR
to TD-LTE as well FD-LTE is
implemented

LTE coverage LTE coverage

area area

GSM coverage area GSM/LTE capable UE GSM coverage area GSM/LTE capable UE

For internal use

8 © Nokia Siemens Networks 2012 MBB CS Network Engineering/Dariusz Tomeczko/November 2012
 General Release Information Table of Contents Main Menu
RG301737 – IS-NCCR for LTE

Release Information Supplementary Information

System Release RG30 NetAct -

BSC S16 For Service Based IS-NCCR, this option

SGSN
should be supported by SGSN
DX200 platform -
MSC -
BTS Ultra Site -
RAN -
BTS Metro Site -
MS GSM/LTE IS-NCCR capable
BTS Talk Family -
BSW/ASW ASW
BTS Prime Site - License Control in
Network Element LAC
BTS InSite - Licence Control
attributes Long-term ON/OFF licence
2nd Gen BTS -

BTS Flexi Edge -

MultiRadio Flexi -

BTSplus -

For internal use

9 © Nokia Siemens Networks 2012 MBB CS Network Engineering/Dariusz Tomeczko/November 2012
 Interdependencies Table of Contents Main Menu
RG301737 – IS-NCCR for LTE

IS-NCCR – Feature Requirements:

• BSS11112 Network Controlled Cell Reselection
• IS-NCCR for LTE could be treated as a kind of extension of regular, intra-GSM, Network Controlled
Cell Reselection, so enabling of NCCR as such is mandatory
• BSS21353 LTE System Information
• Basic interworking functionality (i.e. autonomous mobile controlled cell reselection) was introduced in
RG20 and it is a prerequisite for the inter-system network controlled cell reselection

BSS11112 BSS21353
NCCR LTE System
Information

RG301737
IS-NCCR for LTE

For internal use

10 © Nokia Siemens Networks 2012 MBB CS Network Engineering/Dariusz Tomeczko/November 2012
 Interdependencies Table of Contents Main Menu
RG301737 – IS-NCCR for LTE

IS-NCCR for LTE – Features Affected:

• BSS 21353 LTE System Information
• In the context of LTE System Information functionality up to 8 various frequencies could be included
as potential target ones for the idle mode mobility. If due to the IS-NCCR two cells with the same
frequency are put as the neighbour cells, then there will be two entries in SI2q for the same LTE
frequency what has two drawbacks:
• suboptimal usage of already cluttered up SI2q (double entries)
• potential UE misbehaviour if such SI2q is received
• BSS11112/RG301736 – other NCCR mechanisms
• Only if the criteria for coverage/service-based NCCR to LTE are not satisfied then criteria related to
IS-NCCR to WCDMA/TD-SCDMA (if enabled) are evaluated
• If also IS-NCCR to WCDMA/TD-SCDMA could not be performed, intra-GSM NCCR critera
(according to implementation of the feature BSS11112 (Network-Controlled Cell Re-selection)) are
evaluated

RG301737
IS-NCCR for LTE

RG301736
BSS21353 BSS11112 Inter- System
LTE System NCCR for TD-
NCCR
Information SCDMA
For internal use
11 © Nokia Siemens Networks 2012 MBB CS Network Engineering/Dariusz Tomeczko/November 2012
 Interdependencies Table of Contents Main Menu
RG301737 – IS-NCCR for LTE

IS-NCCR for LTE – Feature Limiting the scope:

• BSS 20088 Dual Transfer Mode
• If there is an ongoing DTM call, IS-NCCR could not be triggered

BSS20088
Dual Transfer
Mode

RG301737
IS-NCCR for LTE

For internal use

12 © Nokia Siemens Networks 2012 MBB CS Network Engineering/Dariusz Tomeczko/November 2012
 Technical Details Table of Contents Main Menu
IS-NCCR – introduction

 There are two feature variants:

 coverage variant
 service variant
 Primary aim of the coverage based version feature is to:
 command the UE to reselect to LTE as soon as LTE
coverage is available assuming that priority of LTE is higher
than priority of GSM
 Primary aim of the service based version feature is to:
LTE coverage
 command the UE to reselect to LTE as soon as LTE area
coverage is available even if priority of LTE cell is lower than
the serving cell GSM coverage area GSM/LTE capable UE

 Available coverage refers to the minimum LTE RSRP

(Reference Signal Received Power) that is received by
the mobile
 Concept of RAT priorities was introduced along with LTE
System Information feature
For internal use
13 © Nokia Siemens Networks 2012 MBB CS Network Engineering/Dariusz Tomeczko/November 2012
 Technical Details Table of Contents Main Menu
IS-NCCR for LTE – introduction

 The actual procedure follows the same rules as introduced for legacy NCCR functionality
e.g.:
 general concept of the network controlled cell reselection
 broadcast of NCCR related parameters
 handling of Packet Measurement Order, Packet Measurement Report, Packet Enhanced
Measurement Report to facilitate the measurement campaign
 usage of Packet Cell Change Order message to order the UE to change the cell
The details related to legacy NCCR feature as such will not be provided in this slideset.
 On the other hand, IS-NCCR for LTE reuses some of the LTE related parameterization like
e.g. handling of network priorities. For details related to this feature, please refer to LTE
System Information NEI (IMS link).
 The add-ons introduced specifically for IS-NCCR for LTE will be described in details in this
NEI.

For internal use

14 © Nokia Siemens Networks 2012 MBB CS Network Engineering/Dariusz Tomeczko/November 2012
 Technical Details Table of Contents Main Menu
IS-NCCR for LTE – new parameters

 For the purpose of this feature new parameters are included in SI2q content - broadcast on
BCCH – in line with 3GPP specification:
– parameterized:
 Qsearch_P_E-UTRAN (BSS: qSearchPEUTRAN),
 E-UTRAN_MULTIRAT_REPORTING (BSS: eUTRANMultiratReporting),
 E-UTRAN_TDD(FDD)_REPORTING_THRESHOLD (BSS: eUTRANReportingThreshold),
 E-UTRAN_TDD(FDD)_REPORTING_THRESHOLD_2 (BSS: eUTRANReportingThreshold2),
 E-UTRAN_TDD(FDD)_REPORTING_OFFSET (BSS: eUTRANReportingOffset).
– hardcoded E-UTRAN_REP_QUANT – fixed to RSRP,
 These parameters are also included in Packet Measurement Order (sent if needed
according to legacy NCCR implementation (nccrControlMode set to 1, 2, 3 where NC0 is
broadcast)). These parameters are sent then only to LTE capable mobiles.
 Checking of IS-NCCR capability of the mobile – under discussion withh R&D
 Actual meaning of these parameters will be provided in the next slides

For internal use

15 © Nokia Siemens Networks 2012 MBB CS Network Engineering/Dariusz Tomeczko/November 2012
 Technical Details Table of Contents Main Menu
IS-NCCR for LTE – cell reporting requirements

 As a general rule, for network controlled cell reselection procedure, mobile station reports
the best valid cells – as described in details in the next slide
 Threshold for search of LTE cells is set by qSearchPEUTRAN parameter set by default to
‘always’.
 The mobile reports only such LTE cells that satisfy simultaneously:
 sufficient RSRP criterion i.e. measured LTE cell is stronger than or equal to
eUTRANReportingThreshold
 sufficient RSRQ criterion i.e. RSRQ of the measured LTE cell is greater than or equal to
eUTRANReportingThreshold2
 At maximum, six neighbours could be included in the measurement report
 RSRP value is reported, while RSRQ criterion is checked by the MS itself, but not reported
 E-UTRAN_REP_QUANT is hardcoded to RSRP

For internal use

16 © Nokia Siemens Networks 2012 MBB CS Network Engineering/Dariusz Tomeczko/November 2012
 Technical Details Table of Contents Main Menu
IS-NCCR for LTE – choice of cells to be reported

More valid cells than could be reported?

YES NO
For each RAT the best cell is taken XXX_MULTIRAT_REPORTING cells for the given technology
(eUTRANMultiratReporting for LTE) are taken to the measurement report

There are still free positions in the measurement

report and some valid non-GSM cells?
NO
YES
For each RAT the next best cell is taken for which XXX_MULTIRAT_REPORTING cells have not yet been included.
In case this would result in including more cells than there are remaining spaces in the measurement report, priority is given to cells from RATs/modes
with higher XXX_MULTIRAT_REPORTING value
In case of equal XXX_MULTIRAT_REPORTING values, the cell for which reported value – XXX_REPORTING_THRESHOLD +
XXX_REPORTING_OFFSET i.e. RSRP – eUTRANReportingThreshold + eUTRANReportingOffset in case of LTE is highest is reported.

There are still free positions in the measurement report?

YES NO
GSM cells are reported

There are still free positions in the measurement report?

YES NO
Next best valid cells in supported other radio access technologies for which
XXX_MULTIRAT_REPORTING is non-zero are reported. The best cell is the cell with the highest
quantity of (reported value – XXX_REPORTING_THRESHOLD + XXX_REPORTING_OFFSET).
For internal use
17 © Nokia Siemens Networks 2012 MBB CS Network Engineering/Dariusz Tomeczko/November 2012
 Technical Details Table of Contents Main Menu
IS-NCCR for LTE – coverage based version

 Coverage based version of the feature could be enabled via setting lteNCCREnabled
parameter to coverage.
 NCCR to LTE will be commanded (i.e. Packet Cell Change Order message that commands
the mobile to leave GSM and enter LTE) if:
– Priority of LTE target cell is higher than the one for the source GSM cell i.e. ADJL/lteAdjCellPriority >
BTS/gsmPriority
– Signal strength of the reported LTE cell is high enough i.e. LTE RSRP > lteNCCRQualityThreshold
 Note however that actually RSRQ is also checked – by the MS itself. So, the PCCO message will not include the
target cell for which RSRQ was too low – since such a cell would not be reported by the MS.

For internal use

18 © Nokia Siemens Networks 2012 MBB CS Network Engineering/Dariusz Tomeczko/November 2012
 Technical Details Table of Contents Main Menu
IS-NCCR for LTE – service based version

 Service based version of the feature could be enabled via setting lteNCCREnabled
parameter to service.
 If Service EUTRAN CCO IE from SGSN is set to the value ‘Network initiated cell change
order to E-UTRAN or PS handover to E-UTRAN procedure should be performed’ the NCCR
to LTE is triggered if:
 Signal strength of the reported LTE cell is high enough (LTE RSRP > lteNCCRQualityThreshold)
even if priority of LTE cell is lower then the serving cell
 If Service EUTRAN CCO IE from SGSN is set to the value ‘Network initiated cell change
order to E-UTRAN or PS handover to E-UTRAN procedure should not be performed’ the
NCCR to LTE is triggered if:
 criteria for the coverage version of the IS-NCCR (see previous slide) are satisfied
 The same is applicable if there is no valid Service EUTRAN CCO IE or this parameter is set to ‘no
information available’
 If Service EUTRAN CCO IE from SGSN is set to the value ‘Network initiated cell change
order to E-UTRAN or PS handover to E-UTRAN procedure shall not be performed’ the
NCCR to LTE is not triggered
For internal use
19 © Nokia Siemens Networks 2012 MBB CS Network Engineering/Dariusz Tomeczko/November 2012
 Technical Details Table of Contents Main Menu
IS-NCCR for LTE – PCCO sending

 Once the criteria for service/coverage based IS-NCCR to LTE are satisfied then Packet Cell
Change Order message is sent to the UE
 In the PCCO target LTE cell is described via providing EARFCN, measurement bandwidth
and Physical Cell ID (that matches the ADJL/pcid together with the frequency put in the
ADJL/earfcn)
 GSM cell could have either TD-LTE neighbours or FD-LTE neighbours but not at the same time

For internal use

20 © Nokia Siemens Networks 2012 MBB CS Network Engineering/Dariusz Tomeczko/November 2012
 Configuration Management Table of Contents Main Menu
IS-NCCR for LTE

 ADJL object in the context of RG20 LTE System Information represents the whole LTE carrier (so all the
cells operating on the particular carrier)
 In the context of RG30 IS-NCCR for LTE, ADJL changes its meaning and actually refers only to the
single LTE cell due to the fact that it relates now not only to the LTE frequency but also to the PCI
(Physical Cell Identity)
 The side effect is that e.g. if there are two neighbours with the same frequency but different PCIs – introduced for
IS-NCCR purposes, there will be double entry in the SI2q for idle mode mobility (handled by LTE System
Information feature) what may potentially lead to suboptimal (and not predictable) behaviour of the mobile station
 Currently, only up to 8 neighbours for all LTE frequencies could be included in the DB for the IS-NCCR
purposes – so only up to to eight ADJL objects (irrespectively of the number of LTE carriers in place)
could be defined
 Only one LTE neighbour per EARFCN + TAC – CR opportunity discussed with R&D
 THIS FUNCTIONALITY IS FOR TRIAL PURPOSE

For internal use

21 © Nokia Siemens Networks 2012 MBB CS Network Engineering/Dariusz Tomeczko/November 2012
 Configuration Management Table of Contents Main Menu
IS-NCCR for LTE

lteMode LTE Mode

Object: BSC This parameter defines whether used LTE mode is TDD-LTE or
Range: TDD (0), FDD FDD-LTE
(1)
Default: TDD (0)
Multiplicity: 1

lteNCCREnabled LTE NCCR Enabled

Object: BTS This parameter activates the IS-NCCR for LTE feature in a cell
Range: 0 – Disabled; level
1 – Coverage; 2 – Service
Default: 0 – Disabled
Multiplicity: 1

For internal use

22 © Nokia Siemens Networks 2012 MBB CS Network Engineering/Dariusz Tomeczko/November 2012
 Configuration Management Table of Contents Main Menu
IS-NCCR for LTE

qSearchPEUTRAN Threshold To Search E-UTRAN Cells

Object: BTS This parameter indicates to the mobile at what GSM radio
Range: 0: -98 dBm, 1: -94 dBm, 2: - conditions the process of searching for LTE cells should be started.
90 dBm, 3: -86 dBm, 4: -82 dBm, The values 0 - 7 refers to the case where signal level should be
5: -78 dBm, 6: -74 dBm, 7: below defined threshold while values 8 – 15 refers to the case
always, 8: -78 dBm, 9: -74 dBm, where signal level should be above given threshold.
10: -70 dBm, 11: -66 dBm, 12: -62
dBm, 13: -58 dBm, 14: -54 dBm,
15: never)
step 1
Default: 7 (always)
Multiplicity: 1
eUTRANMultiratReporting E-UTRAN Multirat Reporting

Object: BTS This parameter defines the number of LTE cells that shall be
Range: 0 – 3, step 1 included in the measurement report.
Default: 3
Multiplicity: 1

For internal use

23 © Nokia Siemens Networks 2012 MBB CS Network Engineering/Dariusz Tomeczko/November 2012
 Configuration Management Table of Contents Main Menu
IS-NCCR for LTE

eUTRANReportingThreshold E-UTRAN Reporting Threshold

Object: BTS This parameter defines Reporting Threshold for LTE cell related to RSRP.
Range: (0 = always, 1 = 6, 2 = 12, 3 Mapping rule:
= 18, 4 = 24, 5 = 30, 6 = 36, 7 =
never) 0 always
Default: 0 (always) 1 = RSRP 6 = RSRP -130 – -128 dBm
2 = RSRP 12 = RSRP -118 – -116 dBm
Multiplicity: 1
3 = RSRP 18 = RSRP -106 – -105 dBm
4 = RSRP 24 = RSRP -100 – -99 dBm
5 = RSRP 30 = RSRP -94 – -93 dBm
6 = RSRP 36 = RSRP -88 – -87 dBm
7 never

It is recommended to set this parameter to value higher than 0 but it should be still less
restrictive than corresponding lteNCCRQualityThreshold (or at least equal to
lteNCCRQualityThreshold).
Recommended initial value: 2 (2 = RSRP 12 = RSRP -118 – -116 dBm)
assuming that the value of 14 (-114 - -112 dBm) was assigned to
lteNCCRQualityThreshold – please see the descrption of lteNCCRQualityThreshold for
further reasoning)

For internal use

24 © Nokia Siemens Networks 2012 MBB CS Network Engineering/Dariusz Tomeczko/November 2012
 Configuration Management Table of Contents Main Menu
IS-NCCR for LTE

eUTRANReportingThreshold2 E-UTRAN Reporting Threshold 2

Object: BTS This parameter indicates the threshold for the parameter that is not
Range: 0 – 63, step 1 reported (so always RSRQ in BSS implementation). The criterion is
checked by the mobile itself i.e. the RSRQ of the cell to be included
Default: 0 in the report should be above provided threshold – according to the
Multiplicity: 1 mapping rule provided below.
Mapping rule:
The range from “-19.5 dB ≤ RSRQ < -19 dB” (reported as 1) to
“-3.5 dB ≤ RSRQ < -3 dB” (reported as 33) is used. RSRQ values
below -19.5 dB shall be reported as 0 and values -3 dB and above
shall be reported as 34.
It is recommended to set this parameter to 0 – i.e. not restrict the
reselection due to RSRQ – unless RSRQ based (re)selection is
introduced on LTE side (currently future study item in RL release)

For internal use

25 © Nokia Siemens Networks 2012 MBB CS Network Engineering/Dariusz Tomeczko/November 2012
 Configuration Management Table of Contents Main Menu
IS-NCCR for LTE

eUTRANReportingOffset E-UTRAN Reporting Offset

Object: BTS This parameter defines an offset to the reported value when
Range: (0 = 0 dB, 1 = 6 dB, 2 = 12 prioritizing the cells (see slide 17 for further details).
dB, 3 = 18 dB, 4 = 24 dB, 5 = 30
dB, 6 = 36 dB, 7 = 42 dB)
Default: 0 (0 dB)
Multiplicity: 1

For internal use

26 © Nokia Siemens Networks 2012 MBB CS Network Engineering/Dariusz Tomeczko/November 2012
 Configuration Management Table of Contents Main Menu
IS-NCCR for LTE

lteNCCRQualityThreshold LTE NCCR Quality Threshold

Object: ADJL This parameter defines a minimum signal quality threshold to select the best possible LTE cell.
Range: 0 – 63 Mapping rule:
RSRP 1 = -140 dBm to -138 dBm
Default: 50 :
:
(-70 – -68 RSRP 17 = -108 dBm to -106 dBm
dBm) RSRP 18 = -106 dBm to -105 dBm
RSRP 19 = -105 dBm to -104 dBm
Multiplicity: 1 :
:
RSRP 44 = -80 dBm to -79 dBm
RSRP 45 = -79 dBm to -78 dBm
RSRP 46 = -78 dBm to -76 dBm
:
:
RSRP 62 = -46 dBm to -44 dBm
RSRP 63 = greater than or equal to 44 dBm
It is recommended to set this parameter to prevent from ping-pong effect (changing the network from LTE to GSM
just after NCCR from GSM to LTE) i.e. lteNCCRQualityThreshold should be set to the value more restrictive (few
dBs is sufficient) than:
- LNBTS/LNCEL/qrxlevmin + LNBTS/LNCEL/threshSrvLow – responsible for idle mode reslection from LTE to
lower priority GSM (RRC Idle state)(assuming that LTE priority is higher than GSM)
- LNBTS/LNCEL/threshold4 – responsible for redirection to GSM from LTE (in RRC Connected state)
- -140 dBm + LNBTS/LNCEL/b2Threshold1GERAN – responsible for triggering the CCO from LTE to GSM (LTE
442 feature)
Assuming: qrxlevmin = -130 dBm, threshSrvLow = 4 dB, threshold4 = -119 dBm, b2Threshold1GERAN = -117
dBm, the value of 14 (-114 - -112 dBm) is a safe initial recommended value.
For internal use
27 © Nokia Siemens Networks 2012 MBB CS Network Engineering/Dariusz Tomeczko/November 2012
 Configuration Management Table of Contents Main Menu
IS-NCCR for LTE

pcid Physical Cell Identity

Object: ADJL This parameter specifies the physical cell identity of a single E-
Range: 0-503, step 1 UTRAN cell.
Introduction of this parameter change the scope of ADJL from
Default: 0
frequency oriented to cell oriented – for the IS-NCCR mechanisms.
Multiplicity: 1

For internal use

28 © Nokia Siemens Networks 2012 MBB CS Network Engineering/Dariusz Tomeczko/November 2012
 Deployment Aspects Table of Contents Main Menu
IS-NCCR for LTE

• Implementation guidelines – IS-NCCR for LTE

– BSC/lteMode should be set by the operator
– IS-NCCR, NCCR and LTE System Information licences should be available
– E(GPRS) should be available
– Following IS-NCCR related BTS parameters should be set: lteNCCREnabled, qSearchPEUTRAN,
eUTRANMultiratReporting, eUTRANReportingThreshold, eUTRANReportingThreshold2, eUTRANReportingOffset
 Hints concerning the parameterization put in the section Configuration Management.
– It should be verified whether LTE ADJL object(s) exist and is/are parameterized
– On top of already existing parameterization the following ADJL parameters should be set:
lteNCCRQualityThreshold and pcid
 Please note that ADJL refers to:
• LTE frequency from the LTE System Information point of view
• LTE cell from the IS-NCCR point of view
 This has certain implications – as presented in ”Features affected” section

For internal use

29 © Nokia Siemens Networks 2012 MBB CS Network Engineering/Dariusz Tomeczko/November 2012
 Performance Aspects Table of Contents Main Menu
IS-NCCR for LTE

 Following new counters were introduced in RG30 for the purpose of monitoring of IS-NCCR for LTE
Counter name Description
95028: The counter counts the number of started inter-system NCCR procedures to LTE.
PCCO SENT DUE The IS-NCCR to LTE is triggered due to coverage bases condition and an
COVERAGE LTE ISNCCR appropriate LTE cell is found.
Trigger event: The counter (95028) is updated when the PCU2 sends PCCO
message to the MS
95029: The counter counts the number of started service based Inter-System NCCR
PCCO SENT DUE procedures to LTE cells.
SERVICE LTE ISNCCR Trigger event: The counter (95029) is updated when the PCU2 sends a PCCO
message to MS
72270: The counter counts the number of times when the service-based ISNCCR to LTE
LTE ISNCCR NO GOOD criteria was triggered but no appropriate neighbour could be found (i.e. IS-NCCR to
NEIGHBOUR LTE does not succeed)
Trigger event: The counter will be updated when P(E)MR measurement report for
LTE cell is received from MS but the criteria is not fulfilled. The updated BTS object
is BCCH BTS.

For internal use

31 © Nokia Siemens Networks 2012 MBB CS Network Engineering/Dariusz Tomeczko/November 2012
 Performance Aspects Table of Contents Main Menu
IS-NCCR for LTE

 Following counters were modified:

Counter name Description
95000: The PLMN identification (MCC/MNC pair) of the WCDMA, TD-SCDMA or LTE cell.
PLMN ID Coded according to the 3GPP 24.008. Relevant only in case of an inter-system
NCCR.
Consists of MCC (2 bytes) and MNC (1 byte).
If the target cell is a GSM cell, the value of the PLMN ID is 0xFFFFFFFF.

27009: The NCCR triggering cause. One of the following: power budget, service based
NCCR TRIGGERING ISNCCR, GSM coverage ISNCCR, quality control, IS-NCCR to TD-SCDMA or IS-
CAUSE NCCR to LTE.

27010: The LAC and CI of the target cell. The LAC is not used, if the target is a WCDMA or
TARGET CELL ID TD-SCDMA cell, value 0xffff is used instead. If target is LTE cell, the target cell is
identified by Tracking Area Code (TAC) and Physical Layer Cell Identity (PCID).

For internal use

32 © Nokia Siemens Networks 2012 MBB CS Network Engineering/Dariusz Tomeczko/November 2012
 Performance Aspects Table of Contents Main Menu
IS-NCCR for LTE

Feature impact How to observe/measure

Influence on the traffic layering • No direct means to measure such influence however it is either
 Better control over traffic handling in the network way recommended to monitor the actual usage of IS-NCCR for
since the UEs could be moved from GSM only to LTE via the new dedicated counters (95028, 95029)
predefined neighbouring LTE cells instead of all
cells belonging to the given LTE frequency (as it
was the case for the LTE System Information
feature)
 Note however that in LTE System Information feature it was
possible to blacklist certain cells (their PCIs). Autonomus mobile
controlled reselection towards such cells is prohibited

For internal use

33 © Nokia Siemens Networks 2012 MBB CS Network Engineering/Dariusz Tomeczko/November 2012
 Performance Aspects Table of Contents Main Menu
IS-NCCR for LTE

Influence on the signalling load • IS-NCCR for LTE could be introduced only on top of NCCR, so:
 Increased signaling load due to sending PMO, • If IS-NCCR for LTE is introduced in the network where NCCR is
PCCO, (E)PMR instead of relying on mobile internal already deployed, no major influence is expected – however it
should be monitored – similarly as it is the case for regular NCCR
reselection algorithms
• If IS-NCCR for LTE is deployed together with NCCR, the increase
of signalling load is expected to be comparable with regular NCCR

• Example KPIs to be monitored:

Downlink GPRS RLC payload trf_213c
Uplink GPRS RLC payload trf_212c
Downlink EGPRS RLC payload trf_215a
Uplink EGPRS RLC payload trf_214a
The effect strongly depends on the parameterization of NCCR (e.g.
periodicity of reporting – please refer to NCCR feature description)

For internal use

34 © Nokia Siemens Networks 2012 MBB CS Network Engineering/Dariusz Tomeczko/November 2012
 Performance Aspects Table of Contents Main Menu
IS-NCCR for LTE

Influence on the E2E delay • Drive tests

 No improvement on end-to-end delay related to
network change is expected with respect to
autonomus mobile controlled cell reselection
(introduced along with RG20 LTE System
Information) – similarly as it is the case for regular
NCCR in intra-GSM deployment

Influence on the performance of LTE System • Lab/field tests with 2G/LTE mobile
Information • CR opportunity discussed
If due to the IS-NCCR two cells with the same
frequency are put as the neighbour cells, than the
UE could potentially misbehave if such SI2q is
received since the mobile would receive two various
entries for the same LTE frequency

For internal use

35 © Nokia Siemens Networks 2012 MBB CS Network Engineering/Dariusz Tomeczko/November 2012
 Compliance Aspects Table of Contents Main Menu
IS-NCCR for LTE

 Inter-System Network-Controlled Cell Re-selection from GSM to LTE is

complaint with the following Release 9 3GPP standards:
 3GPP TS 23.060
 3GPP TS 44.018
 3GPP TS 44.060
 3GPP TS 45.008
 3GPP TS 48.018

For internal use

36 © Nokia Siemens Networks 2012 MBB CS Network Engineering/Dariusz Tomeczko/November 2012
 End to End Operability Table of Contents Main Menu
IS-NCCR for LTE

 IS-NCCR for LTE requires regular interconnection between UE, eNB and Core Network – as it is the
case for all interworking procedures
 On top, for service based IS-NCCR, SGSN should be enhanced with the functionality that provides
Service EUTRAN CCO IE. NSN SGSN does not provide such functionality. So, currently, at least with
NSN Core Network, service based IS-NCCR will not work.
 UE should be LTE capable according to its MS RAC

For internal use

37 © Nokia Siemens Networks 2012 MBB CS Network Engineering/Dariusz Tomeczko/November 2012