6.1.7 Error handling

32.2913GPP5G system, charging serviceCharging managementRelease 17Stage 3Telecommunication managementTS

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

6.1.7.1 General

HTTP error handling shall be supported as specified in clause 5.2.4 of 3GPP TS 29.500 [299].

For the Nchf_ConvergedCharging API, HTTP error responses shall be supported as specified in clause 4.8 of 3GPP TS 29.501 [2]. Protocol errors and application errors specified in table 5.2.7.2-1 of 3GPP TS 29.500 [299] shall be supported for an HTTP method if the corresponding HTTP status codes are specified as mandatory for that HTTP method in table 5.2.7.1-1 of 3GPP TS 29.500 [299]. In addition, the requirements in the following clauses shall apply.

6.1.7.2 Protocol Errors

There are no additional protocol errors applicable for the Nchf_ConvergedCharging API compared to the Protocol Error Handling specified in clause5.2.7.2 of 3GPP TS 29.500 [299].

6.1.7.3 Application errors

The application errors defined for the Nchf_ConvergedCharging API are listed in table 6.1.7.3-1. The CHF shall include in the HTTP status code a "ProblemDetails" data structure with the "cause" attribute indicating the application error as listed in table 6.1.7.3-1. The common application errors defined in the table 5.2.7.2-1 in 3GPP TS 29.500 [7] may also be used for the Nchf_ConvergedCharging service.

Table 6.1.7.3-1: Application errors

Application Error	HTTP status code	Description
CHARGING_FAILED	400 Bad Request	The HTTP request is rejected because the set of session or subscriber information needed by the CHF for charging or CDR creation is incomplete or erroneous or not available e.g., rating group, subscriber information.
RE_AUTHORIZATION_FAILED	400 Bad Request	The HTTP request is rejected because the set of information needed by the CTF to report the usage is incomplete or erroneous or not available.
CHARGING_NOT_APPLICABLE	403 Forbidden	The HTTP request is rejected by the CHF since it has been determined that the service can be allowed to the end user without any charging or CDR creation.
USER_UNKNOWN	404 Not Found	The HTTP request is rejected because the end user specified in the request cannot be served by the CHF.
END_USER REQUEST_DENIED	403 Forbidden	The HTTP request denied by the CHF due to restrictions or limitations related to the end-user.
QUOTA_LIMIT_REACHED	403 Forbidden	The HTTP request denied by the CHF because the end user’s account could not cover the requested service. If the request contained used units they are deducted, if applicable.
END_USER_REQUEST_REJECTED	403 Forbidden	The HTTP request rejected by the CHF due to end-user restrictions or limitations.