Parameter-Based Load Balancing for Server Mode 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 operational modes, leading to potential human errors and system outages.

Innovation Solution

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

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual reconfiguration is used when server clusters switch between operational modes, then routing can be adjusted, but human errors and system outages increase

Engineering Contradiction:
Improvesystem reliabilityVSAvoidmanual reconfiguration complexity
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The load balancer automatically detects operational mode changes of server clusters and adjusts traffic routing without manual intervention. The system monitors server status, identifies mode transitions, and reconfigures load balancing rules autonomously, eliminating human error while maintaining operational flexibility

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The load balancer continuously monitors operational mode parameters of server clusters and uses this feedback to dynamically adjust routing decisions. When mode changes are detected, the system automatically updates load balancing configurations based on real-time server status, ensuring reliable traffic distribution without manual reconfiguration

Inventive Principle:
Principle #23Feedback

2Adaptability or versatility

If manual reconfiguration is performed, then routing changes can be made, but processing and power resources are consumed

Engineering Contradiction:
Improverouting adaptabilityVSAvoidprocessing resource consumption
Core Design Contradiction:
Adaptability or versatilityVSUse of energy by moving object

Solution Approach 1:

The load balancer pre-configures multiple routing rules corresponding to different operational modes before mode changes occur. When a server cluster transitions modes, the system simply switches to the pre-prepared routing configuration for that mode, avoiding resource-intensive real-time computation and manual reconfiguration

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The load balancer implements dynamic routing rules that automatically adapt to changing operational modes. The system continuously monitors server status and adjusts traffic distribution in real-time based on current mode parameters, maintaining optimal routing without consuming excessive processing resources through static manual reconfiguration

Inventive Principle:
Principle #15Dynamics

3Loss of time

If automatic parameter-based routing is implemented, then reconfiguration time is reduced, but system complexity increases

Engineering Contradiction:
Improvereconfiguration timeVSAvoidload balancer complexity
Core Design Contradiction:
Loss of timeVSDevice complexity

Solution Approach 1:

The load balancer uses operational mode parameters as the basis for automatic routing decisions. By monitoring changes in these parameters and switching between pre-configured routing rules based on parameter values, the system achieves rapid reconfiguration without complex real-time computation or manual intervention

Inventive Principle:
Principle #35Parameter changes

Solution Approach 2:

The load balancer divides routing logic into separate, modular rules corresponding to different operational modes. Each rule is independently configured and can be quickly activated or deactivated based on server cluster mode, reducing overall system complexity while enabling fast reconfiguration through rule selection rather than complex decision-making

Inventive Principle:
Principle #1Segmentation

Data Source

PatentEP4583484A1Load balancing between multiple traffic flows using a parameter
Publication Date: 2025.07.09 T MOBILE INNOVATIONS LLC
  • EP4583484A1 patent drawingFigure 1
  • EP4583484A1 patent drawingFigure 2A
  • EP4583484A1 patent drawingFigure 2B

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.