6.3 Integrity KPI

28.5543GPP5G end to end Key Performance Indicators (KPI)Management and orchestrationRelease 18TS

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

6.3.1 Latency and delay of 5G networks

6.3.1.0 Void

6.3.1.1 Downlink latency in gNB-DU

a) DLLat_gNB-DU.

b) This KPI describes the gNB-DU part of the packet transmission latency experienced by an end-user. It is used to evaluate the gNB latency contribution to the total packet latency. It is the average (arithmetic mean) of the time from reception of IP packet to gNB-DU until transmission of first part of that packet over the air interface, for a packet arriving when there is no previous data in queue for transmission to the UE. It is a time interval (0.1 mS). The KPI type is MEAN. This KPI can optionally be split into KPIs per QoS level (mapped 5QI or QCI in NR option 3) and per S-NSSAI.

c) DLLat_gNB-DU = DRB.RlcSduLatencyDl

or optionally DLLat_gNB-DU.QoS = DRB.RlcSduLatencyDl.QoS where QOS identifies the target QoS quality of service class.

or optionally DLLat_gNB-DU.SNSSAI = DRB.RlcSduLatencyDl.SNSSAI where SNSSAI identifies the S-NSSAI.

d) NRCellDU

6.3.1.2 Integrated downlink delay in RAN

6.3.1.2.1 Downlink delay in NG-RAN for a sub-network

a) DLDelay_NR_SNw.

b) This KPI describes the average packet transmission delay through the RAN part to the UE. It is used to evaluate delay performance of NG-RAN in downlink for a sub-network. It is the weighted average packets delay from reception of IP packet in gNB-CU-UP until the last part of an RLC SDU packet was received by the UE according to received HARQ feedback information for UM mode or until the last part of an RLC SDU packet was received by the UE according to received RLC ACK for AM mode. It is a time interval (0.1 ms). The KPI type is MEAN. This KPI can optionally be split into KPIs per QoS level (mapped 5QI or QCI in NR option 3) and per S-NSSAI.

c) Below are the equations for average “Integrated downlink delay in RAN” for this KPI on SubNetwork level. The “Integrated downlink delay in RAN” is the sum of average DL delay in gNB-CU-UP of the sub-network (DLDelay_gNBCUUP_SNw) and the average DL delay in gNB-DU of the sub-network (DLDelay_gNBDU_SNw):

DLDelay_NR_SNw = DLDelay_gNBCUUP_SNw + DLDelay_gNBDU_SNw

or optionally DLDelay_ NR_SNw.QOS = DLDelay_gNBCUUP_SNw.QOS + DLDelay_gNBDU_SNw.QOS where QOS identifies the target quality of service class.

or optionally DLDelay_NR_SNw.SNSSAI = DLDelay_gNBCUUP_SNw.SNSSAI + DLDelay_gNBDU_SNw.SNSSAI where SNSSAI identifies the S-NSSAI.

d) SubNetwork

6.3.1.2.2 Downlink delay in NG-RAN for a network slice subnet

a) DLDelay_NR_Nss.

b) This KPI describes the average packet transmission delay through the RAN part to the UE. It is used to evaluate delay performance of NG-RAN in downlink for a network slice subnet. It is the weighted average packets delay from reception of IP packet in gNB-CU-UP until the last part of an RLC SDU packet was received by the UE according to received HARQ feedback information for UM mode or until the last part of an RLC SDU packet was received by the UE according to received RLC ACK for AM mode. It is a time interval (0.1 ms). The KPI type is MEAN.

c) Below is the equation for average "Integrated downlink delay in RAN" for this KPI on NetworkSliceSubnet level. The "Integrated downlink delay in RAN" for network slice subnet is the sum of average DL delay in gNB-CU-UP of the network slice subnet (DLDelay_gNBCUUP_Nss) and the average DL delay in gNB-DU of the network slice subnet (DLDelay_gNBDU_Nss):

DLDelay_NR_Nss.SNSSAI = DLDelay_gNBCUUP_Nss.SNSSAI + DLDelay_gNBDU_Nss.SNSSAI where SNSSAI identifies the S-NSSAI that the network slice subnet supports.

d) NetworkSliceSubnet

6.3.1.3 Downlink delay in gNB-DU

6.3.1.3.1 Downlink delay in gNB-DU for a NRCellDU

a) DLDelay_gNBDU_Cell.

b) This KPI describes the average packet transmission delay through the gNB-DU part to the UE. It is used to evaluate delay performance of gNB-DU in downlink. It is the average packets delay time from arrival of an RLC SDU at the RLC ingress F1-U termination until the last part of an RLC SDU packet was received by the UE according to received HARQ feedback information for UM mode or until the last part of an RLC SDU packet was received by the UE according to received RLC ACK for AM mode. It is a Time interval (0.1 ms). The KPI type is MEAN. This KPI can optionally be split into KPIs per QoS level (mapped 5QI or QCI in NR option 3) and per S-NSSAI.

c) Below is the equation for average DL delay in gNB-DU for a NRCellDU:

DLDelay_gNBDU_Cell = DRB.RlcSduDelayDl + DRB.AirIfDelayDl.

and optionally: DLDelay_gNBDU.QOS = DRB.RlcSduDelayDl.QOS + DRB.AirIfDelayDl.QOS where QOS identifies the target quality of service class.

and optionally: DLDelay_gNB.SNSSAI = DRB.RlcSduDelayDl.SNSSAI + DRB.AirIfDelayDl.SNSSAI where SNSSAI identifies the S-NSSAI

d) NRCellDU

6.3.1.3.2 Downlink delay in gNB-DU for a sub-network

a) DLDelay_gNBDU_SNw.

b) This KPI describes the average packet transmission delay through the gNB-DU part to the UE. It is used to evaluate delay performance of gNB-DU in downlink for a sub-network. It is the weighted average packets delay time from arrival of an RLC SDU at the RLC ingress F1-U termination until the last part of an RLC SDU packet was received by the UE according to received HARQ feedback information for UM mode or until the last part of an RLC SDU packet was received by the UE according to received RLC ACK for AM mode. It is a Time interval (0.1 ms). The KPI type is MEAN. This KPI can optionally be split into KPIs per QoS level (mapped 5QI or QCI in NR option 3) and per S-NSSAI.

c) Below is the equation for average DL delay in gNB-DU for a sub-network, where

– W is the measurement for the weighted average, one of the following:

– the DL data volume of the NR cell;

– the number of UL user data packets of the NR cell;

– any other types of weight defined by the consumer of KPI

– the #NRCellDU is the number of NRCellDU’s in the SubNetwork.

and optionally KPI on SubNetwork level per QoS and per S-NSSAI:

d) SubNetwork

6.3.1.3.3 Downlink delay in gNB-DU for a network slice subnet

a) DLDelay_gNBDU_Nss.

b) This KPI describes the average packet transmission delay through the gNB-DU part to the UE. It is used to evaluate delay performance of gNB-DU in downlink for a network slice subnet. It is the weighted average packets delay time from arrival of an RLC SDU at the RLC ingress F1-U termination until the last part of an RLC SDU packet was received by the UE according to received HARQ feedback information for UM mode or until the last part of an RLC SDU packet was received by the UE according to received RLC ACK for AM mode. It is a Time interval (0.1 ms). The KPI type is MEAN.

c) Below is the equation for average DL delay in gNB-DU for a network slice subnet, where

– W is the measurement for the weighted average, one of the following:

– the DL data volume of the NR cell;

– the number of DL user data packets of the NR cell;

– any other types of weight requested by the consumer of KPI;

– the #NRCellDU is the number of NRCellDU’s associated with the NetworkSliceSubnet.

d) NetworkSliceSubnet

6.3.1.4 Downlink delay in gNB-CU-UP

6.3.1.4.1 Downlink delay in gNB-CU-UP

a) DLDelay_gNBCUUP.

b) This KPI describes the average packet transmission delay through the gNB-CU-UP to the gNB-DU. It is used to evaluate the delay performance of gNB-CU-UP in downlink. It is the average packets delay from reception of IP packet in gNB-CU-UP until the time of arrival, at the gNB-DU, of the RLC SDU at the RLC ingress F1-U termination. It is a Time interval (0.1 ms). The KPI type is MEAN. This KPI can optionally be split into KPIs per QoS level (mapped 5QI or QCI in NR option 3) and per S-NSSAI.

c) Below the equation for average DL delay in a gNB-CU-CP:

DLDelay_gNBCUUP = DRB. PdcpSduDelayDl + DRB.PdcpF1Delay

and optionally: DLDelay_ gNBCUUP.QOS = DRB.PdcpSduDelayDl.QOS + DRB.PdcpF1Delay.QOS where QOS identifies the target quality of service class.

and optionally: DLDelay_gNBCUUP.SNSSAI = DRB.PdcpSduDelayDl.SNSSAI + DRB.PdcpF1Delay.SNSSAI where SNSSAI identifies the S-NSSAI.

d) GNBCUUPFunction

e) In non-split gNB scenario, the value of DRB.PdcpF1Delay (optionally DRB.PdcpF1Delay.QOS, and optionally DRB.PdcpF1Delay.SNSSAI) is set to zero because there are no F1-interfaces in this scenario.

6.3.1.4.2 Downlink delay in gNB-CU-UP for a sub-network

a) DLDelay_gNBCUUP_SNw.

b) This KPI describes the average packet transmission delay through the gNB-CU-UP to the gNB-DU. It is used to evaluate the delay performance of gNB-CU-UP in downlink for a sub-network. It is the weighted average packets delay from reception of IP packet in gNB-CU-UP until the time of arrival, at the gNB-DU, of the RLC SDU at the RLC ingress F1-U termination. It is a Time interval (0.1 ms). The KPI type is MEAN. This KPI can optionally be split into KPIs per QoS level (mapped 5QI or QCI in NR option 3) and per S-NSSAI.

c) Below is the equation for average UL delay in gNB-CU-UP for a sub-network, where

– W is the measurement for the weighted average, one of the following:

– the DL data volume in gNB-CU-UP;

– the number of DL user data packets in gNB-CU-UP;

– any other types of weight requested by the consumer of KPI;

– the # GNBCUUPFunctions is the number of GNBCUUPFunctions’s in the SubNetwork.

and optionally KPI on SubNetwork level per QoS and per S-NSSAI:

d) SubNetwork

e) In non-split gNB scenario, the value of DRB.PdcpF1Delay (optionally DRB.PdcpF1Delay.QOS, and optionally DRB.PdcpF1Delay.SNSSAI) is set to zero because there are no F1-interfaces in this scenario.

6.3.1.4.3 Downlink delay in gNB-CU-UP for a network slice subnet

a) DLDelay_gNBCUUP_Nss.

b) This KPI describes the average packet transmission delay through the gNB-CU-UP to gNB-DU. It is used to evaluate the delay performance of gNB-CU-UP in downlink for a network slice subnet. It is the weighted average packets delay from reception of IP packet in gNB-CU-UP until the time of arrival, at the gNB-DU, of the RLC SDU at the RLC ingress F1-U termination. It is a Time interval (0.1 ms). The KPI type is MEAN.

c) Below is the equation for average UL delay in gNB-CU-UP for a network slice subnet, where

– W is the measurement for the weighted average, one of the following:

– the DL data volume in gNB-CU-UP;

– the number of DL user data packets in gNB-CU-UP;

– any other types of weight requested by the consumer of KPI;

– the # GNBCUUPFunctions is the number of GNBCUUPFunctions’s associated with the NetworkSliceSubnet.

d) NetworkSliceSubnet

e) In non-split gNB scenario, the value of DRB.PdcpF1Delay.SNSSAI is set to zero because there are no F1-interfaces in this scenario.

6.3.1.5 Uplink delay in gNB-DU

6.3.1.5.1 Uplink delay in gNB-DU for a NR cell

a) ULDelay_gNBDU_Cell.

b) This KPI describes the average packet transmission delay through the gNB-DU part from the UE in a NR cell. It is used to evaluate delay performance of gNB-DU in uplink. It is the average packet delay from when an UL RLC SDU was scheduled, as per the scheduling grant provided, until time when the RLC SDU is sent to PDCP or CU for split gNB. It is a time interval (0.1 ms). The KPI type is MEAN. This KPI can optionally be split into KPIs per QoS level (mapped 5QI or QCI in NR option 3) and per S-NSSAI.

c) Below is the equation for average UL delay in gNB-DU for a NRCellDU:

ULDelay_gNBDU_Cell = DRB.RlcDelayUI + DRB.AirIfDelayUI

and optionally: where QOS identifies the target quality of service class.

and optionally: where SNSSAI identifies the S-NSSAI.

d) NRCellDU

6.3.1.5.2 Uplink delay in gNB-DU for a sub-network

a) ULDelay_gNBDU_SNw.

b) This KPI describes the average packet transmission delay through the gNB-DU part from the UE for a sub-network. It is used to evaluate delay performance of gNB-DU in uplink for a sub-network. It is the weighted average packet delay from when an UL RLC SDU was scheduled, as per the scheduling grant provided, until time when the RLC SDU is sent to PDCP or CU for split gNB. It is a time interval (0.1 ms). The KPI type is MEAN. This KPI can optionally be split into KPIs per QoS level (mapped 5QI or QCI in NR option 3) and per S-NSSAI.

c) Below is the equation for average UL delay in gNB-DU for a sub-network, where

– W is the measurement for the weighted average, one of the following:

– the UL data volume of the NR cell;

– the number of UL user data packets of the NR cell;

– any other types of weight defined by the consumer of KPI

– the #NRCellDU is the number of NRCellDU’s in the SubNetwork.

and optionally KPI on SubNetwork level per QoS and per S-NSSAI:

d) SubNetwork

6.3.1.5.3 Uplink delay in gNB-DU for a network slice subnet

a) ULDelay_gNBDU_Nss.

b) This KPI describes the average packet transmission delay through the gNB-DU part from the UE for a network slice subnet. It is used to evaluate delay performance of gNB-DU in uplink for a network slice subnet. It is the weighted average packet delay from when an UL RLC SDU was scheduled, as per the scheduling grant provided, until time when the RLC SDU is sent to PDCP or CU for split gNB. It is a time interval (0.1 ms). The KPI type is MEAN.

c) Below is the equation for average UL delay in gNB-DU for a network slice subnet, where

– W is the measurement for the weighted average, one of the following:

– the UL data volume of the NR cell;

– the number of UL user data packets of the NR cell;

– any other types of weight requested by the consumer of KPI;

– the #NRCellDU is the number of NRCellDU’s associated with the NetworkSliceSubnet.

d) NetworkSliceSubnet

6.3.1.6 Uplink delay in gNB-CU-UP

6.3.1.6.1 Uplink delay in gNB-CU-UP

a) ULDelay_gNBCUUP.

b) This KPI describes the average packet transmission delay through the gNB-CU-UP from gNB-DU. It is used to evaluate delay performance of gNB-CU-UP in uplink. It is the average packet delay from when the RLC SDU is sent to PDCP or CU for split gNB, until time when the corresponding PDCP SDU was sent to the core network from gNB-CU-UP. It is a time interval (0.1 ms). The KPI type is MEAN. This KPI can optionally be split into KPIs per QoS level (mapped 5QI or QCI in NR option 3) and per S-NSSAI.

c) Below the equation for average UL delay in a gNB-CU-CP:

and optionally: where QOS identifies the target quality of service class.

and optionally: where SNSSAI identifies the S-NSSAI.

d) GNBCUUPFunction

e) It is assumed that the F1 uplink delay is the same as the F1 downlink delay. In non-split gNB scenario, the value of DRB.PdcpF1Delay (optionally DRB.PdcpF1Delay.QOS, and optionally DRB.PdcpF1Delay.SNSSAI) is set to zero because there are no F1-interfaces in this scenario.

6.3.1.6.2 Uplink delay in gNB-CU-UP for a sub-network

a) ULDelay_gNBCUUP_SNw.

b) This KPI describes the average packet transmission delay through the gNB-CU-UP part from the gNB-DU for a sub-network. It is used to evaluate delay performance of gNB-CU-UP in uplink for a sub-network. It is the weighted average packet delay from when the RLC SDU is sent to PDCP or CU for split gNB, until time when the corresponding PDCP SDU was sent to the core network from gNB-CU-UP. It is a time interval (0.1 ms). The KPI type is MEAN. This KPI can optionally be split into KPIs per QoS level (mapped 5QI or QCI in NR option 3) and per S-NSSAI.

c) Below is the equation for average UL delay in gNB-CU-UP for a sub-network, where

– W is the measurement for the weighted average, one of the following:

– the UL data volume in gNB-CU-UP ;

– the number of UL user data packets in gNB-CU-UP ;

– any other types of weight requested by the consumer of KPI;

– the # GNBCUUPFunctions is the number of GNBCUUPFunctions’s in the SubNetwork.

and optionally KPI on SubNetwork level per QoS and per S-NSSAI:

d) SubNetwork

6.3.1.6.3 Uplink delay in gNB-CU-UP for a network slice subnet

a) ULDelay_gNBCUUP_Nss.

b) This KPI describes the average packet transmission delay through the gNB-CU-UP part from the gNB-DU for a network slice subnet. It is used to evaluate delay performance of gNB-CU-UP in uplink for a network slice subnet. It is the weighted average packet delay from when the RLC SDU is sent to PDCP or CU for split gNB, until time when the corresponding PDCP SDU was sent to the core network from gNB-CU-UP. It is a time interval (0.1 ms). The KPI type is MEAN. This KPI can optionally be split into KPIs per QoS level (mapped 5QI or QCI in NR option 3) and per S-NSSAI.

c) Below is the equation for average UL delay in gNB-CU-UP for a network slice subnet, where

– W is the measurement for the weighted average, one of the following:

– the UL data volume in gNB-CU-UP;

– the number of UL user data packets in gNB-CU-UP;

– any other types of weight requested by the consumer of KPI;

– the # GNBCUUPFunctions is the number of GNBCUUPFunctions’s associated with the NetworkSliceSubnet.

d) NetworkSliceSubnet

e) It is assumed that the F1 uplink delay is the same as the F1 downlink delay. In non-split gNB scenario, the value of DRB.PdcpF1Delay.SNSSAI is set to zero because there are no F1-interfaces in this scenario.

6.3.1.7 Integrated uplink delay in RAN

6.3.1.7.1 Uplink delay in NG-RAN for a sub-network

a) ULDelay_NR_SNw.

b) This KPI describes the average packet transmission delay through the RAN part from the UE for a sub-network. It is used to evaluate delay performance of NG-RAN in uplink. It is the weighted average packet delay from when an UL RLC SDU was scheduled, as per the scheduling grant provided, until time when the corresponding PDCP SDU was sent to the core network from gNB-CU-UP. It is a time interval (0.1 ms). The KPI type is MEAN. This KPI can optionally be split into KPIs per QoS level (mapped 5QI or QCI in NR option 3) and per S-NSSAI.

c) Below are the equations for average "Integrated uplink delay in RAN" for this KPI on SubNetwork level. The "Integrated uplink delay in RAN" is the sum of average UL delay in gNB-CU-UP of the sub-network (ULDelay_gNBCUUP_SNw) and the average UL delay in gNB-DU of the sub-network (ULDelay_gNBDU_SNw):

ULDelay_NR_SNw = ULDelay_gNBCUUP_SNw + ULDelay_gNBDU_SNw

or optionally ULDelay_ NR_SNw.QOS = ULDelay_gNBCUUP_SNw.QOS + ULDelay_gNBDU_SNw.QOS where QOS identifies the target quality of service class.

or optionally ULDelay_NR_SNw.SNSSAI = ULDelay_gNBCUUP_SNw.SNSSAI + ULDelay_gNBDU_SNw.SNSSAI where SNSSAI identifies the S-NSSAI.

d) SubNetwork

6.3.1.7.2 Uplink delay in NG-RAN for a network slice subnet

a) ULDelay_NR_Nss.

b) This KPI describes the average packet transmission delay through the RAN part from the UE for a network slice subnet. It is used to evaluate delay performance of NG-RAN in uplink. It is the weighted average packet delay from when an UL RLC SDU was scheduled, as per the scheduling grant provided, until time when the corresponding PDCP SDU was sent to the core network from gNB-CU-UP. It is a time interval (0.1 ms). The KPI type is MEAN. This KPI can optionally be split into KPIs per QoS level (mapped 5QI or QCI in NR option 3) and per S-NSSAI.

c) Below is the equation for average “Integrated uplink delay in RAN” for this KPI on NetworkSliceSubNet level. The “Integrated uplink delay in RAN” for network slice subnet is the sum of average UL delay in gNB-CU-UP of the network slice subnet (ULDelay_gNBCUUP_Nss) and the average UL delay in gNB-DU of the network slice subnet (ULDelay_gNBDU_Nss):

ULDelay_NR_Nss.SNSSAI = ULDelay_gNBCUUP_Nss.SNSSAI + ULDelay_gNBDU_Nss.SNSSAI where SNSSAI identifies the S-NSSAI that the network slice subnet supports.

d) NetworkSliceSubnet

6.3.1.8 E2E delay for network slice

6.3.1.8.1 Average e2e uplink delay for a network slice

a) DelayE2EUlNs.

b) This KPI describes the average e2e UL packet delay between the PSA UPF and the UE for a network slice. It is the weighted average packet delay from the time when an UL RLC SDU was scheduled at the UE until the time when the corresponding GTP PDU was received by the PSA UPF. The KPI type is MEAN in unit of 0.1 ms.

c) This KPI is the weighted average of UL packet delay between PSA UPF and UE, for all N3 interfaces (modelled by EP_N3 MOIs) and N9 interfaces (modelled by EP_N9 MOIs) of all PSA UPFs supporting the network slice (modelled by NetworkSlice MOI) identified by the S-NSSAI.

This KPI is calculated in the equation below, where Wn3 and Wn9 are the measurements for the weighted average, Wn3 is one of the following:

– the data volume of UL GTP PDUs received by PSA UPF on the N3 interface;

– the number of UL GTP PDUs received by PSA UPF on the N3 interface;

– any other types of weight defined by the consumer of KPI.

And Wn9 is one of the following:

– the data volume of UL GTP PDUs received by PSA UPF on the N9 interface;

– the number of UL GTP PDUs received by PSA UPF on the N9 interface;

– any other types of weight defined by the consumer of KPI.

DelayE2EUlNs =

Where the SNSSAI identifies the S-NSSAI.

d) NetworkSlice.

6.3.1.8.2 Average e2e downlink delay for a network slice

a) DelayE2EDlNs.

b) This KPI describes the average e2e DL packet delay between the PSA UPF and the UE for a network slice. It is the weighted average packet delay from the time when an GTP PDU has been sent by the PSA UPF until time when the corresponding RLC SDU was received by the UE. The KPI type is MEAN in unit of 0.1 ms.

c) This KPI is the weighted average of DL packet delay between PSA UPF and UE, for all N3 interfaces (modelled by EP_N3 MOIs) and N9 interfaces (modelled by EP_N9 MOIs) of all PSA UPFs supporting the network slice (modelled by NetworkSlice MOI) identified by the S-NSSAI.

This KPI is calculated in the equation below, where Wn3 and Wn9 are the measurements for the weighted average, Wn3 is one of the following:

– the data volume of DL GTP PDUs transmitted by PSA UPF on the N3 interface;

– the number of DL GTP PDUs transmitted by PSA UPF on the N3 interface;

– any other types of weight defined by the consumer of KPI.

And Wn9 is one of the following:

– the data volume of DL GTP PDUs transmitted by PSA UPF on the N9 interface;

– the number of DL GTP PDUs transmitted by PSA UPF on the N9 interface;

– any other types of weight defined by the consumer of KPI.

DelayE2EDlNs =

Where the SNSSAI identifies the S-NSSAI.

d) NetworkSlice.

6.3.2 Upstream throughput for network and Network Slice Instance

a) UTSNSI.

b) This KPI describes the upstream throughput of one single network slice by computing the packet size for each successfully received UL IP packet through the network slice during each observing granularity period and is used to evaluate integrity performance of the end-to-end network slice . It is obtained by upstream throughput provided by N3 interface from NG-RAN to all UPFs which are related to the single network slice . The KPI unit is kbit/s and the KPI type is CUM.

d) NetworkSlice, SubNetwork.

6.3.3 Downstream throughput for Single Network Slice Instance

a) DTSNSI.

b) This KPI describes the downstream throughput of one single network slice instance by computing the packet size for each successfully transmitted DL IP packet through the network slice instance during each observing granularity period and is used to evaluate integrity performance of the end-to-end network slice instance. It is obtained by downstream throughput provided by N3 interface from all UPFs to NG-RAN which are related to the single network slice . The KPI unit is kbit/s and the KPI type is CUM.

d) NetworkSlice.

6.3.4 Upstream Throughput at N3 interface

a) N3UpstreamThr.

b) This KPI describes the total number of octets of all incoming GTP data packets on the N3 interface (measured at UPF) which have been generated by the GTP-U protocol entity on the N3 interface, during a granularity period. This KPI is used to evaluate upstream GTP throughput integrity performance at the N3 interface. It is obtained by measuring the GTP data upstream throughput provided by N3 interface from NG-RAN to UPF, during the granularity period. The KPI unit is kbit/s and the KPI type is MEAN.

c) UGTPTS=SUM (GTP.InDataOctN3UPF)/timeperiod) at UPF

d) NetworkSlice

6.3.5 Downstream Throughput at N3 interface

a) N3DownstreamThr.

b) This KPI describes the total number of octets of all downstream GTP data packets on the N3 interface (transmitted downstream from UPF) which have been generated by the GTP-U protocol entity on the N3 interface, during a granularity period. This KPI is used to evaluate integrity performance at N3 interface. It is obtained by measuring the GTP data downstream throughput provided by N3 interface from UPF to NG-RAN, during the granularity period. The KPI unit is kbit/s and the KPI type is MEAN.

c) DGTPTS=SUM (GTP.OutDataOctN3UPF)/timeperiod) at UPF

d) NetworkSlice

6.3.6 RAN UE Throughput

6.3.6.1 Void

6.3.6.2 RAN UE Throughput definition

To achieve a Throughput measurement (below examples are given for DL) that is independent of file size and gives a relevant result it is important to remove the volume and time when the resource on the radio interface is not fully utilized. (Successful transmission, buffer empty in figure 1).

Time (slots)

Data arrives to

empty DL buffer

First data is

transmitted to the UE

The send buffer is

again empty

calulations since it

can be impacted

by packet size of

User Plane (UP) packets.

ThpTimeDl

Failed transmission (

”

Block

error

”

)

Successful transmission,

buffer not empty

Successful transmission,

buffer empty

ThpVolDl =

∑

Total DL transferred volume =

∑

(kbits)

UE Throughput in DL =

ThpVolDl / ThpTimeDl (kbits/s)

No transmission, buffer not

empty (e.g. due to contention)

The last slot shall always be removed from

Figure 1

To achieve a throughput measurement that is independent of bursty traffic pattern, it is important to make sure that idle gaps between incoming data is not included in the measurements. That shall be done as considering each burst of data as one sample.

6.3.6.3 DL RAN UE throughput

6.3.6.3.1 DL RAN UE throughput for a NRCellDU

a) DlUeThroughput _Cell.

b) This KPI describes the average DL RAN UE throughput for a NRCellDU. The KPI type is MEAN in kbit per second. This KPI can optionally be split into KPIs per QoS level (mapped 5QI or QCI in NR option 3) and per S-NSSAI.

c) Below is the equation for average DL RAN UE throughput for a NRCellDU:

DlUeThroughput _Cell = DRB.UEThpDl;

and optionally: DlUeThroughput _Cell.QOS = DRB.UEThpDl.QOS, where QOS identifies the target quality of service class;

and optionally: DlUeThroughput _Cell.SNSSAI = DRB.UEThpDl.SNSSAI, where SNSSAI identifies the S-NSSAI.

d) NRCellDU

6.3.6.3.2 DL RAN UE throughput for a sub-network

a) DlUeThroughput _SNw.

b) This KPI describes the average DL RAN UE throughput for a sub-network. The KPI type is MEAN in kbit per second. This KPI can optionally be split into KPIs per QoS level (mapped 5QI or QCI in NR option 3) and per S-NSSAI.

c) Below is the equation for average DL RAN UE throughput for a sub-network, where

– W is the measurement for the weighted average, it is one of the following:

– the DL data volume of the NR cell;

– a weight defined by the consumer of KPI

– the #NRCellDU is the number of NRCellDU’s in the SubNetwork.

and optionally KPI on SubNetwork level per QoS and per S-NSSAI:

d) SubNetwork

6.3.6.3.3 DL RAN UE throughput for a network slice subnet

a) DlUeThroughput _Nss.

b) This KPI describes the average DL RAN UE throughput for a network slice subnet. The KPI type is MEAN in kbit per second.

c) Below is the equation for average DL RAN UE throughput for a network slice subnet, where

– W is the measurement for the weighted average, it is one of the following:

– the DL data volume of the NR cell;

– a weight defined by the consumer of KPI

– the #NRCellDU is the number of NRCellDU’s associated with the NetworkSliceSubnet.

, where the SNSSAI identifies the S-NSSAI that the NetworkSliceSubnet supports.

d) NetworkSliceSubnet

6.3.6.4 UL RAN UE throughput

6.3.6.4.1 UL RAN UE throughput for a NRCellDU

a) UlUeThroughput_Cell.

b) This KPI describes the average UL RAN UE throughput for a NRCellDU. The KPI type is MEAN in kbit per second. This KPI can optionally be split into KPIs per QoS level (mapped 5QI or QCI in NR option 3) and per S-NSSAI.

c) Below is the equation for average UL RAN UE throughput for a NRCellDU:

UlUeThroughput _Cell = DRB.UEThpUl;

and optionally: UlUeThroughput_Cell.QOS = DRB.UEThpUl.QOS, where QOS identifies the target quality of service class;

and optionally: UlUeThroughput_Cell.SNSSAI = DRB.UEThpUl.SNSSAI, where SNSSAI identifies the S-NSSAI.

d) NRCellDU

6.3.6.4.2 UL RAN UE throughput for a sub-network

a) UlUeThroughput_SNw.

b) This KPI describes the average UL RAN UE throughput for a sub-network. The KPI type is MEAN in kbit per second. This KPI can optionally be split into KPIs per QoS level (mapped 5QI or QCI in NR option 3) and per S-NSSAI.

c) Below is the equation for average UL RAN UE throughput for a sub-network, where

– W is the measurement for the weighted average, it is one of the following:

– the UL data volume of the NR cell;

– a weight defined by the consumer of KPI

– the #NRCellDU is the number of NRCellDU’s in the SubNetwork.

and optionally KPI on SubNetwork level per QoS and per S-NSSAI:

d) SubNetwork

6.3.6.4.3 UL RAN UE throughput for a network slice subnet

a) UlUeThroughput _Nss.

b) This KPI describes the average UL RAN UE throughput for a network slice subnet. The KPI type is MEAN in kbit per second.

c) Below is the equation for average UL RAN UE throughput for a network slice subnet, where

– W is the measurement for the weighted average, it is one of the following:

– the UL data volume of the NR cell;

– a weight defined by the consumer of KPI

– the #NRCellDU is the number of NRCellDU’s associated with the NetworkSliceSubnet.

, where the SNSSAI identifies the S-NSSAI that the NetworkSliceSubnet supports.

d) NetworkSliceSubnet