What is Activate Dedicated EPS Bearer Context Reject in LTE?
It is the UE message that rejects the dedicated bearer activation proposed by the network.
| Protocol | nas | Network | lte |
|---|---|---|---|
| Spec | 3GPP TS 24.301 | Spec Section | 6.4.2.3, 8.3.2 |
| Direction | UE to MME | Message Type | ESM signaling |
| Full message name | LTE Activate Dedicated 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 Dedicated EPS Bearer Context Request. |
| Typical trigger | Triggered when the UE cannot apply the dedicated bearer parameters returned by the network. |
| Main purpose | Returns the ESM cause that explains why the UE rejected the proposed dedicated bearer. |
| Main specification | 3GPP TS 24.301, 6.4.2.3, 8.3.2 |
| Release added | Release 8 |
| Procedures where used | Dedicated EPS Bearer Context Activation Procedure |
| Related timers | T3485 |
| Related cause values | ESM cause |
Activate Dedicated EPS Bearer Context Reject is the LTE NAS message the UE sends when it cannot accept the dedicated bearer the network tried to activate.
Returns the ESM cause that explains why the UE rejected the proposed dedicated bearer.
Activate Dedicated EPS Bearer Context Reject means the UE did not accept the dedicated bearer the network proposed.
Call flow position: UE reject message sent when a dedicated bearer for a service-specific branch cannot be accepted.
Typical state: The default bearer may stay active, but the additional dedicated bearer was not accepted.
Preconditions:
Next likely message: Service-specific failure handling
Call flow position: UE reject message sent when the dedicated bearer for IMS or another QoS-sensitive service cannot be applied.
Typical state: The wider PDN branch may survive, but the requested dedicated bearer activation failed.
Preconditions:
Next likely message: Service continuation on default bearer or failure handling
Call flow position: UE reject message sent when a dedicated bearer created from an earlier bearer-resource procedure cannot be applied.
Typical state: The resource request reached bearer activation, but the dedicated bearer itself was not accepted.
Preconditions:
Next likely message: Bearer-resource failure handling
Previous message(s): Activate Dedicated EPS Bearer Context Request
Next message(s): Dedicated bearer failure handling
Security context: Protected by the active NAS security context.
Activate Dedicated 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 dedicated bearer.
Activate Dedicated EPS Bearer Context Reject
Protocol discriminator: EPS session management
EPS bearer identity: 6
Procedure transaction identity: 9
Message type: Activate Dedicated EPS Bearer Context Reject
ESM cause: EPS QoS not accepted
| IE | Required | Description |
|---|---|---|
ESM cause | Yes | Explains why the UE rejected the dedicated bearer activation. |
Protocol configuration options | Optional | May carry additional configuration-side detail related to the reject branch. |
ESM causeExplains why the UE rejected the dedicated 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 branch.
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 dedicated bearer activation.
What to inspect: Check Activate Dedicated EPS Bearer Context Request and the returned ESM cause.
Next step: Treat the problem as dedicated-bearer activation failure rather than default-bearer loss.
It is the UE message that rejects the dedicated 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.