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.
Classification
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (31 CRs across 5 releases). Complements the general historical overview above with the evidence-based evolution of this function.
In Release 15, specific enhancements for the DTCH function included clarifications on dedicated serving cell configuration during RRC Re-establishment and dedicated priority handling for state transitions from RRC_INACTIVE to RRC_IDLE. Furthermore, the release introduced new UE-specific channel bandwidth signaling and validation procedures, alongside support for wider channel bandwidths such as 70MHz. These updates provided more precise control and configuration of the Dedicated Traffic Channel for individual user equipment.
- UE specific channel bandwidth signaling TS 38.331CR0791
- Clarification to channel bandwidth signalling TS 38.331CR0812
- Clarification on dedicated serving cell configuration in Re-establishment TS 38.331CR0823
- Clarification of dedicated priority handling from RRC_INACTIVE to RRC_IDLE TS 38.331CR1106
- Channel Bandwidth validation upon SIB1 acquisition TS 38.331CR1220
- CR to 38.331 on support of 70MHz channel bandwidth TS 38.331CR1410
+ 3 more changes
In Release 16, the DTCH function itself was not directly modified, but its reliable transport over new network architectures was enhanced. Specifically, the release introduced procedures for transmission suspension and management of Backhaul (BH) RLC channels upon an IAB-MT failure, ensuring dedicated traffic continuity. These corrections and new management procedures for the BH RLC channel provided a more robust transport mechanism for DTCH within integrated access and backhaul (IAB) networks.
- Correction on the configuration of subframe #0 and #5 for MCH in MBMS dedicated cell TS 36.331CR4259
- CR to 36.331 on F1-C traffic over LTE TS 36.331CR4379
- 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
+ 2 more changes
In Release 17, specific corrections were made to the RRC layer procedures governing the DTCH. These included a correction to support the autonomous change of UE channel bandwidth during the RACH procedure, directly impacting dedicated channel configuration.
- RRC Correction on including GNSS validity duration and dedicated SIB31 TS 36.331CR4952
- 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
- Correction to support autonomous change of UE channel bandwidth during RACH TS 38.331CR4395
In Release 18, specific changes to the DTCH function are not directly detailed in the provided grounding context or Change Request titles. The listed corrections and new capabilities primarily concern other channels and UE capabilities, such as enhancements for dedicated spectrum, channel raster, and PC5 RLC handling, rather than introducing new features for the Dedicated Traffic Channel itself. Therefore, based solely on the given materials, there is no explicitly stated new feature or modification for the DTCH in this release.
- Introduction of NR support for dedicated spectrum less than 5MHz for FR1 TS 36.331CR4983
- 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
- Correction to PC5 RLC channel handling TS 38.331CR5270
- Correction on NW restriction for dedicated SL-PRS resource pool TS 38.331CR5104
+ 2 more changes
In Release 19, the primary update for the Dedicated Traffic Channel (DTCH) function was the introduction of a new 7MHz channel bandwidth option. This change specifically defines a new, wider RF carrier configuration for the channel, measured in MHz, which serves as a direct reference for updated transmitter and receiver requirements. No other specific DTCH functional changes are indicated by the provided materials.
Explore further
Broader topics and technologies where DTCH plays a role.
Defining Specifications
3GPP specifications that define or reference DTCH, 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 23.146 vj00 | 3G Facsimile Group 3 Technical Realization | 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.914 vj00 | 3G UE Radio Performance Test Methods | 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 |
| TR 26.935 vj00 | Speech Codec Performance for Packet Switched Multimedia | Rel-19 |
| TS 34.114 vc20 | Radiated Performance Test Procedure for UE/MS | Rel-12 |
| 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 |
| TS 37.544 vg70 | UE Radiated Performance Test Procedures | Rel-16 |
| TS 38.331 vj00 | NR Radio Resource Control (RRC) Protocol Specification | Rel-19 |