CCE

Control Channel Element

Physical Layer →
Introduced in Rel-8

CCE is the fundamental resource unit for constructing downlink control channels in LTE and NR, consisting of aggregated Resource Elements to form control messages for efficient scheduling and signaling.

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

Description

A Control Channel Element (CCE) is a logical grouping of physical resources used to transmit Downlink Control Information (DCI) on the Physical Downlink Control Channel (PDCCH). In LTE (Rel-8 onwards), a CCE is defined as a set of 36 Resource Elements (REs), which correspond to 9 Resource Element Groups (REGs) of 4 REs each, excluding those used for reference signals. This structure allows the PDCCH to be constructed by aggregating multiple CCEs (e.g., 1, 2, 4, or 8 CCEs) to support different DCI formats and coding rates, catering to various channel conditions and control information sizes. The mapping of CCEs to specific REGs within the control region of a subframe follows a predefined interleaving pattern to provide robustness against fading and interference.

In 5G NR (from Rel-15), the concept of CCE is retained and refined within the new control resource set (CORESET) framework. A CCE in NR consists of 6 Resource Blocks (RBs) in the frequency domain over the duration of one symbol (or multiple symbols if configured) within a CORESET. Each CCE is further subdivided into 6 Resource Element Groups (REGs), where a REG equals one RB in one symbol. This structure provides flexibility in control channel scheduling across the bandwidth part. The aggregation level (AL), defining the number of aggregated CCEs (1, 2, 4, 8, 16, or even 32 for extended coverage), is dynamically adapted based on the user's radio conditions, which is determined through channel state information and the chosen DCI format.

The operation of CCEs involves several key processes. First, the DCI message, containing scheduling assignments or grants, is channel coded and rate-matched. This coded bit sequence is then mapped to the allocated CCEs. The specific CCE indices for a user are derived from a hash function based on the user's Radio Network Temporary Identifier (RNTI), ensuring a pseudo-random distribution to minimize blocking collisions. The physical mapping of the CCE's REGs to actual REs within the CORESET follows a specified pattern, which can be interleaved or non-interleaved, offering trade-offs between diversity and localized transmission.

CCEs are fundamental to the operation of the control plane. They enable the transmission of critical signaling such as uplink and downlink resource grants, power control commands, slot format indications, and preemption indicators. The ability to scale the aggregation level allows the system to ensure reliable control channel reception for users at the cell edge (using high AL) while maintaining efficiency for users with good signal quality (using low AL). This dynamic adaptation is a cornerstone of the spectral efficiency and robust performance of LTE and NR networks. The entire process, from DCI generation to CCE mapping and transmission, is tightly integrated with the scheduling algorithms in the base station (gNB/eNB).

Purpose & Motivation

The CCE was introduced in LTE Rel-8 to provide a structured, scalable, and efficient method for transmitting downlink control information. Prior systems lacked such a granular and flexible unit for control channel construction, which limited the adaptability of control signaling to varying user conditions and control message sizes. The CCE architecture solves the problem of reliably delivering scheduling commands and other critical signaling in diverse radio environments by allowing the aggregation of multiple basic units to achieve different coding rates and robustness levels.

The primary motivation was to decouple the control channel design from the fixed payload sizes and to enable link adaptation specifically for the control channel. By defining a CCE as a fundamental building block, the system can dynamically decide how many CCEs (the aggregation level) to use for a particular user's DCI. This directly addresses the challenge of maintaining control channel coverage across the entire cell, from near the base station to the edge, without wasting excessive resources for users in good conditions. It provides a balance between reliability and efficiency.

Furthermore, the structured mapping of CCEs to physical REs, using interleaving patterns, was designed to exploit frequency and time diversity within the control region. This mitigates the impact of narrowband interference and channel fading, ensuring that control information remains decodable even under adverse conditions. The CCE concept thus underpins the dynamic scheduling and robust operation of the cellular network, forming a critical part of the radio interface's control plane architecture from LTE through to 5G NR.

Classification

Part ofCORESET
Related approachesPDCCHDCI

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

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

Rel-16 1 change

In Release 16, a correction was made to the CCE-to-REG mapping procedure. This change also involved a correction to the associated CSI-RS mapping for the Control Channel Element function.

  • Correction to CCE-to-REG mapping and CSI-RS mapping TS 38.211CR0078
Rel-17 3 changes

In Release 17, specific corrections were made to the rules governing the Blind Decoding (BD) and Control Channel Element (CCE) budget for scheduling cells operating in the FR2-2 frequency range. These corrections addressed the calculation of the BD/CCE budget when using a release-specific number of serving cells for NR operation in FR2-2. Furthermore, the release corrected the method for determining the number of configured downlink component carriers (DL-CCs) used in this BD/CCE budget calculation for FR2-2.

  • Correction for BD/CCE budget of scheduling cell(s) in FR2-2 TS 38.213CR0373
  • Correction on BD/CCE decoding with release-specific number of serving cell(s) for NR operation in FR2-2 TS 38.213CR0382
  • Correction of number of configured DL-CCs for BD/CCE budget for FR2-2 TS 38.213CR0425

Explore further

Broader topics and technologies where CCE plays a role.

Defining Specifications

3GPP specifications that define or reference CCE, 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.141 vj00 E-UTRA BS Conformance Testing Rel-19
TS 36.211 vj10 LTE Physical Layer Specification Rel-19
TS 36.213 vj10 LTE Physical Layer Procedures Rel-19
TS 36.216 vj00 LTE Relay Node Physical Layer 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.211 vj10 NR Physical Channels and Modulation Rel-19
TS 38.213 vj10 NR Physical Layer Control Procedures Rel-19
TS 38.300 vj00 NG-RAN Overall Description 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
TR 38.912 vj00 Study on New Radio Access Technology Rel-19
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.