Description
The Data Description Indicator (DDI) is a fundamental component within the Radio Resource Control (RRC) protocol layer, specifically detailed in specifications like 25.331. It functions as a structured information element embedded within RRC messages, such as Radio Bearer Setup, Reconfiguration, and Release messages. The DDI's primary role is to convey a detailed profile of a data flow that the network intends to establish, modify, or terminate for a User Equipment (UE). This profile includes a comprehensive set of attributes that define how data should be treated across the air interface and within the UE's protocol stack.
Architecturally, the DDI is generated by the Core Network, typically based on the QoS profile negotiated during a PDP Context Activation or similar session establishment procedure. This information is passed to the Radio Access Network (RAN), specifically the Radio Network Controller (RNC) in UMTS, via the Iu interface. The RNC then incorporates the relevant parameters from this profile into the DDI structure within the RRC message sent to the UE. The UE's RRC layer parses the DDI to configure its lower layers, such as the Packet Data Convergence Protocol (PDCP), Radio Link Control (RLC), and Medium Access Control (MAC), accordingly. This configuration ensures the logical channels, RLC modes, and scheduling priorities are aligned with the service's needs.
Key components described by a DDI typically include the Traffic Class (e.g., Conversational, Streaming, Interactive, Background), key QoS parameters like Guaranteed Bit Rate (GBR), Maximum Bit Rate (MBR), Transfer Delay, and Traffic Handling Priority (THP). It also specifies the mapping between the radio bearer and the logical channel, defining whether the bearer is for user plane data or control plane signaling. The DDI essentially acts as a translation mechanism, converting the abstract service requirements from the core network into concrete, actionable configuration commands for the radio interface protocols. Its accurate interpretation by both the RAN and the UE is vital for ensuring that the end-to-end data path supports the intended application performance, whether it be a voice call, video stream, or web browsing session.
Purpose & Motivation
The DDI was introduced to solve the critical problem of dynamically and efficiently communicating complex data service requirements from the network core to the radio interface and the mobile device. Prior to standardized QoS signaling mechanisms, managing diverse data services with varying latency, reliability, and bandwidth needs was challenging. The DDI provides a structured, unambiguous way to describe these requirements, enabling the RAN to allocate appropriate radio resources (like spreading codes, power, and timeslots) and configure protocol layers optimally for each specific data flow.
Its creation was motivated by the evolution from circuit-switched voice-centric networks (2G) to packet-switched, data-capable networks (3G/UMTS). This shift introduced a multitude of new services—from web browsing to video telephony—each with distinct QoS demands. A simple "best-effort" channel was insufficient. The DDI, as part of the RRC protocol, became the essential vehicle for QoS negotiation and enforcement over the air interface. It addressed the limitation of having fixed, pre-defined bearer types by allowing for a flexible and detailed description of data characteristics on a per-session basis, which was fundamental for enabling differentiated services and efficient radio resource utilization in 3GPP networks.
Key Features
- Encapsulates detailed QoS parameters for a data flow
- Enables dynamic radio bearer establishment and reconfiguration
- Facilitates mapping between service requirements and logical channel configuration
- Carried within RRC signaling messages (e.g., Radio Bearer Setup)
- Supports multiple traffic classes (Conversational, Streaming, Interactive, Background)
- Allows network-controlled prioritization and resource allocation
Evolution Across Releases
Introduced as a core element of the RRC protocol in the first UMTS release. It provided the initial framework for describing data flows with parameters like Traffic Class, RLC mode, and logical channel identity, enabling basic QoS differentiation for early 3G packet services.
Defining Specifications
| Specification | Title |
|---|---|
| TS 21.801 | 3GPP TS 21.801 |
| TS 21.905 | 3GPP TS 21.905 |
| TS 22.975 | 3GPP TS 22.975 |
| TS 25.331 | 3GPP TS 25.331 |