Recovery Data Table for AV Content Metadata Integrity
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In digital broadcasting systems, the enhanced service data provided by broadcasting stations is often altered or removed by Multichannel Video Programming Distributors (MVPDs), leading to inconsistencies between the intended and received enhanced service data at AV presentation devices, which can result in loss of metadata and increased latency due to separate requests for content and signaling servers.
Innovation Solution
A method and system for audio-visual content watermarking that includes a content recognizing service providing server inserting watermarks with enhanced service data into the AV content, allowing AV presentation devices to extract these watermarks and request additional data from a single server, thereby maintaining metadata integrity and reducing latency.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If MVPD extracts and converts AV content, then AV content is delivered to AV presentation device, but enhanced service data is removed or altered causing metadata loss
Solution Approach 1:
The recovery file is generated in advance by the broadcasting station, containing all necessary content identifiers and enhanced service data information before the content reaches the MVPD. This preliminary preparation ensures that the AV presentation device can retrieve the correct enhanced service data directly from the recovery file, bypassing the need for MVPD processing and eliminating metadata loss.
Solution Approach 2:
The recovery file acts as an intermediary data structure that carries content identifier information from the broadcasting station to the AV presentation device. This intermediary contains a recovery data table with contentID fields that link AV content to its corresponding enhanced service data, enabling direct retrieval without relying on MVPD's enhanced service data processing.
2Reliability
If AV presentation device requests content and signaling separately, then complete data is obtained, but latency increases
Solution Approach 1:
The recovery file combines content identifier information and enhanced service data references into a single integrated data structure. By merging what would otherwise require separate requests (content identification and signaling data retrieval) into one unified recovery file, the system eliminates the time delay of sequential requests while ensuring all necessary data is obtained.
3Ease of operation
If broadcast receiving device extracts only uncompressed AV data, then AV content is delivered, but enhanced service data is not available
Solution Approach 1:
The solution adds a new dimension to the data delivery system by introducing the recovery file as a separate parallel data stream. While the broadcast receiving device continues its simple function of extracting and delivering uncompressed AV content, the recovery file independently carries content identifier and enhanced service data information to the AV presentation device, which then correlates the two streams to access complete functionality.
Data Source
AI summary
A method and a receiver to receive “recovery data table” (See FIGS. 36A and 38F.) which is used for retrieving “supplementary content” are disclosed. Said “recovery data table” (See FIGS. 36A and 38F.) has “contentID. type” field describing “type of content identifier” and defining “uniform resource name”.