Server Farm Load Balancing via Capability-Based Segmentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current load balancing systems in server farms, particularly for GPRS Gateway Support Node (GGSN) servers, are inefficient as they do not utilize information from access requests to direct traffic based on server capabilities, leading to suboptimal resource allocation and lack of support for specific connection types, and do not effectively integrate with AAA protocols for intelligent traffic direction.
Innovation Solution
Implement a system that segregates servers based on their capabilities, using information from access requests to direct traffic to the most suitable server farm and within that farm, leveraging GTP tunnel messages and RADIUS protocols to optimize resource allocation and support multiple protocol types, including IPv4 and IPv6, and integrating with AAA systems for enhanced authentication and accounting.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If load balancing is done strictly on hardware utilization basis, then hardware resources are efficiently utilized, but server capability compatibility is compromised
Solution Approach 1:
The patent segments the server farm into multiple service groups based on server capabilities (e.g., IPv4-only, IPv6-only, dual-stack servers). This segmentation allows the load balancer to direct traffic to appropriate server groups based on capability requirements while still utilizing hardware resources efficiently within each segment.
Solution Approach 2:
The patent applies local quality by assigning different load balancing strategies to different server groups based on their specific capabilities. Each service group has tailored selection criteria that match the hardware utilization goal with the capability requirements, ensuring optimal performance for each segment.
2Adaptability or versatility
If external provisioning approaches are used, then server capability support is improved, but IP address efficiency deteriorates
Solution Approach 1:
The load balancer performs capability-based routing autonomously by examining access request parameters and matching them against server group capabilities. This self-service approach eliminates the need for external provisioning systems, allowing efficient IP address utilization while maintaining full capability support.
3Device complexity
If AAA server information is not integrated with load balancer, then system complexity is reduced, but intelligent traffic direction capability is lost
Solution Approach 1:
The patent implements feedback by having the load balancer receive capability information from AAA servers and use this information to make intelligent traffic direction decisions. The AAA server's authentication and authorization data provide feedback that enables the load balancer to optimize traffic routing based on user credentials and service requirements.
Data Source
AI summary
Techniques and systems for server farm load balancing and resource allocation are disclosed. In one embodiment, a method of load balancing can include: arranging servers into service groups; receiving an access request with information related to a differentiation between the service groups; selecting one of the service groups based on a mapping comparison to the information; and selecting one of the servers within the selected service group based on a hardware utilization comparison. The servers can include GPRS (General Packet Radio Service) Gateway Support Node (GGSN) or Remote Authentication Dial In User Service (RADIUS) servers, for example. The information can include an Access Point Name (APN) or Calling Station ID, for example.