Stateless Bidder Architecture for Real-Time Bidding Latency

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Real-time bidding (RTB) systems for online advertisements face challenges in managing large volumes of bidding opportunities across multiple exchanges, ensuring scalability, reducing latency, and minimizing overage costs due to uncertainties in inventory availability and campaign delivery goals.

Innovation Solution

A stateless bidding system that communicates with impression and event tracking servers to determine whether to bid on online advertisement impressions based on campaign performance data, using a distributed architecture to manage bidders and servers across multiple exchanges, and employing a controller to regulate bidding and prevent excessive spending.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If a geographically distributed set of servers is used to handle large advertising campaigns across multiple exchanges, then the system can meet time and scale requirements for processing tens or hundreds of thousands of bid opportunities per second, but the device complexity and difficulty of managing distributed bidders increase significantly

Engineering Contradiction:
Improvebid processing capacityVSAvoidsystem architecture complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system segments the bidding functionality into independent stateless bidder components that can be distributed across multiple servers and geographic locations. Each bidder operates autonomously without shared state, allowing the system to scale horizontally to handle tens or hundreds of thousands of bid opportunities per second while maintaining manageable complexity through modular design

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The stateless bidder design creates a universal component that can be deployed anywhere in the distributed system and perform the same bidding function. This multi-functionality allows any bidder instance to handle any campaign or exchange, eliminating the need for specialized components and simplifying the management of geographically distributed servers

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

2Reliability

If traditional stateful bidding systems are used to manage campaign delivery, then bidding decisions can be made with full context, but the system cannot scale to handle large volumes of bid opportunities across multiple exchanges and the latency increases

Engineering Contradiction:
Improvebidding decision accuracyVSAvoidbid processing throughput
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The invention extracts the state management functionality from the bidder decision-making process. By separating the stateless bidding logic from campaign state tracking, the system enables high-speed parallel processing of bid opportunities while maintaining reliable decision-making. The state information is externalized and made accessible without becoming a bottleneck

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system introduces an intermediary mechanism (campaign manager or control plane) that handles state management and coordinates between multiple stateless bidders. This mediator allows individual bidders to make rapid decisions without holding state, while still ensuring overall campaign delivery goals are met through centralized coordination

Inventive Principle:
Principle #24Intermediary (Mediator)

3Speed

If bidders are placed physically close to exchanges to reduce latency, then the response time meets the 50-100 millisecond requirement, but the geographic distribution increases the complexity of managing and coordinating bidders across different locations

Engineering Contradiction:
Improvebid response timeVSAvoiddistributed system management
Core Design Contradiction:
SpeedVSDevice complexity

Solution Approach 1:

Each stateless bidder is designed to be self-sufficient, containing all the logic needed to make bidding decisions independently without requiring coordination with other bidders or access to shared state. This self-service capability allows bidders to be deployed in any geographic location near exchanges, meeting the 50-100 millisecond response time requirement while simplifying distributed system management through autonomous operation

Inventive Principle:
Principle #25Self-service

4Adaptability or versatility

If multiple RTB exchanges are integrated to deliver campaigns across different publishers, then the campaign delivery coverage and reach increase, but the system complexity and difficulty of exercising consolidated control increase

Engineering Contradiction:
Improvecampaign delivery coverageVSAvoidmulti-exchange integration
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The stateless bidder design creates a universal interface that can interact with multiple different RTB exchanges through standardized protocols. Each bidder can participate in auctions across any exchange without requiring exchange-specific customization, enabling broad campaign delivery coverage while simplifying multi-exchange integration through a unified approach

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

Data Source

PatentUS11854048B1System and method for controlling real-time bidding for online advertisements
Publication Date: 2023.12.26 VALASSIS DIGITAL CORP
  • US11854048B1 patent drawing
  • US11854048B1 patent drawing
  • US11854048B1 patent drawing

AI summary

A method and system for controlling real-time bidding for online advertisements is disclosed. According to one embodiment, a computer-implemented method comprises communicating with a bidder and an impression server and an event tracking server. The bidder receives a real-time bidding (RTB) request containing an available impression from an exchange and places a bid corresponding to the RTB request. The impression server receives impression requests from a browser and responds to the impression requests from the browser. The event tracking server receives event requests from the browser and responds to event requests from the browser. Campaign performance data is retrieved from one or more of the impression server and the event tracking server and compared to the campaign target. The bidder is notified whether to bid for online advertisement impressions based on the campaign performance data.