Network Load Balancing With Dynamic Packet-Drop Feedback

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Flow-based load balancing in networks often leads to load imbalance or overflow due to the dynamic nature of network traffic, with no mechanism to analyze why such issues occur or automatically reconfigure load balancing configurations to improve performance.

Innovation Solution

A system and method for dynamic load balancing that involves monitoring network packet flows, creating metadata for dropped packets, and transmitting it to a flow processing analysis device for determining reconfiguration settings to mitigate packet dropping and enhance performance.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If flow-based load balancing is used to distribute network traffic across servers, then network throughput and server utilization are improved, but packet dropping and load imbalance occur due to dynamic traffic patterns

Engineering Contradiction:
Improvenetwork throughputVSAvoidpacket delivery reliability
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system implements feedback by monitoring actual packet dropping at load balancers and using this information to dynamically adjust load balancing configurations. The monitoring component tracks packet flow patterns and dropping events, feeds this data back to a configuration system, which then automatically modifies load balancing rules to prevent future dropping, creating a closed-loop control system that continuously optimizes performance while maintaining reliability

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system transitions from static load balancing configurations to dynamic adaptation by automatically adjusting load balancing rules based on real-time traffic patterns and dropping events. The configuration parameters are no longer fixed but are continuously modified in response to changing network conditions, allowing the system to adapt to dynamic traffic demands while preventing packet dropping

Inventive Principle:
Principle #15Dynamics

2Ease of operation

If manual load balancing configuration is used, then configuration simplicity is maintained, but the system cannot automatically adapt to dynamic traffic patterns causing load imbalance

Engineering Contradiction:
Improveconfiguration simplicityVSAvoidautomatic adaptation to traffic patterns
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

The system implements self-service by enabling load balancers to automatically monitor their own performance, detect packet dropping, and trigger reconfiguration without human intervention. The monitoring and configuration components work autonomously to analyze traffic patterns, identify dropping events, and adjust load balancing rules dynamically, allowing the system to self-optimize while maintaining operational simplicity

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system performs preliminary action by proactively monitoring traffic patterns and detecting potential packet dropping events before they significantly impact performance. The configuration system prepares and applies load balancing rule adjustments in advance, based on predicted traffic patterns and historical dropping data, preventing performance degradation before it occurs

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS12363040B2Method and system for dynamic load balancing
Publication Date: 2025.07.15 NETSCOUT SYSTEMS TEXAS LLC
  • US12363040B2 patent drawing
  • US12363040B2 patent drawing
  • US12363040B2 patent drawing

AI summary

A system and method for performing dynamic load balancing in a network load balancer device. A network packet flow is monitored in a load balancer device for detecting dropped network packets, or a sampling of traffic flow, in the monitored network packet flow. Metadata (e.g., a 5-tuple) is created for the detected dropped network packets or sampling of network traffic flow. The metadata is then transmitted to a flow processing analysis device for performing load balancing flow processing. Upon analysis, a determination is made in the flow processing analysis device for determining reconfiguration load balancing settings for the load balancer to mitigate occurrence of unintended dropping of network packets in the load balancer and/or improve its overall performance. The reconfiguration load balancing settings are then transmitted to the load balancer device, whereupon receipt the load balancer changes its settings in accordance with the determined reconfiguration settings.