Backup Ingress Node for P2MP LSPs
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current MPLS and GMPLS networks lack a mechanism for efficiently computing and implementing a backup ingress node for Point-to-Multipoint (P2MP) Label Switched Paths, leading to resource consumption and delays in traffic rerouting during node failures, especially in real-time services like IPTV.
Innovation Solution
A method and system for computing and communicating a backup ingress node for P2MP LSPs using the Path Computation Element (PCE) Communication Protocol (PCEP), which allows the PCE to select and inform a backup ingress node without establishing a complete secondary P2MP LSP, reducing resource usage and latency.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a complete secondary P2MP LSP is established for backup, then reliability is improved, but network resource consumption increases
Solution Approach 1:
The patent extracts only the essential backup function from a complete secondary P2MP LSP by implementing a backup ingress node mechanism. Instead of establishing a full redundant P2MP LSP, the system selectively activates a backup ingress node that can take over traffic forwarding when the primary ingress node fails, thereby providing necessary protection while consuming minimal network resources.
Solution Approach 2:
The patent applies local quality by implementing protection only at the critical ingress node level rather than providing redundant protection throughout the entire P2MP LSP path. The backup ingress node is strategically positioned to provide localized protection where it is most needed, reducing overall resource consumption while maintaining reliability for the protected service.
2Reliability
If a complete secondary P2MP LSP is established for backup, then reliability is improved, but device complexity increases
Solution Approach 1:
The patent simplifies device complexity by extracting only the essential backup functionality from a complete secondary P2MP LSP. The system uses a backup ingress node that can be activated on-demand, avoiding the complexity of managing a full redundant P2MP LSP while still providing necessary protection. This reduces the management overhead and computational requirements at network devices.
3Reliability
If traffic rerouting is implemented during node failure, then reliability is maintained, but traffic delays increase
Solution Approach 1:
The patent applies preliminary action by pre-configuring the backup ingress node with necessary forwarding information and state before failure occurs. The backup ingress node is prepared in advance to immediately take over traffic forwarding when the primary ingress node fails, eliminating the need for complex real-time path computation and reducing rerouting latency.
Solution Approach 2:
The backup ingress node is designed to self-activate and self-configure when the primary ingress node fails. It automatically takes over traffic forwarding without requiring complex coordination or re-computation, thereby minimizing disruption and reducing rerouting delays while maintaining reliable packet delivery.
Data Source
AI summary
A method of Path Computation Element (PCE) Communication Protocol (PCEP) communication includes sending, to a path computation element (PCE), a request to compute a backup ingress node for a Point-to-Multipoint (P2MP) Label Switched Path (LSP) in a network, and receiving, from the PCE, the backup ingress node for the P2MP LSP in accordance with the request.