B Error Codes Generated by SCP

The following table describes HTTP error codes generated by SCP:

Note:

In the following table, consumer NF refers to the client, and producer NF refers to the server.

Table B-1 SCP Generated Error Codes

HTTP Status Code Protocol or Application Error Sample Error Scenarios at SCP
400 Bad Request NF_DISCOVERY_FAILURE Indicates that an empty list of NF profiles is received in the delegated NF discovery response.
400 Bad Request UNSPECIFIED_MSG_FAILURE
  • Indicates that the message could not be routed due to the unavailability of routing destinations for the incoming Inter-PLMN request after Delegated NF Discovery.
  • Indicates that the message could not be routed due to the unavailability of routing destinations for the incoming InterPlmn request with the received 3gpp-sbi-target-apiroot header.
  • Indicates that the message could not be routed because the eligible producer NF was filtered out for OCI.
400 Bad Request INVALID_ACCESS_TOKEN Indicates that the message could not be routed due to an invalid OAuth2 access token.
400 Bad Request ACCESS_TOKEN_NOT_RECEIVED Indicates that the request could not be routed because OAuth2 access token was not received from consumer NF.
400 Bad Request MISSING_ACCESS_TOKEN_INFO Indicates that the message could not be routed because the discovery headers, required to obtain the OAuth2 access token, are missing from the received request.
400 Bad Request MANDATORY_QUERY_PARAM_MISSING Indicates that the received SBI request does not contain all mandatory discovery headers required for Delegated NF Discovery.
400 Bad Request MANDATORY_IE_INCORRECT
  • Indicates that the SBI request received has a malformed 3gpp-sbi-routing-binding header.
  • Indicates that the received SBI request has imperfectly formed target PLMN.
  • Indicates that the received SBI request has a malformed default notification request.
  • Indicates that the message could not be routed due to an invalid host value received in the 3gpp-sbi-target-apiroot header.
400 Bad Request MANDATORY_IE_MISSING Indicates that the message could not be routed due to the absence of expected headers required to select a producer NF for routing.
400 Bad Request INVALID_API Indicates that the message could not be routed due to the presence of an API version in the incoming SBI request that is not supported by the producer NF, as per the learned NF profile available at SCP.
403 Forbidden ACCESS_TOKEN_DENIED Indicates that the message could not be routed due to OAuth2 access token being denied.
403 Forbidden CCA_VERIFICATION_FAILURE Indicates that the received CCA header failed validation.
404 Not Found - Indicates that the message could not be routed due to the absence of a learnt producer NF for the received 3gpp-sbi-routing-binding header and the absence of the 3gpp-sbi-target-apiroot header.
429 Too Many Requests NF_CONGESTION_RISK

This error code is sent in any of the following conditions:

  • The message could not be routed due to pod overload.
  • The message could not be routed because the ingress rate was more than the allowed rate configured for the consumer NF as specified by the rules configured in the Ingress Rate Limiter REST API.
  • The message could not be routed because the egress rate was more than the allowed rate configured for the producer NF as specified by the rules configured in the Egress Rate Limiter REST API.
431 Request Header Fields Too Large - For HTTP/2, SCP sends 431 responses with no details when the header size is greater than 8 KB.
500 Internal Server Error -
  • Indicates that an error response was received by the SCP-Worker client from the Mediation service.
  • When the response is greater than the configured value of maxPayloadSizeInKb in the ocscp_values.yaml file. For example, if maxPayloadSizeInKb value is set to 512, error 500 is received when the response size exceeds 512 Kb.
  • Indicates that the current object pool is exhausted and no streamInfo objects are available.
  • Indicates that a request is received with an incorrect value of a Content-Length header field.
  • Indicates that a request payload size (Content-Length) has exceeded the allowed threshold (256KB).
500 Internal Server Error UNSPECIFIED_NF_FAILURE
  • Indicates that a decode failure occurred when processing the response received from the mediation.
  • Indicates that the message could not be routed because the access token request from the SCP-worker to the SCP-NrfProxy-Oauth service timed out.
  • Indicates that the message could not be routed because the access token request from the SCP-worker to the SCP-NrfProxy-Oauth service encountered a transport error.
  • Indicates that the message could not be routed because the access token request from SCP-worker to SCP-NrfProxy-Oauth encountered an exception other than TimeoutException, ConnectException, or UnknownHostException.
  • Indicates that the message could not be routed because the access token request from SCP-Worker to SCP-NrfProxy-Oauth failed due to decoding exception in the access token error response body to the ProblemDetails instance.
  • Indicates that the delegated discovery request from SCP-Worker to SCP-NrfProxy failed due to an exception other than TimeoutException, ConnectException, or UnknownHostException.
  • Indicates that the delegated discovery request from SCP-Worker to SCP-NrfProxy failed due to decoding exception in the delegated NF discovery error response body to the ProblemDetails instance.
  • Indicates that the message could not be routed due to downstream task queue being full.
  • Indicates that the delegated discovery request from SCP-Worker to SCP-NrfProxy failed due to TimeoutException.
  • Indicates that the delegated discovery request from the SCP-worker to the SCP-NrfProxy service failed due to a WebClientRequestException.
  • Indicates that message could not be routed due to an exception caused failure of downstream asynchronous call.
  • Indicates that the message could not be routed due to an exception encountered on the request processing path.
  • Indicates that the message could not be routed due to an exception encountered during SBI message processing.
  • Indicates that the message could not be routed due to an exception encountered on the response processing path.
500 Internal Server Error UNKNOWN_STATUS_CODE Indicates that SCP has received a nonstandard HTTP status code from a producer NF.
500 Internal Server Error NF_SERVICE_FAILOVER
  • SCP sends this error by default when OCI is enabled, the selected producer NF is overloaded, and no alternate is available.
  • Indicates that the message could not be routed because the selected producer NF is congested and there is no other eligible producer NF available for routing.
504 Gateway Timeout TIMED_OUT_REQUEST
  • Indicates that the message could not be routed due to a response timeout at SCP, based on the 3GPP-sbi-max-rsp-time header.
  • Indicates that the message could not be routed because a TimeoutException was encountered at the Worker Client while reaching the upstream producer NF.
  • Indicates that the message could not be routed because the total transaction timeout for the service was reached.
504 Gateway Timeout TARGET_NF_NOT_REACHABLE
  • Unable to connect to the producer NF, and alternate routing is disabled (service unavailable).
    • Indicates that the message could not be routed because WebClientRequestException was encountered at the Worker Client while reaching upstream the producer NF.
    • Indicates that the message could not be routed due to an exception other than WebClientResponseException, WebClientRequestException, or TimeoutException encountered at the Worker Client while reaching upstream the producer NF.
  • HTTP2 stream resets on the upstream connection (upstream connect error or disconnect).
  • DNS resolution failure for producer NF FQDN.
  • Indicates that the message could not be routed due to an error response received from the platform service mesh.
  • Indicates that the message could not be routed because eligible producer NFs were proactively filtered due to circuit breaking, outlier detection, egress rate limiting, and so on.
508 Loop Detected - Indicates that the message could not be routed due to the presence of the SCP's self FQDN in the incoming SBI request's Via header. It also suggests that required headers or information, such as target-apiroot, binding headers, discovery headers, or any other necessary routing information, are missing from the request header.