Inline Keyed Metadata Encoding Protocol

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing metadata coding protocols in multimedia files are inflexible and inefficient, as they do not allow for the addition of new metadata types without restarting the file creation process, leading to increased processing time and metadata track overhead.

Innovation Solution

A metadata declaration protocol that uses a reservation identifier and inline key system to dynamically add new metadata items to the metadata track during the coding session, allowing for flexible handling of new metadata types without significant overhead or processing time increases.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If all possible metadata types are declared in the metadata header, then new metadata types can be added without restarting file creation, but the metadata track size increases significantly due to overhead

Engineering Contradiction:

Improveability to add new metadata typesVSAvoidmetadata track size

Core Design Contradiction:

Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

The patent reserves a specific identifier (identifier 0) in the metadata header in advance as a placeholder for inline metadata. This preliminary action enables dynamic addition of new metadata types during file creation without requiring all possible metadata types to be declared upfront, thus avoiding significant overhead while maintaining adaptability.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent divides metadata into two segments: declared metadata types in the header and inline metadata types added during processing. This segmentation allows the system to maintain a compact header with only essential declarations while accommodating additional metadata types dynamically through inline mechanisms, reducing overall overhead.

Inventive Principle:

Principle #1Segmentation

2Adaptability or versatility

If multiple types of metadata are encountered in a single media item, the file creation process must recur each time, but this significantly increases processing time and recording time

Engineering Contradiction:

Improvehandling of multiple metadata typesVSAvoidprocessing and recording time

Core Design Contradiction:

Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent enables continuous file creation processing by allowing inline metadata to be added without aborting or restarting the file creation process. When new metadata types are encountered, the system seamlessly integrates them into the existing file structure through the inline mechanism, maintaining continuous processing and avoiding time-consuming recursions.

Inventive Principle:

Principle #20Continuity of useful action

Solution Approach 2:

By pre-reserving identifier 0 in the metadata header for inline metadata, the patent prepares the file structure in advance to accommodate additional metadata types. This preliminary preparation eliminates the need to abort and restart file creation when new metadata types are encountered, significantly reducing processing time.

Inventive Principle:

Principle #10Preliminary action

3Quantity of substance

If the coding protocol does not provide for declarations of metadata outside the metadata header, then the header remains compact, but new metadata types cannot be added without aborting file creation

Engineering Contradiction:

Improvemetadata header sizeVSAvoidability to add new metadata types

Core Design Contradiction:

Quantity of substanceVSAdaptability or versatility

Solution Approach 1:

The patent segments metadata declarations into two parts: a compact header containing only essential metadata type declarations, and an inline section that accommodates additional metadata types dynamically. This segmentation maintains header compactness while enabling flexible addition of new metadata types through the inline mechanism using reserved identifier 0.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary mechanism (inline metadata with reserved identifier 0) that bridges the gap between the compact header structure and the need for dynamic metadata addition. This intermediary allows new metadata types to be integrated without expanding the header significantly or aborting the file creation process.

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentUS10733146B2Inline keyed metadata

Publication Date: 2020.08.04 APPLE INC

AI summary

An encoding system may include a metadata manager, a key manager, and an encoder. The metadata manager may interface with one or more metadata sources to determine whether to include a metadata item from the one or more metadata sources. The key manager may determine whether the metadata item can be represented using one of already-allocated keys or an inline key must be used to represent the metadata item. The encoder may encode the metadata. If an inline key must be used to represent the metadata item, the encoder may associate the inline key and the type of the metadata item to the media file, and the encoder may encode the metadata item using the inline key in the media file.