Bearer Context Modification Confirm is the E1AP message the gNB-CU-CP sends after Bearer Context Modification Required to confirm the control-plane action that the gNB-CU-UP requested for an active bearer context.
Message Fact Sheet
Protocol
e1ap
Network
5g
Spec
3GPP TS 37.483
Spec Section
Bearer Context Modification Required follow-up and related IE definitions (Release 18 baseline)
What is Bearer Context Modification Confirm in simple terms?
Bearer Context Modification Confirm is the E1AP message the gNB-CU-CP sends after Bearer Context Modification Required to confirm the control-plane action that the gNB-CU-UP requested for an active bearer context.
Confirms the control-plane follow-up chosen by the CU-CP after the CU-UP raised Bearer Context Modification Required for an existing bearer branch.
Why this message matters
Bearer Context Modification Confirm is the CU-CP saying yes to the bearer follow-up that the CU-UP asked for.
Where this message appears in the call flow
Confirmed CU-UP initiated bearer follow-up
Confirmation branch: the CU-CP accepts the CU-UP initiated bearer-change escalation and confirms the control-plane follow-up direction.
Call flow position: The CU-UP has escalated a bearer issue and the CU-CP confirms the follow-up direction on the same procedural branch.
Typical state: The control plane accepts the need for follow-up and the bearer branch now proceeds under the confirmed decision.
Preconditions:
Bearer Context Modification Required was received from the CU-UP.
The CU-CP has chosen to confirm the requested follow-up path.
Next likely message: Bearer Context Modification Request or another confirmed bearer-control continuation
Cause-driven confirm path
Follow-up branch: the confirm message tells the CU-UP that the bearer-control escalation was accepted and can move into the next control-plane step.
Call flow position: The confirm message closes the immediate decision point opened by the CU-UP initiated request.
Typical state: The bearer issue raised by the CU-UP has an accepted control-plane direction.
Preconditions:
The CU-CP has interpreted the reason and bearer payload carried in Bearer Context Modification Required.
Next likely message: A concrete bearer-control action on the confirmed path
Sender and receiver: gNB-CU-CP -> gNB-CU-UP successfulOutcome-style follow-up
Interface: E1 between gNB-CU-CP and gNB-CU-UP
Domain: CU-CP response to CU-UP initiated bearer-change escalation
Signaling bearer: UE-associated E1AP signaling
Logical channel: SCTP carried E1AP follow-up response on the modification-required path
Transport / encapsulation: E1AP over SCTP/IP between gNB-CU-CP and gNB-CU-UP
Security context: Bearer Context Modification Confirm does not create security context. It confirms the control-plane handling of a CU-UP initiated bearer-change requirement.
Message Structure Overview
Bearer Context Modification Confirm is part of the follow-up to Bearer Context Modification Required.
Its main value is that it confirms the CU-CP accepted the CU-UP initiated bearer-change direction.
Engineers should read it together with the earlier Modification Required payload.
ASN.1 for 5G E1AP - Bearer Context Modification Confirm
Read confirm together with the earlier Bearer Context Modification Required message.
The important question is what control-plane path the CU-CP accepted.
Important Information Elements
IE
Required
Description
gNB-CU-CP UE E1AP ID
Yes
Mandatory CU-CP side UE identifier used to correlate the confirm with the bearer branch under discussion.
gNB-CU-UP UE E1AP ID
Yes
Mandatory CU-UP side UE identifier for the active bearer context that triggered the modification-required path.
System Bearer Context Modification Confirm
Yes
Mandatory payload that confirms the control-plane follow-up for the bearer branch raised by the CU-UP.
Detailed field explanation
gNB-CU-CP UE E1AP ID
Mandatory CU-CP side UE identifier used to correlate the confirm with the bearer branch under discussion.
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 triggered the modification-required path.
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 Confirm
Mandatory payload that confirms the control-plane follow-up for the bearer branch raised by the CU-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
Match the confirm to the preceding Bearer Context Modification Required branch.
Use both UE identifiers to tie the confirm to the active bearer context.
Check what confirmed bearer-control action is implied next.
Common Issues and Troubleshooting
The CU-UP asks for bearer follow-up, but later traces do not clearly show whether the CU-CP accepted that direction.
Likely cause: The confirm path may be missing, mis-correlated, or followed by a different bearer-control branch than expected.
What to inspect: Read Bearer Context Modification Confirm together with the earlier Modification Required payload.
Next step: Drive the rest of the trace from the confirmed control-plane decision, not from the original CU-UP request alone.
LTE / 5G / Variant Comparison
Compared with Bearer Context Modification Required
Modification Required is the CU-UP asking for control-plane action. Modification Confirm is the CU-CP accepting that follow-up direction.
FAQ
What is Bearer Context Modification Confirm in 5G E1AP?
It is the E1AP message the CU-CP sends to confirm the follow-up requested by a CU-UP initiated Bearer Context Modification Required procedure.
Why does Bearer Context Modification Confirm matter?
It matters because it shows that the CU-CP accepted the control-plane follow-up direction requested by the CU-UP.
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.