Browser Media Segment Playback via JavaScript Mediator
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
HTML5 standard does not natively support HTTP adaptive streaming protocols, requiring browser plugins or additional functionality for playing media items with multiple segments, which is not universally available across different browser applications.
Innovation Solution
A method that allows playing multiple media segments in a browser application without plugins, using a content distribution network to manage media segments, selecting segments based on quality and bandwidth requirements, and constructing playable files using JavaScript, supporting protocols like HLS, MSS, DASH, or HDS without external plugins by utilizing HTTP GET requests and manifest files.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of time
If HTTP adaptive streaming protocols (HLS, MSS, DASH, HDS) are used to enable progressive media playback, then playback starts before complete download and network traffic is optimized, but browser compatibility is lost because HTML5 does not natively support these protocols
Solution Approach 1:
The patent introduces a mediator component that translates between HTTP adaptive streaming protocols and HTML5 native media playback. This intermediary layer enables browser-compatible playback by converting protocol-specific segment requests into standard HTML5 media element operations, resolving the contradiction between protocol functionality and browser compatibility
Solution Approach 2:
The patent creates a universal playback mechanism that works across multiple browser applications by implementing a common interface layer. This multi-functional approach allows the same HTML5 media element to handle various HTTP adaptive streaming protocols uniformly, achieving both protocol support and broad browser compatibility
2Reliability
If browser plugins are implemented to support HTTP adaptive streaming protocols, then protocol-specific playback functionality is achieved, but device complexity increases and universal availability across browsers is reduced
Solution Approach 1:
The patent extracts the protocol-specific processing logic from the browser core and isolates it into a separate, optional module. This extraction allows standard HTML5 playback to remain simple while providing protocol support only where needed, reducing overall browser complexity while maintaining functionality
Solution Approach 2:
The patent implements self-service mechanisms where the media playback system automatically detects and handles protocol requirements without requiring external plugins. The system serves its own protocol translation needs through integrated functionality, eliminating the need for separate browser add-ons
3Productivity
If separate browser functionality is developed for each HTTP adaptive streaming protocol, then protocol-specific optimization is achieved, but the number of required components increases and maintenance complexity grows
Solution Approach 1:
The patent merges multiple protocol handling capabilities into a single unified module. By combining HLS, MSS, DASH, and HDS protocol support within one integrated component, the system achieves protocol-specific optimization without multiplying the number of separate browser functionalities, thereby improving productivity while controlling complexity
Data Source
AI summary
Media comprising media segments is played in a browser application. The segments comprise video and/or audio payload data encoded by a codec supported by this browser application. To play the media, several steps are performed by the browser application. First, a first subset of media segments of the media is obtained from a server. Then, a first media file is constructed comprising the video and/or audio payload data of the first subset of media segments. In a third step, a second subset of media segments of the media is obtained from the content distribution network whereas the second subset is consequent in time to the first subset. Then, the second media file is constructed comprising the video and/or audio payload data of the second subset of media segments. Finally, the first and second media files are played in the browser according to the codec.