CCCH

Common Control Channel

Radio Access Network →
Introduced in R99 Also in: Management, User Equipment

CCCH is a logical channel used for transmitting control information between the network and mobile devices to handle initial access procedures like random access, paging, and system information broadcast.

Category
Radio Access Network
Introduced
R99
Where
Radio Access Network › NG-RAN (5G)
Also touches
2 segments
Specifications
20 specs
CCCH Description Purpose Related Classification Detected Changes Specifications

Description

The Common Control Channel (CCCH) is a fundamental logical channel in 3GPP radio access networks (UTRAN, E-UTRAN, and NR) that operates in the uplink and downlink directions. As a control channel, it does not carry user data but is essential for the initial signaling procedures that enable a User Equipment (UE) to access the network. The CCCH is used when no Radio Resource Control (RRC) connection exists between the UE and the network, or when the UE is in an RRC_IDLE state and needs to initiate communication. It operates over shared radio resources and is mapped to transport channels like the Random Access Channel (RACH) in the uplink and the Forward Access Channel (FACH) in UMTS or the Downlink Shared Channel (DL-SCH) in LTE/NR for the downlink.

In the uplink direction, the CCCH is primarily used by the UE to send initial access messages. The most critical procedure is the RRC Connection Request, where the UE initiates a connection to the network by sending its identity (like a Temporary Mobile Subscriber Identity - TMSI or a random value) and the establishment cause (e.g., mobile originating call, emergency call, or tracking area update). This message is transmitted after the UE successfully completes the physical layer random access procedure on the PRACH. The uplink CCCH message is carried over the RACH transport channel in UMTS or the UL-SCH in LTE/NR, following a successful contention-based random access preamble.

In the downlink direction, the network uses the CCCH to respond to the UE's access attempts and to broadcast essential system information. The key downlink message is the RRC Connection Setup, which is the network's response to a successful RRC Connection Request. This message contains the initial radio resource configuration for the UE, instructing it to move to an RRC_CONNECTED state and switch to using dedicated control channels (DCCH). The downlink CCCH is also used to carry RRC Connection Reject messages when the network cannot accommodate the request. Furthermore, system information blocks (SIBs), which contain critical parameters for cell selection, access control, and neighboring cell information, are broadcast on the BCCH logical channel, but the scheduling information for these SIBs is often signaled using control information associated with the CCCH's shared resource allocation.

The architecture of CCCH handling involves multiple protocol layers. At the RRC layer, the CCCH is a Service Access Point (SAP) for control messages. These messages are then processed by the Packet Data Convergence Protocol (PDCP) layer for integrity protection (in NR) and by the Radio Link Control (RLC) layer, which operates in transparent mode (TM) for CCCH messages, meaning it does not add a header. The Medium Access Control (MAC) layer is responsible for multiplexing logical channels (including CCCH) onto transport channels and handling the scheduling and HARQ processes for the shared resources. The physical layer then maps these transport channels to physical channels for transmission over the air interface. The CCCH's role is transient but critical; once an RRC connection is established, all subsequent signaling moves to the Dedicated Control Channel (DCCH), which uses acknowledged mode RLC for reliable delivery.

Purpose & Motivation

The CCCH was created to solve the fundamental problem of initial network access in a cellular system. Before any dedicated resources are allocated, a mobile device must have a standardized, efficient method to contact the network, identify itself, and request service. The CCCH provides this shared, contention-based signaling channel, allowing any device in the cell to initiate communication without pre-established context. It is the entry point for all network services, from voice calls to data sessions.

Historically, early cellular systems like GSM also had common control channels (like the RACH and AGCH), and the 3GPP CCCH concept evolved from these principles into the UMTS and later LTE/5G NR frameworks. It addresses the limitations of having only dedicated channels by providing a scalable and resource-efficient method for handling sporadic access attempts from potentially thousands of idle devices. Without a common channel, the network would need to permanently assign dedicated resources to every device, which is impossible from a radio resource management perspective. The CCCH enables a many-to-one communication model for initial access, which is essential for network scalability and battery efficiency in mobile devices, as they only need to activate their transmitters briefly to send an access request.

Furthermore, the CCCH is crucial for network-controlled mobility and reachability. Through the associated paging channel (which is technically on the PCCH logical channel but relies on the control plane structure that includes CCCH), the network can locate and notify idle UEs of incoming calls or data. The initial response from a paged UE also uses the uplink CCCH. Thus, the CCCH solves the dual problems of initial network attachment and efficient device reachability, forming the cornerstone of the control plane architecture in all 3GPP radio access technologies.

Classification

Part ofDCCH
Related approachesBCCHRACH

Detected Changes Across Releases

from 3GPP Change Requests

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

Rel-15 22 changes

In Release 15, specific corrections and clarifications were introduced for the Common Control Channel (CCCH) function, focusing on the configuration and signaling of common control resources. This included corrections to the `commonControlResourceSet` and its frequency reference point, as well as clarifications to the `commonSearchSpaceList` within `PDCCH-ConfigCommon`. Additionally, procedures for transferring common configuration during handover were addressed.

  • Control Plane latency reduction TS 36.331CR3453
  • Corrections to random access power control for TDD in 36.331 TS 36.331CR3580
  • correction on power control TS 36.331CR3663
  • Supporting MME and AMF overload control TS 36.331CR3745
  • Correction to commonControlResourceSet TS 38.331CR0418
  • Correction for TCI state in ControlResourceSet TS 38.331CR0558

+ 16 more changes

Rel-16 9 changes

In Release 16, the CCCH-related updates primarily involved corrections and clarifications for operation on an active bandwidth part (BWP), specifically for the common search space. Furthermore, the release introduced corrections to the description of msg1-SubcarrierSpacing within the RACH-ConfigCommon, which is part of the common control channel procedures for random access.

  • Introduction of additional RACH configurations for TDD FR1 TS 38.331CR1486
  • Corrections on default BH RLC channel TS 38.331CR1954
  • Corrections on BH RLC channel TS 38.331CR2124
  • Clarifications for the common search space on the active BWP TS 38.331CR2146
  • Transmission suspension on BH RLC channel upon IAB-MT failure TS 38.331CR2265
  • Correction on RSSI and channel occupancy measurements TS 38.331CR2306

+ 3 more changes

Rel-17 14 changes

In Release 17, the Common Control Channel (CCCH) function saw enhancements primarily focused on RACH partitioning, including support for both 2-step and 4-step RA configurations and corrections for related control plane procedures. It also introduced specific RACH configuration corrections for RedCap UEs and for features like SDT (Small Data Transmission) and NR-DC (NR Dual Connectivity). Furthermore, new aspects for channel access control for msg1/msgA in the FR2-2 frequency range and support for autonomous change of UE channel bandwidth during RACH were implemented.

  • Introduction of Common RACH Partitioning Aspects TS 38.331CR2951
  • Correction for features applicable to RACH partitioning TS 38.331CR3177
  • Correction for features applicable for common signalling for RACH Partitioning TS 38.331CR3469
  • Correction for RACH partitioning with both 2-step and 4-step RA configurations TS 38.331CR3771
  • Corrections to control plane procedures for RedCap UEs TS 38.331CR3780
  • Correction on RACH configuration for RedCap TS 38.331CR3800

+ 8 more changes

Rel-18 17 changes

In Release 18, specific clarifications were introduced for the configuration of the Common Control Channel (CCCH), particularly regarding the **RACH-ConfigCommon** parameters used for Contention-Free Random Access (CFRA) procedures. These updates provided clearer configuration rules for procedures initiated by PDCCH order and for System Information requests. The release also included miscellaneous corrections related to RACH-less handover, which impacts the CCCH's role in control signaling during mobility.

  • Introduction of Network Controlled Repeaters in RRC spec TS 38.331CR4162
  • UE capability for Enhanced channel raster TS 38.331CR4445
  • Generalization of RACH-less handover [RACH-lessHO] TS 38.331CR4636
  • Introduction of new capability for intra-band EN-DC channel spacing [Intra-Band_EN-DC_Channelspacing] TS 38.331CR5013
  • Miscellaneous RRC corrections for Network-controlled repeaters TS 38.331CR4617
  • Rapporteur corrections on RRC for the generalization of RACH-less [RACH-lessHO] TS 38.331CR4706

+ 11 more changes

Rel-19 7 changes

In Release 19, the updates to the Common Control Channel (CCCH) function included the introduction of control parameters for an on-demand posSIB request procedure. Furthermore, the release specified updates to UE capabilities relevant to system control. These changes were part of broader corrections and enhancements to various radio resource control and management procedures.

  • Introduction of 7MHz channel bandwidth TS 38.331CR5308
  • Introduction of control parameters for on-demand posSIB request [OdPosSIB_Req] TS 38.331CR5406
  • Updates of Rel-19 UE capability, including [Simul_SRSCS], [Common_PDCCH_rep_TN], [Pos_SRSHop] TS 38.331CR5590
  • Correction on PC5 Relay RLC channel configuration TS 38.331CR5510
  • Correction on NCD-SSB based RACH-less HO [RACH-lessHO] TS 38.331CR5585
  • Correction on uplink power control for Type-1 CG-PUSCH [PL RS Type 1 CG] TS 38.331CR5606

+ 1 more changes

Explore further

Broader topics and technologies where CCCH plays a role.

Defining Specifications

3GPP specifications that define or reference CCCH, 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 25.222 vj00 UTRA TDD Multiplexing & Channel Coding Rel-19
TS 25.301 vj00 UE-UTRAN Radio Interface Protocol Architecture Rel-19
TS 25.302 vj00 UTRA Physical Layer Services Rel-19
TS 25.321 vj00 MAC Protocol Specification for UTRAN Rel-19
TS 25.322 vj00 RLC Protocol Specification Rel-19
TS 25.331 vj00 UTRAN RRC Protocol Specification Rel-19
TS 25.423 vj00 UTRAN RNSAP Specification Rel-19
TR 25.931 vj00 UTRAN Signalling Procedures Examples Rel-19
TS 32.401 vj00 Performance Management Concept & Requirements Rel-19
TS 34.124 vj00 EMC Requirements for 3G UTRA Terminals Rel-19
TS 36.124 vj00 EMC for E-UTRA User Equipment Rel-19
TS 36.133 vj20 E-UTRA RRM Requirements Rel-19
TS 36.322 vj00 E-UTRA Radio Link Control Protocol Specification Rel-19
TS 36.331 vj00 LTE RRC Protocol Specification Rel-19
TS 38.331 vj00 NR Radio Resource Control (RRC) Protocol Specification Rel-19
TS 43.868 vc10 GERAN Improvements for MTC Feasibility Study Rel-12
TS 44.060 vj00 GERAN RLC/MAC Protocol Specification Rel-19
TS 49.008 vj00 BSSAP on E-interface for inter-MSC handover Rel-19
TS 52.402 vj00 GSM Performance Management Measurements Rel-19