Description
The Enhanced Dedicated Channel (E-DCH) is a transport channel defined in UMTS and enhanced as part of HSPA (High-Speed Packet Access), specifically for the uplink direction (from User Equipment to the network). It represents a major evolution from the original Dedicated Channel (DCH). The E-DCH is not a single physical resource but a logical channel mapped onto a set of dedicated physical channels: the E-DPDCH (Enhanced Dedicated Physical Data Channel) for carrying the actual user data and the E-DPCCH (Enhanced Dedicated Physical Control Channel) for carrying control information necessary for demodulation and decoding.
The operation of the E-DCH is centrally managed by a fast, NodeB-based scheduler, a key advancement over the RNC-controlled scheduling of the DCH. The UE sends scheduling requests (via the E-DPCCH) indicating its available power headroom and data buffer status. The NodeB, having a much faster reaction time than the RNC, grants transmission resources by sending absolute grants (setting a maximum allowed power offset) and relative grants (increment/decrement commands) to the UE. This allows for very fast adaptation to changing radio conditions and traffic demands, maximizing uplink capacity.
Furthermore, E-DCH employs physical layer Hybrid Automatic Repeat Request (HARQ) with multiple parallel stop-and-wait processes. This allows for rapid retransmissions at the physical layer between the UE and NodeB without involving higher layers, drastically reducing latency and improving reliability. Data is transmitted in 2 ms subframes (or optionally 10 ms), a much shorter Transmission Time Interval (TTI) than the 10/20/40/80 ms of the original DCH, enabling faster delivery and more granular scheduling. The combination of NodeB scheduling, fast HARQ, and short TTI is what enables the high peak data rates (theoretically up to 5.76 Mbps) and low latency characteristic of HSUPA.
Purpose & Motivation
The E-DCH was developed to solve the critical bottleneck of uplink performance in UMTS networks. While HSDPA (High-Speed Downlink Packet Access) dramatically improved downlink speeds, the uplink remained based on the relatively slow and inefficient DCH, which was controlled by the RNC with high latency. This asymmetry was unsuitable for emerging symmetric and interactive applications like video conferencing, large file uploads, real-time gaming, and social media with user-generated content.
Its creation was motivated by the need to bring HSPA's performance enhancements to the uplink, creating a balanced high-speed packet access system. E-DCH addressed the limitations of the DCH by moving fast scheduling decisions to the NodeB (reducing control loop latency), introducing physical layer HARQ for rapid error recovery, and shortening the TTI for more responsive transmission. This allowed mobile networks to offer a true broadband experience in both directions, enabling new services and improving the responsiveness of existing ones, which was crucial for maintaining competitiveness against other broadband technologies.
Key Features
- Foundation for High-Speed Uplink Packet Access (HSUPA).
- Features NodeB-controlled fast scheduling (as opposed to RNC scheduling).
- Employs physical-layer Hybrid ARQ (HARQ) with multiple parallel processes for low-latency retransmissions.
- Uses a short 2 ms Transmission Time Interval (TTI) for rapid data delivery.
- Utilizes dedicated physical channels: E-DPDCH for data and E-DPCCH for control signaling.
- Supports advanced techniques like 16QAM modulation (in later releases) and enhanced serving cell change procedures.
Evolution Across Releases
Initial introduction as the core of HSUPA. Defined the fundamental architecture with NodeB scheduling, 2ms TTI (and optional 10ms), physical layer HARQ, and the E-DPDCH/E-DPCCH physical channel structure. Supported QPSK modulation and introduced new MAC entities (MAC-e/es in UE and NodeB).
Defining Specifications
| Specification | Title |
|---|---|
| TS 25.101 | 3GPP TS 25.101 |
| TS 25.102 | 3GPP TS 25.102 |
| TS 25.133 | 3GPP TS 25.133 |
| 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.214 | 3GPP TS 25.214 |
| TS 25.221 | 3GPP TS 25.221 |
| TS 25.222 | 3GPP TS 25.222 |
| TS 25.224 | 3GPP TS 25.224 |
| TS 25.301 | 3GPP TS 25.301 |
| TS 25.302 | 3GPP TS 25.302 |
| TS 25.309 | 3GPP TS 25.309 |
| TS 25.319 | 3GPP TS 25.319 |
| TS 25.321 | 3GPP TS 25.321 |
| TS 25.331 | 3GPP TS 25.331 |
| TS 25.401 | 3GPP TS 25.401 |
| TS 25.420 | 3GPP TS 25.420 |
| TS 25.423 | 3GPP TS 25.423 |
| 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.706 | 3GPP TS 25.706 |
| TS 25.800 | 3GPP TS 25.800 |
| TS 25.823 | 3GPP TS 25.823 |
| TS 25.874 | 3GPP TS 25.874 |
| TS 25.903 | 3GPP TS 25.903 |
| TS 25.927 | 3GPP TS 25.927 |
| TS 25.929 | 3GPP TS 25.929 |
| TS 25.931 | 3GPP TS 25.931 |
| TS 32.836 | 3GPP TR 32.836 |
| TS 37.320 | 3GPP TR 37.320 |