Server-Side Content Management for Latency Reduction

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current methods for delivering advertising content in electronic environments lead to increased latency and bandwidth usage due to client-side requests, limiting the content provider's ability to adapt primary content based on available advertising, which affects the quality of the final display and user experience.

Innovation Solution

Implementing server-side content management that determines supplemental content, such as advertising, before primary content is sent to the client device, allowing for real-time optimization and synchronization of advertising IDs, enabling targeted and dynamic ad placement without the latency of client-side calls.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If advertising content is requested by the display device (client-side requests), then the device can display advertising along with primary content, but latency increases and bandwidth is consumed

Engineering Contradiction:
Improveadvertising content deliveryVSAvoidlatency
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent applies preliminary action by having the content provider determine and prepare advertising content selections before the client device requests them. The content provider receives the primary content request, determines supplemental advertising content based on that request, and prepares the advertising content in advance, so that when the client device requests advertising, the content is already ready or can be delivered immediately, thereby reducing latency.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If advertising content is requested by the display device, then the device can display advertising, but additional bandwidth is required

Engineering Contradiction:
Improveadvertising content deliveryVSAvoidbandwidth
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent applies merging by combining the primary content delivery and advertising content delivery into a single integrated process. The content provider determines both primary and supplemental advertising content in one operation, and can deliver them together in a single response to the client device, thereby reducing the total bandwidth consumption compared to separate requests and responses.

Inventive Principle:
Principle #5Merging (Combining)

3Ease of operation

If advertising is requested from the user's device instead of the content provider, then the device can display advertising, but the content provider's ability to adapt primary content based on available advertising is limited

Engineering Contradiction:
Improveadvertising display capabilityVSAvoidcontent adaptation
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

The patent applies inversion by reversing the traditional request flow. Instead of the client device requesting advertising content from advertising servers, the content provider receives the primary content request, determines the appropriate advertising content based on that request and available advertising inventory, and then delivers both primary and advertising content to the client device. This inversion enables the content provider to adapt primary content based on available advertising.

Inventive Principle:
Principle #13The other way round (Inversion)

Data Source

PatentUS11893604B2Server-side content management
Publication Date: 2024.02.06 AMAZON TECH INC
  • US11893604B2 patent drawing
  • US11893604B2 patent drawing
  • US11893604B2 patent drawing

AI summary

Supplemental content can be determined through a server-side process, wherein a primary content provider can obtain the supplemental content from a supplemental content provider before any of the content is sent to the client device initially requesting the primary content. A primary content provider submits a request that can include an authorization token for the primary content provider, a publisher token including a proxy identifier for the user, application, or client device, and other relevant information. The supplemental content provider can verify the information and select targeted content based on the information. The supplemental content can then be provided to the primary content provider for incorporation with the primary content. The primary content provider can adjust the layout or selection before sending to the client device for display.