Extending DASH Manifests for Multi-Path Streaming

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The existing DASH adaptive streaming technique only considers HTTP delivery and does not support broadcast or multicast delivery, limiting the ability to describe streams delivered via various networks and select optimal streams based on Quality Of Service (QoS) parameters.

Innovation Solution

A content supply system that extends the MPD to include descriptions of various delivery paths such as terrestrial, satellite, and mobile broadcasting networks, and generates a metafile with QoS parameters to enable adaptive streaming across different networks, allowing for HTTP, FLUTE, or broadcast delivery.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If the DASH adaptive streaming technique is used with HTTP delivery only, then the system is simple and easy to implement, but it cannot support broadcast or multicast delivery paths

Engineering Contradiction:
Improvedelivery path supportVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The manifest file format is extended to support multiple delivery path types (HTTP, broadcast, multicast) within a single unified structure. The AdaptationSet element is enhanced with deliveryPathInfo and QoSParameter elements that can describe different delivery mechanisms, allowing one system to handle multiple delivery functions without requiring separate systems for each delivery type.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The delivery path information is segmented into distinct elements within the manifest file structure. Each delivery path (HTTP, broadcast, multicast) is described as a separate deliveryPathInfo element with its own QoS parameters, allowing the reception device to process and select from multiple independent delivery path descriptions without confusion.

Inventive Principle:
Principle #1Segmentation

2Adaptability or versatility

If multiple delivery paths are supported without QoS parameters, then the system becomes more versatile, but the reception side cannot optimally select streams based on service quality

Engineering Contradiction:
Improvemulti-path delivery supportVSAvoidQoS parameter description
Core Design Contradiction:
Adaptability or versatilityVSMeasurement precision

Solution Approach 1:

The manifest file structure is extended to include QoSParameter elements that define specific measurable parameters for each delivery path. These parameters (such as bandwidth, latency, error rate) can be quantified and compared, enabling the reception device to make precise, data-driven decisions about which stream to select based on current network conditions and service quality requirements.

Inventive Principle:
Principle #35Parameter changes

3Adaptability or versatility

If the MPD is extended to include broadcast and multicast delivery paths, then content can be delivered through diverse networks, but the complexity of describing and managing multiple delivery paths increases

Engineering Contradiction:
Improvedelivery network diversityVSAvoidmetafile description complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

A unified manifest file structure is designed that can accommodate multiple delivery path types through standardized elements. The deliveryPathInfo element serves as a universal container that can describe HTTP, broadcast, or multicast delivery mechanisms using consistent syntax and structure, reducing the complexity that would arise from maintaining separate description formats for each delivery type.

Inventive Principle:
Principle #6Universality (Multi-functionality)

4Ease of manufacture

If only HTTP delivery is considered in DASH, then the implementation is straightforward, but it limits content delivery to internet-based paths only

Engineering Contradiction:
Improveimplementation simplicityVSAvoiddelivery path options
Core Design Contradiction:
Ease of manufactureVSAdaptability or versatility

Solution Approach 1:

The system is designed to dynamically adapt between different delivery path types based on the content being delivered. The manifest file can include conditional deliveryPathInfo elements that allow the reception device to switch between HTTP, broadcast, and multicast delivery modes depending on the specific content requirements and available network conditions, making the system flexible rather than static.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS10212208B2Content supply device, content supply method, program, and content supply system
Publication Date: 2019.02.19 SATURN LICENSING LLC
  • US10212208B2 patent drawing
  • US10212208B2 patent drawing
  • US10212208B2 patent drawing

AI summary

The present disclosure relates to a content supply device, a content supply method, a program, and a content supply system that make it possible to extend an adaptive streaming technique employing the DASH and supply content through a plurality of different delivery paths According to a first aspect of the present disclosure, there is provided a content supply device that supplies a plurality of pieces of streaming data that include content of a same subject and differ in an attribute according to an adaptive streaming technique, the content supply device including: a supply unit configured to supply the plurality of pieces of streaming data to a reception side via a plurality of different networks; and a metafile generating unit configured to generate a metafile including an acquisition destination of a manifest file in which a QoS parameter for selecting the plurality of pieces of streaming data to be supplied by the reception side and a condition value of the QoS parameter are described and supply the metafile to the reception side. The present disclosure can be applied to a system that delivers content in a streaming manner.