HTTP Streaming via Compressed Playlist Segments
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current streaming services require specialized servers and skills, leading to high costs and limited content availability, especially in large-scale deployments, as they typically rely on dedicated streaming protocols.
Innovation Solution
The use of non-streaming protocols like HTTP for streaming, where media data is segmented into multiple files and a playlist file with URIs directs clients to these files, enabling near real-time streaming without the need for specialized servers, and allowing for dynamic updates and bit rate switching.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If specialized streaming servers and protocols are used, then streaming reliability is improved, but device complexity and cost increase
Solution Approach 1:
The patent makes standard HTTP web servers perform the specialized function of streaming content delivery by segmenting media into sequential segments and using playlist files (M3U8) with URL lists to direct clients through the segments. This allows ordinary web servers to handle streaming without requiring dedicated streaming infrastructure, resolving the contradiction between reliability and device complexity.
Solution Approach 2:
The media content is divided into multiple sequential segments that can be delivered independently through standard HTTP protocols. Each segment is a separate file that can be requested and downloaded individually, allowing the streaming system to use conventional web server infrastructure while maintaining reliable content delivery through the segmented approach.
2Productivity
If specialized streaming servers are deployed at large scale, then streaming capability is improved, but cost increases
Solution Approach 1:
By enabling standard web servers to perform streaming functions through segment-based delivery and playlist management, the patent eliminates the need for expensive specialized streaming server infrastructure. Organizations can leverage existing web server deployments to provide streaming capabilities, dramatically reducing deployment costs while maintaining streaming functionality at scale.
3Speed
If dedicated streaming protocols are used, then streaming performance is improved, but adaptability decreases
Solution Approach 1:
The patent uses standard HTTP protocols and conventional web server infrastructure to deliver streaming content, making the system highly adaptable and compatible with existing web infrastructure. The segment-based approach with playlist files allows the system to maintain streaming performance while working within the constraints and capabilities of standard HTTP, rather than requiring proprietary protocols.
Solution Approach 2:
The playlist file (M3U8) acts as an intermediary that coordinates the delivery of media segments through standard HTTP. It contains a list of URLs pointing to sequential segments, enabling the system to orchestrate streaming delivery using conventional web protocols, thus bridging the gap between streaming performance requirements and standard protocol compatibility.
4Adaptability or versatility
If media data is segmented into multiple files, then adaptability is improved, but device complexity increases
Solution Approach 1:
The playlist file serves as an intermediary that manages the complexity of segmented media delivery. It contains organized lists of URLs for media segments in sequential order, allowing client devices to automatically retrieve segments in the correct sequence without requiring complex logic. The playlist file handles the coordination overhead, keeping client device complexity low while enabling adaptability through segment-based delivery.
Data Source
Figure 1
Figure 2A
Figure 2B
AI summary
Methods and apparatuses provide real-time or near real-time streaming of content using transfer protocols such as an HTTP compliant protocol. In one embodiment, a method includes providing a request for a playlist file (e.g. an updated playlist) and specifying a compression protocol with or for the request; the request can come from a client device which is requesting the playlist from a web server. The web server can provide the playlist in a compressed format.