Coordinator Device for DASH Bottleneck Coordination
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Dynamic Adaptive Streaming over HTTP (DASH) lacks information about bottleneck resource constraints and rate-distortion trade-offs, leading to inefficient traffic coordination and suboptimal Quality of Experience (QoE) for video sessions, especially over wireless channels where HTTP transport misinterprets packet loss as congestion.
Innovation Solution
A resource allocation method using a coordinator device and user equipment (UE) that communicates through a communication interface to determine and adjust initial resource prices and requests, employing a marginal utility maximization scheme to optimize bandwidth allocation and alleviate bottlenecking, thereby maximizing QoE across multiple video sessions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If DASH uses HTTP transport protocol for media streaming, then ease of operation and compatibility are improved, but traffic coordination efficiency and QoE maximization deteriorate due to lack of bottleneck resource information
Solution Approach 1:
The patent introduces a coordinator entity that acts as an intermediary between multiple DASH clients and the network bottleneck. This coordinator collects bottleneck resource constraint information and rate-distortion trade-off data, then distributes this information to clients to enable coordinated traffic management. The coordinator resolves the contradiction by providing the missing information that HTTP/DASH lacks inherently, allowing efficient traffic coordination while maintaining HTTP compatibility.
Solution Approach 2:
The system implements feedback mechanisms where the coordinator continuously monitors bottleneck resource usage and QoE metrics, then adjusts resource allocation decisions based on this feedback. Clients report their playback status and network conditions to the coordinator, which uses this feedback to dynamically adjust resource pricing and allocation, enabling adaptive traffic coordination that maximizes overall QoE while maintaining HTTP transport simplicity.
2Adaptability or versatility
If DASH operates as a client-driven pull-based streaming solution, then adaptability is improved, but resource allocation efficiency deteriorates due to lack of bottleneck information
Solution Approach 1:
The coordinator serves as an intermediary that bridges client-driven adaptability with network-aware resource allocation. Clients maintain their adaptive bitrate selection capabilities, while the coordinator provides bottleneck information and coordinates resource allocation across multiple clients. This allows the system to preserve client adaptability while achieving network-efficient resource allocation that pure client-driven DASH cannot accomplish.
Solution Approach 2:
The system segments the resource allocation function between clients and the coordinator. Clients handle local adaptation decisions based on their playback buffers and device capabilities, while the coordinator handles network-wide resource allocation based on bottleneck constraints. This segmentation allows each component to operate independently in its optimal domain while achieving overall system efficiency.
3Reliability
If HTTP transport interprets packet loss as congestion, then reliability is improved by reducing transmitting window, but productivity deteriorates due to slow start and channel underutilization
Solution Approach 1:
The coordinator acts as an intermediary that decouples packet loss interpretation from automatic transmission window adjustment. Instead of relying on HTTP's conservative congestion control that misinterprets wireless packet loss, the coordinator receives explicit feedback about actual network conditions and bottleneck status, then provides informed resource allocation guidance to clients. This allows the system to maintain reliability while avoiding unnecessary transmission window reductions that would reduce channel utilization.
Solution Approach 2:
The patent replaces HTTP's mechanical congestion control mechanism (automatic window halving based on packet loss) with an information-based coordination mechanism. The coordinator substitutes the blind reactive response of HTTP congestion control with proactive resource allocation decisions based on actual bottleneck measurements and QoE requirements, enabling more efficient channel utilization without sacrificing reliability.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
Systems and methods for allocating bandwidth between a coordinator device and a user equipment (UE). In the system, the UE includes a communication interface configured to communicate with the coordinator device. The UE also includes a processor configured to receive an initial resource price from the coordinator device, determine an initial resource request, and transmit the initial resource request to the coordinator device.