409282776-5G-RAN2-0-KPI-Introduction.pptx

HUAWEI TECHNOLOGIES CO., LTD.
5G RAN2.0 KPI Introduction

2 Huawei Confidential
Catalog
Basic Concepts of Counters
1
KPI Description
2
5G Counters for NSA Evaluation
3

Counter Organization
Measurement
object 1
Measurement
object 2
Function
subset 1
Function
subset 2
Counter 1
Function
subset l
Function
subset n
…
Function set 3
Function set 1
Function
subset m
Counter 2 Counter 3 Counter 6
Counter 4 Counter 5 Counter 7 Counter 8 … …
Function set 2
Counter organization:
1. Counter -> Function subset -> Measurement object
2. Counter -> Function subset -> Function set
Each counter belongs to only one function subset.
Each function subset belongs to only one measurement object and only one function set.

Service Measurement Object, Function Set, and Function Subset
in 5G RAN2.0
• * In RAN2.0, the NRLOCELL MO is renamed "NRDUCELL" due to configuration object changes. The corresponding function subsets are
also renamed.
• The configuration model of CloudRAN becomes more complicated than that of integrated base stations. Therefore, there are more
measurement objects after CloudRAN is introduced.
Measurement Object ID Measurement Object Name Description Introduced In
NRCELL
Measurement of Cell Performance
(NRCELL)
The NRCELL measurement object contains
cell-level function subsets. Cells are deployed
on gNodeB central units (CUs).
RAN1.0
NRDUCELL
Measurement of Local Cell
Performance (NRDUCELL)
The NRDUCELL measurement object
contains NR DU cell function subsets.
RAN1.0
gNodeB
Measurement of gNodeB Performance
(gNodeB)
The gNodeB measurement object contains
gNodeB-level function subsets, which indicate
the operating status of gNodeBs.
RAN1.0
gNBDU
Measurement of gNodeB DU
Performance(gNBDU)
The gNodeB measurement object contains
gNodeB distribution unit function subsets,
which indicate the operating status of gNodeB
distribution unit.
RAN2.0

Service Function Subsets in 5G RAN2.0
Function Subset ID Function Subset Name Function Set Measurement Object Introduced In
PDCP.Cell PDCP Measurement PDCP NRCELL RAN1.0
User.Cell Cell User Quantity Measurement Traffic NRCELL RAN1.0
Reserve.Cell Cell Reserved Counter Measurement Reserve NRCELL RAN1.0
Thp.DuCell Throughput and Data Volume Measurement Traffic NRDUCELL RAN1.0
PRB.DuCell PRB Measurement RadioRes NRDUCELL RAN1.0
RLC.DuCell RLC Measurement RLC NRDUCELL RAN1.0
MAC.DuCell MAC Measurement MAC NRDUCELL RAN1.0
ChMeas.MCS. DuCell MCS Measurement ChMeas NRDUCELL RAN1.0
ChMeas.CQI. DuCell CQI Measurement ChMeas NRDUCELL RAN1.0
ChMeas.Pwr. DuCell Channel Quality Measurement ChMeas NRDUCELL RAN1.0
RA.DuCell Random Access Measurement RadioRes NRDUCELL RAN1.0
DC.Cell DC Measurement Algo NRDUCELL RAN1.0
Traffic.TRPIP.gNodeB gNodeB Transmission Interface Measurement Transport gNodeB RAN2.0
Traffic.TRPIP.gNBDU gNBDU Transmission Interface Measurement Transport gNBDU RAN2.0
Algo.Cell Cell Algorithm Measurement Algo NRCELL RAN2.0
Algo.gNodeB gNodeB Algorithm Measurement Algo gNodeB RAN2.0
CallAtt.gNBDU gNodeB DU Call Processing Times Sig gNBDU RAN2.0
CallAtt.gNodeB gNodeB Call Processing Times Sig gNodeB RAN2.0
MIMO.DuCell MIMO Channel Measurement ChMeas NRDUCELL RAN2.0
CA.Cell Cell CA Measurement Algo NRDUCELL RAN2.0
CA.DuCell DU Cell CA measurement Algo NRDUCELL RAN2.0
UlDlDecoupling.Cell Uplink and Downlink Decoupling Measurement Algo NRDUCELL RAN2.0
• * In RAN2.0, the NRLOCELL MO is renamed "NRDUCELL" due to configuration object changes. The corresponding function subsets are
also renamed.

Report Interval
 A gNodeB reports measurement results to the U2020 at the end of each measurement period. Therefore, the length
of a report interval equals the length of measurement period.
 The measurement period is configurable on the U2020. The length of a long measurement period can be 30 minutes
or 60 minutes, and the length of a short measurement period can be 5 minutes or 15 minutes. Only one long
measurement period and one short measurement period can be configured.
5G Service Counter Report Interval

U2000 Performance Management

Catalog
1
KPI Description
2
3

5G KPI Architecture
Accessibility
Retainability
Mobility
Service Integrity
Traffic
KPI
architecture
(counter-based)
SA only
SA & NSA
Availability
Utilization
• User Uplink/Downlink Average Throughput
• Cell Uplink/Downlink Average Throughput
• Uplink/Downlink Resource Block Utilizing Rate
• Average CPU load
In NSA architecture, it is recommended that accessibility
KPIs, retainability KPIs, and mobility KPIs be obtained
from the LTE side.
In SA architecture, 5G-dedicated accessibility KPIS,
retainability KPIs, and mobility KPIs will be designed.
• Radio Network Unavailability Rate
• Uplink/Downlink Traffic Volume
• Average/Maximum User Number
(will support in 5G
RAN2.1)

KPI Attributes
Description
Object
Formula
Associated
counter
KPI
Name

Service integrity KPIs are used to evaluate the service quality of end-users in the 5G RAN.
In RAN2.0, service integrity KPIs include:
 User Uplink/Downlink Average Throughput
 Cell Uplink/Downlink Average Throughput
Note: Since 5G standards in 3GPP protocols are under discussion, the preceding KPIs may be changed in
later versions.
Service Integrity KPIs

SCG bearer - option 3A (not supported in versions RAN1.0 and
RAN2.0)
SCG split bearer - option 3X
MCG bearer
MCG split bearer - option 3
A PDCP
RLC RLC
PDCP
MAC
MAC MAC
MAC
gNodeB eNodeB
B
C
SCG split
bearer 1
SCG split
bearer 2
MCG split
bearer 1
MCG split
bearer 2
SCG
bearer
MCG
bearer
Data transfer illustration in NSA DC architecture Comparison between RAN measurement and UE measurement
1. In DC scenarios, the transmit/receive traffic volume and corresponding rate cannot be accurately measured for 5G at the PDCP layer. It is recommended that UE rates be measured at the RLC layer.
2. In CA scenarios, the rate and traffic volume over the air interface of a specific 5G cell cannot be accurately measured at the RLC layer. It is recommended that cell rates be measured at the MAC layer.
Traffic Volume/Throughput Counter Design
MeNB SgNB UE-LTE Cell UE-5G Cell UE Perception
PDCP traffic
volume
MCG bearer+MCG split
bearer
SCG bearer+SCG split
bearer
Cell-specific PDCP traffic volume is not
measured.
1. Total traffic volume
2. Service rate. In SA
scenarios, the 5QI may
not map to the DRB in
one-to-one mode.
3. Rates of the following
bearers (for PDCP):
MCG bearer
MCG split bearer
SCG bearer
SCG split bearer
PDCP
transmission
duration
bearer
SCG bearer+SCG split
bearer
RLC traffic
volume
bearer 2+SCG split bearer
2
SCG bearer+MCG split
bearer 1+SCG split
bearer 1
MCG bearer+MCG
split bearer 2+SCG
split bearer 2
(The RLC traffic
volume is measured in
the PCell in MeNB CA
scenarios.)
SCG bearer+MCG
split bearer 1+SCG
split bearer 1
(The RLC traffic
volume is measured
in the PCell in SeNB
CA scenarios.)
Rates of the following
bearers:
MCG bearer
MCG split bearer 1
SCG split bearer 2
SCG bearer
MCG split bearer 2
SCG split bearer 2
RLC
transmission
duration
2
SCG bearer+MCG split
bearer 1+SCG split
bearer 1
MAC traffic
volume
(MCG bearer+MCG split
2)
Volume of traffic transmitted
over the air interface of a
specific DU cell
(SCG bearer+MCG
split bearer 1+SCG
split bearer 1)
Volume of traffic
transmitted over the air
interface of a DU cell
(MCG+MCG split
bearer 2+SCG split
bearer 2)
CC-specific traffic
volume
(SCG bearer+MCG
split bearer 1+SCG
split bearer 1)
CC-specific traffic
volume
MAC
transmission
duration
(MCG bearer+MCG split
2)
Duration of transmission
over the air interface of a
specific DU cell
(SCG bearer+MCG
split bearer 1+SCG
split bearer 1)
Duration of
transmission over the
air interface of a
specific DU cell

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
Object Cell or RAN
Formula
UserULAveThp =
UserULRmvSmallPktTrafficVolume/UserULRmvSmallPktTransferTime
Associated
Counter
User Uplink Average Throughput = (N.ThpVol.UL-
N.ThpVol.UE.UL.SmallPkt)/N.ThpTime.UE.UL.RmvSmallPkt
Unit Gbit/s
Name User Downlink Average Throughput
Object Cell or RAN
Formula
UserDLAveThp =
UserDLRmvLastSlotTrafficVolume/UserDLRmvLastSlotTransferTime
Associated
Counter
User Downlink Average Throughput = (N.ThpVol.DL -
N.ThpVol.DL.LastSlot)/N.ThpTime.DL.RmvLastSlot
Unit Gbit/s
Note: The throughputs are measured based on RLC SDUs. For the KPI design, see the appendix.
Name User Uplink Average Throughput
Object Cell or RAN
Formula UserULAveThp =
UserULTrafficVolume/UserULTransferTime
Associated
Counter
User Uplink Average Throughput =
N.ThpVol.UL/N.ThpTime.UL
Unit Gbps
Name User Downlink Average Throughput
Object Cell or RAN
Formula UserDLAveThp = UserDLTrafficVolume/UserDLTransferTime
Associated
Counter
User Downlink Average Throughput =
N.ThpVol.DL/N.ThpTime.DL
Unit Gbps
RAN2.0
RAN1.0

Service Integrity KPIs – Cell Uplink/Downlink Average Throughput
These KPIs indicate the average uplink and downlink cell throughputs, which reflect the cell capacity.
Note: The throughputs are measured based on MAC TBs.
Name Cell Uplink Average Throughput
Object Cell or RAN
Formula
CellULAveThp =
CellULTrafficVolume/CellULTransferTime
Associated
Counter
Cell Uplink Average Throughput =
N.ThpVol.UL.Cell/N.ThpTime.UL.Cell
Note:
When comparing this KPI with the theoretical peak rate
for TDD, pay attention to the uplink-downlink subframe
configuration.
Unit Gbit/s
Name Cell Downlink Average Throughput
Object Cell or RAN
Formula CellDLAveThp = CellDLTrafficVolume/CellDLTransferTime
Associated
Counter
Cell Downlink Average Throughput =
N.ThpVol.DL.Cell/N.ThpTime.DL.Cell
Note:
When comparing this KPI with the theoretical peak rate for
TDD, pay attention to the uplink-downlink subframe
configuration.
Unit Gbit/s

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

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
Object Cell or RAN
Formula RB_URUL = (RB_UsedUL/RB_AvailableUL) x 100%
Associated
Counter
Uplink Resource Block Utilizing Rate =
(N.PRB.UL.Used.Avg/N.PRB.UL.Avail.Avg) x 100%
Unit %
Name Downlink Resource Block Utilizing Rate
Object Cell or RAN
Formula RB_URDL = (RB_UsedDL/RB_AvailableDL) x 100%
Associated
Counter
Downlink Resource Block Utilizing Rate =
(N.PRB.DL.Used.Avg/N.PRB.DL.Avail.Avg) x 100%
Unit %

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

An available cell indicates that it can provide EPS bearer services.
In RAN1.0, availability KPI is not supported.
In RAN2.0, availability KPI includes:
 Radio network unavailability rate
Availability KPI

Name Radio Network Unavailability Rate
Object Radio Network
Formula RAN_Unavail_Rate = (ΣCellUnavailTime/(TheTotalNumberOfCellsInCluster x {SP} x 60)) x 100%
Associated
Counter
Radio Network Unavailability Rate =((N.Cell.Unavail.Dur.System + N.Cell.Unavail.Dur.Manual)/(Number
of cells x {SP} x 60)) x 100%
SP represents the reporting period of counters. The unit is minute.
Unit %
This KPI indicates the percentage of time when cells in a radio network are unavailable. It is used to evaluate
the deterioration of network performance caused by cell unavailability of the radio network during busy hours.
Availability KPI – Radio Network Unavailability Rate

Traffic KPIs are used to measure the traffic volume on the 5G RAN. In RAN2.0, utilization
KPIs include:
 Uplink/Downlink Traffic Volume
 Average/Maximum User Number
later versions.
Traffic KPIs

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
Object Cell or RAN
Formula ULTraffic Volume
Associated
Counter
Uplink Traffic Volume = N.ThpVol.UL
Unit kbit
Name Downlink Traffic Volume
Object Cell or RAN
Formula DLTrafficVolume
Associated
Counter
Downlink Traffic Volume = N.ThpVol.DL
Unit kbit

Traffic KPI – Average/Maximum User Number
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 at the end
of each measurement period.
Name Average User Number
Object Cell or RAN
Formula AvgUserNumber
Associated
Counter Average User Number = N.User.RRCConn.Avg
Unit N/A
Name Maximum User Number
Object Cell or RAN
Formula MaxUserNumber
Associated
Counter
Maximum User Number = N.User.RRCConn.Max
Unit N/A

Catalog
1
KPI Description
2
3

NSA Evaluation
RAN2.0 NSA Architecture and SgNB Evaluation
EPC
LTE
eNodeB
gNodeB
S1-C S1-U
S1-U
NSA Architecture
• Control plane: LTE
• User plane:
 GBR services: LTE
 Non-GBR services: LTE and NR,
controlled by a specific algorithm
SgNB addition
SgNB release
SgNB
modification
Traffic evaluation
• SgNB access success rate
• SgNB abnormal release rate
• SgNB PSCell change success rate
• Number of NSA UEs
• NSA option 3X:
 Total volume of PDCP traffic
 Volume of PDCP traffic
transferred to MeNB
* Data split from SgNB in option 3X
* Data split from MeNB in option 3.

SgNB Addition Procedure and Counters
UE MN SN S-GW MME
1. SgNB Addition Request
Acknowledge
3.
RRCConnectionRecon
figuration
4.
RRCConnectionRecon
figurationComplete
9. E-RAB Modification
Indication
5. SgNB Reconfiguration
Complete
Confirmation
10. Bearer Modication
7. SN Status Transfer
8. Data Forwarding
6. Random Access Procedure
Path Update procedure
11. End Marker Packet
A
B
Counter
Name
Counter
Description
Measurement Point
N.NsaDc.S
gNB.Add.A
tt
Number of
SgNB
addition
requests in
the LTE-NR
NSA DC
scenario
As shown at point A in the figure,
the N.NsaDc.SgNB.Add.Att
counter is incremented by 1
each time the gNodeB receives
an SgNB Addition Request
message from the eNodeB. The
counter value is accumulated in
the PSCell specified by the
gNodeB.
N.NsaDc.S
gNB.Add.S
ucc
Number of
successful
SgNB
additions in
the LTE-NR
NSA DC
scenario
As shown at point B in the figure,
the N.NsaDc.SgNB.Add.Succ
counter is incremented by 1
each time the gNodeB receives
an SgNB Reconfiguration
Complete message from the
eNodeB. The counter value is
accumulated in the PSCell
specified by the gNodeB.

UE MN SN S-GW MME
1. SgNB Release Required
3.
RRCConnectionRecon
figuration
4.
RRCConnectionRecon
figurationComplete
6. Data Forwarding
8. Path Update procedure
2. SgNB Release Confirm
9. UE Context Release
7. Secondary RAT Data
Volume report
UE MN SN S-GW MME
3.
RRCConnectionRecon
figuration
4.
RRCConnectionRecon
figurationComplete
6. Data Forwarding
8. Path Update procedure
1. SgNB Release Request
Volume Report
2. SgNB Release Request
Acknowledge
SgNB Release Procedure and Counters
A
B
Counter
Name
Counter
Description
Measurement Point
N.NsaDc.
SgNB.Rel
Total number
of SgNB
releases in the
LTE-NR NSA
DC scenario
As shown at point A in figure 1, the
N.NsaDc.SgNB.Rel counter is incremented
by 1 each time the gNodeB receives an
SgNB Release Request message from the
eNodeB. As shown at point B in figure 2,
the N.NsaDc.SgNB.Rel counter is
incremented by 1 each time the gNodeB
receives an SgNB Release Confirm
message from the eNodeB. The counter
value is accumulated in the PSCell of LTE-
NR NSA DC UEs.
N.NsaDc.
SgNB.Abn
ormRel
Number of
abnormal
SgNB
releases in the
LTE-NR NSA
DC scenario
As shown at points A and B in figure 2,
after the gNodeB sends an SgNB Release
Required message with the cause value of
"Radio Connection With UE Lost" or
"Failure in the Radio Interface" to the
eNodeB, if the gNodeB receives an SgNB
Release Confirm message from the
eNodeB, the N.NsaDc.SgNB.AbnormRel
counter is incremented by 1. The counter
value is accumulated in the PSCell of LTE-
NR NSA DC UEs.
A

UE MN S-SN S-GW MME
9a. SN Status Transfer
10. Data Forwarding
1. SgNB Change Required
T-SN
Acknowledge
4.
RRCConnectionRecon
figuration
5.
RRCConnectionRecon
figurationComplete
7. SgNB Reconfiguration
Complete
Indication
Confirm
13. Bearer Modification
14. End Marker Packet
15. New Path
8. Random Access Procedure
9b. SN Status Transfer
6. SgNB Change Confirm
Volume Report
SgNB Modification Procedure and Counters
A
B
Counter
Name
Counter
Description
Measurement Point
N.NsaDc.In
traSgNB.P
SCell.Chan
ge.Att
Number of intra-
SgNB PSCell
change requests
in the LTE-NR
NSA DC scenario
N.NsaDc.IntraSgNB.PSCell.Change.Att counter
is incremented by 1 each time the gNodeB
sends an SgNB Modification Required message
to the eNodeB to request a PSCell change.
N.NsaDc.In
traSgNB.P
SCell.Chan
ge.Succ
Number of
successful intra-
SgNB PSCell
changes in the
LTE-NR NSA DC
scenario
As shown at point B in figure 1, the
N.NsaDc.IntraSgNB.PSCell.Change.Succ
counter is incremented by 1 each time the
gNodeB is notified of a PSCell change via an
SgNB Modification Confirm message from the
eNodeB.
N.NsaDc.In
terSgNB.P
SCell.Chan
ge.Att
Number of inter-
SgNB PSCell
change requests
in the LTE-NR
NSA DC scenario
N.NsaDc.InterSgNB.PSCell.Change.Att
gNodeB sends an SgNB Change Required
message to the eNodeB. The counter value is
accumulated in the PSCell of the LTE-NR NSA
DC UE.
N.NsaDc.In
terSgNB.P
SCell.Chan
ge.Succ
Number of
successful inter-
SgNB PSCell
changes in the
LTE-NR NSA DC
scenario
N.NsaDc.InterSgNB.PSCell.Change.Succ
gNodeB receives an SgNB Change Confirm
message from the eNodeB. The counter value is
accumulated in the PSCell of the LTE-NR NSA
DC UE.
A
Figure 1 Change to an intra-site gNodeB
Figure 2 Change to inter-site gNodeB
B

Number of SgNB DRB Additions
Counter
Name
Counter
Description
Measurement Point
N.NsaDc.D
RB.Add.Att
Number of DRB
addition requests
for LTE-NR NSA
DC UEs on the
SgNB
As shown at point A in figure 1, when the
gNodeB receives an SgNB Addition Request
message from the eNodeB, the gNodeB adds
the value of E-RAB number contained in "E-
RABs To Be Added List" to the
N.NsaDc.DRB.Add.Att counter.
As shown at point A in figure 2, when the
gNodeB receives an SgNB Modification
Request message from the eNodeB, the
gNodeB adds the value of E-RAB number
contained in "E-RABs To Be Added List" to the
N.NsaDc.DRB.Add.Att counter.
N.NsaDc.D
RB.Add.Su
cc
Number of
successful DRB
additions for
LTE-NR NSA DC
UEs on the
SgNB
As shown at points B and C in figure 1, when
the gNodeB receives an SgNB Reconfiguration
Complete message from the eNodeB, the
contained in "E-RABs Admitted To Be Added
Item" of the SgNB Addition Request
Acknowledge message to the
N.NsaDc.DRB.Add.Succ counter.
As shown at points B and C in figure 2, when
the gNodeB receives an SgNB Reconfiguration
Complete message from the eNodeB, the
contained in "E-RABs Admitted To Be Added
Item" of the SgNB Modification Request
Acknowledge message to the
N.NsaDc.DRB.Add.Succ counter.
Figure 1
Figure 2

Number of SgNB DRB Releases
Counter
Name
Counter Description Measurement Point
N.NsaDc.DRB
.Rel
Number of DRB
releases for LTE-NR
NSA DC UEs on the
SgNB
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 an SgNB Release
Confirm 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 B and C in figure 3, when the gNodeB receives an SgNB
Reconfiguration Complete message from the eNodeB, the gNodeB adds the
value of E-RAB number contained in "E-RABs Admitted To Be Released Item"
of the SgNB Modification Request Acknowledge 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. The counter value is accumulated in the PSCell of LTE-NR NSA DC
UEs.
N.NsaDc.DRB
.AbnormRel
Number of abnormal
DRB releases for
LTE-NR NSA DC
UEs on the SgNB
Modification Confirm 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.AbnormRel counter if the cause value contained in the SgNB
Modification Required message is "Radio Connection With UE Lost" or "Failure
in the Radio Interface".
Release Confirm 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.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".
The counter value is accumulated in the PSCell of LTE-NR NSA DC UEs.
Figure 1
Figure 2
Figure 3
Figure 4

N.PDCP.UL.TrfSDU.TxPackets
Number of PDCP SDUs for DRBs transmitted to the upper
layer in a cell
N.PDCP.DL.TrfSDU.RxPackets
Number of SDUs for DRBs received at the PDCP layer in a
cell
N.PDCP.Vol.UL.TrfSDU.Tx
Traffic of PDCP SDUs for DRBs transmitted to the upper layer
in a cell
N.PDCP.Vol.DL.TrfSDU.Rx Traffic of SDUs for DRBs received at the PDCP layer in a cell
N.PDCP.DL.TrfPDU.TxPackets
Number of PDCP PDUs for DRBs transmitted to the RLC layer
in a cell
N.PDCP.UL.TrfPDU.RxPackets
Number of RLC PDUs for DRBs received at the PDCP layer in
a cell
N.PDCP.DL.TrfPDU.ReTxPackets
Number of PDCP PDUs retransmitted to the RLC layer in a
cell
N.PDCP.Vol.DL.TrfPDU.Tx
Traffic of PDCP PDUs for DRBs transmitted to the RLC layer
in a cell
N.PDCP.Vol.UL.TrfPDU.Rx
Traffic of RLC PDUs for DRBs received at the PDCP layer in a
cell
N.PDCP.UL.TrfSDU.RxPacket.Loss Number of lost uplink PDCP SDUs for DRBs in a cell
N.PDCP.DL.X2U.TrfPDU.TxPackets
Number of PDCP PDUs transmitted in the downlink over the
X2 interface in a cell
N.PDCP.UL.X2U.TrfPDU.RxPackets
Number of PDCP PDUs for DRBs received in the uplink over
the X2
N.PDCP.DL.X2U.ReqRetransPackets
Number of PDCP PDUs retransmitted in the downlink over the
N.PDCP.Vol.DL.X2U.TrfPDU.Tx
Traffic of PDCP PDUs for DRBs transmitted in the downlink
over the X2 interface in a cell
N.PDCP.Vol.UL.X2U.TrfPDU.Rx
Traffic of PDCP PDUs for DRBs received in the uplink over the
SgNB Traffic Evaluation
In the NSA architecture, the average/maximum user number of NSA DC is evaluated using the N.User.NsaDc.PSCell.Avg counter.
In the NSA architecture, the number of RRC users is evaluated using the N.User.RRCConn.Avg counter and the N.User.RRCConn.Max
counter. These two counters are also applicable to SA.
In NSA architecture, traffic volume is evaluated using the counters listed in the following table.
Number of PDUs
transmitted to LTE and
the volume of the PDUs
Number of SDUs transmitted to or
received from the upper layer and the
volume of the SDUs
Number of PDUs transmitted to
or received from the lower layer
and the volume of the PDUs
Downlink air
interface packet loss
Uplink PDCP packet loss

Copyright © 2018 Huawei Technologies Co., Ltd. All Rights Reserved.
The information in this document may contain predictive statements including, without limitation, statements regarding the future financial and
operating results, future product portfolio, new technology, etc. There are a number of factors that could cause actual results and developments to
differ materially from those expressed or implied in the predictive statements. Therefore, such information is provided for reference purpose only and
constitutes neither an offer nor an acceptance. Huawei may change the information at any time without notice.
Thank you
www.huawei.com

LTE: NSA DC Feature Evaluation
NSA DC MeNB Evaluation
EPC
LTE
eNodeB
gNodeB
S1-C S1-U
S1-U
SgNB addition
SgNB release
SgNB
modification
Traffic evaluation
• SgNB access success rate
• SgNB abnormal release rate
• SgNB PSCell change success rate
• Number of NSA UEs
• NSA option 3X:
 Total volume of PDCP traffic
 Volume of PDCP traffic
transferred to MeNB
NSA Architecture
• Control plane: LTE
• User plane:
 GBR services: LTE
 Non-GBR services: LTE and NR, controlled by a
specific algorithm
* Data split from SgNB in option 3X
* Data split from MeNB in option 3.

SgNB Addition Procedure and Counters
Counter Name Counter Description Measurement Point
L.NsaDc.SgNB.
Add.Att
Total number of SgNB
addition attempts for UEs
that treat the local cell as
their PCell in the LTE-NR
NSA DC state
L.NsaDc.SgNB.Add.Att counter is
incremented each time the eNodeB
sends an SgNB Addition Request
message to the gNodeB.
L.NsaDc.SgNB.
Add.Succ
Total number of
successful SgNB
additions for UEs that
treat the local cell as
NSA DC state
L.NsaDc.SgNB.Add.Succ counter is
sends an SgNB Reconfiguration
Complete message to the gNodeB.
SgNB Addition Request
MeNB
UE SgNB
Acknowledge
A
B
RRCConnectionReconfiguration
Complete
SgNB Reconfiguration Complete

SgNB Release Procedure and Counters
L.NsaDc.SgNB.
Rmv.Att
Total number of SgNB
removal attempts for UEs
NSA DC state
L.NsaDc.SgNB.Rmv.Att counter is
sends an SgNB Release Request
L.NsaDc.SgNB.Rmv.Att counter is
sends an SgNB Release Confirm
SgNB Release Request
MeNB
UE SgNB
A
Complete
SgNB Release Required
MeNB
UE SgNB
Complete
SgNB Release Confirm
A
Figure 2
Figure 1

SgNB Modification Procedure and Counters
L.NsaDc.SCG.
Change.Att
Total number of SCG change
attempts for UEs that treat the
local cell as their PCell in the
LTE-NR NSA DC state
L.NsaDc.SCG.Change.Att counter is incremented
each time the eNodeB receives an SgNB Change
Required message from the gNodeB.
each time the eNodeB sends an SgNB Modification
Request message to the gNodeB.
each time the eNodeB receives an SgNB
Modification Required message from the gNodeB.
The counter is incremented in the PCell of UEs in
the LTE-NR NSA DC state.
L.NsaDc.SCG.
Change.Succ
Total number of successful
SCG changes for UEs that
treat the local cell as their
PCell in the LTE-NR NSA DC
state
L.NsaDc.SCG.Change.Succ counter is
incremented each time the eNodeB sends an SgNB
Change Confirm message to the gNodeB.
Reconfiguration Complete message to the gNodeB.
Modification Confirm message to the gNodeB.
The counter is incremented in the PCell of UEs in
the LTE-NR NSA DC state.
Figure 2
Figure 1
SgNB Change Required
MeNB
UE S-SgNB
A
B
Complete
SgNB Change Confirm
T-SgNB
Acknowledge
SgNB Modification Request
MeNB
UE SgNB
A
B
Complete
SgNB Reconfiguration Complete
SgNB Modification Request
Acknowledge
SgNB Modification Required
MeNB
UE SgNB
A
B
Complete
SgNB Modification Confirm
Figure 3

Number of PCell Change Executions and Successful PCell
Changes in the LTE-NR NSA DC State (Newly Added in RAN2.0)
Counter ID Counter Name
Counter
Description
Measurement Point
L.NsaDc.PCell.Ch
ange.Exec
Total number
of PCell
change
executions in
the LTE-NR
NSA DC state.
As shown at point A in figure 1,
L.NsaDc.PCell.Change.Exec counter is incremented
each time the source MeNB sends an
RRCConnectionReconfiguration message containing
the configuration indicator of the SgNB handover to
UEs.
As shown at point B in figure 1,
L.NsaDc.PCell.Change.Succ counter is incremented
each time the source MeNB receives an UE Context
Release message from the target MeNB if the
RRCConnectionReconfiguration message contains the
configuration indicator of the SgNB handover at point B.
As shown at point A in figure 2,
L.NsaDc.PCell.Change.Exec is incremented each time
the source MeNB sends an
RRCConnectionReconfiguration message containing
the configuration indicator of the SgNB handover to
UEs.
As shown at point B in figure 3,
L.NsaDc.PCell.Change.Succ is incremented each time
the source MeNB receives an
RRCConnectionReconfigurationComplete message
from UE. The counter value is accumulated in the PCell
of the LTE-NR NSA DC UE.
L.NsaDc.PCell.Ch
ange.Succ
Total number
of successful
PCell changes
in the LTE-NR
NSA DC state.
Successful MeNB changes is defined as follows: Change with SgNB.
That is, the SgNB remains the same after MeNB changes.
Figure 1
Figure 2

Total Number of Abnormal E-RAB Releases for NSA DC UEs
(Newly Added in RAN2.0)
Counter
ID
Counter
Name
Counter
Description
Measurement Point
L.NsaDc.E-
RAB.Abnorm
Rel
Total number
of abnormal
E-RAB
releases in
the LTE-NR
NSA DC state.
As shown at point A in this figure,
L.NsaDc.E-RAB.AbnormRel is incremented
each time MeNB sends an E-RAB
RELEASE INDICATION message to MME.
The counter value is accumulated if the
corresponding bearer has data transmission
and the release cause is not normal release,
detach, user inactivity, Om-intervention, CS
fallback triggered, UE not available for PS
service and inter-RAT redirection.
If the E-RAB RELEASE INDICATION
message requires to release multiple E-
RABs at the same time, the counter value is
accumulated according to the number of E-
RAB.

Number of SCG-Related Failures
SCGFailureInformation
UE EUTRAN
RRC connection reconfiguration
(Scg-Configuration)
A
Counter ID Counter Name Counter Description Measurement Point
1526747855
L.NsaDc.ScgFail
ure
Total number of SCG-
related failures for UEs
NSA DC state
As shown at point A in this figure, the
L.NsaDc.ScgFailure counter is
receives an SCGFailureInformation
message from the UE. The counter
value is accumulated in the PCell of
the LTE-NR NSA DC UE.
4 scenarios will be counted as SCG Failure.
I. SCG RLF,
II. SN change failure,
III. SCG configuration failure (only for messages on SRB3),
IV. SCG RRC integrity check failure (on SRB3) ,

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

• 3GPP has discussed E2E KPI in SA5. Slicing and
latency is to be updated in June 2018. The UE
throughput depending on RAN2 has not been
discussed yet.
• The RAN KPI (Layer 2 Measurements) is to be
discussed in the RAN2, including the UE
throughput. The RAN2 mainly deals with the
NSA/SA basic protocol and has not been planned
for discussion.
3GPP PM Protocol Roadmap
New specifications
Series Title For info at TSG# For approval at TSG#
"28.XXX" Performance Management for 5G networks and network slicing; stage 1 SA#79 (Mar 2018) SA#80 (Jun 2018)
"28.XXX" Performance Management for 5G networks and network slicing; stage 2 and stage 3 SA#79 (Mar 2018) SA#80 (Jun 2018)
"28.XXX" Performance measurements and assurance data for NG-RAN Network Functions SA#79 (Mar 2018) SA#80 (Jun 2018)
"28.XXX" Performance measurements and assurance data for 5GC Network Functions SA#79 (Mar 2018) SA#80 (Jun 2018)
"28.XXX"
End to end KPIs, Performance measurements and assurance data for 5G networks and
network slicing
SA#79 (Mar 2018) SA#80 (Jun 2018)
Impacted existing TS/TR
TS/TR No. Description of change
Target completion
plenary#
32.425
Add performance measurements for ng-eNB in terms of connectivity with
5GC
SA#80 (Jun 2018)
32.426 Add performance measurements for EPC in terms of connectivity with NR SA#80 (Jun 2018)
32.450 Add KPIs for ng-eNB in terms of connectivity with 5GC SA#80 (Jun 2018)
32.451 Add KPI requirements for ng-eNB in terms of connectivity with 5GC SA#80 (Jun 2018)
32.455 Add KPIs for EPC in terms of connectivity with NR SA#80 (Jun 2018)

1. LTE Layer 2 measurement methods
are defined in 36.314.
2. Some KPIs rely on MDT
(minimization of drive tests), such as
Packet Delay, Packet Discard Rate
in the DL per QCI, Scheduled IP
Throughput for MDT. 5G MDT will be
discussed in Release 16 (Jun 2019),
So these KPIs are not implemented
now.
The impact of Layer 2 measurement undefined
The contents of LTE Layer 2 Measurements in Protocol 36.314.

409282776-5G-RAN2-0-KPI-Introduction.pptx

Recommended

Recommended

More Related Content

Similar to 409282776-5G-RAN2-0-KPI-Introduction.pptx

Similar to 409282776-5G-RAN2-0-KPI-Introduction.pptx (20)

Recently uploaded

Recently uploaded (20)

409282776-5G-RAN2-0-KPI-Introduction.pptx

Editor's Notes