Controller-Based Protected Load Balancing for Network Traffic
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional load balancing methods in communication networks fail to efficiently utilize bandwidth and protect traffic from failures, leading to potential traffic loss and high bandwidth utilization on certain links, especially when failures occur.
Innovation Solution
A centralized solution for protected load balancing is introduced, where a controller configures network nodes to split traffic across multiple paths of a tunnel, anticipating potential failures by setting 'safe' split ratios and bandwidth thresholds, allowing for zero traffic loss by dynamically adjusting load balancing configurations and bandwidth reservations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Use of energy by moving object
If traffic is load balanced over multiple paths using conventional methods, then bandwidth utilization is improved, but traffic protection against failures is insufficient leading to potential traffic loss
Solution Approach 1:
The controller pre-calculates and configures safe load balancing weights that guarantee traffic protection before failures occur. By anticipating potential failures and pre-configuring appropriate weight distributions, the system ensures that traffic can be safely rerouted without loss when failures happen, resolving the contradiction between bandwidth utilization and traffic protection.
Solution Approach 2:
The system continuously monitors traffic status and failure conditions, then dynamically adjusts load balancing weights in response to detected failures. This feedback mechanism ensures that when a failure occurs, the controller can reconfigure the load balancing to protect traffic while maintaining optimal bandwidth utilization across remaining paths.
2Reliability
If bandwidth reservations are made for each backup path in conventional protected load balancing, then traffic protection is improved, but bandwidth efficiency deteriorates due to redundant reservations
Solution Approach 1:
The system merges the functions of multiple backup paths into a single shared backup resource. Instead of making separate bandwidth reservations for each potential failure scenario, the controller dynamically allocates a shared backup bandwidth that can be flexibly redirected to any failed path. This eliminates redundant reservations while maintaining comprehensive traffic protection.
Solution Approach 2:
The load balancing weights and bandwidth allocations are made dynamic rather than static. The controller continuously adjusts the weight distribution based on current network conditions and failure states, allowing the same bandwidth resource to serve multiple protection purposes. This dynamic approach replaces static redundant reservations with efficient adaptive resource sharing.
3Ease of operation
If load balancing weights are fixed once decided, then implementation simplicity is improved, but adaptability to failures and changing network conditions deteriorates
Solution Approach 1:
The system implements dynamic load balancing weights that automatically adjust in response to failures and changing network conditions. The controller continuously monitors the network state and reconfigures weights as needed, transforming the static implementation into an adaptive system that maintains both simplicity through automation and high adaptability to various failure scenarios.
Data Source
AI summary
A controller is configured to obtain traffic information of one or more tunnels in the network, where the traffic information of each tunnel is indicative of a protection type of the tunnel against failures, and provide configuration information to each network node that is a head-end node of a determined tunnel with a certain protection type according to the obtained traffic information of the determined tunnel, where the configuration information includes a bandwidth threshold and a load balancing configuration for the determined tunnel. A network node is configured to receive configuration information from the controller, and send the notification to the controller, if it is determined that the traffic of the tunnel is above the bandwidth threshold.