Description
The Dedicated Control Channel (DCCH) is a fundamental logical channel within the 3GPP radio interface protocol architecture, operating in the control plane. It is established for a specific User Equipment (UE) when a Radio Resource Control (RRC) connection is set up, providing a dedicated, reliable signaling path. The DCCH is a bidirectional channel, meaning it is used for both uplink (UE to network) and downlink (network to UE) transmission of control information. It exists only in RRC_CONNECTED state, as it is intrinsically linked to the management of an active connection. As a logical channel, the DCCH is mapped to transport channels (like the Dedicated Transport Channel, DTCH, or common transport channels during connection establishment) and subsequently to physical channels for over-the-air transmission, with the specific mapping defined by the Radio Access Technology (RAT), such as UMTS, LTE, or NR.
In terms of operation, the DCCH carries all dedicated control signaling for a connected UE. This includes RRC protocol messages that manage the connection itself, such as RRC Connection Reconfiguration, RRC Connection Release, and measurement reporting commands. Crucially, the DCCH also serves as the conduit for higher-layer, Non-Access Stratum (NAS) signaling messages between the UE and the core network (e.g., MME in LTE, AMF in 5G). These NAS messages, which are transparent to the RAN, are encapsulated within RRC messages for transport over the DCCH. The channel employs acknowledged mode (AM) RLC (Radio Link Control) to ensure reliable, in-sequence delivery of signaling messages, which is critical for maintaining connection state consistency and executing complex procedures like handover.
The key components involved with the DCCH are the RRC protocol entities in the UE and the gNB/eNB/NodeB, and the RLC layer configured in Acknowledged Mode. Its role is central to virtually all connected-mode procedures: mobility management (handover preparation and execution), radio bearer management (setup, modification, release), security activation (ciphering and integrity protection of signaling), and the transfer of UE capability information. The establishment, maintenance, and release of the DCCH are synonymous with the lifecycle of the RRC connection. In 5G NR, while the fundamental concept remains, the protocol stack and some message structures are evolved, but the DCCH's role as the dedicated signaling bearer for a connected UE is preserved and essential for network-controlled mobility and service management.
Purpose & Motivation
The DCCH was created to provide a reliable, dedicated, and secure signaling path for individual UEs once they transition from idle to connected mode. Prior to connection establishment, UEs use common control channels (like CCCH) for initial access, but these are shared, contention-based, and not suitable for the ongoing, bidirectional exchange of sensitive control information required to maintain an active session. The DCCH solves the problem of managing complex, stateful interactions—such as handovers, bearer management, and secure NAS signaling—by providing a point-to-point logical link with guaranteed delivery semantics.
Historically, introduced in 3G UMTS (Release 99), the DCCH was a key innovation that enabled efficient, network-controlled mobility and quality of service management for packet-switched services. It addressed the limitations of using only common or broadcast channels for all control signaling, which would be inefficient, insecure, and incapable of supporting sophisticated connection states. The DCCH allows the network to maintain a precise context for each connected UE, enabling rapid adaptation of radio resources, seamless mobility across cells, and the secure transfer of subscription and session management signaling between the UE and the core network.
Its continued existence through LTE and into 5G NR underscores its fundamental purpose: to decouple the reliable transport of dedicated control signaling from user data traffic and from the initial access signaling, thereby creating a robust control plane architecture. This separation is critical for network scalability, security (enabling integrity protection and ciphering of signaling), and the efficient execution of real-time control procedures that underpin user mobility and service continuity.
Classification
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (54 CRs across 5 releases). Complements the general historical overview above with the evidence-based evolution of this function.
In Release 15, specific clarifications and corrections were introduced for the Dedicated Control Channel (DCCH) function, particularly regarding the RRC Connection Re-establishment procedure for the control plane. This included clarifications on dedicated serving cell configuration during Re-establishment and the handling of dedicated priorities when a UE transitions from RRC_INACTIVE to RRC_IDLE. Additionally, corrections were made to the control plane procedures to address missing descriptions and ensure proper UE behavior.
- 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 for TCI state in ControlResourceSet TS 38.331CR0558
- Correction to ControlResourceSetZero TS 38.331CR0580
+ 13 more changes
In Release 16, enhancements for the Dedicated Control Channel (DCCH) function included specific corrections and new procedures for Backhaul (BH) RLC channel management in IAB nodes, such as transmission suspension upon IAB-Mobile Termination (MT) failure. The release also introduced corrections for RSSI and channel occupancy measurements and extended support for Bandwidth Combination Sets (BCS) to asymmetric channel bandwidths.
- Correction on the configuration of subframe #0 and #5 for MCH in MBMS dedicated cell TS 36.331CR4259
- Corrections on default BH RLC channel TS 38.331CR1954
- Corrections on BH RLC channel TS 38.331CR2124
- Transmission suspension on BH RLC channel upon IAB-MT failure TS 38.331CR2265
- Correction on RSSI and channel occupancy measurements TS 38.331CR2306
- Miscellaenous corrections on BH RLC channel management for IAB-MT TS 38.331CR2557
+ 1 more changes
In Release 17, specific control plane corrections were introduced for Dedicated Control Channel (DCCH) functions, primarily to support new capabilities like RedCap UEs and Small Data Transmission (SDT). These included corrections to procedures for autonomous changes of UE channel bandwidth during RACH and for NR-Dual Connectivity (NR-DC) power control parameters. The updates ensured proper handling of dedicated control channels for these enhanced features and scenarios.
- RRC Correction on including GNSS validity duration and dedicated SIB31 TS 36.331CR4952
- Corrections to control plane procedures for RedCap UEs TS 38.331CR3780
- Channel Access Control for msg1/msgA in FR2-2 TS 38.331CR3827
- Correction to RRC for 71 GHz on channel occupancy duration TS 38.331CR3968
- Control plane corrections for SDT TS 38.331CR4114
- Correction to support autonomous change of UE channel bandwidth during RACH TS 38.331CR4395
+ 2 more changes
In Release 18, specific enhancements to the Dedicated Control Channel (DCCH) function included corrections to improve the delivery of posSIB segments via dedicated signaling while the UE is in RRC_CONNECTED state. This refinement ensures more reliable system information delivery on this dedicated logical channel. Additionally, other corrections and configurations related to uplink power control within the unified TCI framework were introduced, which impact the network's control signaling transmitted to the UE on the DCCH.
- Introduction of NR support for dedicated spectrum less than 5MHz for FR1 TS 36.331CR4983
- Introduction of Network Controlled Repeaters in RRC spec TS 38.331CR4162
- UE capability for Enhanced channel raster TS 38.331CR4445
- Introduction of NR support for dedicated spectrum less than 5MHz for FR1 TS 38.331CR4525
- 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
+ 9 more changes
In Release 19, the Dedicated Control Channel (DCCH) saw enhancements for on-demand positioning system information, introducing new control parameters for the on-demand posSIB request procedure. This update provided the network with additional configuration capabilities to manage how UEs request positioning assistance data via dedicated signaling. No other specific DCCH changes are indicated by the provided CR titles or grounding context.
- Introduction of 7MHz channel bandwidth TS 38.331CR5308
- Introduction of control parameters for on-demand posSIB request [OdPosSIB_Req] TS 38.331CR5406
- Correction on PC5 Relay RLC channel configuration TS 38.331CR5510
- Correction on uplink power control for Type-1 CG-PUSCH [PL RS Type 1 CG] TS 38.331CR5606
- Correction for UL full power control TS 38.331CR5675
Explore further
Broader topics and technologies where DCCH plays a role.
Defining Specifications
3GPP specifications that define or reference DCCH, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| 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 |
| TR 25.912 vj00 | Evolved UTRA and UTRAN Technical Report | Rel-19 |
| TR 25.931 vj00 | UTRAN Signalling Procedures Examples | Rel-19 |
| TR 26.902 vj00 | Video Codec Performance for 3GPP Packet Services | Rel-19 |
| TS 32.401 vj00 | Performance Management Concept & Requirements | Rel-19 |
| TS 36.133 vj20 | E-UTRA RRM Requirements | 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.314 vj00 | E-UTRA Radio Measurements Specification | 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 |
| TR 37.901 vf10 | UE Application Layer Data Throughput Performance | Rel-15 |
| TS 38.331 vj00 | NR Radio Resource Control (RRC) Protocol Specification | Rel-19 |
| TS 52.402 vj00 | GSM Performance Management Measurements | Rel-19 |