Feature Description

SMF supports sending and receiving the ProblemDetails JSON object on the N11 interface and supports roaming.

An application error can prevent the SMF service, acting as an HTTP server, from completing the HTTP request. In this case, the SMF service maps the application error to the similar 4xx or 5xx HTTP status.

An HTTP status code determines the cause of the error. However, sometimes these status codes don't have adequate information about an error. In this case, the SMF service acting as the HTTP server provides more application-related error information to the SMF service acting as an HTTP client. This SMF service provides the additional information by including the representation of “ProblemDetails” data structure in the response body.

3GPP specification defines JSON as one of the document formats. HTTP APIs reuse this format to identify various problem types based on the requirement.

The ProblemDetails structure specified for N11 interface is sent on the N16 interface for roaming call flows on hSMF. After receiving ProblemDetails from hSMF, the vSMF rejects the corresponding message from AMF and saves the ProblemDetails that vSMF receives from hSMF.