HTTP Streaming MPD Update Frequency Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In HTTP streaming, clients face service interruptions during server migrations due to the need to frequently fetch updated Media Presentation Descriptions (MPDs), which can be burdensome and lead to missed updates, especially when network latency occurs, causing disruptions in live content streaming.
Innovation Solution
Implementing parameters such as maximumMPDFetchInterval, minimumUpdatePeriodMPD, and timeShiftBufferDepth in the MPD to manage the frequency of MPD updates and ensure seamless service migration by maintaining segment locations on both old and new servers for a specified duration, along with a guard interval to account for network latency, and using OMA DM Management Objects for push-based updates.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If clients frequently fetch updated MPDs to detect server migrations, then service continuity is improved, but network bandwidth is wasted and client processing overhead increases
Solution Approach 1:
The server performs preliminary action by proactively pushing MPD update notifications to clients before clients would naturally need to fetch updates. This is achieved through the OMA DM push mechanism where the server sends notifications containing version information, allowing clients to stay synchronized without frequent active fetching, thus conserving bandwidth while maintaining service continuity.
Solution Approach 2:
The system implements feedback through the notification mechanism where the server informs clients about MPD updates. The client receives push notifications with version information and can selectively fetch updated MPDs only when necessary, creating an efficient feedback loop that balances service continuity with resource conservation.
2Loss of energy
If clients wait for MPD updates between fetches to reduce bandwidth usage, then network bandwidth is conserved, but service interruptions occur during server migrations
Solution Approach 1:
The server performs preliminary action by proactively pushing MPD update notifications to clients before clients would naturally need to fetch updates. This is achieved through the OMA DM push mechanism where the server sends notifications containing version information, allowing clients to stay synchronized without frequent active fetching, thus conserving bandwidth while maintaining service continuity.
Solution Approach 2:
The system implements feedback through the notification mechanism where the server informs clients about MPD updates. The client receives push notifications with version information and can selectively fetch updated MPDs only when necessary, creating an efficient feedback loop that balances service continuity with resource conservation.
3Ease of operation
If clients fetch MPDs at fixed intervals, then client implementation is simplified, but updates may be missed during network latency or server migrations
Solution Approach 1:
The system implements feedback through the notification mechanism where the server informs clients about MPD updates. The client receives push notifications with version information and can selectively fetch updated MPDs only when necessary, creating an efficient feedback loop that balances service continuity with resource conservation.
Solution Approach 2:
The server performs preliminary action by proactively pushing MPD update notifications to clients before clients would naturally need to fetch updates. This is achieved through the OMA DM push mechanism where the server sends notifications containing version information, allowing clients to stay synchronized without frequent active fetching, thus conserving bandwidth while maintaining service continuity.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A client device and a server receive and send a presentation streamed via HTTP. The client device sends a content request and the server receives the content request. The client device receives and the server sends a first presentation description based on the content request, wherein the presentation description comprises a fetch interval. The client device requests or otherwise receives a second presentation description before a duration associated with the fetch interval is exceeded.