Client-Side Secondary Event Data Instructions for Streaming Branding
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Traditional content streaming services face strain and increased costs due to the need for server-side processing of secondary event data for multiple regions or viewer groups, which requires re-encoding original content with region-specific branding graphics or audio watermarks.
Innovation Solution
Implementing client-side processing of secondary event data, where client computing devices receive encoded content segments and secondary event instructions, allowing them to insert and synchronize secondary event data such as graphics and audio codes based on pre-defined rules, without the need for server-side re-encoding.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If server-side processing of secondary event data is performed to insert region-specific branding graphics or audio watermarks into original content, then personalized channel branding for multiple regions is achieved, but computational burden on server resources increases and costs associated with resource usage increase
Solution Approach 1:
The patent extracts the secondary event data processing function from the server-side encoding system and relocates it to client-side devices. The manifest file contains instructions that enable client devices to independently insert and synchronize secondary event data (such as branding graphics and audio watermarks) with the encoded content segments, eliminating the need for servers to perform computationally intensive re-encoding operations for each region-specific customization.
Solution Approach 2:
The patent segments the content delivery process into distinct components: the server provides encoded content segments with embedded secondary event instructions in the manifest file, while client devices independently execute the secondary event data insertion and synchronization. This segmentation allows the server to avoid the computational burden of processing multiple region-specific versions, as each client handles its own customization locally.
2Adaptability or versatility
If server-side re-encoding of original content with region-specific branding is performed, then personalized channel branding is achieved, but the complexity of the content delivery system increases
Solution Approach 1:
The patent implements preliminary action by embedding secondary event instructions within the manifest file during the initial content preparation phase. These instructions contain all necessary information (such as timing, synchronization data, and branding parameters) that client devices need to perform localized secondary event data insertion. This preliminary preparation eliminates the need for complex server-side processing during content delivery, as the customization logic is already prepared and transmitted with the content.
3Adaptability or versatility
If multiple encoded content segments with different secondary event data are generated for different regions, then personalized channel branding is achieved, but the quantity of content that needs to be processed and transmitted increases
Solution Approach 1:
The patent merges the original content encoding with secondary event instructions by embedding the instructions directly within the manifest file that accompanies the encoded content segments. This combining approach allows a single set of encoded content segments to serve multiple regions, as each client device extracts and executes its own region-specific secondary event instructions from the shared manifest file, eliminating the need to generate and transmit separate encoded content versions for each region.
Data Source
AI summary
Systems and methods for client-side processing of secondary event data are provided. Client computing device receive and process manifest information provided by a streaming content service in response to a content request. In addition to the identification of the set of encoded content segments, the returned manifest information includes the secondary event instructions that instruct the client computing device on how to further process received encoded content segments with secondary event data. The client computing device may process the secondary event instructions to identify what graphics and audio codes need to be inserted be include; timing information regarding when graphics or codes are needed to be inserted; location or placement information regarding how these graphics or codes are inserted when rendered by the client computing device.