5G RAN KPI Reference

Contents
8.4.4 5G RAN KPI Reference
8.4.4.2 Changes in 5G RAN KPI Reference
8.4.4.3 Accessibility KPIs
8.4.4.3.1 RRC Setup Success Rate (CU)
8.4.4.3.2 RRC Setup Success Rate (Service) (CU)
8.4.4.3.3 RRC Setup Success Rate (Signaling) (CU)
8.4.4.3.4 NGSIG Connection Setup Success Rate (CU)
8.4.4.3.5 QoS Flow Setup Success Rate (CU)
8.4.4.3.6 Call Setup Success Rate (CU)
8.4.4.4 Retainability KPIs
8.4.4.5 Mobility KPIs
8.4.4.5.1 Intra-Frequency Handover Out Success Rate (CU)
8.4.4.5.2 Intra-RAT Handover In Success Rate (CU)
8.4.4.5.3 Inter-RAT Handover Out Success Rate (NR to LTE) (CU)
8.4.4.6 Service Integrity KPIs
8.4.4.6.1 User Downlink Average Throughput (DU)
8.4.4.6.2 User Uplink Average Throughput (DU)
8.4.4.6.3 Cell Downlink Average Throughput (DU)
8.4.4.6.4 Cell Uplink Average Throughput (DU)
8.4.4.7 Utilization KPIs
8.4.4.7.1 Downlink Resource Block Utilizing Rate (DU)
8.4.4.7.2 Uplink Resource Block Utilizing Rate (DU)
8.4.4.7.3 Average CPU Load
8.4.4.8 Availability KPIs
8.4.4.8.1 Radio Network Unavailability Rate (CU)
8.4.4.9 Traffic KPIs
8.4.4.9.1 Downlink Traffic Volume (DU)
8.4.4.9.2 Uplink Traffic Volume (DU)
8.4.4.9.3 Average User Number (CU)
8.4.4.9.4 Maximum User Number
8.4.4.10 NSA DC Accessibility and Mobility KPIs
8.4.4.10.1 SgNB Addition Success Rate
8.4.4.10.2 Intra-SgNB PSCell Change Success Rate
8.4.4.10.3 Inter-SgNB PSCell Change Success Rate
8.4.4.10.4 SgNB-Triggered Abnormal SgNB Release Rate
8.4.4.11 Reference Documents

8.4.4 5G RAN KPI Reference

Purpose
 This document describes basic key performance indicators (KPIs) in the 5G RAN. The
KPI formulas are used in common scenarios. Only associated key counters are provided
in this document.

NOTE:
 The KPIs described in this document are for common scenarios, and the formulas are for
instruction only. For details on KPIs that are closely related to features, see the related
feature parameter description.
 This document lists only key counters associated with the KPIs. For details on other counters
used on the live network, see 3900 & 5900 Series Base Station Performance Counter
Reference.
 If 3GPP protocols are updated, KPIs described in this document may change.

Intended Audience
This document is intended for:
 Network planners
 Network administrators
 Network operators

Product Versions
The following table lists the product versions related to this document.

Product Name Solution Version Product Version

DBS5900  SRAN15.1 V100R015C10

 5G RAN2.1
DBS5900 LampSite

DBS3900

DBS3900 LampSite

BTS3900

BTS5900

BTS3900A

BTS5900A

BTS3900L

BTS5900L

BTS3900AL
 Product Name Solution Version Product Version

BTS5900AL

Organization

5G RAN KPI Reference

Changes in 5G RAN KPI Reference
Accessibility KPIs
Retainability KPIs
Mobility KPIs
Service Integrity KPIs
Utilization KPIs
Availability KPIs
Traffic KPIs
NSA DC Accessibility and Mobility KPIs
Reference Documents
Copyright © Huawei Technologies Co., Ltd.

Copyright © Huawei Technologies Co., Ltd.

8.4.4.2 Changes in 5G RAN KPI

Reference
This chapter describes the changes in 5G RAN KPI Reference.

01 (2019-06-06)
This is the first commercial release.
Compared with Draft A (2018-12-30), this issue includes the following new topics:
NSA DC Accessibility and Mobility KPIs

Compared with Draft A (2018-12-30), this issue does not include any changes or
exclude any topics.

Draft A (2018-12-30)
This is a draft.
Compared with V100R013C10, this issue includes the following changes:
 Added KPIs in Accessibility KPIs, Retainability KPIs, Mobility KPIs, and Availability KPIs.
 Update KPIs in User Downlink Average Throughput (DU) and User Uplink Average Throughput
(DU).

 Revised KPI names to add CU or DU as suffix to KPI names.

Parent Topic: 5G RAN KPI Reference

Copyright © Huawei Technologies Co., Ltd.
 Copyright © Huawei Technologies Co., Ltd.
< Previous topicNext topic >

8.4.4.3 Accessibility KPIs

Accessibility KPIs are used to measure the probability that a user successfully accesses
the network and requests services. The services include RRC connection setup, NGSIG
setup, PDU session setup, and QoS flow setup.
RRC Setup Success Rate (CU)
RRC Setup Success Rate (Service) (CU)
RRC Setup Success Rate (Signaling) (CU)
NGSIG Connection Setup Success Rate (CU)
QoS Flow Setup Success Rate (CU)
Call Setup Success Rate (CU)

Parent Topic: 5G RAN KPI Reference

Copyright © Huawei Technologies Co., Ltd.

Copyright © Huawei Technologies Co., Ltd.

< Previous topicNext topic >

8.4.4.3.1 RRC Setup Success Rate (CU)

Description
According to 3GPP TS 38.331, the RRC connection setup procedure is triggered by
different causes. The upper layer determines the cause value for the RRC connection
setup initiated by the UE. The RRC connection setup for the cause value of mo-
signaling is related to signaling. The RRC connection setup for other reasons is related
to services.
This KPI is calculated by the gNodeB when the UE initiates an RRC connection setup
procedure. As shown at point A in Figure 1, the total number of RRC connection setup
attempts due to different causes is incremented by 1 each time the gNodeB receives an
RRCSetupRequest message from the UE. As shown at point C, the total number of
successful RRC connection setups due to different setup causes is incremented by 1.
 Figure 1 Measurement points for RRC connection setup

Definition
The RRC Setup Success Rate KPI is defined in Table 1.

Table 1 RRC Setup Success Rate (CU)

Name RRC Setup Success Rate (CU)

Object Cell or radio network

Formula RRCS_SR = (RRCSetupSuccess/RRCSetupAttempt) x 100%

Associated RRC Setup Success Rate = (N.RRC.SetupReq.Succ/N.RRC.SetupReq.Att) x

Counters 100%

Unit %

Note None

Parent Topic: Accessibility KPIs

Copyright © Huawei Technologies Co., Ltd.

Copyright © Huawei Technologies Co., Ltd.

 Next topic >

8.4.4.3.2 RRC Setup Success Rate

(Service) (CU)
Description
According to 3GPP TS 38.331, the RRC connection setup procedure is triggered by
different causes. The upper layer determines the cause value for the RRC connection
setup initiated by the UE. The RRC connection setup for the cause value of mo-
signaling is related to signaling. The RRC connection setup for other reasons is related
to services. This KPI is used to evaluate the RRC connection setup success rate of
services in a cell or on the entire network.
This KPI is calculated by the gNodeB when the UE initiates an RRC connection setup
procedure. As shown at point A in Figure 1, the total number of RRC connection setup
attempts due to services is incremented by 1 each time the gNodeB receives an
RRCSetupRequest message from the UE. As shown at point C, the number of
successful RRC connection setups due to services is incremented by 1.
Figure 1 Measurement points for RRC connection setup

Definition
The RRC Setup Success Rate (Service) KPI is defined in Table 1.
 Table 1 RRC Setup Success Rate (Service) (CU)

Name RRC Setup Success Rate (Service) (CU)

Object Cell or radio network

Formula RRCS_SRservice = (RRCSetupSuccessservice/RRCSetupAttemptservice) x

100%

Associated RRC Setup Success Rate (Service) = ((N.RRC.SetupReq.Succ.Emc +

Counters N.RRC.SetupReq.Succ.HighPri + N.RRC.SetupReq.Succ.Mt +
N.RRC.SetupReq.Succ.MoData + N.RRC.SetupReq.Succ.MoVoiceCall +
N.RRC.SetupReq.Succ.MpsPri + N.RRC.SetupReq.Succ.MoSms +
N.RRC.SetupReq.Succ.MoVideoCall)/(N.RRC.SetupReq.Att.Emc +
N.RRC.SetupReq.Att.HighPri + N.RRC.SetupReq.Att.Mt +
N.RRC.SetupReq.Att.MoData + N.RRC.SetupReq.Att.MoVoiceCall +
N.RRC.SetupReq.Att.MpsPri + N.RRC.SetupReq.Att.MoSms +
N.RRC.SetupReq.Att.MoVideoCall)) x 100%

Unit %

Note None

Parent Topic: Accessibility KPIs

Copyright © Huawei Technologies Co., Ltd.

Copyright © Huawei Technologies Co., Ltd.

< Previous topicNext topic >

8.4.4.3.3 RRC Setup Success Rate

(Signaling) (CU)
Description
This KPI is used to evaluate the RRC connection setup success rate of signaling in a cell
or on the entire network. This KPI indicates the RRC setup success rate of the
signaling-related cause (mo-signaling).
This KPI is calculated by the gNodeB when the UE initiates an RRC connection setup
procedure. As shown at point A in Figure 1, the number of RRC connection setup
attempts due to signaling is incremented by 1 each time the gNodeB receives an
RRCSetupRequest message from the UE. As shown at point C, the number of
successful RRC connection setups due to signaling is incremented by 1.
 Figure 1 Measurement points for RRC connection setup

Definition
The RRC Setup Success Rate (Signaling) KPI is defined in Table 1.

Table 1 RRC Setup Success Rate (Signaling) (CU)

Name RRC Setup Success Rate (signaling) (CU)

Object Cell or radio network

Formula RRCS_SRsignaling = (RRCSetupSuccesssignaling/RRCSetupAttemptsignaling) x

100%

Associated RRC Setup Success Rate (Signaling) =

Counters (N.RRC.SetupReq.Succ.MoSig/N.RRC.SetupReq.Att.MoSig) x 100%

Unit %

Note None

Parent Topic: Accessibility KPIs

Copyright © Huawei Technologies Co., Ltd.
 Copyright © Huawei Technologies Co., Ltd.
< Previous topicNext topic >

8.4.4.3.4 NGSIG Connection Setup

Success Rate (CU)
Description
This KPI is used to evaluate the success rate of signaling connection setups over the NG
interface. This KPI includes counters such as the number of setup attempts of NG
signaling connections related to UEs and the number of successful setups of NG
signaling connections related to UEs.
The number of setup times of NG signaling connections related to UEs is incremented
by 1 each time when the gNodeB sends an INITIAL UE MESSAGE to the AMF or
receives the first NG message from the AMF. INITIAL UE MESSAGE is the first NG
message that the gNodeB sends to the AMF. It contains the NAS configuration
information related to UEs, based on which the AMF sets up NG signaling connections
for UEs. The first NG interface message received from the AMF may be an INITIAL
CONTEXT SETUP REQUEST, DOWNLINK NAS TRANSPORT, or UE CONTEXT
RELEASE COMMAND message. If the message is received, an NG signaling
connection is set up successfully.
As shown at point A in Figure 1, the number of NG signaling connection setup attempts
is incremented by 1 each time the gNodeB sends an INITIAL UE MESSAGE message
to the AMF.
As shown at point B in Figure 1, the number of successful NG signaling connection
setups is incremented by 1 each time the gNodeB sends an INITIAL UE MESSAGE
message to the AMF and receives the first NG message from the AMF.
 Figure 1 Measurement points for signaling connection setup

Definition
The NGSIG Connection Setup Success Rate KPI is defined in Table 1.

Table 1 NGSIG Connection Setup Success Rate (CU)

Name NGSIG Connection Setup Success Rate (CU)

Object Cell or radio network

Formula NGSIGS_SR =
(NGSIGConnectionEstablishSuccess/NGSIGConnectionEstablishAttempt)
x 100%

Associated NGSIG Connection Setup Success Rate =

Counters (N.NGSig.ConnEst.Succ/N.NGSig.ConnEst.Att) x 100%

Unit %

Note None
 Parent Topic: Accessibility KPIs
Copyright © Huawei Technologies Co., Ltd.

Copyright © Huawei Technologies Co., Ltd.

< Previous topicNext topic >

8.4.4.3.5 QoS Flow Setup Success Rate

(CU)
Description
This KPI is used to evaluate the QoS flow setup success rate of all services. The
involved counters include the number of QoS flow setup attempts and the number of
successful QoS flow setups.
1. As shown at point A in Figure 1, Figure 2, and Figure 3, the number of QoS flow setup
attempts is incremented by 1 each time the gNodeB receives an INITIAL CONTEXT
SETUP REQUEST, PDU SESSION RESOURCE SETUP REQUEST, or PDU
SESSION RESOURCE MODIFY REQUEST message from the AMF. If the INITIAL
CONTEXT SETUP REQUEST, PDU SESSION RESOURCE SETUP REQUEST, or
PDU SESSION RESOURCE MODIFY REQUEST message requests the setup of
multiple QoS flows, the number of QoS flow setup attempts is incremented by the
number of QoS flow setups.
2. As shown in Figure 1 and Figure 2, the number of successful QoS flow setups is
incremented by 1 each time the gNodeB sends a PDU SESSION RESOURCE SETUP
RESPONSE, INITIAL CONTEXT SETUP RESPONSE, or PDU SESSION
RESOURCE MODIFY RESPONSE message to the AMF. If the PDU SESSION
RESOURCE SETUP RESPONSE, INITIAL CONTEXT SETUP RESPONSE, or PDU
SESSION RESOURCE MODIFY RESPONSE message contains multiple QoS flow
setup success results, the total number of successful QoS flow setups is accumulated
based on the number in the message.
These counters are accumulated in the cell serving the UE.
Figure 1 Measurement points for initial context setup

Figure 2 Measurement points for PDU session setup

 Figure 3 Measurement points for PDU session modification

Definition
Table 1lists the definition of the QoS flow setup success rate of all services. For details
about how to measure the number of QoS flow setup attempts and the number of
successful setups, see "Description" in this section.

Table 1 Qos Flow Setup Success Rate (CU)

Name Qos Flow Setup Success Rate (CU)

Object Cell or radio network

Formula Qos FlowS_SR = (QosFlowSetupSuccess/QosFlowSetupAttempt) x

100%

Associated QoS Flow Setup Success Rate = (N.QosFlow.Est.Succ/N.QosFlow.Est.Att) ×

Counters 100%

Unit %

Note None

Parent Topic: Accessibility KPIs

Copyright © Huawei Technologies Co., Ltd.
 Copyright © Huawei Technologies Co., Ltd.
< Previous topicNext topic >

8.4.4.3.6 Call Setup Success Rate (CU)

Description
This KPI is used to evaluate the call setup success rate of all services, including the
RRC connection setup success rate for services, NG signaling connection setup success
rate, and QoS flow setup success rate.

Definition
The Call Setup Success Rate KPI is defined in Table 1. This KPI is the product of the
RRC connection setup success rate for services, NG signaling connection setup success
rate, and QoS flow setup success rate.

Table 1 Call Setup Success Rate

Name Call Setup Success Rate (CU)

Object Cell / Radio Network (CU)

Formula CSSR = (RRCSetupSuccessservice/RRCSetupAttemptservice) x

(NGSIGConnectionEstablishSuccess/NGSIGConnectionEstablishAttempt)
x (QosFlowSetupSuccess/QosFlowSetupAttempt) x 100%

Associated Call Setup Success Rate = ((N.RRC.SetupReq.Succ.Emc +

Counters N.RRC.SetupReq.Succ.HighPri + N.RRC.SetupReq.Succ.Mt +
N.RRC.SetupReq.Succ.MoData + N.RRC.SetupReq.Succ.MoVoiceCall +
N.RRC.SetupReq.Succ.MpsPri + N.RRC.SetupReq.Succ.MoSms +
N.RRC.SetupReq.Succ.MoVideoCall)/(N.RRC.SetupReq.Att.Emc +
N.RRC.SetupReq.Att.HighPri + N.RRC.SetupReq.Att.Mt + N.RRC.SetupReq.Att.MoData
+ N.RRC.SetupReq.Att.MoVoiceCall + N.RRC.SetupReq.Att.MpsPri +
N.RRC.SetupReq.Att.MoSms + N.RRC.SetupReq.Att.MoVideoCall)) x
(N.NGSig.ConnEst.Succ/N.NGSig.ConnEst.Att) x
(N.QosFlow.Est.Succ/N.QosFlow.Est.Att) x 100%

Unit %

Note None

Parent Topic: Accessibility KPIs

Copyright © Huawei Technologies Co., Ltd.

Copyright © Huawei Technologies Co., Ltd.

 < Previous topic

8.4.4.4 Retainability KPIs

Retainability KPIs are used to evaluate network's capability to retain services of UEs in
connected mode on the network and indicate whether the system can maintain the
service quality at a certain level.

NOTE:
Retainability KPIs, such as the service drop rate, are not defined because protocols are not
specified. The definition of 5G retainability KPIs will be provided after the standards are
specified in protocols.

Parent Topic: 5G RAN KPI Reference

Copyright © Huawei Technologies Co., Ltd.

Copyright © Huawei Technologies Co., Ltd.

< Previous topicNext topic >

8.4.4.5 Mobility KPIs

Mobility KPIs are used to evaluate the mobility performance of the NR network, which
is critical to user experience. Three categories of mobility KPIs are defined based on the
following handover types: intra-RAT intra-frequency, intra-RAT inter-frequency, and
inter-RAT.
Intra-Frequency Handover Out Success Rate (CU)
Intra-RAT Handover In Success Rate (CU)
Inter-RAT Handover Out Success Rate (NR to LTE) (CU)

Parent Topic: 5G RAN KPI Reference

Copyright © Huawei Technologies Co., Ltd.

Copyright © Huawei Technologies Co., Ltd.

< Previous topicNext topic >

8.4.4.5.1 Intra-Frequency Handover Out

Success Rate (CU)
Description
This KPI indicates the success rate of intra-NR intra-frequency outgoing handovers.
The intra-frequency outgoing handovers are classified into intra- and inter-gNodeB
outgoing handovers.
Intra-gNodeB Outgoing Handover
Intra-gNodeB outgoing handovers can be further classified into handovers with RRC
connection reestablishment and handovers without RRC connection reestablishment.
 Intra-gNodeB outgoing handovers without RRC connection reestablishment
As shown in Figure 1, the source cell and the target cell operate at the same frequency.
At point B, when the gNodeB sends an RRC Reconfiguration message carrying the
handover command to the UE, the gNodeB counts the number of intra-gNodeB intra-
frequency outgoing handover execution attempts in the source cell. At point C, when
the gNodeB receives an RRC Reconfiguration Complete message from the UE,
which indicates that the handover is complete, the gNodeB counts the number of
successful intra-gNodeB intra-frequency outgoing handover executions in the source
cell.
Figure 1 Intra-gNodeB outgoing handovers without RRC connection
reestablishment

 Intra-gNodeB outgoing handovers with RRC connection reestablishment

As shown in Figure 2, the source cell and the target cell operate at the same frequency.
At point B, when the gNodeB sends an RRC Reconfiguration message carrying the
handover command to the UE, the gNodeB counts the number of intra-gNodeB intra-
frequency outgoing handover execution attempts in the source cell. At point C, when
the gNodeB receives an RRC Reestablishment Complete message from the UE, the
gNodeB counts the number of successful intra-gNodeB intra-frequency outgoing
handover executions in the source cell.
 Figure 2 Intra-gNodeB outgoing handovers with RRC connection reestablishment

Inter-gNodeB Outgoing Handover

Inter-gNodeB outgoing handovers can be further classified into handover without
RRC connection reestablishment, handover with RRC connection reestablishment to
the target cell, and handover with RRC connection reestablishment to the source cell.
 Inter-gNodeB outgoing handover without RRC connection reestablishment
As shown in Figure 3 and Figure 4, the source cell and target cell operate at the same
frequency. When the source gNodeB sends an RRC Reconfiguration message
containing the handover command to the UE, the source gNodeB counts the number
of intra-frequency outgoing handover execution attempts in the source cell at point
B. When the source gNodeB receives a UE CONTEXT RELEASE message from the
target gNodeB or receives a UE CONTEXT RELEASE COMMAND message from
the AMF, indicating that the UE successfully accesses the target cell, the source
gNodeB counts the number of successful intra-frequency outgoing handover
executions in the source cell at point C.
 Figure 3 Xn-based inter-gNodeB outgoing handover without RRC connection
reestablishment

Figure 4 NG-based inter-gNodeB outgoing handover without RRC connection

reestablishment

 Inter-gNodeB outgoing handover with RRC connection reestablishment to the target

cell
As shown in Figure 5 and Figure 6, the source cell and target cell operate at the same
frequency. When the source gNodeB sends an RRC Reconfiguration message
containing the handover command to the UE, the source gNodeB counts the number
of intra-frequency outgoing handover execution attempts in the source cell at point
 B. When the source gNodeB receives a UE CONTEXT RELEASE message from the
target gNodeB or receives a UE CONTEXT RELEASE COMMAND message from
the AMF, indicating that the UE successfully accesses the target cell, the source
gNodeB counts the number of successful intra-frequency outgoing handover
executions in the source cell at point C.
Figure 5 Xn-based inter-gNodeB outgoing handover with RRC connection
reestablishment to the target cell

Figure 6 NG-based inter-gNodeB outgoing handover with RRC connection

reestablishment to the target cell

 Inter-gNodeB outgoing handover with RRC connection reestablishment to the source

cell
As shown in Figure 7 and Figure 8, the source cell and target cell operate at the same
frequency. At point B, when the source gNodeB sends an RRC Reconfiguration
message carrying the handover command to the UE, the source gNodeB counts the
number of intra-frequency outgoing handover execution attempts in the source cell.
At point C, when the source gNodeB receives an RRC Reestablishment Complete
message from the UE, the source gNodeB counts the number of successful intra-
frequency outgoing handover executions in the source cell.
Figure 7 Xn-based inter-gNodeB outgoing handover with RRC connection
reestablishment to the source cell
 Figure 8 NG-based inter-gNodeB outgoing handover with RRC connection
reestablishment to the source cell

Definition
The Intra-Frequency Handover Out Success Rate KPI is defined in Table 1. The number
of outgoing handover execution attempts and the number of successful outgoing
handover executions are collected based on the description in "Description" in this
section.

Table 1 Intra-frequency Handover Out Success Rate (CU)

Name Intra-frequency Handover Out Success Rate (CU)

Object Cell or radio network

Formula IntraFreqHOOut_SR =
(IntraFreqHOOutSuccess/IntraFreqHOOutAttempt) x 100%

Associated Intra-Frequency Handover Out Success Rate =

Counters ((N.HO.IntraFreq.Ng.IntergNB.ExecSuccOut +
N.HO.IntraFreq.Xn.IntergNB.ExecSuccOut +
N.HO.IntraFreq.IntragNB.ExecSuccOut)/(N.HO.IntraFreq.Ng.IntergNB.ExecAttOut +
N.HO.IntraFreq.IntragNB.ExecAttOut + N.HO.IntraFreq.Xn.IntergNB.ExecAttOut)) x
100%
 Unit %

Note None

Parent Topic: Mobility KPIs

Copyright © Huawei Technologies Co., Ltd.

Copyright © Huawei Technologies Co., Ltd.

Next topic >

8.4.4.5.2 Intra-RAT Handover In Success

Rate (CU)
Description
This KPI indicates the success rate of intra-NR incoming handovers. The intra-NR
incoming handovers are classified into intra- and inter-gNodeB incoming handovers.
Intra-gNodeB Incoming Handover
Intra-gNodeB incoming handovers can be further classified into handovers with RRC
connection reestablishment and handovers without RRC connection reestablishment.
 Intra-gNodeB incoming handovers without RRC connection reestablishment
Figure 1illustrates an intra-gNodeB incoming handover without RRC connection
reestablishment. When the gNodeB sends an RRC Reconfiguration message
containing the handover command to the UE, the gNodeB counts the number of
intra-gNodeB incoming handover execution attempts in the target cell at point B.
When the gNodeB receives an RRC Reconfiguration Complete message from the
UE, indicating that the handover finishes, the gNodeB counts the number of
successful intra-gNodeB incoming handover executions in the target cell at point C.
 Figure 1 Intra-gNodeB incoming handovers without RRC connection
reestablishment

 Intra-gNodeB incoming handovers with RRC connection reestablishment

Figure 2illustrates an intra-gNodeB incoming handover without RRC connection
reestablishment. When the gNodeB sends an RRC Reconfiguration message
containing the handover command to the UE, the gNodeB counts the number of
intra-gNodeB incoming handover execution attempts in the target cell at point B.
When the gNodeB receives an RRC Reestablishment Complete message from the
UE, the gNodeB counts the number of successful intra-gNodeB incoming handover
executions in the target cell at point C.
 Figure 2 Intra-gNodeB incoming handovers with RRC connection reestablishment

Inter-gNodeB Incoming Handover

Inter-gNodeB incoming handovers can be further classified into handovers with RRC
connection reestablishment and handovers without RRC connection reestablishment.
 Inter-gNodeB incoming handovers without RRC connection reestablishment
As shown in Figure 3 and Figure 4, when the target gNodeB sends a Handover Request
Acknowledge message to the source gNodeB or AMF, the target gNodeB counts the
number of incoming handover execution attempts in the target cell at point B. When
the target gNodeB receives an RRC Reconfiguration Complete message from the UE
and sends a UE Context Release message to the source gNodeB over the Xn
interface or sends a Handover Notify message to the AMF over the NG interface to
instruct the source gNodeB to release the UE context, the target gNodeB counts the
number of successful incoming handover executions in the target cell at point C.
Figure 3 Xn-based inter-gNodeB incoming handover without RRC connection
reestablishment

Figure 4 NG-based inter-gNodeB incoming handover without RRC connection

reestablishment

 Inter-gNodeB incoming handover with RRC connection reestablishment to the target

cell
Figure 5illustrates Xn-based inter-gNodeB incoming handover with RRC connection
reestablishment to the target cell. When the target gNodeB sends a Handover
Request Acknowledge message to the source gNodeB or AMF, the target gNodeB
counts the number of incoming handover execution attempts in the target cell at
point B. When the target gNodeB receives an RRC Reestablishment Complete
message from the UE and sends a UE CONTEXT RELEASE message to the source
 gNodeB over the Xn interface to instruct the source gNodeB to release the UE
context, the target gNodeB counts the number of successful incoming handover
executions in the target cell at point C.
Figure 5 Xn-based inter-gNodeB incoming handover with RRC connection
reestablishment to the target cell

Figure 6illustrates NG-based inter-gNodeB incoming handover with RRC connection

reestablishment to the target cell. When the target gNodeB sends a Handover Request
Acknowledge message to the source gNodeB or AMF, the target gNodeB counts the
number of incoming handover execution attempts in the target cell at point B. When the
target gNodeB receives an RRC Reestablishment Complete message from the UE and
sends a Handover Notify message to the AMF over the NG interface to instruct the
source gNodeB to release the UE context, the target gNodeB counts the number of
successful incoming handover executions in the target cell at point C.
 Figure 6 NG-based inter-gNodeB incoming handover with RRC connection
reestablishment to the target cell

Definition
The Intra-RAT Handover In Success Rate KPI is defined in Table 1.

Table 1 Intra-RAT Handover In Success Rate (CU)

Name Intra-RAT Handover In Success Rate (CU)

Object Cell or radio network

Formula Intra-RATHOIn_SR = (Intra-RATHOInSuccess/Intra-

RATHOInAttempt) x 100%

Associated Intra-RAT Handover In Success Rate = ((N.HO.Ng.IntergNB.ExecSuccIn +

Counters N.HO.IntragNB.ExecSuccIn +
N.HO.Xn.IntergNB.ExecSuccIn)/(N.HO.Ng.IntergNB.ExecAttIn +
N.HO.IntragNB.ExecAttIn + N.HO.Xn.IntergNB.ExecAttIn)) x 100%

Unit %

Note None

Parent Topic: Mobility KPIs

Copyright © Huawei Technologies Co., Ltd.

Copyright © Huawei Technologies Co., Ltd.

< Previous topicNext topic >
 8.4.4.5.3 Inter-RAT Handover Out
Success Rate (NR to LTE) (CU)
Description
This KPI indicates the inter-RAT outgoing handover success rate from NR to LTE.
The number of NR-to-LTE outgoing handover execution attempts is incremented by 1
as shown in Figure 1 after the gNodeB sends a HANDOVER COMMAND message to
the UE. The number of successful NR-to-LTE outgoing handover executions is
incremented by 1 at point C when the gNodeB receives a UE CONTEXT RELEASE
COMMAND message from the AMF after the UE accesses the LTE network.
Figure 1 Inter-RAT handover (NR to LTE)

Definition
The Inter-RAT Handover Out Success Rate (NR to LTE) KPI is defined in Table 1.

Table 1 Inter-RAT Handover Out Success Rate (NR to LTE) (CU)

Name Inter-RAT Handover Out Success Rate (NR to LTE) (CU)

Object Cell or radio network

 Formula IRATHO_N2E_SR = (IRATHO_N2E_Success/IRATHO_N2E_Attempt)
x 100%

Associated Inter-RAT Handover Out Success Rate (NR to LTE) =

Counters (N.HO.InterRAT.N2E.ExecSuccOut)/(N.HO.InterRAT.N2E.ExecAttOut) x 100%

Unit %

Note If the failure caused by the core network is not calculated in some
scenarios, the following formula can be used:
Inter-RAT Handover Out Success Rate (NR to LTE) =
(N.HO.InterRAT.N2E.ExecSuccOut –
N.HO.InterRAT.N2E.AMFAbnormRsp)/(N.HO.InterRAT.N2E.ExecAttOut) x 100%

Parent Topic: Mobility KPIs

Copyright © Huawei Technologies Co., Ltd.

Copyright © Huawei Technologies Co., Ltd.

< Previous topic

8.4.4.6 Service Integrity KPIs

Service integrity KPIs are used to evaluate the service quality of end-users in the 5G
RAN.
User Downlink Average Throughput (DU)
User Uplink Average Throughput (DU)
Cell Downlink Average Throughput (DU)
Cell Uplink Average Throughput (DU)

Parent Topic: 5G RAN KPI Reference

Copyright © Huawei Technologies Co., Ltd.

Copyright © Huawei Technologies Co., Ltd.

< Previous topicNext topic >

8.4.4.6.1 User Downlink Average

Throughput (DU)
Description
This KPI indicates the average downlink UE throughput in a cell.

Definition
 The User Downlink Average Throughput KPI is defined in Table 1 and is calculated
based on the total traffic volume and data transmission duration of a UE in the downlink
when the tail packet transmission is not counted.

Table 1 User Downlink Average Throughput (DU)

Name User Downlink Average Throughput (DU)

Object Cell or radio network

Formula UserDLAveThp =
UserDLRmvLastSlotTrafficVolume/UserDLRmvLastSlotTransferTime

Associated User Downlink Average Throughput = (N.ThpVol.DL –

Counters N.ThpVol.DL.LastSlot)/N.ThpTime.DL.RmvLastSlot

Unit Gbit/s

Note None

Parent Topic: Service Integrity KPIs

Copyright © Huawei Technologies Co., Ltd.

Copyright © Huawei Technologies Co., Ltd.

Next topic >

8.4.4.6.2 User Uplink Average

Throughput (DU)
Description
This KPI indicates the average uplink UE throughput in a cell.

Definition
The User Uplink Average Throughput KPI is defined in Table 1 and is calculated based
on the total traffic volume and data transmission duration of a UE in the uplink when
the small packet transmission is not counted.

Table 1 User Uplink Average Throughput (DU)

Name User Uplink Average Throughput (DU)

Object Cell or radio network

 Formula UserULAveThp =
UserULRmvSmallPktTrafficVolume/UserULRmvSmallPktTransferTime

Associated User Uplink Average Throughput = (N.ThpVol.UL –

Counters N.ThpVol.UE.UL.SmallPkt)/N.ThpTime.UE.UL.RmvSmallPkt

Unit Gbit/s

Note None

Parent Topic: Service Integrity KPIs

Copyright © Huawei Technologies Co., Ltd.

Copyright © Huawei Technologies Co., Ltd.

< Previous topicNext topic >

8.4.4.6.3 Cell Downlink Average

Throughput (DU)
Description
This KPI indicates the average downlink cell throughput, which reflects the cell
capacity in the downlink.

Definition
The Cell Downlink Average Throughput KPI is defined in Table 1 and is calculated
based on the total traffic volume and data transmission duration in the downlink of a
cell.

Table 1 Cell Downlink Average Throughput (DU)

Name Cell Downlink Average Throughput (DU)

Object Cell or radio network

Formula CellDLAveThp = CellDLTrafficVolume/CellDLTransferTime

Associated Cell Downlink Average Throughput = N.ThpVol.DL.Cell/N.ThpTime.DL.Cell

Counters

Unit Gbit/s

Note None
 Parent Topic: Service Integrity KPIs
Copyright © Huawei Technologies Co., Ltd.

Copyright © Huawei Technologies Co., Ltd.

< Previous topicNext topic >

8.4.4.6.4 Cell Uplink Average

Throughput (DU)
Description
This KPI indicates the average uplink cell throughput, which reflects the cell capacity in
the uplink.

Definition
The Cell Uplink Average Throughput KPI is defined in Table 1 and is calculated based
on the total traffic volume and data transmission duration in the uplink of a cell.

Table 1 Cell Uplink Average Throughput (DU)

Name Cell Uplink Average Throughput (DU)

Object Cell or radio network

Formula CellULAveThp = CellULTrafficVolume/CellULTransferTime

Associated Cell Uplink Average Throughput = N.ThpVol.UL.Cell/N.ThpTime.UL.Cell

Counters

Unit Gbit/s

Note None

Parent Topic: Service Integrity KPIs

Copyright © Huawei Technologies Co., Ltd.

Copyright © Huawei Technologies Co., Ltd.

< Previous topic

8.4.4.7 Utilization KPIs

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

Parent Topic: 5G RAN KPI Reference

Copyright © Huawei Technologies Co., Ltd.

Copyright © Huawei Technologies Co., Ltd.

< Previous topicNext topic >

8.4.4.7.1 Downlink Resource Block

Utilizing Rate (DU)
Description
This KPI indicates the busy-hour downlink RB usage in each cell or network.

Definition
The Downlink Resource Block Utilizing Rate KPI is defined in Table 1.

Table 1 Downlink Resource Block Utilizing Rate (DU)

Name Downlink Resource Block Utilizing Rate (DU)

Object Cell or radio network

Formula RB_URDL = (RB_UsedDL/RB_AvailableDL) x 100%

Associated Downlink Resource Block Utilizing Rate =

Counters (N.PRB.DL.Used.Avg/N.PRB.DL.Avail.Avg) x 100%

Unit %

Note None

Parent Topic: Utilization KPIs

Copyright © Huawei Technologies Co., Ltd.

Copyright © Huawei Technologies Co., Ltd.

Next topic >

8.4.4.7.2 Uplink Resource Block Utilizing

Rate (DU)
Description
This KPI indicates the busy-hour uplink RB usage in each cell or network.

Definition
The Uplink Resource Block Utilizing Rate KPI is defined in Table 1.

Table 1 Uplink Resource Block Utilizing Rate (DU)

Name Uplink Resource Block Utilizing Rate (DU)

Object Cell or radio network

Formula RB_URUL = (RB_UsedUL/RB_AvailableUL) x 100%

Associated Uplink Resource Block Utilizing Rate =

Counters (N.PRB.UL.Used.Avg/N.PRB.UL.Avail.Avg) x 100%

Unit %

Note None

Parent Topic: Utilization KPIs

Copyright © Huawei Technologies Co., Ltd.

Copyright © Huawei Technologies Co., Ltd.

< Previous topicNext topic >

8.4.4.7.3 Average CPU Load

Description
This KPI indicates the CPU usage during busy hours.

Definition
The Average CPU Load KPI is defined in Table 1.

Table 1 Average CPU Load

Name Average CPU Load

Object CPU

Formula MeanCPUUtility
 Associated Average CPU Load = VS.BBUBoard.CPULoad.Mean
Counter

Unit %

Note None

Parent Topic: Utilization KPIs

Copyright © Huawei Technologies Co., Ltd.

Copyright © Huawei Technologies Co., Ltd.

< Previous topic

8.4.4.8 Availability KPIs

A cell is available when the gNodeB can provide EPS bearer services.
Radio Network Unavailability Rate (CU)

Parent Topic: 5G RAN KPI Reference

Copyright © Huawei Technologies Co., Ltd.

Copyright © Huawei Technologies Co., Ltd.

< Previous topicNext topic >

8.4.4.8.1 Radio Network Unavailability

Rate (CU)
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 cell unavailability of the radio network during busy
hours.

Definition
The Radio Network Unavailability Rate KPI is defined in Table 1. This KPI is calculated
based on the length of time all cell services are unavailable on the radio network.

Table 1 Radio Network Unavailability Rate

Name Radio Network Unavailability Rate

Object Radio network

 Formula RAN_Unavail_Rate =
(ΣCellUnavailTime/(TheTotalNumberOfCellsInCluster x {SP} × 60)) x
100%

Associated Radio Network Unavailability Rate = ((N.Cell.Unavail.Dur.System +

Counters N.Cell.Unavail.Dur.Manual)/(Number of cells x {SP} x 60)) x 100%
SP indicates the reporting period for counters in minutes.

Unit %

Note None

Parent Topic: Availability KPIs

Copyright © Huawei Technologies Co., Ltd.

Copyright © Huawei Technologies Co., Ltd.

8.4.4.9 Traffic KPIs

Traffic KPIs are used to measure the traffic volume in the 5G RAN. The traffic KPIs are
classified into downlink traffic volume, uplink traffic volume, and user number.
Downlink Traffic Volume (DU)
Uplink Traffic Volume (DU)
Average User Number (CU)
Maximum User Number

Parent Topic: 5G RAN KPI Reference

Copyright © Huawei Technologies Co., Ltd.

Copyright © Huawei Technologies Co., Ltd.

< Previous topicNext topic >

8.4.4.9.1 Downlink Traffic Volume (DU)

Description
This KPI is used to evaluate the downlink traffic volume in a cell, which is measured at
the Radio Link Control (RLC) layer.

Definition
The Downlink Traffic Volume KPI is defined in Table 1.

Table 1 Downlink Traffic Volume (DU)

 Name Downlink Traffic Volume (DU)

Object Cell or radio network

Formula DLTrafficVolume

Associated Downlink Traffic Volume = N.ThpVol.DL

Counters

Unit kbit

Note None

Parent Topic: Traffic KPIs

Copyright © Huawei Technologies Co., Ltd.

Copyright © Huawei Technologies Co., Ltd.

Next topic >

8.4.4.9.2 Uplink Traffic Volume (DU)

Definition
This KPI is used to evaluate the uplink traffic volume in a cell, which is measured at the
RLC layer.

Description
The Uplink Traffic Volume KPI is defined in Table 1.

Table 1 Uplink Traffic Volume (DU)

Name Uplink Traffic Volume (DU)

Object Cell or radio network

Formula ULTraffic Volume

Associated Uplink Traffic Volume = N.ThpVol.UL

Counters

Unit kbit

Note None

Parent Topic: Traffic KPIs

 Copyright © Huawei Technologies Co., Ltd.

Copyright © Huawei Technologies Co., Ltd.

< Previous topicNext topic >

8.4.4.9.3 Average User Number (CU)

Description
This KPI indicates the average number of UEs in RRC_CONNECTED mode in a cell.
The gNodeB samples and records the number of UEs every second and then calculates
the average value of these samples in each measurement period.

Definition
The Average User Number KPI is defined in Table 1.

Table 1 Average User Number (CU)

Name Average User Number (CU)

Object Cell or radio network

Formula AvgUserNumber

Associated Average User Number =N.User.RRCConn.Avg

Counters

Unit N/A

Note None

Parent Topic: Traffic KPIs

Copyright © Huawei Technologies Co., Ltd.

Copyright © Huawei Technologies Co., Ltd.

< Previous topicNext topic >

8.4.4.9.4 Maximum User Number

Description
This KPI indicates the maximum number of UEs in RRC_CONNECTED mode in a
cell. The gNodeB samples and records the number of UEs every second and then
calculates the maximum value of these samples in each measurement period.
Definition
The Maximum User Number KPI is defined in Table 1.

Table 1 Maximum User Number

Name Maximum User Number

Object Cell or radio network

Formula MaxUserNumber

Associated Maximum User Number = N.User.RRCConn.Max

Counters

Unit N/A

Note None

Parent Topic: Traffic KPIs

Copyright © Huawei Technologies Co., Ltd.

Copyright © Huawei Technologies Co., Ltd.

< Previous topic

8.4.4.10 NSA DC Accessibility and

Mobility KPIs
NSA DC accessibility and mobility KPIs are used to measure the success rates of SgNB
addition, intra-SgNB cell change, and inter-SgNB cell change in NSA DC scenarios.
The KPIs are also used to measure the abnormal SgNB releases.
SgNB Addition Success Rate
Intra-SgNB PSCell Change Success Rate
Inter-SgNB PSCell Change Success Rate
SgNB-Triggered Abnormal SgNB Release Rate

Parent Topic: 5G RAN KPI Reference

Copyright © Huawei Technologies Co., Ltd.

Copyright © Huawei Technologies Co., Ltd.

< Previous topicNext topic >

8.4.4.10.1 SgNB Addition Success Rate

Description
 This KPI is used to evaluate the SgNB addition success rate in NSA DC scenarios. For
details about SgNB addition procedures, see 3GPP TS 37.340. The number of SgNB
addition attempts is measured at point A in Figure 1, and the number of successful SgNB
additions is measured at point B in Figure 1.
Figure 1 Measurement points of SgNB addition in NSA DC scenarios

Definition
The SgNB Addition Success Rate KPI is defined in Table 1.

Table 1 SgNB Addition Success Rate

Name SgNB Addition Success Rate

Object Cell or radio network

Formula SgNBAdd_SR = (SgNBAdditionSuccess/SgNBAdditionAttempt) x

100%

Associated SgNB Addition Success Rate =

Counters (N.NsaDc.SgNB.Add.Succ/N.NsaDc.SgNB.Add.Att) x 100%

Unit %

Note None

Parent Topic: NSA DC Accessibility and Mobility KPIs

Copyright © Huawei Technologies Co., Ltd.

Copyright © Huawei Technologies Co., Ltd.

Next topic >
 8.4.4.10.2 Intra-SgNB PSCell Change
Success Rate
Definition

This KPI is used to evaluate the intra-SgNB cell change success rate in NSA DC
scenarios. For details about intra-SgNB cell change procedures, see 3GPP TS 37.340.
The number of intra-SgNB cell change attempts is measured at point A in Figure 1, and
the number of successful intra-SgNB cell changes is measured at point B in Figure 1.
Figure 1 Measurement points of intra-SgNB cell change in NSA DC scenarios

Description
The Intra-SgNB PSCell Change Success Rate KPI is defined in Table 1.

Table 1 Intra-SgNB PSCell Change Success Rate

Name Intra-SgNB PSCell Change Success Rate

Object Cell or radio network

Formula IntraSgNBPscellChange_SR =
(IntraSgNBPscellChangeSuccess/IntraSgNBPscellChangeAttempt) x
100%

Associated Intra-SgNB PSCell Change Success Rate =

Counters (N.NsaDc.IntraSgNB.PSCell.Change.Succ/N.NsaDc.IntraSgNB.PSCell.Change.Att) x
100%

Unit %
 Note None

Parent Topic: NSA DC Accessibility and Mobility KPIs

Copyright © Huawei Technologies Co., Ltd.

Copyright © Huawei Technologies Co., Ltd.

< Previous topicNext topic >

8.4.4.10.3 Inter-SgNB PSCell Change

Success Rate
Description

This KPI is used to evaluate the inter-SgNB cell change success rate in NSA DC
scenarios. For details about inter-SgNB cell change procedures, see 3GPP TS 37.340.
The number of inter-SgNB cell change attempts is measured at point A in Figure 1, and
the number of successful inter-SgNB cell changes is measured at point B in Figure 1.
Figure 1 Measurement points of inter-SgNB cell change in NSA DC scenarios

Definition
The Inter-SgNB PSCell Change Success Rate KPI is defined in Table 1.

Table 1 Inter-SgNB PSCell Change Success Rate

Name Inter-SgNB PSCell Change Success Rate

Object Cell or radio network

 Formula InterSgNBPscellChange_SR =
(InterSgNBPscellChangeSuccess/InterSgNBPscellChangeAttempt) x
100%

Associated Inter-SgNB PSCell Change Success Rate =

Counters (N.NsaDc.InterSgNB.PSCell.Change.Succ/N.NsaDc.InterSgNB.PSCell.Change.Att) x
100%

Unit %

Note None

Parent Topic: NSA DC Accessibility and Mobility KPIs

Copyright © Huawei Technologies Co., Ltd.

Copyright © Huawei Technologies Co., Ltd.

< Previous topicNext topic >

8.4.4.10.4 SgNB-Triggered Abnormal

SgNB Release Rate
Description
This KPI is used to evaluate abnormal SgNB releases triggered by the SgNB in NSA
DC scenarios. For details about SgNB release procedures, see 3GPP TS 37.340.

Definition
The SgNB-Triggered Abnormal SgNB Release Rate KPI is defined in Table 1.

Table 1 SgNB-Triggered Abnormal SgNB Release Rate

Name SgNB-Triggered Abnormal SgNB Release Rate

Object Cell or radio network

Formula SgNBTriSgNBAbnormalReleaseRate =
(SgNBTriSgNBAbnormalRelease/SgNBRelease) x 100%

Associated SgNB-Triggered Abnormal SgNB Release Rate =

Counters (N.NsaDc.SgNB.AbnormRel/N.NsaDc.SgNB.Rel) x 100%

Unit %

Note None
Parent Topic: NSA DC Accessibility and Mobility KPIs
Copyright © Huawei Technologies Co., Ltd.

Copyright © Huawei Technologies Co., Ltd.

< Previous topic

8.4.4.11 Reference Documents

[1] gNodeB performance counter reference
Parent Topic: 5G RAN KPI Reference
Copyright © Huawei Technologies Co., Ltd.

Copyright © Huawei Technologies Co., Ltd.

< Previous topic