Description
A Timing Advance Group (TAG) is a fundamental concept in 3GPP carrier aggregation (CA) and dual connectivity (DC) architectures, defined in specifications such as TS 36.302, TS 36.321, TS 36.855, and TS 38.321. A TAG consists of a group of Serving Cells that is configured by RRC (Radio Resource Control) and that, for the cells with an uplink (UL) configured, uses the same timing reference cell and the same Timing Advance value. This grouping mechanism allows the network to manage uplink timing alignment efficiently across multiple component carriers, which is essential for maintaining orthogonality between uplink transmissions from different user equipments (UEs) in the same cell.
The architecture of TAGs is closely tied to the concept of carrier aggregation, where a UE can transmit and receive on multiple component carriers simultaneously to increase throughput. In a CA scenario, different component carriers may experience different propagation delays, particularly when they are deployed on different frequency bands or in different geographic locations (e.g., in inter-band CA or coordinated multi-point scenarios). If all component carriers shared a single Timing Advance value, uplink transmissions on some carriers could arrive at the base station outside the cyclic prefix window, causing inter-symbol interference and degrading performance. TAGs solve this problem by allowing the network to assign different Timing Advance values to different groups of cells, each group sharing a common timing reference.
A TAG containing the Special Cell (SpCell) of a MAC entity is referred to as a Primary Timing Advance Group (PTAG), while the term Secondary Timing Advance Group (STAG) refers to other TAGs. The SpCell is either the Primary Cell (PCell) in a master cell group (MCG) or the Primary Secondary Cell (PSCell) in a secondary cell group (SCG). The PTAG is particularly important because it contains the cell that serves as the timing reference for the entire group, and its Timing Advance is typically maintained through the random access procedure on the SpCell. STAGs, on the other hand, contain only secondary cells (SCells) and may use a different timing reference cell and Timing Advance value.
The operation of TAGs involves several key procedures. The network configures TAGs via RRC signaling, assigning each Serving Cell to a specific TAG. The UE then applies the Timing Advance value received for each TAG to all cells within that group. Timing Advance values are maintained through Timing Advance Commands (TACs) sent in MAC Control Elements (MAC CEs), and the UE adjusts its uplink transmission timing accordingly. When a TAG's timing alignment timer expires without receiving a Timing Advance Command, the UE considers the TAG to be out of sync and takes appropriate actions, such as releasing uplink resources or initiating a random access procedure. This mechanism ensures that uplink timing is continuously maintained and that the network can detect and recover from timing misalignment.
The TAG concept was introduced in 3GPP Release 11 as part of the enhancements to carrier aggregation, specifically to support scenarios where multiple component carriers require different timing advances. Prior to Rel-11, all component carriers in a CA configuration shared a single Timing Advance value, which was sufficient for intra-band contiguous CA but inadequate for inter-band CA or scenarios with significantly different propagation delays. The introduction of TAGs enabled more flexible and robust CA deployments, including inter-band CA and later dual connectivity and multi-connectivity scenarios. The definition has evolved over subsequent releases, with the addition of PTAG and STAG terminology in Rel-15 to align with the dual connectivity architecture introduced in 5G NR.
Purpose & Motivation
The Timing Advance Group concept exists to solve the problem of uplink timing alignment across multiple component carriers in carrier aggregation and dual connectivity scenarios. In a cellular network, uplink transmissions from different UEs must arrive at the base station at approximately the same time to maintain orthogonality between subcarriers and avoid inter-symbol interference. This is achieved through the Timing Advance mechanism, where each UE adjusts its uplink transmission timing based on commands from the network. However, when a UE is configured with multiple component carriers, different carriers may experience different propagation delays, especially in inter-band CA or multi-point deployments. A single Timing Advance value for all carriers would be insufficient to maintain alignment on all carriers simultaneously.
Before the introduction of TAGs in Rel-11, carrier aggregation was limited to scenarios where all component carriers could share a single Timing Advance value, typically intra-band contiguous CA where propagation delays are similar across carriers. This limitation restricted the deployment flexibility of CA, preventing its use in inter-band scenarios or in configurations where component carriers were served by different transmission points. The TAG concept removed this limitation by allowing the network to group cells with similar timing characteristics and assign different Timing Advance values to different groups, enabling a much broader range of CA deployments.
The introduction of PTAG and STAG terminology in Rel-15 further refined the TAG concept to align with the dual connectivity architecture of 5G NR. In dual connectivity, a UE maintains connections to both a Master Node (MN) and a Secondary Node (SN), each with its own MAC entity and timing reference. The PTAG/STAG distinction provides a clear framework for managing timing alignment in this multi-connectivity environment, ensuring that each MAC entity can independently maintain its uplink timing while the overall system coordinates across nodes. This evolution reflects the ongoing need for flexible, robust timing management as cellular networks grow in complexity and diversity of deployment scenarios.
What changed in its specifications
The latest release-to-release comparison of specifications that define Timing Advance Group. Each summary describes the whole specification, not only this term.
Rel-13 added BL/enhanced-coverage exclusions, modulation limits, and new downlink reception types for MTC, plus SC-PTM downlink channel combinations and UE capability requirements.
Full comparison in TS 36.302 →Rel-19 adds to TS 36.321 a contention-based Msg3 early data transmission (CB-Msg3-EDT) procedure, along with new definitions and abbreviations. This is the only feature overview provided, so no other additions can be named.
Full comparison in TS 36.321 →Release Timeline
Evolution Across Releases
An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.
Initial definition introduced in 3GPP TS 36.302, TS 36.321, and TS 36.855: 'A group of Serving Cells that is configured by RRC and that, for the cells with an UL configured, using the same timing reference cell and the same Timing Advance value.' Introduced to support carrier aggregation scenarios requiring multiple timing advances.
Wording changed to add: 'A Timing Advance Group containing the SpCell of a MAC entity is referred to as Primary Timing Advance Group (PTAG), whereas the term Secondary Timing Advance Group (STAG) refers to other TAGs.' This addition aligned the TAG definition with the dual connectivity architecture of 5G NR, introducing explicit terminology for primary and secondary groups.
Wording changed to revert to the original Rel-11 definition: 'A group of Serving Cells that is configured by RRC and that, for the cells with an UL configured, using the same timing reference cell and the same Timing Advance value.' The PTAG/STAG terminology was removed from the definition text, though the concepts remain in use elsewhere in the specifications.
Defining Specifications
3GPP specifications that define or reference Timing Advance Group, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 36.302 vj00 | E-UTRA Physical Layer Services | Rel-19 read |
| TS 36.321 vj30 | E-UTRA MAC Protocol Specification | Rel-19 read |
| TS 36.855 vd00 | E-UTRA Positioning Enhancements Study | Rel-13 read |
| TS 38.321 vj40 | NR MAC Protocol Specification | Rel-19 read |