Livestream Supplemental Content Timing for Fair Load Distribution

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing livestream systems fail to account for client devices joining or leaving at different times, leading to unequal distribution of supplemental content and network resource spikes, resulting in some users missing content or experiencing delayed delivery.

Innovation Solution

Implementing non-concurrent supplemental content item loading by using timestamped markers and elapsed time thresholds to determine when client devices present content, distributing the load over time to reduce demand spikes and ensure equitable distribution.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If supplemental content items are presented at fixed times synchronized across all client devices, then the content distribution follows a traditional broadcast model, but client devices that join or leave at different times receive unequal amounts of supplemental content

Engineering Contradiction:
Improveequitable content distributionVSAvoidhandling of dynamic client joining/leaving
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The system transitions from static fixed-time supplemental content presentation to dynamic timing based on client device elapsed time. Each client device determines when to present supplemental content based on its own elapsed time metric, which accounts for when the device joined the livestream. This dynamic approach ensures that clients joining at different times receive appropriate supplemental content while maintaining equitable distribution across all users.

Inventive Principle:
Principle #15Dynamics

2Device complexity

If supplemental content items are presented at fixed synchronized times, then the broadcast model is simple to implement, but the content server experiences excessive demand spikes at those fixed times

Engineering Contradiction:
Improvecontent delivery systemVSAvoidnetwork and server load
Core Design Contradiction:
Device complexityVSPower

Solution Approach 1:

The system implements periodic supplemental content presentation at multiple different times across the client population. Instead of all clients requesting supplemental content simultaneously at fixed intervals, each client device periodically checks its elapsed time and requests supplemental content at different moments. This distributes the periodic demand across time, eliminating demand spikes while maintaining the periodic nature of supplemental content delivery.

Inventive Principle:
Principle #19Periodic action

3Reliability

If all client devices request supplemental content simultaneously at fixed times, then the content delivery is synchronized, but network and processing resources are excessively utilized

Engineering Contradiction:
Improvecontent delivery synchronizationVSAvoidnetwork and processing resources
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The system segments the synchronized supplemental content request process into individual client device decisions based on elapsed time. Rather than all devices simultaneously requesting content at fixed times, each device independently determines its request timing based on its own elapsed time metric. This segmentation distributes the resource-intensive simultaneous requests across different time points, reducing overall network and processing resource utilization while maintaining reliable content delivery.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS20260067514A1Non-concurrent supplemental content load for livestreams
Publication Date: 2026.03.05 GOOGLE LLC
  • US20260067514A1 patent drawing
  • US20260067514A1 patent drawing
  • US20260067514A1 patent drawing

AI summary

The systems and methods disclosed herein relate to providing or presenting supplemental content non-concurrently during a livestream. In one embodiment, a method for providing supplemental content includes receiving from a client device a request for a supplemental content item; determining whether an elapsed time between the request for the supplemental content item and an earlier event exceeds a supplemental content interval; and responsive to determining that the elapsed time exceeds the supplemental content interval, causing the supplemental content item to be transmitted to the client device.