Telecom engineering reference for protocols, messages, call flows, troubleshooting, releases, and tools.
Menu
NASLTEUE to MME3GPP TS 24.301
LTE Tracking Area Update Complete
Tracking Area Update Complete is the EPS NAS message the UE sends after Tracking Area Update Accept when the accepted TAU branch requires explicit UE completion.
Message Fact Sheet
Protocol
nas
Network
lte
Spec
3GPP TS 24.301
Spec Section
5.5.3, 8.2.27
Direction
UE to MME
Message Type
EMM signaling
Full message name
LTE Tracking Area Update Complete
Protocol
NAS
Technology
LTE
Direction
UE to MME
Interface
N1 over LTE access / S1-MME control path
Signaling bearer / channel
NAS signaling / Commonly carried in uplink NAS transport after Tracking Area Update Accept when explicit completion is required.
Typical trigger
Sent after Tracking Area Update Accept when the UE must explicitly confirm processing of the accepted TAU context.
Main purpose
Confirms that the UE processed the returned TAU context, especially updated identity context such as a reallocated GUTI, and lets the network stop waiting for TAU completion.
Main specification
3GPP TS 24.301, 5.5.3, 8.2.27
Release added
Release 8
Procedures where used
Tracking Area Updating Procedure, Normal TA Change, Periodic Updating, Recovery-triggered Mobility Refresh
What is LTE Tracking Area Update Complete in simple terms?
Tracking Area Update Complete is the EPS NAS message the UE sends after Tracking Area Update Accept when the accepted TAU branch requires explicit UE completion.
Confirms that the UE processed the returned TAU context, especially updated identity context such as a reallocated GUTI, and lets the network stop waiting for TAU completion.
Why this message matters
Tracking Area Update Complete is the UE telling the network that it processed the accepted TAU result.
Where this message appears in the call flow
Normal tracking area change completion
After a normal tracking area change is accepted, Tracking Area Update Complete closes the TAU branch when explicit UE completion is required.
Call flow position: UE completion message sent after the network accepted a TA change and returned refreshed tracking-area context.
Typical state: The UE remains EPS-registered and is closing the accepted TAU branch rather than starting a new registration path.
Preconditions:
The MME sent Tracking Area Update Accept.
The accepted TAU branch required explicit completion from the UE.
Next likely message: Protected registered-state continuation
Periodic tracking area update completion
In a periodic TAU branch, Tracking Area Update Complete confirms that the UE processed the accepted periodic-update context.
Call flow position: UE completion message sent after a periodic TAU was accepted and the returned periodic-update context was processed.
Typical state: The UE remains registered and confirms the accepted periodic-update branch.
Preconditions:
Periodic updating was due.
The MME accepted the TAU procedure with an explicit completion branch.
Next likely message: Normal registered idle behavior
Tracking area update after recovery trigger
When the UE preserves usable EPS context after a recovery-related trigger, Tracking Area Update Complete closes the accepted TAU branch instead of falling back to attach.
Call flow position: UE completion message sent after a recovery-related TAU was accepted and the preserved EPS context was refreshed.
Typical state: The UE confirms the accepted TAU branch instead of falling back to attach rebuild.
Preconditions:
Usable EPS context still existed.
The network accepted the TAU path and expected explicit completion.
Next likely message: Protected service continuation or idle continuation with preserved registration
Interface: N1 over LTE access / S1-MME control path
Domain: Core-side EPS mobility management signaling that closes the accepted TAU branch and keeps the UE in refreshed EPS registration.
Signaling bearer: NAS signaling
Logical channel: Commonly carried in uplink NAS transport after Tracking Area Update Accept when explicit completion is required.
Transport / encapsulation: EPS NAS message sent by the UE and delivered to the MME through the eNodeB during the final completion phase of the tracking area updating procedure.
Security context: Normally sent under existing NAS security because TAU completion operates on already valid EPS registration context.
Message Structure Overview
Tracking Area Update Complete is an EPS mobility-management message rather than an ASN.1 LTE RRC structure.
It is structurally small because the message mainly signals that the UE finished processing the accepted TAU outcome.
The practical reading path starts with whether the accepted TAU branch actually required completion and whether the message arrived in time.
ASN.1 Message Syntax for LTE Tracking Area Update Complete
Tracking Area Update Complete
How to read this message syntax
Tracking Area Update Complete is a NAS layer-3 message, not an ASN.1 LTE RRC message. Its value comes from its position in the TAU procedure rather than from a large IE payload.
LTE Tracking Area Update Complete - Example Dump
Tracking Area Update Complete
Protocol discriminator: EPS mobility management
Security header type: Integrity protected and ciphered
Message type: Tracking Area Update Complete
How to read this dump
Start by confirming that the earlier Tracking Area Update Accept actually created a completion branch that should end here.
This message is operationally small, but it is one of the strongest checkpoints showing that the UE accepted the returned TAU context.
If Tracking Area Update Accept is retransmitted, this message is one of the first places to check.
What to check in logs and traces
Confirm the message follows the correct Tracking Area Update Accept.
Check whether the accepted TAU branch required explicit completion.
Correlate the message with T3450 stopping on the network side.
Check whether the UE continues with stable registered behavior afterward.
If missing, compare the accept retransmission timing and any later fallback behavior.
Common Issues and Troubleshooting
Tracking Area Update Accept is seen, but the TAU branch does not close cleanly.
Likely cause: Tracking Area Update Complete may be missing, delayed, or not delivered back to the network.
What to inspect: Check whether the UE sent Tracking Area Update Complete and whether the uplink NAS path delivered it.
Next step: Read Tracking Area Update Accept and Tracking Area Update Complete as one completion pair.
The network retransmits Tracking Area Update Accept.
Likely cause: The network may still be waiting for Tracking Area Update Complete and T3450 may still be running.
What to inspect: Check whether the UE transmitted Tracking Area Update Complete and whether the message reached the MME.
Next step: Correlate the retransmission timing with T3450-related behavior before assuming TAU was rejected.
Some TAU cases end with explicit completion and others do not.
Likely cause: The accepted branch may differ depending on whether the network returned identity updates or other context that requires TAU completion.
What to inspect: Compare the returned Tracking Area Update Accept content and whether explicit completion was expected in the working and failing traces.
Next step: Decide first whether the TAU branch really required Tracking Area Update Complete.
LTE / 5G / Variant Comparison
Compared with Tracking Area Update Accept
Tracking Area Update Accept returns the network-granted TAU context. Tracking Area Update Complete is the UE confirmation that closes that accepted branch.
Compared with Attach Complete
Attach Complete closes a successful attach branch. Tracking Area Update Complete closes an accepted TAU branch that required explicit completion.
Compared with Tracking Area Update Request
Tracking Area Update Request starts the TAU procedure. Tracking Area Update Complete is the UE closeout message near the end of a successful TAU branch.
FAQ
What is Tracking Area Update Complete in LTE?
It is the EPS NAS message the UE sends after Tracking Area Update Accept when the accepted TAU branch requires explicit completion.
What should I inspect first in Tracking Area Update Complete?
Start by checking whether the accepted TAU branch really required completion, then correlate the message with the earlier accept and T3450 behavior.
Why is Tracking Area Update Complete important in troubleshooting?
Because it shows that the UE actually closed the accepted TAU branch instead of leaving the network waiting for completion.
What usually comes after Tracking Area Update Complete?
The UE continues in protected registered-state behavior, subject to the refreshed TAU context the network already accepted.
Decode this message with the 3GPP Decoder, inspect the related message database, or open the matching call flow to see where this signaling step fits in the full procedure.
