Network Flow State Migration for Hardware Load Balancing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing network communication systems face challenges with static load balancing and resiliency, leading to network performance degradation and asymmetrical traffic distribution, which are not effectively addressed by current algorithmic approaches.

Innovation Solution

Implementing hardware-supported flow migration by migrating network references such as 5-tuples or QPs between network hardware, using commands like suspend, save, and load flow to dynamically balance load and ensure resiliency without interrupting applications.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If algorithmic load balancing approaches are used, then network resiliency is improved, but network performance and traffic distribution symmetry deteriorate

Engineering Contradiction:
Improvenetwork resiliencyVSAvoidnetwork performance
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent replaces software-based algorithmic load balancing with hardware-based flow migration mechanisms. Network hardware (switches, routers, gateways) directly migrates flow states between forwarding engines using hardware registers and memory structures, eliminating the need for complex software algorithms. This substitution maintains high network performance while providing resiliency through hardware-level failover capabilities.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

Solution Approach 2:

The patent introduces flow state structures as intermediaries between network flows and forwarding engines. These flow states contain all necessary information (5-tuples, QPs, configuration data) to enable rapid migration of network flows between different hardware components. The intermediary flow state mechanism allows seamless load balancing and failover without performance degradation.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of manufacture

If static load balancing algorithms are used, then implementation simplicity is improved, but traffic distribution symmetry and adaptability deteriorate

Engineering Contradiction:
Improveimplementation simplicityVSAvoidtraffic distribution symmetry
Core Design Contradiction:
Ease of manufactureVSAdaptability or versatility

Solution Approach 1:

The patent implements dynamic load balancing through hardware-supported flow migration that automatically adapts to changing network conditions. Flow states can be migrated between forwarding engines based on real-time load conditions, link status, and failover requirements. This dynamic approach maintains traffic distribution symmetry while providing adaptability to various network scenarios without complex algorithms.

Inventive Principle:
Principle #15Dynamics

3Reliability

If flow migration between network hardware is implemented, then dynamic load balancing and resiliency are improved, but hardware complexity increases

Engineering Contradiction:
Improvenetwork resiliencyVSAvoidhardware complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements universal flow state structures that can be used across different network hardware platforms and forwarding engines. The flow state format (containing 5-tuples, QPs, and configuration data) is standardized and platform-independent, allowing seamless migration between different hardware components. This universality reduces overall system complexity by providing a common interface for flow management across diverse hardware.

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

Solution Approach 2:

The patent uses flow state copying mechanisms where complete flow information is replicated between forwarding engines during migration. Instead of complex pointer-based references, the system creates accurate copies of flow states containing all necessary data. This copying approach simplifies the migration process and reduces hardware complexity by eliminating the need for complex shared memory management and synchronization mechanisms.

Inventive Principle:
Principle #26Copying

4Productivity

If hardware-supported flow migration is used, then network performance is maintained during failover, but device complexity and implementation difficulty increase

Engineering Contradiction:
Improvenetwork performanceVSAvoiddevice complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent pre-allocates flow state storage structures and establishes forwarding rules in hardware registers before failures occur. Flow states are maintained in dedicated memory regions with pre-configured migration paths and target forwarding engines. This preliminary preparation enables instantaneous failover and performance maintenance without complex runtime decision-making or algorithmic processing.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent replaces complex software-based flow management and migration algorithms with hardware-level mechanisms including dedicated registers, memory structures, and control logic implemented in ASICs or FPGAs. This mechanical substitution at the hardware level maintains network performance during failover while reducing the complexity of software implementation by embedding migration capabilities directly in the network hardware.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

Data Source

PatentUS20250358181A1Hardware supported flow migration
Publication Date: 2025.11.20 MELLANOX TECHNOLOGIES LTD(IL)
  • US20250358181A1 patent drawing
  • US20250358181A1 patent drawing
  • US20250358181A1 patent drawing

AI summary

Systems and methods herein are for at least one circuit that can determine that a network reference associated with a first network hardware is subject to a network performance degradation in a network, can cause suspension of traffic flow associated with the network reference, can save configuration for at least the network reference at a node associated with the first network hardware, and can cause the configuration to be deployed in a second network hardware so that the network reference that was previously in the first network hardware is provided from the second network hardware to resume the traffic flow.