Hierarchical Initialization Signaling for DASH Interoperability

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The existing initialization sets in DASH standards lack the ability to effectively signal interoperability points and capabilities, particularly failing to address scenarios with multiple codecs, unclear codec requirements, and the inability to signal optional capabilities, and lack unique identifiers for equivalence purposes.

Innovation Solution

The introduction of a hierarchical initialization system with new attributes and elements such as '@inAllPeriods', 'InitializationGroup', and 'InitializationPresentation' in the MPD file, allowing for flexible signaling of interoperability points and capabilities, enabling clients to identify and support necessary codecs and media types without requiring every period to support every initialization set.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If initialization sets list common initialization segments for all periods, then interoperability signaling is provided, but flexibility to support different codecs in different periods is lost

Engineering Contradiction:
Improveinteroperability signalingVSAvoidcodec flexibility
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent divides the initialization set structure into hierarchical levels: InitializationSet (basic unit), InitializationGroup (collection of initialization sets), and InitializationPresentation (complete playback capability). This segmentation allows different periods to reference different initialization sets within groups, enabling codec flexibility while maintaining interoperability signaling through the hierarchical structure.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent adds a temporal dimension to initialization set usage by introducing the '@inAllPeriods' attribute. This attribute allows initialization sets to be selectively applied across different time periods (false by default, true when all periods must support the initialization set), enabling flexible codec selection per period while maintaining interoperability where needed.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

2Device complexity

If a single common codec is signaled for all periods, then simplicity is maintained, but ability to support multiple codecs across periods is lost

Engineering Contradiction:
Improvesignaling simplicityVSAvoidmulti-codec support
Core Design Contradiction:
Device complexityVSAdaptability or versatility

Solution Approach 1:

The patent segments codec signaling into per-period adaptation sets, each referencing initialization sets by ID. This allows each period to have its own codec configuration while the hierarchical group structure maintains organized complexity, avoiding the need for a single common codec declaration.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent uses initialization set IDs as references that can be copied and referenced across multiple periods. Instead of repeating full codec configurations, periods reference initialization set identifiers, simplifying multi-codec support through compact referencing while maintaining full codec capability descriptions.

Inventive Principle:
Principle #26Copying

3Device complexity

If optional capabilities are not signaled, then manifest simplicity is maintained, but client ability to identify supported features is reduced

Engineering Contradiction:
Improvemanifest structureVSAvoidcapability information
Core Design Contradiction:
Device complexityVSLoss of information

Solution Approach 1:

The patent adds an optional dimension to capability signaling through the '@inAllPeriods' attribute and hierarchical group structure. Clients can identify optional capabilities by examining which initialization sets are grouped together and whether the '@inAllPeriods' attribute is set, providing rich capability information without forcing all periods to support all features.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

Solution Approach 2:

The patent makes capability signaling dynamic through the hierarchical structure where InitializationGroups can include optional initialization sets. The '@inAllPeriods' attribute dynamically indicates whether an initialization set is required for all periods or optional, allowing clients to adapt their capability detection based on the actual manifest content.

Inventive Principle:
Principle #15Dynamics

4Ease of operation

If initialization sets lack unique identifiers, then parsing flexibility is maintained, but equivalence recognition and efficiency are reduced

Engineering Contradiction:
Improveparsing flexibilityVSAvoidequivalence recognition efficiency
Core Design Contradiction:
Ease of operationVSProductivity

Solution Approach 1:

The patent uses unique identifier IDs for initialization sets that can be copied and referenced across the manifest. Instead of requiring clients to parse and compare full initialization set contents for equivalence, the system uses compact ID references that enable efficient equivalence recognition through simple ID comparison while maintaining parsing flexibility.

Inventive Principle:
Principle #26Copying

Data Source

PatentEP3906693B1Flexible interoperability and capability signaling using initialization hierarchy
Publication Date: 2024.05.08 TENCENT AMERICA LLC
  • EP3906693B1 patent drawingFigure 1A
  • EP3906693B1 patent drawingFigure 1B
  • EP3906693B1 patent drawingFigure 1C

AI summary

A method and apparatus include including, in a moving pictures experts group (MPEG) dynamic adaptive streaming over hypertext transfer protocol (DASH) media presentation description (MPD) file, an initialization presentation element that identifies an initialization presentation and one or more initialization groups included in the initialization presentation. An initialization group element that identifies an initialization group and one or more initialization sets included in the initialization group is included in the MPD file. An initialization set element that identifies an initialization set is included in the MPD file. The MPD file is transmitted to a client device.