5.8 Performance measurements for N3IWF
28.5523GPP5G performance measurementsManagement and orchestrationRelease 18TS
5.8.1 PDU Session Resource management
5.8.1.1 PDU Session Resource setup
5.8.1.1.1 Number of PDU Sessions requested to setup
a) This measurement provides the number of PDU Sessions in the PDU SESSION RESOURCE SETUP REQUESTs received by the N3IWF from AMF. This measurement is split into subcounters per S-NSSAI.
b) CC.
c) Receipt of PDU SESSION RESOURCE SETUP REQUEST message (see TS 29.413 [22]) by the N3IWF from the AMF. Each PDU Session requested to setup increments the relevant subcounter per S-NSSAI by 1.
d) Each subcounter is an integer value.
e) SM.PDUSessionSetupNon3GPPReq.SNSSAI.
Where SNSSAI identifies the S-NSSAI.
f) N3IWFFunction.
g) Valid for packet switched traffic.
h) 5GS.
5.8.1.1.2 Number of PDU Sessions successfully setup
a) This measurement provides the number of PDU Sessions successfully setup by the N3IWF for the PDU SESSION RESOURCE SETUP REQUESTs received from AMF. This measurement is split into subcounters per S-NSSAI.
b) CC.
c) Transmission of PDU SESSION RESOURCE SETUP RESPONSE message containing the "PDU Session Resource Setup Response List" IE (see TS 38.413 [11]) by the N3IWF to the AMF. Each PDU Session listed in the "PDU Session Resource Setup Response List" IE increments the relevant subcounter per S-NSSAI by 1.
d) Each subcounter is an integer value.
e) SM.PDUSessionSetupNon3GPPSucc.SNSSAI.
Where SNSSAI identifies the S-NSSAI.
f) N3IWFFunction.
g) Valid for packet switched traffic.
h) 5GS.
5.8.1.1.3 Number of PDU Sessions failed to setup
a) This measurement provides the number of PDU Sessions failed to setup by the N3IWF for the PDU SESSION RESOURCE SETUP REQUESTs received from AMF. This measurement is split into subcounters per failure cause.
b) CC.
c) Transmission of PDU SESSION RESOURCE SETUP RESPONSE message containing the "PDU Session Resource Failed to Setup List" IE (see TS 38.413 [11]) by the N3IWF to the AMF. Each PDU Session listed in the "PDU Session Resource Failed to Setup List" IE increments the relevant subcounter per failure cause (see clause 9.3.1.2 of TS 38.413 [11]) by 1.
d) Each subcounter is an integer value.
e) SM.PDUSessionSetupNon3GPPFail.Cause.
Where Cause identifies the cause of the PDU Sessions Resource Setup failure, per the "PDU Session Resource Setup Unsuccessful Transfer" IE. Encoding of the Cause is defined in clause 9.3.1.2 of TS 38.413 [11].
f) N3IWFFunction.
g) Valid for packet switched traffic.
h) 5GS.
5.8.1.2 PDU Session Resource modification
5.8.1.2.1 Number of PDU Sessions requested to modify
a) This measurement provides the number of PDU Sessions in the PDU SESSION RESOURCE MODIFY REQUESTs received by the N3IWF from AMF. This measurement is split into subcounters per S-NSSAI.
b) CC.
c) Receipt of PDU SESSION RESOURCE MODIFY REQUEST message (see TS 29.413 [22]) by the N3IWF from the AMF. Each PDU Session requested to modify increments the relevant subcounter per S-NSSAI by 1.
d) Each subcounter is an integer value.
e) SM.PDUSessionModifyNon3GPPReq.SNSSAI.
Where SNSSAI identifies the S-NSSAI.
f) N3IWFFunction.
g) Valid for packet switched traffic.
h) 5GS.
5.8.1.2.2 Number of PDU Sessions successfully modified
a) This measurement provides the number of PDU Sessions successfully modified by the N3IWF for the PDU SESSION RESOURCE MODIFY REQUESTs received from AMF. This measurement is split into subcounters per S-NSSAI.
b) CC.
c) Transmission of PDU SESSION RESOURCE MODIFY RESPONSE message containing the "PDU Session Resource Modify Response Item" IE (see TS 38.413 [11]) by the N3IWF to the AMF. Each PDU Session listed in the "PDU Session Resource Modify Response Item" IE increments the relevant subcounter per S-NSSAI by 1.
d) Each subcounter is an integer value.
e) SM.PDUSessionModifyNon3GPPSucc.SNSSAI.
Where SNSSAI identifies the S-NSSAI.
f) N3IWFFunction.
g) Valid for packet switched traffic.
h) 5GS.
5.8.1.2.3 Number of PDU Sessions failed to modify
a) This measurement provides the number of PDU Sessions failed to modify by the N3IWF for the PDU SESSION RESOURCE MODIFY REQUESTs received from AMF. This measurement is split into subcounters per failure cause.
b) CC.
c) Transmission of PDU SESSION RESOURCE MODIFY RESPONSE message containing the "PDU Session Resource Failed to Modify List" IE (see TS 38.413 [11]) by the N3IWF to the AMF. Each PDU Session listed in the "PDU Session Resource Failed to Modify List" IE increments the relevant subcounter per failure cause (see clause 9.3.1.2 of TS 38.413 [11]) by 1.
d) Each subcounter is an integer value.
e) SM.PDUSessionModifyNon3GPPFail.Cause.
Where Cause identifies the cause of the PDU Sessions Resource modification failure, per the "PDU Session Resource Modify Unsuccessful Transfer" IE. Encoding of the Cause is defined in clause 9.3.1.2 of TS 38.413 [11].
f) N3IWFFunction.
g) Valid for packet switched traffic.
h) 5GS.
5.8.2 QoS flow management
5.8.2.1 QoS flow setup via untrusted non-3GPP access
5.8.2.1.1 Number of initial QoS flows attempted to setup via untrusted non-3GPP access
a) This measurement provides the number of QoS flows attempted to setup via untrusted non-3GPP access during initial UE context setup. The measurement is split into subcounters per 5QI and subcounters per network slice identifier (S-NSSAI).
b) CC.
c) Receipt by the N3IWF of an INITIAL CONTEXT SETUP REQUEST message (see TS 29.413 [22]). Each QoS flow requested to setup in the message is added to the relevant measurement per 5QI and relevant subcounter per per S-NSSAI.
d) Each measurement is an integer value.
e) QF.EstabNbrInitUntrustNon3gppAtt.5QI, where 5QI identifies the 5QI, and
QF.EstabNbrInitUntrustNon3gppAtt.SNSSAI, where SNSSAI identifies the S-NSSAI.
f) N3IWFFunction.
g) Valid for packet switched traffic.
h) 5GS.
5.8.2.1.2 Number of initial QoS flows successfully setup via untrusted non-3GPP access
a) This measurement provides the number of QoS flows successfully setup via untrusted non-3GPP access during initial UE context setup. The measurement is split into subcounters per 5QI and subcounters per network slice identifier (S-NSSAI).
b) CC.
c) Transmission by the N3IWF of an INITIAL CONTEXT SETUP RESPONSE message (see TS 29.413 [22]). Each QoS flow successfully setup in the message is added to the relevant measurement per 5QI and per S-NSSAI.
d) Each measurement is an integer value.
e) The measurement name has the form:
e) QF.EstabNbrInitUntrustNon3gppSucc.5QI, where 5QI identifies the 5QI, and
QF.EstabNbrInitUntrustNon3gppSucc.SNSSAI, where SNSSAI identifies the S-NSSAI.
f) N3IWFFunction.
g) Valid for packet switched traffic.
h) 5GS.
5.8.2.1.3 Number of initial QoS flows failed to setup via untrusted non-3GPP access
a) This measurement provides the number of QoS flows failed to setup via untrusted non-3GPP access during initial UE context setup. The measurement is split into subcounters per failure cause.
b) CC.
c) Transmission by the N3IWF of an INITIAL CONTEXT SETUP RESPONSE message (see TS 29.413 [22]). Each QoS flow failed to setup in the message is added to the relevant measurement per cause, the possible causes are specified in TS 38.413 [11].
d) Each measurement is an integer value.
e) QF.EstabNbrInitUntrustNon3gppFail.cause, where cause identifies the cause (see TS 38.413 [11]).
f) N3IWFFunction.
g) Valid for packet switched traffic.
h) 5GS.
5.8.2.1.4 Number of additional QoS flows attempted to setup via untrusted non-3GPP access
a) This measurement provides the number of additional QoS flows attempted to setup via untrusted non-3GPP access. The measurement is split into subcounters per 5QI and subcounters per network slice identifier (S-NSSAI).
b) CC.
c) Receipt by the N3IWF of a PDU SESSION RESOURCE SETUP REQUEST message or a PDU SESSION RESOURCE MODIFY REQUEST message (see TS 29.413 [22]). Each QoS flow requested to setup in the message is added to the relevant measurement per 5QI and relevant subcounter per per S-NSSAI.
d) Each measurement is an integer value.
e) QF.EstabNbrAddUntrustNon3gppAtt.5QI, where 5QI identifies the 5QI, and
QF.EstabNbrAddUntrustNon3gppAtt.SNSSAI, where SNSSAI identifies the S-NSSAI.
f) N3IWFFunction.
g) Valid for packet switched traffic.
h) 5GS.
5.8.2.1.5 Number of additional QoS flows successfully setup via untrusted non-3GPP access
a) This measurement provides the number of additional QoS flows successfully setup via untrusted non-3GPP access. The measurement is split into subcounters per 5QI and subcounters per network slice identifier (S-NSSAI).
b) CC.
c) Transmission by the N3IWF of a PDU SESSION RESOURCE SETUP RESPONSE message or a PDU SESSION RESOURCE MODIFY RESPONSE message (see TS 29.413 [22]). Each QoS flow successfully setup in the message is added to the relevant measurement per 5QI and per S-NSSAI.
d) Each measurement is an integer value.
e) The measurement name has the form:
e) QF.EstabNbrAddUntrustNon3gppSucc.5QI, where 5QI identifies the 5QI, and
QF.EstabNbrAddUntrustNon3gppSucc.SNSSAI, where SNSSAI identifies the S-NSSAI.
f) N3IWFFunction.
g) Valid for packet switched traffic.
h) 5GS.
5.8.2.1.6 Number of additional QoS flows failed to setup via untrusted non-3GPP access
a) This measurement provides the number of additional QoS flows failed to setup via untrusted non-3GPP access. The measurement is split into subcounters per failure cause.
b) CC.
c) Transmission by the N3IWF of a PDU SESSION RESOURCE SETUP RESPONSE message or a PDU SESSION RESOURCE MODIFY RESPONSE message (see TS 29.413 [22]). Each QoS flow failed to setup in the message is added to the relevant measurement per cause, the possible causes are specified in TS 38.413 [11].
d) Each measurement is an integer value.
e) QF.EstabNbrAddUntrustNon3gppFail.cause, where cause identifies the cause (see TS 38.413 [11]).
f) N3IWFFunction.
g) Valid for packet switched traffic.
h) 5GS.
5.8.2.2 QoS flow modification via untrusted non-3GPP access
5.8.2.2.1 Number of QoS flows attempted to modify via untrusted non-3GPP access
a) This measurement provides the number of QoS flows attempted to modify via untrusted non-3GPP access. The measurement is split into subcounters per QoS level (5QI) and subcounters per network slice identifier (S-NSSAI).
b) CC.
c) On receipt by the N3IWF of a PDU SESSION RESOURCE MODIFY REQUEST message (see TS 38.413 [11]), each QoS flow requested to modify in this message is added to the relevant subcounter per QoS level (5QI) and relevant subcounter per S-NSSAI. In case the 5QI of the QoS flow is modified, the QoS flow is counted to the subcounter for the target 5QI.
d) Each measurement is an integer value.
e) QF.ModNbrUntrustNon3gppAtt.5QI, where 5QI identifies the 5QI, and
QF.ModNbrUntrustNon3gppAtt.SNSSAI, where SNSSAI identifies the S-NSSAI.
f) N3IWFFunction.
g) Valid for packet switched traffic.
h) 5GS.
5.8.2.2.2 Number of QoS flows successfully modified via untrusted non-3GPP access
a) This measurement provides the number of QoS flows successfully modified via untrusted non-3GPP access. The measurement is split into subcounters per QoS level (5QI) and subcounters per network slice identifier (S-NSSAI).
b) CC.
c) On transmission by the N3IWF of a PDU SESSION RESOURCE MODIFY RESPONSE message (see TS 38.413 [11]), each QoS flow successfully modified is added to the relevant subcounter per QoS level (5QI) and relevant subcounter per S-NSSAI. In case the 5QI of the QoS flow is modified, the QoS flow is counted to the subcounter for the target 5QI.
d) Each measurement is an integer value.
e) QF.ModNbrUntrustNon3gppSucc.5QI, where 5QI identifies the 5QI, and
QF.ModNbrUntrustNon3gppSucc.SNSSAI, where SNSSAI identifies the S-NSSAI.
f) N3IWFFunction.
g) Valid for packet switched traffic.
h) 5GS.
5.8.2.X.3 Number of QoS flows failed to modify via untrusted non-3GPP access
a) This measurement provides the number of QoS flows failed to modify via untrusted non-3GPP access. The measurement is split into subcounters per failure cause.
b) CC.
c) On transmission by the N3IWF of a PDU SESSION RESOURCE MODIFY RESPONSE message (see TS 38.413 [11]), each QoS flow failed to modify is added to the relevant subcounter per cause.
d) Each measurement is an integer value.
e) QF.ModNbrUntrustNon3gppFail.cause, where cause identifies the cause (see TS 38.413 [11]).
f) N3IWFFunction.
g) Valid for packet switched traffic.
h) 5GS.
5.8.2.3 QoS flow release via untrusted non-3GPP access
5.8.2.3.1 Number of QoS flows attempted to release
a) This measurement provides the number of QoS flows attempted to release via untrusted non-3GPP access. The measurement is split into subcounters per QoS level (5QI) and subcounters per network slice identifier (S-NSSAI).
b) CC.
c) Receipt by the N3IWF of a PDU SESSION RESOURCE RELEASE COMMAND, PDU SESSION RESOURCE MODIFY REQUEST or UE CONTEXT RELEASE COMMAND message from AMF. Each QoS flow requested to release increments the relevant subcounter per 5QI and the relevant subcounter per S-NSSAI by 1 respectively.
d) Each measurement is an integer value.
e) QF.RelNbrUntrustNon3gppAtt.5QI, where 5QI identifies the 5QI, and
QF.RelNbrUntrustNon3gppAtt.SNSSAI, where SNSSAI identifies the S-NSSAI.
f) N3IWFFunction.
g) Valid for packet switched traffic.
h) 5GS.
5.8.2.3.2 Number of QoS flows successfully released
a) This measurement provides the number of QoS flows successfully released via untrusted non-3GPP access. The measurement is split into subcounters per QoS level (5QI) and subcounters per network slice identifier (S-NSSAI).
b) CC.
c) Transmission by the N3IWF of a PDU SESSION RESOURCE RELEASE RESPONSE, PDU SESSION RESOURCE MODIFY RESPONSE or UE CONTEXT RELEASE COMPLETE message. Each QoS flow requested to release increments the relevant subcounter per 5QI and the relevant subcounter per S-NSSAI by 1 respectively.
d) Each measurement is an integer value.
e) QF.RelNbrUntrustNon3gppSucc.5QI, where 5QI identifies the 5QI, and
QF.RelNbrUntrustNon3gppSucc.SNSSAI, where SNSSAI identifies the S-NSSAI.
f) N3IWFFunction.
g) Valid for packet switched traffic.
h) 5GS.
5.8.2.3.3 Number of released active QoS flows
a) This measurement provides the number of released QoS flows that were active at the time of release via untrusted non-3GPP access. 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 always seen as active QoS flows in the context of this measurement. This measurement is split into subcounters per QoS level (5QI) and subcounters per network slice identifier (S-NSSAI).
b) CC.
c) Transmission by the N3IWF of a PDU SESSION RESOURCE RELEASE RESPONSE message for the PDU session resource 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 PDU SESSION RESOURCE MODIFY RESPONSE message for the PDU session resource 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 N3IWF of UE CONTEXT RELEASE COMPLETE for the UE context release initiated by the N3IWF 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 N3IWF 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 receipt by the N3IWF 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 transmission by the N3IWF of a NG RESET ACKNOWLEDGE message to AMF; or receipt by the N3IWF of a NG RESET ACKNOWLEDGE message from AMF; if any of the UL or DL of the QoS flow is considered active in TS 38.413 [11].
QoS flows with bursty flow are considered active when there is still data transmission in the DL or UL. QoS flows with continuous flow are always seen as active QoS flows in the context of this measurement. Each released active QoS flow increments the relevant subcounter per QoS level (5QI) and subcounters per network slice identifier (S-NSSAI) by 1 respectively.
How to define for a particular 5QI if the QoS flow is of type bursty flow or continuous flow is outside the scope of this document.
d) Each measurement is an integer value.
e) QF.RelActNbrUntrustNon3gpp.5QI, where 5QI identifies the 5QI, and
QF.RelActNbrUntrustNon3gpp.SNSSAI, where SNSSAI identifies the S-NSSAI.
f) N3IWFFunction.
g) Valid for packet switched traffic.
h) 5GS.