Black Core Network Failover via Bonding Module

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current Black Core networks face challenges in achieving fault tolerance, high availability, and efficient failover mechanisms, leading to increased costs, latency, and vulnerability to eavesdropping due to the lack of infrastructure support and immature technology.

Innovation Solution

The implementation of cooperative signaling mechanisms, including CT-to-PT Disable, dynamic routing topology updates, and ICMP-DU, along with redundant HAIPE devices and self-healing network topologies, enables rapid failover and self-healing in Black Core networks, ensuring seamless operation and low latency.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If striping techniques are used to achieve fault tolerance in black core networks, then reliability is improved, but device complexity increases

Engineering Contradiction:
Improvefault toleranceVSAvoidnetwork complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The network is segmented into multiple independent paths (primary and secondary paths) that can operate autonomously. Each path is treated as a separate entity with its own routing and failover capabilities, allowing the system to achieve fault tolerance through division rather than complex centralized striping mechanisms.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Alternate paths and failover mechanisms are pre-configured and established before failures occur. The system prepares backup routing paths and failover policies in advance, so when a failure occurs, the transition to redundancy is immediate without requiring complex real-time decision-making or reconfiguration.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If striping techniques are used to achieve fault tolerance, then reliability is improved, but latency increases

Engineering Contradiction:
Improvefault toleranceVSAvoidlatency
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

Failover paths and routing decisions are predetermined and pre-configured. When a failure occurs, the system immediately switches to the pre-established alternate path without requiring complex real-time calculations or negotiations, thereby minimizing latency while maintaining fault tolerance.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If redundant components are used to achieve high availability, then reliability is improved, but device complexity increases

Engineering Contradiction:
Improvehigh availabilityVSAvoidinfrastructure complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The failover mechanism is designed to be universal and applicable across multiple network devices and scenarios. The same failover policy and path selection logic can be applied to different types of network equipment and failure conditions, reducing the need for device-specific complex configurations and enabling high availability through standardized multi-functional approaches.

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

Data Source

PatentUS9491122B2Systems and methods for server and switch failover in a black core network
Publication Date: 2016.11.08 RAYTHEON CO
  • US9491122B2 patent drawing
  • US9491122B2 patent drawing
  • US9491122B2 patent drawing

AI summary

A black core network system and method, wherein the system includes a ciphertext network, a server having a bonding module and a plurality of network interfaces, a plurality of encryptor devices and one or more routers, wherein each router is connected through one or more of the server network interfaces to the server and through one or more encryptor devices to the ciphertext network. The server establishes, in the bonding module, a server gateway for each server network interface, selects a first network interface as primary link and a second server network interface as backup link, and sends routing metric information out through the primary link and the backup link, wherein sending includes sending metric information indicating that the cost of routing through the primary link is less than the cost of routing through the backup link. When the server receives, from one of the one or more routers, an indication that there is a link failure on the primary link, the server manipulates the server gateway for the second server network interface to direct traffic for the primary link out the second server network interface, wherein the second link becomes the new primary link and the server sends routing metric information out through the new primary link to the second router.