5.1.2 Performance measurements valid only for non-split gNB deployment scenario

28.5523GPP5G performance measurementsManagement and orchestrationRelease 18TS

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

5.1.2.1 PDCP Data Volume

5.1.2.1.1 DL PDCP SDU Data Volume Measurements

5.1.2.1.1.1 DL Cell PDCP SDU Data Volume

This measurement provides the Data Volume (amount of PDCP SDU bits) in the downlink delivered to PDCP layer. The measurement is calculated per PLMN ID and per QoS level (mapped 5QI) and per S-NSSAI.
The unit is Mbit.

b) CC.

c) This measurement is obtained by counting the number of bits entering the NG-RAN PDCP layers. The measurement is performed at the PDCP SDU level. The measurement is performed per configured PLMN ID and per QoS level (mapped 5QI) and per S-NSSAI.

d) Each measurement is an integer value representing the number of bits measured in Mbits (1MBits=1000*1000 bits). The number of measurements is equal to the number of PLMNs multiplied by the number of QoS levels multiplied by the number of S-NSSAIs.
[Total no. of measurement instances] x [no. of filter values for all measurements] (DL and UL) ≤ 100.

e) The measurement name has the form DRB.PdcpSduVolumeDL_Filter.

Where filter is a combination of PLMN ID and QoS level and S-NSSAI.

Where PLMN ID represents the PLMN ID, QoS representes the mapped 5QI or the QCI level, and SNSSAI represents S-NSSAI.

f) NRCellCU.

g) Valid for packet switched traffic.

h) 5GS .

i) One usage of this measurement is for performance assurance within integrity area (user plane connection quality) and in the energy efficency (EE) area.

NRCellCU in non-split NG-RAN deployment scenarios represents NRCell.

5.1.2.1.1.2 DL Cell PDCP SDU Data Volume on X2 Interface

This measurement provides the Data Volume (amount of PDCP SDU bits) in the downlink delivered on X2 interface in DC-scenarios. The measurement is calculated per PLMN ID and per QoS level (mapped 5QI or QCI in NR option 3).
The unit is Mbit.

b) CC.

c) This measurement is obtained by counting the number of bits transferred in the downlink through X2 interface. The measurement is performed at the PDCP SDU level. The measurement is performed per configured PLMN ID and per QoS level (mapped 5QI or QCI in NR option 3).

d) Each measurement is an integer value representing the number of bits measured in Mbits (1MBits=1000*1000 bits). The number of measurements is equal to the number of PLMNs multiplied by the number of QoS levels.
[Total no. of measurement instances] x [no. of filter values for all measurements] (DL and UL) ≤ 100.

e) The measurement name has the form DRB.PdcpSduVolumeX2DL_Filter.

Where filter is a combination of PLMN ID and QoS level.

Where PLMN ID represents the PLMN ID, QoS representes the mapped 5QI or the QCI level.

f) NRCellCU.

g) Valid for packet switched traffic..

h) 5GS.

i) One usage of this measurement is for performance assurance within integrity area (user plane connection quality) and in the energy efficency (EE) area.

NRCellCU in non-split NG-RAN deployment scenarios represents NRCell.

5.1.2.1.1.3 DL Cell PDCP SDU Data Volume on Xn Interface

This measurement provides the Data Volume (amount of PDCP SDU bits) in the downlink delivered on Xn interface . The measurement is calculated per PLMN ID and per QoS level (mapped 5QI) and per S-NSSAI.
The unit is Mbit.

b) CC.

c) This measurement is obtained by counting the number of bits transferred in the downlink through Xn interface. The measurement is performed at the PDCP SDU level. The measurement is performed per configured PLMN ID and per QoS level (mapped 5QI) and per S-NSSAI.

e) The measurement name has the form DRB.PdcpSduVolumeXnDL_Filter.
Where filter is a combination of PLMN ID and QoS level and S-NSSAI.

Where PLMN ID represents the PLMN ID, QoS representes the mapped 5QI or the QCI level, and SNSSAI represents S-NSSAI.

f) NRCellCU.

g) Valid for packet switched traffic.

h) 5GS.

i) One usage of this measurement is for performance assurance within integrity area (user plane connection quality) and in the energy efficency (EE) area.

NRCellCU in non-split NG-RAN deployment scenarios represents NRCell.

5.1.2.1.2 UL PDCP SDU Data Volume Measurements

5.1.2.1.2.1 UL Cell PDCP SDU Data Volume

This measurement provides the Data Volume (amount of PDCP SDU bits) in the uplink delivered from PDCP layer to higher layers. The measurement is calculated per PLMN ID and per QoS level (mapped 5QI) and per S-NSSAI.
The unit is Mbit.

b) CC.

c) This measurement is obtained by counting the number of bits delivered from PDCP layer to higher layers. The measurement is performed at the PDCP SDU level. The measurement is performed per configured PLMN ID and per QoS level (mapped 5QI) and per S-NSSAI.

e) The measurement name has the form DRB.PdcpSduVolumeUL_Filter.
Where filter is a combination of PLMN ID and QoS level and S-NSSAI.

Where PLMN ID represents the PLMN ID, QoS representes the mapped 5QI or the QCI level, and SNSSAI represents S-NSSAI.

f) NRCellCU.

g) Valid for packet switched traffic.

h) 5GS.

i) One usage of this measurement is for performance assurance within integrity area (user plane connection quality) and in the energy efficency (EE) area.

NRCellCU in non-split NG-RAN deployment scenarios represents NRCell.

5.1.2.1.2.2 UL Cell PDCP SDU Data Volume on X2 Interface

This measurement provides the Data Volume (amount of PDCP SDU bits) in the uplink delivered on X2 interface in NSA scenarios. The measurement is calculated per PLMN ID and per QoS level (mapped 5QI or QCI in NR option 3).
The unit is Mbit.

b) CC

c) This measurement is obtained by counting the number of bits transferred in the uplink through X2 interface. The measurement is performed at the PDCP SDU level. The measurement is performed per configured PLMN ID and per QoS level (mapped 5QI or QCI in NR option 3).

d) Each measurement is an integer value representing the number of bits measured in Mbits (1MBits=1000*1000 bits). The number of measurements is equal to the number of PLMNs multiplied by the number of QoS levels.
[Total no. of measurement instances] x [no. of filter values for all measurements] (DL and UL) ≤ 100.

e) The measurement name has the form DRB.PdcpSduVolumeX2UL_Filter.

Where filter is a combination of PLMN ID and QoS level.

Where PLMN ID represents the PLMN ID, QoS representes the mapped 5QI or the QCI level.

f) NRCellCU.

g) Valid for packet switched traffic.

h) 5GS.

i) One usage of this measurement is for performance assurance within integrity area (user plane connection quality) and in the energy efficency (EE) area.

NRCellCU in non-split NG-RAN deployment scenarios represents NRCell.

5.1.2.1.2.3 UL Cell PDCP SDU Data Volume on Xn Interface

a) This measurement provides the Data Volume (amount of PDCP SDU bits) in the uplink delivered on Xn interface in SA scenarios. The measurement is calculated per PLMN ID and per QoS level (mapped 5QI) and per S-NSSAI.
The unit is Mbit.

b) CC.

c) This measurement is obtained by counting the number of bits transferred in the uplink through Xn interface. The measurement is performed at the PDCP SDU level. The measurement is performed per configured PLMN ID and per QoS level (mapped 5QI) and per S-NSSAI.

e) The measurement name has the form DRB.PdcpSduVolumeXnUL_Filter.

Where filter is a combination of PLMN ID and QoS level and S-NSSAI.

Where PLMN ID represents the PLMN ID, QoS representes the mapped 5QI or the QCI level, and SNSSAI represents S-NSSAI.

f) NRCellCU.

g) Valid for packet switched traffic..

h) 5GS.

i) One usage of this measurement is for performance assurance within integrity area (user plane connection quality) and in the energy efficency (EE) area.

NRCellCU in non-split NG-RAN deployment scenarios represents NRCell.

5.1.2.2 Packet Success Rate

5.1.2.2.1 UL PDCP SDU Success Rate

a) This measurement provides the fraction of PDCP SDU packets which are successfully received at gNB. It is a measure of the UL packet delivery success including any packet success in the air interface and in the gNB. Only user-plane traffic (DTCH) and only PDCP SDUs that have entered PDCP (and given a PDCP sequence number) are considered. The measurement is optionally split into subcounters per QoS level (mapped 5QI or QCI in NR option 3), and subcounters per supported S-NSSAI.

b) SI.

c) This measurement is obtained as: Number of successfully received UL PDCP sequence numbers, representing packets that are successfully delivered to higher layers, of a data radio bearer, divided by Total number of UL PDCP sequence numbers of a bearer, starting from the sequence number of the first packet delivered by UE PDCP to gNB until the sequence number of the last packet. Separate counters are optionally maintained for mapped 5QI (or QCI for NR option 3) and per supported S-NSSAI.

d) Each measurement is an integer value representing the success rate. The number of measurements is equal to one. If the optional QoS and S-NSSAI level measurements are performed, the measurements are equal to the number of mapped 5QIs or the number of supported S-NSSAIs.

e) The measurement name has the form DRB.PacketSuccessRateUlgNBUu and optionally DRB.PacketSuccessRateUlgNBUu.QOS where QOS identifies the target quality of service class, and DRB.PacketSuccessRateUlgNBUu.SNSSAI where SNSSAI identifies the S-NSSAI.

f) NRCellCU

g) Valid for packet switched traffic.

h) 5GS.

i) One usage of this measurement is for performance assurance within integrity area (user plane connection quality) and for reliability KPI.

Note : NRCellCU in non-split NG-RAN deployment scenarios represents NRCell.

5.1.2.3 QoS flow release

5.1.2.3.1 Mean interruption time interval for 5QI 1 QoS Flow released due to double NG (double UE context)

a) This measurement provides the average interruption time interval for 5QI 1 QoS Flow released due to double NG (double UE context).

b) CC

c) This measurement is obtained by taking the arithmetic mean of samples where each one is obtained as point in time when NG: UE context Release Command with the cause "Release due to CN-detected mobility" (TS 38.413 [11]) is received (without previous reception of the PDU SESSION RESOURCE RELEASE COMMAND with NAS Normal cause related to the 5QI 1 QoS Flow) from AMF minus point in time when gNB internally evaluates radio link failure for the UE and T-RLF timer has been started for the UE with 5QI 1 QoS Flow established.

d) Each measurement is an integer value (in milliseconds).

e) The measurement name has the form MeanTime5QI1Flow.RelDoubleNG.

f) NRCellCU

g) Valid for packet switched traffic

h) 5GS

– According to TS 38.413 [11] the cause within the NG: UE context Release Command related to double NG shall correspond to “Release due to CN-detected mobility” when in this scenario the context release is requested by the AMF because CN detected the UE is already served either by another NG interface or there are two logical NG-connections for the same UE of the same NG interface.

– The samples with PDU SESSION RESOURCE RELEASE COMMAND with NAS Normal cause related to the 5QI 1 QoS Flow received prior to NG: UE context Release Command with the cause related to the double NG from AMF must be excluded from counting because they point out the second party normally terminated the call, which means the end user has to re-dial the call again.

– One use case of the measurement is to evaluate the interruption time of the QoS of the 5QI 1 Flows due to double NG (double UE context)”. Furthermore, the 5QI 1 QoS Flows that shall be immediately released due to radio reasons with UE connectivity lost (when T-RLF timer was not started) can be delayed by time interval based on this measurement to possibly transform them to double NG scenario to reduce further the 5QI 1 QoS flow Drop Ratio.