ATSC 3.0 Ad Timing via Event Streams

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

In ATSC 3.0 systems, broadcasters cannot accurately determine when advertising content starts or stops, making it difficult to update the user interface (UI) accordingly, as the broadcaster app lacks timely signals for ad-related UI presentations or replacements.

Innovation Solution

The implementation of Event Streams with xlinkResolution signals provides timestamps for ad start and stop times, allowing the broadcaster app to receive notifications from the receiver app, enabling timely UI updates and ad replacements within the ATSC 3.0 xlinkResolution Period element.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If the broadcaster app uses traditional ATSC 3.0 signaling without Event Streams, then the system maintains simplicity in communication protocols, but the broadcaster cannot accurately determine ad start and stop times for UI updates

Engineering Contradiction:

Improvead timing detection accuracyVSAvoidcommunication protocol complexity

Core Design Contradiction:

Measurement precisionVSDevice complexity

Solution Approach 1:

The ad delivery process is segmented into distinct phases: ad insertion by receiver app, ad playback execution, and UI update triggering. Event Streams separate the timing signal generation (broadcaster) from the ad content delivery (receiver), allowing precise timing measurement without complex integrated protocols.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

Event Streams act as an intermediary mechanism between the broadcaster app and receiver app. The broadcaster publishes ad timing events to the Event Stream, which the receiver subscribes to, enabling accurate timing signal transmission without requiring direct complex communication between applications.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Productivity

If the broadcaster app receives real-time ad playback notifications via Event Streams, then the broadcaster can update UI and monetize ad viewing, but the system requires additional subscription and notification infrastructure

Engineering Contradiction:

Improvead monetization capabilityVSAvoidnotification system complexity

Core Design Contradiction:

ProductivityVSDevice complexity

Solution Approach 1:

The receiver app autonomously subscribes to Event Streams and automatically sends playback status notifications to the broadcaster app. This self-service mechanism enables monetization tracking without requiring the broadcaster to implement complex active monitoring or query systems.

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

Event Streams establish a feedback loop where the receiver app reports ad playback status (start, stop, completion) back to the broadcaster app. This real-time feedback enables the broadcaster to update UI elements and trigger monetization actions based on actual ad viewing behavior.

Inventive Principle:

Principle #23Feedback

3Adaptability or versatility

If the receiver app autonomously manages ad insertion and playback, then the ad delivery flexibility is improved, but the broadcaster loses control over ad presentation timing

Engineering Contradiction:

Improvead delivery flexibilityVSAvoidad presentation timing control

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

The broadcaster app performs preliminary action by publishing ad timing information to Event Streams before the actual ad playback occurs. This advance signaling ensures that the receiver app has the necessary timing information to execute ad insertion and playback reliably, maintaining broadcaster control over presentation timing.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system merges two approaches: the receiver app autonomously manages ad content insertion and playback execution (flexibility), while the broadcaster app controls ad timing through Event Streams (reliability). This combination allows both adaptability in ad delivery and reliability in timing control.

Inventive Principle:

Principle #5Merging (Combining)

Data Source

PatentUS11706465B2ATSC 3.0 advertising notification using event streams

Publication Date: 2023.07.18 SONY GROUP CORP

AI summary

An Event Streams ‘event’ which contains information about ads is sent via ATSC 3.0 to a receiver player along with an xlinkResolution signal. This information includes but is not limited to time stamps for when the ads will start and stop. When this xlinkResolution is sent to the receiver player, the receiver player sends a notification to a broadcaster app containing the information about start and stop time for presenting the ad. Using this information, the broadcaster app updates itself so that, for example, the broadcaster app can present a message on a user interface regarding the subject of the ad, or present content related to but different from the ad along with the ad itself.