Multicast-Only Fast Reroute With Precomputed Backup Paths
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing multicast Fast Re-Route (FRR) technologies face challenges in managing complex networks with limited computational resources, scalability issues, and dynamic network conditions, leading to delays in rerouting during failures.
Innovation Solution
Implementing a multicast-only Fast Re-Route (MoFRR) mechanism that sends two join messages with distinct upstream paths, marked as primary and backup joins, and encodes information for node differentiation, enabling nodes to identify and diverge paths as needed to minimize data disruption.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional multicast FRR technologies are implemented in complex networks, then path redundancy and fault tolerance are improved, but computational resource consumption and device complexity increase significantly
Solution Approach 1:
The patent segments the multicast FRR mechanism by introducing specific packet types (Join packets, Prune packets, Assert packets) with dedicated functions. Each packet type handles specific aspects of path management, failure detection, or state synchronization, dividing the complex control logic into modular, manageable units that reduce overall computational burden while maintaining reliability
Solution Approach 2:
The patent implements preliminary action by pre-establishing backup paths and pre-configuring fast reroute mechanisms before failures occur. The system proactively sets up alternative multicast paths and pre-computes repair routes, enabling immediate switchover when failures happen without requiring complex real-time computation during actual failure events
2Reliability
If comprehensive monitoring and multiple repair paths are implemented over complex networks, then network reliability is improved, but scalability deteriorates due to increased overhead
Solution Approach 1:
The patent applies universality by designing a unified segment routing framework that handles both monitoring and repair path management through common mechanisms. The same segment routing protocol and packet structures are used for diverse functions including path establishment, failure detection, and repair, allowing the system to scale efficiently while maintaining comprehensive monitoring and multiple repair paths
Solution Approach 2:
The patent implements partial action by selectively applying comprehensive monitoring and multiple repair paths only where needed in the network, rather than uniformly across all nodes. The system can dynamically adjust the level of monitoring and repair path redundancy based on network requirements, enabling scalable deployment from minimal to comprehensive protection levels
3Reliability
If dynamic path adjustments are made during failures, then uninterrupted data transmission is achieved, but rerouting delay increases due to complex real-time computations
Solution Approach 1:
The patent resolves this contradiction by performing all complex path computation and validation activities in advance, before failures occur. Backup paths are pre-computed and validated during normal operation, so when failures happen, the system only needs to execute pre-prepared switchover actions rather than performing real-time computations during the critical failure response window
Solution Approach 2:
The patent applies skipping by enabling the data plane to immediately switch to pre-computed backup paths without waiting for control plane verification or additional computations. The fast reroute mechanism allows traffic to be rapidly redirected along predetermined repair paths, skipping the time-consuming steps of real-time path calculation and validation that would otherwise cause rerouting delays
Data Source
AI summary
In some aspects, a method for establishing a multicast-only Fast Re-Route (FRR) (MoFRR) path between a source node and a receiving node in a network, the method includes receiving, by a merged receiving node, a plurality of data packets in a data flow comprising an FRR indicator, wherein the merged receiving node is configured to identify an FRR path for data transmission to the source node, extracting, by the merged receiving node, from the FRR indicator, an identification of the source node as a destination of the data transmission, and a first identifier identifying a first data packet as part of a first flow of a MoFRR, and a second identifier identifying a second data packet as part of a second flow of a MoFRR, transmitting, by the receiving node, the first data packet along a primary data path and the second data packet along a secondary data path.