Traffic Management Agent for Server Load Balancing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Anycast networks face challenges in managing server load, particularly when a server returns to an online state after being offline, as it can quickly become overwhelmed by a surge of traffic, leading to unhealthy server states and availability issues.

Innovation Solution

Implementing a traffic management agent that detects the return of a server to an online state and selectively directs a portion of incoming requests to a secondary IP address block, thereby reducing the total volume of traffic received by the primary POP group and preventing server overload.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a server announces its route to BGP after being offline, then server availability is improved, but the server becomes overwhelmed by traffic surge leading to unhealthy state

Engineering Contradiction:
Improveserver availabilityVSAvoidtraffic overload
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The system performs preliminary action by detecting when a server returns online and proactively redirecting traffic away from it before the server can be overwhelmed. The load management system identifies newly-online servers and preemptively directs traffic to other servers in the pool, preventing the traffic surge from reaching the vulnerable server in the first place.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The load management system acts as an intermediary between the BGP routing system and the server pool. It sits in the middle, monitoring server status and controlling traffic flow to individual servers. This intermediary layer prevents direct exposure of newly-online servers to the full traffic surge by mediating and regulating the traffic distribution.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Speed

If BGP selects lowest latency path for Anycast requests, then access speed is improved, but newly-online servers receive excessive traffic causing instability

Engineering Contradiction:
Improveaccess speedVSAvoidserver stability
Core Design Contradiction:
SpeedVSReliability

Solution Approach 1:

The system implements dynamic traffic management by continuously monitoring server status and adjusting traffic distribution in real-time. When a server comes online, the system dynamically modifies traffic routing to exclude or limit traffic to that server temporarily. As the server stabilizes, traffic allocation is dynamically adjusted again, allowing the system to adapt to changing conditions while maintaining both speed and stability.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The load management system employs feedback mechanisms by monitoring server health status, online/offline states, and traffic patterns. This feedback information is used to continuously adjust traffic routing decisions. When a server returns online, the feedback loop triggers traffic redirection away from that server, and when the server stabilizes, the feedback signals allow gradual traffic reintroduction, creating a self-regulating system that balances speed and stability.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS12273413B2Load management for servers in shared address network architecture
Publication Date: 2025.04.08 MICROSOFT TECHNOLOGY LICENSING LLC
  • US12273413B2 patent drawing
  • US12273413B2 patent drawing
  • US12273413B2 patent drawing

AI summary

A system for load management in a shared address networking architecture includes a primary point-of-presence (POP) group of servers configured to serve content of a domain and that are each reachable at an address of a first IP address block and a secondary PoP group of servers configured to serve the content of the domain and that are each reachable at an address of a second IP address block. The system further includes a traffic management agent configured to reduce a total volume of incoming requests received by the primary PoP group for a period of time following a return of a first server in the primary PoP group of servers to an online state by selectively directing a first percentage of the incoming requests to the second IP address block instead of the first IP address block.