DASH Content Supply Device for Seamless Unicast Multicast Switching

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current DASH systems lack the ability to seamlessly switch between unicast HTTP transmission and multicast or broadcast RTP transmission, due to the inability to describe the correspondence relation between HTTP unicast-delivered and RTP multicast/broadcast-delivered content segments, and the lack of a specified payload format for RTP packets that maintain the box structure of fragmented MP4 content streams.

Innovation Solution

A content supply device and method that converts streaming data into segment files for HTTP unicast transmission and stores these files in RTP packets for multicast or broadcast transmission, while generating a metafile that describes the temporal correspondence between HTTP and RTP transmission segments, allowing seamless switching between transmission paths.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If unicast HTTP transmission is used for DASH content delivery, then content can be delivered to individual clients, but scalability is limited and cost is high when serving multiple simultaneous clients

Engineering Contradiction:
Improvecontent delivery scalabilityVSAvoidCDN infrastructure complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent segments content into chunks that can be delivered via both unicast HTTP and multicast/broadcast RTP paths. By dividing the content stream into manageable segments with temporal identifiers, the system enables selective delivery through different transmission paths, allowing scalability improvement through multicast while maintaining individual client control via unicast.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent creates a universal content delivery mechanism that supports both unicast HTTP and multicast/broadcast RTP transmission for the same content segments. The metafile format is designed to be path-agnostic, enabling the same content to be delivered through multiple transmission paths depending on client needs and network conditions, thus achieving multi-functionality.

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

2Productivity

If multicast or broadcast RTP transmission is used for content delivery, then scalability is improved, but the ability to maintain box structure of fragmented MP4 content streams is lost

Engineering Contradiction:
Improvecontent delivery scalabilityVSAvoidcontent stream integrity
Core Design Contradiction:
ProductivityVSManufacturing precision

Solution Approach 1:

The patent introduces an intermediary encoding process that converts fragmented MP4 content into RTP-compatible formats while preserving essential structure through payload type indicators and timing metadata. This intermediary representation acts as a bridge between the HTTP unicast path (which maintains original box structure) and the RTP multicast path (which requires different formatting), allowing content integrity to be maintained across both transmission paths.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Adaptability or versatility

If seamless switching between unicast and multicast/broadcast transmission is implemented, then adaptive content delivery is enabled, but the system complexity increases due to lack of correspondence description between transmission paths

Engineering Contradiction:
Improvetransmission path switching capabilityVSAvoidpath correspondence management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent performs preliminary action by pre-establishing the correspondence relationship between unicast and multicast/broadcast content segments through the metafile format. By embedding temporal identifiers and path mapping information in advance, the system eliminates the need for complex runtime correspondence management, allowing clients to seamlessly switch between transmission paths based on pre-provided mapping information without increasing system complexity.

Inventive Principle:
Principle #10Preliminary action

4Adaptability or versatility

If a metafile describing temporal correspondence between HTTP and RTP segments is generated, then path switching is enabled, but the complexity of generating and maintaining the metafile increases

Engineering Contradiction:
Improvetransmission path correspondenceVSAvoidmetafile generation complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent simplifies metafile generation by changing the parameter representation approach - using temporal identifiers and standardized path mapping fields that can be automatically generated from the content segmentation process. This parameter change transforms the metafile from a complex manual configuration into an automatically generated structure that reflects the actual content delivery timing and path relationships, reducing generation complexity while maintaining adaptability.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS9942619B2Content supply device, content supply method, program, and content supply system
Publication Date: 2018.04.10 SATURN LICENSING LLC
  • US9942619B2 patent drawing
  • US9942619B2 patent drawing
  • US9942619B2 patent drawing

AI summary

The present disclosure relates to a content supply device, a content supply method, a program, and a content supply system, which are capable of extending the DASH and seamlessly switching reception and reproduction of unicast transmission, multicast transmission, or broadcast transmission. A content supply device includes a HTTP transmitting unit that unicast-transmits a segment file of streaming data according to HTTP, an RTP transmitting unit that stores the segment file in an RTP packet without change, and transmits the RTP packet through at least one of multicasting and broadcasting according to RTP, and a metafile generating unit that generates a metafile in which a temporal correspondence relation between the segment file transmitted according to the HTTP and the segment file transmitted according to the RTP is described, and supplies the metafile to a reception side. The present disclosure can be applied to a system that delivers content in a streaming manner.