6.1.7 Error Handling
29.5023GPP5G SystemRelease 16Session Management ServicesStage 3TS
6.1.7.1 General
HTTP error handling shall be supported as specified in clause 5.2.4 of 3GPP TS 29.500 [4].
The Cause codes mapping performed by AMF between the following HTTP responses returned by the SMF services to the AMF and the 5GMM related values is specified in clause 4.3.2 of 3GPP TS 29.524 [34].
In order to enable the AMF to figure out whether a request (e.g. PDU session establishment request) fails at the V-SMF/I-SMF or at the H-SMF/SMF for a HR PDU session or a PDU session with an I-SMF:
– a V-SMF/I-SMF that returns an HTTP error response to the AMF that was originated by the H-SMF/SMF shall include the remoteError attribute set to "true" in the ProblemDetails information in the HTTP error response;
– a V-SMF/I-SMF that originates an error to the AMF may include the remoteError attribute set to "false" in the ProblemDetails information in the HTTP error response.
For a HR PDU session or a PDU session with an I-SMF, if the V-SMF or I-SMF needs to reject the request from the AMF or the H-SMF/SMF because the H-SMF/SMF or the AMF is not reachable respectively (even after retrying alternative endpoint addresses e.g. according to the Binding Indication when available), the V-SMF or I-SMF shall send a 504 Gateway Timeout response including a problemDetails data structure with the cause attribute set to "PEER_NOT_RESPONDING" and with the remoteError attribute set to "false".
6.1.7.2 Protocol Errors
Protocol errors handling shall be supported as specified in clause 5.2.7 of 3GPP TS 29.500 [4].
6.1.7.3 Application Errors
The common application errors defined in Table 5.2.7.2-1 of 3GPP TS 29.500 [4] may be used for the Nsmf_PDUSession service.
The following application errors listed in Table 6.1.7.3-1 are specific to the Nsmf_PDUSession service.
Table 6.1.7.3-1: Application errors
|
Application Error |
HTTP status code |
Description |
|
N1_SM_ERROR |
403 Forbidden |
This indicates that an error, other than those listed in this table, was detected when processing the N1 SM information received in the request, e.g. N1 SM protocol error. |
|
N2_SM_ERROR |
403 Forbidden |
This indicates that an error, other than those listed in this table, was detected when processing the N2 SM information received in the request, e.g. N2 SM protocol error. |
|
SNSSAI_DENIED |
403 Forbidden |
The subscriber does not have the necessary subscription to access the SNSSAI. |
|
DNN_DENIED |
403 Forbidden |
The subscriber does not have the necessary subscription to access the DNN. |
|
PDUTYPE_DENIED |
403 Forbidden |
The subscriber does not have the necessary subscription for the requested PDU session type. |
|
SSC_DENIED |
403 Forbidden |
The subscriber does not have the necessary subscription for the requested SSC mode. |
|
SUBSCRIPTION_DENIED |
403 Forbidden |
This indicates an error, other than those listed in this table, due to lack of necessary subscription to serve the UE request. |
|
DNN_NOT_SUPPORTED |
403 Forbidden |
The DNN is not supported by the SMF. |
|
PDUTYPE_NOT_SUPPORTED |
403 Forbidden |
The requested PDU session type is not supported by the SMF for the PDN corresponding to the DNN. |
|
SSC_NOT_SUPPORTED |
403 Forbidden |
The requested SSC mode is not supported by the SMF for the PDN corresponding to the DNN. |
|
HOME_ROUTED_ROAMING_REQUIRED |
403 Forbidden |
It is used in LBO roaming, if the V-SMF is not able to process some part of the N1 SM information that requires Home Routed Roaming. |
|
OUT_OF_LADN_SERVICE_AREA |
403 Forbidden |
The PDU session corresponds to a LADN and the UE is outside of the LADN Service Area. |
|
N2_SM_ERROR |
403 Forbidden |
This indicates that an error, other than those listed in this table, was detected when processing the N2 SM information received in the request, e.g. N2 SM protocol error. |
|
PRIORITIZED_SERVICES_ONLY |
403 Forbidden |
The SMF was notified that the UE is reachable only for regulatory prioritized service and the PDU Session to be activated is not for a regulatory prioritized service. |
|
PDU_SESSION_ANCHOR_CHANGE |
403 Forbidden |
The SMF decided to change the PDU Session Anchor for the PDU Session. |
|
TARGET_MME_CAPABILITY |
403 Forbidden |
A request to retrieve an SM context is rejected due to the target MME not capable to support the PDU session. |
|
NO_EPS_5GS_CONTINUITY |
403 Forbidden |
It is used during an EPS to 5GS Idle mode mobility or handover, if the PDU session does not support seamless session continuity to 5GS. |
|
UNABLE_TO_PAGE_UE |
403 Forbidden |
The request is rejected due to a temporarily inability to page the UE. |
|
UE_NOT_RESPONDING |
403 Forbidden |
The UE did not respond to the request initiated by the network, e.g. paging. |
|
REJECTED_BY_UE |
403 Forbidden |
The request is rejected by the UE. |
|
REJECTED_DUE_VPLMN_POLICY |
403 Forbidden |
The request is rejected due to VPLMN operator policy. |
|
HO_TAU_IN_PROGRESS |
403 Forbidden |
The request is rejected temporarily due to a mobilty procedure in progress. |
|
INTEGRITY_PROTECTED_MDR_NOT_ACCEPTABLE |
403 Forbidden |
The integrity protected maximum data rate value provided by the UE is not acceptable for the PDU session based on local policy at the SMF. This error is applicable when the UP Security Policy for the PDU Session is determined to have Integrity Protection set to "Required". An NF service consumer that receives this error cause may use it for maintaining KPIs. |
|
EBI_EXHAUSTED |
403 Forbidden |
The allocation of EPS Bearer ID failed due to exhaustion of EBI as the maximum number of EBIs has already been allocated to the UE. |
|
EBI_REJECTED_LOCAL_POLICY |
403 Forbidden |
The allocation of EPS Bearer ID was rejected due to local policy in the Serving PLMN. |
|
EBI_REJECTED_NO_N26 |
403 Forbidden |
The allocation of EPS Bearer ID was rejected when the AMF is in a serving PLMN that does not support 5GS-EPS interworking procedures with N26 interface. |
|
DEFAULT_EPS_BEARER_INACTIVE |
403 Forbidden |
It is used during EPS to 5GS mobility if the default EPS bearer context of the PDU session is reported as inactive by the UE in the epsBearerCtxStatus attribute. |
|
HANDOVER_RESOURCE_ALLOCATION_FAILURE |
403 Forbidden |
It is used during a N2 handover preparation or an EPS to 5GS handover preparation, if no resource is allocated by the target NG-RAN for the PDU session. |
|
LATE_OVERLAPPING_REQUEST |
403 Forbidden |
The request is rejected because it collides with an existing SM context or PDU session context with a more recent origination timestamp (see clause 5.2.3.3). |
|
DEFAULT_EBI_NOT_TRANSFERRED |
403 Forbidden |
It is used during 5GS to EPS mobility if the EBI of the default EPS bearer is included in the notToTransferEbiList attribute. |
|
NOT_SUPPORTED_WITH_ISMF |
403 Forbidden |
The request is rejected due to a requested functionality that is not supported for a PDU session with an I-SMF/V-SMF. |
|
SERVICE_NOT_AUTHORIZED_BY_NEXT_HOP |
403 Forbidden |
The SMF is not authorized to access service provided by next hop NF producer, e.g. H-SMF or SMF or old I-SMF or old V-SMF. |
|
CONTEXT_NOT_FOUND |
404 Not Found |
It is used when no context corresponding to the request exists in the SMF. |
|
HIGHER_PRIORITY_REQUEST_ONGOING |
409 Conflict |
The request is rejected temporarily due to procedure for higher priority session in progress. |
|
UE_IN_CM_IDLE_STATE |
409 Conflict |
The request is rejected due to the UE being in CM-IDLE state for the PDU session associated to non-3GPP access. |
|
INSUFFICIENT_RESOURCES_SLICE |
500 Internal Server Error |
The request cannot be provided due to insufficient resources for the specific slice. |
|
INSUFFICIENT_RESOURCES_SLICE_DNN |
500 Internal Server Error |
The request cannot be provided due to insufficient resources for the specific slice and DNN. |
|
DNN_CONGESTION |
503 Service Unavailable |
The SMF has detected congestion for the requested DNN and performs overload control for that DNN which does not allow the PDU session to be established. |
|
S_NSSAI_CONGESTION |
503 Service Unavailable |
The SMF has detected congestion for the requested S-NSSAI and performs overload control for that S-NSSAI which does not allow the PDU session to be established. |
|
PEER_NOT_RESPONDING |
504 Gateway Timeout |
No response is received from a remote peer, or the remote peer is known to be not reachable, e.g. to indicate that no response has been received from the H-SMF for a HR PDU session or the SMF for a PDU session with I-SMF. |
|
NETWORK_FAILURE |
504 Gateway Timeout |
The request is rejected due to a network problem. |
|
UPF_NOT_RESPONDING |
504 Gateway Timeout |
The request is rejected due to no response received from the UPF. |
|
UE_NOT_REACHABLE |
504 Gateway Timeout |
The UE is not reachable for service. |