LTE Service KPI

eRAN KPI Reference
Contents
8.4.3 eRAN KPI Reference
8.4.3.2 Changes in eRAN KPI Reference
8.4.3.3 Accessibility KPIs
8.4.3.3.1 RRC Setup Success Rate
8.4.3.3.2 RRC Setup Success Rate (Service)
8.4.3.3.3 RRC Setup Success Rate (Signaling)
8.4.3.3.4 S1SIG Connection Setup Success Rate
8.4.3.3.5 E-RAB Setup Success Rate (VoIP)
8.4.3.3.6 E-RAB Setup Success Rate
8.4.3.3.7 Call Setup Success Rate
8.4.3.3.8 RRC Setup Success Rate (eMTC)
8.4.3.4 Retainability KPIs
8.4.3.4.1 Call Drop Rate (VoIP)
8.4.3.4.2 Service Drop Rate
8.4.3.4.3 Minutes Per Service Drop
8.4.3.4.4 Minutes Per Drop (VoIP)
8.4.3.4.5 Service Drop Rate (eMTC)
8.4.3.4.6 Service Drop Rate (NSA DC)
8.4.3.5 Mobility KPIs
8.4.3.5.1 Intra-Frequency Handover Out Success Rate
8.4.3.5.2 Intra-Frequency Handover Out Success Rate (VoIP)
8.4.3.5.3 Inter-Frequency Handover Out Success Rate
8.4.3.5.4 Inter-Frequency Handover Out Success Rate (VoIP)
8.4.3.5.5 Inter-FddTdd Handover Out Success Rate
8.4.3.5.6 Inter-FddTdd Handover Out Success Rate (VoIP)
8.4.3.5.7 Intra-RAT Handover In Success Rate
8.4.3.5.8 Inter-RAT Handover Out Success Rate (LTE to CDMA2000)
8.4.3.5.9 Inter-RAT Handover Out Success Rate (LTE to WCDMA)
8.4.3.5.10 Inter-RAT Handover Out Success Rate (LTE to GSM)
8.4.3.5.11 Inter-RAT Handover Out Success Rate (LTE to TD-SCDMA)
8.4.3.5.12 CSFB Preparation Success Rate
8.4.3.5.13 CSFB Success Rate Based Handover (LTE to WCDMA)
8.4.3.5.14 CSFB Success Rate Based Handover (LTE to GSM)
8.4.3.5.15 CSFB Success Rate Based Handover (LTE to TD-SCDMA)
8.4.3.5.16 SRVCC Success Rate (LTE to WCDMA)
8.4.3.5.17 SRVCC Success Rate (LTE to GSM)
8.4.3.5.18 SRVCC Success Rate (LTE to TD-SCDMA)
8.4.3.5.19 Intra-Frequency Handover Out Success Rate (eMTC)
8.4.3.5.20 Inter-Frequency Handover Out Success Rate (eMTC)
8.4.3.5.21 Intra-RAT Handover Out Success Rate (NSA DC)
8.4.3.6 Service Integrity KPIs
8.4.3.6.1 User Downlink Average Throughput
8.4.3.6.2 User Uplink Average Throughput
8.4.3.6.3 Service Downlink Average Throughput
8.4.3.6.4 Service Uplink Average Throughput
8.4.3.6.5 Cell Downlink Average Throughput
8.4.3.6.6 Cell Uplink Average Throughput
8.4.3.6.7 Downlink Packet Loss Rate
8.4.3.6.8 Downlink Packet Loss Rate (VoIP)
8.4.3.6.9 Uplink Packet Loss Rate
8.4.3.6.10 Uplink Packet Loss Rate (VoIP)
8.4.3.6.11 Downlink Residual Block Error Rate (eMTC)
8.4.3.6.12 Uplink Residual Block Error Rate (eMTC)
8.4.3.6.13 User Downlink Split Average Throughput (NSA DC)
8.4.3.6.14 User Uplink Split Average Throughput (NSA DC)
8.4.3.7 Utilization KPIs
8.4.3.7.1 Downlink Resource Block Utilizing Rate
8.4.3.7.2 Uplink Resource Block Utilizing Rate
8.4.3.7.3 Uplink Preschedule Resource Block Occupied Rate
8.4.3.7.4 Average CPU Load
8.4.3.7.5 Downlink Resource Block Utilizing Rate (NSA DC)
8.4.3.7.6 Uplink Resource Block Utilizing Rate (NSA DC)
8.4.3.8 Availability KPIs
8.4.3.8.1 Radio Network Availability Rate
8.4.3.9 Traffic KPIs
8.4.3.9.1 Radio Bearers
8.4.3.9.2 Downlink Traffic Volume
8.4.3.9.3 Uplink Traffic Volume
8.4.3.9.4 Average User Number
8.4.3.9.5 Maximum User Number
8.4.3.10 NB-IoT Accessibility KPIs
8.4.3.10.1 RRC Setup Success Rate (NB-IoT)
8.4.3.10.2 RRC Resume Success Rate (NB-IoT)
8.4.3.11 NB-IoT Retainability KPIs
8.4.3.11.1 Service Drop Rate (NB-IoT)
8.4.3.12 NB-IoT Service Integrity KPIs
8.4.3.12.1 Downlink SRB Packet Loss Rate (NB-IoT)
8.4.3.12.2 Downlink Residual Block Error Rate (NB-IoT)
8.4.3.12.3 Uplink Residual Block Error Rate (NB-IoT)
8.4.3.12.4 Downlink Packet Loss Rate (NB-IoT)
8.4.3.12.5 Uplink DRB Packet Loss Rate (NB-IoT)
8.4.3.13 NB-IoT Availability KPIs
8.4.3.13.1 Radio Network Availability Rate (NB-IoT)
8.4.3.14 NSA DC Accessibility KPIs
8.4.3.14.1 SgNB Addition Success Rate
8.4.3.15 References
8.4.3 eRAN KPI Reference

Purpose
This document describes basic key performance indicators (KPIs) in the eRAN. The
KPI calculation formulas are used in common scenarios. Associated counters provided
in this document are only key counters.
NOTE:
 The KPIs described in this document are for common scenarios, and the formulas are for
instruction only. For details about KPIs that are closely related to features, see the related
feature parameter description.
 Counters associated with the KPIs listed in this document are only key counters. For details
about other counters used on the live network, see 3900 & 5900 Series Base Station
Performance Counter Reference.
Intended Audience
This document is intended for:
 Network planners
 Network administrators
 Network operators
Product Version
The following table lists the product versions related to this document.
Product Name Solution Version Product Version
BTS3900  SRAN15.1 V100R015C10

 eRAN15.1
BTS5900
BTS3900A
BTS5900A
BTS3900L
BTS5900L
BTS3900AL
BTS5900AL
BTS3911E
DBS3900  SRAN15.1
 eRAN15.1
DBS5900
 eRAN TDD 15.1
DBS3900
LampSite
Product Name Solution Version Product Version
DBS5900
LampSite
Organization
eRAN KPI Reference Summary

Changes in eRAN KPI Reference
Accessibility KPIs
Accessibility KPIs are used to measure the probability that a user accesses the
network and requests services. Radio Resource Control (RRC) connection
setups and E-UTRAN radio access bearer (E-RAB) setups are the main
procedures whose performance is measured by accessibility KPIs.
Retainability KPIs
Retainability KPIs indicate the network's capability to retain services requested

by a user for a desired duration once the user is connected to the services.
Retainability KPIs are important in evaluating whether the system can maintain
a certain level of QoS.
Mobility KPIs
Mobility KPIs are used to evaluate E-UTRAN mobility performance, which is

critical to customer experience. Four categories of mobility KPIs are defined
based on the following handover types: intra-frequency, inter-frequency, inter-
duplex-mode, and inter-radio access technology (inter-RAT).
Service Integrity KPIs
The service integrity KPIs indicate service quality provided for UEs in an E-
UTRAN.
Utilization KPIs
Utilization KPIs are used to evaluate the capabilities, such as the capability to
meet traffic demands, in specific internal conditions.
Availability KPIs
A cell is available when the eNodeB can provide EPS bearer services.
Availability in a cell can be measured when a variety of hardware or software
faults occur in the cell.
Traffic KPIs
Traffic KPIs are used to measure the traffic volume on the LTE radio access
network (RAN). Based on traffic types, the traffic KPIs are classified into the
following categories: radio bearers, downlink traffic volume, and uplink traffic
volume.
NB-IoT Accessibility KPIs
NB-IoT accessibility KPIs represent the probability that UEs access an NB-IoT
network and are used to evaluate the UE access performance in the NB-IoT
network.
NB-IoT Retainability KPIs
Retainability KPIs indicate the network's capability to retain services requested
by a user for a desired duration once the user is connected to the services.
Retainability KPIs are important in evaluating whether the system can maintain
a certain level of QoS.
NB-IoT Service Integrity KPIs
The NB-IoT service integrity KPIs indicate service quality provided for UEs in
an NB-IoT network.
NB-IoT Availability KPIs
A cell is available when the eNodeB can provide EPS bearer services.
Availability in a cell can be measured when a variety of hardware or software
faults occur in the cell.
NSA DC Accessibility KPIs
NSA DC Accessibility KPIs are used to evaluate the SgNB addition success rate
in NSA DC scenarios.
References
Copyright © Huawei Technologies Co., Ltd.
8.4.3.2 Changes in eRAN KPI Reference

This chapter describes the changes in eRAN KPI Reference.
01 (2019-06-06)
This is the first commercial release.
Compared with Draft B (2019-05-10), this issue includes the following new
information:
 Service Drop Rate (NSA DC)
 Intra-RAT Handover Out Success Rate (NSA DC)
 User Downlink Split Average Throughput (NSA DC)
 User Uplink Split Average Throughput (NSA DC)
 Downlink Resource Block Utilizing Rate (NSA DC)
 Uplink Resource Block Utilizing Rate (NSA DC)
 NSA DC Accessibility KPIs
Compared with Draft B (2019-05-10), this issue does not include any new topics or
changes, or exclude any topics.
Draft B (2019-05-10)
This is a draft.
Compared with Draft A (2018-12-30), this issue does not include any new topics.
Compared with Draft A (2018-12-30), this issue includes the following changes.
Topic Change Description
Availability KPIs Changed the availability KPI from Radio

Network Unavailability Rate to Radio
Network Availability Rate.
NB-IoT Availability KPIs Changed the NB-IoT availability KPI
from Radio Network Unavailability Rate
(NB-IoT) to Radio Network Availability
Rate (NB-IoT).
Compared with Draft A (2018-12-30), this issue does not exclude any topics.
Draft A (2018-12-30)
This is a draft.
Compared with eRAN13.1 01 (2018-04-10), this issue deletes the CSFB Success Rate
Based Handover (LTE to CDMA2000) KPI.
Parent Topic: eRAN KPI Reference


< Previous topicNext topic >
8.4.3.3 Accessibility KPIs

Accessibility KPIs are used to measure the probability that a user accesses the network
and requests services. Radio Resource Control (RRC) connection setups and E-UTRAN
radio access bearer (E-RAB) setups are the main procedures whose performance is
measured by accessibility KPIs.
RRC Setup Success Rate
RRC Setup Success Rate (Service)
RRC Setup Success Rate (Signaling)
S1SIG Connection Setup Success Rate
E-RAB Setup Success Rate (VoIP)
E-RAB Setup Success Rate
Call Setup Success Rate
RRC Setup Success Rate (eMTC)



Description
According to 3GPP TS 36.331, the RRC connection setup procedure is triggered by
different causes. A UE sets the setup cause in accordance with the information it
receives from upper layers. An RRC connection setup procedure with a cause mo-
signaling is related to signaling. An RRC connection setup procedure with a cause other
than mo-signaling is related to service.
This KPI is calculated based on the counters measured at the eNodeB when the eNodeB
receives an RRC Connection Request message from the UE, as shown in Figure 1 The
number of RRC connection attempts is collected by the eNodeB at measurement point
A, and the number of successful RRC connections is counted at measurement point C.
Figure 1 Measurement points for RRC connection setup
Definition
The RRC Setup Success Rate KPI is defined in Table 1.
Table 1 RRC Setup Success Rate
Name RRC Setup Success Rate
Object Cell or radio network
Formula RRCS_SR = (RRCConnectionSuccess/RRCConnectionAttempt) x

100%
Associated RRC Setup Success Rate = (L.RRC.ConnReq.Succ/L.RRC.ConnReq.Att) x

Counters 100%
Unit Percentage (%)
Note None
Parent Topic: Accessibility KPIs


Next topic >

(Service)
Description
According to 3GPP TS 36.331, the RRC connection setup procedure is triggered by
different causes. A UE sets the setup cause in accordance with the information it
receives from upper layers. An RRC connection setup procedure with a cause mo-
signaling is related to signaling. An RRC connection setup procedure with a cause other
than mo-signaling is related to service. This KPI evaluates the RRC setup success rate
of service-related causes in a cell or on a radio network.
The KPI is calculated based on the counters measured at the eNodeB when the eNodeB
receives an RRC Connection Request message from the UE, as shown in Figure 1. The
number of RRC connection attempts (Service) is collected by the eNodeB at
measurement point A, and the number of successful RRC connections (Service) is
counted at measurement point C.
Definition
The RRC Setup Success Rate (Service) KPI is defined in Table 1.
Table 1 RRC Setup Success Rate (Service)
Name RRC Setup Success Rate (Service)

Formula RRCS_SRservice =
(RRCConnectionSuccessservice/RRCConnectionAttemptservice) ×
100%
Associated RRC Setup Success Rate (Service) = [(L.RRC.ConnReq.Succ.Emc +

Counters L.RRC.ConnReq.Succ.HighPri + L.RRC.ConnReq.Succ.Mt +
L.RRC.ConnReq.Succ.MoData + L.RRC.ConnReq.Succ.DelayTol +
L.RRC.ConnReq.Succ.MoVoiceCall)/(L.RRC.ConnReq.Att.Emc +
L.RRC.ConnReq.Att.HighPri + L.RRC.ConnReq.Att.Mt +
L.RRC.ConnReq.Att.MoData + L.RRC.ConnReq.Att.DelayTol +
L.RRC.ConnReq.Att.MoVoiceCall)] x 100%
Unit Percentage (%)
Note None



(Signaling)
Description
This KPI indicates the RRC setup success rate of the signaling-related cause (mo-
signaling) in a cell or on a radio network.
The KPI is calculated based on the counters measured at the eNodeB when the eNodeB
receives an RRC Connection Request message from the UE, as shown in Figure 1. The
number of RRC connection attempts (signaling) is collected by the eNodeB at
measurement point A, and the number of successful RRC connections (signaling) is
counted at measurement point C.
Definition
The RRC Setup Success Rate (Signaling) KPI is defined in Table 1.
Table 1 RRC Setup Success Rate (Signaling)
Name RRC Setup Success Rate (Signaling)
Formula RRCS_SRsignaling =
(RRCConnectionSuccesssignaling/RRCConnectionAttemptsignaling) ×
100%
Associated RRC Setup Success Rate (Signaling) =

Counters (L.RRC.ConnReq.Succ.MoSig/L.RRC.ConnReq.Att.MoSig) x 100%
Unit Percentage (%)
Note None


8.4.3.3.4 S1SIG Connection Setup

Success Rate
Description
This KPI indicates the success rate of signaling connection setups over the S1 interface.
The KPI includes counters such as the number of setup attempts of S1 signaling
connections related to UEs and the number of successful setups of S1 signaling
connections related to UEs.
The number of setup times of S1 signaling connections related to UEs is incremented by
1 each time when the eNodeB sends an INITIAL UE MESSAGE to the MME or
receives the first message from the MME. INITIAL UE MESSAGE is the first S1
message that the eNodeB sends to the MME. It contains the NAS configuration
information related to UEs, based on which the MME sets up S1 signaling connections
for UEs. The first S1 message sent by the MME may be INITIAL CONTEXT SETUP
REQUEST, DOWNLINK NAS TRANSPORT, or UE CONTEXT RELEASE
COMMAND. Receiving any of these messages indicates that the S1 signaling
connection is set up successfully.
As shown at point A in Figure 1, the L.S1Sig.ConnEst.Att counter is incremented by 1
when the eNodeB sends an INITIAL UE MESSAGE to the MME.
As shown at point B in Figure 1, the L.S1Sig.ConnEst.Succ counter is incremented by 1
when the eNodeB receives the first S1 message sent from an MME after sending an
INITIAL UE MESSAGE to the MME.
Figure 1 Measurement points for signaling connection setup
Definition
The S1SIG Connection Setup Success Rate KPI is defined in Table 1. Note that the
number of setup attempts of S1 signaling connections and the number of successful
setups of S1 signaling connections are collected based on the description in Description.
Table 1 S1SIG Connection Setup Success Rate
Name S1SIG Connection Setup Success Rate

Formula S1SIGS_SR =
(S1SIGConnectionEstablishSuccess/S1SIGConnectionEstablishAttempt)
× 100%
Associated S1SIG Connection Setup Success Rate =

Counters (L.S1Sig.ConnEst.Succ/L.S1Sig.ConnEst.Att) x 100%
Unit Percentage (%)
Note None



(VoIP)
Description
This KPI indicates the E-RAB setup success rate of the voice over IP (VoIP) services.
VoIP services can be identified based on the QCI information carried in the E-RAB
setup request message. Generally, the QCI is 1 for VoIP services.
Definition
The E-RAB Setup Success Rate (VoIP) KPI is defined in Table 1.
Table 1 E-RAB Setup Success Rate (VoIP)
Name E-RAB Setup Success Rate (VoIP)
Formula VoIPERABS_SR =
(VoIPERABSetupSuccess/VoIPERABSetupAttempt) x 100%
Associated E-RAB Setup Success Rate (VoIP) = [L.E-RAB.SuccEst.QCI.1/(L.E-

Counters RAB.AttEst.QCI.1 – L.E-RAB.FailEst.X2AP.VoIP)] x 100%
Unit Percentage (%)

Note None



Description
This KPI indicates the success rate of E-RABs for all services including VoIP.
Associated counters are E-RAB setup attempts and successful E-RAB setups.
Definition
The E-RAB Setup Success Rate KPI is defined in Table 1. For details about how to
measure the counters E-RAB setup attempts and successful E-RAB setups, see
Description.
Table 1 E-RAB Setup Success Rate
Name E-RAB Setup Success Rate
Formula ERABS_SR = (ERABSetupSuccess/ERABSetupAttempt) x 100%
Associated E-RAB Setup Success Rate = [L.E-RAB.SuccEst/(L.E-RAB.AttEst – L.E-

Counters RAB.FailEst.X2AP)] x 100%
Unit Percentage (%)
Note None


8.4.3.3.7 Call Setup Success Rate

Description
This KPI indicates the call setup success rate for all services. This KPI is calculated
based on the RRC Setup Success Rate (Service) KPI, the S1 Signaling Connection
Setup Success Rate KPI, and the E-RAB Setup Success Rate KPI.
Definition
The Call Setup Success Rate KPI is defined in Table 1. The KPI is calculated by
multiplying the RRC Setup Success Rate (Service) KPI, the S1 Signaling Connection
Setup Success Rate KPI, and the E-RAB Setup Success Rate KPI.
Table 1 Call Setup Success Rate
Name Call Setup Success Rate
Formula CSSR = (RRCConnectionSuccessservice/RRCConnectionAttemptservice) ×

(S1SIGConnectionEstablishSuccess/S1SIGConnectionEstablishAttempt)
× (ERABSetupSuccess/ERABSetupAttempt) × 100%
Associated Call Setup Success Rate = [(L.RRC.ConnReq.Succ.Emc +

Counters L.RRC.ConnReq.Succ.HighPri + L.RRC.ConnReq.Succ.Mt +
L.RRC.ConnReq.Succ.MoData + L.RRC.ConnReq.Succ.DelayTol
+L.RRC.ConnReq.Succ.MoVoiceCall)/(L.RRC.ConnReq.Att.Emc +
L.RRC.ConnReq.Att.HighPri + L.RRC.ConnReq.Att.Mt + L.RRC.ConnReq.Att.MoData
+ L.RRC.ConnReq.Att.DelayTol + L.RRC.ConnReq.Att.MoVoiceCall)] x
(L.S1Sig.ConnEst.Succ/L.S1Sig.ConnEst.Att) x [L.E-RAB.SuccEst/(L.E-RAB.AttEst -
L.E-RAB.FailEst.X2AP)] x 100%
Unit Percentage (%)
Note None



(eMTC)
Description
According to 3GPP specifications[8], the RRC connection setup procedure for an eMTC
UE can be triggered by different causes including mt-Access, mo-Signalling, mo-Data,
and mo-ExceptionData. A UE sets the setup cause in accordance with the information it
receives from upper layers. This KPI indicates the RRC connection setup success rate of
eMTC UEs in a cell. The KPI is measured by the eNodeB when eMTC UEs initiate
RRC connection setup procedures. As shown in Figure 1, the number of RRC connection
setup attempts is counted at point A when the eNodeB receives RRC Connection
Request messages from UEs. The number of successful RRC connection setups is
counted at point C.
Definition
The RRC Setup Success Rate (eMTC) KPI is defined in Table 1.
Table 1 RRC Setup Success Rate (eMTC)
Name RRC Setup Success Rate (eMTC)
Formula RRCS_SReMTC =
(RRCConnectionSuccess/RRCConnectionAttempt) x 100%
Associated RRC Setup Success Rate (eMTC) =

Counters (L.RRC.ConnReq.eMTC.Succ/L.RRC.ConnReq.eMTC.Att) x 100%
Unit Percentage (%)
Note None


< Previous topic
8.4.3.4 Retainability KPIs

Retainability KPIs indicate the network's capability to retain services requested by a
user for a desired duration once the user is connected to the services. Retainability KPIs
are important in evaluating whether the system can maintain a certain level of QoS.
Call Drop Rate (VoIP)
Service Drop Rate
Minutes Per Service Drop
Minutes Per Drop (VoIP)
Service Drop Rate (eMTC)
Service Drop Rate (NSA DC)


8.4.3.4.1 Call Drop Rate (VoIP)

Description
This KPI indicates the call drop rate for VoIP services, and can be calculated based on
the proportion of abnormally released E-RABs for VoIP services. Each E-RAB is
associated with QoS information. Usually, the QCI of VoIP services is 1.
Definition
The Call Drop Rate (VoIP) KPI is defined in Table 1.
Table 1 Call Drop Rate (VoIP)
Name Call Drop Rate (VoIP)
Formula VoIP_CDR = (VoIPERABAbnormalRelease/VoIPERABRelease) x

100%
Associated Call Drop Rate (VoIP) = [L.E-RAB.AbnormRel.QCI.1/(L.E-

Counters RAB.AbnormRel.QCI.1 + L.E-RAB.NormRel.QCI.1 + L.E-
RAB.NormRel.IRatHOOut.QCI.1)] x 100%
Unit Percentage (%)

Note None
Parent Topic: Retainability KPIs


Next topic >
8.4.3.4.2 Service Drop Rate

Description
This KPI indicates the service drop rate of all services (including VoIP). Similar to the
KPI defined in Call Drop Rate (VoIP), this KPI is calculated using the formula defined in
Table 1.
Definition
The Service Drop Rate KPI is defined in Table 1.
Table 1 Service Drop Rate
Name Service Drop Rate
Formula Service_CDR = (ERABAbnormalRelease/ERABRelease) x 100%
Associated Service Drop Rate (All) = [L.E-RAB.AbnormRel/(L.E-RAB.AbnormRel +

Counters L.E-RAB.NormRel + L.E-RAB.NormRel.IRatHOOut)] x 100%
Unit Percentage (%)
Note None


8.4.3.4.3 Minutes Per Service Drop

Description
This KPI indicates the proportion of the data transmission duration to the number of
times that services are dropped due to exceptions. This KPI reflects the average duration
that a service drop occurs and is used to evaluate service retainability.
Definition
The Minutes Per Service Drop KPI is defined in Table 1.
Table 1 Minutes Per Service Drop (All)
Name Minutes Per Service Drop
Formula Minutes Per Service Drop =

TimeOfTranmission/ERABAbnormalRelease
Associated Minutes Per Service Drop = (L.E-RAB.SessionTime.HighPrecision/L.E-

Counters RAB.AbnormRel) x 100/1000/60
Unit Minute
Note None


8.4.3.4.4 Minutes Per Drop (VoIP)

Description
This KPI indicates the proportion of the data transmission duration of VoIP services to
the number of times that VoIP services are dropped due to exceptions. This KPI reflects
the average duration that a VoIP service drop occurs and is used to evaluate voice
service retainability.
Definition
The Minutes Per Drop (VoIP) KPI is defined in Table 1.
Table 1 Minutes Per Drop (VoIP)

Name Minutes Per Drop (VoIP)
Formula Minutes Per Drop (VoIP) =

TimeOfTranmission/ERABAbnormalRelease
Associated Minutes Per Drop (VoIP) = (L.E-RAB.SessionTime.HighPrecision.QCI1/L.E-

Counters RAB.AbnormRel.QCI.1) x 100/1000/60
Unit Minute
Note None


8.4.3.4.5 Service Drop Rate (eMTC)

Description
This KPI indicates the service drop rate of all services for eMTC UEs. This KPI can be
evaluated based on the proportion of abnormal UE context releases. For details about its
calculation formula, see Table 1.
Definition
The Service Drop Rate (eMTC) KPI is defined in Table 1.
Table 1 Service Drop Rate (eMTC)
Name Service Drop Rate (eMTC)
Formula Service_CDR = (UECNTXAbnormalRelease/UECNTXRelease) x

100%
Associated Service Drop Rate (eMTC) =

Counters [L.UECNTX.eMTC.AbnormRel/(L.UECNTX.eMTC.NormRel +
L.UECNTX.eMTC.AbnormRel)] x 100%
Unit Percentage (%)

Note None


8.4.3.4.6 Service Drop Rate (NSA DC)

Description
This KPI indicates the service drop rate of non-standalone (NSA) dual connectivity
(DC) UEs. This KPI is calculated using the formula defined in Table 1.
Definition
The Service Drop Rate (NSA DC) KPI is defined in Table 1.
Table 1 Service Drop Rate (NSA DC)
Name Service Drop Rate (NSA DC)
Formula Service_CDR = (ERABAbnormalRelease/ERABRelease) x 100%
Associated Service Drop Rate (NSA DC) = L.NsaDc.E-RAB.AbnormRel/(L.NsaDc.E-

Counters RAB.AbnormRel + L.NsaDc.E-RAB.NormRel) x 100%
Unit Percentage (%)
Note None


< Previous topic
8.4.3.5 Mobility KPIs

Mobility KPIs are used to evaluate E-UTRAN mobility performance, which is critical to
customer experience. Four categories of mobility KPIs are defined based on the
following handover types: intra-frequency, inter-frequency, inter-duplex-mode, and
inter-radio access technology (inter-RAT).
Intra-Frequency Handover Out Success Rate
Intra-Frequency Handover Out Success Rate (VoIP)
Inter-Frequency Handover Out Success Rate
Inter-Frequency Handover Out Success Rate (VoIP)
Inter-FddTdd Handover Out Success Rate
Inter-FddTdd Handover Out Success Rate (VoIP)
Intra-RAT Handover In Success Rate
Inter-RAT Handover Out Success Rate (LTE to CDMA2000)
Inter-RAT Handover Out Success Rate (LTE to WCDMA)
Inter-RAT Handover Out Success Rate (LTE to GSM)
Inter-RAT Handover Out Success Rate (LTE to TD-SCDMA)
CSFB Preparation Success Rate
CSFB Success Rate Based Handover (LTE to WCDMA)
CSFB Success Rate Based Handover (LTE to GSM)
CSFB Success Rate Based Handover (LTE to TD-SCDMA)
SRVCC Success Rate (LTE to WCDMA)
SRVCC Success Rate (LTE to GSM)
SRVCC Success Rate (LTE to TD-SCDMA)
Intra-Frequency Handover Out Success Rate (eMTC)
Inter-Frequency Handover Out Success Rate (eMTC)
Intra-RAT Handover Out Success Rate (NSA DC)


8.4.3.5.1 Intra-Frequency Handover Out

Success Rate
Description
This KPI indicates the success rate of intra-frequency handovers (HOs) from the local
cell to neighboring E-UTRAN cells. The intra-frequency HOs are classified into intra-
and inter-eNodeB HOs.
Intra-eNodeB Outgoing HO
Intra-eNodeB outgoing HOs can be further classified into HO with RRC connection
reestablishment and HO without RRC connection reestablishment.
 Intra-eNodeB outgoing HO without RRC connection reestablishment
Figure 1illustrates an intra-eNodeB outgoing HO without RRC connection

reestablishment, and the source and target cells operate at the same frequency. When
the eNodeB sends an RRC Connection Reconfiguration message containing the
handover command to the UE, the eNodeB counts the number of intra-eNodeB intra-
frequency outgoing HO execution attempts in the source cell at point B. When the
eNodeB receives an RRC Connection Reconfiguration Complete message from the
UE, the eNodeB counts the number of successful intra-eNodeB intra-frequency
outgoing HO executions in the source cell at point C.
Figure 1 Intra-eNodeB outgoing HO without RRC connection reestablishment
 Intra-eNodeB outgoing HO with RRC connection reestablishment
Figure 2illustrates an intra-eNodeB outgoing HO with RRC connection

reestablishment, and the source and target cells operate at the same frequency. When
the eNodeB sends an RRC Connection Reconfiguration message containing the
handover command to the UE, the eNodeB counts the number of intra-eNodeB intra-
frequency outgoing HO execution attempts in the source cell at point B. When the
eNodeB receives an RRC Connection Reestablishment Complete message from the
UE, the eNodeB counts the number of successful intra-eNodeB intra-frequency
outgoing HO executions in the source cell at point C.
Figure 2 Intra-eNodeB outgoing HO with RRC connection reestablishment
Inter-eNodeB Outgoing HO
Inter-eNodeB outgoing HOs can be further classified into HO without RRC connection
reestablishment, HO with RRC connection reestablishment to the target cell, and HO
with RRC connection reestablishment to the source cell.
 Inter-eNodeB outgoing HO without RRC connection reestablishment
Figure 3and Figure 4 illustrate X2- and S1-based outgoing HOs with RRC connection
reestablishment to the source cell, respectively, and the source cell and target cell
operate on the same frequency. When the source eNodeB sends an RRC Connection
Reconfiguration message containing the handover command to the UE, the source
eNodeB counts the number of intra-frequency outgoing HO execution attempts in the
source cell at point B. When the source eNodeB receives a UE Context Release
message from the target eNodeB or receives a UE Context Release Command
message from the MME, indicating that the UE successfully accesses the target cell,
the source eNodeB counts the number of successful intra-frequency HO executions
in the source cell at point C.
Figure 3 X2-based outgoing HO without RRC connection reestablishment
Figure 4 S1-based outgoing HO without RRC connection reestablishment
 Inter-eNodeB outgoing HO with RRC connection reestablishment to the target cell
source cell at point B. When the source eNodeB receives a UE Context Release
message from the target eNodeB or receives a UE Context Release Command
message from the MME, indicating that the UE successfully accesses the target cell,
the source eNodeB counts the number of successful intra-frequency HO executions
in the source cell at point C.
Figure 5 X2-based outgoing HO with RRC connection reestablishment to the target
cell
Figure 6 S1-based outgoing HO with RRC connection reestablishment to the target
cell
 Inter-eNodeB outgoing HO with RRC connection reestablishment to the source cell
source cell at point B. When the source eNodeB receives an RRC Connection
Reestablishment Complete message from the UE, the source eNodeB counts the
number of successful intra-frequency outgoing HO executions in the source cell at
point C.
Figure 7 X2-based outgoing HO with RRC connection reestablishment to the source
cell
Figure 8 S1-based outgoing HO with RRC connection reestablishment to the source
cell
Definition
The Intra-Frequency Handover Out Success Rate KPI is defined in Table 1. Note that the
number of outgoing HO execution attempts and the number of successful outgoing HO
executions are collected based on the description in Description.
Table 1 Intra-Frequency Handover Out Success Rate
Name Intra-Frequency Handover Out Success Rate
Formula IntraFreqHOOut_SR =
(IntraFreqHOOutSuccess/IntraFreqHOOutAttempt) x 100%
Associated Intra-Frequency Handover Out Success Rate =

Counters [(L.HHO.IntraeNB.IntraFreq.ExecSuccOut +
L.HHO.IntereNB.IntraFreq.ExecSuccOut)/(L.HHO.IntraeNB.IntraFreq.ExecAttOut
+ L.HHO.IntereNB.IntraFreq.ExecAttOut)] x 100%
Unit Percentage (%)

Note None
Parent Topic: Mobility KPIs


Next topic >
8.4.3.5.2 Intra-Frequency Handover Out

Success Rate (VoIP)
Description
This KPI indicates the success rate of intra-frequency handovers (HOs) from the local
cell to neighboring E-UTRAN cells for VoIP services. The intra-frequency HOs are
classified into intra- and inter-eNodeB HOs.
Definition
The Intra-Frequency Handover Out Success Rate (VoIP) KPI is defined in Table 1.
Table 1 Intra-Frequency Handover Out Success Rate (VoIP)
Name Intra-Frequency Handover Out Success Rate (VoIP)
Formula IntraFreqHOOut_SR(VoIP) =
(IntraFreqHOOutSuccess_VoIP/IntraFreqHOOutAttempt_VoIP) x 100%
Associated Intra-Frequency Handover Out Success Rate (VoIP) =

Counters [(L.HHO.IntraeNB.IntraFreq.ExecSuccOut.VoIP +
L.HHO.IntereNB.IntraFreq.ExecSuccOut.VoIP)/(L.HHO.IntraeNB.IntraFreq.ExecAttOut.VoIP
+ L.HHO.IntereNB.IntraFreq.ExecAttOut.VoIP)] x 100%
Unit Percentage (%)
Note None


8.4.3.5.3 Inter-Frequency Handover Out
Success Rate
Description
This KPI indicates the success rate of inter-frequency handovers (HOs) from the local
cell to neighboring E-UTRAN cells. The measurement methods of the related counters
are similar to those for intra-frequency HOs described in Intra-Frequency Handover Out
Success Rate (All) > Description. The only difference is that the source and target cells
operate on different frequencies and both work in FDD or TDD mode.
Figure 1and Figure 2 illustrate intra-eNodeB HOs, and the source and target cells operate
on different frequencies. The source eNodeB counts the number of intra-eNodeB inter-
frequency outgoing HO execution attempts in the source cell at point B and counts the
number of successful intra-eNodeB inter-frequency HO executions in the source cell at
point C. Figure 3, Figure 4, Figure 5, Figure 6, Figure 7, and Figure 8 illustrate inter-eNodeB
HOs, and the source and target cells operate on different frequencies. The source
eNodeB counts the number of inter-eNodeB inter-frequency outgoing HO execution
attempts in the source cell at point B and counts the number of successful inter-eNodeB
inter-frequency HO executions in the source cell at point C.

Figure 5 X2-based outgoing HO with RRC connection reestablishment to the target cell
Figure 6 S1-based outgoing HO with RRC connection reestablishment to the target cell
cell
cell
Definition
The Inter-Frequency Handover Out Success Rate KPI is defined in Table 1. Note that the
Table 1 Inter-Frequency Handover Out Success Rate
Name Inter-Frequency Handover Out Success Rate
Formula InterFreqHOOut_SR =
(InterFreqHOOutSuccess/InterFreqHOOutAttempt) x 100%
Associated Inter-Frequency Handover Out Success Rate =

Counters [(L.HHO.IntraeNB.InterFreq.ExecSuccOut +
L.HHO.IntereNB.InterFreq.ExecSuccOut)/(L.HHO.IntraeNB.InterFreq.ExecAttOut
+ L.HHO.IntereNB.InterFreq.ExecAttOut)] x 100%
Unit Percentage (%)

Note None



Success Rate (VoIP)
Description
This KPI indicates the success rate of inter-frequency handovers (HOs) from the local
cell to neighboring E-UTRAN cells for VoIP services. The inter-frequency HOs are
classified into intra- and inter-eNodeB HOs. The source and target cells operate on
different frequencies and both work in FDD or TDD mode.
Definition
The the Inter-frequency Handover Out Success Rate (VoIP) KPI is defined in Table 1.
Table 1 Inter-frequency Handover Out Success Rate (VoIP)
Name Inter-frequency Handover Out Success Rate (VoIP)
Formula InterFreqHOOut_SR(VoIP) =
(InterFreqHOOutSuccess_VoIP/InterFreqHOOutAttempt_VoIP) x 100%
Associated Intra-Frequency Handover Out Success Rate (VoIP) =

Counters [(L.HHO.IntraeNB.InterFreq.ExecSuccOut.VoIP +
L.HHO.IntereNB.InterFreq.ExecSuccOut.VoIP)/(L.HHO.IntraeNB.InterFreq.ExecAttOut.VoIP
+ L.HHO.IntereNB.InterFreq.ExecAttOut.VoIP)] x 100%
Unit Percentage (%)
Note None


8.4.3.5.5 Inter-FddTdd Handover Out
Success Rate
Description
This KPI indicates the success rate of inter-duplex-mode handovers (HOs) from the
local cell to neighboring E-UTRAN cells. The measurement methods of the related
counters are similar to those for intra-frequency HOs described in Intra-Frequency Handover
Out Success Rate > Description. The only difference is that the source and target cells work
in different duplex modes.
Figure 1 and Figure 2 illustrate intra-eNodeB HOs, and the source and target cells work in
different duplex modes. The source eNodeB counts the number of intra-eNodeB inter-
duplex-mode outgoing HO execution attempts in the source cell at point B and counts
the number of successful intra-eNodeB inter-duplex-mode HO executions in the source
cell at point C. Figure 3, Figure 4, Figure 5, Figure 6, Figure 7, and Figure 8 illustrate inter-
eNodeB HOs, and the source and target cells work in different duplex modes. The
source eNodeB counts the number of inter-eNodeB inter-duplex-mode outgoing HO
execution attempts in the source cell at point B and counts the number of successful
inter-eNodeB inter-duplex-mode HO executions in the source cell at point C.

Figure 5 X2-based outgoing HO with RRC connection reestablishment to the target cell
Figure 6 S1-based outgoing HO with RRC connection reestablishment to the target cell
cell
cell
Definition
The Inter-FddTdd Handover Out Success Rate KPI is defined in Table 1. Note that the
Table 1 Inter-FddTdd Handover Out Success Rate
Name Inter-FddTdd Handover Out Success Rate
Formula InterFddTddHOOut_SR =
(InterFddTddHOOutSuccess/InterFddTddHOOutAttempt) x 100%
Associated Inter-FddTdd Handover Out Success Rate =

Counters [(L.HHO.IntraeNB.InterFddTdd.ExecSuccOut +
L.HHO.IntereNB.InterFddTdd.ExecSuccOut)/(L.HHO.IntraeNB.InterFddTdd.ExecAttOut
+ L.HHO.IntereNB.InterFddTdd.ExecAttOut)] x 100%
Unit Percentage (%)

Note None


8.4.3.5.6 Inter-FddTdd Handover Out

Success Rate (VoIP)
Description
This KPI indicates the success rate of inter-duplex-mode outgoing handovers for VoIP
services. The source and target cells work in different duplex modes.
Definition
The Inter-FddTdd Handover Out Success Rate (VoIP) KPI is defined in Table 1.
Table 1 Inter-FddTdd Handover Out Success Rate (VoIP)
Name Inter-FddTdd Handover Out Success Rate (VoIP)
Formula InterFddTddHOOut_SR(VoIP) =
(InterFddTddHOOutSuccess_VoIP/InterFddTddHOOutAttempt_VoIP) x 100%
Associated Inter-FddTdd Handover Out Success Rate (VoIP) =

Counters [(L.HHO.IntraeNB.InterFddTdd.ExecSuccOut.VoIP +
L.HHO.IntereNB.InterFddTdd.ExecSuccOut.VoIP)/(L.HHO.IntraeNB.InterFddTdd.ExecAttOut.VoIP
+ L.HHO.IntereNB.InterFddTdd.ExecAttOut.VoIP)] x 100%
Unit Percentage (%)
Note None


8.4.3.5.7 Intra-RAT Handover In Success
Rate
Description
This KPI indicates the success rate of intra-RAT handovers (HOs) from neighboring E-
UTRAN cells to the local cell. The intra-RAT HOs are classified into intra- and inter-
eNodeB HOs.
Intra-eNodeB Incoming HO
Intra-eNodeB incoming HOs can be further classified into HO with RRC connection
reestablishment and HO without RRC connection reestablishment.
 Intra-eNodeB incoming HO without RRC connection reestablishment
Figure 1illustrates an intra-eNodeB handover without RRC connection

reestablishment. When the eNodeB sends an RRC Connection Reconfiguration
message containing the handover command to the UE, the eNodeB counts the
number of intra-eNodeB incoming HO execution attempts in the target cell at point
B. When the eNodeB receives an RRC Connection Reconfiguration Complete
message from the UE, indicating that the handover finishes, the eNodeB counts the
number of successful intra-eNodeB incoming HO executions in the target cell at
point C.
Figure 1 Intra-eNodeB incoming HO without RRC connection reestablishment
 Intra-eNodeB incoming HO with RRC connection reestablishment
Figure 2illustrates an intra-eNodeB handover with RRC connection reestablishment.

When the eNodeB sends an RRC Connection Reconfiguration message containing
the handover command to the UE, the eNodeB counts the number of intra-eNodeB
incoming HO execution attempts in the target cell at point B. When the eNodeB
receives an RRC Connection Reestablishment Complete message from the UE, the
eNodeB counts the number of successful intra-eNodeB incoming HO executions in
the target cell at point C.
Figure 2 Intra-eNodeB incoming HO with RRC connection reestablishment
Inter-eNodeB Incoming HO
Inter-eNodeB incoming HOs can be further classified into HO without RRC connection
reestablishment and HO with RRC connection reestablishment to the target cell.
 Inter-eNodeB incoming HO without RRC connection reestablishment
Figure 3and Figure 4 illustrate X2- and S1-based incoming HOs without RRC
connection reestablishment, respectively. When the target eNodeB sends a Handover
Request Acknowledge message to the source eNodeB or MME, the target eNodeB
counts the number of incoming HO execution attempts in the target cell at point B.
When the target eNodeB receives an RRC Connection Reconfiguration Complete
message from the UE and sends a UE CONTEXT RELEASE message to the source
eNodeB or sends a HANDOVER NOTIFY message to the MME to instruct the
source eNodeB to release the UE context, the target eNodeB counts the number of
successful incoming HO executions in the target cell at point C.
Figure 3 X2-based incoming HO without RRC connection reestablishment
Figure 4 S1-based incoming HO without RRC connection reestablishment
 Inter-eNodeB incoming HO with RRC connection reestablishment to the target cell
Figure 5 illustrates an X2-based incoming HO with RRC connection reestablishment

to the target cell. When the target eNodeB sends a Handover Request Acknowledge
message to the source eNodeB or MME, the target eNodeB counts the number of
incoming HO execution attempts in the target cell at point B. When the target
UE and then sends a UE CONTEXT RELEASE message to the source eNodeB to
instruct the source eNodeB to release the UE context, the target eNodeB counts the
number of successful incoming HO executions in the target cell at point E.
Figure 5 X2-based incoming HO with RRC connection reestablishment to the target
cell
Figure 6illustrates an S1-based incoming HO with RRC connection reestablishment to

the target cell. When the target eNodeB sends a Handover Request Acknowledge
message to the source eNodeB or MME, the target eNodeB counts the number of
incoming HO execution attempts in the target cell at point B. When the target
UE and then sends a HANDOVER NOTIFY message to the MME to instruct the
source eNodeB to release the UE context, the target eNodeB counts the number of
successful incoming HO executions in the target cell at point C.
Figure 6 S1-based incoming HO with RRC connection reestablishment to the target
cell
Definition
The Intra-RAT Handover In Success Rate KPI is defined in Table 1. Note that the
number of incoming HO execution attempts and the number of incoming HO
Table 1 Intra-RAT Handover In Success Rate
Name Intra-RAT Handover In Success Rate
Formula Intra-RATHOIn_SR = (Intra-RATHOInSuccess/Intra-

RATHOInAttempt) x 100%
Associated Intra-RAT Handover In Success Rate = [(L.HHO.IntraeNB.ExecSuccIn +

Counters L.HHO.IntereNB.ExecSuccIn)/(L.HHO.IntraeNB.ExecAttIn +
L.HHO.IntereNB.ExecAttIn)] x 100%
Unit Percentage (%)
Note None

8.4.3.5.8 Inter-RAT Handover Out

Success Rate (LTE to CDMA2000)
Description
This KPI indicates the success rate of handovers from an LTE cell or radio network to
CDMA2000 networks.
The number of LTE-to-CDMA2000 HO attempts increases by 1 at point B as shown in
Figure 1 after the eNodeB sends a Mobility From EUTRA Command message to the UE.
The number of successful inter-RAT HOs from LTE to CDMA2000 increases by 1 at
point C, where the eNodeB receives a UE Context Release Command message from the
MME after the UE accesses the CDMA2000 network.
Figure 1 Inter-RAT handover (LTE to CDMA2000)
Definition
The Inter-RAT Handover Out Success Rate (LTE to CDMA2000) KPI is defined in
Table 1. For details about related counters, see Description.
Table 1 Inter-RAT Handover Out Success Rate (LTE to CDMA2000)
Name Inter-RAT Handover Out Success Rate (LTE to CDMA2000)
Formula IRATHO_L2C_SR =
(IRATHO_L2C_Success/IRATHO_L2C_Attempt) x 100%
Associated Inter-RAT Handover Out Success Rate (LTE to CDMA2000) =

Counters (L.IRATHO.E2C.ExecSuccOut/L.IRATHO.E2C.ExecAttOut) x 100%
Unit Percentage (%)
Note None



Success Rate (LTE to WCDMA)
Description
WCDMA networks.
The number of LTE-to-WCDMA HO attempts increases by 1 at point B as shown in
The number of successful inter-RAT HOs from LTE to WCDMA increases by 1 at
MME after the UE accesses the WCDMA network.
Figure 1 Inter-RAT handover (LTE to WCDMA/GSM/TD-SCDMA)
Definition
The Inter-RAT Handover Out Success Rate (LTE to WCDMA) KPI is defined in Table
1. For details about related counters, see Description.
Table 1 Inter-RAT Handover Out Success Rate (LTE to WCDMA)
Name Inter-RAT Handover Out Success Rate (LTE to WCDMA)
Formula IRATHO_L2W_SR =
(IRATHO_L2W_Success/IRATHO_L2W_Attempt) x 100%
Associated Inter-RAT Handover Out Success Rate (LTE to WCDMA) =

Counters (L.IRATHO.E2W.ExecSuccOut/L.IRATHO.E2W.ExecAttOut) x 100%
Unit Percentage (%)
Note None


Success Rate (LTE to GSM)
Description
GSM networks.
The number of LTE-to-GSM HO attempts increases by 1 at point B as shown in Figure 1
after the eNodeB sends a Mobility From EUTRA Command message to the UE. The
number of successful inter-RAT HOs from LTE to GSM increases by 1 at point C,
where the eNodeB receives a UE Context Release Command message from the MME
after the UE accesses the GSM network.
Definition
The Inter-RAT Handover Out Success Rate (LTE to GSM) KPI is defined in Table 1. For
details about related counters, see Description.
Table 1 Inter-RAT Handover Out Success Rate (LTE to GSM)
Name Inter-RAT Handover Out Success Rate (LTE to GSM)

Formula IRATHO_L2G_SR =
(IRATHO_L2G_Success/IRATHO_L2G_Attempt) x 100%
Associated Inter-RAT Handover Out Success Rate (LTE to GSM) =

Counters (L.IRATHO.E2G.ExecSuccOut/L.IRATHO.E2G.ExecAttOut) x 100%
Unit Percentage (%)
Note None



Success Rate (LTE to TD-SCDMA)
Description
TD-SCDMA networks.
The number of LTE-to-TD-SCDMA HO attempts increases by 1 at point B as shown in
The number of successful inter-RAT HOs from LTE to TD-SCDMA increases by 1 at
MME after the UE accesses the TD-SCDMA network.
Definition
The Inter-RAT Handover Out Success Rate (LTE to TD-SCDMA) KPI is defined in
Table 1. For details about related counters, see Description.
Table 1 Inter-RAT Handover Out Success Rate (LTE to TD-SCDMA)
Name Inter-RAT Handover Out Success Rate (LTE to TD-SCDMA)
Formula IRATHO_L2T_SR =
(IRATHO_L2T_Success/IRATHO_L2T_Attempt) x 100%
Associated Inter-RAT Handover Out Success Rate (LTE to TD-SCDMA) =

Counters (L.IRATHO.E2T.ExecSuccOut/L.IRATHO.E2T.ExecAttOut) x 100%
Unit Percentage (%)
Note None


8.4.3.5.12 CSFB Preparation Success
Rate
Description
This KPI indicates the preparation success rate of CS fallback (CSFB) from the E-
UTRAN to inter-RAT networks.
For a UE in RRC_Idle mode, the number of CSFB preparation attempts increases by 1
at point A as shown in Figure 1 after the eNodeB receives an INITIAL CONTEXT
SETUP REQUEST (with CS Fallback Indicator) message from the MME and
determines that the request is triggered by a voice service. The number of successful
CSFB preparations increases by 1 at point C, where the eNodeB successfully responses
an INITIAL CONTEXT SETUP RESPONSE message for the request triggered by the
voice service.
Figure 1 CSFB preparation for a UE in RRC_idle mode
For a UE in RRC_Connected mode, the number of CSFB preparation attempts increases

by 1 at point A as shown in Figure 2 after the eNodeB receives a UE CONTEXT
MODIFICATION REQUEST (with CS Fallback Indicator) message from the MME
and determines that the request is triggered by a voice service. The number of
successful CSFB preparations increases by 1 at point C, where the eNodeB successfully
responses a UE CONTEXT MODIFICATION RESPONSE message for the request
triggered by the voice service.
Figure 2 CSFB preparation for a UE in RRC_Connected mode
Definition
The CSFB Preparation Success Rate KPI is defined in Table 1. For details about related
counters, see Description.
Table 1 CSFB Preparation Success Rate
Name CSFB Preparation Success Rate
Formula CSFB_Preparation_SR =
(CSFB_Preparation_Success/CSFB_Preparation_Attempt) x 100%
Associated CSFB Preparation Success Rate = (L.CSFB.PrepSucc/L.CSFB.PrepAtt) x

Counters 100%
Unit Percentage (%)
Note None


8.4.3.5.13 CSFB Success Rate Based

Handover (LTE to WCDMA)
Description
This KPI indicates the success rate of handover-based LTE-to-WCDMA CSFB.
The number of handover-based LTE-to-WCDMA CSFB attempts increases by 1 at
point B as shown in Figure 1 after the eNodeB sends a Mobility From EUTRA Command
message to the UE and performs CSFB to a WCDMA network. The number of
successful handover-based LTE-to-WCDMA CSFB executions increases by 1 at point
C, where the eNodeB receives a UE CONTEXT RELEASE COMMAND message from
the MME after the UE successfully accesses the WCDMA network.
Definition
The CSFB Success Rate Based Handover (LTE to WCDMA) KPI is defined in Table 1.
For details about related counters, see Description.
Table 1 CSFB Success Rate Based Handover (LTE to WCDMA)
Name CSFB Success Rate Based Handover (LTE to WCDMA)
Formula CSFB_L2W_BasedHO_SR =
(CSFB_L2W_BasedHO_Success/CSFB_L2W_BasedHO_Attempt)
x 100%
Associated CSFB Success Rate Based Handover (LTE to WCDMA) =
Counters (L.IRATHO.E2W.CSFB.ExecSuccOut/L.IRATHO.E2W.CSFB.ExecAttOut) x
100%
Unit Percentage (%)
Note None



Handover (LTE to GSM)
Description
This KPI indicates the success rate of handover-based LTE-to-GSM CSFB.
The number of handover-based LTE-to-GSM CSFB attempts increases by 1 at point B
as shown in Figure 1 after the eNodeB sends a Mobility From EUTRA Command
message to the UE and performs CSFB to a GSM network. The number of successful
handover-based LTE-to-GSM CSFB executions increases by 1 at point C, where the
eNodeB receives a UE CONTEXT RELEASE COMMAND message from the MME
after the UE successfully accesses the GSM network.
Definition
The CSFB Success Rate Based Handover (LTE to GSM) KPI is defined in Table 1.For
details about related counters, see Description.
Table 1 CSFB Success Rate Based Handover (LTE to GSM)
Name CSFB Success Rate Based Handover (LTE to GSM)
Formula CSFB_L2G_BasedHO_SR =
(CSFB_L2G_BasedHO_Success/CSFB_L2G_BasedHO_Attempt) x
100%
Associated CSFB Success Rate Based Handover (LTE to GSM) =

Counters (L.IRATHO.E2G.CSFB.ExecSuccOut/L.IRATHO.E2G.CSFB.ExecAttOut) x
100%
Unit Percentage (%)
Note None


Handover (LTE to TD-SCDMA)
Description
This KPI indicates the success rate of handover-based LTE-to-TD-SCDMA CSFB.
The number of handover-based LTE-to-TD-SCDMA CSFB attempts increases by 1 at
point B as shown in Figure 1 after the eNodeB sends a Mobility From EUTRA Command
message to the UE and performs CSFB to a TD-SCDMA network. The number of
successful handover-based LTE-to-TD-SCDMA CSFB executions increases by 1 at
point C, where the eNodeB receives a UE CONTEXT RELEASE COMMAND
message from the MME after the UE successfully accesses the TD-SCDMA network.
Definition
The CSFB Success Rate Based Handover (LTE to TD-SCDMA) KPI is defined in Table
1. The number of handover-based LTE-to-TD-SCDMA CSFB attempts and the number
of successful handover-based LTE-to-TD-SCDMA CSFB executions are collected as
described in Description.
Table 1 CSFB Success Rate Based Handover (LTE to TD-SCDMA)
Name CSFB Success Rate Based Handover (LTE to TD-SCDMA)
Formula CSFB_L2T_BasedHO_SR =
(CSFB_L2T_BasedHO_Success/CSFB_L2T_BasedHO_Attempt) x
100%
Associated CSFB Success Rate Based Handover (LTE to TD-SCDMA) =

Counters (L.IRATHO.E2T.CSFB.ExecSuccOut/L.IRATHO.E2T.CSFB.ExecAttOut) x 100%
Unit Percentage (%)
Note None


8.4.3.5.16 SRVCC Success Rate (LTE to

WCDMA)
Description
This KPI indicates the success rate of SRVCC-based LTE-to-WCDMA handovers.
Definition
The SRVCC Success Rate (LTE to WCDMA) KPI is defined in Table 1.
Table 1 SRVCC Success Rate (LTE to WCDMA)
Name SRVCC Success Rate (LTE to WCDMA)
Formula SRVCC _SR _L2W = (SRVCC_Success_L2W /

SRVCC_Attempt_L2W) x 100%
Associated SRVCC Success Rate (LTE to WCDMA) =

Counters [(L.IRATHO.SRVCC.E2W.ExecSuccOut –
L.IRATHO.SRVCC.E2W.MMEAbnormRsp)/L.IRATHO.SRVCC.E2W.ExecAttOut]
x 100%
Unit Percentage (%)
Note None



GSM)
Description
This KPI indicates the success rate of SRVCC-based LTE-to-GSM handovers.
Definition
The SRVCC Success Rate (LTE to GSM) KPI is defined in Table 1.
Table 1 SRVCC Success Rate (LTE to GSM)
Name SRVCC Success Rate (LTE to GSM)
Formula SRVCC_SR_L2G = (SRVCC_Success_L2G /

SRVCC_Attempt_L2G) x 100%
Associated SRVCC Success Rate (LTE to GSM) =

Counters [(L.IRATHO.SRVCC.E2G.ExecSuccOut –
L.IRATHO.SRVCC.E2G.MMEAbnormRsp)/L.IRATHO.SRVCC.E2G.ExecAttOut] x
100%
Unit Percentage (%)
Note None


TD-SCDMA)
Description
This KPI indicates the success rate of SRVCC-based LTE-to-TD-SCDMA handovers.
Definition
The SRVCC Success Rate (LTE to TD-SCDMA) KPI is defined in Table 1.
Table 1 SRVCC Success Rate (LTE to TD-SCDMA)
Name SRVCC Success Rate (LTE to TD-SCDMA)
Formula SRVCC_SR_L2T = (SRVCC_Success_L2T/SRVCC_Attempt_L2T)

x 100%
Associated SRVCC Success Rate (LTE to TD-SCDMA) =

Counters [(L.IRATHO.SRVCC.E2T.ExecSuccOut –
L.IRATHO.SRVCC.E2T.MMEAbnormRsp)/L.IRATHO.SRVCC.E2T.ExecAttOut] x
100%
Unit Percentage (%)
Note None


8.4.3.5.19 Intra-Frequency Handover

Out Success Rate (eMTC)
Description
This KPI indicates the intra-frequency outgoing handover success rate of eMTC UEs.
The measurement methods of related counters are described in Intra-Frequency Handover
Out Success Rate(All) > KPI Description.
Definition
The Intra-Frequency Handover Out Success Rate (eMTC) KPI is defined in Table 1.
Table 1 Intra-Frequency Handover Out Success Rate (eMTC)
Name Intra-Frequency Handover Out Success Rate (eMTC)
Formula IntraFreqHOOut_SR =
(IntraFreqHOOutSuccess/IntraFreqHOOutAttempt) x 100%
Associated Intra-Frequency Handover Out Success Rate (eMTC) =

Counters (L.HHO.IntraFreq.eMTC.ExecSuccOut/L.HHO.IntraFreq.eMTC.ExecAttOut) x
100%
Unit Percentage (%)
Note None



Success Rate (eMTC)
Description
This KPI indicates the inter-frequency outgoing handover success rate of eMTC UEs.
The measurement methods of related counters are described in Inter-Frequency Handover
Out Success Rate(All) > KPI Description.
Definition
The Inter-Frequency Handover Out Success Rate (eMTC) KPI is defined in Table 1.
Table 1 Inter-Frequency Handover Out Success Rate (eMTC)
Name Inter-Frequency Handover Out Success Rate (eMTC)
Formula InterFreqHOOut_SR =
(InterFreqHOOutSuccess/InterFreqHOOutAttempt) x 100%
Associated Inter-Frequency Handover Out Success Rate (eMTC) =

Counters (L.HHO.InterFreq.eMTC.ExecSuccOut/L.HHO.InterFreq.eMTC.ExecAttOut) x
100%
Unit Percentage (%)
Note None


8.4.3.5.21 Intra-RAT Handover Out

Success Rate (NSA DC)
Description
This KPI indicates the intra-frequency and inter-frequency outgoing handover success
rate of NSA DC UEs. The measurement methods of related counters are described in
Intra-Frequency Handover Out Success Rate (All) > KPI Description and Inter-Frequency Handover Out
Success Rate (All) > KPI Description.
Definition
The Intra-RAT Handover Out Success Rate (NSA DC) KPI is defined in Table 1.
Table 1 Intra-RAT Handover Out Success Rate (NSA DC)
Name Intra-RAT Handover Out Success Rate (NSA DC)
Formula IntraRATHOOut_SR =
(IntraRATHOOutSuccess/IntraRATHOOutAttempt) x 100%
Associated Intra-RAT Handover Out Success Rate (NSA DC) =
Counters (L.NsaDc.HHO.ExecSuccOut/L.NsaDc.HHO.ExecAttOut) x 100%
Unit Percentage (%)
Note None


< Previous topic
8.4.3.6 Service Integrity KPIs

The service integrity KPIs indicate service quality provided for UEs in an E-UTRAN.
User Downlink Average Throughput
User Uplink Average Throughput
Service Downlink Average Throughput
Service Uplink Average Throughput
Cell Downlink Average Throughput
Cell Uplink Average Throughput
Downlink Packet Loss Rate
Downlink Packet Loss Rate (VoIP)
Uplink Packet Loss Rate
Uplink Packet Loss Rate (VoIP)
Downlink Residual Block Error Rate (eMTC)
Uplink Residual Block Error Rate (eMTC)
User Downlink Split Average Throughput (NSA DC)
User Uplink Split Average Throughput (NSA DC)


8.4.3.6.1 User Downlink Average

Throughput
Description
This KPI indicates the average downlink UE throughput in a cell. According to 3GPP
TS 32.450, the throughput measurement needs to remove the data scheduled in the last
TTI before the downlink buffer is empty, as shown in Figure 1.
Figure 1 Downlink throughput measurement defined in 3GPP TS 32.450
Definition
The User Downlink Average Throughput KPI is defined in Table 1 and is calculated
based on the total downlink traffic volume except for the data scheduled in the last TTI
before the downlink buffer is empty and the downlink data transmission duration except
for the last TTI before the downlink buffer is empty.
Table 1 User Downlink Average Throughput
Name User Downlink Average Throughput
Formula UserDLAveThp =
UserDLRmvLastTTITrafficVolume/UserDLRmvLastTTITransferTime
Associated User Downlink Average Throughput = (L.Thrp.bits.DL –

Counters L.Thrp.bits.DL.LastTTI)/L.Thrp.Time.DL.RmvLastTTI
Unit kbit/s
Note None
Parent Topic: Service Integrity KPIs


Next topic >
8.4.3.6.2 User Uplink Average

Throughput
Description
This KPI indicates the average uplink UE throughput in a cell.
The throughput measurement needs to exclude the data scheduled in the last TTI before
the uplink buffer is empty.
Definition
The User Uplink Average Throughput KPI in FDD and TDD is defined in Table 1.
Table 1 User Uplink Average Throughput
Name User Uplink Average Throughput
Formula UserULAveThp =
UserULRmvLastTTITrafficVolume/UserULRmvLastTTITransferTime
UserULAveThp =
UserULRmvSmallPktTrafficVolume/UserULRmvSmallPktTransferTime
Associated The following formulas are both applicable, and the second formula is
Counters more close to the protocol.
User Uplink Average Throughput = (L.Thrp.bits.UL –
L.Thrp.bits.UE.UL.LastTTI)/L.Thrp.Time.UE.UL.RmvLastTTI
User Uplink Average Throughput = (L.Thrp.bits.UL –
L.Thrp.bits.UE.UL.SmallPkt)/L.Thrp.Time.UE.UL.RmvSmallPkt
Unit kbit/s
Note For LTE TDD, the uplink-downlink subframe configuration must be

considered when operators compare the calculation result using the first
formula with the theoretical peak rate.


8.4.3.6.3 Service Downlink Average

Throughput
Description
This KPI consists of nine sub-KPIs that are mapped to nine QCIs. These sub-KPIs
indicate the busy-hour downlink (DL) throughput of a service with a specific QCI per
user in each cell. The Service Downlink Average Throughput KPI reflects the end-user
experience.
Definition
The Service Downlink Average Throughput KPI is defined in Table 2[6]. Nine different
sub-KPIs exist for each QCI. The formula for each KPI is mapped to its corresponding
counter. Table 1 lists the requirements for services with different QCIs.
Table 1 Requirements for services with different QCIs
QCI Resource Priority Packet Packet Error Example of Services

Type Delay Loss Rate
Budget (Note 2)
(Note 1)
1 GBR 2 100 ms 10-2 Conversational voice
2 4 150 ms 10-3 Conversational video

(live streaming)
3 3 50 ms 10-3 Real time gaming
4 5 300 ms 10-6 Non-conversational video

(buffered streaming)
5 Non-GBR 1 100 ms 10-6 IMS signaling
6 6 300 ms 10-6 Video (buffered

streaming) TCP-based
(e.g., www, e-mail, chat,
ftp, p2p file sharing,
progressive video, etc.)
7 7 100 ms 10-3 Voice, video (live

streaming) interactive
gaming
8 8 300 ms 10-6 Video (buffered

streaming) TCP-based
9 9 300 ms 10-6 (e.g., www, e-mail, chat,
ftp, p2p file sharing,
progressive video, etc.)
Table 2 Service Downlink Average Throughput
Name Service Downlink Average Throughput
Formula DLAverageThroughput_QCI_1
DLAverageThroughput_QCI_2
Associated Service Downlink Average Throughput = (L.Thrp.bits.DL.QCI.n –

Counters L.Thrp.bits.DL.LastTTI.QCI.n)/L.Thrp.Time.DL.RmvLastTTI.QCI.n
n = 1 to 9
Unit kbit/s
Note None


8.4.3.6.4 Service Uplink Average

Throughput
Description
This KPI consists of nine sub-KPIs that are mapped to nine QCIs. These sub-KPIs
indicate the busy-hour uplink (UL) throughput of a service with a specific QCI per user
in each cell. The Service Uplink Average Throughput KPI reflects the end-user
experience.
Definition
The Service Uplink Average Throughput KPI is defined in Table 1[6]. Nine sub-KPIs
exist for each QCI. The formula for each KPI is mapped to its corresponding counter.
Table 1 Service Uplink Average Throughput
Name Service Uplink Average Throughput
Formula ULAverageThroughput_QCI_1
ULAverageThroughput_QCI_2
Associated  FDD:
Counters Service Uplink Average Throughput =
L.Thrp.bits.UL.QCI.n/L.Thrp.Time.UL.QCI.n
 TDD:
Service Uplink Average Throughput =
L.Thrp.bits.UL.QCI.n/L.Thrp.Time.UL.QCI.n x (Number of uplink
subframes per radio frame/10)
n = 1 to 9
Unit kbit/s
Note None


8.4.3.6.5 Cell Downlink Average

Throughput
Description
This KPI indicates a cell's average downlink throughput when data is transferring at the
downlink. The Cell Downlink Average Throughput KPI reflects the cell's capacity.
Definition
The Cell Downlink Average Throughput KPI is defined in Table 1 and is calculated
based on all the data transferred at the downlink and the time it takes to transfer. The
formula is mapped to its corresponding counters.
Table 1 Cell Downlink Average Throughput

Name Cell Downlink Average Throughput
Formula CellDLAveThp = CellDLTrafficVolume/CellDLTransferTime
Associated Cell Downlink Average Throughput =

Counters L.Thrp.bits.DL/L.Thrp.Time.Cell.DL.HighPrecision
Unit kbit/s

considered when operators compare the calculation result with the
theoretical peak rate.


8.4.3.6.6 Cell Uplink Average

Throughput
Description
This KPI indicates the average cell uplink throughput. The Cell Uplink Average
Throughput KPI reflects the cell's capacity.
Definition
The Cell Uplink Average Throughput KPI is defined in Table 1 and is calculated based
on all the data transferred at the uplink and the time it takes to transfer. The formula is
mapped to its corresponding counters.
Table 1 Cell Uplink Average Throughput
Name Cell Uplink Average Throughput
Formula CellULAveThp = CellULTrafficVolume/CellULTransferTime
Associated Cell Uplink Average Throughput =

Counters L.Thrp.bits.UL/L.Thrp.Time.Cell.UL.HighPrecision
Unit kbit/s

considered when operators compare the calculation result with the
theoretical peak rate.



Description
This KPI indicates the downlink packet loss situation of a cell at the PDCP layer. This
KPI is calculated based on the number of dropped PDCP SDUs and the total number of
downlink PDCP SDUs transmitted for services carried on DRBs with all QCIs
(including the QCI for PTT services and extended QCIs) in a cell over the Uu interface.
Definition
The Downlink Packet Loss Rate KPI is defined in Table 1.
Table 1 Downlink Packet Loss Rate
Name Downlink Packet Loss Rate
Formula DLPacketLossRate =
NumOfDlLostPackets/NumberOfDlTransmittedPacket
Associated Downlink Packet Loss Rate =

Counters (L.Traffic.DL.PktUuLoss.Loss/L.Traffic.DL.PktUuLoss.Tot) x 100%
Unit Percentage (%)
Note None


(VoIP)
Description
This KPI indicates the downlink packet loss situation of a cell at the PDCP layer. The
KPI is decided by the number of lost PDCP SDUs and the total number of downlink
PDCP SDUs transmitted for services carried on DRBs with QCI of 1 in a cell over the
Uu interface.
Definition
The Downlink Packet Loss Rate KPI is defined in Table 1.
Table 1 Downlink Packet Loss Rate (VoIP)
Name Downlink Packet Loss Rate (VoIP)
Formula DLPacketLossRate (VoIP) =

Associated Downlink Packet Loss Rate (VoIP) =

Counters (L.Traffic.DL.PktUuLoss.Loss.QCI.1/L.Traffic.DL.PktUuLoss.Tot.QCI.1) x 100%
Unit Percentage (%)
Note None



Description
This KPI indicates the uplink packet loss situation of a cell at the PDCP layer. The KPI
is calculated based on the total number of dropped uplink PDCP SDUs for services
carried on DRBs with all QCIs (including the QCI for PTT services and extended QCIs)
and the total number of packets expected to be received in the uplink.
Definition
The Uplink Packet Loss Rate KPI is defined in Table 1.
Table 1 Uplink Packet Loss Rate
Name Uplink Packet Loss Rate
Formula ULPacketLossRate =
NumOfUlLostPackets/NumberOfUlTransmittedPacket
Associated Uplink Packet Loss Rate =

Counters (L.Traffic.UL.PktLoss.Loss/L.Traffic.UL.PktLoss.Tot) x 100%
Unit Percentage (%)
Note None



(VoIP)
Description
This KPI indicates the uplink packet loss situation of a cell at the PDCP layer for VoIP
services. The KPI is calculated based on the total number of dropped PDCP SDUs for
services carried on DRBs with QCI of 1 and the total number of packets expected to be
received in the uplink.
Definition
The Uplink Packet Loss Rate KPI is defined in Table 1.
Table 1 Uplink Packet Loss Rate (VoIP)
Name Uplink Packet Loss Rate (VoIP)

Formula ULPacketLossRate (VoIP) =
Associated Uplink Packet Loss Rate (VoIP) =

Counters (L.Traffic.UL.PktLoss.Loss.QCI.1/L.Traffic.UL.PktLoss.Tot.QCI.1) x 100%
Unit Percentage (%)
Note None


8.4.3.6.11 Downlink Residual Block

Error Rate (eMTC)
Description
This KPI indicates the downlink residual bit error rate of eMTC UEs in a cell. The KPI
is calculated based on the number of TBs that failed to be retransmitted on the DL-SCH
after the maximum number of retransmissions is reached for eMTC UEs in the cell and
the number of TBs that are initially transmitted on the DL-SCH for eMTC UEs in the
cell.
Definition
The Downlink Residual Block Error Rate (eMTC) KPI is defined in Table 1.
Table 1 Downlink Residual Block Error Rate (eMTC)
Name Downlink Residual Block Error Rate (eMTC)
Formula Downlink Residual Block Error Rate (eMTC) =

NumOfDlschErrTB/NumberOfDlschTransmittedTB x 100%
Associated Downlink Residual Block Error Rate (eMTC) =

Counters [(L.Traffic.DL.SCH.QPSK.eMTC.ErrTB.Rbler +
L.Traffic.DL.SCH.16QAM.eMTC.ErrTB.Rbler)/(L.Traffic.DL.SCH.QPSK.eMTC.TB
+ L.Traffic.DL.SCH.16QAM.eMTC.TB)] x 100%
Unit Percentage (%)
Note None


8.4.3.6.12 Uplink Residual Block Error

Rate (eMTC)
Description
This KPI indicates the uplink residual bit error rate of eMTC UEs in a cell. The KPI is
calculated based on the number of TBs that failed to be retransmitted on the UL-SCH
after the maximum number of retransmissions is reached for eMTC UEs in the cell and
the number of TBs that are initially transmitted on the UL-SCH for eMTC UEs in the
cell.
Definition
The Uplink Residual Block Error Rate (eMTC) KPI is defined in Table 1.
Table 1 Uplink Residual Block Error Rate (eMTC)
Name Uplink Residual Block Error Rate (eMTC)
Formula Uplink Residual Block Error Rate (eMTC) =

NumOfUlschErrTB/NumberOfUlschTransmittedTB x 100%
Associated Uplink Residual Block Error Rate (eMTC) =

Counters [(L.Traffic.UL.SCH.QPSK.eMTC.ErrTB.Rbler +
L.Traffic.UL.SCH.16QAM.eMTC.ErrTB.Rbler)/(L.Traffic.UL.SCH.QPSK.eMTC.TB
+ L.Traffic.UL.SCH.16QAM.eMTC.TB)] x 100%
Unit Percentage (%)
Note None


8.4.3.6.13 User Downlink Split Average

Throughput (NSA DC)
Description
This KPI indicates the average downlink split throughput of NSA DC UEs in a cell.
According to 3GPP TS 32.450, the throughput measurement needs to remove the data
scheduled in the last TTI before the downlink buffer is empty.
Definition
The User Downlink Split Average Throughput (NSA DC) KPI is defined in Table 1 and
is calculated based on the total downlink traffic volume of NSA DC UEs except for the
data scheduled in the last TTI before the downlink buffer is empty and the downlink
data transmission duration for NSA DC UEs except for the last TTI before the downlink
buffer is empty.
Table 1 User Downlink Split Average Throughput (NSA DC)
Name User Downlink Split Average Throughput (NSA DC)
Formula NsaDcUserDLAveThp =
NsaDcUserDLRmvLastTTITrafficVolume/NsaDcUserDLRmvLastTTITransferTime
Associated User Downlink Split Average Throughput (NSA DC) = (L.Thrp.bits.DL.NsaDc –

Counters L.Thrp.bits.DL.LastTTI.NsaDc)/L.Thrp.Time.DL.RmvLastTTI.NsaDc
Unit kbit/s
Note None


8.4.3.6.14 User Uplink Split Average
Throughput (NSA DC)
Description
This KPI indicates the average uplink split throughput of NSA DC UEs in a cell.
Definition
The User Uplink Split Average Throughput (NSA DC) KPI is defined in Table 1.
Table 1 User Uplink Split Average Throughput (NSA DC)
Name User Uplink Split Average Throughput (NSA DC)
Formula NsaDcUserULAveThp =
UserULTrafficVolume/UserULransferTime
Associated User Uplink Split Average Throughput (NSA DC) =

Counters L.Thrp.bits.UL.NsaDc/L.Thrp.Time.UL.NsaDc
Unit kbit/s
Note None


< Previous topic
8.4.3.7 Utilization KPIs

Utilization KPIs are used to evaluate the capabilities, such as the capability to meet
traffic demands, in specific internal conditions.
Downlink Resource Block Utilizing Rate
Uplink Resource Block Utilizing Rate
Uplink Preschedule Resource Block Occupied Rate
Average CPU Load
Downlink Resource Block Utilizing Rate (NSA DC)
Uplink Resource Block Utilizing Rate (NSA DC)

8.4.3.7.1 Downlink Resource Block

Utilizing Rate
Description
This KPI indicates the busy-hour downlink RB utilization rates in a cell or on a radio
network.
Definition
The downlink Resource Block Utilizing Rate KPI is defined in Table 1.
Table 1 Downlink Resource Block Utilizing Rate
Name Downlink Resource Block Utilizing Rate
Formula RB_URDL = (RB_UsedDL/RB_AvailableDL) x 100%
Associated Downlink Resource Block Utilizing Rate =

Counters (L.ChMeas.PRB.DL.Used.Avg/L.ChMeas.PRB.DL.Avail) x 100%
Unit Percentage (%)
Note None
Parent Topic: Utilization KPIs


Next topic >
8.4.3.7.2 Uplink Resource Block Utilizing

Rate
Description
This KPI indicates the busy-hour uplink RB utilization rates in a cell or on a radio
network.
Definition
The uplink Resource Block Utilizing Rate KPI is defined in Table 1.
Table 1 Uplink Resource Block Utilizing Rate
Name Uplink Resource Block Utilizing Rate
Formula RB_URUL = (RB_UsedUL/RB_AvailableUL) x 100%
Associated Uplink Resource Block Utilizing Rate =

Counters (L.ChMeas.PRB.UL.Used.Avg/L.ChMeas.PRB.UL.Avail) x 100%
Unit Percentage (%)
Note None


8.4.3.7.3 Uplink Preschedule Resource

Block Occupied Rate
Description
This KPI indicates the percentage of uplink RBs allocated to UEs for pre-scheduling.
The KPI is used to evaluate the impact on uplink RB usage caused by pre-scheduling.
If pre-scheduling is enabled, when there are remaining uplink RBs in a cell, the eNodeB
allocates uplink RBs to UEs that have not sent a bandwidth request to reduce the uplink
service delay of these UEs.
Definition
The Uplink Preschedule Resource Block Occupied Rate KPI is defined in Table 1.
Table 1 Uplink Preschedule Resource Block Occupied Rate
Name Uplink Preschedule Resource Block Occupied Rate

Formula PrescheduleRB_URUL =
RB_PrescheduleUsedUL/RB_AvailableUL
Associated Uplink Preschedule Resource Block Occupied Rate =

Counters L.ChMeas.PRB.UL.PreSch.Used.Avg/L.ChMeas.PRB.UL.Avail
Unit Percentage (%)
Note None


8.4.3.7.4 Average CPU Load

Description
This KPI indicates the CPU usage during busy hours.
Definition
The Average CPU Load KPI is defined in Table 1. The CPU load is calculated by
averaging the CPU usage ratio during the measurement period.
Table 1 Average CPU Load
Name Average CPU Load
Object CPU
Formula MeanCPUUtility
Associated Average CPU Load = VS.BBUBoard.CPULoad.Mean

Counters
Unit Percentage (%)
Note None

8.4.3.7.5 Downlink Resource Block

Utilizing Rate (NSA DC)
Description
This KPI indicates the busy-hour downlink RB utilization rates of NSA DC UEs in a
cell or on a radio network.
Definition
The Downlink Resource Block Utilizing Rate (NSA DC) KPI is defined in Table 1.
Table 1 Downlink Resource Block Utilizing Rate (NSA DC)
Name Downlink Resource Block Utilizing Rate (NSA DC)
Formula RB_URDL = (RB_UsedDL/RB_AvailableDL) x 100%
Associated Downlink Resource Block Utilizing Rate (NSA DC) =

Counters (L.ChMeas.PRB.DL.NsaDc.Used.Avg/L.ChMeas.PRB.DL.Avail) x 100%
Unit Percentage (%)
Note None


8.4.3.7.6 Uplink Resource Block Utilizing

Rate (NSA DC)
Description
This KPI indicates the busy-hour uplink RB utilization rates of NSA DC UEs in a cell
or on a radio network.
Definition
The Uplink Resource Block Utilizing Rate (NSA DC) KPI is defined in Table 1.
Table 1 Uplink Resource Block Utilizing Rate (NSA DC)
Name Uplink Resource Block Utilizing Rate (NSA DC)
Formula RB_URUL = (RB_UsedUL/RB_AvailableUL) x 100%
Associated Uplink Resource Block Utilizing Rate (NSA DC) =

Counters (L.ChMeas.PRB.UL.NsaDc.Used.Avg/L.ChMeas.PRB.UL.Avail) x 100%
Unit Percentage (%)
Note None


< Previous topic
8.4.3.8 Availability KPIs

A cell is available when the eNodeB can provide EPS bearer services. Availability in a
cell can be measured when a variety of hardware or software faults occur in the cell.
Radio Network Availability Rate


8.4.3.8.1 Radio Network Availability Rate

Description
This KPI indicates the percentage of time when cells in a radio network are available.
The KPI is used to evaluate the cell working status during busy hours.
Definition
The Radio Network Availability Rate KPI is defined in Table 1. The KPI is calculated
based on all cells on the radio network.
Table 1 Radio Network Availability Rate
Name Radio Network Availability Rate
Object Radio network
Formula RAN_Avail_Rate =
[CellAvailTime/(TheTotalNumberOfCellsInCluster x SP x 60)] x
100%
Associated Radio Network Availability Rate = [L.Cell.Avail.Dur/(Number of cells x

Counters SP x 60)] x 100%
SP indicates the reporting period for counters in minutes.
Unit Percentage (%)
Note None
Parent Topic: Availability KPIs

8.4.3.9 Traffic KPIs

Traffic KPIs are used to measure the traffic volume on the LTE radio access network
(RAN). Based on traffic types, the traffic KPIs are classified into the following
categories: radio bearers, downlink traffic volume, and uplink traffic volume.
Radio Bearers
Downlink Traffic Volume
Uplink Traffic Volume
Average User Number
Maximum User Number


8.4.3.9.1 Radio Bearers

Description
This KPI consists of ten sub-KPIs. One KPI corresponds to the total of radio bearers
and the other nine correspond to nine QCIs. This set of sub-KPIs indicates the average
number of radio bearers in a cell or on a radio network. The radio bearer for each QCI is
based on the number of active RRC connections for each QCI, according to the QCI
defined in the QoS information.
Definition
The Radio Bearers KPIs are defined in Table 1 and include ten different sub-KPIs. The
formula for each KPI is mapped to its corresponding counter.
Table 1 Radio Bearers
Name Radio Bearers
Formula RadioBearers
RadioBearers_QCI_1
RadioBearers_QCI_2
RadioBearers_QCI_3
RadioBearers_QCI_4
RadioBearers_QCI_5
RadioBearers_QCI_6
RadioBearers_QCI_7
RadioBearers_QCI_8
RadioBearers_QCI_9
Associated Radio Bearers = L.Traffic.DRB

Counters RadioBearers of QCIn = L.Traffic.DRB.QCI.n
n = 1 to 9
Unit N/A
Note None
Parent Topic: Traffic KPIs


Next topic >
8.4.3.9.2 Downlink Traffic Volume

Description
Similar to the Radio Bearers KPI, the Downlink Traffic Volume KPI consists of ten
sub-KPIs. One KPI corresponds to the total DRB traffic volume, and the other nine
correspond to nine QCIs. This set of sub-KPIs indicates the downlink traffic volume in
a cell, which is measured at the PDCP layer and excludes the PDCP header.
Definition
The Downlink Traffic Volume KPI is defined in Table 1.
Table 1 Downlink Traffic Volume
Name Downlink Traffic Volume
Formula DLTrafficVolume
DLTrafficVolume_QCI_1
Associated Downlink Traffic Volume = L.Thrp.bits.DL

Counters Downlink Traffic Volume of QCIn = L.Thrp.bits.DL.QCI.n
n = 1 to 9
Unit bit
Note None


8.4.3.9.3 Uplink Traffic Volume

Definition
Similar to the Downlink Traffic Volume KPI, the Uplink Traffic Volume KPI consists
of ten sub-KPIs. One KPI corresponds to the total of traffic volume for DRBs, and the
other nine correspond to nine QCIs. This set of sub-KPIs indicates a cell's uplink traffic
volume. The sub-KPIs are measured at the PDCP layer and exclude the PDCP header.
Description
The Uplink Traffic Volume KPI is defined in Table 1.
Table 1 Uplink Traffic Volume
Name Uplink Traffic Volume
Formula ULTraffic Volume

ULTraffic Volume_QCI_1
Associated Uplink Traffic Volume = L.Thrp.bits.UL

Counters Uplink Traffic Volume of QCIn = L.Thrp.bits.UL.QCI.n
n = 1 to 9
Unit bit
Note None


8.4.3.9.4 Average User Number

Description
This KPI indicates the average number of users in RRC_Connected mode in a cell. This
value is calculated based on samples. The eNodeB records the number of users in the
cell to be sampled every second and then calculates the average value of these samples
throughout the measurement period.
Definition
The Average User Number KPI is defined in Table 1. The formula is mapped to its
corresponding counters.
Table 1 Average User Number
Name Average User Number
Formula AvgUserNumber
Associated Average User Number = L.Traffic.User.Avg

Counters
Unit N/A
Note None


8.4.3.9.5 Maximum User Number

Description
This KPI evaluates the maximum number of users in RRC_Connected mode of a cell in
a certain period of time. This value is calculated based on samples. The eNodeB records
the number of users in the cell to be sampled every second and then calculates the
maximum value of these samples throughout the measurement period.
Definition
The Maximum User Number KPI is defined in Table 1. The formula is mapped to its
corresponding counters.
Table 1 Maximum User Number
Name Maximum User Number
Formula MaxUserNumber
Associated Maximum User Number = L.Traffic.User.Max

Counters
Unit N/A
Note None


< Previous topic
8.4.3.10 NB-IoT Accessibility KPIs

NB-IoT accessibility KPIs represent the probability that UEs access an NB-IoT network
and are used to evaluate the UE access performance in the NB-IoT network.
RRC Setup Success Rate (NB-IoT)
RRC Resume Success Rate (NB-IoT)


8.4.3.10.1 RRC Setup Success Rate (NB-

IoT)
Description
According to 3GPP specifications[7], RRC connection setup procedures can be triggered
by the causes mt-Access, mo-Signalling, mo-Data, and mo-ExceptionData. A UE sets
the setup cause in accordance with the information it receives from upper layers. This
KPI indicates the RRC connection setup success rate of an NB-IoT cell or an entire NB-
IoT network.
The KPI is measured by the eNodeB when UEs initiate RRC connection setup
procedures. As shown in Figure 1, the number of RRC connection setup attempts is
counted at point A when the eNodeB receives RRC Connection Request messages from
UEs. The number of successful RRC connection setups is counted at point C.
In addition, when a UE-initiated RRC connection resume procedure fails, the eNodeB
transfers the resume procedure into an RRC connection setup procedure in accordance
with the 3GPP specifications. As shown in Figure 2, the
L.NB.RRC.ResumeFail.RRCSetup counter is incremented at point A when the eNodeB
receives an RRC Connection Resume Request message from a UE, and the RRC
connection resume procedure fails and is transferred into an RRC connection setup
procedure. The number of successful RRC connection setups is counted at point C.
Figure 2 Measurement points for RRC connection setup transferred from RRC
connection resume failure
Definition
The RRC Setup Success Rate (NB-IoT) KPI is defined in Table 1. For details about how
to measure counters related to the number of RRC connection setup attempts and the
number of successful RRC connection setups, see Description.
Table 1 RRC Setup Success Rate (NB-IoT)
Name RRC Setup Success Rate (NB-IoT)
Object NB-IoT cell or radio network
(RRCConnectionSuccess/RRCConnectionAttempt) x 100%
Associated RRC Setup Success Rate (NB-IoT) =

Counters [L.NB.RRC.ConnReq.Succ/(L.NB.RRC.ConnReq.Att +
L.NB.RRC.ResumeFail.RRCSetup)] x 100%
Unit Percentage (%)
Note None
Parent Topic: NB-IoT Accessibility KPIs


Next topic >
8.4.3.10.2 RRC Resume Success Rate

(NB-IoT)
Description
When there are UP-mode UEs in a commercial NB-IoT network, this KPI is used to
evaluate the performance related to RRC connection resumes for such UEs in the NB-
IoT network. In accordance with [7], a UE initiates an RRC connection resume request
with a cause value such as emergency, highPriorityAccess, mt-Access, mo-Signalling,
mo-Data, delayTolerantAccess, and mo-VoiceCall. The cause value is determined by
the upper layer.
The KPI is measured by the eNodeB when UEs initiate RRC connection resume
procedures. As shown in Figure 1, the number of RRC connection resume requests is
counted by the eNodeB at point A when the eNodeB receives RRC Connection Resume
Request messages from UEs. The number of successful RRC connection resumes is
counted at point C.
Figure 1 Measurement points for RRC connection resume
Definition
The RRC Resume Success Rate (NB-IoT) KPI is defined in Table 1. For details about
how to measure counters related to the number of RRC connection resume requests and
the number of successful RRC connection resumes, see Description.
Table 1 RRC Resume Success Rate (NB-IoT)
Name RRC Resume Success Rate (NB-IoT)
(RRCConnectionResumeComplete/RRCConnectionResumeRequest)
x 100%
Associated RRC Resume Success Rate (NB-IoT) =

Counters (L.NB.RRC.ResumeReq.Succ/L.NB.RRC.ResumeReq.Att) x 100%
Unit Percentage (%)
Note None
Parent Topic: NB-IoT Accessibility KPIs


< Previous topic
8.4.3.11 NB-IoT Retainability KPIs

Retainability KPIs indicate the network's capability to retain services requested by a
user for a desired duration once the user is connected to the services. Retainability KPIs
are important in evaluating whether the system can maintain a certain level of QoS.
Service Drop Rate (NB-IoT)


8.4.3.11.1 Service Drop Rate (NB-IoT)

Description
This KPI indicates the service drop rate of all services in an NB-IoT network. When
UEs perform transmission in CP mode for a service, the service drop rate of such
services is evaluated based on abnormal UE context releases. When UEs perform
transmission in UP mode for a service, the service drop rate of such services is
evaluated based on abnormal E-RAB releases. The KPI considers both cases. For details
about its calculation formula, see Table 1.
Definition
The Service Drop Rate (NB-IoT) KPI is defined in Table 1.
Table 1 Service Drop Rate (NB-IoT)
Name Service Drop Rate (NB-IoT)
Formula Service_DR = [AbnormalRelease/(NormalRelease +

AbnormalRelease)] x 100%
Associated Service Drop Rate (NB-IoT) = [(L.NB.UECNTX.AbnormRel –

Counters L.NB.UECNTX.AbnormRel.Up + L.NB.E-
RAB.AbnormRel)/(L.NB.UECNTX.NormRel – L.NB.UECNTX.NormRel.Up +
L.NB.E-RAB.NormRel + L.NB.UECNTX.AbnormRel –
L.NB.UECNTX.AbNormRel.Up + L.NB.E-RAB.AbNormRel)] × 100%
Unit Percentage (%)
Note None
Parent Topic: NB-IoT Retainability KPIs

8.4.3.12 NB-IoT Service Integrity KPIs

The NB-IoT service integrity KPIs indicate service quality provided for UEs in an NB-
IoT network.
Downlink SRB Packet Loss Rate (NB-IoT)
Downlink Residual Block Error Rate (NB-IoT)
Uplink Residual Block Error Rate (NB-IoT)
Downlink Packet Loss Rate (NB-IoT)
Uplink DRB Packet Loss Rate (NB-IoT)


8.4.3.12.1 Downlink SRB Packet Loss

Rate (NB-IoT)
Description
This KPI indicates the downlink SRB packet loss rate of an NB-IoT cell. This KPI is
calculated based on the number of lost downlink SRB packets in an NB-IoT cell and the
total number of transmitted downlink SRB packets in the cell.
Definition
The Downlink SRB Packet Loss Rate (NB-IoT) KPI is defined in Table 1.
Table 1 Downlink SRB Packet Loss Rate (NB-IoT)
Name Downlink SRB Packet Loss Rate (NB-IoT)
Formula DLPacketLossRate (SRB) =

Associated Downlink SRB Packet Loss Rate (NB-IoT) =

Counters (L.NB.Thrp.Pkts.DL.SRB.Loss/ L.NB.Thrp.Pkts.DL.SRB.Tot) x 100%
Unit Percentage (%)

Note None
Parent Topic: NB-IoT Service Integrity KPIs


Next topic >
8.4.3.12.2 Downlink Residual Block

Error Rate (NB-IoT)
Description
This KPI indicates the downlink residual block error rate of an NB-IoT cell. This KPI is
calculated based on the number of TBs that failed to be retransmitted on the DL-SCH
after the maximum number of retransmissions is reached in the NB-IoT cell and the
number of TBs that are initially transmitted on the DL-SCH in the NB-IoT cell.
Definition
The Downlink Residual Block Error Rate (NB-IoT) KPI is defined in Table 1.
Table 1 Downlink Residual Block Error Rate (NB-IoT)
Name Downlink Residual Block Error Rate (NB-IoT)
Formula Downlink Residual Block Error Rate (NB-IoT) =

NumOfDlschErrTB/NumberOfDlschTransmittedTB
Associated Downlink Residual Block Error Rate (NB-IoT) =

Counters (L.NB.Traffic.DL.SCH.ErrTB.Rbler/L.NB.Traffic.DL.SCH.TB) x 100%
Unit Percentage (%)
Note None


8.4.3.12.3 Uplink Residual Block Error
Rate (NB-IoT)
Description
This KPI indicates the uplink residual block error rate of an NB-IoT cell. This KPI is
calculated based on the number of TBs that failed to be retransmitted on the UL-SCH
after the maximum number of retransmissions is reached in the NB-IoT cell and the
number of TBs that are initially transmitted on the UL-SCH in the NB-IoT cell.
Definition
The Uplink Residual Block Error Rate (NB-IoT) KPI is defined in Table 1.
Table 1 Uplink Residual Block Error Rate (NB-IoT)
Name Uplink Residual Block Error Rate (NB-IoT)
Formula Uplink Residual Block Error Rate (NB-IoT) =

NumOfUlschErrTB/NumberOfUlschTransmittedTB
Associated Uplink Residual Block Error Rate (NB-IoT) =

Counters (L.NB.Traffic.UL.SCH.ErrTB.Rbler/L.NB.Traffic.UL.SCH.TB) x 100%
Unit Percentage (%)
Note None



(NB-IoT)
Description
When there are both CP-mode and UP-mode UEs in a commercial network, this KPI is
used to evaluate the performance related to downlink packet loss in an NB-IoT cell. The
KPI considers both the CP-mode downlink SRB packet loss and the UP-mode downlink
DRB packet loss.
Definition
The Downlink Packet Loss Rate (NB-IoT) KPI is defined in Table 1.
Table 1 Downlink Packet Loss Rate (NB-IoT)
Name Downlink Packet Loss Rate (NB-IoT)
Formula DLPacketLossRate (NB-IoT) =

Associated Downlink Packet Loss Rate (NB-IoT) = (L.NB.Thrp.Pkts.DL.SRB.Loss +

Counters L.NB.Traffic.PktUuLoss.DL.DRB.Loss)/(L.NB.Thrp.Pkts.DL.SRB.Tot +
L.NB.Traffic.PktUuLoss.DL.DRB.Tot) x 100%
Unit Percentage (%)
Note None


8.4.3.12.5 Uplink DRB Packet Loss Rate

(NB-IoT)
Description
When there are UP-mode UEs in an NB-IoT network, this KPI can be used to evaluate
the performance related to uplink packet loss for the UP-mode UEs in the network. The
KPI is calculated based on the total number of lost PDCP SDUs for services carried on
DRBs in the uplink in an NB-IoT cell and the total number of PDCP SDUs expected to
be received in the uplink in the NB-IoT cell.
Definition
The Uplink DRB Packet Loss Rate (NB-IoT) KPI is defined in Table 1.
Table 1 Uplink DRB Packet Loss Rate (NB-IoT)
Name Uplink DRB Packet Loss Rate (NB-IoT)
Formula ULPacketLossRate (DRB) =

Associated Uplink DRB Packet Loss Rate (NB-IoT) =

Counters (L.NB.Traffic.PktLoss.UL.DRB.Loss/L.NB.Traffic.PktLoss.UL.DRB.Tot) x 100%
Unit Percentage (%)
Note None


< Previous topic
8.4.3.13 NB-IoT Availability KPIs

A cell is available when the eNodeB can provide EPS bearer services. Availability in a
cell can be measured when a variety of hardware or software faults occur in the cell.
Radio Network Availability Rate (NB-IoT)


8.4.3.13.1 Radio Network Availability

Rate (NB-IoT)
Description
This KPI indicates the percentage of time when a radio network is available. The KPI is
used to evaluate the working status of NB-IoT cells.
Definition
The Radio Network Availability Rate (NB-IoT) KPI is defined in Table 1. The KPI is
calculated based on all NB-IoT cells on the radio network.
Table 1 Radio Network Availability Rate (NB-IoT)
Name Radio Network Availability Rate (NB-IoT)
Object Radio network
Formula RAN_Avail_Rate =
[CellAvailTime/(TheTotalNumberOfCellsInCluster x SP x 60)] x
100%
Associated Radio Network Availability Rate (NB-IoT) =

Counters [L.NB.Cell.Avail.Dur/(Number of NB-IoT cells x SP x 60)] x 100%
Unit Percentage (%)
Note SP indicates the reporting period for counters in minutes.
Parent Topic: NB-IoT Availability KPIs

8.4.3.14 NSA DC Accessibility KPIs

NSA DC Accessibility KPIs are used to evaluate the SgNB addition success rate in
NSA DC scenarios.
SgNB Addition Success Rate


8.4.3.14.1 SgNB Addition Success Rate

Description
This KPI indicates the SgNB addition success rate in NSA DC scenarios. For details
about SgNB addition procedures, see 3GPP TS 37.340. The number of SgNB addition
attempts is measured at point A in Figure 1, and the number of successful SgNB
additions is measured at point B in Figure 1.
Figure 1 Measurement points of SgNB addition in NSA DC scenarios
Definition
The SgNB Addition Success Rate KPI is defined in Table 1.
Table 1 SgNB Addition Success Rate
Name SgNB Addition Success Rate
Formula SgNBAdd_SR = (SgNBAdditionSuccess/SgNBAdditionAttempt) x

100%
Associated SgNB Addition Success Rate =

Counters (L.NsaDc.SgNB.Add.Succ/L.NsaDc.SgNB.Add.Att) x 100%
Unit Percentage (%)
Note None
Parent Topic: NSA DC Accessibility KPIs

8.4.3.15 References
1. 3GPP, TS36.331 v10.9.0 (March 2013), "Evolved Universal Terrestrial Radio Access
(E-UTRA), Radio Resource Control (RRC); Protocol Specification, (Release 10)"
2. 3GPP, TS36.300 v8.6.0 (September 2008), "Evolved Universal Terrestrial Radio
Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-
UTRAN); Overall description; Stage 2 (Release 8)"
3. 3GPP, TS36.413 v8.3.0 (September 2008), "Evolved Universal Terrestrial Radio
Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-
UTRAN); S1 Application Protocol (S1AP) (Release 8)"
4. 3GPP, TS23.401 v8.4.0 (December 2008), "Technical Specification Group Services
and System Aspects; General Packet Radio Service (GPRS) enhancements for Evolved
Universal Terrestrial Radio Access Network (E-UTRAN) access (Release 8)"
5. 3GPP, TS23.203 v8.3.1 (September 2008), "Technical Specification Group Services
and System Aspects: Policy and charging control architecture (Release 8)"
6. eNodeB Performance Counter Reference
7. 3GPP TS 36.331 V13.2.0, "3rd Generation Partnership Project; Technical
Specification Group Radio Access Network; Evolved Universal Terrestrial Radio
Access (E-UTRA); Radio Resource Control (RRC); Protocol specification (Release
13)"
8. 3GPP TS 36.331 v13.3.0, "3rd Generation Partnership Project; Technical
Specification Group Radio Access Network; Evolved Universal Terrestrial Radio
Access (E-UTRA); Radio Resource Control (RRC); Protocol specification (Release
13)"

< Previous topic

LTE Service KPI

Uploaded by

Copyright:

Available Formats

LTE Service KPI

Uploaded by

Document Information

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

LTE Service KPI

Uploaded by

Copyright:

Available Formats

eRAN KPI Reference

8.4.3 eRAN KPI Reference

Product Name Solution Version Product Version

BTS3900  SRAN15.1 V100R015C10

eRAN KPI Reference Summary

Retainability KPIs indicate the network's capability to retain services requested

Mobility KPIs are used to evaluate E-UTRAN mobility performance, which is

Copyright © Huawei Technologies Co., Ltd.

8.4.3.2 Changes in eRAN KPI Reference

 Intra-RAT Handover Out Success Rate (NSA DC)

 User Downlink Split Average Throughput (NSA DC)

 User Uplink Split Average Throughput (NSA DC)

 Downlink Resource Block Utilizing Rate (NSA DC)

 Uplink Resource Block Utilizing Rate (NSA DC)

 NSA DC Accessibility KPIs

Topic Change Description

Availability KPIs Changed the availability KPI from Radio

Parent Topic: eRAN KPI Reference

Copyright © Huawei Technologies Co., Ltd.

8.4.3.3 Accessibility KPIs

Parent Topic: eRAN KPI Reference

Copyright © Huawei Technologies Co., Ltd.

8.4.3.3.1 RRC Setup Success Rate

Table 1 RRC Setup Success Rate

Name RRC Setup Success Rate

Object Cell or radio network

Formula RRCS_SR = (RRCConnectionSuccess/RRCConnectionAttempt) x

Associated RRC Setup Success Rate = (L.RRC.ConnReq.Succ/L.RRC.ConnReq.Att) x

Unit Percentage (%)

Parent Topic: Accessibility KPIs

Copyright © Huawei Technologies Co., Ltd.

8.4.3.3.2 RRC Setup Success Rate

Table 1 RRC Setup Success Rate (Service)

Name RRC Setup Success Rate (Service)

Object Cell or radio network

Associated RRC Setup Success Rate (Service) = [(L.RRC.ConnReq.Succ.Emc +

Unit Percentage (%)

Parent Topic: Accessibility KPIs

Copyright © Huawei Technologies Co., Ltd.

8.4.3.3.3 RRC Setup Success Rate

Table 1 RRC Setup Success Rate (Signaling)

Name RRC Setup Success Rate (Signaling)

Object Cell or radio network

Associated RRC Setup Success Rate (Signaling) =

Unit Percentage (%)

Parent Topic: Accessibility KPIs

Copyright © Huawei Technologies Co., Ltd.

8.4.3.3.4 S1SIG Connection Setup

Table 1 S1SIG Connection Setup Success Rate

Name S1SIG Connection Setup Success Rate

Object Cell or radio network

Associated S1SIG Connection Setup Success Rate =

Unit Percentage (%)

Parent Topic: Accessibility KPIs

Copyright © Huawei Technologies Co., Ltd.

8.4.3.3.5 E-RAB Setup Success Rate

Table 1 E-RAB Setup Success Rate (VoIP)

Name E-RAB Setup Success Rate (VoIP)

Object Cell or radio network

Associated E-RAB Setup Success Rate (VoIP) = [L.E-RAB.SuccEst.QCI.1/(L.E-