Telecom engineering reference for protocols, messages, call flows, troubleshooting, releases, and tools.
Menu
NASLTEMME to UE3GPP TS 24.301
LTE Tracking Area Update Reject
Tracking Area Update Reject is the EPS NAS message the network sends when the tracking area updating procedure is not accepted.
Message Fact Sheet
Protocol
nas
Network
lte
Spec
3GPP TS 24.301
Spec Section
5.5.3, 8.2.28
Direction
MME to UE
Message Type
EMM signaling
Full message name
LTE Tracking Area Update Reject
Protocol
NAS
Technology
LTE
Direction
MME to UE
Interface
N1 over LTE access / S1-MME control path
Signaling bearer / channel
NAS signaling / Commonly carried in downlink NAS transport when the network decides not to accept the tracking area updating procedure
Typical trigger
Sent when the network cannot accept the requested tracking area update because of mobility restrictions, subscription limits, roaming conditions, congestion, or related registration-state control reasons.
Main purpose
Rejects the TAU procedure, returns the main EMM cause for the failed mobility-refresh path, and may provide timer or forbidden-area information that changes how the UE should retry, wait, or stop.
Main specification
3GPP TS 24.301, 5.5.3, 8.2.28
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 Reject in simple terms?
Tracking Area Update Reject is the EPS NAS message the network sends when the tracking area updating procedure is not accepted.
Rejects the TAU procedure, returns the main EMM cause for the failed mobility-refresh path, and may provide timer or forbidden-area information that changes how the UE should retry, wait, or stop.
Why this message matters
Tracking Area Update Reject is the network telling the UE that the requested tracking area update was not accepted and that the UE must follow the returned reject handling.
Where this message appears in the call flow
Normal tracking area change rejection
In a normal tracking area change, Tracking Area Update Reject ends the TAU path and returns the reject branch the UE must follow next.
Call flow position: Reject message sent after the UE attempted to refresh mobility context for a new tracking area but the network did not accept that TAU path.
Typical state: UE does not receive refreshed registered-area context for the new tracking area.
Preconditions:
The UE sent Tracking Area Update Request because of a TA change.
The network decided not to accept the current TAU attempt.
Next likely message: Retry later, attach fallback, or restricted registered behavior depending on the returned cause
Periodic tracking area update rejection
When periodic updating is due but the network rejects the TAU path, Tracking Area Update Reject defines the retry or restricted behavior that follows.
Call flow position: Reject message sent when periodic presence refresh is not accepted and the network ends the current TAU cycle.
Typical state: UE does not keep the expected periodic mobility-refresh path and must follow the returned reject handling.
Preconditions:
Periodic updating was due.
The MME rejected the TAU procedure.
Next likely message: Timer-driven wait, restricted behavior, or broader registration recovery
Tracking area update after recovery trigger
When the UE tries to preserve existing EPS context after a recovery-related trigger, Tracking Area Update Reject explains why that TAU preservation path still failed.
Call flow position: Reject message sent when the UE tried to preserve existing EPS context through TAU after a recovery-related trigger but the network did not accept that branch.
Typical state: UE cannot continue on the preserved TAU path and may need broader recovery or fresh registration handling.
Preconditions:
Usable or apparently usable EPS context still existed at the UE.
The network rejected the recovery-triggered TAU branch.
Next likely message: Retry timing, attach fallback, or no normal service continuation
Next message(s): Retry after timer expiry, Attach or wider NAS recovery handling, No normal TAU continuation
Message direction and transport
Sender and receiver: MME to UE
Interface: N1 over LTE access / S1-MME control path
Domain: Core-side EPS mobility management signaling that ends the current TAU attempt and determines the next UE mobility behavior
Signaling bearer: NAS signaling
Logical channel: Commonly carried in downlink NAS transport when the network decides not to accept the tracking area updating procedure
Transport / encapsulation: EPS NAS message sent by the MME and delivered to the UE through the eNodeB when tracking area updating is rejected
Security context: Normally sent under NAS security because TAU usually operates on already existing EPS context, although the returned cause still determines whether that context can be kept.
Message Structure Overview
Tracking Area Update Reject is an EPS mobility-management message rather than an ASN.1 LTE RRC structure.
The practical reading path starts with EMM cause, then moves into T3346, T3402, or other returned restrictions that change the UE's next mobility behavior.
In real traces, this is the message that tells you why the TAU branch stopped and what the UE is expected to do next.
ASN.1 Message Syntax for LTE Tracking Area Update Reject
Tracking Area Update Reject
EMM cause
T3346 value OPTIONAL
T3402 value OPTIONAL
extended EMM cause OPTIONAL
lower bound timer value OPTIONAL
Forbidden TAI(s) for the list of roaming OPTIONAL
Forbidden TAI(s) for regional provision of service OPTIONAL
T3448 value OPTIONAL
How to read this message syntax
Tracking Area Update Reject is a NAS layer-3 message, not an ASN.1 LTE RRC message. Read this NAS syntax from the EMM cause first, then inspect any returned timers or forbidden-area information because those fields explain the UE's next TAU behavior.
LTE Tracking Area Update Reject - Example Dump
Tracking Area Update Reject
Protocol discriminator: EPS mobility management
Security header type: Integrity protected and ciphered
Message type: Tracking Area Update Reject
EMM cause: tracking area not allowed
T3346 value: 2 minutes
Forbidden TAI(s) for the list of roaming: MCC 001 MNC 01 TAC 0x1001
How to read this dump
Start with EMM cause because that field selects the main reject branch.
T3346 and T3402 are the next fields to inspect because they directly change retry timing and backoff behavior.
Forbidden-TAI information can explain why later mobility behavior changes even when the radio side looks normal.
May be returned when control-plane user-data congestion or related service restrictions are relevant.
Detailed field explanation
EMM cause
Gives the main reason why the network rejected the tracking area updating procedure.
Presence: Required
In practice: In practice, compare this field with the original request and with any later release-dependent optional fields so you can see whether the network accepted the same service model the UE asked for.
T3346 value
May provide NAS-level congestion backoff information.
Presence: Optional
In practice: In practice, compare this field with the original request and with any later release-dependent optional fields so you can see whether the network accepted the same service model the UE asked for.
T3402 value
May indicate when later EPS mobility retry is allowed.
Presence: Optional
In practice: In practice, compare this field with the original request and with any later release-dependent optional fields so you can see whether the network accepted the same service model the UE asked for.
Extended EMM cause
May provide more detail associated with the main reject reason.
Presence: Optional
In practice: In practice, compare this field with the original request and with any later release-dependent optional fields so you can see whether the network accepted the same service model the UE asked for.
Lower bound timer value
May guide minimum storage time for the affected PLMN condition when the related cause is used.
Presence: Optional
In practice: In practice, compare this field with the original request and with any later release-dependent optional fields so you can see whether the network accepted the same service model the UE asked for.
Forbidden TAI(s) for roaming
May provide forbidden tracking-area information for roaming handling.
Presence: Optional
In practice: In practice, compare this field with the original request and with any later release-dependent optional fields so you can see whether the network accepted the same service model the UE asked for.
Forbidden TAI(s) for regional provision of service
May provide forbidden tracking-area information for regional service restrictions.
Presence: Optional
In practice: In practice, compare this field with the original request and with any later release-dependent optional fields so you can see whether the network accepted the same service model the UE asked for.
T3448 value
May be returned when control-plane user-data congestion or related service restrictions are relevant.
Presence: Optional
In practice: In practice, compare this field with the original request and with any later release-dependent optional fields so you can see whether the network accepted the same service model the UE asked for.
What to check in logs and traces
Confirm which Tracking Area Update Request the reject belongs to.
Inspect the EMM cause first.
Check whether T3346, T3402, or T3448 was returned.
Inspect any forbidden-TAI information when roaming or regional behavior looks unusual.
Correlate the reject with the UE's next retry, wait state, or fallback to attach.
Common Issues and Troubleshooting
The UE detects a TA change but never settles into normal registered behavior in the new area.
Likely cause: Tracking Area Update Reject is ending the TAU path and the returned cause or forbidden-area information defines why.
What to inspect: Check EMM cause first, then inspect returned timers and any forbidden-TAI information.
Next step: Treat the returned reject branch as the main explanation before debugging radio mobility.
Periodic TAU does not refresh cleanly and the UE behaves inconsistently after timer expiry.
Likely cause: The periodic update branch may be rejected with timer-driven or restriction-driven handling.
What to inspect: Check Tracking Area Update Reject together with the periodic trigger and any returned timer values.
Next step: Read the periodic TAU attempt as a full request-reject sequence rather than only as a timer event.
The UE tries to preserve registration after a recovery event but still falls back to broader recovery.
Likely cause: The network rejected the recovery-triggered TAU branch, so the stored EPS context was not usable enough to preserve the path.
What to inspect: Compare the trigger, EMM cause, returned timers, and any later attach or service behavior.
Next step: Decide first whether the UE is staying in a TAU-based mobility-refresh model or crossing into registration rebuild.
LTE / 5G / Variant Comparison
Compared with Tracking Area Update Accept
Tracking Area Update Accept preserves and refreshes existing EPS registration context. Tracking Area Update Reject ends that TAU path and returns the failure branch.
Compared with Tracking Area Update Request
Tracking Area Update Request starts the TAU procedure. Tracking Area Update Reject is the network response when that mobility-refresh path is not accepted.
Compared with Attach Reject
Tracking Area Update Reject applies when the UE tried to preserve existing registration through TAU. Attach Reject applies when EPS registration creation or rebuild itself is rejected.
FAQ
What is Tracking Area Update Reject in LTE?
It is the EPS NAS message the network sends when the tracking area updating procedure is rejected.
What should I inspect first in Tracking Area Update Reject?
Start with the EMM cause, then inspect any returned T3346, T3402, T3448, or forbidden-TAI information.
Why is Tracking Area Update Reject important in troubleshooting?
Because it explains not only that the TAU path failed, but also which reject branch and retry behavior the UE is expected to follow.
What usually comes after Tracking Area Update Reject?
That depends on the returned cause and timers: the UE may wait, retry later, or move into attach or broader recovery handling.
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.
