HTTP Server Partial Segment Delivery for DASH Streaming
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current HTTP protocols do not support the delivery of incomplete versions of files or segments to clients, leading to playback interruptions and reduced functionality in media streaming applications, as they only provide full responses or error messages when partial segments are requested.
Innovation Solution
Implementing a mechanism in HTTP servers to deliver incomplete segments to DASH clients by determining client capabilities and sending partial segments with access position indications, using extension headers and specific response codes to facilitate partial content delivery.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If current HTTP protocols only provide full responses or error messages for segment requests, then protocol simplicity and server implementation ease are maintained, but media playback continuity and user experience deteriorate due to interruptions when partial segments are received
Solution Approach 1:
The patent segments the HTTP response into two distinct parts: a status code indicating partial content availability, and an extension header providing metadata about the incomplete segment (such as expected size, received size, or recovery information). This allows the protocol to convey partial content information without fundamentally changing the HTTP framework, thereby improving playback continuity while minimizing protocol complexity increases
Solution Approach 2:
The extension header acts as an intermediary mechanism that bridges the gap between simple HTTP protocols and complex partial content delivery requirements. It carries additional information about incomplete segments without requiring changes to the core HTTP protocol structure, enabling enhanced functionality while maintaining protocol simplicity
2Reliability
If servers drop partial segments to maintain protocol simplicity, then HTTP protocol implementation remains simple, but media delivery reliability and playback quality worsen due to increased interruptions
Solution Approach 1:
The server performs preliminary assessment of the received partial segment data before responding to the client. It determines whether the partial content is sufficient to be useful, identifies recovery options, and prepares appropriate status codes and extension headers in advance. This preliminary processing enables reliable segment delivery without requiring complex real-time decision-making during operation
Solution Approach 2:
The extension header provides feedback information to the client about the state of the received segment, including details about what was received, what is missing, and how to proceed. This feedback mechanism enables the client to make informed decisions about playback, buffering, or requesting alternative content, thereby improving delivery reliability while keeping server operations straightforward
3Adaptability or versatility
If servers send incomplete segments without indication headers, then response message simplicity is maintained, but client ability to process and utilize partial content deteriorates
Solution Approach 1:
The extension header effectively 'colors' or tags the response message with additional information about the segment's completeness status. Just as color changes can indicate different states or properties, the extension header provides visual (informational) cues to the client about whether the segment is complete, partially received, or corrupted, enabling the client to adapt its processing accordingly without losing critical information
Solution Approach 2:
The extension header introduces new parameters that describe the segment's completeness characteristics (such as Content-Range, X-Partial-Content, or similar indicators). These parameter changes provide the client with quantitative and qualitative information about the partial content, enabling adaptive processing while preserving all necessary information about the segment state
Data Source
Figure 1
Figure 2A
Figure 2B
AI summary
Systems, methods, and devices of the various embodiments enable HTTP servers, such as HTTP servers providing segments to DASH clients according to the various embodiments, to pass incomplete versions of segments in response to segment requests from the DASH clients. The various embodiments may enable clients, such as DASH clients, to parse incomplete versions of segments.