6.2.7 Error Handling
29.5623GPP5G SystemHome Subscriber Server (HSS) servicesRelease 18Stage 3TS
6.2.7.1 General
HTTP error handling shall be supported as specified in clause 5.2.4 of 3GPP TS 29.500 [4].
6.2.7.2 Protocol Errors
Protocol errors handling shall be supported as specified in clause 5.2.7 of 3GPP TS 29.500 [4].
6.2.7.3 Application Errors
The common application errors defined in the Table 5.2.7.2-1 in 3GPP TS 29.500 [4] may also be used for the Nhss_imsSDM service. The following application errors listed in Table 6.2.7.3-1 are specific for the Nhss_imsSDM service.
Table 6.2.7.3-1: Application errors
|
Application Error |
HTTP status code |
Description |
|
USER_NOT_FOUND |
404 Not Found |
The user does not exist in the HPLMN |
|
SERVICE_NOT_FOUND |
404 Not Found |
The service (PSI) does not exist in the HPLMN |
|
DATA_NOT_FOUND |
404 Not Found |
The requested data is not found/does not exist. Additional information (if any) about this application error is indicated for each specific resource. |
|
CONTEXT_NOT_FOUND |
404 Not Found |
It is used during the modification of an existing subscription when no corresponding context exists. |
|
OPERATION_NOT_ALLOWED |
403 Forbidden |
The requested data is not allowed to be accessed by the service consumer, e.g. the IMS-AS does not have permissions for the requested resource and/or HTTP method. |
|
OUT_OF_SYNC |
409 Conflict |
The request could not be completed due to a conflict with the current state of the target resource (wrong version or sequence number) |
|
TOO_MUCH_DATA |
413 Payload Too Large |
The request could not be completed due to large amount of data (e.g. size of repository data is too large). This response may be due to constraints applied by the service producer, e.g. based on local policy. |