Interface Error Codes
This section describes the codes that PCF reports for the interface errors.
Interface codes are generated as part of the logs or captured in the statistics.
The following tables describes the error and the corresponding codes:
Error |
Error Code |
Description |
---|---|---|
USER_UNKNOWN |
400 Bad Request |
The HTTP request is rejected because the end user who is specified in the request is unknown to the PCF. |
ERROR_INITIAL_PARAMETERS |
400 Bad Request |
The HTTP request is rejected. This error is reported when the set of session or subscriber information which PCF requires for a rule selection is incomplete, erroneous, or unavailable for decision making. For example, QoS, RAT type, and subscriber information. |
ERROR_TRIGGER_EVENT |
400 Bad Request |
The HTTP request is rejected because the set of session information sends a message that originated due to a trigger is incoherent with the previous set of session information for the same session. For example, trigger met was RAT changed, and the RAT notified is the same as before. |
TRAFFIC_MAPPING_ INFO_REJECTED |
403 Forbidden |
The HTTP request is rejected because the PCF doesn’t accept one or more of the traffic mappings filters provided by the SMF in a PCC Request. |
ERROR_CONFLICTING_REQUEST |
403 Forbidden |
The HTTP request is rejected because the PCF can’t accept the UE-initiated resource request as a network initiated resource allocation is already in-progress. This resource allocation has packet filters that cover the packet filters in the received UE-initiated resource request. The SMF rejects the attempt for a UE-initiated resource request. |
POLICY_CONTEXT_DENIED | 403 Forbidden |
The HTTP request is rejected because the PCF doesn’t accept the SMF request due to operator policies and local configuration. |
Error |
Error Code |
Description |
---|---|---|
USER_UNKNOWN |
400 Bad Request |
The subscriber that is specified in the request isn’t known at the CHF and the subscription can’t be created. |
NO_AVAILABLE_POLICY _COUNTERS |
400 Bad Request |
There are no policy counters available for the subscriber at the CHF. |
Note | The generic error codes are applicable for all the network interfaces. |
Error |
Error Code |
Description |
---|---|---|
TIMEOUT |
408 Request Timeout |
The HTTP request to the server took longer than the period the server is configured to wait. |
OVERLOAD |
429 Too Many Requests |
The server has received too many consecutive requests to process within a short interval. |
INTERNAL_ERROR |
500 Internal Server Error |
The server has encountered an unprecedented condition, which does not have an appropriate message. |
SERVICE_UNAVAILABLE |
503 Service Unavailable |
The server cannot process the request because it is either, overloaded or is unavailable due to scheduled maintenance. This is a transient state. |