Traffic Management Systems Failure Tolerance via Shared IP Pool

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing traffic management systems face challenges in efficiently handling failures, leading to potential service disruptions and inefficient load balancing when traffic managers become inoperative, as current solutions like slave traffic managers or active/standby setups can be costly and prone to faults.

Innovation Solution

Each functional traffic management system periodically signals its availability to others, maintains configuration data specifying address responsibilities, and automatically takes over responsibilities for network addresses when a system fails, using a transition table to ensure seamless IP address reassignment and balanced workload distribution.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If slave traffic managers are included for each operational traffic manager, then service continuity is improved during failures, but system cost and complexity increase

Engineering Contradiction:
Improveservice continuityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

Multiple traffic managers share a common pool of IP addresses rather than each having dedicated backup resources. The system merges the address management functions into a collective resource pool that any operational traffic manager can access, reducing overall system complexity while maintaining service continuity.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

Traffic managers automatically detect failures through periodic signals and self-reconfigure by taking over addresses from failed managers without requiring manual intervention or complex centralized control. The system performs its own failure response actions, reducing the need for additional control infrastructure.

Inventive Principle:
Principle #25Self-service

2Productivity

If addresses are shared out evenly among traffic managers, then workload distribution is improved, but failure response becomes complex requiring elections between systems

Engineering Contradiction:
Improveworkload distributionVSAvoidfailure response complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system pre-associates each traffic manager with specific IP addresses in the shared pool before failures occur. When a failure happens, the reconfiguration follows predetermined rules based on these associations, eliminating the need for complex real-time elections or decision-making processes during failure response.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system changes the state parameter of IP addresses from being statically bound to specific traffic managers to being dynamically assignable from a shared pool. This parameter change enables flexible workload distribution while simplifying failure response through automatic reassignment based on operational status.

Inventive Principle:
Principle #35Parameter changes

3Reliability

If traffic managers periodically signal availability, then failure detection is improved, but network traffic and system overhead increase

Engineering Contradiction:
Improvefailure detectionVSAvoidnetwork overhead
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

Traffic managers send periodic availability signals rather than continuous streams, reducing network overhead while maintaining effective failure detection. The periodic nature of these signals balances the need for timely failure awareness with the cost of network communication.

Inventive Principle:
Principle #19Periodic action

Solution Approach 2:

The periodic signals serve multiple functions simultaneously: they confirm operational status, provide a mechanism for failure detection, and can carry address assignment information. This multi-functionality reduces the need for separate communication channels and minimizes overall network overhead.

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

Data Source

PatentUS7523178B2Tolerating failure of traffic management systems
Publication Date: 2009.04.21 PULSE SECURE LLC
  • US7523178B2 patent drawing
  • US7523178B2 patent drawing
  • US7523178B2 patent drawing

AI summary

Failures are tolerated in an environment in which a plurality of traffic management systems are coordinated to manage the supply of data to and from a plurality of clients via a plurality of network addresses. Each functional traffic management system is responsible for at least one network address, and each functional traffic management system periodically transmits a signal to each of the other traffic management systems to confirm functionality. Each of the traffic management systems creates and maintains configuration data that specifies the responsibility of traffic management systems for network addresses dependent upon the status of each of the traffic management systems. Each of the traffic management systems responds to a failure of any of the traffic management systems by taking responsibility for certain network addresses as prescribed by the configuration data.