UECM Errors
The following errors are expected on UECM interface during the POST Operation, and causes the actions described below:
Application Error |
Description |
NAS Cause Code/Action |
---|---|---|
403 Forbidden |
||
UNKNOWN_5GS_SUBSCRIPTION |
No 5GS subscription is associated with the user. |
#7, 5GS services not allowed |
NO_PS_SUBSCRIPTION |
No PS (5GS, EPS, GPRS) subscription is associated with the user. |
#7, 5GS services not allowed |
ROAMING_NOT_ALLOWED |
The subscriber is not allowed to roam within that PLMN. |
#13, Roaming not allowed in the tracking area |
ACCESS_NOT_ALLOWED |
Access type is not allowed for the user. |
#7, 5GS services not allowed |
RAT_NOT_ALLOWED |
RAT is not allowed for the user. |
#7, 5GS services not allowed |
INVALID_GUAMI |
The AMF is not allowed to modify the registration information stored in the UDM as it is not the registered AMF. |
#15, No suitable cells in tracking area |
404 Not Found |
||
USER_NOT_FOUND |
The user does not exist in the HPLMN. |
#7, 5GS services not allowed |
CONTEXT_NOT_FOUND |
It is used when no corresponding context exists. |
#15, No suitable cells in tracking area |
The following errors are not expected. If they occur, it is due to a logic error. Since AMF always rejects a message in this state, the error should be logged, and the call must be rejected with NO SUITABLE CELLS IN TRACKING AREA.
Application Error |
Description |
Response to UE |
---|---|---|
422 Unprocessable Entity |
||
UNPROCESSABLE_REQUEST |
The request cannot be processed due to semantic errors when trying to process a patch method. |
Registration Reject with Cause #111, protocol error unspecified |