Shared Manifest Updating for Scalable Timeline-Based Content Delivery
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing content delivery systems require significant computational resources to maintain separate manifest files for each client device, especially when multiple devices are outputting the same content at different times, leading to inefficiencies in compute and storage requirements.
Innovation Solution
Utilizing a single manifest file per content item, supplemented by an update file, which allows each client device to modify the manifest file based on its playback timeline, reducing the need for separate files and optimizing resource usage.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If separate manifest files are maintained for each client device, then each device can have customized content delivery, but computational and storage requirements increase significantly
Solution Approach 1:
The patent merges multiple device-specific manifest files into a single shared manifest file that contains content segment information for all client devices. This consolidation eliminates redundant data storage and reduces computational overhead while maintaining the ability to serve different devices with appropriate content segments based on their playback timelines and device characteristics
Solution Approach 2:
The single manifest file is designed to serve multiple client devices simultaneously with different playback timelines. It contains universal content segment information that can be adapted to various devices' needs, making the manifest file multi-functional rather than requiring separate specialized files for each device
2Ease of operation
If separate manifest files are generated for each client device outputting content at different times, then each device's playback timeline can be optimized, but device complexity and resource management become more difficult
Solution Approach 1:
The patent segments the manifest file into reusable content segment blocks that can be independently referenced by different client devices. Each device can select and assemble the specific segments needed for its playback timeline from the shared manifest, allowing playback optimization without requiring separate complete manifest files for each device
Solution Approach 2:
Instead of creating separate manifest files for each device, the system creates a single master manifest that can be copied and distributed to multiple devices. Each device receives a copy of the shared manifest and independently determines its playback timeline based on the same source data, simplifying resource management while maintaining customization capability
Data Source
AI summary
Methods, systems, and apparatuses for updating content data are described herein. A single manifest file may be maintained per content item and provided to client devices with an update file. The manifest file each client device receives may not initially facilitate output of content segments. Instead, the manifest file may be a partial manifest file that initializes playback and/or facilitates output of a most-recent content segment(s). The client devices may each determine a playback timeline. And each client device may use the corresponding update file to modify the manifest file based on the determined playback timeline, resulting in a modified manifest file that facilitates output of one or more content segments associated with the playback timeline for that particular client device.