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

Glossary term · Physical Layer

PUCCH

Physical Uplink Control Channel

Physical Layer →

PUCCH is the physical uplink channel in LTE and 5G NR that carries essential control information from the user equipment to the network, including HARQ acknowledgments, channel state reports, and scheduling requests.

Introduced
Rel-8
Where
Radio Access Network › NG-RAN (5G)
Specifications
39 specs
PUCCH Description Purpose What changed Neighbours Detected Changes Specifications

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.

What changed in its specifications

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

TR 21.905Rel-17 → Rel-18

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 →
TS 36.104Rel-17 → Rel-18

Rel-18 adds NR bands n54, n105, n106 and n109 to the BS emission and spurious and blocking requirements in TS 36.104. These entries cover wide-area, local and medium-range base stations.

Full comparison in TS 36.104 →

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

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

Rel-15 20 changes
  • Correction on the 1ms HARQ-ACK transmission for the collision between sPUSCH and PUCCH/PUSCH TS 36.213CR1232
  • CR for PUCCH Format 1 TS 38.211CR0005
  • CR on PUCCH format 1 TS 38.211CR0010
  • Correction to last PUCCH resource set configuration TS 38.213CR0019
  • CR on the determination of the minimum number of PRBs for PUCCH transmission TS 38.213CR0036
  • CR to 38.213 on PUCCH configuration for NR-DC TS 38.213CR0060

+ 14 more changes

Rel-16 20 changes
  • Correction on PUCCH transmit power control for LTE-M TS 36.213CR1396
  • Correction for PUCCH repetition transmission TS 38.213CR0120
  • 38.213 CR Correction on HARQ-ACK codebook for secondary PUCCH group TS 38.213CR0167
  • CR on handling overlapping PUCCH/PUSCH transmissions with repetitions and with different priorities TS 38.213CR0178
  • Correction on UCI multiplexing with PUCCH overriding TS 38.213CR0183
  • CR on Timing for secondary cell activation / deactivation with sub-slot PUCCH TS 38.213CR0197

+ 14 more changes

Rel-17 24 changes
  • IoT NTN RRC Correction on PUCCH TX duration TS 36.331CR4936
  • CR on the clarification of PUCCH resource determination in 38.213 TS 38.213CR0339
  • Correction for HARQ-ACK codebook generation for PUCCH cell switching and UL BWP switching TS 38.213CR0347
  • Correction of CSI assumptions over multiplexing NCJT CSI reports in PUCCH TS 38.213CR0354
  • CR on spatial domain filter for sensing for PUCCH transmission in FR2-2 TS 38.213CR0371
  • CR on power control for PUCCH TS 38.213CR0385

+ 18 more changes

Rel-18 9 changes
  • Update of FR2 EVM MU for PUCCH TS 38.903CR0962
  • Correction on PUCCH power determination for Type-2 HARQ-ACK codebook TS 38.213CR0524
  • CR on PUCCH resources for multicast HARQ-ACK TS 38.213CR0528
  • Correction on PUCCH power control parameter determination TS 38.213CR0539
  • CR on default pathloss reference signal for SRS and PUCCH TS 38.213CR0548
  • CR on Simultaneous PUCCH and PUSCH transmission with same priority in UL CA TS 38.213CR0557

+ 3 more changes

Rel-19 2 changes
  • CR on UEIRI information bit in PUCCH in TS 38.213 TS 38.213CR0784
  • CR on overlapping of PUCCH with UEIRI and other channels/signals in TS 38.213 TS 38.213CR0785
Rel-20 1 change
  • CR on correction of test cases for SRS antenna port switching and PUCCH SCell activation/deactivation TS 38.133CR6788

Defining Specifications

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

SpecificationTitleRelease
TR 21.905 vj20 3GPP Terminology and Definitions Rel-19 read
TS 36.104 vj20 E-UTRA/NB-IoT Base Station RF Requirements Rel-19 read
TS 36.116 vj00 E-UTRA Relay RF Requirements Rel-19 read
TS 36.117 vj00 E-UTRA Relay RF Test Methods & Requirements Rel-19 read
TS 36.133 vj60 LTE Radio Resource Management Requirements Rel-19 read
TS 36.141 vj10 RF Test Methods for LTE and NB-IoT Base Stations Rel-19 read
TS 36.201 vj00 LTE Physical Layer General Description Rel-19 read
TS 36.211 vj30 E-UTRA Physical Layer Specifications Rel-19 read
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.216 vj00 LTE Relay Node Physical Layer Rel-19 read
TS 36.300 vj20 E-UTRAN Radio Interface Protocol Architecture Rel-19 read
TS 36.302 vj00 E-UTRA Physical Layer Services Rel-19 read
TS 36.306 vj30 E-UTRA UE Radio Access Capability Parameters Rel-19 read
TS 36.331 vj40 E-UTRA Radio Resource Control (RRC) Protocol Rel-19 read
TS 36.825 vd00 Study on Additional LTE TDD Configurations Rel-13 read
TS 36.863 vc00 CRS Interference Mitigation for Homogeneous Networks Rel-12 read
TS 36.878 vd00 LTE Performance Enhancements for High Speed Scenarios Rel-13 read
TR 37.911 vj00 3GPP 5G NTN Self-Evaluation Report Rel-19 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.201 vj00 NR Physical Layer General Description Rel-19 read
TS 38.202 vj00 5G NR Physical Layer Services Rel-19 read
TS 38.211 vj50 NR Physical Channels and Signals 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.300 vj40 NR and NG-RAN Overall Description Rel-19 read
TS 38.521 vj10 UE Conformance Spec for NR Satellite Access Rel-19 read
TS 38.523 vj40 UE Conformance Specification for 5G NR Rel-19 read
TR 38.808 vh00 Study on NR above 52.6 GHz to 71 GHz Rel-17 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.838 vh00 Study on XR Evaluations for NR Rel-17 read
TR 38.869 vi00 Study on low-power wake up signal and receiver for NR Rel-18 read
TR 38.889 vg00 NR-based access to unlicensed spectrum study Rel-16 read
TR 38.903 vj40 NR UE Test Tolerances and Uncertainties Rel-19 read
TS 45.820 vd10 CIoT for Internet of Things Rel-13 read