Uplink Control Information

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.

Key Features

• Carries HARQ acknowledgments (ACK/NACK) for downlink data
• Transports Channel State Information (CQI, PMI, RI) for link adaptation
• Includes Scheduling Request (SR) for uplink resource grants
• Primarily transmitted on the Physical Uplink Control Channel (PUCCH)
• Can be multiplexed with data on the Physical Uplink Shared Channel (PUSCH)
• Uses specific channel coding (e.g., polar coding in NR for reliability)

Evolution Across Releases

Defining Specifications