5.1.1 Performance measurements valid for all gNB deployment scenarios

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

5.1.1.1.4 Average RLC packet delay in the UL

a) This measurement provides the average (arithmetic mean) RLC packet delay on the uplink, ie the delay within the gNB-DU. The measurement is calculated per PLMN ID and per QoS level (mapped 5QI or QCI in NR option 3) and per supported S-NSSAI.

b) DER (n=1)

c) This measurement is obtained according to the definition in TS 38.314 [29], named "Average RLC packet delay in the UL per DRB per UE". The measurement is performed per PLMN ID and per QoS level (mapped 5QI or QCI in NR option 3) and per supported S-NSSAI.

d) Each measurement is a real representing the mean delay in the unit 0.1 milliseconds. The number of measurements is equal to the number of PLMNs multiplied by the number of QoS levels or multiplied by the number of supported 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.RlcDelayUl_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 QCI level, and SNSSAI represents S-NSSAI.

f) NRCellDU.

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

5.1.1.1.5 Average PDCP re-ordering delay in the UL

a) This measurement provides the average (arithmetic mean) PDCP re-ordering delay on the uplink, ie the delay within the gNB-CU-UP. The measurement is calculated per PLMN ID and per QoS level (mapped 5QI or QCI in NR option 3) and per supported S-NSSAI.

b) DER (n=1)

c) This measurement is obtained according to the definition in TS 38.314 [29], named "Average PDCP re-ordering delay in the UL per DRB per UE. The measurement is performed per PLMN ID and per QoS level (mapped 5QI or QCI in NR option 3) and per supported S-NSSAI.

[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.PdcpReordDelayUl_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 QCI level, and SNSSAI represents S-NSSAI.

f) GNBCUUPFunction

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

5.1.1.1.6 Distribution of DL delay between NG-RAN and UE

a) This measurement provides the distribution of DL packet delay between NG-RAN and UE, which is 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. This measurement is calculated per PLMN ID and per 5QI and per supported S-NSSAI.

b) DER (n=1).

c) The measurement is obtained by the following method:

The gNB performs the GTP PDU packet delay measurement for QoS monitoring per the GTP PDU monitoring packets received from UPF, and records the following time stamps and information included in the GTP-U header of each GTP PDU monitoring response packet (packet i) sent to UPF (see 23.501 [4] and 38.415 [31]):

– 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 5QI and S-NSSAI associated to the GTP PDU monitoring response packet.

The gNB increments the corresponding bin with the delay range where the falls into by 1 for the counters.

The measurement is performed per PLMN ID and per QoS level (mapped 5QI or QCI in NR option 3) and per supported S-NSSAI.

d) Each measurement is an integer representing the number of GTP PDUs measured with the delay within the range of the bin.The number of measurements is equal to the number of PLMNs multiplied by the number of QoS levels or multiplied by the number of supported S-NSSAIs.
[Total No. of measurement instances] x [No. of filter values for all measurements] (DL and UL) ≤ 100.

e) DRB.DelayDlNgranUeDist.Bin_Filter, where Bin indicates a delay range which is vendor specific;

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 QCI level, and SNSSAI represents S-NSSAI.

f) NRCellCU (for non-split and 2-split scenario);
GNBCUUPFunction (for 3-split scenario).

g) Valid for packet switched traffic.

h) 5GS.

5.1.1.1.7 Distribution of UL delay between NG-RAN and UE

a) This measurement provides the distribution of UL packet delay between NG-RAN and UE, which is 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. This measurement is calculated per PLMN ID and per 5QI and per supported S-NSSAI.

b) DER (n=1).

c) The measurement is obtained by the following method:

– 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 5QI and S-NSSAI associated to the GTP PDU monitoring response packet.

The gNB increments the corresponding bin with the delay range where the falls into by 1 for the counters.

The measurement is performed per PLMN ID and per QoS level (mapped 5QI or QCI in NR option 3) and per supported S-NSSAI.

d) Each measurement is an integer representing the number of GTP PDUs measured with the delay within the range of the bin. The number of measurements is equal to the number of PLMNs multiplied by the number of QoS levels or multiplied by the number of supported S-NSSAIs.
[Total No. of measurement instances] x [No. of filter values for all measurements] (DL and UL) ≤ 100.

e) DRB.DelayUlNgranUeDist.Bin_Filter, where Bin indicates a delay range which is vendor specific;
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 QCI level, and SNSSAI represents S-NSSAI.

f) NRCellCU (for non-split and 2-split scenario);
GNBCUUPFunction (for 3-split scenario).

g) Valid for packet switched traffic.

h) 5GS.

5.1.1.1.8 DL packet delay between NG-RAN and PSA UPF

5.1.1.1.8.1 Average DL GTP packet delay between PSA UPF and NG-RAN

a) This measurement provides the average DL 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 DL GTP PDU (packet i) encapsulated with QFI, TEID, and QMP indicator for QoS monitoring, the gNB records the following time stamps and information (see 23.501 [4] and 38.415 [31]):

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

– T2 that the DL GTP PDU was received by NG-RAN;

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

The gNB counts the number (N) of DL GTP PDUs encapsulated with QFI, TEID, and QMP indicator 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.DelayDlPsaUpfNgranMean.5QI, where 5QI identifies the 5QI;
GTP.DelayDlPsaUpfNgranMean.SNSSAI, where SNSSAI identifies the S-NSSAI.

f) EP_N3 (contained by GNBCUUPFunction).

g) Valid for packet switched traffic.

h) 5GS.

5.1.1.1.8.2 Distribution of DL GTP packet delay between PSA UPF and NG-RAN

a) This measurement provides the distribution of DL 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 DL GTP PDU (packet i) encapsulated with QFI, TEID, and QMP indicator for QoS monitoring, the gNB records the following time stamps and information (see 23.501 [4] and 38.415 [31]):

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

– T2 that the DL GTP PDU was received by NG-RAN;

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

The gNB 1) takes the following calculation for each DL GTP PDU (packet i) encapsulated with QFI, TEID, and QMP indicator 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.DelayDlPsaUpfNgranDist.5QI.Bin, Where Bin indicates a delay range which is vendor specific, and 5QI identifies the 5QI;
GTP.DelayDlPsaUpfNgranDist.SNSSAI.bin, Where Bin indicates a delay range which is vendor specific, and SNSSAI identifies the S-NSSAI.

f) EP_N3 (contained by GNBCUUPFunction).

g) Valid for packet switched traffic.

h) 5GS.

5.1.1.2 Radio resource utilization

5.1.1.2.1 DL Total PRB Usage

a) This measurement provides the total usage (in percentage) of physical resource blocks (PRBs) on the downlink for any purpose.

b) SI

c) This measurement is obtained as: , where is the DL total PRB usage, which is percentage of PRBs used, averaged during time period with value range: 0-100%; is a count of full physical resource blocks and all PRBs used for DL traffic transmission shall be included; is total number of PRBs available for DL traffic transmission during time period ; and is the time period during which the measurement is performed.

d) A single integer value from 0 to 100.

e) RRU.PrbTotDl, which indicates the DL PRB Usage for all traffic

f) NRCellDU

g) Valid for packet switched traffic

h) 5GS

i) One usage of this measurement is for monitoring the load of the radio physical layer.

5.1.1.2.2 UL Total PRB Usage

a) This measurement provides the total usage (in percentage) of physical resource blocks (PRBs) on the uplink for any purpose.

b) SI

c) This measurement is obtained as: , where is the UL total PRB usage, which is percentage of PRBs used, averaged during time period with value range: 0-100%; is a count of full physical resource blocks and all PRBs used for UL traffic transmission shall be included; is total number of PRBs available for UL traffic transmission during time period ; and is the time period during which the measurement is performed

d) A single integer value from 0 to 100.

e) RRU.PrbTotUl, which indicates the UL PRB Usage for all traffic

f) NRCellDU

g) Valid for packet switched traffic

h) 5GS

i) One usage of this measurement is for monitoring the load of the radio physical layer.

5.1.1.2.3 Distribution of DL Total PRB Usage

a) This measurement provides the distribution of samples with total usage (in percentage) of physical resource blocks (PRBs) on the downlink in different ranges. This measurement is a useful measure of whether a cell is under high loads or not in the scenario which a cell in the downlink may experience high load in certain short times (e.g. in a millisecond) and recover to normal very quickly.

b) CC

c) Each measurement sample is obtained as: , where is total PRB usage at sample n for DL, which is a percentage of PRBs used, averaged during time period t_n (e.g. a millisecond) with value range: 0-100%; is a count of full physical resource blocks and all PRBs used for DL traffic transmission shall be included;is the total number of PRBs available for DL traffic transmission during time period t_n and n is the sample with time period t_n during which the measurement is performed.

d) Distribution of total PRB usage is calculated in the time-frequency domain only. The reference point is the Service Access Point between MAC and L1. The distribution of PRB usage provides the histogram result of the samples collected during time period t_n.

e) Depending on the value of the sample, the proper bin of the counter is increased. The number of samples during one measurement period is provided by the operator.

f) A set of integers. Each representing the (integer) number of samples with a DL total PRB percentage usage in the range represented by that bin.

g) RRU.PrbTotDlDist.BinX, which indicates the distribution of DL PRB Usage for all traffic.

h) NRCellDU

i) Valid for packet switched traffic

j) 5GS

k) One usage of this measurement is for monitoring the load of the radio physical layer.

5.1.1.2.4 Distribution of UL total PRB usage

a) This measurement provides the distribution of samples with total usage (in percentage) of physical resource blocks (PRBs) on the uplink in different usage ranges. This measurement is a useful measure of whether a cell is under high loads or not in the scenario which a cell in the uplink may experience high load in certain short times (e.g. in a millisecond) and recover to normal very quickly.

b) CC

c) Each measurement sample is obtained as: , where is total PRB usage at sample n for UL, which is a percentage of PRBs used, averaged during time period t_n (e.g. a millisecond) with value range: 0-100%; is a count of full physical resource blocks and all PRBs used for UL traffic transmission shall be included;is the total number of PRBs available for UL traffic transmission during time period t_n and n is the sample with time period t_n during which the measurement is performed.

Distribution of total PRB usage is calculated in the time-frequency domain only. The reference point is the Service Access Point between MAC and L1. The distribution of PRB usage provides the histogram result of the samples collected during time period t_n.

Depending on the value of the sample, the proper bin of the counter is increased. The number of samples during one measurement period is provided by the operator.

d) A set of integers, each representing the (integer) number of samples with a UL PRB percentage usage in the range represented by that bin.

e) RRU.PrbTotUlDist.BinX, which indicates the distribution of UL PRB Usage for all traffic.

f) NRCellDU

g) Valid for packet switched traffic

h) 5GS

i) One usage of this measurement is for monitoring the load of the radio physical layer.

5.1.1.2.5 Mean DL PRB used for data traffic

a) This measurement provides the number of physical resource blocks (PRBs) in average used in downlink for data traffic. The measurement is optionally split into subcounters per QoS level (mapped 5QI or QCI in NR option 3) and subcounters per supported S-NSSAI and subcounters per supported PLMN ID.

b) SI.

c) Each measurement is obtained as the averagenumber (arithmetic mean) of all PRBs used for DL data traffic transmission per S-NSSAI and per PLMN ID during a time period T.

d) Each measurement is a single integer value. If the optional measurements are perfomed, the number of measurements is equal to the number of QoS levels and the number of supported S-NSSAIs and the number of supported PLMN.

e) RRU.PrbUsedDl, or optionally RRU.PrbUsedDl.QoS, where the QoS identifies the target quality of service class and RRU.PrbUsedDl.SNSSAI, where SNSSAI identifies the S-NSSAI, and RRU.PrbUsedDl.PLMN, where PLMN identifies the PLMN ID.

f) NRCellDU.

g) Valid for packet switched traffic.

h) 5GS.

i) One usage of this measurement is for monitoring the DL PRB load of the radio physical layer per S-NSSAI.

a) This measurement provides the number of PRBs used in uplink for data traffic. 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) Each measurement is obtained by sampling at a pre-defined interval, the PRBs used for UL data traffic transmission per S-NSSAI during a time period T, and selecting the sample with the maximum value from the samples collected in a given period.

e) RRU.MaxPrbUsedUl, or optionally RRU.MaxPrbUsedUl.QoS, where the QoS identifies the target quality of service class and RRU.MaxPrbUsedUl.SNSSAI, where SNSSAI identifies the S-NSSAI.

f) NRCellDU.

g) Valid for packet switched traffic.

h) 5GS.

i) One usage of this measurement is for monitoring the UL PRB load of the radio physical layer per S-NSSAI to support RRM resources optimization (see TS 28.313 [30]).

5.1.1.2.11 PDSCH PRB Usage per cell for MIMO

a) This measurement provides the total usage (in percentage) of physical resource blocks (PRBs) per cell for MIMO with time domain averaged maximum scheduled layer number as spatial factor in the downlink.

b) SI

c) This measurement is obtained as:

Where

denotes total PDSCH PRB usage per cell which is percentage of PRBs used, averaged during time period 𝑇 with integer value range: 0-100;

denotes the number of PDSCH PRBs multiplexed by i MIMO layers at sampling occasion j.

denotes total number of PDSCH PRBs available for sampling occasion j on single MIMO layer per cell;

LM(T) denotes the time-domain averaged maximum scheduled layer number of PDSCH in time period T defined in clause 5.1.1.30.3 of the present document;

NOTE: At every sampling occasion the maximum scheduled layer number of all PRBs included in PDSCH is collected as a sampling value and at the end of statistical duration the average of all non-zero sampling values is the measuremnt result as defined in clause 5.1.1.30.3 of the present document.

T denotes the time period during which measurement is performed;

i is an integer denoting a MIMO layer number that is scheduled in time period T;

j denotes sampling occasion (e.g. 1 slot) during time period T.

d) A single integer value from 0 to 100.

e) RRU.PrbTotDlMimo, which indicates the PDSCH PRB Usage per cell for MIMO

f) NRCellDU

g) Valid for packet switched traffic

h) 5GS

i) One usage of this measurement is for monitoring the load of the radio physical layer under MIMO scenario.

5.1.1.2.12 PUSCH PRB Usage per cell for MIMO

b) SI

c) This measurement is obtained as:

Where

denotes total PUSCH PRB usage per cell which is percentage of PRBs used, averaged during time period 𝑇 with integer value range: 0-100;

denotes the number of PUSCH PRBs multiplexed by i MIMO layers at sampling occasion j.

denotes total number of PUSCH PRBs available for sampling occasion j on single MIMO layer per cell;

LM(T) denotes the time-domain averaged maximum scheduled layer number of PUSCH in time period T defined in clause 5.1.1.30.4 of the present document;

NOTE: At every sampling occasion the maximum scheduled layer number of all PRBs included in PUSCH is collected as a sampling value and at the end of statistical duration the average of all non-zero sampling values is the measuremnt result as defined in clause 5.1.1.30.4 of the present document.

T denotes the time period during which measurement is performed;

i is an integer denoting a MIMO layer number that is scheduled in time period T;

j denotes sampling occasion (e.g. 1 slot) during time period T.

d) A single integer value from 0 to 100.

e) RRU.PrbTotUlMimo, which indicates the PUSCH PRB Usage per cell for MIMO

f) NRCellDU

g) Valid for packet switched traffic

h) 5GS

i) One usage of this measurement is for monitoring the load of the radio physical layer under MIMO scenario.

5.1.1.2.13 SDM PDSCH PRB Usage

a) Due to MIMO technology (strong Space Division Multiplexing ability), the cell capacity has been improved obviously. This measurement provides the total usage (in percentage) of PDSCH physical resource blocks (PRBs), based on statistical MIMO layers. The objective is to measure the usage of cell DL capacity in MIMO scenario. A use-case is wireless network workload observation.

b) SI

c) This measurement is defined according to "PDSCH PRB Usage based on statistical MIMO layer in the DL per cell " in TS 38.314 [29] as:

Where

denotes total PDSCH PRB usage per cell which is percentage of PRBs used, averaged during time period with integer value.

denotes a count of PDSCH PRBs used for traffic transmission for UE on single MIMO layer per cell at sampling occasion . Counting unit for PRB is 1 Resource Block x 1 symbol. (1 Resource Block = 12 sub-carriers).

denotes the number of MIMO layers scheduled for UE at sampling occasion .

denotes a UE that is scheduled during time period .

denotes sampling occasion during time period . A sampling occasion is 1 symbol.

denotes total number of PDSCH PRBs available for sampling occasion j on single MIMO layer per cell.

denotes the time period during which the measurement is performed to calculate , e.g. 15min, 1 hour, etc.

is a variable factor for MIMO layers assigned with the maximum during time period 2 with float value 1.00-100.00. For this measurement, the same β value is used for the entire duration of T1.

is the "Average value of scheduled MIMO layers per PRB on the DL", during time period with float value 1.00-100.00, as defined in 5.1.1.30.

denotes time period during which the measurement is performed to calculate , as defined in 5.1.1.30.

is the time period during which the measurement is performed to calculate , e.g.1 week, etc.

d) A single integer value from 0 to 100.

e) RRU.PrbTotSdmDl, which indicates the DL SDM PRB Usage in a Cell supporting MIMO.

f) NRCellDU

g) Valid for packet switched traffic

h) 5GS

i) One usage of this measurement is for monitoring the DL Radio Resource Utilization in a cell supporting MIMO.

5.1.1.2.14 SDM PUSCH PRB Usage

a) Due to MIMO technology (strong Space Division Multiplexing ability), the cell capacity has been improved obviously. This measurement provides the total usage (in percentage) of PUSCH physical resource blocks (PRBs), based on statistical MIMO layers. The objective is to measure the usage of cell UL capacity in MIMO scenario. A use-case is wireless network workload observation.

b) SI

c) This measurement is defined according to "PUSCH PRB Usage based on statistical MIMO layer in the UL per cell " in TS 38.314 [29] as:

Where

denotes total PUSCH PRB usage per cell which is percentage of PRBs used, averaged during time period with integer value.

denotes a count of PUSCH PRBs used for traffic transmission for UE on single MIMO layer per cell at sampling occasion . Counting unit for PRB is 1 Resource Block x 1 symbol. (1 Resource Block = 12 sub-carriers).

denotes the number of MIMO layers scheduled for UE at sampling occasion .

denotes a UE that is scheduled during time period .

denotes sampling occasion during time period . A sampling occasion is 1 symbol.

denotes total number of PUSCH PRB available for sampling occasion j on single MIMO layer per cell.

denotes the time period during which the measurement is performed to calculate , e.g. 15min, 1 hour, etc.

is a variable factor for MIMO layers assigned with the maximum during time period 2 with float value 1.00-100.00. For this measurement, the same β value is used for the entire duration of T1.

is the "Average value of scheduled MIMO layers per PRB on the UL", during time period with float value 1.00-100.00, as defined in 5.1.1.30.

denotes time period during which the measurement is performed to calculate , as defined in 5.1.1.30.

is the time period during which the measurement is performed to calculate , e.g.1 week, etc.

d) A single integer value from 0 to 100.

e) RRU.PrbTotSdmUl, which indicates the UL SDM PRB Usage in a Cell supporting MIMO.

f) NRCellDU

g) Valid for packet switched traffic

h) 5GS

i) One usage of this measurement is for monitoring the UL Radio Resource Utilization in a cell supporting MIMO.

5.1.1.3 UE throughput

5.1.1.3.1 Average DL UE throughput in gNB

a) This measurement provides the average UE throughput in downlink. This measurement is intended for data bursts that are large enough to require transmissions to be split across multiple slots. The UE data volume refers to the total volume scheduled for each UE regardless if using only primary- or also supplemental aggregated carriers. The measurement is optionally split into subcounters per QoS level (mapped 5QI or QCI in NR option 3) and subcounters per supported S-NSSAI, and subcounters per PLMN ID, and subcounters per BWP. In the case of per BWP, the UE data volume refers to the total volume scheduled for each Active BWP with same bandwith except UEs with activated supplemental aggregated carrier(s).

b) DER(N=1)

c) This measurement is obtained according to the following formula based on the "ThpVolDl" and "ThpTimeDl" defined below. Separate counters are maintained for each mapped 5QI (or QCI for option 3) and for each supported S-NSSAI, and for each PLMN ID , and for each Active BWP.

If , ×1000 [kbit/s]

If , 0 [kbit/s]

For small data bursts, where all buffered data is included in one initial HARQ transmission, , otherwise

ThpTimeDl	The time to transmit a data burst excluding the data transmitted in the slot when the buffer is emptied. A sample of "ThpTimeDl" for each time the DL buffer for one DataRadioBearer (DRB) is emptied.
	The point in time after T2 when data up until the second last piece of data in the transmitted data burst which emptied the RLC SDU available for transmission for the particular DRB was successfully transmitted, as acknowledged by the UE.
	The point in time when the first transmission begins after a RLC SDU becomes available for transmission, where previously no RLC SDUs were available for transmission for the particular DRB.
	The RLC level volume of a data burst, excluding the data transmitted in the slot when the buffer is emptied. A sample for ThpVolDl is the data volume, counted on RLC SDU level, in kbit successfully transmitted (acknowledged by UE) in DL for one DRB during a sample of ThpTimeDl. (It shall exclude the volume of the last piece of data emptying the buffer).

d) Each measurement is a real value representing the throughput in kbit per second. The number of measurements is equal to one. If the optional QoS level subcounter and S-NSSAI subcounter and PLMN ID subcounter and BWP subcounter measurements are performed, the number of measurements is equal to the number of mapped 5QIs and the number of supported S-NSSAIs, and the number of PLMN IDs, and the number of Active BWPs.

e) The measurement name has the form
DRB.UEThpDl, or optionally DRB.UEThpDl.QOS, where QOS identifies the target quality of service class, and DRB.UEThpDl.SNSSAI, where SNSSAI identifies the S-NSSAI, and DRB.UEThpDl.PLMN, where PLMN identifies the PLMN ID, and DRB.UEThpDl.BWP, where BWP identifies the Active BWP.

f) NRCellDU

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

5.1.1.3.2 Distribution of DL UE throughput in gNB

a) This measurement provides the distribution of the UE throughput in downlink. This measurement is intended for data bursts that are large enough to require transmissions to be split across multiple slots. The UE data volume refers to the total volume scheduled for each UE regardless if using only primary- or also supplemental aggregated carriers. The measurement is optionally split into subcounters per QoS level (mapped 5QI or QCI in NR option 3) and subcounters per supported S-NSSA, and subcounters per PLMN IDI.

b) CC

c) Considering there are n samples during measurement time T and each sample has the same time period tn, the measurement of one sample is obtained by the following formula for a measurement period tn:

If , ×1000 [kbit/s]

If , 0 [kbit/s]

For small data bursts, where all buffered data is included in one initial HARQ transmission, , otherwise

ThpTimeDl	The time to transmit a data burst excluding the data transmitted in the slot when the buffer is emptied. A sample of "ThpTimeDl" for each time the DL buffer for one DataRadioBearer (DRB) is emptied.
	The point in time after T2 when data up until the second last piece of data in the transmitted data burst which emptied the RLC SDU available for transmission for the particular DRB was successfully transmitted, as acknowledged by the UE.
	The point in time when the first transmission begins after a RLC SDU becomes available for transmission, where previously no RLC SDUs were available for transmission for the particular DRB.
	The RLC level volume of a data burst, excluding the data transmitted in the slot when the buffer is emptied. A sample for ThpVolDl is the data volume, counted on RLC SDU level, in kbit successfully transmitted (acknowledged by UE) in DL for one DRB during a sample of ThpTimeDl. (It shall exclude the volume of the last piece of data emptying the buffer).

Alternatively, for small data bursts, that are successfully transmitted in any given slot (i.e. the requirement that data bursts need to span across several slots excluding transmission of the last piece of the data in a data burst does not apply). where all buffered data is included in one initial HARQ transmission, fraction of the slot time ( may be counted and obtained by the formula:

slot	Duration of the slot
TBVol	Volume of the TB related to one slot burst
PaddingVol	Volume of padding bits added into Transport Block related to one slot burst.

For each measurement sample, the bin corresponding to the DL throughput experienced by the UE is incremented by one. Separate counters are maintained for each mapped 5QI (or QCI for option 3) and for each supported S-NSSAI.

d) A set of integers, each representing the (integer) number of samples with a DL UE throughput in the range represented by that bin. If the optional QoS level subcounter and S-NSSAI subcounter and PLMN ID subcounter measurements are performed, the number of measurements is equal to the number of mapped 5QIs and the number of supported S-NSSAIs, and the number of PLMN IDs.

e) The measurement name has the form
DRB.UEThpDlDist.Bin where Bin represents the bin, or optionally DRB.UEThpDlDist.Bin.QOS, where QOS identifies the target quality of service class, and DRB.UEThpDlDist.Bin.SNSSAI, where SNSSAI identifies the S-NSSAI, and DRB.UEThpDlDist.Bin.PLMN, where PLMN identifies the PLMN ID.

NOTE: Number of bins and the range for each bin is left to implementation

f) NRCellDU

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

5.1.1.3.3 Average UL UE throughput in gNB

a) This measurement provides the average UE throughput in uplink. This measurement is intended for data bursts that are large enough to require transmissions to be split across multiple slots. The UE data volume refers to the total volume scheduled for each UE regardless if using only primary- or also supplemental aggregated carriers. The measurement is optionally split into subcounters per QoS level (mapped 5QI or QCI in NR option 3) and subcounters per supported S-NSSAI, and subcounters per PLMN ID, and subcounters per BWP. In the case of per BWP, the UE data volume refers to the total volume scheduled for each Active BWP with same bandwith except UEs with activated supplemental aggregated carrier(s).

B) DER(N=1)

c) This measurement is obtained according to the following formula based on the "ThpVolUl" and "ThpTimeUl" defined below. Separate counters are maintained for each mapped 5QI (or QCI for option 3) and for each supported S-NSSAI, and for each PLMN ID, and for each Active BWP.

If , ×1000 [kbit/s]

If , 0 [kbit/s]

For small data bursts, where all buffered data is included in one initial HARQ transmission otherwise:

ThpTimeUl	The time to transmit a data burst excluding the data transmitted in the slot when the buffer is emptied. A sample of "ThpTimeUl" for each time the UL buffer for one DataRadioBearer (DRB) is emptied.
	The point in time when the data up until the second last piece of data in data burst has been successfully received for a particular DRB
	The point in time when transmission is started for the first data in data burst for a particular DRB.
	The RLC level volume of a data burst, excluding the data transmitted in the slot when the buffer is emptied. A sample for ThpVolUl is the data volume counted on RLC SDU level in kbit received in UL for one DRB during a sample of ThpTimeUl, (It shall exclude the volume of the last piece of data emptying the buffer).

e) The measurement name has the form
DRB.UEThpUl, or optionally DRB.UEThpUl.QOS, where QOS identifies the target quality of service class and DRB.UEThpUl.SNSSAI, where SNSSAI identifies the S-NSSAI, and DRB.UEThpUl.PLMN, where PLMN identifies the PLMN ID, and DRB.UEThpUl.BWP, where BWP identifies the Active BWP.

f) NRCellDU

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

5.1.1.3.4 Distribution of UL UE throughput in gNB

a) This measurement provides the distribution of the UE throughput in uplink. This measurement is intended for data bursts that are large enough to require transmissions to be split across multiple slots. The UE data volume refers to the total volume scheduled for each UE regardless if using only primary- or also supplemental aggregated carriers. The measurement is optionally split into subcounters per QoS level (mapped 5QI or QCI in NR option 3) and subcounters per supported S-NSSAI, and subcounters per PLMN ID.

b) CC

If , ×1000 [kbit/s]

If , 0 [kbit/s]

For small data bursts, where all buffered data is included in one initial HARQ transmission otherwise:

ThpTimeUl	The time to transmit a data burst excluding the data transmitted in the slot when the buffer is emptied. A sample of "ThpTimeUl" for each time the UL buffer for one DataRadioBearer (DRB) is emptied.
T1	The point in time when the data up until the second last piece of data in data burst has been successfully received for a particular DRB
T2	The point in time when transmission is started for the first data in data burst for a particular DRB.
ThpVolUL	The RLC level volume of a data burst, excluding the data transmitted in the slot when the buffer is emptied. A sample for ThpVolUl is the data volume counted on RLC SDU level in kbit received in UL for one DRB during a sample of ThpTimeUl, (It shall exclude the volume of the last piece of data emptying the buffer).

slot	Duration of the slot
TBVol	Volume of the TB related to one slot burst
PaddingVol	Volume of padding bits added into Transport Block related to one slot burst.

For each measurement sample, the bin corresponding to the UL throughput experienced by the UE is incremented by one. Separate counters are maintained for each mapped 5QI (or QCI for option 3) and for each supported S-NSSAI, and for each PLMN ID.

d) A set of integers, each representing the (integer) number of samples with a UL UE throughput in the range represented by that bin. If the optional QoS level subcounter and S-NSSAI subcounter and PLMN ID subcounter measurements are performed, the number of measurements is equal to the number of mapped 5QIs and the number of supported S-NSSAIs, and the number of PLMN IDs.

e) The measurement name has the form
DRB.UEThpUlDist.Bin where Bin represents the bin, or optionally DRB.UEThpUlDist.Bin.QOS, where QOS identifies the target quality of service class, and DRB.UEThpUlDist.Bin.SNSSAI, where SNSSAI identifies the S-NSSAI, and DRB.UEThpUlDist.Bin.PLMN, where PLMN identifies the PLMN ID.

NOTE: Number of bins and the range for each bin is left to implementation

f) NRCellDU

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

5.1.1.3.5 Percentage of unrestricted DL UE data volume in gNB

a) This measurement provides the percentage of DL data volume for UEs in the cell that is classified as unrestricted, i.e., when the volume is so low that all data can be transferred in one slot and no UE throughput sample could be calculated. The UE data volume refers to the total volume scheduled for each UE regardless if using only primary- or also supplemental aggregated carriers. The measurement is optionally split into subcounters per QoS level (mapped 5QI or QCI in NR option 3) and subcounters per supported S-NSSAI, and subcounters per PLMN ID.

b) SI.

c) For periods when no data is transferred at all Percentage Unrestricted Volume DL = 0, otherwise:

ThpUnresVolDl	The volume of a data burst that is transmitted in the slot when the buffer is emptied (which could be the only slot needed to transmit the data burst) and not included in the UE throughput measurement. A sample for ThpUnresVolDl is the data volume counted on RLC SDU level in kbits sent in DL for one DRB.
ThpVolDl	The volume of a data burst, excluding the data transmitted in the slot when the buffer is emptied. A sample for ThpVolDl is the data volume counted on RLC SDU level in kbits sent in DL for one DRB.

d) Each measurement is a single integer value from 0 to 100. The number of measurements is equal to one. If the optional QoS level subcounter and S-NSSAI subcounter and PLMN ID subcounter measurements are perfomed, the number of measurements is equal to the number of mapped 5QIs and the number of supported S-NSSAIs, and the number of PLMN IDs.

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

f) NRCellDU

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

5.1.1.3.6 Percentage of unrestricted UL UE data volume in gNB

a) This measurement provides the percentage of UL data volume for UEs in the cell that is classified as unrestricted, i.e., when the volume is so low that all data can be transferred in one slot and no UE throughput sample could be calculated. The UE data volume refers to the total volume scheduled for each UE regardless if using only primary- or also supplemental aggregated carriers. The measurement is optionally split into subcounters per QoS level (mapped 5QI or QCI in NR option 3) and subcounters per supported S-NSSAI, and subcounters per PLMN ID.

b) SI

c) For periods when no data is transferred at all Percentage Unrestricted Volume UL = 0, otherwise:

ThpUnresVolUl	The volume of a data burst that is transmitted in the slot when the buffer is emptied (which could be the only slot needed to transmit the data burst) and not included in the UE throughput measurement. A sample for ThpUnresVolUl is the data volume counted on RLC SDU level in kbits received in UL for one DRB.
ThpVolUl	The volume of a data burst, excluding the data transmitted in the slot when the buffer is emptied. A sample for ThpVolUl is the data volume counted on RLC SDU level in kbits received in UL for one DRB.

d) Each measurement is a single integer value from 0 to 100. The number of measurements is equal to one. If the optional QoS level subcounter and S-NSSAI subcounter and PLMN ID subcounter measurements are performed, the number of measurements is equal to the number of mapped 5QIs and the number of supported S-NSSAIs, and the number of PLMN IDs.

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

f) NRCellDU.

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

5.1.1.4 RRC connection number

5.1.1.4.1 Mean number of RRC Connections

a) This measurement provides the mean number of users in RRC connected mode for each NR cell during each granularity period. The measurement is optionally split into subcounters per PLMN ID.

b) SI.

c) This measurement is obtained by sampling at a pre-defined interval, the number of users in RRC connected mode for each NR cell and for each PLMN ID, and then taking the arithmetic mean.

d) Each measurement is a single integer value. If the optional measurement is perfomed, the number of measurements is equal to the number of supported PLMNs.

e) RRC.ConnMean, or optionally RRC.ConnMean.PLMN, where PLMN identifies the PLMN ID.

f) NRCellCU

g) Valid for packet switched traffic

h) 5GS

i) One usage of this measurement is for monitoring the number of RRC connections in connected mode during the granularity period.

5.1.1.4.2 Max number of RRC Connections

a) This measurement provides the maximum number of users in RRC connected mode for each NR cell during each granularity period. The measurement is optionally split into subcounters per PLMN ID.

b) SI.

c) This measurement is obtained by sampling at a pre-defined interval, the number of users in RRC connected mode for each NR cell and for each PLMN ID, and then taking the maximum.

d) Each measurement is a single integer value. If the optional measurement is perfomed, the number of measurements is equal to the number of supported PLMNs.

e) RRC.ConnMax, or optionally RRC.ConnMax.PLMN, where PLMN identifies the PLMN ID.

f) NRCellCU

g) Valid for packet switched traffic

h) 5GS

i) One usage of this measurement is for monitoring the number of RRC connections in connected mode during the granularity period.

5.1.1.4.3 Mean number of stored inactive RRC Connections

a) This measurement provides the mean number of users in RRC inactive mode for each NR cell during each granularity period. The measurement is optionally split into subcounters per PLMN ID.

b) SI

c) This measurement is defined according to measurement "Mean number of stored inactive UE contexts" in TS 38.314 [29]. Separate counters are optionally maintained for each PLMN ID.

d) Each measurement is a real representing the mean number. If the optional measurement is perfomed, the number of measurements is equal to the number of supported PLMNs.

e) The measurement name has the form RRC.InactiveConnMean, or optionally RRC.InactiveConnMean.PLMN, where PLMN identifies the PLMN ID.

f) NRCellCU.

g) Valid for packet switched traffic.

h) 5GS.

i) One usage of this measurement is for monitoring the memory allocation due to storage of inactive RRC connections.

5.1.1.6 Mobility Management

h) 5GS.

i) One usage of this performance measurements is for performance assurance.

5.1.1.6.1.4 Number of requested legacy handover resource allocations

a) This measurement provides the number of legacy handover resource allocation requests received by the target NR cell CU.

b) CC.

c) On receipt of HANDOVER REQUEST message (see TS 38.413 [1]) by the NR cell CU from the AMF, or receipt of HANDOVER REQUEST message (see TS 38.423 [13]) , where the message denotes a legacy handover, by the target NR cell CU from the source NR cell CU, for requesting the preparation of resources for handover.

d) A single integer value.

e) MM.HoResAlloInterReq.

f) NRCellCU.

g) Valid for packet switched traffic.

h) 5GS.

i) One usage of this performance measurements is for performance assurance.

5.1.1.6.1.5 Number of successful legacy handover resource allocations

a) This measurement provides the number of successful legacy handover resource allocations at the target NR cell CU for the handover.

b) CC.

c) On transmission of HANDOVER REQUEST ACKNOWLEDGE message (see TS 38.413 [11]) by the NR cell CU to the AMF, or transmission of HANDOVER REQUEST ACKNOWLEDGE message (see TS 38.423 [13]) , where the message corresponds to a previously received legacy handover HANDOVER REQUEST message, by the target NR cell CU to the source NR cell CU, for informing that the resources for the handover have been prepared.

d) A single integer value.

e) MM.HoResAlloInterSucc.

f) NRCellCU.

g) Valid for packet switched traffic.

h) 5GS.

i) One usage of this performance measurements is for performance assurance.

5.1.1.6.1.6 Number of failed legacy handover resource allocations

a) This measurement provides the number of failed legacy handover resource allocations at the target NR cell CU for the handover. This measurement is split into subcounters per failure cause.

b) CC.

c) On transmission of HANDOVER FAILURE message (see TS 38.413 [11]) by the NR cell CU to the AMF, or transmission of HANDOVER PREPARATION FAILURE message (see TS 38.423 [13]) , where the message corresponds to a previously sent legacy handover HANDOVER REQUEST message, by the target NR cell CU to the source NR cell CU, for informing that the preparation of resources has failed. Each transmitted HANDOVER FAILURE message or HANDOVER PREPARATION FAILURE message increments the relevant subcounter per failure cause by 1.

d) Each subcounter is an integer value.

e) MM.HoResAlloInterFail.cause.

Where cause identifies the failure cause of the legacy handover resource allocations.

f) NRCellCU.

g) Valid for packet switched traffic.

h) 5GS.

i) One usage of this performance measurements is for performance assurance.

5.1.1.6.1.7 Number of requested legacy handover executions

a) This inter gNB handover measurement provides the number of outgoing legacy handover executions requested by the source gNB.

b) CC.

c) On transmission of RRCReconfiguration message, where the message denotes a legacy handover, to the UE triggering the inter gNB legacy handover from the source NRCellCU to the target NRCellCU, indicating the attempt of an outgoing inter gNB legacy handover (see TS 38.331 [20]), the counter is stepped by 1.

d) A single integer value.

e) MM.HoExeInterReq.

f) NRCellCU;
NRCellRelation.

g) Valid for packet switched traffic.

h) 5GS.

i) One usage of this performance measurement is for performance assurance.

5.1.1.6.1.8 Number of successful legacy handover executions

a) This inter gNB handover measurement provides the number of successful legacy handover executions received by the source gNB.

b) CC.

c) On receipt at the source gNB of UE CONTEXT RELEASE [13] over Xn from the target gNB following a successful handover, where the message denotes a legacy handover, or, if handover is performed via NG, on receipt of UE CONTEXT RELEASE COMMAND [11] from AMF following a successful inter gNB handover, where the message denotes a legacy handover, the counter is stepped by 1.

d) A single integer value.

e) MM.HoExeInterSucc.

f) NRCellCU;
NRCellRelation.

g) Valid for packet switched traffic.

h) 5GS.

i) One usage of this performance measurement is for performance assurance.

5.1.1.6.1.9 Number of failed legacy handover executions

a) This inter gNB handover measurement provides the number of failed legacy handover executions for asource gNB.

b) CC.

c) This counter is incremented when handover execution failures occur. It is assumed that the UE context is available in the source gNB. The following events are counted:

1) On reception of NGAP UE CONTEXT RELEASE COMMAND [11] from AMF indicating an unsuccessful inter gNB handover;

2) On reception of RrcReestablishmentRequest [20] where the reestablishmentCause is handoverFailure, from the UE in the source gNB, where the reestablishment occurred in the source gNB;

3) On expiry of a Handover Execution supervision timer in the source gNB;

4) On reception of XnAP RETRIEVE UE CONTEXT REQUEST [13] in the source gNB, when the reestablishment occurred in another gNB.

The failure causes for UE CONTEXT RELEASE COMMAND are listed in [11] clause 9.3.1.2. An event increments the relevant subcounter by 1. For MM.HoExeInterFail.UE_CONTEXT_RELEASE_COMMAND, an event increments the relevant subcounter per failure cause by 1. ¨

As one handover failure might cause more than one of the above events, duplicates need to be filtered out.

d) Each subcounter is an integer value.

e) MM.HoExeInterFail.UeCtxtRelCmd.cause;

MM.HoExeInterFail.RrcReestabReq;

MM.HoExeInterFail.HoExeSupTimer;

MM.HoExeInterFail.RetrUeCtxtReq;

Where cause identifies the failure cause of the UE CONTEXT RELEASE COMMAND message.

f) NRCellCU;
NRCellRelation.

g) Valid for packet switched traffic.

h) 5GS.

i) One usage of this performance measurement is for performance assurance.

5.1.1.6.1.10 Mean Time of requested legacy handover executions

a) This measurement provides the mean time of inter gNB legacy handover executions during each granularity period. The measurement is split into subcounters per S-NSSAI.

b) DER(n=1).

c) This measurement is obtained by accumulating the time interval for every successful inter gNB handover executions procedure per S-NSSAI between the receipt by the source NG-RAN from the target NG-RAN of a "Release Resource" and the sending of a "N2 Path Switch Request" message from source NG-RAN to the target NG-RAN over a granularity period using DER, for legacy handovers. The end value of this time will then be divided by the number of inter gNB legacy handovers observed in the granularity period to give the arithmetic mean, the accumulator shall be reinitialised at the beginning of each granularity period.

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

e) MM.HoExeInterReq.TimeMean.SNSSAI.

f) NRCellCU.

g) Valid for packet switched traffic.

h) 5GS.

i) One usage of this measurement is for monitoring the mean time of inter gNB handovers during the granularity period.

5.1.1.6.1.11 Max Time of requested legacy handover executions

a) This measurement provides the max time of inter gNB legacy handover executions during each granularity period. The measurement is split into subcounters per S-NSSAI.

b) DER(n=1).

c) This measurement is obtained by measuring the time interval for every successful inter gNB handover executions procedure per S-NSSAI between the receipt by the source NG-RAN from the target NG-RAN of a "Release Resource" and the sending of a "N2 Path Switch Request" message from source NG-RAN to the target NG-RAN over a granularity period using DER, for legacy handovers. The high tide mark of this time will be stored in a gauge, the gauge shall be reinitialised at the beginning of each granularity period.

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

e) MM.HoExeInterReq.TimeMax.SNSSAI.

f) NRCellCU.

g) Valid for packet switched traffic.

h) 5GS.

i) One usage of this measurement is for monitoring the max time of inter gNB handovers during the granularity period.

5.1.1.6.1.12 Number of successful handover executions per beam pair

a) This inter gNB handover measurement provides the number of successful handover executions received by the source gNB per beam pair, i.e. beam in the source and beam in the target cell.

b) CC

c) On receipt at the source gNB of UE CONTEXT RELEASE [13] over Xn from the target gNB following a successful handover, or, if handover is performed via NG, on receipt of UE CONTEXT RELEASE COMMAND [11] from AMF following a successful inter gNB handover, the counter is stepped by 1.

d) A single integer value.

e) MM.HoExeInterSSBSucc

f) Beam.

g) Valid for packet switched traffic.

h) 5GS.

i) One usage of this performance measurement is for performance assurance.

5.1.1.6.1.13 Number of failed handover executions per beam pair

a) This inter gNB handover measurement provides the number of failed handover executions for source gNB per beam pair.

b) CC.

c) This counter is incremented when handover execution failures occur. It is assumed that the UE context is available in the source gNB. The following events are counted:

1) On reception at the source of NGAP UE CONTEXT RELEASE COMMAND [11] from AMF indicating an unsuccessful inter gNB handover,

2) On reception of RrcReestablishmentRequest [20] where the reestablishmentCause is handoverFailure, from the UE in the source gNB, where the reestablishment occurred in the source gNB;

3) On expiry of a Handover Execution supervision timer in the source gNB;

4) On reception of XnAP RETRIEVE UE CONTEXT REQUEST [13] in the source gNB, when the reestablishment occurred in another gNB.

The failure causes for NGAP UE CONTEXT RELEASE COMMAND are listed in [11]. An event increments the relevant subcounter by 1. For MM.HoExeInterSSBFail.UeCtxtRelCmd, an event increments the relevant subcounter per failure cause by 1.

As one handover failure might cause more than one of the above events, duplicates need to be filtered out.

Editor’s note: FFS how the beam pair is identified

d) Each subcounter is an integer value.

e) MM.HoExeInterSSBFail.UeCtxtRelCmd.cause;

a) This measurement provides the number of failed preparations received by the source gNB for the outgoing handovers from 5GS to EPS. This measurement is split into subcounters per failure cause.

b) CC

c) Receipt of HANDOVER PREPARATION FAILURE message (see TS 38.413 [11]) by the gNB-CU from the AMF, for informing that the preparation of resources have been failed at the target E-Utran Cell for the handover from 5GS and EPS. Each received HANDOVER PREPARATION FAILURE message increments the relevant subcounter per failure cause by 1.

d) Each subcounter is an integer value.

e) MM.HoOut5gsToEpsPrepFail.cause

Where cause identifies the failure cause of the handover preparations.

f) EutranRelation (contained by NRCellCU),
NRCellCU.

g) Valid for packet switched traffic.

h) 5GS.

5.1.1.6.3.4 Number of requested resource allocations for handovers from EPS to 5GS

a) This measurement provides the number of resource allocation requests received by the target gNB for handovers from EPS to 5GS.

b) CC

c) Receipt of HANDOVER REQUEST message containing the "Handover Type" IE set to "EPSto5GS" (see TS 38.413 [11]) by the gNB-CU from the AMF.

d) A single integer value.

e) MM.HoIncEpsTo5gsResAlloReq.

f) EutranRelation (contained by NRCellCU),
NRCellCU.

g) Valid for packet switched traffic.

h) 5GS.

5.1.1.6.3.5 Number of successful resource allocations for handovers from EPS to 5GS

a) This measurement provides the number of successful resource allocations at the target gNB for handovers from EPS to 5GS.

b) CC.

c) Transmission of HANDOVER REQUEST ACKNOWLEDGE message (see TS 38.413 [11]) by the gNB-CU to the AMF, for informing that the resources for the handover from EPS to 5GS have been allocated.

d) A single integer value.

e) MM.HoIncEpsTo5gsResAlloSucc.

f) EutranRelation (contained by NRCellCU),
NRCellCU.

g) Valid for packet switched traffic.

h) 5GS.

i) One usage of this performance measurements is for performance assurance.

5.1.1.6.3.6 Number of failed resource allocations for handovers from EPS to 5GS

a) This measurement provides the number of failed resource allocations at the target gNB for handovers from EPS to 5GS. This measurement is split into subcounters per failure cause.

b) CC

c) Transmission of HANDOVER FAILURE message (see TS 38.413 [11]) by the gNB-CU to the AMF, for informing that the allocation of resources for the handover from EPS to 5GS has failed. Each transmitted HANDOVER FAILURE message increments the relevant subcounter per failure cause by 1.

d) Each subcounter is an integer value.

e) MM.HoIncEpsTo5gsResAlloFail.cause

Where cause identifies the failure cause of the handover resource allocations.

f) EutranRelation (contained by NRCellCU),
NRCellCU.

g) Valid for packet switched traffic.

h) 5GS

5.1.1.6.3.7 Number of requested executions for handovers from 5GS to EPS

a) This measurement provides the number of executions requested by the source gNB for handovers from 5GS to EPS.

b) CC.

c) Transmission of MobilityFromNRCommand message to the UE triggering the handover from the source NR Cell to the target E-UTRAN cell for the handover from 5GS to EPS (see TS 38.331 [20]).

d) A single integer value.

e) MM.HoOutExe5gsToEpsReq.

f) EutranRelation (contained by NRCellCU),
NRCellCU.

g) Valid for packet switched traffic.

h) 5GS.

5.1.1.6.3.8 Number of successful executions for handovers from 5GS to EPS

a) This measurement provides the number of successful executions at the source gNB for handovers from 5GS to EPS.

b) CC

c) Receipt of UE CONTEXT RELEASE COMMAND message by the gNB-CU from AMF (see TS 38.413 [11]) following a successful handover from 5GS to EPS.

d) A single integer value.

e) MM.HoOutExe5gsToEpsSucc.

f) EutranRelation (contained by NRCellCU),
NRCellCU.

g) Valid for packet switched traffic.

h) 5GS.

5.1.1.6.3.9 Number of failed executions for handovers from 5GS to EPS

a) This measurement provides the number of failed executions at the source gNB for handovers from 5GS to EPS. This measurement is split into subcounters per failure cause.

b) CC

c) Receipt of UE CONTEXT RELEASE COMMAND at the source gNB-CU from AMF (see TS 38.413 [11]) indicating an unsuccessful handover from 5GS to EPS. Each received message increments the relevant subcounter per failure cause by 1.

d) Each subcounter is an integer value.

e) MM.HoOutExe5gsToEpsFail.cause.

Where cause identifies the failure cause in the UE CONTEXT RELEASE COMMAND message.

f) EutranRelation (contained by NRCellCU),
NRCellCU.

g) Valid for packet switched traffic.

h) 5GS.

5.1.1.6.3.10 Number of requested preparations for EPS fallback handovers

a) This measurement provides the number of EPS fallback preparations requested by the source gNB for the outgoing handovers from 5GS to EPS.

b) CC

c) Transmission of HANDOVER REQUIRED message containing the "Handover Type" IE set to "5GStoEPS" by the gNB-CU to the AMF after the source gNodeB sends the AMF a PDU Session modification response in which "PDUSessionResourceModifyUnsuccessfulTransfer" carries the failure cause "IMS voice EPS fallback or RAT fallback triggered" (see TS 38.413 [11]) .

d) A single integer value.

e) MM.HoOut5gsToEpsFallbackPrepReq.

f) NRCellCU.

g) Valid for packet switched traffic.

h) 5GS.

5.1.1.6.3.11 Number of successful preparations for EPS fallback handovers

a) This measurement provides the number of successful EPS fallback preparations received by the source gNB for the outgoing handovers from 5GS to EPS.

b) CC

c) Receipt of HANDOVER COMMAND message by the gNB-CU from the AMF,after the source gNodeB sends the AMF a PDU Session modification response in which "PDUSessionResourceModifyUnsuccessfulTransfer" carries the failure cause "IMS voice EPS fallback or RAT fallback triggered" (see TS 38.413 [11]), for informing that the resources have been successfully prepared at the target E-Utran Cell for the EPS fallback handover from 5GS and EPS (see TS 38.413 [11]).

d) A single integer value.

e) MM.HoOut5gsToEpsFallbackPrepSucc.

f) NRCellCU.

g) Valid for packet switched traffic.

h) 5GS.

5.1.1.6.3.12 Number of failed preparations for EPS fallback handovers

a) This measurement provides the number of failed preparations received by the source gNB for the outgoing handovers from 5GS to EPS. This measurement is split into subcounters per failure cause.

b) CC

c) Receipt of HANDOVER PREPARATION FAILURE message by the gNB-CU from the AMF after the source gNodeB sends the AMF a PDU Session modification response in which "PDUSessionResourceModifyUnsuccessfulTransfer" carries the failure cause "IMS voice EPS fallback or RAT fallback triggered", for informing that the preparation of resources have been failed at the target E-Utran Cell for the handover from 5GS and EPS. Each received HANDOVER PREPARATION FAILURE message increments the relevant subcounter per failure cause by 1 (see TS 38.413 [11]).

d) Each subcounter is an integer value.

e) MM.HoOut5gsToEpsFallbackPrepFail.cause

Where cause identifies the failure cause of the handover preparations.

f) NRCellCU.

g) Valid for packet switched traffic.

h) 5GS.

5.1.1.6.3.13 Number of successful executions for EPS fallback handovers

a) This measurement provides the number of successful EPS fallback executions at the source gNB for handovers from 5GS to EPS.

b) CC

c) Receipt of UE CONTEXT RELEASE COMMAND message by the gNB-CU from AMF following a successful handover from 5GS to EPS,after the source gNodeB sends the AMF a PDU Session modification response in which "PDUSessionResourceModifyUnsuccessfulTransfer" carries the failure cause "IMS voice EPS fallback or RAT fallback triggered"(see TS 38.413 [11]).

d) A single integer value.

e) MM.HoOutExe5gsToEpsFallbackSucc.

f) NRCellCU.

g) Valid for packet switched traffic.

h) 5GS.

5.1.1.6.3.14 Number of failed executions for EPS fallback handovers

a) This measurement provides the number of failed EPS fallback executions at the source gNB for handovers from 5GS to EPS. This measurement is split into subcounters per failure cause.

b) CC

c) Receipt of UE CONTEXT RELEASE COMMAND at the source gNB-CU from AMF indicating an unsuccessful handover from 5GS to EPS,after the source gNodeB sends the AMF a PDU Session modification response in which "PDUSessionResourceModifyUnsuccessfulTransfer" carries the failure cause "IMS voice EPS fallback or RAT fallback triggered". Each received message increments the relevant subcounter per failure cause by 1 (see TS 38.413 [11]).

d) Each subcounter is an integer value.

e) MM.HoOutExe5gsToEpsFallbackFail.cause.

Where cause identifies the failure cause in the UE CONTEXT RELEASE COMMAND message.

f) NRCellCU.

g) Valid for packet switched traffic.

h) 5GS.

5.1.1.6.3.15 Mean Time of EPS fallback handover

a) This measurement provides the mean time of EPS fallback whole handover during each granularity period.

b) DER (n=1)

c) This measurement is obtained by accumulating the time interval for every successful EPS fallback handover procedure between the receipt by the NG-RAN from the EPS of a "UE CONTEXT RELEASE COMMAND" and the sending of a "HANDOVER REQUIRED" message from NG-RAN to the EPS over a granularity period using DER. The end value of this time will then be divided by the number of EPS fallback handovers observed in the granularity period to give the arithmetic mean, the accumulator shall be reinitialised at the beginning of each granularity period.

d) A single integer value (in milliseconds)

e) MM.Ho5gsToEpsFallbackTimeMean.

f) NRCellCU.

g) Valid for packet switched traffic

h) 5GS

i) One usage of this measurement is for monitoring the mean time of EPS fallback handovers during the granularity period.

5.1.1.6.3.16 Mean Time of EPS fallback handover executions

a) This measurement provides the mean time of EPS fallback handover executions during each granularity period.

b) DER (n=1)

c) This measurement is obtained by accumulating the time interval for every successful EPS fallback handover executions procedure between the receipt by the NG-RAN from the EPS of a "UE CONTEXT RELEASE COMMAND" and the sending of the MobilityFromNRCommand message to the UE over a granularity period using DER. The end value of this time will then be divided by the number of EPS fallback handovers observed in the granularity period to give the arithmetic mean, the accumulator shall be reinitialised at the beginning of each granularity period.

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

e) MM.HoExeHo5gsToEpsFallbackTimeMean.

f) NRCellCU.

g) Valid for packet switched traffic

h) 5GS

i) One usage of this measurement is for monitoring the mean time of EPS fallback handover executions during the granularity period.

5.1.1.6.4 RRC redirection measurement

5.1.1.6.4.1 number of EPS fallback redirection

a) This measurement provides the number of RRC release for EPS fallback redirection.

b) SI

c) Transmission of a "RRCRelease" message to UE, which contains "redirectedCarrierInfo" IE and "voiceFallbackIndication" IE indication EPS fallback for IMS voice. (see TS 38.331 [20]).

d) A single integer value.

e) MM.Redirection.5gsToEpsFallback.

f) NRCellDU

g) Valid for packet switched traffic

h) 5GS

5.1.1.6.5 Intra/Inter-frequency Handover related measurements

5.1.1.6.5.1 Number of requested intra-frequency handover executions

a) This measurement provides the number of outgoing intra-frequency handover executions requested by the source NRCellCU.

b) CC.

c) On transmission of RRCReconfiguration message to the UE triggering the handover from the source NRCellCU to the target NRCellCU, indicating the attempt of an outgoing intra-frequency handover (see TS 38.331 [20]), the counter is steped by 1.

d) A single integer value.

e) MM.HoExeIntraFreqReq.

f) NRCellCU

g) Valid for packet switched traffic.

h) 5GS.

i) One usage of this performance measurement is for performance assurance.

5.1.1.6.5.2 Number of successful intra-frequency handover executions

a) This measurement provides the number of successful intra-frequency handover executions received by the source NRCellCU.

b) CC.

c) On reception of RRCReconfigurationComplete message from the UE to the target NRCellCU indicating a successful intra-frequency intra gNB handover (see TS 38.331 [20]), or, on reception of UE CONTEXT RELEASE [13] over Xn from the target gNB following a successful intra-frequency inter gNB handover, or, if handover is performed via NG, on reception of UE CONTEXT RELEASE COMMAND [11] from AMF following a successful intra-frequency inter gNB handover, the counter is stepped by 1.

d) A single integer value.

e) MM.HoExeIntraFreqSucc.

f) NRCellCU.

g) Valid for packet switched traffic.

h) 5GS.

i) One usage of this performance measurement is for performance assurance.

5.1.1.6.5.3 Number of requested inter-frequency handover executions

a) This measurement provides the number of outgoing inter-frequency handover executions requested by the source NRCellCU.

b) CC.

c) On transmission of RRCReconfiguration message to the UE triggering the handover from the source NRCellCU to the target NRCellCU, indicating the attempt of an outgoing inter-frequency handover (see TS 38.331 [20]), the counter is steped by 1.

d) A single integer value.

e) MM.HoExeInterFreqReq.

f) NRCellCU

g) Valid for packet switched traffic.

h) 5GS.

i) One usage of this performance measurement is for performance assurance.

5.1.1.6.5.4 Number of successful inter-frequency handover executions

a) This measurement provides the number of successful inter-frequency handover executions received by the source NRCellCU.

b) CC.

c) On reception of RRCReconfigurationComplete message from the UE to the target NRCellCU indicating a successful inter-frequency intra gNB handover (see TS 38.331 [20]), or, on reception of UE CONTEXT RELEASE [13] over Xn from the target gNB following a successful inter-frequency inter gNB handover, or, if handover is performed via NG, on reception of UE CONTEXT RELEASE COMMAND [11] from AMF following a successful inter-frequency inter gNB handover, the counter is stepped by 1.

d) A single integer value.

e) MM.HoExeInterFreqSucc.

f) NRCellCU.

g) Valid for packet switched traffic.

h) 5GS.

i) One usage of this performance measurement is for performance assurance.

h) 5GS

i) One usage of this performance measurements is for performance assurance

5.1.1.6.6.4 Number of requested conditional handover resource allocations

a) This measurement provides the number of conditional handover resource allocation requests received by the target NR cell CU.

b) CC

c) On receipt of HANDOVER REQUEST message (see TS 38.423 [13] clause 8.2.1), where the message denotes a conditional handover, by the target NR cell CU from the source NR cell CU, for requesting the preparation of resources for handover.

d) A single integer value.

e) MM.ChoResAlloInterReq

f) NRCellCU

g) Valid for packet switched traffic.

h) 5GS.

i) One usage of this performance measurements is for performance assurance.

5.1.1.6.6.5 Number of successful conditional handover resource allocations

a) This measurement provides the number of successful conditional handover resource allocations at the target NR cell CU for the handover.

b) CC.

c) On transmission of HANDOVER REQUEST ACKNOWLEDGE message (see TS 38.423 [13] clause 8.2.1), where the message corresponds to a previously received conditional handover HANDOVER REQUEST message, by the target NR cell CU to the source NR cell CU, for informing that the resources for the handover have been prepared.

d) A single integer value.

e) MM.ChoResAlloInterSucc

f) NRCellCU

g) Valid for packet switched traffic.

h) 5GS.

i) One usage of this performance measurements is for performance assurance.

5.1.1.6.6.6 Number of failed conditional handover resource allocations

a) This measurement provides the number of failed conditional handover resource allocations at the target NR cell CU for the handover. This measurement is split into subcounters per failure cause.

b) CC

c) On transmission of HANDOVER PREPARATION FAILURE message (see TS 38.423 [13] clause 8..2.1.3), where the message corresponds to a previously sent conditional handover HANDOVER REQUEST message, by the target NR cell CU to the source NR cell CU, for informing that the preparation of resources has failed. Each HANDOVER PREPARATION FAILURE message increments the relevant subcounter per failure cause by 1.

d) Each subcounter is an integer value.

e) MM.ChoResAlloInterFail.cause

Where cause identifies the failure cause of the conditional handover resource allocations.

f) NRCellCU

g) Valid for packet switched traffic.

h) 5GS

i) One usage of this performance measurements is for performance assurance.

5.1.1.6.6.7 Number of configured conditional handover candidates

a) This inter gNB handover measurement provides the number of outgoing conditional handover candidates requested by the source gNB.

b) CC.

c) On transmission of RRCReconfiguration message (TS 38.331 [20] clause 5.3.5), where the message denotes a conditional handover configuration, to the UE configuring an inter-gNB conditional handover from the source NRCellCU to the target NRCellCU. The counter on NRCellCU is incremented by the number of candidates configured in the conditionalReconfiguration IE. The counter on NRCellRelation is incremented by 1 for each relation that is present in the conditionalReconfiguration IE.

d) A single integer value.

e) MM.ConfigInterReqCho

f) NRCellCU
NRCellRelation

g) Valid for packet switched traffic.

h) 5GS.

i) One usage of this performance measurement is for performance assurance.

5.1.1.6.6.8 Number of UEs configured with conditional handover.

a) This inter-gNB handover measurement provides the number of UEs that has been configured with conditional handover by the source gNB.

b) CC.

c) On transmission of RRCReconfiguration message (TS 38.331 [20] clause 5.3.5), where the message denotes a conditional handover configuration, to the UE configured with an inter-gNB conditional handover from the source NRCellCU to the target NRCellCU, the counter is stepped by 1. The counter shall only be stepped by 1 even is several configurations are sent to the UE during a cell dwelling time.

d) A single integer value.

e) MM.ConfigInterReqChoUes

f) NRCellCU

g) Valid for packet switched traffic.

h) 5GS.

i) One usage of this performance measurement is for performance assurance.

5.1.1.6.6.9 Number of successful conditional handover executions

a) This inter-gNB handover measurement provides the number of successful conditional handover executions received by the source gNB.

b) CC

c) On receipt at the source gNB of UE CONTEXT RELEASE (TS 38.423 [13] clause 8.2.7) over Xn from the target gNB following a successful inter-gNB conditional handover, the counter is stepped by 1.

d) A single integer value.

e) MM.ChoExeInterSucc

f) NRCellCU
NRCellRelation

g) Valid for packet switched traffic.

h) 5GS.

i) One usage of this performance measurement is for performance assurance.

5.1.1.6.6.10 Void

5.1.1.6.6.11 Mean Time of requested conditional handover executions

a) This measurement provides the mean time of inter-gNB conditional handover executions during each granularity period. The measurement is split into subcounters per S-NSSAI.

b) DER(n=1)

c) This measurement is obtained by accumulating the time interval for every successful Inter-gNB handover executions procedure per S-NSSAI between the receipt by the Source NG-RAN from the Target NG-RAN of a "Release Resource" and the sending of a "N2 Path Switch Request" message from Source NG-RAN to the Target NG-RAN over a granularity period using DER, for conditional handovers. The end value of this time will then be divided by the number of inter-gNB conditional handovers observed in the granularity period to give the arithmetic mean, the accumulator shall be reinitialised at the beginning of each granularity period.

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

e) MM.ChoExeInterReq.TimeMean.SNSSAI

f) NRCellCU

g) Valid for packet switched traffic

h) 5GS

i) One usage of this measurement is for monitoring the mean time of Inter-gNB handovers during the granularity period.

5.1.1.6.6.12 Max Time of requested conditional handover executions

a) This measurement provides the max time of inter-gNB conditional handover executions during each granularity period. The measurement is split into subcounters per S-NSSAI.

b) DER(n=1)

c) This measurement is obtained by measuring the time interval for every successful Inter-gNB handover executions procedure per S-NSSAI between the receipt by the source NG-RAN from the target NG-RAN of a "Release Resource" and the sending of a "N2 Path Switch Request" message from Source NG-RAN to the Target NG-RAN over a granularity period using DER, for conditional handovers. The high tide mark of this time will be stored in a gauge, the gauge shall be reinitialised at the beginning of each granularity period.

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

e) MM.ChoExeInterReq.TimeMax.SNSSAI

f) NRCellCU

g) Valid for packet switched traffic

h) 5GS

i) One usage of this measurement is for monitoring the mean time of Inter-gNB handovers during the granularity period.

5.1.1.6.6.13 Number of UEs for which conditional handover preparations are requested

a) This measurement provides the number of UEs for which conditional handover preparations were requested by the source gNB.

b) CC.

d) A single integer value.

e) MM.ChoPrepInterReqUes.

f) NRCellCU.

g) Valid for packet switched traffic.

h) 5GS.

i) One usage of this performance measurements is for performance assurance.

h) 5GS.

i) One usage of this performance measurements is for performance assurance.

5.1.1.6.8.4 Number of requested DAPS handover resource allocations

a) This measurement provides the number of DAPS handover resource allocation requests received by the target NR cell CU.

b) 1CC

c) On receipt of HANDOVER REQUEST message (see TS 38.413 [1]) by the NR cell CU from the AMF, or receipt of HANDOVER REQUEST message (see TS 38.423 [13]) by the target NR cell CU], where the message denotes a DAPS handover, from the source NR cell CU, for requesting the preparation of resources for handover.

d) A single integer value.

e) MM.DapsHoResAlloInterReq.

f) NRCellCU.

g) Valid for packet switched traffic.

h) 5GS.

i) One usage of this performance measurements is for performance assurance.

5.1.1.6.8.5 Number of successful DAPS handover resource allocations

a) This measurement provides the number of successful DAPS handover resource allocations at the target NR cell CU for the handover.

b) CC.

c) On transmission of HANDOVER REQUEST ACKNOWLEDGE message (see TS 38.413 [11]) by the NR cell CU to the AMF, or transmission of HANDOVER REQUEST ACKNOWLEDGE message (see TS 38.423 [13]) by the target NR cell CU to the source NR cell CU, where the message denotes a DAPS handover, for informing that the resources for the handover have been prepared.

d) A single integer value.

e) MM.DapsHoResAlloInterSucc

f) NRCellCU.

g) Valid for packet switched traffic.

h) 5GS.

i) One usage of this performance measurements is for performance assurance.

5.1.1.6.8.6 Number of failed DAPS handover resource allocations

a) This measurement provides the number of failed DAPS handover resource allocations at the target NR cell CU for the handover. This measurement is split into subcounters per failure cause.

b) CC

c) On transmission of HANDOVER FAILURE message (see TS 38.413 [11]) by the NR cell CU to the AMF, or transmission of HANDOVER PREPARATION FAILURE message (see TS 38.423 [13]) by the target NR cell CU to the source NR cell CU, where the message denotes a DAPS handover, for informing that the preparation of resources has failed. Each transmitted HANDOVER FAILURE message or HANDOVER PREPARATION FAILURE message increments the relevant subcounter per failure cause by 1.

d) Each subcounter is an integer value.

e) MM.DapsHoResAlloInterFail.cause

Where cause identifies the failure cause of the handover resource allocations.

f) NRCellCU

g) Valid for packet switched traffic.

h) 5GS

i) One usage of this performance measurements is for performance assurance.

5.1.1.6.8.7 Number of requested DAPS handover executions

a) This inter gNB handover measurement provides the number of outgoing DAPS handover executions requested by the source gNB.

b) CC.

c) On transmission of RRCReconfiguration message to the UE triggering the inter gNB handover from the source NRCellCU to the target NRCellCU, indicating the attempt of an outgoing inter-gNB DAPS handover (see TS 38.331 [20]), the counter is stepped by 1.

d) A single integer value.

e) MM.DapsHoExeInterReq.

f) NRCellCU,
NRCellRelation.

g) Valid for packet switched traffic.

h) 5GS.

i) One usage of this performance measurement is for performance assurance.

5.1.1.6.8.8 Number of successful DAPS handover executions

a) This inter gNB handover measurement provides the number of successful DAPS handover executions received by the source gNB.

b) CC

c) On receipt at the source gNB of UE CONTEXT RELEASE [13] over Xn from the target gNB following a successful DAPS handover, or, if handover is performed via NG, on receipt of UE CONTEXT RELEASE COMMAND [11] from AMF following a successful inter gNB DAPS handover, the counter is stepped by 1.

d) A single integer value.

e) MM.DapsHoExeInterSucc.

f) NRCellCU,
NRCellRelation.

g) Valid for packet switched traffic.

h) 5GS.

i) One usage of this performance measurement is for performance assurance.

5.1.1.6.8.9 Number of failed DAPS handover executions

a) This inter gNB handover measurement provides the number of failed DAPS handover executions.

b) CC.

c) This counter is incremented when handover execution failures occur. It is assumed that the UE context is available in the source gNB. The following events are counted:

1) On reception of NGAP UE CONTEXT RELEASE COMMAND [11] from AMF indicating an unsuccessful inter gNB DAPS handover;

2) On reception of RrcReestablishmentRequest [20] where the reestablishmentCause is handoverFailure, from the UE in the source gNB, where the reestablishment occurred in the source gNB, for a DAPS handover;

3) On expiry of a Handover Execution supervision timer in the source gNB for a DAPS handover;

4) On reception of XnAP RETRIEVE UE CONTEXT REQUEST [13] in the source gNB, for a DAPS handover, when the reestablishment occurred in another gNB;

5) On reception of FailureInformation [20] where failureType-r16 is set to daps-failure.

The failure causes for UE CONTEXT RELEASE COMMAND are listed in [11] clause 9.3.1.2. An event increments the relevant subcounter by 1. For MM.DapsHoExeInterFail.UE_CONTEXT_RELEASE_COMMAND, an event increments the relevant subcounter per failure cause by 1.

5.1.1.7.1 Total number of DL initial TBs

a) This measurement provides the total number of initial TBs transmitted on the downlink in a cell. HARQ re-transmissions are excluded from this measurement.This measurement is optionally split into subcounters per modulation schema.

b) CC.

c) On transmission by the gNB of TB to UE during the period of measurement.This measurement is optionally split into subcounters per modulation schema.

d) A single integer value.

e) The measurement name has the form TB.TotNbrDlInitial, TB.TotNbrDlInitial.Qpsk, TB.TotNbrDlInitial.16Qam.

TB.TotNbrDlInitial.64Qam, TB.TotNbrDlInitial.256Qam.

f) NRCellDU.

g) Valid for packet switched traffic .

h) 5GS.

5.1.1.7.2 Intial error number of DL TBs

a) This measurement provides the number of initial faulty TBs transmitted on the downlink in a cell.This measurement is optionally split into subcounters per modulation schema.

b) CC.

c) On receipt by the gNB of a NACK or DTX from UE which indicates a faulty reception of TB by UE at first HARQ feedback during the period of measurement. This measurement is optionally split into subcounters per modulation schema.

d) A single integer value.

e) The measurement name has the form TB.IntialErrNbrDl, TB.IntialErrNbrDl.Qpsk, TB.IntialErrNbrDl.16Qam

TB.IntialErrNbrDl.64Qam, TB.IntialErrNbrDl.256Qam.

f) NRCellDU.

g) Valid for packet switched traffic .

h) 5GS.

5.1.1.7.3 Total number of DL TBs

a) This measurement provides the total number of TBs transmitted on the downlink in a cell.The measurement is split into subcounters per layer at MU-MIMO case. This measurement includes all transmitted TBs (including the successful and failed TBs during initial transmission and HARQ re-transmission).

b) CC.

c) On transmission by the gNB of TB to UE during the period of measurement.The measurement is split into subcounters per Layer at MU-MIMO case.A single integer value. .

d) Each measurement is an integer.

e) TB.TotNbrDl.X

Where X identified by DL MU-MIMO maximum layer.

f) NRCellDU.

g) Valid for packet switched traffic .

h) 5GS.

5.1.1.7.4 Total error number of DL TBs

a) This measurement provides the number of total faulty TBs transmitted on the downlink in a cell .The measurement is split into subcounters per layer at MU-MIMO case.This measurement include all transmitted faulty TBs of initial transmission and re-transmission .

b) CC.

c) On receipt by the gNB of a NACK or DTX from UE which indicates a faulty reception of TB by UE during the period of measurement. The measurement is split into subcounters per Layer at MU-MIMO case.

d) Each measurement is an integer.

e) TB.ErrToltalNbrDl.X.

Where X identified by DL MU-MIMO maximum layer.

f) NRCellDU.

g) Valid for packet switched traffic .

h) 5GS.

5.1.1.7.5 Residual error number of DL TBs

a) This measurement provides the number of final faulty TBs transmitted on the downlink in a cell at last HARQ re-transmissions.

b) CC.

c) On receipt by the gNB of a NACK or DTX from UE which indicates a faulty reception of TB by UE at the last HARQ feedback during the period of measurement.

d) A single integer value.

e) TB.ResidualErrNbrDl.

f) NRCellDU.

g) Valid for packet switched traffic

h) 5GS.

5.1.1.7.6 Total number of UL initial TBs

a) This measurement provides the total number of initial TBs on the uplink in a cell.This measurement is optionally split into subcounters per modulation schema.

b) CC

c) On receipt by the gNB of TB from UE during the period of measurement.This measurement is optionally split into subcounters per modulation schema.

d) A single integer value.

e) The measurement name has the form TB.TotNbrUlInit, TB.TotNbrUlInit.Qpsk, TB.TotNbrUlInit.16Qam,

f) TB.TotNbrUlInit.64Qam, TB.TotNbrUlInit.256Qam.

g) NRCellDU.

h) Valid for packet switched traffic .

i) 5GS.

5.1.1.7.7 Error number of UL initial TBs

a) This measurement provides the number of initial faulty TBs on the uplink in a cell. This measurement is optionally split into subcounters per modulation schema.

b) CC

c) On receipt by the gNB of a initial TB on which CRC fails or DTX from UE during the period of measurement.This measurement is optionally split into subcounters per modulation schema.

d) A single integer value.

e) The measurement name has the form TB.ErrNbrUlInitial, TB.ErrNbrUlInitial.Qpsk, TB.ErrNbrUlInitial.16Qam

TB.ErrNbrUlInitial.64Qam, TB.ErrNbrUlInitial.256Qam.

f) NRCellDU.

g) Valid for packet switched traffic .

h) 5GS.

5.1.1.7.8 Total number of UL TBs

a) This measurement provides the total number of TBs on the uplink in a cell.The measurement is split into subcounters per layer at MU-MIMO case.This measurement includes all transmitted TBs (including the successful and failed TBs during initial transmission and HARQ re-transmission).

b) CC

c) On receipt by the gNB of TB from UE during the period of measurement.The measurement is split into subcounters per Layer at MU-MIMO case.A single integer value. The sum value identified by the .sum suffix.

d) Each measurement is an integer.

e) TB.TotNbrUl.X

Where X identified by UL MU-MIMO maximum layer.

f) NRCellDU.

g) Valid for packet switched traffic.

h) 5GS.

5.1.1.7.9 Total error number of UL TBs

a) This measurement provides the number of total faulty TBs on the uplink in a cell. The measurement is split into subcounters per layer at MU-MIMO case.This measurement include all transmitted faulty TBs of initial and re-transmission .

b) CC

c) On receipt by the gNB of a TB on which CRC fails or DTX from UE during the period of measurement. The measurement is split into subcounters per Layer at MU-MIMO case.A single integer value.

d) Each measurement is an integer.

e) TB.ErrToltalNbrUl.X

Where X identified by UL MU-MIMO maximum layer.

f) NRCellDU.

g) Valid for packet switched traffic.

h) 5GS.

5.1.1.7.10 Residual error number of UL TBs

a) This measurement provides the number of final faulty TBs on the uplink in a cell.

b) CC

c) On receipt by the gNB of a TB on which CRC fails or DTX at last HARQ re-transmissions from UE during the period of measurement.

d) A single integer value.

e) TB.ResidualErrNbrUl .

f) NRCellDU.

g) Valid for packet switched traffic.

h) 5GS.

5.1.1.8 Void

5.1.1.9 Void

5.1.1.10 DRB related measurements

5.1.1.10.1 Number of DRBs attempted to setup

a) This measurement provides the number of DRBs attempted to setup to support all requested QoS flows in the PDU sessions to be setup by the INITIAL CONTEXT SETUP REQUESTs, PDU SESSION RESOURCE SETUP REQUESTs and PDU SESSION RESOURCE MODIFY REQUEST message received by the gNB from AMF. This measurement is split into subcounters per mapped 5QI and per S-NSSAI.

b) CC.

c) On receipt of "PDU Session Resource Setup Request List" IE in a INITIAL CONTEXT SETUP REQUEST message, PDU SESSION RESOURCE SETUP REQUEST message (see TS 38.413 [11]) or a by the PDU SESSION RESOURCE MODIFY REQUEST message to gNB from the AMF. Each DRB that is needed to setup in the transmitted RRCReconfiguration message increments the relevant subcounter per mapped 5QI by 1, and the relevant subcounter per S-NSSAI by 1. Any DRBs attempted to setup to support all requested QoS flows in the PDU SESSION RESOURCE SETUP REQUEST messages with same PDU Session IDs as an existing PDU Session are excluded.

d) Each subcounter is an integer value.

e) DRB.EstabAtt.5QI, where 5QI identifies mapped 5QI and

DRB.EstabAtt.SNSSAI, where SNSSAI identifies the S-NSSAI.

f) NRCellCU.

g) Valid for packet switched traffic.

h) 5GS.

i) One usage of this performance measurements is for performance assurance.

5.1.1.10.2 Number of DRBs successfully setup

a) This measurement provides the number of DRBs successfully setup to support all requested QoS flows in the PDU sessions to be setup by the INITIAL CONTEXT SETUP REQUESTs, PDU SESSION RESOURCE SETUP REQUESTs and PDU SESSION RESOURCE MODIFY REQUEST message received by the gNB from AMF. This measurement is split into subcounters per mapped 5QI and per S-NSSAI.

b) CC.

c) On transmission of INITIAL CONTEXT SETUP RESPONSE, PDU SESSION RESOURCE SETUP RESPONSE message containing the "PDU Session Resource Setup Response List" IE (see TS 38.413 [11]) or by the PDU SESSION RESOURCE MODIFY REQUEST message from the gNB to the AMF.The counter increases by the number of DRBs that was successfully setup indicated by the RRCReconfigurationComplete message from the UE, as the response to the transmitted RRCReconfiguration message that contains the DRBs to add (see TS 38.331[20]). Each DRB that was successfully setup to the UE increments the relevant subcounter per mapped 5QI by 1, and the relevant subcounter per S-NSSAI by 1.

d) Each subcounter is an integer value.

e) DRB.EstabSucc.5QI, where 5QI identifies mapped 5QI and

DRB.EstabSucc.SNSSAI, where SNSSAI identifies the S-NSSAI.

f) NRCellCU.

g) Valid for packet switched traffic.

h) 5GS.

i) One usage of this performance measurements is for performance assurance.

5.1.1.10.3 Number of released active DRBs

a) This measurement provides the number of abnormally released DRBs that were active at the time of release. DRBs with bursty flow are seen as being active if there is user data in the PDCP queue in any of the directions or if any DRB data on a Data Radio Bearer (UL or DL) has been transferred during the last 100 ms. DRBs with continuous flow are seen as active DRBs in the context of this measurement, as long as the UE is in RRC connected state. DRBs used in 3GPP option 3 shall not be covered in this measurement
The measurement is split into sub counters per mapped 5QI and per S-NSSAI.

b) CC

c) On

– transmission by the NG-RAN of a PDU SESSION RESOURCE RELEASE RESPONSE message for the PDU release initiated by the AMF with the exception of corresponding PDU SESSION RESOURCE RELEASE COMMAND message with "Cause" equal to "Normal Release" or "User inactivity", "Load balancing TAU required", "Release due to CN-detected mobility", "O&M intervention", or-

– transmission by the NG-RAN of a PDU SESSION RESOURCE MODIFY RESPONSE message for the PDU modification initiated by the AMF with the exception of corresponding PDU SESSION RESOURCE MODIFY REQUEST message with the "Cause" equal to "Normal Release", or

– transmission by the NG-RAN of a UE CONTEXT RELEASE COMPLETE for the UE context release initiated by the NG-RAN with the exception of the corresponding UE CONTEXT RELEASE REQUEST message with the cause equal to "Normal Release" or "User inactivity", "Partial handover", "Successful handover", or

– transmission by the NG-RAN of a UE CONTEXT RELEASE COMPLETE message for the UE context release initiated by the AMF with the exception of the corresponding UE CONTEXT RELEASE COMMAND message with "Cause" equal to "Normal Release", "Handover Cancelled" or a successful mobility activity (e.g., cause "Successful Handover", or "NG Intra system Handover triggered"), or

– receipt by the NG-RAN of a PATH SWITCH REQUEST ACKNOWLEDGE or PATH SWITCH REQUEST FAILED message by which some or all DRBs in the corresponding PATH SWITCH REQUEST need to be released, or

– transmission of a NG RESET ACKNOWLEDGE message to AMF; or

– receipt of a NG RESET ACKNOWLEDGE message from AMF,

Any of the UL or DL DRBs release using the RRCReconfiguration message (see TS 38.331[20]) sent to the UE, triggers the corresponding counter to increment by 1.

DRBs with bursty flow are considered active if there is user data in the PDCP queue in any of the directions or if any data (UL or DL) has been transferred during the last 100 ms. DRBs with continuous flow are seen as active DRBs in the context of this measurement, as long as the UE is in RRC connected state. Each corresponding DRB to release is added to the relevant measurement per mapped 5QI and S-NSSAI.

A particular DRB is defined to be of type continuous flow if the mapped 5QI is any of {1, 2, 65, 66}.

d) Each measurement is an integer value. The number of measurements is equal to the number of mapped 5QI levels plus the number of S-NSSAIs.

e) The measurements name has the form DRB.RelActNbr.5QI, where 5QI identifies the mapped 5QI and DRB.RelActNbr.SNSSAI, where SNSSAI identifies the S-NSSAI.

f) NRCellCU

g) Valid for packet switched traffic

h) 5GS

i) This measurement is to support the Retainability KPI "DRB Retainability" defined in TS 28.554 [8].

5.1.1.10.4 In-session activity time for DRB

a) This measurement provides the aggregated active session time for DRBs in a cell. The measurement is split into sub counters per mapped 5QI and per S-NSSAI. DRBs used in 3GPP option 3 shall not be covered in this measurement.

b) CC

c) Number of "in session" seconds aggregated for DRBs with a certain mapped 5QI level or for a certain S-NSSAI, where "in session" has the following definitions:

– DRBs with bursty flow is said to be "in session" if there is user data in the PDCP queue in any of the directions or if any data (UL or DL) has been transferred during the last 100 ms for that DRB.

– DRBs with continuous flow are seen as being "in session" in the context of this measurement, as long as the UE is in RRC connected state, and the session time is increased from the first data transmission on the DRB until 100 ms after the last data transmission on the DRB.

A particular DRB is defined to be of type continuous flow if the mapped 5QI is any of {1, 2, 65, 66}.

d) Each measurement is an integer value. The number of measurements is equal to the number of mapped 5QI levels plus the number of S-NSSAIs.

e) The measurement name has the form DRB.SessionTime.5QI, where 5QI identifies the mapped 5QI and DRB.SessionTime.SNSSAI, where SNSSAI identifies the S-NSSAI.

f) NRCellCU

g) Valid for packet switched traffic

h) 5GS

i) This measurement is to support the Retainability KPI "DRB Retainability" defined in TS 28.554 [8].

5.1.1.10.5 Number of Initial DRBs attempted to setup

a) This measurement provides the number of initial DRBs attempted to setup to support all requested QoS flows in the PDU sessions to be setup by the INITIAL CONTEXT SETUP REQUEST messages received by the gNB from AMF. This measurement is optionally split into subcounters per mapped 5QI and per S-NSSAI.

b) CC.

c) On receipt of "PDU Session Resource Setup Request List" IE in an INITIAL CONTEXT SETUP REQUEST message (see TS 38.413 [11]) to gNB from the AMF. Each DRB that is needed to setup in the transmitted RRCReconfiguration message increments the relevant subcounter per mapped 5QI by 1, and optionally the relevant subcounter per S-NSSAI by 1.

d) Each measurement is an integer value.

e) The measurement name has the form.

DRB.InitialEstabAtt.5QI where 5QI identifies the mapped 5QI and

DRB.InitialEstabAtt.SNSSAI, where SNSSAI identifies the S-NSSAI.

f) NRCellCU.

g) Valid for packet switched traffic.

h) 5GS.

i) One usage of this performance measurements is for performance assurance.

5.1.1.10.6 Number of Initial DRBs successfully setup

a) This measurement provides the number of initial DRBs successfully setup to support all requested QoS flows in the PDU sessions to be setup by the INITIAL CONTEXT SETUP REQUEST messages received by the gNB from AMF. This measurement is optionally split into subcounters per mapped 5QI and per S-NSSAI.

b) CC.

c) On transmission of INITIAL CONTEXT SETUP RESPONSE message containing the "PDU Session Resource Setup Response List" IE (see TS 38.413 [11]) from the gNB to the AMF. The counter increases by the number of DRBs that was successfully setup indicated by the RRCReconfigurationComplete message from the UE, as the response to the transmitted RRCReconfiguration message that contains the DRBs to add (see TS 38.331[20]). Each DRB that was successfully setup to the UE increments the relevant subcounter per mapped 5QI by 1, and optionally the relevant subcounter per S-NSSAI by 1.

d) Each measurement is an integer value.

e) The measurement name has the form:

DRB.InitialEstabSucc.5QI where 5QI identifies the mapped 5QI and

DRB.InitialEstabSucc.SNSSAI where SNSSAI identifies the S-NSSAI.

f) NRCellCU.

g) Valid for packet switched traffic.

h) 5GS.

i) One usage of this performance measurements is for performance assurance.

5.1.1.10.7 Number of DRBs attempted to be resumed

a) This measurement provides the number of DRBs attempted to be resumed. This measurement is split into subcounters per mapped 5QI and per S-NSSAI.

b) CC.

c) On Receipt of the RRCResumeRequest message or RRCResumeRequest1 corresponding number of DRBs that are identified by gNB as to be resumed for the UE is counted. The identified DRBs related to consequent RRC connection resume fallback to RRC connection establishment initiated by gNB are excluded from the counting.

d) Each subcounter is an integer value.

e) DRB.ResumeAtt.5QI, where 5QI identifies mapped 5QI and

DRB.ResumeAtt.SNSSAI, where SNSSAI identifies the S-NSSAI.

f) NRCellCU.

g) Valid for packet switching.

h) 5GS.

a) This measurement provides the number of DRB’s prone to GTP-U Error Indication, the 5G CU-UP shall return a GTP-U Error Indication if it does not have a corresponding GTP-U context (see clause 5.2 of TS 23.527 [x]).

b) CC.

c) The 5G CU-UP should also notify the GTP-U user plane path failure via the Operation and Maintenance system. All DRB’s of this UE are counted for this measurement to the target 5GS cell. Each DRB attempted to establish is added to the relevant measurement per QCI, the possible QCIs are included in TS 23.501 [4]. The sum of all supported per QCI measurements shall equal the total number of DRB’s attempted to setup. In case only a subset of per QCI or per supported S-NSSAI measurements are supported, a sum subcounter will be provided first.

d) Each measurement is an integer value. The number of measurements is equal to the number of causes supported plus a possible sum value identified by the .sum suffix.

e) The measurement name has the form DRB.GTPUPathFailure.5QI, where 5QI identifies mapped 5QI and DRB.GTPUPathFailure.SNSSAI, where SNSSAI identifies the S-NSSAI.

f) NRCellCU.

g) Valid for packet switched traffic.

h) 5GS.

5.1.1.11 CQI related measurements

5.1.1.11.1 Wideband CQI distribution

a) This measurement provides the distribution of Wideband CQI (Channel Quality Indicator) reported by UEs in the cell.

5.1.1.13.1 QoS flow release

5.1.1.13.1.1 Number of released active QoS flows

a) This measurement provides the number of released QoS flows that were active at the time of release. QoS flows with bursty flow are seen as being active when there is user data in the queue in any of the directions. QoS flows with continuous flow are seen as active QoS flows in the context of this measurement, as long as the UE is in RRC connected state.
The measurement is split into subcounters per QoS level.

b) CC.

c) On transmission by the NG-RAN of a PDU SESSION RESOURCE RELEASE RESPONSE message for the PDU release initiated by the AMF with the exception of corresponding PDU SESSION RESOURCE RELEASE COMMAND message with "Cause" equal to "Normal Release" or "User inactivity", "Load balancing TAU required", "Release due to CN-detected mobility", "O&M intervention", or on transmission by the PDU SESSION RESOURCE MODIFY RESPONSE message for the PDU modification initiated by the AMF with the exception of corresponding PDU SESSION RESOURCE MODIFY REQUEST message with the "Cause" equal to "Normal Release", or on transmission by the NG-RAN of UE CONTEXT RELEASE COMPLETE for the UE context release initiated by the NG-RAN with the exception of the corresponding UE CONTEXT RELEASE REQUEST message with the cause equal to "Normal Release" or "User inactivity", "Partial handover", "Successful handover", or on transmission by the NG-RAN of UE CONTEXT RELEASE COMPLETE message for the UE context release initiated by the AMF with the exception of the corresponding UE CONTEXT RELEASE COMMAND message with "Cause" equal to "Normal Release", "Handover Cancelled" or a successful mobility activity (e.g., cause "Successful Handover", or "NG Intra system Handover triggered"), or on receipt by the NG-RAN of a PATH SWITCH REQUEST ACKNOWLEDGE or PATH SWITCH REQUEST FAILED message by which some or all QoS flows in the corresponding PATH SWITCH REQUEST need to be released , or on transmission of a NG RESET ACKNOWLEDGE message to AMF; or on receipt of a NG RESET ACKNOWLEDGE message from AMF, if any of the UL or DL are considered active in TS 38.413 [11].

QoS flows with bursty flow are considered active if there is user data in the PDCP queue in any of the directions or if any data (UL or DL) has been transferred during the last 100 ms.QoS flows with continuous flow are seen as active QoS flows in the context of this measurement, as long as the UE is in RRC connected state. Each corresponding QoS flows to release is added to the relevant measurement per QoS level (5QI), the possible 5QIs are described in TS 23.501 [4]. The sum of all supported per QoS flow measurements shall equal the total number of QoS flows attempted to release when the QoS flows is active according to the definition of bursty flow/continuous flow. In case only a subset of per QoS flows measurements is supported, a sum subcounter will be provided first.

d) Each measurement is an integer value. The number of measurements is equal to the number of QoS flows plus a possible sum value identified by the .sum suffix.

e) The measurement name has the form QF.RelActNbr.QoS.

f) NRCellCU.

g) Valid for packet switched traffic.

h) 5GS.

i) This measurement is to support the Retainability KPI "QoS flow Retainability" defined in TS 28.554 [8].

5.1.1.13.1.2 Number of QoS flows attempted to release

a) This measurement provides the number of QoS flows attempted to release. The measurement is split into subcounters per QoS level and per S-NSSAI.

b) CC.

c) On receipt by the gNB of an PDU SESSION RESOURCE RELEASE COMMAND or PDU SESSION RESOURCE MODIFY REQUEST message, or on gNB send the message of UE CONTEXT RELEASE REQUEST or PDU SESSION RESOURCE NOTIFY to AMF, each requested QoS Flow release Item in the message is release to the relevant measurement per QoS level, the possible QoS levels are included in TS 38.413. The sum of all supported per QoS level measurements shall equal the total number of Qos FlowS attempted to setup plus the number of S-NSSAI. In case only a subset of per QoS level measurements is supported, a sum subcounter will be provided first. Measurements are subcounters per 5QI and subcounters per S-NSSAI.

d) A single integer value.

e) The measurement name has the form:

QF.ReleaseAttNbr.5QI where 5QI identifies the 5QI and

QF.ReleaseAttNbr.SNSSAI identifies the S-NSSAI

f) NRCellCU.

g) Valid for packet switched traffic.

h) 5GS.

5.1.1.13.2 QoS flow activity

5.1.1.13.2.1 In-session activity time for QoS flow

a) This measurement provides the aggregated active session time for QoS flow in a cell. The measurement is split into subcounters per QoS level .

b) CC.

c) Number of "in session" seconds aggregated for QoS flows with a certain QoS level. , where "in session" has the following definitions:
– QoS flows with bursty flow is said to be "in session" for a UE if there is user data in the PDCP queue in any of the directions or if any QoS flow data (UL or DL) has been transferred during the last 100 ms for that 5QI
– QoS flows with continuous flow are seen as being "in session" in the context of this measurement as long as the UE is in RRC connected state, and the session time is increased from the first data transmission on the QoS flow until 100 ms after the last data transmission on the QoS flow.

The sum of all supported per QoS flow measurements shall equal the total session seconds. In case only a subset of per QoS flow measurements is supported, a sum subcounter will be provided first.

A particular QoS flow is defined to be of type continuous flow if the 5QI is any of {1, 2, 65, 66}.

d) Each measurement is an integer value. The number of measurements is equal to the number of QoS levels plus a possible sum value identified by the .sum suffix.

e) The measurement name has the form QF.SessionTimeQoS.QoS.

f) NRCellCU.

g) Valid for packet switched traffic.

h) 5GS.

i) This measurement is to support the Retainability KPI "QoS flow Retainability" defined in TS 28.554 [8].

5.1.1.13.2.2 In-session activity time for UE

a) This measurement provides the aggregated active session time for UEs in a cell.

a) This measurement provides the number of QoS flows failed to setup. The measurement is split into subcounters per failure cause.

b) CC.

c) On transmission by the NG-RAN of a PDU SESSION RESOURCE SETUP RESPONSE message, or transmission by the NG-RAN of a INITIAL CONTEXT SETUP RESPONSE message, or transmission by the NG-RAN of a PDU SESSION RESOURCE MODIFY RESPONSE message, each QoS flow failed to establish is added to the relevant measurement per cause, the possible causes are included in TS 38.413 [11]. The sum of all supported per cause measurements shall equal the total number of additional QoS flows failed to setup. In case only a subset of per cause measurements is supported, a sum subcounter will be provided first.

d) Each measurement is an integer value. The number of measurements is equal to the number of causes plus a possible sum value identified by the .sum suffix.

e) The measurement name has the form QF. EstabFailNbr.Cause
where Cause identifies the cause resulting in the QoS flow setup failure.

f) NRCellCU.

g) Valid for packet switched traffic.

h) 5GS.

5.1.1.13.3.4 Number of Initial QoS flow attempted to setup

a) This measurement provides the number of Initial QoS flows attempted to setup. The measurement is split into subcounters per QoS level (5QI).

b) CC.

c) On receipt by the NG-RAN of a INITIAL CONTEXT SETUP REQUEST message, each requested QoS flow in the message is added to the relevant measurement per QoS level (5QI) and per S-NSSAI, the possible 5QIs are included in TS 23.501 [4]. The sum of all supported per QoS level measurements shall equal the total number of Initial QoS flows attempted to setup. In case only a subset of per QoS level measurements is supported, a sum subcounter will be provided first.

d) Each measurement is an integer value. The number of measurements is equal to the number of QoS levels plus the number of S-NSSAIs, plus a possible sum value identified by the .sum suffix.

e) The measurement name has the form.

QF. InitialEstabAttNbr.5QI where 5QI identifies the 5QI and

QF.InitialEstabAttNbr.SNSSAI identifies the S-NSSAI.

f) NRCellCU.

g) Valid for packet switched traffic.

h) 5GS.

5.1.1.13.3.5 Number of Initial QoS flow successfully established

a) This measurement provides the number of Initial QoS flows successfully established. The measurement is split into subcounters per QoS level and per S-NSSAI.

b) CC.

c) On transmission by the NG-RAN of a INITIAL CONTEXT SETUP RESPONSE message,each QoS flow successfully established is added to the relevant measurement per QoS level (5QI) and per S-NSSAI, the possible 5QIs are included in TS 23.501 [4]. The sum of all supported per QoS level measurements shall equal the total number of Initial QoS flows successfully setup. In case only a subset of per QoS level measurements is supported, a sum subcounter will be provided first.

d) Each measurement is an integer value. The number of measurements is equal to the number of QoS levels plus a possible sum value identified by the .sum suffix.

e) The measurement name has the form:

QF.InitialEstabSuccNbr.5QI where 5QI identifies the 5QI and

QF. InitialEstabSuccNbr.SNSSAI identifies the S-NSSAI.

f) NRCellCU.

g) Valid for packet switched traffic.

h) 5GS.

5.1.1.13.3.6 Number of Initial QoS flow failed to setup

5.1.1.15.1 Attempted RRC connection establishments

a) This measurement provides the number of RRC connection establishment attempts for each establishment cause.

b) CC

c) Receipt of an RRCSetupRequest message by the gNB from the UE. Each RRCSetupRequest message received is added to the relevant per establishment cause measurement. RRCSetupRequests that are received while a setup procedure is already ongoing for this UE are excluded. RRCSetupRequests that are received during AMF Overload action (see clause 9.3.1.105 in TS 38.413) are effectively to be excluded from the measurement. The possible establishmentCause are included in TS 38.331 [20] (clause 6.2.2). The sum of all supported per cause measurement values shall be equal the total number of RRCSetupRequest.

d) Each measurement is an integer value. The number of measurements is equal to the number of establishment causes.

e) RRC.ConnEstabAtt.Cause where Cause identifies the establishment cause.

f) NRCellCU.

g) Valid for packet switched traffic.

h) 5GS.

i) One usage of this performance measurements is for performance assurance within accessibility area.

5.1.1.15.2 Successful RRC connection establishments

a) This measurement provides the number of successful RRC establishments for each establishment cause.

b) CC

c) Receipt by the gNB of an RRCSetupComplete message following a RRC connection setup request. Each RRCSetupComplete message received is added to the relevant per establishment cause measurement. The possible causes are included in TS 38.331 [20] (clause 6.2.2). The sum of all supported per cause measurements shall be equal the total number of RRCSetupComplete messages.

d) Each measurement is an integer value. The number of measurements is equal to the number of establishment causes.

e) RRC.ConnEstabSucc.Cause where Cause identifies the establishment cause.

f) NRCellCU.

g) Valid for packet switched traffic.

h) 5GS.

i) One usage of this performance measurements is for performance assurance within accessibility area.

5.1.1.15.3 Failed RRC connection establishments

a) This measurement provides the number of failed RRC establishments, this measurmenet is split into subcounters per failure cause.

a) This measurement provides the number of RRC connection resuming followed by network suspension.

b) CC.

c) On Transmission of a RRCRelease with suspension configuration message to UE after RRC connection resume request.

d) Each measurement is an integer value.

e) The measurement name has the form RRC.ResumeFollowedbySuspension.

f) NRCellCU.

g) Valid for packet switching.

h) 5GS.

5.1.1.18.6 Number of RRC connection resuming attempts followed by RRC Setup

a) This measurement provides the number of RRC connection resuming attempts where no UE context could be retrieved and therefore fallback to RRC Setup procedure was attempted.

b) CC.

c) On transmission of RRCSetup message to UE, after first having received RRCResumeRequest message or RRCResumeRequest1 from UE, the relevant subcounter per resume cause is stepped.

d) Each subcounter is an integer value.

e) The measurement name has the form RRC.ResumeFallbackToSetupAtt.cause.

Where cause indicates the RRC resume cause defined in clause 6.2.2 of TS 38.331 [20].

f) NRCellCU.

g) Valid for packet switching.

h) 5GS

5.1.1.19 Power, Energy and Environmental (PEE) measurements

5.1.1.19.1 Applicability of measurements

5.1.1.20.1 Received Random Access Preambles per cell

a) This measurement provides the average (arithmetic mean) number of RACH preambles received in a cell. Separate counts are provided for dedicated preambles, randomly chosen preambles in group A (aka "low range") and randomly chosen preambles in group B (aka "high range").

b) DER (n=1)

c) This measurement is obtained by collecting the measurements of "Received Random Access Preambles per cell" where the unit of measured value is per second, as defined in 38.314 [29] in the granularity period, and then taking the arithmetic mean of these measurements. Separate measurements will be obtained based on the following measurements contained in "Received Random Access Preambles per cell" measurement:

– Dedicated preambles

– Randomly selected preambles in the low range

– Randomly selected preambles in the high range.

d) Each counter is an integer value. The number of measurements is equal to three.

e) RACH.PreambleDedCell

RACH.PreambleACell

RACH.PreambleBCell

f) NRCellDU

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 to support RACH optimization (see TS 28.313 [30]).

5.1.1.20.2 Received Random Access Preambles per SSB

a) This measurement provides the average (arithmetic mean) number of RACH preambles received in a cell per SSB. Separate counts are provided for dedicated preambles, randomly chosen preambles in group A (aka "low range") and randomly chosen preambles in group B (aka "high range").

b) DER (n=1)

c) This measurement is obtained by collecting the measurements of "Received Random Access Preambles per SSB" where the unit of measured value is per second, as defined in 38.314 [29] in the granularity period, and then taking the arithmetic mean of these measurements. Separate measurements will be obtained based on the following measurements contained in "Received Random Access Preambles per cell" measurement:

– Dedicated preambles

– Randomly selected preambles in the low range

– Randomly selected preambles in the high range.

d) Each counter is an integer value. The number of measurements is equal to three times the number of SSB beams defined in the cell.

e) RACH.PreambleDed.Ssb, where Ssb represents the subcounter associated with SSB.

RACH.PreambleA.Ssb, where Ssb represents the subcounter associated with SSB.

RACH.PreambleB.Ssb, where Ssb represents the subcounter associated with SSB.

f) NRCellDU

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 to support RACH optimization (see TS 28.313 [30]).

5.1.1.20.3 Distribution of number of RACH preambles per cell

a) This measurement provides the distribution of the number of RACH preambles sent by the UE when successfully accessing the network, as reported by the UEs inside the RA-ReportList-r16 IE in the UEInformationResponse-r16 message. The measurement is incremented each time a UEInformationResponse-r16 message containing a RA-ReportList-r16 IE (see TS 38.331 [20]) is received.

b) CC.

c) Each of the RA-Report-r16 IEs in the RA-ReportList-r16 increments the measurement bin that is identified by Bin, where Bin corresponds to the number of RACH preambles sent to the cell denoted by cellId-r16 before a successful connection establishment. The number of RACH preambles is equal to:

, where

"n" equals to the number of numberOfPreamblesSentOnSSB-r16 IEs in all PerRASSBInfo-r16 IEs in the RA-Report-r16,

"numOfPreamblesPerSSB" equals to numberOfPreamblesSentOnSSB-r16 attribute in PerRASSBInfo-r16 IE, See TS 38.331 [20] clause 6.2.2.

d) Each measurement is an integer value.

e) RACH.PreambleDist.Bin

where Bin is to identify the bins associated with the number of preambles sent.

NOTE: The number of Bins and the range for each bin is left to implementation.

f) NRCellDU.

g) Valid for packet switched traffic.

h) 5GS.

i) One usage of this measurement is to support RACH optimization management, see TS 28.313 [30].

5.1.1.20.4 Distribution of RACH access delay

a) This measurement provides an estimate of the distribution of the RACH access delay, that is the interval from the time a UE sends its first RACH preamble until the UE is connected to the network. The measurement is incremented each time a UEInformationResponse-r16 message containing a RA-ReportList-r16 IE (see TS 38.331 [20]) is received.

b) CC.

c) Each of the RA-Report-r16 IEs in the RA-ReportList-r16 increments the measurement bin that is identified by Bin, where Bin corresponds to the UE RACH access delay for that particular RA-Report-r16 received from UE. The access delay is estimated based on the value of numberOfPreamblesSentOnSSB-r16 IE and contentionDetected-r16 IE in PerRAAttemptInfo-r16, where numberOfPreamblesSentOnSSB-r16 IE and PerRAAttemptInfo-r16 IE are contained in PerRASSBInfo-r16 IE. See TS 38.331 [20] clause 6.2.2.

NOTE: The estimate of the access delay is left to implementation.

d) Each measurement is an integer value.

e) RACH.AccessDelayDist.Bin

where Bin is to identify the bins associated with the RACH access delay.

NOTE: Bin and the range for each bin is left to implementation.

f) NRCellDU.

g) Valid for packet switched traffic.

h) 5GS.

i) One usage of this measurement is to support RACH optimization management, see TS 28.313 [30].

5.1.1.21 Intra-NRCell SSB Beam switch Measurement

5.1.1.21.1 Number of requested Intra-NRCell SSB Beam switch executions

a) This measurement provides the number of outgoing intra-NRCell SSB Beam switch executions requested by the source SSB Beam in an NRCell in case the beam switch function is enabled (see TS 38.331[20]).

b) CC.

c) On transmission of tci-StatesPDCCH-ToAddList in MAC CE to the UE triggering the switch from the source SSB Beam to the target SSB Beam, indicating the attempt of an outgoing intra-NRCell SSB Beam switch (see TS 38.321 [32]), the counter is stepped by 1.

d) A single integer value.

e) MR.IntraCellSSBSwitchReq

f) Beam

g) Valid for packet switched traffic

h) 5GS

i) One usage of this performance measurements is for performance assurance. This measurement is only applicable when the beam switch function is activated.

5.1.1.21.2 Number of successful Intra-NRCell SSB Beam switch executions

b) CC.

c) This measurement is obtained by incrementing the appropriate measurement bin using measured quantity value (see Table 10.1.6.1-1 in TS 38.133 [35]) when a RSRP value for the neighbour E-UTRA cell is reported by a UE to the gNB via RRC MeasurementReport message (see TS 38.331 [20]).

d) Each subcounter is an integer.

e) L1M.RSRPEutraNbr.Bin

where the Bin represents the range of reported RSRP value to 97).

NOTE: Number of bins and the range for each bin is left to implementation.

f) EUtranCellRelation

g) Valid for packet switched traffic

h) 5GS

i) One usage of this performance measurements is to support MDA.

5.1.1.23 Number of Active Ues

5.1.1.23.1 Mean number of Active UEs in the DL per cell

a) This measurement provides the mean number of active DRBs for UEs in an NRCellDU. The measurement is calculated per PLMN ID and per QoS level (mapped 5QI or/and QCI in NR option 3) and per supported S-NSSAI.

b) DER (n=1).

c) This measurement is obtained by aggregating the measurement " Mean number of Active UEs in the DL per DRB per cell " (see clause 4.2.1.3.2 in TS 38.314 [29]). The measurement is performed per PLMN ID and per QoS level (mapped 5QI or/and QCI in NR option 3) and per supported S-NSSAI.

d) Each measurement is a single integer value. The number of measurements is equal to the number of PLMNs multiplied by the number of QoS levels or multiplied by the number of supported 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.MeanActiveUeDl_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/and QCI level, and SNSSAI represents S-NSSAI.

f) NRCellDU.

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

5.1.1.23.2 Max number of Active UEs in the DL per cell

a) This measurement provides the max number of active DRBs for UEs in an NRCellDU. The measurement is calculated per PLMN ID and per QoS level (mapped 5QI or/and QCI in NR option 3) and per supported S-NSSAI.

b) DER (n=1).

c) This measurement is defined according to measurement " Max number of Active UEs in the DL per DRB per cell " (see clause 4.2.1.3.3 in TS 38.314 [29]). The measurement is performed per PLMN ID and per QoS level (mapped 5QI or/and QCI in NR option 3) and per supported S-NSSAI. d) Each measurement is a single integer value. The number of measurements is equal to the number of PLMNs multiplied by the number of QoS levels or multiplied by the number of supported 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.MaxActiveUeDl_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/and QCI level, and SNSSAI represents S-NSSAI.

f) NRCellDU.

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

5.1.1.23.3 Mean number of Active UEs in the UL per cell

b) DER (n=1)

c) This measurement is obtained by aggregating the measurement " Mean number of Active UEs in the UL per DRB per cell " (see clause 4.2.1.3.4 in TS 38.314 [29]). The measurement is performed per PLMN ID and per QoS level (mapped 5QI or/and QCI in NR option 3) and per supported S-NSSAI.

d) Each measurement is a single integer value. The number of measurements is equal to the number of PLMNs multiplied by the number of QoS levels or multiplied by the number of supported 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.MeanActiveUeUl_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/and QCI level, and SNSSAI represents S-NSSAI.

f) NRCellDU.

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

5.1.1.23.4 Max number of Active UEs in the UL per cell

a) This measurement provides the max number of active DRBs for UEs in an NRCellDU. The measurement is optionally split into subcounters per QoS level (mapped 5QI or/and QCI in NR option 3) and subcounters per S-NSSAI.

b) DER (n=1)

c) This measurement is defined by the measurement " Max number of Active UEs in the UL per DRB per cell " (see clause 4.2.1.3.5 in TS 38.314 [29]). Separate counters are optionally maintained for each mapped 5QI (or/and QCI for option 3) and for each S-NSSAI.

d) The number of measurements is equal to one. If the optional QoS level measurement is perfomed, the number of measurements is equal to the number of mapped 5QIs (or/and number of QCI for option 3), and the number of S-NSSAIs.

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

f) NRCellDU.

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

5.1.1.24 5QI 1 QoS Flow Duration Monitoring

5.1.1.24.1 Average Normally Released Call (5QI 1 QoS Flow) Duration

a) This measurement provides the average value of normally released call (5QI 1 QoS Flow) duration.

b) CC

c) The measurement is done as an arithmetical average of the samples of normally released calls (5QI 1 QoS Flows) duration at the end of measurement period. Each sample is measured from the point in time the 5QI 1 QoS Flow has been successfully established via initial Context setup procedure (INITIAL CONTEXT SETUP RESPONSE message sent by NR CU cell to AMF according to TS 38.413 [11]) or additional 5QI 1 QoS Flow setup procedure (PDU SESSION RESOURCE SETUP RESPONSE or a PDU SESSION RESOURCE MODIFY RESPONSE message sent by NR CU cell to AMF according to TS 38.413 [11]) or incoming handover (HANDOVER REQUEST ACKNOWLEDGE sent by target NR CU cell to AMF in case of NG intra/inter-system handover or sent by target to source NR CU cell via Xn in case of Xn based handover according to TS 38.413 [11]) till the point in time the 5QI 1 QoS Flow is released via gNB (UE CONTEXT RELEASE REQUEST message sent by NR CU cell to AMF according to TS 38.413 [11]) or AMF initiated release procedure (UE CONTEXT RELEASE COMMAND or PDU SESSION RESOURCE RELEASE COMMAND or PDU SESSION RESOURCE MODIFY REQUEST message sent by AMF to NR CU cell according to TS 38.413 [11)) or successful outgoing handover (UE CONTEXT RELEASE over Xn received from the target NG CU cell in case of Xn based handover or UE CONTEXT RELEASE COMMAND message sent by AMF to NR CU cell in case of NG intra/inter-system handover according to TS 38.413 [11]) due to normal release cause.

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

e) The measurement name has the form 5QI1QoSflow.Rel.Average.NormCallDuration.

f) NRCellCU

g) Valid for packet switched traffic

h) 5GS

i) Possible normal release causes according to TS 38.413 [11] are the following ones: "Normal Release", "Deregister", "User inactivity", "Release due to CN-detected mobility", "Handover Cancelled", "Partial handover", "Successful handover".

5.1.1.24.2 Average Abnormally Released Call (5QI 1 QoS Flow) Duration

a) This measurement provides the average value of abnormally released call (5QI 1 QoS Flow) duration.

b) CC

c) The measurement is done as an arithmetical average of the samples of abnormally released calls (5QI 1 QoS Flows) duration at the end of measurement period. Each sample is measured from the point in time the 5QI 1 QoS Flow has been successfully established via initial Context setup procedure (INITIAL CONTEXT SETUP RESPONSE message sent by NR CU cell to AMF according to TS 38.413 [11]) or additional 5QI 1 QoS Flow setup procedure (PDU SESSION RESOURCE SETUP RESPONSE or a PDU SESSION RESOURCE MODIFY RESPONSE message sent by NR CU cell to AMF according to TS 38.413 [11]) or incoming handover (HANDOVER REQUEST ACKNOWLEDGE sent by target NR CU cell to AMF in case of NG intra/inter-system handover or sent by target to source NR CU cell via Xn in case of Xn based handover according to TS 38.413 [11]) till the point in time the 5QI 1 QoS Flow is released via gNB (UE CONTEXT RELEASE REQUEST message sent by NR CU cell to AMF according to TS 38.413 [11]) or AMF initiated release procedure (UE CONTEXT RELEASE COMMAND, PDU SESSION RESOURCE RELEASE COMMAND or PDU SESSION RESOURCE MODIFY REQUEST message sent by AMF to NR CU cell according to TS 38.413 [11)) due to abnormal release cause.

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

e) The measurement name has the form 5QI1QoSflow.Rel.Average.AbnormCallDuration.

f) NRCellCU

g) Valid for packet switched traffic

h) 5GS

i) Possible abnormal release causes are given in TS 38.413 [11] except for the following causes: "Normal Release", "Deregister", "User inactivity", "Release due to CN-detected mobility", "Handover Cancelled", "Partial handover", "Successful handover".

5.1.1.24.3 Distribution of Normally Released Call (5QI 1 QoS Flow) Duration

a) This measurement provides the histogram result of the samples related to normally released call (5QI 1 QoS Flow) duration collected during measurement period duration.

b) CC

c) Each sample is measured from the point in time the 5QI 1 QoS Flow has been successfully established via initial Context setup or additional 5QI 1 QoS Flow setup procedure or incoming handover till the point in time the 5QI 1 QoS Flow is released via gNB or AMF initiated release procedure or successful outgoing handover due to normal release cause (refer to 5QI1QoSflow.Rel.Average.NormCallDuration part c) in clause 5.1.1.24.1 for detailed sampling). Triggering is done for the bin the given sample falls in.

d) Each measurement is an integer value.

e) The measurement name has the form 5QI1QoSflow.Rel.NormCallDurationBinX where X denotes the X-th bin from total number of N configured bins. X-th bin stands for the normal call duration which is within the range from t_x-1to t_x.

f) NRCellCU

g) Valid for packet switched traffic

h) 5GS

i) Each histogram function is represented by the configured number of bins with configured bin width by operator.

b) CC.

c) The measurements of too late handovers for the beam per adjacent cell events are obtained respectively by accumulating the number of failure events detected by gNB during the inter-system mobility from 5GS to EPS, where adjacent cells are identified by their E-UTRAN Cell Global Identifier (ECGI).

d) Each measurement is an integer value.

e) HO.InterSys.bTooLate.ECGI

f) Beam

g) Valid for packet switched traffic.

h) 5GS.

i) One usage of this measurement is to support MRO (see TS 28.313 [30]).

5.1.1.25.7 Unnecessary handovers per beam-cell pair for inter-system mobility

a) This measurement provides the number of unnecessary handover events per beam-cell pair (source beam, i.e., the last beam before handover, and target cell) detected during the inter-system mobility from 5GS to EPS. An example of unnecessary handover occurred when a UE handed over from NG-RAN to other system (e.g. UTRAN) even though quality of the NG-RAN coverage was sufficient.

b) CC.

c) The measurement of unnecessary handovers for the beam per adjacent cell is obtained by accumulating the number of inter-system unnecessary handover reports detected by gNB during the inter-system mobility from 5GS to EPS, where adjacent cells are identified by their E-UTRAN Cell Global Identifier (ECGI).

d) Each measurement is an integer value.

e) HO.InterSys.bUnnecessary.ECGI

f) Beam

g) Valid for packet switched traffic.

h) 5GS.

i) One usage of this measurement is to support MRO (see TS 28.313 [30]).

5.1.1.25.8 Handover ping-pong per beam-cell pair for inter-system mobility

a) This measurement provides the number of handover ping-pong events per beam-cell pair (source beam, i.e., the last beam before failure, and target cell) detected during the inter-system mobility from 5GS to EPS. An example of handover ping-pong occurred when a UE is handed over from a cell in a source system (e.g. NG-RAN) to a cell in a target system different from the source system (e.g. E-UTRAN), then within a predefined limited time the UE is handed over back to a cell in the source system, while the coverage of the source system was sufficient for the service used by the UE.

b) CC.

c) The measurement of handover ping-pong events for the beam per adjacent cell is obtained by accumulating the number of failure events detected by gNB during the inter-system mobility from 5GS to EPS, where adjacent cells are identified by their NR Cell Identity (NCI).

d) Each measurement is an integer value.

e) HO.InterSys.bPingPong.NCI

f) Beam

g) Valid for packet switched traffic.

h) 5GS.

i) One usage of this measurement is to support MRO (see TS 28.313 [30]).

5.1.1.26 PHR Measurement

5.1.1.26.1 Type 1 power headroom distribution

a) This measurement provides a bin distribution (histogram) of Type 1 power headroom (See in TS 38.321 [32]) measurements.

b) CC.

c) This measurement is obtained by incrementing the appropriate measurement bin using Type1 power headroom value when GNB received Type1 power headroom contained in Single Entry PHR MAC CE or Multiple Entry PHR MAC CE (See in TS 38.321 [32]) for period headroom report from UE.

5.1.1.28.1 Number of UE related the SSB beam Index (mean)

a) This measurement provides number of UE related the SSB beam index.

b) CC.

c) The measurement is obtained by sampling at a pre-defined interval, the number of UE related SSB beam index, and then taking the arithmetic mean. The UE related beam index which maintained by UE random access and handover and beam switch in case the beam switch function is enabled (see TS 38.331[20]).

d) A single integer value.

e) L1M.SSBBeamRelatedUeNbr.

f) Beam

g) Valid for packet switched traffic

h) 5GS

i) One usage of this performance measurements is for performance assurance. This measurement is only applicable when the beam switch function is activated.

5.1.1.29 Transmit power utilization measurements

5.1.1.29.1 Maximum transmit power of NR cell

a) This measurement provides the maximum carrier transmit power in the measurement granularity interval.

b) SI.

c) This measurement is obtained by retaining the maximum value of the total carrier power transmitted in the cell within the measurement granularity period. The power includes all radio power transmitted, included common channels, traffic channels, control channels. The value is expressed in dBm.

d) Float in dBm.

e) CARR.MaxTxPwr

f) NRCellDU.

g) Valid for packet switched traffic.

h) 5GS.

5.1.1.29.2 Mean transmit power of NR cell

a) This measurement provides the mean carrier transmit power in the measurement granularity interval.

a) This measurement provides the Time-domain average maximum scheduled layer number for PDSCH under MIMO scenario in the downlink.

b) SI

c) This measurement is obtained as:

Where LM(T) denotes the Time-domain average of maximum scheduled layer number for PDSCH under MIMO scenario in the downlink in the time period T. denotes the maximum number of scheduled layer of PDSCH at sampling occasion j; K(T) denotes the number of sampling occasions at which is not 0; T denotes the time period during which the measurement is performed; and j denotes the sampling occasion during time period T, for example, a sampling occasion is 1 slot.

d) A single real value.`

e) RRU.MaxLayerDlMimo, which indicates the PDSCH Time-domain average maximum scheduled layer number for MIMO scenario in the downlink.

f) NRCellDU.

g) Valid for packet switching.

h) 5GS.

i) One usage of this measurement is evaluate the actural spatial capability of a cell in the downlink under MIMO scenario.

5.1.1.30.4 PUSCH Time-domain average Maximum Scheduled Layer Number of cell for MIMO scenario

a) This measurement provides the Time-domain average maximum scheduled layer number for PUSCH under MIMO scenario in the uplink.

b) SI

c) This measurement is obtained as:

Where LM(T) denotes the Time-domain average of maximum scheduled layer number for PUSCH under MIMO scenario in the uplink in the time period T. denotes the maximum number of scheduled layer of PUSCH at sampling occasion j; K(T) denotes the number of sampling occasions at which is not 0; T denotes the time period during which the measurement is performed; and j denotes the sampling occasion during time period T, for example, a sampling occasion is 1 slot.

d) A single real value.

e) RRU.MaxLayerUlMimo, which indicates the PUSCH Time-domain average maximum scheduled layer number for MIMO scenario in the uplink.

f) NRCellDU.

g) Valid for packet switching.

h) 5GS.

i) One usage of this measurement is evaluate the actural spatial capability of a cell in the uplink under MIMO scenario.

5.1.1.30.5 Average value of scheduled MIMO layers per PRB on the DL

a) This measurement provides the average value of allocated MIMO layers on the downlink per PRB per cell, for MIMO scenario within the measurement period.

b) SI.

c) This measurement is obtained by computing the average value of scheduled MIMO layers among all used PRBs that are used within the measurement period in the cell. The average value is obtained by this formula:

where denotes the average value of scheduled MIMO layers per PRB per cell on the DL. denotes the measurement period (e.g. 1 hour). And denotes the sampling occasion (e.g. 1 symbol). And denotes the number of kinds of MIMO layers (e.g. 2 kinds). denotes the number of MIMO layers (e.g. 1 layers, 4layers, etc.) scheduled for traffic transmission at sampling occasion . denotes the number of PDSCH PRBs used for transmission corresponding to , at sampling occasion . For example, a cell has 10 PRBs in total for one sampling occasion (=1), within which 9 PRBs are used and 1 left spare. Among 9 used PRBs, one is multiplexed by 4 layers, three is multiplexed by 2 layers, and five only has 1 layer (no multiplexing). So the in this case is: (1*4+3*2+5*1)/(1+3+5) = 1.67 layers per PRB.

d) Each measurement is a real value.

e) The measurement name has the form CARR.AverageLayersDl

f) NRCellDU.

g) Valid for packet switched traffic.

h) 5GS.

i）One usage of this measurement is to monitor the cell capacity for MIMO scenario, on the DL.

5.1.1.30.6 Average value of scheduled MIMO layers per PRB on the UL

a) This measurement provides the average value of allocated MIMO layers on the uplink per PRB per cell, for MIMO scenario within the measurement period.

b) SI.

where denotes the average value of scheduled MIMO layers per PRB per cell on the UL. denotes the measurement period (e.g. 1 hour). And denotes the sampling occasion (e.g. 1 symbol). And denotes the number of kinds of MIMO layers (e.g. 2 kinds). denotes the number of MIMO layers (e.g. 1 layers, 4layers, etc.) scheduled for traffic transmission at sampling occasion . denotes the number of PUSCH PRBs used for transmission corresponding to , at sampling occasion . For example, a cell has 10 PRBs in total for one sampling occasion (=1), within which 9 PRBs are used and 1 left spare. Among 9 used PRBs, one is multiplexed by 4 layers, three is multiplexed by 2 layers, and five only has 1 layer (no multiplexing). So the in this case is: (1*4+3*2+5*1)/(1+3+5) = 1.67 layers per PRB.

d) Each measurement is a real value.

e) The measurement name has the form CARR.AverageLayersUl

f) NRCellDU.

g) Valid for packet switched traffic.

h) 5GS.

i）One usage of this measurement is to monitor the cell capacity for MIMO scenario, on the UL.

5.1.1.31 RSRQ measurement

5.1.1.31.1 SS-RSRQ distribution in gNB

a) This measurement provides the distribution of SS-RSRQ received by gNB from UEs in the cell. The periodical UE measurement reports towards all of the UEs need to be triggered by gNB in the measured New Radio cell (See in TS 38.331[20]).

b) CC.

c) This measurement is obtained by incrementing the appropriate measurement bin using measured quantity value (See Table 10.1.11.1-1 in TS 38.133 [35], clause 5.1.3 SS reference signal received quality (SS-RSRQ) in 38.215[34] ) when a RSRQ value is reported by a UE when RSRQ is used for MeasQuantityResults IE that is in resultsSSB-Cell IE within the measResult IE as configured by MeasurementReport configurations as defined in TS 38.331 [20].

d) A set of integer.

e) MR.NRScSSRSRQ.BinX

where X represents the range of Measured quantity SS-RSRQ value (-43 to 20 dB)

NOTE: Number of bins and the range for each bin is left to implementation.

f) NRCellCU

g) Valid for packet switched traffic

h) 5GS

5.1.1.31.2 SS-RSRQ distribution per SSB

a) This measurement provides the distribution of SS-RSRQ per SSB received by the gNB of a serving cell from UEs in the measResults IEs in MeasurementReport messages that is triggered by the gNB sending the measConfig messages to request UEs to send the UE measurement reports (see clause 5.5.2 in TS 38.331 [35]).

b) CC.

c) This measurement is obtained by incrementing the appropriate measurement bin identified by rsrq value in the MeasQuantityResults IE in ssb-Results IE for the SSB identified by ssb-Index, where the rsrq value for the SSB beam of the serving cell is reported by a UE to the gNB via the measResultServingCell in MeasResultServMO IE in the measResults message (see TS 38.331 [20]).

d) Each subcounter is an integer.

e) MR.SS-RSRQPerSSB.Bin

where Bin represents the range of reported SS-RSRQ value (0 .. 127) mapping to -43 dB to 20 dB with 0.5 dB resolution (See Table 10.1.11.1-1 in TS 38.133 [35]).

NOTE: Number of bins and the range for each bin is left to implementation.

f) Beam

g) Valid for packet switched traffic

h) 5GS

5.1.1.31.3 SS-RSRQ distribution per SSB of neighbor NR cell

a) This measurement provides the distribution of SS-RSRQ per SSB received by the gNB of a neighbour cell from UEs in the measResults IEs in MeasurementReport messages that is triggered by the gNB sending the measConfig messages to request UEs to send the UE measurement reports (see clause 5.5.2 in TS 38.331 [20]).

b) CC.

c) This measurement is obtained by incrementing the appropriate measurement bin identified by rsrq value in the MeasQuantityResults IE in ssb-Results IE for the SSB identified by ssb-Index, where the rsrq value for the SSB beam of the neighbor cell is reported by a UE to the gNB via the measResultListNR in MeasResultNeighCells IE in the measResults message (see TS 38.331 [20]).

d) Each subcounter is an integer.

e) MR.SS-RSRQ.SSBIndex.Bin

where SSBIndex identifies the SSB beam of the neighbor NR cell.

Bin represents the range of reported SS-RSRQ value (0 .. 127) mapping to -43 dB to 20 dB with 0.5 dB resolution (See Table 10.1.11.1-1 in TS 38.133 [35]).

NOTE: Number of bins and the range for each bin is left to implementation.

f) NRCellRelation

g) Valid for packet switched traffic

f) NRCellRelation

g) Valid for packet switched traffic

h) 5GS

5.1.1.33 Timing Advance

5.1.1.33.1 Timing Advance distribution for NR Cell

a) This measurement provides the distribution of the Absolute Timing Advance (T_A) values transmitted by the gNB to UEs in the cell..

b) CC

c) This measurement is obtained by incrementing the appropriate measurement bin when an Absolute Timing Advance Command is sent to a UE in the NR cell, see TS 38.321 [32].

d) Each subcounter is an integer.

e) L1M. ATADist.Bin
where Bin represents the range of absolute T_A value (0 to 4095).

NOTE: Number of bins and the range for each bin is left to implementation.

f) NRCellDU

g) Valid for packet switched traffic

h) 5GS

i) One usage of this performance measurements is to support MDA.

5.1.1.34 Incoming GTP Data Packet Loss in gNB over N3

a) This measurement provides the number of GTP data packets which are not successfully received at gNB over N3 after being sent by UPF. It is a measure of the incoming GTP data packet loss per N3 interface. The measurement is split into subcounters per QoS level (5QI) and subcounters per supported 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 UPF to a gNB 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 lost GTP packets. 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.InDataPktPacketLossN3gNB or GTP.InDataPktPacketLossN3gNB.QoS where QoS identifies the target quality of service class or GTP.InDataPktPacketLossN3gNB.SNSSAI, where SNSSAI identifies the S-NSSAI.

f) EP_NgU (contained by GNBCUUPFunction)

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.