Error Reporting

HTTP Error Reporting

The SCEF application generates an error response when an HTTP request fails to get processed successfully. The SCEF application inserts an error cause whenever possible for easy of debugging. The error cause is contained in json format for requests of type POST/PATCH/PUT. The content of the detail attribute of the problem json structure is formatted as:

SCEF-ERR-XXX-YYY: <human readable text description of the error>

where XXX is the HTTP Response Code and YYY is a 3-digit problem code Table 2-4.

Table 2-4 Problem Codes for HTTP Error Reporting

Problem Code	Problem Details
099	Generic Error
100	The configuration sets were not found for the given SCS/AS.
101	Stack-Event deserialization failed
102	An internal database error was encountered
103	A Diameter response did not contain requisite parameters to complete the transaction
104	NIDD Authorization/Grant time received from the HSS is in the past
105	A Diameter error response was received due to which the current HTTP transaction cannot be processed
106	An unexpected response was received from the Database (USBR) server
107	A Database integrity error was detected for the (IMSI, APN) Alternate Key
108	The HTTP message contains an invalid JSON content
109	The HTTP message contains a JSON content that failed schema validation
110	A context record was not found in the USBR database
111	The downlink data delivery packet was rejected as the data size exceeds the configured maximum limit
112	A USBR read request failed
113	A message or event was received that was not expected in the current state of the transaction context
114	An internal error was encountered while processing an NIDD transaction
115	A PDN connection was not found for the User Entity
116	A downlink data delivery message could not be buffered because it contains a T8 Transaction Identifier that is already in use by one of the buffered data messages
117	A downlink data delivery message was rejected as it did not contain any data
118	A downlink data delivery message could not be processed as the downlink data rate limit has been reached
119	The MME was not able to deliver the downlink data to the UE
120	A parameter value in the request message is not supported (in the current version)
121	The transaction could not be processed as the operation is not valid in the current transaction state
122	Unused
123	Unused
124	The downlink data delivery message could not be buffered as the packet size exceeds the maximum allowed size for a packet that can be buffered
125	The downlink data delivery message could not be buffered as the maximum latency is too small
126	The downlink data delivery message could not be buffered as the number of currently buffered messages is at the configured maximum
127	The transaction request was failed as the UE is not authorized by Access Control
128	The transaction request as failed as the feature requested is not enabled for the requesting SCS/AS
129	The transaction request as failed as the feature requested is not enabled for the requesting UE
130	The API version requested is not supported
131	The HTTP message did not contain a mandatory parameter
132	The transaction was failed as the requesting SCS/AS is not configured

Diameter Error Reporting

Diameter error reporting problem codes will be introduced in a future DSR release.