5G RAN2.

0 KPI Introduction
I ntroduction

HUAWEI TECHNOLOGIES CO., LTD.

Catalog
1 Basic Concepts of Counters

2 KPI Description

3 5G Counters for NSA Evaluation

Evaluation
 Counter Organization
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.
Measurement Measurement
object 1 object 2

Function set 1 Function set 2 Function set 3

Function Function … Function Function Function

subset 1 subset 2 subset n subset m subset l 

Counter 1 Counter 2 Counter 3 Counter 4 Counter 5 Counter 6 Counter 7 Counter 8 … …

Service Measurement Object, Function Set, and Function Subset
in 5G RAN2.0

Measurement Object ID Measurement Object Name Description Introduced In

The NRCELL measurement object contains
Measurement of Cell Performance
NRCELL cell-level function subsets. Cells are deployed RAN1.0
(NRCELL)
on gNodeB central units (CUs).

Measurement of Local Cell The NRDUCELL measurement object

NRDUCELL RAN1.0
Performance
Performance (NRDUCELL
(NRDUCELL)) contains NR DU cell function subsets.

The gNodeB measurement object contains

Measurement of gNodeB Performance
gNodeB gNodeB-level function subsets, which indicate RAN1.0
(gNodeB)
the operating status of gNodeBs.

The gNodeB
gNodeB measurement object contains
Measurement of gNodeB DU
gNodeB
gNodeB distributio
distributionn unit function
function subsets,
gNBDU Performance(gNBDU) RAN2.0
which indicate the operating status of gNodeB
distribution unit.

• * 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
CloudRAN is introduced.
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 c orresponding function subsets are
5G Service Counter Report Interval

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.
U2000 Performance Management
Catalog
1 Basic Concepts of Counters

2 KPI Description

3 5G Counters for NSA Evaluation

 5G KPI Architecture

Accessibility In NSA architecture, it is recommended that accessibility

KPIs, retainability KPIs, and mobility KPIs be obtained
from the LTE side.
Retainability In SA architecture, 5G-dedicated accessibility KPIS, SA only
retainability KPIs, and mobility KPIs will be designed. (will support in 5G
RAN2.1)
Mobility

KPI
architecture • User Uplink/Downlink Average Throughput
Service Integrity • Cell Uplink/Downlink Average Throughput
(counter-based)
• Uplink/Downlink Resource Block Utilizing Rate
Utilization
•  Average CPU load
SA & NSA
Availability • Radio Network Unavailability Rate

• Uplink/Downlink Traffic Volume

Traffic
•  Average/Maximum User Number 
KPI Attributes

Object

Description

Name
KPI
Formula

 Associated
counter 
Service Integrity KPIs

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.
Traffic Volume/Throughput Counter Design
Data transfer illustration in NSA DC architecture Comparison between RAN measurement and UE measurement
gNodeB eNodeB MeNB SgNB UE-LTE Cell UE-5G Cell UE Perception

PDCP traffic MCG bearer+MCG split SCG bearer +SCGsplit Cell-specific PDCP traffic volume is not 1. Total traffic volume
volume bearer  bearer  measured. 2. Service rate. In SA
scenarios, the 5QI may
not map to the DRB in
one-to-one mode.
3. Rates of the following
 A PDCP PDCP PDCP
transmission
MCG bearer+MCG split SCG bearer+SCGsplit bearers (for PDCP):
bearer  bearer  MCGbearer 
duration
MCG split bearer 
SCG bearer 
SCG split bearer 

MCG bearer+MCG SCG bearer+MCG

split bearer 2+SCG split bearer 1+SCG Rates of the following
MCG bearer+MCG split SCG bearer+MCG split split bearer 2 split bearer 1 bearers:
SCG split MCG split MCG RLC traffic
SCG SCG split MCG split bearer 2+SCG split bearer bearer 1+SCG split (The RLC traffic (The RLC traffic MCGbearer 
bearer 2 bearer 2 bearer  volume
bearer  bearer 1 bearer 1 2 bearer 1 volume is measured in volume is measured MCG split bearer 1
the PCell in MeNB CA in the PCell in SeNB SCG split bearer 2

B RLC RLC
scenarios.) CA scenarios.)
SCG bearer 
RLC MCG bearer+MCG split SCG bearer+MCG split MCG split bearer 2
transmission bearer 2+SCG split bearer  bearer 1+SCG split SCG split bearer 2
duration 2 bearer 1

C (MCG bearer+MCG split

bearer 2+SCG split bearer
(SCG bearer +MCG
split bearer 1+SCG
(MCG+MCG split
bearer 2+SCG split
(SCG bearer +MCG
split bearer 1+SCG
MAC traffic 2) split bearer 1)
bearer 2) split bearer 1)
volume Volume of traffic transmitted Volume of traffic
MAC MAC MAC MAC over the air interface of a transmitted over the air
CC-specific traffic
volume
CC-specific traffic
volume
specific DU cell interface of a DU cell

(SCG bearer +MCG
(MCG bearer+MCG split
split bearer 1+SCG
SCG bearer - option 3A (not supported in versions RAN1.0 and MAC
bearer 2+SCG split bearer
split bearer 1)
RAN2.0) 2)
SCG split bearer - option 3X transmission
Duration of transmission
Duration of
duration transmission over the
MCG bearer  over the air interface of a
air interface of a
specific DU cell
specific DU cell
MCG split bearer - option 3
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 thatUE 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 thatcell rates be measured at the MAC layer 
 Service Integrity KPIs  – User Uplink/Downlink Average Throughput
These KPIs indicate the average uplink and downlink UE throughputs in a cell.
Name User Up link Ave ra ge Throu ghp ut Na me Us er D ownlin k Ave rage T hro ugh put

Object Cell or RAN Object Cell or RAN

UserULAveThp = UserDLAveThp =
Formula Formula
UserULRmvSmallPktTrafficVolume/UserULRmvSmallPktTransferTime UserDLRmvLastSlotTrafficVolume/UserDLRmvLastSlotTransferTime

 Associated User Uplink Average Throughput = (N.ThpVol.UL-  Associated User Downlink Average Throughput = (N.ThpVol.DL -
Counter  N.ThpVol.UE.UL.SmallPkt)/N.ThpTime.UE.UL.RmvSmallPkt Counter  N.ThpVol.DL.LastSlot)/N.ThpTime.DL.RmvLastSlot

Unit Gbit/s Unit Gbit/s

RAN2.0

RAN1.0 Name User Uplink Average Throughput Name User Downlink Average Throughput

Object Cell or RAN Object Cell or RAN

UserULAveThp =
Formula Formula UserDLAveThp = UserDLTrafficVolume/UserDLTransferTime
UserULTrafficVolume/UserULTransferTime

 Associated User Uplink Average Throughput =  Associated User Downlink Average Throughput =
Counter  N.ThpVol.UL/N.ThpTime.UL Counter  N.ThpVol.DL/N.ThpTime.DL

Unit Gbps Unit Gbps

Service Integrity KPIs  – Cell Uplink/Downlink Average Throughput

These KPIs indicate the average uplink and downlink cell throughputs, which reflect the cell capacity.

Name Cell Uplink Average Throughput Name Cell Downlink Average Throughput

Object Cell or RAN Object Cell or RAN

CellULAveThp =
Formula Formula CellDLAveThp = CellDLTrafficVolume/CellDLTransferTime
CellULTrafficVolume/CellULTransferTime

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  When comparing this KPI with the theoretical peak rate Counter 
When comparing this KPI with the theoretical peak rate for
for TDD, pay attention to the uplink-downlink subframe TDD, pay attention to the uplink-downlink subframe
configuration. configuration.
Unit Gbit/s Unit Gbit/s

Note: The throughputs are measured based on MAC TBs.

Utilization KPIs

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
Note: Since 5G standards in 3GPP protocols are under discussion, the preceding KPIs may be changed in
later versions.
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 Cell or RAN Object Cell or RAN

Formula RB_URUL = (RB_UsedUL/RB_AvailableUL) x 100% Formula RB_URDL = (RB_UsedDL/RB_AvailableDL) x 100%

 Associated Uplink Resource Block Utilizing Rate =  Associated Downlink Resource Block Utilizing Rate =
Counter  (N.PRB.UL.Used.Avg/N.PRB.UL.Avail.Avg) x 1 00% Counter  (N.PRB.DL.Used.Avg/N.PRB.DL.Avail.Avg) x 10 0%

Unit % Unit %
Utilization KPI  – Average CPU Load

This KPI indicates the CPU usage during busy hours.

Name Average CPU Load

Object CPU

Formula MeanCPUUtility

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

Unit %
Availability KPI

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  – Radio Network Unavailability Rate

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.

Name Rad io Ne twork Un availa bility Ra te

Object Radio Network

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

Radio Network Unavailability Rate =((N.Cell.Unavail.Dur.System + N.Cell.Unavail.Dur.Manual)/(Number

 Associated
of cells x {SP} x 60)) x 100%
Counter 
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. In RAN2.0, utilization
KPIs include:
 Uplink/Downlink Traffic Volume
  Average/Maximum User Number 
Note: Since 5G standards in 3GPP protocols are under discussion, the preceding KPIs may be changed in
later versions.
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.

Na me Uplink Traffic Volume Na me Down link Tra ffic Volume

Object Cell or RAN Object Cell or RAN

Formula ULTrafficVolume F ormula DLTrafficVo lume

 Associated  Associated
Uplink Traffic Volume = N.ThpVol.UL Downlink Traffic Volume = N.ThpVol.DL
Counter  Counter 

Unit kbit 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   Name Maximum User Number  

Object Cell or RAN Object Cell or RAN

Formula AvgUserNumber  Formula MaxUserNumber 

 Associated  Associated
Maximum User Number = N.User.RRCConn.Max
Counter   Average User Number = N.User.RRCConn.Avg Counter 

Unit N/A Unit N/A

Catalog
1 Basic Concepts of Counters

2 KPI Description

3 5G Counters for NSA Evaluation

RAN2.0 NSA Architecture and SgNB Evaluation

NSA Architecture NSA 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

SgNB
• SgNB PSCell change success rate
EPC modification
S1-C S1-U S1-U

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

UE MN SN S-GW MME  As shown at points A and B in figure 2,

after the gNodeB sends an SgNB Release
Required message with the cause value of
3.
RRCConnectionRecon
1. SgNB Release Required
 A Number of
"Radio Connection With UE Lost" or
figuration 2. SgNB Release Confirm
abnormal
4.
B N.NsaDc.
SgNB
"Failure in the Radio Interface" to the
RRCConnectionRecon SgNB.Abn eNodeB, if the gNodeB receives an SgNB
figurationComplete releases in the
5. SN Status Transfer  ormRel Release Confirm message from the
LTE-NR NSA
6. Data Forwarding eNodeB, the N.NsaDc.SgNB.AbnormRel
DC scenario
7. Secondary RAT Data
Volume report
counter is incremented by 1. The counter
value is accumulated in the PSCell of LTE-
8. Path Update procedure
NR NSA DC UEs.
9. UE Context Release
SgNB Modification Procedure and Counters
Figure 1 Change to an intra-site gNodeB
Counter Counter
Measurement Point
Name Description

 A N.NsaDc.In
Number of intra-  As shown at point A in figure 1, the
SgNB PSCell N.NsaDc.IntraSgNB.PSCell.Change.Att counter
traSgNB.P
change requests is incremented by 1 each time the gNodeB
SCell.Chan
in the LTE-NR sends an SgNB Modification Required message
ge.Att
NSA DC scenario to the eNodeB to request a PSCell change.
Number of  As shown at point B in figure 1, the
B N.NsaDc.In successful intra- N.NsaDc.IntraSgNB.PSCell.Change.Succ
traSgNB.P SgNB PSCell counter is incremented by 1 each time the
SCell.Chan changes in the gNodeB is notified of a PSCell change via an
ge.Succ LTE-NR NSA DC SgNB Modification Confirm message from the
scenario eNodeB.
 As shown at point A in figure 2, the
Figure 2 Change to inter-site gNodeB Number of inter- N.NsaDc.InterSgNB.PSCell.Change.Att
N.NsaDc.In
UE MN S-SN T-SN S-GW MME SgNB PSCell counter is incremented by 1 each time the
terSgNB.P
change requests gNodeB sends an SgNB Change Required
4.
1. SgNB Change Required

2. SgNB Addition Request  A SCell.Chan

in the LTE-NR message to the eNodeB. The counter value is
RRCConnectionRecon
figuration
3. SgNB Addition Request
 Acknowledge ge.Att
5.
NSA DC scenario accumulated in the PSCell of the LTE-NR NSA
RRCConnectionRecon
figurationComplete
6. SgNB Change Confirm
DC UE.

8. Random Access Procedure

7. SgNB Reconfiguration
Complete B  As shown at point B in figure 2, the
Number of
9a. SN Status Transfer  N.NsaDc.InterSgNB.PSCell.Change.Succ
9b. SN Status Transfer  N.NsaDc.In successful inter-
10. Data Forwarding counter is incremented by 1 each time the
terSgNB.P SgNB PSCell
11. Secondary RAT Data gNodeB receives an SgNB Change Confirm
Volume Report SCell.Chan changes in the
12. E-RAB Modification
Indication message from the eNodeB. The counter value is
13. Bearer Modification ge.Succ LTE-NR NSA DC
accumulated in the PSCell of the LTE-NR NSA
14. End Marker Packet
scenario
16. E-RAB Modification
15. New Path DC UE.
Confirm
Number of SgNB DRB Additions
Figure 1 Counter Counter
Measurement Point
Name Description
 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-
Number of DRB
RABs To Be Added List" to the
addition requests
N.NsaDc.D N.NsaDc.DRB.Add.Att counter.
for LTE-NR NSA
RB.Add.Att  As shown at point A in figure 2, when the
DC UEs on the
gNodeB receives an SgNB Modification
SgNB
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 points B and C in figure 1, when
Figure 2
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 Added
Number of Item" of the SgNB Addition Request
successful DRB  Acknowledge message to the
N.NsaDc.D
additions for N.NsaDc.DRB.Add.Succ counter.
RB.Add.Su
LTE-NR NSA DC  As shown at points B and C in figure 2, when
cc
UEs on the the gNodeB receives an SgNB Reconfiguration
SgNB Complete message from the eNodeB, the
gNodeB adds the value of E-RAB number
contained in "E-RABs Admitted To Be Added
Item" of the SgNB Modification Request
 Acknowledge message to the
 Number of SgNB DRB Releases
Figure 1
Counter
Counter Description Measurement Point
Name

 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
Figure 2 number contained in "E-RABs To Be Released Item" to the N.NsaDc.DRB.Rel
Number of DRB counter.
N.NsaDc.DRB releases for LTE-NR  As shown at points B and C in figure 3, when the gNodeB receives an SgNB
.Rel NSA DC UEs on the Reconfiguration Complete message from the eNodeB, the gNodeB adds the
SgNB 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
Figure 3 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.

 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 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
Figure 4 Number of abnormal
in the Radio Interface".
N.NsaDc.DRB DRB releases for
 As shown at points A and B in figure 2, when the gNodeB receives an SgNB
.AbnormRel LTE-NR NSA DC
Release Confirm message from the eNodeB, the gNodeB adds the value of E-
UEs on the SgNB
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
 SgNB Traffic Evaluation
In NSA architecture, traffic volume is evaluated using the counters listed in the following table.
N.PDCP.UL.TrfSDU.TxPackets
N.PDCP.DL.TrfSDU.RxPackets
N.PDCP.Vol.UL.TrfSDU.Tx
N.PDCP.Vol.DL.TrfSDU.Rx
N.PDCP.DL.TrfPDU.TxPackets
N.PDCP.UL.TrfPDU.RxPackets
N.PDCP.DL.TrfPDU.ReTxPackets
N.PDCP.Vol.DL.TrfPDU.Tx
N.PDCP.Vol.UL.TrfPDU.Rx
N.PDCP.UL.TrfSDU.RxPacket.Loss
Number of PDCP SDUs for DRBs transmi tted to the upper
layer in a cell
Number of SDUs for DRBs received at the P DCP layer in a
cell
Traffic of PDCP SDUs for DRBs transmitted to the upper layer Number of SDUs transmitted to or
received from the upper layer and the
in a cell
volume of the SDUs
Traffic of SDUs for DRBs received at the PDCP layer in a cell
Number of PDCP PDUs for DRBs transmi tted to the RLC layer
in a cell
Number of RLC PDUs for DRBs received at the PDCP layer in Uplink PDCP packet loss
a cell
Number of PDCP PDUs retransmitted to the RLC layer i n a Number of PDUs transmitted to
cell or received from the lower layer
Traffic of PDCP PDUs for DRBs transmitted to the RLC layer and the volume of the PDUs
in a cell
Traffic of RLC PDUs for DRBs received at the PDCP layer in a Number of PDUs
cell transmitted to LTE and
Number of lost uplink PDCP SDUs for DRBs in a cell the volume of the PDUs

Number of PDCP PDUs transmitted in the downlink over the Downlink air
N.PDCP.DL.X2U.TrfPDU.TxPackets
X2 interface in a cell interface packet loss
Number of PDCP PDUs for DRBs received i n the uplink over
N.PDCP.UL.X2U.TrfPDU.RxPackets
the X2
Number of PDCP PDUs retransmitted in the downlink over the
N.PDCP.DL.X2U.ReqRetransPackets
X2 interface in a cell
Traffic of PDCP PDUs for DRBs transmitted in the downlink
N.PDCP.Vol.DL.X2U.TrfPDU.Tx
over the X2 interface in a cell
Traffic of PDCP PDUs for DRBs received in the uplink over the
N.PDCP.Vol.UL.X2U.TrfPDU.Rx
X2 interface in a cell

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
 Thank you
www.huawei.com

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

SgNB
• SgNB PSCell change success rate
EPC modification
S1-C S1-U S1-U

LTE
  gNodeB • Number of NSA UEs
eNodeB
Traffic evaluation • 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 MeNB
  SgNB
Counter Name Counter Description Measurement Point

Total number of SgNB  As shown at point A in figure 1, the

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

UE MeNB
  SgNB

SgNB Release Request Counter Name Counter Description Measurement Point

A

RRCConnectionReconfiguration  As shown at point A in figure 1, the

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

SgNB Release Confirm

RRCConnectionReconfiguration

RRCConnectionReconfiguration
Complete
 SgNB Modification Procedure and Counters
Figure 1
Counter Name Counter Description Measurement Point
UE MeNB S-SgNB T-SgNB

 As shown at point A in figure 1, the

SgNB Change Required
L.NsaDc.SCG.Change.Att counter is incremented
A
SgNB Addition Request each time the eNodeB receives an SgNB Change
SgNB Addition Request Required message from the gNodeB.
 Acknowledge
RRCConnectionReconfiguration
 As shown at point A in figure 2, the
RRCConnectionReconfiguration Total number of SCG change L.NsaDc.SCG.Change.Att counter is incremented
Complete
SgNB Change Confirm L.NsaDc.SCG. attempts for UEs that treat the each time the eNodeB sends an SgNB Modification
Change.Att local cell as their PCell in the Request message to the gNodeB.
B
LTE-NR NSA DC state  As shown at point A in figure 4, the
Figure 2 L.NsaDc.SCG.Change.Att counter is incremented
each time the eNodeB receives an SgNB
UE MeNB
  SgNB
Modification Required message from the gNodeB.
The counter is incremented in the PCell of UEs in
SgNB Modification Request
the LTE-NR NSA DC state.
A

SgNB Modification Request  As shown at point B in figure 2, the

RRCConnectionReconfiguration
RRCConnectionReconfiguration
Complete
Figure 3
UE
RRCConnectionReconfiguration
RRCConnectionReconfiguration
Complete
 Acknowledge
L.NsaDc.SCG.Change.Succ counter is
incremented each time the eNodeB sends an SgNB
SgNB Reconfiguration Complete
Change Confirm message to the g NodeB.
 As shown at point B in figure 3, the
Total number of successful
B L.NsaDc.SCG.Change.Succ counter is
SCG changes for UEs that
L.NsaDc.SCG. incremented each time the eNodeB sends an SgNB
treat the local cell as their
Change.Succ Reconfiguration Complete message to the gNodeB.
PCell in the LTE-NR NSA DC
MeNB
  SgNB  As shown at point B in figure 4, the
state
L.NsaDc.SCG.Change.Succ counter is
SgNB Modification Required incremented each time the eNodeB sends an SgNB
A Modification Confirm message to the gNodeB.
The counter is incremented in the PCell of UEs in
the LTE-NR NSA DC state.
SgNB Modification Confirm
 Number of PCell Change Executions and Successful PCell
Changes in the LTE-NR NSA DC State (Newly Added in RAN2.0)
Figure 1 Counter 
Counter ID Counter Name Measurement Point
Description
Total number  As shown at point A in figure 1,
of PCell L.NsaDc.PCell.Change.Exec counter is incremented
L.NsaDc.PCell.Ch change each time the source MeNB sends an
ange.Exec executions in RRCConnectionReconfiguration message containing
the LTE-NR
the configuration indicator of the SgNB handover to
NSA DC state.
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.
Figure 2
 As shown at point A in figure 2,
Total number L.NsaDc.PCell.Change.Exec is incremented each time
of successful
L.NsaDc.PCell.Ch the source MeNB sends an
PCell changes
ange.Succ RRCConnectionReconfiguration message containing
in the LTE-NR
NSA DC state. 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.

Successful MeNB changes is defined as follows: Change with SgNB.

That is, the SgNB remains the same after MeNB changes.
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 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
Total number
and the release cause is not normal release,
L.NsaDc.E- of abnormal
detach, user inactivity, Om-intervention, CS
RAB.Abnorm E-RAB
fallback triggered, UE not available for PS
Rel releases in
service and inter-RAT redirection.
the LTE-NR
NSA DC state.
If the E-RAB RELEASE INDICATION
message requires to release multiple E-
RABs at the same t ime, the counter value is
accumulated according to the number of E-
RAB.
Number of SCG-Related Failures

Counter ID Counter Name Counter Description Measurement Point

UE
RRC connection reconfiguration
(Scg-Configuration)
SCGFailureInformation
EUTRAN
 As shown at point A in this figure, the
Total number of SCG- L.NsaDc.ScgFailure counter is
related failures for UEs incremented each time the eNodeB
L.NsaDc.ScgFail
1526747855 that treat the local cell as receives an SCGFailureInformation
ure
their PCell in the LTE-NR message from the UE. The counter 
NSA DC state value is accumulated in the PCell of
A
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
L.Thpt.bits.DL.McgSplit.MeNB
L.Thpt.bits.DL.McgSplit.SgNB
L.Thpt.bits.UL.McgSplit.MeNB
L.Thpt.bits.UL.McgSplit.SgNB
 
L.Traffic.User.NsaDc.PCell.Avg cell as their PCell in the LTE-NR NSA DC
Counter Description
Total traffic volume offloaded from UEs in the
PCell at the PDCP layer to the MeNB during
LTE-NR NSA DC Option3 offloading
Total traffic volume offloaded from UEs in the
PCell at the PDCP layer to the SgNB during
LTE-NR NSA DC Option3 offloading
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
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
Average number of UEs that treat the local
state
Measurement Point
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.
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.
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.
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.
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 PM Protocol Roadmap

• 3GPP has discussed E2E KPI in SA5. Slicing and

Impacted existing TS/TR
latency is to be updated in June 2018. The UE
Target completion
throughput depending on RAN2 has not been TS/TR No. Description of change
plenary#
discussed yet.  Add performance measurements for ng-eNB in terms of connectivity with
32.425 SA#80 (Jun 2018)
5GC
• The RAN KPI (Layer 2 Measurements) is to be
32.426  Add performance measurements for EPC in terms of connectivity with NR SA#80 (Jun 2018)
discussed in the RAN2, including the UE
32.450  Add KPIs for ng-eNB in terms of connectivity with 5GC SA#80 (Jun 2018)
throughput. The RAN2 mainly deals with t he
32.451  Add KPI requirements for ng-eNB in terms of connectivity with 5GC SA#80 (Jun 2018)
NSA/SA basic protocol and has not been planned
32.455  Add KPIs for EPC in terms of connectivity with NR SA#80 (Jun 2018)
for discussion.

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)

End to end KPIs, Performance measurements and assurance data for 5G networks and
"28.XXX" SA#79 (Mar 2018) SA#80 (Jun 2018)
network slicing