Sign in Subscribe

RRC Connection Reestablishment Cause

Last updated on 


The RRC (Radio Resource Control) Connection Reestablishment Cause is an element within the RRC Connection Reestablishment Request message in LTE (Long-Term Evolution) and 5G wireless networks. It provides information about the reason for the reestablishment of an RRC connection between the User Equipment (UE) and the network. Understanding the cause is essential for network management and troubleshooting. Here's a detailed technical explanation of the RRC Connection Reestablishment Cause:

1. Initial RRC Connection:

  • Normal Operation: The UE and the network are initially connected, allowing the UE to access network services.

2. Trigger for Reestablishment:

  • Connection Interruption: The need for RRC connection reestablishment arises when the current RRC connection is temporarily lost or disrupted. The cause for this interruption could be due to various factors.

3. UE Monitoring:

  • RRC State Tracking: The UE continuously monitors its RRC state, which indicates whether it is actively connected or in an idle state.
  • Connection Loss Detection: The UE detects when the RRC connection is lost.

4. RRC Connection Reestablishment Request Generation:

  • UE Initiates Request: When the UE detects the loss of the RRC connection and determines that reestablishment is required, it generates an RRC Connection Reestablishment Request message.
  • Cause Information: Within the message, the UE includes information about the cause of the reestablishment.

5. RRC Connection Reestablishment Cause Types:

  • Numerical Codes: The cause information is typically represented as a numerical code, where each code corresponds to a specific type of reestablishment cause.
  • Common Causes: Common causes for RRC connection reestablishment include handover failure, radio link failure, cell change failure, and mobility management-related issues.

6. Message Signaling:

  • Transmission to Network: The UE sends the RRC Connection Reestablishment Request message to the network's eNodeB (in LTE) or gNodeB (in 5G) over the radio interface.

7. Network Handling:

  • Message Reception: The eNodeB/gNodeB receives the RRC Connection Reestablishment Request message from the UE.
  • Cause Interpretation: The network interprets the cause code to understand why the UE is requesting the reestablishment.

8. Network Response:

  • RRC Connection Reestablishment Acceptance: If the network determines that reestablishment is permissible and necessary based on the cause, it generates an RRC Connection Reestablishment Acceptance message.
  • Message Contents: The acceptance message may include details about granted resources, timing, and parameters for the reestablished connection.

9. Message Signaling:

  • Response to UE: The RRC Connection Reestablishment Acceptance message is sent back to the UE over the radio interface.

10. UE Processing:

  • Message Reception: The UE receives the RRC Connection Reestablishment Acceptance message and processes it.
  • Context Configuration: The UE configures its radio context based on the parameters provided in the acceptance message, preparing for the reestablished connection.

11. RRC Connection Reestablishment:

  • Connection Resumption: The UE transitions from the RRC idle state back to an active RRC connection state, resuming communication with the network.
  • Reactivation of Services: Services and data transfer can be resumed, and the UE can participate in network activities.

The RRC Connection Reestablishment Cause provides crucial information for diagnosing and addressing the specific issues that led to the loss of the RRC connection. It enables the network to take appropriate actions to address the underlying cause and ensure that the UE can reconnect and continue operating seamlessly within the network.