Common Control Channel

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.

Key Features

• Provides initial uplink signaling for RRC connection establishment (RRC Connection Request)
• Carries downlink network responses like RRC Connection Setup and RRC Connection Reject
• Operates when no RRC connection exists, using shared/contention-based resources
• Utilizes RLC Transparent Mode for low-latency message delivery
• Mapped to transport channels like RACH (UL) and FACH/DL-SCH (DL) depending on the RAT
• Essential for cell selection, system information acquisition, and paging response procedures

Evolution Across Releases

Defining Specifications