Physical Uplink Control Channel

Description

The Physical Uplink Control Channel (PUCCH) is a fundamental physical layer channel in both LTE (from Release 8) and NR (5G) radio access networks. It is dedicated to transmitting uplink control information (UCI) from the User Equipment (UE) to the gNB (in NR) or eNB (in LTE). Unlike the PUSCH (Physical Uplink Shared Channel), which carries user data, the PUCCH is specifically designed for signaling that is vital for maintaining the radio link, supporting feedback mechanisms, and enabling efficient dynamic scheduling.

The PUCCH occupies specific resource blocks at the edges of the system bandwidth in LTE, while in NR its location is more flexible and configurable within the bandwidth part. It uses specific formats (PUCCH formats 0-4 in NR, formats 1-5 in LTE) optimized for different payload sizes and reliability requirements. These formats employ different modulation schemes, ranging from simple On-Off Keying for 1-bit ACK/NACK to π/2-BPSK or QPSK for larger CSI reports. The channel coding varies by format, with some using block-based codes and others using Reed-Muller or Polar codes (in NR) for error protection.

The primary types of UCI carried on the PUCCH are: Hybrid Automatic Repeat Request Acknowledgement (HARQ ACK/NACK) for downlink transport blocks, which is crucial for retransmission protocols; Channel State Information (CSI), including Channel Quality Indicator (CQI), Precoding Matrix Indicator (PMI), and Rank Indicator (RI), which guides downlink scheduling and MIMO configuration; and Scheduling Requests (SR), which the UE uses to indicate it has data to send and requires uplink resources. The PUCCH is a scheduled channel, but its resources are semi-statically configured via RRC signaling, with dynamic indication for certain formats. Its design involves a trade-off between control overhead, coverage, capacity, and latency, leading to multiple formats tailored for different deployment scenarios and UE capabilities.

Purpose & Motivation

The PUCCH was created to provide a reliable and efficient mechanism for transmitting essential control signaling from the UE to the network in OFDMA-based systems like LTE and NR. Its introduction with LTE Release 8 was motivated by the need for a channel separate from user data to carry time-critical feedback. This solves several key problems: it enables fast HARQ ACK/NACK feedback for downlink packets, which is fundamental to achieving high throughput with low latency; it provides the network with timely CSI to perform channel-dependent scheduling and adaptive modulation and coding, maximizing spectral efficiency; and it gives the UE a means to request uplink resources without needing dedicated scheduled resources beforehand, improving uplink latency for sporadic traffic.

Before dedicated control channels like PUCCH, systems used more integrated or less efficient methods for control signaling. The PUCCH's dedicated design allows for optimized transmission characteristics (power, coding) independent of user data traffic. This separation ensures that critical link maintenance information is transmitted reliably even when the UE has no uplink data to send on the shared channel. It is a cornerstone of the dynamic, feedback-driven operation that defines modern cellular systems, enabling advanced features like carrier aggregation, massive MIMO, and ultra-reliable low-latency communication (URLLC) by providing the necessary low-latency control plane link.

Key Features

• Carries Uplink Control Information (UCI): HARQ ACK/NACK, CSI, Scheduling Requests
• Multiple formats optimized for different payload sizes (1-2 bits to >10 bits) and reliability needs
• Uses specific, configured resource blocks at bandwidth edges (LTE) or flexibly within a bandwidth part (NR)
• Employs modulation schemes like OOK, π/2-BPSK, and QPSK suited for control signaling
• Supports simultaneous transmission of HARQ-ACK and CSI on the same resource
• Enables crucial network functions like link adaptation, MIMO configuration, and dynamic scheduling

Evolution Across Releases

Defining Specifications