TAC

Time Alignment Command

Physical Layer →
Introduced in Rel-5 Also in: Core Network, Services, Management

TAC is a control signal sent by a base station to a User Equipment to adjust its uplink transmission timing, ensuring signals arrive synchronously to prevent interference in SC-FDMA/OFDMA systems.

Category
Physical Layer
Introduced
Rel-5
Where
Radio Access Network › NG-RAN (5G)
Also touches
3 segments
Specifications
21 specs
TAC Description Purpose Detected Changes Specifications

Description

The Time Alignment Command (TAC) is a fundamental mechanism in the LTE and 5G NR physical layer for maintaining uplink synchronization. In OFDMA (Orthogonal Frequency Division Multiple Access) and SC-FDMA (Single Carrier FDMA) systems used in the uplink, precise timing alignment of signals from all User Equipments (UEs) is essential to preserve orthogonality between subcarriers and prevent inter-symbol interference (ISI) and inter-carrier interference (ICI). The TAC is a parameter sent via the Medium Access Control (MAC) layer in a MAC Control Element (MAC CE) to instruct a specific UE to advance or delay its uplink transmission timing.

The process works as follows: The base station (eNB in LTE, gNB in NR) continuously measures the timing of received uplink signals from each UE, such as during the transmission of Sounding Reference Signals (SRS) or the Physical Uplink Shared Channel (PUSCH). It calculates the timing error, which is the difference between the ideal reception time and the actual arrival time of the UE's signal. This error is quantized and mapped to a TAC value. The TAC is then transmitted to the UE in a downlink control message. Upon receiving the TAC, the UE adjusts its uplink transmission timing by a corresponding amount, typically in steps of a fraction of the basic time unit (e.g., Ts in LTE, Tc in NR). The adjustment range is defined by the standard, and the UE maintains a Time Alignment Timer (TAT); as long as this timer is running, the UE considers itself uplink-synchronized.

Key components involved are the base station's uplink scheduler and timing measurement unit, the MAC layer for generating the MAC CE, and the UE's physical layer and timing advance control mechanism. The TAC is part of a closed-loop control system. Its role is absolutely critical for mobility, especially as UEs move and their propagation delay changes. Without continuous time alignment, the carefully constructed orthogonality of the uplink would break down, leading to increased interference, reduced data rates, and degraded overall system capacity. In 5G NR, the concept remains fundamentally the same but operates within the new NR frame structure and supports wider carrier bandwidths and more diverse numerologies.

Purpose & Motivation

The Time Alignment Command mechanism was introduced to solve the fundamental problem of uplink synchronization in cellular OFDMA/SC-FDMA systems. In earlier CDMA-based systems like UMTS, precise power control was the primary method for managing multiple access interference, but timing alignment was less critical. With the shift to OFDMA in LTE, orthogonality in the frequency domain became paramount. If uplink signals from different UEs do not arrive at the base station within the cyclic prefix (CP) duration, their orthogonality is lost, causing severe interference that cannot be filtered out.

Before a standardized, dynamic TAC mechanism, maintaining uplink synchronization for moving UEs would be nearly impossible, severely limiting cell sizes and mobility support. The TAC provides a fast, network-controlled method to compensate for varying propagation delays as UEs change their distance from the base station or due to multipath effects. It addresses the limitations of a simple initial random access procedure, which only provides coarse timing alignment. The continuous fine-tuning enabled by TACs is what allows LTE and NR to support high-speed mobility, large cell radii, and efficient uplink resource sharing among many users. Its creation was motivated by the need to achieve the high spectral efficiency targets of 4G and 5G, making the uplink as robust and efficient as the downlink.

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (9 CRs across 2 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Rel-15 7 changes

In Release 15, the TAC function was enhanced through corrections to its encoding and application across multiple interfaces, including for 5GS and NG-RAN cells. Key introductions included a Configured TAC for NR neighbour and served cell information elements, alongside corrections to support multiple TACs in shared network deployments. The release also addressed critical issues in the presence of TAC lists within the Service Area Item IE.

  • Correction of 5GS TAC LSB TS 24.501CR0042
  • Correction of TAC for NG-RAN cells before NSA ASN.1 freeze TS 36.423CR1094
  • Introduction of a Configured TAC into the NR Neighbour Information IE and the Served NR Cell Information IE TS 36.423CR1176
  • Correction of 5GS TAC TS 36.423CR1217
  • Critical correction to the presence of the TAC lists in the Service Area Item IE TS 38.423CR0153
  • Correction of 5GS TAC TS 38.473CR0090

+ 1 more changes

Rel-16 2 changes

In Release 16, the TAC function was updated in two specific areas. First, the requirement to use the TAC combined with the Software Version (SV) to identify a UE model within a manufacturer's assigned ID was removed. Second, clarifications were provided regarding the presence of the TAC within Serving Cell information communicated over the X2 interface.

  • removing requirement that TAC+SV is used to identify UE model in manufacturer assigned ID TS 23.401CR3549
  • Clarification on TAC presence in Serving Cell Info over X2 TS 36.423CR1539

Explore further

Broader topics and technologies where TAC plays a role.

Defining Specifications

3GPP specifications that define or reference TAC, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TR 21.905 vj00 3GPP Technical Terms and Definitions Rel-19
TS 23.401 vj50 Evolved Packet System (EPS) Stage 2 Description Rel-19
TS 24.229 vj50 IMS call control protocol based on SIP and SDP Rel-19
TS 24.301 vj60 NAS protocol for Evolved Packet System Rel-19
TS 24.484 vj30 MCS Configuration Management Rel-19
TS 24.501 vj50 5G NAS Protocols Specification Rel-19
TS 24.801 v810 CT1 SAE NAS Aspects for EPC Rel-8
TS 24.890 vg00 5G NAS Protocol for 5GS Stage 3 Rel-16
TS 28.875 vj00 Study on IAB Node Management Rel-19
TS 32.836 vc00 NM Centralized Coverage and Capacity Optimization Study Rel-12
TS 36.300 vj00 E-UTRAN Radio Interface Protocol Architecture Overview Rel-19
TS 36.413 vj10 S1 Application Protocol (S1AP) Rel-19
TS 36.423 vj10 X2 Application Protocol (X2AP) Specification Rel-19
TS 36.463 vj00 XwAP Protocol Specification Rel-19
TR 36.763 vh00 NB-IoT/eMTC Support for Non-Terrestrial Networks Rel-17
TS 37.473 vj00 W1 Application Protocol (W1AP) Specification Rel-19
TS 38.401 vj10 NG-RAN Architecture Specification Rel-19
TS 38.413 vj10 NG Application Protocol (NGAP) Rel-19
TS 38.423 vj10 Xn Application Protocol (XnAP) specification Rel-19
TS 38.473 vj10 5G F1 Application Protocol (F1AP) Rel-19
TS 48.061 vj00 BTS-TRAU Protocol for HR Speech/Data Rel-19
Patrick Zandl

About the author: Patrick Zandl (b. 1974)

Telecommunications specialist, technology journalist (founder of the Mobil server), and developer who has been running since 2025 — the largest Czech-language resource on AI-assisted programming. Formerly Chief Wizard Architect at Prusa3D and head of development for Turris at CZ.NIC; currently a consultant and instructor on AI implementation in companies.