What is Activate Default EPS Bearer Context Reject in LTE?
It is the UE message that rejects the default bearer activation proposed by the network.
| Protocol | nas | Network | lte |
|---|---|---|---|
| Spec | 3GPP TS 24.301 | Spec Section | 6.4.1.3, 8.3.5 |
| Direction | UE to MME | Message Type | ESM signaling |
| Full message name | LTE Activate Default EPS Bearer Context Reject |
|---|---|
| Protocol | NAS |
| Technology | LTE |
| Direction | UE to MME |
| Interface | N1 over LTE access / S1-MME control path |
| Signaling bearer / channel | NAS signaling / Sent as the failure branch after Activate Default EPS Bearer Context Request. |
| Typical trigger | Triggered when the UE cannot apply the returned default bearer configuration. |
| Main purpose | Returns the ESM cause that explains why the UE rejected the proposed default bearer definition. |
| Main specification | 3GPP TS 24.301, 6.4.1.3, 8.3.5 |
| Release added | Release 8 |
| Procedures where used | Default EPS Bearer Context Activation Procedure |
| Related timers | T3485 |
| Related cause values | ESM cause |
Activate Default EPS Bearer Context Reject is the LTE NAS message the UE sends when it cannot accept the default bearer the network tried to activate.
Returns the ESM cause that explains why the UE rejected the proposed default bearer definition.
Activate Default EPS Bearer Context Reject means the UE did not accept the default bearer the network offered.
Call flow position: UE reject message sent when the default bearer inside the attach-related branch cannot be accepted.
Typical state: Attach may continue or fail depending on the wider branch, but the proposed bearer itself was not accepted.
Preconditions:
Next likely message: Attach or PDN failure handling
Call flow position: UE reject message sent when a standalone PDN-connectivity branch returned a default bearer the UE cannot accept.
Typical state: The PDN branch is failing at bearer activation time.
Preconditions:
Next likely message: PDN failure handling
Call flow position: UE reject message sent when another PDN connection such as IMS returned a default bearer that the UE cannot apply.
Typical state: The earlier registration may remain intact, but the new PDN branch is failing at default bearer activation time.
Preconditions:
Next likely message: Additional APN or IMS failure handling
Previous message(s): Activate Default EPS Bearer Context Request
Next message(s): Bearer setup failure handling
Security context: Protected by the active NAS security context.
Activate Default EPS Bearer Context Reject
ESM cause
Protocol configuration options OPTIONAL
Extended protocol configuration options OPTIONAL
Read the ESM cause first because it explains why the UE rejected the proposed default bearer.
Activate Default EPS Bearer Context Reject
Protocol discriminator: EPS session management
EPS bearer identity: 5
Procedure transaction identity: 3
Message type: Activate Default EPS Bearer Context Reject
ESM cause: insufficient resources
| IE | Required | Description |
|---|---|---|
ESM cause | Yes | Explains why the UE rejected the default bearer activation. |
Protocol configuration options | Optional | May carry additional configuration-side detail related to the reject decision. |
ESM causeExplains why the UE rejected the default bearer activation.
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.
Protocol configuration optionsMay carry additional configuration-side detail related to the reject decision.
Presence: Optional
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 UE may have rejected the proposed bearer definition.
What to inspect: Check Activate Default EPS Bearer Context Request and the returned ESM cause in the reject.
Next step: Treat the issue as bearer-activation failure rather than only an attach problem.
It is the UE message that rejects the default bearer activation proposed by the network.
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.