5G E1AP - Bearer Context Modification Required

Message Fact Sheet

Protocol	e1ap	Network	5g
Spec	3GPP TS 37.483	Spec Section	Bearer Context Modification Required procedure and related IE definitions (Release 18 baseline)
Direction	gNB-CU-UP -> gNB-CU-CP initiatingMessage	Message Type	UE-associated CU-UP initiated bearer-change request

Full message name	5G E1AP - Bearer Context Modification Required
Protocol	E1AP
Technology	5G
Direction	gNB-CU-UP -> gNB-CU-CP initiatingMessage
Interface	E1 between gNB-CU-CP and gNB-CU-UP
Signaling bearer / channel	UE-associated E1AP signaling / SCTP carried E1AP initiatingMessage
Typical trigger	The CU-UP determines that the existing bearer branch requires CU-CP action, such as a control-plane driven bearer modification or follow-up reconfiguration.
Main purpose	Tells the CU-CP that the CU-UP needs a bearer-context modification action from the control plane for the current bearer branch.
Main specification	3GPP TS 37.483, Bearer Context Modification Required procedure and related IE definitions (Release 18 baseline)
Release added	Release 17
Procedures where used	CU-UP initiated bearer-change handling, Bearer-state mismatch escalation, Control-plane follow-up for active bearer state

What is Bearer Context Modification Required in simple terms?

Bearer Context Modification Required is the E1AP message the gNB-CU-UP sends to the gNB-CU-CP when the CU-UP requires the control plane to take bearer-context modification action for an existing UE.

Tells the CU-CP that the CU-UP needs a bearer-context modification action from the control plane for the current bearer branch.

Why this message matters

Bearer Context Modification Required is the CU-UP asking the CU-CP to take bearer-modification action for an existing UE.

Where this message appears in the call flow

CU-UP initiated bearer-change escalation

5G E1AP flow showing the gNB-CU-UP sending Bearer Context Modification Required to escalate a bearer-context issue to the gNB-CU-CP — Escalation branch: the CU-UP raises a bearer-change requirement toward the CU-CP instead of changing the bearer branch silently.

Call flow position: The CU-UP detects that the current bearer context needs control-plane action and raises that requirement toward the CU-CP.

Typical state: The bearer context exists, but the CU-UP is asking the CU-CP to decide and drive the next modification step.

Preconditions:

A bearer context already exists at the CU-UP.
The CU-UP has identified a condition that requires CU-CP intervention.

Next likely message: Bearer Context Modification Confirm, Bearer Context Modification Refuse, or another CU-CP bearer action

Cause-driven follow-up decision

5G E1AP flow showing Bearer Context Modification Required driving a control-plane follow-up decision at the gNB-CU-CP — Follow-up branch: Cause and the returned bearer payload guide the CU-CP toward confirm, refuse, or another bearer-control action.

Call flow position: The CU-UP reports a reason that the bearer branch needs control-plane follow-up rather than silently changing state locally.

Typical state: The CU-CP must interpret the reason and choose whether or how to continue bearer modification handling.

Preconditions:

The CU-UP can identify the bearer branch and provide a reason for escalation.

Next likely message: Control-plane decision through confirm, refuse, or later modification command

Call flow position

Previous message(s): Bearer Context Setup Response, Bearer Context Modification Response

Next message(s): Bearer Context Modification Confirm, Bearer Context Modification Refuse, Bearer Context Modification Request

Message direction and transport

Sender and receiver: gNB-CU-UP -> gNB-CU-CP initiatingMessage

Interface: E1 between gNB-CU-CP and gNB-CU-UP

Domain: CU-UP initiated bearer-change escalation toward CU-CP

Signaling bearer: UE-associated E1AP signaling

Logical channel: SCTP carried E1AP initiatingMessage

Transport / encapsulation: E1AP over SCTP/IP between gNB-CU-CP and gNB-CU-UP

Security context: Bearer Context Modification Required does not create security context. It escalates a bearer-state issue or required change from CU-UP to CU-CP.

Message Structure Overview

Bearer Context Modification Required is CU-UP initiated, unlike the ordinary modification request which is CU-CP initiated.
The message escalates a needed control-plane action rather than directly changing the bearer context locally.
From an engineering perspective, its main value is explaining why the CU-UP is asking the CU-CP to take the next step.

ASN.1 for 5G E1AP - Bearer Context Modification Required

BearerContextModificationRequired ::= SEQUENCE {
  protocolIEs ProtocolIE-Container { {BearerContextModificationRequired-IEs} },
  ...
}

BearerContextModificationRequired-IEs E1AP-PROTOCOL-IES ::= {
  { gNB-CU-CP UE E1AP ID, mandatory } |
  { gNB-CU-UP UE E1AP ID, mandatory } |
  { Cause, mandatory } |
  { System Bearer Context Modification Required, mandatory },
  ...
}

How to read this ASN.1

This message is operationally important because the CU-UP is the initiator. Read it as an escalation from user-plane reality back toward control-plane decision logic.

5G E1AP - Bearer Context Modification Required - Example Dump

E1AP-PDU
  initiatingMessage
    procedureCode: id-bearerContextModificationRequired
    criticality: reject
    value: BearerContextModificationRequired
      protocolIEs:
        - id: id-gNB-CU-CP-UE-E1AP-ID
          value: 0x00004192
        - id: id-gNB-CU-UP-UE-E1AP-ID
          value: 0x00000087
        - id: id-Cause
          value:
            radioNetwork: unspecified
        - id: id-System-BearerContextModificationRequired
          value:
            pdu-session-list:
              - pdu-session-id: 10

How to read this dump

Start by noticing the direction: this is CU-UP initiated.
Cause explains why the CU-UP is escalating bearer follow-up to the CU-CP.
The bearer payload tells the CU-CP which branch needs attention.

Important Information Elements

IE	Required	Description
`gNB-CU-CP UE E1AP ID`	Yes	Mandatory CU-CP side UE identifier used so the control plane can correlate the CU-UP initiated escalation with the right bearer context.
`gNB-CU-UP UE E1AP ID`	Yes	Mandatory CU-UP side UE identifier for the active bearer context that needs follow-up.
`Cause`	Yes	Mandatory reason explaining why the CU-UP requires CU-CP bearer-modification action.
`System Bearer Context Modification Required`	Yes	Mandatory bearer payload describing the bearer branch that requires CU-CP follow-up.

Detailed field explanation

`gNB-CU-CP UE E1AP ID`

Mandatory CU-CP side UE identifier used so the control plane can correlate the CU-UP initiated escalation with the right bearer context.

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.

`gNB-CU-UP UE E1AP ID`

Mandatory CU-UP side UE identifier for the active bearer context that needs follow-up.

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.

`Cause`

Mandatory reason explaining why the CU-UP requires CU-CP bearer-modification action.

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.

`System Bearer Context Modification Required`

Mandatory bearer payload describing the bearer branch that requires CU-CP follow-up.

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.

What to check in logs and traces

Confirm the message direction is CU-UP to CU-CP.
Match both UE identifiers with the active bearer context.
Read Cause before deciding whether the next action should be confirm, refuse, or another modification path.

Common Issues and Troubleshooting

The CU-UP is asking for control-plane action on a bearer branch that seemed stable.

Likely cause: The CU-UP detected a bearer-state condition that requires explicit CU-CP follow-up rather than silent local handling.

What to inspect: Read Bearer Context Modification Required and inspect Cause together with the related bearer payload.

Next step: Drive the next action from the CU-UP reason instead of assuming the old bearer state is still sufficient.

LTE / 5G / Variant Comparison

Compared with Bearer Context Modification Request

Modification Request is CU-CP initiated. Modification Required is CU-UP initiated and asks the CU-CP to decide the next bearer-modification action.

FAQ

What is Bearer Context Modification Required in 5G E1AP?

It is the E1AP message the CU-UP sends when it requires the CU-CP to take bearer-context modification action.

Why is this message important?

It is important because it shows the CU-UP initiating the need for a new control-plane bearer decision.

Related message pages

Related Procedures

Related Tools

Use This Reference in Practice

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.