Load Balancer ECN Feedback for Congestion-Aware Traffic Routing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional load balancers in cloud environments do not consider network congestion when distributing traffic among nodes, leading to reduced quality of service due to network overload, which is typically handled by applications within the data center.

Innovation Solution

A load balancer that detects network congestion through Explicit Congestion Notification (ECN) data and selects application instances based on their hardware capabilities to reduce network congestion without degrading the quality of experience, using more efficient encoding capabilities when congestion is detected.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If conventional load balancers distribute traffic based on monitored load on worker nodes, then application availability and responsiveness are improved, but network congestion is not considered leading to reduced quality of service

Engineering Contradiction:
Improveapplication availabilityVSAvoidnetwork congestion
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The load balancer implements feedback by continuously monitoring ECN (Explicit Congestion Notification) markers in network packets to detect congestion conditions. This feedback loop allows the system to adjust traffic distribution dynamically based on actual network state, resolving the contradiction between maintaining application availability and avoiding network congestion.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system changes the parameter used for load balancing decisions from purely application-level load metrics to include network-level congestion indicators (ECN markers). This parameter change enables the load balancer to respond to network conditions and prevent congestion while maintaining service availability.

Inventive Principle:
Principle #35Parameter changes

2Reliability

If load balancers route jobs to nodes with reduced load, then server overloads are prevented, but network congestion between data center and external networks is not addressed

Engineering Contradiction:
Improveserver overload preventionVSAvoidnetwork bandwidth usage
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The load balancer uses ECN feedback from the network to adjust traffic routing decisions. When congestion is detected, the system routes traffic to application instances that can process requests more efficiently, thereby reducing network bandwidth consumption while still preventing server overloads.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system incorporates network congestion status as an additional parameter in load balancing decisions. This enables the system to select not just any available server, but specifically those that will minimize network bandwidth usage under congested conditions, addressing both server overload prevention and network efficiency.

Inventive Principle:
Principle #35Parameter changes

3Speed

If application instances process work with standard encoding capabilities, then processing speed is maintained, but bandwidth usage increases during network congestion

Engineering Contradiction:
Improveprocessing speedVSAvoidbandwidth usage
Core Design Contradiction:
SpeedVSLoss of energy

Solution Approach 1:

The system applies local quality by selecting specific application instances with enhanced encoding capabilities (such as GPU-accelerated instances) for processing tasks during network congestion. This localized optimization allows faster processing that generates less bandwidth-consuming output, resolving the contradiction between processing speed and bandwidth usage.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The system changes the hardware capability parameter of selected application instances based on network conditions. During congestion, it selects instances with superior encoding hardware (GPU/FPGA) that can process data more efficiently and produce smaller output, thereby maintaining processing speed while reducing bandwidth consumption.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS12388754B2Reducing network congestion using a load balancer
Publication Date: 2025.08.12 TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
  • US12388754B2 patent drawing
  • US12388754B2 patent drawing
  • US12388754B2 patent drawing

AI summary

Reducing network congestion using a load balancer is described. The load balancer receives network traffic for processing work for a delay-sensitive application. The load balancer is coupled with multiple application instances executing on compute nodes that are each capable of processing the work. The load balancer determines from the network traffic whether there is an indication of network congestion. If there is an indication of network congestion, the load balancer selects one of the application instances for processing the work based at least in part on reducing the network congestion. The load balancer causes the work to be processed at the selected application instance.