HTTP Error Codes Supported by Policy

C HTTP Error Codes Supported by Policy

HTTP Error Codes supported by Policy for AM, SM, and UE Interfaces

Table C-1 HTTP Error codes and cause supported by Policy for AM, SM, and UE Interfaces for Notification

Error Code-Message	Cause Code	Description	Action
400 - Bad requests	INVALID_MSG_FORMAT	The HTTP request has an invalid format.	POST retry with POST request If retry is exhausted, then terminate the transaction.
400 - Bad requests	INVALID_QUERY_PARAM	The HTTP request contains an unsupported query parameter in the URI.	`invalidParams` attribute is included in the `ProblemDetails`data structure indicating unsupported.
400 - Bad requests	MANDATORY_IE_INCORRECT	A mandatory IE for an HTTP method received a semantically incorrect request.	POST retry with POST request If retry is exhausted, then terminate the transaction.
400 - Bad requests	MANDATORY_QUERY_PARAM_INCORRECT	A mandatory query parameter, or a conditional query parameter, but mandatory required for an HTTP method was received in the URI with semantically incorrect value.
400 - Bad requests	OPTIONAL_QUERY_PARAM_INCORRECT	An optional query parameter for an HTTP method was received in the URI with asemantically incorrect value that prevents successful processing of the service request.
400 - Bad requests	MANDATORY_QUERY_PARAM_MISSING	Query parameter which is defined as mandatory, or as conditional but mandatory required for a HTTP method is not included in the URI of the request.
400 - Bad requests	MANDATORY_IE_MISSING	A mandatory IE for an HTTP method is not included in the request.	POST retry with POST request If retry is exhausted, then terminate the transaction.
400 - Bad requests	UNSPECIFIED_MSG_FAILURE	The request is rejected due to unspecified client error.	POST retry with POST request If retry is exhausted, then terminate the transaction.
400 - Bad requests	ERROR_REQUEST_PARAMETERS	The HTTP request is rejected because the set of information needed by the PCF for UE Policy selection is incomplete for the decision to be made.	POST retry with POST request If retry is exhausted, then terminate the transaction.
400 - Bad requests	OPTIONAL_IE_INCORRECT	An optional IE for a HTTP method was received with a semantically incorrect value that prevents successful processing of the service request.
400 - Bad requests	USER_UNKNOWN	The HTTP request is rejected because either the end user specified in the request is unknown to the PCF or when a error occurs in PCF and the validate User flag is set as `true`.
401- Unauthorized	With header "WWW-Authenticate"	There will be a new function to enable retry for this error code.	POST retry with POST request If retry is exhausted, terminate the transaction
403-Forbidden	MODIFICATION_NOT_ALLOWED	The request is rejected because modification is not allowed.	POST retry with POST request If retry is exhausted, terminate the transaction
404 - Not Found	SUBSCRIPTION_NOT_FOUND	The request for modification or deletion of subscription is rejected because the subscription is not found in the NF.	POST retry with POST request If retry is exhausted, delete the session
404 - Not Found	RESOURCE_URI_STRUCTURE_NOT_FOUND	The request is rejected because a fixed part after the first variable part of an "apiSpecificResourceUriPart" is not found in the NF.	POST retry with POST request If retry is exhausted, delete the session
405 - Method Not Allowed	NA	If the NF supports the HTTP method for several resources in the API, but not for the target resource of a given HTTP request	POST retry with POST request If retry is exhausted, terminate the transaction
406 - Not Acceptable	NA	The server cannot generate a response in a format specified as acceptable by the client in the "Accept" headers.	POST retry with POST request If retry is exhausted, terminate the transaction
408 - Request Timeout	NA	The server did not receive a complete request from the client within the expected time frame.	POST retry with POST request If retry is exhausted, terminate the transaction
409 - Conflict	NA	The server did not receive a complete request from the client within the expected time frame.	POST retry with POST request If retry is exhausted, terminate the transaction
410 - Gone	NA	The server did not receive a complete request from the client within the expected time frame.	POST retry with POST request If retry is exhausted, terminate the transaction
411 - Length Required	INCORRECT_LENGTH	The request is rejected due to incorrect value of a Content-length header field.	POST retry with POST request If retry is exhausted, terminate the transaction
412 - Precondition Failed	NA	One or more preconditions specified in the request headers were not met.	POST retry with POST request If retry is exhausted, terminate the transaction
413 - Payload Too Large	NA	The server refuses to process the request because the payload size exceeds its limitations.	POST retry with POST request If retry is exhausted, terminate the transaction
414 - URI Too Long	NA	The server cannot process the request because the provided URI exceeds its maximum length limit.	POST retry with POST request If retry is exhausted, terminate the transaction
415 - Unsupported Media Type	NA	The server cannot process the request due to an unsupported media type in the request payload.	POST retry with POST request If retry is exhausted, terminate the transaction
429 - Too Many Requests	NF_CONGESTION_RISK	The request is rejected due to excessive traffic which, if continued over time, may lead to (or may increase) an overload situation.	POST retry with POST request If retry is exhausted, terminate the transaction
500 -Internal Server Error	INSUFFICIENT_RESOURCES	The request is rejected due to insufficient resources.	POST retry with POST request If retry is exhausted, terminate the transaction
500 - Internal Server Error	UNSPECIFIED_NF_FAILURE	The request is rejected due to unspecified reason at the NF.	POST retry with POST request If retry is exhausted, terminate the transaction
500 - Internal Server Error	SYSTEM_FAILURE	The request is rejected due to generic error condition in the NF.	POST retry with POST request If retry is exhausted, terminate the transaction
500 -Internal Server Error	NF_FAILOVER	The request is rejected due to generic error condition in the NF.	POST retry with POST request If retry is exhausted, terminate the transaction
503 - Server temporarily unavailable	NF_CONGESTION	The NF experiences congestion and performs overload control, which does not allow the request to be processed.	POST retry with POST request If retry is exhausted, terminate the transaction

Policy as a producer of Error to AM Interface

Table C-2 Policy as a producer of Error to AM Interface

Message	Cause Code	Description
400 - Bad request	MANDATORY_IE_INCORRECT	When the SUPI was incorrectly written into the request body and sent to Ingress.
400 - Bad request	MANDATORY_IE_MISSING	When a request is sent without a mandatory IE (SUPI) in the request body.
400 - Bad request	UNSPECIFIED_MSG_FAILURE	When there is malformed JSON object.
400 - Bad request	USER_UNKNOWN	A correct request is sent with a SUPI that is not registered in the UDR. The validate-user in the CNC Console of the UE Policy is activated.
400 - Bad request	ERROR_REQUEST_PARAMETERS	When there is malformed JSON object.
400 - Bad request	PENDING_TRANSACTION	In case of Pending transaction.
401 - Unauthorized	With header "WWW-Authenticate"	Supported by Gateway service.
403 - Forbidden	MODIFICATION_NOT_ALLOWED	Supported by Gateway service.
404 - Not Found	SUBSCRIPTION_NOT_FOUND	When UE-Delete is sent with a polAssoId that does not exist in the database.
404 - Not Found	RESOURCE_URI_STRUCTURE_NOT_FOUND	When resource URI structure is not found.
408 - Request Timeout	NA	Supported by Gateway service.
411 - Length Required	INCORRECT_LENGTH	Incorrect length.
429 - Too Many Requests	NF_CONGESTION_RISK	When there is congestion risk in the NF.
500 - Internal Server Error	UNSPECIFIED_NF_FAILURE	When an unexpected error occurs within the service.
503 - Service Unavailable	NF_CONGESTION	Supported by Gateway service.

Policy as a producer of Error to SM

Table C-3 Policy as a producer of Error to SM

Message	Cause Code	Description
400 - Bad request	MANDATORY_IE_MISSING	A request is sent without a mandatory IE (SUPI) in the request body.
400 - Bad request	UNSPECIFIED_MSG_FAILURE	malformed json object.
400 - Bad request	USER_UNKNOWN	A correct request is sent, with a SUPI that is not registered in the UDR. We activate the validate-user in the UE Policy GUI.
400 - Bad request	ERROR_INITIAL_PARAMETERS	A request is sent with an error in one or more of its parameters
400 - Bad request	PENDING_TRANSACTION	This error shall be used when the PendingTransaction feature is supported and the AMF receives an incoming request on a policy association while it has an ongoing transaction on the same policy association.
401- Unauthorized	With header "WWW-Authenticate"	Supported by Gateway service.
403 - Forbidden	MODIFICATION_NOT_ALLOWED	Supported by Gateway service.
403 - Forbidden	POLICY_CONTEXT_DENIED	When an error occurs in PRE service.
403 - Forbidden	LATE_OVERLAPPING_REQUEST	The request is rejected because it collides with an existing SM context or PDU session context with a more recent origination timestamp.
404 - Not Found	SUBSCRIPTION_NOT_FOUND	When UE-Delete is sent with a polAssoId that does not exist in the database.
404 - Not Found	RESOURCE_URI_STRUCTURE_NOT_FOUND	This error is being handled by IGW, never reaches the core service, send 404 Not Found without cause.
408 - Request Timeout	NA	Supported by Gateway service.
411 - Length Required	INCORRECT_LENGTH	The error cause will be changed to ERROR_REQUEST_PARAMETERS.
429 - Too Many Requests	NF_CONGESTION_RISK	This will be supported with IGW congestion control and load shedding profiles.
500 - Internal Server Error	UNSPECIFIED_NF_FAILURE	The request is rejected due to unspecified reason at the NF.
503 - Service Unavailable	NF_CONGESTION	Supported by Gateway service.

Table C-4 List of errors sent by SM service for AF 5G

Message	Cause Code	Description
500 Internal Server Error	PDU_SESSION_NOT_AVAILABLE	The PCRF rejects a new Rx session setup when it fails to associate the described service. IP flows within the session information received from the AF to an existing IP-CAN session.
400 Bad Request	ERROR_INITIAL_PARAMETERS	This error is used when the set of bearer/session information needed in the CRF for rule selection is incomplete or erroneous for the decision to be made. For example, QoS, AGW/SGSN address, RAT type, and TFT.
404 Not Found	APPLICATION_SESSION_CONTEXT_NOT_FOUND	The request contained an unknown Session-Id.
403 Forbidden	REQUESTED_SERVICE_TEMPORARILY_NOT_AUTHORIZED	The PCRF rejects new or modified service information because the requested service, as described by the service information provided by the AF, is not consistent with either the related subscription information or operator defined policy rules.
403 Forbidden	UNAUTHORIZED_NON_EMERGENCY_SESSION	The PCRF rejects a new Rx session setup because the session binding function associated a non-Emergency IMS session to an IP-CAN session established to an Emergency APN.

Policy as a producer of Error to UE

Table C-5 Policy as a producer of Error to UE

Message	Cause Code	Description
400 - Bad request	MANDATORY_IE_INCORRECT	The SUPI was incorrectly written into the request body and sent to Ingress.
400 - Bad request	MANDATORY_IE_MISSING	A request is sent without a mandatory IE (SUPI) in the request body,the cases that are related to this cause will be handled asERROR_REQUEST_PARAMETERS.
400 - Bad request	UNSPECIFIED_MSG_FAILURE	When there is malformed JSON object.
400 - Bad request	USER_UNKNOWN	A correct request is sent, with a SUPI that is not registered in the UDR. We activate the validate-user in the UE Policy GUI.
400 - Bad request	ERROR_REQUEST_PARAMETERS	The HTTP request is rejected because the set of information needed by the PCF for UE Policy selection is incomplete or erroneous or not available for the decision to be made.
400 - Bad request	PENDING_TRANSACTION	This error shall be used when the Pending Transaction feature is supported and the AMF receives an incoming request on a policy association while it has an ongoing transaction on the same policy association.
401 - Unauthorized	With header "WWW-Authenticate"	Supported by Gateway service.
403 - Forbidden	MODIFICATION_NOT_ALLOWED	Supported by Gateway service.
404 - Not Found	SUBSCRIPTION_NOT_FOUND	When UE-Delete is sent with a polAssoId that does not exist in the database.
404 - Not Found	RESOURCE_URI_STRUCTURE_NOT_FOUND	This error is being handled by IGW, never reaches the core service, send 404 Not Found without cause.
408 - Request Timeout	NA	Request gets timed out.
411 - Length Required	INCORRECT_LENGTH	The error cause will be changed to ERROR_REQUEST_PARAMETERS.
429 - Too Many Requests	NF_CONGESTION_RISK	This will be supported with IGW congestion control and load shedding profiles.
500 - Internal Server Error	UNSPECIFIED_NF_FAILURE	The request is rejected due to unspecified reason at the NF.
503 - Service Unavailable	NF_CONGESTION	Supported by Gateway service.

HTTP Error Codes supported by Policy for CHF and UDR Interfaces

Table C-6 Error codes and cause supported by Policy for CHF Interface

Message	Cause Code	Description	Actions
400 - Bad Request	INVALID_API	The HTTP request contains an unsupported API name or API version in the URI.	Session Retry using connector configuration with PUT and POST requests. After the session retry is exhausted, final error code for PUT or POST failure will reach core service for Policy evaluation.
400 - Bad Request	INVALID_MSG_FORMAT	The HTTP request has an invalid format.	Session Retry using connector configuration with PUT and POST requests. After the session retry is exhausted, final error code for PUT or POST failure will reach core service for Policy evaluation.
400 - Bad Request	INVALID_QUERY_PARAM	The HTTP request contains an unsupported query parameter in the URI.	Session Retry using connector configuration with PUT and POST requests. After the session retry is exhausted, final error code for PUT or POST failure will reach core service for Policy evaluation.
400 - Bad Request	MANDATORY_QUERY_PARAM_INCORRECT	A mandatory query parameter, or a conditional query parameter but mandatory required, for an HTTP method was received in the URI with semantically incorrect value.	Session Retry using connector configuration with PUT and POST requests. After the session retry is exhausted, final error code for PUT or POST failure will reach core service for Policy evaluation.
400 - Bad Request	OPTIONAL_QUERY_PARAM_INCORRECT	A mandatory query parameter, or a conditional query parameter but mandatory required, for an HTTP method was received in the URI with semantically incorrect value.	Session Retry using connector configuration with PUT and POST requests. After the session retry is exhausted, final error code for PUT or POST failure will reach core service for Policy evaluation.
400 - Bad Request	MANDATORY_QUERY_PARAM_MISSING	Query parameter which is defined as mandatory, or as conditional but mandatory required, for an HTTP method is not included in the URI of the request.	Session Retry using connector configuration with PUT and POST requests. After the session retry is exhausted, final error code for PUT or POST failure will reach core service for Policy evaluation.
400 - Bad Request	MANDATORY_IE_INCORRECT	A mandatory IE or conditional IE but mandatory required, for an HTTP method was received with a semantically incorrect.	Session Retry using connector configuration with PUT and POST requests. After the session retry is exhausted, final error code for PUT or POST failure will reach core service for Policy evaluation.
400 - Bad Request	OPTIONAL_IE_INCORRECT	-	Session Retry using connector configuration with PUT and POST requests. After the session retry is exhausted, final error code for PUT or POST failure will reach core service for Policy evaluation.
400 - Bad Request	MANDATORY_IE_MISSING	A mandatory query parameter is missing in the HTTP request.	Session Retry using connector configuration with PUT and POST requests. After the session retry is exhausted, final error code for PUT or POST failure will reach core service for Policy evaluation.
400 - Bad Request	USER_UNKNOWN	The HTTP request is rejected because PCF received an unknown user.	Session Retry using connector configuration with PUT and POST requests. After the session retry is exhausted, final error code for PUT or POST failure will reach core service for Policy evaluation.
400 - Bad Request	NO_AVAILABLE_POLICY_COUNTERS	Policy counters are not available.	Session Retry using connector configuration with PUT and POST requests. After the session retry is exhausted, final error code for PUT or POST failure will reach core service for Policy evaluation.
400 - Bad Request	UNKNOWN_POLICY_COUNTERS	Policy counters are unknown.	Session Retry using connector configuration with PUT and POST requests. After the session retry is exhausted, final error code for PUT or POST failure will reach core service for Policy evaluation.
401 - Unauthorized	WWW-Authenticate	Unauthorized with Header "WWW-Authenticate"	Post Retry with POST request (Session retry) Put retry with POST (Revalidation/Reset context) If retry is exhausted, then terminate the transaction.
403 - Forbidden	Modification_Not_Allowed	Request is forbidden.	Retry with POST request If retry is exhausted, delete the session
404 - Not Found	SUBSCRIPTION_NOT_FOUND	The request for modification or deletion of a subscription is rejected because the subscription is not found in the NF.	Retry with POST request If retry is exhausted, delete the session
404 - Not Found	RESOURCE_URI_STRUCTURE_NOT_FOUND	Resource URI structure is not found.	Post Retry with POST request (Session retry) Put retry with POST (Revalidation/Reset context) If retry is exhausted, then terminate the transaction.
405 - Method Not Allowed	NA	The HTTP request is rejected as the performed operation is not allowed.	Post Retry with POST request (Session retry) Put retry with POST (Revalidation/Reset context) If retry is exhausted, then terminate the transaction.
406 - Not acceptable	NA	The request is not acceptable.	Post Retry with POST request (Session retry) Put retry with POST (Revalidation/Reset context) If retry is exhausted, then terminate the transaction.
409 - Conflict	NA	The request is rejected due to schema errors and conflicts in versions.	Post Retry with POST request (Session retry) Put retry with POST (Revalidation/Reset context) If retry is exhausted, then terminate the transaction.
410 - Gone	NA	This requested resource has been permanently deleted.	Post Retry with POST request (Session retry) Put retry with POST (Revalidation/Reset context) If retry is exhausted, then terminate the transaction.
411 - Length Required	NA	The HTTP request is rejected due to incorrect value of a Content-length header field.	Post Retry with POST request (Session retry) Put retry with POST (Revalidation/Reset context) If retry is exhausted, then terminate the transaction.
412 - Precondition Failed	NA	The request is rejected due to incorrect conditions in GET request.	Post Retry with POST request (Session retry) Put retry with POST (Revalidation/Reset context) If retry is exhausted, then terminate the transaction.
413 - Payload Too Large	NA	The payload is larger than the limit.	Post Retry with POST request (Session retry) Put retry with POST (Revalidation/Reset context) If retry is exhausted, then terminate the transaction.
414 - URI Too Long	NA	The request URI is longer than the limit.	Post Retry with POST request (Session retry) Put retry with POST (Revalidation/Reset context) If retry is exhausted, then terminate the transaction.
415 - Unsupported Media Type	NA	The HTTP request contains unsupported payload payload type.	Post Retry with POST request (Session retry) Put retry with POST (Revalidation/Reset context) If retry is exhausted, then terminate the transaction.
429 - Too many requests	NA	The request is rejected due to excessive traffic, which if continued over time, may lead to (or may increase) an overload situation.	Post Retry with POST request (Session retry) Put retry with POST (Revalidation/Reset context) If retry is exhausted, then terminate the transaction.
500 - Internal Server Error	NA	The request is rejected due to generic error condition in the NF.	Post Retry with POST request (Session retry) Put retry with POST (Revalidation/Reset context) If retry is exhausted, then terminate the transaction.
501 - Not Implemented	NA	The service operation cannot be implemented due to invalid resource URI to be monitored.	Post Retry with POST request (Session retry) Put retry with POST (Revalidation/Reset context) If retry is exhausted, then terminate the transaction.
503 - Service Unavailable	NA	The NF experiences congestion and performs overload control, which does not allow the request to be processed.	Post Retry with POST request (Session retry) Put retry with POST (Revalidation/Reset context) If retry is exhausted, then terminate the transaction.
504 - Gateway Timeout	NA	This error code is generated in case of timeout due to inactivity.	Post Retry with POST request (Session retry) Put retry with POST (Revalidation/Reset context) If retry is exhausted, then terminate the transaction.

Table C-7 Error codes and cause supported by Policy for UDR Interface.

Error Code - Message	Cause Code	Description	Action
400 - Bad Request	INVALID_API	The HTTP request contains an unsupported API name or API version in the URI.	Session Retry using connector configuration with PUT and POST requests. If retry is exhausted, terminate the transaction.
400 - Bad Request	INVALID_MSG_FORMAT	The HTTP request has an invalid format.	Session Retry using connector configuration with PUT and POST requests. If retry is exhausted, terminate the transaction.
400 - Bad Request	INVALID_QUERY_PARAM	The HTTP request contains an unsupported query parameter in the URI.	Session Retry using connector configuration with PUT and POST requests. If retry is exhausted, terminate the transaction.
400 - Bad Request	MANDATORY_QUERY_PARAM_INCORRECT	A mandatory query parameter, or aconditional query parameter but mandatoryrequired, for an HTTP method was received in the URI with semantically incorrect value.	Session Retry using connector configuration with PUT and POST requests. If retry is exhausted, terminate the transaction.
400 - Bad Request	OPTIONAL_QUERY_PARAM_INCORRECT	A mandatory query parameter, or aconditional query parameter but mandatoryrequired, for an HTTP method was received in the URI with semantically incorrect value.	Session Retry using connector configuration with PUT and POST requests. If retry is exhausted, terminate the transaction.
400 - Bad Request	MANDATORY_QUERY_PARAM_MISSING	Query parameter which is defined asmandatory, or as conditional but mandatoryrequired, for an HTTP method is not included in the URI of the request.	Session Retry using connector configuration with PUT and POST requests. If retry is exhausted, terminate the transaction.
400 - Bad Request	MANDATORY_IE_INCORRECT	A mandatory IE or conditional IE butmandatory required, for an HTTP methodwas received with a semantically incorrect.	Session Retry using connector configuration with PUT and POST requests. If retry is exhausted, terminate the transaction.
400 - Bad Request	OPTIONAL_IE_INCORRECT	-	Session Retry using connector configuration with PUT and POST requests. If retry is exhausted, terminate the transaction.
400 - Bad Request	MANDATORY_IE_MISSING	A mandatory query parameter is missing in theHTTP request.	Session Retry using connector configuration with PUT and POST requests. If retry is exhausted, terminate the transaction.
400 - Bad Request	USER_UNKNOWN	The HTTP request is rejected because PCF received an unknown user.	Session Retry using connector configuration with PUT and POST requests. If retry is exhausted, terminate the transaction.
401 -Unauthorized	WWW-Authenticate	Unauthorized with Header "WWW-Authenticate"	Post Retry with POST request (Session retry) Put retry with POST (Revalidation/Reset context) If retry is exhausted, terminate the transaction
403- Forbidden	Modification_Not_Allowed	Request is forbidden.	Retry with POST request
404 - Not Found	SUBSCRIPTION_NOT_FOUND	The request for modification or deletion of a subscription is rejected because the subscription is not found in the NF.	POST Retry with POST request (Session retry) Put retry with POST (Revalidation/Reset context) If retry is exhausted, delete the subscription
404 - Not Found	RESOURCE_URI_STRUCTURE_NOT_FOUND	Resource URI structure is not found.	Retry with POST request If retry is exhausted, terminate the transaction
404 - Not Found	USER_UNKNOWN	User is unknown.	Retry with POST request If retry is exhausted, terminate the transaction
405 - Method Not Allowed	NA	The HTTP request is rejected as the performed operation is not allowed.	Retry with POST request If retry is exhausted, terminate the transaction
406 - Not acceptable	NA	The request is not acceptable.	Retry with POST request If retry is exhausted, terminate the transaction
409 -Conflict	NA	The request is rejected due to schema errors and conflicts in versions.
410 - Gone	NA	This requested resource has been permanently deleted.	Retry with POST request If retry is exhausted, terminate the transaction
411 - Length Required	NA	The HTTP request is rejected due to incorrect value of a Content-length header field.	Retry with POST request If retry is exhausted, terminate the transaction
412 - Precondition Failed	NA	The request is rejected due to incorrect conditions in GET request.	Retry with POST request If retry is exhausted, terminate the transaction
413 - Payload Too Large	NA	The payload is larger than the limit.	Retry with POST request If retry is exhausted, terminate the transaction
414 - URI Too Long	NA	The request URI is longer than the limit.	Retry with POST request If retry is exhausted, terminate the transaction
415 - Unsupported Media Type	NA	The HTTP request contains unsupported payload payload type.	Retry with POST request If retry is exhausted, terminate the transaction
429 - Too many requests	NA	The request is rejected due to excessive traffic, which if continued over time, may lead to (or may increase) an overload situation.	NA
500 - Internal Server Error	NA	The request is rejected due to generic error condition in the NF.	Retry with POST request If retry is exhausted, terminate the transaction
501 - Not Implemented	NA	The service operation cannot be implemented due to invalid resource URI to be monitored.	Retry with POST request If retry is exhausted, terminate the transaction
503 - Service Unavailable	NA	The NF experiences congestion and performs overload control, which does not allow the request to be processed.	Retry with POST request If retry is exhausted, terminate the transaction
504 - Gateway Timeout	NA	This error code is generated in case of timeout due to inactivity.	Retry with POST request If retry is exhausted, terminate the transaction

Policy as a producer of Error for Notification for CHF Interface

Table C-8 Policy as a producer of Error for Notification for CHF Interface

Error Code - Message	Cause Code	Scenario
400 - Bad Request	MANDATORY_IE_MISSING	When SUPI is not present in the request body for update or terminate notification.
400 - Bad Request	INVALID_MESSAGE_FORMAT	When the request body does not adhere to update or terminate notification structure.
400 - Bad Request	invalid_API	The HTTP request contains an unsupported API name or API version in the URI.
404 - Not Found	RESOURCE_URI_STRUCTURE_NOT_FOUND	The notification URI is incorrect.
404 - Not Found	SUBSCRIPTION_NOT_FOUND	When the spendinglimit resource is not found in DB.
504 - Gateway Timeout	GATEWAY_TIMEOUT	This error code is generated in case of timeout due to inactivity.

Policy as a producer of Error for Notification for UDR Interface

Table C-9 Policy as a producer of Error for Notification for UDR Interface

Error Code - Message	Cause Code	Scenario
400 - Bad Request	INVALID_MESSAGE_FORMAT	When the request body does not adhere to update or terminate notification structure.
404 - Not Found	SUBSCRIPTION_NOT_FOUND	When the PolicyDataChangeNotification resource is not found in DB.
501 - Not Implemented	UNSUPPORTED_MONITORED_URI	When the PolicyDataChangeNotification received have resource other than smPolicyData,operatorSpecificData, amPolicyData, and UePolicySet.

HTTP Error Codes supported by Policy for NRF Interface

HTTP Error codes supported by Policy for NRF Interface:

Error Code - Message	Description	Action
400 - Bad Request	The Request contains invalid values.	Autonomous mode: The NF retries primary NRF configurable N times, if fails NF retries secondary NRF configurable M times. NF continues switching back and forth between primary and secondary NRF until success registration. The time interval between one attempt and another is configurable. On demand mode: NF retries non primary NRF, if Primary NRF fails. If non primary NRF fails, NF continues with call flow and shall not be able to deregister in NRF.
403 - Forbidden	Request is forbidden.	Autonomous mode: The NF retries primary NRF configurable N times, if fails NF retries secondary NRF configurable M times. NF continues switching back and forth between primary and secondary NRF until success registration. The time interval between one attempt and another is configurable. On demand mode: NF retries non primary NRF, if Primary NRF fails. If non primary NRF fails, NF continues with call flow and shall not be able to deregister in NRF.
404- Not Found	The request for modification or deletion of a subscription is rejected because the subscription is not found in the NF.	Autonomous mode: The NF retries primary NRF configurable N times, if fails NF retries secondary NRF configurable M times. NF continues switching back and forth between primary and secondary NRF until success registration. The time interval between one attempt and another is configurable. On demand mode: NF retries non primary NRF, if Primary NRF fails. If non primary NRF fails, NF continues with call flow and shall not be able to deregister in NRF.
405 - Method Not Allowed	The request method is not GET, PUT, PATCH or DELETE.	Autonomous mode: The NF retries primary NRF configurable N times, if fails NF retries secondary NRF configurable M times. NF continues switching back and forth between primary and secondary NRF until success registration. The time interval between one attempt and another is configurable. On demand mode: NF retries non primary NRF, if Primary NRF fails. If non primary NRF fails, NF continues with call flow and shall not be able to deregister in NRF.
411 - Length Required	The request is rejected due to incorrect value of a Content-length header field, or the header doesn't exist.	Autonomous mode: The NF retries primary NRF configurable N times, if fails NF retries secondary NRF configurable M times. NF continues switching back and forth between primary and secondary NRF until success registration. The time interval between one attempt and another is configurable. On demand mode: NF retries non primary NRF, if Primary NRF fails. If non primary NRF fails, NF continues with call flow and shall not be able to deregister in NRF.
500 - Internal Server Error	Internal error occurred in NRF.	Autonomous mode: The NF retries primary NRF configurable N times, if fails NF retries secondary NRF configurable M times. NF continues switching back and forth between primary and secondary NRF until success registration. The time interval between one attempt and another is configurable. On demand mode: NF retries non primary NRF, if Primary NRF fails. If non primary NRF fails, NF continues with call flow and shall not be able to deregister in NRF.
503 - Service Unavailable	Rejecting traffic for overload control.	Autonomous mode: The NF retries primary NRF configurable N times, if fails NF retries secondary NRF configurable M times. NF continues switching back and forth between primary and secondary NRF until success registration. The time interval between one attempt and another is configurable. On demand mode: NF retries non primary NRF, if Primary NRF fails. If non primary NRF fails, NF continues with call flow and shall not be able to deregister in NRF.

Table C-10 Policy as a producer of Error for Notification for NRF Interface

Message	Cause Code	Scenario
400 - Bad Request	INVALID_MSG_FORMAT	NRF terminates the notification transaction.
400 - Bad Request	MANDATORY_IE_INCORRECT	NRF terminates the notification transaction.
400 - Bad Request	OPTIONAL_IE_INCORRECT	NRF terminates the notification transaction.
400 - Bad Request	MANDATORY_IE_MISSING	NRF terminates the notification transaction.
400 - Bad Request	UNSPECIFIED_MSG_FAILURE	NRF terminates the notification transaction.
429 - Too Many Requests	NF_CONGESTION_RISK	NRF terminates the notification transaction.
500 - Internal Server Error	SYSTEM_FAILURE	NRF terminates the notification transaction.
503 - Service Unavailable	NA	NRF terminates the notification transaction.

Table C-11 Error Codes and Cause Supported by Policy for PCRF Core

Message	Cause Code	Description
3001	DIAMETER_COMMAND_UNSUPPORTED	The Request contained a Command-Code that the receiver did not recognize or support. This must be used when a Diameter node receives an experimental command that it does not understand.
3004	DIAMETER_TOO_BUSY	When returned, a Diameter node must attempt to send the message to an alternate peer. This error must only be used when a specific server is requested, and it cannot provide the requested service.
3005	DIAMETER_LOOP_DETECTED	An agent detected a loop while trying to get the message to the intended recipient. The message can be sent to an alternate peer, if one is available, but the peer reporting the error has identified a configuration problem.
5003	DIAMETER_AUTHORIZATION_REJECTED	A request was received for which the user can not be authorized. This error can occur if the service requested is not permitted to the user.
5005	DIAMETER_MISSING_AVP	The request did not contain an AVP that is required by the Command Code definition. If this value is sent in the Result-Code AVP, a `Failed-AVP` must be included in the message. The `Failed-AVP` must contain an example of the missing AVP complete with the Vendor-Id if applicable. The value field of the missing AVP should be of correct minimum length and contain zeroes.
5001	DIAMETER_AVP_UNSUPPORTED	The peer received a message that contained an AVP that is not recognized or supported and was marked with the Mandatory bit. A Diameter message with this error must contain one or more `Failed-AVP` containing the AVPs that caused the failure.
5009	DIAMETER_AVP_OCCURS_TOO_MANY_TIMES	A message was received that included an AVP that appeared more often than permitted in the message definition. The `Failed-AVP` must be included and contain a copy of the first instance of the offending AVP that exceeded the maximum number of occurrences.
5014	DIAMETER_INVALID_AVP_LENGTH	The request contained an AVP with an invalid length. A Diameter message indicating this error must include the offending AVPs within a `Failed-AVP`.
5004	DIAMETER_INVALID_AVP_VALUE	The request contained an AVP with an invalid value in its data portion. A Diameter message indicating this error must include the offending AVPs within a `Failed-AVP`.
3009	DIAMETER_INVALID_AVP_BITS	A request was received that included an AVP whose flag bits are set to an unrecognized value, or that is inconsistent with the AVP's definition.
3008	DIAMETER_INVALID_HDR_BITS	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's definition.
3002	DIAMETER_UNABLE_TO_DELIVER	This error is given when Diameter can not deliver the message to the destination, either because no host within the realm supporting the required application was available to process the request, or because Destination-Host AVP was given without the associated Destination-Realm AVP.
5012	DIAMETER_UNABLE_TO_COMPLY	This error is returned when a request is rejected for unspecified reasons.
5002	DIAMETER_UNKNOWN_SESSION_ID	The request contained an unknown Session-Id.

Table C-12 List of errors sent by Diameter Connector for AF

Message	Cause Code	Description
5063	REQUESTED_SERVICE_NOT_AUTHORIZED	The PCRF rejects new or modified service information because the requested service, as described by the service information provided by the AF, is not consistent with either the related subscription information or operator defined policy rules.
5065	IP_CAN_SESSION_NOT_AVAILABLE	The PCRF rejects a new Rx session setup when it fails to associate the described service IP flows within the session information received from the AF to an existing IP-CAN session.
5002	DIAMETER_UNKNOWN_SESSION_ID	The request contained an unknown Session-Id.
5012	DIAMETER_UNABLE_TO_COMPLY	This error is returned when a request is rejected for unspecified reasons.
3004	DIAMETER_TOO_BUSY	When returned, a Diameter node must attempt to send the message to an alternate peer. This error must only be used when a specific server is requested, and it cannot provide the requested service.

Table C-13 List of errors sent by Diameter Connector for Sy

Message	Cause Code	Description
5002	DIAMETER_UNKNOWN_SESSION_ID	The request contained an unknown Session-Id.
5012	DIAMETER_UNABLE_TO_COMPLY	This error is returned when a request is rejected for unspecified reasons.
3004	DIAMETER_TOO_BUSY	When returned, a Diameter node must attempt to send the message to an alternate peer. This error must only be used when a specific server is requested, and it cannot provide the requested service.

Table C-14 List of errors sent by Diameter Gateway for AF

Message	Cause Code	Description
3002	DIAMETER_UNABLE_TO_DELIVER	This error is given when Diameter can not deliver the message to the destination, either because no host within the realm supporting the required application was available to process the request, or because Destination-Host AVP was given without the associated Destination-Realm AVP.
5065	IP_CAN_SESSION_NOT_AVAILABLE	Context owner not found after binding service query for session-id.
3004	DIAMETER_TOO_BUSY	Error 5xx response received from binding service query for session-id.
5012	DIAMETER_UNABLE_TO_COMPLY	Error response received from binding service query for session-id.

Table C-15 List of errors sent by DIAM-STACK (Diameter Gateway, Diameter Connector)

Message	Cause Code	Description
3001	DIAMETER_COMMAND_UNSUPPORTED	The request contained a Command-Code that the receiver did not recognize or support. This must be used when a Diameter node receives an experimental command that it does not understand.
3005	DIAMETER_LOOP_DETECTED	An agent detected a loop while trying to get the message to the intended recipient. The message can be sent to an alternate peer, if one is available, but the peer reporting the error has identified a configuration problem.
5005	DIAMETER_MISSING_AVP	The request did not contain an AVP that is required by the Command-Code definition. If this value is sent in the Result-Code AVP, a `Failed-AVP` must be included in the message. The `Failed-AVP` must contain an example of the missing AVP complete with the Vendor-Id if applicable. The value field of the missing AVP must be of correct minimum length and contain zeroes.
5001	DIAMETER_AVP_UNSUPPORTED	The peer received a message that contained an AVP that is not recognized or supported and was marked with the Mandatory bit. A Diameter message with this error must contain one or more `Failed-AVP` containing the AVPs that caused the failure.
5009	DIAMETER_AVP_OCCURS_TOO_MANY_TIMES	A message was received that included an AVP that appeared more often than permitted in the message definition. The `Failed-AVP` must be included and contain a copy of the first instance of the offending AVP that exceeded the maximum number of occurrences.
5014	DIAMETER_INVALID_AVP_LENGTH	The request contained an AVP with an invalid length. A Diameter message indicating this error must include the offending AVPs within a `Failed-AVP`.
5004	DIAMETER_INVALID_AVP_VALUE	The request contained an AVP with an invalid value in its data portion. A Diameter message indicating this error must include the offending AVPs within a `Failed-AVP`.
3009	DIAMETER_INVALID_AVP_BITS	A request was received that included an AVP whose flag bits are set to an unrecognized value, or that is inconsistent with the AVP's definition.
3008	DIAMETER_INVALID_HDR_BITS	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's definition.
3002	DIAMETER_UNABLE_TO_DELIVER	This error is given when Diameter can not deliver the message to the destination, either because no host within the realm supporting the required application was available to process the request, or because Destination-Host AVP was given without the associated Destination-Realm AVP.
5012	DIAMETER_UNABLE_TO_COMPLY	This error is returned when a request is rejected for unspecified reasons.

Table C-16 List of errors sent by PCRF Core for AF

Message	Cause Code	Description
5063	REQUESTED_SERVICE_NOT_AUTHORIZED	The PCRF rejects a new Rx session setup because the session binding function associated a non-Emergency IMS session to an IP-CAN session established to an Emergency APN.
5012	DIAMETER_UNABLE_TO_COMPLY	This error is returned when a request is rejected for unspecified reasons.
5065	IP_CAN_SESSION_NOT_AVAILABLE	The PCRF rejects a new Rx session setup when it fails to associate the described service IP flows within the session information received from the AF to an existing IP-CAN session.
5066	UNAUTHORIZED_NON_EMERGENCY_SESSION	The PCRF rejects a new Rx session setup because the session binding function associated a non-Emergency IMS session to an IP-CAN session established to an Emergency APN.
5454	DIAMETER_ERROR_TIMED_OUT_REQUEST	PCRF to indicate the incoming request is known to have already timed out at the originating entity.
5068	TEMPORARY_NETWORK_FAILURE	The PCRF rejects new or modified service information because there is a temporary failure in the access network such as the SGW has failed.
5003	DIAMETER_AUTHORIZATION_REJECTED	A request was received for which the user could not be authorized. This error could occur if the service requested is not permitted to the user.

Table C-17 List of errors sent by PCRF Core for Gx

Message	Cause Code	Description
5453	DIAMETER_ERROR_LATE_OVERLAPPING_REQUEST	To indicate that the incoming request collides with an existing session, which has a more recent time stamp than the time stamp of the new request.
5030	DIAMETER_USER_UNKNOWN	The specified end user is unknown in the credit-control server.
5454	DIAMETER_ERROR_TIMED_OUT_REQUEST	PCRF to indicate the incoming request is known to have already timed out at the originating entity.
5002	DIAMETER_UNKNOWN_SESSION_ID	The request contained an unknown Session-Id.
5003	DIAMETER_AUTHORIZATION_REJECTED	A request was received for which the user could not be authorized. This error could occur if the service requested is not permitted to the user.
5012	DIAMETER_UNABLE_TO_COMPLY	This error is returned when a request is rejected for unspecified reasons.
4144	DIAMETER_PENDING_TRANSACTION	A race condition detected, this is 3GPP specific result code

Table C-18 List of errors sent by PCRF Core for Sd

Message	Cause Code	Description
5012	DIAMETER_UNABLE_TO_COMPLY	This error is returned when a request is rejected for unspecified reasons.
5003	DIAMETER_AUTHORIZATION_REJECTED	A request was received for which the user could not be authorized. This error could occur if the service requested is not permitted to the user.

Table C-19 List of errors that Diameter Connector for Sd for 5G

Code	Status Code	Description
408	Request Timeout	This error is returned when Diameter Connector detects a timeout while forwarding Sd:TSR/Sd:RAR message.
400	Bad Request	This error is returned when Diameter Connector detects that Sd session Id value is null or empty.
503	Service Unavailable	This error is returned when Diameter Connector detects that Sd session Id is set as deferred result when Timeout is triggered for Sd:TSR/Sd:RAR message.

Table C-20 List of errors produced by LDAP-GATEWAY as a producer

Code	Status Code	Comments
400	Bad request	This error code indicates that the server cannot process the request sent by the client.
404	Not Found	This error code indicates that there is a mistyped URL and cannot be found.
414	URI Too Long	This error code indicates that URI provided in the client's request is longer than the server is willing to interpret.
500	Internal Servicer Error	This error code indicates that the server encountered an unexpected condition that prevented it from fulfilling your request.
503	Service Unavailable	This error code indicates that the server is temporarily unable to handle the request.

Table C-21 List of errors produced by LDAP-GATEWAY as a consumer

Code	Status Code	Comments
408	Request Timeout	This error code indicates that the server did not receive a complete request from the client within the time it was prepared to wait

Table C-22 List of errors produced by SOAP Connector as a consumer

Code	Status Code	Comments
500	Internal Servicer Error	This error code indicates that the server encountered an unexpected condition that prevented it from fulfilling your request.
503	Service Unavailabl.	This error code indicates that the server is currently unable to handle the request due to a temporary overload or scheduled maintenance.

Table C-23 List of errors produced by Usage Monitor as a producer

Code	Status Code	Comments
400	Bad request	This error code indicates that the server cannot process the request sent by the client.
500	Internal Server Error	This error code indicates that the server encountered an unexpected condition that prevented it from fulfilling your request.
504	Gateway Timeout	Gateway Timeout Dependency failure for e.g. Unable to reach PRE

Table C-24 List of errors produced by Usage Monitor as a consumer

Code	Status Code	Comments
500	Internal Servicer Error	This error code indicates that the server encountered an unexpected condition that prevented it from fulfilling your request.