PDCCH

Physical Downlink Control Channel

Physical Layer →
Introduced in Rel-8

PDCCH is the fundamental downlink physical channel in LTE and NR that carries Downlink Control Information (DCI) for resource allocation, scheduling, and other critical control signaling to user equipment.

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

Description

The Physical Downlink Control Channel (PDCCH) is a key physical channel in both LTE (E-UTRA) and NR (New Radio) that transports Downlink Control Information (DCI) from the network (gNB in NR, eNB in LTE) to User Equipments (UEs). It operates in the control region of a subframe (LTE) or slot (NR). The PDCCH does not carry higher-layer data; instead, it carries essential scheduling assignments and control commands. A UE must continuously monitor a set of PDCCH candidates for potential DCIs addressed to it, using a unique identifier (C-RNTI, SI-RNTI, etc.) scrambled in the DCI's cyclic redundancy check (CRC).

Architecturally, PDCCH transmission involves several key steps. First, the DCI payload is generated, which includes information like resource block assignment, modulation and coding scheme (MCS), HARQ process number, and power control commands. This payload is attached with a CRC, which is then scrambled with the target UE's RNTI. The bit sequence is then channel coded (using tail-biting convolutional coding in LTE and Polar coding in NR for most cases), rate-matched, and mapped to Control Channel Elements (CCEs). In LTE, CCEs are grouped (aggregation levels 1, 2, 4, 8) to provide different coding rates for link adaptation. These CCEs are then mapped to specific Resource Element Groups (REGs) within the control region of the OFDMA grid, which is defined by the first few OFDM symbols of a subframe, as indicated by the PCFICH.

In NR, the concept evolved into a more flexible structure. NR-PDCCH is organized in Control Resource Sets (CORESETs) and Search Spaces. A CORESET defines a time-frequency region (up to 3 OFDM symbols and a configurable bandwidth) where PDCCH can be transmitted. Within a CORESET, the UE monitors predefined PDCCH candidates in one or more Search Spaces (common or UE-specific). NR uses Polar coding for DCI and supports aggregation levels from 1 to 16. The PDCCH's role is absolutely central to network operation: it delivers uplink grants (telling the UE when and where to transmit), downlink assignments (telling the UE where to receive PDSCH), slot format indicators, pre-emption indications, and power control commands. Its reliable reception is a prerequisite for any data transmission, making its design critical for system capacity, latency, and UE battery life.

Purpose & Motivation

The PDCCH was created to solve the fundamental problem of dynamic and efficient resource allocation in packet-based OFDMA cellular systems like LTE and NR. Previous systems like UMTS used dedicated channels or less dynamic shared channels, which were inefficient for bursty data traffic. The PDCCH enables fast, per-subframe (or per-slot) scheduling, allowing the network to assign radio resources optimally based on instantaneous channel conditions, traffic demand, and QoS requirements for multiple UEs.

Historically, the move to all-IP, packet-switched architectures necessitated a control channel that could handle rapid scheduling decisions. The PDCCH provides this by carrying compact DCI messages that instruct UEs on precisely which time-frequency resources are allocated for their uplink or downlink data transmissions (on PUSCH or PDSCH). This solves the limitations of static or semi-static allocation, dramatically improving spectral efficiency and supporting advanced features like frequency-selective scheduling, multi-user MIMO, and low-latency communication.

Furthermore, the PDCCH design addresses the challenge of control channel capacity and reliability. By using CCE aggregation and link adaptation, it ensures that control information can reach UEs even at the cell edge. The introduction of enhanced PDCCH (EPDCCH) in LTE Rel-11 and the completely redesigned NR-PDCCH in Rel-15 were motivated by the need for increased control channel capacity, improved interference coordination, support for beamforming, and flexibility for diverse use cases like massive IoT and ultra-reliable low-latency communication (URLLC). The PDCCH is thus the primary tool for the medium access control (MAC) layer to exert its scheduling function, making it indispensable for the performance of modern cellular networks.

Classification

Part ofCORESET
Related approachesPDSCHPUSCHDCIRNTICCE

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

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

Rel-15 15 changes

In Release 15, several clarifications and corrections were introduced for the PDCCH, including defining PDCCH-subframes for NB-IoT UEs and clarifying PDCCH monitoring for overlapped CORESETs and when not fully aligned with PDCCH periods. Specific corrections addressed PDCCH order, resource allocation for PDSCH in Type 0 common search space, and PDCCH reception type combinations on CSS. The release also added monitoring for PDCCH ordering PRACH on an SCell and established QCL assumptions for receiving PDCCH for RAR.

  • Number of PDCCH/EPDCCH/SPDCCH received parallel TS 36.302CR1198
  • Correction on PDCCH order TS 36.302CR1199
  • Clarifying PDCCH Period Definition TS 36.321CR1300
  • Defining PDCCH-Subframes for NB-IoT UE TS 36.321CR1327
  • Clarification of PDCCH monitoring when not fully aligned with PDCCH periods TS 36.321CR1459
  • CR on inclusion of TC-RNTI for monitored RNTI for UL-SCH and inclusion of monitoring PDCCH ordering PRACH on SCell TS 38.202CR0007

+ 9 more changes

Rel-16 6 changes

In Release 16, enhancements to the PDCCH included introducing PDCCH-based HARQ-ACK feedback for multi-TB scheduling and making corrections to PDCCH monitoring procedures. These corrections addressed specific scenarios for DAPS handover, for cells using Rel-15 monitoring capability, and for the UE procedure to determine PDCCH assignment with Rel-16 capability. Additional fixes resolved collisions between PDCCH and PDSCH in multi-TRP deployments and corrected blind detection for NR-Dual Connectivity.

  • PDCCH-based HARQ-ACK for a specific HARQ process with multi-TB scheduling TS 36.321CR1517
  • CR on correction on PDCCH monitoring for DAPS HO TS 38.213CR0132
  • Correction on PDCCH monitoring on cell(s) configured with Rel-15 PDCCH monitoring capability TS 38.213CR0170
  • Correction on UE procedure for determining physical downlink control channel assignment for Rel-16 PDCCH monitoring capability TS 38.213CR0230
  • Corrections for the issue of PDCCH and PDSCH colliding in multi-TRP TS 38.214CR0135
  • Correction on PDCCH Blind Detection for NR-DC TS 38.213CR0102
Rel-17 16 changes

In Release 17, enhancements to the PDCCH function included introducing mechanisms for PDCCH repetition with SSSG switching and refining multi-slot PDCCH monitoring for NR-DC, CA scenarios, and the FR2-2 frequency range. Corrections and clarifications were also made for procedures such as PDCCH monitoring adaptation, PDCCH skipping, and broadcast PDCCH monitoring in the active DL BWP. Additionally, specific adjustments addressed PDCCH reception timing alignment with uplink cancellation indications and validation for semi-persistent CSI activation/deactivation DCI formats.

  • CR on PDCCH repetition with SSSG switching TS 38.213CR0332
  • Correction on the tables for determining Type0 PDCCH monitoring occasions TS 38.213CR0337
  • Correction on multi-slot PDCCH monitoring in NR-DC and CA scenarios with mixed capability types TS 38.213CR0342
  • Corrections on PDCCH monitoring enhancement for 52-71GHz spectrum TS 38.213CR0346
  • Correction for multi-slot PDCCH monitoring in FR2-2 TS 38.213CR0372
  • CR on PDCCH monitoring when overlapping with the rate matching pattern to TS 38.213 TS 38.213CR0383

+ 10 more changes

Rel-18 8 changes

In Release 18, enhancements to the PDCCH function included clarifying and correcting procedures for PDCCH order-initiated Contention-Free Random Access (CFRA), particularly for PRACH association and retransmission indicators. It also introduced specific adaptations for PDCCH monitoring, addressing behavior for DRX groups, operation in dedicated spectrum below 5 MHz, and for HD-FDD RedCap UEs monitoring Type0B CSS. Furthermore, the release detailed beam collision handling between PDCCH and PDSCH with small offsets in both multi-DCI and single-DCI based multi-TRP (MTRP) deployments.

  • Corrections on PRACH association indicator in PDCCH order in 38.212 TS 38.212CR0192
  • CR on the PRACH retransmission indicator field included in the PDCCH order TS 38.212CR0213
  • CR on PDCCH monitoring for dedicated spectrum less than 5 MHz TS 38.213CR0596
  • CR on Beam collision between PDSCH with offset less than a threshold and PDCCH in M-DCI based MTRP TS 38.214CR0620
  • CR on Beam collision between PDSCH with offset less than a threshold and PDCCH in S-DCI based MTRP TS 38.214CR0621
  • Clarification of PDCCH ordered CFRA for 2TA TS 38.300CR0868

+ 2 more changes

Rel-19 6 changes

In Release 19, key enhancements to the PDCCH include the introduction of repetitions for the Type0-PDCCH CSS set and for common PDCCH in terrestrial networks (TN), as well as specific support for non-terrestrial networks (NTN). The release also introduces corrections for PDCCH candidate skipping when overlapping with SSB, aligns parameters for intra-slot repetition, and adds applicability for eRedCap in performance test cases.

  • Introduction of PDCCH repetitions for Type0-PDCCH CSS set in TNs [Common_PDCCH_Rep_TN] TS 38.213CR0748
  • Introduction of common PDCCH repetition (Rel-19 NTN) for TN [Common_PDCCH_rep_TN] TS 38.300CR1058
  • Correction on PDCCH candidates skipping for receiving RAR when overlapping with candidate SSB TS 38.213CR0755
  • Alignment on parameter for intra-slot PDCCH repetition TS 38.213CR0761
  • Introduction of SIB1 PDSCH repetition for FR1 TN [Common_PDCCH_rep_TN] TS 38.300CR1085
  • Addition of applicability for eRedCap for PDCCH performance test cases TS 38.522CR0685

Explore further

Broader topics and technologies where PDCCH plays a role.

Defining Specifications

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

SpecificationTitleRelease
TR 21.905 vj00 3GPP Technical Terms and Definitions Rel-19
TS 36.104 vj10 Base Station (BS) radio transmission and reception Rel-19
TS 36.116 vj00 E-UTRA Relay RF Requirements Rel-19
TS 36.117 vj00 E-UTRA Relay RF Test Methods & Requirements Rel-19
TS 36.133 vj20 E-UTRA RRM Requirements Rel-19
TS 36.141 vj00 E-UTRA BS Conformance Testing Rel-19
TS 36.201 vj00 LTE Physical Layer General Description Rel-19
TS 36.211 vj10 LTE Physical Layer Specification Rel-19
TS 36.212 vj10 LTE Multiplexing and Channel Coding Rel-19
TS 36.213 vj10 LTE Physical Layer Procedures Rel-19
TS 36.216 vj00 LTE Relay Node Physical Layer 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.306 vj00 E-UTRA UE Radio Access Capability Parameters Rel-19
TS 36.321 vj00 E-UTRA MAC Protocol Specification Rel-19
TS 36.331 vj00 LTE RRC Protocol Specification Rel-19
TS 36.747 ve00 Enhanced CRS and SU-MIMO IM Performance Requirements Rel-14
TS 36.825 vd00 Study on Additional LTE TDD Configurations Rel-13
TS 36.863 vc00 CRS Interference Mitigation for Homogeneous Networks Rel-12
TS 36.867 vd00 LTE DL 4 Rx Antenna Port Study TR Rel-13
TS 36.871 vb00 Downlink MIMO Enhancement for LTE-Advanced Rel-11
TS 36.878 vd00 LTE Performance Enhancements for High Speed Scenarios Rel-13
TR 36.976 vj00 LTE-based 5G Terrestrial Broadcast Overview Rel-19
TR 37.901 vf10 UE Application Layer Data Throughput Performance Rel-15
TR 37.911 vj00 3GPP 5G NTN Self-Evaluation Report Rel-19
TS 38.133 vj20 5G UE Radio Requirements for RRC_IDLE Mobility Rel-19
TS 38.174 vj10 NR Integrated Access and Backhaul Radio Spec Rel-19
TS 38.176 vj20 IAB Conformance Testing Specification Rel-19
TS 38.201 vj00 NR Physical Layer General Description Rel-19
TS 38.202 vj00 5G NR Physical Layer Services Rel-19
TS 38.211 vj10 NR Physical Channels and Modulation Rel-19
TS 38.212 vj10 NR Multiplexing and Channel Coding Rel-19
TS 38.213 vj10 NR Physical Layer Control Procedures Rel-19
TS 38.214 vj10 NR Physical Layer Procedures for Data Rel-19
TS 38.300 vj00 NG-RAN Overall Description Rel-19
TS 38.521 vj20 NR Physical Layer UE Conformance Testing Rel-19
TS 38.522 vj11 UE Conformance Test Applicability Statement Rel-19
TS 38.523 vj20 5G NR UE Conformance Testing: Idle/Inactive Rel-19
TR 38.808 vh00 Study on NR above 52.6 GHz to 71 GHz Rel-17
TS 38.824 vg00 NR URLLC Physical Layer Enhancements Study Rel-16
TR 38.830 vh00 NR Coverage Enhancements Study Rel-17
TS 38.831 vg10 UE RF Requirements for FR2 Enhancements Rel-16
TR 38.838 vh00 Study on XR Evaluations for NR Rel-17
TR 38.840 vg00 NR UE Power Saving Study Rel-16
TR 38.869 vi00 Study on low-power wake up signal and receiver for NR Rel-18
TR 38.889 vg00 NR-based access to unlicensed spectrum study Rel-16
TR 38.903 vj00 Test Tolerances & Measurement Uncertainties Rel-19
TS 45.820 vd10 CIoT for Internet of Things Rel-13
Patrick Zandl

About the author: Patrick Zandl (b. 1974)

Telecommunications specialist, technology journalist (founder of the Mobil server), and developer who has been running since 2025 — the largest Czech-language resource on AI-assisted programming. Formerly Chief Wizard Architect at Prusa3D and head of development for Turris at CZ.NIC; currently a consultant and instructor on AI implementation in companies.