SPUCCH

Short Physical Uplink Control Channel

Physical Layer →
Introduced in Rel-15

SPUCCH is a short-duration physical uplink control channel in LTE and NR for low-latency transmission of uplink control information like HARQ feedback and scheduling requests.

Category
Physical Layer
Introduced
Rel-15
Where
Radio Access Network › NG-RAN (5G)
Specifications
6 specs
SPUCCH Description Purpose Related Classification Detected Changes Specifications

Description

The Short Physical Uplink Control Channel (SPUCCH) is a physical layer channel standardized in 3GPP, primarily for LTE and NR systems, to carry uplink control information (UCI) with reduced transmission time. Unlike the legacy PUCCH, which occupies a full subframe or slot, SPUCCH is designed with a short duration, often spanning only a few symbols within a subframe or slot. This design minimizes latency for control signaling, which is essential for applications demanding ultra-reliable low-latency communication (URLLC), such as industrial automation and autonomous vehicles. SPUCCH transmits critical feedback like Hybrid Automatic Repeat Request (HARQ) acknowledgments (ACK/NACK), channel state information (CSI), and scheduling requests (SR), ensuring efficient resource utilization and reliable data transmission.

Architecturally, SPUCCH is integrated into the uplink frame structure, occupying specific resource elements (REs) in the time-frequency grid. It operates within the physical layer (Layer 1) of the protocol stack, as defined in specifications like 36.201 and 36.212 for LTE and 38.889 for NR. The channel uses modulation schemes such as Binary Phase Shift Keying (BPSK) or Quadrature Phase Shift Keying (QPSK) to encode control bits, and it may employ sequence-based or block-based spreading techniques to enhance robustness against interference. Key components include the resource allocation mechanism, which assigns SPUCCH resources dynamically or semi-statically via Radio Resource Control (RRC) signaling, and the multiplexing scheme, which allows multiple users to share SPUCCH resources through orthogonal sequences or frequency division.

In operation, SPUCCH works by mapping encoded UCI bits to physical resources based on configurations from the base station (e.g., eNB in LTE or gNB in NR). The transmission process involves channel coding, modulation, and mapping to REs, followed by inverse Fast Fourier Transform (IFFT) for OFDM waveform generation. SPUCCH supports multiple formats tailored to different payload sizes and latency requirements, such as short-duration formats for ACK/NACK and longer formats for CSI reporting. Its role in the network is pivotal for maintaining link adaptation, enabling rapid retransmissions, and supporting dynamic scheduling, thereby improving overall system performance, spectral efficiency, and user experience in both LTE and 5G NR deployments.

Purpose & Motivation

SPUCCH was created to address the growing demand for low-latency control signaling in modern cellular networks, particularly with the advent of 5G and its emphasis on URLLC. Prior to SPUCCH, legacy PUCCH in LTE used longer transmission durations (e.g., full subframes), which introduced delays in feedback loops for HARQ and scheduling. This limitation hindered applications requiring millisecond-level latency, such as real-time control in industrial IoT and vehicle-to-everything (V2X) communication. SPUCCH solves this by reducing control channel duration, enabling faster acknowledgment and resource requests, thus enhancing network responsiveness and reliability.

Historically, as 3GPP evolved from Rel-14 to Rel-15, the need for more efficient uplink control channels became apparent with the introduction of NR and enhanced LTE features. SPUCCH was motivated by the requirement to support diverse use cases in 5G, including massive machine-type communication (mMTC) and enhanced mobile broadband (eMBB), where efficient control signaling is critical for scalability and performance. By minimizing control overhead and latency, SPUCCH facilitates advanced techniques like grant-free uplink transmission and dynamic TDD, addressing limitations of previous approaches that were optimized for less stringent latency targets.

Classification

Part ofPUCCH

Detected Changes Across Releases

from 3GPP Change Requests

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

Rel-15 40 changes

In Release 15, the SPUCCH function was introduced as part of the broader "shortened TTI and processing time" enhancements for LTE to reduce control plane latency. This involved integrating the shortened processing time and shortened TTI framework into the physical layer specifications TS 36.201 and TS 36.212. These changes enabled shorter transmission time intervals for uplink control channels, including SPUCCH, to expedite HARQ-ACK feedback and other control signaling.

  • Introduction of shortened processing time and shortened TTI into TS36.201 TS 36.201CR0023
  • Introduction of shortened processing time and shortened TTI into 36.212 TS 36.212CR0278
  • Introduction of shortened TTI and processing time for LTE TS 36.300CR1084
  • Introduction of shortened TTI and processing time for LTE TS 36.302CR1192
  • Introduction of shortened TTI and processing time for LTE TS 36.331CR3202
  • Control Plane latency reduction TS 36.331CR3453

+ 34 more changes

Rel-16 4 changes

In Release 16, the SPUCCH function was updated with clarifications on the Transmit Power Control (TPC) command procedure for PUCCH. Additionally, a new "Reception Type" was introduced specifically for uplink HARQ ACK feedback to support Rel-15 eMTC devices. These changes provided more precise operational rules and enhanced support for existing IoT device categories.

  • CR on clarification of TPC command for PUCCH TS 36.212CR0358
  • Adding Reception Type for uplink HARQ ACK feedback for Rel-15 eMTC TS 36.302CR1210
  • Correction of AUL HARQ process TS 36.331CR4343
  • Following RAN#82 decision, Rel-16 specification goes under change control TS 38.889
Rel-17 2 changes

In Release 17, the SPUCCH function was enhanced to support uplink RRC segmentation capability, allowing for more efficient transmission of control information. Additionally, corrections were made to the PUCCH transmission duration procedures to improve operation for IoT devices in Non-Terrestrial Networks (NTN). These updates provided more reliable uplink control signaling for specific use cases.

  • Introduction of uplink RRC Segmentation capability TS 36.331CR4826
  • IoT NTN RRC Correction on PUCCH TX duration TS 36.331CR4936

Explore further

Broader topics and technologies where SPUCCH plays a role.

Defining Specifications

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

SpecificationTitleRelease
TS 36.201 vj00 LTE Physical Layer General Description Rel-19
TS 36.212 vj10 LTE Multiplexing and Channel Coding Rel-19
TS 36.300 vj00 E-UTRAN Radio Interface Protocol Architecture Overview Rel-19
TS 36.302 vj00 E-UTRA Physical Layer Services Rel-19
TS 36.331 vj00 LTE RRC Protocol Specification Rel-19
TR 38.889 vg00 NR-based access to unlicensed spectrum study Rel-16