Description
The CSI-RS Resource Indicator (CRI) is a critical feedback mechanism within the 5G New Radio (NR) and evolved LTE physical layer framework for channel state information (CSI) reporting. It operates within the context of beam management and multi-antenna (MIMO) operations. The network configures the User Equipment (UE) with a resource set containing multiple Channel State Information Reference Signal (CSI-RS) resources. Each resource corresponds to a specific transmission configuration, such as a particular beamformed signal from a gNB's antenna array or a specific port configuration. The UE measures the signal quality (e.g., based on Reference Signal Received Power (RSRP) or Signal to Interference plus Noise Ratio (SINR)) of each CSI-RS resource in this set.
Upon being triggered to report CSI, the UE selects the CSI-RS resource that yields the best measured quality according to the reporting configuration. The index of this selected resource within the configured set is encoded and reported back to the gNB as the CRI. This index is a compact representation, typically requiring only a few bits, which specifies which pre-configured beam or port configuration is currently optimal for the UE. The CRI is reported alongside other CSI parameters, such as the Rank Indicator (RI), Precoding Matrix Indicator (PMI), and Channel Quality Indicator (CQI), as part of a unified CSI report structure defined in specifications like 38.214.
The CRI's role is foundational for beam management procedures like beam selection and beam refinement. In initial access and mobility, the CRI helps identify the best Synchronization Signal Block (SSB) or CSI-RS beam for establishing a connection. In connected mode, it enables dynamic beam switching and tracking, allowing the network to adapt the transmission beam to the UE's changing position or radio conditions. For multi-TRP (Transmission Reception Point) or multi-beam operations, the CRI can indicate a preferred TRP or a combination of beams, facilitating advanced coordination schemes.
Architecturally, the CRI is generated by the UE's physical layer based on Layer 1 (L1) measurements. The reporting is configured via higher-layer RRC signaling, which defines the CSI-RS resource set, the reporting periodicity, and the event triggers. The CRI report is then transmitted via the Uplink Control Information (UCI) on the PUCCH or PUSCH. The gNB's scheduler uses the CRI feedback to select the appropriate downlink beamforming weights, thereby directing energy towards the UE and improving link reliability and data throughput. This closed-loop feedback is essential for harnessing the gains of massive MIMO and high-frequency bands (e.g., mmWave) where beamforming is mandatory for coverage.
Purpose & Motivation
The CRI was introduced to address the fundamental challenge of beam management in 5G NR, particularly as networks began utilizing higher frequency bands with massive MIMO antenna arrays. In sub-6 GHz LTE, wide-area coverage was achievable with relatively broad beams. However, in mmWave spectrum (e.g., FR2), signal propagation suffers from high path loss and blockage, necessitating the use of narrow, high-gain beams to maintain a viable link. The network must identify and track the best directional beam for each UE, a process that requires efficient feedback from the device. The CRI provides this mechanism by allowing the UE to indicate its preferred beam from a set of candidates configured by the network.
Prior to 5G, LTE's CSI feedback primarily focused on reporting wideband CQI and PMI for MIMO precoding across a relatively homogeneous cell coverage area. It lacked a standardized, efficient method for explicit beam indication. Early beamforming implementations often relied on cell-specific reference signals or required proprietary solutions. The CRI, standardized starting in 3GPP Release 13 for LTE enhancements and fully leveraged in NR from Release 15, created a unified, flexible framework for beam reporting. It solves the problem of overhead; instead of reporting full channel matrices for many beams, the UE simply sends a short indicator, conserving uplink resources.
Its creation was motivated by the need for dynamic and agile beam management to support high mobility, robust connectivity, and spatial multiplexing in dense deployments. The CRI enables key 5G use cases like enhanced Mobile Broadband (eMBB) in mmWave and ultra-reliable low-latency communications (URLLC) by ensuring the network can quickly switch to the strongest beam, minimizing interruption. It forms the basis for more advanced features like multi-beam CSI reporting, beam failure recovery, and multi-TRP operation, making it a cornerstone of 5G's physical layer design.
What changed in its specifications
The latest release-to-release comparison of specifications that define CRI. Each summary describes the whole specification, not only this term.
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 →Rel-19 adds sub-band full duplex (SBFD) support to TS 38.212. It introduces UEIRI handling, new SBFD abbreviations and definitions, and SBFD-specific resource counting in PUSCH uplink control information procedures.
Full comparison in TS 38.212 →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
- CRI used together with CSI-RS
“For a UE configured in transmission mode 9 or 10, when reporting CRI the UE reports a single instance of one or more selected CSI-RS resource(s).” TS 36.213
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 7 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.
CRI (CSI-RS Resource Indicator) is specified for the first time: UE reports a selected CSI-RS resource for CLASS B eMIMO-Type, with CRI coding and multiplexing on PUSCH and CSI conditioned on the reported CRI.
- “CRI CSI-RS Resource Indicator” TS 36.213 v13.16.0
- “For a UE configured in transmission mode 9 or 10, when reporting CRI the UE reports a single instance of a selected CSI-RS resource.” TS 36.213 v13.16.0
- “If CRI is reported, the reported PMI, CQI, and RI values are calculated conditioned on the reported CRI.” TS 36.213 v13.16.0
CRI reporting was extended to multi-shot CSI-RS (csi-RS-NZP-mode) using activated resources, with new CRI bit-width tables and joint CRI/RI coding for activated-resource cases.
- “when a UE is configured with higher layer parameter eMIMO-Type set to 'CLASS B' and high layer parameter csi-RS-NZP-mode set to 'multiShot'” TS 36.213 v14.17.0
- “Table 5.2.2.6.1-2C shows the fields and the corresponding bit width for the CRI feedback for wideband CQI reports” TS 36.212 v14.16.0
- Corrections on CRI reporting for multi-shot CSI-RS in 36.213 TS 36.213CR0902
NR CRI is specified for the first time: TS 38.212 defines CRI bitwidth tables and CSI field mapping, and TS 38.214 defines CRI determination and reporting conditions.
- “the UE shall determine a CRI from the supported set of CRI values as defined in clause 6.3.1.1.2 of [5, TS 38.212] and report the number in each CRI report” TS 38.214 v15.16.0
- “The bitwidth for CRI, SSBRI, RSRP, and differential RSRP are provided in Table 6.3.1.1.2-6.” TS 38.212 v15.13.0
- “the UE shall derive the CSI parameters other than CRI conditioned on the reported CRI” TS 38.214 v15.16.0
CRI reporting was extended to L1-SINR: new CRI/SINR reporting with its own bitwidth table and CSI field mapping order, plus cri-SINR as a reportQuantity and further CRI restrictions for Type II r16 codebooks.
- “Table 6.3.1.1.2-8A: Mapping order of CSI fields of one report for CRI/SINR or SSBRI/SINR reporting” TS 38.212 v16.15.0
- “The bitwidth for CRI, SSBRI, SINR, and differential SINR are provided in Table 6.3.1.1.2-6A.” TS 38.212 v16.15.0
- “CRI reporting is not supported when the higher layer parameter codebookType is set to either 'typeII', 'typeII-PortSelection', 'typeII-r16'” TS 38.214 v16.17.0
CRI reporting was extended for multi-TRP CSI: new CRI definitions for resource pairs with csi-ReportMode Mode1/Mode2, new CRI bitwidth tables, and up to two CRIs reported per report.
- “If the higher layer parameter csi-ReportMode is set to 'Mode1' and the higher layer parameter numberOfSingleTRP-CSI-Mode1 is set to X” TS 38.214 v17.16.0
- “each of the NN Resource Pairs is associated to a CRI value.” TS 38.214 v17.16.0
- “Table 6.3.1.1.2-3A: RI, LI, CQI, and CRI associated with one CSI-RS resource pair and csi-ReportMode= Mode 1 or Mode 2” TS 38.212 v17.13.0
In Rel-18, CRI gains new behaviour: CRI bitwidth follows the CSI-RS resources in CSI-ReportSubConfig, and a sub-configuration's CRI k maps to the (k+1)-th resource in its list.
- “for the determination of the bitwidth of a CRI field, the value of KsCSI−RSK_{s}^{CSI - RS} is the number of CSI-RS resources configured” TS 38.212 v18.8.0
- “the UE shall derive the CSI parameters other than CRI conditioned on the reported CRI, where the CRI k (k ≥ 0) for the sub-configuration corresponds” TS 38.214 v18.11.0
- “First CRI as in Table 6.3.1.1.2-3B, if associated with one CSI-RS resource, numberOfSingleTRP-CSI-Mode1 = 2 and if reported” TS 38.212 v18.8.0
CRI reporting was extended in Rel-19: new Type I single/multi-panel r19 codebooks get CRI bitwidth tables, predicted CRI (P-CRI) is added, and CRI/SSBRI reporting for nrofReportedRS-r19 is modified.
- “The bitwidth for predicted CRI, predicted SSBRI, predicted RSRP, differential predicted RSRP are provided in Table 6.3.1.1.2-6C.” TS 38.212 v19.4.0
- “The bitwidth for RI/LI/CQI/CRI of codebookType=typeI-SinglePanel-r19 is provided in Table 6.3.1.1.2-3C.” TS 38.212 v19.4.0
- “different CRI or SSBRI for each report setting, or single CRI or SSBRI for each report setting when nrofReportedRS-r19 is equal to the size” TS 38.214 v19.5.0
Defining Specifications
3GPP specifications that define or reference CRI, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 36.321 vj30 | E-UTRA MAC Protocol Specification | Rel-19 read |
| TS 38.212 vj40 | NR Multiplexing and Channel Coding | Rel-19 read |
| TS 38.214 vj50 | NR Physical Layer Data Channel Procedures | Rel-19 read |
| TR 38.889 vg00 | NR-based access to unlicensed spectrum study | Rel-16 read |