Sign in Subscribe

E-RAB Release Response

Last updated on 


The E-RAB (Evolved Radio Access Bearer) Release Response procedure in LTE (Long-Term Evolution) and 5G networks is a crucial step in terminating or releasing an established dedicated bearer, which is a communication path between the user equipment (UE) and the core network. This procedure involves signaling exchanges between the UE, the eNodeB (in LTE), or the gNodeB (in 5G), and the core network entities. Below is a technical explanation of the E-RAB Release Response procedure:

1. E-RAB Release Request and Initiation:

  • UE Request: The E-RAB Release Response procedure is initiated in response to an E-RAB Release Request, which may have been initiated by the UE or the network. The UE or the network decides to release a dedicated bearer for various reasons, including session completion, handovers, or network optimization.

2. UE Signaling (E-RAB Release Command):

  • UE-to-eNodeB/gNodeB Message: If the UE initiated the release, it 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 and may include a release cause, explaining the reason for the release.

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 complies with network policies.

4. E-RAB Release Signaling (to MME):

  • 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.
  • Release Cause Forwarding: The eNodeB/gNodeB includes information about the release cause in the message to the MME, indicating the reason for the release.

5. MME Handling:

  • Release Confirmation to Core Network: The MME processes the E-RAB Release Command message received from the eNodeB/gNodeB and validates 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 (E-RAB Release Response):

  • 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 Response message to the eNodeB/gNodeB.
  • Release Confirmation to UE: The eNodeB/gNodeB receives the E-RAB Release Response message and forwards it to the UE. This confirms the successful release of the E-RAB.

7. UE State Transition:

  • UE Response: Upon receiving the E-RAB Release Response 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 Response 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 Response 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.