Media Container Checksum for Metadata Synchronization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current multimedia file formats lack effective mechanisms for linking and synchronizing coded media data with metadata, leading to issues where entities manipulating media data may fail to update corresponding metadata, resulting in metadata becoming useless due to desynchronization.

Innovation Solution

Incorporating a checksum mechanism within the container file that is derived from media units, along with scope information, to validate the integrity and relevance of metadata items, ensuring they remain valid and synchronized with the associated media data units.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If metadata items are stored separately from media data units without verification mechanisms, then the container file structure remains simple and easy to manipulate, but metadata desynchronization occurs when media data is modified

Engineering Contradiction:
Improvemetadata synchronizationVSAvoidcontainer file structure
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

A checksum is pre-calculated from media data units and embedded into the container file structure during file creation or modification. This preliminary action ensures that when media data changes, the checksum will detect the change and alert the system to update or invalidate associated metadata, preventing desynchronization without requiring continuous verification mechanisms

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The checksum serves as a feedback mechanism that continuously validates the relationship between media data units and metadata items. When media data is modified, the checksum changes, providing feedback that triggers metadata updates or invalidation, ensuring synchronization is maintained through a closed-loop verification system

Inventive Principle:
Principle #23Feedback

2Reliability

If no verification mechanism is implemented, then processing and manipulating media data is faster and more efficient, but metadata integrity cannot be ensured

Engineering Contradiction:
Improvemetadata integrityVSAvoidmedia data processing speed
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The checksum is calculated and embedded in advance during file creation or modification operations. This preliminary calculation eliminates the need for repeated verification during subsequent processing operations, maintaining high processing speed while ensuring metadata integrity through the pre-established verification baseline

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The checksum acts as an intermediary verification element that indirectly validates metadata integrity without requiring direct comparison or verification of each metadata item against media data. This intermediary mechanism ensures metadata integrity with minimal processing overhead by simply comparing checksum values

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If checksum verification is performed on all media data units, then metadata validity is thoroughly ensured, but processing time and computational resources increase

Engineering Contradiction:
Improvemetadata validityVSAvoidverification processing time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The checksum is pre-calculated and stored during file creation or modification operations. This preliminary action creates a verification baseline that can be quickly compared against future changes, ensuring metadata validity without requiring time-consuming re-verification of all media data units during subsequent operations

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

Instead of verifying all media data units comprehensively during each operation, the system performs a targeted checksum comparison that verifies only the specific media data units that have changed or are relevant to the current metadata item. This partial verification approach maintains high reliability while minimizing processing time and computational resources

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentEP3092772B1Media encapsulating and decapsulating
Publication Date: 2019.07.31 NOKIA TECHNOLOGIES OY
  • EP3092772B1 patent drawingFigure 1
  • EP3092772B1 patent drawingFigure 2
  • EP3092772B1 patent drawingFigure 3~4

AI summary

There are disclosed various methods, apparatuses and computer program products for media encapsulating and decapsulating. A container file according to a first format is obtained or generated including or referring to at least two media data units and to an obtained or generated metadata item according to a second format, the metadata item being valid for one or more media data units; and scope information is included in the container file indicating said one or more of said at least two media data units. There is also disclosed a method comprising receiving the container file; receiving the metadata item; and parsing from the container file the scope information; selecting one or more of said at least two media data units on the basis of the scope information; and determining the validity of the metadata item for said one or more of said at least two media data units.