Cause values for EPS session management

The main function of the ESM sublayer is to support the EPS bearer context handling in the UE and in the MME.

The ESM comprises procedures for:

-     the activation, deactivation and modification of EPS bearer contexts;

-     the request for resources (IP connectivity to a PDN or dedicated bearer resources) by the UE; and

-     the transport of user data via the control plane between the UE and the MME.

Each EPS bearer context represents an EPS bearer between the UE and a PDN. EPS bearer contexts can remain activated even if the radio and S1 bearers constituting the corresponding EPS bearers between UE and MME are temporarily released.

	Cause values for EPS session management
	Causes related to nature of request
Cause #8	Operator Determined Barring	This ESM cause is used by the network to indicate that the requested service was rejected by the MME due to Operator Determined Barring.
Cause #26	Insufficient resources	This ESM cause is used by the UE or by the network to indicate that the requested service cannot be provided due to insufficient resources.
Cause #27	Missing or unknown APN	This ESM cause is used by the network to indicate that the requested service was rejected by the external packet data network because the access point name was not included although required or if the access point name could not be resolved.
Cause #28	Unknown PDN type	This ESM cause is used by the network to indicate that the requested service was rejected by the external packet data network because the PDN type could not be recognised.
Cause #29	User authentication failed	This ESM cause is used by the network to indicate that the requested service was rejected by the external packet data network due to a failed user authentication.
Cause #30	Request rejected by Serving GW or PDN GW	This ESM cause is used by the network to indicate that the requested service or operation or the request for a resource was rejected by the Serving GW or PDN GW.
Cause #31	Request rejected, unspecified	This ESM cause is used by the network or by the UE to indicate that the requested service or operation or the request for a resource was rejected due to unspecified reasons.
Cause #32	Service option not supported	This ESM cause is used by the network when the UE requests a service which is not supported by the PLMN.
Cause #33	Requested service option not subscribed	This ESM cause is sent when the UE requests a service option for which it has no subscription.
Cause #34	Service option temporarily out of order	This ESM cause is sent when the network cannot service the request because of temporary outage of one or more functions required for supporting the service.
Cause #35	PTI already in use	This ESM cause is used by the network to indicate that the PTI included by the UE is already in use by another active UE requested procedure for this UE.
Cause #36	Regular deactivation	This ESM cause is used to indicate a regular UE or network initiated release of EPS bearer resources.
Cause #37	EPS QoS not accepted	This ESM cause is used by the network if the new EPS QoS cannot be accepted that was indicated in the UE request.
Cause #38	Network failure	This ESM cause is used by the network to indicate that the requested service was rejected due to an error situation in the network.
Cause #39	Reactivation requested	This ESM cause is used by the network to request a PDN connection reactivation.
Cause #41	Semantic error in the TFT operation.	This ESM cause is used by the network or the UE to indicate that the requested service was rejected due to a semantic error in the TFT operation included in the request.
Cause #42	Syntactical error in the TFT operation.	This ESM cause is used by the network or the UE to indicate that the requested service was rejected due to a syntactical error in the TFT operation included in the request.
Cause #43	Invalid EPS bearer identity	This ESM cause is used by the network or the UE to indicate that the EPS bearer identity value provided to it is not a valid value for the received message or the EPS bearer context identified by the linked EPS bearer identity IE in the request is not active.
Cause #44	Semantic errors in packet filter(s)	This ESM cause is used by the network or the UE to indicate that the requested service was rejected due to one or more semantic errors in packet filter(s) of the TFT included in the request.
Cause #45	Syntactical error in packet filter(s)	This ESM cause is used by the network or the UE to indicate that the requested service was rejected due to one or more syntactical errors in packet filter(s) of the TFT included in the request.
Cause #47	PTI mismatch	This ESM cause is used by the UE to indicate that the PTI value which is included in the ESM message that the UE receives does not match a PTI in use.
Cause #49	Last PDN disconnection not allowed	This ESM cause is used by the network, in case of EMM-REGISTERED without PDN connection is not supported by the UE or the MME, to indicate that the UE requested PDN disconnection procedure on the last remaining PDN connection is not allowed.
Cause #50	PDN type IPv4 only allowed	This ESM cause is used by the network to indicate that only PDN type IPv4 is allowed for the requested PDN connectivity.
Cause #51	PDN type IPv6 only allowed	This ESM cause is used by the network to indicate that only PDN type IPv6 is allowed for the requested PDN connectivity.
Cause #52	single address bearers only allowed	This ESM cause is used by the network to indicate that the requested PDN connectivity is accepted with the restriction that only single IP version bearers are allowed.
Cause #53	ESM information not received	This ESM cause is used by the network to indicate that the PDN connectivity procedure was rejected due to the ESM information was not received.
Cause #54	PDN connection does not exist	This ESM cause is used by the network at handover from a non-3GPP access network to indicate that the MME does not have any information about the requested PDN connection.
Cause #55	Multiple PDN connections for a given APN not allowed	This ESM cause is used by the network to indicate that the PDN connectivity procedure was rejected due to multiple PDN connections for a given APN are not allowed.
Cause #56	Collision with network initiated request	This ESM cause is used by the network to indicate that the network has already initiated the activation, modification or deactivation of bearer resources which was requested by the UE.
Cause #59	Unsupported QCI value	This ESM cause is used by the network if the QCI indicated in the UE request cannot be supported.
Cause #60	Bearer handling not supported	This ESM cause is used by the network to indicate that the procedure requested by the UE was rejected because the bearer handling is not supported.
Cause #65	Maximum number of EPS bearers reached	This ESM cause is used by the network to indicate that the procedure requested by the UE was rejected as the network has reached the maximum number of simultaneously active EPS bearer contexts for the UE.
Cause #66	Requested APN not supported in current RAT and PLMN combination	This ESM cause is used by the network to indicate that the procedure requested by the UE was rejected as the requested APN is not supported in the current RAT and PLMN.
Cause #81	Invalid PTI value	This ESM cause is used by the network or UE to indicate that the PTI provided to it is unassigned or reserved.
Cause #112	APN restriction value incompatible with active EPS bearer context.	This ESM cause is used by the network to indicate that the EPS bearer context(s) have an APN restriction value that is not allowed in combination with a currently active EPS bearer context. Restriction values are defined in 3GPP TS 23.060 [4].
Cause #113	Multiple accesses to a PDN connection not allowed	This ESM cause is used by the network to indicate that multiple accesses to a PDN connection for NBIFOM is not allowed.
	Protocol errors (e.g., unknown message) class
Cause #95	Semantically incorrect message	This ESM cause is used to report receipt of a message with semantically incorrect contents.
Cause #96	Invalid mandatory information	This ESM cause indicates that the equipment sending this ESM cause has received a message with a non-semantical mandatory IE error.
Cause #97	Message type non-existent or not implemented	This ESM cause indicates that the equipment sending this ESM 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 ESM cause.
Cause #98	Message type not compatible with protocol state	This ESM cause indicates that the equipment sending this ESM cause has received a message not compatible with the protocol state.
Cause #99	Information element non-existent or not implemented	This ESM cause indicates that the equipment sending this ESM 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 ESM cause. However, the information element is not required to be present in the message in order for the equipment sending the ESM cause to process the message.
Cause #100	Conditional IE error	This ESM cause indicates that the equipment sending this cause has received a message with conditional IE errors.
Cause #101	Message not compatible with protocol state	This ESM cause indicates that a message has been received which is incompatible with the protocol state.
Cause #111	Protocol error, unspecified	This ESM cause is used to report a protocol error event only when no other ESM 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)