Sign in Subscribe

Explain the significance of TAU Reject Causes and their impact on UE mobility.

Last updated on 


The Tracking Area Update (TAU) Reject Causes in LTE play a significant role in managing the mobility of User Equipment (UE), such as smartphones and other mobile devices, within the LTE network. When a UE initiates a TAU procedure to update its location, the network may respond with a TAU Reject message containing a specific cause. The TAU Reject Causes have various implications for UE mobility, and understanding them is crucial for efficient network management. Let's delve into the technical details:

  1. Insufficient Resources (TAU Reject Cause 12):
    • Significance: The network may lack the necessary resources to handle the TAU request at that moment.
    • Impact on UE Mobility: The UE might need to delay its TAU or attempt the procedure later when the network has more available resources. This can affect the UE's ability to quickly update its location information.
  2. Failure in the Radio Interface Procedure (TAU Reject Cause 17):
    • Significance: This cause indicates a failure in the radio interface procedure during the TAU.
    • Impact on UE Mobility: The UE may need to address the radio interface issue before successfully completing the TAU. This could involve reestablishing the radio connection or resolving radio-related problems.
  3. PLMN not Allowed (TAU Reject Cause 13):
    • Significance: The UE is attempting a TAU for a Public Land Mobile Network (PLMN) that is not allowed in the current location.
    • Impact on UE Mobility: The UE may need to select a different PLMN or wait until it enters an area where the desired PLMN is allowed. This can affect the UE's ability to connect to its preferred network.
  4. TAU/RAU Procedure in Progress (TAU Reject Cause 21):
    • Significance: The TAU/RAU (Routing Area Update) procedure is already in progress for the UE.
    • Impact on UE Mobility: The UE may need to wait until the ongoing procedure completes before initiating another TAU. This ensures orderly handling of mobility procedures within the network.
  5. Roaming Not Allowed in This Tracking Area (TAU Reject Cause 19):
    • Significance: The UE is not allowed to roam in the current tracking area.
    • Impact on UE Mobility: The UE may need to move to a different tracking area or location where roaming is allowed to successfully complete the TAU. This restriction may impact the UE's ability to roam freely between tracking areas.
  6. UE Not Reachable for PS (TAU Reject Cause 39):
    • Significance: The UE is not reachable for packet-switched (PS) services.
    • Impact on UE Mobility: The UE may need to resolve issues related to its PS services, such as activating data services, before attempting the TAU again. This can affect the UE's ability to use data services in the new location.
  7. Security Mode Rejected (TAU Reject Cause 26):
    • Significance: The network rejects the security mode requested by the UE during the TAU procedure.
    • Impact on UE Mobility: The UE may need to renegotiate security parameters with the network before successfully completing the TAU. This ensures the security and integrity of communication between the UE and the network.

Understanding these TAU Reject Causes is essential for network operators to troubleshoot issues, optimize network performance, and ensure seamless UE mobility. It enables the network to communicate specific reasons for rejection to the UE, guiding the device in taking appropriate actions to address the issues and successfully complete the mobility procedures.