01-LTE KPI Introduction

LTE eRAN8.
1 KPI Introduction
Confidential Information of Huawei. No Spreading Without Permission

LTE eRAN8.1 KPI Introduction



The traffic measurement data and drive test data are the objective basis of the network
optimization, while the human perception is the subjective basis. It is necessary to trace
and analyze signalling messages to locate problems before these problems are solved. It is
obvious that the traffic measurement data provide a very important method to analyze the
network performance. Especially when there is traffic in the network, the traffic
measurement data provide important references and guide for the network optimization.
The integrity and accuracy of the measurement items and the convenience of operations
will directly affect the efficiency of network optimization. Meanwhile, the quality of
measurement items is also a very important factor to measure the effect of network
optimization.
On the other hand, network operators set much store by the traffic measurement data.
The boss of network operators usually learns and judges the running status of networks
according to the visual data obtained from traffic measurement. These visual traffic
measurement data also provide an important basis for the future network capacity
expansion.

Each measurement result is related to a specific measurement object.

Counters are organized by Measurement Unit/Family.
Function set. A function set consists of several function subsets that are related to a
specific system function. Function sets are also referred to as measurement sets. If a
function set belongs to NEs of different types, this function set is referred to as a shared
function set.
Function subset. A function subset consists of several measurement counters that are
related to a certain system function. Function subsets are also referred to as measurement
units. If a function subset belongs to NEs of different types, this function subset is referred
to as a shared function subset.
Each function subset has a unique ID in the system. You can view the ID of a function
subset in the text box that is displayed when resting the pointer on the function subset
(button).
Measurement counter. If a measurement counter belongs to NEs of different types, this
measurement counter is referred to as a shared measurement counter.


KPI name: It is a descriptive name of the KPI.

Description: It provides a brief overview of the KPI.
Measurement scope: It specifies the KPI monitoring scope. In general, the measurement is
made in terms of cells. The KPI value reflects the performance in a cell or a cluster. The
associated counters can be obtained from cell statistics. In this document, cluster indicates
a group of cells selected by user.
Formula: It is used to calculate the KPI. Generally the formula consists of several counters
that are specified in other sub-clauses.
Associated counters: It contains counters used in the formula.

eNodeB supports two meaurement report:

Default period: 60 min
Minimal period: 15 min



The RRC connection setup procedure is triggered by various different causes as identified
by the establishmentCause field in RRCConnectionRequest message: emergency,
highPriorityAccess, mt (Mobile terminating)-Access, mo (Mobile Originating)-Signaling, and
mo-Data. The UE sets the establishmentCause in accordance with the information received
from upper layers. Causes except mo-signaling are categorized as service-related ones. The
mo-signaling cause is a signaling-related cause.
Establishment Cause
Emergency
TheEmergency cause value is used if the EPS Attach Type within the
Attach Request message is set to EPS Emergency Attach. The Emergency
cause value can also be used if the higher layers within the UE indicate the
requirement to establish emergency bearer services, even when the EPS
Attach Type is not set to EPS Emergency Attach.
High Priority Access
For these NAS procedures initiated by UEs of access class 12, 13 or 14 in
their home country, the RRC establishment cause will be set to "High
priority access AC 11 15". For this purpose the home country is defined
as the country of the MCC part of the IMSI, see 3GPP TS 22.011 [1A].
For these NAS procedures initiated by UE of access class 11 or 15 in their
HPLMN (if the EHPLMN list is not present or is empty) or EHPLMN (if the
EHPLMN list is present), the RRC establishment cause will be set to "High
priority access AC 11 15.
This KPI evaluates the RRC setup success rate in a cell or cluster involved.
According to Reference, the RRC connection setup procedure is triggered by various
different causes as identified by the establishmentCause field in RRCConnectionRequest
message: emergency, highPriorityAccess, mt-Access (Mobile terminating), mo-Signaling
(Mobile Originating), and mo-Data. The UE sets the establishmentCause in accordance
with the information received from upper layers. Causes except mo-signaling are
categorized as service-related ones. The mo-signaling cause is a signaling-related cause.
MO-signaling refers to RRC connection setup request result from Attach,Tracking Area
Update,Detach

The counters measure the number of RRC connection setup requests for different causes in
a cell. The RRC Connection Request message is the first RRC signaling message sent from
the UE to the eNodeB. The corresponding counter are incremented by 1 each time the
eNodeB receives an RRC Connection Request message from the UE. Note: The
L.RRC.ConnReq.Att counter is incremented by 1 when the eNodeB receives the message
for the first time. The counter will not be incremented repeatedly, if the eNodeB receives
the message for multiple times.
Counter Name Description

Counter ID
1526726658 L.RRC.ConnReq.Att Number of RRC Connection Request

messages received from the UE in a cell,
excluding the number of retransmitted
messages
1526728217 L.RRC.ConnReq.Att.Emc Number of RRC Connection Request
messages received from the UE for the
emergency call cause in a cell
1526728218 L.RRC.ConnReq.Att.HighPri Number of RRC Connection Request
highPriorityAccess cause in a cell
1526728219 L.RRC.ConnReq.Att.Mt Number of RRC Connection Request
messages received from the UE for the mt-
Access cause in a cell

Counter ID Counter Name Description

1526728220 L.RRC.ConnReq.Att.MoSig Number of RRC Connection Request
mo-Signaling cause in a cell
1526728221 L.RRC.ConnReq.Att.MoData Number of RRC Connection Request
mo-Data cause in a cell
1526728357 L.RRC.ConnReq.Att.DelayTol Number of RRC connection setup attempts
with a cause value of delayTolerantAccess-
v1020
Number of RRC Connection Setup Attempts in a Cell:
1526728216 L.RRC.ConnSetup Number of RRC Connection Setup messages

responses to UE in a cell
The counter measures the number of RRC connection setup attempts in a cell. That is, the
counter measures the number of times that the eNodeB sends an RRC Connection Setup
message to the UE after receiving an RRC Connection Request message from the UE. The
RRC Connection Setup message is an RRC signaling message sent from the eNodeB to the
UE. The message is used to inform the UE of the related configuration information and the
result of the RRC connection setup. the corresponding counter is incremented by 1 each
time the eNodeB sends an RRC Connection Setup message to the UE after receiving an
RRC Connection Request message from the UE.

Number of Successful RRC Connection Setups in a Cell
1526726659 L.RRC.ConnReq.Succ Number of RRC Connection Setup

Complete messages received from the UE in
a cell
1526728222 L.RRC.ConnReq.Succ.Emc Number of RRC Connection Setup
Complete messages received from the UE
for the emergency call cause in a cell
1526728223 L.RRC.ConnReq.Succ.HighPri Number of RRC Connection Setup
for the highPriorityAccess cause in a cell
1526728224 L.RRC.ConnReq.Succ.Mt Number of RRC Connection Setup
for the mt-Access cause in a cell
1526728225 L.RRC.ConnReq.Succ.MoSig Number of RRC Connection Setup
for the mo-Singnalling cause in a cell
1526728226 L.RRC.ConnReq.Succ.MoData Number of RRC Connection Setup
for the mo-Data cause in a cell
1526728358 L.RRC.ConnReq.Succ.DelayTol Number of successful RRC connection setups
with a cause value of delayTolerantAccess-
v1020
The counters measure the number of successful RRC connection setups for different causes
in a cell. They refer to the number of RRC Connection Setup Complete messages received
by the eNodeB from the UE. The RRC Connection Setup Complete message is an RRC
signaling message sent from the UE to the eNodeB.
The message is used to inform the eNodeB that the RRC connection setup is completed
and informs the eNodeB of the carried NAS signaling information and the information
about MME and PLMN selections. the corresponding counter is incremented by 1 each
time the eNodeB receives an RRC Connection Setup Complete message from the UE

Number of RRC Connection Setup Failures for Different Causes in a Cell

1526727083 L.RRC.SetupFail.ResFail Number of RRC connection setup failures due
to resource allocation failures
1526727084 L.RRC.SetupFail.NoReply Number of RRC connection setup failures due
to no responses from the UE
1526728269 L.RRC.SetupFail.Rej Number of RRC Connection Reject messages
sent to the UE in a cell
1526728485 L.RRC.SetupFail.ResFail.SRS Number of RRC connection setup failures due to
SRS resource allocation failure
1526728486 L.RRC.SetupFail.ResFail.PUCCH Number of RRC connection setup failures due to
PUCCH resource allocation failure
1526728489 L.RRC.ConnReq.Msg.disc.FlowCtrl Number of times the RRC Connection Request
message is discarded due to flow control
1526729949 L.RRC.SetupFail.ResFail.UserSpec Number of RRC connection setup failures
because of limitation of UE number specification
1526732044 L.RRC.SetupFail.Rej.MMEOverload Number of times the eNodeB sends an RRC
Connection Reject message to the UE due to
MME overload
1526732920 L.RRC.SetupFail.Rej.Other Number of RRC connection setup requests
rejected due to other causes
1526732921 L.RRC.SetupFail.ResFail.Other Number of RRC connection setup failures due to
other resource allocation failure
As shown at point A in Figure 1, the L.RRC.SetupFail.ResFail, L.RRC.SetupFail.ResFail.SRS,
L.RRC.SetupFail.ResFail.PUCCH, or L.RRC.SetupFail.ResFail.UserSpec counter is incremented
by 1 each time the eNodeB sends an RRC Connection Reject message to a UE because of
resource allocation failure, SRS resource allocation failure, PUCCH resource allocation
failure, or UE number specification limitation, respectively, after receiving an RRC
Connection Request message from the UE.
As shown at point A in Figure 2, the L.RRC.SetupFail.NoReply counter is incremented by 1
each time the eNodeB does not receive an RRC Connection Setup Complete message from
the UE within the specified time. Before that, the eNodeB has sent an RRC Connection
Setup message to the UE after receiving an RRC Connection Request message from the UE.
As shown at point A in Figure 1, the L.RRC.SetupFail.Rej counter is incremented by 1 each
time the eNodeB sends an RRC Connection Reject message to the UE after receiving an
RRC Connection Request message from the UE.
As shown at point A in Figure 1, the L.RRC.SetupFail.Rej.FlowCtrl counter is incremented
by 1 each time the eNodeB sends an RRC Connection Reject message to the UE due to
flow control after receiving an RRC Connection Request message from the UE.
As shown at point A in Figure 1, the L.RRC.SetupFail.Rej.MMEOverload counter is
incremented by 1 each time the eNodeB sends an RRC Connection Reject message to the
UE because the MME is overloaded or no MME is available for other reasons after receiving
an RRC Connection Request message from the UE.
As shown at point A in Figure 1, the L.RRC.SetupFail.Rej.Other counter is incremented by 1
when the eNodeB sends an RRC Connection Reject message to a UE after receiving an RRC
Connection Request message from the UE and the RRC Connection Reject message has a
cause value other than resource allocation failure, flow control, or MME overloaded.
As shown at point A in Figure 1, the L.RRC.SetupFail.ResFail.Other counter is incremented
by 1 when the eNodeB sends an RRC Connection Reject message to a UE after receiving an
RRC Connection Request message from the UE and the RRC Connection Reject message
has a cause value of resource allocation failure and a sub-cause-value other than SRS
resource allocation failure, PUCCH resource allocation failure, or UE number exceeding
specification.
As shown at point A in Figure 3, the L.RRC.ConnReq.Msg.disc.FlowCtrl counter is
incremented by 1 each time the eNodeB discards an RRC Connection Request message
(including retransmissions) from a UE due to flow control.

The purpose of this procedure is to re-establish the RRC connection, which involves the
resumption of the Signaling Bearer 1 operation and the re-activation of security.
Possible Reestablishment Causes in the RRC Connection Reestablishment Request Message:
Handover Failure, Reconfiguration Failure, Other Failure
Number of RRC Connection Reestablishment Requests in a Cell:

1526727085 L.RRC.ReEst.Att Number of RRC connection reestablishment
requests
1526727087 L.RRC.ReEst.ReconfFail.Att Number of RRC connection reestablishment

requests due to a failed reconfiguration
1526727090 L.RRC.ReEst.HoFail.Att Number of RRC connection reestablishment

requests due to a failed handover
1526730536 L.RRC.ReEst.NonSrccell.Att Number of RRC connection reestablishment

requests to another cell

The counters measure the number of RRC connection reestablishment requests for
different causes in a cell. The RRC Connection Reestablishment Request message is an RRC
signaling message sent by the UE. The message is used to recover the RRC signaling
connection. The corresponding counter is incremented by 1 each time the eNodeB receives
an RRC Connection Reestablishment Request message from the UE. Note: The
L.RRC.ConnReq.Att counter is incremented by 1 when the eNodeB receives the message
for the first time. The counter will not be incremented repeatedly, if the eNodeB receives
the message for multiple times.
Number of Successful RRC Connection Reestablishments in a Cell:

1526727086 L.RRC.ReEst.Succ Number of successful RRC connection
reestablishments
1526727088 L.RRC.ReEst.ReconfFail.Succ Number of successful RRC connection
reestablishments due to a failed
reconfiguration
1526727091 L.RRC.ReEst.HoFail.Succ Number of successful RRC connection
reestablishments due to a failed handover
1526730537 L.RRC.ReEst.NonSrccell.Succ Number of successful RRC connection

reestablishment times to another cell
The counters measure the number of successful RRC connection reestablishments for
different causes in a cell. The RRC Connection Reestablishment Complete message is an
RRC signaling message sent from the UE to the eNodeB. The message is used to inform the
eNodeB that the RRC connection reestablishment is completed. The corresponding counter
is incremented by 1 each time the eNodeB receives an RRC Connection Reestablishment
Complete message from the UE.

Number of RRC Connection Reestablishment Failures for Different Causes in a Cell

1526737854 L.RRC.ReEstFail.Disc.FlowCtrl Number of times the RRC Connection Reestablishment
Request messages are discarded due to flow control
1526727089 L.RRC.ReEst.ReconfFail.Rej Number of RRC connection reestablishment failures
due to reconfiguration failures
1526727092 L.RRC.ReEst.HoFail.Rej Number of RRC connection reestablishment failures
due to failed handovers
1526727093 L.RRC.ReEstFail.ResFail Number of RRC connection reestablishment failures
due to failed resource allocations
1526727094 L.RRC.ReEstFail.NoReply Number of RRC connection reestablishment failures
due to no responses from the UE
1526728270 L.RRC.ReEstFail.Rej Total number of RRC connection reestablishment
rejections
1526728271 L.RRC.ReEstFail.NoCntx Number of RRC connection reestablishment failures
due to unavailability of UE contexts
1526730857 L.RRC.ReEstFail.NoCntx.PreProc Number of RRC connection reestablishment failures
Fail due to UE context unavailability caused by the pre-
processing failure
The counters measure the number of RRC connection reestablishment failures for different causes in a cell. The
RRC Connection Reestablishment Reject message is an RRC signaling message sent from the eNodeB to the UE.
The message is used to inform the UE that the reestablishment is rejected by the eNodeB. The corresponding
counter is incremented by 1 each time the eNodeB sends an RRC Connection Reestablishment Reject message
after receiving an RRC Connection Reestablishment Request message from the UE.

As shown in point A in Figure 1, the corresponding counter is incremented each time the
eNodeB sends an RRC Connection Reestablishment Reject message after receiving an RRC
Connection Reestablishment Request message from the UE. The counters are measured as
follows:
The L.RRC.ReEstFail.Rej counter is incremented by 1 each time the eNodeB sends
the RRC connection Reestablishment Reject message
The L.RRC.ReEst.ReconfFail.Rej counter is incremented by 1 each time the eNodeB
receives an RRC Connection Reestablishment Request message from the UE and
the Reestablishment Cause information element of the message
is reconfigurationFailure.
The L.RRC.ReEst.HoFail.Rej counter is incremented by 1 each time the eNodeB
receives an RRC Connection Reestablishment Request message from the UE and
the Reestablishment Cause information element of the message is handoverFailure.
The L.RRC.ReEstFail.ResFail counter is incremented by 1 each time the RRC
connection reestablishment fails due to a failed resource allocation.
The L.RRC.ReEstFail.NoCntx counter is incremented by 1 each time the RRC
connection reestablishment fails because UE contexts are unavailable.
As shown in point A in Figure 2, the L.RRC.ReEstFail.NoReply counter is incremented by 1
each time the eNodeB does not receive an RRC Connection Reestablishment Complete
message from the UE within the specified time.
As shown at point A in Figure 3, the L.RRC.ReEstFail.Disc.FlowCtrl counter is incremented
by 1 each time the cell discards an RRC Connection Reestablishment Request message
from a UE because of flow control


The characteristics describe the packet forwarding treatment that an SDF aggregate
receives edge-to-edge between the UE and the PCEF (see figure 6.1.7-1) in terms of the
following performance characteristics:
1 Resource Type (GBR or Non-GBR);
2 Priority;
3 Packet Delay Budget;
4 Packet Error Loss Rate.

An E-RAB is the access layer bearer for carrying service data of users. The E-RAB setup
success rate in a cell directly represents the capability of the cell to provide E-RAB
connection setups for users

The E-RAB is part of the Evolved Packet Service (EPS) bearer. According to 3GPP TS 23.401,
an E-RAB is one or more Service Data Flows between UE and an EPC.
The E-RAB identity remains unique for the UE even if the UE-associated logical S1-
connection (S1 bearer) is released during periods of user inactivity.
UE-triggered E-RAB setup is triggered by the radio bearer setup. Initial Context Setup
Request messages are exchanged between the eNodeB and the MME. If the E-RAB Setup
Request message or Initial Context Setup Request message requires multiple E-RAB setups
at the same time, specific counters are incremented for each E-RAB.


LTE-SAE QoS Class Identifier
Packet
Packet
QCI Type Priority Delay Example Service
Error Rate
Budget (ms)
-2
1 GBR 2 100 10 Conversational Voice
-3
2 GBR 4 150 10 Conversational Video
-3
3 GBR 3 50 10 Real Time Gaming
-6
4 GBR 5 300 10 Non-Conversational Voice
Non- -6
5 1 100 10 IMS Signaling
GBR
Non- -6
6 6 300 10 Video, TCP Based
GBR
Non- -3 Voice, Video, Interactive
7 7 100 10
GBR Gaming
Non- -6
GBR
Non- -6
GBR

Number of Initial E-RAB Setup Attempts in a Cell
1526728192 L.E-RAB.InitAttEst.QCI.1 Number of initial E-RAB setup attempts for the

service with QCI of 1 in a cell
......... .................. ..........................

The counters measure the number of initial E-RAB setup attempts for each service with a
different QCI ranging from 1 to 9 in a cell. The corresponding counter is incremented by 1
each time the eNodeB receives an INITIAL CONTEXT SETUP REQUEST message from the
MME.

Number of Successful Initial E-RAB Setups in a Cell

1526728193 L.E-RAB.InitSuccEst.QCI.1 Number of successful initial E-RAB setups for
the service with QCI of 1 in a cell
The counters measures the number of successful initial E-RAB setups for each service with
a different QCI ranging from 1 to 9 in a cell. the corresponding counter is incremented by
1 each time the eNodeB sends an INITIAL CONTEXT SETUP RESPONSE message to the
MME. If the INITIAL CONTEXT SETUP RESPONSE message contains multiple successful E-
RAB setups at the same time, the corresponding counter is incremented by 1 according to
the QCI of each service.

Number of E-RAB Setup Attempts in a Cell

1526726668 L.E-RAB.AttEst.QCI.1 Number of E-RAB setup attempts for the service
with QCI of 1 in a cell
... ...
These counters measure the number of E-RAB setup attempts for each service with a
specific QCI ranging from 1 to 9 in a cell. The corresponding counter is incremented by 1
each time the eNodeB receives an E-RAB SETUP REQUEST message or an INITIAL CONTEXT
SETUP REQUEST message from the MME.

Number of Successful E-RAB Setups in a Cell

1526726669 L.E-RAB.SuccEst.QCI.1 Number of successful E-RAB setups for the
........... ..............
The counters measures the number of successful E-RAB setups for each service with a
different QCI ranging from 1 to 9 in a cell. The corresponding counter is incremented by 1
each time the eNodeB sends an E-RAB SETUP RESPONSE message or an INITIAL CONTEXT
SETUP RESPONSE message to the MME. If the E-RAB SETUP RESPONSE message or INITIAL
CONTEXT SETUP RESPONSE message contains multiple successful E-RAB setups at the
same time, the corresponding counter is incremented by 1 according to the QCI of each
service.
Total Number of Successful E-RAB Setups

1526727544 L.E-RAB.SuccEst Total number of successful E-RAB setup
procedures initiated by UEs
The counter measures the total number of successful E-RAB setups in the eNodeB cell. the
counter is incremented by 1 each time the eNodeB sends an E-RAB SETUP RESPONSE
message or an INITIAL CONTEXT SETUP RESPONSE message to the MME. If the E-RAB
SETUP RESPONSE message or INITIAL CONTEXT SETUP RESPONSE message contains
multiple successful E-RAB setups at the same time, the counter is incremented repeatedly.
Total Number of E-RAB Setup Attempts

1526727545 L.E-RAB.AttEst Total number of attempts by UEs to initiate E-
RAB setup procedures
This counter measures the total number of E-RAB setup attempts in the eNodeB cell. The
corresponding counter is incremented each time the eNodeB receives an E-RAB SETUP
REQUEST message or an INITIAL CONTEXT SETUP REQUEST message from the MME. If the
E-RAB SETUP REQUEST message or INITIAL CONTEXT SETUP REQUEST message requires
multiple E-RAB setups at the same time, the corresponding counter is incremented
repeatedly.


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, 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, 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.


This KPI can be used to evaluate the call setup success rate of all services including the
VoIP service in a cell or a cluster. This KPI is calculated based on the KPI of RRC Setup
Success Rate (Service) and the KPI of ERAB Setup Success Rate (All).

Number of UE-Specific Signaling Connection Setups over the S1 Interface

The counters measure the number of UE-specific signaling connection setups on
the S1 interface, that is, number of INITIAL UE MESSAGE messages sent from the
eNodeB to the MME and number of first S1 messages received from the MME. The
eNodeB transmits the UE-specific NAS layer data configuration to the MME
through the INITIAL UE MESSAGE. The MME sets up S1 signaling connections
based on NAS information in the message. The first S1 interface message received
from the MME may be the INITIAL CONTEXT SETUP REQUEST, DOWNLINK NAS
TRANSPORT, or UE CONTEXT RELEASE COMMAND message. If the message is
received, an S1 signaling connection is set up successfully.


Call Drop Rate(VoIP)

This KPI can be used to evaluate the call drop rate of the VoIP service in a cell or a
cluster. The call drop rate is calculated by monitoring the VoIP ERAB abnormal
release rate. Each E-RAB is associated with the QoS information.
E-RAB includes both the E-RAB radio bearer and corresponding S1 bearer. Any
abnormal release on either bearer causes call drop and therefore is counted into
the call drop rate. The abnormal release is identified by the Cause IE (Information
Element) defined in Reference.
Call Drop Rate(All)
This KPI can be used to evaluate the call drop rate of all services in a cell or a
cluster, including VoIP service.

Abnormal E-RAB releases can be classified into the following two scenarios:
Scenario 1: When the eNodeB sends an E-RAB Release Indication message to the MME,
the abnormal E-RAB release counter is incremented if the bearer to be released carries data
and the release cause is not "Normal Release", "Detach", "User Inactivity", "CS Fallback
triggered", "UE Not Available for PS Service", or "Inter-RAT Redirection".
Scenario 2: When the eNodeB sends a UE Context Release Request message to the MME,
the abnormal E-RAB release counter is incremented if the bearer to be released carries data
and the release cause is not "Normal Release", "Detach", "User Inactivity", "CS fallback
triggered", "UE Not Available For PS Service", "Inter-RAT redirection", "Time Critical
Handover", "Handover Cancelled".



Number of Normal E-RAB Releases in a Cell

1526726687 L.E-RAB.NormRel.QCI.1 Number of normal E-RAB releases for the service
The counters measure the number of normal E-RAB releases for each service with a
different QCI ranging from 1 to 9 in a cell.
As shown in point A in Figure 1, the corresponding counter is incremented by 1 each time
the eNodeB receives an E-RAB RELEASE COMMAND message from the MME and the
Release Cause information element is Normal Release, Detach, User Inactivity, or cs fallback
triggered. If the E-RAB RELEASE COMMAND message requires multiple E-RAB releases at
the same time, the corresponding counter is incremented by 1 according to the QCI of
each service.
As shown in point A in Figure 2, the eNodeB releases all E-RABs of the UE after receiving a
UE CONTEXT RELEASE COMMAND message from the MME. If the Release Cause
information element of the UE CONTEXT RELEASE COMMAND message is Normal Release,
Detach, User Inactivity, or cs fallback triggered, the corresponding counter is incremented
by 1 according to the QCI of each service.

Total Number of E-RAB Normal Releases

1526727547 L.E-RAB.NormRel Total number of normal E-RAB releases by
the eNodeB
This counter measures the total number of E-RAB normal releases in the eNodeB cell.
The corresponding counter is incremented by 1 each time the eNodeB receives an E-RAB
RELEASE COMMAND message from the MME and the Release Cause information element
is Normal Release, User Inactivity, Detach, or cs fallback triggered.
The eNodeB releases all E-RABs of the UE after receiving a UE CONTEXT RELEASE
COMMAND message from the MME. If the Release Cause information element of the UE
CONTEXT RELEASE COMMAND message is Normal Release, User Inactivity, Detach, or cs
fallback triggered, the counter is incremented by 1 repeatedly.
Number of normal E-RAB releases for PTT services
1526736858 L.E-RAB.NormRel.QCI.PTT Number of normal E-RAB releases for PTT
services in a cell

Number of Abnormal E-RAB Releases for Different Causes in a Cell

1526728282 L.E-RAB.AbnormRel.Radio Number of abnormal E-RAB releases due to
faults at the radio network layer
1526728283 L.E-RAB.AbnormRel.TNL Number of abnormal E-RAB releases due to
faults at the transport network layer
1526728284 L.E-RAB.AbnormRel.Cong Number of abnormal E-RAB releases due to
network congestion
1526728291 L.E-RAB.AbnormRel.HOFailure Number of abnormal E-RAB releases due to
handover failures
1526728292 L.E-RAB.AbnormRel.MME Number of abnormal E-RAB releases due to
faults in the EPC
The counters measure the number of abnormal E-RAB releases due to different causes in a
cell. An E-RAB is the access layer bearer for carrying service data of users. The E-RAB
release is a process of releasing the access layer bearer resources of users.


1526728940 L.E-RAB.AbnormRel.MMETot Total number of MME-triggered abnormal E-RAB
releases
1526729549 L.E- Number of abnormal releases of activated E-RABs
RAB.AbnormRel.Radio.SRBRes because the RLC PDU for an SRB has been
et retransmitted for the maximum number of times
RAB.AbnormRel.Radio.DRBRe because the RLC PDU for a DRB has been
set retransmitted for the maximum number of times
1526729551 L.E- Number of abnormal releases of activated E-RABs due
RAB.AbnormRel.Radio.ULSync to uplink resynchronization failures
Fail
RAB.AbnormRel.Radio.UuNoR because of no responses from the UE
eply
RAB.AbnormRel.MME.EUtran triggered by the MME with the release cause of
Gen Release due to E-UTRAN Generated Reason
RAB.AbnormRel.Cong.PreEmp because of radio resource preemption
RAB.AbnormRel.Cong.Load because of radio resource overload
RAB.AbnormRel.TNL.PreEmp because of transport resource preemption
1526729915 L.E-RAB.AbnormRel.TNL.Load Number of abnormal releases of activated E-RABs

because of transport resource overload
1526729916 L.E- Number of MME-triggered abnormal releases of E-

RAB.AbnormRel.MMETot.VoI RABs for voice services
P
1526729917 L.E- Number of abnormal releases of activated E-RABs for
RAB.AbnormRel.Radio.SRBRes voice services because the RLC PDU for an SRB has
et.VoIP been retransmitted for the maximum number of times
RAB.AbnormRel.Radio.NoRepl voice services because of no responses from the UE
y.VoIP
RAB.AbnormRel.Radio.ULSync voice services because of uplink resynchronization
Fail.VoIP failures
RAB.AbnormRel.MME.EUtran voice services triggered by the MME with the release
Gen.VoIP cause of Release due to E-UTRAN Generated Reason
RAB.AbnormRel.Radio.VoIP voice services because of faults at the radio network
layer


RAB.AbnormRel.HOFailure.Vo voice services because of handover failures
IP
RAB.AbnormRel.Cong.VoIP voice services because of radio network congestion
1526729924 L.E- Number of MME-triggered abnormal releases of
RAB.AbnormRel.MME.VoIP activated E-RABs for voice services
1526729925 L.E-RAB.AbnormRel.TNL.VoIP Number of abnormal releases of activated E-RABs for
voice services because of faults at the transport
network layer
RAB.AbnormRel.Cong.PreEmp voice services because of radio resource preemption
.VoIP
RAB.AbnormRel.Cong.Load.V voice services because of radio resource overload
oIP
RAB.AbnormRel.TNL.PreEmp. voice services because of transport resource
VoIP preemption
RAB.AbnormRel.TNL.Load.VoI voice services because of transport resource overload
P
RAB.AbnormRel.UlWeak.VoIP voice services because of uplink weak coverage

Release Cause information element is not Normal Release, Detach, User Inactivity,
Partial Handover, Handover triggered, successful handover, or cs fallback
each service.
information element of the UE CONTEXT RELEASE COMMAND message is not Normal
Release, Detach, User Inactivity, Partial Handover, Handover triggered, successful
handover, or cs fallback triggered, the corresponding counter is incremented by 1
according to the QCI of each service.

Number of Abnormal E-RAB Releases in a Cell

1526726686 L.E-RAB.AbnormRel.QCI.1 Number of abnormal E-RAB releases for the service

Release Cause information element is not Normal Release, Detach, User Inactivity,
Partial Handover, Handover triggered, successful handover, or cs fallback
each service.
information element of the UE CONTEXT RELEASE COMMAND message is not Normal
Release, Detach, User Inactivity, Partial Handover, Handover triggered, successful
handover, or cs fallback triggered, the corresponding counter is incremented by 1
according to the QCI of each service.

the eNodeB sends an E-RAB RELEASE INDICATION message to the MME and the Release
Cause information element is not Normal Release, Detach, User Inactivity, Partial Handover,
Handover triggered, successful handover, or cs fallback triggered. If the E-RAB RELEASE
INDICATION message requires multiple E-RAB releases at the same time, the corresponding
counter is incremented by 1 according to the QCI of each service.
As shown in point A in Figure 4, the eNodeB releases all E-RABs of the UE after sending a
UE CONTEXT RELEASE REQUEST message to the MME. If the Release Cause information
element of the UE CONTEXT RELEASE REQUEST message is not Normal Release, Detach,
User Inactivity, Partial Handover, Handover triggered, successful handover, or cs fallback
triggered, and in this case when the MME sends UE CONTEXT RELEASE COMMAND
message back to the eNodeB, this counter won`t be incremented repeatedly. If the UE
CONTEXT RELEASE REQUEST message requires multiple E-RAB releases at the same time,
the corresponding counter is incremented according to the QCI of each service.
Total Number of Abnormal E-RAB Releases

1526727546 L.E-RAB.AbnormRel Total number of abnormal E-RAB releases by the
eNodeB
This counter measures the total number of abnormal E-RAB releases in the eNodeB cell.
The corresponding counter is incremented each time the eNodeB receives an E-RAB
RELEASE COMMAND message from the MME and the Release Cause information element
is not Normal Release, User Inactivity, Partial Handover, Handover triggered, successful
handover, or cs fallback triggered. If the E-RAB RELEASE COMMAND message requires
multiple E-RAB releases at the same time, the corresponding counter is incremented
repeatedly.
The eNodeB releases all E-RABs of the UE after receiving a UE CONTEXT RELEASE
COMMAND message from the MME. If the Release Cause information element of the UE
CONTEXT RELEASE COMMAND message is not Normal Release, User Inactivity, Partial
Handover, Handover triggered,successful handover, or cs fallback triggered, the counter is
incremented repeatedly.
The corresponding counter is incremented by 1 each time the eNodeB sends an E-RAB
RELEASE INDICATION message to the MME and the Release Cause information element is
not Normal Release, User Inactivity, Partial Handover, Handover triggered, successful
handover, or cs fallback triggered. If the E-RAB RELEASE INDICATION message requires
multiple E-RAB releases at the same time, the corresponding counter is incremented
repeatedly.
The eNodeB releases all E-RABs of the UE after sending a UE CONTEXT RELEASE REQUEST
message to the MME. If the Release Cause information element of the UE CONTEXT
RELEASE REQUEST message is not Normal Release, User Inactivity, Partial Handover,
Handover triggered, successful handover, or cs fallback triggered, the counter is
incremented repeatedly.



This KPI can be used to evaluate the intra/inter-frequency Handover out success rate in a
cell or a cluster. The intra-frequency handover (HO) includes both inter-eNodeB and intra-
eNodeB.
The intra/inter-frequency handover (HO) includes both inter-eNodeB and intra-eNodeB
scenarios.


During a handover where the source cell and target cell are controlled by the same
eNodeB, as shown in point B, the corresponding counter is incremented by 1 each time
the eNodeB sends an RRC Connection Reconfiguration message to the UE. The counters
are measured as follows:
If the source cell and target cell work at the same frequency, the
L.HHO.IntraeNB.IntraFreq.ExecAttOut counter is incremented by 1.
If the source cell and target cell work at different frequencies, the
L.HHO.IntraeNB.InterFreq.ExecAttOut counter is incremented by 1.
As shown in point C , the corresponding counter is incremented each time the eNodeB
receives an RRC Connection Reconfiguration Complete message from the UE and the
subsequent operations are successful. The counters are measured as follows:
If the source cell and target cell are at the same frequency, the
L.HHO.IntraeNB.IntraFreq.ExecSuccOut counter is incremented by 1.
If the source cell and target cell are at different frequencies, the
L.HHO.IntraeNB.InterFreq.ExecSuccOut counter is incremented by 1.

During such a handover where the source cell and target cell are controlled by different
eNodeBs, as shown in point B in the figure above, the corresponding counter is
incremented each time the source eNodeB sends an RRC Connection Reconfiguration
message to the UE after receiving a HANDOVER REQUEST ACKNOWLEDGE from the target
eNodeB or receiving a HANDOVER COMMAND message from the MME. The counters are
measured as follows:
L.HHO.IntereNB.IntraFreq.ExecAttOut counter is incremented by 1.
L.HHO.IntereNB.InterFreq.ExecAttOut counter is incremented by 1.
As shown in point C , the corresponding counter is incremented each time the source
eNodeB receives a UE CONTEXT RELEASE message from the target eNodeB or a UE
CONTEXT RELEASE COMMAND message from the MME. The counters are measured as
follows:
L.HHO.IntereNB.IntraFreq.ExecSuccOut counter is incremented by 1.
L.HHO.IntereNB.InterFreq.ExecSuccOut counter is incremented by 1.

During such a handover where the source cell and target cell are controlled by different
eNodeBs, as shown in point B in the figure above, the corresponding counter is
incremented each time the source eNodeB sends an RRC Connection Reconfiguration
message to the UE after receiving a HANDOVER REQUEST ACKNOWLEDGE from the target
eNodeB or receiving a HANDOVER COMMAND message from the MME. The counters are
measured as follows:
L.HHO.IntereNB.IntraFreq.ExecAttOut counter is incremented by 1.
L.HHO.IntereNB.InterFreq.ExecAttOut counter is incremented by 1.
As shown in point C , the corresponding counter is incremented each time the source
eNodeB receives a UE CONTEXT RELEASE message from the target eNodeB or a UE
CONTEXT RELEASE COMMAND message from the MME. The counters are measured as
follows:
L.HHO.IntereNB.IntraFreq.ExecSuccOut counter is incremented by 1.
L.HHO.IntereNB.InterFreq.ExecSuccOut counter is incremented by 1.

The HO.eRAN.Out.Cell measurement unit measures the performance of intra-frequency or
inter-frequency outgoing handovers in a cell.

1526726995 L.HHO.IntraeNB.IntraFreq.PrepAttOut Number of intra-eNodeB intra-frequency
outgoing handover attempts in a cell
1526726998 L.HHO.IntraeNB.InterFreq.PrepAttOut Number of intra-eNodeB inter-frequency
1526726996 L.HHO.IntraeNB.IntraFreq.ExecAttOut Number of performed intra-eNodeB intra-

frequency outgoing handovers in a cell
1526726999 L.HHO.IntraeNB.InterFreq.ExecAttOut Number of performed intra-eNodeB inter-

1526726997 L.HHO.IntraeNB.IntraFreq.ExecSuccOut Number of successful intra-eNodeB intra-

1526727000 L.HHO.IntraeNB.InterFreq.ExecSuccOut Number of successful intra-eNodeB inter-

1526727001 L.HHO.IntereNB.IntraFreq.PrepAttOut Number of inter-eNodeB intra-frequency

1526727004 L.HHO.IntereNB.InterFreq.PrepAttOut Number of inter-eNodeB inter-frequency

1526727002 L.HHO.IntereNB.IntraFreq.ExecAttOut Number of performed inter-eNodeB intra-

1526727005 L.HHO.IntereNB.InterFreq.ExecAttOut Number of performed inter-eNodeB inter-

1526727003 L.HHO.IntereNB.IntraFreq.ExecSuccOut Number of successful inter-eNodeB intra-

1526727006 L.HHO.IntereNB.InterFreq.ExecSuccOut Number of successful inter-eNodeB inter-

1526728229 L.HHO.BlindHO.PrepAttOut Number of outgoing blind handover

attempts in a cell

This KPI can be used to evaluate the handover in success rate in a cell or a cluster.
The HO includes both inter-eNodeB and intra-eNodeB scenarios.

Number of Intra-eNB incoming handover attempts

During a handover where the source cell and target cell are controlled by the same
eNodeB, as shown in point B, the counter is incremented by 1 in the target cell
each time the eNodeB sends an RRC Connection Reconfiguration message to the
UE.
Number of successful intra-eNB incoming handovers
As shown in point C , the counter is incremented by 1 in the target cell each time
the eNodeB receives an RRC Connection Reconfiguration Complete message from
the UE and the subsequent operations are successful

Related Counters (Inter eNB) X2 Handover

Number of Inter-eNB incoming handover attempts
The source cell and target cell of a handover are controlled by different
eNodeBs. As shown in point B, the counter is incremented by 1 in the
target cell each time the target eNodeB sends a HANDOVER REQUEST
ACKNOWLEDGE message to the source eNodeB over the X2 interface or to
the MME over the S1 interface.
Number of successful Inter-eNB incoming handovers
As shown in point C , the counter is incremented by 1 in the target cell
each time the target eNodeB sends a UE CONTEXT RELEASE to the source
eNodeB over the X2 interface after receiving a PATH SWITCH ACK message
from the MME or the target eNodeB sends a HANDOVER NOTIFY message
to the MME over the S1 interface.
Related Counters (Inter eNB) S1 Handover
Number of Inter-eNB incoming handover attempts
The source cell and target cell of a handover are controlled by different
eNodeBs. As shown in point B, the counter is incremented by 1 in the
target cell each time the target eNodeB sends a HANDOVER REQUEST
ACKNOWLEDGE message to the source eNodeB over the X2 interface or to
the MME over the S1 interface.

Number of successful Inter-eNB incoming handovers

As shown in point C , the counter is incremented by 1 in the target cell
each time the target eNodeB sends a UE CONTEXT RELEASE to the source
eNodeB over the X2 interface after receiving a PATH SWITCH ACK message
from the MME or the target eNodeB sends a HANDOVER NOTIFY message
to the MME over the S1 interface.
Incoming Handover Measurement (Cell) (HO.eRAN.In.Cell)
The HO.eRAN.In.Cell measurement unit measures the performance of intra-frequency or
inter-frequency incoming handovers in a cell.

1526727253 L.HHO.IntraeNB.PrepAttIn Number of intra-eNodeB incoming handover
attempts in a cell
1526727254 L.HHO.IntraeNB.ExecAttIn Number of performed intra-eNodeB incoming
handovers in a cell
1526727255 L.HHO.IntraeNB.ExecSuccIn Number of successful intra-eNodeB incoming
handovers in a cell
1526727256 L.HHO.IntereNB.PrepAttIn Number of inter-eNodeB incoming handover
attempts in a cell
1526727257 L.HHO.IntereNB.ExecAttIn Number of performed inter-eNodeB incoming
handovers in a cell
1526727258 L.HHO.IntereNB.ExecSuccIn Number of successful inter-eNodeB incoming
handovers in a cell


Inter_RAT Handover Out Success Rate (LTE to WCDMA)

This KPI can be used to evaluate the inter-RAT handover out success rate in a cell
or a cluster. As suggested by the name, this KPI measures the performance of the
inter-RAT handover from LTE to WCDMA.
Inter_RAT Handover Out Success Rate (LTE to GSM)
This KPI can be used to evaluate the inter-RAT handover out success rate in a cell
or a cluster. As suggested by the name, this KPI measures the performance of the
inter-RAT handover from LTE to GSM.

Associated Counters (LTE to WCDMA)

Number of Performed Outgoing Handovers from E-UTRAN to UTRAN
As shown in point B, the counter is incremented by 1 each time the
eNodeB sends a Mobility from EUTRA Command message to the UE during
a handover from E-UTRAN to UTRAN. Number of Successful Outgoing
Handovers from E-UTRAN to UTRAN
Number of Successful Outgoing Handovers from E-UTRAN to UTRAN
As shown in point C, the counter is incremented by 1 each time the
eNodeB receives a UE CONTEXT RELEASE COMMAND message from the
MME after the UE is handed over from E-UTRAN to UTRAN.
Associated Counters (LTE to GSM)
Number of Performed Outgoing Handovers from E-UTRAN to GERAN
eNodeB sends a Mobility from EUTRA Command message to the UE during
a handover from E-UTRAN to UTRAN. Number of Successful Outgoing
Handovers from E-UTRAN to GERAN
Number of Successful Outgoing Handovers from E-UTRAN to GERAN
MME after the UE is handed over from E-UTRAN to GERAN

Inter-RAT Outgoing Handover Measurement (Cell) (HO.IRAT.Out.Cell)
The HO.IRAT.Out.Cell measurement unit measures the performance of outgoing handovers
from E-UTRAN to UTRAN or GERAN.

1526726989 L.IRATHO.E2W.PrepAttOut Number of Outgoing Handover Attempts from E-
UTRAN to UTRAN. The counter is incremented
by 1 each time the eNodeB receives a
Measurement Report message from the UE and
decides to perform a handover from E-UTRAN to
UTRAN.
1526726990 L.IRATHO.E2W.ExecAttOut Number of Performed Outgoing Handovers from
E-UTRAN to UTRAN. The counter is incremented
by 1 each time the eNodeB sends a Mobility
from EUTRA Command message to the UE
during a handover from E-UTRAN to UTRAN.
1526726991 L.IRATHO.E2W.ExecSuccOut Number of Successful Outgoing Handovers from
E-UTRAN to UTRAN. The counter is incremented
by 1 each time the eNodeB receives a UE
CONTEXT RELEASE COMMAND message from
the MME after the UE is handed over from E-
UTRAN to UTRAN.
1526726992 L.IRATHO.E2G.PrepAttOut Number of Outgoing Handover Attempts from E-
UTRAN to GERAN. The counter is incremented
by 1 each time the eNodeB receives a
Measurement Report message from the UE and
decides to perform a handover from E-UTRAN to
GERAN.
1526726993 L.IRATHO.E2G.ExecAttOut Number of Performed Outgoing Handovers from
E-UTRAN to GERAN. The counter is incremented
by 1 each time the eNodeB sends a Mobility
from EUTRA Command message to the UE
during a handover from E-UTRAN to GERAN.
1526726994 L.IRATHO.E2G.ExecSuccOut Number of Successful Outgoing Handovers from
E-UTRAN to GERAN. The counter is incremented
by 1 each time the eNodeB receives a UE
CONTEXT RELEASE COMMAND message from
the MME after the UE is handed over from E-
UTRAN to GERAN.

The number of LTE-to-CDMA2000 HO attempts increases by 1 at point B as shown 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.


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
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.

The number of handover-based LTE-to-CDMA2000 CSFB attempts increases by 1 at point

B after the eNodeB sends a Mobility From EUTRA Command message to the UE and
performs CSFB to a CDMA2000 network. The number of successful handover-based LTE-
to-CDMA2000 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 CDMA2000 network.

CSFB Success Rate Based Handover (LTE to WCDMA)

This KPI can be used to evaluate the success rate of handover-based LTE-to-
WCDMA CSFB in a cluster. As suggested by the name, this KPI measures the
performance of the inter-RAT handover-based CSFB from LTE to WCDMA.
CSFB Success Rate Based Handover (LTE to GSM)
This KPI can be used to evaluate the inter-RAT handover-based LTE-to-GSM CSFB
success rate in a cell or a cluster. As suggested by the name, this KPI measures the
performance of the inter-RAT handover-based CSFB from LTE to GSM.

Associated Counters (LTE to WCDMA)

The number of handover-based LTE-to-WCDMA CSFB attempts
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
MME after the UE successfully accesses the WCDMA network.
Associated Counters (LTE to GSM)
Number of handover-based LTE-to-GSM CSFB attempts
eNodeB sends a Mobility From EUTRA Command message to the UE and
performs CSFB to a GSM network
Number of successful handover-based LTE-to-GSM CSFB executions
As shown in point C, the counter is incremented by 1 each time where the
MME after the UE successfully accesses the GSM network.

Inter-RAT Outgoing Handover Measurement (Cell) (HO.IRAT.Out.Cell)
The HO.IRAT.Out.Cell measurement unit measures the performance of outgoing handovers
from E-UTRAN to CDMA2000 network, WCDMA network, GERAN, or TD-SCDMA
network.
1526728501 L.IRATHO.E2C.CSFB.PrepAttOut Number of CSFB-based inter-RAT handover
preparation attempts from E-UTRAN to
CDMA2000 network
1526728502 L.IRATHO.E2C.CSFB.ExecAttOut Number of CSFB-based handover execution
attempts from E-UTRAN to CDMA2000 network
1526728503 L.IRATHO.E2C.CSFB.ExecSuccO Number of successful CSFB-based inter-RAT
handover executions from E-UTRAN to
ut CDMA2000 network
1526728504 L.IRATHO.E2W.CSFB.PrepAttOu Number of CSFB-based inter-RAT handover
preparation attempts from E-UTRAN to WCDMA
t network
1526728505 L.IRATHO.E2W.CSFB.ExecAttOu Number of CSFB-based inter-RAT handover
execution attempts from E-UTRAN to WCDMA
t network
1526728506 L.IRATHO.E2W.CSFB.ExecSuccO Number of successful CSFB-based inter-RAT
handover executions from E-UTRAN to WCDMA
ut network
1526728507 L.IRATHO.E2G.CSFB.PrepAttOut Number of CSFB-based inter-RAT handover
preparation attempts from E-UTRAN to GERAN
1526728508 L.IRATHO.E2G.CSFB.ExecAttOut Number of CSFB-based inter-RAT handover

execution attempts from E-UTRAN to GERAN
1526728509 L.IRATHO.E2G.CSFB.ExecSuccO Number of successful CSFB-based inter-RAT

handover executions from E-UTRAN to GERAN
ut
1526728510 L.IRATHO.E2T.CSFB.PrepAttOut Number of CSFB-based inter-RAT handover

preparation attempts from E-UTRAN to TD-
SCDMA network
1526728511 L.IRATHO.E2T.CSFB.ExecAttOut Number of CSFB-based inter-RAT handover
execution attempts from E-UTRAN to TD-SCDMA
network
1526728512 L.IRATHO.E2T.CSFB.ExecSuccO Number of successful CSFB-based inter-RAT
handover executions from E-UTRAN to TD-
ut SCDMA network


This KPI provides the percentage of time of a cell in order to evaluate the degradation of
the network performance caused by the unavailable cells in busy hours on the radio
network.
Duration of Cell Unavailability
1526727209 L.Cell.Unavail.Dur.Sys Duration of cell unavailability due to non-

human factors
1526727210 L.Cell.Unavail.Dur.Manual Duration of cell unavailability due to human
factors
The counters measure the duration of cell unavailability due to human factors or non-
human factors. Human factors refer to operation maintenance, include the operator
execute the command on LMT(Local Maintenance Terminal): block cells or de-active
cell.Non-human factors refer to other reasons except operation maintenance, mainly
include: board inner fault, The CPRI link is faulty, The baseband processing unit carrying
services is faulty, The transmit/receive channel of the RF unit is faulty, transport resource
for control plane (S1 signaling link) or user plane (IP path) is unavailable, The license
resources are insufficient, the clock resources are unavailable.
The duration of cell unavailability is sampled every five seconds. If a cell is unavailable, the
corresponding counter is incremented by five at each sampling point accordingly. At the
end of a measurement period, the sum of these sampling results is reported.

Human operations include blocking and deactivating a cell by

using MML commands.
System faults include board faults, faults on a CPRI link, faults
on the LBBP carrying services of the cell, faults on TX or RX
channels of an RF module, unavailability of control-plane
transmission resources (S1 links), unavailability of user-plane
transmission resources (IP paths), insufficiency of license
resources, or unavailability of clocks.


This KPI consists of two sub-KPIs: uplink resource block (RB) utilizing rate and downlink RB
utilizing rate. These two sub-KPIs can be used to evaluate the busy-hour DL and UL RB
utilizing rate in each cell or cluster.
The available RB for DL/UL is fixed value according to the system bandwidth.


Number of Used Uplink PRBs

1526726737 L.ChMeas.PRB.UL.Used.Avg Average number of used uplink PRBs
The uplink PRBs in a cell are occupied by the PUSCH,PRACH and PUCCH in frequency
division mode, with those PRBs at both ends being used by the PUCCH and others in the
middle being used for the PUSCH and PRACH. The total number of PRBs used by the
PUCCH,PRACH and PUSCH is the number of used uplink PRBs. The counter measures the
average number of used uplink PRBs in a cell. It is used to analyze the usage of uplink PRBs.

1526726740 L.ChMeas.PRB.DL.Used.Avg Average number of used downlink PRBs

Maximum Board CPU Usage

Average Board CPU Usage
These counters provide the maximum and average CPU usage of a board in a specified
measurement period. The value type of these counters is integer and the results are in
round numbers. For example, if the result is 0%, the actual value ranges from 0.00% to
0.99%.
The CPU usage is sampled every second, and the average CPU usage of each 5s is used
as the sampling result. The maximum or the average of the final sampling results is used
as the value of this counter. For example, if the number of times that the average CPU
usage exceeds the preconfigured threshold in the measurement period is X1, X2, X3, ...,
and Xn, the values of the VS.BBUBoard.CPUload.Max and VS.BBUBoard.CPUload.Mean
counters are calculated using the following formulae: VS.BBUBoard.CPUload.Max =
MAX(Xi), VS.BBUBoard.CPUload.Mean = (X1+X2+...+Xn)/n.
The number of times of CPU Use Rate Overload
This counter provides the number of times of CPU use rate overload.
The CPU usage is sampled every second, and the average CPU usage of each 5s is used
as the sampling result. At the end of a measurement period, the number of times that
the average CPU usage exceeds the preconfigured threshold is used as the value of the
counter. The preconfigured threshold is 85%. For example, if the number of times that
the average CPU usage exceeds the preconfigured threshold in the measurement period
is X1, X2, X3, ..., and Xn, the value of the
VS.BBUBoard.CPULoad.CumulativeHighloadCount counter is the sum of X1, X2, X3, ...,
and Xn
Percentage of Cpu Use Rate Overload
This counter provides the percentage of the period during which the CPU usage of a
board exceeds the threshold to the entire measurement period

Number of Users in a Cell

Description
The counters measure the average number and maximum number of UEs in
a cell.
Measurement Points
This kind of counters are measured based on the user state at the sampling
time. The number of UEs in connected mode in a cell is sampled per second.
At the end of a measurement period, the maximum and average of these
sampling results are used as the values of the corresponding counters.
Number of Users with Data in the Uplink Buffer
Description
The counters measure the average and maximum number of users with
data in the uplink buffer in a cell.
Measurement Points
This kind of counters are measured based on the user state within the
sampling period. The number of connected users with data in the uplink
buffer in a cell is sampled per second. At the end of a measurement period,
the maximum and average of these sampling results is used as the values of
the corresponding counters.

Number of Users with Data in the Downlink Buffer

Description
The counters measure the average and maximum number of users with
data in the downlink buffer in a cell.
Measurement Points
This kind of counters are measured based on the user state within the
sampling period. The number of connected users with data in the downlink
buffer in a cell is sampled per second. At the end of a measurement period,
the average and maximum of these sampling results are used as the values
of the corresponding counters.
Number of UL Synchronized Users in a Cell
Description
The counter measures the number of UL synchronized users in a cell.
Measurement Points
The counters are measured based on the user state at the sampling time.
The number of all UL synchronized users in a cell is sampled per second. At
the end of a measurement period, the average of these sampling results is
used as the value of the counter.

Number of UEs Transmitting or Receiving Data in a Cell

Description
The counters measure the average and maximum number of users
transmitting or receiving data in a cell.
Measurement Points
The counters are measured based on the status of users within the
sampling period. The number of users in connected mode and with data in
the buffer in a cell is sampled per second. At the end of a measurement
period, the average and maximum of these sampling results is used as the
value of the corresponding counters.
Number of Activated UEs in the Downlink in a Cell
Description
The counters measure the number of UEs that have data in the downlink
buffer in a cell.
Measurement Points
The number of UEs that are in RRC_CONNECTED mode and have data in
the downlink buffer in a cell is sampled per millisecond. At the end of a
measurement period, the average and maximum of these sampling results
are used as the values of the corresponding counters.
Number of Activated UEs in the Uplink in a Cell
Description
The counters measure the number of UEs that have data in the uplink
buffer in a cell.
Measurement Points
the uplink buffer in a cell is sampled per millisecond. At the end of a
measurement period, the average and maximum of these sampling results
are used as the values of the corresponding counters.
Number of Activated UEs in a Cell
Description
The counters measure the number UEs that have data in the buffer in a cell.
Measurement Points
either the downlink or uplink buffer in a cell is sampled per millisecond. At
the end of a measurement period, the average and maximum of these
sampling results are used as the values of the corresponding counters.




Formula: None
Unit: bit

Formula: None
Unit: bit



Unit:


Unit:ms
Receive Duration of Uplink PDCP SDUs in a Cell
1526728260 L.Thrp.Time.UL Total receive duration of uplink PDCP SDUs in a cell

Receive duration of uplink PDCP SDUs for services with the QCI
1526726777 L.Thrp.Time.UL.QCI.1
of 1 in a cell
of 2 in a cell
of 3 in a cell
of 4 in a cell
of 5 in a cell
of 6 in a cell
of 7 in a cell
of 8 in a cell
of 9 in a cell

This KPI evaluates the cell downlink average throughput when there are data transferring
at downlink. It reflects the cell capacity.
Unit: kbit/s

Downlink Traffic Volume for PDCP SDUs in a Cell
Counters
1526728261 L.Thrp.bits.DL Total downlink traffic volume for PDCP SDUs
in a cell
Description
The total bits of successfully received signaling SDUs on SRBs at the PDCP
layer are sampled per second. At the end of a measurement period, the
sum of these sampling results is used as the value of the counter.
Measurement Points
The total bits of successfully received signaling SDUs on SRBs at the PDCP
layer are sampled per second. At the end of a measurement period, the
sum of these sampling results is used as the value of the counter.
FormulaNone
Unitbit

Total Duration of Uplink Data Transmission in a Cell

Counters

1526728998 L.Thrp.Time.Cell.UL.Hi Total duration of downlink data transmission in a
ghPrecision cell (with the precision of 1 ms)
Description
The counters measure the total duration of downlink data transmission in a
cell with the precision of 1 millisecond.
Measurement Points
The duration of uplink data transmission in a cell is sampled per millisecond.
If there is uplink data transmission within a sampling period, the sampling
result is 1 ms. At the end of a measurement period, the sum of these
sampling results is used as the value of the
L.Thrp.Time.Cell.UL.HighPrecision counter.
The internal timer of the eNodeB has a deviation of one period, and
therefore the measurement result of the counter has a deviation.
FormulaNone
Unitms
Total Bits of Transmitted Signaling SDUs on SRBs at the PDCP Layer
Counters

1526728261 L.Thrp.bits.DL Total downlink traffic volume for PDCP SDUs in a
cell
Description
The total bits of successfully transmitted SDUs on SRBs at the PDCP layer
are sampled per second. At the end of a measurement period, the sum of
these sampling results is used as the value of the counter.
Measurement Points
The total bits of successfully transmitted SDUs on SRBs at the PDCP layer
are sampled per second. At the end of a measurement period, the sum of
these sampling results is used as the value of the counter.
Formula: None
Unit: bit

Total Duration of Downlink Data Transmission in a Cell

Counters

1526728997 L.Thrp.Time.Cell.DL. Total duration of uplink data transmission in a cell
HighPrecision (with the precision of 1 ms)
Description
The counter measures the total duration of downlink data transmission in a
cell.
Measurement Points
The duration of downlink data transmission in a cell is sampled per
millisecond. If there is downlink data transmission within a sampling period,
the sampling result is 1 ms. At the end of a measurement period, the sum
of these sampling results is used as the value of the
L.Thrp.Time.Cell.DL.HighPrecision counter.
The internal timer of the eNodeB has a deviation of one period, and
therefore the measurement result of the counter has a deviation.
Formula: None
Unit: ms








01-LTE KPI Introduction

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

01-LTE KPI Introduction

Transféré par

Droits d'auteur :

Formats disponibles

LTE eRAN8.

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Each measurement result is related to a specific measurement object.

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

KPI name: It is a descriptive name of the KPI.

Confidential Information of Huawei. No Spreading Without Permission

eNodeB supports two meaurement report:

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Counter Name Description

1526726658 L.RRC.ConnReq.Att Number of RRC Connection Request

Confidential Information of Huawei. No Spreading Without Permission

Counter ID Counter Name Description

Number of RRC Connection Setup Attempts in a Cell:

Counter ID Counter Name Description

1526728216 L.RRC.ConnSetup Number of RRC Connection Setup messages

Confidential Information of Huawei. No Spreading Without Permission

Counter ID Counter Name Description

1526726659 L.RRC.ConnReq.Succ Number of RRC Connection Setup

Confidential Information of Huawei. No Spreading Without Permission

Number of RRC Connection Setup Failures for Different Causes in a Cell

Confidential Information of Huawei. No Spreading Without Permission

Counter ID Counter Name Description

1526727087 L.RRC.ReEst.ReconfFail.Att Number of RRC connection reestablishment

1526727090 L.RRC.ReEst.HoFail.Att Number of RRC connection reestablishment

1526730536 L.RRC.ReEst.NonSrccell.Att Number of RRC connection reestablishment

Confidential Information of Huawei. No Spreading Without Permission

Counter ID Counter Name Description

1526730537 L.RRC.ReEst.NonSrccell.Succ Number of successful RRC connection

Confidential Information of Huawei. No Spreading Without Permission

Number of RRC Connection Reestablishment Failures for Different Causes in a Cell

Counter ID Counter Name Description

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

LTE-SAE QoS Class Identifier

Confidential Information of Huawei. No Spreading Without Permission

Number of Initial E-RAB Setup Attempts in a Cell

Counter ID Counter Name Description

1526728192 L.E-RAB.InitAttEst.QCI.1 Number of initial E-RAB setup attempts for the

......... .................. ..........................

Confidential Information of Huawei. No Spreading Without Permission

Counter ID Counter Name Description

Confidential Information of Huawei. No Spreading Without Permission

Number of E-RAB Setup Attempts in a Cell

Counter ID Counter Name Description

Confidential Information of Huawei. No Spreading Without Permission

Counter ID Counter Name Description

Counter ID Counter Name Description

Counter ID Counter Name Description

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

The number of setup times of S1 signaling connections related to UEs is incremented by 1