P2MP Backup LSP Local Protection for MPLS Networks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional Internet Gateway Protocol (IGP)-mLDP convergence mechanisms fail to meet the required protection switching times for real-time applications, leading to potential interruptions in services like stock trading, online games, and multimedia teleconferencing, as they often rely on redundant dual-feeding Point-to-Point (P2P) methods that consume significant bandwidth and cause performance degradation.
Innovation Solution
Implementing a Point-to-Multipoint (P2MP) based Label Distribution Protocol (LDP) local protection solution that establishes a backup LSP, allowing nodes to distinguish between primary and backup LSPs, and enables local merging of traffic back to the primary path, thereby avoiding redundant P2P methods and reducing bandwidth overload.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If conventional IGP-mLDP convergence mechanisms use redundant dual-feeding P2P methods for protection switching, then network reliability is improved, but bandwidth consumption increases and performance degradation occurs
Solution Approach 1:
The patent merges multiple P2P backup LSPs into a single P2MP backup LSP that serves multiple downstream nodes. The upstream LSR establishes one backup LSP that branches to multiple merge points, eliminating the need for separate backup paths to each node. This consolidation reduces bandwidth consumption while maintaining protection capability across the network segment.
Solution Approach 2:
The P2MP backup LSP serves multiple functions simultaneously: it provides protection to multiple downstream nodes through a single path, enables efficient bandwidth utilization by avoiding redundant transmissions, and maintains fast convergence capability. The single backup LSP structure universally protects all downstream nodes affected by the failed primary LSP.
2Device complexity
If conventional IGP-mLDP convergence mechanisms are used for protection switching, then device complexity is reduced, but protection switching time increases causing application interruptions
Solution Approach 1:
The backup LSP is pre-established and pre-configured before any failure occurs. The upstream LSR and downstream LSRs prepare the backup path in advance with all necessary label mappings and forwarding states. When a failure is detected, the switch to the pre-prepared backup LSP occurs immediately without requiring complex real-time computation or path establishment, thus achieving fast convergence.
Solution Approach 2:
The protection mechanism is segmented into distinct functional components: the upstream LSR that detects failures and initiates switching, the backup LSP that provides the alternative path, and the downstream LSRs that execute local merging. This segmentation allows each component to perform its function efficiently with minimal complexity, while the overall system achieves fast protection switching.
3Reliability
If redundant dual-feeding P2P backup LSPs are established for each downstream node, then network reliability is improved, but device complexity and bandwidth consumption increase
Solution Approach 1:
Multiple P2P backup LSPs that would individually protect each downstream node are merged into a single P2MP backup LSP structure. The upstream LSR creates one backup LSP that naturally branches to multiple downstream nodes, eliminating the need to manage separate backup paths for each node. This reduces LSP management complexity while maintaining comprehensive protection coverage.
Data Source
AI summary
In one aspect, the disclosure includes an apparatus comprising a processor configured to function as a merge point (MP) in a point to multi-point (P2MP) backup label switching path (LSP) for a primary LSP, receive P2MP backup LSP information originating from a protected node, wherein the P2MP backup LSP information comprises the identity of a point of local repair (PLR), determine a backup label switching router (LSR), and send a message with the identity of the backup LSR to an upstream node.


