DANE

DASH Aware Network Element

Services
Introduced in Rel-12
A network element that is aware of Dynamic Adaptive Streaming over HTTP (DASH) operations to optimize media delivery. It monitors DASH client behavior and network conditions to improve Quality of Experience (QoE) by enabling network-assisted streaming optimizations. This is crucial for efficient video delivery in mobile networks.

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.

Key Features

  • MPD-aware traffic analysis to identify and understand DASH streaming sessions
  • Correlation of client adaptation behavior with real-time network condition measurements
  • Ability to trigger policy controls (e.g., via PCRF) to allocate dedicated bearer resources for streaming
  • Support for network-assisted rate adaptation guidance to DASH clients
  • QoE metrics collection and monitoring for DASH services (e.g., rebuffering ratio, average bitrate)
  • Integration points with core network functions like TDF, PCRF, and user plane gateways

Evolution Across Releases

Rel-12 Initial

Introduced the initial DANE concept and architecture. Defined DANE as a logical function capable of being aware of DASH sessions, monitoring client requests and network conditions, and interacting with the PCRF for policy enforcement to improve streaming QoE. Specified the foundational use cases for network-assisted streaming.

Enhanced DANE capabilities with a focus on QoE reporting and more detailed metrics collection. Defined standardized QoE measurements for DASH (e.g., initial playback delay, stalling events) that DANE could collect or derive, enabling more sophisticated analytics and optimization triggers.

Strengthened integration with the Policy and Charging Control (PCC) architecture. Refined the signaling flows between DANE, the Traffic Detection Function (TDF), and the PCRF. Worked on enabling more dynamic policy adjustments based on real-time QoE feedback from the DANE.

Aligned DANE concepts with the 5G System (5GS) architecture, considering its implementation in the context of the Session Management Function (SMF), User Plane Function (UPF), and the 5G Policy Control Function (PCF). Explored DANE functionality for edge computing scenarios (MEC).

Further integration into 5G, including support for network slicing. Enhanced capabilities for optimized media delivery in edge computing environments, allowing DANE logic to be deployed closer to the user at the network edge for lower latency optimizations.

Extended DANE applicability to new media types and streaming enhancements, such as support for Low-Latency HLS (LL-HLS) and CMAF. Continued work on edge deployment optimizations and integration with analytics frameworks like the Network Data Analytics Function (NWDAF).

Investigated AI/ML-based enhancements for DANE functionality, enabling predictive QoE optimization and more intelligent adaptation guidance. Explored tighter coupling with the NWDAF for advanced analytics-driven media delivery control.

Ongoing studies on the evolution of media-aware networks, including DANE, for immersive media services (e.g., extended reality - XR). Focus on dynamic and efficient resource utilization for variable bitrate media with stringent latency and reliability requirements.

Defining Specifications

SpecificationTitle
TS 23.795 3GPP TS 23.795
TS 26.233 3GPP TS 26.233
TS 26.247 3GPP TS 26.247
TS 26.347 3GPP TS 26.347
TS 26.512 3GPP TS 26.512
TS 26.804 3GPP TS 26.804
TS 26.852 3GPP TS 26.852
TS 26.891 3GPP TS 26.891
TS 26.946 3GPP TS 26.946
TS 26.957 3GPP TS 26.957