Sign in Subscribe

E-RAB Modify Request

Last updated on 


The E-RAB (Evolved Radio Access Bearer) Modify Request procedure in LTE (Long-Term Evolution) and 5G networks is used to request changes or modifications to an existing dedicated bearer, which is a communication path between the user equipment (UE) and the core network. These modifications can include changes to Quality of Service (QoS) parameters, security settings, or other characteristics of the bearer. Below is a technical explanation of the E-RAB Modify Request procedure:

1. E-RAB Modification Trigger:

  • UE Request: The E-RAB Modify Request procedure can be initiated by the UE when it needs to request changes to an existing dedicated bearer, such as requesting higher data rates, different QoS parameters, or changes in security configuration.
  • Network-Initiated: Alternatively, the network may initiate an E-RAB modification due to network optimization, handovers, or policy changes.

2. UE Signaling:

  • UE-to-eNodeB/gNodeB Message: If the UE initiates the modification, it sends an E-RAB Modify Request message to the serving eNodeB (in LTE) or gNodeB (in 5G). This message contains details about the requested modifications, including new QoS parameters or security settings.
  • Modification Cause: The message may include a modification cause, indicating the reason for the requested changes (e.g., UE-requested, handover).

3. eNodeB/gNodeB Processing:

  • Message Handling: The eNodeB/gNodeB receives the E-RAB Modify Request message from the UE and processes it.
  • Modification Validation: The eNodeB/gNodeB verifies the validity of the modification request, ensuring that it pertains to an established E-RAB and that the request is consistent with network policies.

4. E-RAB Modification Signaling:

  • Forwarding to MME: If the eNodeB/gNodeB determines that the modification request is valid, it forwards the E-RAB Modify Request message to the Mobility Management Entity (MME) in the core network.
  • Notification: The eNodeB/gNodeB may send a notification to the UE indicating that the modification procedure is in progress.

5. MME Handling:

  • Handling the Request: The MME processes the E-RAB Modify Request message received from the eNodeB/gNodeB and validates the request.
  • Resource Negotiation: The MME negotiates with the eNodeB/gNodeB to apply the requested modifications to the E-RAB.

6. E-RAB Modification Confirmation:

  • MME Confirmation to Core Network: Once the MME has successfully negotiated the requested changes and updated the E-RAB parameters, it sends an E-RAB Modify Response message to the eNodeB/gNodeB.
  • Confirmation to UE: The eNodeB/gNodeB receives the E-RAB Modify Response message and forwards it to the UE, confirming that the requested modifications have been applied.

7. UE State Transition:

  • UE Response: Upon receiving the E-RAB Modify Response message, the UE transitions its internal state accordingly. It adjusts its context to reflect the modified E-RAB parameters.

8. Continued Data Transfer:

  • Post-Modification Operation: After a successful E-RAB Modify Request procedure, the UE and the network continue data transfer over the modified dedicated bearer according to the updated parameters and configurations.

The E-RAB Modify Request procedure is essential for adapting communication sessions to changing requirements, ensuring that the network resources are optimized for the current needs of the UE and the network. It allows for real-time adjustments to bearer characteristics, enhancing the efficiency and flexibility of LTE and 5G networks.