Header-Based Server Status Exchange for Dynamic Load Balancing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Traditional network load balancers are expensive and create bottlenecks due to static routing rules that fail to account for dynamic changes in servers and network loads, leading to slowed network traffic in growing networks.
Innovation Solution
The use of HTTP or similar protocol-based headers to exchange server health and client information between servers and a request management entity for intelligent routing, throttling, and load balancing, allowing dynamic decision-making based on server availability and client requests.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If traditional network load balancers are used for routing requests, then request management is provided, but network traffic slows down and bottlenecks occur as the network grows
Solution Approach 1:
The patent extracts the load balancing functionality from traditional dedicated hardware devices and implements it as a software-based request management entity that operates at the application layer. This extraction allows the system to perform intelligent routing decisions without the performance penalties of traditional hardware load balancers, maintaining high network traffic speed while providing effective request management through header-based server status exchange.
Solution Approach 2:
The patent replaces the mechanical hardware-based load balancing system with a software-based solution that uses HTTP headers for communication. Instead of relying on dedicated load balancer devices, the system uses standard web protocol extensions to exchange server status information, enabling flexible and scalable request routing without the performance bottlenecks of traditional hardware approaches.
2Ease of operation
If traditional routers perform multi-layer routing, then request routing is achieved, but the router creates a bottleneck as the network grows
Solution Approach 1:
The patent segments the routing function into two parts: traditional network layer routing handled by routers, and application layer request management handled by a specialized request management entity. This segmentation allows routers to focus on basic packet forwarding while the request management entity handles intelligent routing decisions based on server status, reducing the complexity burden on routers and improving overall system scalability.
Solution Approach 2:
The patent introduces a request management entity as an intermediary between clients and servers that handles intelligent routing decisions. This intermediary uses header-based communication to exchange server status information and make routing decisions, separating the complexity of intelligent routing from the traditional router infrastructure and enabling scalable request management without overwhelming router capabilities.
3Ease of manufacture
If static routing rules are used, then simple routing is achieved, but dynamic changes in servers and network loads are not accounted for
Solution Approach 1:
The patent implements dynamic routing by having servers periodically update their status information in HTTP headers, allowing the request management entity to adapt routing decisions based on current server conditions. This dynamic approach replaces static routing rules with a flexible system that automatically responds to changes in server availability, load conditions, and network status without requiring manual configuration changes.
Solution Approach 2:
The patent establishes a feedback mechanism where servers continuously report their status through HTTP headers to the request management entity, which then adjusts routing decisions based on this feedback. This closed-loop system enables automatic adaptation to dynamic changes in server and network conditions, maintaining optimal routing performance without requiring manual intervention or static pre-configured rules.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
Server health and client information are exchanged through headers for request management. Headers in standardized or proprietary protocol communication between servers and a request management module and/or clients and the request management module may be used to exchange server health and client information. The exchanged server health and/or client information may be employed in throttling, routing, and/or load balancing the incoming requests. Rules specified by the client through the header exchange may also be used for throttling, routing, and/or load balancing decisions.