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

Glossary term · Physical Layer

PUSCH

Physical Uplink Shared Channel

Physical Layer →

PUSCH is the primary dynamically scheduled uplink channel in 3GPP networks, used by User Equipment to transmit both user data and control information to the base station as a shared resource.

Introduced
Rel-4
Where
Radio Access Network › NG-RAN (5G)
Specifications
47 specs
PUSCH Description Purpose What changed Neighbours Detected Changes Specifications

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.

What changed in its specifications

The latest release-to-release comparison of specifications that define PUSCH. 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 25.221Rel-9 → Rel-10

MU-MIMO for 1.28Mcps TDD (four midamble-to-spreading-code association patterns, new MU-MIMO term). Multi-carrier HSUPA (per-carrier E-DCH channels, E-AGCH association, up to four E-HICHs).

Full comparison in TS 25.221 →

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

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

Rel-15 21 changes
  • Performance requirements for subslot-PUSCH TS 36.104CR4800
  • Introduction of PUSCH demodulation requirements for sTTI TS 36.104CR4803
  • Correction on the partial PUSCH mode field for FeLAA in 36.212 TS 36.212CR0300
  • Edge PRB restriction for flexible starting PUSCH PRB for LTE-MTC TS 36.213CR1223
  • Correction on the 1ms HARQ-ACK transmission for the collision between sPUSCH and PUCCH/PUSCH TS 36.213CR1232
  • Correction on PUSCH scheduling with CSS for Case 1 HARQ timing TS 36.213CR1282

+ 15 more changes

Rel-16 19 changes
  • CR to 36.104 on LTE HST PUSCH conditions TS 36.104CR4873
  • CR to TS 36.104: Introduction of PUSCH performance requirements for enhanced HST scenario TS 36.104CR4883
  • CR to TS 36.104 Updates of PUSCH performance requirements for enhanced HST scenario TS 36.104CR4891
  • CR to TS 36.104 Finalization on PUSCH performance requirements for enhanced HST scenario TS 36.104CR4895
  • PUR correction on PUSCH Repetition Adjustment and Zero Padding Procedures TS 36.212CR0361
  • PUR correction on PUSCH Repetition Adjustment TS 36.213CR1379

+ 13 more changes

Rel-17 15 changes
  • CR on the description of the SRS resource set indication for PUSCH repetition TS 38.212CR0117
  • Correction on TDRA for multiple PUSCH scheduling in TS 38.212 TS 38.212CR0127
  • CR on default PUSCH power control parameters for mTRP PUSCH TS 38.213CR0344
  • CR for power control of mTRP PUSCH repetition TS 38.213CR0345
  • CR on HP DG PUSCH and LP CG PUSCH collision resolution TS 38.213CR0355
  • Correction on parallel transmission of PRACH and SRS/PUCCH/PUSCH TS 38.213CR0386

+ 9 more changes

Rel-18 16 changes
  • Introduction of RS for pathloss determination of Type 1 CG PUSCH [PL RS Type 1 CG] TS 38.213CR0567
  • Introduction of multiplexing in a PUSCH with repetitions HARQ-ACK associated with DL assignments received after an UL grant for the PUSCH [HARQ-ACK MUX on PUSCH] TS 38.213CR0568
  • Clarification on not multiplexing UCI on MSG3 PUSCH TS 38.213CR0631
  • Correction on multiplexing HARQ-ACK in a PUSCH transmission TS 38.213CR0636
  • Correction on PUSCH retransmission for CG RACH-less handover TS 38.213CR0638
  • Correction on HARQ-ACK multiplexing on a PUSCH repetition [HARQ-ACK MUX on PUSCH] TS 38.213CR0646

+ 10 more changes

Rel-19 6 changes
  • CR on UEIRI multiplexed into PUSCH in TS 38.212 TS 38.212CR0244
  • CR on UEIRI multiplexed into PUSCH in TS 38.213 TS 38.213CR0762
  • CR on UL power reduction prioritization for PUSCH multiplexed with UEIRI in TS 38.213 TS 38.213CR0768
  • Corrections on CG-PUSCH transmission for conditional LTM TS 38.213CR0769
  • CR for TS 38.213 for phase continuity with OCC PUSCH in NR NTN TS 38.213CR0777
  • CR for UCI multiplexing with OCC PUSCH in NR NTN TS 38.213CR0778

Defining Specifications

3GPP specifications that define or reference PUSCH, 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 25.202 vj00 7.68Mcps TDD Option Technical Specification Rel-19 read
TS 25.221 vj00 UTRA TDD Physical Layer Specification Rel-19 read
TS 25.224 vj00 UTRA TDD Physical Layer Procedures Rel-19 read
TS 25.225 vj00 UTRA TDD Physical Layer Measurements Rel-19 read
TS 25.331 vj01 UTRAN Radio Resource Control Protocol Rel-19 read
TS 25.402 vj00 UTRAN Synchronisation Mechanisms Rel-19 read
TS 25.430 vj00 Introduction to Iub Interface Specifications Rel-19 read
TS 25.433 vj00 Node B Application Part (NBAP) Protocol Rel-19 read
TS 25.435 vj00 UTRAN Iub Interface User Plane Protocols Rel-19 read
TR 25.931 vj00 UTRAN Signalling Procedures Examples 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.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.790 vf00 LAA/eLAA for CBRS 3.5GHz Band in US Rel-15 read
TS 36.878 vd00 LTE Performance Enhancements for High Speed Scenarios Rel-13 read
TS 36.884 vd10 MMSE-IRC Receiver Performance for LTE BS Rel-13 read
TS 37.106 vj00 UE RF Requirements for Shared Spectrum Access Rel-19 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.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