Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Issue 01
Date 2018-04-10
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or
representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Website: http://www.huawei.com
Email: support@huawei.com
Contents
3 Retainability KPIs....................................................................................................................... 11
3.1 Call Drop Rate (VoIP)...................................................................................................................................................11
3.2 Service Drop Rate.........................................................................................................................................................12
3.3 Minutes Per Service Drop.............................................................................................................................................12
3.4 Minutes Per Drop (VoIP).............................................................................................................................................. 13
3.5 Service Drop Rate (eMTC)...........................................................................................................................................14
4 Mobility KPIs............................................................................................................................... 15
4.1 Intra-Frequency Handover Out Success Rate...............................................................................................................16
4.2 Intra-Frequency Handover Out Success Rate (VoIP)................................................................................................... 23
4.3 Inter-Frequency Handover Out Success Rate...............................................................................................................23
4.4 Inter-Frequency Handover Out Success Rate (VoIP)................................................................................................... 30
4.5 Inter-FddTdd Handover Out Success Rate................................................................................................................... 30
4.6 Inter-FddTdd Handover Out Success Rate (VoIP)....................................................................................................... 37
4.7 Intra-RAT Handover In Success Rate...........................................................................................................................37
4.8 Inter-RAT Handover Out Success Rate (LTE to CDMA2000).................................................................................... 43
4.9 Inter-RAT Handover Out Success Rate (LTE to WCDMA).........................................................................................44
4.10 Inter-RAT Handover Out Success Rate (LTE to GSM)..............................................................................................45
4.11 Inter-RAT Handover Out Success Rate (LTE to TD-SCDMA)..................................................................................47
4.12 CSFB Preparation Success Rate................................................................................................................................. 48
4.13 CSFB Success Rate Based Handover (LTE to WCDMA)......................................................................................... 50
4.14 CSFB Success Rate Based Handover (LTE to GSM).................................................................................................51
4.15 CSFB Success Rate Based Handover (LTE to TD-SCDMA).................................................................................... 53
6 Utilization KPIs........................................................................................................................... 70
6.1 Downlink Resource Block Utilizing Rate.................................................................................................................... 70
6.2 Uplink Resource Block Utilizing Rate......................................................................................................................... 71
6.3 Uplink Preschedule Resource Block Occupied Rate....................................................................................................71
6.4 Average CPU Load....................................................................................................................................................... 72
7 Availability KPIs......................................................................................................................... 73
7.1 Radio Network Unavailability Rate............................................................................................................................. 73
8 Traffic KPIs...................................................................................................................................75
8.1 Radio Bearers............................................................................................................................................................... 75
8.2 Downlink Traffic Volume............................................................................................................................................. 76
8.3 Uplink Traffic Volume..................................................................................................................................................77
8.4 Average User Number.................................................................................................................................................. 78
8.5 Maximum User Number............................................................................................................................................... 79
13 References................................................................................................................................... 92
Index..................................................................................................................................................93
01 (2018-04-10)
This is the first commercial release.
Compared with the last issue, this issue does not include any changes.
Draft A (2018-02-05)
This is a draft.
Compared with eRAN12.1 03 (2016-07-30), this issue includes the following changes:
l Added the 2.1 RRC Setup Success Rate KPI.
l Deleted the Resource Block Utilizing Rate KPI, which is replaced by the 6.1 Downlink
Resource Block Utilizing Rate and 6.2 Uplink Resource Block Utilizing Rate KPIs.
l Optimized formulas and related descriptions of the following KPIs:
– 4.17 SRVCC Success Rate (LTE to WCDMA)
– 4.18 SRVCC Success Rate (LTE to GSM)
– 4.19 SRVCC Success Rate (LTE to TD-SCDMA)
– 5.3 Service Downlink Average Throughput
– 5.2 User Uplink Average Throughput
– 5.5 Cell Downlink Average Throughput
– 5.6 Cell Uplink Average Throughput
2 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.
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.
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 2-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.
Definition
The RRC Setup Success Rate KPI is defined in Table 2-1.
Note None
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. The RRC Setup Success Rate (Service) KPI evaluates the RRC setup success rate of
service-related causes in a cell or 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 2-2. The
Definition
The RRC Setup Success Rate (Service) KPI is defined in Table 2-2.
Note None
Description
The RRC Setup Success Rate (Signaling) KPI indicates the RRC setup success rate of the
signaling-related cause (mo-signaling) in a cell or 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 2-3. 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 2-3.
Note None
Description
The S1SIG Connection Setup Success Rate KPI indicates the success rate of signaling
connection setups over the S1 interface. This 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.
Definition
The S1SIG Connection Setup Success Rate KPI is defined in Table 2-4. 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.
Note None
Description
The E-RAB Setup Success Rate (VoIP) 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 2-5.
Note None
Description
The E-RAB Setup Success Rate 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 2-6. For details about how to
measure the counters E-RAB setup attempts and successful E-RAB setups, see Description.
Note None
Description
The Call Setup Success Rate KPI indicates the call setup success rate for all services in a cell
or radio network. 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 2-7. 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.
Note None
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. This KPI is measured at the eNodeB when eMTC UEs initiate RRC connection setup
procedures. As shown in Figure 2-5, the number of RRC connection setup attempts is
counted by the eNodeB 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 2-8.
Note None
3 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.
Description
The Call Drop Rate (VoIP) 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 3-1.
Note None
Description
The Service Drop Rate KPI indicates the service drop rate of all services (including VoIP).
Similar to the KPI defined in 3.1 Call Drop Rate (VoIP), this KPI is calculated using the
formula defined in Table 3-2.
Definition
The Service Drop Rate KPI is defined in Table 3-2.
Note None
Description
The Minutes Per Service Drop 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 3-3.
Unit Minute
Note None
Description
The Minutes Per Drop (VoIP) 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 3-4.
Unit Minute
Note None
Description
The Service Drop Rate (eMTC) 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 3-5.
Definition
The Service Drop Rate (eMTC) KPI is defined in Table 3-5.
Note None
4 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).
Description
The Intra-Frequency Handover Out Success Rate 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.
l Intra-eNodeB outgoing HO without RRC connection reestablishment
Figure 4-1 illustrates 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
HO outgoing 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.
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.
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.
l Inter-eNodeB outgoing HO without RRC connection reestablishment
Figure 4-3 and Figure 4-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.
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 4-5 X2-based outgoing HO with RRC connection reestablishment to the target
cell
Figure 4-6 S1-based outgoing HO with RRC connection reestablishment to the target
cell
Figure 4-7 X2-based outgoing HO with RRC connection reestablishment to the source
cell
Figure 4-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 4-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.
Note None
Description
The Intra-Frequency Handover Out Success Rate (VoIP) 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 4-2.
Note None
Description
The Inter-Frequency Handover Out Success Rate 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 4-9 and Figure 4-10 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 4-11, Figure 4-12, Figure 4-13, Figure 4-14, Figure 4-15, and Figure 4-16
illustrate inter-eNodeB HOs, and the source and target cells operate on different frequencies.
Figure 4-13 X2-based outgoing HO with RRC connection reestablishment to the target cell
Figure 4-14 S1-based outgoing HO with RRC connection reestablishment to the target cell
Figure 4-15 X2-based outgoing HO with RRC connection reestablishment to the source cell
Figure 4-16 S1-based outgoing HO with RRC connection reestablishment to the source cell
Definition
The Inter-Frequency Handover Out Success Rate KPI is defined in Table 4-3. 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.
Note None
Description
The Intra-Frequency Handover Out Success Rate (VoIP) 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
Table 4-4 defines the Inter-frequency Handover Out Success Rate (VoIP) KPI.
Note None
Description
The Inter-FddTdd Handover Out Success Rate 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 4-17 and Figure 4-18 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 4-19, Figure 4-20, Figure 4-21, Figure 4-22, Figure 4-23, and Figure 4-24
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 4-21 X2-based outgoing HO with RRC connection reestablishment to the target cell
Figure 4-22 S1-based outgoing HO with RRC connection reestablishment to the target cell
Figure 4-23 X2-based outgoing HO with RRC connection reestablishment to the source cell
Figure 4-24 S1-based outgoing HO with RRC connection reestablishment to the source cell
Definition
The Inter-FddTdd Handover Out Success Rate KPI is defined in Table 4-5. 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.
Note None
Description
The Inter-FddTdd Handover Out Success Rate (VoIP) 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 4-6.
Note None
Description
The Intra-RAT Handover In Success Rate 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.
l Intra-eNodeB incoming HO without RRC connection reestablishment
Figure 4-25 illustrates 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
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.
l Inter-eNodeB incoming HO without RRC connection reestablishment
Figure 4-27 and Figure 4-28 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 4-29 X2-based incoming HO with RRC connection reestablishment to the target
cell
Figure 4-30 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 4-7. Note that the number
of incoming HO execution attempts and the number of incoming HO executions are collected
based on the description in Description.
Note None
Description
The Inter-RAT Handover Out Success Rate (LTE to CDMA2000) 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 4-31 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.
Definition
The Inter-RAT Handover Out Success Rate (LTE to CDMA2000) KPI is defined in Table 4-8.
For details about related counters, see Description.
Note None
Description
The Inter-RAT Handover Out Success Rate (LTE to WCDMA) KPI indicates the success rate
of handovers from an LTE cell or radio network to WCDMA networks.
The number of LTE-to-WCDMA HO attempts increases by 1 at point B as shown in Figure
4-32 after the eNodeB sends a Mobility From EUTRA Command message to the UE. The
number of successful inter-RAT HOs from LTE to WCDMA increases by 1 at point C, where
the eNodeB receives a UE Context Release Command message from the MME after the UE
accesses the WCDMA network.
Definition
The Inter-RAT Handover Out Success Rate (LTE to WCDMA) KPI is defined in Table 4-9.
For details about related counters, see Description.
Note None
Description
The Inter-RAT Handover Out Success Rate (LTE to GSM) KPI indicates the success rate of
handovers from an LTE cell or radio network to GSM networks.
The number of LTE-to-GSM HO attempts increases by 1 at point B as shown in Figure 4-33
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 4-10. For
details about related counters, see Description.
Note None
Description
The Inter-RAT Handover Out Success Rate (LTE to TD-SCDMA) KPI indicates the success
rate of handovers from an LTE cell or radio network to TD-SCDMA networks.
Definition
The Inter-RAT Handover Out Success Rate (LTE to TD-SCDMA) KPI is defined in Table
4-11. For details about related counters, see Description.
Note None
Description
The CSFB Preparation Success Rate 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 4-35 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.
Definition
The CSFB Preparation Success Rate KPI is defined in Table 4-12. For details about related
counters, see Description.
Note None
Description
The CSFB Success Rate Based Handover (LTE to WCDMA) 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 4-37 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 4-13.
For details about related counters, see Description.
Note None
Description
The CSFB Success Rate Based Handover (LTE to GSM) 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 4-38 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 4-14.For
details about related counters, see Description.
Note None
Description
The CSFB Success Rate Based Handover (LTE to TD-SCDMA) KPI indicates the success
rate of handover-based LTE-to-TD-SCDMA CSFB.
Definition
The CSFB Success Rate Based Handover (LTE to TD-SCDMA) KPI is defined in Table 4-15.
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.
Note None
Description
The CSFB Success Rate Based Handover (LTE to CDMA2000) KPI indicates the success rate
of handover-based LTE-to-CDMA2000 CSFB.
The number of handover-based LTE-to-CDMA2000 CSFB attempts increases by 1 at point B
as shown in Figure 4-40 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.
Definition
The CSFB Success Rate Based Handover (LTE to CDMA2000) KPI is defined in Table 4-16.
For details about related counters, see Description.
Note None
Description
The SRVCC Success Rate (LTE to WCDMA) 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 4-17.
Note None
Description
The SRVCC Success Rate (LTE to GSM) 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 4-18.
Note None
Description
The SRVCC Success Rate (LTE to TD-SCDMA) 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 4-19.
Note None
Description
The Intra-Frequency Handover Out Success Rate (eMTC) 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 4-20.
Note None
Description
The Inter-Frequency Handover Out Success Rate (eMTC) 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 4-21.
Note None
The service integrity KPIs indicate service quality provided for UEs in an E-UTRAN.
Description
The User Downlink Average Throughput 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 5-1.
Definition
The User Downlink Average Throughput KPI is defined in Table 5-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.
Unit kbit/s
Note None
Description
The User Uplink Average Throughput 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 is defined in Table 5-2.
Associat The following formulas are both applicable, and the second formula is more
ed close to the protocol.
Counter User Uplink Average Throughput = (L.Thrp.bits.UL –
s 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 None
Description
The Service Downlink Average Throughput 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 5-4[6]. Nine different sub-
KPIs exist for each QCI. The formula for each KPI is mapped to its corresponding counter.
Table 5-3 lists the requirements for services with different QCIs.
Formu DLAverageThroughput_QCI_1
la DLAverageThroughput_QCI_2
DLAverageThroughput_QCI_3
DLAverageThroughput_QCI_4
DLAverageThroughput_QCI_5
DLAverageThroughput_QCI_6
DLAverageThroughput_QCI_7
DLAverageThroughput_QCI_8
DLAverageThroughput_QCI_9
Unit kbit/s
Note None
Description
The Service Uplink Average Throughput 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 5-5[6]. Nine sub-KPIs exist
for each QCI. The formula for each KPI is mapped to its corresponding counter.
Formul ULAverageThroughput_QCI_1
a ULAverageThroughput_QCI_2
ULAverageThroughput_QCI_3
ULAverageThroughput_QCI_4
ULAverageThroughput_QCI_5
ULAverageThroughput_QCI_6
ULAverageThroughput_QCI_7
ULAverageThroughput_QCI_8
ULAverageThroughput_QCI_9
Associat l FDD:
ed Service Uplink Average Throughput = L.Thrp.bits.UL.QCI.n/
Counter L.Thrp.Time.UL.QCI.n
s l 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
Description
The Cell Downlink Average Throughput 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 5-6 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.
Unit kbit/s
Note None
Description
The Cell Uplink Average Throughput KPI indicates the average cell uplink throughput when
data is transferring at the uplink. The Cell Uplink Average Throughput KPI reflects the cell's
capacity.
Definition
The Cell Uplink Average Throughput KPI is defined in Table 5-7 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.
Unit kbit/s
Note None
Description
The Downlink Packet Loss Rate (VoIP) 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 5-8.
Note None
Description
The Downlink Packet Loss Rate (VoIP) 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 5-9.
Note None
Description
The Uplink Packet Loss Rate KPI indicates the uplink packet loss situation of a cell at the
PDCP layer. This 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 5-10.
Note None
Description
The Uplink Packet Loss Rate (VoIP) KPI indicates the uplink packet loss situation of a cell at
the PDCP layer for VoIP services. This 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 5-11.
Note None
Description
The Downlink Residual Block Error Rate (eMTC) KPI indicates the downlink residual bit
error rate of eMTC UEs in a 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 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 5-12.
Note None
Description
The Uplink Residual Block Error Rate (eMTC) KPI indicates the uplink residual bit error rate
of eMTC UEs in a 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 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 5-13.
Note None
6 Utilization KPIs
Utilization KPIs are used to evaluate the capabilities, such as the capability to meet traffic
demands, in specific internal conditions.
Description
The KPI indicates the busy-hour DL RB utilizing rates in each cell or radio network.
Definition
The downlink Resource Block Utilizing Rate KPI is defined in Table 6-1.
Note None
Description
The KPI indicates the busy-hour UL RB utilizing rates in each cell or radio network.
Definition
The uplink Resource Block Utilizing Rate KPI is defined in Table 6-2.
Note None
Description
The Uplink Preschedule Resource Block Occupied Rate KPI indicates the percentage of
uplink RBs allocated to UEs for pre-scheduling. The Uplink Preschedule Resource Block
Occupied Rate KPI can be 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 6-3.
Note None
Description
The Average CPU Load KPI indicates the CPU usage during busy hours.
Definition
The Average CPU Load KPI is defined in Table 6-4. The CPU load is calculated by averaging
the CPU usage ratio during the measurement period.
Object CPU
Formul MeanCPUUtility
a
Note None
7 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.
Description
The Radio Network Unavailability Rate KPI indicates the percentage of time when cells in a
radio network are unavailable. This KPI is used to evaluate the deterioration of network
performance caused by unavailable cells on the radio network during busy hours.
Definition
The Radio Network Unavailability Rate KPI is defined in Table 7-1. This KPI is calculated
based on the length of time all cell services are unavailable on the radio network.
Note None
8 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.
Description
The Radio Bearers 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 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 8-1 and include ten different sub-KPIs. The
formula for each KPI is mapped to its corresponding counter.
Formu RadioBearers
la 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
Unit N/A
Note None
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 8-2.
Formu DLTrafficVolume
la DLTrafficVolume_QCI_1
DLTrafficVolume_QCI_2
DLTrafficVolume_QCI_3
DLTrafficVolume_QCI_4
DLTrafficVolume_QCI_5
DLTrafficVolume_QCI_6
DLTrafficVolume_QCI_7
DLTrafficVolume_QCI_8
DLTrafficVolume_QCI_9
Unit bit
Note None
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 8-3.
Unit bit
Note None
Description
The Average User Number 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 8-4. The formula is mapped to its
corresponding counters.
Formul AvgUserNumber
a
Unit N/A
Note None
Description
The Maximum User Number 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 8-5. The formula is mapped to its
corresponding counters.
Formul MaxUserNumber
a
Unit N/A
Note None
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.
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. The RRC Setup
Success Rate (NB-IoT) KPI indicates the RRC connection setup success rate of an NB-IoT
cell or an entire NB-IoT network.
This KPI is measured by the eNodeB when UEs initiate RRC connection setup procedures.
As shown in Figure 9-1, the number of RRC connection setup attempts is counted by the
eNodeB 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 9-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 9-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 9-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.
Note None
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.
This KPI is measured at the eNodeB when UEs initiate RRC connection resume procedures.
As shown in Figure 9-3, 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.
Definition
The RRC Resume Success Rate (NB-IoT) KPI is defined in Table 9-2. 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.
Note None
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.
Description
The Service Drop Rate (NB-IoT) 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. This KPI considers both cases. For details about its
calculation formula, see Table 10-1.
Definition
The Service Drop Rate (NB-IoT) KPI is defined in Table 10-1.
Note None
The NB-IoT service integrity KPIs indicate service quality provided for UEs in an NB-IoT
network.
Description
The Downlink SRB Packet Loss Rate (NB-IoT) 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 11-1.
Note None
Definition
The Downlink Residual Block Error Rate (NB-IoT) KPI is defined in Table 11-2.
Note None
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 11-3.
Note None
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. This 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 11-4.
Note None
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. This 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 11-5.
Note None
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.
Description
The Radio Network Unavailability Rate (NB-IoT) KPI indicates the percentage of time when
a radio network is unavailable. This KPI is used to evaluate the radio network performance
deterioration caused by NB-IoT cell unavailability.
Definition
The Radio Network Unavailability Rate (NB-IoT) KPI is defined in Table 12-1. This KPI is
calculated based on the length of time in which all NB-IoT cells are unavailable on the radio
network.
Note None
13 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)"
Index