Sign in Subscribe

E-RAB Release Confirm

Last updated on 


In LTE (Long-Term Evolution) and 5G networks, the E-RAB (Evolved Radio Access Bearer) Release Confirm procedure is a critical step in terminating or releasing an established E-RAB. An E-RAB is a dedicated communication path between the user equipment (UE) and the core network, used to transmit data for specific services. The Release Confirm procedure ensures that the resources associated with the E-RAB are properly deallocated and the UE transitions to the correct state. Here's a technical explanation of the E-RAB Release Confirm procedure:

1. E-RAB Release Initiation:

  • E-RAB Deactivation: The E-RAB Release Confirm procedure is initiated when there is a need to deactivate or release an established E-RAB. This can occur for various reasons, including the completion of a data session, handovers, or network optimization.

2. UE-to-eNodeB/gNodeB Message:

  • UE Signaling: The UE sends an E-RAB Release Command message to the serving eNodeB (in LTE) or gNodeB (in 5G). This message indicates the UE's intention to release the specific E-RAB.

3. eNodeB/gNodeB Processing:

  • Message Handling: The eNodeB/gNodeB receives the E-RAB Release Command from the UE and processes it.
  • Release Validation: The eNodeB/gNodeB verifies the validity of the release request, ensuring that it pertains to an established E-RAB and that the request is in line with network policies.

4. E-RAB Release Signaling:

  • Release Request to MME: If the eNodeB/gNodeB determines that the release request is valid, it forwards the E-RAB Release Command message to the Mobility Management Entity (MME) in the core network.
  • Confirmation Pending: The eNodeB/gNodeB may acknowledge the UE's request by sending an E-RAB Release Request Acknowledgment message to the UE, indicating that the release procedure is in progress.

5. MME Handling:

  • Release Confirmation to Core Network: The MME processes the E-RAB Release Command message received from the eNodeB/gNodeB and verifies the release request.
  • Resource Deallocation: The MME initiates the deallocation of resources associated with the E-RAB within the core network and informs relevant network elements, including the Serving Gateway (S-GW) and Packet Data Network Gateway (P-GW), to release their resources.

6. E-RAB Release Confirmation:

  • MME Confirmation to eNodeB/gNodeB: Once the MME has successfully deallocated the resources and verified the E-RAB release, it sends an E-RAB Release Confirm message to the eNodeB/gNodeB.
  • Release Indication to UE: The eNodeB/gNodeB receives the E-RAB Release Confirm message and forwards it to the UE. This informs the UE that the E-RAB has been successfully released.

7. UE State Transition:

  • UE Response: Upon receiving the E-RAB Release Confirm message, the UE transitions its internal state accordingly. The UE releases any remaining resources associated with the E-RAB and updates its context.

8. Continued Operation:

  • Post-Release Operation: After the E-RAB Release Confirm procedure, the UE can continue its communication, establish new E-RABs if needed, or transition to a different operational state based on the network's requirements.

The E-RAB Release Confirm procedure is crucial for efficiently managing network resources and ensuring that communication resources are deallocated when no longer needed. It allows for the graceful termination of communication sessions and is an essential part of LTE and 5G network operation.