What is ESM Status in LTE?
It is the LTE NAS message used to report an ESM protocol error or invalid session-management message handling condition.
| Protocol | nas | Network | lte |
|---|---|---|---|
| Spec | 3GPP TS 24.301 | Spec Section | Release 18 message definition for ESM Status |
| Direction | UE to MME | Message Type | ESM signaling |
| Full message name | LTE ESM Status |
|---|---|
| Protocol | NAS |
| Technology | LTE |
| Direction | UE to MME |
| Interface | N1 over LTE access / S1-MME control path |
| Signaling bearer / channel | NAS signaling / Sent during active ESM signaling when an ESM protocol error is detected. |
| Typical trigger | Triggered when an ESM message is semantically wrong, malformed, or not compatible with the current ESM state. |
| Main purpose | Carries an ESM cause value so the peer can understand why the received ESM message could not be processed correctly. |
| Main specification | 3GPP TS 24.301, Release 18 message definition for ESM Status |
| Release added | Release 8 |
| Procedures where used | ESM protocol error handling |
| Related cause values | ESM cause |
ESM Status is the LTE NAS message used to report an ESM protocol error, invalid state, or malformed session-management message.
Carries an ESM cause value so the peer can understand why the received ESM message could not be processed correctly.
ESM Status is the LTE NAS message used to report a session-management protocol error.
Call flow position: Error-report message sent when the received ESM message does not fit the current ESM state.
Typical state: The branch is active, but the peer sent an ESM message that cannot be handled in the current state.
Preconditions:
Next likely message: Procedure abort or later corrected signaling
Call flow position: Error-report message sent when mandatory information is missing or invalid in an ESM message.
Typical state: The receiving side rejects the current ESM message as a protocol error.
Preconditions:
Next likely message: Procedure abort or recovery handling
Previous message(s): PDN Connectivity Request, Activate Default EPS Bearer Context Request, Modify EPS Bearer Context Request
Next message(s): Procedure abort, Protocol recovery handling
Security context: Usually protected because it reports an error on an already active ESM branch.
ESM Status
ESM cause
Read ESM Status from the returned ESM cause first and then correlate it with the message that triggered the protocol error.
ESM Status
Protocol discriminator: EPS session management
EPS bearer identity: 0
Procedure transaction identity: 3
Message type: ESM Status
ESM cause: message type not compatible with protocol state
| IE | Required | Description |
|---|---|---|
ESM cause | Yes | Explains why the received ESM message could not be processed. |
ESM causeExplains why the received ESM message could not be processed.
Presence: Required
In practice: In practice, compare this field with the original request and with any later release-dependent optional fields so you can see whether the network accepted the same service model the UE asked for.
Likely cause: The branch may have ended with ESM Status because one side treated the previous ESM message as invalid.
What to inspect: Check the earlier ESM message and the returned ESM cause.
Next step: Treat the branch as protocol error handling rather than normal PDN or bearer reject logic.
It is the LTE NAS message used to report an ESM protocol error or invalid session-management message handling condition.
Decode this message with the 3GPP Decoder, inspect the related message database, or open the matching call flow to see where this signaling step fits in the full procedure.