Inter-domain Fast Reroute via Cross-Domain Backup Next Hops
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing IP fast reroute technologies are limited to intra-domain routing, where both primary and backup next hops are within the same domain, and use a single routing protocol, which restricts their applicability and effectiveness in inter-domain scenarios.
Innovation Solution
The development of network devices and methods that enable inter-domain fast reroute by allowing a backup next hop to exist in a different network domain than its corresponding primary next hop, using different routing protocols if necessary, to provide a loop-free alternate path during network failures.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If IP fast reroute is limited to intra-domain routing with a single routing protocol, then the implementation is simpler and more manageable, but the applicability and effectiveness are restricted in inter-domain scenarios
Solution Approach 1:
The patent segments the fast reroute functionality into separate control plane modules, with each module responsible for a specific network domain. This modular architecture allows independent management of different domains while maintaining overall system coherence, thereby enabling inter-domain applicability without proportionally increasing complexity.
Solution Approach 2:
The control plane is designed with universal fast reroute capabilities that can operate across multiple network domains and routing protocols. The system provides a unified interface and consistent behavior for fast reroute operations whether within a single domain or across multiple domains, enhancing adaptability without requiring completely separate implementation for each scenario.
2Reliability
If routing protocols have long convergence times following network topology changes, then thorough routing information gathering is achieved, but significant data loss occurs during the convergence period
Solution Approach 1:
The system performs preliminary computation of backup next hops and pre-configures fast reroute paths before network failures occur. By having backup paths pre-computed and ready, the system can immediately switch to alternative routes upon failure detection, preventing data loss without waiting for routing protocol convergence.
Solution Approach 2:
The invention introduces a fast reroute mechanism that acts as an intermediary between the control plane and data plane during network failures. This intermediary layer provides temporary backup paths that bridge the gap during routing protocol convergence, ensuring continuous traffic flow and preventing data loss while the main routing protocols complete their convergence process.
3Adaptability or versatility
If backup next hops are pre-computed within the same domain as primary next hops, then the fast reroute implementation is straightforward, but the solution is inadequate for inter-domain routing scenarios
Solution Approach 1:
The patent extends the fast reroute capability from a single-domain dimension to a multi-domain dimension. By allowing backup next hops to be located in different network domains than their corresponding primary next hops, the system adds the dimension of cross-domain routing to fast reroute operations, enabling inter-domain applicability while managing complexity through modular control plane design.
Data Source
AI summary
A network device, is to be deployed in a network between a first network domain and a second network domain, and is to be configured for fast reroute. The network device includes a first traffic forwarder control module, corresponding to the first network domain, which is to determine a primary next hop in the first network domain. The control plane includes a second traffic forwarder control module, corresponding to the second network domain, which is to determine a backup next hop in the second network domain. The backup next hop is to be used as a fast reroute for the primary next hop in response to a failure associated with the primary next hop. The control plane includes a controller module, in communication with the first and second traffic forwarder control modules, which is to configure a forwarding structure of the forwarding plane with the primary and backup next hops.