Ingress Router Load Balancing via Dynamic IP Mapping

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current network management tools are inadequate for effectively controlling incoming traffic, leading to manual, error-prone, and unstable methods that fail to predictably manage load balancing and avoid congestion.

Innovation Solution

A method and system that monitor the loads of multiple ingress routers, select the most appropriate router based on load, and create a mapping between internal and client IP addresses to rewrite destination IP addresses, ensuring efficient traffic routing and load balancing.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual methods are used to control incoming traffic, then operators can implement basic traffic control, but the methods become error-prone, unstable, and unpredictable

Engineering Contradiction:
Improvetraffic control stabilityVSAvoidmanual configuration complexity
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The system enables automated self-service traffic control where the network infrastructure automatically monitors router loads, selects appropriate ingress routers, creates IP address mappings, and rewrites destination addresses without manual intervention. This eliminates human errors and provides stable, predictable traffic control outcomes.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system continuously monitors the loads of ingress routers and uses this feedback information to dynamically select the most appropriate router for incoming traffic. This closed-loop feedback mechanism ensures stable and adaptive traffic control that responds to changing network conditions.

Inventive Principle:
Principle #23Feedback

2Adaptability or versatility

If existing protocols are used to control outgoing traffic, then outgoing traffic can be managed, but systematic control of incoming traffic remains lacking

Engineering Contradiction:
Improveincoming traffic control capabilityVSAvoidsystem architecture complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system introduces an intermediary mechanism that sits between incoming traffic and the network core. This intermediary performs load monitoring, router selection, IP mapping creation, and destination address rewriting, providing systematic incoming traffic control without requiring changes to existing router protocols or architectures.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The traffic control functionality is segmented into distinct operational components: load monitoring, router selection, IP mapping management, and address rewriting. This segmentation allows each component to be optimized independently while working together to provide comprehensive incoming traffic control capability.

Inventive Principle:
Principle #1Segmentation

3Reliability

If traffic is distributed across multiple ingress routers, then network reliability improves, but load balancing becomes difficult to control

Engineering Contradiction:
Improvenetwork redundancyVSAvoidtraffic flow efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system implements dynamic load balancing by continuously monitoring router loads and adapting traffic distribution in real-time. The IP address mappings and destination rewrites are dynamically adjusted based on current router conditions, ensuring both network reliability through multiple paths and optimal traffic flow efficiency through load-aware routing.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS10680953B2Controlling incoming traffic
Publication Date: 2020.06.09 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US10680953B2 patent drawing
  • US10680953B2 patent drawing
  • US10680953B2 patent drawing

AI summary

A method and system are provided for controlling a volume of incoming traffic into a network having a plurality of ingress routers. The method includes monitoring respective loads of the plurality of ingress routers. The method further includes selecting a particular one of the plurality of ingress routers to receive future incoming traffic based on at least the respective loads of the plurality of ingress routers. The method also includes creating a mapping between an internal source IP address and a client IP address. The internal source IP address relates to the particular one of the plurality of routers. The client IP address is for a client device accessing the Internet through the network. The method additionally includes rewriting a destination IP address of the incoming traffic based on the mapping. At least the monitoring, selecting, and creating steps are performed by a controller.