Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Physical Layer

UCI

Uplink Control Information

Physical Layer →

UCI is the uplink control signaling from a UE that carries essential information like Hybrid ARQ acknowledgments, Channel State Information, and Scheduling Requests for link adaptation, retransmissions, and resource scheduling.

Introduced
Rel-8
Where
Radio Access Network › NG-RAN (5G)
Specifications
14 specs
Also in
User Equipment
UCI Description Purpose What changed Neighbours Detected Changes Specifications

Description

Uplink Control Information (UCI) is a fundamental component of the physical layer control signaling in 3GPP LTE and NR. It comprises the set of control data that a User Equipment (UE) transmits to the base station (eNodeB/gNB) to support the operation of the uplink and downlink data channels. UCI is primarily carried on the Physical Uplink Control Channel (PUCCH) and, in certain cases, can be multiplexed with uplink data on the Physical Uplink Shared Channel (PUSCH). The content, encoding, and resource mapping of UCI are meticulously defined in the physical layer specifications (e.g., 3GPP TS 36.212/38.212 for channel coding and TS 36.213/38.213 for physical layer procedures).

Architecturally, UCI consists of several distinct information types, each serving a specific purpose in the radio link control loop. The key components are: Hybrid Automatic Repeat Request (HARQ) Acknowledgment (ACK/NACK), which informs the gNB whether a downlink transport block was received correctly; Channel State Information (CSI), which includes Channel Quality Indicator (CQI), Precoding Matrix Indicator (PMI), and Rank Indicator (RI) to report downlink channel conditions; and Scheduling Request (SR), which is a single-bit indicator used by the UE to request uplink resources for data transmission. The physical layer processes these bits through specific channel coding schemes (e.g., Reed-Muller codes, polar codes in NR) and modulates them for transmission.

How UCI works is tightly integrated with the scheduling timeline and frame structure. The gNB schedules downlink data and allocates specific resources for the UE to send the corresponding HARQ-ACK feedback after a fixed time offset. For periodic CSI reporting, the gNB configures the UE with a reporting configuration, dictating when and on which resources the UE should send CSI. The SR resources are semi-statically configured. The network must correctly receive and decode UCI to adapt its transmissions (via link adaptation based on CSI), initiate retransmissions (based on HARQ-ACK), and grant uplink resources (based on SR). Its role is therefore central to maintaining a robust, adaptive, and efficient radio link, directly impacting throughput and latency.

Purpose & Motivation

UCI was created to provide a reliable and efficient mechanism for the UE to send essential control feedback to the network. In the packet-switched, scheduled architecture of LTE and NR, the base station requires timely information from the UE to make optimal scheduling decisions. Previous systems had less dynamic control signaling. UCI addresses the need for low-latency, frequent feedback to enable advanced features like fast link adaptation, HARQ with soft combining, and dynamic scheduling.

The problems it solves are multifaceted. Without HARQ-ACK, the network would not know if a transmission failed, leading to higher-layer retransmissions with much greater latency. Without CSI, the network cannot adapt the modulation and coding scheme (MCS) to current radio conditions, resulting in either wasted capacity (if too conservative) or high error rates (if too aggressive). Without SR, the UE would have to rely on random access or pre-allocated periodic resources to request uplink grants, increasing latency and reducing efficiency for bursty traffic.

Its introduction and evolution were motivated by the increasing demands for higher data rates, lower latency, and more reliable connections. As technologies evolved from LTE to NR, UCI mechanisms were enhanced to support more antenna ports (for MIMO), wider bandwidths, ultra-reliable low-latency communication (URLLC) with very short feedback timelines, and operation in unlicensed spectrum. The design of UCI is a key factor in achieving the spectral efficiency and responsiveness that define 4G and 5G systems.

What changed in its specifications

The latest release-to-release comparison of specifications that define UCI. Each summary describes the whole specification, not only this term.

TS 36.212Rel-18 → Rel-19

Rel-19 adds NTN IoT Phase 3 support to TS 36.212 for LTE. It adds OCC enabled/disabled and OCC sequence index fields to the DCI Format N0 description.

Full comparison in TS 36.212 →
TS 36.213Rel-18 → Rel-19

Rel-19 adds CB-Msg3-EDT procedure support for NTN IoT in TS 36.213, covering new identifiers, MPDCCH/PDSCH/PUSCH handling, and timing and TDD subframe rules. It also adds OCC-related conditions to NPUSCH format 1 transmission, controlled by npusch-OCC-Enabled and the DCI OCC setting.

Full comparison in TS 36.213 →

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

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

Rel-15 6 changes
  • Correction to AUL-UCI resource allocation in 36.213 TS 36.213CR1155
  • Correction to UCI multiplexing TS 38.212CR0008
  • CR on UE procedure for reporting multiple UCI types TS 38.213CR0033
  • CR on UE procedure for reporting multiple UCI types TS 38.213CR0052
  • CR on beta_offset values for UCI reporting in PUSCH TS 38.213CR0062
  • UCI multiplexing for eVoLTE TS 36.213CR1041
Rel-16 7 changes
  • Correction on UCI bit sequence generation TS 38.212CR0047
  • Corrections on CG-UCI multiplexing in TS38.212 TS 38.212CR0078
  • Correction on UCI multiplexing with PUCCH overriding TS 38.213CR0183
  • Clarification on UCI and SL HARQ-ACK TS 38.213CR0262
  • Correction to PUSCH skipping with UCI without LCH-based prioritization TS 38.321CR1062
  • Corrections on UCI multiplexing for partial PUSCH mode 1 TS 36.212CR0360

+ 1 more changes

Rel-17 2 changes
  • CR on priority of CG-UCI TS 38.212CR0128
  • CR on CSI on LP PUSCH with CG-UCI TS 38.213CR0407
Rel-18 3 changes
  • Correction of RRC parameter names for UTO-UCI indication TS 38.212CR0179
  • Correction of RRC parameter names and applicable configuration for UTO-UCI indication TS 38.213CR0592
  • Clarification on not multiplexing UCI on MSG3 PUSCH TS 38.213CR0631
Rel-19 1 change
  • CR for UCI multiplexing with OCC PUSCH in NR NTN TS 38.213CR0778

Defining Specifications

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

SpecificationTitleRelease
TS 36.212 vj30 E-UTRA Physical Layer Procedures Rel-19 read
TS 36.213 vj50 LTE Physical Layer Procedures Rel-19 read
TS 36.306 vj30 E-UTRA UE Radio Access Capability Parameters Rel-19 read
TS 38.104 vk10 NR Base Station RF Requirements Rel-20 read
TS 38.141 vj40 BS Conformance Testing (TR 38.141) Rel-19 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.300 vj40 NR and NG-RAN Overall Description Rel-19 read
TS 38.321 vj40 NR MAC Protocol Specification Rel-19 read
TR 38.802 ve20 Study on New Radio Access Technology Physical Layer Aspects Rel-14 read
TS 38.824 vg00 NR URLLC Physical Layer Enhancements Study Rel-16 read
TR 38.830 vh00 NR Coverage Enhancements Study Rel-17 read
TR 38.912 vj00 Study on New Radio Access Technology Rel-19 read