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.
What changed in its specifications
The latest release-to-release comparison of specifications that define TCI. Each summary describes the whole specification, not only this term.
Rel-18 brings only minor changes to TS 21.905: 0 clauses changed, with no change attributed to a release feature.
Full comparison in TR 21.905 →Rel-19 adds low band carrier aggregation via switching and low-power wake-up receiver (LP-WUR) requirements to TS 38.133. It also adds ATG network support, intra-band non-collocated NR-CA receiver types, and multi-carrier BWP switch and SCell activation delay requirements.
Full comparison in TS 38.133 →Technology family
MIMO and beam management · Radio Access Network › NG-RAN (5G)
- R99 Transmit diversity, TSTD
- Rel-7 MIMO
- Rel-8 CSI, DM-RS, MU-MIMO, PMI, RI, SDMA, SRS, SU-MIMO, TPMI
- Rel-10 CSI-RS, NZP CSI-RS
- Rel-11 CoMP, CSI-IM, QCL, UL CLTD, UL MIMO
- Rel-13 CRI, FD-MIMO
- Rel-15 Beam Level Mobility, Beam management, BFD, BFD-RS, BFR, PT-RS, TCI, ZP CSI-RS
- Rel-18 CJT
Also in this family (introduction release not pinned to a single defining specification): Beamforming
Members and relations were proposed independently by several models and kept only where at least two agree; quotes are verified verbatim against the specifications. Release = first approved version of the defining specification.
Release Timeline
Detected Changes Across Releases
verified against 3GPP sourcesDocumented changes in 5 releases, each verified against the text of 3GPP specifications or approved change requests and shown with the exact wording. The release timeline above shows the same releases. A release without an entry has no documented change for this term.
TCI states and their signalling are specified for the first time in Rel-15: DCI TCI field, MAC CE activation and indication of TCI states for PDSCH and PDCCH, and QCL/RLM handling based on active TCI state.
- “The network may activate and deactivate the configured TCI states for PDSCH of a Serving Cell by sending the TCI States Activation/Deactivation for UE-specific PDSCH MAC CE” TS 38.321 v15.14.0
- “used to map up to 8 TCI states to the codepoints of the DCI field 'Transmission Configuration Indication'” TS 38.214 v15.16.0
- “The network may indicate a TCI state for PDCCH reception for a CORESET of a Serving Cell by sending the TCI State Indication for UE-specific PDCCH MAC CE” TS 38.321 v15.14.0
In Rel-16 TCI gains multi-TRP indication of two TCI states per DCI codepoint, an Enhanced TCI States Activation/Deactivation MAC CE, and simultaneous multi-cell TCI state update.
- “When two TCI states are indicated in a DCI and the UE is set to 'fdmSchemeA', the UE shall receive a single PDSCH transmission occasion” TS 38.214 v16.17.0
- “6.1.3.24 Enhanced TCI States Activation/Deactivation for UE-specific PDSCH MAC CE” TS 38.321 v16.22.0
- “the UE applies the antenna port quasi co-location provided by TCI-States with same activated tci-StateID value to CORESETs with a same index” TS 38.213 v16.17.0
Rel-17 extends TCI with a unified TCI framework (joint DL/UL TCI states, activation MAC CE, two-TCI-state SFN schemes) and adds TCI state switching and UL timing requirements.
- “The network may activate and deactivate the configured unified TCI states of a Serving Cell or a set of Serving Cells” TS 38.321 v17.15.0
- “used to map up to 8 TCI states and/or pairs of TCI states, with one TCI state for DL channels/signals” TS 38.214 v17.16.0
- “DL TCI state switching for unified TCI or UL TCI state switching for unified TCI, a reference signal is considered to be QCLed” TS 38.133 v17.23.0
In Rel-18 TCI states gain new behaviour: LTM candidate cell TCI states, unified TCI with two indicated states for PDSCH, and TCI-associated timing alignment handling in MAC.
- “the one or more DL RS configured by a TCI state provided by CandidateTCI-State, where the TCI state is indicated by an LTM Cell Switch Command MAC CE” TS 38.213 v18.9.0
- “if the UE configured with dl-OrJointTCI-StateList is having two indicated TCI States to be applied to PDSCH” TS 38.214 v18.11.0
- TCI States for LTM TS 38.401CR0479
In Rel-19, TCI state handling was extended for conditional LTM (CLTM) cell switch: TCI state determination, activation delays, QCL assumptions and UL spatial filter rules were added and corrected.
- “After RACH-based conditional LTM cell switch is triggered, all activated TCI states are deactivated.” TS 38.213 v19.5.0
- “if the time between receiving the CLTM candidate cell TCI state activation MAC-CE and UE starting to execute cell switch towards the target cell is at least TCI state activation delay” TS 38.133 v19.6.0
- Correction on TCI state determination for CLTM TS 38.213CR0754
Defining Specifications
3GPP specifications that define or reference TCI, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TR 21.905 vj20 | 3GPP Terminology and Definitions | Rel-19 read |
| TS 38.106 vk00 | NR Repeaters: RF Requirements (TS 38.106) | Rel-20 read |
| TS 38.133 vk10 | NR Radio Resource Management Requirements | Rel-20 read |
| TS 38.174 vk00 | NR Integrated Access and Backhaul Requirements | Rel-20 read |
| TS 38.176 vj40 | IAB Conformance Testing | Rel-19 read |
| TS 38.212 vj40 | NR Multiplexing and Channel Coding | Rel-19 read |
| TS 38.213 vj50 | NR Physical Layer Control Procedures | Rel-19 read |
| TS 38.214 vj50 | NR Physical Layer Data Channel Procedures | Rel-19 read |
| TS 38.321 vj40 | NR MAC Protocol Specification | Rel-19 read |
| TS 38.551 vj10 | NR MIMO OTA Performance Requirements | Rel-19 read |
| TS 38.771 vj00 | FR2-1 OTA Testing for STxMP UEs | Rel-19 read |
| TR 38.833 vh00 | NR Demodulation Performance Enhancement | Rel-17 read |
| TR 38.878 vi40 | Technical Report on Advanced Receiver for MU-MIMO | Rel-18 read |