HTTP Server Handling Incomplete Files for Media Playback
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current File Delivery Over Unidirectional Transport (FLUTE) interfaces and Hypertext Transfer Protocol (HTTP) 1.1 are unable to pass incomplete or corrupted files to clients, limiting the functionality of applications and clients that can recover and playback partially received files, leading to reduced user experience due to discarded incomplete files and lack of error recovery mechanisms.
Innovation Solution
Enhanced FLUTE and HTTP servers are enabled to deliver incomplete versions of files by assigning modified URLs/URIs for incomplete files, allowing clients to handle and utilize partial data, and indicating the status of responses to support error recovery and playback of media content.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If current FLUTE receivers discard incomplete files, then data integrity is maintained, but media playback continuity is reduced
Solution Approach 1:
The patent changes the parameter of file completeness from binary (complete/incomplete) to a spectrum of completeness levels. The FLUTE receiver now passes files with varying degrees of completeness to applications, allowing media players to playback content even when files are partially incomplete, thus maintaining playback continuity while managing data integrity through adaptive error correction.
Solution Approach 2:
Instead of requiring complete files for playback, the patent enables partial action by allowing media players to utilize and playback incomplete files. The system accepts less than perfect data (incomplete files) and still achieves the primary function of media playback, reducing stalls and improving continuity.
2Measurement precision
If HTTP servers return error codes for incomplete files, then data accuracy is ensured, but client functionality for error recovery is reduced
Solution Approach 1:
The patent introduces an intermediary mechanism where the HTTP server includes detailed error information and file status data in the response along with the incomplete file content. This intermediary information layer enables the client to make informed decisions about error recovery strategies without sacrificing data accuracy, as the server precisely indicates what is incomplete and what is available.
Solution Approach 2:
The system implements feedback by providing the client with specific information about the incomplete file's status, including which portions are missing or corrupted. This feedback enables the client to request specific missing segments or apply targeted error correction, enhancing adaptability while maintaining data accuracy through informed recovery actions.
3Reliability
If FLUTE receivers deliver only complete files, then data reliability is maintained, but application functionality for partial file recovery is reduced
Solution Approach 1:
The patent applies dynamics by making the file delivery system adaptive rather than static. The FLUTE receiver dynamically assesses file completeness and delivers files with varying levels of completeness based on application capabilities and error correction potential. This dynamic approach maintains reliability for complete files while enabling partial recovery functionality when appropriate.
Solution Approach 2:
The enhanced FLUTE receiver achieves multi-functionality by serving both complete and incomplete files to different applications based on their capabilities. The system universally handles various file completeness states and adapts delivery strategies accordingly, enabling both traditional complete-file playback and new partial-file recovery scenarios through a single unified interface.
Data Source
AI summary
Embodiments enable HTTP servers to pass incomplete and/or corrupted files in response to file requests from clients. In the various embodiments, HTTP servers may be enabled to generate status codes identifying that an incomplete version of a file is being returned in response to a file request. In an embodiment, an HTTP server may be enabled to determine the ability of a client to handle incomplete versions of files.