D Error Code Dictionary

Table D-1 Error Code Dictionary for SM

App Error ID Description Cause Action
EC-OPCF-SM-REQVLD-EI-05-02-400-00009-05-01 SM Create request from SMF to PCF failed at SM Service. HTTP Status: 400 - BAD_REQUEST.

Cause: OPTIONAL_IE_INCORRECT.

Error Category: Request validation (REQVLD) 		SM Create request has optional parameters in invalid format. If sending SM Create with optional parameters, then those parameters should be in a valid format.
EC-OPCF-SM-INTRNL-EI-05-02-500-00039-05-01

SM Create request from SMF to PCF failed at SM Service

HTTP Status: 500 -INTERNAL_SERVER_ERROR

Cause: UNSPECIFIED_NF_FAILURE

Error Category: Internal (INTRNL)

The request is rejected due to unspecified reasons at the NF. Refer My Oracle Support for the guidance.
EC-OPCF-SM-REQVLD-EI-05-02-400-00048-05-01

SM Create request from SMF to PCF failed at SM Service

HTTP Status: 400 - BAD_REQUEST

Cause:ERROR_INITIAL_PARAMETERS

Error Category: Request validation (REQVLD)

SM Create requests have empty or invalid mandatory request elements Send create request with all required and valid parameters
EC-OPCF-SM-REQVLD-EI-05-02-400-00010-05-01

SM Create request from SMF to PCF failed SM Service

HTTP Status: 400 - BAD_REQUEST

Cause: MANDATORY_IE_MISSING

Error Category: Request validation (REQVLD)

SM Create request does not have mandatory elements Send create request with all required parameters

EC-OPCF-SM-REQVLD-EI-05-02-400-00011-05-01

SM Create request from SMF to PCF failed at SM Service

HTTP Status: 400 - BAD_REQUEST

Cause: UNSPECIFIED_MSG_FAILURE

Error Category: Request validation (REQVLD)

SM Create request has an invalid JSON body Send create request with valid JSON

EC-OPCF-SM-REQVLD-EI-05-02-411-00046-05-01

SM Create request from SMF to PCF failed at SM Service

HTTP Status: 411 - LENGTH_REQUIRED

Cause: INCORRECT_LENGTH

Error Category: Request validation (REQVLD)

Server (that is, PCF, specifically SM Services) rejects the request with incorrect Content-Length header. Send create request with valid JSON and content-length
EC-OPCF-SM-REQVLD-EI-05-02-400-00001-05-01

SM Create request from SMF to PCF failed at SM Service

HTTP Status: 400 -BAD_REQUEST

Cause: USER_UNKNOWN

Error Category: Request validation (REQVLD)

SM Create request has SUPI not registered with UDR and validate-user configuration is enabled in SM Policy GUI. send request with a SUPI that is registered in the UDR or disable validate-user in the SM
EC-OPCF-SM-SIG-EI-05-02-403-00022-05-01

SM Create request from SMF to PCF failed at SM Service

HTTP Status: 403 - FORBIDDEN

Cause: POLICY_CONTEXT_DENIED

Error Category: Signaling operations errors (SIG)

PCF-SM Policy evaluation returns mandatory action "Reject"SM Create request has an invalid content length for the request body check policy created, the criteria not matching for the accepting policy. correct policy/send correct request to evaluate it to "Accept"
EC-OPCF-SM-SIG-EI-05-04-404-00025-05-01

SM Delete request from SMF to PCF failed at SM Service

HTTP Status: 404 - NOT_FOUND

Cause: SUBSCRIPTION_NOT_FOUND

Error Category: Signaling operations errors (SIG)

SMF sends a Delete request with an association ID which is not associated with any existing SM session. send a Delete request with a valid association ID which is associated with the existing SM session.
EC-OPCF-SM-SIG-EI-05-02-403-00023-05-01

SM Create request from SMF to PCF failed at SM Service

HTTP Status: 403 -FORBIDDEN

Cause: LATE_OVERLAPPING_REQUEST

Error Category: Signaling operations errors (SIG)

On SMF create Collision detected with older timestamp, request rejected Refer My Oracle Support for the guidance.

EC-OPCF-SM-SIG-EI-05-03-400-00019-05-01

SM Update request from SMF to PCF failed at SM Service

HTTP Status: 400 - BAD_REQUEST

Cause: PENDING_TRANSACTION

Error Category: Signaling operations errors (SIG)

The error occurs when concurrent request arrives and Lock is already acquired by ongoing transaction in SM. Refer My Oracle Support for the guidance.
EC-OPCF-SM-INTRNL-EI-05-02-504-00069-05-01 SM request from SMF to PCF failed at SM Service

HTTP Status: 504 - GATEWAY_TIMEOUT

Cause: TIMED_OUT_REQUEST

Error Category: Internal (INTRNL) 		The request has timed out and was rejected. Verify network connectivity, retry the request, and adjust the timeout value if needed.
EC-OPCF-SM-REQVLD-EI-05-02-400-00008-05-01 SM Create request from SMF to PCF failed at SM Service

HTTP Status: 400 - BAD_REQUEST

Cause: MANDATORY_IE_INCORRECT

Error Category: Request validation (REQVLD) 		SM Create request does not have mandatory parameters as expected Send create request with all required parameters in valid format
EC-OPCF-SM-REQVLD-EI-05-02-400-00009-05-01

SM Create request from SMF to PCF failed at SM Service.

HTTP Status: 400 - BAD_REQUEST

Cause: OPTIONAL_IE_INCORRECT.

Error Category: Request validation (REQVLD)

SM Create request has optional parameters but in invalid format.

If sending SM Create with optional parameters then those parameters should be in valid format.

Table D-2 Error Code Dictionary for AM

App Error Id Description Cause Action
EC-OPCF-AM-REQVLD-EI-05-02-400-00010-06-01

The AM-Create request

from AMF to PCF failed at AM Service with

HttpStatus - 400 BAD_REQUEST

Cause - MANDATORY_IE_MISSING

Error Category: Request Validation (REQVLD)

A mandatory Information element is missing in request. Send the Create request with required parameters in the request body.
EC-OPCF-AM-REQVLD-EI-05-02-400-00011-06-01

The AM-Create request

from AMF to PCF failed at AM Service with

HttpStatus - 400 BAD_REQUEST

Cause - UNSPECIFIED_MSG_FAILURE

Error Category: Request Validation (REQVLD)

The request is rejected due to unspecified client error. Make sure the request body is in right Json format.
EC-OPCF-AM-REQVLD-EI-05-03-400-00011-06-01

The AM-Update request

from AMF to PCF failed at AM Service with

HttpStatus - 400 BAD_REQUEST

Cause - UNSPECIFIED_MSG_FAILURE

Error Category: Request Validation (REQVLD)

The request is rejected due to unspecified client error. Make sure the request body is in right Json format.
EC-OPCF-AM-REQVLD-EI-05-02-400-00048-06-01

The AM-Create request

from AMF to PCF failed at AM Service with

HttpStatus - 400 BAD_REQUEST

Cause - ERROR_INITIAL_PARAMETERS

Error Category: Request Validation (REQVLD)

A request is sent with an error in one or more of its parameters. Send the Create request with right values for the mandatory parameters.
EC-OPCF-AM-REQVLD-EI-05-02-411-00046-06-01

The AM-Create request

from AMF to PCF failed at AM Service with

HttpStatus - 411 Length Required

Cause - INCORRECT_LENGTH

Error Category: Request Validation (REQVLD)

The request is rejected because the length of a provided value does not meet the expected or required criteria. Make sure that the length of the input matches the required specifications.
EC-OPCF-AM-REQVLD-EI-05-03-411-00046-06-01

The AM-Update request

from AMF to PCF failed at AM Service with

HttpStatus - 411 Length Required

Cause - INCORRECT_LENGTH

Error Category: Request Validation (REQVLD)

The request is rejected because the length of a provided value does not meet the expected or required criteria. Make sure that the length of the input matches the required specifications.
EC-OPCF-AM-REQVLD-EI-05-02-400-00018-06-01

The AM-Create request

from AMF to PCF failed at AM Service with

HttpStatus - 400 BAD_REQUEST

Cause - ERROR_REQUEST_PARAMETERS

Error Category: Request Validation (REQVLD)

The Create request is rejected because the information set required by the PCF for AM Policy selection is incomplete, preventing a decision from being made. Make sure the required parameters are in expected format.
EC-OPCF-AM-REQVLD-EI-05-02-400-00001-06-01

The AM-Create request

from AMF to PCF failed at AM Service with

HttpStatus - 400 BAD_REQUEST

Cause - USER_UNKNOWN

Error Category: Request Validation (REQVLD)

When validate user is enabled and Create request is sent for a SUPI that is not registered in the UDR. Send the Create request with right/registered Supi.
EC-OPCF-AM-SIG-EI-05-03-404-00025-06-01

The AM-Update request

from AMF to PCF failed at AM Service with

HttpStatus - 404 Not Found

Cause - SUBSCRIPTION_NOT_FOUND

Error Category: Signaling (SIG)

When AM-Update is sent with a polAssoId that is not associated with any existing AM session. Send the Update request with right/registered Supi.
EC-OPCF-AM-SIG-EI-05-04-404-00025-06-01

The AM-Terminate request

from AMF to PCF failed at AM Service with

HttpStatus - 404 Not Found

Cause - SUBSCRIPTION_NOT_FOUND

Error Category: Signaling (SIG)

When AM-Delete is sent with a polAssoId that is not associated with any existing AM session. Send the Delete request with right/registered polAssoId.
EC-OPCF-AM-INTRNL-EI-05-02-500-00039-06-01

The AM-Create request

from AMF to PCF failed at AM Service with

HttpStatus - 500 Internal Server Error

Cause - UNSPECIFIED_NF_FAILURE

Error Category: Internal (INTRNL)

The request is rejected due to unspecified reason at the NF. Refer My Oracle Support for the guidance.
EC-OPCF-AM-INTRNL-EI-05-03-500-00039-06-01

The AM-Update request

from AMF to PCF failed at AM Service with

HttpStatus - 500 Internal Server Error

Cause - UNSPECIFIED_NF_FAILURE

Error Category: Internal (INTRNL)

The request is rejected due to unspecified reason at the NF. Refer My Oracle Support for the guidance.
EC-OPCF-AM-INTRNL-EI-05-04-500-00039-06-01

The AM-Terminate request

from AMF to PCF failed at AM Service with

HttpStatus - 500 Internal Server Error

Cause - UNSPECIFIED_NF_FAILURE

Error Category: Internal (INTRNL)

The request is rejected due to unspecified reason at the NF. Refer My Oracle Support for the guidance.
EC-OPCF-AM-SIG-EI-05-02-403-00022-06-01

The AM-Create request

from AMF to PCF failed at AM Service with

HttpStatus - 403 Forbidden

Cause - POLICY_CONTEXT_DENIED

Error Category: Signaling (SIG)

AM Create request is rejected by PRE Check and update PRE policy accordingly
EC-OPCF-AM-SIG-EI-05-03-403-00022-06-01

The AM-Update request

from AMF to PCF failed at AM Service with

HttpStatus - 403 Forbidden

Cause - POLICY_CONTEXT_DENIED

Error Category: Signaling (SIG)

AM Update request is rejected by PRE Check and update PRE policy accordingly
EC-OPCF-AM-SIG-EI-05-04-403-00022-06-01

The AM-Terminate request

from AMF to PCF failed at AM Service with

HttpStatus - 403 Forbidden

Cause - POLICY_CONTEXT_DENIED

Error Category: Signaling (SIG)

AM Terminate request is rejected by PRE Check and update PRE policy accordingly
EC-OPCF-AM-SIG-EI-05-02-403-00023-06-01

The AM-Create request

from AMF to PCF failed at AM Service with

HttpStatus - 403 Forbidden

Cause - LATE_OVERLAPPING_REQUEST

Error Category: Signaling (SIG)

The request is rejected because it collides with

an existing AM context or PDU session context

with a more recent origination timestamp.

 Refer My Oracle Support for the guidance.
EC-OPCF-AM-SIG-EI-05-03-400-00019-06-01

The AM-Update request from AMF to PCF failed at AM Service

HttpStatus - 400 Bad Request

Cause - PENDING_TRANSACTION

Error Category: Signaling (SIG)

This error shall be used when the PendingTransaction feature is supported and the PCF receives an incoming request on a policy association while it has an ongoing transaction on the same policy association. Refer My Oracle Support for the guidance.
EC-OPCF-AM-INTRNL-EI-05-02-504-00069-06-01 AM request from AMF to PCF failed at AM Service

HTTP Status: 504 - GATEWAY_TIMEOUT

Cause: TIMED_OUT_REQUEST

Error Category: Internal (INTRNL)

 The request has timed out and was rejected. Refer My Oracle Support for the guidance.

Table D-3 Error Code Dictionary for UE

App Error Id Description Cause Action
EC-OPCF-UE-REQVLD-EI-05-02-400-00010-06-01

UE Create request from AMF to PCF failed at UE Service.

HTTP Status: 400 - BAD_REQUEST

Cause: MANDATORY_IE_MISSING

Error Category: Request Validation (REQVLD)

UE Create request does not have mandatory information elements Send create request with all required parameters
EC-OPCF-UE-REQVLD-EI-05-02-400-00011-06-01

UE Create request from AMF to PCF failed at UE Service.

HTTP Status: 400 - BAD_REQUEST

Cause: UNSPECIFIED_MSG_FAILURE

Error Category: Request Validation (REQVLD)

UE Create request have invalid JSON body Send create request with valid JSON body
EC-OPCF-UE-REQVLD-EI-05-02-400-00001-06-01

UE Create request from AMF to PCF failed at UE Service.

HTTP Status: 400 - BAD_REQUEST

Cause: USER_UNKNOWN

Error Category: Request Validation (REQVLD)

UE Create request have unregistered SUPI.

Configuration: Validate user flag is enabled

Send create request with a registered SUPI
EC-OPCF-UE-REQVLD-EI-05-02-400-00018-06-01

UE Create request from AMF to PCF failed at UE Service.

HTTP Status: 400 - BAD_REQUEST

Cause: ERROR_REQUEST_PARAMETERS

Error Category: Request Validation (REQVLD)

UE Create request have empty mandatory information elements Send create request with all required and valid parameters
EC-OPCF-UE-SIG-EI-05-02-400-00019-06-01

UE Create request from AMF to PCF failed at UE Service.

HTTP Status: 400 - BAD_REQUEST

Cause: PENDING_TRANSACTION

Error Category: Signaling (SIG)

 UE Create request cannot be processed because of the pending transaction of same policy association in request. Wait for the current transaction to complete, then retry the UE Create request.
EC-OPCF-UE-SIG-EI-05-02-403-00022-06-01

UE Create request from AMF to PCF failed at UE Service.

HTTP Status: 403 - FORBIDDEN

Cause: POLICY_CONTEXT_DENIED

Error Category: Signaling (SIG)

UE Create request rejected by PRE Check and update PRE policy accordingly if needed
EC-OPCF-UE-SIG-EI-05-02-403-00023-06-01

UE Create request from AMF to PCF failed at UE Service.

HTTP Status: 403 - FORBIDDEN

Cause: LATE_OVERLAPPING_REQUEST

Error Category: Signaling (SIG)

UE Create request rejected because it collides with an existing UE context or PDU session context with more recent origination timestamp. Wait for sometime and resend UE create request
EC-OPCF-UE-REQVLD-EI-05-02-411-00046-06-01

UE Create request from AMF to PCF failed at UE Service.

HTTP Status: 411 - LENGTH REQUIRED

Cause: INCORRECT_LENGTH

Error Category: Request Validation (REQVLD)

Server (i.e. PCF, specifically UE Services) rejects the request with incorrect Content-Length header Check if Content-Length header is present in request headers and has a valid value which matches to the request body size.
EC-OPCF-UE-INTRNL-EI-05-02-500-00039-06-01

UE Create request from AMF to PCF failed at UE Service.

HTTP Status: 500 INTERNAL SERVER ERROR

Cause: UNSPECIFIED_NF_FAILURE

Error Category: Internal (INTRNL)

UE Create request failed with unexpected internal service error. Refer My Oracle Support for the guidance.
EC-OPCF-UE-REQVLD-EI-05-03-400-00011-06-01

UE Update request from AMF to PCF failed at UE Service.

HTTP Status: 400 - BAD_REQUEST

Cause: UNSPECIFIED_MSG_FAILURE

Error Category: Request Validation (REQVLD)

UE Update request have invalid JSON body Send update request with valid JSON body
EC-OPCF-UE-SIG-EI-05-03-403-00022-06-01

UE Update request from AMF to PCF failed at UE Service.

HTTP Status: 403 - FORBIDDEN

Cause: POLICY_CONTEXT_DENIED

Error Category: Signaling (SIG)

UE Update request rejected by PRE Check and update PRE policy accordingly if needed
EC-OPCF-UE-SIG-EI-05-03-403-00023-06-01

UE Update request from AMF to PCF failed at UE Service.

HTTP Status: 403 - FORBIDDEN

Cause: LATE_OVERLAPPING_REQUEST

Error Category: Signaling (SIG)

UE Update request rejected because it collides with an existing UE context or PDU session context with more recent origination timestamp. Refer My Oracle Support for the guidance.
EC-OPCF-UE-SIG-EI-05-03-404-00025-06-01

UE Update request from AMF to PCF failed at UE Service.

HTTP Status: 404 - NOT FOUND

Cause: SUBSCRIPTION_NOT_FOUND

Error Category: Signaling (SIG)

UE Update request failed because of unregistered association ID in URL. Send update request with a registered association ID
EC-OPCF-UE-REQVLD-EI-05-03-411-00046-06-01

UE Update request from AMF to PCF failed at UE Service.

HTTP Status: 411 - LENGTH REQUIRED

Cause: INCORRECT_LENGTH

Error Category: Request Validation (REQVLD)

Server (i.e. PCF, specifically UE Services) rejects the request with incorrect Content-Length header Check if Content-Length header is present in request headers and has a valid value which matches to the request body size.
EC-OPCF-UE-INTRNL-EI-05-03-500-00039-06-01

UE Update request from AMF to PCF failed at UE Service.

HTTP Status: 500 INTERNAL SERVER ERROR

Cause: UNSPECIFIED_NF_FAILURE

Error Category: Internal (INTRNL)

UE Update request failed with unexpected internal service error. Contact My Oracle Support for the guidance.
EC-OPCF-UE-SIG-EI-05-04-404-00025-06-01

UE Delete request from AMF to PCF failed at UE Service.

HTTP Status: 404 - NOT FOUND

Cause: SUBSCRIPTION_NOT_FOUND

Error Category: Signaling (SIG)

UE Delete request failed because of unregistered association ID in URL. Send update request with a registered association ID
EC-OPCF-UE-INTRNL-EI-05-04-500-00039-06-01

UE Delete request from AMF to PCF failed at UE Service.

HTTP Status: 500 INTERNAL SERVER ERROR

Cause: UNSPECIFIED_NF_FAILURE

Error Category: Internal (INTRNL)

UE Update request failed with unexpected internal service error. Refer My Oracle Support for the guidance.
EC-OPCF-UE-SIG-EI-05-08-404-00025-06-01

UE N1 notification or failure notification request from AMF to PCF failed at UE Service.

HTTP Status: 404 NOT FOUND

Cause: SUBSCRIPTION_NOT_FOUND

Error Category: Signaling (SIG)

UE N1 notification or failure notification failed due to subscription not found Send notification request with a registered association ID.
EC-OPCF-UE-INTRNL-EI-05-08-404-00000-06-01

UE N1 notification request from AMF to PCF failed at UE Service.

HTTP Status: 404 NOT FOUND

Cause: PTI does not match

Error Category: Internal (INTRNL)

UE N1 notification or failure notification failed due to PTI mismatch in the association Send notification request with a right PTI for the association.
EC-OPCF-UE-INTRNL-EI-05-08-500-00039-06-01

UE N1 notification or failure notification request from AMF to PCF failed at UE Service.

HTTP Status: 500 INTERNAL SERVER ERROR

Cause: UNSPECIFIED_NF_FAILURE

Error Category: Internal (INTRNL)

Any exception during request validation Send the right notification body
EC-OPCF-UE-INTRNL-EI-05-08-500-00000-06-01

UE N1 notification or failure notification request from AMF to PCF failed at UE Service.

HTTP Status: 500 INTERNAL SERVER ERROR

Cause: Null or Exception in processing notification request

Error Category: Internal (INTRNL)

  1. Timeout exception

    Cause: null

  2. Any other internal exception in processing notification

    Cause: Exception in processing notification request

 Please contact My Oracle Support for any guidance
EC-OPCF-UE-INTRNL-EI-05-08-403-00000-06-01

UE N1 notification request from AMF to PCF failed at UE Service.

HTTP Status: 403 Forbidden

Cause: Exception in decoding N1 NAS Message

Error Category: Internal (INTRNL)

N1 notification with incorrect NAS data. Send the right NAS message from AMF
EC-OPCF-UE-INTRNL-EI-05-02-504-00069-06-01 UE request from AMF to PCF failed at UE Service

HTTP Status: 504 - GATEWAY_TIMEOUT

Cause: TIMED_OUT_REQUEST

Error Category: Internal (INTRNL) 		The request has timed out and was rejected. Verify network connectivity, retry the request, and adjust the timeout value if needed.

Table D-4 Error Code Dictionary for UDR Connector

App Error Id Description Cause Action
EC-OPCF-UDR_C-REQVLD-EI-05-08-400-00003-03-01

The UDR notification request

from UDR to PCF failed at UDR-Connector with

httpStatus- 400 BAD_REQUEST

cause- INVALID_MSG_FORMAT

Note: Applies for UM notification as well
  1. Incorrect JSON format
  2. Empty Notification Body i.e., []
  1. Verify UDR to send the content with right JSON format
  2. Verify UDR to send the notification with notification data
EC-OPCF-UDR_C-REQVLD-EI-05-08-400-00011-03-01

The UDR notification request

from UDR to PCF failed at UDR-Connector with

httpStatus- 400 BAD_REQUEST

cause- UNSPECIFIED_MSG_FAILURE

Note: Applies for UM notification as well
  1. Null notification body i.e., no content in the body
  1. Verify UDR to send the notification with content
EC-OPCF-UDR_C-REQVLD-EI-05-08-501-00043-03-01

The UDR notification request

from UDR to PCF failed at UDR-Connector with

httpStatus- 501 Not Implemented

cause-UNSUPPORTED_MONITORED_URI

Note: Applies for UM notification as well
  1. When notification body doesn't contain at least one of the data source notification data among the below
    1. smPolicyData
    2. amPolicyData
    3. uePolicySet
    4. delResources
  1. Verify UDR to send the notification with at least one of the listed data Source information
EC-OPCF-UDR_C-EI-05-08-404-00025-03-01

The UDR notification request

from UDR to PCF failed at UDR-Connector with

httpStatus- 404 Not Found

cause- SUBSCRIPTION_NOT_FOUND

Note: Applies for UM notification as well
  1. When the notification received user session is not present in Policy-ds
  2. Session for the user is found but subscription information is missing.
 Refer My Oracle Support for the guidance.
EC-OPCF-UDR_C-INTRNL-EI-05-08-504-00069-03-01 Request from UDR to PCF failed

HTTP Status: 504 - GATEWAY_TIMEOUT

Cause: TIMED_OUT_REQUEST

Error Category: Internal (INTRNL) 		The request has timed out and was rejected. Verify network connectivity, retry the request, and adjust the timeout value if needed

Table D-5 Error Code Dictionary for CHF Connector

App Error Id Description Cause Action
EC-OPCF-CHF_C-REQVLD-EI-05-08-400-00003-04-01 The NOTIFY-POST request from CHF to PCF failed with status code 400 and cause 'INVALID_MSG_FORMAT' The request body JSON need to follow a certain format Send the POST request in the correct format.
EC-OPCF-CHF_C-REQVLD-EI-05-08-400-00010-04-01 The NOTIFY-POST request from CHF to PCF failed with status code 400 and cause 'MANDATORY_IE_MISSING' SUPI is a mandatory parameter for the POST request Send the POST request with the SUPI information present in the body.
EC-OPCF-CHF_C-REQVLD-EI-05-08-400-00011-04-01 The NOTIFY-POST request from CHF to PCF failed with status code 400 and cause 'UNSPECIFIED_MSG_FAILURE' The request body JSON needs to follow a certain format Send the POST request in the correct format.
EC-OPCF-CHF_C-SIG-EI-05-08-404-00025-04-01 The NOTIFY-POST request from CHF to PCF failed with status code 404 and cause 'SUBSCRIPTION_NOT_FOUND' The user session is not present in PolicyDS or the session for the user is found but the subscription information is missing. Refer My Oracle Support for the guidance.

EC-OPCF-CHF_C-INTRNL-EI-05-08-500-00000-04-01

 The NOTIFY-POST request from CHF to PCF failed with status code 500 and cause 'UNKNOWN' PDS responded back with status code 500 Refer My Oracle Support for the guidance.
EC-OPCF-CHF_C-INTRNL-EI-05-08-503-00000-04-01 The NOTIFY-POST request from CHF to PCF failed with status code 503 and cause 'UNKNOWN' Required service is unavailable Check whether all services are up and running
EC-OPCF-CHF_C-REQVLD-EI-05-11-400-00003-04-01 The TERMINATE-POST request from CHF to PCF failed with status code 400 and cause 'INVALID_MSG_FORMAT' The request body JSON need to follow a certain format Send the POST request in the correct format.

EC-OPCF-CHF_C-REQVLD-EI-05-04-400-00011-04-01

 The TERMINATE-POST request from CHF to PCF failed with status code 400 and cause 'UNSPECIFIED_MSG_FAILURE' The request body JSON needs to follow a certain format Send the POST request in the correct format.

EC-OPCF-CHF_C-SIG-EI-05-08-404-00025-04-01

 The TERMINATE-POST request from CHF to PCF failed with status code 404 and cause 'SUBSCRIPTION_NOT_FOUND' The user session is not present in PolicyDS or the session for the user is found but the subscription information is missing. Refer My Oracle Support for the guidance.
EC-OPCF-CHF_C-INTRNL-EI-05-08-500-00000-04-01 The TERMINATE-POST request from CHF to PCF failed with status code 500 and cause 'UNKNOWN' PDS responded back with status code 500 Refer My Oracle Support for the guidance.
EC-OPCF-CHF_C-INTRNL-EI-05-08-503-00000-04-01 The TERMINATE-POST request from CHF to PCF failed with status code 503 and cause 'UNKNOWN' Required service is unavailable Check whether all services are up and running
EC-OPCF-CHF_C-INTRNL-EI-05-08-504-00069-04-01 Request from CHF to PCF failed

HTTP Status: 504 - GATEWAY_TIMEOUT

Cause: TIMED_OUT_REQUEST

Error Category: Internal (INTRNL) 		The request has timed out and was rejected. Verify network connectivity, retry the request, and adjust the timeout value if needed

Table D-6 Error Code Dictionary for Binding

App Error Id Description Cause Action
EC-OPCF-BINDING-REQVLD-EI-05-19-500-00011-02-01

BSF Audit request

from BSF to PCF failed at Binding Service with

HttpStatus - 500 Internal Server Error

Cause - UNSPECIFIED_MSG_FAILURE

Error Category: Request Validation (REQVLD)

The request is rejected due to unspecified client error. Make sure the request body is in right Json format.
EC-OPCF-BINDING-REQVLD-EI-05-19-500-00046-02-01

BSF Audit request

from BSF to PCF failed at Binding Service with

HttpStatus - 500 Internal Server Error

Cause - INCORRECT_LENGTH

Error Category: Request Validation (REQVLD)

The request has an invalid content length for the request body Check if Content-Length header is present in request headers and has a valid value which matches to the request body size.
EC-OPCF-BINDING-SIG-EI-05-19-404-00053-02-01

BSF Audit request

from BSF to PCF failed at Binding Service with

HttpStatus - 404 Not Found

Cause - CONTEXT_NOT_FOUND

Error Category: Signaling (SIG)

 BSF Audit request is sent with a context id that is not associated with any existing Binding session. Send the request with registered context id.
EC-OPCF-BINDING-INTRNL-EI-05-19-500-00000-02-01

BSF Audit request

from BSF to PCF failed at Binding Service with

HttpStatus - 500 Internal Server Error

Cause - UNKNOWN

Error Category: Internal (INTRNL)

The request is rejected due to unknown error. Refer My Oracle Support for the guidance.

Table D-7 Error Code Dictionary for Egress Gateway

App Error Id Description Cause Action
OPCF-EGW-E001

Error Type: CONNECTION_TIMEOUT

This error code indicates that Egress Gateway is unable to establish the connection with peer NF in the configured connectionTimeout period. The server is down, or it takes too long to respond. Increase the timeout value or check if the server is up and running.
OPCF-EGW-E002

Error Type: REQUEST_TIMEOUT

This error code indicates that request processing time is more than the configured request timeout at Egress Gateway. A successful TCP connection was established, but no response was received within the expected time frame. To resolve this issue, increase the request timeout setting on the Egress Gateway or optimize the back-end services to handle the request faster.
OPCF-EGW-E003

Error Type: UNKNOWN_HOST_EXCEPTION

This error code indicates that Egress Gateway is unable to resolve the peer NF service host name. The error message indicates that Egress Gateway is unable to resolve the configured back-end service hostname. This could be due to several reasons, such as incorrect DNS settings, network issues, or misconfigured hostnames. Ensure that the hostname provided in the configuration file matches the actual hostname of the back-end service. If required, update the DNS records or configure Gateway Services to use Alternative Routing Service.
OPCF-EGW-E004

Error Type: CONNECT_EXCEPTION

This error code indicates that Egress Gateway is unable to establish the connection with peer NF service. Peer or NF service is refused due to incorrect network configuration and inactive service. Verify peer or NF service availability, network routing, and ensure that the correct IP address and port are being used.
OPCF-EGW-E005

Error Type: INVALID_HTTP_REQUEST_EXCEPTION

This error code indicates an exception occurred because HTTP1.1 is disabled, but the oc-http-version header has a value http1. The enableOutgoingHttp1 parameter of Egress Gateway is set to false. Set the enableOutgoingHTTP1 parameter in Egress Gateway config to true.
OPCF-EGW-E006

Error Type: CLOSED_CHANNEL_EXCEPTION

This error code indicates that a closed channel exception has occurred as the incoming TCP connection was abruptly terminated before Egress Gateway sent the response. Unexpected behavior is observed within the network. Capture network traces to identify the cause why the connection was terminated abruptly.
OPCF-EGW-E007

Error Type: SSL_HANDSHAKE_EXCEPTION

This error code indicates the SSL handshake exception occurred in Egress Gateway. Incorrect certificates are used to establish the connection. Use of incorrect certificates or cipher suites mismatch or TLS version incompatibility. Check certificates, Cipher suites, and TLS version match between the client and server.
OPCF-EGW-E051

Error Type: REJECTED_EXECUTION_EXCEPTION

This error code indicates that RejectedExecutionException has occurred at Egress Gateway as the number of incoming requests is more than queueCapacity configured in applicationThreadPoolConfig. Value set for the applicationThreadPoolConfig configuration in Egress Gateway is low for incoming traffic. Increase the value of applicationThreadPoolConfig in Egress Gateway Configuration or reduce the number of requests to Egress Gateway for incoming traffic.
OPCF-EGW-E052

Error Type: NOT_FOUND_EXCEPTION

This error code indicates that Egress Gateway received a request path with an endpoint that is not implemented in the peer NF service. URI of the request has not been configured in the routesConfig for Egress Gateway. Configure the required URI in routesConfig or correct the URI of the request.
OPCF-EGW-E054

Error Type: INTERNAL_ERROR

This error code indicates that some unknown internal error occurred in Egress Gateway while processing the request. NA NA
OPCF-EGW-E102

Error Type: LATE_ARRIVAL_EXCEPTION

This error code indicates that late arrival exception has occurred at Egress Gateway as the request has already expired as part of the SbiTimer feature.
  • Timezone mismatch or 12H/24H time format mismatch is leading to some time in the past in SBI Timer header for SBI Timer feature.
  • Header of MaxRspTime might have been configured with the wrong value.
  • The calculated request timeout value based on SBI Timer Headers is less than the configured requiredTime value at the route level.
 Ensure that the timestamp and maximum response time attached in the header are of the correct time with respect to the time zone and not a time in the past. Verify if the requiredTime is accommodating to the calculated timeout value from SBI Timer header values.
OPCF-EGW-E112

Error Type: NOTIFICATION_RATE_LIMIT

This error code indicates that requests are being rejected after exceeding the bucketCapacity when the notificationRateLimit feature is enabled. Request count is higher than the configured bucketCapacity at notificationRateLimit in Egress Gateway configurations. Either increase the bucketCapacity or reduce the number of requests.
OPCF-EGW-E122

Error Type: RETRY_AFTER_ERROR

This error code indicates that the retry-after feature is enabled and producer FQDN is blocklisted, therefore the request cannot be fulfilled. The RetryAfter feature is enabled, and the blackListPeriod is completed for the peer. But when the peer is accessed when it is blocklisted, this error is displayed. If not the intended behavior, disable the RetryAfter feature.
OPCF-EGW-E127

Error Type: GRACEFUL_SHUTDOWN

This error code indicates that the service shutdown is in progress. During the processing of requests, if the IP changes and DNS refresh occurs. Wait for the IP reset and DNS refresh to complete. After establishing connection to the service, try sending the request again.
OPCF-EGW-E132

Error Type: VIRTUAL_HOST_RESOLUTION_ERROR

This error code indicates that the DNS resolution of virtual FQDN failed. The vFQDN provided for the virtual host cannot be resolved by the DNS servers.
  • Verify that the vFQDN is correctly spelled and formatted.
  • Ensure that the DNS server is operational.
  • Confirm that the FQDN exists in the DNS records.
OPCF-EGW-E152

Error Type: INVALID_OAUTH_TOKEN_REQUEST

This error code indicates the exception occurred because of a bad AccessToken request received. The OAuth token received might be of the incorrect format or value. Check the correct format or value on the basis of the configurations at Egress Gateway.
OPCF-EGW-E153

Error Type: OAUTH_INTERNAL_ERROR

This error code indicates that Egress Gateway is unable to send an AccessToken request to NRF. InternalServerError because of error while processing or sending a request to NRF. NA
OPCF-EGW-E154

Error Type: OAUTH_TOKEN_RETRIEVAL_FAILURE

This error code indicates an error in retrieving a token from NRF. Error while retrieving the token from a response received from NRF. NA
OPCF-EGW-E155

Error Type: OAUTH_NRF_RESPONSE_FAILURE

This error code indicates response failure from NRF (invalid/bad response) while trying to fetch OAuth token. Error while processing the response received from NRF. NA
OPCF-EGW-E172

Error Type: EGRESS_RATE_LIMITING

This error code indicates that requests are being rejected after exceeding the bucketCapacity when the egressRateLimiting feature is enabled. The number of requests is exceeding the bucket size set in the configurations for Egress Gateway. Edit the bucket size in Egress Gateway configurations, or reduce the rate of requests.
OPCF-EGW-E182

Error Type: EGW_CUSTOM_EXCEPTION

This error code indicates that custom exception occurred in some feature at Egress Gateway because some conditions failed to fulfill at runtime, such as SbiRouting, SeppProxyFilter, PeerBlackListHelper, EgressGatewayFilter, and so on. NA Identify the error from the response received, and verify with the respective documentaiton.
OPCF-EGW-E183

Error Type: RESPONSE_STATUS_EXCEPTION

This error code indicates that ResponseStatusException was created by Spring boot as Egress Gateway exception handler was unable to handle an exception. NA NA
OPCF-EGW-E192

Error Type: PARTIAL_SHUTDOWN

This error code indicates that requests are being discarded partially at Egress Gateway when the control shutdown feature is enabled. Behavior is observed when ControlledShutdown is enabled. Disable the ControlledShutdown configuration.
OPCF-EGW-E193

Error Type: COMPLETE_SHUTDOWN

This error code indicates that requests are being discarded completely at Egress Gateway when the control shutdown feature is enabled. Behavior is observed when ControlledShutdown is enabled. Disable the ControlledShutdown configuration.
OPCF-EGW-E202

Error Type: INVALID_ROUTE_EXCEPTION

This error code indicates that an invalid route exception has occurred as invalidRouteFilter was configured in routesConfiguration. Invalid route exception filter is enabled at the route level in routesConfig. If this is unexpected behavior, check if the expected path was supposed to be marked as an invalid route.
OPCF-EGW-E206

Error Type: IP_TYPE_MISMATCH_EXCEPTION

This error code indicates that there is a mismatch in the configured EgressRoutingMode IP type and the DNS resolved IP type. The type of IP resolved by DNS is different from the IP type configured at Egress Gateway. Verify if Gateway Services is deployed in a dual stack IP setup.

Table D-8 App Error Code Dictionary for Ingress Gateway

Application Error Code ID Description Cause Action
OPCF-IGW-E001

Error Type: CONNECTION_TIMEOUT

This error code indicates that Ingress Gateway is unable to establish connection with the back-end service in the configured connectionTimeout period.

 The server is down, or it takes too long to respond. Increase the timeout value or check if the server is up and running.
OPCF-IGW-E002

Error Type: REQUEST_TIMEOUT

This error code indicates that request processing time is more than the configured request timeout at Ingress Gateway.

 A successful TCP connection was established, but no response was received within the expected time frame. To resolve this issue, increase the request timeout setting on the Ingress Gateway or optimize the back-end services to handle the request faster.
OPCF-IGW-E003

Error Type: UNKNOWN_HOST_EXCEPTION

This error code indicates that Ingress Gateway is unable to resolve the configured back-end service host name. The error message indicates that the Ingress Gateway is unable to resolve the configured back-end service hostname. This occurs due to several reasons, such as incorrect DNS settings, network issues, or misconfigured hostnames. Check if the FQDN of the back-end service is correctly resolved from the Ingress Gateway. If required, update the DNS records or configure Ingress Gateway to use alternative routing servers. Additionally, ensure that the hostname provided in the configuration file matches the actual hostname of the back-end service.
OPCF-IGW-E004

Error Type: CONNECT_EXCEPTION

This error code indicates that Ingress Gateway is unable to establish the connection with the back-end service. Peer or NF service is refused due to incorrect network configuration and inactive service. Verify peer or NF service availability, network routing, and ensure that the correct IP address and port are being used.
OPCF-IGW-E005

Error Type: BLACKLIST_IP_EXCEPTION

This error code indicates that Blocklist IP exception has occurred while establishing a new connection with the blocklisted IP at Ingress Gateway. IP is blocklisted if the TCP connection to this IP has failed more than 10 times Gateway Services is unable to establish TCP connection for more than 10 times. Verify why the IP is not accepting TCP connecitons.
OPCF-IGW-E006

Error Type: CLOSED_CHANNEL_EXCEPTION

This error code indicates that closed channel exception has occurred because the incoming TCP connection was abruptly terminated before Ingress Gateway sent back the response. Unexpected behavior is observed within the network. Capture network traces to identify the cause why the connection was terminated abruptly.
OPCF-IGW-E051

Error Type: REJECTED_EXECUTION_EXCEPTION

This error code indicates that RejectedExecutionException has occurred at Ingress Gateway as the number of incoming requests is more than the queueCapacity configured in applicationThreadPoolConfig. Value set for the applicationThreadPoolConfig configuration in Ingress Gateway is low for incoming traffic. Increase the value of applicationThreadPoolConfig in Ingress Gateway Configuration or reduce the number of requests to Ingress Gateway for incoming traffic.
OPCF-IGW-E052

Error Type: NOT_FOUND_EXCEPTION

This error code indicates that Ingress Gateway received the request path with no endpoint implemented in the back-end service. URI of the Request has not been configured in the routesConfig for Ingress Gateway. Configure the required URI in routesConfig or correct the URI of the request.
OPCF-IGW-E053

Error Type: SOCKET_EXCEPTION

This error indicates that SocketException has occurred as Ingress Gateway was unable to create a TCP connection. Due to network connectivity issues, network restrictions, or misconfigured endpoints. Verify if there are any network policies blocking the communication between the Ingress Gateway and the back-end service. Ensure that the endpoint URL provided in the configuration file is correct and reachable from Ingress Gateway.
OPCF-IGW-E054

Error Type: INTERNAL_ERROR

This error code indicates some unknown internal error occurred at Ingress Gateway while processing the request.

 Internal errors occur when there is an issue with improper configurations and mismatches in Helm charts and versions. Identify the cause from the error message sent back in the response and refer to the documentation for the specific feature that is being used and verify all the configurations. Helm charts and respective versions can be checked.
OPCF-IGW-E102

Error Type: LATE_ARRIVAL_EXCEPTION

This error code indicates that late arrival exception occurred at Ingress Gateway as the request has already expired as part of the SbiTimer feature.
  • Timezone mismatch (or) 12H/24H time format mismatch leading to some time in the past in SBI Timer
  • Header for SBI Timer Feature (or) Header of MaxRspTime might have been configured with the wrong value
  • The calculated request timeout value based on SBI Timer Headers is less than the configured required Time value at route level
 Ensure that the timestamp and maximum response time attached in the header are of the correct time with respect to the time zone and not a time in the past. Verify if the requiredTime is accommodating to the calculated timeout value from SBI Timer header values.
OPCF-IGW-E112

Error Type: USERAGENT_VALIDATION_FAILURE_EXCEPTION

This error code indicates validation of the User-Agent header failure at Ingress Gateway. The NF configured in the User-Agent header of the request does not match with the configured NFs in Ingress Gateway. Either verify if the request has the correct NF value configured, or if the intended NF has been added into the list of acceptable NFs at Ingress Gateway.
OPCF-IGW-E122

Error Type: GRACEFUL_SHUTDOWN

This error code indicates that requests received at ingress-gateway were rejected gracefully during the ingress-gateway shutdown.

 This indicates that the service or pod is shutting down, and the responses include error response. Redeploy Ingress Gateway or prevent shutdown.
OPCF-IGW-E132

Error Type: GLOBAL_RATELIMIT

This error code indicates requests are being rejected after exceeding the burstCapacity when the global ratelimit feature is enabled. Number of requests is exceeding the bucket size set in the configurations for Ingress Gateway, which is calculated on the basis of maxTokenRequest and burstCapacity. Modify the globalIngressRateLimiting parameter of Gateway Services configurations to accommodate incoming requests.
OPCF-IGW-E152

Error Type: RSS_BASED_RATELIMIT

This error code indicates that requests are being rejected after exceeding the burstCapacity when the rss ratelimit feature is enabled. When egressrateLimitingConfigMap is configured with burstCapacity and ratelimiting enabled, this exception is thrown when the requests count exceeds this burstCapacity and it is also based on the MNC and MCC values. If this is an unexpected behavior, change the values or attributes in egressrateLimitingConfigMap.
OPCF-IGW-E162

Error Type: XFCC_HEADER_VALIDATION_FAILURE

This error code indicates that validation of the XFCC header failed at Ingress Gateway.

 Indicates that the XFCC header in the request is in the correct format but is not validated as it is the wrong value for the request. Verify if the right value is updated in the XFCC header based on the Ingress Gateway deployment configuration.
OPCF-IGW-E163

Error Type: XFCC_HEADER_NOT_PRESENT_OR_EMPTY

This error code indicates that a request received at Ingress Gateway has no XFCC header or an empty XFCC header.

 XFCC Header is not present Include the XFCC Header in the Request.
OPCF-IGW-E164

Error Type: XFCC_MATCHCERTCOUNT_GREATER_THAN_CERTS_IN_HEADER

This error code indicates that the XFCC header validation failed due to XFCC certificate count mismatch in Ingress Gateway.

 Ingress Gateway configuration requires more certs than the number of certs sent in the request. Check the number of certificates in the request sent and attach the certificates matching the configuration set for Ingress Gateway.
OPCF-IGW-E165

Error Type: XFCC_HEADER_INVALID

This error code indicates that an invalid XFCC header is received at Ingress Gateway.

 XFCC Header present in the request is not of the right format. Fix the XFCC Header of the request and send.
OPCF-IGW-E171

Error Type: OAUTH_TOKEN_VALIDATION_FAILURE

This error code indicates that validation of the OAuth token failed at Ingress Gateway. The OAuth token passed with the request is enclosed with values that are incorrect with respect to the configuration present at Gateway Services. Verify and include the OAuth token with the correct set of values related to the deployed Ingress Gateway config.
OPCF-IGW-E172

Error Type: OAUTH_CERT_EXPIRED

This error code indicates that the OAuth cert that has expired is received at Ingress Gateway. Indicates that all the attributes are present and in the correct format, but the token has expired with respect to Ingress Gateway configuration. Attach an OAuth token in the request, which has not expired.
OPCF-IGW-E173

Error Type: OAUTH_MISMATCH_IN_KID

This error code indicates that OAuth mismatch occurred in KID at Ingress Gateway. Incorrect issuer and incorrect KID value is included in the request. Check the issuer attribute and KID value passed in the request.
OPCF-IGW-E173

Error Type: OAUTH_MISMATCH_IN_ALGORITHM_FOR_KID

This error code indicates that the algorithm used while generating the token does not match the configured algorithm when the oauthValidationMode is "KID_ONLY". The algorithm used while generating the token does not match the configured algorithm. Check the issuer attribute and KID value passed in the request.
OPCF-IGW-E174

Error Type: OAUTH_PRODUCER_SCOPE_NOT_PRESENT

This error code indicates that producer scope is absent in the OAuth token received at Ingress Gateway.

 Producer scope is absent in the token of the request. Check for the producer scope value in the token used in the request.
OPCF-IGW-E175

Error Type: OAUTH_PRODUCER_SCOPE_MISMATCH

This error code indicates that the producer scope present in the OAuth token mismatches with the producer scope configured at Ingress Gateway.

 The producer scope sent through the token either has a wrong format, has been used incorrectly, or an incorrect value is present. Verify the producer scope attribute of the token sent through the request.
OPCF-IGW-E176

Error Type: OAUTH_MISMATCH_IN_NRF_INSTANCEID

This error code indicates that the NRF instance ID present in the OAuth token mismatches with the NRF instance ID configured at Ingress Gateway. A wrong issuer attribute is passed along with the access token. Check the issue attribute attached along with the request.
OPCF-IGW-E176

Error Type: OAUTH_MISMATCH_IN_ALGORITHM

This error code indicates that the algorithm used while generating the token does not match the configured algorithm when the oauthValidationMode is "KID_PREFERRED" or "INSTANCEID_ONLY". The algorithm used while generating the token does not match the configured algorithm. Correct the algorithm used.
OPCF-IGW-E177

Error Type: OAUTH_PRODUCER_PLMNID_MISMATCH

This error code indicates that the received OAuth token mismatches with the producer PLMN configured at Ingress Gateway. The configured PLMN ID in Ingress Gateway is not matching with the PLMN ID received through the OAuth token. Correct the PLMN ID in the configuration for Ingress Gateway or correct the ID in the OAuth token.
OPCF-IGW-E178

Error Type: OAUTH_AUDIENCE_NOT_PRESENT_OR_INVALID

This error code indicates that the received OAuth token does not contain an audience or an invalid audience at Ingress Gateway. The token is passed with the Audience parameter containing only correct nfType but in a different case. An Audience parameter with missing or wrong values for NfType and NfInstanceId can also raise this error. Verify and include the correct NfType or NfInstanceID in the request.
OPCF-IGW-E179

Error Type: OAUTH_TOKEN_INVALID

This error code indicates that an invalid OAuth token is received at Ingress Gateway.

 Indicates that the OAuth token received at Ingress Gateway is not valid, that is, not in the correct format. Verify if the OAuth token is in the right format and configured with the right set of values with respect to the configuration at Gateway Services.
OPCF-IGW-E180

Error Type: OAUTH_TOKEN_ABSENCE

This error code indicates that a request was received at Ingress Gateway with no OAuth token or an empty OAuth token.

 The OAuth Token is missing in the request. Include the OAuth token in the request.
OPCF-IGW- E182

Error Type: IGW_OVERLOAD_CONTROL_EXCEPTION

This error code indicates that overload control exception occurred at Ingress Gateway. Occurs when the OverloadControl feature is enabled and configured at the requests per second being sent. Modify the configuration for acceptable requests per second.
OPCF-IGW-E183

Error Type: RESPONSE_STATUS_EXCEPTION

This error code indicates that ResponseStatusException was created by Spring boot as Ingress Gateway exception handler was unable to handle an exception. NA NA
OPCF-IGW-E184

Error Type: NO_RESOURCE_FOUND_EXCEPTION

This error code indicates that no route is configured for the requested URI. The invalid request URI or missing route configuration for the required route. Update the request URI or routesConfiguration.
OPCF-IGW-E191

Error Type: CCA_HEADER_VALIDATION_FAILURE

This error code indicates that validation of the CCA header failed at Ingress Gateway. The CCA header sent through the request failed while validation. Include the correct value for the CCA header in the request.
OPCF-IGW-E192

Error Type: PARTIAL_SHUTDOWN

This error code indicates that requests are being discarded partially at Ingress Gateway when the control shutdown feature is enabled.

 This behavior is observed when ControlledShutdown is enabled. Disable ControlledShutdown.
OPCF-IGW-E193

Error Type: COMPLETE_SHUTDOWN

This error code indicates that requests are being discarded at Ingress Gateway when the control shutdown feature is enabled.

 This behavior is observed when ControlledShutdown is enabled. Disable ControlledShutdown.
OPCF-IGW-E201

Error Type: IGW_OVERLOAD_CONTROL_PERCENTAGE_DISCARD

This error code indicates that requests are being rejected when the load level matches the configured percentage in the discard policy mapping of the overload control feature.

 The number of requests has reached the configured percentage for OverloadControl. When this value is reached, the respective Error Code is displayed. Change the percentage value to accommodate more requests and not to display the error code.
OPCF-IGW-E202

Error Type: IGW_OVERLOAD_CONTROL_PRIORITY_DISCARD

This error code indicates that requests with the sbi-priority header with value greater than the configured value of the discarded load level match the discard policy mapping of the overload control feature.

The number of requests has reached the configured priority for OverloadControl. When this value is reached, the respective Error Code is displayed. Change the priority value to accommodate more requests and not to display the error code.
OPCF-IGW-E211

Error Type: IGW_ROUTE_RATELIMITER_PRIORITY_DISCARD

This error code indicates that requests are being rejected when the priority level matches with the configured priority in the discard policy mapping of the route-level ratelimiting feature. Request is rejected because the priority level set in the SBI header is greater than the configured priority in the route-level rate limiting and discard policy mapping. Increase the Priority in discard policy mapping for route-level rate limiting, so requests with higher priority are accepted.
OPCF-IGW-E220

Error Type: IGW_PLMN_EGRESS_RATELIMIT

This error code indicates that requests are being rejected after exceeding the burstCapacity when the PLMN Egress Rate Limit feature is enabled. When egressrateLimitingConfigMap is configured with burstCapacity and ratelimiting enabled, this exception is thrown when the requests count exceeds this burstCapacity and it is also based on the MNC and MCC values. If this is an unexpected behavior, change the values or attributes in egressrateLimitingConfigMap.
OPCF-IGW-E221

Error Type: INVALID_ROUTE_EXCEPTION

This error code indicates that an invalid route exception has occurred as invalidRouteFilter was configured in the routesConfiguration. Invalid Route Exception is a filter enabled at the route-level in routesConfig. If this is an unexpected behavior, check the path if that is the expected path that was supposed to be marked as an invalid route.
OPCF-IGW-E223

Error Type: OAUTH_ALGORITHM_INVALID

This error code indicates that the algorithm used while generating the token is invalid. The algorithm used while generating the token is invalid. Provide a valid algorithm while generating the token.

Table D-9 Error Code Dictionary for NRF Client

App Error Id Description Cause Action
OPCF-NCMGMT-E502 NRF client generates 400 Error code with cause "BAD REQUEST" and "OPCF-NCMGMT-E502" as App Error ID. UDR SUSPENSION status change notification is with wrong version as "apiVersionInUri": "v1.0". Send UDR SUSPENSION status change notification with wrong version as "apiVersionInUri": "v1.0".
OPCF-NCMGMT-E033 NRF client generates 400 Error code with cause "BAD REQUEST" and "OPCF-NCMGMT-E033" as App Error ID. UDR SUSPENSION status change notification without any event as "event": "" . Send UDR SUSPENSION status change notification without any event as "event": "" .

Table D-10 Error Cause Diameter Connector to SM service

Diameter Error Name Diameter Result Code Response Body 'Cause' from Diameter Connector to SM
DIAMETER_UNABLE_TO_COMPLY 5012 An internal failure occurred.
DIAMETER_UNKNOWN_SESSION_ID 5002 A request is received with unknown session ID.
DIAMETER_UNABLE_TO_DELIVER 3002 Request did not delivered to the destination.
DIAMETER_TOO_BUSY 3004 An upstream peer is either in congestion or too busy to handle a request.
DIAMETER_MISSING_AVP 5005 The request did not contain an AVP that is required by the Command Code definition.
DIAMETER_COMMAND_UNSUPPORTED 3001 The Request contained a Command-Code that the receiver did not recognize or support.
DIAMETER_LOOP_DETECTED 3005 An agent detected a loop while trying to get the message to the intended recipient.
DIAMETER_UNSUPPORTED_VERSION 5011 A request was received, whose version number is unsupported.
DIAMETER_AVP_OCCURS_TOO_MANY_TIMES 5009 A message was received that included an AVP that appeared more often than permitted in the message definition.
DIAMETER_AVP_UNSUPPORTED 5001 The peer received a message that contained an AVP that is not recognized or supported and was marked with the Mandatory bit.
DIAMETER_INVALID_AVP_VALUE 5004 The request contained an AVP with an invalid value in its data portion.
DIAMETER_INVALID_AVP_LENGTH 5014 The request contained an AVP with an invalid length.
DIAMETER_INVALID_HDR_BITS 3008 A request was received whose bits in the Diameter header were either set to an invalid combination, or to a value that is inconsistent with the command code definition.
DIAMETER_INVALID_AVP_BITS 3009 A request was received that included an AVP whose flag bits are set to an unrecognized value, or that is inconsistent with the AVP definition.

Table D-11 Diameter Result Codes from TDF toward SM service

Diameter Result Code HTTP Response Code Diameter Connector Response Body
DIAMETER_SUCCESS 200 No response body
DIAMETER_MISSING_AVP / DIAMETER_UNABLE_TO_COMPLY / DIAMETER_UNABLE_TO_DELIVER / DIAMETER_TOO_BUSY / DIAMETER_LOOP_DETECTED/ DIAMETER_APPLICATION_UNSUPPORTED 500 

{
      "type": null,
      "title": "INTERNAL_SERVER_ERROR",
      "status": 500,
      "detail": "Error Occurred",
      "instance": null,
      "cause": "<Mapping of Diameter Result Code with Cause is provided in below table>",
      "invalidParams": null
}
DIAMETER_UNKNOWN_SESSION_ID 404 

{
      "type": null,
      "title": "NOT_FOUND",
      "status": 404,
      "detail": "Session Does not Exist",
      "instance": null,
      "cause": "A request is received with unknown session ID.",
      "invalidParams": null
}

Table D-12 HTTP Result Codes from SM service toward TDF

HTTP Response Code Diameter Result Code
204/200 DIAMETER_SUCCESS
500 DIAMETER_UNABLE_TO_COMPLY
503 DIAMETER_UNABLE_TO_COMPLY
400 DIAMETER_UNABLE_TO_COMPLY
404 DIAMETER_UNKNOWN_SESSION_ID

Table D-13 Cause Codes

Error Cause Code
UNKNOWN 00000
USER_UNKNOWN 00001
INVALID_API 00002
INVALID_MSG_FORMAT 00003
INVALID_QUERY_PARAM 00004
MANDATORY_QUERY_PARAM_INCORRECT 00005
OPTIONAL_QUERY_PARAM_INCORRECT 00006
MANDATORY_QUERY_PARAM_MISSING 00007
MANDATORY_IE_INCORRECT 00008
OPTIONAL_IE_INCORRECT 00009
MANDATORY_IE_MISSING 00010
UNSPECIFIED_MSG_FAILURE 00011
PCC_RULE_EVENT 00012
UE_STATUS_SUSPEND 00013
RULE_TEMPORARY_ERROR 00014
PCC_QOS_FLOW_EVENT 00015
NO_AVAILABLE_POLICY_COUNTERS 00016
UNKNOWN_POLICY_COUNTERS 00017
ERROR_REQUEST_PARAMETERS 00018
PENDING_TRANSACTION 00019
ERROR_TRIGGER_EVENT 00020
WWW_AUTHENTICATE 00021
POLICY_CONTEXT_DENIED 00022
LATE_OVERLAPPING_REQUEST 00023
UPDATE_NOT_ALLOWED 00024
SUBSCRIPTION_NOT_FOUND 00025
USER_NOT_FOUND 00026
DATA_NOT_FOUND 00027
RESOURCE_URI_STRUCTURE_NOT_FOUND 00028
METHOD_NOT_ALLOWED 00029
NOT_ACCEPTABLE 00030
CONFLICT 00031
GONE 00032
LENGTH_REQUIRED 00033
PRECONDITION_FAILED 00034
PAYLOAD_TOO_LARGE 00035
URI_TOO_LONG 00036
UNSUPPORTED_MEDIA_TYPE 00037
INSUFFICIENT_RESOURCES 00038
UNSPECIFIED_NF_FAILURE 00039
SYSTEM_FAILURE 00040
NF_FAILOVER 00041
DATABASE_INCONSISTENCY 00042
UNSUPPORTED_MONITORED_URI 00043
NF_CONGESTION 00044
NF_CONGESTION_RISK 00045
INCORRECT_LENGTH 00046
GATEWAY_TIMEOUT 00047
ERROR_INITIAL_PARAMETERS 00048
BULWARK_SERVICE_ERROR 00049
OPTIONAL_IE_MISSING 00050
INVALID_MESSAGE_FORMAT 00051
APP_IN_CONGESTION_STATE 00052
CONTEXT_NOT_FOUND 00053
BULWARK_ALREADY_LOCKED 00054
BULWARK_SERVICE_UNREACHABLE 00055
INTERNAL_SERVER_ERROR 00056
BAD_REQUEST 00057
UNAUTHORIZED 00058
FORBIDDEN 00059
NOT_FOUND 00060
REQUEST_TIMEOUT 00061
TOO_MANY_REQUESTS 00062
ERROR_4XX 00063
SERVICE_UNAVAILABLE 00064
ERROR_5XX 00065
BINDING_SERVICE_ERROR 00066
INSUFFICIENT_RESOURCES_SLICE 00067
REQUESTED_SERVICE_TEMPORARILY_NOT_AUTHORIZED 00068
TIMED_OUT_REQUEST 00069