4 Mapping between 5GC interfaces causes and 5GMM Cause Codes by AMF

29.5243GPP5G SystemCause codes mapping between 5GC interfacesRelease 17Stage 3TS

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

4.1 General

This clause defines the mapping performed by the AMF between HTTP responses (status codes and Protocol or Application Errors) returned by NF services contacted by the AMF and the5GMM cause values sent to UEs.

No mapping is required for:

– the Nsmsf_SMService_Activate, Nsmsf_SMService_Deactivate and Nsmsf_SMService_UplinkSMS operations described in 3GPP TS 29.540 [10].

– the Npcf_AMPolicyControl service operations described in 3GPP TS 29.507 [12].

– the Npcf_UEPolicyControl service operations described in 3GPP TS 29.525 [13].

4.2 Mapping between Nausf services causes and 5GMM causes

4.2.1 General

This clause defines the mapping performed by the AMF between HTTP responses (status codes and Protocol or Application Errors) returned by AUSF services to the AMF and the 5GMM cause values sent to UEs.

4.2.2 Mapping between Nausf_UEAuthentication service causes on N12 and 5GMM causes

4.2.2.1. General

This clause defines the mapping for the Nausf_UEAuthentication service (see 3GPP TS 29.509 [7]). It also contains the mapping in case of a 200 OK is returned but the Authentication has failed.

4.2.2.2 Mapping from HTTP to 5GMM causes values – Request rejected by AUSF

Table .4.2.2-1: Mapping from HTTP to 5GMM cause values – Request rejected by AUSF

HTTP status code on N12	Protocol or Application Error	5GMM cause to UE
403 Forbidden	SERVING_NETWORK_NOT_AUTHORIZED	Cause #11 – PLMN not allowed Cause #73 – Serving network not authorized Cause #12 – Tracking area not allowed Cause #15 – No suitable cells in tracking area (NOTE1)
	AUTHENTICATION_REJECTED	N/A (NOTE 2)
	INVALID_HN_PUBLIC_KEY_IDENTIFIER	N/A (NOTE 2)
	INVALID_HN_PUBLIC_KEY_IDENTIFIER	N/A (NOTE 2)
404 Not Found	CONTEXT_NOT_FOUND	N/A (NOTE 2)
	USER_NOT_FOUND	N/A (NOTE 2)
504 Gateway Timeout	UPSTREAM_SERVER_ERROR	N/A (NOTE 2)
504 Gateway Timeout	NETWORK_FAILURE	N/A (NOTE 2)
500 Internal Server Error	AV_GENERATION_PROBLEM	N/A (NOTE 2)
501 Not Implemented	UNSUPPORTED_PROTECTION_SCHEME	N/A (NOTE 2)
NOTE 1: .One of these 5GMM causes may be used. NOTE 2: There is no corresponding mapping since the Authentication is rejected and the Authentication Reject message does not have a 5GMM cause.

4.2.2.3 Mapping from HTTP to 5GMM cause values – Request accepted by AUSF

Table .4.2.2.3-1: Mapping from HTTP to 5GMM cause values – Request accepted by AUSF

HTTP status code on N12	Protocol or Application Error	5GMM cause to UE
200 OK	The "authResult" in "ConfirmationDataResponse" is set to "AUTHENTICATION_FAILURE" (see clause 6.1.6.2.8 of 3GPP TS 29.509 [7]).	Cause #3 – Illegal UE
200 OK	The "authResult" in "EapSession" is set to "AUTHENTICATION_FAILURE" (see clause 6.1.6.2.8 of 3GPP TS 29.509 [7]).	Cause #3 – Illegal UE

4.3 Mapping between Nsmf services causes and 5GMM causes

4.3.1 General

This clause defines the mapping performed by the AMF between HTTP responses (status codes and Protocol or Application Errors) returned by SMF services to the AMF and the 5GMM cause values sent to UEs.

The AMF may invoke SMF service operations upon receipt of:

– 5GSM messages (e.g. PDU Session establishment request) piggybacked in 5GMM UL NAS TRANSPORT message;

– 5GMM Service Request or Registration Request messages, to establish the user-plane resources of a PDU session.

A 5GMM cause is defined in:

– the DL NAS TRANSPORT message;

– the PDU session reactivation result error cause IE of a REGISTRATION ACCEPT or SERVICE ACCEPT message;

– the REGISTRATION REJECT or SERVICE REJECT message.

The AMF shall support mapping the status code and/or Protocol or Application Error received from the SMF to a 5GMM cause code, where 3GPP TS 24.501 [3] requires a 5GMM Cause to be included in the 5GMM message sent to the UE.

NOTE: REGISTRATION REJECT and SERVICE REJECT messages are rejected only due to 5GMM-specific reasons, i.e. not for problems specific to session management.

4.3.2 Mapping between Nsmf_PDUSession service causes on N11 and 5GMM causes

4.3.2.1 General

This clause defines the mapping for the Nsmf_PDUSession service (see 3GPP TS 29.502 [8]).

4.3.2.2 Mapping from HTTP to 5GMM Cause Values

Table 4.3.2.2-1: Mapping from HTTP to 5GMM cause values – Request rejected by SMF

HTTP status code on N11	Protocol or Application Error	5GMM cause to UE
200 OK	The upCnxState IE is set to DEACTIVATED and the Cause IE set to "INSUFFICIENT_UP_RESOURCES" (see clause 5.2.2.3.2.2 of 3GPP TS 29.502 [8]) (NOTE 2)	#92 – Insufficient user-plane resources for the PDU session
403 Forbidden	OUT_OF_LADN_SERVICE_AREA	#43 – LADN not available
403 Forbidden	PRIORITIZED_SERVICES_ONLY	#28 – Restricted service area
404 Not Found	CONTEXT_NOT_FOUND	N/A (NOTE 1)




504 Gateway Timeout	NETWORK_FAILURE	N/A (NOTE 1)
NOTE 1: An N1 SM cause is included by the SMF in the HTTP error response in this case. NOTE 2: This corresponds to the scenario where NG-RAN cannot establish user plane resources during the activation of the User Plane connection of a PDU session.

4.4 Mapping between Nudm services causes and 5GMM causes

4.4.1 General

This clause defines the mapping performed by the AMF between HTTP responses (status codes and Protocol or Application Errors) returned by UDM services to AMF and the 5GMM cause values sent to UEs.

4.4.2 Mapping between Nudm_UEContextManagement service causes on N8 and 5GMM causes

4.4.2.1 General

This clause defines the mapping for the Nudm_UEContextManagement service is described in 3GPP TS 29.503 [5]).

4.4.2.1 Mapping from HTTP to NAS cause values – Request rejected by UDM

Table 4.4.2.1-1: Mapping from HTTP to 5GMM cause values – Request rejected by UDM

HTTP status code on N8	Protocol or Application Error	5GMM cause to UE
403 Forbidden	UNKNOWN_5GS_SUBSCRIPTION	#27 – N1 mode not allowed
	ACCESS_NOT_ALLOWED	#15 "No suitable cells in tracking area", or #12 "Tracking area not allowed" or #72 – Non-3GPP access to 5GCN not allowed (NOTE)
	RAT_NOT ALLOWED	#15 "No suitable cells in tracking area", or #13 "Roaming not allowed in this tracking area", or #12 "Tracking area not allowed" (NOTE)
	NO_PS_SUBSCRIPTION	#7 – 5GS services not allowed
	ROAMING_NOT_ALLOWED	#11 "PLMN not allowed" or #13 "Roaming not allowed in this tracking area", (NOTE)
404 Not Found	CONTEXT_NOT_FOUND	#9 "UE identity cannot be derived by the network"
404 Not Found	USER_NOT_FOUND	#3 "Illegal UE"
422 Unprocessable Entity	UNPROCESSABLE_REQUEST	#111 protocol error unspecified
NOTE: Any of those NAS Cause Code values may be sent to the UE, depending on operator’s choice.

4.4.3 Mapping between Nudm_SubscriberDataManagement service causes on N8 and 5GMM causes

4.4.3.1 General

This clause defines the mapping for the Nudm_SubscriberDataManagement service is described in 3GPP TS 29.503 [5]).

4.4.3.2 Mapping from HTTP to NAS cause values – Request rejected by UDM due to N8 failure

Table 4.4.x.2-1: Mapping from HTTP to 5GMM cause values – Request rejected by UDM due to N8 failures when consuming Nudm_SubscriberDataManagement service

HTTP status code on N8

Protocol or Application Error

5GMM cause to UE

404 Not Found

USER_NOT_FOUND

DATA_NOT_FOUND

#3 "Illegal UE"

#27 "N1 mode not allowed"

NOTE: Any of those NAS Cause Code values may be sent to the UE, depending on operator’s choice.

4.5 Mapping between Neir services causes and 5GMM causes

4.5.1 General

This clause defines the mapping performed by the AMF between HTTP responses (status code and Protocol or Application Errors) returned by the EIR to the AMF and the 5GMM cause values sent to UEs.

4.5.2 Mapping between N5g-eir_EquipmentIdentityCheck Service causes on N17 and 5GMM causes

4.5.2.1 General

This clause defines the mapping for the N5g-eir_EquipmentIdentityCheck service (see 3GPP TS 29.511 [11]).

4.5.2.2 Mapping from HTTP to NAS cause values – Request accepted by EIR

Table 4.5.2.2-1: Mapping from HTTP to 5GMM cause values – Request accepted by EIR

HTTP Status on N17	Protocol or Application information	5GMM cause to UE
200 OK	Equipment Status is set to "BLACKLISTED", which indicates that the equipment is in the prohibited list.	#6 "Illegal ME"

4.6 Mapping between Nnssf services causes and 5GMM causes

4.6.1 General

This clause defines the mapping performed by the AMF between HTTP responses (Status Code and Protocol or Application Errors) returned by the NSSF to the AMF and the 5GMM cause values sent to UEs.

4.6.2 Mapping between Nnssf_NSSelection service causes on N22 and 5GMM causes

4.6.2.1 General

This clause defines the mapping for the Nnssf_NSSelection service (see 3GPP TS 29.531 [4]).

4.6.2.2 Mapping from HTTP to 5GMM Cause Values

Table 4.6.2.2-1: Mapping from HTTP to 5GMM cause values – Request rejected by NSSF

HTTP status code on N22	Protocol or Application Error	5GMM cause to UE
403 Forbidden	SNSSAI_NOT_SUPPORTED	#62 – No Network Slices available