C HTTP Status Codes Supported on SBI

Table C-1 HTTP Status Codes Supported on Service Based Interface (SBI)

HTTP Status Code Description
204

There is no PCF session binding information matching the query parameters.

400
  • The HTTP request contains an unsupported API name or API version in the URI.
  • The HTTP request has an invalid format.
  • The HTTP request contains an unsupported query parameter in the URI.
  • The HTTP request contains an invalid value for a mandatory parameter.
  • The HTTP request contains a semantically incorrect value for an optional parameter.
  • A mandatory query parameter is missing in the HTTP request.
  • The HTTP request contains a semantically incorrect value for a mandatory IE.
  • The HTTP request contains a semantically incorrect value for an optional IE.
  • A mandatory IE for an HTTP method is not included in the payload body of the request.
  • The request is rejected due to a malformed request.
  • The BSF found more than one binding resource. Therefore, the selected PCF cannot be provided.
401

Unauthorized With Header "WWW-Authenticate"

403 Request is forbidden.
404 The request for modification or deletion of a subscription is rejected because the subscription is not found in the NF.
405 The HTTP request is rejected as the performed operation is not allowed.
406 The request is not acceptable.
408 The request is rejected is segmented and all parts of the message are not received within the expected timeframe.
409 The request is rejected due to schema errors and conflicts in versions.
410 This requested resource has been permanently deleted.
411 The request is rejected due to the incorrect value of a Content-length header field.
412 The request is rejected due to incorrect conditions in the GET request.
413 The payload is larger than the limit.
414 The request URI is longer than the limit.
415 The HTTP request contains an unsupported payload type.
429 The request is rejected due to excessive traffic, which if continued over time, may lead to (or may increase) an overload situation.
500
  • The request is rejected due to insufficient resources.
  • The request is rejected due to unspecified reasons at the NF.
  • The request is rejected due to a generic error condition in the NF.
503 The NF experiences congestion and performs overload control that does not allow the request to be processed.
504 This error code is generated in case of timeout due to inactivity.