Cause values for EPS mobility management

The main function of the mobility management sublayer is to support the mobility of a user equipment, such as informing the network of its present location and providing user identity confidentiality.

A further function of the mobility management sublayer is to provide connection management services to the session management (SM) sublayer and the short message services (SMS) entity of the connection management (CM) sublayer.

Cause	Cause values for EPS mobility management	Description
##	Causes related to UE identification
2	IMSI unknown in HSS	This EMM cause is sent to the UE if the UE is not known (registered) in the HSS or if the UE has packet only subscription. This EMM cause does not affect operation of the EPS service, although is may be used by an EMM procedure.
3	Illegal UE	This EMM cause is sent to the UE when the network refuses service to the UE either because an identity of the UE is not acceptable to the network or because the UE does not pass the authentication check, i.e. the RES received from the UE is different from that generated by the network.
6	Illegal ME	This EMM cause is sent to the UE if the ME used is not acceptable to the network, e.g. blacklisted.
9	UE identity cannot be derived by the network.	This EMM cause is sent to the UE when the network cannot derive the UE's identity from the GUTI/S-TMSI/P-TMSI and RAI e.g. no matching identity/context in the network or failure to validate the UE's identity due to integrity check failure of the received message.
10	Implicitly detached	This EMM cause is sent to the UE either if the network has implicitly detached the UE, e.g. after the implicit detach timer has expired, or if the EMM context data related to the subscription does not exist in the MME e.g. because of a MME restart, or because of a periodic tracking area update request routed to a new MME.
##	Cause related to subscription options
5	IMEI not accepted	This cause is sent to the UE if the network does not accept an attach procedure for emergency bearer services using an IMEI.
7	EPS services not allowed	This EMM cause is sent to the UE when it is not allowed to operate EPS services.
8	EPS services and non-EPS services not allowed	This EMM cause is sent to the UE when it is not allowed to operate either EPS or non-EPS services.
11	PLMN not allowed	This EMM cause is sent to the UE if it requests service, or if the network initiates a detach request, in a PLMN where the UE, by subscription or due to operator determined barring, is not allowed to operate.
12	Tracking area not allowed	This EMM cause is sent to the UE if it requests service, or if the network initiates a detach request, in a tracking area where the HPLMN determines that the UE, by subscription, is not allowed to operate.
		NOTE 1: If EMM cause #12 is sent to a roaming subscriber the subscriber is denied service even if other PLMNs are available on which registration was possible.
13	Roaming not allowed in this tracking area	This EMM cause is sent to an UE which requests service, or if the network initiates a detach request, in a tracking area of a PLMN which by subscription offers roaming to that UE but not in that tracking area.
14	EPS services not allowed in this PLMN	This EMM cause is sent to the UE which requests service, or if the network initiates a detach request, in a PLMN which does not offer roaming for EPS services to that UE.
		NOTE 2:Since only one list of forbidden PLMNs for packet services is maintained in the UE, then the "forbidden PLMNs for GPRS service" is the maintained list and the forbidden PLMNs for EPS service is equivalent to it.
15	No suitable cells in tracking area	This EMM cause is sent to the UE if it requests service, or if the network initiates a detach request, in a tracking area where the UE, by subscription, is not allowed to operate, but when it should find another allowed tracking area or location area in the same PLMN or an equivalent PLMN.
		NOTE 3:Cause #15 and cause #12 differ in the fact that cause #12 does not trigger the UE to search for another allowed tracking area on the same PLM.
25	Not authorized for this CSG	This EMM cause is sent to the UE if it requests access, or if the network initiates a detach request, in a CSG cell with CSG ID where the UE either has no subscription to operate or the UE's subscription has expired and it should find another cell in the same PLMN or an equivalent PLMN.
35	Requested service option not authorized in this PLMN	This EMM cause is sent to the UE if it requests in a PLMN a service option for which it is not authorized, e.g. if it attempts to attach for relay node operation in a PLMN with a USIM which does not belong to a relay node-specific subscription.
40	No EPS bearer context activated	This EMM cause is sent to the UE, if during a tracking area updating procedure or a service request, the MME detects that there is no active EPS bearer context in the network.
##	Causes related to PLMN specific network failures and congestion/authentication failures
16	MSC temporarily not reachable	This EMM cause is sent to the UE if it requests a combined EPS attach or tracking area updating in a PLMN where the MSC is temporarily not reachable via the EPS part of the network.
17	Network failure	This EMM cause is sent to the UE if the MME cannot service an UE generated request because of PLMN failures.
18	CS domain not available	This EMM cause is sent to the UE if the MME cannot service an UE generated request because CS domain is not available and SMS in MME is not supported.
19	ESM failure	This EMM cause is sent to the UE when there is a failure in the ESM message contained in the EMM message.
20	MAC failure	This EMM cause is sent to the network if the USIM detects that the MAC in the AUTHENTICATION REQUEST message is not fresh (see 3GPP TS 33.401 [19]).
21	Synch failure	This EMM cause is sent to the network if the USIM detects that the SQN in the AUTHENTICATION REQUEST message is out of range (see 3GPP TS 33.401 [19]).
22	Congestion	This EMM cause is sent to the UE because of congestion in the network (e.g. no channel, facility busy/congested etc.).
23	UE security capabilities mismatch	This EMM cause is sent to the network if the UE detects that the UE security capability does not match the one sent back by the network.
24	Security mode rejected, unspecified	This EMM cause is sent to the network if the security mode command is rejected by the UE if the UE detects that the nonceUE does not match the one sent back by the network or for unspecified reasons.
26	Non-EPS authentication unacceptable	This EMM cause is sent to the network in S1 mode if the "separation bit" in the AMF field of AUTN is set to 0 in the AUTHENTICATION REQUEST message (see 3GPP TS 33.401 [19]).
39	CS service temporarily not available	This EMM cause is sent to the UE when the CS fallback or 1xCS fallback request cannot be served temporarily due to O&M reasons or a mobile terminating CS fallback call is aborted by the network during call establishment (see 3GPP TS 29.118 [16A]).
42	Severe network failure	This EMM cause is sent to the UE when the network has determined that the requested procedure cannot be completed successfully due to network failure. The failure is not expected to be temporary and repeated request is not likely to succeed in near future.
##	Causes related to invalid messages
95	Semantically incorrect message.	This cause is used to report receipt of a message with semantically incorrect contents
96	Invalid mandatory information.	This cause indicates that the equipment sending this cause has received a message with a non-semantical mandatory IE error
97	Message type non-existent or not implemented.	This cause indicates that the equipment sending this cause has received a message with a message type it does not recognize either because this is a message not defined, or defined but not implemented by the equipment sending this cause.
98	Message type not compatible with protocol state.	This cause indicates that the equipment sending this cause has received a message not compatible with the protocol state
99	Information element non-existent or not implemented.	This cause indicates that the equipment sending this cause has received a message which includes information elements not recognized because the information element identifier is not defined or it is defined but not implemented by the equipment sending the cause. However, the information element is not required to be present in the message in order for the equipment sending the cause to process the message.
100	Conditional IE error.	This cause indicates that the equipment sending this cause has received a message with conditional IE errors
101	Message not compatible with protocol state.	This cause indicates that a message has been received which is incompatible with the protocol state or that a STATUS message has been received indicating an incompatible call state.
111	Protocol error, unspecified.	This cause is used to report a protocol error event only when no other cause in the protocol error class applies.

Source:

3GPP TS 24.301 V14.0.1 (2016-06)

3rd Generation Partnership Project;

Technical Specification Group Core Network and Terminals;

Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); 

Stage 3

(Release 14)

3GPP TS 24.008 V14.0.0 (2016-06)

3rd Generation Partnership Project;

Technical Specification Group Core Network and Terminals;

Mobile radio interface Layer 3 specification;

Core network protocols; Stage 3

(Release 14)