5.4 Performance measurements for UPF

28.5523GPP5G performance measurementsManagement and orchestrationRelease 18TS

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

5.4.1 N3 interface related measurements

5.4.1.1 Number of incoming GTP data packets on the N3 interface, from (R)AN to UPF

a) This measurement provides the number of GTP data PDUs on the N3 interface which have been accepted and processed by the GTP-U protocol entity in UPF on the N3 interface. .The measurement can optionally be split into subcounters per S-NSSAI.

b) CC

c) Reception by the UPF of a GTP-U data PDU on the N3 interface from the (R)AN. See TS 23.501 [4].

d) Each measurement is a single integer value, the number of measurements is equal to one. If the optional S-NSSAI subcounter measurements are perfomed, the number of measurements is equal to the number of supported S-NSSAIs.

e) GTP.InDataPktN3UPF and optionally GTP.InDataPktN3UPF.SNSSAI, where SNSSAI identifies the S-NSSAI.

f) EP_N3 (contained by UPFFunction).

g) Valid for packet switching.

h) 5GS.

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

5.4.1.2 Number of outgoing GTP data packets of on the N3 interface, from UPF to (R)AN

a) This measurement provides the number of GTP data PDUs on the N3 interface which have been generated by the GTP-U protocol entity on the N3 interface. The measurement can optionally be split into subcounters per S-NSSAI.

b) CC

c) Transmission by the UPF of a GTP-U data PDU of on the N3 interface to the (R)AN. See TS 23.501 [4].

e) GTP.OutDataPktN3UPF and optionally GTP.OutDataPktN3UPF.SNSSAI, where SNSSAI identifies the S-NSSAI.

f) EP_N3 (contained by UPFFunction).

g) Valid for packet switching.

h) 5GS

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

5.4.1.3 Number of octets of incoming GTP data packets on the N3 interface, from (R)AN to UPF

a) This measurement provides the number of octets of incoming GTP data packets on the N3 interface which have been generated by the GTP-U protocol entity on the N3 interface. The measurement can optionally be split into subcounters per S-NSSAI.

b) CC

c) Reception by the UPF of a GTP-U data PDU on the N3 interface from (R)AN. See TS 23.501 [4].

e) GTP.InDataOctN3UPF and optionally GTP.OutDataOctN3UPF.SNSSAI, where SNSSAI identifies the S-NSSAI.

f) EP_N3

g) Valid for packet switching

h) 5GS

5.4.1.4 Number of octets of outgoing GTP data packets on the N3 interface, from UPF to (R)AN

a) This measurement provides the number of octets of outgoing GTP data packets on the N3 interface which have been generated by the GTP-U protocol entity on the N3 interface. The measurement can optionally be split into subcounters per S-NSSAI.

b) CC

c) Transmission by the UPF of a GTP-U data PDU on the N3 interface to the(R)AN, .See TS 23.501 [4].

e) GTP.OutDataOctN3UPF and optionally GTP.OutDataOctN3UPF.SNSSAI, where SNSSAI identifies the S-NSSAI.

f) EP_N3

g) Valid for packet switching

h) 5GS

5.4.1.5 Data volume of incoming GTP data packets per QoS level on the N3 interface, from (R)AN to UPF

a) This measurement provides the data volume of the incoming GTP data packets per QoS level which have been accepted and processed by the GTP-U protocol entity on the N3 interface. The measurement is calculated and split into subcounters per QoS level (5QI).

b) CC.

c) This measurement is obtained by counting the number of GTP PDU bits sent from GNB to UPF on the N3 interface. The measurement is performed per configured QoS level (5QI).

d) Each measurement is an integer value representing the number of bits measured in kbit . The number of measurements is equal to the number of QoS levels.

e) GTP.InDataVolumeQoSLevelN3UPF.

f) EP_N3.

g) Valid for packet switching.

h) 5GS.

5.4.1.6 Data volume of outgoing GTP data packets per QoS level on the N3 interface, from UPF to (R)AN

a) This measurement provides the data volume of the outgoing GTP data packets per QoS level which have been generated by the GTP-U protocol entity on the N3 interface. The measurement is calculated and split into subcounters per QoS level (5QI).

b) CC.

c) This measurement is obtained by counting the number of GTP PDU bits sent from UPF to GNB on the N3 interface. The measurement is performed per configured QoS level (5QI).

d) Each measurement is an integer value representing the number of bits measured in kbitk . The number of measurements is equal to the number of QoS levels.

e) GTP.OutDataVolumeQoSLevelN3UPF

f) EP_N3.

g) Valid for packet switching.

h) 5GS.

5.4.1.7 Incoming GTP Data Packet Loss in UPF over N3

a) This measurement provides the number of GTP data packets which are not successfully received at UPF. It is a measure of the incoming GTP data packet loss per N3 on an UPF interface. The measurement is split into subcounters per QoS level (5QI) or subconters per GTP tunnel (TEID) or subcounters per QoS level per GTP tunnel (TEID) or subcounters per S-NSSAI.

b) CC.

c) This measurement is obtained by a counter: Number of missing incoming GTP sequence numbers (TS 29.281 [42]) among all GTP packets delivered by a gNB to an UPF per N3 interface.The separate subcounter can be maintained for each 5QI or for each GTP tunnel identified by TEID or for each supported S-NSSAI.

d) Each measurement is an integer value representing the number of the lost GTP pakets. If the QoS level measurement is perfomed, the measurements are equal to the number of 5QIs. If the optional S-NSSAI subcounter measurements are performed, the number of measurements is equal to the number of supported S-NSSAIs.

e) The measurement name has the form GTP.InDataPktPacketLossN3UPF or GTP.InDataPktPacketLossN3UPF.QoS or GTP.InDataPktPacketLossN3UPF.TEID or GTP.InDataPktPacketLossN3UPF.TEID.QoS where QoS identifies the target quality of service class or GTP.InDataPktPacketLossN3UPF.SNSSAI, where SNSSAI identifies the S-NSSAI.

f) EP_N3 (contained by UPFFunction).

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.

5.4.1.8 Outgoing GTP Data Packet Loss

a) This measurement provides the number of GTP data packets which are not successfully received at gNB over N3. It is a measure of the outgoing GTP data packet loss per N3 on an UPF interface. The measurement is split into subcounters per QoS level (5QI).

b) CC.

c) This measurement is obtained by a counter: Number of missing outgoing GTP sequence numbers (TS 29.281) among all GTP packets delivered by an UPF interface to a gNB. Separate counter is maintained for each 5QI.

d) Each measurement is an integer value representing the lost GTP packets.. If the QoS level measurement is perfomed, the measurements are equal to the number of 5QIs.

e) The measurement name has the form GTP.OutDataPktPacketLossN3UPF or GTP.OutDataPktPacketLossN3UPF.QoS where QoS identifies the target quality of service class.

f) EP_N3.

g) Valid for packet switched traffic.

h) 5GS.

5.4.1.9 Round-trip GTP Data Packet Delay

5.4.1.9.1 Average round-trip N3 delay on PSA UPF

a) This measurement provides the average round-trip delay on a N3 interface on PSA UPF. This measurement is split into subcounters per DSCP (Differentiated Services Code Point).

b) DER (n=1).

c) This measurement is obtained as: the sum (the time when receiving a GTP echo reply message from the gNB-CU-UP at PSA UPF’s ingress GTP termination, minus time when sending the associated echo request message to gNB-CU-UP at the PSA UPF’s GTP egress termination) divided by total number of GTP echo reply message received at PSA UPF’s ingress GTP termination. This measurement is calculated for each DSCP.

d) Each measurement is a real representing the average delay in microseconds.

e) The measurement name has the form GTP.RttDelayN3DlPsaUpfMean.DSCP
Where DSCP identifies the DSCP.

f) EP_N3 (contained by UPFFunction).

g) Valid for packet switched traffic.

h) 5GS.

5.4.1.9.2 Distribution of round-trip N3 delay on PSA UPF

a) This measurement provides the distribution of delay on a N3 interface on PSA UPF. This measurement is split into subcounters per DSCP (Differentiated Services Code Point).

b) DER (n=1).

c) This measurement is obtained by 1) calculating the RTT N3 delay by: the time when receiving a GTP echo reply message from the gNB-CU-UP at PSA UPF’s ingress GTP termination, minus time when sending the associated echo request message to gNB-CU-UP at the PSA UPF’s GTP egress termination; and 2) incrementing the corresponding bin with the delay range where the result of 1) falls into by 1 for the subcounters per DSCP.

d) Each measurement is an integer representing the number of GTP echo messages measured with the delay within the range of the bin.

e) The measurement name has the form GTP.RttDelayN3PsaUpfDist.Bin.DSCP
Where Bin indicates a delay range which is vendor specific, and DSCP identifies the DSCP.

f) EP_N3 (contained by UPFFunction).

g) Valid for packet switched traffic.

h) 5GS.

5.4.1.9.3 Average round-trip N3 delay on I-UPF

a) This measurement provides the average round-trip delay on a N3 interface on I-UPF. This measurement is split into subcounters per DSCP (Differentiated Services Code Point).

b) DER (n=1).

c) This measurement is obtained as: the sum (the time when receiving a GTP echo reply message from the gNB-DU at I-UPF’s ingress GTP termination, minus time when sending the associated echo request message to gNB-DU at the I-UPF’s GTP egress termination) divided by total number of GTP echo reply message received at I-UPF’s ingress GTP termination. This measurement is calculated for each DSCP.

d) Each measurement is a real representing the average delay in microseconds.

e) The measurement name has the form GTP.RttDelayN3IUpfMean.DSCP
Where DSCP identifies the DSCP.

f) EP_N3 (contained by UPFFunction).

g) Valid for packet switched traffic.

h) 5GS.

5.4.1.9.4 Distribution of round-trip N3 delay on I-UPF

a) This measurement provides the distribution of delay on a N3 interface on I-UPF. This measurement is split into subcounters per DSCP (Differentiated Services Code Point).

b) DER (n=1).

c) This measurement is obtained by 1) calculating the RTT N3 delay by: the time when receiving a GTP echo reply message from the gNB-DU at I-UPF’s ingress GTP termination, minus time when sending the associated echo request message to gNB-DU at the I-UPF’s GTP egress termination; and 2) incrementing the corresponding bin with the delay range where the result of 1) falls into by 1 for the subcounters per DSCP.

d) Each measurement is an integer representing the number of GTP echo messages measured with the delay within the range of the bin.

e) The measurement name has the form GTP.RttDelayN3IUpfsDist.Bin.DSCP
Where Bin indicates a delay range which is vendor specific, and DSCP identifies the DSCP.

f) EP_N3 (contained by UPFFunction).

g) Valid for packet switched traffic.

h) 5GS.

5.4.1.10 Number of incoming GTP data packets out-of-order on the N3 interface, from (R)AN to UPF

a) This measurement provides the number of incoming GTP data packets out-of-order on the N3 interface. The measurement is calculated and split into sub-counters per QoS level (5QI).

b) CC

c) This measurement is obtained by counting the number of GTP data packets with sequence numbers less than the maximum GTP sequence number received by UPF. Separate counter is maintained for each 5QI.

d) Each measurement is an integer value representing the number of GTP packets out-of-order. If the QoS level measurement is performed, the measurements are equal to the number of 5QIs.

e) The measurement name has the form GTP.InDataPktDisorderN3UPF or GTP.InDataPktDisorderN3UPF.QoS where QoS identifies the target quality of service class.

f) EP_N3

g) Valid for packet switching

h) 5GS

5.4.2 N6 related measurements

5.4.2.1 N6 incoming link usage

a) This measurement provides the PDU-layer incoming link usage of N6 interface.

b) CC

c) See clause 2.3.4 for IP packet. Definition: IP-type-P (broad spectrum of packet types) Link Usage in IETF RFC 5136 [5].

NOTE: How to measure the unstructured data type is not specified in the present document.

d) Each measurement is an integer value.

e) IP.N6IncLinkUsage.N6RP
where N6RP identifies the N6 reference point of this UPF, the format of N6RP is vendor specific.

f) EP_N6

g) Valid for packet switched traffic.

h) 5GS

5.4.2.2 N6 outgoing link usage

a) This measurement provides the PDU-layer outcoming link usage of N6 interface.

b) CC

c) See clause 2.3.4 for IP packet. Definition: IP-type-P (broad spectrum of packet types) Link Usage in IETF RFC 5136 [5].

NOTE: How to measure the unstructured data type is not specified in the present document.

d) Each measurement is an integer value.

e) IP.N6OutLinkUsage.N6RP
where N6RP identifies the N6 reference point of this UPF, the format of N6RP is vendor specific.

f) EP_N6

g) Valid for packet switched traffic.

h) 5GS

5.4.3 N4 interface related measurements

5.4.3.1 Session establishments

5.4.3.1.1 Number of requested N4 session establishments

a) This measurement provides the number of N4 session establishment requests received by the UPF.

b) CC.

c) On receipt of N4 session establishment request message (see TS 23.502 [7]) by the UPF from SMF.

d) A single integer value.

e) SM.N4SessionEstabReq.

f) UPFFunction.

g) Valid for packet switched traffic.

h) 5GS.

5.4.3.1.2 Number of failed N4 session establishments

a) This measurement provides the number of failed N4 session establishments at the UPF. This measurement is split into subcounters per rejection cause.

b) CC.

c) On transmission of N4 session establishment response message that contains the cause indicating the rejection of N4 session establishment request (see TS 23.502 [7]) by the UPF to SMF. Each N4 session establishment response message indicating the rejection of N4 session establishment request triggers the relevant subcounter per rejection cause to increment by 1.

d) A single integer value.

e) SM.N4SessionEstabFail.cause
where the cause identities the cause of the rejection of N4 session establishment request, per the encoding of the cause defined in clause 8.2.1 of TS 29.224 [16].

f) UPFFunction.

g) Valid for packet switched traffic.

h) 5GS.

5.4.3.2 N4 Session reports

5.4.3.2.1 Number of requested N4 session reports

a) This measurement provides the number of N4 session reports sent by the UPF.

b) CC.

c) When UPF sends N4 session report message (see TS 23.502 [7]) to SMF.

d) A single integer value.

e) SM.N4SessionReport.

f) UPFFunction.

g) Valid for packet switched traffic.

h) 5GS.

5.4.3.2.2 Number of successful N4 session reports

a) This measurement provides the number of successful N4 session report at the UPF.

b) CC.

c) On receipt of N4 session report ACK message (see TS 23.502 [7] by the UPF. Each N4 session report ACK message indicating the successful N4 session report request triggers the counter to increment by 1.

d) A single integer value.

e) SM.N4SessionReportSucc

f) UPFFunction.

g) Valid for packet switched traffic.

h) 5GS.

5.4.4 N9 interface related measurements

5.4.4.1 Round-trip GTP Data Packet Delay on N9 interface

5.4.4.1.1 Average round-trip N9 delay on PSA UPF

a) This measurement provides the average round-trip delay on a N9 interface on PSA UPF. This measurement is split into subcounters per DSCP (Differentiated Services Code Point).

b) DER (n=1).

c) This measurement is obtained as: the sum (the time when receiving a GTP echo reply message from the I-UPF at PSA UPF’s ingress GTP termination, minus time when sending the associated echo request message to I-UPF at the PSA UPF’s GTP egress termination) divided by total number of GTP echo reply message received at PSA UPF’s ingress GTP termination. This measurement is calculated for each DSCP.

d) Each measurement is a real representing the average delay in microseconds.

e) The measurement name has the form GTP.RttDelayN9PsaUpfMean.DSCP
Where DSCP identifies the DSCP.

f) EP_N9.

g) Valid for packet switched traffic.

h) 5GS.

5.4.4.1.2 Distribution of round-trip N9 delay on PSA UPF

a) This measurement provides the distribution of delay on a N9 interface on PSA UPF. This measurement is split into subcounters per DSCP (Differentiated Services Code Point).

b) DER (n=1).

c) This measurement is obtained by 1) calculating the RTT N9 delay by: the time when receiving a GTP echo reply message from the I-UPF at PSA UPF’s ingress GTP termination, minus time when sending the associated echo request message to I-UPF at the PSA UPF’s GTP egress termination; and 2) incrementing the corresponding bin with the delay range where the result of 1) falls into by 1 for the subcounters per DSCP.

d) Each measurement is an integer representing the number of GTP echo messages measured with the delay within the range of the bin.

e) The measurement name has the form GTP.RttDelayN9PsaUpfDist.Bin.DSCP
Where Bin indicates a delay range which is vendor specific, and DSCP identifies the DSCP.

f) EP_N9.

g) Valid for packet switched traffic.

h) 5GS.

5.4.4.1.3 Average round-trip N9 delay on I-UPF

a) This measurement provides the average round-trip delay on a N9 interface on I-UPF. This measurement is split into subcounters per DSCP (Differentiated Services Code Point).

b) DER (n=1).

c) This measurement is obtained as: the sum (the time when receiving a GTP echo reply message from the PSA UPF at I-UPF’s ingress GTP termination, minus time when sending the associated echo request message to PSA UPF at the I-UPF’s GTP egress termination) divided by total number of GTP echo reply message received at I-UPF’s ingress GTP termination. This measurement is calculated for each DSCP.

d) Each measurement is a real representing the average delay in microseconds.

e) The measurement name has the form GTP.RttDelayN9IUpfMean.DSCP
Where DSCP identifies the DSCP.

f) EP_N9.

g) Valid for packet switched traffic.

h) 5GS.

5.4.4.1.4 Distribution of round-trip N9 delay on I-UPF

a) This measurement provides the distribution of delay on a N9 interface on I-UPF. This measurement is split into subcounters per DSCP (Differentiated Services Code Point).

b) DER (n=1).

c) This measurement is obtained by 1) calculating the RTT N9 delay by: the time when receiving a GTP echo reply message from the PSA UPF at I-UPF’s ingress GTP termination, minus time when sending the associated echo request message to PSA UPF at the I-UPF’s GTP egress termination; and 2) incrementing the corresponding bin with the delay range where the result of 1) falls into by 1 for the subcounters per DSCP.

d) Each measurement is an integer representing the number of GTP echo messages measured with the delay within the range of the bin.

e) The measurement name has the form GTP.RttDelayN9IUpfDist.Bin.DSCP
Where Bin indicates a delay range which is vendor specific, and DSCP identifies the DSCP.

f) EP_N9.

g) Valid for packet switched traffic.

h) 5GS.

5.4.4.2 GTP Data Packets and volume on N9 interface

5.4.4.2.1 Number of incoming GTP data packets on the N9 interface for PSA UPF

a) This measurement provides the number of GTP data PDUs received on the N9 interface by the PSA UPF. This measurement is optionally split into subcounters per S-NSSAI.

b) CC

c) Reception by the PSA UPF of a GTP-U data PDU on the N9 interface from the I-UPF, see TS 23.501 [4].

d) Each measurement is an integer value.

e) GTP.InDataPktN9PsaUpf, and optionally
GTP.InDataPktN9PsaUpf.SNSSAI, where SNSSAI identifies the S-NSSAI.

f) EP_N9

g) Valid for packet switching.

h) 5GS

5.4.4.2.2 Number of outgoing GTP data packets of on the N9 interface for PSA UPF

a) This measurement provides the number of GTP data PDUs sent on the N9 interface by the PSA UPF. This measurement is optionally split into subcounters per S-NSSAI.

b) CC

c) Transmission by the PSA UPF of a GTP-U data PDU of on the N9 interface to the I-UPF, see TS 23.501 [4].

d) Each measurement is an integer value.

e) GTP.OutDataPktN9PsaUpf, and optionally
GTP.OutDataPktN9PsaUpf.SNSSAI, where SNSSAI identifies the S-NSSAI

f) EP_N9

g) Valid for packet switching.

h) 5GS

5.4.4.2.3 Number of octets of incoming GTP data packets on the N9 interface for PSA UPF

a) This measurement provides the number of octets of GTP data PDUs received on the N9 interface by the PSA UPF. This measurement is optionally split into subcounters per S-NSSAI.

b) CC

c) Reception by the PSA UPF of a GTP-U data PDU on the N9 interface from the I-UPF, see TS 23.501 [4].

d) Each measurement is an integer value.

e) GTP.InDataOctN9PsaUpf, and optionally
GTP.InDataOctN9PsaUpf.SNSSAI, where SNSSAI identifies the S-NSSAI.

f) EP_N9

g) Valid for packet switching

h) 5GS

5.4.4.2.4 Number of octets of outgoing GTP data packets on the N9 interface for PSA UPF

a) This measurement provides the number of octets of outgoing GTP data PDUs sent on the N9 interface by the PSA UPF. This measurement is optionally split into subcounters per S-NSSAI.

b) CC

c) Transmission by the PSA UPF of a GTP-U data PDU of on the N9 interface to the I-UPF, see TS 23.501 [4].

d) Each measurement is an integer value.

e) GTP.OutDataOctN9PsaUpf and optionally
GTP.OutDataOctN9PsaUpf.SNSSAI, where SNSSAI identifies the S-NSSAI.

f) EP_N9

g) Valid for packet switching

h) 5GS

5.4.5 GTP packets delay in UPF

5.4.5.1 DL GTP packets delay in UPF

5.4.5.1.1 Average DL GTP packets delay in PSA UPF

a) This measurement provides the average (arithmetic mean) DL GTP packets delay within the PSA UPF. The measurement is split into subcounters per 5QI and subcounters per S-NSSAI.

b) DER (n=1).

c) This measurement is obtained as: 1) sampling the DL GTP PDUs (sampling rate is vendor specific) for this measurement, 2) sum of (time when sending the sampled DL GTP PDU to the gNB-CU-UP or I-UPF at the PSA UPF’s egress GTP termination, minus time of arrival of the same packet at PSA UPF’s ingress IP termination for N6 interface) divided by total number of sampled DL GTP PDUs sent to the gNB-CU-UP or I-UPF. The measurement is calculated per 5QI and per S-NSSAI.

d) Each measurement is an integer representing the mean delay in microseconds.

e) GTP.DelayDlInPsaUpfMean.5QI, where 5QI identifies the 5QI;
GTP.DelayDlInPsaUpfMean.SNSSAI, where SNSSAI identifies the S-NSSAI.

f) UPFFunction.

g) Valid for packet switched traffic.

h) 5GS.

5.4.5.1.2 Distribution of DL GTP packets delay in PSA UPF

a) This measurement provides the distribution of DL GTP packets delay within the PSA UPF. The measurement is split into subcounters per 5QI and subcounters per S-NSSAI.

b) DER (n=1).

c) This measurement is obtained by 1) sampling the DL GTP PDUs (sampling rate is vendor specific) for this measurement, 2) calculating the DL delay for the sampled GTP PDU in I-UPF by: time when sending the sampled DL GTP PDU to the gNB-CU-UP or I-UPF at the PSA UPF’s egress GTP termination, minus time of arrival of the same packet at PSA UPF’s ingress IP termination for N6 interface; and 3) incrementing the corresponding bin with the delay range where the result of 2) falls into by 1 for the subcounters per 5QI and subcounters per S-NSSAI.

d) Each measurement is an integer representing the number of sampled DL GTP PDUs measured with the delay within the range of the bin.

e) GTP.DelayDlInPsaUpfDist.Bin.5QI, where Bin indicates a delay range which is vendor specific, and 5QI identifies the 5QI;
GTP.DelayDlInPsaUpfDist.Bin.SNSSAI, where Bin indicates a delay range which is vendor specific, and SNSSAI identifies the S-NSSAI.

f) UPFFunction.

g) Valid for packet switched traffic.

h) 5GS.

5.4.5.1.3 Average DL GTP packets delay in I-UPF

a) This measurement provides the average (arithmetic mean) DL GTP packets delay within the I-UPF. The measurement is split into subcounters per 5QI and subcounters per S-NSSAI.

b) DER (n=1).

c) This measurement is obtained as: 1) sampling the DL GTP PDUs (sampling rate is vendor specific) for this measurement, 2) sum of (time when sending the sampled DL GTP PDU to the gNB-CU-UP at the I-UPF’s egress GTP termination, minus time of arrival of the same packet at I-UPF’s ingress GTP termination for N9 interface) divided by total number of sampled DL GTP PDUs sent to the gNB-CU-UP. The measurement is calculated per 5QI and per S-NSSAI.

d) Each measurement is an integer representing the mean delay in microseconds.

e) GTP.DelayDlInIUpfMean.5QI, where 5QI identifies the 5QI;
GTP.DelayDlInIUpfMean.SNSSAI, where SNSSAI identifies the S-NSSAI.

f) UPFFunction.

g) Valid for packet switched traffic.

h) 5GS.

5.4.5.1.4 Distribution of DL GTP packets delay in I-UPF

a) This measurement provides the distribution of DL GTP packets delay within the I-UPF. The measurement is split into subcounters per 5QI and subcounters per S-NSSAI.

b) DER (n=1).

c) This measurement is obtained by 1) sampling the DL GTP PDUs (sampling rate is vendor specific) for this measurement, 2) calculating the DL delay for the sampled GTP PDU in I-UPF by: time when sending the DL GTP PDU to the gNB-CU-UP at the I-UPF’s egress GTP termination, minus time of arrival of the same packet at I-UPF’s ingress GTP termination for N9 interface; and 3) incrementing the corresponding bin with the delay range where the result of 2) falls into by 1 for the subcounters per 5QI and subcounters per S-NSSAI.

d) Each measurement is an integer representing the number of sampled DL GTP PDUs measured with the delay within the range of the bin.

e) GTP.DelayDlInIUpfDist. Bin.5QI, where Bin indicates a delay range which is vendor specific, and 5QI identifies the 5QI;
GTP.DelayDlInIUpfDist. Bin.SNSSAI, where Bin indicates a delay range which is vendor specific, and SNSSAI identifies the S-NSSAI.

f) UPFFunction.

g) Valid for packet switched traffic.

h) 5GS.

5.4.5.2 UL GTP packets delay in UPF

5.4.5.2.1 Average UL GTP packets delay in PSA UPF

a) This measurement provides the average (arithmetic mean) UL GTP packets delay within the PSA UPF. The measurement is split into subcounters per 5QI and subcounters per S-NSSAI.

b) DER (n=1).

c) This measurement is obtained as: 1) sampling the UL GTP PDUs (sampling rate is vendor specific) for this measurement, 2) sum of (time when sending the sampled UL data packet at the PSA UPF’s egress IP termination for N6 interface, minus time of arrival of the corresponding GTP SDU from N3 or N9 interface at PSA UPF’s ingress GTP termination) divided by total number of sampled UL data packets sent to N6 interface. The measurement is calculated per 5QI and per S-NSSAI.

d) Each measurement is an integer representing the mean delay in microseconds.

e) GTP.DelayUlInPsaUpfMean.5QI, where 5QI identifies the 5QI;
GTP.DelayUlInPsaUpfMean.SNSSAI, where SNSSAI identifies the S-NSSAI.

f) UPFFunction.

g) Valid for packet switched traffic.

h) 5GS.

5.4.5.2.2 Distribution of UL GTP packets delay in PSA UPF

a) This measurement provides the distribution of UL GTP packets delay within the PSA UPF. The measurement is split into subcounters per 5QI and subcounters per S-NSSAI.

b) DER (n=1).

c) This measurement is obtained by 1) sampling the UL GTP PDUs (sampling rate is vendor specific) for this measurement, 2) calculating the UL delay for a GTP PDU in I-UPF by: time when sending the sampled UL data packet at the PSA UPF’s egress IP termination for N6 interface, minus time of arrival of the corresponding GTP SDU from N3 or N9 interface at PSA UPF’s ingress GTP termination; and 3) incrementing the corresponding bin with the delay range where the result of 2) falls into by 1 for the subcounters per 5QI and subcounters per S-NSSAI.

d) Each measurement is an integer representing the number of sampled UL GTP PDUs measured with the delay within the range of the bin.

e) GTP.DelayUlInPsaUpfDist.Bin.5QI, where Bin indicates a delay range which is vendor specific, and 5QI identifies the 5QI;
GTP.DelayUlInPsaUpfDist.Bin.SNSSAI, where Bin indicates a delay range which is vendor specific, and SNSSAI identifies the S-NSSAI.

f) UPFFunction.

g) Valid for packet switched traffic.

h) 5GS.

5.4.5.2.3 Average UL GTP packets delay in I-UPF

a) This measurement provides the average (arithmetic mean) UL GTP packets delay within the I-UPF. The measurement is split into subcounters per 5QI and subcounters per S-NSSAI.

b) DER (n=1).

c) This measurement is obtained as: 1) sampling the UL GTP PDUs (sampling rate is vendor specific) for this measurement, 2) sum of (time when sending the sampled UL GTP PDU to the PSA UPF at the I-UPF’s egress GTP termination, minus time of arrival of the same packet from N3 interface at I-UPF’s ingress GTP termination) divided by total number of sampled UL GTP PDUs sent to the PSA UPF. The measurement is calculated per 5QI and per S-NSSAI.

d) Each measurement is an integer representing the mean delay in microseconds.

e) GTP.DelayUlInIUpfMean.5QI, where 5QI identifies the 5QI;
GTP.DelayUlInIUpfMean.SNSSAI, where SNSSAI identifies the S-NSSAI.

f) UPFFunction.

g) Valid for packet switched traffic.

h) 5GS.

5.4.5.2.4 Distribution of UL GTP packets delay in I-UPF

a) This measurement provides the distribution of UL GTP packets delay within the I-UPF. The measurement is split into subcounters per 5QI and subcounters per S-NSSAI.

b) DER (n=1).

c) This measurement is obtained by 1) sampling the UL GTP PDUs (sampling rate is vendor specific) for this measurement, 2) calculating the UL delay for a GTP PDU in I-UPF by: time when sending the sampled UL GTP PDU to the PSA UPF at the I-UPF’s egress GTP termination, minus time of arrival of the same packet from N3 interface at I-UPF’s ingress GTP termination; and 3) incrementing the corresponding bin with the delay range where the result of2) falls into by 1 for the subcounters per 5QI and subcounters per S-NSSAI.

d) Each measurement is an integer representing the number of sampled UL GTP PDUs measured with the delay within the range of the bin.

e) GTP.DelayUlInIUpfDist.Bin.5QI, where Bin indicates a delay range which is vendor specific, and 5QI identifies the 5QI;
GTP.DelayUlInIUpfDist.Bin.SNSSAI, where Bin indicates a delay range which is vendor specific, and SNSSAI identifies the S-NSSAI.

f) UPFFunction.

g) Valid for packet switched traffic.

h) 5GS.

5.4.6 Void

5.4.7 One way packet delay between NG-RAN and PSA UPF

5.4.7.1 UL packet delay between NG-RAN and PSA UPF

5.4.7.1.1 Average UL GTP packet delay between PSA UPF and NG-RAN

a) This measurement provides the average UL GTP packet delay between PSA UPF and NG-RAN. This measurement is split into subcounters per 5QI and subcounters per S-NSSAI. This measurement is only applicable to the case the PSA UPF and NG-RAN are time synchronised.

b) DER (n=1).

c) The measurement is obtained by the following method:

The UPF samples the GTP packets for QoS monitoring based on the policy provided by OAM or SMF.

NOTE: The sampling rate may vary for different S-NSSAI and different 5QIs, and the specific sampling rate is up to implementation unless given by the QoS monitoring policy.

For each GTP PDU monitoring response packet (packet i) for QoS monitoring, the PSA UPF records the following time stamps and information (see 23.501 [4] and 38.415 [31]):

– T3 received in the GTP-U header of the monitoring response packet indicating the local time that the monitoring response packet was sent by the NG-RAN;

– T4 that the monitoring response packet was received by the PSA UPF;

– The 5QI and S-NSSAI associated to the GTP PDU.

The PSA UPF counts the number (N) of GTP PDU monitoring response packets for each 5QI and each S-NSSAI respectively, and takes the following calculation for each 5QI and each S-NSSAI:

d) Each measurement is a real representing the average delay in microseconds.

e) GTP.DelayUlPsaUpfNgranMean.5QI, where 5QI identifies the 5QI;
GTP.DelayUlPsaUpfNgranMean.SNSSAI, where SNSSAI identifies the S-NSSAI.

f) EP_N3 (contained by UPFFunction);
EP_N9 (contained by UPFFunction).

g) Valid for packet switched traffic.

h) 5GS.

5.4.7.1.2 Distribution of UL GTP packet delay between PSA UPF and NG-RAN

a) This measurement provides the distribution of UL GTP packet delay between PSA UPF and NG-RAN. This measurement is split into subcounters per 5QI and subcounters per S-NSSAI. This measurement is only applicable to the case the PSA UPF and NG-RAN are time synchronised.

b) DER (n=1).

c) The measurement is obtained by the following method:

The UPF samples the GTP packets for QoS monitoring based on the policy provided by OAM or SMF.

NOTE: The sampling rate may vary for different S-NSSAI and different 5QIs, and the specific sampling rate is up to implementation unless given by the QoS monitoring policy.

For each GTP PDU monitoring response packet (packet i) for QoS monitoring, the PSA UPF records the following time stamps and information (see 23.501 [4] and 38.415 [31]):

– T3 received in the GTP-U header indicating the local time that the NG-RAN sent out the monitoring response packet to the UPF;

– T4 that the monitoring response packet received by the PSA UPF;

– The 5QI and S-NSSAI associated to the DL GTP PDU.

The PSA UPF 1) takes the following calculation for each GTP PDU monitoring response packets for each 5QI and each S-NSSAI respectively, and 2) increment the corresponding bin with the delay range where the result of 1) falls into by 1 for the subcounters per 5QI and subcounters per S-NSSAI.

d) Each measurement is an integer representing the number of GTP PDUs measured with the delay within the range of the bin.

e) GTP.DelayUlPsaUpfNgranDist.5QI.Bin, Where Bin indicates a delay range which is vendor specific, and 5QI identifies the 5QI;
GTP.DelayUlPsaUpfNgranDist.SNSSAI.bin, Where Bin indicates a delay range which is vendor specific, and SNSSAI identifies the S-NSSAI.

f) EP_N3 (contained by UPFFunction);
EP_N9 (contained by UPFFunction).

g) Valid for packet switched traffic.

h) 5GS.

5.4.8 Round-trip packet delay between PSA UPF and NG-RAN

5.4.8.1 Average round-trip packet delay between PSA UPF and NG-RAN

a) This measurement provides the average round-trip GTP packet delay between PSA UPF and NG-RAN. This measurement is split into subcounters per 5QI and subcounters per S-NSSAI. This measurement is only applicable to the case the PSA UPF and NG-RAN are not time synchronised.

b) DER (n=1).

c) The measurement is obtained by the following method:

The UPF samples the GTP packets for QoS monitoring based on the policy provided by OAM or SMF.

NOTE: The sampling rate may vary for different S-NSSAI and different 5QIs, and the specific sampling rate is up to implementation unless given by the QoS monitoring policy.

For each received GTP PDU monitoring response packet (packet i) encapsulated with QFI, TEID, and QMP indicator for QoS monitoring, the PSA UPF records the following time stamps and information (see 23.501 [4] and 38.415 [31]):

– T1 received in the GTP-U header of the monitoring response packet indicating the local time that the DL GTP PDU was sent by the PSA UPF;

– T2 received in the GTP-U header of the monitoring response packet indicating the local time that the DL GTP PDU was received by NG-RAN;

– T3 received in the GTP-U header of the monitoring response packet indicating the local time that the monitoring response packet was sent by the NG-RAN;

– T4 that the monitoring response packet was received by the PSA UPF;

– The 5QI and S-NSSAI associated to the DL GTP PDU.

The PSA UPF counts the number (N) of received GTP PDU monitoring response packets for each 5QI and each S-NSSAI respectively, and takes the following calculation for each 5QI and each S-NSSAI:

d) Each measurement is a real representing the average delay in microseconds.

e) GTP.RttDelayPsaUpfNgranMean.5QI, where 5QI identifies the 5QI;
GTP.RttDelayPsaUpfNgranMean.SNSSAI, where SNSSAI identifies the S-NSSAI.

f) EP_N3 (contained by UPFFunction);
EP_N9 (contained by UPFFunction).

g) Valid for packet switched traffic.

h) 5GS.

5.4.8.2 Distribution of round-trip packet delay between PSA UPF and NG-RAN

a) This measurement provides the distribution of round-trip GTP packet delay between PSA UPF and NG-RAN. This measurement is split into subcounters per 5QI and subcounters per S-NSSAI. This measurement is only applicable to the case the PSA UPF and NG-RAN are not time synchronised.

b) DER (n=1).

c) The measurement is obtained by the following method:

The UPF samples the GTP packets for QoS monitoring based on the policy provided by OAM or SMF.

NOTE: The sampling rate may vary for different S-NSSAI and different 5QIs, and the specific sampling rate is up to implementation unless given by the QoS monitoring policy.

For each received GTP PDU monitoring response packet (packet i) for QoS monitoring, the PSA UPF records the following time stamps and information (see 23.501 [4] and 38.415 [31]):

– T1 received in the GTP-U header of the monitoring response packet indicating the local time that the DL GTP PDU was sent by the PSA UPF;

– T2 received in the GTP-U header of the monitoring response packet indicating the local time that the DL GTP PDU was received by NG-RAN;

– T3 received in the GTP-U header of the monitoring response packet indicating the local time that the monitoring response packet was sent by the NG-RAN;

– T4 that the monitoring response packet was received by the PSA UPF;

– The 5QI and S-NSSAI associated to the DL GTP PDU.

The PSA UPF 1) takes the following calculation for each received GTP PDU monitoring response packet (packet i) for each 5QI and each S-NSSAI respectively, and 2) increment the corresponding bin with the delay range where the result of 1) falls into by 1 for the subcounters per 5QI and subcounters per S-NSSAI.

d) Each measurement is an integer representing the number of DL GTP PDUs measured with the delay within the range of the bin.

e) GTP.RttDelayPsaUpfNgranDist.5QI.Bin, Where Bin indicates a delay range which is vendor specific, and 5QI identifies the 5QI;
GTP.RttDelayPsaUpfNgranDist.SNSSAI.bin, Where Bin indicates a delay range which is vendor specific, and SNSSAI identifies the S-NSSAI.

f) EP_N3 (contained by UPFFunction);
EP_N9 (contained by UPFFunction).

g) Valid for packet switched traffic.

h) 5GS.

5.4.9 One way packet delay between PSA UPF and UE

5.4.9.1 DL packet delay between PSA UPF and UE

5.4.9.1.1 Average DL packet delay between PSA UPF and UE

a) This measurement provides the average DL packet delay between PSA UPF and UE. This measurement is split into subcounters per S-NSSAI. This measurement is only applicable to the case the PSA UPF and NG-RAN are time synchronised.

b) DER (n=1).

c) The measurement is obtained by the following method:

The UPF performs QoS monitoring per the request received from SMF during PDU Session Establishment or Modification procedure.

NOTE: The UPF may sample the GTP packets for QoS monitoring, the specific sampling rate is up to implementation

For each received GTP PDU monitoring response packet (packet i) for QoS monitoring, the PSA UPF records the following time stamps and information included in the GTP-U header (see 23.501 [4] and 38.415 [31]):

– T1 indicating the local time the DL GTP PDU monitoring packet was sent by the PSA UPF;

– T2 indicating the local time that the DL GTP PDU monitoring packet was received by NG-RAN;

– The DL Delay Result from NG-RAN to UE indicating the downlink delay measurement result which is the sum of the delay incurred in NG-RAN (including the delay at gNB-CU-UP, on F1-U and on gNB-DU) and the delay over Uu interface (see 38.415 [31],and the DL Delay Result is denoted by in the present document);

– The S-NSSAI associated to the DL GTP PDU monitoring response packet.

The PSA UPF counts the number (N) of GTP PDU monitoring response packets for each S-NSSAI, and takes the following calculation for each S-NSSAI:

d) Each measurement is a real representing the average delay in 0.1ms.

e) GTP.DelayDlPsaUpfUeMean.SNSSAI, where SNSSAI identifies the S-NSSAI.

f) EP_N3 (contained by UPFFunction);
EP_N9 (contained by UPFFunction).

g) Valid for packet switched traffic.

h) 5GS.

5.4.9.1.2 Distribution of DL packet delay between PSA UPF and UE

a) This measurement provides the distribution of DL packet delay between PSA UPF and UE. This measurement is split into subcounters per S-NSSAI. This measurement is only applicable to the case the PSA UPF and NG-RAN are time synchronised.

b) DER (n=1).

c) The measurement is obtained by the following method:

The UPF performs QoS monitoring per the request received from SMF during PDU Session Establishment or Modification procedure.

NOTE: The UPF may sample the GTP packets for QoS monitoring the specific sampling rate is up to implementation.

For each received DL GTP PDU monitoring response packet (packet i) for QoS monitoring, the PSA UPF records the following time stamps and information included in the GTP-U header (see 23.501 [4] and 38.415 [31]):

– T1 indicating the local time the DL GTP PDU monitoring packet was sent by the PSA UPF;

– T2 indicating the local time that the DL GTP PDU monitoring packet was received by NG-RAN;

– The S-NSSAI associated to the DL GTP PDU monitoring response packet.

The PSA UPF 1) takes the following calculation for each GTP PDU monitoring response packet for each S-NSSAI, and 2) increment the corresponding bin with the delay range where the result of 1) falls into by 1 for the subcounter per S-NSSAI.

d) Each measurement is an integer representing the number of GTP PDUs measured with the delay within the range of the bin.

e) GTP.DelayDlPsaUpfUeDist.SNSSAI.bin, where Bin indicates a delay range which is vendor specific, and SNSSAI identifies the S-NSSAI.

f) EP_N3 (contained by UPFFunction);
EP_N9 (contained by UPFFunction).

g) Valid for packet switched traffic.

h) 5GS.

5.4.9.2 UL packet delay between PSA UPF and UE

5.4.9.2.1 Average UL packet delay between PSA UPF and UE

a) This measurement provides the average UL packet delay between PSA UPF and UE. This measurement is split into subcounters per S-NSSAI. This measurement is only applicable to the case the PSA UPF and NG-RAN are time synchronised.

b) DER (n=1).

c) The measurement is obtained by the following method:

The UPF performs QoS monitoring per the request received from SMF during PDU Session Establishment or Modification procedure.

NOTE: The UPF may sample the GTP packets for QoS monitoring, the specific sampling rate is up to implementation.

For each received GTP PDU monitoring response packet (packet i) for QoS monitoring, the PSA UPF records the following time stamps and information (see 23.501 [4] and 38.415 [31]):

– T3 received in the GTP-U header of the monitoring response packet indicating the local time that the monitoring response packet was sent by the NG-RAN;

– T4 that the monitoring response packet was received by the PSA UPF;

– The UL Delay Result from UE to NG-RAN indicating the uplink delay measurement result which is the sum of the delay incurred in NG-RAN (including the delay at gNB-CU-UP, on F1-U and on gNB-DU) and the delay over Uu interface (see 38.415 [31], and the UL Delay Result is denoted by in the present document);

– The S-NSSAI associated to the GTP PDU monitoring response packet.

The PSA UPF counts the number (N) of GTP PDU monitoring response packets for each S-NSSAI, and takes the following calculation for each S-NSSAI:

d) Each measurement is a real representing the average delay in 0.1ms.

e) GTP.DelayUlPsaUpfUeMean.SNSSAI, where SNSSAI identifies the S-NSSAI;

f) EP_N3 (contained by UPFFunction);
EP_N9 (contained by UPFFunction).

g) Valid for packet switched traffic.

h) 5GS.

5.4.9.2.2 Distribution of UL packet delay between PSA UPF and UE

a) This measurement provides the distribution of UL packet delay between PSA UPF and UE. This measurement is split into subcounters per S-NSSAI. This measurement is only applicable to the case the PSA UPF and NG-RAN are time synchronised.

b) DER (n=1).

c) The measurement is obtained by the following method:

The UPF performs QoS monitoring per the request received from SMF during PDU Session Establishment or Modification procedure.

NOTE: The UPF may sample the GTP packets for QoS monitoring, the specific sampling rate is up to implementation.

For each received GTP PDU monitoring response packet (packet i) for QoS monitoring, the PSA UPF records the following time stamps and information (see 23.501 [4] and 38.415 [31]):

– T3 received in the GTP-U header of the monitoring response packet indicating the local time that the monitoring response packet was sent by the NG-RAN;

– T4 that the monitoring response packet was received by the PSA UPF;

– The S-NSSAI associated to the GTP PDU monitoring response packet.

The PSA UPF 1) takes the following calculation for each GTP PDU monitoring response packet (packet i) for each S-NSSAI, and 2) increment the corresponding bin with the delay range where the result of 1) falls into by 1 for the subcounter per S-NSSAI.

d) Each measurement is an integer representing the number of GTP PDUs measured with the delay within the range of the bin.

e) GTP.DelayUlPsaUpfUeDist.SNSSAI.bin, where Bin indicates a delay range which is vendor specific, and SNSSAI identifies the S-NSSAI.

f) EP_N3 (contained by UPFFunction);
EP_N9 (contained by UPFFunction).

g) Valid for packet switched traffic.

h) 5GS.

5.4.10 QoS flow related measurements

5.4.10.1 Mean number of QoS flows

a) This measurement provides the mean number of QoS flows of UPF.

b) SI

c) This measurement is obtained by sampling at a pre-defined interval, the number of QoS flows and then taking the arithmetic mean.The measurement is optionally split into subcounters per S-NSSAI and per DNN.

d) A single integer value

e) UPF.MeanQosFlows
UPF.MeanQosFlows.SNSSAI , where SNSSAI identifies the S-NSSAI.
UPF.MeanQosFlows.Dnn , where Dnn identifies the Data Network Name.

f) UPFFunction

g) Valid for packet switching

h) 5GS

5.4.10.2 Maximum number of QoS flows

a) This measurement provides the max number of QoS flows of UPF.

b) SI

c) This measurement is obtained by sampling at a pre-defined interval, the number of QoS flows and then selecting the maximum value. The measurement is optionally split into subcounters per S-NSSAI and per DNN.

d) A single integer value

e) UPF.MaxQosFlows
UPF.MaxQosFlows.SNSSAI , where SNSSAI identifies the S-NSSAI.
UPF.MaxQosFlows.Dnn , where Dnn identifies the Data Network Name.

f) UPFFunction

g) Valid for packet switching

h) 5GS