VoLTE KPI White Paper

Voice over LTE Key Performance Indicators
Public White Paper
Author Zoltán Nagy

Owner Zoltán Nagy
Organization MN / CC / Cloud IMS BL
Approver Jukka Luoma
Document ID
Document location
Change History
Version Status Date Author Owner Reviewed by Reviewed Approver Approval Description of changes
date date
0.1 Draft DD-MM-YYYY YourNameHere YourNameHere YourNameHere DD-MM-YYYY YourNameHere DD-MM-YYYY TypeYourCommentsHere
0.2 Draft DD-MM-YYYY YourNameHere YourNameHere YourNameHere DD-MM-YYYY YourNameHere DD-MM-YYYY TypeYourCommentsHere
1.0 Approved DD-MM-YYYY YourNameHere YourNameHere YourNameHere DD-MM-YYYY YourNameHere DD-MM-YYYY TypeYourCommentsHere
06-09-2016 – TypeDocIDHere - 1 / 36 © Nokia Solutions and Networks 2016

Public
This material, including documentation and any related computer programs, is protected
by copyright controlled by Nokia Solutions and Networks. All rights are reserved. Copying,
including reproducing, storing, adapting or translating, any or all of this material requires the
prior written consent of Nokia Solutions and Networks. This material also contains
confidential information, which may not be disclosed to others without the prior written
consent of Nokia Solutions and Networks.

Public
Contents
1 Abstract ....................................................................................................................... 5
2 Terms and abbreviations ............................................................................................ 5
3 Non-call related KPI-s ................................................................................................. 6
3.1 EPC attach success rate ............................................................................................ 6
3.2 IMS registration ........................................................................................................... 8
3.3 Application server registration .................................................................................... 9
3.4 SMS over IP ................................................................................................................ 10
3.4.1 Mobile originated SMS over IP ................................................................................... 10
3.4.2 Mobile terminated SMS over IP .................................................................................. 11
4 Call related KPI-s ........................................................................................................ 12
4.1 Call setup success rate ............................................................................................... 12
4.1.1 Mobile originated call setup success rate................................................................... 12
4.1.2 Mobile terminated call setup success rate ................................................................. 14
4.1.3 Counters ...................................................................................................................... 16
4.2 Call setup time ............................................................................................................ 19
4.2.1 Mobile originated call setup time ................................................................................ 19
4.2.2 Mobile terminated call setup time ............................................................................... 19
4.2.3 Counters ...................................................................................................................... 20
4.3 SRVCC success rate .................................................................................................. 21
4.3.1 SRVCC transfer to 2G, success rate .......................................................................... 21
4.3.2 SRVCC transfer to 3G, success rate .......................................................................... 22
4.3.3 eSRVCC handover success rate ................................................................................ 23
4.3.4 Counters ...................................................................................................................... 23
4.3.5 SRVCC duration ......................................................................................................... 26
4.4 Average session duration ........................................................................................... 26
4.4.1 Average mobile originated session duration .............................................................. 26
4.4.2 Average mobile terminated session duration ............................................................. 27
4.4.3 Counters ...................................................................................................................... 27
4.5 Call drop rate............................................................................................................... 28
5 User plane related KPI-s............................................................................................. 30
Public
5.1 Peak user plane connections...................................................................................... 30
5.2 Ethernet interface errors ............................................................................................. 31
5.3 Throughput .................................................................................................................. 31
5.4 Transcoding ................................................................................................................ 32
5.5 Counters ...................................................................................................................... 32
6 Subscription related KPI-s .......................................................................................... 35
6.1 Number of registered subscribers .............................................................................. 35

Public
1 Abstract
Voice over LTE (VoLTE) enabled networks employ generally different network elements and protocols as
legacy circuit switched networks. Therefore, network operators need to create new Key Performance
Indicators (KPI-s) to be able to supervise and troubleshoot their VoLTE networks effectively. This paper is
intended to help define the end-to-end VoLTE KPI-s and correlate them to individual network elements.
The counters used for the KPI-s are coming from Nokia proprietary network elements. It is assumed that
the reader has basic knowledge of the VoLTE network architecture and the communications procedures
used in 4G networks.
2 Terms and abbreviations

• LTE: Long Term Evolution, the name of the 4G mobile telecommunications standard
• VoLTE: Voice over LTE
• VoWiFi: Voice over WiFi
• KPI: Key Performance Indicator
• EPC: Evolved Packet Core (see 3GPP TS 23.002)
• IMS: IP Multimedia Subsystem (see 3GPP TS 23.228)
• UE: User Equipment (e.g. mobile phone)
• eNodeB: The LTE base station (see 3GPP TS 36.300)
• MME: Mobility Management Entity (see 3GPP TS 23.002)
• SGW: Serving Gateway (see 3GPP TS 23.002)
• PGW: Packet Data Network Gateway (see 3GPP TS 23.002)
• PCRF: Policy and Charging Rules Function (see 3GPP TS 23.203)
• HSS: Home Subscriber Server (see 3GPP TS 23.228)
• NAS: Non Access Stratum (see 3GPP TS 24.301)
• S1: A signalling protocol used between the eNodeB and MME and between the eNodeB
and the SGW (see 3GPP TS 36.413)
• SRB1: One of the types of signalling radio bearers used in LTE radio networks (see
3GPP TS 36.331)
• EPS: Evolved Packet System (see 3GPP TS 23.002)
• SIP: Session Initiation Protocol (see 3GPP TS 24.228)
• P-CSCF: Proxy Call State Control Function (see 3GPP TS 23.228)
• I-CSCF: Interrogating Call State Control Function (see 3GPP TS 23.228)
• S-CSCF: Serving Call State Control Function (see 3GPP TS 23.228)
• TAS: Telecom Application Server, the AS that provides MMTel and other voice services in
the IMS

Public
3 Non-call related KPI-s
3.1 EPC attach success rate
The EPC attach procedure is the first step when a 4G capable device is trying to connect to the
network. The authentication, authorization and the default bearer reservation happen in this
stage. The success ratio of the EPC attach is essential for network monitoring. Figure 1 shows
the involved network elements and the relevant counters.
Figure 1
eNodeB counters
• SRB1_SETUP_ATT
The number of attempted signalling radio bearer (SRB1) establishments
• SRB1_SETUP_SUCC
The number of successful signalling radio bearer (SRB1) establishments
• INI_CONT_STP_REQ
The number of initial context setup requests
• INI_CONT_STP_COMP
The number of successful initial context setup requests
• S1_SETUP_ATT
The number of attempted S1 connections between the eNodeB and the MME
Public
• S1_SETUP_SUCC
The number of successful S1 connections between the eNodeB and the MME
MME counters
• EPS_ATTACH_SUCC
The number of successful EPS attach procedures
• EPS_ATTACH_FAIL
The number of failed EPS attach procedures
Figure 2 shows the bearer activation related counters collected from the MME.
Figure 2
• EPS_PDN_ACT_FOR_VOLTE_SUCC
The number of successful PDN activations
• EPS_PDN_ACT_FOR_VOLTE_FAIL
The number of failed PDN activations
• EPS_DEF_BEARER_ACT_VOLTE_SUCC
The number of successful default bearer activations
• EPS_DEF_BEARER_ACT_VOLTE_FAIL
The number of failed default bearer activations

Public
3.2 IMS registration
While the EPC attach procedure is necessary for the initial 4G data connection, the IMS
registration is required on top of it in order to use the VoLTE services. This registration happens
over the standard SIP protocol and all of the involved counters are collected from the S-CSCF.
The initial registrations and the periodic re-registrations are collected to separate counters. Also
there is a group of counters dedicated to the registrations that happen over LTE access (derived
from the P-Access-Network-Info SIP headers). These counters can be used for example to
separate the VoLTE and VoWiFi related registration KPI-s.
Figure 3
• initRegSuccSumCtr
The number of successful initial registrations
• initRegFailSumCtr
The number of failed initial registrations
• ReRegSuccSumCtr
The number of successful re-registrations
• ReRegFailSumCtr
The number of failed re-registrations
• AttInitRegAT
The number of attempted initial registrations over LTE access
• SuccInitRegAT
The number of successful initial registrations over LTE access

Public
• AttReRegAT
The number of attempted re-registrations over LTE access
• SuccReRegAT
The number of successful re-registrations over LTE access
3.3 Application server registration
Usually a SIP application server is needed to provide roles like the MMTel and SCC-AS. In the
Nokia portfolio, these roles are taken by the Open TAS and the IMS can be configured to do the
third party registration to the TAS. This network traffic can be monitored with the below counters
provided by the TAS.
Figure 4
TAS counters
• INITIAL_REG_ATT
The number of attempted initial registrations
• INITIAL_REG_SUCC
The number of successful initial registrations
• REREG_ATT
The number of attempted re-registrations

Public
• REREG_SUCC
The number of successful re-registrations
S-CSCF counters
• ISCInitialRegSentCtr
The number of sent initial registration requests over the ISC interface
• ISCReRegSentCtr
The number of sent re-registration requests over the ISC interface
• ISCDeRegSentCtr
The number of sent de-registration requests over the ISC interface
• ISC200RespRecRegCtr
The number of received 200 OK responses to REGISTER requests over the ISC interface
3.4 SMS over IP
SMS over IP is the basic SMS service over LTE. The SIP MESSAGE requests are used to
transfer the text message data to the IMS and towards the recipient.
3.4.1 Mobile originated SMS over IP
The mobile originated SMS scenario is when the UE sends the SIP MESSAGE request to the
IMS and the SMSC accepts and stores the text message.

Public
Figure 5
S-CSCF counters
• SipMessageRecCntr
The number of received SIP MESSAGE requests
• SipMSG2xxSentCntr
The number of sent positive responses to SIP MESSAGE requests (e.g. 200 OK or 202
Accepted)
TAS counters
• SMSC_SUCC_VTAS_MO_LOGICAL
The number of successful SMS transfers to the SMSC
• SMSC_UNSUCC_VTAS_MO_LOGICAL
The number of failed SMS transfers to the SMSC
3.4.2 Mobile terminated SMS over IP

The mobile terminated SMS scenario is when the SMSC is trying to deliver the text message
towards the recipient. This request is converted to a SIP MESSAGE request which is sent to the
intended UE through the IMS.
Figure 6

Public
S-CSCF counters
• SipMessageRecCntr
The number of received SIP MESSAGE requests
• SipMSG2xxSentCntr
The number of sent positive responses to SIP MESSAGE requests (e.g. 200 OK or 202
Accepted)
TAS counters
• SMSC_SUCC_VTAS_MT_PHYS
The number of successfully delivered terminating message requests
• SMSC_PERM_FAIL_VTAS_MT_PHYS
The number of permanently failed message deliveries
4 Call related KPI-s

4.1 Call setup success rate
The successful call setup on LTE consists of the following basic steps:
- SIP call setup initiation over the default bearer towards the IMS
- Dedicated bearer activation in the EPC
- Call rings and then it’s answered by the called party
The mobile originated and mobile terminated success rate KPI-s detailed below reflect these
steps.
4.1.1 Mobile originated call setup success rate

Public
Figure 7
Figure 8

Public
Figure 9
4.1.2 Mobile terminated call setup success rate

Public
Figure 10
Figure 11

Public
Figure 12
4.1.3 Counters
TAS counters
• TCAT_CALL_AMOUNT
Number of call attempts. The field is updated when the TAS successfully started the call setup.
• TCAT_RING_AMOUNT
Number of calls that reached the ringing phase. Used only if Ring counter in traffic
measurements feature is in use. When the TAS receives the first provisional response, statistics
saves that the call has reached the ringing phase.
• TCAT_OK_AMOUNT
Number of answered calls. The field is updated when the TAS receives the 200 OK response for
the initial INVITE request.
S-CSCF counters
• OrigInitAudioAT
Counts the total number of INVITE requests per access technology received on behalf of the
originating user for audio.
• OrigSuccAudioAT
originating user for audio for which either a 180 ringing or 200 OK response is received.

Public
• OrigAnsAudioAT
originating user for audio for which 200 OK response is received.
• TermInitAudioAT
terminating user for audio.
• TermSuccAudioAT
terminating user for audio for which either a 180 ringing or 200 OK response is received.
• TermAnsAudioAT
terminating user for audio for which 200 OK response is received.
S/P/SAE-GW counters
• SM_NBR_SEC_DEDIC_BEAR_ACT
This counter contains the duration of Flexi NG-initiated dedicated bearer creation. The
measurement is obtained in a P-GW or SAE-GW by accumulating the time intervals for every
successful dedicated bearer creation between the transmission of a "Create Bearer Request"
message and the corresponding "Create Bearer Response" message over a granularity period. If
the S-GW and P-GW are in different Flexi NG nodes, then the counter is increased only in the P-
GW node based on the Create Bearer Request/Response messages sent over the S5/S8
interface.
• SM_IMS_QCI1_DED_BEAR_ACT_S11
This counter contains the number of dedicated bearer create procedures initiated over the S11
interface when related APN is IMS and bearer has QCI 1. The counter is increased once for each
bearer in the Create Bearer Request message sent over the S11 as an S-GW or SAE-GW.
Counter is updated only if the related APN-NI of the PDN connection is IMS and bearer has QCI
1.
• SM_BEAR_ACT_NG_INIT_QC1
This counter contains the number of Flexi NG-initiated bearer create procedures where bearer
has QCI 1. The counter is increased once for each QCI 1 bearer in the Create Bearer Request
message sent as a P-GW or SAE-GW. If an S-GW and a P-GW are in the same Flexi NG node,
then the counter is increased based on Create Bearer Request sent over the S11/S4 interface. If
the S-GW and P-GW are in different Flexi NG nodes, then the counter is increased only in the P-
GW node based on Create Bearer Request sent over the S5/S8 interface.
• SM_SUC_IMSQC1_DED_BEAR_ACT_S11
This counter contains the number of successful dedicated bearer create procedures over the S11
interface when related APN is IMS and bearer has QCI 1. The counter is increased once for each
bearer in the Create Bearer Response message received over the S11 as an S-GW or SAE-GW
where the Cause IE value in the Bearer Context IE contains the value "Request accepted".

Public
Counter is updated only if the related APN-NI of the PDN connection is IMS and bearer has QCI
1.
• SM_SUCC_BEAR_ACT_NG_INIT_QC1
This counter contains the number of successful Flexi NG-initiated bearer create procedures,
where bearer has QCI 1. The counter is increased once for each QCI 1 bearer in the Create
Bearer Response message received as a P-GW or SAE-GW, where the Cause IE value in the
Bearer Context IE contains value "Request accepted". If an S-GW and a P-GW are in the same
Flexi NG node, then the counter is increased based on Create Bearer Response received over
the S11/S4 interface. If the S-GW and P-GW are in different Flexi NG nodes, then the counter is
increased only in the P-GW node based on the Create Bearer Response received over the S5/S8
interface.
eNodeB counters
• ERAB_INI_SETUP_ATT_QCI1
This measurement provides the number of setup attempts for initial E-RABs of QCI1. Updated at
the 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_ADD_SETUP_ATT_QCI1
This measurement provides the number of setup attempts for additional E-RABs of QCI1.
Updated at the 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_INI_SETUP_SUCC_QCI1
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.
• ERAB_ADD_SETUP_SUCC_QCI1
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.
MME counters
• EPS_DD_BEARER_VOLTE_ACT_SUCC
The number of successful dedicated bearer activation procedures for VoLTE service. Updated
when a PDN connectivity procedure is successfully completed and the MME detects that the
APN is "IMS" and the QCI of the subscription data for the APN is 1.
• EPS_DD_BEARER_VOLTE_ACT_FAIL
The number of failed dedicated bearer activation procedures for VoLTE service. Updated when a

Public
PDN connectivity procedure fails and the MME detects that the APN is "IMS" and the QCI of the
subscription data for the APN is 1.
4.2 Call setup time
The call setup time KPI shows how much time was needed on average for the successful call
setup until the ringing phase. This can depend on the location of the two parties and on the used
access technologies.
4.2.1 Mobile originated call setup time
Figure 13
4.2.2 Mobile terminated call setup time

Public
Figure 14
4.2.3 Counters
TAS counters
• CSTS_SUCC_SETUP_AVE
The longest successful setup time in the report period.
S-CSCF counters
• SipOrigSessSetupDur
Accumulated originating session setup duration (duration from receiving the initial INVITE as
originating S-CSCF till receiving 180 or 200).
• SipTermSessSetupDur
Accumulated terminating session setup duration (duration from receiving the initial INVITE as
terminating S-CSCF till receiving 180 or 200).
P-CSCF counters
• SipOrigSessSetupDur
Accumulated originating session setup duration (duration from receiving the initial INVITE as P-
CSCF till receiving 180 or 200).

Public
• SipTermSessSetupDur
Accumulated terminating session setup duration (duration from receiving the initial INVITE as P-
CSCF till receiving 180 or 200).
4.3 SRVCC success rate
The SRVCC procedure is triggered when a subscriber with an active call loses LTE coverage
and has to be transferred to 3G or 2G without losing the call. This is also called an inter-system
handover. A high SRVCC success rate is important for perceived VoLTE reliability. Also the
duration of the handover can affect the service continuity.
4.3.1 SRVCC transfer to 2G, success rate
Figure 15

Public
Figure 16
4.3.2 SRVCC transfer to 3G, success rate
Figure 17

Public
Figure 18
4.3.3 eSRVCC handover success rate
Figure 19
4.3.4 Counters

Public
TAS counters
• PS_TO_CS_SESS_TRANS_ATTEMPT
The amount of PS to CS session transfer attempts
• PS_TO_CS_SESS_TRANS_SUCCESS
The amount of successful PS to CS session transfers
• SESSION_TRANSFER_ATTEMP
The amount of session transfer attempts
• SESSION_TRANSFER_SUCCESS
The amount of successful session transfers
MME counters
• SRVCC_CS_HO_2G_SUCC
The number of successful SRVCC CS-only handover procedures to GERAN.
• SRVCC_CS_HO_2G_FAIL
The number of failed SRVCC CS-only handover procedures to GERAN.
• SRVCC_2G_CANCELLED
The number of cancelled SRVCC handover procedures to GERAN.
• SRVCC_EME_HO_2G_SUCC
The number of successful SRVCC emergency handover procedures to GERAN.
• SRVCC_EME_HO_2G_FAIL
The number of failed SRVCC emergency handover procedures to GERAN.
• SRVCC_EME_2G_CANCELLED
The number of cancelled SRVCC emergency handover procedures to GERAN.
• SRVCC_PS_AND_CS_HANDOVER_SUCC
Number of successful SRVCC CS and PS handovers to 3G.
• SRVCC_PS_AND_CS_HO_3G_FAIL
The number of failed SRVCC CS handover procedures to UTRAN, no matter whether PS
handover procedures succeed or fail.
• SRVCC_CS_HANDOVER_SUCC
Number of successful SRVCC CS only handovers to 3G.
• SRVCC_HO_3G_FAIL
The number of failed SRVCC handover procedures to UTRAN.
• SRVCC_3G_CANCELLED
The number of cancelled SRVCC handover procedures to UTRAN.
• SRVCC_EME_HO_3G_SUCC
The number of successful SRVCC emergency handover procedures to UTRAN.
• SRVCC_EME_HO_3G_FAIL
The number of failed SRVCC emergency handover procedures to UTRAN.
• SRVCC_EME_3G_CANCELLED
The number of cancelled SRVCC emergency handover procedures to UTRAN.

Public
eNodeB counters
• ISYS_HO_GERAN_SRVCC_SUCC_NB
This measurement provides the number of successful Inter System Handover completions to
GERAN with SRVCC per neighbor cell relationship. Updated at the reception of an S1AP:UE
CONTEXT RELEASE COMMAND message with Cause value "Radio Network Layer (Successful
Handover)" in case this message is received for an Inter System Handover to GERAN with
SRVCC.
• ISYS_HO_UTRAN_SRVCC_SUCC_NB
This measurement provides the number of successful Inter System Handover completions to
UTRAN with SRVCC per neighbor cell relationship. Updated at the reception of an S1AP:UE
CONTEXT RELEASE COMMAND message with Cause value "Radio Network Layer (Successful
Handover)" in case that this message is received for an Inter System Handover to UTRAN with
SRVCC.
MSS counters
• SRVCC_INTRA_MSS_GSM_SUCC
The number of successful SRVCC intra MSS handovers to GSM. Updated when the E-MSS
sends SRVCC PS to CS Complete Notification message on the Sv interface and the E-MSS
controls the target BSC.
• SRVCC_INTRA_MSS_GSM_FAIL
The number of unsuccessful SRVCC intra MSS handovers to GSM. Updated when the E-MSS
sends SRVCC PS to CS Response message with a rejected cause on the Sv interface (failure
occurs before E-MSS initiates Session Transfer) and the E-MSS controls the target BSC.
• SRVCC_INTER_MSS_GSM_SUCC
The number of successful SRVCC inter MSS handovers to GSM. Updated when the E-MSS
doesn’t control the target BSC.
• SRVCC_INTER_MSS_GSM_FAIL
The number of unsuccessful SRVCC inter MSS handovers to GSM. Updated when the E-MSS
occurs before E-MSS initiates Session Transfer) and the E-MSS doesn’t control the target BSC.
• SRVCC_INTRA_MSS_UMTS_SUCC
The number of successful SRVCC intra MSS handovers to UMTS. Updated when the E-MSS
controls the target RNC.
• SRVCC_INTRA_MSS_UMTS_FAIL
The number of unsuccessful SRVCC intra MSS handovers to UMTS. Updated when the E-MSS
occurs before E-MSS initiates Session Transfer) and the E-MSS controls the target RNC.

Public
• SRVCC_INTER_MSS_UMTS_SUCC
The number of successful SRVCC inter MSS handovers to UMTS. Updated when the E-MSS
doesn’t control the target RNC.
• SRVCC_INTER_MSS_UMTS_FAIL
The number of unsuccessful SRVCC inter MSS handovers to UMTS. Updated when the E-MSS
occurs before E-MSS initiates Session Transfer) and the E-MSS doesn’t control the target RNC.
ATCF counters
• AtcfDTInvCntr
Counts the accumulated total number of DT Attempts (INVITE due to STN-SR)
• AtcfDt2xxCntr
Counts the accumulated total number of DT Attempts accepted by ATCF with 2xx
4.3.5 SRVCC duration

The Open TAS provides the following counter:
• SESSION_TRANSFER_DURATION
Average duration of successful session transfers. The duration is calculated in milliseconds.
4.4 Average session duration
The session duration KPI is counting the average time between the call answer and the hang up.
It shows the utilization of the VoLTE network.
4.4.1 Average mobile originated session duration

Public
Figure 20
4.4.2 Average mobile terminated session duration
Figure 21
4.4.3 Counters

Public
eNodeB counters
• ERAB_IN_SESSION_TIME_QCI1
This measurement provides the aggregated in-session activity time in seconds for all E-RABs
with QCI1 characteristics. The E-RAB is said to be "in session" if any user data has been
transferred in UL or DL direction within the last 100msec. Updated when user data are
transferred the in-session activity time is aggregated during the E-RAB lifetime. At the end of the
measurement period and when E-RAB is released the sum counter for all E-RABs with QCI1
characteristics are be updated.
MME counters
• EPS_BEARER_DEDICATED_NBR_SUM
The sum of active dedicated bearers. This sum is used as a numerator when calculating the
average amount of active dedicated bearers.
• EPS_BEARER_DEDICATED_NBR_DEN
The number of samples taken of active dedicated bearers. This number is used as a
denominator when calculating the average amount of active dedicated bearers.
• DDBEARER_PGWINIT_ACT_SUCC
Number of all successful PGW initiated dedicated bearer activation.
• DDBEARER_UEINIT_ACT_SUCC
Number of all successful UE initiated dedicated bearer activation.
S-CSCF counters
• SipOrigSessDurCtr
Counts the accumulated duration of egress/outbound sessions (duration from receiving 200 Ok
till receiving BYE message).
• OrigAnsSesAt
Counts the number of successful session establishments for which 200 OK response was sent
by originating S-CSCF to the UE belonging to a given access technology. SipTermSessDurCtr:
Counts the accumulated duration of ingress/inbound sessions (duration from receiving 200 Ok till
receiving BYE message).
• TermAnsSesAt
Counts the number of successful session establishments for which 200 OK response was sent
by terminating S-CSCF to the UE belonging to a given access technology.
4.5 Call drop rate
A VoLTE call can be dropped because of the loss of radio bearer. This event can be measured
by the call drop rate KPI. The PCRF notifies the P-CSCF of the loss of radio bearer over the
standard Rx interface. The prerequisite of this KPI is that the Rx interface has to be activated.

Public
Figure 22
eNodeB counters
• ERAB_REL_ENB_QCI1
This measurement provides the total number of eNB-initiated releases of QCI1 E-RABs
regardless of the release cause. This counter is updated following the transmission of an
S1AP:E-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.
• ERAB_REL_HO_PART_QCI1
This measurement provides the number of QCI1 E-RABs released due to a partial HO. The
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. The counter is incremented
with the number of QCI1 E-RABs not admitted by the HO target.
• EPC_EPS_BEAR_REL_REQ_D_QCI1
The number of EPC-initiated EPS Bearer Release requests for QCI1 due to the Detach
procedure by the UE or the MME. Each bearer of the E-RAB to be Released List IE is counted.
Updated at the reception of an S1AP:E-RAB Release Command or an S1AP:UE Context
Release Command message sent by the MME to eNB.
• EPC_EPS_BEAR_REL_REQ_R_QCI1
The number of EPC-initiated EPS Bearer Release requests for QCI1 due to the Radio Network
Layer cause. Each bearer of the E-RAB to be Released List IE is counted. Updated at the
reception of an S1AP:E-RAB Release Command or an S1AP:UE Context Release Command
message sent by the MME to eNB.

Public
• EPC_EPS_BEAR_REL_REQ_O_QCI1
The number of EPC-initiated EPS Bearer Release requests for QCI1 due to other causes. Each
bearer of the E-RAB to be Released List IE is counted. Updated at the reception of an S1AP:E-
RAB Release Command or an S1AP:UE Context Release Command message sent by the MME
to eNB. The counter is updated if the release request detected does not match any other failure
counter.
P-CSCF counters
• VoLteNisrLOB
Counts network-initiated session releases triggered by Rx sessions because of loss of bearer for
VoLTE access.
• VoLteSessions
Counts successfully established sessions via LTE access.
5 User plane related KPI-s

5.1 Peak user plane connections
The peak user plane connections KPI measures the volume of the voice traffic and the peak
number of parallel calls.
Figure 23

Public
5.2 Ethernet interface errors
The quality of the voice calls depends on the number of Ethernet interface errors. If these KPI-s
increase, it means that the quality of voice calls are degrading.
Figure 24
5.3 Throughput
This KPI shows the volume of the voice data on the Ethernet interface level.

Public
Figure 25
5.4 Transcoding
The amount of transcoding also affects the voice quality. If there is a lot of codec transcoding,
then the subscribers will perceive that the voice quality is decreasing.
Figure 26
5.5 Counters
MME counters
• EPS_VOLTE_USER_MAX
The maximum number of sampled values measuring the number of users initiated VoLTE

Public
service. The current value and the previous maximum value of the measurement period are
compared every time a sample is taken.
S-CSCF/P-CSCF counters
• CurrInvDlgCntr
Counts the total number of currently active SIP INVITE dialogs (only sessions).
S/P/SAE-GW counters
• SM_NBR_ACT_BEARER_QCI1
This gauge contains the number of active QCI 1 bearers. Incremented when a QCI 1 bearer is
created. Decremented when a QCI 1 bearer is deleted.
• RECEIVED_ERRORS
The number of inbound packets that contain errors. Updated when an erroneous packet is
received on the networking interface.
• RECEIVED_PACKETS
The number of packets received. Updated when a packet is received on the networking interface.
• TRANSMIT_ERRORS
The number of outbound packets that are not transmitted because of errors. Updated when a
packet transmission fails on the networking interface.
• TRANSMIT_PACKETS
The number of packets transmitted out of the interface. Updated when a packet is transmitted on
the networking interface.
• TRANSMIT_DROPS
The number of outbound packets chosen to be dropped. Updated when a packet to be
transmitted by the networking interface is dropped.
• RECEIVED_OCTETS
The number of octets received. Updated when a packet is received on the networking interface.
• TRANSMIT_OCTETS
The number of octets transmitted out of the interface. Updated when a packet is transmitted on
TAS counters
• SIMUL_TAS_PEAK_SIM_CALL
The peak number of simultaneous calls in TAS.
BGW counters
• ALL_CAS_AVERAGE
The average value of simultaneously active contexts in one granularity period. Samples are

Public
taken every 20 seconds from the corresponding current counter and average value is calculated
at the end of each granularity period.
• RECEIVED_ERRORS
The number of inbound packets that contain errors. Updated when an erroneous packet is
received on the networking interface.
• RECEIVED_PACKETS
The number of packets received. Updated when a packet is received on the networking interface.
• TRANSMIT_ERRORS
The number of outbound packets that are not transmitted because of errors. Updated when a
packet transmission fails on the networking interface.
• TRANSMIT_PACKETS
The number of packets transmitted out of the interface. Updated when a packet is transmitted on
• RECEIVED_OCTETS
The number of octets received. Updated when a packet is received on the networking interface.
• TRANSMIT_OCTETS
The number of octets transmitted out of the interface. Updated when a packet is transmitted on
• TRANSCODING_USE
The number of audio and speech connections which transcoding has been used for. This counter
shows how many times transcoding has been used between two terminations for all connections.
Updated when user plane in both terminations have been established and transcoding services
have been reserved at least for one termination.
• TRANSCODING_AVERAGE
The average value of simultaneously active usage of transcoding service in one granularity
period. Samples are taken every 20 seconds from the corresponding current counter and
average value is calculated at the end of each granularity period.
• TRFO_USE
The number of TrFO operation use for all audio and speech connections. This counter shows
how many times the TrFO operation has been successfully used for all connections. Updated
when user plane in both terminations have been established and both-way topology connected
and there are TrFO services reserved for these two terminations.
• G711_USE
The number of audio and speech connections which G.711 service has been used for both
terminations. This counter shows how many times G.711 service has been used between two
terminations for all connections. Updated when user plane have been established and G.711
services have been reserved to both subscribers.

Public
6 Subscription related KPI-s
6.1 Number of registered subscribers
These KPI-s show how many subscribers are registered in the operator’s VoLTE network. The
amount of registered subscribers is not the same as the amount of activated subscribers (i.e. the
maximum amount of registered subscribers).
Figure 27
TAS counters
• TOTALAVERAGE
The average number of registered subscribers in the TAS.
One-NDS counters
• EXPHLRWX000002 – SubRegInHlr
Indicates how many mobile subscribers are registered in the HLR.
• EXPEPSWX000001 – SubWithEPS
Indicates the Number of EPS subscribers.

Public
MME counters
• EPS_VOLTE_USER_SUM
The sum of sampled values measuring the number of users, initiated VoLTE service. Updated
when a sample is taken.
• EPS_VOLTE_USER_DENOM
The number of samples taken for the users initiated VoLTE service and used as a denominator
to calculate the average. Updated when a sample is taken.
• EPS_VOLTE_USER_MAX
The maximum number of sampled values measuring the number of users initiated VoLTE
service.The current value and the previous maximum value of the measurement period are
compared every time a sample is taken.
P-CSCF/S-CSCF counters
• CurrFullyRegUsersCntr
Counts the total number of currently active fully registered users.
• IMSSAUCntr
Counts the total number of Simultaneously Active Users per every UTC hour.

Public

VoLTE KPI White Paper

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

VoLTE KPI White Paper

Uploaded by

Copyright:

Available Formats

Voice over LTE Key Performance Indicators

Public White Paper

Author Zoltán Nagy

06-09-2016 – TypeDocIDHere - 1 / 36 © Nokia Solutions and Networks 2016

06-09-2016 – TypeDocIDHere - 2 / 36 © Nokia Solutions and Networks 2016

06-09-2016 – TypeDocIDHere - 4 / 36 © Nokia Solutions and Networks 2016

2 Terms and abbreviations

06-09-2016 – TypeDocIDHere - 5 / 36 © Nokia Solutions and Networks 2016

06-09-2016 – TypeDocIDHere - 7 / 36 © Nokia Solutions and Networks 2016

06-09-2016 – TypeDocIDHere - 8 / 36 © Nokia Solutions and Networks 2016

3.3 Application server registration

06-09-2016 – TypeDocIDHere - 9 / 36 © Nokia Solutions and Networks 2016

3.4 SMS over IP

06-09-2016 – TypeDocIDHere - 10 / 36 © Nokia Solutions and Networks 2016

3.4.2 Mobile terminated SMS over IP

06-09-2016 – TypeDocIDHere - 11 / 36 © Nokia Solutions and Networks 2016

4 Call related KPI-s

06-09-2016 – TypeDocIDHere - 12 / 36 © Nokia Solutions and Networks 2016

06-09-2016 – TypeDocIDHere - 13 / 36 © Nokia Solutions and Networks 2016

4.1.2 Mobile terminated call setup success rate

06-09-2016 – TypeDocIDHere - 14 / 36 © Nokia Solutions and Networks 2016

06-09-2016 – TypeDocIDHere - 15 / 36 © Nokia Solutions and Networks 2016

06-09-2016 – TypeDocIDHere - 16 / 36 © Nokia Solutions and Networks 2016

06-09-2016 – TypeDocIDHere - 17 / 36 © Nokia Solutions and Networks 2016

06-09-2016 – TypeDocIDHere - 18 / 36 © Nokia Solutions and Networks 2016

4.2 Call setup time

4.2.2 Mobile terminated call setup time

06-09-2016 – TypeDocIDHere - 19 / 36 © Nokia Solutions and Networks 2016

06-09-2016 – TypeDocIDHere - 20 / 36 © Nokia Solutions and Networks 2016

4.3 SRVCC success rate

06-09-2016 – TypeDocIDHere - 21 / 36 © Nokia Solutions and Networks 2016

06-09-2016 – TypeDocIDHere - 22 / 36 © Nokia Solutions and Networks 2016

06-09-2016 – TypeDocIDHere - 23 / 36 © Nokia Solutions and Networks 2016

06-09-2016 – TypeDocIDHere - 24 / 36 © Nokia Solutions and Networks 2016

06-09-2016 – TypeDocIDHere - 25 / 36 © Nokia Solutions and Networks 2016

4.3.5 SRVCC duration

4.4 Average session duration

06-09-2016 – TypeDocIDHere - 26 / 36 © Nokia Solutions and Networks 2016

06-09-2016 – TypeDocIDHere - 27 / 36 © Nokia Solutions and Networks 2016

4.5 Call drop rate

06-09-2016 – TypeDocIDHere - 28 / 36 © Nokia Solutions and Networks 2016

06-09-2016 – TypeDocIDHere - 29 / 36 © Nokia Solutions and Networks 2016

5 User plane related KPI-s

06-09-2016 – TypeDocIDHere - 30 / 36 © Nokia Solutions and Networks 2016

06-09-2016 – TypeDocIDHere - 31 / 36 © Nokia Solutions and Networks 2016

06-09-2016 – TypeDocIDHere - 32 / 36 © Nokia Solutions and Networks 2016

06-09-2016 – TypeDocIDHere - 33 / 36 © Nokia Solutions and Networks 2016

06-09-2016 – TypeDocIDHere - 34 / 36 © Nokia Solutions and Networks 2016

06-09-2016 – TypeDocIDHere - 35 / 36 © Nokia Solutions and Networks 2016

06-09-2016 – TypeDocIDHere - 36 / 36 © Nokia Solutions and Networks 2016

You might also like