Training Course - 5G RAN3.0 KPI Introduction V1.00

Introduction to 5G RAN3.
0 KPI
www.huawei.com
Copyright © Huawei Technologies Co., Ltd. All rights reserved.

Objectives
 Upon completion of this course, you will be able to:

 Describe 5G counter overview.
 Describe the 5G KPI architecture.
Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 2

Contents
1. Basic Concepts of 5G Counters
2. 5G KPI Description
3. 5G Counters for NSA Evaluation

Counter Organization
 Counter organization: Counter -> Function subset -> Measurement object

 The result of each measurement is associated with a specific measurement object.
Measurement object
Function Measurement Measurement Function Measurement

...
unit 1 unit 2 unit n
set 1 set 2
Counter 1 Counter 2 Counter 3 Counter 4 Counter 5 Counter 6 Counter 7 ... ...

5G RAN3.0 Counter Overview - Measurement Objects
ID Name Description Introduced In
Measurement of Cell Contains cell-level counters. Cells are deployed on gNodeB central units
NRCELL
Performance (CUs).
Measurement of DU Cell
NRDUCELL Contains NR distribution unit (DU) cell counters. 5G RAN1.0
Performance
Measurement of gNodeB Contains gNodeB-level counters, which indicate the operating status of
gNodeB
Performance gNodeBs.
Measurement of gNodeB DU Contains gNodeB DU counters, which indicate the operating status of
gNBDU 5G RAN2.0
Performance gNodeB DUs.
Measurement of QCI
Contains QCI counters, which indicate QCI performance of DU cells in
NRDUCELL.NSAQCI Performance in NSA Networking 5G RAN2.1
NSA networking.
Based on DU Cell
Measurement of Neighboring NR Contains counters that measure intra-NR handovers between two
NRCellRelation 5G RAN2.1
Cell Performance specific cells, which reflect the handover performance of specific cells.
Contains counters that measure handovers between NR cells and
Measurement of Neighboring E-
NRCELLtoECELL neighboring E-UTRAN cells, which reflect the QoS of various types of 5G RAN2.1
UTRAN Cell Performance
handover services between these cells.
Contains function subsets related to each operator in an NR CU cell,
Measurement of NR CU Cell
NRCell.Operator which reflect the QoS of various services provided by the NR CU cell for 5G RAN2.1
Operator Performance
each operator.
Contains function subsets related to each operator in an NR DU cell,
Measurement of NR DU Cell
NRDUCell.Operator which reflect the QoS of various services provided by the NR DU cell for 5G RAN2.1
Operator Performance
each operator.

ID Name Description Introduced In
Measures the 5QI performance of NR cells. Users can

Measurement of Cell 5QI
NRCELL.5QI activate the required 5QI measurement objects via the 5G RAN3.0
Performance
gNB5qiConfig.CounterObjSubscriptionInd parameter.
Measures the 5QI performance of NR DU cells. Users

Measurement of DU Cell 5QI can activate the required 5QI measurement objects via
NRDUCELL.5QI 5G RAN3.0
Performance the gNB5qiConfig.CounterObjSubscriptionInd
parameter.
Measurement of NR DU Cell
NRDUCELLTRP Measures the performance of NR DU cell TRPs. 5G RAN3.0
TRP Performance
Contains function subsets related to the X2 interface in
Measurement of X2 Interface the gNodeB. It represents the quality of each type of
X2Interface 5G RAN3.0
Performance service provided by an X2 link between a gNodeB and an
eNodeB.
Remarks: The design of counters related to QCI and 5QI is different in LTE and 5G. In LTE, Such counters
are designed at the counter level in LTE and at the counter object level in 5G. That is, such counters are
reported only after the corresponding counter objects are activated. The maximum number of QCI and 5QI
objects must not exceed 20.

5G Network Resource Model (28.541) According to 3GPP TS 28.541, Network

Resource Model (NRM) is divided into CUCP,
CUUP, and DU. The current measurement
object model is different from that in 3GPP
specifications. Changes will be made to
comply with the protocols or subsequent
updates.
Major Impact
GNBCUUPFunction (SDAP and PDCP layer
measurement) in the protocol does not include
gNodeB-level cell-level measurement. That is,
1) Currently, NR cell PDCP counters are
measurement incompatible with the protocol.
in 3GPP 2) PDCP counters cannot measure cell-level
performance, including traffic, packet loss, and
delay.
NR DU cell NR cell 3) Retainability KPIs cannot be designed
following LTE. This is because LTE retainability
KPIs count data transmission in the user buffer
but CUCP in 5G protocols cannot perceive the
data transmission in buffer.

5G RAN3.0 Counter Overview - Function Subset
Function Function Subset Measurement Introduced Function Subset Function Subset Measurement Introduced
Subset ID Name Object In ID Name Object In
PDCP.Cell PDCP Measurement NRCELL gNodeB Transmission
Traffic.TRPIP.gNodeB gNodeB
Interface Measurement
Cell User Quantity
User.Cell NRCELL
Measurement gNodeBDU Transmission
Traffic.TRPIP.gNBDU gNBDU
Interface Measurement
Cell Reserved Counter
Reserve.Cell NRCELL Cell Algorithm
Measurement Algo.Cell NRCELL
Measurement
Throughput or Data
Thp.DuCell NRDUCELL gNodeB Algorithm
Volume Measurement Algo.gNodeB gNodeB
Measurement
PRB.DuCell PRB Measurement NRDUCELL
gNodeB DU Call
RLC.DuCell RLC Measurement NRDUCELL CallAtt.gNBDU gNBDU
Processing Times
MAC.DuCell MAC Measurement NRDUCELL 5G RAN2.0
5G RAN1.0 gNodeB Call Processing
CallAtt.gNodeB gNodeB
ChMeas.MCS. Times
MCS Measurement NRDUCELL
DuCell MIMO Channel
MIMO.DuCell NRDUCELL
Measurement
ChMeas.CQI.
CQI Measurement NRDUCELL
DuCell
CA.Cell Cell CA Measurement NRDUCELL
ChMeas.Pwr. Channel Quality
NRDUCELL DU Cell CA
DuCell Measurement CA.DuCell NRDUCELL
measurement
Random Access
RA.DuCell NRDUCELL Uplink and Downlink
Measurement
UlDlDecoupling.Cell Decoupling NRDUCELL
DC.Cell DC Measurement NRDUCELL Measurement

Measurement Introduced Measurement Introduced
Function Subset ID Function Subset Name Function Subset ID Function Subset Name
Object In Object In
RRC.Setup.Cell RRC Setup Measurement NRCELL
Security Mode
RRC.SetupFail.Cell RRC Setup Failure Measurement NRCELL SecurMode.Cell NRCELL
Measurement
RRC.ReEst.Cell RRC Reestablishment Measurement NRCELL
Paging.DuCell Cell Paging Measurement NRDUCELL
RRC Reestablishment Failure
RRC.ReEstFail.Cell NRCELL Throughput Distribution
Measurement Thp.PDF.DuCell NRDUCELL
Measurement
UeCntx.Est.Cell UE Context Setup Measurement NRCELL
UeCntx.EstFail.Cell UE Context Setup Failure Measurement NRCELL Cell Service Quality
QoS.Cell NRDUCELL
Measurement
UeCntx.Modify.Cell UE Context Modification Measurement NRCELL
gNodeB User Number
UeCntx.Rel.Cell UE Context Release Measurement NRCELL User.gNodeB gNodeB
Measurement
PDUSession.Est.Cell PDU Session Setup Measurement NRCELL
DU Cell QCI User
PDUSession.Modify. User.DuCell.QCI NRDUCELL.NSAQCI
PDU Session Modification Measurement NRCELL Quantity Measurement
Cell 5G RAN2.1
QCI Throughput 5G RAN2.1
PDUSession.Rel.Cell PDU Session Release Measurement NRCELL Thp.DuCell.QCI NRDUCELL.NSAQCI
Measurement
QosFlow.Est.Cell QoS Flow Setup Measurement NRCELL
RLC Measurement for All
QosFlow.EstFail.Cell QoS Flow Setup Failure Measurement NRCELL Traffic.RLC.DuCell.Operator NRDUCell.Operator
Users of Operator
QosFlow.Modify.Cell QoS Flow Modification Measurement NRCELL
Cell User Quantity
QosFlow.Rel.Cell QoS Flow Release Measurement NRCELL Traffic.User.Cell.Operator NRCell.Operator
Measurement of Operator
Incoming Intra-RAT Handover
HO.NR.In.Cell NRCELL Traffic.DRB.Cell DRB Measurement NRCELL
Measurement
Outgoing Intra-RAT Handover Intra-RAT Inter-cell
HO.NR.Out.Cell NRCELL
Measurement HO.NRCellRelation.Out.Cell Outgoing Handover NRCellRelation
Outgoing Inter-RAT Handover Measurement
N.HO.InterRAT NRCELL
Measurement
Inter-RAT Inter-cell
IRATHO.NrCell.ECell NRCELLtoECELL
Handover Measurement

Function Subset ID Function Subset Name Measurement Object Introduced In
Measurement per MCS Index in the MCS

ChMeas.PDSCH.64QAM.MCS.DuCell NRDUCELL
Index Table for PDSCH with 64QAM

ChMeas.PDSCH.256QAM.MCS.DuCell NRDUCELL
Index Table for PDSCH with 256QAM

ChMeas.PUSCH.64QAM.MCS.DuCell NRDUCELL
Index Table for PUSCH with 64QAM

ChMeas.PUSCH.256QAM.MCS.DuCell NRDUCELL
Index Table for PUSCH with 256QAM 5G RAN2.1

ChMeas.PUSCH.64QAMTP.MCS.DuCell Index Table for PUSCH with Transform NRDUCELL
Precoding and 64QAM
Measurement of CQIs in the CQI Table with

ChMeas.64QAM.CQI.DuCell NRDUCELL
64QAM
Measurement of CQIs in the CQI Table with

ChMeas.256QAM.CQI.DuCell NRDUCELL
256QAM

Function Subset ID Function Subset Name Measurement Object Introduced In
PRB0To99.Interference.DuCell Uplink Interference Measurement on PRB 0 to PRB 99 NRDUCEL
Paging.Cell Cell Paging Measurement NRCELL
QosFlow.Est.Cell5QI 5QI QoS Flow Setup Measurement NRCELL.5QI
QosFlow.Modify.Cell5QI 5QI QoS Flow Modification Measurement NRCELL.5QI
QosFlow.Rel.Cell5QI 5QI QoS Flow Release Measurement NRCELL.5QI
PDCP.Cell5QI Cell 5QI PDCP Measurement NRCELL.5QI 5G RAN3.0
Traffic.DuCell5QI DU Cell 5QI Traffic Measurement NRDUCELL.5QI
SI.DuCell DU Cell SI Message Measurement NRDUCELL
MAC.HyperCellTRP Hyper Cell TRP MAC Measurement NRDUCELL
PRB.HyperCellTRP Hyper Cell TRP PRB Measurement NRDUCELL
User.HyperCellTRP Hyper Cell TRP User Number Measurement NRDUCELL
N.HO.InterRAT.In.Cell Incoming Inter-RAT Handover Measurement NRCELL
DC.X2Interface X2 Interface DC Measurement NRCELL

Counter Changes from 5G RAN1.0 to 5G RAN2.0
Function Subset ID Function Subset Name Introduced In Changes in RAN2.0
New: Average/maximum number of UEs in RRC_CONNECTED
User.Cell Cell User Quantity Measurement RAN1.0 mode, number of B2H UEs, and numbers of CA uplink and
downlink PCell/SCell UEs
Added counters related to the throughput with the last slot
Thp.DuCell Throughput or Data Volume Measurement RAN1.0
deleted.
PRB.DuCell PRB Measurement RAN1.0 Added PDCCH CCE statistics.
ChMeas.MCS. DuCell MCS Measurement RAN1.0 Added counters related to PUSCH 256QAM MCS.
ChMeas.Pwr. DuCell Channel Quality Measurement RAN1.0 Added average and minimum values of RSSI.
Added counters related to abnormal SgNB releases in the NSA
DC.Cell DC Measurement RAN1.0
DC scenario.
Traffic.TRPIP.gNBDU gNodeBDU Transmission Interface Measurement RAN2.0 Added counters related to the F1 interface.
Algo.Cell Cell Algorithm Measurement RAN2.0 Added counters related to cell unavailability.
Algo.gNodeB gNodeB Algorithm Measurement RAN2.0 Added counters related to heavy cell load.
Added counters related to the number of call processing times,
CallAtt.gNBDU gNodeB DU Call Processing Times RAN2.0
which is used for license specifications.
Added counters related to the number of call processing times,
CallAtt.gNodeB gNodeB Call Processing Times RAN2.0
which is used for license specifications.
MIMO.DuCell MIMO Channel Measurement RAN2.0 Added counters related to MIMO pairing.
CA.Cell Cell CA Measurement RAN2.0 Added counters related to CA SCell addition/changes.
CA.DuCell DU Cell CA measurement RAN2.0 Added counters related to CA UE activation and deactivation.
UlDlDecoupling.Cell Uplink and Downlink Decoupling Measurement RAN2.0 Added counters related to decoupling cell changes.

RRC.Setup.Cell RRC Setup Measurement RAN2.1 Added counters related to RRC
RRC.SetupFail.Cell RRC Setup Failure Measurement RAN2.1 connection setup.
RRC.ReEst.Cell RRC Reestablishment Measurement RAN2.1 Added counters related to RRC
RRC.ReEstFail.Cell RRC Reestablishment Failure Measurement RAN2.1 connection reestablishment.
UeCntx.Est.Cell UE Context Setup Measurement RAN2.1
UeCntx.EstFail.Cell UE Context Setup Failure Measurement RAN2.1 Add counters related to UE context
UeCntx.Modify.Cell UE Context Modification Measurement RAN2.1 setup, modification, and release.
UeCntx.Rel.Cell UE Context Release Measurement RAN2.1
PDUSession.Est.Cell PDU Session Setup Measurement RAN2.1
Added counters related to PDU session
PDUSession.Modify.Cell PDU Session Modification Measurement RAN2.1
setup, modification, and release.
PDUSession.Rel.Cell PDU Session Release Measurement RAN2.1
QosFlow.Est.Cell QoS Flow Setup Measurement RAN2.1
QosFlow.EstFail.Cell QoS Flow Setup Failure Measurement RAN2.1 Added counters related to QoS flow
QosFlow.Modify.Cell QoS Flow Modification Measurement RAN2.1 setup, modification, and release.
QosFlow.Rel.Cell QoS Flow Release Measurement RAN2.1
HO.NR.In.Cell Incoming Intra-RAT Handover Measurement RAN2.1
HO.NR.Out.Cell Outgoing Intra-RAT Handover Measurement RAN2.1 Added mobility-related counters.
N.HO.InterRAT Outgoing Inter-RAT Handover Measurement RAN2.1
Paging.Cell Cell Paging Measurement RAN2.1 Added paging-related counters.

Traffic.DRB.Cell DRB Measurement RAN2.1 Added counters related to DRBs.
HO.NRCellRelation.Out.Cell Intra-RAT Inter-cell Outgoing Handover Measurement RAN2.1 Added counters related to intra-RAT handover between two cells.
IRATHO.NrCell.ECell Inter-RAT Inter-cell Handover Measurement RAN2.1 Added counters related to inter-RAT handover between two cells.
SecurMode.Cell Security Mode Measurement RAN2.1 Added counters related to security mode.
Traffic.RLC.DuCell.Operator RLC Measurement for All Users of Operator RAN2.1
Added operator-related counters.
Traffic.User.Cell.Operator Cell User Quantity Measurement of Operator RAN2.1
User.DuCell.QCI DU Cell QCI User Quantity Measurement RAN2.1
Added QCI-related counters in the NSA networking.
Thp.DuCell.QCI QCI Throughput Measurement RAN2.1
Thp.PDF.DuCell Throughput Distribution Measurement RAN2.1 Added counters related to throughput range distribution.
PRB.DuCell PRB Measurement RAN1.0 Added PDCCH CCE aggregation level statistics.
Added maximum transmit power and average power of a cell (for
ChMeas.Pwr. DuCell Channel Quality Measurement RAN1.0
EMF).
MAC.DuCell MAC Measurement RAN1.0 Added downlink IBLER statistics.
RA.DuCell Random Access Measurement RAN1.0 Added TA range distribution.
Measurement per MCS Index in the MCS Index Table for
ChMeas.PDSCH.64QAM.MCS.DuCell RAN2.1
PDSCH with 64QAM Added counters related to the number of RBs of downlink MCS
Measurement per MCS Index in the MCS Index Table for indexes corresponding to ranks in different MCS index tables.
ChMeas.PDSCH.256QAM.MCS.DuCell RAN2.1
PDSCH with 256QAM
ChMeas.PUSCH.64QAM.MCS.DuCell RAN2.1
PUSCH with 64QAM
Added counters related to the number of RBs of uplink MCS
ChMeas.PUSCH.256QAM.MCS.DuCell RAN2.1 indexes corresponding to ranks in different MCS index tables.
PUSCH with 256QAM
ChMeas.PUSCH.64QAMTP.MCS.DuCell RAN2.1
PUSCH with Transform Precoding and 64QAM
ChMeas.64QAM.CQI.DuCell Measurement of CQIs in the CQI Table with 64QAM RAN2.1 Added counters related to CQIs corresponding to ranks in
ChMeas.256QAM.CQI.DuCell Measurement of CQIs in the CQI Table with 256QAM RAN2.1 different CQI tables.

Uplink Interference Measurement on PRB 0
PRB0To99.Interference.DuCell RAN3.0
to PRB 99
Uplink Interference Measurement on PRB
PRB200To272.Interference.DuCell RAN3.0 Measured the uplink interference and noise based on the PRB.
200 to PRB 272
Uplink Interference Measurement on PRB
PRB100To199.Interference.DuCell RAN3.0
100 to PRB 199
Paging.Cell Cell Paging Measurement RAN3.0 Measured CU cell paging.
QosFlow.Est.Cell5QI 5QI QoS Flow Setup Measurement RAN3.0
QosFlow.Modify.Cell5QI 5QI QoS Flow Modification Measurement RAN3.0 Contained counters related to 5QI on the CU, including the QoS
flow setup, modification, and release, as well as uplink and
QosFlow.Rel.Cell5QI 5QI QoS Flow Release Measurement RAN3.0 downlink traffic volume at the PDCP layer.
PDCP.Cell5QI Cell 5QI PDCP Measurement RAN3.0
Distinguished the number of activated UEs with 5QI and the
Traffic.DuCell5QI DU Cell 5QI Traffic Measurement RAN3.0
throughput except for tail packages.
SI.DuCell DU Cell SI Message Measurement RAN3.0 Contained counters related to SI message transmission times.
MAC.HyperCellTRP Hyper Cell TRP MAC Measurement RAN3.0
Contained counters related to hyper cells, including the traffic
PRB.HyperCellTRP Hyper Cell TRP PRB Measurement RAN3.0
volume and duration at the MAC layer, number of UEs, and PRB.
User.HyperCellTRP Hyper Cell TRP User Number Measurement RAN3.0
N.HO.InterRAT.In.Cell Incoming Inter-RAT Handover Measurement RAN3.0 Contained counters related to incoming inter-RAT handovers.
Collected statistics about NSA-related signaling through the X2
DC.X2Interface X2 Interface DC Measurement RAN3.0 interface. This is because traffic statistics about neighboring cells
cannot be collected in NSA networking due to protocol restrictions.

5G Counter Reporting Interval
 The EMS supports 15-, 30-, and 60-minute measurement periods.

 The measurement period is configurable on the EMS. The gNodeB reports the result
to the EMS at the end of each measurement period. The reporting interval is the
same as the measurement period.
 A common example is a 60-minute long period and a 5-minute short period.

U2020 Performance Management

3GPP PM Protocol Roadmap
 3GPP has discussed E2E KPIs in SA5. In November 2018, some SA networking counters and KPIs are discussed.
However, due to the separation of CUCP and CUUP, retainability KPIs are introduced in 3GPP specifications in June
2019. The implementation in RAN3 is still pending and is not supported in this version yet.
 RAN KPIs (Layer 2 Measurements) are still under discussion and have not been officially released. It is expected that
KPIs inherit the SA5 conclusion.
Impact on the Current TS/TR

TS/TR No. Change Description
Management and orchestration of networks and network slicing;
28.552 NR and NG-RAN performance measurements and assurance data (management and organization networks are sliced; performance
measurement and guarantee data of NR and NG-RAN)
28.554 5G end to end Key Performance Indicators (KPI) (5G E2E KPI)
Add performance measurements for ng-eNB in terms of connectivity with 5GC (management and organization networks are sliced; performance
32.425
measurement and guarantee data of NR and NG-RAN)
32.426 Add performance measurements for EPC in terms of connectivity with NR (added gNodeB performance measurement for the 5G core network)
32.450 Add KPIs for ng-eNB in terms of connectivity with 5GC (added NR performance measurement for the EPC)
32.451 Add KPI requirements for ng-eNB in terms of connectivity with 5GC (added KPI requirements for gNodeB for the 5G core network)
32.455 Add KPIs for EPC in terms of connectivity with NR (added KPI requirements for gNodeB for the 5G core network)

Contents

5G KPI Architecture
In SA architecture, 5G-dedicated
Accessibility accessibility KPIs, retainability KPIs,
and mobility KPIs will be designed.
Retainability SA only
In NSA architecture, it is
recommended that accessibility (planning)
Mobility KPIs, retainability KPIs, and mobility
KPIs be obtained from the LTE side.
KPI architecture
• User Uplink/Downlink Average Throughput
(counter-based) Service integrity • Cell Uplink/Downlink Average Throughput
• PRB Usage
Utilization • CPU Usage
SA & NSA
Availability • Radio Network Unavailability Rate
• Uplink/Downlink Traffic Volume

Traffic • Average/Maximum User Number

KPI Attributes
Range
Description
Name
KPI
Formula
Associated
counter

4G&5G Coordination Measurement in NSA
Data transfer illustration in NSA DC architecture

gNodeB eNodeB
A D
Traffic Evaluation
PDCP PDCP A Upper layer <--> gNodeB PDCP
B gNodeB PDCP <--> gNodeB RLC
MCG
SCG SCG MCG split SCG
split
MCG C gNodeB PDCP <--> eNodeB RLC
bearer split bearer 1 split bearer
bearer 2
bearer 1 bearer 2
B F C E D Upper layer <--> eNodeB PDCP
RLC RLC E eNodeB PDCP <--> eNodeB RLC
F eNodeB PDCP <--> gNodeB RLC
MAC MAC MAC MAC

SgNB Traffic Volume Evaluation
Transmitted Packet Loss Number of Transmitted Number of Lost
Protocol Layer
Traffic Volume Volume Packets Packets
Data sent from the PDCP N.PDCP.Vol.UL.TrfS
N.PDCP.UL.TrfSDU.TxPackets
layer to the upper layer DU.Tx
Downlink data received by N.PDCP.Vol.DL.TrfS

N.PDCP.DL.TrfSDU.RxPackets
the PDCP DU.Rx
Uplink data received by the N.PDCP.Vol.UL.TrfP N.PDCP.UL.TrfSDU.

N.PDCP.UL.TrfPDU.RxPackets
PDCP from the RLC layer DU.Rx RxPacket.Loss
Downlink data sent by the N.PDCP.Vol.DL.TrfP

N.PDCP.DL.TrfPDU.ReTxPackets
PDCP to the RLC layer DU.Tx
Downlink data offloaded by N.PDCP.Vol.DL.X2U. N.PDCP.DL.X2U.Req

N.PDCP.UL.TrfSDU.RxPacket.Loss
PDCP over the X2 interface TrfPDU.Tx RetransPackets
Uplink data offloaded by N.PDCP.Vol.UL.X2U.

N.PDCP.UL.X2U.TrfPDU.RxPackets
PDCP over the X2 interface TrfPDU.Rx
Note: Currently, these counters are measured at the cell level under the NR cell. It does not comply with the
NRM model specified in 3GPP TS 28.541.

Service Integrity KPIs
 Service integrity KPIs are used to evaluate the service quality of end users in the 5G RAN, which include:
 User Uplink/Downlink Average Throughput
 Cell Uplink/Downlink Average Throughput Refer to 3GPP TS 28.554 and 3GPP 28.552.
Successful transmission,
buffer not empty
The last slot shall always
be removed from
Failed transmission block error
ThpTimeDl
calculations since it
Successful transmission,
can be impacted
buffer empty
by packet size of
User Plane (UP) packets.
No transmission, buffer not
empty (e.g. due to contention)
Data arrives to Time (slots)

empty DL buffer
First data is The send buffer is

transmitted to the UE again empty
Remarks: The uplink and downlink

average UE throughput is ThpVolDl = ∑ (kbits)
implemented based on 3GPP TS ∑ + (kbits)

Total DL transferred volume =
28.554 and 3GPP TS 28.552.
UE Throughput in DL = ThpVolDl/ThpTimeDl (kbit/s)

Service Integrity KPIs - User Uplink/Downlink Average Throughput
 These KPIs indicate the average uplink and downlink UE throughputs in a cell.
Name User Uplink Average Throughput Name User Downlink Average Throughput
Measurement Measurement
Cell or RAN Cell or RAN
Object Object
UserULAveThp = UserDLAveThp =
Formula UserULRmvSmallPktTrafficVolume/UserULR Formula UserDLRmvLastSlotTrafficVolume/UserDLRm
mvSmallPktTransferTime vLastSlotTransferTime
User Uplink Average Throughput = User Downlink Average Throughput =

Associated (N.ThpVol.UL – Associated (N.ThpVol.DL –
Counter N.ThpVol.UE.UL.SmallPkt)/N.ThpTime.UE.UL Counter N.ThpVol.DL.LastSlot)/N.ThpTime.DL.RmvLa
.RmvSmallPkt stSlot
Unit Gbit/s Unit Gbit/s

Service Integrity KPIs - Cell Uplink/Downlink Average Throughput
 These KPIs evaluate the uplink/downlink capacity of a cell.
Name Cell Uplink Average Throughput Name Cell Downlink Average Throughput
Object Object
CellULAveThp =
Formula CellDLAveThp =
CellULTrafficVolume/CellULTransferTime Formula
CellDLTrafficVolume/CellDLTransferTime
Cell Uplink Average Throughput =
Cell Downlink Average Throughput =
N.ThpVol.UL.Cell/N.ThpTime.UL.Cell N.ThpVol.DL.Cell/N.ThpTime.DL.Cell
Associated Note: Associated Note:
Counter Counter
When comparing this KPI with the theoretical When comparing this KPI with the theoretical
peak rate for TDD, pay attention to the peak rate for TDD, pay attention to the uplink-
uplink-downlink subframe configuration. downlink subframe configuration.
Unit Gbit/s Unit Gbit/s

Utilization KPIs
 Utilization KPIs are used to evaluate the capabilities, such as the capability to meet
traffic demands, in specific internal conditions. Utilization KPIs include:
 Uplink/Downlink Resource Block Utilizing Rate
 Average CPU Load

Utilization KPIs - Uplink/Downlink Resource Block Utilizing Rate
 These KPIs indicate the busy-hour uplink and downlink RB usages in a cell or RAN.
Name Uplink Resource Block Utilizing Rate Name Downlink Resource Block Utilizing Rate
Object Object
RB_URUL = (RB_UsedUL/RB_AvailableUL) x RB_URDL = (RB_UsedDL/RB_AvailableDL) x
Formula Formula
100% 100%
Uplink Resource Block Utilizing Rate = Downlink Resource Block Utilizing Rate =
Associated Associated
(N.PRB.UL.Used.Avg/N.PRB.UL.Avail.Avg) x (N.PRB.DL.Used.Avg/N.PRB.DL.Avail.Avg) x
Counter Counter
100% 100%
Unit % Unit %

Utilization KPI - Average CPU Load
 This KPI indicates the CPU usage during busy hours.
Name Average CPU Load
Measurement Object CPU
Formula MeanCPUUtility
Associated Counter Average CPU Load = VS.BBUBoard.CPULoad.Mean
Unit %

Availability KPI
 Availability KPIs are used to evaluate the service status of a cell.

 Cell available indicates that the cell can provide EPS bearer services.
 Availability KPI includes radio network unavailability rate.

Availability KPI - Radio Network Unavailability Rate
 This KPI indicates the percentage of time when cells in a radio network are
unavailable.
Name Radio Network Unavailability Rate
Measurement
Radio network
Object
RAN_Unavail_Rate =
Formula (ΣCellUnavailTime/(TheTotalNumberOfCellsInCluster × {SP} x 60)) x
100%
Radio Network Unavailability Rate = ((N.Cell.Unavail.Dur.System +

Associated N.Cell.Unavail.Dur.Manual)/(Number of cells x {SP} x 60)) x 100%
Counter Note: SP represents the reporting period of counters. The unit is
minute.
Unit %

Traffic KPIs
 Traffic KPIs are used to measure the traffic volume on the 5G RAN. Traffic KPIs
include:
 Uplink/Downlink Traffic Volume
 Average/Maximum User Number

Traffic KPIs - Uplink/Downlink Traffic Volume
 These KPIs indicate the uplink and downlink traffic volumes in a cell, which are
measured at the Radio Link Control (RLC) layer.
Name Uplink Traffic Volume Name Downlink Traffic Volume

Object Object
Formula ULTraffic Volume Formula DLTrafficVolume
Associated Associated
Uplink Traffic Volume = N.ThpVol.UL Downlink Traffic Volume =N.ThpVol.DL
Counter Counter
Unit kbit Unit kbit

Traffic KPIs - Average/Maximum User Number
 These KPIs indicate the number of UEs in RRC_CONNECTED mode in a cell.
Name Average User Number Name Maximum User Number

Object Object
Formula AvgUserNumber Formula MaxUserNumber
Associated Average User Number = Associated Maximum User Number =

Counter N.User.RRCConn.Avg Counter N.User.RRCConn.Max
Unit N/A Unit N/A

Accessibility KPIs in SA Networking
 Accessibility KPIs reflect the probability that a UE successfully accesses the network
and initiates services, including:
 RRC connection setup
 NGSIG setup
 QoS flow setup

Accessibility KPI - RRC Setup Success Rate
 This KPI is used to evaluate the RRC connection setup success rate.
Name RRC Setup Success Rate
Measurement
Cell or RAN
Object
Formula RRCS_SR = (RRCSetupSuccess/RRCSetupAttempt) x 100%
Associated RRC Setup Success Rate (Signaling) =

Counter (N.RRC.SetupReq.Succ/N.RRC.SetupReq.Att) x 100%
Unit %

Accessibility KPI - RRC Setup Success Rate (Service)
 This KPI is used to evaluate the RRC connection setup success rate of services.
Name RRC Setup Success Rate (Service)
Measurement Object Cell or RAN
Formula RRCS_SRservice = (RRCSetupSuccessservice/RRCSetupAttemptservice) x 100%
RRC Setup Success Rate (Service) = ((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 +
Associated Counter
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 %

Accessibility KPI - RRC Setup Success Rate (Signaling)
 This KPI is used to evaluate the RRC connection setup success rate of signaling.
Name RRC Setup Success Rate (signaling)
RRCS_SRsignaling = (RRCSetupSuccesssignaling/RRCSetupAttemptsignaling) x
Formula
100%
RRC Setup Success Rate (Signaling) =

Associated Counter
(N.RRC.SetupReq.Succ.MoSig/N.RRC.SetupReq.Att.MoSig) x 100%
Unit %

Accessibility KPI - NGSIG Connection Setup Success Rate
 This KPI is used to evaluate the signaling connection setup success rate of the NG
interface.
Name NGSIG Connection Setup Success Rate
NGSIGS_SR =
Formula
(NGSIGConnectionEstablishSuccess/NGSIGConnectionEstablishAttempt) x 100%
NGSIG Connection Setup Success Rate =

Associated Counter
(N.NGSig.ConnEst.Succ/N.NGSig.ConnEst.Att) x 100%
Unit %

Accessibility KPI - QoS Flow Setup Success Rate
 This KPI is used to evaluate the QoS flow setup success rate of all services.
Name QoS Flow Setup Success Rate
Formula Qos FlowS_SR = (QosFlowSetupSuccess/QosFlowSetupAttempt) x 100%
Associated Counter QoS Flow Setup Success Rate = (N.QosFlow.Est.Succ/N.QosFlow.Est.Att) x 100%
Unit %

Accessibility KPI - Call Setup Success Rate
 This KPI is used to evaluate the call setup success rate of all services.
Name Call Setup Success Rate
CSSR = (RRCSetupSuccessservice/RRCSetupAttemptservice) x
Formula (NGSIGConnectionEstablishSuccess/NGSIGConnectionEstablishAttempt) x
(QosFlowSetupSuccess/QosFlowSetupAttempt) x 100%
Call Setup Success Rate = ((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 +
Associated Counter
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 %

Retainability KPIs in SA Networking
 Retainability KPIs are introduced in 3GPP TS 28.554 at the end of June 2019, as shown in the following figure. The implementation
details are to be confirmed. Retainability KPIs are not supported in this version.
Currently, only the signaling service drop rate (N.QosFlow.AbnormRel/(N.QosFlow.NormRel + N.QosFlow.AbnormRel) is supported.
Remarks: The QoS flow signaling release can be obtained on the original CUCP but there is no data transmission buffer due to the
separation of CUCP and CUUP. This situation is updated in 3GPP specifications but the detailed cause is still being analyzed.

Mobility KPIs in SA Networking
 Mobility KPIs are used to evaluate the mobility performance of the NR network, which
directly reflect user experience. Based on the handover type, mobility KPIs are
classified into the following types:
 Intra-RAT intra-frequency handover KPIs
 Intra-RAT inter-frequency handover KPIs
 Inter-RAT handover KPIs

Mobility KPI - Intra-Frequency Handover Out Success Rate
 This KPI is used to evaluate the intra-NR intra-frequency outgoing handover success
rate.
Name Intra-frequency Handover Out Success Rate
IntraFreqHOOut_SR = (IntraFreqHOOutSuccess/IntraFreqHOOutAttempt) x
Formula
100%
Intra-Frequency Handover Out Success Rate =

((N.HO.IntraFreq.Ng.IntergNB.ExecSuccOut +
N.HO.IntraFreq.Xn.IntergNB.ExecSuccOut +
Associated Counter
N.HO.IntraFreq.IntragNB.ExecSuccOut)/(N.HO.IntraFreq.Ng.IntergNB.ExecAtt
Out + N.HO.IntraFreq.IntragNB.ExecAttOut +
N.HO.IntraFreq.Xn.IntergNB.ExecAttOut)) x 100%
Unit %

Mobility KPI - Inter-Frequency Handover Out Success Rate
 This KPI is used to evaluate the intra-NR inter-frequency outgoing handover success rate.
Name Inter-frequency Handover Out Success Rate
Formula InterFreqHOOut_SR = (InterFreqHOOutSuccess/InterFreqHOOutAttempt) x 100%
Inter-Frequency Handover Out Success Rate =

((N.HO.InterFreq.IntragNB.ExecSuccOut +
N.HO.InterFreq.Xn.IntergNB.ExecSuccOut +
Associated Counters
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 %

Mobility KPI - Intra-RAT Handover In Success Rate
 This KPI is used to evaluate the intra-NR incoming handover success rate.
Name Intra-RAT Handover In Success Rate
Intra-RATHOIn_SR = (Intra-RATHOInSuccess/Intra-RATHOInAttempt) x
Formula
100%
Intra-RAT Handover In Success Rate = ((N.HO.Ng.IntergNB.ExecSuccIn +

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

Mobility KPI - Inter-RAT Handover Out Success Rate (NR to LTE)
 This KPI is used to evaluate the inter-RAT outgoing handover success rate from NR
to LTE.
Name Inter-RAT Handover Out Success Rate (NR to LTE)
IRATHO_N2E_SR = (IRATHO_N2E_Success/IRATHO_N2E_Attempt) x
Formula
100%
Inter-RAT Handover Out Success Rate (NR to LTE) =
Associated Counter (N.HO.InterRAT.N2E.ExecSuccOut)/(N.HO.InterRAT.N2E.ExecAttOut) x
100%
Unit %
Remarks: If the failures caused by the core network do not need to be counted 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%

Mobility KPI - EPSFB Success Rate Based Handover (NR to
E-UTRAN)
 This KPI is used to evaluate the success rate of handover-based EPS fallback from NG-RAN to E-UTRAN.
Name EPSFB Success Rate Based Handover (NR to E-UTRAN)
EPSFB_N2E_BasedHO_SR =
Formula (EPSFB_N2E_BasedHO_Success/EPSFB_N2E_BasedHO_Attempt) x
100%
EPSFB Success Rate Based Handover(NR to E-UTRAN) =

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

KPI Summary
Measurement
Type Name Formula Unit
Object
Average downlink cell throughput (Cell
N.ThpVol.DL.Cell/N.ThpTime.DL.Cell Cell or RAN Gbit/s
Downlink Average Throughput)
Average uplink cell throughput (Cell Uplink Cell Uplink Average Throughput =
Cell or RAN Gbit/s
Average Throughput) N.ThpVol.UL.Cell/N.ThpTime.UL.Cell
Service
(N.ThpVol.UL –
Integrity KPIs Average uplink UE throughput (User Uplink
N.ThpVol.UE.UL.SmallPkt)/N.ThpTime.UE. Cell or RAN Gbit/s
Average Throughput)
UL.RmvSmallPkt
(N.ThpVol.DL-
Average downlink UE throughput (User
N.ThpVol.UE.DL.SmallPkt)/N.ThpTime.UE. Cell or RAN Gbit/s
Downlink Average Throughput)
DL.RmvSmallPkt
Uplink PRB usage (Uplink Resource Block (N.PRB.UL.Used.Avg/N.PRB.UL.Avail.Avg)
Cell or RAN %
Utilizing Rate) x 100%
Utilization Downlink PRB usage (Downlink Resource (N.PRB.DL.Used.Avg/N.PRB.DL.Avail.Avg)
KPIs Cell or RAN %
Block Utilizing Rate) x 100%
Average CPU usage (Average CPU Load) VS.BBUBoard.CPULoad.Mean CPU %

KPI Summary - Cont 1
Type Name Formula Measurement Object Unit

((N.Cell.Unavail.Dur.System +
Radio network unavailability N.Cell.Unavail.Dur.Manual)/(Number of cells x
Availability KPI rate (Radio Network {SP} x 60)) x 100% Radio network %
Unavailability Rate) Note: SP represents the reporting period of
counters. The unit is minute.
Uplink traffic volume (Uplink
N.ThpVol.UL Cell or RAN kbit/s
Traffic Volume)
Downlink traffic volume
N.ThpVol.DL Cell or RAN kbit/s
(Downlink Traffic Volume)
Traffic KPIs
Average UE number (Average
N.User.RRCConn.Avg Cell or RAN N/A
User Number)
Maximum UE number
N.User.RRCConn.Max Cell or RAN N/A
(Maximum User Number)

KPI Summary - Cont 2 (SA Networking)
Measurement
Object
RRC Setup Success Rate N.RRC.SetupReq.Succ/N.RRC.SetupReq.Att
(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 +
RRC Setup Success Rate
N.RRC.SetupReq.Succ.MoVideoCall)/(N.RRC.SetupReq.Att.Emc +
(Service)
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)
Accessibility RRC Setup Success Rate

N.RRC.SetupReq.Succ.MoSig/N.RRC.SetupReq.Att.MoSig Cell or RAN %
KPIs (Signaling)
NGSIG Connection Setup

N.NGSig.ConnEst.Succ/N.NGSig.ConnEst.Att
Success Rate
QoS Flow Setup Success

N.QosFlow.Est.Succ/N.QosFlow.Est.Att
Rate
(RRCSetupSuccessservice/RRCSetupAttemptservice) x
Call Setup Success Rate (NGSIGConnectionEstablishSuccess/NGSIGConnectionEstablishAttempt) x
(QosFlowSetupSuccess/QosFlowSetupAttempt)

KPI Summary - Cont 3 (SA Networking)
Measurement
Object
(N.HO.IntraFreq.Ng.IntergNB.ExecSuccOut +
Intra-Frequency N.HO.IntraFreq.Xn.IntergNB.ExecSuccOut +
Handover Out N.HO.IntraFreq.IntragNB.ExecSuccOut)/(N.HO.IntraFreq.Ng.IntergNB.ExecAtt
Success Rate Out + N.HO.IntraFreq.IntragNB.ExecAttOut +
N.HO.IntraFreq.Xn.IntergNB.ExecAttOut)
(N.HO.InterFreq.IntragNB.ExecSuccOut +
Mobility
Inter-frequency Cell or RAN %
KPIs N.HO.InterFreq.Xn.IntergNB.ExecSuccOut +
Handover Out N.HO.InterFreq.Ng.IntergNB.ExecSuccOut)/(N.HO.InterFreq.IntragNB.ExecAtt
Success Rate Out + N.HO.InterFreq.Xn.IntergNB.ExecAttOut +
N.HO.InterFreq.Ng.IntergNB.ExecAttOut)
Intra-RAT (N.HO.Ng.IntergNB.ExecSuccIn + N.HO.IntragNB.ExecSuccIn +

Handover In N.HO.Xn.IntergNB.ExecSuccIn)/(N.HO.Ng.IntergNB.ExecAttIn +
Success Rate N.HO.IntragNB.ExecAttIn + N.HO.Xn.IntergNB.ExecAttIn)

KPI Summary-Cont 4 (SA Networking)
Measurement
Object
(N.HO.InterRAT.N2E.ExecSuccOut)/(N.HO.InterRAT.N2E.ExecAttOut)
Remarks: If the failures caused by the core network do not need to be
Inter-RAT Handover counted in some scenarios, the following formula can be used:
Out Success Rate 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
Mobility 100% Cell or RAN %
KPIs
EPSFB Success
Rate Based N.HO.InterRAT.N2E.EPSFB.ExecSuccOut/
Handover (NR to E- N.HO.InterRAT.N2E.EPSFB.ExecAttOut
UTRAN)

Air Interface Quality and Efficiency Evaluation – 1 (for Internal
Use Only) d
s an
lysi ve ly.
3GPP TS 38.214 provides typical spectral efficiency for CQIs and MCS n li on
a indexes.
e
al a n th se ting
etic le o al u omo
eor lab tern pr
a th vai r in hen rs.
s is is a is fo n w me
i a o to
Th dat rk. It auti cus
no two se c e to
ne erci atur
Ex s f e
thi

Air Interface Quality and Efficiency Evaluation – 2 (for Internal
Use Only)
Spectral efficiency distribution of CQIs reported by UEs Spectrum efficiency distribution of scheduling Spectral efficiency experienced by users
Implementation assumption: Implementation assumption: Implementation assumption (to be

Proportion of CQI-specific spectral efficiency (spectral Proportion of scheduled spectral efficiency (spectral discussed):
efficiency in the table multiplied by rank value)
s is
efficiency in the table multiplied by rank value) = DL spectral efficiency = DL cell throughput/DL PRB
ly
measure by UE = Specific CQI proportion Proportion of RBs corresponding to the MCS used
Specific CQI proportion = Specific CQI/(All CQIs,
a
Proportion of RBs corresponding to the MCS =
n on
including different CQI tables)
l a
Number of MCS -specific RBs/(Number of all MCS
e
Measurement point: RLC
For example:
a
RBs, including different MCS tables)
c b l If the last timeslot is not excluded, the downlink cell
Proportion of Rank 2 CQI 5 in 256QAM Table = Rank 2 For example:
eti ila or throughput is affected by the traffic model (packet
or ava is f cise is
CQI 5 reporting times in 256QAM Table /(Total number of Proportion of RBs with Rank 2 MCS 10 in 256QAM size). If the last timeslot is excluded, the downlink cell
CQI reportings, including different CQI tables)
t e
Table = Number of RBs with Rank 2 MCS 10 in
h is . It er
256QAM Table/Total number of RBs corresponding to
th
throughput is not affected by the service model.
Proportion of CQI spectral efficiency (spectral efficiency:
a
s data ork y. E otin
the MCS
x g
i
1.9141 x 2) measured by UE = Proportion of Rank 2 CQI Proportion of scheduling spectral efficiency (spectral
is o etw nl m .
5 in 256QAM Table efficiency: 2.5703 x 2) = Proportion of RBs with Rank 2
Measurement point: UE h n n epoint:
T dMeasurement
MCS 10 in 256QAM Table
o MAC r o rs
n liv us n e p e
a l he to Impact m
Factor Impact e
Factor
thUE channel a
n quality
w s Factor Impact
t e r n o c u UE channel quality (coverage) Affected

UE channel quality (coverage) Affected
n io
i utmodel (packet
(coverage)
t size) Affected
Affected
UE traffic model (packet size) Not affected a tur

UE traffic
c e UE traffic model (packet size) Throughput
affected
f ea
Air interface resource Affected
Air interface resource Affected
Air interface resource Not affected Number of scheduling times Affected Number of scheduling times Affected
(traffic model, timeslot, and other (traffic model, timeslot, and other
CQI reporting frequency Affected numerologies are also affected.) numerologies are also affected.)

Introduction to the MCS Index Table in 3GPP TS 38.214
1. The spectral efficiency of the same MCS index in different tables is different. When collecting statistics about spectral efficiency, distinguish between different tables.
2. The following tables apply to RANK1. Different RANKs also affect the spectral efficiency.
3. Corresponding to the spectral efficiency application ratio, it is also necessary to consider the number of scheduled RBs instead of the number of scheduling.
64QAMLowSE table (not supported

64QAM table 256QAM table in the current version)
Scheduling Spectral Efficiency Statistical Method
Suggested method: 5G RAN2.0 statistical method problem:

Spectral efficiency = Spectral efficiency in MCS table x RANK 5G RAN2.0 counter:
Number of times MCS index 0 is scheduled on the PDSCH
Spectral efficiency ratio = RB ratio corresponding to MCS = Number of RBs ...
Number of times MCS index 31 is scheduled on the PDSCH
scheduled by a specific MCS/Number of RBs scheduled by all MCSs
Example: Problem:
Spectral efficiency of table2 MCS index10 with RANK2 = 2.5703 x 2 = 5.1406 1. Did not distinguish MCS index table: Different spectral efficiencies in
different tables.
Ratio of spectral efficiency to 5.1406 = (Number of scheduled RBs in table2
MCS index10)/(Number of RBs scheduled by all MCS) 2. Did not distinguish RANK: With the same MCS, the spectral efficiency
Notes: 2.5703 is from "Table 5.1.3.1-2: MCS index table 2 for PDSCH". of RANK2 may be twice that of RANK1.
3. Did not distinguish RB number: Scheduling 1 RB at a time is the

Original counter design (5G RAN2.1): same as scheduling 100 RBs, which is easy to mislead. For example,
Number of RBs allocated for PDSCH with rank 1 and MCS index 0 in the an MCS schedules 100 times, but one RB at a time, and another MCS
MCS index table with 64QAM schedules 100 RBs at a time, resulting in a difference of 100 times.
...
Number of RBs allocated for PDSCH with rank 4 and MCS index 28 in the
MCS index table with 64QAM
...

Statistical Requirements in 3GPP TS 28.552
The RAN2.1 design is consistent with the protocol requirements, distinguishing the RANK and MCS index tables, and
counting according to the number of RBs.
Statistical requirements in 3GPP TS 28.552

Contents

SgNB Evaluation Dimensions in the NSA Architecture
Evaluation dimensions in the NSA control plane
SgNB addition • SgNB addition success rate
SgNB release • SgNB abnormal release rate
SgNB modification • SgNB PScell modification success rate

SgNB Addition Procedure and Counters
UE MN SN S-GW MME Counter Counter

Counter ID Measurement Point
Name Description
1. SgNB Addition Request
As shown at point A in the figure, the
Number of N.NsaDc.SgNB.Add.Att counter is
2. SgNB Addition Request Acknowledge
SgNB addition incremented by 1 each time the
N.NsaDc.Sg
3. RRCConnectionReconfiguration 1911816746 requests in the gNodeB receives an SgNB Addition
NB.Add.Att
LTE-NR NSA Request message from the eNodeB.
4. RRCConnectionReconfigurationComplete
DC scenario The counter value is accumulated in
5. SgNB Reconfiguration Complete the PSCell specified by the gNodeB.
6. Random Access Procedure
7. SN Status Transfer As shown at point B in the figure,
8. Data Forwarding Number of the N.NsaDc.SgNB.Add.Succ
successful counter is incremented by 1 each
N.NsaDc.Sg SgNB time the gNodeB receives an SgNB
Path Update procedure 9. E-RAB Modification Indication 1911816747
NB.Add.Succ additions in the Reconfiguration Complete message
10. Bearer Modication
11. End Marker Packet LTE-NR NSA from the eNodeB. The counter value
DC scenario is accumulated in the PSCell
12. E-RAB Modification Confirmation
specified by the gNodeB.

SgNB Release Procedure and Counters
Figure 1 SgNB release
Counter Counter
UE MN SN S-GW MME Name Description
1. SgNB Release Request A As shown at point A in Figure 1, the
2. SgNB Release Request Acknowledge N.NsaDc.SgNB.Rel counter is incremented
3. RRCConnectionReconfiguration
by one each time the gNodeB receives an
Total number
4. RRCConnectionReconfigurationComplete SgNB Release Request message from the
of SgNB
eNodeB. As shown at point B in Figure 2,
5. SN Status Transfer
N.NsaDc. releases in
1911816752 the N.NsaDc.SgNB.Rel counter is
6. Data Forwarding SgNB.Rel the LTE-NR
incremented by one each time the gNodeB
7. Secondary RAT Data Volume Report NSA DC
receives an SgNB Release Confirm
scenario
8. Path Update procedure message from the eNodeB. The counter
9. UE Context Release value is accumulated in the PSCell of the
LTE-NR NSA DC UE.
Figure 2 Abnormal SgNB release As shown at points A and B in Figure 2, the

N.NsaDc.SgNB.AbnormRel counter is
UE MN SN S-GW MME incremented by 1 each time when the
Total number following conditions are met: the gNodeB
1. SgNB Release Required A of abnormal receives an SgNB Release Confirm
N.NsaDc. SgNB message from the eNodeB after sending
2. SgNB Release Confirm
B 1911816753 SgNB.Abn releases in an SgNB Release Required message to
4. RRCConnectionReconfigurationComplete ormRel the LTE-NR the eNodeB, the cause in the SgNB
5. SN Status Transfer NSA DC Release Required message is "Radio
6. Data Forwarding
scenario Connection With UE Lost" or "Failure in the
7. Secondary RAT Data Volume report
Radio Interface". The counter value is
8. Path Update procedure accumulated in the PSCell of the LTE-NR
9. UE Context Release NSA DC UE.

SgNB Change Procedure and Counters
Figure 1 Intra-site change
Counter ID Counter Name Counter Description Measurement Point
A As shown at point A in Figure 1, the

N.NsaDc.IntraSgNB.PSCell.Change.Att counter is
Number of Intra-SgNB
N.NsaDc.IntraS incremented by 1 each time the gNodeB sends an
PSCell Change
1911816750 gNB.PSCell.Ch SgNB Modification Required message to the
Attempts in the LTE-
ange.Att eNodeB to request a PSCell change. The counter
NR NSA DC Scenario
value is accumulated in the PSCell of the LTE-NR
NSA DC UE.
B
As shown at point B in Figure 1, the
N.NsaDc.IntraSgNB.PSCell.Change.Succ counter
Number of Successful
N.NsaDc.IntraS is incremented by 1 each time the gNodeB is
Intra-SgNB PSCell
1911816751 gNB.PSCell.Ch notified of a PSCell change via an SgNB
Changes in the LTE-
ange.Succ Modification Confirm message from the eNodeB.
NR NSA DC Scenario
The counter value is accumulated in the PSCell of
Figure 2 Inter-site change the LTE-NR NSA DC UE.
UE MN S-SN T-SN S-GW MME
As shown at point A in Figure 2, the
Number of Inter-SgNB N.NsaDc.InterSgNB.PSCell.Change.Att counter is
A
1. SgNB Change Required
2. SgNB Addition Request N.NsaDc.InterS

PSCell Change incremented by 1 each time the gNodeB sends an
1911816748 gNB.PSCell.Ch
3. SgNB Addition Request Acknowledge
Attempts in the LTE- SgNB Change Required message to the eNodeB.
5. RRCConnectionReconfigurationComplete ange.Att
NR NSA DC Scenario The counter value is accumulated in the PSCell of
8. Random Access Procedure
6. SgNB Change Confirm
B
7. SgNB Reconfiguration Complete the LTE-NR NSA DC UE.
9a. SN Status Transfer
9b. SN Status Transfer As shown at point B in Figure 2, the
Number of Successful N.NsaDc.InterSgNB.PSCell.Change.Succ counter
10. Data Forwarding
N.NsaDc.InterS
Inter-SgNB PSCell is incremented by 1 each time the gNodeB
11. Secondary RAT Data Volume Report 1911816749 gNB.PSCell.Ch
Changes in the LTE- receives an SgNB Change Confirm message from
12. E-RAB Modification Indication
ange.Succ
14. End Marker Packet
13. Bearer Modification
NR NSA DC Scenario the eNodeB. The counter value is accumulated in
15. New Path the PSCell of the LTE-NR NSA DC UE.
16. E-RAB Modification Confirm
17. UE Context Release

SgNB DRB Addition Procedure and Counters
Figure 1
Counter Counter
Name Description
As shown at point A in Figure 1, when the gNodeB

receives an SgNB Addition Request message from the
Number of
eNodeB, the gNodeB adds the value of "E-RABs To Be
DRB Addition
Added List" in the received message to the
N.NsaDc.DRB. Attempts for
1911816754 N.NsaDc.DRB.Add.Att counter. As shown at point A in
Add.Att LTE-NR NSA
Figure 2, when the gNodeB receives an SgNB
DC UEs on
Modification Request message from the eNodeB, the
the SgNB
gNodeB adds the value of "E-RABs To Be Added List" to
the N.NsaDc.DRB.Add.Att counter.
Figure 2
As shown at points B and C in Figure 1, when the
gNodeB receives an SgNB Reconfiguration Complete
message from the eNodeB, the gNodeB adds the value
Number of
of E-RAB number contained in "E-RABs Admitted To Be
Successful
Added Item" of the SgNB Addition Request Acknowledge
DRB
N.NsaDc.DRB. message to the N.NsaDc.DRB.Add.Succ counter. As
1911816755 Additions for
Add.Succ shown at points B and C in Figure 2, when the gNodeB
LTE-NR NSA
receives an SgNB Reconfiguration Complete message
DC UEs on
from the eNodeB, the gNodeB adds the value of E-RAB
the SgNB
number contained in "E-RABs Admitted To Be Added
Item" of the SgNB Modification Request Acknowledge
message to the N.NsaDc.DRB.Add.Succ counter.

SgNB DRB Release Procedure and Counters
Counter Counter Counter

Measurement Point
ID Name Description
Figure 1 Figure 2 As shown at points A and B in Figure 1, when the gNodeB receives an
SgNB Modification Confirm message from the eNodeB, the gNodeB
adds the value of E-RAB number in "E-RABs To Be Released Item" of
the SgNB Modification Required message to the N.NsaDc.DRB.Rel
counter. As shown at point B in Figure 2, when the gNodeB receives
Number of an SgNB Release Confirm message from the eNodeB, the gNodeB
DRB adds the value of E-RAB number contained in "E-RABs To Be
Releases in Released Item" to the N.NsaDc.DRB.Rel counter. As shown at points
191181 N.NsaDc
the SgNB in B and C in Figure 3, when the gNodeB receives an SgNB
6756 .DRB.Rel
LTE-NR NSA Reconfiguration Complete message from the eNodeB, the gNodeB
DC adds the value of E-RAB number contained in "E-RABs Admitted To
Scenarios Be Released Item" of the SgNB Modification Request Acknowledge
Figure 3 Figure 4 message to the N.NsaDc.DRB.Rel counter. As shown at point A in
Figure 4, when the gNodeB receives an SgNB Release Request
message from the eNodeB, the gNodeB adds the value of E-RAB
number contained in "E-RABs To Be Released Item" to the
N.NsaDc.DRB.Rel counter.
As shown at points A and B in Figure 1, when the gNodeB receives an

SgNB Modification Confirm message from the eNodeB, the gNodeB
Number of adds the value of E-RAB number contained in "E-RABs To Be
Abnormal Released Item" to the N.NsaDc.DRB.AbnormRel counter if the cause
DRB value contained in the SgNB Modification Required message is "Radio
N.NsaDc
191181 Releases in Connection With UE Lost" or "Failure in the Radio Interface". As
.DRB.Ab
6757 the SgNB in shown at points A and B in Figure 2, when the gNodeB receives an
normRel
LTE-NR NSA SgNB Release Confirm message from the eNodeB, the gNodeB adds
DC the value of E-RAB number contained in "E-RABs To Be Released
Scenarios Item" to the N.NsaDc.DRB.AbnormRel counter if the cause value
contained in the SgNB Release Required message is "Radio
Connection With UE Lost" or "Failure in the Radio Interface".

Questions
1. Do access and service drops exist in NSA networking? If they do, how to
define them? Is SgNB addition or release equivalent to service drops in
traditional networks? nly
n o
sio
2. What are the objectives of NSA DC networkus optimization? How to evaluate
sc
the quality of an NSA network? al di
r n
nt e
r i
F o

NSA Network KPI Application (Suggestions for China Telecom)
From the perspective of end users, NSA DC is the maximum capability improvement of data services. NSA
DC can be used to improve user experience and relieve LTE capacity pressure, which is the objective of
network optimization.
ion
No. NSA Network Evaluation Points KPI ownership: SgNB
ss n KPI ownership: anchor eNodeB Cause
c u tio rs
is au te
1 Number of NSA UEs N/A Average number of RRC connections of an NSA UE Operator UE promotion
l d c oun . Average number of RRC connections in dual-connectivity

a
2 Proportion of NSA UEs in dual-connectivity state N/A See "3".
h
state/Average number of RRC connections of an NSA UE
r n it c ted
Top causes for low proportion of NSA UEs in dual-
N/A
t e w e N/A Registration on the operator
in se om en
connectivity state - registration on core network
r
Fo ly. U se s plem
(Number of normal SgNB releases triggered by SgNB
Top causes for low proportion of NSA UEs in dual- Service promotion by operators
– Number of SgNB releases triggered by
connectivity state - dual-connectivity release due to no and the requirement of user
on cau t im
coverage)/Number of SgNB releases triggered by
requirement activation
SgNB
3
be e no
Top causes for low proportion of NSA UEs in dual- Resource and configuration
SgNB access: SgNB addition success rate
connectivity state - resource configuration problems
Top causes for low proportion of NSA UEs in dual-

connectivity state - proportion of SgNB releases
triggered by coverage
ar
Number of SgNB releases triggered by
coverage/Number of SgNB releases triggered by
SgNB
Coverage
Top causes for low proportion of NSA UEs in dual- Retainability of the SgNB for NSA UEs in dual-
Coverage
connectivity state - NSA DRB service drop rate connectivity state: NSA DRB service drop rate
SgNB handover (mobility): SgNB change success MeNB handover (mobility): Intra-RAT handover success
4 Coverage continuity (handover) Coverage
rate rate with SN
NSA DC UE proportion vs. split

5 NSA UE traffic proportion N/A Traffic proportion of NSA UE in the eNodeB
data
6 NSA DC user experience User throughput and delay on the gNodeB side

Thank you
www.huawei.com
LTE: NSA DC Feature Evaluation
NSA Architecture NSA DC MeNB Evaluation

• Control plane: LTE
SgNB addition • SgNB access success rate
• User plane:
 GBR services: LTE
 Non-GBR services: LTE and NR,
controlled by a specific algorithm SgNB release • SgNB abnormal release rate
EPC SgNB change • SgNB PSCell change success rate

S1-C S1-U S1-U
• Number of NSA UEs
• NSA option 3X:
LTE
eNodeB
gNodeB Traffic evaluation  Total volume of PDCP traffic
 Volume of PDCP traffic
transferred to MeNB
* Data is transferred to SgNB in option 3x

and to MeNB in option 3.

SgNB Addition Procedure and Counters
Figure 1
UE MeNB SgNB
Total number of SgNB As shown at point A in figure 1, the
addition attempts for UEs L.NsaDc.SgNB.Add.Att counter is
SgNB Addition Request L.NsaDc.SgNB.
1526747851 that treat the local cell as incremented each time the eNodeB
Add.Att
A SgNB Addition Request
their PCell in the LTE-NR sends an SgNB Addition Request
Acknowledge NSA DC state message to the gNodeB.
RRCConnectionReconfiguration
Complete
Total number of successful As shown at point B in figure 1, the
SgNB Reconfiguration Complete SgNB additions for UEs L.NsaDc.SgNB.Add.Succ counter is
L.NsaDc.SgNB.
1526747852 that treat the local cell as incremented each time the eNodeB
B Add.Succ
their PCell in the LTE-NR sends an SgNB Reconfiguration
NSA DC state Complete message to the gNodeB.

SgNB Release Procedure and Counters
Figure 1
UE MeNB SgNB
SgNB Release Request
A As shown at point A in figure 1, the
RRCConnectionReconfiguration L.NsaDc.SgNB.Rmv.Att counter is
incremented each time the eNodeB
RRCConnectionReconfiguration Total number of SgNB
sends an SgNB Release Request
Complete removal attempts for
L.NsaDc.SgNB message to the gNodeB.
1526747855 UEs that treat the local
.Rmv.Att As shown at point A in figure 2, the
cell as their PCell in the
L.NsaDc.SgNB.Rmv.Att counter is
LTE-NR NSA DC state
incremented each time the eNodeB
Figure 2 sends an SgNB Release Confirm
message to the gNodeB.
UE MeNB SgNB
SgNB Release Required

SgNB Release Confirm
A
Complete

Number of SCG Failures
Counter Counter
Name Description
UE EUTRAN
As shown at point A in the figure, the
L.NsaDc.ScgFailure counter is incremented
RRC connection reconfiguration Total number of
(Scg-Configuration) each time the eNodeB receives an
SCG failures for
SCGFailureInfomationNR message from a
L.NsaDc.Scg UEs that treat the
SCGFailureInformation 1526747856 UE. Before that, on the NR side, the UE
Failure local cell as their
experiences a random access failure, the
PCell in the LTE-
A number of RLC retransmissions reaches its
NR NSA DC state
maximum value for the UE, or the SCG
configuration fails for the UE.
After receiving the SCG Failure sent by the UE, the MeNB triggers delivery of the SgNB Release message.

SgNB Change Procedure and Counters

Total number of SCG change attempts L.NsaDc.SCG.Change.Att counter is
1526747853 L.NsaDc.SCG.Change.Att for UEs that treat the local cell as their incremented each time the eNodeB receives an
PCell in the LTE-NR NSA DC state SgNB Change Required message from the
gNodeB.
Total number of successful SCG As shown at point B in Figure 1, the
changes for UEs that treat the local L.NsaDc.SCG.Change.Succ counter is
1526747854 L.NsaDc.SCG.Change.Succ
cell as their PCell in the LTE-NR NSA incremented each time the eNodeB sends an
DC state SgNB Change Confirm message to the gNodeB.

SgNB Modification Procedure and Counters
Number of SCG As shown at point A in Figure 1, the

modification attempts L.NsaDc.SCG.Mod.Req.Att counter
L.NsaDc.SCG. for all LTE-NR NSA is incremented each time the
1526748825
Mod.Req.Att DC UEs that treat the eNodeB sends an SgNB
local cell as their Modification Request message to
PCell the gNodeB.
Number of successful As shown at point B in Figure 1, the

SCG modifications for L.NsaDc.SCG.Mod.Req.Succ
L.NsaDc.SCG. all LTE-NR NSA DC counter is incremented each time
1526748826
Mod.Req.Succ UEs that treat the the eNodeB sends an SgNB
local cell as their Reconfiguration Complete message
PCell to the gNodeB.

Number of SCG
L.NsaDc.SCG.Mod.Required.Att
L.NsaDc.SCG. modification attempts
counter is incremented each time
1526748827 Mod.Required. received by all LTE-
the eNodeB receives an SgNB
Att NR NSA DC UEs in a
Modification Required message
cell
from the gNodeB.
As shown at point B in Figure 2, the

Number of successful
L.NsaDc.SCG.Mod.Required.Succ
L.NsaDc.SCG. SCG modifications
counter is incremented each time
1526748828 Mod.Required. received by all LTE-
the eNodeB sends an SgNB
Succ NR NSA DC UEs in a
Modification Confirm message to
cell
the gNodeB.

Total Number of Abnormal E-RAB Releases for NSA DC UEs
(Newly Added in RAN2.0)
Counter Counter Counter
Measurement Point
ID Name Description
As shown at point A in Figure 2, the L.NsaDc.E-
RAB.AbnormRel counter is incremented for NSA
DC UEs each time the following conditions are
met: (1) The MeNB sends an E-RAB RELEASE
Total number
INDICATION message to the MME. (2) The
of abnormal
release cause is not "Normal Release", "Detach",
L.NsaDc.E- E-RAB
"User Inactivity", "Om-Intervention", "CS Fallback
RAB.Abnor releases in
triggered", "UE Not Available for PS Service",
mRel LTE-NR NSA
"Inter-RAT Redirection", "Successful Handover",
DC scenarios
or "Redirection towards 1xRTT". (3) The
corresponding E-RAB carries data.
If the message requires multiple E-RAB releases
at the same time, the counter is incremented by
the number of E-RABs.

Traffic Volume and User Number
The counter measures the total downlink traffic volume offloaded

Total traffic volume offloaded from UEs in the
from LTE-NR NSA DC UEs in the cell at the PDCP layer to the
L.Thpt.bits.DL.McgSplit.MeNB PCell at the PDCP layer to the MeNB during
MeNB during 3C offloading. The volume of successfully
LTE-NR NSA DC 3C offloading
offloaded SDU data is accumulated as the value of this counter.
The counter measures the total downlink traffic volume offloaded

Total traffic volume offloaded from UEs in the
from LTE-NR NSA DC UEs in the cell at the PDCP layer to the
L.Thpt.bits.DL.McgSplit.SgNB PCell at the PDCP layer to the SgNB during
SgNB during 3C offloading. The volume of successfully offloaded
LTE-NR NSA DC 3C offloading
SDU data is accumulated as the value of this counter.
The counter measures the total uplink traffic volume received at

Total uplink MeNB traffic volume received by
the PDCP layer by LTE-NR NSA DC UEs from the MeNB during
L.Thpt.bits.UL.McgSplit.MeNB UEs in the PCell from the PDCP layer of the
uplink 3C offloading. The volume of successfully received SDU
MeNB during LTE-NR NSA DC 3C offloading
data is accumulated as the value of this counter.
The counter measures the total uplink traffic volume received at
Total uplink SgNB traffic volume received by
the PDCP layer by LTE-NR NSA DC UEs from the SgNB during
L.Thpt.bits.UL.McgSplit.SgNB UEs in the PCell from the PDCP layer of the
uplink 3C offloading. The volume of successfully received SDU
MeNB during LTE-NR NSA DC 3C offloading
data is accumulated as the value of this counter.
The number of all UEs in connected mode (in both the LTE PCell
Average number of UEs that treat the local and the NR PSCell) that are in the LTE-NR NSA DC state and
L.Traffic.User.NsaDc.PCell.Avg cell as their PCell in the LTE-NR NSA DC treat the local cell as their PCell are sampled per second in a
state cell. At the end of a measurement period, the average of these
sampling results is taken as the counter value.

Training Course - 5G RAN3.0 KPI Introduction V1.00

Uploaded by

Copyright:

Available Formats

Training Course - 5G RAN3.0 KPI Introduction V1.00

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

Training Course - 5G RAN3.0 KPI Introduction V1.00

Uploaded by

Copyright:

Available Formats

Introduction to 5G RAN3.

Copyright © Huawei Technologies Co., Ltd. All rights reserved.

 Upon completion of this course, you will be able to:

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 2

1. Basic Concepts of 5G Counters

3. 5G Counters for NSA Evaluation

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 3

 Counter organization: Counter -> Function subset -> Measurement object

Function Measurement Measurement Function Measurement

Counter 1 Counter 2 Counter 3 Counter 4 Counter 5 Counter 6 Counter 7 ... ...

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 4

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 5

Measures the 5QI performance of NR cells. Users can

Measures the 5QI performance of NR DU cells. Users

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 6

5G Network Resource Model (28.541) According to 3GPP TS 28.541, Network

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 7

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 8

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 9

Measurement per MCS Index in the MCS

Measurement per MCS Index in the MCS

Measurement per MCS Index in the MCS

Measurement per MCS Index in the MCS

Measurement per MCS Index in the MCS

Measurement of CQIs in the CQI Table with

Measurement of CQIs in the CQI Table with

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 10

PRB200To272.Interference.DuCell Uplink Interference Measurement on PRB 200 to PRB 272 NRDUCEL

PRB100To199.Interference.DuCell Uplink Interference Measurement on PRB 100 to PRB 199 NRDUCEL

Paging.Cell Cell Paging Measurement NRCELL

QosFlow.Est.Cell5QI 5QI QoS Flow Setup Measurement NRCELL.5QI

QosFlow.Modify.Cell5QI 5QI QoS Flow Modification Measurement NRCELL.5QI

QosFlow.Rel.Cell5QI 5QI QoS Flow Release Measurement NRCELL.5QI

PDCP.Cell5QI Cell 5QI PDCP Measurement NRCELL.5QI 5G RAN3.0

Traffic.DuCell5QI DU Cell 5QI Traffic Measurement NRDUCELL.5QI

SI.DuCell DU Cell SI Message Measurement NRDUCELL

MAC.HyperCellTRP Hyper Cell TRP MAC Measurement NRDUCELL

PRB.HyperCellTRP Hyper Cell TRP PRB Measurement NRDUCELL

User.HyperCellTRP Hyper Cell TRP User Number Measurement NRDUCELL

N.HO.InterRAT.In.Cell Incoming Inter-RAT Handover Measurement NRCELL

DC.X2Interface X2 Interface DC Measurement NRCELL

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 11

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 12

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 13

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 14

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 15

 The EMS supports 15-, 30-, and 60-minute measurement periods.

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 16

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 17

Impact on the Current TS/TR

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 18

1. Basic Concepts of 5G Counters

3. 5G Counters for NSA Evaluation

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 19

• Uplink/Downlink Traffic Volume

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 20

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 21

Data transfer illustration in NSA DC architecture

B gNodeB PDCP <--> gNodeB RLC