Playlist Type Indicators for Adaptive Streaming
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current streaming services require specialized servers and skills, leading to high costs and a limited content library, especially in large-scale deployments, as they are designed for 'live' content and lack flexibility in handling different types of media content.
Innovation Solution
The use of playlist files with type indicators (e.g., #EXT-X-PLAYLIST-TYPE: VOD, Live, Event) allows clients to optimize processing based on content type, enabling streaming over non-streaming protocols like HTTP, supporting dynamic updates, bit rate switching, and redundancy, while also allowing for the inclusion of supplementary content and error handling.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If specialized streaming servers are used for live content distribution, then streaming capability is improved, but device complexity and cost increase
Solution Approach 1:
The patent enables standard HTTP servers to perform streaming functions by implementing playlist-based content delivery that supports both VOD and live streaming. The server uses a unified architecture that handles different content types through software configuration rather than hardware specialization, allowing one server to serve multiple streaming purposes.
Solution Approach 2:
The patent creates a virtual streaming layer using playlist files that reference media segments. Instead of requiring specialized streaming server hardware, the system copies the functionality of streaming servers through software-based playlist management and HTTP protocol usage, allowing standard web servers to provide streaming capabilities.
2Productivity
If specialized streaming servers are deployed at large scale, then content delivery is improved, but cost increases
Solution Approach 1:
The system allows existing HTTP web servers to handle streaming workloads alongside their traditional web serving functions. This eliminates the need for dedicated streaming server infrastructure, reducing hardware costs and operational expenses while maintaining content delivery capabilities at scale.
Solution Approach 2:
The patent implements automated playlist management where the server automatically generates, updates, and serves playlist files based on media segment availability. This self-service approach reduces manual configuration and management overhead, lowering operational costs while maintaining efficient content delivery.
3Ease of operation
If standard HTTP protocols are used for streaming, then ease of operation is improved, but streaming performance deteriorates
Solution Approach 1:
The patent divides media content into smaller segmented files that can be individually requested and assembled by the client. This segmentation approach works well with HTTP protocols, allowing for efficient partial content requests, parallel downloads, and automatic retry mechanisms without requiring specialized streaming protocol overhead.
Solution Approach 2:
The system pre-generates playlist files that contain references to media segments before streaming begins. This preliminary organization of content metadata allows clients to efficiently request and assemble streaming content using standard HTTP protocols, maintaining good playback performance while utilizing simple web protocols.
4Adaptability or versatility
If playlist files include type indicators for different content types, then adaptability is improved, but manufacturing precision requirements increase
Solution Approach 1:
The patent incorporates type indicators (such as #EXT-X-PLAYLIST-TYPE tags) within specific locations in the playlist file format to denote different content types like VOD or live streaming. This localized tagging approach provides content type information exactly where needed without requiring complex format changes throughout the entire file structure, balancing adaptability with format simplicity.
Data Source
AI summary
A near real time content streaming system can use a playlist file, in one embodiment, that includes an indicator of the type of content represented by the playlist file. The type can be indicated by a parameter, such as Video on Demand (VOD) or live, or event, that specifies the type of playlist file, and a client device can process the playlist file based upon the type of playlist file indicated by the parameter. For example, the client device, after determining the type of playlist from a playlist file can make efficiency optimizations when processing the playlist file. For example, the client, knowing the playlist file is a VOD playlist, can save the previously used variant playlist when switching to a new variant playlist rather than discarding the previously used variant playlist.