Description
The Physical Uplink Shared Channel (PUSCH) is a fundamental physical channel defined in 3GPP specifications for uplink transmission from the User Equipment (UE) to the network's base station (NodeB in UMTS, eNodeB in LTE, gNB in NR). It serves as the primary conduit for uplink user plane data, such as application data from a smartphone, and can also carry uplink control information (UCI) when configured to do so. The channel is termed 'shared' because its time-frequency resources are dynamically allocated by the network scheduler to different UEs, allowing for statistical multiplexing and efficient use of the available radio spectrum. This dynamic scheduling is a cornerstone of modern cellular systems, enabling them to adapt to varying traffic loads and channel conditions.
From a technical perspective, the PUSCH's operation is governed by a grant-based access mechanism. The UE must receive an uplink grant from the network, typically via a Downlink Control Information (DCI) message on the Physical Downlink Control Channel (PDCCH), before it can transmit. This grant specifies critical transmission parameters such as the allocated resource blocks (time and frequency), modulation and coding scheme (MCS), power control commands, and precoding information for MIMO. Upon receiving a valid grant, the UE processes its transport block (data) through a chain of physical layer procedures including channel coding (e.g., Turbo coding in LTE, LDPC in NR), scrambling, modulation (e.g., QPSK, 16QAM, 64QAM, 256QAM), layer mapping for MIMO, precoding, and finally mapping to the assigned resource elements on the OFDM (in LTE) or DFT-s-OFDM/CP-OFDM (in NR) waveform.
The architecture of the PUSCH is tightly integrated with other physical channels and signals. For instance, the Demodulation Reference Signal (DM-RS) is transmitted alongside the PUSCH within the same allocated resources to enable the base station to estimate the radio channel for coherent demodulation. The Sounding Reference Signal (SRS), transmitted separately, assists the network scheduler in understanding the uplink channel quality to make informed scheduling decisions. Furthermore, the PUSCH supports hybrid automatic repeat request (HARQ) with multiple parallel processes, allowing for rapid retransmissions in case of decoding failures, which is crucial for achieving high reliability and low latency. In 5G NR, the PUSCH design introduced greater flexibility, supporting multiple numerologies (subcarrier spacings), mini-slot-based transmissions for ultra-reliable low-latency communications (URLLC), and enhanced support for grant-free (configured grant) transmissions to reduce latency for periodic traffic.
Purpose & Motivation
The PUSCH was created to provide an efficient, flexible, and high-capacity mechanism for uplink data transmission in 3GPP systems, moving beyond the circuit-switched and dedicated channel paradigms of earlier 2G systems. Prior to shared channels, uplink resources were often statically assigned, leading to inefficient spectrum utilization when a user's data traffic was bursty or intermittent. The introduction of the shared channel concept, starting with the High-Speed Uplink Packet Access (HSUPA) enhancement in UMTS and fully realized in LTE, addressed this by allowing the network to dynamically allocate resources on a very short timescale (e.g., every 1 ms subframe in LTE) to only those users who actively have data to send.
This dynamic allocation solves the core problem of radio resource scarcity. By sharing the channel among many users based on instantaneous need, the PUSCH maximizes the overall system throughput and capacity. It also enables advanced radio features like link adaptation, where the modulation and coding scheme is adjusted based on the reported channel quality, and multi-user MIMO, where spatial layers are used to serve multiple users simultaneously on the same time-frequency resources. The evolution into 5G NR further refined its purpose to support a vastly wider range of services, from enhanced mobile broadband (eMBB) with very high data rates to massive Machine-Type Communications (mMTC) and Ultra-Reliable Low-Latency Communications (URLLC), necessitating features like grant-free access and support for diverse numerologies.
Key Features
- Dynamic scheduling via uplink grants transmitted in DCI
- Support for multiple modulation schemes (QPSK to 256QAM) and adaptive coding
- Integration with DM-RS for channel estimation and coherent demodulation
- Hybrid ARQ (HARQ) with multiple parallel processes for reliability
- Support for Single-User and Multi-User MIMO transmissions
- In 5G NR, support for both CP-OFDM and DFT-s-OFDM waveforms and configurable grant (grant-free) operation
Evolution Across Releases
Introduced as part of the UMTS/HSDPA specifications. The initial PUSCH in UMTS was based on Wideband Code Division Multiple Access (W-CDMA) and was a key component of the Dedicated Transport Channel (DCH) and later the Enhanced Dedicated Channel (E-DCH) for HSUPA. It provided a code-multiplexed shared resource for uplink packet data.
Fundamentally re-architected for LTE, moving from W-CDMA to OFDMA/SC-FDMA for the uplink. The LTE PUSCH used Single-Carrier FDMA (SC-FDMA) to improve power amplifier efficiency in UEs. It introduced dynamic scheduling on a 1 ms TTI basis, advanced channel coding (Turbo codes), and explicit support for carrying control information (CQI/PMI/RI).
Redesigned for 5G New Radio (NR). Key enhancements include support for multiple numerologies (flexible subcarrier spacing), both CP-OFDM and DFT-s-OFDM waveforms, mini-slot transmission for low latency, enhanced DM-RS patterns, and the introduction of configured grant (Type 1 and Type 2) for grant-free uplink transmission to reduce latency for periodic traffic.
Enhanced PUSCH for industrial IoT and URLLC. Introduced enhancements for reliable multi-TRP transmission, improved resource allocation flexibility, and support for integrated access and backhaul (IAB). Further refined configured grant operation and reliability mechanisms.
Extended PUSCH capabilities for new use cases. Introduced support for reduced capability (RedCap) devices, requiring modifications for lower complexity. Enhanced multi-TRP and multi-panel UE operation, and improved support for non-terrestrial networks (NTN) with longer timing adjustments.
Defining Specifications
| Specification | Title |
|---|---|
| TS 21.905 | 3GPP TS 21.905 |
| TS 25.202 | 3GPP TS 25.202 |
| TS 25.221 | 3GPP TS 25.221 |
| TS 25.224 | 3GPP TS 25.224 |
| TS 25.225 | 3GPP TS 25.225 |
| TS 25.331 | 3GPP TS 25.331 |
| TS 25.402 | 3GPP TS 25.402 |
| TS 25.430 | 3GPP TS 25.430 |
| TS 25.433 | 3GPP TS 25.433 |
| TS 25.435 | 3GPP TS 25.435 |
| TS 25.931 | 3GPP TS 25.931 |
| TS 36.104 | 3GPP TR 36.104 |
| TS 36.116 | 3GPP TR 36.116 |
| TS 36.117 | 3GPP TR 36.117 |
| TS 36.133 | 3GPP TR 36.133 |
| TS 36.201 | 3GPP TR 36.201 |
| TS 36.211 | 3GPP TR 36.211 |
| TS 36.212 | 3GPP TR 36.212 |
| TS 36.213 | 3GPP TR 36.213 |
| TS 36.216 | 3GPP TR 36.216 |
| TS 36.300 | 3GPP TR 36.300 |
| TS 36.302 | 3GPP TR 36.302 |
| TS 36.306 | 3GPP TR 36.306 |
| TS 36.790 | 3GPP TR 36.790 |
| TS 36.878 | 3GPP TR 36.878 |
| TS 36.884 | 3GPP TR 36.884 |
| TS 37.106 | 3GPP TR 37.106 |
| TS 37.911 | 3GPP TR 37.911 |
| TS 38.133 | 3GPP TR 38.133 |
| TS 38.174 | 3GPP TR 38.174 |
| TS 38.176 | 3GPP TR 38.176 |
| TS 38.201 | 3GPP TR 38.201 |
| TS 38.202 | 3GPP TR 38.202 |
| TS 38.211 | 3GPP TR 38.211 |
| TS 38.212 | 3GPP TR 38.212 |
| TS 38.213 | 3GPP TR 38.213 |
| TS 38.300 | 3GPP TR 38.300 |
| TS 38.521 | 3GPP TR 38.521 |
| TS 38.523 | 3GPP TR 38.523 |
| TS 38.808 | 3GPP TR 38.808 |
| TS 38.824 | 3GPP TR 38.824 |
| TS 38.830 | 3GPP TR 38.830 |
| TS 38.838 | 3GPP TR 38.838 |
| TS 38.869 | 3GPP TR 38.869 |
| TS 38.889 | 3GPP TR 38.889 |
| TS 38.903 | 3GPP TR 38.903 |
| TS 45.820 | 3GPP TR 45.820 |