Description
The DASH Aware Network Element (DANE) is a functional entity within the 3GPP network architecture specifically designed to enhance the delivery of media content using MPEG-DASH (Dynamic Adaptive Streaming over HTTP). Unlike traditional network elements that treat all HTTP traffic equally, DANE possesses intelligence about DASH-specific protocols, client behaviors, and adaptation logic. It operates as an intermediary between DASH clients and content servers, actively monitoring and potentially influencing the streaming session to maintain optimal Quality of Experience (QoE) for the end user.
Architecturally, DANE can be implemented as a standalone network function or integrated into existing nodes like the Traffic Detection Function (TDF), Policy and Charging Rules Function (PCRF), or within the user plane path (e.g., as part of a User Plane Function (UPF) enhancement). Its core operation involves analyzing HTTP traffic to identify DASH sessions, typically by inspecting HTTP headers and the Media Presentation Description (MPD) file—the manifest that describes the available media segments, their bitrates, resolutions, and other characteristics. By parsing the MPD, DANE understands the available adaptation set and the client's potential choices.
Key to DANE's functionality is its ability to gather and correlate two primary information streams: network conditions and client behavior. It monitors real-time network metrics such as available bandwidth, latency, and packet loss on the bearer serving the DASH client. Simultaneously, it observes the client's requests for media segments, noting the selected bitrate, resolution, and the timing of these requests. By combining this knowledge, DANE can detect suboptimal client decisions, such as a client selecting a high bitrate when network congestion is imminent or sticking with a low bitrate despite abundant available bandwidth.
Based on its analysis, DANE can initiate various optimization actions. These are often facilitated through interfaces with policy control (e.g., Rx interface) or directly within the user plane. For example, DANE can trigger network policies to allocate guaranteed bitrate (GBR) resources for a streaming session during critical playback periods to prevent rebuffering. It can also provide network assistance information to the client, either implicitly by shaping traffic or explicitly via in-band signaling or enhanced MPDs, to guide the client's adaptation logic towards a choice that maximizes QoE given the current network state. This transforms the streaming process from a purely client-driven, reactive adaptation into a network-assisted, more predictive optimization loop.
Purpose & Motivation
DANE was created to address the fundamental challenges of delivering high-quality video streaming over mobile networks, where bandwidth is variable and shared among many users. Prior to DANE, DASH adaptation was entirely client-driven (client-based adaptation). The client would estimate available bandwidth based on its own observations (like segment download times) and select an appropriate bitrate from the MPD. This approach has significant limitations: client estimates can be inaccurate due to cross-traffic, the client has no visibility into broader network congestion or radio conditions, and its decisions can lead to instability (oscillating bitrates), inefficient use of network resources, or poor QoE (frequent rebuffering or low video quality).
The motivation for DANE stemmed from the operator's need to regain some control and insight into the dominant type of traffic on their networks—video. Operators possess holistic network knowledge that individual clients lack. DANE enables a shift towards network-assisted streaming, where the network provides guidance or enforces conditions to improve overall efficiency and user satisfaction. This is particularly important in mobile environments where radio resources are scarce and the cost of inefficient streaming (in terms of both user experience and network capacity) is high.
Historically, its introduction in Release 12 was part of 3GPP's broader focus on service-aware networks and QoE optimization. It represented a move beyond simple traffic prioritization (Deep Packet Inspection) to true application-layer awareness and cooperation. By solving the problem of the client-network information asymmetry, DANE allows for more stable streaming sessions, better utilization of network resources during congestion, and ultimately a more consistent and higher-quality video experience for subscribers, which is a key competitive differentiator for mobile operators.
Classification
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (2 CRs across 2 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Studied in Rel-12, normative work from Rel-16.
In Release 16, the DANE function was introduced specifically for V2X applications, where the VAE client and VAE server act as a DASH Client and a DANE server, respectively. This enables network assistance procedures where the client can request a recommended bitrate from the DANE server to enhance QoE. Furthermore, the capability was expanded to support hybrid HLS/DASH services alongside pure DASH services.
- Support of HLS and hybrid HLS/DASH services TS 26.347CR0008
In Release 17, the enhancements for the DASH Aware Network Element (DANE) function focused on refining its role within V2X applications, specifically for network assistance to enhance QoE. The corrections targeted the DASH quality metric and the configuration and reporting of QoE, as detailed in the procedures between the VAE client (acting as a DASH Client) and the VAE server (acting as a DANE server). This included the network assistance request procedure where the client provides a video file index and available bitrates, and the DANE server responds with a recommended bitrate.
- Corrections to DASH quality metric and QoE configuration and reporting TS 26.247CR0178
Explore further
Broader topics and technologies where DANE plays a role.
Defining Specifications
3GPP specifications that define or reference DANE, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.795 vg10 | V2X Application Architecture Study | Rel-16 |
| TS 26.233 vf00 | 3GPP Packet-Switched Streaming Service (PSS) | Rel-15 |
| TS 26.247 vj00 | 3GPP Progressive Download & DASH over HTTP | Rel-19 |
| TS 26.347 vj00 | MBMS Transport Protocol and API (TRAPI) | Rel-19 |
| TS 26.512 vj10 | 5G Media Streaming Protocols & APIs | Rel-19 |
| TS 26.804 vj10 | 5G Media Streaming Extensions Study | Rel-19 |
| TS 26.852 ve20 | MBMS user service profiles, APIs and transport enabler study | Rel-14 |
| TS 26.891 vg00 | Media Distribution Services in 5G System | Rel-16 |
| TR 26.946 vj00 | MBMS User Services Overview | Rel-19 |
| TR 26.957 vj00 | Evaluation of MPEG DASH SAND for 3GPP | Rel-19 |