Classification : Public

Orange France Swap Modernization Program

4G LTE Part
VoLTE Troubleshooting Guideline

January, 2016
Version 0.5 - DRAFT

1 06/03/2024 © Nokia 2016

Confidential
Classification : Public

Introduction
Scope
• This document should give guidance of VoLTE monitoring, worst performing cell assessment and further
troubleshooting and remedy actions.
• As VoLTE is a complex service spanning several networks domains (UE, radio access, EPC, IMS, TAS,
user data management etc.), also the monitoring and troubleshooting can point to any of these domain(s).
Neverthless, the primary scope of this document is radio access network. Considering also an embraced
need for mobility (Single Radio Voice Call Continuity - SRVCC) of users between different radio access
network types, that involves LTE, UTRAN & GERAN.
• Proactive KPI monitoring and capacity management out of scope of this guideline.
• VoLTE principles and theoretical background is out of scope of this guideline

2 © Nokia 2016
Classification : Public

Introduction
Need for document updates
• This version of the document has been issued prior to swap to Nokia. Hence no real VoLTE experience
has been made on Nokia in Orange network.
• For the reason above this version of the document should be treated as draft version, which is as such
rather theoretical. Further versions of document could be enriched by real cases from ORF network
addressing already encountered problems and giving more concrete problem troubleshooting and
resolution hints.
• This version of the document assumes SRAN16.2 (FL16) with some remarks to the next release
SRAN16.10 (FL16A). However, updates are required with every new system release as there could be
new VoLTE related features and counters introduced.
• Any potential changes in parameter baseline (template) shall be reflected in this document is available.
For instance, there could be a new VoLTE related feature globally activated in Orange network. Such
feature can have eventually a dedicated set of counters through which the performance of the feature
could be monitored.

3 © Nokia 2016
Classification : Public

Monitoring Principles
VoLTE performance monitoring
There are several inputs that could be utilized for VoLTE performance monitoring and assessment:
• OSS KPI’s (focus on EUTRAN KPI’s)
• Drive test KPI’s
• Customer complaints
• Additional KPI’s from EPC, IMS, TAS, PCRF, HSS, UTRAN, GERAN etc.
• Interface traces (from probing system or NE internal traces capturing also IF/protocols terminated at the
particular NE)
The primary scope of this document are EUTRAN KPI’s from OSS. These should be used for initial
KPI monitoring and assessment. The other imputs could be used for enhanced ad hoc troubleshooting if the
OSS KPI’s for EUTRAN aren’t sufficient for root cause analysis.
Important note: EUTRAN KPI’s do not necessarily reflect end-to-end performance. Remember, SIP
signaling (UE<>IMS) is transparent to EUTRAN!

4 © Nokia 2016
Classification : Public

Monitoring Principles
VoLTE performance monitoring
Similar to any other service, VoLTE performance could be measured, monitored and assessed in several well
known performance areas:
• Accessibility
• Retainability
• Mobility
• Quality/Integrity
Note, these ‘performance areas’ should not be treated as standalone as there’s a relation between them. For
example, if there are issues with VoLTE mobility (failed HO, SRVCC), it can be also reflected in other
areas, such as retainability (drops due to failed or missing HO) or quality/integrity (frequent radio link
related issues and RRC connection reestablishments due missing or failed HO).
Primary goal is to make cell level KPI monitoring, assessment and troubleshooting. Even cell level
approach can capture some wider area (e.g. network-wide) issues, such as global configuration issues etc.

5 © Nokia 2016
Classification : Public

Monitoring Principles
VoLTE – bearers / protocol stacks
VoLTE utilizes at least the following two EPS bearers:
• Default EPS bearer for IMS PDN connectivity (QCI5 – SIP/SDP)
• Dedicated EPS bearer for VoLTE session/call (QCI1 – RTP/RTCP)
IR.92 requires support of the following radio bearers:
• UE must support: SRB1 + SRB2 + 4 x AM DRB + 1 x UM DRB
• Network must support: SRB1 + SRB2 + 2 x AM DRB + 1 x UM DRB
• QCI5 (Non-GBR) mapped on AM DRB, QCI1 (GBR) mapped on UM DRB

Both, VoLTE control plane (SIP/SDP) and media plane (RTP/RTCP), are
transparent to E-UTRAN (&EPC)! Radio access network treats this kind of
traffic as pure user plane payload with certain QoS.
This makes VoLTE troubleshooting just from EPS less efficient.

Control Plane (NAS)

User Plane (QCI5/ QCI1)

6 © Nokia 2016
Classification : Public

Performance Monitoring
KPI’s to be monitored

Attached workbook lists all the KPIs Aand counters that shall be monitored according to:
• KPI categories (accessibility, retainability,…)
• Purpose (main – for top level KPI monitoring, auxiliary – for drill down analysis)

VoLTE_KPI's_and_
Counters_FL16

7 © Nokia 2016
Classification : Public

Summary
VoLTE KPI’s in reports available in Reporting Suite (NPM)
System Program (RSLTE000) / System Program (cell level) (RSLTE001)
• System Program report provides an overview of network status. RSLTE000_-_Syste RSLTE001_-_Syste
m_Program m_Program_cell_level
• Contains group ‘VoLTE’ with VoLTE related Top level KPI’s

Usage - VoLTE (RSLTE052)

• This report provides information to monitor traffic load and VoLTE service quality. RSLTE052_-_VoLT
E

Mobility – HO analysis (RSLTE005)

• From FL16, it contains following VoLTE related groups:
RSLTE005_-_HO_a
- VoLTE handover, intra eNB nalysis

- VoLTE handover, inter eNB

- VoLTE handover, inter-frequency
- VoLTE handover, intra-frequency
- Service Based HO for VoLTE

8 © Nokia 2016
Classification : Public

Accessibility Appendix A
S1AP release causes
Retainability
Appendix B
Mobility (intra-LTE & inter-RAT) X2AP release causes

Quality / Integrity
Appendix C
VoLTE flow charts per
KPI category

9 © Nokia Solutions
2016 and Networks 2016 Confidential
Classification : Public

VoLTE KPI
Random access & RRC accessibility
• UE attempting to make either SIP registration or VoLTE call (MOC/MTC) could be either in RRC Connected or
RRC Idle state.
UE eNB EPC/IMS
• If UE is initially in RRC Idle state, it has to
go through random access and RRC setup PRACH MAC Random Access Preamble
procedure before it can initiate any SIP
PDCCH MAC RA-RNTI
related procedure ( SIP registration / VoLTE
call setup). PDSCH MAC Random Access Response
• Random access procedure as well as RRC
RRCConnectionRequest
Connection Setup procedure has no
VoLTE specifics. PDSCH MAC Contention Resolution

• From KPI monitoring, assessment and

RRCConnectionSetup
troubleshooting point of view it could be
treated the same way as for a regular RRC-ConnectionSetupComplete
LTE.
S1AP:(SIP
E-RAB (QCI5 /QCI1) setup & SIP procedures INITIAL UE MESSAGE
registration / VoLTE call setup)

10 © Nokia 2016
Classification : Public

VoLTE KPI
Random access & RRC accessibility
• By default VoLTE reuses existing RRC establishement causes. Based on these causes it’s not possible to distinguish
between data calls and VoLTE calls. For example, in case of MOC VoLTE call the RRC establishment cause would
be “mo-Data”
• TS 36.331 V12.8.0 (2015-12) introduces new RRC connection establishment cause “mo-VoiceCall”. However, this
cause is not supported in the current Nokia system release (FL16)

11 © Nokia 2016 SIB2: voiceServiceCauseIndication

Indicates whether UE is requested to use the establishment cause mo-VoiceCall for mobile originating MMTEL voice calls.
Classification : Public

VoLTE KPI
‘IMS’ default bearer accessibility
• Every VoLTE UE need to have default bearer for well known APN “IMS” established in order to make
SIP registration. Only when UE is registered in IMS, it can initiate and receive VoLTE calls.

• Default bearer for IMS PDN connectivity uses QCI5.

Note1:
E-RAB could be set up either via Initial Context Setup (initial E-RAB)
procedure or E-RAB setup (additional E-RAB) procedure
Note2:
It depends on operator’s trategy whether ‘IMS’ default bearer (QCI5) gets
established prior to ‘internet’ default bearer or not.

12 © Nokia 2016
Classification : Public

VoLTE KPI
‘IMS’ default bearer accessibility
E-UTRAN E-RAB Setup Success Ratio, QCI5 [LTE_5646a], unit: %
This KPI indicates the setup success ratio of the elementary E-RAB setup procedure, used to set up the E-RAB between MME and UE
for QCI5 DRBs. It indicates the E-UTRAN's contribution to network accessibility for the end user, not the whole end-to-end service
accessibility.

Formula: (Logical)
E-RAB SSR QCI5=(E-RAB setup successes QCI5 / E-RAB setup attempts QCI5)*100%

Formula: (NE names)

100*sum([Successfully established initial E-RABs of QCI5] + [Successfully establishedadditional E-RABs of QCI5]) / sum([Setup
attempts for initial E-RABs of QCI5] + [Setupattempts for additional E-RABs of QCI5])

Formula: (NetAct names)

100*sum(ERAB_INI_SETUP_SUCC_QCI5 + ERAB_ADD_SETUP_SUCC_QCI5) /sum(ERAB_INI_SETUP_ATT_QCI5 +
ERAB_ADD_SETUP_ATT_QCI5)

13 © Nokia 2016
Classification : Public

VoLTE KPI
‘IMS’ default bearer accessibility
ERAB_INI_SETUP_ATT_QCI5 [M8006C192]
• This measurement provides the number of setup attempts for initial E-RABs of QCI5
• Reception of an S1AP:INITIAL CONTEXT SETUP REQUEST message sent by the MME to the eNB. The counter is updated with the number of
QCI5 bearers contained in the "E-RAB to Be Setup List" IE.
ERAB_INI_SETUP_SUCC_QCI5 [M8006C210]
• This measurement provides the number of successfully established initial E-RABs of QCI5.
• Transmission of an S1AP:INITIAL CONTEXT SETUP RESPONSE message sent by eNB to the MME. The counter is updated with the number of
QCI5 bearers contained in the "E-RAB Setup List" IE.

eNB MME

ERAB_INI_SETUP_ATT_QCI5 [M8006C192] INITIAL CONTEXT SETUP REQUEST

ERAB_INI_SETUP_SUCC_QCI5 [M8006C210] INITIAL CONTEXT SETUP RESPONSE

14 © Nokia 2016
Classification : Public

VoLTE KPI
‘IMS’ default bearer accessibility
ERAB_ADD_SETUP_ATT_QCI5 [M8006C201]
• This measurement provides the number of setup attempts for additional E-RABs of QCI5.
• Reception of an S1AP:E-RAB SETUP REQUEST message sent by the MME to the eNB. The counter is updated with the number of QCI5 bearers
contained in the "E-RAB to Be Setup List" IE.
ERAB_ADD_SETUP_SUCC_QCI5 [M8006C219]
• This measurement provides the number of successfully established additional E-RABs of QCI5.
• Transmission of an S1AP:E-RAB SETUP RESPONSE message sent by eNB to the MME. The counter is updated with the number of QCI5 bearers
contained in the "E-RAB Setup List" IE.

eNB MME

ERAB_ADD_SETUP_ATT_QCI5 [M8006C201] E-RAB SETUP REQUEST

ERAB_ADD_SETUP_SUCC_QCI5 [M8006C219] E-RAB SETUP RESPONSE

15 © Nokia 2016
Classification : Public

VoLTE KPI
‘IMS’ default bearer accessibility
• If E-UTRAN E-RAB Setup Success Ratio, QCI5
[LTE_5646a] equals to ‘0’, check:
- whether there are any QCI5 setup attempts at all: E-UTRAN E-
RAB Setup Attempts, QCI5 [LTE_5641a]
- eNB configuration whether QCI5 is supported
(LNBTS:qciTab5/qciSupp=ENABLE)

E-UTRAN E-RAB Setup Attempts, QCI5 [LTE_5641a], unit: #

The KPI indicates the number of E-RAB setup attempts for QCI5.
Formula: (Logical)
E-RAB Satt QCI5= E-RAB setup init attempts for QCI5 + E-RAB setup add attempts for
QCI5
Formula: (NE names)
sum([Setup attempts for initial E-RABs of QCI5] + [Setup attempts for additional E-RABs
of QCI5])
Formula: (NetAct names)
16 © Nokia 2016
sum(ERAB_INI_SETUP_ATT_QCI5 + ERAB_ADD_SETUP_ATT_QCI5)
Classification : Public INITIAL CONTEXT SETUP RESPONSE
IE/Group Name Presence Range IE type and Semantics Criticality Assigned

VoLTE KPI Message Type

MME UE S1AP ID
M
M
reference
9.2.1.1
9.2.3.3
description
YES
YES
Criticality
reject
ignore

‘IMS’ default bearer accessibility

eNB UE S1AP ID M 9.2.3.4 YES ignore
E-RAB Setup List 1 YES ignore
>E-RAB Setup Item IEs 1 .. <maxnoofE- EACH ignore
RABs>
>>E-RAB ID M 9.2.1.2 -
• For worst performing cells in terms of E- >>Transport Layer
Address
M 9.2.2.1 -

>>GTP-TEID M 9.2.2.2 -
UTRAN E-RAB Setup Success Ratio, E-RAB Failed to Setup List O E-RAB List
9.2.1.36
A value for E-
RAB ID shall
YES ignore

QCI5 [LTE_5646a] collect traces only be present

once in E-RAB

(containing at least S1AP) and check the E-RAB for Setup List IE
and E-RAB
‘IMS’ (QCI5) Failed to Setup
cause(s) of the failures in the Criticality Diagnostics O 9.2.1.21
List IE.
YES ignore
corresponding S1AP messages:
- INITIAL CONTEXT SETUP RESPONSE E-RAB SETUP RESPONSE
IE/Group Name Presence Range IE type and Semantics Criticality Assigned
- E-RAB SETUP RESPONSE reference description Criticality
Message Type M 9.2.1.1 YES reject
- INITIAL CONTEXT SETUP FAILURE MME UE S1AP ID M 9.2.3.3 YES ignore
eNB UE S1AP ID M 9.2.3.4 YES ignore
E-RAB Setup List 0..1 YES ignore
E-RAB List >E-RAB Setup Item IEs 1 .. <maxnoof E- EACH ignore
IE/Group Presence Range IE type and Semantics Critica Assigned RABs>
Name reference description lity Criticality >>E-RAB ID M -
E-RAB List 1 .. EACH ignore >>Transport Layer Address M 9.2.2.1 -
Item <maxnoofE >>GTP-TEID M 9.2.2.2 eNB TEID. -
-RABs> E-RAB Failed to Setup List O E-RAB List A value for E- YES ignore
>E-RAB ID M 9.2.1.2 - - 9.2.1.36 RAB ID shall
>Cause M 9.2.1.3 - - only be present
once in E-RAB
Setup List IE
E-RAB for and in E-RAB
Failed to Setup
‘IMS’ (QCI5) List IE.
Details on causes are in Appendix A Criticality Diagnostics O 9.2.1.21 YES ignore
17 © Nokia 2016
Classification : Public

VoLTE KPI
‘IMS’ default bearer accessibility
• For worst performing cells in terms of E- eNB MME

UTRAN E-RAB Setup Success Ratio,

INITIAL CONTEXT SETUP REQUEST
QCI5 [LTE_5646a] collect traces
(containing at least S1AP) and check the INITIAL CONTEXT SETUP FAILURE
cause(s) of the failures in the
corresponding S1AP messages:
- INITIAL CONTEXT SETUP RESPONSE
INITIAL CONTEXT SETUP FAILURE
- E-RAB SETUP RESPONSE If the eNB is not able to establish an S1 UE context, or cannot even establish
- INITIAL CONTEXT SETUP FAILURE one non GBR bearer it shall consider the procedure as failed and reply with
the INITIAL CONTEXT SETUP FAILURE message.
IE/Group Name Presence Range IE type and Semantics Criticality Assigned
reference description Criticality
Message Type M 9.2.1.1 YES reject
MME UE S1AP ID M 9.2.3.3 YES ignore
eNB UE S1AP ID M 9.2.3.4 YES ignore
Details on causes are in Appendix A Cause
Criticality Diagnostics
M
O
9.2.1.3
9.2.1.21
YES
YES
ignore
ignore

18 © Nokia 2016
Classification : Public

VoLTE KPI
Dedicated bearer (QCI1) accessibility
• VoLTE call utilizes dedicated bearer (QCI1) for media plane (RTP/RTCP).
• From EUTRAN perspective VoLTE call setup is represented by E-RAB (QCI1) setup

E-RAB (QCI1) setup

Continuation of SIP signaling related to VoLTE call setup

19 © Nokia 2016
Classification : Public

VoLTE KPI
Dedicated bearer (QCI1) accessibility
E-UTRAN E-RAB Setup Success Ratio, QCI1 [LTE_5204b], unit: %
The KPI indicates the setup success ratio for the elementary E-RAB setup procedure, used to set up the E-RAB between MME and UE
for QCI1 DRBs. It indicates the E-UTRAN's contribution to network accessibility for the end user, not the whole end-to-end service
accessibility.

Formula: (Logical)
E-RAB SSR QCI1=(E-RAB setup successes QCI1 / E-RAB setup attempts QCI1)*100%

Formula: (NE names)

100*sum([Successfully established initial E-RABs of QCI1] + [Successfully establishedadditional E-RABs of QCI1]) / sum([Setup
attempts for initial E-RABs of QCI1] + [Setupattempts for additional E-RABs of QCI1])

Formula: (NetAct names)

100*sum(ERAB_INI_SETUP_SUCC_QCI1 + ERAB_ADD_SETUP_SUCC_QCI1) /sum(ERAB_INI_SETUP_ATT_QCI1 +
ERAB_ADD_SETUP_ATT_QCI1)

20 © Nokia 2016
Classification : Public

VoLTE KPI
Dedicated bearer (QCI1) accessibility
ERAB_INI_SETUP_ATT_QCI1 [M8006C188]
• This measurement provides the number of setup attempts for initial E-RABs of QCI1
• Reception of an S1AP:INITIAL CONTEXT SETUP REQUEST message sent by the MME to the eNB. The counter is updated with the number of
QCI1 bearers contained in the "E-RAB to Be Setup List" IE.
ERAB_INI_SETUP_SUCC_QCI1 [M8006C206]
• This measurement provides the number of successfully established initial E-RABs of QCI1.
• Transmission of an S1AP:INITIAL CONTEXT SETUP RESPONSE message sent by eNB to the MME. The counter is updated with the number of
QCI1 bearers contained in the "E-RAB Setup List" IE.

eNB MME

ERAB_INI_SETUP_ATT_QCI1 [M8006C188] INITIAL CONTEXT SETUP REQUEST

ERAB_INI_SETUP_SUCC_QCI1 [M8006C206] INITIAL CONTEXT SETUP RESPONSE

21 © Nokia 2016
Classification : Public

VoLTE KPI
Dedicated bearer (QCI1) accessibility
ERAB_ADD_SETUP_ATT_QCI1 [M8006C197]
• This measurement provides the number of setup attempts for additional E-RABs of QCI1.
• Reception of an S1AP:E-RAB SETUP REQUEST message sent by the MME to the eNB. The counter is updated with the number of QCI1 bearers
contained in the "E-RAB to Be Setup List" IE.
ERAB_ADD_SETUP_SUCC_QCI1 [M8006C215]
• This measurement provides the number of successfully established additional E-RABs of QCI1.
• Transmission of an S1AP:E-RAB SETUP RESPONSE message sent by eNB to the MME. The counter is updated with the number of QCI1 bearers
contained in the "E-RAB Setup List" IE.

eNB MME

ERAB_ADD_SETUP_ATT_QCI1 [M8006C197] E-RAB SETUP REQUEST

ERAB_ADD_SETUP_SUCC_QCI1 [M8006C215] E-RAB SETUP RESPONSE

22 © Nokia 2016
Classification : Public

VoLTE KPI
Dedicated bearer (QCI1) accessibility
• If E-UTRAN E-RAB Setup Success Ratio, QCI1
[LTE_5204b] equals to ‘0’, check:
- whether there are any QCI1 setup attempts at all: E-UTRAN E-
RAB Setup Attempts, QCI1 [LTE_5205b]
- eNB configuration whether QCI1 is supported
(LNBTS:qciTab1/qciSupp=ENABLE)

E-UTRAN E-RAB Setup Attempts, QCI1 [LTE_5205b], unit: #

The KPI indicates the number of E-RAB setup attempts for QCI1.
Formula: (Logical)
E-RAB Satt QCI1= E-RAB setup init attempts for QCI1 + E-RAB setup add attempts for
QCI1
Formula: (NE names)
sum([Setup attempts for initial E-RABs of QCI1] + [Setup attempts for additional E-RABs
of QCI1])
Formula: (NetAct names)
23 © Nokia 2016
sum(ERAB_INI_SETUP_ATT_QCI1 + ERAB_ADD_SETUP_ATT_QCI1)
Classification : Public INITIAL CONTEXT SETUP RESPONSE
IE/Group Name Presence Range IE type and Semantics Criticality Assigned

VoLTE KPI Message Type

MME UE S1AP ID
M
M
reference
9.2.1.1
9.2.3.3
description
YES
YES
Criticality
reject
ignore

Dedicated bearer (QCI1) accessibility

eNB UE S1AP ID M 9.2.3.4 YES ignore
E-RAB Setup List 1 YES ignore
>E-RAB Setup Item IEs 1 .. <maxnoofE- EACH ignore
RABs>
>>E-RAB ID M 9.2.1.2 -
• For worst performing cells in terms of E- >>Transport Layer
Address
M 9.2.2.1 -

>>GTP-TEID M 9.2.2.2 -
UTRAN E-RAB Setup Success Ratio, E-RAB Failed to Setup List O E-RAB List
9.2.1.36
A value for E-
RAB ID shall
YES ignore

QCI1 [LTE5_204b] collect traces only be present

once in E-RAB

(containing at least S1AP) and check the E-RAB Setup List IE

and E-RAB
(QCI1) Failed to Setup
cause(s) of the failures in the Criticality Diagnostics O 9.2.1.21
List IE.
YES ignore
corresponding S1AP messages:
- INITIAL CONTEXT SETUP RESPONSE E-RAB SETUP RESPONSE
IE/Group Name Presence Range IE type and Semantics Criticality Assigned
- E-RAB SETUP RESPONSE reference description Criticality
Message Type M 9.2.1.1 YES reject
- INITIAL CONTEXT SETUP FAILURE MME UE S1AP ID M 9.2.3.3 YES ignore
eNB UE S1AP ID M 9.2.3.4 YES ignore
E-RAB Setup List 0..1 YES ignore
E-RAB List >E-RAB Setup Item IEs 1 .. <maxnoof E- EACH ignore
IE/Group Presence Range IE type and Semantics Critica Assigned RABs>
Name reference description lity Criticality >>E-RAB ID M -
E-RAB List 1 .. EACH ignore >>Transport Layer Address M 9.2.2.1 -
Item <maxnoofE >>GTP-TEID M 9.2.2.2 eNB TEID. -
-RABs> E-RAB Failed to Setup List O E-RAB List A value for E- YES ignore
>E-RAB ID M 9.2.1.2 - - 9.2.1.36 RAB ID shall
>Cause M 9.2.1.3 - - only be present
once in E-RAB
Setup List IE
E-RAB and in E-RAB
Failed to Setup
(QCI1) List IE.
Details on causes are in Appendix A Criticality Diagnostics O 9.2.1.21 YES ignore
24 © Nokia 2016
Classification : Public

VoLTE KPI
Dedicated bearer (QCI1) accessibility
• For worst performing cells in terms of E- eNB MME

UTRAN E-RAB Setup Success Ratio,

INITIAL CONTEXT SETUP REQUEST
QCI1 [LTE_5204b] collect traces
(containing at least S1AP) and check the INITIAL CONTEXT SETUP FAILURE
cause(s) of the failures in the
corresponding S1AP messages:
- INITIAL CONTEXT SETUP RESPONSE
INITIAL CONTEXT SETUP FAILURE
- E-RAB SETUP RESPONSE If the eNB is not able to establish an S1 UE context, or cannot even establish
- INITIAL CONTEXT SETUP FAILURE one non GBR bearer it shall consider the procedure as failed and reply with
the INITIAL CONTEXT SETUP FAILURE message.
IE/Group Name Presence Range IE type and Semantics Criticality Assigned
reference description Criticality
Message Type M 9.2.1.1 YES reject
MME UE S1AP ID M 9.2.3.3 YES ignore
eNB UE S1AP ID M 9.2.3.4 YES ignore
Details on causes are in Appendix A Cause
Criticality Diagnostics
M
O
9.2.1.3
9.2.1.21
YES
YES
ignore
ignore

25 © Nokia 2016
Classification : Public

VoLTE KPI
Dedicated bearer (QCI1) accessibility
• In case the cause of dedicated bearer setup in S1AP is
“Radio Network Layer: Invalid QoS combination”, check:
- eNB configuration whether QCI1 is supported
(LNBTS:qciTab1/qciSupp=ENABLE)
- eNB configuration whether the maximum GBR for downlink and
uplink (LNBTS:qciTab1/maxGbrDl, LNBTS:qciTab1/maxGbrUl)
is greated that what’s requested in E-RAB setup:
E-RAB to be Setup List

BR
ax G
>E-RAB To Be Setup Item IEs

<m
>>E-RAB Level QoS Parameters

R
GB
>>>GBR QoS Information
>>>>E-RAB Guaranteed Bit Rate Downlink / Uplink

26 © Nokia 2016
Classification : Public RAC – Radio Admission Control

VoLTE KPI
Dedicated bearer (QCI1) accessibility
• In case the cause of dedicated bearer setup in S1AP is “Radio Network Layer: Radio resources not
available”, check:
- activation status of feature Smart Admission Cotrol (LTE497) (LNBTS:actEnhAcAndGbrServices) and the
corresponding parameterization

LTE497

- settings of counter based RAC (LNCEL:maxNumQci1Drb) if the above listed feature is not enabled
- cell load via the following KPI’s:
• E-UTRAN Average Number of Simultaneous QCI1 E-RABs [LTE_5394a]
RSLTE052_-_VoLT RSLTE054_-_Capa
• E-UTRAN Maximum Number of Simultaneous QCI1 E-RABs [LTE_5610a] E city

• Additional KPI’s as defined in Nokia predefined reports in NPM: RSLTE052 “VoLTE” & RSLTE054 “Capacity”
- If the radio is congested, initiate radio extension feasible for the site under investigation -> capacity management task

27 © Nokia 2016
Classification : Public TAC – Transport Admission Control

VoLTE KPI
Dedicated bearer (QCI1) accessibility
• In case the cause of dedicated bearer setup in S1AP is “Transport Layer: Transport Resource
Unavailable”, check:
- parameterization of feature Transport Admission Cotrol (LTE144) and Measurement based TAC (LTE1401)

LTE144 LTE1401
- cell load via the following KPI’s:
• feature related counters (as listed in the feature description document) RSLTE048_-_TAC_
traffic_per_TAC_Interface
• Nokia predefined report in NPM: RSLTE048 “TAC traffic per TAC Interface”
- If the transport is congested, initiate transport extension with corresponding TAC parameter tuning -> capacity
management task

28 © Nokia 2016
Classification : Public

Accessibility Appendix A
S1AP release causes
Retainability
Appendix B
Mobility (intra-LTE & inter-RAT) X2AP release causes

Quality / Integrity
Appendix C
VoLTE flow charts per
KPI category

29 © Nokia Solutions
2016 and Networks 2016 Confidential
Classification : Public

VoLTE KPI
Dedicated bearer (QCI1) retainability
Example of normal VoLTE call clearing
• From EUTRAN perspective VoLTE call is
successfully cleared if dedicated bearer (QCI1) gets
released ‘normally’.
• Any eventual ‘abnormal’ release of dedicated bearer
(QCI1) degrades retainability of VoLTE
• Retainability for data and voice can’t be directly
compared due to different average holding time of
each service: E-RAB (QCI1) release

• Average data session duration is typically ≈ 10-15sec UE init

UE rec
• Average voice call duration is typically ≈ 60-120sec
• Therefore, call drop rate for voice is expected to be
4x – 12x higher compared to call drop rate for data
services.

30 © Nokia 2016
Classification : Public

VoLTE KPI
Dedicated bearer (QCI1) retainability
• E-RAB release counters are updated based on specific signaling on S1 interface (S1AP)
• There are two main categories. Each category contains several counters per release cause:
Each bearer of the E-RAB to be Released
eNB initiated E-RAB release EPC initiated E-RAB release
List IE is counted.
eNB MME eNB MME Note: According to IR.92 “IMS Profile for
QCI1 Voice and SMS” only one QC1 bearer can
QCI1
E-RAB RELEASE COMMAND be created for UE:
E-RAB RELEASE INDICATION
“Since the minimum requirement for the
E-RAB RELEASE RESPONSE UE is the support of one (1) UM bearer
which is used for voice (see Section 7.3.1
and Annex B in 3GPP TS 36.331 [52]), the
eNB MME eNB MME network must not create more than one
dedicated bearer for voice media.
UE CONTEXT RELEASE COMMAND Therefore, the UE and network must be
UE CONTEXT RELEASE REQUEST able to multiplex the media streams from
UE CONTEXT RELEASE COMPLETE multiple concurrent voice sessions.”

31 © Nokia 2016
Classification : Public

VoLTE KPI Measurement ID 8006: LTE EPS Bearer

Dedicated bearer (QCI1) retainability eNB initiated E-RAB release
Counter ID Network Element Name NetAct Name Description Updated Unit
M8006C176 Released active ERABs QCI1 ERAB_REL_ENB_ACT_QCI1 This measurement provides the number of released active E-RABs The counters must be updated in case that user data are buffered Integer number
(that is when there was user data in the queue at the time of (UL/DL) for an E-RAB with QCI1 characteristics and the "S1AP UE
release) with QCI1 characteristics. The release is initiated by the Context Release Request" message is sent by eNB to the MME with
eNB due to radio connectivity problems. the release cause "RNL Radio Connection with UE lost".
M8006C266 Total number of released QCI1 E-RABs ERAB_REL_ENB_QCI1 This measurement provides the total number of eNB-initiated This counter is updated following the transmission of an S1AP:E- Integer number
initiated by the eNB releases of QCI1 E-RABs regardless of the release cause. RAB RELEASE INDICATION or an S1AP:UE CONTEXT RELEASE
REQUEST message sent by the eNB to the MME. The counter is
incremented with the number of QCI1 E-RABs released
independently from the release cause (3GPP TS 36.413).
M8006C267 eNB initiated QCI1 E-RAB releases due ERAB_REL_ENB_RNL_INA_QCI1 This measurement provides the number of QCI1 E-RABs released This counter is updated following the transmission of an S1AP:UE Integer number
to user inactivity due to user inactivity. CONTEXT RELEASE REQUEST message with the RNL cause
"User Inactivity" sent by the eNB to the MME. The counter is
incremented with the number of released QCI1 E-RABs (3GPP TS
36.413).
M8006C268 eNB initiated QCI1 E-RAB releases due ERAB_REL_ENB_RNL_UEL_QCI1 This measurement provides the number of QCI1 E-RABs released This counter is updated following the transmission of an S1AP:UE Integer number
to loss of connection to the UE if the connection to the UE is lost. CONTEXT RELEASE REQUEST message with the RNL cause
"Radio Connection with UE lost" sent by the eNB to the MME. If the
S1AP:UE CONTEXT RELEASE REQUEST message with the RNL
cause "Radio Connection with UE lost" is sent due to a failed intra
eNB HO, (for example, expiration of HO guard timer THOoverall), the
counter ERAB_REL_HO_FAIL_TIM_QCI1 is incremented instead.
The counter is incremented with the number of released QCI1 E-
RABs (3GPP TS 36.413).
M8006C269 eNB initiated QCI1 E-RAB releases due ERAB_REL_ENB_TNL_TRU_QCI1 This measurement provides the number of QCI1 E-RABs released This counter is updated following the transmission of an S1AP:E- Integer number
to insufficient transport resources if the associated transport resources are not available anymore. RAB RELEASE INDICATION message or an S1AP:UE CONTEXT
RELEASE REQUEST message sent by the eNB to the MME with
the TNL cause "Transport Resources Unavailable". The counter is
incremented with the number of released QCI1 E-RABs (3GPP TS
36.413).
M8006C270 eNB initiated QCI1 E-RAB releases due ERAB_REL_ENB_RNL_RED_QCI1 This measurement provides the number of QCI1 E-RABs released This counter is updated following the transmission of an S1AP:UE Integer number
to redirect to another cell if the UE gets redirected to another cell. CONTEXT RELEASE REQUEST message sent by the eNB to the
MME with the RNL causes "Inter-RAT redirection", "Redirection
towards 1xRTT", "CS Fallback Triggered", "UE Not Available For PS
Service", or "E-UTRAN Generated Reason" if the release cause is
set due to an intra-LTE redirect. The counter is incremented with the
number of released QCI1 E-RABs (3GPP TS 36.413).

32 © Nokia 2016
Classification : Public

VoLTE KPI Measurement ID 8006: LTE EPS Bearer

Dedicated bearer (QCI1) retainability eNB initiated E-RAB release
Counter ID Network Element Name NetAct Name Description Updated Unit
M8006C271 eNB initiated QCI1 E-RAB releases due ERAB_REL_ENB_RNL_EUGR_QCI1 This measurement provides the number of QCI1 E-RABs released This counter is updated following the transmission of an S1AP:UE Integer number
to E-UTRAN Generated Reason due to E-UTRAN-generated reasons. CONTEXT RELEASE REQUEST message with the RNL cause "E-
UTRAN Generated Reason" sent by the eNB to the MME if the
release cause is not set due to an intra-LTE redirect. The counter is
incremented with the number of released QCI1 E-RABs (3GPP TS
36.413).
M8006C272 eNB initiated QCI1 E-RAB releases due ERAB_REL_ENB_RNL_RRNA_QCI1 This measurement provides the number of QCI1 E-RABs released This counter is updated following the transmission of an S1AP:E- Integer number
to "Radio Network Layer Cause - Radio due to pre-emption if the available radio resources are insufficient. RAB RELEASE INDICATION or an S1AP:UE CONTEXT RELEASE
resources not available" REQUEST message sent by the eNB to the MME. The counter is
incremented with the number of QCI1 E-RABs released with the RNL
cause "Radio resources not available" (3GPP TS 36.413).
M8006C273 QCI1 E-RABs released due to partial ERAB_REL_HO_PART_QCI1 This measurement provides the number of QCI1 E-RABs released Intra-eNB HO: Integer number
Handover due to a partial HO. The partial HO means that the HO for the n.a.
admitted E-RABs was successfully completed, although not all E-
RABs were admitted by the HO target during HO preparation. The Inter-eNB HO via X2:
counter is incremented with the number of QCI1 E-RABs not Following the reception of the X2AP:UE CONTEXT RELEASE
admitted by the HO target. The counter is maintained in the source message, the counter is incremented with the number of QCI1
cell. bearers not admitted by the target eNB of the preceding HO
preparation procedure. The bearers, which are not admitted, are
t
his do cu men contained in the "E-RABs Not Admitted List" IE of the
X2AP:HANDOVER REQUEST ACKNOWLEDGE message that is

s e ct i on o f t received from the target eNB (3GPP TS 36.423).

il i t y
d in mo b Inter-eNB HO via S1/Inter-system HO to UTRAN/SRVCC to UTRAN:
c o v e re Following the reception of the S1AP:UE CONTEXT RELEASE
COMMAND message with the cause "RNL Successful Handover",
the counter is incremented with the number of QCI1 bearers not
admitted by the HO target of the preceding HO preparation
procedure. The bearers, which are not admitted, are contained in the
"E-RABs to Release List" IE of the S1AP:HANDOVER COMMAND
message that is received from MME (3GPP TS 36.413).

33 © Nokia 2016
Classification : Public

VoLTE KPI Measurement ID 8006: LTE EPS Bearer

Dedicated bearer (QCI1) retainability EPC initiated E-RAB release

Counter ID Network Element Name NetAct Name Description Updated Unit

M8006C89 EPC initiated EPS Bearer EPC_EPS_BEAR_REL_REQ_ The number of EPC-initiated EPS Bearer Release The reception of an S1AP:E-RAB Release Command Integer
Release requests for QCI1 due N_QCI1 requests for QCI1 due to normal release by UE. Each or an S1AP:UE Context Release Command message number
to Normal release by UE bearer of the E-RAB to be Released List IE is sent by the MME to eNB.
counted.
M8006C98 EPC initiated EPS Bearer EPC_EPS_BEAR_REL_REQ_ The number of EPC-initiated EPS Bearer Release The reception of an S1AP:E-RAB Release Command Integer
Release requests for QCI1 due D_QCI1 requests for QCI1 due to the Detach procedure by the or an S1AP:UE Context Release Command message number
to Detach procedure by UE or UE or the MME. Each bearer of the E-RAB to be sent by the MME to eNB.
MME Released List IE is counted.
M8006C107 EPC initiated EPS Bearer EPC_EPS_BEAR_REL_REQ_ The number of EPC-initiated EPS Bearer Release The reception of an S1AP:E-RAB Release Command Integer
Release requests per QCI1 R_QCI1 requests for QCI1 due to the Radio Network Layer or an S1AP:UE Context Release Command message number
due to Radio Network Layer cause. Each bearer of the E-RAB to be Released List sent by the MME to eNB.
cause IE is counted.
M8006C116 EPC initiated EPS Bearer EPC_EPS_BEAR_REL_REQ_ The number of EPC-initiated EPS Bearer Release The reception of an S1AP:E-RAB Release Command Integer
Release requests for QCI1 due O_QCI1 requests for QCI1 due to Other causes. Each bearer or an S1AP:UE Context Release Command message number
to Other causes of the E-RAB to be Released List IE is counted. sent by the MME to eNB.The counter is updated if the
release request detected does not match any other
failure counter.
M8006C278 EPC initiated QCI1 E-RAB ERAB_REL_EPC_PATH_SWIT This measurement provides the number of QCI1 E- This counter is incremented with the number of QCI1 E- Integer
releases due to Path Switch CH_QCI1 RABs abnormally released in case that EPC has RABs contained in the "E-RAB To Be Released List " of number
failed to perform the UP path switch for at least one, the S1AP: PATH SWITCH ACKNOWLDEGE message,
covered in mobility section of this document but not for all, of the E-RABs included in the preceding which is received from the MME (3GPP TS 36.413).
S1AP: PATH SWITCH REQUEST.

34 © Nokia 2016
Classification : Public

VoLTE KPI
Dedicated bearer (QCI1) retainability
• E-RAB release counters per cause for both categories (eNB initiated / EPC initiated) shall be collected on cell level
and distribution shall be made.
• Most frequent ‘abnormal’ causes shall be anaysed and corresponding most typical failure scenarios shall be
identified along with the root causes.
• The essential task is to make categorization of causes - which cause should be considered as ‘normal’ and which
causes as ‘abnormal’
• Following slides provide certain guidance for the E-RAB counters per causes in respect to categorization
‘normal’/’abnormal’ release
• Note: All EPC initiated E-RAB releases are considered as ‘normal’ from E-UTRAN point of view as reflected in KPI
LTE_5572c, LTE_5571d, LTE_5209c. Neverthless, some of the ECP initiated E-RAB release counters are related to
‘abnormal’ behavior of EPC. Hence it is recommended to monitor and assess these counters as well

35 © Nokia 2016
Classification : Public

VoLTE KPI
Dedicated bearer (QCI1) retainability
eNB initiated QCI1 E-RAB releases due to loss of connection to the UE [M8006C268]
Released active ERABs QCI1 [M8006C176]
• Release cause: "RNL Radio Connection with UE lost“
• The latter counter considers only releases when there were user data in the queue at the time of release
• Abnormal release from user’s perspective
• Typically related to RLF, e.g. T310 expiry.
• Following features and their tuning can reduce pegging of this counter:
- LTE1617: RLF Triggered Handover
- LTE1569: QCI 1 specific RLF and reestablishment control
- LTE2206: Extended RLF handling
- LTE2098: VoLTE Uplink Coverage Boosting
- Mobility related features (intra-LTE, SRVCC)

36 © Nokia 2016
Classification : Public

VoLTE KPI
Dedicated bearer (QCI1) retainability
eNB initiated QCI1 E-RAB releases due to user inactivity [M8006C267]
• Release cause: "User Inactivity"
• Normal / Abnormal release
• Normal release: typically caused by user inactivity during ringtone (if ringtone generated locally in UE). UE goes to RRC idle mode
due to inactivity, for example, during a ringtone, which might last longer than a normal inactivity timer
- Probability increases with lover Inactivity Timer settings
- Could be eliminated with feature LTE2430: QCI1 Establishment Triggered Protection Timer
• Abnormal release: typically indicates mute call (both directions), i.e. no RTP neither RTCP traffic. Note: Prerequisite is that
inactivity is also detected for other established E-RAB’s (e.g. ‘internet’ APN).
- Detailed troubleshooting required
- Media plane (RTP, RTCP) traces need to be analysed on several interfaces involved
• Not considered as abnormal in KPI LTE_5572c, LTE_5209c

37 © Nokia 2016
Classification : Public

VoLTE KPI
Dedicated bearer (QCI1) retainability
eNB initiated QCI1 E-RAB releases due to insufficient transport resources [M8006C269]
• Release cause: "Transport Resources Unavailable"
• Abnormal release from user’s perspective
• As this counter is related to E-RAB release not setup, it’s not TAC (Transport Admission Control) related. TAC is done in case of
inter eNB mobility though – see mobility section
• Check transport related alarms for particular eNB(s) and parameterization of GTP-U path supervision (eNB <> S-GW)
• Typical failure scenarios to be identified

38 © Nokia 2016
Classification : Public

VoLTE KPI
Dedicated bearer (QCI1) retainability
eNB initiated QCI1 E-RAB releases due to redirect to another cell [M8006C270]
• Release cause: "Inter-RAT redirection", "Redirection towards 1xRTT", "CS Fallback Triggered", "UE Not Available For PS
Service", or "E-UTRAN Generated Reason" if the release cause is set due to an intra-LTE redirect.
• Normal / Abnormal release
• Normal release: from E-UTRAN point of view, redirection is a normal release as per system desing – i.e. conditions for redirection
fulfilled (corresponding A2 measurement event reported by UE)
• Abnormal release: from UE point of view, IRAT redirection during ongoing VoLTE call is abnormal as VoLTE call can’t be
sustained and need to be prematurely terminated. Normal procedure for VoLTE IRAT mobility is SRVCC not redirection!
• Check/optimize:
- Redirection thresholds (A2) and other related parameters
- SRVCC thresholds (A2/B2) and other related parameters
- Status of A2-based redirect for VoLTE calls (LNCEL:a2RedirectQci1)
• Not considered as abnormal in KPI LTE_5572c, LTE_5209c

39 © Nokia 2016
Classification : Public

VoLTE KPI
Dedicated bearer (QCI1) retainability
eNB initiated QCI1 E-RAB releases due to E-UTRAN Generated Reason [M8006C271]
• Release cause: "E-UTRAN Generated Reason" sent by the eNB to the MME if the release cause is not set due to an intra-LTE
redirect.
• Abnormal release from user’s perspective
• Typical failure scenarios to be identified
• Collect additional traces (UE, RRC, eNB internal,…) for further troubleshooting

40 © Nokia 2016
Classification : Public

VoLTE KPI
Dedicated bearer (QCI1) retainability
eNB initiated QCI1 E-RAB releases due to "Radio Network Layer Cause - Radio resources not available“
[M8006C272]
• Release cause: "Radio resources not available"
• Normal / Abnormal release
• Normal release: from E-UTRAN point of view, QCI1 E-RAB could be intentionally released if there are no radio resources
available.
• Abnormal release from user’s perspective
• As this counter is related to E-RAB release not setup, it’s not RAC (Radio Admission Control) related. RAC is done in case of inter-
cell mobility though – see mobility section
• Collect additional traces (UE, RRC, eNB internal,…) for further troubleshooting
• Not considered as abnormal in KPI LTE_5572c, LTE_5209c

41 © Nokia 2016
Classification : Public

VoLTE KPI
Dedicated bearer (QCI1) retainability
There are several Nokia standard KPIs for VoLTE (QCI1) retainability:

E-UTRAN E-RAB QCI1 Drop Ratio, RAN View [LTE_5572c], unit: %

This KPI describes the ratio of abnormally released (dropped) QCI1 E-RABs from RAN point of view.

E-UTRAN E-RAB QCI1 with data in the queue drop ratio, RAN View, RNL Failure with UE Lost [LTE_5571d], unit: %
This KPI indicates the ratio of a specific E-RAB drop (abnormal release) cause to all E-RAB releases. Cause: E-RAB QCI1 with data in the queue drop ratio, RAN View, RNL
Failure with UE Lost.

E-UTRAN E-RAB QCI1 Normal Release Ratio User Perspective [LTE_5209c], unit: %
This KPI describes the ratio of normally released QCI1 E-RABs from user perspective. This KPI is corresponding to a Connection Completion Ratio.

Important note: Formula versions above refer to FL16 system release. All three formulas have newer versions in FL16A!!!

42 © Nokia 2016
Classification : Public

VoLTE KPI
Dedicated bearer (QCI1) retainability
E-UTRAN E-RAB QCI1 Drop Ratio, RAN View [LTE_5572c], unit: %
This KPI describes the ratio of abnormally released (dropped) QCI1 E-RABs from RAN point of view.
Notes:
1. Each QCI1 bearer of the "Bearer to be Released List" IE is counted.
2. RAN point of view means that as abnormal E-RAB drops only those ones initiated by eNB are counted.
3. In the denominator of the formula normal and abnormal E-RAB releases except the successful intra LTE and inter RAT HO are counted.
4. QCI1 E-RAB releases due to S1 RESET are not counted at all.
5. Inter RAT HO to GERAN is excluded from counting on ERAB_REL_HO_PART and ERAB_REL_HO_PART_QCI1 because it is not certain whether the MME will include
the E-RAB with QCI#1 into the "E-RABs to Release List". So the restriction is not only in eNB side but also in EPC side.

Formula: (Logical)
E-RAB QCI1 DR RAN = (abnormal QCI1 E-RAB releases from RAN point of view / all QCI1 E-RABreleases) * 100%

43 © Nokia 2016
Classification : Public

VoLTE KPI
Dedicated bearer (QCI1) retainability
E-UTRAN E-RAB QCI1 Drop Ratio, RAN View [LTE_5572c], unit: %
Formula: (NE names)
100*sum([QCI1 E-RABs released due to partial Handover] + [Total number of released QCI1E-RABs initiated by the eNB] - [eNB
initiated QCI1 E-RAB releases due to user inactivity]- [eNB initiated QCI1 E-RAB releases due to redirect to another cell] - [eNB
initiatedQCI1 E-RAB releases due to "Radio Network Layer Cause - Radio resources not available"])
/
sum([Total number of released QCI1 E-RABs initiated by the eNB] + [QCI1 E-RABs releaseddue to partial Handover] + [EPC initiated
EPS Bearer Release requests for QCI1 due toNormal release by UE] + [EPC initiated EPS Bearer Release requests for QCI1 due to
Detachprocedure by UE or MME] + [EPC initiated EPS Bearer Release requests per QCI1 due toRadio Network Layer cause] + [EPC
initiated EPS Bearer Release requests for QCI1 due toOther causes] + [EPC initiated QCI1 E-RAB releases due to Path Switch])

Formula: (NetAct names)

100*sum(ERAB_REL_HO_PART_QCI1 + ERAB_REL_ENB_QCI1 - ERAB_REL_ENB_RNL_INA_QCI1 -
ERAB_REL_ENB_RNL_RED_QCI1 - ERAB_REL_ENB_RNL_RRNA_QCI1)
/
sum(ERAB_REL_ENB_QCI1 + ERAB_REL_HO_PART_QCI1 + EPC_EPS_BEAR_REL_REQ_N_QCI1
+EPC_EPS_BEAR_REL_REQ_D_QCI1 + EPC_EPS_BEAR_REL_REQ_R_QCI1 + EPC_EPS_BEAR_REL_REQ_O_QCI1
+ERAB_REL_EPC_PATH_SWITCH_QCI1)

44 © Nokia 2016
Classification : Public

VoLTE KPI
Dedicated bearer (QCI1) retainability
E-UTRAN E-RAB QCI1 with data in the queue drop ratio, RAN View, RNL Failure with UE Lost
[LTE_5571d], unit: %
This KPI indicates the ratio of a specific E-RAB drop (abnormal release) cause to all E-RAB releases. Cause: E-RAB QCI1 with data in
the queue drop ratio, RAN View, RNL Failure with UE Lost.
Notes:
1. Each bearer of the "Bearer to be Released List" IE is counted.
2. There is an overlapping in the abnormal E-RABs counted within the LTE_5090d and LTE_5570e but from network planning and optimization point of view it is mandatory
to have also an own indicator dealing with active E-RAB drops with data in the buffer only.
3. The formula LTE_5571d is needed to monitor the VoIP Call Drop Ratio.
4. In the denominator of the formula normal and abnormal E-RAB releases except the successful intra LTE and inter RAT HO are counted.
5. E-RAB releases due to S1 RESET are not counted at all.
6. E-RAB releases due to "No Radio Resources Available" initiated by eNB are counted as normal releases as they are not real drops resulted from any radio quality problems.
7. Inter RAT HO to GERAN is excluded from counting on ERAB_REL_HO_PART and ERAB_REL_HO_PART_QCI1 because it is not certain whether the MME will include
the E-RAB with QCI#1 into the "E-RABs to Release List". So the restriction is not only in eNB side but also in EPC side.

Formula: (Logical)
E-RAB DRCause = (abnormal E-RAB release request_x / all E-RAB releases) * 100%

45 © Nokia 2016
Classification : Public

VoLTE KPI
Dedicated bearer (QCI1) retainability
E-UTRAN E-RAB QCI1 with data in the queue drop ratio, RAN View, RNL Failure with UE Lost
[LTE_5571d], unit: %
Formula: (NE names)
100*sum([Released active ERABs QCI1])
/
sum([Total number of released QCI1 E-RABs initiated by the eNB] + [QCI1 E-RABs released due to partial Handover] + [EPC initiated
EPS Bearer Release requests for QCI1 due toNormal release by UE] + [EPC initiated EPS Bearer Release requests for QCI1 due to
Detach procedure by UE or MME] + [EPC initiated EPS Bearer Release requests per QCI1 due toRadio Network Layer cause] +
[EPC initiated EPS Bearer Release requests for QCI1 due toOther causes] + [EPC initiated QCI1 E-RAB releases due to Path
Switch])

Formula: (NetAct names)

100*sum(ERAB_REL_ENB_ACT_QCI1)
/
sum(ERAB_REL_ENB_QCI1 + ERAB_REL_HO_PART_QCI1 + EPC_EPS_BEAR_REL_REQ_N_QCI1
+EPC_EPS_BEAR_REL_REQ_D_QCI1 + EPC_EPS_BEAR_REL_REQ_R_QCI1 + EPC_EPS_BEAR_REL_REQ_O_QCI1
+ERAB_REL_EPC_PATH_SWITCH_QCI1)

46 © Nokia 2016
Classification : Public

VoLTE KPI
Dedicated bearer (QCI1) retainability
E-UTRAN E-RAB QCI1 Normal Release Ratio User Perspective [LTE_5209c], unit: %
This KPI describes the ratio of normally released QCI1 E-RABs from user perspective. This KPI is corresponding to a Connection
Completion Ratio.
Notes:
1. Each QCI1 bearer of the "Bearer to be Released List" IE is counted.
2. In both the numerator and denominator of the formula normal E-RAB releases except the successful intra LTE and inter RAT HO are counted.
3. QCI1 E-RAB releases due to S1 RESET are not counted at all.
4. Inter RAT HO to GERAN is excluded from counting on ERAB_REL_HO_PART and ERAB_REL_HO_PART_QCI1 because it is not certain whether the MME will include
the E-RAB with QCI#1 into the "E-RABs to Release List". So the restriction is not only in eNB side but also in EPC side.

Formula: (Logical)
E-RAB QCI1 NRR UP = (normal E-RAB QCI1 releases user perspective / all E-RAB QCI1 releases) * 100%

47 © Nokia 2016
Classification : Public

VoLTE KPI
Dedicated bearer (QCI1) retainability
E-UTRAN E-RAB QCI1 Normal Release Ratio User Perspective [LTE_5209c], unit: %

Formula: (NE names)

100*sum([eNB initiated QCI1 E-RAB releases due to user inactivity] + [eNB initiated QCI1E-RAB releases due to redirect to another
cell] + [eNB initiated QCI1 E-RAB releases dueto "Radio Network Layer Cause - Radio resources not available"] + [EPC initiated
EPSBearer Release requests for QCI1 due to Normal release by UE] + [EPC initiated EPS BearerRelease requests for QCI1 due to
Detach procedure by UE or MME]) / sum([EPC initiated EPSBearer Release requests for QCI1 due to Normal release by UE] + [EPC
initiated EPS BearerRelease requests for QCI1 due to Detach procedure by UE or MME] + [EPC initiated EPSBearer Release
requests per QCI1 due to Radio Network Layer cause] + [EPC initiated EPSBearer Release requests for QCI1 due to Other causes] +
[Total number of released QCI1E-RABs initiated by the eNB] + [QCI1 E-RABs released due to partial Handover] + [EPCinitiated
QCI1 E-RAB releases due to Path Switch])

Formula: (NetAct names)

100*sum(ERAB_REL_ENB_RNL_INA_QCI1 + ERAB_REL_ENB_RNL_RED_QCI1 +ERAB_REL_ENB_RNL_RRNA_QCI1 +
EPC_EPS_BEAR_REL_REQ_N_QCI1 + EPC_EPS_BEAR_REL_REQ_D_QCI1) /sum(EPC_EPS_BEAR_REL_REQ_N_QCI1 +
EPC_EPS_BEAR_REL_REQ_D_QCI1 +EPC_EPS_BEAR_REL_REQ_R_QCI1 + EPC_EPS_BEAR_REL_REQ_O_QCI1 +
ERAB_REL_ENB_QCI1 +ERAB_REL_HO_PART_QCI1 + ERAB_REL_EPC_PATH_SWITCH_QCI1)

48 © Nokia 2016
Classification : Public
E-RAB RELEASE INDICATION
VoLTE KPI IE/Group Name

Message Type
Presence

M
Range IE type and
reference
9.2.1.1
Semantics
description
Criticality

YES
Assigned
Criticality
ignore

Dedicated bearer (QCI1) retainability MME UE S1AP ID

eNB UE S1AP ID
M
M
9.2.3.3
9.2.3.4
YES
YES
reject
reject
E-RAB Released List M E-RAB List A value for E- YES ignore
9.2.1.36 RAB ID shall
only be present
• For worst performing cells in terms of: once in E-RAB
Released List
IE.
- E-UTRAN E-RAB QCI1 Drop Ratio, RAN View User Location O 9.2.1.93 YES ignore
[LTE_5572c] Information

- E-UTRAN E-RAB QCI1 with data in the queue drop E-RAB RELEASE COMMAND
ratio, RAN View, RNL Failure with UE Lost [LTE_5571d] IE/Group Name Presence Range IE type and Semantics Criticality Assigned
reference description Criticality
- E-UTRAN E-RAB QCI1 Normal Release Ratio User Message Type M 9.2.1.1 YES reject
MME UE S1AP ID M 9.2.3.3 YES reject
Perspective [LTE_5209c] eNB UE S1AP ID M 9.2.3.4 YES reject
UE Aggregate O 9.2.1.20 YES reject
collect traces (containing at least S1AP & X2AP) Maximum Bit Rate
E-RAB To Be Released M E-RAB List A value for E- YES ignore
and check the cause(s) of the failures in the List 9.2.1.36 RAB ID shall
only be present
corresponding S1AP messages: once in E-RAB
To Be Released
List IE.
- E-RAB RELEASE INDICATION NAS-PDU O 9.2.3.5 YES ignore

- E-RAB RELEASE COMMAND

IE/Group Name Presence Range IE type and Semantics Criticality Assigned
- UE CONTEXT RELEASE REQUEST reference description Criticality
E-RAB List Item 1 .. <maxnoofE- EACH ignore
- UE CONTEXT RELEASE COMMAND >E-RAB ID M
RABs>
9.2.1.2 - -
>Cause M 9.2.1.3 - -

Details on causes are in Appendix A

49 © Nokia 2016
Classification : Public

VoLTE KPI
Dedicated bearer (QCI1) retainability
• For worst performing cells in terms of: UE CONTEXT RELEASE REQUEST
- E-UTRAN E-RAB QCI1 Drop Ratio, RAN View IE/Group Name Presence Range IE type and Semantics Criticality Assigned
reference description Criticality
[LTE_5572c] Message Type M 9.2.1.1 YES ignore
MME UE S1AP ID M 9.2.3.3 YES reject
- E-UTRAN E-RAB QCI1 with data in the queue drop eNB UE S1AP ID M 9.2.3.4 YES reject
Cause M 9.2.1.3 YES ignore
ratio, RAN View, RNL Failure with UE Lost [LTE_5571d] GW Context Release O 9.2.1.84 YES reject
Indication
- E-UTRAN E-RAB QCI1 Normal Release Ratio User
Perspective [LTE_5209c] UE CONTEXT RELEASE COMMAND
collect traces (containing at least S1AP & X2AP) IE/Group Name Presence Range IE type and
reference
Semantics
description
Criticality Assigned
Criticality
and check the cause(s) of the failures in the Message Type
CHOICE UE S1AP IDs
M
M
9.2.1.1 YES
YES
reject
reject
corresponding S1AP messages: >UE S1AP ID pair
>>UE S1AP ID pair M 9.2.3.18
>MME UE S1AP ID
- E-RAB RELEASE INDICATION >>MME UE S1AP
ID
M 9.2.3.3

Cause M 9.2.1.3 YES ignore

- E-RAB RELEASE COMMAND
- UE CONTEXT RELEASE REQUEST
- UE CONTEXT RELEASE COMMAND

Details on causes are in Appendix A

50 © Nokia 2016
Classification : Public

VoLTE KPI
Dedicated bearer (QCI1) retainability
• For worst performing cells in terms of:
- E-UTRAN E-RAB Setup Success Ratio, QCI1 [LTE5204b]
- E-UTRAN E-RAB QCI1 Normal Release Ratio User Perspective [LTE_5209c]
- E-UTRAN E-RAB QCI1 Normal Release Ratio User Perspective [LTE_5209c]
collect traces (containing at least S1AP & X2AP) and check the cause(s) of the failures in the corresponding X2AP
messages:
- HANDOVER REQUEST ACKNOWLEDGE
- HANDOVER PREPARATION FAILURE
• Handover failures covered in mobility section of this document

51 © Nokia 2016
Classification : Public

VoLTE KPI
Default ‘IMS’ bearer (QCI5) retainability
• As default bearer for ‘IMS’ APN is a default bearer, it should coexist with default bearer for ‘Internet’ APN. From
that perspective, the retainability performance and troubleshooting could be combined for both default bearers. Note,
there could be even more than two default bearers depending on the network specific configuration.
• There’s currently just one counter related to QCI5 E-RAB retainability:

Counter ID Network Element Name NetAct Name Description Updated Unit

M8006C239 Released active ERABs QCI5 ERAB_REL_ENB_ACT_QCI5 This measurement provides the number of released active The counter is updated in case that user data are buffered Integer
E-RABs (that is when there was user data in the queue at (UL/DL) for an E-RAB with QCI5 characteristics and the number
the time of release) with QCI5 characteristics. The release "S1AP UE Context Release Request" message is sent by
is initiated by the eNB due to radio connectivity problems. eNB to the MME with the release cause "RNL Radio
Connection with UE lost".

52 © Nokia 2016
Classification : Public

Accessibility Appendix A
S1AP release causes
Retainability
Appendix B
Mobility (intra-LTE & inter-RAT) X2AP release causes

Quality / Integrity
Appendix C
VoLTE flow charts per
KPI category

53 © Nokia Solutions
2016 and Networks 2016 Confidential
Classification : Public

VoLTE KPI
Dedicated bearer (QCI1) mobility

Intra-LTE mobility Inter-RAT mobility (SRVCC)

Intra-cell LTE to 2G
Inter-cell / intra-eNB LTE to 3G
Inter-cell / inter-eNB
With PS
Intra-band Intra-frequency Without PS
Inter-frequency
coverage – based
Inter-band Inter-frequency load - based
service – based

X2 – based
S1 - based

coverage – based Basic categorization of VoLTE mobility

load - based Note: Not all categories are necessarily applicable to Orange –
service – based it depends on the feature set in use
capability - based

54 © Nokia 2016
Classification : Public Example: intra-LTE X2 based mobility
VoLTE KPI UE Source eNB Target eNB MME Serving Gateway

Dedicated bearer (QCI1) mobility

0. Area Restriction Provided
1. Measurement Control

packet data packet data

• Mobility (Handovers) typically consist of the UL allocation Legend

L3 signalling
2. Measurement Reports

following phases: 3. HO decision

L1/L2 signalling

User Data
4. Handover Request
- eNB configures measurements in UE

Handover Preparation
5. Admission Control
- UE solicitated measurements with event reporting (A3, A5, A2, B2,…) 6. Handover Request Ack
DL allocation

- HO decision in eNB 7.
RRC Conn. Reconf. incl.
mobilityControlinformation
Detach from old cell
Deliver buffered and in transit
- HO preparation (resource allocation in the target cell) and
synchronize to new cell
packets to target eNB

Handover Execution
- HO execution (UE moves to target cell) 8. SN Status Transfer

Data Forwarding
- HO completion (path switch, UE context release in the source cell)
Buffer packets from

• In general, mobility issues might be related to any of the 9. Synchronisation

Source eNB

above listed. 10. UL allocation + TA for UE

11. RRC Conn. Reconf. Complete

packet data
packet data
12. Path Switch Request
13. Modify Bearer
Request

End Marker
14. Switch DL path

Handover Completion
KPI’s and counters are related to these phases. End Marker
packet data
15. Modify Bearer
There are no HO counters per failure cause in the current system Response
16.Path Switch Request Ack
release (FL16). 17. UE Context Release

18. Release
Resources

55 © Nokia 2016
Classification : Public
GROUP: VoLTE handover, intra eNB
VoLTE KPI Preparation
E-UTRAN HO Preparation Success Ratio, intra
eNB for QCI1 %
LTE_5871a
Dedicated bearer (QCI1) mobility – KPI’s (intra-LTE)
/ HO prep SR intra eNB QCI1
E-UTRAN HO Preparations, intra eNB for QCI1
%
LTE_5872a / HO preps intra eNB QCI1
E-UTRAN HO Success Ratio, intra eNB for
QCI1 %
• KPI’s (& counters) are updated in the source cell of the LTE_5873a Execution / HO SR intra eNB QCI1
E-UTRAN HO Attempts, intra eNB for QCI1
handover! LTE_5874a / HO att intra eNB QCI1
#

E-UTRAN Total HO Success Ratio, intra eNB

• Note: Total = Preparation + Execution LTE_5875a Total

for QCI1
/ HO tot SR intra eNB QCI1
%

GROUP: VoLTE handover, inter eNB

E-UTRAN HO Preparation Success Ratio, inter
Preparation eNB X2 based for QCI1 %
GROUP: VoLTE handover, intra-frequency
E-UTRAN Intra-Frequency HO Success Ratio LTE_5876a / HO prep SR inter eNB X2 QCI1
for QCI1 E-UTRAN HO Preparations, inter eNB X2
Execution %
based for QCI1
LTE_5886a / IntraFreq HO SR QCI1 #
E-UTRAN Intra-Frequency HO attempts for LTE_5877a / HO preps inter eNB X2 QCI1
QCI1 E-UTRAN HO Success Ratio, inter eNB X2
#
based for QCI1 %
LTE_1515a / IntraFreq HO att QCI1 Execution
LTE_5880a / HO SR inter eNB X2 QCI1
E-UTRAN HO Attempts, inter eNB X2 based
GROUP: VoLTE handover, inter-frequency for QCI1 #
E-UTRAN Inter-Frequency HO Success Ratio LTE_5881a / HO att inter eNB X2 QCI1
Execution for QCI1 % E-UTRAN HO Preparation Success Ratio, inter
LTE_5884a / InterFreq HO SR QCI1 eNB S1 based for QCI1 %
E-UTRAN Inter-Frequency HO Attempts for Preparation
QCI1 LTE_5878a / HO prep SR inter eNB S1 QCI1
#
E-UTRAN HO Preparations, inter eNB S1 based
LTE_5885a / InterFreq HO att QCI1
for QCI1 #
E-UTRAN Inter-Frequency QCI1 HO Success LTE_5879a
Event A4 service-based Ratio for A3/A5 measurement-based handovers %
/ HO preps inter eNB S1 QCI1
E-UTRAN HO Success Ratio, inter eNB S1
handovers and event A4 load- LTE_5712a Execution / Inter Frequency QCI1 HO SR based for QCI1 %
based handovers are not E-UTRAN Inter-Frequency QCI1 HO Attempts LTE_5882a Execution / HO SR inter eNB S1 QCI1
for A3/A5 measurement-based handovers E-UTRAN HO Attempts, inter eNB S1 based for
counted #
QCI1
LTE_5711a / Inter Freq QCI1 HO Att #
LTE_5883a / HO att Inter eNB S1 QCI1

56 © Nokia 2016
Classification : Public

VoLTE KPI
Dedicated bearer (QCI1) mobility – KPI’s (SRVCC)
• KPI’s (& counters) are updated in the source cell of the handover!
• In FL16 there are no dedicated KPI’s / counters for SRVCC preparation phase, just counters for all IRAT mobility in
connected mode (covering all E-RAB’s). Such counters are introduced in FL16A with feature LTE2140: New
Performance Counters LTE16A

LTE2140 GROUP: Inter RAT HO with SRVCC

E-UTRAN Inter RAT HO UTRAN with SRVCC
Execution Success Ratio %
LTE_5564a / Inter RAT HO SR, UTRAN, SRVCC
E-UTRAN Inter RAT HO UTRAN with SRVCC
Failure Ratio %
Execution
LTE_5563a / Inter RAT HO FR, UTRAN, SRVCC
E-UTRAN Inter RAT HO Attempts to UTRAN
SRVCC #
LTE_5562a / Inter RAT HO Att, UTRAN, SRVCC
E-UTRAN Inter RAT HO GERAN with SRVCC
Success Ratio %
LTE_5567a Execution / Inter RAT HO SR, GERAN, SRVCC
E-UTRAN Inter RAT HO GERAN with SRVCC
Failure Ratio %
LTE_5566a Execution / Inter RAT HO FR, GERAN, SRVCC
E-UTRAN Inter RAT HO Attempts to GERAN
SRVCC #
LTE_5565a / Inter RAT HO Att, GERAN, SRVCC

57 © Nokia 2016
Classification : Public

VoLTE KPI
Dedicated bearer (QCI1) mobility – preparation phase
• Preparation phase means that source eNB which makes a positive HO decision (with known target cell) sends S1AP:
HANDOVER REQUEST or X2AP: HANDOVER REQUIRED message to the target eNB (or RNC/BSC in case of
SRVCC) passing necessary information to prepare the HO at the target side.
• Target side can perform admission control to make sure that resources can be granted by target access system.
• The target access system is responsible for giving exact guidance for the UE on how to make the radio access there
(this includes radio resource configuration, target cell system information etc.). This information is given during the
handover preparation and should be transported completely transparently through the source access system to the
UE.

58 © Nokia 2016
Classification : Public

VoLTE KPI
Dedicated bearer (QCI1) mobility – preparation phase
• Preparation phase is supervised from source eNB side by corresponding supervision timer:
- Supervision timer preparation intra LTE HO X2-based, LNBTS:tX2RelPrep = ​500 (Nokia FL16 hardcoded value)
- Supervision timer preparation intra LTE HO S1-based, LNBTS:tS1RelPrepL = ​500 (Nokia FL16 default value)
- Supervision timer for the preparation HO WCDMA, LNBTS:tS1RelPrepU = ​2000 (Nokia FL16 default value)
- Supervision​timer​for​handover​preparation​to​​G​S​M, LNBTS:tS1RelPrepG = ​1000 (Nokia FL16 default value)

• Timer is started in the source eNB when the S1AP: HANDOVER REQUIRED message is sent to the MME and is
stopped when the S1AP: HANDOVER COMMAND or S1AP: PREPARATION FAILURE message is received in
response. If the timer expires the handover is aborted or cancelled.

source target source

eNB eNB eNB MME

HANDOVER REQUEST HANDOVER REQUIRED

tX2RelPrep HANDOVER REQUEST ACKNOWLEDGE

tS1RelPrep
HANDOVER COMMAND

59 © Nokia 2016
Classification : Public

VoLTE KPI
Dedicated bearer (QCI1) mobility – partial HO
• Partial HO means that the HO for the admitted E-RABs was successfully completed, although not all E-RABs were
admitted by the HO target during HO preparation.
• For example, QCI8 & QCI5 E-RAB could be admitted duriong HO while QCI1 E-RAB is rejected (e.g. due to
admission control).
Counter ID Network Element Name NetAct Name Description Updated Unit
M8006C273 QCI1 E-RABs released ERAB_REL_HO_PART_QCI1 This measurement provides the number of Intra-eNB HO: Integer number
due to partial Handover QCI1 E-RABs released due to a partial HO. n.a.
The partial HO means that the HO for the
admitted E-RABs was successfully Inter-eNB HO via X2:
completed, although not all E-RABs were Following the reception of the X2AP:UE CONTEXT RELEASE message, the counter is incremented with the
admitted by the HO target during HO number of QCI1 bearers not admitted by the target eNB of the preceding HO preparation procedure. The bearers,
preparation. The counter is incremented with which are not admitted, are contained in the "E-RABs Not Admitted List" IE of the X2AP:HANDOVER REQUEST
the number of QCI1 E-RABs not admitted by ACKNOWLEDGE message that is received from the target eNB (3GPP TS 36.423).
the HO target. The counter is maintained in
the source cell. Inter-eNB HO via S1/Inter-system HO to UTRAN/SRVCC to UTRAN:
Following the reception of the S1AP:UE CONTEXT RELEASE COMMAND message with the cause "RNL
Successful Handover", the counter is incremented with the number of QCI1 bearers not admitted by the HO target
of the preceding HO preparation procedure. The bearers, which are not admitted, are contained in the "E-RABs to
Release List" IE of the S1AP:HANDOVER COMMAND message that is received from MME (3GPP TS 36.413).

• E-RAB QCI1 releases due to partial Handover [LTE_1445b], unit: %

- Percentage of QCI1 E-RABs released due to partial Handover
- Formula (NetAct names): 100*SUM (ERAB_REL_HO_PART_QCI1) / SUM(ERAB_REL_ENB_QCI1 +
ERAB_REL_HO_PART_QCI1 + EPC_EPS_BEAR_REL_REQ_N_QCI1 + EPC_EPS_BEAR_REL_REQ_D_QCI1 +
EPC_EPS_BEAR_REL_REQ_R_QCI1 + EPC_EPS_BEAR_REL_REQ_O_QCI1 + ERAB_REL_EPC_PATH_SWITCH_QCI1)

60 © Nokia 2016
Classification : Public

VoLTE KPI
Dedicated bearer (QCI1) mobility – preparation phase (X2 based HO)

source target
eNB eNB HANDOVER PREPARATION FAILURE
IE/Group Name Presence Range IE type and Semantics Criticality Assigned
reference description Criticality
Message Type M 9.2.13 YES reject
HANDOVER REQUEST Old eNB UE X2AP ID M eNB UE Allocated at YES ignore
X2AP ID the source
9.2.24 eNB
HANDOVER PREPARATION FAILURE Cause M 9.2.6 YES ignore
Criticality Diagnostics O 9.2.7 YES ignore

E-RAB List
IE/Group Name Presence Range IE type Semantic Criticalit Assigned
and s y Criticalit
reference descripti y
on
E-RAB List Item 1 .. EACH ignore
<maxnoofBe
arers>
>E-RAB ID M 9.2.23 – –
>Cause M 9.2.6 – –

Details on causes are in Appendix B

This scenario represents complete HO failure

61 © Nokia 2016
Classification : Public

VoLTE KPI
Dedicated bearer (QCI1) mobility – preparation phase (X2 based HO)
HANDOVER REQUEST ACKNOWLEDGE
IE/Group Name Presence Range IE type and Semantics description Criticality Assigned
source target reference Criticality
eNB eNB Message Type M 9.2.13 YES reject
Old eNB UE X2AP ID M eNB UE X2AP ID Allocated at the source YES ignore
9.2.24 eNB
HANDOVER REQUEST
New eNB UE X2AP ID M eNB UE X2AP ID Allocated at the target YES ignore
9.2.24 eNB

HANDOVER REQUEST ACKNOWLEDGE E-RABs Admitted List 1 YES ignore

> E-RABs Admitted Item 1 .. <maxnoof EACH ignore
Bearers>
>>E-RAB ID M 9.2.23 – –
>>UL GTP Tunnel Endpoint O GTP Tunnel Identifies the X2 – –
Endpoint 9.2.1 transport bearer used
for forwarding of UL
PDUs
E-RAB List
IE/Group Name Presence Range IE type Semantic Criticalit Assigned >>DL GTP Tunnel Endpoint O GTP Tunnel Identifies the X2 – –
and s y Criticalit Endpoint 9.2.1 transport bearer. used
reference descripti y for forwarding of DL
PDUs
on
E-RAB List Item 1 .. EACH ignore
<maxnoofBe E-RABs Not Admitted List O E-RAB List A value for E-RAB ID YES ignore
arers> 9.2.28 shall only be present
>E-RAB ID M 9.2.23 – – once in E-RABs
>Cause M 9.2.6 – – E-RAB Admitted List IE and in
E-RABs Not Admitted
(QCI1/5) List IE.

Details on causes are in Appendix B Target eNB To Source eNB M OCTET STRING Includes the RRC E- YES ignore
Transparent Container UTRA Handover
Command message as
defined in subclause
10.2.2 in TS 36.331 [9]
This scenario represents partial HO with QCI1 (or/and
QCI5) failure Criticality Diagnostics O 9.2.7 YES ignore

62 © Nokia 2016
Classification : Public

VoLTE KPI
Dedicated bearer (QCI1) mobility – preparation phase (S1 based HO)

source
eNB MME
HANDOVER PREPARATION FAILURE
IE/Group Name Presence Range IE type and Semantics Criticality Assigned
HANDOVER REQUIRED reference description Criticality
Message Type M 9.2.1.1 YES reject
MME UE S1AP ID M 9.2.3.3 YES ignore
HANDOVER PREPARATION FAILURE eNB UE S1AP ID M 9.2.3.4 YES ignore
Cause M 9.2.1.3 YES ignore
Criticality Diagnostics O 9.2.1.21 YES ignore

target In case of intra-LTE HO

eNB MME
Details on causes are in Appendix A
HANDOVER REQUEST

HANDOVER FAILURE

This scenario represents partial HO with QCI1 (or/and QCI5) failure

63 © Nokia 2016
Classification : Public

VoLTE KPI
Dedicated bearer (QCI1) mobility – preparation phase (S1 based HO)
source
HANDOVER COMMAND
eNB MME IE/Group Name Presence Range IE type and Semantics Criticality Assigned
reference description Criticality
Message Type M 9.2.1.1 YES reject
HANDOVER REQUIRED MME UE S1AP ID M 9.2.3.3 YES reject
eNB UE S1AP ID M 9.2.3.4 YES reject
Handover Type M 9.2.1.13 YES reject
HANDOVER COMMAND NAS Security Parameters from C- 9.2.3.30 The eNB shall use YES reject
E-UTRAN iftoUTRAN this IE as specified
GERAN in TS 33.401 [15].

E-RABs Subject to Forwarding 0..1 YES ignore

target In case of intra-LTE HO List
eNB MME >E-RABs Subject to 1 .. <maxnoofE- EACH ignore
Forwarding Item IEs RABs>
>>E-RAB ID M 9.2.1.2 -
HANDOVER REQUEST >>DL Transport Layer O 9.2.2.1 -
Address
>>DL GTP-TEID O 9.2.2.2 To deliver -
HANDOVER REQUEST ACKNOWLEDGE forwarded DL
PDCP SDUs.
>>UL Transport Layer O 9.2.2.1 -
Address
>>UL GTP-TEID O 9.2.2.2 To deliver -
forwarded UL
E-RAB List PDCP SDUs.
IE/Group Presence Range IE type and Semantics Critica Assigned E-RABs to Release List O E-RAB List YES ignore
Name reference description lity Criticality 9.2.1.36
E-RAB List 1 .. EACH ignore Target to Source Transparent M 9.2.1.57 YES reject
Item <maxnoofE Container
-RABs> Target to Source Transparent O Target to YES reject
Container Secondary Source
>E-RAB ID M 9.2.1.2 - -
Transparent
>Cause M 9.2.1.3 - - Container
9.2.1.57
Criticality Diagnostics O 9.2.1.21 YES ignore
Details on causes are in Appendix A
64 © Nokia 2016 This scenario represents complete HO failure
Classification : Public

VoLTE KPI
Dedicated bearer (QCI1) mobility – preparation phase: typical failure scenarios
HANDOVER REQUIRED
Unknown target cell IE/Group Name Presence Range IE type and reference Semantics Criticality Assigned
description Criticality
Message Type M 9.2.1.1 YES reject
• Usually could be recognized by HANDOVER MME UE S1AP ID M 9.2.3.3 YES reject
PREPARATION FAILURE with cause “Radio Network eNB UE S1AP ID M 9.2.3.4 YES reject
Handover Type M 9.2.1.13 YES reject
Layer: Unknown Target ID” Cause M 9.2.1.3 YES ignore
Target ID M 9.2.1.6 YES reject
• More relevant to IRAT mobility as intra-LTE mobility Direct Forwarding Path
Availability
O 9.2.3.15 YES ignore

usually relies on X2 eNB Configuration Update SRVCC HO Indication O 9.2.1.59 YES reject
Source to Target Transparent M 9.2.1.56 YES reject
procedure to keep the configuration data up-to-date in Container
the source eNB Source to Target Transparent O
Target
ContainerIDSecondary
Source to Target
Transparent Container
YES reject

IE/Group Name Presence Range IE type and9.2.1.56 Semantics description Criticality Assigned
• Check whether the target ID exist according to IE in MS Classmark 2 C-ifSRVCCtoGERAN reference 9.2.1.64 YES reject
Criticality
MS Classmark
Target3 ID MC-ifSRVCCtoGERAN 9.2.1.65 YES - ignore
HANDOVER REQUIRED and there is routing via CHOICE
CSG Id O 9.2.1.62 YES -
-
reject
>Target eNB-ID -
serving MME to the target radio access system Cell Access Mode
>>Global eNB ID M
O
9.2.1.37
9.2.1.74 YES
-
reject
-
PS Service Not Available O 9.2.1.77 YES ignore
(RNC/BSC) >>Selected TAI M TAI
9.2.3.16
- -

>Target RNC-ID - -
• Check the topology of network and geographical >>LAI M 9.2.3.1 - -
location of source and target whether such neighbor >>RAC O 9.2.3.2 - -
>>RNC-ID M INTEGER If the Extended RNC-ID IE is - -
relation makes sense (0..4095) included in the Target ID IE, the RNC-
ID IE shall be ignored.
• Make necessary corrections (Target ID correction, >>Extended RNC-ID O 9.2.1.14 The Extended RNC-ID IE shall be - -
used if the RNC identity has a value
deletion of neighbor relation) larger than 4095.
>CGI - -
>>PLMN Identity M 9.2.3.8 - -
>>LAC M OCTET 0000 and FFFE not allowed. - -
STRING
(SIZE(2))
>>CI M OCTET - -
65 © Nokia 2016 STRING
(SIZE(2))
Classification : Public

VoLTE KPI
Dedicated bearer (QCI1) mobility – preparation phase: typical failure scenarios
Incoming HO not supported by the target
• Some or all E-RAB’s might not be supported in the target
• In case of intra-LTE HO, check whether corresponding QCI’s are enabled with corresponding QoS attribute values (max bitrates) in the target cell –
details here (QCI5), here & here (QCI1) and support of conversational voice bearer is activated (LNBTS:actConvVoice=TRUE) Fully correlated with
VoLTE accessibility in the target cell
• In case of IRAT (SRVCC), check feature activation status:
- UTRAN → Insoming SRVCC is enabled via RAN2435: SRVCC from LTE and CSFB with HO (RNFC:SRVCCEnabled=ENABLED)
- GERAN → To perform MS handover from LTE to GSM for speech calls LTE can use SRVCC handover procedure. Inter-System Handover (ISHO) must be
enabled in BSC to support SRVCC handovers (SRVCC handovers are handled and signalled as inter-system handovers in BSC). Corresponding feature
BSS10101 and BSS11107:GSM-WCDMA Interworking

66 © Nokia 2016
Classification : Public

VoLTE KPI
Dedicated bearer (QCI1) mobility – preparation phase: typical failure scenarios
Congestion in target radio access system
• Ususally could be recognized by one of the following causes:
- “Radio Network Layer: No radio resources available in target cell”
- “Transport Layer - Transport Resource Unavailable”
• Occurrence of this scenario depends on several factors:
- Use and parameterization of Radio Admission Control / Transport Admission Control
- Radio / Transport load in the target
• Analyze this scenario per neighbor cell relationship to see which target cells are the most affected by congestion. As there are currently
no HO preparation counters per neighbor cell relationship, the analysis must be performed from interface traces
• In general, capacity management shall be in place and any eventual action shall be treated as part of it (capacity extensions, overload
handling etc.)

67 © Nokia 2016
Classification : Public

VoLTE KPI
Dedicated bearer (QCI1) mobility – preparation phase: typical failure scenarios
Supervision timer expiry
• Supervision timer (tX2RelPrep/tS1RelPrep) expiry due to either late or no response from EPC (and/or the target radio access system).
• There are dedicated causes for this scenario: S1AP “ TS1RELOCprep Expiry”, X2AP “TRELOCprep Expiry”
• More details about HO preparation supervision timer here
• S1/X2 traces shall be analyzed for this scenario.
• Check if timer settings are according to Nokia recommendations.
• Consider higher value of the timer to be used.
• Check the delays on the EPC and target RAN side whether they are in expected ranges.

68 © Nokia 2016
Classification : Public

VoLTE KPI
Dedicated bearer (QCI1) mobility – execution phase
• When HO preparation phase completed, eNB sends handover command (RRC Connection Reconfiguration /
MobilityFromEUTRACommand) to UE
• The UE receives the handover command with necessary parameters and is commanded by the source eNB to
perform the HO. UE performs HO to the target cell, i.e. UE detaches from source cell and synchronize to target cell.
• HO is acknowledged by UE with corresponding RRC message (RRC Connection Reconfiguration Complete,
Handover to UTRAN Complete, Handover Complete).

69 © Nokia 2016
Classification : Public

VoLTE KPI
Dedicated bearer (QCI1) mobility – execution phase
• HO execution phase could be analyzed per neighbor cell relationship to see if there are any specific neighbor
relations showing low HO success rate.
• Following counters could be used for such analysis:
Counter ID Network Element Name NetAct Name Description Updated Unit
M8017C11 Inter System Handover attempts to UTRAN ISYS_HO_UTRAN_SRVCC_ATT_N This measurement provides the number of Inter System Handover attempts Reception of an S1AP:HANDOVER COMMAND message (source eNB <- Integer number
with SRVCC per neighbor cell relationship B to UTRAN with SRVCC (Single Radio Voice Call Continuity, 3GPP TS MME; 3GPP TS 36.413) in case that this message is received in response to
23.216) per neighbor cell relationship. the preparation of an Inter System Handover to UTRAN with SRVCC (Single
Radio Voice Call Continuity, 3GPP TS 23.216).
M8017C12 Successful Inter System Handover ISYS_HO_UTRAN_SRVCC_SUCC_ This measurement provides the number of successful Inter System Reception of an S1AP:UE CONTEXT RELEASE COMMAND message Integer number
completions to UTRAN with SRVCC per NB Handover completions to UTRAN with SRVCC (Single Radio Voice Call (source eNB <- MME; 3GPP TS 36.413) with Cause value "Radio Network
neighbor cell relationship Continuity, 3GPP TS 23.216) per neighbor cell relationship. Layer (Successful Handover)" in case that this message is received for an
Inter System Handover to UTRAN with SRVCC (Single Radio Voice Call
Continuity, 3GPP TS 23.216).
M8017C13 Failed Inter System Handover attempts to ISYS_HO_UTRAN_SRVCC_FAIL_N This measurement provides the number of failed Inter System Handover Expiration of the guarding timer TS1RELOCoverall (3GPP TS 36.413) in Integer number
UTRAN with SRVCC per neighbor cell B attempts to UTRAN with SRVCC (Single Radio Voice Call Continuity, case that this timer was started because of an Inter System Handover to
relationship 3GPP TS 23.216) per neighbor cell relationship. UTRAN with SRVCC (Single Radio Voice Call Continuity, 3GPP TS
23.216).
M8019C3 Inter System Handover attempts to GERAN ISYS_HO_GERAN_SRVCC_ATT_N This measurement provides the number of Inter System Handover attempts Reception of an S1AP:HANDOVER COMMAND message (source eNB <- Integer number
with SRVCC per neighbor cell relationship B to GERAN with SRVCC (Single Radio Voice Call Continuity, 3GPP TS MME; 3GPP TS 36.413) in case this message is received in response to the
23.216) per neighbor cell relationship. preparation of an Inter System Handover to GERAN with SRVCC (Single
Radio Voice Call Continuity, 3GPP TS 23.216).
M8019C4 Successful Inter System Handover ISYS_HO_GERAN_SRVCC_SUCC_ This measurement provides the number of successful Inter System Reception of an S1AP:UE CONTEXT RELEASE COMMAND message Integer number
completions to GERAN with SRVCC per NB Handover completions to GERAN with SRVCC (Single Radio Voice Call (source eNB <- MME; 3GPP TS 36.413) with Cause value "Radio Network
neighbor cell relationship Continuity, 3GPP TS 23.216) per neighbor cell relationship. Layer (Successful Handover)" in case this message is received for an Inter
System Handover to GERAN with SRVCC (Single Radio Voice Call
Continuity, 3GPP TS 23.216).
M8019C5 Failed Inter System Handover attempts to ISYS_HO_GERAN_SRVCC_FAIL_N This measurement provides the number of failed Inter System Handover Expiration of the guarding timer TS1RELOCoverall (3GPP TS 36.413) in Integer number
GERAN with SRVCC per neighbor cell B attempts to GERAN with SRVCC (Single Radio Voice Call Continuity, case this timer was started because of an Inter System Handover to GERAN
relationship 3GPP TS 23.216) per neighbor cell relationship. with SRVCC (Single Radio Voice Call Continuity, 3GPP TS 23.216).

70 © Nokia 2016
Classification : Public

VoLTE KPI
Dedicated bearer (QCI1) mobility – execution phase
There is a specific set of timers that guard HO execution phase in the eNB (from receiving HANDOVER COMMAND to receiving of
the UE CONTEXT RELEASE COMMAND)
• X2-based HO (3GPP TS36.423):
- Upon reception of the HANDOVER REQUEST ACKNOWLEDGE message the source eNB shall stop the timer T RELOCprep, start the timer
TX2RELOCoverall and terminate the Handover Preparation procedure. The source eNB is then defined to have a Prepared Handover for that X2 UE-
associated signalling.
- If the UE Context Release procedure is not initiated towards the source eNB from any prepared eNB before the expiry of the timer TX2 RELOCoverall,
the source eNB shall request the MME to release the UE context.
- If the UE returns to source eNB before the reception of the UE CONTEXT RELEASE message or the expiry of the timer TX2 RELOCoverall, the
source eNB shall stop the TX2RELOCoverall and continue to serve the UE.

• S1-based HO (3GPP TS36.413):

- Upon reception of the HANDOVER COMMAND message the source eNB shall stop the timer TS1 RELOCprep and start the timer TS1RELOCoverall.
- If the UE Context Release procedure is not initiated towards the eNB before the expiry of the timer TS1 RELOCOverall, the eNB shall request the MME
to release the UE context.
- If the UE returns to the eNB before the reception of the UE CONTEXT RELEASE COMMAND message or the expiry of the timer TS1 RELOCOverall,
the eNB shall stop the TS1RELOCOverall and continue to serve the UE.

71 © Nokia 2016
Classification : Public

VoLTE KPI
Dedicated bearer (QCI1) mobility – execution phase
Supervision timers are calculated in the following way:
• Intra-LTE HO X2-based: TX2RELOCoverall = t304IntraLte + t311 + t301 + tX2RelODelta
• Intra-LTE HO S1-based: TS1RELOCoverall = t304IntraLte + t311 + t301 + tS1RelOvDeltL
• HO to GSM: TS1RELOCoverall = t304InterRATGsm + t311 + t301 + tS1RelOvDeltG
• HO to WCDMA: TS1RELOCoverall = t304InterRAT + t311 + t301 + tS1RelOvDeltU

X2-based HO:
If TX2RELOCoverall expires, eNB sends HANDOVER CANCEL to target eNB.

S1-based HO:
If TS1RELOCoverall expires, eNB sends HANDOVER CANCEL to MME. MME shall reply with HANDOVER CANCEL
ACKNOWLEDGE.

72 © Nokia 2016
Classification : Public

VoLTE KPI
Dedicated bearer (QCI1) mobility – execution phase
Handover execution has its own supervision timer T304 which supervises the successful completion of a handover or cell change.

Timer Start Stop At expiry

T304 Reception of RRCConnectionReconfiguration Criterion for successful completion of handover In case of cell change order from E-UTRA or intra E-
message including the MobilityControl Info or within E-UTRA, handover to E-UTRA or cell change UTRA handover, initiate the RRC connection re-
reception of MobilityFromEUTRACommand order is met (the criterion is specified in the target establishment procedure; In case of handover to E-
message including CellChangeOrder RAT in case of inter-RAT) UTRA, perform the actions defined in the
specifications applicable for the source RAT.
If T304 expires, handover failure occurs (if air interface security is active)

In Nokia implementation the timer is handover type specific:

Abbreviated Name Full Name

t​3​0​4e​Nacc​Gsm ​Timer​​T​3​0​4​for​e​N​A​C​C​to​​G​S​M
t​3​0​4​Inter​R​A​T ​Timer​​T​3​0​4​for​inter​R​A​T (to WCDMA)
t​3​0​4​Inter​R​A​T​Gsm ​Timer​​T​3​0​4​for​inter​R​A​T​​G​S​M
t​3​0​4​Intra​Lte ​Timer​​T​3​0​4​intra​-​L​T​E

73 © Nokia 2016
Classification : Public

VoLTE KPI
Dedicated bearer (QCI1) mobility – execution phase
Handover failure can be a trigger for RRC connection re-
establishment procedure.
There are two main RRC connection re-establishment related timers,
T311 & T301
Timer Start Stop At expiry
T301 Transmission of Reception of Go to RRC_IDLE
RRCConnectionReesta RRCConnectionReestablishment or
bilshmentRequest RRCConnectionReestablishmentRej
ect message as well as when the
selected cell becomes unsuitable
T311 Upon initiating the Selection of a suitable E-UTRA cell Enter RRC_IDLE
RRC connection re- or a cell using another RAT.
establishment
procedure

Both parameters are operator configurable.

74 © Nokia 2016
Classification : Public

VoLTE KPI
Dedicated bearer (QCI1) mobility – execution phase: typical failure scenarios
Bad quality in the target cell
• Scenario 1: IRAT HO to 3G is triggered based on RSCP which is sufficient but EcNo is poor
• Scenario 2: Fast changing radio conditions of the target cell – HO preparation phase takes some time (in the range of
x100ms). During that time the radio conditions in the target cell might have deteriorated.
• Check logs for the actual quality of target cell during UE access. Check the geographical situation
• Optimization of neighbor relation, HO parameterization shall take place.
Example

RSCP=-105dBm
75 © Nokia 2016 EcNo=-18.5dB
Classification : Public

VoLTE KPI
Dedicated bearer (QCI1) mobility – execution phase: typical failure scenarios
HO prepared in a wrong cell 3G

• PCI (PSC, BCCH) confusion

• UE reports a neighbor physical layer identity (PSC,
BCCH) which is mapped to Target ID by source eNB. 2. HO preparation
LTE
• HO is prepared in the target cell NB 2
PSC 11
• UE is commanded to HO to the target cell
1. PSC11 defined as
• UE makes attempt to access target cell. However, the real neighbor (NB2)
target cell where UE makes attempt is different from the Source eNB 2. UE measures and
reports B2 for PSC11
one in Target ID. The real cell is in this case ‘unprepared’, 3. HO command to 3G
i.e. not aware of any incoming HO. PSC11 of NB2

• Check neighbor plan and make necessary corrections 4. HO failure

NB 1
PSC 11
PSC – Primary Scrambling code

76 © Nokia 2016
Classification : Public

VoLTE KPI
Dedicated bearer (QCI1) mobility – execution phase: typical failure scenarios
UE failures
• UE vendor or chipset vendor specific
• No further details available at this stage

77 © Nokia 2016
Classification : Public

VoLTE KPI Reference - 3GPP TS36.300

Dedicated bearer (QCI1) mobility – completion phase

The handover completion phase for X2 initiated handovers comprises the following steps:
• The PATH SWITCH message is sent by the target eNB to the MME when the UE has successfully been transferred to the target cell.
The PATH SWITCH message includes the outcome of the resource allocation: successfully established E-RAB(s). If the eNB
supports SIPTO@LN with stand-alone gateway, the message shall include the LHN ID.
• The MME responds with the PATH SWITCH ACK message which is sent to the eNB.
• The MME responds with the PATH SWITCH FAILURE message in case a failure occurs in the EPC.

UE Target eNB MME

RRC: HANDOVER CONFIRM

S1-AP: PATH SWITCH
S1-AP: PATH SWITCH ACK

S1-AP: PATCH SWITCH FAlLURE

78 © Nokia 2016
Classification : Public

VoLTE KPI Reference - 3GPP TS36.300

Dedicated bearer (QCI1) mobility – completion phase

The Handover Completion for S1 initiated handovers comprises the following steps:
• The HANDOVER NOTIFY message is sent by the target eNB to the MME when the UE has successfully been transferred to the
target cell. If the eNB supports SIPTO@LN with stand-alone gateway, the message shall include the LHN ID.

UE Target eNB MME

RRC: HANDOVER CONFIRM

S1-AP: HANDOVER NOTIFY

79 © Nokia 2016
Classification : Public

VoLTE KPI
Dedicated bearer (QCI1) mobility – completion phase
FL16 feature LTE439: SGW Relocation with PATH SWITCH ACKNOWLEDGE
X2 Connection introduces support of E-RAB IE/Group Name Presence Range IE type and
reference
Semantics
description
Criticality Assigned
Criticality

release at HO completion phase. Feature belongs Message Type

MME UE S1AP ID
M
M
9.2.1.1
9.2.3.3
YES
YES
reject
ignore
eNB UE S1AP ID M 9.2.3.4 YES ignore
to basic SW and does not require any explicit UE Aggregate Maximum Bit
Rate
O 9.2.1.20 YES ignore

activation E-RAB To Be Switched in

Uplink List
0..1 YES ignore

>E-RABs Switched in Uplink 1 .. <maxnoofE- EACH ignore

Item IEs RABs>
>>E-RAB ID M 9.2.1.2 -
>>Transport Layer Address M 9.2.2.1 -
Feature description attached: >>GTP-TEID M 9.2.2.2 -
E-RAB To Be Released List O E-RAB List A value for E-RAB YES ignore
9.2.1.36 ID shall only be
LTE439 present once in E-
RAB To Be
E-RAB Switched in Uplink
List IE and E-RAB
(QCI1) to Be Released List
IE.

Security Context M 9.2.1.26 One pair of {NCC, YES reject

NH} is provided.
UE Target eNB MME
Criticality Diagnostics O 9.2.1.21 YES ignore
MME UE S1AP ID 2 O 9.2.3.3 This IE indicates YES ignore
RRC: HANDOVER CONFIRM the MME UE S1AP
S1-AP: PATH SWITCH ID assigned by the
MME.
S1-AP: PATH SWITCH ACK
CSG Membership Status O 9.2.1.73 YES ignore
ProSe Authorized O 9.2.1.99 YES ignore

80 © Nokia 2016
Classification : Public

VoLTE KPI
Dedicated bearer (QCI1) mobility – completion phase
Feature LTE439: SGW Relocation with X2 Connection introduces two counters related to VoLTE mobility (completion
phase):
Counter ID Network Element Name NetAct Name Description Updated Unit
M8006C280 eNB initiated QCI1 E-RAB ERAB_REL_ENB_TNL_UN This measurement provides the number of QCI1
This counter is updated following the transmission Integer
releases due to a failed SP_QCI1 E-RABs released due to a failed Handover of an S1AP:UE CONTEXT RELEASE REQUEST number
Handover Completion Completion phase at the target cell. message sent by the eNB to the MME. The
phase at target cell counter is incremented with the number of QCI1
E-RABs released with the TNL cause "TNL
Unspecified" (3GPP TS 36.413).
M8006C278 EPC initiated QCI1 E-RAB ERAB_REL_EPC_PATH_S This measurement provides the number of QCI1 This counter is incremented with the number of Integer
releases due to Path WITCH_QCI1 E-RABs abnormally released in case that EPC QCI1 E-RABs contained in the "E-RAB To Be number
Switch has failed to perform the UP path switch for at Released List " of the S1AP: PATH SWITCH
least one, but not for all, of the E-RABs included ACKNOWLDEGE message, which is received
in the preceding S1AP: PATH SWITCH from the MME (3GPP TS 36.413).
REQUEST.

81 © Nokia 2016
Classification : Public

VoLTE KPI
Dedicated bearer (QCI1) mobility
• Since there are no details per HO failure cause available directly from counters, trace analysis might be inevitable. For that reason
trace collection need to be done: S1_MME, X2, UE logs
• Handover performance could be analyzed per neighbor relation using the following Nokia predefined reports in NPM:
- RSLTE031 “Neighbor HO analysis” – KPI’s are not QCI1 specific!
GROUP: Intra eNB neighbor HO
Intra eNB Neighbor Handover Preparation Success ratio
LTE_706a % Prep SR
/ Adj Intra eNB HO PREP SR
Intra eNB Neighbour Handover Success ratio
% SR
LTE_707a / Adj Intra eNB HO SR
Integer
M8015C1 INTRA_HO_ATT_NB Att
number
Intra eNB Neighbour HO failure ratio
% Cancel R
LTE_708a / Intra eNB NB HO fail ratio
GROUP: Inter eNB neighbor HO
Inter eNB Neighbor Handover Preparation Success ratio
% Prep SR
LTE_12b / Adj Inter eNB HO PREP SR
Inter eNB Neighbour Handover Success ratio
% SR
LTE_13a / Adj Inter eNB HO SR
Integer
INTER_HO_ATT_NB Att
M8015C8 number
Inter eNB Neighbour HO failure ratio
% FR
LTE_14a / Inter eNB NB HO fail ratio
GROUP: Late/Early HO ratio, per neighbor
Late Handover Ratio
# Late HO
LTE_1061a / Late HO R
Early Handover Type 1 Ratio
# Early HO, type 1
LTE_1062a / Early HO type 1 R
Early Handover Type 2 Ratio
82 © Nokia 2016 # Early HO, type 2
LTE_1063a / Early HO type 2 R
Classification : Public

VoLTE KPI
Dedicated bearer (QCI1) mobility
- RSLTE044 “HO analysis for UTRAN per neighbor”
GROUP: Int-Sys HO to UTRAN per neighbor
Preparation Inter System HO for UTRAN FR, per neighbour
% Prep FR
LTE_980a / Inter-System HO FR for UTRAN, neighbour
Integer
ISYS_HO_UTRAN_PREP_FAIL_TIM_NB Prep Fails, TIM
M8017C4 number
Integer
ISYS_HO_UTRAN_PREP_FAIL_AC_NB Prep Fails, AC
M8017C5 number
Integer
ISYS_HO_UTRAN_PREP_FAIL_OTH_NB Prep Fails, Other
M8017C6 number
Total Inter-System HO for UTRAN SR, per neighbour
% Total SR
LTE_981a / Total Inter-System HO SR for UTRAN, neighbour
Integer
ISYS_HO_UTRAN_PREP_NB Prep Att
M8017C10 number
Inter-System HO for UTRAN SR, per neighbour
% SR
LTE_982a / Inter-System HO SR for UTRAN, neighbour
Integer
ISYS_HO_UTRAN_ATT_NB Att
M8017C7 number
Inter-System HO for UTRAN FR, per neighbour
% FR
LTE_983a / Inter-System HO FR for UTRAN, neighbour
Integer
ISYS_HO_UTRAN_FAIL_NB Fails
M8017C9 number

GROUP: Int-Sys HO to UTRAN w/ SRVCC per neighbor

Int-Sys HO to UTRAN with SRVCC per neighbour cell relationship Success Ratio
% SR
LTE_1054a / Int-Sys HO UTRAN SRVCC SR
Integer
ISYS_HO_UTRAN_SRVCC_ATT_NB Att
M8017C11 number

83 © Nokia 2016 Int-Sys HO to UTRAN with SRVCC per neighbour cell relationship Failure Ratio
% FR
LTE_1055a / Int-Sys HO UTRAN SRVCC FR
Classification : Public

VoLTE KPI
Dedicated bearer (QCI1) mobility
- RSLTE045 “HO to GSM per neighbor”

GROUP: NACC to GSM per neighbor

Integer
M8019C0 NACC_TO_GSM_ATT_NB Att
number

GROUP: HO to GSM w/ SRVCC per neighbor

Int-Sys HO to GERAN with SRVCC per neighbour cell relationship Success Ratio
LTE_1057a % SR
/ Int-Sys HO GERAN SRVCC SR
Integer
M8019C3 ISYS_HO_GERAN_SRVCC_ATT_NB Att
number
Int-Sys HO to GERAN with SRVCC per neighbour cell relationship Failure Ratio
LTE_1058a % FR
/ Int-Sys HO GERAN SRVCC FR

84 © Nokia 2016
Classification : Public

Accessibility Appendix A
S1AP release causes
Retainability
Appendix B
Mobility (intra-LTE & inter-RAT) X2AP release causes

Quality / Integrity
Appendix C
VoLTE flow charts per
KPI category

85 © Nokia Solutions
2016 and Networks 2016 Confidential
Classification : Public

VoLTE KPI
Dedicated bearer (QCI1) quality/integrity
• Speech signal has to travel E2E which inflicts large variety of degradations to speech signals.
• These degradations include loudness loss, talker and listener echo, temporal gaps on speech signal, filtering,
amplitude clipping, variable delays, distortions, channel errors etc.
• Degradation also may happen due to bit errors on the air interface layer and also by silent gaps caused by, for
example, handovers
• In packet-switched networks variable delays and packet losses inflict other types of problems.
• AMR, WB-AMR and EVS codecs are supported for VoLTE. Duration of one speech frame-block is 20 ms for all
codecs.

86 © Nokia 2016
Classification : Public

VoLTE KPI
Dedicated bearer (QCI1) quality/integrity
• Handover performance can affect the overall quality of VoLTE call. Hence the previous section dealing with
mobility is also relevant to quality/integrity.
• VoLTE call quality/integrity could be affected by:
- Late or early handovers
- Handover failures in any phase
- High service interruption time (packet loss) during handovers
• Due to suboptimally performing mobility UE can experience bad radio link quality leading to high BLER.
• SRVCC can meet the 3GPP voice interruption performance target defined in 3GPP TS22.278:
“The user experience shall be as far as possible unaffected by the change of domain and RAT. The RAT change procedure executed to
enable service continuity for an established voice call shall target an interruption time not higher than 300 ms.”

SRVCC

87 © Nokia 2016
Classification : Public

VoLTE KPI
Dedicated bearer (QCI1) quality/integrity
• Poor retainability of radio link can have negative impact on the overall quality of VoLTE call. For example, too
frequent radio link failures leading to RRC connection re-establishments would degrade E2E speech quality.
• Basic principle of RRC Connection Reestablishment described here.
• It is recommended to use LTE1617: RLF Triggered Handover in connection with VoLTE
• The following KPI’s available in Nokia NPM could be used to identify cells with high amount of re-establishments
along with re-establishment SR. Please note, these KPI’s are not QCI1 specific!

GROUP: RRC Re-Estab

Total E-UTRAN RRC Connection Re-establishment failure Ratio
LTE_5145a % Conn FR
/ Total RRC Connection Re-estab FR
Total E-UTRAN RRC Connection Re-establishment rejection Ratio
LTE_5144a % Conn Rejct Ratio
/ Total RRC Conn Re-estab reject Ratio
Total E-UTRAN RRC Connection Re-establishment Success Ratio
LTE_5143a % Conn SR
/ Total RRC Conn Re-estab SR
Integer
M8008C4 RRC_CON_RE_ESTAB_ATT
number
Att
RRC Connection Re-establishment Attempts, HO fail
LTE_5141a # Fails, HO
/ RRC Re-estab Att, HO
RRC Connection Re-establishment Attempts, other fails
LTE_5142a # Fails, Other
/ RRC Re-estab Att, other

88 © Nokia 2016
Classification : Public

VoLTE KPI
Dedicated bearer (QCI1) quality/integrity
• Poor retainability of radio link could be furter optimized via LTE1569: QCI 1 specific RLF and re-establishment control:
- Introduces dedicated parameters for the radio link failure (RLF) and the radio resource control (RRC) connection re-establishment behavior for
UEs with an established QoS class identifier 1 (QCI1) data radio bearer → n310Qci1, t310Qci1.
- The t310Qci1 and n310Qci1 operator-configurable parameters are signaled together with the t301, t311, and n311 LNCEL parameters, which are
configured for the system information broadcast 2 (SIB2) to the UE during the QCI1 data bearer setup with the RRC connection reconfiguration
message
Con Usage Timer Start Stop At expiry
stant T310 Upon detecting physical Upon receiving N311 If security is not activated: go to
layer problems for the consecutive in-sync indications RRC_IDLE else: initiate the
N310 Maximum number of PCell i.e. upon receiving from lower layers for the PCell, connection re-establishment 1
consecutive "out-of-sync" N310 consecutive out-of- upon triggering the handover procedure 6 . 33
3
indications for the PCell received sync indications from procedure and upon initiating P TS
from lower layers lower layers the connection re-establishment P
3G
procedure

89 © Nokia 2016
Classification : Public

VoLTE KPI
Dedicated bearer (QCI1) quality/integrity
• High packet loss on air interface (Uu) is one of the typical factors affecting VoLTE E2E speech quality.
• Referig to link budget calculation, VoLTE coverage typically uplink limited. Hence the uplink usually suffers worse
quality in terms of packet loss compared to downlink.
• The following KPI’s available in Nokia NPM could be used to identify cells with high packet loss in UL/DL for
QCI1/QCI5:

GROUP: PDCP SDU Data Integrity for QCI1/QCI5

E-UTRAN PDCP SDU Loss Ratio in the DL, QCI1
LTE_5305b / E-UTRAN PDCP SDU DL QCI1 LR
% Loss Ratio, DL
E-UTRAN PDCP SDU Discard Ratio in DL, QCI1
LTE_5256b / PDCP SDU Discard Ratio in DL, QCI1
% Disc Ratio, DL
E-UTRAN PDCP SDU Loss Ratio in the UL, QCI1
LTE_5311b / E-UTRAN PDCP SDU UL QCI1 LR
% Loss Ratio, UL
LTE_5450a E-UTRAN PDCP SDU Loss Ratio in the DL, QCI5 % Loss Ratio, DL

LTE_5455a E-UTRAN PDCP SDU Loss Ratio in the UL, QCI5 % Loss Ratio, UL

90 © Nokia 2016
Classification : Public

VoLTE KPI
Dedicated bearer (QCI1) quality/integrity
• There are several possible ways to resolve quality issues in problematic cells. Nevertheless, it is essential
to get familiar with:
- geographical situation in the area surrounding these cells
- Network topology and coverage including other RAT’s (3G, 2G)
- estimate location of VoLTE users
- Network load → high GBR load can lead to quality deterioration, especially with relaxed admission control for GBR

• There are several Nokia features addressing potential issues with bad VoLTE quality resulting from UL
coverage limitation, such as the following ones available in FL16:
- LTE571: Controlled uplink packet segmentation
- LTE907: TTI Bundling
- LTE2098: VoLTE uplink coverage boosting

91 © Nokia 2016
Classification : Public

VoLTE KPI
Dedicated bearer (QCI1) quality/integrity
• In some cases mobility optimization can improve VoLTE speech quality. For instance, SRVCC might be
required at different thresolds compared to pure data connections. There are several enhancement
features available in FL16 covering VoLTE mobility:
- LTE1127: Service Based Mobility Trigger
- LTE2112: Dedicated Mobility Thresholds for SRVCC
- LTE64: Service-based Handover Thresholds
- LTE1942: Dedicated VoLTE Inter-frequency Target Frequency List

92 © Nokia 2016
Classification : Public

Appendix A
S1AP causes

93 06/03/2024 © Nokia 2016

Confidential
Classification : Public
The purpose of the Cause IE is to indicate the reason for a particular
S1AP causes (1/5) event for the S1AP protocol.
3GPP 36.413 – 9.2.1.3 Cause
IE/Group Name Presence Range IE Type and Reference Semantics
Description
CHOICE Cause Group M
>Radio Network Layer
>>Radio Network Layer M ENUMERATED
Cause (Unspecified,
TX2RELOCOverall Expiry,
Successful Handover,
Release due to E-UTRAN Generated Reason,
Handover Cancelled, Partial Handover, Handover Failure In Target EPC/eNB Or Target System,
Handover Target not allowed,
TS1RELOCoverall Expiry,
TS1RELOCprep Expiry,
Cell not available,
Unknown Target ID,
No Radio Resources Available in Target Cell, Unknown or already allocated MME UE S1AP ID,
Unknown or already allocated eNB UE S1AP ID,
Unknown or inconsistent pair of UE S1AP ID, Handover desirable for radio reasons,
Time critical handover,
Resource optimisation handover,
Reduce load in serving cell, User inactivity,
Radio Connection With UE Lost, Load Balancing TAU Required, CS Fallback Triggered,
UE Not Available For PS Service, Radio resources not available,
Failure in the Radio Interface Procedure,
Invalid QoS combination, Inter-RAT redirection,
Interaction with other procedure, Unknown E-RAB ID, Multiple E-RAB ID instances, Encryption and/or integrity protection
algorithms not supported, S1 intra system Handover triggered, S1 inter system Handover triggered, X2 Handover triggered
…,
Redirection towards 1xRTT,
Not supported QCI value,
invalid CSG Id)

94 © Nokia 2016
Classification : Public
The purpose of the Cause IE is to indicate the reason for a particular
S1AP causes (2/5) event for the S1AP protocol.
3GPP 36.413 – 9.2.1.3 Cause
IE/Group Name Presence Range IE Type and Reference Semantics
Description
CHOICE Cause Group M
>Transport Layer
>>Transport Layer Cause M ENUMERATED
(Transport Resource Unavailable,
Unspecified,
…)
>NAS
>>NAS Cause M ENUMERATED (Normal Release,
Authentication failure,
Detach,
Unspecified,
…,
CSG Subscription Expiry)
>Protocol
>>Protocol Cause M ENUMERATED
(Transfer Syntax Error,
Abstract Syntax Error (Reject),
Abstract Syntax Error (Ignore and Notify),
Message not Compatible with Receiver State,
Semantic Error,
Abstract Syntax Error (Falsely Constructed Message), Unspecified, …)
>Misc
>>Miscellaneous Cause M ENUMERATED
(Control Processing Overload, Not enough User Plane Processing Resources,
Hardware Failure,
O&M Intervention,
Unspecified, Unknown PLMN, …)

95 © Nokia 2016
Classification : Public
The meaning of the different cause values is described in the following table. In general, “not
S1AP causes (3/5) supported” cause values indicate that the related capability is missing. On the other hand, “not
available” cause values indicate that the related capability is present, but insufficient
3GPP 36.413 – 9.2.1.3 Cause resources were available to perform the requested action.

Radio Network Layer cause Meaning

Unspecified Sent for radio network layer cause when none of the specified cause values applies.
TX2RELOCOverall Expiry The timer guarding the handover that takes place over X2 has abnormally expired.
Successful Handover Successful handover.
Release due to E-UTRAN generated reason Release is initiated due to E-UTRAN generated reason.
Handover Cancelled The reason for the action is cancellation of Handover.
Partial Handover Provides a reason for the handover cancellation. The HANDOVER COMMAND message from MME contained E-RABs to Release List IE and
the source eNB estimated service continuity for the UE would be better by not proceeding with handover towards this particular target eNB.
Handover Failure In Target EPC/eNB Or Target System The handover failed due to a failure in target EPC/eNB or target system.
Handover Target not allowed Handover to the indicated target cell is not allowed for the UE in question.
TS1RELOCoverall Expiry The reason for the action is expiry of timer TS1 RELOCoverall.
TS1RELOCprep Expiry Handover Preparation procedure is cancelled when timer TS1 RELOCprep expires.
Cell not available The concerned cell is not available.
Unknown Target ID Handover rejected because the target ID is not known to the EPC.
No radio resources available in target cell Load on target cell is too high.
Unknown or already allocated MME UE S1AP ID The action failed because the MME UE S1AP ID is either unknown, or (for a first message received at the eNB) is known and already allocated
to an existing context.
Unknown or already allocated eNB UE S1AP ID The action failed because the eNB UE S1AP ID is either unknown, or (for a first message received at the MME) is known and already allocated
to an existing context.
Unknown or inconsistent pair of UE S1AP ID The action failed because both UE S1AP IDs are unknown, or are known but do not define a single UE context.
Handover Desirable for Radio Reasons The reason for requesting handover is radio related.
Time Critical Handover Handover is requested for time critical reason i.e., this cause value is reserved to represent all critical cases where the connection is likely to be
dropped if handover is not performed.
Resource Optimisation Handover The reason for requesting handover is to improve the load distribution with the neighbour cells.
Reduce Load in Serving Cell Load on serving cell needs to be reduced. When applied to handover preparation, it indicates the handover is triggered due to load balancing.
User Inactivity The action is requested due to user inactivity on all E-RABs, e.g., S1 is requested to be released in order to optimise the radio resources.
Radio Connection With UE Lost The action is requested due to losing the radio connection to the UE.

96 © Nokia 2016
Classification : Public
The meaning of the different cause values is described in the following table. In general, “not
S1AP causes (4/5) supported” cause values indicate that the related capability is missing. On the other hand, “not
available” cause values indicate that the related capability is present, but insufficient
3GPP 36.413 – 9.2.1.3 Cause resources were available to perform the requested action.

Radio Network Layer cause Meaning

Load Balancing TAU Required The action is requested for all load balancing and offload cases in the MME.
CS Fallback triggered The action is due to a CS fallback that has been triggered. When it is included in UE CONTEXT RELEASE REQUEST message, it indicates the
PS service suspension is not required in the EPC.
UE Not Available for PS Service The action is requested due to a CS fallback to GERAN that has been triggered.
When it is included in the UE CONTEXT RELEASE REQUEST message, it indicates that the PS service suspension is required in the EPC due
to the target GERAN cell or the UE has no DTM capability.
Radio resources not available No requested radio resources are available.
Invalid QoS combination The action was failed because of invalid QoS combination.
Inter-RAT Redirection The release is requested due to inter-RAT redirection. When it is included in UE CONTEXT RELEASE REQUEST message, it indicates the PS
service suspension is not required in the EPC.
Failure in the Radio Interface Procedure Radio interface procedure has failed.
Interaction with other procedure The action is due to an ongoing interaction with another procedure.
Unknown E-RAB ID The action failed because the E-RAB ID is unknown in the eNB.
Multiple E-RAB ID Instances The action failed because multiple instance of the same E-RAB had been provided to the eNB.
Encryption and/or integrity protection algorithms not The eNB is unable to support any of the encryption and/or integrity protection algorithms supported by the UE.
supported
S1 Intra system Handover triggered The action is due to a S1 intra system handover that has been triggered.
S1 Inter system Handover triggered The action is due to a S1 inter system handover that has been triggered.
X2 Handover triggered The action is due to an X2 handover that has been triggered.
Redirection towards 1xRTT The release of the UE-associated logical S1 connection is requested due to redirection towards a 1xRTT system e.g., CS fallback to 1xRTT, or
SRVCC to 1xRTT, when the PS service suspension is required in the EPC. During this procedure, the radio interface message might but need not
include redirection information.
Not supported QCI Value The E-RAB setup failed because the requested QCI is not supported.
Invalid CSG Id The CSG ID provided to the target eNB was found invalid.

97 © Nokia 2016
Classification : Public
The meaning of the different cause values is described in the following table. In general, “not
S1AP causes (5/5) supported” cause values indicate that the related capability is missing. On the other hand, “not
available” cause values indicate that the related capability is present, but insufficient
3GPP 36.413 – 9.2.1.3 Cause resources were available to perform the requested action.

Transport Layer cause Meaning

Transport Resource Unavailable The required transport resources are not available.
Unspecified Sent when none of the above cause values applies but still the cause is Transport Network Layer related.

NAS cause Meaning

Normal Release The release is normal.
Authentication Failure The action is due to authentication failure.
Detach The action is due to detach.
Unspecified Sent when none of the above cause values applies but still the cause is NAS related.
CSG Subscription Expiry The action is due to the UE becoming a non-member of the currently used CSG.

Protocol cause Meaning

Transfer Syntax Error The received message included a transfer syntax error.
Abstract Syntax Error (Reject) The received message included an abstract syntax error and the concerning criticality indicated “reject”.
Abstract Syntax Error (Ignore And Notify) The received message included an abstract syntax error and the concerning criticality indicated “ignore and notify”.
Message Not Compatible With Receiver State The received message was not compatible with the receiver state.
Semantic Error The received message included a semantic error.
Abstract Syntax Error (Falsely Constructed Message) The received message contained IEs or IE groups in wrong order or with too many occurrences.

Miscellaneous cause Meaning

Control Processing Overload Control processing overload.
Not Enough User Plane Processing Resources Available No enough resources are available related to user plane processing.
Hardware Failure Action related to hardware failure.
O&M Intervention The action is due to O&M intervention.
Unspecified Failure Sent when none of the above cause values applies and the cause is not related to any of the categories Radio Network Layer, Transport
Network Layer, NAS or Protocol.
Unknown PLMN The MME does not identify any PLMN provided by the eNB.

98 © Nokia 2016
Classification : Public

Appendix B
X2AP causes

99 06/03/2024 © Nokia 2016

Confidential
Classification : Public
The purpose of the cause information element is to indicate the reason
X2AP causes (1/5) for a particular event for the whole protocol.
3GPP 36.423 – 9.2.6 Cause
IE/Group Name Presence Range IE Type and Reference Semantics Description
CHOICE Cause Group M
>Radio Network Layer
>>Radio Network Layer Cause M ENUMERATED
(
Handover Desirable for Radio Reasons,
Time Critical Handover,
Resource Optimisation Handover,
Reduce Load in Serving Cell,
Partial Handover,
Unknown New eNB UE X2AP ID, Unknown Old eNB UE X2AP
ID, Unknown Pair of UE X2AP ID,
HO Target not Allowed,
TX2RELOCoverall Expiry,
TRELOCprep Expiry,
Cell not Available,
No Radio Resources Available in Target Cell,
Invalid MME Group ID,
Unknown MME Code, Encryption And/Or Integrity Protection
Algorithms Not Supported, ReportCharacteristicsEmpty,
NoReportPeriodicity, ExistingMeasurementID, Unknown eNB
Measurement ID, Measurement Temporarily not Available,
Unspecified,
...,
Load Balancing, Handover Optimisation, Value out of allowed
range, Multiple E-RAB ID instances, Switch Off Ongoing, Not
supported QCI value, Measurement not supported for the object
)

10 © Nokia 2016
0
Classification : Public
The purpose of the cause information element is to indicate the reason
X2AP causes (2/5) for a particular event for the whole protocol.
3GPP 36.423 – 9.2.6 Cause
IE/Group Name Presence Range IE Type and Reference Semantics Description
CHOICE Cause Group M
>Transport Layer
>>Transport Layer Cause M ENUMERATED
(Transport Resource Unavailable,
Unspecified,
...)
>Protocol
>>Protocol Cause M ENUMERATED
(Transfer Syntax Error,
Abstract Syntax Error (Reject),
Abstract Syntax Error (Ignore and Notify),
Message not Compatible with Receiver State,
Semantic Error,
Unspecified,
Abstract Syntax Error (Falsely Constructed Message),...)
>Misc
>>Miscellaneous Cause M ENUMERATED
(Control Processing Overload,
Hardware Failure,
O&M Intervention,
Not enough User Plane Processing Resources,
Unspecified,...)

10 © Nokia 2016
1
Classification : Public
The meaning of the different cause values is described in the following table. In general, "not
X2AP causes (3/5) supported" cause values indicate that the concerned capability is missing. On the other hand,
"not available" cause values indicate that the concerned capability is present, but insufficient
3GPP 36.423 – 9.2.6 Cause resources were available to perform the requested action.

Radio Network Layer cause Meaning

Cell not Available The concerned cell is not available.
Handover Desirable for Radio Reasons The reason for requesting handover is radio related.
Handover Target not Allowed Handover to the indicated target cell is not allowed for the UE in question
Invalid MME Group ID The target eNB doesn’t belong to the same pool area of the source eNB i.e. S1 handovers should be attempted instead.
No Radio Resources Available in Target Cell The target cell doesn’t have sufficient radio resources available.
Partial Handover Provides a reason for the handover cancellation. The target eNB did not admit all E-RABs included in the HANDOVER
REQUEST and the source eNB estimated service continuity for the UE would be better by not proceeding with handover towards
this particular target eNB.
Reduce Load in Serving Cell Load on serving cell needs to be reduced. When applied to handover preparation, it indicates the handover is triggered due to
load balancing.
Resource Optimisation Handover The reason for requesting handover is to improve the load distribution with the neighbour cells.
Time Critical Handover handover is requested for time critical reason i.e. this cause value is reserved to represent all critical cases where the connection
is likely to be dropped if handover is not performed.
TX2RELOCoverall Expiry The reason for the action is expiry of timer TX2 RELOCoverall.
TRELOCprep Expiry Handover Preparation procedure is cancelled when timer T RELOCprep expires.
Unknown MME Code The target eNB belongs to the same pool area of the source eNB and recognizes the MME Group ID. However, the MME Code is
unknown to the target eNB.
Unknown New eNB UE X2AP ID The action failed because the New eNB UE X2AP ID is unknown.
Unknown Old eNB UE X2AP ID The action failed because the Old eNB UE X2AP ID is unknown.
Unknown Pair of UE X2AP ID The action failed because the pair of UE X2 AP IDs is unknown.
Encryption And/Or Integrity Protection Algorithms Not The target eNB is unable to support any of the encryption and/or integrity protection algorithms supported by the UE.
Supported

10 © Nokia 2016
2
Classification : Public
The meaning of the different cause values is described in the following table. In general, "not
X2AP causes (4/5) supported" cause values indicate that the concerned capability is missing. On the other hand,
"not available" cause values indicate that the concerned capability is present, but insufficient
3GPP 36.423 – 9.2.6 Cause resources were available to perform the requested action.

Radio Network Layer cause Meaning

ReportCharacteristicsEmpty The action failed because there is no characteristic reported.
NoReportPeriodicity The action failed because the periodicity is not defined.
ExistingMeasurementID The action failed because measurement-ID is already used.
Unknown eNB Measurement ID The action failed because some eNB Measurement-ID is unknown.
Measurement Temporarily not Available The eNB can temporarily not provide the requested measurement object.
Load Balancing The reason for mobility settings change is load balancing.
Handover Optimisation The reason for mobility settings change is handover optimisation.
Value out of allowed range The action failed because the proposed Handover Trigger parameter change in the eNB 2 Proposed Mobility Parameters IE is too
low or too high.
Multiple E-RAB ID Instances The action failed because multiple instances of the same E-RAB had been provided to the eNB.
Switch Off Ongoing The reason for the action is an ongoing switch off i.e. the concerned cell will be switched off after offloading and not be
available. It aides the receiving eNB in taking subsequent actions, e.g. selecting the target cell for subsequent handovers.
Not supported QCI value The action failed because the requested QCI is not supported.
Unspecified Sent when none of the above cause values applies but still the cause is Radio Network Layer related.
Measurement not Supported For The Object At least one of the concerned cell(s) does not support the requested measurement.

Transport Network Layer cause Meaning

Transport resource unavailable The required transport resources are not available.
Unspecified Sent when none of the above cause values applies but still the cause is Transport Network Layer related

10 © Nokia 2016
3
Classification : Public
The meaning of the different cause values is described in the following table. In general, "not
X2AP causes (5/5) supported" cause values indicate that the concerned capability is missing. On the other hand,
"not available" cause values indicate that the concerned capability is present, but insufficient
3GPP 36.423 – 9.2.6 Cause resources were available to perform the requested action.

Protocol cause Meaning

Abstract Syntax Error (Reject) The received message included an abstract syntax error and the concerned criticality indicated "reject" (see sub clause 10.3 of
TS 36.413 [4]).
Abstract Syntax Error (Ignore and Notify) The received message included an abstract syntax error and the concerned criticality indicated "ignore and notify" (see sub
clause 10.3 of TS 36.413 [4]).
Abstract syntax error (falsely constructed message) The received message contained IEs or IE groups in wrong order or with too many occurrences (see sub clause 10.3 of TS
36.413 [4]).
Message not Compatible with Receiver State The received message was not compatible with the receiver state (see sub clause 10.4 of TS 36.413 [4]).
Semantic Error The received message included a semantic error (see sub clause 10.4 of TS 36.413 [4]).
Transfer Syntax Error The received message included a transfer syntax error (see sub clause 10.2 of TS 36.413 [4]).
Unspecified Sent when none of the above cause values applies but still the cause is Protocol related

Miscellaneous cause Meaning

Control Processing Overload eNB control processing overload
Hardware Failure eNB hardware failure
Not enough User Plane Processing Resources eNB has insufficient user plane processing resources available.
O&M Intervention Operation and Maintenance intervention related to eNB equipment
Unspecified Sent when none of the above cause values applies and the cause is not related to any of the categories Radio Network Layer,
Transport Network Layer or Protocol

10 © Nokia 2016
4
Classification : Public

Appendix C
VoLTE flow charts per KPI category

10 06/03/2024 © Nokia 2016

5
Confidential
Classification : Public

Flow charts
Introduction
• Flow charts on the following slides show just part of the overall process which is VoLTE specific.
• Refer to “Troubleshooting Guideline – General Aspects” document for overall troubleshooting procedure
and related flow charts

10 © Nokia 2016
6
Classification : Public

Flow charts VoLTE quality/integrity

troubleshooting
Quality/Integrity

Y N
Is UL
impaired?

Activate / optimize LTE571, Y N

LTE907, LTE2098 Low RRC
retainability?

Check if T310/N310 Y N
optimization can resolve issue
(see also LTE1569) Mobility related
quality issue?

Check if activation/optimization of the Ad Hoc troubleshooting

following features can resolve issue:
LTE1127, LTE2112, LTE64, LTE1942
Mobility troubleshooting section will
provide additional means of
investigation/resolution

10 © Nokia 2016 Proceed to the next step

7
Classification : Public

Flow charts VoLTE retainability

troubleshooting
Check: RL supervision
Y parameters, RLF stats and
Retainability Cause RNL Radio
Connection with features (LTE1617) – take
Analyze E-RAB release caues UE lost? necessary actions

N Check availability of radio and

EPC initiated Y
Cause transport, mainly via alarms –
releases?
Radio/Transport take necessary actions
Res.Unavailable?
Y
N

Y N
Abnormal? Y Check: RL supervision
(‘other’,’path Cause redirection? parameters, RLF stats and
switch) features (LTE1617) – take
Pass the symptoms to core necessary actions
network experts
N
N

N Problem resolved in
the previous steps?

Ad Hoc troubleshooting
Y

10 © Nokia 2016 Proceed to the next step

8
Classification : Public
VoLTE mobility troubleshooting
Flow charts
Mobility Y N
Failures in HO
preparation
phase?

Y cause “RNL:
Check whether the target ID
Unknown Target
exist and make necessary
ID”
corrections N Y
Failures in HO
N execution
phase?
Y cause RNL/TNL:
Check RNL/TNL congestion
No resources
state in the target → make
available
necessary actions to relief
congestion N
Ad Hoc troubleshooting

Check and eventually optimize Y cause

timer value TS1/X2RELOCp
(TS1/X2RELOCprep) rep Expiry
Analyze delays in HO prep
N

Ad Hoc troubleshooting Y Other cause(s)

10 © Nokia 2016 N Proceed to the next step

9
Classification : Public

Flow charts VoLTE accessibility

troubleshooting
Collect S1AP traces and make E-
RAB setup failure ‘cause’
Accessibility distribution

YE Is E-UTRAN E-RAB NO Is the cause : RNL: YE

S Setup Success Ratio, Radio resources not S
QCI5/QCI1 equal to ‘0’? available?

NO Check:
LNBTS:qciTab5(1)/ YE
RAC status and config
qciSupp=ENABL S
Cell load
E
Initiate eventual capacity
expansion
Is the cause : TNL: YE
NO
Transport Resource S
Unavailable?
Set to Ad Hoc troubleshooting
LNBTS:qciTab5(1)/qciSupp=
ENABLE NO
Check:
TAC status and config
transport load
Initiate eventual capacity
expansion of transport

11 © Nokia 2016 Proceed to the next step

0
Classification : Public

Thank You

11 06/03/2024 © Nokia 2016

1
Confidential
Classification : Public

11 06/03/2024 © Nokia 2016

2
Confidential
Classification : Public

Copyright and confidentiality

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

11 © Nokia 2016 Confidential

3