USER_UNKNOWN

400 Bad Request

The HTTP request is rejected because the end user specified in the request is unknown to the PCF. (NOTE 1) (NOTE 3)

ERROR_INITIAL_PARAMETERS

400 Bad Request

The HTTP request is rejected because the set of session or subscriber information needed by the PCF for rule selection is incomplete or erroneous or not available for the decision to be made. (E.g. QoS, RAT type, subscriber information) (NOTE 1) (NOTE 2) (NOTE 3)

ERROR_TRIGGER_EVENT

400 Bad Request

The HTTP request is rejected because the set of session information sent the message originated due to a trigger been met is incoherent with the previous set of session information for the same session. (E.g. trigger met was RAT changed, and the RAT notified is the same as before) (NOTE 2) (NOTE 3)

PENDING_TRANSACTION

400 Bad Request

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 and cannot handle the request as described in clause 9.2 of 3GPP TS 29.513 [7]. (NOTE 2)

ERROR_TRAFFIC_MAPPING_INFO_REJECTED

403 Forbidden

The HTTP request is rejected because the PCF does not accept one or more of the traffic mapping filters provided by the NF service consumer in a PCC Request. (NOTE 2) (NOTE 3)

ERROR_CONFLICTING_REQUEST

403 Forbidden

The HTTP request is rejected because the PCF cannot accept the UE-initiated resource request as a network-initiated resource allocation is already in progress that has packet filters that cover the packet filters in the received UE-initiated resource request. The NF service consumer shall reject the attempt for UE-initiated resource request. (NOTE 2) (NOTE 3)

LATE_OVERLAPPING_REQUEST

403 Forbidden

The request is rejected because it collides with and exiting Policy Association with a more recent originating timestamp. (NOTE 1)

POLICY_CONTEXT_DENIED

403 Forbidden

The HTTP request is rejected because the PCF does not accept the NF service consumer request due to operator policies and/or local configuration. (NOTE 1) (NOTE 2) (NOTE 3)

VALIDATION_CONDITION_NOT_MET

403 Forbidden

The HTTP request is rejected because the PCF does not accept the NF service consumer request because the validation condition of background data transfer policy is not met. (NOTE 1) (NOTE 3)

INVALID_BDT_POLICY

403 Forbidden

The HTTP request is rejected because the PCF does not accept the NF service consumer request because the background data transfer policy is invalid. (NOTE 1)

EXCEEDED_UE_SLICE_DATA_RATE

403 Forbidden

The HTTP request is rejected because the PCF does not accept the NF service consumer request because the authorized data rate exceeds the consumed data rate for that UE and network slice. (NOTE 1) (NOTE 2)

EXCEEDED_SLICE_DATA_RATE

403 Forbidden

The HTTP request is rejected because the PCF does not accept the NF service consumer request because the authorized data rate exceeds the consumed data rate for that slice. (NOTE 1) (NOTE 2)

POLICY_ASSOCIATION_NOT_FOUND

404 Not Found

The HTTP request is rejected because no policy association corresponding to the request exists in the PCF. (NOTE 2)

NOTE 1: These application errors are used by the create service operation (see clause 4.2.2.2) and included in the responses to the POST request.

NOTE 2: These application errors are used by the update service operation (see clause 4.2.4.2) and included in the responses to the POST request.

NOTE 3: The Cause codes mapping performed by NF service consumer between this Application Error and the 5GSM related value is specified in clause 5.2.2.2 of 3GPP TS 29.524 [40].

NOTE 4: Including a "ProblemDetails" data structure with the "cause" attribute in the HTTP response is optional unless explicitly mandated in the service operation clauses.

PCC_RULE_EVENT

400 Bad Request

The HTTP request is rejected because all the PCC rules provisioned by the PCF in the request cannot be installed/activated. It is used to inform the PCF that the request failed, and should not be attempted again. (NOTE 1)

PCC_QOS_FLOW_EVENT

400 Bad Request

The HTTP request is rejected because for some reason all the PCC rules provisioned by the PCF in the request cannot be enforced or modified successfully in a network initiated procedure. It is used to inform the PCF that the request could not be satisfied at the time it was received, but may be able to satisfy the request in the future. (NOTE 1)

UE_STATUS_SUSPEND

400 Bad Request

The HTTP request is rejected because the UE’s status is suspended and the policy decisions received from the PCF cannot be enforced by the NF service consumer. Applicable only to functionality introduced with the PolicyUpdateWhenUESuspends feature as described in clause 5.8. (NOTE 1)

RULE_PERMANENT_ERROR

400 Bad Request

The HTTP request is rejected because all the PCC rules and/or session rules provisioned by the PCF in the request cannot be installed/activated. It is used to inform the PCF that the request failed, and should not be attempted again. Applicable only to functionality introduced with the SessionRuleErrorHandling feature as described in clause 5.8. (NOTE 1)

RULE_TEMPORARY_ERROR

400 Bad Request

The HTTP request is rejected because for some reason all the PCC rules and/or session rules provisioned by the PCF in the request cannot be enforced or modified successfully in a network initiated procedure. It is used to inform the PCF that the request could not be satisfied at the time it was received, but may be able to satisfy the request in the future. Applicable only to functionality introduced with the SessionRuleErrorHandling feature as described in clause 5.8. (NOTE 1)

PENDING_TRANSACTION

400 Bad Request

This error shall be used when the PendingTransaction feature is supported and the NF service consumer receives an incoming request on a policy association while it has an ongoing transaction on the same policy association and cannot handle the request as described in clause 9.2 of 3GPP TS 29.513 [7]. (NOTE 1)

AN_GW_FAILED

400 Bad Request

This error shall be used when SGWRest feature is supported and the received policy decisions (i.e. installation/modification of PCC rules or session rules) cannot be enforced by the SMF because the AN-Gateway has failed. (NOTE 1)

POL_DEC_ERROR

400 Bad Request

This error shall be used when Ext2PolicyDecisionErrorHandling feature is supported, the PCF provides only SM policy decisions and/or condition data and all the policy decisions and/or conditions in the request cannot be stored in the NF service consumer.

NOTE 1: These application errors are used by the UpdateNotify service operation (see clause 4.2.3.2) and included in the responses to the POST request.

NOTE 2: Including a "ProblemDetails" data structure with the "cause" attribute in the HTTP response is optional unless explicitly mandated in the service operation clauses.