Load Balancer Parameter Routing for Maintenance-Mode Cluster Switching

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current load balancing systems require manual and resource-intensive reconfiguration when server clusters switch between active and maintenance modes, leading to potential human errors and system outages.

Innovation Solution

Implement a load balancer with virtual service applications that use a single parameter and pre-programmed rules to automatically determine server clusters for packet routing, reducing the need for manual reconfiguration and minimizing errors.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of manufacture

If manual reconfiguration is used when server clusters switch between active and maintenance modes, then system control is direct and simple, but processing resources are consumed heavily and human errors occur

Engineering Contradiction:
Improveease of reconfigurationVSAvoidprocessing resource consumption
Core Design Contradiction:
Ease of manufactureVSLoss of energy

Solution Approach 1:

The load balancing rules are pre-configured with conditions for different server cluster states. When a server cluster switches to maintenance mode, the pre-configured rules automatically direct traffic to alternative active server clusters without requiring manual reconfiguration, thus reducing processing resource consumption and preventing human errors.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The load balancer automatically detects changes in server cluster states and self-adjusts traffic routing based on pre-configured rules. This self-service mechanism eliminates the need for manual intervention during server cluster maintenance, reducing both processing resource consumption and the risk of human errors while maintaining system control.

Inventive Principle:
Principle #25Self-service

2Ease of operation

If manual reconfiguration is performed for load balancing, then direct control over traffic routing is achieved, but system outages and packet drops may occur due to human errors

Engineering Contradiction:
Improvecontrol over traffic routingVSAvoidsystem availability
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The load balancer continuously monitors the state of server clusters and automatically adjusts traffic routing based on real-time feedback. When a server cluster enters maintenance mode, the system detects this change and automatically redirects traffic to active server clusters according to pre-configured rules, eliminating human errors and ensuring continuous system availability while maintaining operational control.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

Traffic routing rules are pre-configured with conditions for various server cluster states. When manual reconfiguration would be required, the pre-configured rules automatically take effect, preventing human errors that could cause system outages or packet drops while maintaining direct control over traffic routing through the rule-based system.

Inventive Principle:
Principle #10Preliminary action

3Adaptability or versatility

If multiple traffic flows are manually managed across server clusters, then each flow can be individually controlled, but the complexity of reconfiguration increases significantly

Engineering Contradiction:
Improveindividual flow controlVSAvoidreconfiguration complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

A single load balancer system handles multiple traffic flows simultaneously, with each flow governed by its own pre-configured rules. This universal approach allows individual control over each traffic flow while avoiding the complexity of manual reconfiguration, as the system automatically manages all flows based on the unified rule set when server cluster states change.

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

Solution Approach 2:

Multiple traffic flows are pre-configured with specific routing rules for different server cluster states. When reconfiguration is needed, all flows automatically apply their pre-configured rules simultaneously, eliminating the need for complex manual reconfiguration of each individual flow while maintaining adaptability and individual control over traffic routing.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS20250219927A1Load Balancing Between Multiple Traffic Flows using a Parameter
Publication Date: 2025.07.03 T MOBILE INNOVATIONS LLC
  • US20250219927A1 patent drawing
  • US20250219927A1 patent drawing
  • US20250219927A1 patent drawing

AI summary

A method comprises receiving, by a first virtual service (VS) application in a load balancer of the communication system, client packets from a client, receiving, by a second VS application in the load balancer, test packets from a tester obtaining, by the first VS application and the second VS application, a parameter from a data store communicatively coupled to the load balancer, determining, by the first VS application, a selected pool in the load balancer toward which to forward the client packets based on a first rule programmed at the first VS application and the parameter, and determining, by the second VS application, a test pool in the load balancer toward which to forward the test packets based on a second rule programmed at the second VS application and the parameter.