Flowpac Traffic Balancing for Granular Network Path Switching
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing traffic balancing methods in data center networks struggle to achieve dynamic load balancing at a sufficient granularity, leading to inefficiencies such as congestion and packet disorder due to hash collisions and inconsistent path utilization.
Innovation Solution
The implementation of flowpacs, where packets are grouped into collections based on destination nodes and network balancing parameters, allowing for dynamic control of path switching based on the flowpac classification, ensuring packets in the same flowpac use the same path and those in different flowpacs use different paths.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If conventional traffic balancing methods are used, then path selection is simplified, but dynamic load balancing at sufficient granularity cannot be achieved
Solution Approach 1:
The patent segments traffic into flowpacs (flow packets) based on destination nodes and network balancing parameters. Each flowpac is independently classified and routed, enabling fine-grained dynamic load balancing. This segmentation allows the system to achieve adaptability by treating different flowpacs differently, while the classification mechanism manages complexity through structured organization.
Solution Approach 2:
The patent implements dynamic path switching by classifying flowpacs based on real-time network balancing parameters. The path selection is not static but adapts dynamically based on the classification results, allowing the system to respond to changing network conditions while maintaining controlled complexity through the classification framework.
2Productivity
If packets are routed individually without flowpac classification, then routing flexibility is maximized, but congestion and packet disorder occur due to hash collisions
Solution Approach 1:
By segmenting packets into flowpacs with consistent hashing based on destination nodes, the patent ensures that packets within each flowpac follow the same path, preventing packet disorder.同时，the segmentation enables better bandwidth utilization by distributing different flowpacs across multiple paths, avoiding hash collisions while maintaining reliability.
Solution Approach 2:
The patent applies different routing qualities to different flowpacs based on their classification. Packets within the same flowpac receive consistent path treatment (same quality), while different flowpacs may receive different path assignments. This local quality approach ensures packet order within flows while achieving overall load balancing and bandwidth utilization.
3Measurement precision
If path switching granularity is too fine, then load balancing precision is improved, but system overhead increases
Solution Approach 1:
The patent segments traffic into flowpacs at an appropriate granularity level, neither too fine nor too coarse. This segmentation achieves load balancing precision by classifying based on destination nodes and network parameters, while the flowpac structure itself manages overhead by grouping packets that share the same routing characteristics.
Solution Approach 2:
The patent changes the classification parameters from simple hash-based routing to multi-parameter flowpac classification based on destination nodes and network balancing parameters. This parameter change improves load balancing precision by considering multiple factors, while the structured classification approach manages the complexity overhead through systematic parameter evaluation.
Data Source
Figure 1~2
Figure 3
Figure 4
AI summary
This application provides a traffic balancing method, a network device, and an electronic device, and relates to the field of communications technologies. The network device includes: a first module, configured to obtain a to-be-sent packet; a second module, configured to create or maintain flowpacs, and classify the to-be-sent packet into a corresponding flowpac based on a destination node; and a third module, configured to send the to-be-sent packet based on the flowpac to which the to-be-sent packet belongs; where one flowpac includes at least one packet, and packets belonging to a same flowpac have a same destination node and a same sending path.