Dynamic Load Balancing Using Backup Paths in Virtual Private Networks

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing network traffic load balancing solutions in Metro Ethernet Networks (MEN) primarily focus on primary paths and do not effectively utilize backup or protection paths for optimization, leading to inefficiencies in resource utilization and traffic distribution.

Innovation Solution

The system dynamically adjusts traffic distribution between primary and backup paths based on detected delays, allowing backup paths to carry part of the network traffic load even during non-protection events, using a novel method of assigning virtual circuit labels and optimizing backup path usage for load balancing.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traffic is routed only through primary paths, then network reliability is maintained for protection events, but resource utilization efficiency deteriorates due to underutilized backup paths

Engineering Contradiction:
Improvenetwork reliabilityVSAvoidresource utilization efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The backup path is designed to serve dual functions: it acts as a protection path for reliability during failures and simultaneously as a load-bearing path for improving resource utilization during normal operation. This multi-functionality resolves the contradiction by allowing the same infrastructure to meet both reliability requirements and efficiency goals.

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

Solution Approach 2:

The system dynamically adjusts traffic distribution between primary and backup paths based on real-time conditions. During normal operation, traffic is distributed to both paths to optimize utilization; during protection events, traffic is automatically redirected to the backup path to maintain reliability. This dynamic behavior resolves the contradiction by adapting to different operational states.

Inventive Principle:
Principle #15Dynamics

2Reliability

If backup paths are reserved exclusively for protection events, then network protection capability is ensured, but network performance optimization deteriorates due to idle backup capacity

Engineering Contradiction:
Improvenetwork protection capabilityVSAvoidnetwork performance optimization
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

Instead of reserving 100% of backup path capacity exclusively for protection events, the system uses partial action by allowing the backup path to carry a portion of normal traffic load. This partial utilization of backup capacity for both protection and load-bearing purposes improves network performance optimization while maintaining adequate protection capability.

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

The system changes the operational parameter of the backup path from a static 'protection-only' state to a dynamic state where it can operate in both protection mode and load-bearing mode. This parameter change allows the backup path to contribute to network performance optimization during normal operation while maintaining its protection function.

Inventive Principle:
Principle #35Parameter changes

3Productivity

If load balancing utilizes both primary and backup paths, then resource utilization efficiency improves, but system complexity increases due to dynamic traffic distribution management

Engineering Contradiction:
Improveresource utilization efficiencyVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system employs feedback mechanisms where network nodes continuously monitor traffic conditions, path status, and performance metrics. Based on this feedback, the system automatically adjusts traffic distribution between primary and backup paths. This feedback-driven approach manages the complexity by using decentralized, rule-based decisions rather than centralized complex optimization algorithms.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The network nodes autonomously perform load balancing decisions and traffic distribution adjustments without requiring external centralized control. Each node independently evaluates local conditions and makes routing decisions, which reduces overall system complexity by distributing the intelligence and eliminating the need for complex centralized management infrastructure.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS7660241B2Load balancing in a virtual private network
Publication Date: 2010.02.09 RPX CORP
  • US7660241B2 patent drawing
  • US7660241B2 patent drawing
  • US7660241B2 patent drawing

AI summary

A network system (10). The system comprises a plurality of nodes (PE, CE). Each node in the plurality of nodes is coupled to communicate with at least one other node in the plurality of nodes. Further, each node in the plurality of nodes is coupled to communicate to another node via a respective primary path and via a respective backup path. Still further, each node in the plurality of nodes is operable to perform the steps of, when receiving network traffic as a receiving node, detecting delay (110, 120; 130, 140; 160, 170) in traffic received from a transmitting node, and, in response to detecting delay, communicating a signal to the transmitting node. In response to the signal, the transmitting node is operable to dynamically adjust (150; 190) a distribution of traffic through a respective primary path and a respective backup path from the transmitting node to the receiving node.