Sign in Subscribe

How does LTE handle tracking area updates that fail to be accepted by the network?

Last updated on 


When a Tracking Area Update (TAU) in LTE (Long-Term Evolution) fails to be accepted by the network, the network responds by sending a TAU Reject message to the User Equipment (UE). This rejection can occur for various reasons, including authentication failure, insufficient resources, or other operational constraints. Here's a technical explanation of how LTE handles tracking area updates that fail to be accepted:

1. Initiation of Tracking Area Update:

  • The TAU procedure is initiated by the UE when there is a change in its location, such as moving to a new tracking area. The UE sends a TAU Request to the Evolved Packet Core (EPC) network.

2. Network Processing:

  • The EPC processes the TAU Request, which involves verifying the UE's identity, validating the requested tracking area update, and checking for any additional mobility-related information.

3. Validation Criteria:

  • The network applies various validation criteria to determine whether it can accept the TAU Request. This includes checks for authentication, authorization, network congestion, or other operational constraints.

4. Preparation of TAU Reject:

  • If the TAU Request cannot be accepted based on the validation criteria, the EPC prepares a TAU Reject message. This message includes a rejection cause that indicates the reason for rejecting the TAU request.

5. Information Included in TAU Reject:

  • The TAU Reject message typically includes:
    • Rejection Cause: A numerical code or specific cause indicating the reason for rejecting the TAU Request. Examples include authentication failure, insufficient resources, or UE not reachable.

6. Sending TAU Reject to UE:

  • The EPC sends the TAU Reject message to the UE using the appropriate radio resources. The message is transmitted over the radio interface to reach the UE.

7. UE Processing:

  • Upon receiving the TAU Reject, the UE processes the information contained in the message. It interprets the rejection cause and takes appropriate actions based on the reason for rejection.

8. Fallback Procedures:

  • Depending on the rejection cause, the UE may initiate fallback procedures. For example, it may retry the TAU procedure after a certain period, attempt to connect to an alternative tracking area, or perform other mobility-related actions to improve the chances of a successful update.

9. Handling Rejection Causes:

  • Different rejection causes may require different actions by the UE. For instance, if the rejection is due to authentication failure, the UE may need to reattempt authentication before retrying the TAU procedure.

10. Network Load Management:

  • TAU Reject helps in network load management. Rejecting TAU requests under certain conditions prevents unnecessary signaling, optimizing network resources and reducing congestion.

11. Optimizing UE Behavior:

  • The TAU Reject message guides the behavior of the UE. It informs the UE about the reason for rejection, enabling the device to adjust its mobility-related procedures and behavior accordingly.

12. Security Considerations:

  • The TAU Reject message may include security-related information to maintain the integrity and confidentiality of the communication between the UE and the network.

13. User Indication:

  • TAU Reject serves as an indication to the user that the TAU Request has not been successful. The UE may display relevant information to the user, such as a notification indicating the inability to update its location.

In summary, LTE handles tracking area updates that fail to be accepted by sending a TAU Reject message to the UE. This rejection message includes information about the reason for rejection, allowing the UE to take appropriate actions, and it helps in optimizing network resources and ensuring efficient mobility management.