Description
The Dedicated Channel (DCH) is a key transport channel within the UMTS Radio Access Network (UTRAN), defined from 3GPP Release 99 onwards. It operates as a bidirectional channel, established per user equipment (UE) to carry dedicated traffic, including user plane data (e.g., voice frames, packet data) and associated control information. The DCH is a transport channel, meaning it defines the characteristics of how data is transferred over the radio interface, and it is directly mapped onto a Dedicated Physical Channel (DPCH) in the physical layer. This mapping involves processes like channel coding, interleaving, and rate matching, which are tailored to the radio conditions and service requirements.
Architecturally, the DCH exists between the UE and the Radio Network Controller (RNC). It is set up, maintained, and released by the RNC via Radio Resource Control (RRC) signaling during a Radio Access Bearer (RAB) establishment or reconfiguration. The DCH supports variable bit rates, which can be changed during a connection through Transport Format Combination (TFC) selection, allowing dynamic adaptation to the user's data flow. It can utilize either Frequency Division Duplex (FDD) or Time Division Duplex (TDD) modes, with the physical layer structure differing accordingly. In FDD, the DPCH uses dedicated channelization and scrambling codes to isolate the user's transmission.
The DCH's operation involves several key layers and protocols. At the Medium Access Control (MAC) layer, data is segmented into transport blocks and assigned a Transport Format (TF), which defines parameters like block size and transmission time interval (TTI). Multiple DCHs can be multiplexed for a single UE. The RNC performs outer loop power control by setting the target Signal-to-Interference Ratio (SIR) for the DCH, while fast closed-loop power control operates on the associated DPCH to combat fading. The DCH is a central component for services requiring guaranteed quality of service (QoS), such as conversational voice (AMR codec) and interactive video calls, as it provides dedicated resources with controlled latency and error rates.
Its role extends to supporting soft handover, where a UE can be simultaneously connected to multiple Node Bs via multiple DCHs, with the RNC performing selection combining. The DCH is tightly integrated with the lub interface (between Node B and RNC) and the lu interface (between RNC and Core Network), where it is carried within the Frame Protocol for user data transport. While primarily a UMTS channel, its concepts influenced later 3GPP systems, though in LTE, dedicated channels were replaced by a shared channel paradigm. The DCH represents the traditional dedicated resource model for circuit-switched and early packet-switched services in 3G networks.
Purpose & Motivation
The DCH was created to provide a dedicated, reliable, and QoS-managed communication path for individual users in UMTS networks, addressing the limitations of GSM's channel structure. In GSM, traffic channels were primarily designed for constant-rate voice, with limited flexibility for data. The transition to 3G aimed to support a wide range of services with varying bandwidth and quality requirements, from voice to video and internet access. The DCH was the core mechanism to enable this by offering a dedicated, bidirectional channel that could be dynamically configured in terms of bit rate, coding, and power control, tailored to the specific service's needs.
It solved the problem of efficiently supporting both circuit-switched services (like traditional telephony) and packet-switched services (like web browsing) within a single radio access technology. For circuit-switched voice, the DCH provided a constant or adaptive bit rate connection with low delay and controlled error rates, essential for toll-quality speech. For packet data, it allowed variable rates and discontinuous transmission, optimizing resource usage when data was bursty. The DCH also facilitated advanced radio features like soft handover and fast power control, which were critical for improving coverage, capacity, and link reliability in CDMA-based UMTS networks.
Historically, the DCH represented a significant evolution from the shared or common channels used for initial access and broadcast. It enabled the network to allocate exclusive resources to a user for the duration of a call or session, ensuring performance isolation and predictable service. This was particularly important for real-time applications before the widespread adoption of all-IP architectures and sophisticated packet scheduling. The DCH's design reflected the 3GPP vision of a unified network capable of delivering multimedia services, bridging the gap between 2G's voice-centric model and the data-centric future.
Key Features
- Point-to-point bidirectional transport channel dedicated to a single UE
- Variable bit rate support with dynamic Transport Format Combination (TFC) selection
- Mapping to Dedicated Physical Channel (DPCH) with dedicated channelization and scrambling codes
- Support for soft handover, enabling simultaneous connection to multiple Node Bs
- Integrated fast closed-loop power control and outer loop power control for link adaptation
- Carries both user plane data and dedicated control information (e.g., measurement reports)
Evolution Across Releases
Introduced as the fundamental dedicated transport channel for UMTS, supporting circuit-switched voice and packet data services. It featured variable bit rates, dedicated physical channel mapping (DPCH), and fast power control. Initial capabilities included support for both FDD and TDD modes, soft handover, and integration with the RRC protocol for connection management.
Defining Specifications
| Specification | Title |
|---|---|
| TS 21.905 | 3GPP TS 21.905 |
| TS 25.141 | 3GPP TS 25.141 |
| TS 25.171 | 3GPP TS 25.171 |
| TS 25.201 | 3GPP TS 25.201 |
| TS 25.202 | 3GPP TS 25.202 |
| TS 25.211 | 3GPP TS 25.211 |
| TS 25.212 | 3GPP TS 25.212 |
| TS 25.213 | 3GPP TS 25.213 |
| TS 25.214 | 3GPP TS 25.214 |
| TS 25.221 | 3GPP TS 25.221 |
| TS 25.222 | 3GPP TS 25.222 |
| TS 25.225 | 3GPP TS 25.225 |
| TS 25.301 | 3GPP TS 25.301 |
| TS 25.302 | 3GPP TS 25.302 |
| TS 25.303 | 3GPP TS 25.303 |
| TS 25.321 | 3GPP TS 25.321 |
| TS 25.322 | 3GPP TS 25.322 |
| TS 25.331 | 3GPP TS 25.331 |
| TS 25.401 | 3GPP TS 25.401 |
| TS 25.402 | 3GPP TS 25.402 |
| TS 25.413 | 3GPP TS 25.413 |
| TS 25.420 | 3GPP TS 25.420 |
| TS 25.425 | 3GPP TS 25.425 |
| TS 25.426 | 3GPP TS 25.426 |
| TS 25.427 | 3GPP TS 25.427 |
| TS 25.430 | 3GPP TS 25.430 |
| TS 25.433 | 3GPP TS 25.433 |
| TS 25.435 | 3GPP TS 25.435 |
| TS 25.702 | 3GPP TS 25.702 |
| TS 25.903 | 3GPP TS 25.903 |
| TS 25.914 | 3GPP TS 25.914 |
| TS 25.927 | 3GPP TS 25.927 |
| TS 25.929 | 3GPP TS 25.929 |
| TS 25.931 | 3GPP TS 25.931 |
| TS 26.935 | 3GPP TS 26.935 |
| TS 26.937 | 3GPP TS 26.937 |
| TS 34.114 | 3GPP TR 34.114 |
| TS 37.320 | 3GPP TR 37.320 |
| TS 37.544 | 3GPP TR 37.544 |
| TS 37.901 | 3GPP TR 37.901 |
| TS 43.051 | 3GPP TR 43.051 |
| TS 44.160 | 3GPP TR 44.160 |
| TS 45.902 | 3GPP TR 45.902 |