TCI

Transmission Configuration Indicator

Physical Layer →
Introduced in Rel-5

TCI is an indicator used in 5G NR to signal a specific set of downlink transmission parameters to a UE by pointing to a pre-configured state containing QCL assumptions for demodulation.

Category
Physical Layer
Introduced
Rel-5
Where
Radio Access Network › NG-RAN (5G)
Specifications
13 specs
TCI Description Purpose Related Classification Detected Changes Specifications

Description

The Transmission Configuration Indicator (TCI) is a fundamental concept in the 5G New Radio (NR) physical layer, specifically within the framework of beam management and quasi-co-location (QCL). It is an index or identifier signaled by the gNodeB (gNB) to the User Equipment (UE) via Downlink Control Information (DCI) or higher-layer Radio Resource Control (RRC) signaling. This indicator points the UE to a specific Transmission Configuration State (TCS) that has been previously configured by RRC. Each TCS contains crucial information, primarily the Quasi-Co-Location (QCL) assumptions between antenna ports of different reference signals. In essence, the TCI tells the UE which reference signal (e.g., a specific CSI-RS or SS/PBCH block) can be used to derive channel estimation parameters (like delay spread, Doppler spread, Doppler shift, average delay, and spatial Rx parameters) for demodulating a subsequent physical downlink shared channel (PDSCH) or physical downlink control channel (PDCCH) transmission.

Architecturally, TCI states are configured per bandwidth part (BWP) and are managed by the gNB's Medium Access Control (MAC) and RRC layers. The process involves several steps. First, the network configures a list of TCI states for a UE via RRC signaling (as per 38.331). Each TCI state includes parameters linking a target reference signal (like a PDSCH's DM-RS) to a source reference signal (like a CSI-RS) and specifies the type of QCL relationship (Type A, B, C, or D). Type D is particularly important for beam management as it indicates spatial Rx parameter similarity, meaning the UE can assume the same receive beam can be used for both the source and target signals. When the gNB schedules a PDSCH transmission, it includes a TCI field in the DCI (format 1_1 or 1_2) to dynamically indicate which of the pre-configured TCI states applies to that specific PDSCH transmission. For PDCCH, a TCI state can be indicated via MAC Control Element (MAC CE) for beam indication of the control channel.

How it works operationally: The UE, upon receiving a DCI with a TCI indicator, looks up the corresponding TCI state from its configured list. It then applies the QCL assumptions from that state. For example, if TCI state #3 indicates that the DM-RS ports of the PDSCH are QCL Type D with CSI-RS resource #5, the UE knows it can use the same receive beamforming settings (spatial filter) that it successfully used to receive CSI-RS #5 when it tries to demodulate the upcoming PDSCH. This is vital in a beamformed mmWave or massive MIMO system where the optimal beam direction is narrow and must be aligned precisely. The TCI framework thus decouples detailed beam measurement and reporting procedures (involving CSI-RS/SSB) from the dynamic scheduling of data, allowing for fast and efficient beam switching without excessive signaling overhead. It is a cornerstone for reliable high-frequency communication and advanced multi-beam operation in 5G NR.

Purpose & Motivation

The TCI was created to solve the critical challenge of managing beam correspondence and channel state information in advanced antenna systems, particularly for 5G NR which operates in high-frequency bands (including mmWave) and employs massive MIMO. In these environments, communication relies on narrow, directional beams to overcome high path loss. A core problem was how to efficiently inform the UE which beam (or more precisely, which spatial reception filter) it should use to receive a scheduled downlink transmission, especially when beams can change rapidly due to mobility or scheduling needs. Previous LTE systems had simpler, less dynamic beam management, lacking a unified framework for indicating spatial relationships across different channel types.

The limitations of prior approaches included high signaling overhead if beam information had to be explicitly signaled for every transmission, and a lack of flexibility in linking different reference signals. The TCI concept addresses this by introducing a layer of indirection and pre-configuration. It allows the network to configure a set of possible transmission configurations (TCI states) in advance via semi-static RRC signaling. Then, during dynamic scheduling, it only needs to send a short indicator (a few bits in DCI) to activate one of these states. This dramatically reduces control channel overhead and latency, which is essential for the low-latency use cases of 5G. It solves the problem of efficiently managing spatial QCL relationships in a dynamic beamforming environment.

Furthermore, TCI enables advanced features like multi-TRP (Transmission Reception Point) operation and multi-beam scheduling. By configuring TCI states associated with different TRPs or different beams, the network can rapidly switch the UE's reception point or beam for diversity or capacity gains. The creation of TCI was motivated by the need for a scalable, flexible, and efficient beam management framework that could support the wide range of 5G deployment scenarios, from sub-6 GHz to mmWave, and from single-beam to complex multi-beam operations. It is a key enabler for the performance and reliability promises of 5G NR.

Classification

Part ofDCI
Related approachesQCLCSI-RSPDSCH

Detected Changes Across Releases

from 3GPP Change Requests

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

Studied in Rel-5, normative work from Rel-15.

Rel-15 44 changes

In Release 15, the TCI (Transmission Configuration Indicator) function was not newly introduced; the provided Change Request titles and grounding context exclusively detail corrections and clarifications to existing procedures such as PUCCH configuration, HARQ-ACK transmission, DCI formats, and timing adjustments.

  • Clarification on UL_SUL indicator field and SRS request field TS 38.212CR0013
  • CR on correction to bitwidth of NNZC indicator TS 38.212CR0014
  • Correction on UL/SUL indicator in DCI format 0_0 TS 38.212CR0016
  • CR on UL/SUL indicator in DCI format 0_1 TS 38.212CR0021
  • CR on timing adjustment indicator TS 38.213CR0010
  • Correction to last PUCCH resource set configuration TS 38.213CR0019

+ 38 more changes

Rel-16 70 changes

In Release 16, the TCI (Transmission Configuration Indicator) framework was enhanced with the introduction of uplink transmission switching and support for aperiodic CSI-RS triggering to report beam switch timing. The release also introduced corrections for the transmission configuration indication in DCI format 1_2 and refined procedures for handling overlapping PUCCH/PUSCH transmissions with different priorities.

  • Introduction of UL transmission switching TS 38.213CR0114
  • Aperiodic CSI-RS Triggering for UE reporting beamSwitchTiming values of 224 and 336 TS 38.214CR0060
  • Introduction of downgraded configurations for SRS antenna switching TS 38.214CR0062
  • Introduction of one-slot periodic TRS configuration for FR1 under a certain condition TS 38.214CR0063
  • Correction on Transmission configuration indication in DCI format 1_2 TS 38.212CR0057
  • Correction on SRS resource set configuration in TS 38.212 TS 38.212CR0070

+ 64 more changes

Rel-17 65 changes

In Release 17, the enhancements to the Transmission Configuration Indicator (TCI) function primarily involved corrections and clarifications to support the unified TCI state framework. Specifically, these included a correction on Power Headroom Report (PHR) procedures when using unified TCI states and corrections for Beam Failure Recovery operations related to this framework. Additionally, a clarification was provided on Hybrid Automatic Repeat Request (HARQ) feedback procedures for TCI state update indications.

  • Introduction of small data transmission in RRC_INACTIVE state for NR TS 38.213CR0278
  • Introduction of NR small data transmissions in INACTIVE state TS 38.214CR0237
  • Introduction of Small Data Transmission for MAC spec TS 38.321CR1198
  • Correction on the short message indicator when TRS availability indication is present TS 38.212CR0132
  • Corrections on small data transmission in RRC_INACTIVE state for NR TS 38.213CR0303
  • Corrections on small data transmission in RRC_INACTIVE state for NR TS 38.213CR0330

+ 59 more changes

Rel-18 86 changes

In Release 18, the TCI function was enhanced with the introduction of a Cross-RRH TCI state switch indication specifically designed for high-speed train scenarios. Furthermore, corrections and clarifications were made regarding the application of TCI states for CORESETs, including both CORESET 0 and other CORESETs, within the LTM (Layer 1/2 Triggered Mobility) framework. These updates also included corrections to the Pathloss Reference Signal (RS) associated with LTM TCI states.

  • Introduction of multi-cell PDSCH / PUSCH scheduling TS 38.214CR0442
  • Introduction of Cross-RRH TCI state switch indication for high speed train TS 38.321CR1706
  • Corrections on PRACH association indicator in PDCCH order in 38.212 TS 38.212CR0192
  • Corrections for Transmission with more than 4 Layers for 8TX UE TS 38.212CR0193
  • CR on the PRACH retransmission indicator field included in the PDCCH order TS 38.212CR0213
  • Correction of RRC parameter names and applicable configuration for UTO-UCI indication TS 38.213CR0592

+ 80 more changes

Rel-19 13 changes

In Release 19, the TCI function saw specific corrections and clarifications, particularly regarding its application for semi-persistent CSI-RS in LTM (Layer 1 Measurement) and the determination of TCI states for CLTM (Connected Mode Layer 1 Measurement). The release also provided a clarification on the scope of deactivation for LTM candidate TCI states.

  • TEI19 Counting of CSI-RS resource referred by N CSI reporting settings [SimCSI_count] TS 38.214CR0681
  • TEI19 Simultaneous NZP-CSI-RS resource counting with NES [SimCSI_countNES] TS 38.214CR0689
  • Correction on TCI state determination for CLTM TS 38.213CR0754
  • Correction on RO validation for on-demand SIB1 configuration TS 38.213CR0756
  • Correction on WUS TCI state TS 38.214CR0731
  • Correction on Semi-persistent CSI/Semi-persistent CSI-RS for LTM TS 38.214CR0733

+ 7 more changes

Explore further

Broader topics and technologies where TCI plays a role.

Defining Specifications

3GPP specifications that define or reference TCI, 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 38.106 vj20 NR Repeater Radio Transmission and Reception Rel-19
TS 38.133 vj20 5G UE Radio Requirements for RRC_IDLE Mobility Rel-19
TS 38.174 vj10 NR Integrated Access and Backhaul Radio Spec Rel-19
TS 38.176 vj20 IAB Conformance Testing Specification Rel-19
TS 38.212 vj10 NR Multiplexing and Channel Coding Rel-19
TS 38.213 vj10 NR Physical Layer Control Procedures Rel-19
TS 38.214 vj10 NR Physical Layer Procedures for Data Rel-19
TS 38.321 vj00 NR MAC Protocol Specification Rel-19
TS 38.551 vi30 User Equipment (UE) Multiple Input Multiple Output (MIMO) Over-the-Air (OTA) performance Rel-18
TS 38.771 vj00 FR2-1 OTA Testing for STxMP UEs Rel-19
TR 38.833 vh00 NR Demodulation Performance Enhancement Rel-17
TR 38.878 vi40 Technical Report on Advanced Receiver for MU-MIMO Rel-18