5G RAN KPI Reference (V100R016C10 - 02) (PDF) - EN

5G RAN3.
1
V100R016C10
KPI Reference
Issue 02
Date 2020-05-21
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2020. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior
written consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
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.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: https://www.huawei.com
Email: support@huawei.com
Issue 02 (2020-05-21) Copyright © Huawei Technologies Co., Ltd. i

5G RAN3.1
KPI Reference Contents
Contents
1 5G RAN KPI Reference............................................................................................................ 1

1.1 Changes in 5G RAN KPI Reference.................................................................................................................................... 2
1.2 Accessibility KPIs...................................................................................................................................................................... 4
1.2.1 RRC Setup Success Rate (CU).......................................................................................................................................... 4
1.2.2 RRC Setup Success Rate (CU, Inactive)........................................................................................................................ 5
1.2.3 RRC Setup Success Rate (Service) (CU)....................................................................................................................... 8
1.2.4 RRC Setup Success Rate (Service) (CU, Inactive)................................................................................................... 10
1.2.5 RRC Setup Success Rate (Signaling) (CU)................................................................................................................ 13
1.2.6 RRC Setup Success Rate (Signaling) (CU, Inactive)............................................................................................... 14
1.2.7 NGSIG Connection Setup Success Rate (CU)........................................................................................................... 16
1.2.8 QoS Flow Setup Success Rate (CU)............................................................................................................................ 18
1.2.9 QoS Flow Setup Success Rate (CU, Inactive)........................................................................................................... 21
1.2.10 QoS Flow Setup Success Rate (CU, VoNR).............................................................................................................25
1.2.11 Call Setup Success Rate (CU)......................................................................................................................................26
1.2.12 Call Setup Success Rate (CU, Inactive).................................................................................................................... 26
1.3 Retainability KPIs.................................................................................................................................................................. 28
1.3.1 Service Call Drop Rate (CU)...........................................................................................................................................28
1.3.2 Service Call Drop Rate (CU, Inactive)......................................................................................................................... 28
1.3.3 Call Drop Rate (CU, VoNR)............................................................................................................................................ 29
1.4 Mobility KPIs........................................................................................................................................................................... 29
1.4.1 Intra-Frequency Handover Out Success Rate (CU)............................................................................................... 30
1.4.2 Inter-Frequency Handover Out Success Rate (CU)................................................................................................36
1.4.3 Intra-RAT Handover In Success Rate (CU)............................................................................................................... 41
1.4.4 Inter-RAT Handover Out Success Rate (NR to LTE) (CU)....................................................................................45
1.4.5 EPSFB Success Rate Based Handover (NR to E-UTRAN) (CU).......................................................................... 47
1.5 Service Integrity KPIs........................................................................................................................................................... 49
1.5.1 User Downlink Average Throughput (DU)............................................................................................................... 49
1.5.2 User Uplink Average Throughput (DU)..................................................................................................................... 49
1.5.3 Cell Downlink Average Throughput (DU).................................................................................................................50
1.5.4 Cell Uplink Average Throughput (DU).......................................................................................................................50
1.6 Utilization KPIs....................................................................................................................................................................... 51
1.6.1 Downlink Resource Block Utilizing Rate (DU)........................................................................................................ 51
1.6.2 Uplink Resource Block Utilizing Rate (DU).............................................................................................................. 52
Issue 02 (2020-05-21) Copyright © Huawei Technologies Co., Ltd. ii

5G RAN3.1
KPI Reference Contents
1.6.3 Average CPU Load.............................................................................................................................................................52

1.7 Availability KPIs..................................................................................................................................................................... 53
1.7.1 Radio Network Availability Rate (CU)....................................................................................................................... 53
1.8 Traffic KPIs.............................................................................................................................................................................. 53
1.8.1 Downlink Traffic Volume (DU)..................................................................................................................................... 53
1.8.2 Uplink Traffic Volume (DU)........................................................................................................................................... 54
1.8.3 Average User Number (CU)...........................................................................................................................................54
1.8.4 Maximum User Number(CU)........................................................................................................................................ 55
1.9 NSA DC Accessibility and Mobility KPIs........................................................................................................................ 55
1.9.1 SgNB Addition Success Rate (CU)............................................................................................................................... 56
1.9.2 Intra-SgNB PSCell Change Success Rate (CU).........................................................................................................57
1.9.3 Intra-SgNB IntraFreq PSCell Change Success Rate (CU)..................................................................................... 58
1.9.4 Inter-SgNB PSCell Change Success Rate (CU)......................................................................................................... 59
1.9.5 Inter-SgNB IntraFreq PSCell Change Success Rate (CU)......................................................................................60
1.9.6 SgNB-Triggered SgNB Abnormal Release Rate (CU)............................................................................................ 61
1.9.7 SgNB Abnormal Release Rate (CU)............................................................................................................................ 61
1.10 Reference Documents....................................................................................................................................................... 62
Issue 02 (2020-05-21) Copyright © Huawei Technologies Co., Ltd. iii

5G RAN3.1
KPI Reference 1 5G RAN KPI Reference
1 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.
● 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
Product Name Solution Version Product Version
DBS3900 ● SRAN16.1 V100R016C10
DBS3900 LampSite ● 5G RAN3.1
DBS5900
DBS5900 LampSite
BTS3900
BTS5900
Issue 02 (2020-05-21) Copyright © Huawei Technologies Co., Ltd. 1

5G RAN3.1
Product Name Solution Version Product Version
BTS3900A
BTS5900A
BTS3900L
BTS5900L
BTS3900AL
BTS5900AL
Organization
5G RAN KPI Reference

1.1 Changes in 5G RAN KPI Reference
1.2 Accessibility KPIs
1.3 Retainability KPIs
1.4 Mobility KPIs
1.5 Service Integrity KPIs
1.6 Utilization KPIs
1.7 Availability KPIs
1.8 Traffic KPIs
1.9 NSA DC Accessibility and Mobility KPIs
1.10 Reference Documents
1.1 Changes in 5G RAN KPI Reference

This chapter describes the changes in 5G RAN KPI Reference.
02 (2020-05-21)
This is the second commercial release.
Compared with Issue 01 (2020-04-07), this issue does not include any new topics.
Compared with Issue 01 (2020-04-07), this issue includes the following changes.

5G RAN3.1
Topic Change Description
● 1.2.8 QoS Flow Setup Success Added counters related to emergency

Rate (CU) voice fallback and EPS fallback in the
● 1.2.9 QoS Flow Setup Success calculation formula.
Rate (CU, Inactive)
● 1.2.10 QoS Flow Setup Success
Rate (CU, VoNR)
● 1.2.11 Call Setup Success Rate
(CU)
● 1.2.12 Call Setup Success Rate
(CU, Inactive)
Compared with Issue 01 (2020-04-07), this issue does not exclude any topics.
01 (2020-04-07)
This is the first commercial release.
Compared with Draft B (2020-03-09), this issue does not include any new topics
or changes, or exclude any topics.
Draft B (2020-03-09)
This is a draft.
Compared with Draft A (2020-01-20), this issue includes the following new
information:
1.2.10 QoS Flow Setup Success Rate (CU, VoNR)
1.3.1 Service Call Drop Rate (CU)
1.3.3 Call Drop Rate (CU, VoNR)
Compared with Draft A (2020-01-20), this issue does not include any changes or
exclude any topics.
Draft A (2020-01-20)
This is a draft.
Compared with V100R015C10, this issue includes the following new topics:
1.2.2 RRC Setup Success Rate (CU, Inactive)
1.2.4 RRC Setup Success Rate (Service) (CU, Inactive)
1.2.6 RRC Setup Success Rate (Signaling) (CU, Inactive)
1.2.9 QoS Flow Setup Success Rate (CU, Inactive)
1.2.12 Call Setup Success Rate (CU, Inactive)

5G RAN3.1
1.3.2 Service Call Drop Rate (CU, Inactive)

1.4.2 Inter-Frequency Handover Out Success Rate (CU)
1.4.5 EPSFB Success Rate Based Handover (NR to E-UTRAN) (CU)
1.9.3 Intra-SgNB IntraFreq PSCell Change Success Rate (CU)
1.9.5 Inter-SgNB IntraFreq PSCell Change Success Rate (CU)
1.9.7 SgNB Abnormal Release Rate (CU)
Compared with V100R015C10, this issue does not include any changes or exclude
any topics.
1.2 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.
1.2.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
causes 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-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.

5G RAN3.1
Figure 1-1 Measurement points for RRC connection setup
Definition
The RRC Setup Success Rate (CU) KPI is defined in Table 1-1.
Table 1-1 RRC Setup Success Rate (CU)

Name RRC Setup Success Rate (CU)
Object Cell or RAN
Formula RRC_SSR = RRCSetupSuccess/RRCSetupAttempt x 100%
Associated RRC Setup Success Rate (CU) = N.RRC.SetupReq.Succ/

Counters N.RRC.SetupReq.Att x 100%
Unit %
Note None
1.2.2 RRC Setup Success Rate (CU, Inactive)

Description
If the RRC_INACTIVE_SWITCH option is selected and a UE does not perform data
transmission for a period of time, the UE transits from the RRC_CONNECTED state
to the RRC_INACTIVE state instead of entering the RRC_IDLE state. As a result, the
number of RRC connection setup attempts and the number of successful RRC
connection setups decrease significantly, affecting the RRC connection setup
success rate and QoS flow setup success rate.
From the perspective of UEs, the RRC connection resume procedure from
RRC_INACTIVE to RRC_CONNECTED for UEs in the RRC_INACTIVE state is

5G RAN3.1
equivalent to the RRC connection setup procedure and QoS flow setup procedure.
Therefore, the number of RRC connection resumes from RRC_INACTIVE to
RRC_CONNECTED is added to the KPI formula.
As defined in 3GPP TS 38.331, the RRC connection setup or RRC connection
resume procedure is triggered by multiple causes. The upper layer determines the
cause value for the RRC connection setup or RRC connection resume initiated by
the UE. The RRC connection setup or RRC connection resume for the cause value
of mo-signaling is related to signaling. The RRC connection setup or RRC
connection resume for other causes is related to services.
setup or RRC connection resume procedure.
As shown at point A in Figure 1-2, the total number of RRC connection setup
attempts due to different causes is incremented 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.
As shown at point A in Figure 1-3, the total number of RRC connection resume
RRCResumeRequest/RRCResumeRequest1 message from the UE. As shown at
point C, the total number of successful RRC connection resumes due to different
setup causes is incremented.

5G RAN3.1
Figure 1-3 Measurement points of RRC connection resume
point C, the total number of successful RRC connection setups due to different
setup causes is incremented.
Figure 1-4 Measurement points of RRC connection setup changed from RRC
connection resume
Definition
The RRC Setup Success Rate (CU, Inactive) KPI is defined in Table 1-2.

5G RAN3.1
Table 1-2 RRC Setup Success Rate (CU, Inactive)

Name RRC Setup Success Rate (CU, Inactive)
Object Cell or RAN
Formula RRC_SSR = RRCSetupSuccess/RRCSetupAttempt x 100%
Associated RRC Setup Success Rate (CU, Inactive) = (N.RRC.SetupReq.Succ

Counters + N.RRC.ResumeReq.Succ)/(N.RRC.SetupReq.Att +
N.RRC.ResumeReq.Att) x 100%
Unit %
Note The KPI formula for the RRC_INACTIVE state applies to

scenarios with the inactive switch turned on or turned off. It
can be used as a common formula.
1.2.3 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
causes 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.
setup procedure. As shown at point A in Figure 1-5, 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.

5G RAN3.1
Definition
The RRC Setup Success Rate (Service) KPI is defined in Table 1-3.
Table 1-3 RRC Setup Success Rate (Service) (CU)

Name RRC Setup Success Rate (Service) (CU)
Object Cell or RAN
Formula RRC_SSRservice = RRCSetupSuccessservice/RRCSetupAttemptservice x

100%
Associated RRC Setup Success Rate (Service) (CU) =

Counters (N.RRC.SetupReq.Succ.Emc + 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

5G RAN3.1
1.2.4 RRC Setup Success Rate (Service) (CU, Inactive)

Description
setup or RRC connection resume procedure. As shown at point A in Figure 1-6, the
total number of RRC connection setup attempts due to services is incremented
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.
attempts due to services is incremented each time the gNodeB receives an

5G RAN3.1

point C, the total number of successful RRC connection resumes due to services is
incremented.
attempts due to services is incremented each time the gNodeB receives an
point C, the total number of successful RRC connection setups due to services is
incremented.

5G RAN3.1
Figure 1-8 Measurement points of RRC connection setup changed from RRC
connection resume
Definition
The RRC Setup Success Rate (Service) (CU, Inactive) KPI is defined in Table 1-4.
Table 1-4 RRC Setup Success Rate (Service) (CU, Inactive)

Name RRC Setup Success Rate (Service) (CU, Inactive)
Object Cell / Radio Network
Formula RRC_SSRservice = RRCSetupSuccessservice/RRCSetupAttemptservice

× 100%

5G RAN3.1
Associated RRC Setup Success Rate (Service) (CU, Inactive) =

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

1.2.5 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).
setup procedure. As shown at point A in Figure 1-9, the number of RRC
connection setup attempts due to signaling is incremented 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.

5G RAN3.1
Definition
The RRC Setup Success Rate (Signaling) KPI is defined in Table 1-5.
Table 1-5 RRC Setup Success Rate (Signaling) (CU)
Name RRC Setup Success Rate (Signaling) (CU)
Object Cell or RAN
Formula RRC_SSRsignaling = RRCSetupSuccesssignaling/

RRCSetupAttemptsignaling x 100%
Associated RRC Setup Success Rate (Signaling) (CU) =

Counters N.RRC.SetupReq.Succ.MoSig/N.RRC.SetupReq.Att.MoSig x 100%
Unit %
Note None
1.2.6 RRC Setup Success Rate (Signaling) (CU, Inactive)
Description

5G RAN3.1
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).
setup or RRC connection resume procedure.
As shown at point A in Figure 1-10, the number of RRC connection setup
attempts due to signaling is incremented 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.
attempts due to signaling is incremented each time the gNodeB receives an
point C, the total number of successful RRC connection setups due to signaling is
incremented.

5G RAN3.1
Definition
The RRC Setup Success Rate (Signaling) (CU, Inactive) KPI is defined in Table 1-6.
Table 1-6 RRC Setup Success Rate (Signaling) (CU, Inactive)
Name RRC Setup Success Rate (Signaling) (CU, Inactive)
Object Cell or RAN
Formula RRC_SSRsignaling = RRCSetupSuccesssignaling/

RRCSetupAttemptsignaling x 100%
Associated RRC Setup Success Rate (Signaling) (CU, Inactive) =

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

1.2.7 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

5G RAN3.1
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-12, 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-12, 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-12 Measurement points for signaling connection setup
Definition
The NGSIG Connection Setup Success Rate KPI is defined in Table 1-7.
Table 1-7 NGSIG Connection Setup Success Rate (CU)
Name NGSIG Connection Setup Success Rate (CU)
Object Cell or RAN

5G RAN3.1
Formula NGSIG_SSR = NGSIGConnectionEstablishSuccess/

NGSIGConnectionEstablishAttempt x 100%
Associated NGSIG Connection Setup Success Rate (CU) =

Counters N.NGSig.ConnEst.Succ/N.NGSig.ConnEst.Att x 100%
Unit %
Note None
1.2.8 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 points A in Figure 1-13, Figure 1-14, and Figure 1-15, the
number of QoS flow setup attempts is incremented 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-13 and Figure 1-14, the number of successful QoS flow
setups is incremented 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.
3. As shown at point A in Figure 1-13, the number of QoS flow setup attempts
triggered by emergency voice fallback is incremented in a cell each time the
gNodeB receives an INITIAL CONTEXT SETUP REQUEST message from the
AMF for an emergency voice fallback UE. If the INITIAL CONTEXT SETUP
REQUEST message requests the setup of multiple QoS flows, the number of
QoS flow setup attempts triggered by emergency voice fallback in the cell is
incremented by the number of QoS flow setups.
triggered by EPS fallback is incremented in a cell each time the gNodeB
receives a PDU SESSION RESOURCE MODIFY REQUEST message from the
AMF for an EPS fallback UE. If the PDU SESSION RESOURCE MODIFY
QoS flow setup attempts triggered by EPS fallback in the cell is incremented
by the number of QoS flow setups.
These counters are accumulated in the cell serving the UE.

5G RAN3.1
Figure 1-13 Measurement points for initial context setup
Figure 1-14 Measurement points for PDU session setup

5G RAN3.1
Figure 1-15 Measurement points for PDU session modification
Definition
Table 1-8 lists 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-8 Qos Flow Setup Success Rate (CU)

Name Qos Flow Setup Success Rate (CU)
Object Cell or RAN
Formula QoS Flow_SSR = QosFlowSetupSuccess/QosFlowSetupAttempt x

100%
Associated QoS Flow Setup Success Rate (CU) = N.QosFlow.Est.Succ/

Counters (N.QosFlow.Est.Att – N.QosFlow.Est.Att.EPSFB –
N.QosFlow.Est.Att.EmcFB) x 100%
Unit %
Note None

5G RAN3.1
1.2.9 QoS Flow Setup Success Rate (CU, Inactive)

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, number of
successful QoS flow setups, number of QoS flow resume attempts from
RRC_INACTIVE to RRC_CONNECTED, and number of successful QoS flow resumes.
Therefore, the number of QoS flow resumes from RRC_INACTIVE to
1. As shown at points A in Figure 1-16, Figure 1-17, and Figure 1-18, the
number of QoS flow setup attempts is incremented 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 at points B in Figure 1-16, Figure 1-17, and Figure 1-18, the
number of successful QoS flow setups is incremented each time the gNodeB
sends an INITIAL CONTEXT SETUP RESPONSE, PDU SESSION RESOURCE
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.
3. As shown at points A in Figure 1-19 and Figure 1-20, the number of QoS
flow resume attempts is incremented each time the gNodeB sends an
RRCResume message to the UE. If the RRC Resume message requests to
resume multiple QoS flows at the same time, the total number of QoS flow
resume attempts is accumulated based on the number of QoS flows to be
resumed in the message.
4. As shown at points B in Figure 1-19 and Figure 1-20, the number of
successful QoS flow resumes is incremented each time the gNodeB receives
an RRCResumeComplete message from the UE or sends a UE CONTEXT
RELEASE message to the last serving gNodeB. The numbers are accumulated
in the cell serving the UE.
triggered by emergency voice fallback is incremented in a cell each time the
gNodeB receives an INITIAL CONTEXT SETUP REQUEST message from the

5G RAN3.1
AMF for an emergency voice fallback UE. If the INITIAL CONTEXT SETUP
QoS flow setup attempts triggered by emergency voice fallback in the cell is
incremented by the number of QoS flow setups.
triggered by EPS fallback is incremented in a cell each time the gNodeB
receives a PDU SESSION RESOURCE MODIFY REQUEST message from the
AMF for an EPS fallback UE. If the PDU SESSION RESOURCE MODIFY
QoS flow setup attempts triggered by EPS fallback in the cell is incremented
by the number of QoS flow setups.
Figure 1-16 Measurement points for initial context setup

5G RAN3.1
Figure 1-17 Measurement points for PDU session setup
Figure 1-18 Measurement points for PDU session modification

5G RAN3.1
Figure 1-19 Measurement points for QoS flow resume
Figure 1-20 Measurement points for QoS flow resume
Definition
Table 1-9 lists the definition of the QoS flow setup success rate of all services. For
number of successful setups, see "Description" in this section.
Table 1-9 QoS Flow Setup Success Rate (CU, Inactive)
Name QoS Flow Setup Success Rate (CU, Inactive)

5G RAN3.1
Object Cell or RAN

100%
Associated QoS Flow Setup Success Rate (CU, Inactive) =

Counters (N.QosFlow.Est.Succ + N.QosFlow.Resume.Succ)/
(N.QosFlow.Est.Att + N.QosFlow.Resume.Att –
N.QosFlow.Est.Att.EPSFB – N.QosFlow.Est.Att.EmcFB) x 100%
Unit %

1.2.10 QoS Flow Setup Success Rate (CU, VoNR)
Description
This KPI is used to evaluate the QoS flow setup success rate of VoNR services. The
involved counters include the number of QoS flow setup attempts and the number
of successful QoS flow setups. Users can activate the required VoNR 5QI
measurement objects via the gNB5qiConfig.CounterObjSubscriptionInd
parameter. Generally, VoNR services are services with the 5QI of 1.
Definition
Table 1-10 lists the definition of the VoNR setup success rate of all services. For
number of successful setups, see Description.
Table 1-10 QoS Flow Setup Success Rate (CU, VoNR)
Name QoS Flow Setup Success Rate (CU, VoNR)
Object Cell or RAN

100%
Associated QoS Flow Setup Success Rate (CU, VoNR) =

Counters N.QosFlow.Est.Succ.Cell5QI/(N.QosFlow.Est.Att.Cell5QI –
N.QosFlow.Est.Att.Cell5QI.EPSFB –
N.QosFlow.Est.Att.Cell5QI.EmcFB) x 100%
Unit %
Note None

5G RAN3.1
1.2.11 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-11. This KPI is the product of
the RRC connection setup success rate for services, NG signaling connection setup
Table 1-11 Call Setup Success Rate
Name Call Setup Success Rate (CU)
Object Cell / Radio Network
Formula CSSR = (RRCSetupSuccessservice/RRCSetupAttemptservice) x

(NGSIGConnectionEstablishSuccess/NGSIGConnectionEstablish-
Attempt) x (QosFlowSetupSuccess/QosFlowSetupAttempt) x
100%
Associated Call Setup Success Rate (CU) = ((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.MoVideoCall)/(N.RRC.SetupReq.Att.Emc +
N.RRC.SetupReq.Att.HighPri + N.RRC.SetupReq.Att.Mt +
N.RRC.SetupReq.Att.MoVideoCall)) x (N.NGSig.ConnEst.Succ/
N.NGSig.ConnEst.Att) x (N.QosFlow.Est.Succ/(N.QosFlow.Est.Att
– N.QosFlow.Est.Att.EPSFB – N.QosFlow.Est.Att.EmcFB)) x 100%
Unit %
Note None
1.2.12 Call Setup Success Rate (CU, Inactive)
Description
This KPI is used to evaluate the call setup success rate of all services and applies
to scenarios with the inactive switch turned on or turned off. The KPI includes the
RRC connection setup success rate for services (inactive), NG signaling connection
setup success rate, and QoS flow setup success rate (inactive).

5G RAN3.1
Definition
The Call Setup Success Rate KPI is defined in Table 1-12. This KPI is the product of
the RRC connection setup success rate for services, NG signaling connection setup
Table 1-12 Call Setup Success Rate (CU, Inactive)

Name Call Setup Success Rate (CU, Inactive)
Object Cell or RAN
Formula CSSR = (RRCSetupSuccessservice/RRCSetupAttemptservice) x

(NGSIGConnectionEstablishSuccess/NGSIGConnectionEstablish-
Attempt) x (QosFlowSetupSuccess/QosFlowSetupAttempt) x
100%
Associated Call Setup Success Rate (CU, Inactive) =

Counters ((N.RRC.SetupReq.Succ.Emc + N.RRC.SetupReq.Succ.HighPri +
N.RRC.SetupReq.Succ.MoVideoCall
+N.RRC.ResumeReq.Succ.Emc + N.RRC.ResumeReq.Succ.HighPri
+ N.RRC.ResumeReq.Succ.Mt + N.RRC.ResumeReq.Succ.MoData
+ N.RRC.ResumeReq.Succ.MoVoiceCall +
N.RRC.ResumeReq.Succ.MpsPri +
N.RRC.ResumeReq.Succ.MoSms +
N.RRC.ResumeReq.Succ.MoVideoCall)/(N.RRC.SetupReq.Att.Emc
+ N.RRC.SetupReq.Att.HighPri + N.RRC.SetupReq.Att.Mt +
N.RRC.SetupReq.Att.MoVideoCall + N.RRC.ResumeReq.Att.Emc
+ N.RRC.ResumeReq.Att.HighPri + N.RRC.ResumeReq.Att.Mt +
N.RRC.ResumeReq.Att.MoData +
N.RRC.ResumeReq.Att.MoVoiceCall +
N.RRC.ResumeReq.Att.MpsPri + N.RRC.ResumeReq.Att.MoSms +
N.RRC.ResumeReq.Att.MoVideoCall)) × (N.NGSig.ConnEst.Succ/
N.NGSig.ConnEst.Att) × (N.QosFlow.Est.Succ +
N.QosFlow.Resume.Succ)/(N.QosFlow.Est.Att +
N.QosFlow.Resume.Att – N.QosFlow.Est.Att.EPSFB –
N.QosFlow.Est.Att.EmcFB) x 100%
Unit %


5G RAN3.1
1.3 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.
1.3.1 Service Call Drop Rate (CU)
Description
This KPI is used to evaluate the QoS flow service drop rate of all services. The
involved counters include the number of normal and abnormal QoS flow releases.
Definition
The Service Call Drop Rate (CU) KPI is defined in Table 1-13.
Table 1-13 Service Call Drop Rate (CU)
Name Service Call Drop Rate (CU)
Object Cell or RAN
Formula Service_CDR = QosFlowAbnormRel/QosFlowRel x 100%
Associated Service Call Drop Rate (CU) = N.QosFlow.AbnormRel/

Counters (N.QosFlow.AbnormRel + N.QosFlow.NormRel) x 100%
Unit %
Note None
1.3.2 Service Call Drop Rate (CU, Inactive)
Description
This KPI is used to evaluate the QoS flow service drop rate of all services. The
involved counters include the number of normal and abnormal QoS flow releases
and the number of QoS flow suspensions from RRC_CONNECTED to
RRC_INACTIVE.
Definition
The Service Call Drop Rate (CU, Inactive) KPI is defined in Table 1-14.
Table 1-14 Service Call Drop Rate (CU, Inactive)
Name Service Call Drop Rate (CU, Inactive)

5G RAN3.1
Object Cell or RAN
Formula Service_CDR = QosFlowAbnormRel/QosFlowRel x 100%
Associated Service Call Drop Rate (CU, Inactive) = N.QosFlow.AbnormRel/

Counters (N.QosFlow.AbnormRel + N.QosFlow.NormRel -
N.QosFlow.RrcInactiveToIdle.Rel +
N.QosFlow.RrcConnToInactive.Suspend) x 100%
Unit %

1.3.3 Call Drop Rate (CU, VoNR)

Description
This KPI is used to evaluate the VoNR service drop rate. It is calculated by
monitoring the proportion of abnormal VoNR QoS flow releases. Users can
activate the required VoNR 5QI measurement objects via the
gNB5qiConfig.CounterObjSubscriptionInd parameter. Generally, VoNR services
are services with the 5QI of 1.
Definition
The Call Drop Rate (VoNR) KPI is defined in Table 1-15.
Table 1-15 Call Drop Rate (CU, VoNR)
Name Call Drop Rate (CU, VoNR)
Object Cell or RAN
Formula VoIP_CDR = VoNRQosFlowAbnormalRelease/

VoNRQosFlowRelease x 100%
Associated Call Drop Rate (CU, VoNR) = N.QosFlow.AbnormRel.Cell5QI/

Counters (N.QosFlow.AbnormRel.Cell5QI + N.QosFlow.NormRel.Cell5QI)
x 100%
Unit %
Note None
1.4 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

5G RAN3.1
based on the following handover types: intra-RAT intra-frequency, intra-RAT inter-

frequency, and inter-RAT.
1.4.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-21, 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-21 Intra-gNodeB outgoing handovers without RRC connection

reestablishment
● Intra-gNodeB outgoing handovers with RRC connection reestablishment

As shown in Figure 1-22, 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

5G RAN3.1
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 1-22 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 1-23 and Figure 1-24, 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.

5G RAN3.1
Figure 1-23 Xn-based inter-gNodeB outgoing handover without RRC

connection reestablishment
Figure 1-24 NG-based inter-gNodeB outgoing handover without RRC

● Inter-gNodeB outgoing handover with RRC connection reestablishment to the

target cell
operate at the same frequency. When the source gNodeB sends an RRC
Reconfiguration message containing the handover command to the UE, the
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

5G RAN3.1
number of successful intra-frequency outgoing handover executions in the

source cell at point C.
Figure 1-25 Xn-based inter-gNodeB outgoing handover with RRC connection

reestablishment to the target cell
Figure 1-26 NG-based inter-gNodeB outgoing handover with RRC connection


5G RAN3.1
● Inter-gNodeB outgoing handover with RRC connection reestablishment to the

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

reestablishment to the source cell

5G RAN3.1

Definition
The Intra-Frequency Handover Out Success Rate KPI is defined in Table 1-16. 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-16 Intra-frequency Handover Out Success Rate (CU)
Name Intra-frequency Handover Out Success Rate (CU)
Object Cell or RAN
Formula IntraFreqHOOut_SR = IntraFreqHOOutSuccess/

IntraFreqHOOutAttempt x 100%
Associated Intra-Frequency Handover Out Success Rate (CU) =

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

5G RAN3.1
1.4.2 Inter-Frequency Handover Out Success Rate (CU)

Description
This KPI indicates the success rate of outgoing inter-frequency handovers. The
measurement methods of the related counters are similar to those for intra-
frequency handovers described in Intra-Frequency Handover Out Success Rate >
Description. The only difference is that the source and target cells operate on
different frequencies.
Figure 1-29 and Figure 1-30 illustrate intra-gNodeB handovers, and the source
and target cells operate on different frequencies. The gNodeB counts the number
of outgoing intra-gNodeB inter-frequency handover execution attempts at point B
and counts the number of successful outgoing intra-gNodeB inter-frequency
handover executions at point C. Figure 1-31, Figure 1-32, Figure 1-33, Figure
1-34, Figure 1-35, and Figure 1-36 illustrate inter-gNodeB handovers, and the
source and target cells operate on different frequencies. The source gNodeB
counts the number of outgoing inter-gNodeB inter-frequency handover execution
attempts at point B and counts the number of successful outgoing inter-gNodeB
inter-frequency handover executions at point C.
Figure 1-29 Outgoing intra-gNodeB handovers without RRC connection

reestablishment

5G RAN3.1
Figure 1-30 Outgoing intra-gNodeB handovers with RRC connection

reestablishment
Figure 1-31 Xn-based inter-gNodeB outgoing handover without RRC connection

reestablishment

5G RAN3.1
Figure 1-32 NG-based inter-gNodeB outgoing handover without RRC connection

reestablishment


5G RAN3.1



5G RAN3.1

Definition
The Inter-Frequency Handover Out Success Rate KPI is defined in Table 1-17. 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-17 Inter-frequency Handover Out Success Rate (CU)
Name Inter-frequency Handover Out Success Rate (CU)
Object Cell or RAN
Formula InterFreqHOOut_SR = InterFreqHOOutSuccess/

InterFreqHOOutAttempt x 100%
Associated Inter-Frequency Handover Out Success Rate (CU) =

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

5G RAN3.1
1.4.3 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
reestablishment.
● Intra-gNodeB incoming handovers without RRC connection reestablishment
Figure 1-37 illustrates 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-37 Intra-gNodeB incoming handovers without RRC connection

reestablishment
● Intra-gNodeB incoming handovers with RRC connection reestablishment

Figure 1-38 illustrates 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.

5G RAN3.1
Figure 1-38 Intra-gNodeB incoming handovers with RRC connection

reestablishment
Inter-gNodeB Incoming Handover

Inter-gNodeB incoming handovers can be further classified into handovers with
reestablishment.
● Inter-gNodeB incoming handovers without RRC connection reestablishment
As shown in Figure 1-39 and Figure 1-40, 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.

5G RAN3.1
Figure 1-39 Xn-based inter-gNodeB incoming handover without RRC

Figure 1-40 NG-based inter-gNodeB incoming handover without RRC

● Inter-gNodeB incoming handover with RRC connection reestablishment to the

target cell
Figure 1-41 illustrates 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

5G RAN3.1
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 1-41 Xn-based inter-gNodeB incoming handover with RRC connection

Figure 1-42 illustrates 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.

5G RAN3.1
Figure 1-42 NG-based inter-gNodeB incoming handover with RRC connection

Definition
The Intra-RAT Handover In Success Rate KPI is defined in Table 1-18.
Table 1-18 Intra-RAT Handover In Success Rate (CU)
Name Intra-RAT Handover In Success Rate (CU)
Object Cell or RAN
Formula Intra-RATHOIn_SR = Intra-RATHOInSuccess/Intra-

RATHOInAttempt x 100%
Associated Intra-RAT Handover In Success Rate (CU) =

Counters (N.HO.Ng.IntergNB.ExecSuccIn + 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
1.4.4 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.

5G RAN3.1
The number of NR-to-LTE outgoing handover execution attempts is incremented

by 1 as shown in Figure 1-43 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-43 Inter-RAT handover (NR to LTE)
Definition
The Inter-RAT Handover Out Success Rate (NR to LTE) KPI is defined in Table
1-19.
Table 1-19 Inter-RAT Handover Out Success Rate (NR to LTE) (CU)
Name Inter-RAT Handover Out Success Rate (NR to LTE) (CU)
Object Cell or RAN
Formula IRATHO_N2E_SR = IRATHO_N2E_Success/

IRATHO_N2E_Attempt x 100%
Associated Inter-RAT Handover Out Success Rate (NR to LTE) (CU) =

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

5G RAN3.1
Note If the failures caused by the core network do not need to be

counted in some scenarios, the handover is regarded successful
on the base station side. 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%
1.4.5 EPSFB Success Rate Based Handover (NR to E-UTRAN)

(CU)
Description
This KPI indicates the success rate of handover-based EPS fallback from NG-RAN
to E-UTRAN.
As shown at point B in Figure 1-44, after sending a Mobility From NR Command
message to the UE, the gNodeB performs EPS fallback to E-UTRAN and counts the
number of execution attempts of handover-based EPS fallback from NG-RAN to E-
UTRAN. As shown at point C in Figure 1-44, the UE performs an EPS fallback from
NG-RAN to E-UTRAN. When the gNodeB receives a UE CONTEXT RELEASE
COMMAND message from the AMF, it indicates that the UE has successfully
accessed the E-UTRAN. In this case, the gNodeB counts the number of successful
executions of handover-based EPS fallback from NG-RAN to E-UTRAN.

5G RAN3.1
Figure 1-44 Inter-RAT handover (NR to LTE)
Definition
The EPSFB Success Rate Based Handover KPI is defined in Table 1-20. For details
about related counters, see "Description" in this section.
Table 1-20 EPSFB Success Rate Based Handover (NR to E-UTRAN) (CU)
Name EPSFB Success Rate Based Handover (NR to E-UTRAN) (CU)
Object Cell or RAN
Formula EPSFB_N2E_BasedHO_SR = EPSFB_N2E_BasedHO_Success/

EPSFB_N2E_BasedHO_Attempt x 100%
Associated EPSFB Success Rate Based Handover (NR to E-UTRAN) (CU) =

Counters N.HO.InterRAT.N2E.EPSFB.ExecSuccOut/
N.HO.InterRAT.N2E.EPSFB.ExecAttOut x 100%
Unit %
Note None

5G RAN3.1
1.5 Service Integrity KPIs

Service integrity KPIs are used to evaluate the service quality of end-users in the
5G RAN.
1.5.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-21 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-21 User Downlink Average Throughput (DU)
Name User Downlink Average Throughput (DU)
Object Cell or RAN
Formula UserDLAveThp = UserDLRmvLastSlotTrafficVolume/

UserDLRmvLastSlotTransferTime
Associated User Downlink Average Throughput (DU) = (N.ThpVol.DL -

Counters N.ThpVol.DL.LastSlot)/N.ThpTime.DL.RmvLastSlot
Unit Gbit/s
Note None
1.5.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-22 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-22 User Uplink Average Throughput (DU)
Name User Uplink Average Throughput (DU)

5G RAN3.1
Object Cell or RAN
Formula UserULAveThp = UserULRmvSmallPktTrafficVolume/

UserULRmvSmallPktTransferTime
Associated User Uplink Average Throughput (DU) = (N.ThpVol.UL -

Counters N.ThpVol.UE.UL.SmallPkt)/N.ThpTime.UE.UL.RmvSmallPkt
Unit Gbit/s
Note None
1.5.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-23 and is
calculated based on the total traffic volume and data transmission duration in the
downlink of a cell.
Table 1-23 Cell Downlink Average Throughput (DU)

Name Cell Downlink Average Throughput (DU)
Object Cell or RAN
Formula CellDLAveThp = CellDLTrafficVolume/CellDLTransferTime
Associated Cell Downlink Average Throughput (DU) = N.ThpVol.DL.Cell/

Counters N.ThpTime.DL.Cell
Unit Gbit/s
Note None
1.5.4 Cell Uplink Average Throughput (DU)

Description
This KPI indicates the average uplink cell throughput, which reflects the cell
capacity in the uplink.

5G RAN3.1
Definition
The Cell Uplink Average Throughput KPI is defined in Table 1-24 and is calculated
based on the total traffic volume and data transmission duration in the uplink of a
cell.
Table 1-24 Cell Uplink Average Throughput (DU)
Name Cell Uplink Average Throughput (DU)
Object Cell or RAN
Formula CellULAveThp = CellULTrafficVolume/CellULTransferTime
Associated Cell Uplink Average Throughput (DU) = N.ThpVol.UL.Cell/

Counters N.ThpTime.UL.Cell
Unit Gbit/s
Note None
1.6 Utilization KPIs

Utilization KPIs are used to evaluate the capabilities, such as the capability to
meet traffic demands, in specific internal conditions.
1.6.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-25.
Table 1-25 Downlink Resource Block Utilizing Rate (DU)
Name Downlink Resource Block Utilizing Rate (DU)
Object Cell or RAN
Formula RB_URDL = RB_UsedDL/RB_AvailableDL x 100%
Associated Downlink Resource Block Utilizing Rate (DU) =

Counters N.PRB.DL.Used.Avg/N.PRB.DL.Avail.Avg x 100%
Unit %
Note None

5G RAN3.1
1.6.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-26.
Table 1-26 Uplink Resource Block Utilizing Rate (DU)
Name Uplink Resource Block Utilizing Rate (DU)
Object Cell or RAN
Formula RB_URUL = RB_UsedUL/RB_AvailableUL x 100%
Associated Uplink Resource Block Utilizing Rate (DU) =

Counters N.PRB.UL.Used.Avg/N.PRB.UL.Avail.Avg x 100%
Unit %
Note None
1.6.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-27.
Table 1-27 Average CPU Load
Name Average CPU Load
Object CPU
Formula MeanCPUUtility
Associated Average CPU Load = VS.BBUBoard.CPULoad.Mean

Counter
Unit %
Note None

5G RAN3.1
1.7 Availability KPIs

A cell is available when the gNodeB can provide EPS bearer services.
1.7.1 Radio Network Availability Rate (CU)
Description
This KPI indicates the percentage of time when cells in a radio network are
available. The KPI is used to evaluate the cell working status during busy hours.
Definition
The Radio Network Availability Rate KPI is defined in Table 1-28. The KPI is
calculated based on all cells on the radio network.
Table 1-28 Radio Network Availability Rate
Name Radio Network Availability Rate (CU)
Object Radio Network
Formula RAN_Avail_Rate = (ΣCellAvailTime/(TheTotalNumberOfCell-

sInCluster x {SP} x 60)) x 100%
Associated Radio Network Availability Rate (CU) = N.Cell.Avail.Dur/

Counters (Number of cells x {SP} x 60) x 100%
SP indicates the reporting period for counters in minutes.
Unit %
Note None
1.8 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.
1.8.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-29.

5G RAN3.1
Table 1-29 Downlink Traffic Volume (DU)
Name Downlink Traffic Volume (DU)
Object Cell or RAN
Formula DLTrafficVolume
Associated Downlink Traffic Volume (DU) = N.ThpVol.DL

Counters
Unit kbit
Note None
1.8.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-30.
Table 1-30 Uplink Traffic Volume (DU)
Name Uplink Traffic Volume (DU)
Object Cell or RAN
Formula ULTrafficVolume
Associated Uplink Traffic Volume (DU) = N.ThpVol.UL

Counters
Unit kbit
Note None
1.8.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.

5G RAN3.1
Definition
The Average User Number KPI is defined in Table 1-31.
Table 1-31 Average User Number (CU)
Name Average User Number (CU)
Object Cell or RAN
Formula AvgUserNumber
Associated Average User Number (CU) = N.User.RRCConn.Avg

Counters
Unit N/A
Note None
1.8.4 Maximum User Number(CU)

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-32.
Table 1-32 Maximum User Number (CU)
Name Maximum User Number (CU)
Object Cell or radio network
Formula MaxUserNumber
Associated Maximum User Number (CU)= N.User.RRCConn.Max

Counters
Unit N/A
Note None
1.9 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.

5G RAN3.1
1.9.1 SgNB Addition Success Rate (CU)

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-45, and the number of
successful SgNB additions is measured at point B in Figure 1-45.
Figure 1-45 Measurement points of SgNB addition in NSA DC scenarios
Definition
The SgNB Addition Success Rate KPI is defined in Table 1-33.
Table 1-33 SgNB Addition Success Rate (CU)

Name SgNB Addition Success Rate (CU)
Object Cell or RAN
Formula SgNBAdd_SR = SgNBAdditionSuccess/SgNBAdditionAttempt x

100%
Associated SgNB Addition Success Rate (CU) = N.NsaDc.SgNB.Add.Succ/

Counters N.NsaDc.SgNB.Add.Att x 100%
Unit %
Note None

5G RAN3.1
1.9.2 Intra-SgNB PSCell Change Success Rate (CU)
Definition
This KPI is used to evaluate the intra-SgNB intra-frequency and inter-frequency
cell change success rate in NSA DC scenarios. For details about intra-SgNB intra-
frequency and inter-frequency cell change procedures, see 3GPP TS 37.340. The
number of intra-SgNB intra-frequency and inter-frequency cell change attempts is
measured at point A in Figure 1-46, and the number of successful intra-SgNB
intra-frequency and inter-frequency cell changes is measured at point B in Figure
1-46.
Figure 1-46 Measurement points of intra-SgNB intra-frequency and inter-

frequency cell change in NSA DC scenarios
Description
The Intra-SgNB PSCell Change Success Rate KPI is defined in Table 1-34.
Table 1-34 Intra-SgNB PSCell Change Success Rate (CU)
Name Intra-SgNB PSCell Change Success Rate (CU)
Object Cell or RAN
Formula IntraSgNBPscellChange_SR = IntraSgNBPscellChangeSuccess/

IntraSgNBPscellChangeAttempt x 100%
Associated Intra-SgNB PSCell Change Success Rate (CU)=

Counters N.NsaDc.IntraSgNB.PSCell.Change.Succ/
N.NsaDc.IntraSgNB.PSCell.Change.Att x 100%
Unit %
Note None

5G RAN3.1
1.9.3 Intra-SgNB IntraFreq PSCell Change Success Rate (CU)
Definition
This KPI is used to evaluate the intra-SgNB intra-frequency cell change success
rate in NSA DC scenarios. For details about intra-SgNB intra-frequency cell change
procedures, see 3GPP TS 37.340. The number of intra-SgNB intra-frequency cell
change attempts is measured at point A in Figure 1-47, and the number of
successful intra-SgNB intra-frequency cell changes is measured at point B in
Figure 1-47.
Figure 1-47 Measurement points of intra-SgNB intra-frequency cell change in NSA

DC scenarios
Description
The Intra-SgNB IntraFreq PSCell Change Success Rate KPI is defined in Table 1-35.
Table 1-35 Intra-SgNB IntraFreq PSCell Change Success Rate (CU)
Name Intra-SgNB IntraFreq PSCell Change Success Rate (CU)
Object Cell or RAN
Formula IntraSgNBIntraFreqPscellChange_SR = IntraSgNBIntraFreqPscell-

ChangeSuccess/IntraSgNBIntraFreqPscellChangeAttempt x
100%
Associated Intra-SgNB IntraFreq PSCell Change Success Rate (CU) =

Counters N.NsaDc.IntraSgNB.IntraFreq.PSCell.Change.Succ/
N.NsaDc.IntraSgNB.IntraFreq.PSCell.Change.Att x 100%
Unit %
Note None

5G RAN3.1
1.9.4 Inter-SgNB PSCell Change Success Rate (CU)
Description
This KPI is used to evaluate the inter-SgNB intra-frequency and inter-frequency
cell change success rate in NSA DC scenarios. For details about inter-SgNB intra-
frequency and inter-frequency cell change procedures, see 3GPP TS 37.340. The
number of inter-SgNB intra-frequency and inter-frequency cell change attempts is
measured at point A in Figure 1-48, and the number of successful inter-SgNB
intra-frequency and inter-frequency cell changes is measured at point B in Figure
1-48.
Figure 1-48 Measurement points of inter-SgNB intra-frequency and inter-

frequency cell change in NSA DC scenarios
Definition
The Inter-SgNB PSCell Change Success Rate KPI is defined in Table 1-36.
Table 1-36 Inter-SgNB PSCell Change Success Rate (CU)
Name Inter-SgNB PSCell Change Success Rate (CU)
Object Cell or RAN
Formula InterSgNBPscellChange_SR = InterSgNBPscellChangeSuccess/

InterSgNBPscellChangeAttempt x 100%
Associated Inter-SgNB PSCell Change Success Rate (CU) =

Counters N.NsaDc.InterSgNB.PSCell.Change.Succ/
N.NsaDc.InterSgNB.PSCell.Change.Att x 100%
Unit %
Note None

5G RAN3.1
1.9.5 Inter-SgNB IntraFreq PSCell Change Success Rate (CU)
Description
This KPI is used to evaluate the inter-SgNB intra-frequency cell change success
rate in NSA DC scenarios. For details about inter-SgNB intra-frequency cell change
procedures, see 3GPP TS 37.340. The number of inter-SgNB intra-frequency cell
change attempts is measured at point A in Figure 1-49, and the number of
successful inter-SgNB intra-frequency cell changes is measured at point B in
Figure 1-49.
Figure 1-49 Measurement points of inter-SgNB intra-frequency cell change in NSA

DC scenarios
Definition
The Inter-SgNB IntraFreq PSCell Change Success Rate KPI is defined in Table 1-37.
Table 1-37 Inter-SgNB IntraFreq PSCell Change Success Rate (CU)
Name Inter-SgNB IntraFreq PSCell Change Success Rate (CU)
Object Cell or RAN
Formula InterSgNBIntraFreqPscellChange_SR = InterSgNBIntraFreqPscell-

ChangeSuccess/InterSgNBIntraFreqPscellChangeAttempt x
100%
Associated Inter-SgNB PSCell IntraFreq Change Success Rate (CU) =

Counters N.NsaDc.InterSgNB.IntraFreq.PSCell.Change.Succ/
N.NsaDc.InterSgNB.IntraFreq.PSCell.Change.Att x 100%
Unit %
Note None

5G RAN3.1
1.9.6 SgNB-Triggered SgNB Abnormal Release Rate (CU)

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-38.
Table 1-38 SgNB-Triggered SgNB Abnormal Release Rate (CU)

Name SgNB-Triggered SgNB Abnormal Release Rate (CU)
Object Cell or RAN
Formula SgNBTriSgNBAbnormalReleaseRate = SgNBTriSgNBAbnormal-

Release/SgNBRelease x 100%
Associated SgNB-Triggered SgNB Abnormal Release Rate (CU) =

Counters N.NsaDc.SgNB.AbnormRel/N.NsaDc.SgNB.Rel x 100%
Unit %
Note None
1.9.7 SgNB Abnormal Release Rate (CU)

Description
This KPI is used to evaluate the total number of abnormal SgNB releases triggered
by the MeNB and SgNB in NSA DC scenarios. For details about SgNB release
procedures, see 3GPP TS 37.340.
Definition
The SgNB Abnormal Release Rate KPI is defined in Table 1-39.
Table 1-39 SgNB Abnormal Release Rate (CU)

Name SgNB Abnormal Release Rate (CU)
Object Cell or RAN
Formula SgNBAbnormalReleaseRate = (MeNBTriSgNBAbnormalRelease

+ SgNBTriSgNBAbnormalRelease)/SgNBRelease x 100%

5G RAN3.1
Associated SgNB Abnormal Release Rate (CU) = (N.NsaDc.SgNB.Rel –

Counters N.NsaDc.SgNB.Rel.SgNBTrigger –
N.NsaDc.SgNB.Rel.MeNBTrigger.NormalRel +
N.NsaDc.SgNB.AbnormRel)/N.NsaDc.SgNB.Rel x 100%
Unit %
Note None
1.10 Reference Documents

[1] gNodeB performance counter reference

5G RAN KPI Reference (V100R016C10 - 02) (PDF) - EN

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

5G RAN KPI Reference (V100R016C10 - 02) (PDF) - EN

Uploaded by

Copyright:

Available Formats

5G RAN3.

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 02 (2020-05-21) Copyright © Huawei Technologies Co., Ltd. i

1 5G RAN KPI Reference............................................................................................................ 1

Issue 02 (2020-05-21) Copyright © Huawei Technologies Co., Ltd. ii

1.6.3 Average CPU Load.............................................................................................................................................................52

Issue 02 (2020-05-21) Copyright © Huawei Technologies Co., Ltd. iii

1 5G RAN KPI Reference

DBS3900 ● SRAN16.1 V100R016C10

DBS3900 LampSite ● 5G RAN3.1

Issue 02 (2020-05-21) Copyright © Huawei Technologies Co., Ltd. 1

Product Name Solution Version Product Version

5G RAN KPI Reference

1.1 Changes in 5G RAN KPI Reference

Issue 02 (2020-05-21) Copyright © Huawei Technologies Co., Ltd. 2

Topic Change Description

● 1.2.8 QoS Flow Setup Success Added counters related to emergency

Issue 02 (2020-05-21) Copyright © Huawei Technologies Co., Ltd. 3

1.3.2 Service Call Drop Rate (CU, Inactive)

1.2 Accessibility KPIs

1.2.1 RRC Setup Success Rate (CU)

Issue 02 (2020-05-21) Copyright © Huawei Technologies Co., Ltd. 4

Figure 1-1 Measurement points for RRC connection setup

Table 1-1 RRC Setup Success Rate (CU)

Object Cell or RAN

Formula RRC_SSR = RRCSetupSuccess/RRCSetupAttempt x 100%

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

1.2.2 RRC Setup Success Rate (CU, Inactive)

Issue 02 (2020-05-21) Copyright © Huawei Technologies Co., Ltd. 5

Figure 1-2 Measurement points for RRC connection setup

Issue 02 (2020-05-21) Copyright © Huawei Technologies Co., Ltd. 6

Figure 1-3 Measurement points of RRC connection resume

Issue 02 (2020-05-21) Copyright © Huawei Technologies Co., Ltd. 7

Table 1-2 RRC Setup Success Rate (CU, Inactive)

Object Cell or RAN

Formula RRC_SSR = RRCSetupSuccess/RRCSetupAttempt x 100%

Associated RRC Setup Success Rate (CU, Inactive) = (N.RRC.SetupReq.Succ

Note The KPI formula for the RRC_INACTIVE state applies to

1.2.3 RRC Setup Success Rate (Service) (CU)

Issue 02 (2020-05-21) Copyright © Huawei Technologies Co., Ltd. 8

Figure 1-5 Measurement points for RRC connection setup

Table 1-3 RRC Setup Success Rate (Service) (CU)

Object Cell or RAN

Formula RRC_SSRservice = RRCSetupSuccessservice/RRCSetupAttemptservice x

Associated RRC Setup Success Rate (Service) (CU) =

Issue 02 (2020-05-21) Copyright © Huawei Technologies Co., Ltd. 9

1.2.4 RRC Setup Success Rate (Service) (CU, Inactive)

Figure 1-6 Measurement points for RRC connection setup

Issue 02 (2020-05-21) Copyright © Huawei Technologies Co., Ltd. 10

RRCResumeRequest/RRCResumeRequest1 message from the UE. As shown at

Figure 1-7 Measurement points of RRC connection resume

Issue 02 (2020-05-21) Copyright © Huawei Technologies Co., Ltd. 11

Table 1-4 RRC Setup Success Rate (Service) (CU, Inactive)

Object Cell / Radio Network

Formula RRC_SSRservice = RRCSetupSuccessservice/RRCSetupAttemptservice

Issue 02 (2020-05-21) Copyright © Huawei Technologies Co., Ltd. 12

Associated RRC Setup Success Rate (Service) (CU, Inactive) =

Note The KPI formula for the RRC_INACTIVE state applies to

1.2.5 RRC Setup Success Rate (Signaling) (CU)

Issue 02 (2020-05-21) Copyright © Huawei Technologies Co., Ltd. 13

Figure 1-9 Measurement points for RRC connection setup