Description
The Dedicated Traffic Channel (DTCH) is a fundamental logical channel in the 3GPP radio protocol architecture, defined for both UMTS (3G) and LTE (4G) systems. A logical channel is defined by the type of information it carries. The DTCH is a traffic channel, meaning its sole purpose is to transport user-plane data. It is 'dedicated' because it is allocated to a specific User Equipment (UE) for the duration of a data session, establishing a point-to-point link between the UE and the network. This contrasts with common channels, which are shared by all UEs in a cell. The DTCH carries all application-layer data, such as web pages, video streams, voice over IP packets, or file downloads, for that particular UE.
In the protocol stack, the DTCH exists at the Medium Access Control (MAC) layer. It is mapped onto transport channels, which are then mapped onto physical channels. This mapping is configurable and is a key part of radio resource management. In UMTS, a DTCH can be mapped onto dedicated transport channels like the Dedicated Channel (DCH) or onto shared channels like the High-Speed Downlink Shared Channel (HS-DSCH) in HSPA. In LTE, which is entirely shared-channel based in the downlink, the DTCH is always mapped onto the shared transport channels: the Downlink Shared Channel (DL-SCH) and the Uplink Shared Channel (UL-SCH). The Radio Resource Control (RRC) layer is responsible for establishing, reconfiguring, and releasing the radio bearers that utilize the DTCH, based on the QoS requirements of the service requested by the UE.
The operation of a DTCH is tied to the establishment of a radio bearer. When a UE initiates a data session (e.g., activates a PDP context in UMTS or a PDN connection in LTE), the core network requests the RAN to set up a radio bearer with specific QoS parameters (e.g., guaranteed bit rate, priority, delay budget). The RAN configures the necessary resources, which includes creating a DTCH logical channel for that bearer. The MAC layer then uses scheduling algorithms to multiplex data from multiple DTCHs (and other logical channels) from different UEs onto the shared physical radio resources. On the downlink, the scheduler in the eNodeB (LTE) or NodeB (UMTS) decides which UE's DTCH data to transmit in each transmission time interval. On the uplink, the UE transmits according to grants received from the network. The DTCH is identified by a Logical Channel ID (LCID) within the MAC layer, allowing the receiver to correctly demultiplex the data streams.
The DTCH's configuration directly defines the user's experience. Parameters like the modulation and coding scheme, the amount of scheduled resources, and the Hybrid ARQ (HARQ) processes are all managed to meet the QoS targets associated with the DTCH's radio bearer. For services requiring low latency (e.g., gaming), the scheduler will prioritize granting frequent, small transmission opportunities for the UE's DTCH. For high-throughput services (e.g., video streaming), it will allocate larger resource blocks. The DTCH is, therefore, not just a passive pipe but a dynamically managed resource that is central to the radio network's ability to deliver diverse services efficiently and with the required quality.
Purpose & Motivation
The DTCH exists to provide a structured, QoS-aware mechanism for delivering user data over the radio interface in a cellular network. Before standardized logical channels like DTCH, data transport mechanisms were less flexible and integrated. The creation of the DTCH addressed the need for efficient, dedicated resource allocation for individual users in a shared medium, which is essential for supporting circuit-switched-like guaranteed services as well as bursty packet data services within a unified architecture.
Its development was motivated by the evolution from pure voice-centric 2G networks to multimedia-capable 3G (UMTS) and 4G (LTE) networks. In GSM, user traffic for a call used a dedicated physical channel (TCH), but the concept was more rigidly tied to the physical layer. The DTCH, as a logical channel, introduced a layer of abstraction. This abstraction separates the service requirement (carry user data for UE X with QoS Y) from the physical implementation (which specific codes, timeslots, or resource blocks to use). This separation is crucial for advanced radio techniques like dynamic channel allocation, shared channel operation (HSPA, LTE), and sophisticated packet scheduling that adapts to rapidly changing radio conditions and traffic demands.
The DTCH solves the problem of multiplexing multiple data flows with different requirements onto the same physical radio resources. By having a dedicated logical channel per radio bearer per UE, the network can apply distinct QoS handling, priority, and error correction mechanisms to each data stream. For example, a VoIP call and a background file download for the same UE would be carried on separate DTCHs with different configurations, allowing the network to prioritize the delay-sensitive VoIP packets. This granular control is fundamental to delivering the mix of services promised by 3G and 4G networks, from voice and video conferencing to web browsing and machine-type communication, all over a common packet-switched infrastructure.
Key Features
- Point-to-point logical channel dedicated to a single User Equipment (UE)
- Carries all user-plane data (IP packets) for a specific radio bearer
- Exists in the Medium Access Control (MAC) layer of the protocol stack
- Mapped onto transport channels (e.g., DCH in UMTS, DL-SCH/UL-SCH in LTE)
- Configuration is defined by Radio Resource Control (RRC) based on QoS requirements
- Identified by a Logical Channel ID (LCID) for multiplexing/demultiplexing
Evolution Across Releases
DTCH was introduced as part of the UMTS Release 99 radio interface architecture. It was defined as a dedicated logical channel for carrying user data, mapped primarily onto the Dedicated Transport Channel (DCH). This established the fundamental model of QoS-aware radio bearers for packet-switched services in 3G.
Defining Specifications
| Specification | Title |
|---|---|
| TS 21.905 | 3GPP TS 21.905 |
| TS 23.146 | 3GPP TS 23.146 |
| TS 25.301 | 3GPP TS 25.301 |
| TS 25.302 | 3GPP TS 25.302 |
| TS 25.321 | 3GPP TS 25.321 |
| TS 25.322 | 3GPP TS 25.322 |
| TS 25.331 | 3GPP TS 25.331 |
| TS 25.912 | 3GPP TS 25.912 |
| TS 25.914 | 3GPP TS 25.914 |
| TS 25.931 | 3GPP TS 25.931 |
| TS 26.902 | 3GPP TS 26.902 |
| TS 26.935 | 3GPP TS 26.935 |
| TS 34.114 | 3GPP TR 34.114 |
| TS 36.133 | 3GPP TR 36.133 |
| TS 36.300 | 3GPP TR 36.300 |
| TS 36.302 | 3GPP TR 36.302 |
| TS 36.314 | 3GPP TR 36.314 |
| TS 36.322 | 3GPP TR 36.322 |
| TS 36.331 | 3GPP TR 36.331 |
| TS 37.544 | 3GPP TR 37.544 |
| TS 38.331 | 3GPP TR 38.331 |