5 Mapping between 5GC interfaces causes and 5GSM Cause Codes by SMF
29.5243GPP5G SystemCause codes mapping between 5GC interfacesRelease 17Stage 3TS
5.1 General
This clause describes the mapping performed by the SMF between HTTP responses (status Code and Protocol or Application Errors) returned by NF services contacted by the SMF and the corresponding 5GSM cause values sent to UEs (in5GSMmessages).
No mapping is required for the Nsmf_PDUSession service over N11 since the SMF includes the 5GSM cause in 5GSM messages sent in N1 SM Information (see 3GPP TS 29.502 [5]).
No mapping is required for the Nsmf_PDUSession service over N16 since the 5GSM cause is generated at the H-SMF and provided to the V-SMF in N1 SM Information (see 3GPP TS 29.502 [9]).
No mapping is required for the Nsmf_EventExposure service specified in 3GPP TS 29.508 [9]
5.2 Mapping between Npcf service causes on N7 and 5GSM causes
5.2.1 General
This clause defines the mapping performed by the SMF between HTTP responses (status code and Protocol or Application Errors) returned by the PCF to the SMF and the 5GSM causes sent to UEs.
5.2.2 Mapping between Npcf_SMPolicyControl Service causes on N7 and 5GSM causes
5.2.2.1 General
This clause defines the mapping for the Npcf_SMPolicyControl service (see 3GPPTS 29.512 [6]).
5.2.2.2 Mapping from HTTP to 5GSM cause values – Request rejected by PCF
Table 5.2.2.2-1: Mapping from HTTP to 5GSM cause values – Request rejected by PCF
|
HTTP status code on N7 |
Protocol or Application Error |
5GSM cause to UE |
|
400 Bad Request |
USER_UNKNOWN |
Cause #29 – User authentication or authorization failed |
|
ERROR_INITIAL_PARAMETERS |
Cause #31 – Request rejected, unspecified |
|
|
ERROR_TRIGGER_EVENT |
Cause #31 – Request rejected, unspecified |
|
|
403 Forbidden |
ERROR_TRAFFIC_MAPPING_INFO_REJECTED |
Cause #29 – User authentication or authorization failed |
|
POLICY_CONTEXT_DENIED |
Cause #29 – User authentication or authorization failed (NOTE) |
|
|
VALIDATION_CONDITION_NOT_MET |
Cause #29 – User authentication or authorization failed |
|
|
NOTE: Upon receiving the cause POLICY CONTEXT DENIED, the SMF may reject the request, or it may accept the request based on the local policy. |
||
5.3 Mapping between Nudm service causes on N10 and 5GSM causes
5.3.1 General
This clause defines the mapping performed by the SMF between HTTP responses (status codes and Protocol or Application Errors) returned by the UDM to the SMF and the 5GSM causes sent to UEs.
5.3.2 Mapping between Nudm_UEContextManagement service causes on N10 and 5GSM causes
5.3.2.1 General
This clause defines the mapping for the Nudm_UEContextManagement service (see 3GPP TS 29.503 [5]).
5.3.2.2 Mapping from HTTP to 5GSM cause values – Request rejected by UDM due to N10 failures
Table 5.3.2.2-1: Mapping from HTTP to 5GSM cause values – Request rejected by UDM due to N10 failures
|
HTTP status code on N10 |
Protocol or Application Error |
5GSM cause to UE |
|||
|
403 Forbidden |
ROAMING_NOT_ALLOWED |
#29 "User authentication or authorization failed" |
|||
|
DNN_NOT ALLOWED |
#27 "Missing or unknown DNN" or #67 "Insufficient resources for specific slice and DNN" #70 "Missing or unknown DNN in a slice" (NOTE) |
||||
|
404 Not Found |
USER NOT FOUND |
#29 "User authentication or authorization failed" |
|||
|
NOTE: Any of those NAS Cause Code values may be sent to the UE, depending on operator’s choice. |
|||||
5.3.3 Mapping between Nudm_SubscriberDataManagement service causes on N10 and 5GSM causes
5.3.3.1 General
This clause defines the mapping for the Nudm_SubscriberDataManagement service (see 3GPP TS 29.503 [5]).
5.3.3.2 Mapping from HTTP to 5GSM cause values – Request rejected by UDM due to N10 failures
Table 5.3.3.2-1: Mapping from HTTP to 5GSM cause values – Request rejected by UDM due to N10 failures when consuming Nudm_SubscriberDataManagement service
|
HTTP status code on N10 |
Protocol or Application Error |
5GSM cause to UE |
|
404 Not Found |
USER NOT FOUND DATA_NOT_FOUND |
#29 "User authentication or authorization failed" |
|
NOTE: Any of those NAS Cause Code values may be sent to the UE, depending on operator’s choice. |
||
5.4 Mapping between N4 causes and 5GSM causes
5.4.1 General
N4 error handling and cause codes are defined in 3GPP TS 29.244 [2].
The receipt of an N4 error may trigger error handling in SMF. This clause defines the mapping performed by the SMF between when an error received on N4 interface cannot be resolved by SMF and results in the SMF sending a 5GSM message to the UE.
5.4.2 Mapping from N4 to 5GSM cause values
Table 5.4.2-1: Mapping from N4 to 5GSM cause values – Request rejected by SMF due to N4 failures
|
N4 Cause Code |
5GSM cause to UE |
||
|
Cause value Decimal |
Error description |
Cause value |
Error description |
|
64 |
Request rejected (reason not specified) |
#31 |
Request rejected, unspecified |
|
74 |
PFCP entity in congestion |
#26 #38 #69 #67 |
Insufficient resources Network Failure Insufficient resources for specific slice Insufficient resources for specific slice and DNN |
|
77 |
System failure |
#31 |
Request rejected, unspecified |
5.5 Mapping between Nnsacf services causes and 5GSM causes
5.5.1 General
This clause defines the mapping performed by the SMF between HTTP responses (Status Code and Protocol or Application Errors) returned by the NSACF to the SMF and the 5GSM cause values sent to UEs.
5.5.2 Mapping between Nnsacf_NSAC service causes on N81 and 5GSM causes
5.5.2.1 General
This clause defines the mapping for the Nnsacf_NSAC service (see 3GPP TS 29.536 [14]).
5.5.2.2 Mapping from HTTP to 5GSM Cause Values
Table 5.X.2.2-1: Mapping from HTTP to 5GSM cause values – Request rejected by NSACF
|
HTTP status code on N81 |
Protocol or Application Error |
5GSM cause to UE |
|
403 Forbidden |
ALL_SLICE_FAILED |
#69 –Insufficient resources for specific slice |
Annex A (informative):
Change history
|
Change history |
|||||||
|
Date |
Meeting |
TDoc |
CR |
Rev |
Cat |
Subject/Comment |
New version |
|
2018-10 |
CT4#86Bis |
First version of this new TS including: C4-187375 (Skeleton) C4-187378 (N11 – 5GMM) C4-187391 (N8 – 5GMM – Request rejected) C4-187589 (Scope) C4-187390 (N4 – 5GMM) |
0.1.0 |
||||
|
2018-12 |
CT4#87 |
The following agreed documents are included: C4-188418 (NSSF) C4-188484 (Nsmf_PDUSession N11 and N16) C4-188486 (Cause 5GMM) C4-188609 (N4) C4-188637 (N8 and 5GMM) C4-188638 (EIR) C4-188640 (N10 and 5GSM) C4-188641 (N7) C4-188642 (Nausf) C4-188643 (N11 5GMM) C4-188647 (Clean-up) (Conclusion from C4-188384 was wrongly reported to be included in 5GSM General Clause while it applied to 5GMM – corrected by Rapporteur). C4-188648 (General 5GSM) |
0.2.0 |
||||
|
2018-12 |
CT#82 |
CP-183104 |
Sent for information and approval |
1.0.0 |
|||
|
2018-12 |
CT#82 |
CP-183104 |
Approved in CT#82 |
15.0.0 |
|||
|
2019-03 |
CT#83 |
CP-190031 |
0001 |
2 |
F |
Corrections on cause mapping in clause 4 |
15.1.0 |
|
2019-03 |
CT#83 |
CP-190031 |
003 |
1 |
F |
Mapping between N11 causes and 5GMM causes |
15.1.0 |
|
2019-03 |
CT#83 |
CP-190031 |
0008 |
1 |
F |
Remove EN’s in 5.2.2.2 |
15.1.0 |
|
2019-03 |
CT#83 |
CP-190031 |
0004 |
2 |
F |
Corrections to 5GMM and 5GSM causes mappings |
15.1.0 |
|
2019-06 |
CT#84 |
CP-191037 |
0012 |
– |
F |
Cause mapping updates |
15.2.0 |
|
2019-06 |
CT#84 |
CP-191037 |
0013 |
1 |
F |
Correction on cause mapping regarding no subscription |
15.2.0 |
|
2019-06 |
CT#84 |
CP-191037 |
0014 |
2 |
F |
Essential Correction on Error mapping for NSSF Services |
15.2.0 |
|
2019-06 |
CT#84 |
CP-191037 |
0015 |
1 |
F |
Essential Correction on mapping for N4 to SBI |
15.2.0 |
|
2019-06 |
CT#84 |
CP-191037 |
0016 |
1 |
F |
Cause mapping corrections |
15.2.0 |
|
2019-06 |
CT#84 |
CP-191037 |
0017 |
1 |
F |
Add a mapping for N10 |
15.2.0 |
|
2019-12 |
CT#86 |
CP-193036 |
0019 |
2 |
F |
Add new mapping towards Cause #62 (No Network Slices available) |
16.0.0 |
|
2020-06 |
CT#88e |
CP-201034 |
0020 |
1 |
F |
Correction of the mapping between PCF service causes and 5GSM causes |
16.1.0 |
|
2021-03 |
CT#91e |
CP-210027 |
0022 |
1 |
D |
Use of inclusive terminology |
17.0.0 |
|
2021-03 |
CT#91e |
CP-210028 |
0023 |
1 |
F |
ERROR CONFLICTING REQUEST |
17.0.0 |
|
2021-06 |
CT#92e |
CP-211146 |
0024 |
F |
Editorial Correction |
17.1.0 |
|
|
2021-09 |
CT#93e |
CP-212230 |
0025 |
1 |
B |
Cause Mapping for NSAC |
17.2.0 |
|
2021-12 |
CT#94e |
CP-213086 |
0026 |
– |
F |
Mapping for the cause from Nudm_SubscriberDataManagement |
17.3.0 |