5.2 Performance measurements for AMF

28.5523GPP5G performance measurementsManagement and orchestrationRelease 18TS

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

5.2.1 Registered subscribers measurement

5.2.1.1 Mean number of registered subscribers

a) This measurement provides the mean number of registered state subscribers per AMF

b) SI

c) This measurement is obtained by sampling at a pre-defined interval the number of registered subscribers in an AMF and then taking the arithmetic mean. The measurement can be split into subcounters per S-NSSAI.

d) A single integer value

e) RM.RegisteredSubNbrMean.SNSSAI

Where SNSSAI identifies the S-NSSAI

f) AMFFunction

g) Valid for packet switching

h) 5GS

5.2.1.2 Maximum number of registered subscribers

a) This measurement provides the maximum number of registered state subscribers per AMF

b) SI

c) This measurement is obtained by sampling at a pre-defined interval the number of registered subscribers in an AMF and then taking the maximum. The measurement can be split into subcounters per S-NSSAI.

d) A single integer value

e) RM.RegisteredSubNbrMax.SNSSAI

Where SNSSAI identifies the S-NSSAI

f) AMFFunction

g) Valid for packet switching

h) 5GS

5.2.2 Registration procedure related measurements

5.2.2.1 Number of initial registration requests

a) This measurement provides the number of initial registration requests received by the AMF.

b) CC

c) On receipt by the AMF from the UE of Registration Request with the registration type indicating an initial registration (see clause 4.2.2.2.2 of TS 23.502 [7]). Each initial registration request is added to the relevant subcounter per S-NSSAI.

d) Each subcounter is an integer value

e) RM.RegInitReq.SNSSAI

Where SNSSAI identifies the S-NSSAI;

f) AMFFunction

g) Valid for packet switched traffic

h) 5GS

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

5.2.2.2 Number of successful initial registrations

a) This measurement provides the number of successful initial registrations at the AMF.

b) CC

c) On transmission of Registration Accept by the AMF to the UE that sent the initial registration request (see TS 23.502 [7]). Each accepted initial registration is added to the relevant subcounter per S-NSSAI.

d) Each subcounter is an integer value

e) RM.RegInitSucc.SNSSAI

Where SNSSAI identifies the S-NSSAI;

f) AMFFunction

g) Valid for packet switched traffic

h) 5GS

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

5.2.2.3 Number of mobility registration update requests

a) This measurement provides the number of mobility registration update requests received by the AMF.

b) CC

c) On receipt by the AMF from the UE of Registration Request with the registration type indicating a Mobility Registration Update (see clause 4.2.2.2.2 of TS 23.502 [7]). Each mobility registration update request is added to the relevant subcounter per S-NSSAI.

d) Each subcounter is an integer value

e) RM.RegMobReq.SNSSAI

Where SNSSAI identifies the S-NSSAI;

f) AMFFunction

g) Valid for packet switched traffic

h) 5GS

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

5.2.2.4 Number of successful mobility registration updates

a) This measurement provides the number of successful mobility registration updates at the AMF.

b) CC

c) On transmission of Registration Accept by the AMF to the UE that sent the mobility registration update request (see TS 23.502 [7]). Each accepted mobility registration update is added to the relevant subcounter per S-NSSAI.

d) Each subcounter is an integer value

e) RM.RegMobSucc.SNSSAI

Where SNSSAI identifies the S-NSSAI;

f) AMFFunction

g) Valid for packet switched traffic

h) 5GS

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

5.2.2.5 Number of periodic registration update requests

a) This measurement provides the number of periodic registration update requests received by the AMF.

b) CC

c) On receipt by the AMF from the UE of Registration Request with the registration type indicating a Periodic Registration Update (see clause 4.2.2.2.2 of TS 23.502 [7]). Each periodic registration update request is added to the relevant subcounter S-NSSAI.

d) Each subcounter is an integer value

e) RM.RegPeriodReq.SNSSAI

Where SNSSAI identifies the S-NSSAI;

f) AMFFunction

g) Valid for packet switched traffic

h) 5GS

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

5.2.2.6 Number of successful periodic registration updates

a) This measurement provides the number of successful mobility registration updates at the AMF.

b) CC

c) On transmission of Registration Accept by the AMF to the UE that sent the periodic registration update request (see TS 23.502 [7]). Each accepted periodic registration update is added to the relevant subcounter per S-NSSAI.

d) Each subcounter is an integer value

e) RM.RegPeriodSucc.SNSSAI

Where SNSSAI identifies the S-NSSAI;

f) AMFFunction

g) Valid for packet switched traffic

h) 5GS

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

5.2.2.7 Number of emergency registration requests

a) This measurement provides the number of emergency registration requests received by the AMF.

b) CC

c) On receipt by the AMF from the UE of Registration Request with the registration type indicating an Emergency Registration (see clause 4.2.2.2.2 of TS 23.502 [7]). Each emergency registration request is added to the relevant subcounter per S-NSSAI.

d) Each subcounter is an integer value

e) RM.RegEmergReq.SNSSAI

Where SNSSAI identifies the S-NSSAI;

f) AMFFunction

g) Valid for packet switched traffic

h) 5GS

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

5.2.2.8 Number of successful emergency registrations

a) This measurement provides the number of successful emergency registrations at the AMF.

b) CC

c) On transmission Registration Accept by the AMF to the UE that sent the emergency registration request (see TS 23.502 [7]). Each accepted emergency registration is added to the relevant subcounter per S-NSSAI.

d) Each subcounter is an integer value

e) RM.RegEmergSucc.SNSSAI

Where SNSSAI identifies the S-NSSAI;

f) AMFFunction

g) Valid for packet switched traffic

h) 5GS

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

5.2.2.9 Mean time of Registration procedure

a) This measurement provides the mean time of registration procedure during each granularity period. The measurement is split into subcounters per S-NSSAI per registration type.

b) DER(n=1)

c) This measurement is obtained by accumulating the time interval for every successful registration procedure per S-NSSAI per registration type between the receipt by the AMF from the UE of a " REGISTRATION REQUEST " and the sending of a " REGISTRATION ACCEPT " message to the UE over a granularity period using DER. The end value of this time will then be divided by the number of successful registration procedures observed in the granularity period to give the arithmetic mean, the accumulator shall be reinitialised at the beginning of each granularity period. The measurement is split into subcounters per registration type, see TS 24.501 [24].

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

e) RM.RegTimeMean.SNSSAI. InitialReg
RM.RegTimeMean.SNSSAI. MobilityRegUpdate
RM.RegTimeMean.SNSSAI. PeriodicRegUpdate
RM.RegTimeMean.SNSSAI. EmergencyReg

Where SNSSAI identifies the S-NSSAI, InitialReg identifies the registration type "Initial Registration ", MobilityRegUpdate identifies the registration type "Mobility Registration Update", PeriodicRegUpdate identifies the registration type "Periodic Registration Update", EmergencyReg identifies the registration type "Emergency Registration".

f) AMFFunction

g) Valid for packet switched traffic

h) 5GS

i) One usage of this measurement is for monitoring the mean time of registration procedure during the granularity period.

5.2.2.10 Max time of Registration procedure

a) This measurement provides the max time of registration procedure during each granularity period. The measurement is split into subcounters per S-NSSAI per registration type.

b) DER(n=1)

c) This measurement is obtained by monitoring the time interval for every successful registration procedure per S-NSSAI per registration type between the receipt by the AMF from the UE of a " REGISTRATION REQUEST " and the sending of a " REGISTRATION ACCEPT " message to the UE over a granularity period using DER. 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. The measurement is split into subcounters per registration type, see TS 24.501 [24].

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

e) RM.RegTimeMax.SNSSAI. InitialReg
RM.RegTimeMax.SNSSAI. MobilityRegUpdate
RM.RegTimeMax.SNSSAI. PeriodicRegUpdate
RM.RegTimeMax.SNSSAI. EmergencyReg

f) Where SNSSAI identifies the S-NSSAI, InitialReg identifies the registration type "Initial Registration ", MobilityRegUpdate identifies the registration type "Mobility Registration Update", PeriodicRegUpdate identifies the registration type "Periodic Registration Update", EmergencyReg identifies the registration type "Emergency Registration".

g) AMFFunction

h) Valid for packet switched traffic

i) 5GS

j) One usage of this measurement is for monitoring the max time of registration procedure during the granularity period.

5.2.3 Service Request procedure related measurements

5.2.3.1 Number of attempted network initiated service requests

a) This measurement provides the number of attempted network initiated service requests.

b) CC.

c) Receipt of Namf_Communication_N1N2MessageTransfer indicating a network initiated service request from SMF or another NF by the AMF (see TS 23.502 [7]).

d) An integer value.

e) MM.ServiceReqNetInitAtt.

f) AMFFunction.

g) Valid for packet switched traffic.

h) 5GS.

5.2.3.2 Number of successful network initiated service requests

a) This measurement provides the number of successful network initiated service requests.

b) CC.

c) Transmission of N2 request that contains "MM NAS Service Accept" by the AMF to (R)AN (see TS 23.502 [7]), corresponding to the received Namf_Communication_N1N2MessageTransfer that indicated a network initiated service request.

d) An integer value.

e) MM.ServiceReqNetInitSucc.

f) AMFFunction.

g) Valid for packet switched traffic.

h) 5GS.

5.2.3.3 Total number of attempted service requests (including both network initiated and UE initiated)

a) This measurement provides the total number of the attempted service requests, including both network initiated and UE initiated service requests.

b) CC.

c) Receipt of Service Request by the AMF from (R)AN (see TS 23.502 [7]).

d) An integer value.

e) MM.ServiceReqTotalAtt.

f) AMFFunction.

g) Valid for packet switched traffic.

h) 5GS.

5.2.3.4 Total number of successful service requests (including both network initiated and UE initiated)

a) This measurement provides the total number of the successful service requests, including both network initiated and UE initiated service requests.

b) CC.

c) Transmission of N2 request that contains "MM NAS Service Accept" by the AMF to (R)AN (see TS 23.502 [7]).

d) An integer value.

e) MM.ServiceReqTotalSucc.

f) AMFFunction.

g) Valid for packet switched traffic.

h) 5GS.

5.2.4 Measurements related to registration via untrusted non-3GPP access

5.2.4.1 Number of initial registration requests via untrusted non-3GPP access

a) This measurement provides the number of initial registration requests via untrusted non-3GPP access received by the AMF.

b) CC.

c) Receipt by the AMF from N3IWF of an N2 message that contains Registration Request with the registration type indicating an initial registration (see clause 4.12.2.2 of TS 23.502 [7]). Each initial registration request is added to the relevant subcounter per S-NSSAI.

d) Each subcounter is an integer value.

e) RM.RegInitReqNon3GPP.SNSSAI.

Where SNSSAI identifies the S-NSSAI;

f) AMFFunction.

g) Valid for packet switched traffic.

h) 5GS.

5.2.4.2 Number of successful initial registrations via untrusted non-3GPP access

a) This measurement provides the number of successful initial registrations via untrusted non-3GPP access at the AMF.

b) CC.

c) Transmission by the AMF to N3IWF of an N2 message that contains Registration Accept corresponding to an initial registration request (see clause 4.12.2.2 of TS 23.502 [7]). Each accepted initial registration is added to the relevant subcounter per S-NSSAI.

d) Each subcounter is an integer value.

e) RM.RegInitSuccNon3GPP.SNSSAI.

Where SNSSAI identifies the S-NSSAI;

f) AMFFunction.

g) Valid for packet switched traffic.

h) 5GS.

5.2.4.3 Number of mobility registration update requests via untrusted non-3GPP access

a) This measurement provides the number of mobility registration update requests via untrusted non-3GPP access received by the AMF.

b) CC.

c) Receipt by the AMF from N3IWF of an N2 message that contains Registration Request with the registration type indicating a Mobility Registration Update (see clause 4.12.2.2 of TS 23.502 [7]). Each mobility registration update request is added to the relevant subcounter per S-NSSAI.

d) Each subcounter is an integer value.

e) RM.RegMobReqNon3GPP.SNSSAI.

Where SNSSAI identifies the S-NSSAI;

f) AMFFunction.

g) Valid for packet switched traffic.

h) 5GS.

5.2.4.4 Number of successful mobility registration updates via untrusted non-3GPP access

a) This measurement provides the number of successful mobility registration updates via untrusted non-3GPP access at the AMF.

b) CC.

c) Transmission by the AMF to N3IWF of an N2 message that contains Registration Accept corresponding to a mobility registration update request (see clause 4.12.2.2 of TS 23.502 [7]). Each accepted mobility registration update is added to the relevant subcounter per S-NSSAI.

d) Each subcounter is an integer value.

e) RM.RegMobSuccNon3GPP.SNSSAI.

Where SNSSAI identifies the S-NSSAI;

f) AMFFunction.

g) Valid for packet switched traffic.

h) 5GS.

5.2.4.5 Number of periodic registration update requests via untrusted non-3GPP access

a) This measurement provides the number of periodic registration update requests via untrusted non-3GPP access received by the AMF.

b) CC.

c) Receipt by the AMF from N3IWF of an N2 message that contains Registration Request with the registration type indicating a Periodic Registration Update (see clause 4.12.2.2 of TS 23.502 [7]). Each periodic registration update request is added to the relevant subcounter per S-NSSAI.

d) Each subcounter is an integer value.

e) RM.RegPeriodReqNon3GPP.SNSSAI.

Where SNSSAI identifies the S-NSSAI;

f) AMFFunction.

g) Valid for packet switched traffic.

h) 5GS.

5.2.4.6 Number of successful periodic registration updates via untrusted non-3GPP access

a) This measurement provides the number of successful mobility registration updates via untrusted non-3GPP access at the AMF.

b) CC.

c) Transmission by the AMF to N3IWF of an N2 message that contains Registration Accept corresponding to a periodic registration update request (see clause 4.12.2.2 of TS 23.502 [7]). Each accepted periodic registration update is added to the relevant subcounter per S-NSSAI.

d) Each subcounter is an integer value.

e) RM.RegPeriodSuccNon3GPP.SNSSAI.

Where SNSSAI identifies the S-NSSAI;

f) AMFFunction.

g) Valid for packet switched traffic.

h) 5GS.

5.2.4.7 Number of emergency registration requests via untrusted non-3GPP access

a) This measurement provides the number of emergency registration requests via untrusted non-3GPP access received by the AMF.

b) CC.

c) Receipt by the AMF from N3IWF of an N2 message that contains Registration Request with the registration type indicating an Emergency Registration (see clause 4.2.2.2.2 of TS 23.502 [7]). Each emergency registration request is added to the relevant subcounter per S-NSSAI.

d) Each subcounter is an integer value.

e) RM.RegEmergReqNon3GPP.SNSSAI.

Where SNSSAI identifies the S-NSSAI;

f) AMFFunction.

g) Valid for packet switched traffic.

h) 5GS.

5.2.4.8 Number of successful emergency registrations via untrusted non-3GPP access

a) This measurement provides the number of successful emergency registrations via untrusted non-3GPP access Transmission by the AMF to N3IWF of an N2 message that contains Registration Accept corresponding to at the AMF.

b) CC.

c) Transmission by the AMF to N3IWF of an N2 message that contains Registration Accept corresponding to an emergency registration request (see clause 4.12.2.2 of TS 23.502 [7]). Each accepted emergency registration is added to the relevant subcounter per S-NSSAI.

d) Each subcounter is an integer value.

e) RM.RegEmergSuccNon3GPP.SNSSAI.

Where SNSSAI identifies the S-NSSAI;

f) AMFFunction.

g) Valid for packet switched traffic.

h) 5GS.

5.2.5 Mobility related measurements

5.2.5.1 Inter-AMF handovers

5.2.5.1.1 Number of PDU sessions requested for inter-AMF incoming handovers

a) This measurement provides the number of PDU sessions requested for the inter-AMF incoming handovers received by target AMF. This measurement is split into subcounters per S-NSSAI.

b) CC.

c) Receipt by the target AMF from source AMF of Namf_Communication_CreateUEContext Request (see clause 4.9.1.3 of TS 23.502 [7]). Each PDU session requested in the Namf_Communication_CreateUEContext Request (see TS 29.518 [21]) increments the relevant subcounter per S-NSSAI by 1.

d) Each measurement is an integer value.

e) MM.NbrPDUReqInterAMFHOInc.SNSSAI.

Where the SNSSAI identifies the S-NSSAI.

f) AMFFunction.

g) Valid for packet switched traffic.

h) 5GS.

5.2.5.1.2 Number of PDU sessions failed to setup for inter-AMF incoming handovers

a) This measurement provides the number of PDU sessions failed to setup for inter-AMF incoming handover requests by target AMF. This measurement is split into subcounters per S-NSSAI and subcounters per failure cause.

b) CC.

c) Transmission by the target AMF to the source AMF of Namf_Communication_CreateUEContext Response (see clause 4.9.1.3 of TS 23.502 [7]) that contains the PDU Sessions failed to be setup list (including List Of PDU Sessions failed to be setup received from target RAN and the Non-accepted PDU session List generated by the T-AMF). Each PDU session failed to setup increments the relevant subcounter per S-NSSAI and the relevant subcounter per failure cause by 1 respectively.

d) Each measurement is an integer value.

e) MM.NbrPDUFailInterAMFHOInc.SNSSAI,
MM.NbrPDUFailInterAMFHOInc.cause,

Where the SNSSAI identifies the S-NSSAI, and cause identifies the failure cause (Encoding of the Cause is defined in clause 9.3.1.2 of TS 38.413 [11]).

f) AMFFunction.

g) Valid for packet switched traffic.

h) 5GS.

5.2.5.1.3 Number of QoS flows requested for inter-AMF incoming handovers

a) This measurement provides the number of QoS flows requested for inter-AMF incoming handover requests by target AMF. This measurement is split into subcounters per S-NSSAI and subcounters per 5QI.

b) CC.

c) Receipt by the target AMF from source AMF of Namf_Communication_CreateUEContext Request (see clause 4.9.1.3 of TS 23.502 [7]). Each QoS flow requested in the Namf_Communication_CreateUEContext Request (see TS 29.518 [21]) increments the relevant subcounter per S-NSSAI and the relevant subcounter per 5QI by 1 respectively.

d) Each measurement is an integer value.

e) MM.NbrQoSFlowReqInterAMFHOInc.SNSSAI,
MM.NbrQoSFlowReqInterAMFHOInc.5QI,

Where the SNSSAI identifies the S-NSSAI, and 5QI identifies the 5QI.

f) AMFFunction.

g) Valid for packet switched traffic.

h) 5GS.

5.2.5.1.4 Number of QoS flows failed to setup for inter-AMF incoming handovers

b) CC.

c) Transmission by the target AMF to the source AMF of Namf_Communication_CreateUEContext Response (see clause 4.9.1.3 of TS 23.502 [7]) that includes 1) the PDU Sessions failed to be setup list (including List Of PDU Sessions failed to be setup received from target RAN and the Non-accepted PDU session List generated by the T-AMF) and/or 2) the PDU sessions successfully setup but with the QoS flow failed to setup List. Each QoS flow corresponding to the PDU Session failed to be setup, or in the QoS flow failed to setup List of the PDU sessions successfully setup increments the relevant subcounter per S-NSSAI, the subcounter per 5QI and the subcounter per failure cause by 1 respectively.

d) Each measurement is an integer value.

e) MM.NbrQoSFlowFailInterAMFHOInc.SNSSAI,
MM.NbrQoSFlowFailInterAMFHOInc.5QI,
MM.NbrQoSFlowFailInterAMFHOInc.cause,

Where the SNSSAI identifies the S-NSSAI, 5QI identifies the 5QI and cause identifies the failure cause (Encoding of the Cause is defined in clause 9.3.1.2 of TS 38.413 [11]).

f) AMFFunction.

g) Valid for packet switched traffic.

h) 5GS.

5.2.5.2 Measurements for 5G paging

5.2.5.2.1 Number of 5G paging procedures

a) This measurement provides the number of 5G paging procedures initiated at the AMF. The initial paging procedures as well as the repeated paging procedures are counted.

b) CC.

c) Incremented when a 5G paging request is sent i.e. at the transmission of the first paging request (TS 23.502 [16] and TS 24.501 [24]).

d) A single integer value.

e) MM.Paging5GReq

f) AMFFunction

g) Valid for packet switching.

h) 5GS.

5.2.5.2.2 Number of successful 5G paging procedures

a) This measurement provides the number of successful 5G paging procedures initiated at the AMF. The initial paging procedures as well as the repeated paging procedures are counted.

b) CC.

c) When a service request from UE that with service type value equal "mobile terminated service" is received at the AMF (see TS 23.502 [7] and TS 24.501 [24]), the AMF increments the count by 1.

d) A single integer value.

e) MM.Paging5GSucc

f) AMFFunction

g) Valid for packet switching.

h) 5GS.

5.2.5.3 Handovers from 5GS to EPS

5.2.5.3.1 Number of attempted handovers from 5GS to EPS via N26 interface

a) This measurement provides the number of attempted handovers from 5GS to EPS via N26 interface.

b) CC.

c) Transmission by the AMF to the MME of a Forward Relocation Request message (see clause 4.11.1.2.1 of TS 23.502 [7]) indicating the handover request from 5GS to EPS.

d) Each measurement is an integer value.

e) MM.HoOut5gsToEpsN26Att.

f) EP_N26 (contained by AMFFunction).

g) Valid for packet switched traffic.

h) 5GS.

5.2.5.3.2 Number of successful handovers from 5GS to EPS via N26 interface

a) This measurement provides the number of successful handovers from 5GS to EPS via N26 interface.

b) CC.

c) Transmission by the AMF to the MME of a Forward Relocation Complete Notification message (see TS 29.274 [27]) indicating a successful handover from 5GS to EPS.

d) Each measurement is an integer value.

e) MM.HoOut5gsToEpsN26Succ.

f) EP_N26 (contained by AMFFunction).

g) Valid for packet switched traffic.

h) 5GS.

5.2.5.3.3 Number of failed handovers from 5GS to EPS via N26 interface

a) This measurement provides the number of failed handovers from 5GS to EPS via N26 interface. This measurement is split into subcounters per failure cause.

b) CC.

c) Receipt by the AMF from the MME of a Forward Relocation Response message (see TS 29.274 [27]) indicating a failed handover from 5GS to EPS. Each received Forward Relocation Response message increments the relevant subcounter per failure cause by 1, and failure cases are specified in TS 29.274 [27].

d) Each measurement is an integer value.

e) MM.HoOut5gsToEpsN26Fail.cause
where cause identifies the failure cause (see TS 29.274 [27])

f) EP_N26 (contained by AMFFunction).

g) Valid for packet switched traffic.

h) 5GS.

5.2.5.4 Handovers from EPS to 5GS

5.2.5.4.1 Number of attempted handovers from EPS to 5GS via N26 interface

a) This measurement provides the number of attempted handovers from EPS to 5GS via N26 interface.

b) CC.

c) Receipt by the AMF from the MME of a Forward Relocation Request message (see clause 4.11.1.2.1 of TS 23.502 [7]) indicating the handover request from EPS to 5GS.

d) Each measurement is an integer value.

e) MM.HoIncEpsTo5gsN26Att.

f) EP_N26 (contained by AMFFunction).

g) Valid for packet switched traffic.

h) 5GS.

5.2.5.4.2 Number of successful handovers from EPS to 5GS via N26 interface

a) This measurement provides the number of successful handovers from EPS to 5GS via N26 interface.

b) CC.

c) Receipt by the AMF from the MME of Forward Relocation Complete Notification message (see TS 29.274 [27]) indicating a successful handover from EPS to 5GS.

d) Each measurement is an integer value.

e) MM.HoIncEpsTo5gsN26Succ.

f) EP_N26 (contained by AMFFunction).

g) Valid for packet switched traffic.

h) 5GS.

5.2.5.4.3 Number of failed handovers from EPS to 5GS via N26 interface

a) This measurement provides the number of failed handovers from EPS to 5GS via N26 interface. This measurement is split into subcounters per failure cause.

b) CC.

c) Transmission by the AMF to the MME of a Forward Relocation Response message (see TS 29.274 [27]) indicating a failed handover from EPS to 5GS. Each transmitted Forward Relocation Response message increments the relevant subcounter per failure cause by 1, and failure cases are specified in TS 29.274 [27].

d) Each measurement is an integer value.

e) MM.HoIncEpsTo5gsN26Fail.cause
where cause identifies the failure cause (see TS 29.274 [27])

f) EP_N26 (contained by AMFFunction).

g) Valid for packet switched traffic.

h) 5GS.

5.2.6 Measurements related to Service Requests via Untrusted non-3GPP Access

5.2.6.1 Number of attempted service requests via Untrusted non-3GPP Access

a) This measurement provides the number of attempted service requests via Untrusted non-3GPP Access.

b) CC.

c) Receipt of an N2 Message indicating the Service Request by the AMF from N3IWF (see TS 23.502 [7]).

d) An integer value.

e) MM.ServiceReqNon3GPPAtt.

f) AMFFunction.

g) Valid for packet switched traffic.

h) 5GS.

5.2.6.2 Number of successful service requests via Untrusted non-3GPP Access

a) This measurement provides the number of successful service requests via Untrusted non-3GPP Access.

b) CC

c) Transmission of N2 request that contains "MM NAS Service Accept" by the AMF to N3IWF (see TS 23.502 [7]).

d) An integer value.

e) MM.ServiceReqNon3GPPSucc.

f) AMFFunction.

g) Valid for packet switched traffic.

h) 5GS.

5.2.7 Measurements related to SMS over NAS

5.2.7.1 Registration of SMS over NAS

5.2.7.1.1 Number of registration requests for SMS over NAS via 3GPP access

a) This measurement provides the number of registration requests for SMS over NAS received by the AF from UEs via 3GPP access.

b) CC

c) Receipt of a Registration Request message containing the "SMS supported" indication indicating that the UE supports SMS delivery over NAS by the AMF from UE via 3GPP access (see TS 23.502 [7]).

d) An integer value

e) SMS.SmsOverNasReg3GPPReq

f) AMFFunction

g) Valid for packet switched traffic

h) 5GS

5.2.7.1.2 Number of successful registrations allowed for SMS over NAS via 3GPP access

a) This measurement provides the number of successful registrations allowed for SMS over NAS sent by the AF to UEs via 3GPP access.

b) CC

c) Transmission of a Registration Accept message containing the "SMS allowed" indication by the AMF to UE via 3GPP access (see TS 23.502 [7]).

d) An integer value

e) SMS.SmsOverNasReg3GPPSucc

f) AMFFunction

g) Valid for packet switched traffic

h) 5GS

5.2.7.1.3 Number of registration requests for SMS over NAS via non-3GPP access

a) This measurement provides the number of registration requests for SMS over NAS received by the AF from UEs via non-3GPP access.

b) CC

c) Receipt of a Registration Request message containing the "SMS supported" indication indicating that the UE supports SMS delivery over NAS by the AMF from UE via non-3GPP access (see TS 23.502 [7]).

d) An integer value

e) SMS.SmsOverNasRegNon3GPPReq

f) AMFFunction

g) Valid for packet switched traffic

h) 5GS

5.2.7.1.4 Number of successful registrations allowed for SMS over NAS via non-3GPP access

a) This measurement provides the number of successful registrations allowed for SMS over NAS sent by the AF to UEs via non-3GPP access.

b) CC

c) Transmission of a Registration Accept message containing the "SMS allowed" indication by the AMF to UE via non-3GPP access (see TS 23.502 [7]).

d) An integer value

e) SMS.SmsOverNasRegNon3GPPSucc

f) AMFFunction

g) Valid for packet switched traffic

h) 5GS

5.2.7.2 MO SMS over NAS

5.2.7.2.1 Number of attempted MO SMS messages over NAS via 3GPP access

a) This measurement provides the number of NAS messages encapsulating the SMS messages received by the AF from UEs via 3GPP access.

b) CC

c) Receipt of an NAS message with an indication of SMS transportation by the AMF from UE via 3GPP access (see TS 23.502 [7]).

d) An integer value

e) SMS.SmsOverNasMo3GPPReq

f) AMFFunction

g) Valid for packet switched traffic

h) 5GS

5.2.7.2.2 Number of MO SMS messages successfully transported over NAS via 3GPP access

a) This measurement provides the number of MO SMS messages successfully transported over NAS via 3GPP access.

b) CC

c) Transmission, by the AMF to UE via 3GPP access, of an NAS message that contains the "submit report" indicating the MO SMS message has been successfully delivered (see TS 23.502 [7]).

d) An integer value

e) SMS.SmsOverNasMo3GPPSucc

f) AMFFunction

g) Valid for packet switched traffic

h) 5GS

5.2.7.2.3 Number of attempted MO SMS messages over NAS via non-3GPP access

a) This measurement provides the number of NAS messages encapsulating the SMS messages received by the AF from UEs via non-3GPP access.

b) CC

c) Receipt of an NAS message with an indication of SMS transportation by the AMF from UE via non-3GPP access (see TS 23.502 [7]).

d) An integer value

e) SMS.SmsOverNasMoNon3GPPReq

f) AMFFunction

g) Valid for packet switched traffic

h) 5GS

5.2.7.2.4 Number of MO SMS messages successfully transported over NAS via non-3GPP access

a) This measurement provides the number of MO SMS messages successfully transported over NAS via non-3GPP access.

b) CC

c) Transmission, by the AMF to UE via non-3GPP access, of an NAS message that contains the "submit report" indicating the MO SMS message has been successfully submitted (see TS 23.502 [7]).

d) An integer value

e) SMS.SmsOverNasMoNon3GPPSucc

f) AMFFunction

g) Valid for packet switched traffic

h) 5GS

5.2.7.3 MT SMS over NAS

5.2.7.3.1 Number of attempted MT SMS messages over NAS via 3GPP access

a) This measurement provides the number of NAS messages encapsulating the SMS messages sent by the AF to UEs via 3GPP access.

b) CC

c) Transmission of an NAS message with an indication of SMS transportation by the AMF to UE via 3GPP access (see TS 23.502 [7]).

d) An integer value

e) SMS.SmsOverNasMt3GPPReq

f) AMFFunction

g) Valid for packet switched traffic

h) 5GS

5.2.7.3.2 Number of MT SMS messages successfully transported over NAS via 3GPP access

a) This measurement provides the number of MT SMS messages successfully transported over NAS via 3GPP access.

b) CC

c) Receipt, by the AMF from UE via 3GPP access, of an NAS message that contains the "delivery report" indicating the MT SMS message has been successfully delivered (see TS 23.502 [7]).

d) An integer value

e) SMS.SmsOverNasMt3GPPSucc

f) AMFFunction

g) Valid for packet switched traffic

h) 5GS

5.2.7.3.3 Number of attempted MT SMS messages over NAS via non-3GPP access

a) This measurement provides the number of NAS messages encapsulating the SMS messages sent by the AF to UEs via non-3GPP access.

b) CC

c) Transmission of an NAS message with an indication of SMS transportation by the AMF to UE via non-3GPP access (see TS 23.502 [7]).

d) An integer value

e) SMS.SmsOverNasMtNon3GPPReq

f) AMFFunction

g) Valid for packet switched traffic

h) 5GS

5.2.7.3.4 Number of MT SMS messages successfully transported over NAS via non-3GPP access

a) This measurement provides the number of MT SMS messages successfully transported over NAS via non-3GPP access.

b) CC

c) Receipt, by the AMF from UE via non-3GPP access, of an NAS message that contains the "delivery report" indicating the MT SMS message has been successfully delivered (see TS 23.502 [7]).

d) An integer value

e) SMS.SmsOverNasMtNon3GPPSucc

f) AMFFunction

g) Valid for packet switched traffic

h) 5GS

5.2.8 UE Configuration Update procedure related measurements

5.2.8.1 Number of UE Configuration Update

a) This measurement provides the number of UE Configuration Update requested by the AMF.

b) CC

c) On transmission of Configuration Update Command from the AMF to UE (see TS 23.502 [7]).

d) Each counter is an integer value

e) MM.ConfUpdate

f) AMFFunction

g) Valid for packet switched traffic

h) 5GS

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

5.2.8.2 Number of successful UE Configuration Update

a) This measurement provides the number of UE Configuration Update successfully completed by the UE.

b) CC

c) On receipt by the AMF from the UE of Configuration Update Complete (see TS 23.502 [7]).

NOTE: Configuration Update Complete shall be requested for all parameters included in Configuration Update Command except when only NITZ is included.

d) Each counter is an integer value

e) MM.ConfUpdateSucc

f) AMFFunction

g) Valid for packet switched traffic

h) 5GS

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

5.2.9 Measurements related to registration via trusted non-3GPP access

5.2.9.1 Number of initial registration requests via trusted non-3GPP access

a) This measurement provides the number of initial registration requests via trusted non-3GPP access received by the AMF.

b) CC.

c) Receipt by the AMF from TNGF of an N2 message that contains Registration Request with the registration type indicating an initial registration (see clause 4.12.2.2 of TS 23.502 [7]). Each initial registration request is added to the relevant subcounter per network slice identifier (S-NSSAI).

d) Each subcounter is an integer value.

e) RM.RegInitReqTrustNon3GPP.SNSSAI.

Where SNSSAI identifies the network slice;

f) AMFFunction.

g) Valid for packet switched traffic.

h) 5GS.

5.2.9.2 Number of successful initial registrations via trusted non-3GPP access

a) This measurement provides the number of successful initial registrations via trusted non-3GPP access at the AMF.

b) CC.

c) Transmission by the AMF to TNGF of an N2 message that contains Registration Accept corresponding to an initial registration request (see clause 4.12.2.2 of TS 23.502 [7]). Each accepted initial registration is added to the relevant subcounter per network slice identifier (S-NSSAI).

d) Each subcounter is an integer value.

e) RM.RegInitSuccTrustNon3GPP.SNSSAI.

Where SNSSAI identifies the network slice;

f) AMFFunction.

g) Valid for packet switched traffic.

h) 5GS.

5.2.9.3 Number of mobility registration update requests via trusted non-3GPP access

a) This measurement provides the number of mobility registration update requests via trusted non-3GPP access received by the AMF.

b) CC.

c) Receipt by the AMF from TNGF of an N2 message that contains Registration Request with the registration type indicating a Mobility Registration Update (see clause 4.12.2.2 of TS 23.502 [7]). Each mobility registration update request is added to the relevant subcounter per network slice identifier (S-NSSAI).

d) Each subcounter is an integer value.

e) RM.RegMobReqTrustNon3GPP.SNSSAI.

Where SNSSAI identifies the network slice;

f) AMFFunction.

g) Valid for packet switched traffic.

h) 5GS.

5.2.9.4 Number of successful mobility registration updates via trusted non-3GPP access

a) This measurement provides the number of successful mobility registration updates via trusted non-3GPP access at the AMF.

b) CC.

c) Transmission by the AMF to TNGF of an N2 message that contains Registration Accept corresponding to a mobility registration update request (see clause 4.12.2.2 of TS 23.502 [7]). Each accepted mobility registration update is added to the relevant subcounter per network slice identifier (S-NSSAI).

d) Each subcounter is an integer value.

e) RM.RegMobSuccTrustNon3GPP.SNSSAI.

Where SNSSAI identifies the network slice;

f) AMFFunction.

g) Valid for packet switched traffic.

h) 5GS.

5.2.9.5 Number of periodic registration update requests via trusted non-3GPP access

a) This measurement provides the number of periodic registration update requests via trusted non-3GPP access received by the AMF.

b) CC.

c) Receipt by the AMF from TNGF of an N2 message that contains Registration Request with the registration type indicating a Periodic Registration Update (see clause 4.12.2.2 of TS 23.502 [7]). Each periodic registration update request is added to the relevant subcounter per network slice identifier (S-NSSAI).

d) Each subcounter is an integer value.

e) RM.RegPeriodReqTrustNon3GPP.SNSSAI.

Where SNSSAI identifies the network slice;

f) AMFFunction.

g) Valid for packet switched traffic.

h) 5GS.

5.2.9.6 Number of successful periodic registration updates via trusted non-3GPP access

a) This measurement provides the number of successful mobility registration updates via trusted non-3GPP access at the AMF.

b) CC.

c) Transmission by the AMF to TNGF of an N2 message that contains Registration Accept corresponding to a periodic registration update request (see clause 4.12.2.2 of TS 23.502 [7]). Each accepted periodic registration update is added to the relevant subcounter per network slice identifier (S-NSSAI).

d) Each subcounter is an integer value.

e) RM.RegPeriodSuccTrustNon3GPP.SNSSAI.

Where SNSSAI identifies the network slice;

f) AMFFunction.

g) Valid for packet switched traffic.

h) 5GS.

5.2.9.7 Number of emergency registration requests via trusted non-3GPP access

a) This measurement provides the number of emergency registration requests via trusted non-3GPP access received by the AMF.

b) CC.

c) Receipt by the AMF from TNGF of an N2 message that contains Registration Request with the registration type indicating an Emergency Registration (see clause 4.2.2.2.2 of TS 23.502 [7]). Each emergency registration request is added to the relevant subcounter per network slice identifier (S-NSSAI).

d) Each subcounter is an integer value.

e) RM.RegEmergReqTrustNon3GPP.SNSSAI.

Where SNSSAI identifies the network slice;

f) AMFFunction.

g) Valid for packet switched traffic.

h) 5GS.

5.2.9.8 Number of successful emergency registrations via trusted non-3GPP access

a) This measurement provides the number of successful emergency registrations via trusted non-3GPP access at the AMF.

b) CC.

c) Transmission by the AMF to TNGF of an N2 message that contains Registration Accept corresponding to an emergency registration request (see clause 4.12.2.2 of TS 23.502 [7]). Each accepted emergency registration is added to the relevant subcounter per network slice identifier (S-NSSAI).

d) Each subcounter is an integer value.

e) RM.RegEmergSuccTrustNon3GPP.SNSSAI.

Where SNSSAI identifies the network slice;

f) AMFFunction.

g) Valid for packet switched traffic.

h) 5GS.

5.2.10 Measurements related to Service Requests via trusted non-3GPP Access

5.2.10.1 Number of attempted service requests via trusted non-3GPP Access

a) This measurement provides the number of attempted service requests via trusted non-3GPP Access.

b) CC.

c) Receipt of an N2 Message indicating the Service Request by the AMF from TNGF (see TS 23.502 [7]).

d) An integer value.

e) MM.ServiceReqTrustNon3GPPAtt.

f) AMFFunction.

g) Valid for packet switched traffic.

h) 5GS.

5.2.10.2 Number of successful service requests via trusted non-3GPP Access

a) This measurement provides the number of successful service requests via trusted non-3GPP Access.

b) CC

c) Transmission of N2 request that contains "MM NAS Service Accept" by the AMF to TNGF (see TS 23.502 [7]).

d) An integer value.

e) MM.ServiceReqTrustNon3GPPSucc.

f) AMFFunction.

g) Valid for packet switched traffic.

h) 5GS.

5.2.11 Authentication procedure related measurements

5.2.11.1 Number of authentication requests

a) This measurement provides the number of authentication requests.

b) SI

c) AMF sends a NAS message Authentication -Request to the UE (see clause 6.1.3.2 in TS 33.501 [36]) to UE.

d) A single integer value

e) AMF.AuthReq

f) AMFFunction

g) Valid for packet switching

h) 5GS

5.2.11.2 Number of failed authentications due to parameter error

a) This measurement provides the number of UE sends the authentication failure message to AMF when detects error authentication parameter contained in the authentication request. b) SI

c) AMF receives a NAS message Authentication Response (see clause 6.1.3.2 in TS 33.501 [36]) sent by UE, indicating UE authentication failure. The measurement is optionally split into subcounters with a CAUSE value indicating the reason for failure. The CAUSE value may be 20, 21, 26.

d) A single integer value

e) AMF.AuthFail
AMF.AuthFail.20
AMF.AuthFail.21
AMF.AuthFail.26

f) AMFFunction

g) Valid for packet switching

h) 5GS

5.2.11.3 Number of authentication rejection

a) This measurement provides the number of authentication rejection.

b) SI

c) AMF sends a NAS message Authentication Reject to the UE (see clause 6.1.3.2 in TS 33.501 [36]) to UE.

d) A single integer value

e) AMF.AuthReject

f) AMFFunction

g) Valid for packet switching

h) 5GS