Multiple Routing Configurations for Fast Network Recovery
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current network routing protocols face challenges in quickly recovering from node or link failures, leading to routing instability and packet loss due to slow convergence times, especially in real-time applications, as most failures are short-lived and require rapid reconfiguration.
Innovation Solution
The implementation of Multiple Routing Configurations (MRC) allows for proactive and local recovery by creating a set of backup configurations with manipulated link weights, enabling immediate rerouting around failed nodes and links without global reconfiguration, ensuring almost continuous packet forwarding and suppressing the re-convergence process.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional IGP routing protocols are used for network failure recovery, then routing information is updated based on changed topology, but convergence time is too long causing routing instability and packet loss
Solution Approach 1:
The patent pre-calculates and stores multiple backup routing configurations (first backup configuration, second backup configuration, etc.) before failures occur. When a link failure is detected, the system immediately switches to a pre-computed backup configuration rather than performing real-time recalculations, thereby achieving fast convergence without routing instability
Solution Approach 2:
The patent divides the routing configuration into multiple independent backup configurations, each optimized for specific failure scenarios. Instead of updating the entire routing table globally, only the affected routing entries are switched to corresponding backup configurations, reducing the scope and time of reconfiguration
2Reliability
If rapid reconfiguration is triggered for every failure to improve recovery speed, then failure recovery is faster, but route flapping and network instability increase
Solution Approach 1:
Multiple backup routing configurations are pre-calculated and stored in advance for different failure scenarios. When a failure occurs, the system checks whether a suitable backup configuration exists and switches to it immediately, avoiding the need for rapid repeated reconfigurations and preventing route flapping
Solution Approach 2:
The system monitors link status and failure patterns, and only triggers configuration switching when actual failures are detected. The feedback mechanism prevents unnecessary switching and allows the system to adapt to transient failures by suppressing reconfiguration triggers, thereby maintaining routing stability
3Reliability
If global reconfiguration is performed to ensure complete failure recovery, then all routing paths are updated, but the process is too slow for real-time applications
Solution Approach 1:
The patent segments the routing configuration into multiple independent backup configurations, each handling specific failure scenarios. Only the affected routing entries need to be switched rather than performing a complete global reconfiguration, dramatically reducing reconfiguration time while ensuring complete failure recovery
Solution Approach 2:
Backup routing configurations are pre-calculated and stored in advance for various failure scenarios. When failures occur, the system immediately switches to appropriate pre-computed configurations without performing real-time global recalculations, achieving both completeness and speed
Data Source
Figure 1~3
Figure 4~5
Figure 6~8
AI summary
A network comprises nodes (1, 2, 3, 4, 5, 6) and links. In addition to a default topology there are backup configurations. Each node is inhibited from transferring data between nodes in at least one backup configuration. When a node detects a fault in the reception of data transmitted to a neighbouring node, it switches to a backup configuration in which the neighbouring node is inhibited. In one arrangement a backup configuration has at least one link (3-5; 4-5; 6-5) which is restricted by having a high weighting so that it transmits data to a node only if that node is the final destination node for that data. Additionally, if the neighbouring node is the final destination, and routing of data is still unsuccessful in the backup configuration, the detecting node selects and switches to an alternate backup configuration in which the detecting node is inhibited.