mRSVP-TE Fast Reroute for Facility Mode Multicast Protection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
MPLS networks employing sender-driven RSVP-TE fast reroute protocols are not interoperable with receiver-driven mRSVP-TE, leading to challenges in providing millisecond-level protection for multicast traffic in case of node or link failures, especially in facility mode where a single backup LSP is required to protect multiple primary LSPs.
Innovation Solution
The implementation of a method and apparatus that supports fast rerouting for multicast traffic in MPLS networks using mRSVP-TE in facility mode, where a backup LSP is established to protect multiple primary LSPs, involving the transmission of PATH and RESV messages to reserve resources, allocate labels, and encapsulate data for rerouting, ensuring seamless data flow during failures.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If sender-driven RSVP-TE fast reroute protocols are used, then millisecond-level protection can be achieved, but interoperability with receiver-driven mRSVP-TE is lost
Solution Approach 1:
The patent inverts the traditional sender-driven RSVP-TE fast reroute mechanism to work with receiver-driven mRSVP-TE. Instead of the sender initiating backup LSP setup, the receiver (merge point) initiates the backup LSP establishment by sending PATH messages upstream to the PLR, enabling interoperability while maintaining fast reroute capabilities
Solution Approach 2:
The patent introduces an intermediary mechanism where the merge point acts as a mediator between the receiver-driven mRSVP-TE protocol and the fast reroute functionality. The merge point receives multicast traffic requests, establishes backup LSPs, and coordinates with PLRs to ensure seamless failover, bridging the gap between receiver-driven signaling and fast protection
2Quantity of substance
If a single backup LSP is used to protect multiple primary LSPs, then resource efficiency is improved, but protocol complexity increases
Solution Approach 1:
The patent implements facility mode 1:N protection where a single backup LSP serves multiple primary LSPs simultaneously. The backup LSP is established once and can be activated to protect any of the N primary LSPs, reducing resource consumption while the patent manages the complexity through standardized mRSVP-TE signaling procedures
Solution Approach 2:
The patent establishes backup LSPs in advance before failures occur. The merge point proactively sets up backup paths and reserves resources ahead of time, allowing immediate activation upon failure detection. This preliminary action simplifies the failure response protocol while efficiently utilizing network resources
3Adaptability or versatility
If backup LSP setup is initiated by merge point, then receiver-driven protocol compatibility is achieved, but signaling overhead increases
Solution Approach 1:
The patent enables the receiver (merge point) to self-initiate backup LSP establishment without requiring additional sender-driven signaling. The merge point autonomously determines the need for backup paths and initiates PATH messages to set up protection, reducing signaling overhead while maintaining receiver-driven protocol compatibility
Data Source
AI summary
An apparatus comprising a memory, and a processor coupled to the memory and configured to transmit a backup Label Switched Path (LSP) multicast Resource Reservation Protocol-Traffic Engineering (mRSVP-TE) path request (PATH) message upstream, wherein the backup LSP PATH message requests reservation of a first backup LSP to protect a first primary LSP configured to transmit multicast data, and wherein the backup LSP PATH message is transmitted to support a facility mode one to many (1:N) fast reroute protocol.