URI Timestamps in MPD for Just-in-Time Content Output

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing content output systems face inefficiencies due to early requests for remote elements, leading to unnecessary storage and frequent updates, which result in suboptimal performance and resource utilization.

Innovation Solution

The proposed solution involves inserting a universal resource identifier (URI) into a media presentation description (MPD) with parameters that ensure a just-in-time response for remote elements, rather than requesting them far in advance. This URI contains data for determining the appropriate time to send or store the response, based on parameters such as time windows and current time.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the client device requests the remote element far in advance of the output period, then the remote element can be retrieved early, but this causes unnecessary storage and frequent updates, reducing system efficiency

Engineering Contradiction:
Improveremote element availabilityVSAvoidsystem efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system performs preliminary actions by pre-computing and storing the just-in-time request timestamp in the MPD file before playback occurs. This allows the client device to know exactly when to request the remote element without needing to request it far in advance, thereby improving system efficiency while ensuring availability.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system uses feedback mechanisms where the processing device monitors the current time against the stored timestamp parameters in the MPD. When the current time matches the predetermined timestamp, the processing device triggers the remote element request, creating a feedback loop that ensures timely retrieval without early or repeated requests.

Inventive Principle:
Principle #23Feedback

2Productivity

If the client device requests the remote element just-in-time before output, then system efficiency improves, but the request timing must be precisely controlled

Engineering Contradiction:
Improvesystem efficiencyVSAvoidtiming control complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system resolves timing control complexity by performing the preliminary action of embedding precise timestamp parameters directly into the MPD file during content preparation. This shifts the complexity from runtime decision-making to offline parameter setting, making the just-in-time request straightforward for the client device.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The MPD file acts as an intermediary that carries the timing information between the processing device and client device. By pre-storing the predetermined timestamp in the MPD, the system simplifies the interaction protocol, allowing the client device to simply compare current time against the stored value without complex timing logic.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If the processing device caches the remote element response early, then the element is available when needed, but this wastes storage resources

Engineering Contradiction:
Improveelement availabilityVSAvoidstorage usage
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The system performs preliminary action by pre-calculating and storing the exact moment when the remote element should be requested in the MPD file. This eliminates the need for early caching, as the element is requested precisely when needed based on the predetermined timestamp, thereby avoiding unnecessary storage consumption.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The processing device uses self-service by automatically monitoring the current time against the stored timestamp parameters and autonomously triggering the remote element request at the correct moment. This eliminates the need for manual intervention or early caching, optimizing both timing and storage usage.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS20250126312A1Systems and methods for content output
Publication Date: 2025.04.17 COMCAST CABLE COMM LLC
  • US20250126312A1 patent drawing
  • US20250126312A1 patent drawing
  • US20250126312A1 patent drawing

AI summary

Methods and systems for content output are disclosed. A client device may receive a media presentation description (MPD). The MPD may comprise a first element associated with a portion of a content item. The first element may comprise a uniform resource identifier (URI). The URI may comprise data associated with responding to a request for a second element associated with a supplemental content item. The request for the second element may be sent to at least one processing device. The request may comprise the URI. The second element may be received from the at least one processing device based on the data associated with responding to the request for the second element. Output of the supplemental content item may be caused during output of the portion of the content item based on replacing the first element with the second element.