3GLTEInfo Text-based logo for the 3GLTEInfo telecom engineering reference platform. 3GLTE INFO TELECOM ENGINEERING REFERENCE
Menu

Home / 5G / Protocols / PHY / PDSCH

5G NR PDSCH - Physical Downlink Shared Channel

The 5G NR PDSCH, or Physical Downlink Shared Channel, is the main scheduled downlink data channel in NR. It carries DL-SCH on physical resources selected by the network and decoded by the UE after the related PDCCH assignment.

Read PDSCH as the point where downlink scheduling turns into actual payload delivery on the OFDM grid. Frequency allocation, time allocation, mapping type, MCS, layer count, DMRS, optional PTRS, and HARQ behavior all shape whether the transport block is delivered efficiently.

Technology 5G NR
Full name Physical Downlink Shared Channel
Transport channel DL-SCH
Main specs 3GPP TS 38.211, 38.212, 38.213, 38.214
Release Release 18
Main concepts Frequency allocation, time allocation, mapping type, MCS, layers, DMRS, PTRS, HARQ
Why it matters PDSCH is the main scheduled downlink data channel, so it directly shapes throughput, BLER, latency, and user-plane delivery
5G NR PDSCH resource view showing payload-bearing resource elements and overhead such as DMRS
PDSCH payload is defined by scheduled time-frequency resources after reference-signal and overhead regions are removed.
5G NR PDSCH workflow showing DCI, allocation, coding, mapping, reference signals, and HARQ outcome
A useful PDSCH reading path starts from the control assignment, then follows allocation, coding, layer mapping, and retransmission outcome.

Contents

  1. Overview
  2. How the PDSCH model works
  3. Operational variants
  4. Where PDSCH appears in real procedures
  5. Troubleshooting
  6. References
  7. FAQ

Overview

PDSCH is the main physical downlink data channel in NR. In most downlink activity, the network sends a scheduling decision on PDCCH, and the UE then receives the transport block on PDSCH inside the active BWP.

  • PDSCH carries DL-SCH on physical resources in the downlink grid.
  • Its time and frequency position come from the scheduling assignment.
  • Its usable payload depends on MCS, layer count, and overhead such as DMRS and PTRS.
  • PDSCH behavior is central to throughput, BLER, latency, and retransmission analysis.

Quick interpretation

Role Main scheduled downlink data channel
Carries DL-SCH transport blocks
Scheduled by PDCCH DCI in the active BWP
Main allocation fields Frequency-domain allocation, time-domain allocation, MCS, HARQ process, redundancy version, layer and antenna-port context
Main overhead DMRS, optional PTRS, reserved resources, and other resource exclusions
Main impact Throughput, decode reliability, latency, retransmission load, and observed downlink efficiency

How the PDSCH model works

Read PDSCH as a downlink delivery chain. The control assignment identifies the allocation and decode settings, channel coding and rate matching prepare the transport block, reference signals support channel estimation, and the UE combines all of that to recover the payload.

Control assignment and allocation

A typical PDSCH event starts from PDCCH. The DCI tells the UE how to find the scheduled resources, including the frequency-domain allocation and time-domain allocation. Read those fields in the context of the active BWP, current numerology, and slot timing from frame structure.

Frequency-domain allocation

Frequency allocation determines which physical resource blocks are used. The allocation is interpreted inside the active BWP, so the same raw field value does not mean the same thing if the BWP changes.

Time-domain allocation and mapping type

Time allocation determines which OFDM symbols carry the PDSCH transmission. Mapping Type A and Mapping Type B describe two main time-domain mapping styles. Mapping Type A is tied to slot-oriented behavior, while Mapping Type B supports more flexible symbol placement such as shorter allocations and front-loaded scheduling.

Transport block, coding, and rate matching

The transport block is processed through the coding chain defined for shared data, including code-block handling and rate matching. The practical payload size depends on the scheduled resources together with the selected modulation and coding scheme. Use Transport Block Size and Resource Allocation and MCS Tables when checking those assumptions.

Layer mapping and transmission scheme

PDSCH may use one or more layers depending on rank, UE capability, and radio conditions. More layers can increase data rate, but only if channel quality, beam behavior, and scheduling conditions support the chosen transmission mode.

DMRS and PTRS

PDSCH decoding depends on DMRS for channel estimation. PTRS may also be present when phase tracking support is needed. Both improve decoding robustness, but they also consume resource elements that would otherwise carry payload.

HARQ outcome

If decoding succeeds, the UE completes the downlink delivery and later provides the relevant feedback. If decoding fails, HARQ retransmission behavior becomes part of the same PDSCH story. Read repeated low throughput together with HARQ, BLER, and scheduling cadence.

Element Meaning in PDSCH reading
Frequency-domain allocation Which PRBs in the active BWP are used for the transmission
Time-domain allocation Which OFDM symbols in the slot or mini-slot carry the PDSCH
Mapping type How the time-domain placement is interpreted for the PDSCH transmission
MCS The modulation and coding efficiency chosen for the transport block
Layers The number of spatial streams used by the transmission
DMRS / PTRS Reference-signal overhead and decode support inside the allocation
HARQ process and RV Retransmission context and combining behavior for failed or repeated delivery

Operational variants

PDSCH does not use user-facing numbered formats like PUCCH. The main practical variants are the allocation and transmission patterns below.

Variant Reading notes
Slot-based PDSCH The common full-slot scheduling style used in steady downlink traffic and throughput analysis
Mini-slot style PDSCH Shorter allocations used when latency or timing flexibility matters more than full-slot packing
Mapping Type A Slot-oriented time-domain mapping often used in regular scheduled downlink operation
Mapping Type B More flexible time-domain mapping useful for non-slot-based or front-loaded scheduling patterns
Single-layer transmission Simpler downlink operation with lower spatial capacity and often more robust decode conditions
Multi-layer transmission Higher capacity mode when rank, beam conditions, and UE support allow more than one layer
DMRS-heavy allocation Higher overhead profile that can improve decode support while reducing net payload space
HARQ retransmission Repeated transport-block delivery using the HARQ process rather than a brand new first transmission

Where PDSCH appears in real procedures

Regular downlink data delivery

PDCCH assignment -> PDSCH reception -> decode -> HARQ feedback

This is the core PDSCH path. The control assignment arrives first, then the UE decodes the transport block on the scheduled PDSCH resources, and later the HARQ process determines whether retransmission is needed.

Connected-mode throughput

Scheduler decision -> PRB and symbol allocation -> PDSCH transport block -> delivered downlink throughput

Use this reading path when throughput is lower than expected. Carrier bandwidth alone is not enough. Check the actual PRB count, symbol count, MCS, layers, overhead, and retransmission rate in the live allocation.

System reconfiguration impact

Changes in BWP, DMRS configuration, layer capability, search space, or related radio setup can change practical PDSCH behavior even when the service itself does not change at higher layers. That is why RRC Reconfiguration context often matters when the downlink pattern changes suddenly.

Troubleshooting

Start with the control assignment, then move through the actual allocation and decode outcome. Many apparent PDSCH failures are really control, BWP, or timing-interpretation problems.

  • Check whether the expected PDCCH assignment was present before the PDSCH event.
  • Check PRB allocation, symbol allocation, and scheduling cadence rather than nominal bandwidth alone.
  • Check MCS, code-rate trend, and layer count against the observed radio conditions.
  • Check DMRS, optional PTRS, and any resource exclusions inside the allocation.
  • Check HARQ retransmission patterns, redundancy version behavior, and downlink BLER.
  • Check the active BWP and current timing interpretation.
Symptom What to inspect first
Low downlink throughput PRB count, symbol count, MCS, layers, scheduling cadence, and retransmission rate
Unexpectedly high BLER Radio quality, DMRS support, MCS aggressiveness, and HARQ combining behavior
No expected downlink data Whether a valid PDCCH assignment appeared, whether the BWP was correct, and whether the UE monitored the right timing window
Throughput lower than carrier width suggests Active BWP, real scheduled symbols, overhead, rank usage, and retransmissions
Allocation looks correct but payload is still small TBS assumptions, MCS table, DMRS or PTRS overhead, and code-rate choice

Common mistakes

  • equating total carrier bandwidth with guaranteed downlink throughput
  • reading PRB count without also checking symbol count and overhead
  • skipping the preceding PDCCH assignment and jumping straight to the data channel
  • ignoring active BWP context when decoding allocation fields
  • assuming more layers always mean better usable throughput under real radio conditions

References

FAQ

What does PDSCH do in 5G NR?

PDSCH carries the main scheduled downlink data delivered through DL-SCH after the UE receives the relevant control assignment.

How is PDSCH related to PDCCH?

In typical operation, PDCCH carries the DCI that tells the UE where and how to decode the following PDSCH transmission.

Why is PDSCH important for throughput?

Because it is the main downlink data-bearing channel. Throughput depends on how much PDSCH resource is really scheduled and how efficiently that allocation is used.

What should I inspect first when downlink data seems low?

Start with the actual PDSCH allocation, MCS, layers, overhead, HARQ behavior, and whether the expected PDCCH assignment was successfully delivered.

Does more PRB allocation always mean more throughput?

No. Symbol count, DMRS and PTRS overhead, MCS, layer count, BLER, and retransmission behavior all affect the final delivered throughput.

How does BWP affect PDSCH?

PDSCH allocations are interpreted inside the active BWP. The same carrier can therefore show different practical resource meaning depending on which BWP is active at that moment.

Related PHY topics and tools