Leaf Node Protection in Point-to-Multipoint MPLS-TE Networks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current Point-To-Multipoint Multi-Protocol Label Switching Traffic Engineering (P2MP MPLS-TE) technologies do not enable fast rerouting of packets in the event of a leaf node failure, which is critical for maintaining service quality, especially for services like IPTV, as they require rerouting in less than 50 milliseconds.
Innovation Solution
A method is introduced to protect a point-to-multipoint primary tree in a communications network by configuring backup routing rules that allow packets to be rerouted from an upstream primary branch to a downstream backup branch, minimizing service disruption and maintaining high-quality service even in the event of a primary leaf node failure, with the ability to detect failures quickly and activate backup routing within 50 milliseconds.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If P2MP MPLS-TE Fast Reroute mechanism is used, then link or transit node failures are protected with less than 50 milliseconds rerouting, but leaf node failures cannot be protected
Solution Approach 1:
The patent segments the protection mechanism by introducing a specific type of backup routing rule that operates at the leaf node level rather than requiring full tree-wide protection. This segmentation allows protection to be applied selectively to individual leaf nodes, reducing overall system complexity while providing targeted protection where needed.
Solution Approach 2:
The patent implements preliminary action by pre-configuring backup routing rules that are activated only upon detection of leaf node failure. The backup routing rules are prepared in advance with specific conditions (failure detection) that trigger their activation, enabling rapid response without requiring complex real-time decision-making across the entire network.
2Reliability
If fast rerouting is implemented for leaf node failure, then service quality is maintained, but resource consumption increases
Solution Approach 1:
The patent applies local quality by implementing protection mechanisms only at specific locations (leaf nodes and their directly connected upstream nodes) rather than uniformly across the entire network. The backup routing rules are configured locally at upstream nodes that have direct connections to leaf nodes, allowing resource-efficient protection where it is most needed while leaving other parts of the network unchanged.
Solution Approach 2:
The patent uses partial action by implementing protection for only the critical leaf node failures that require service continuity, rather than providing comprehensive protection for all possible network failures. The backup routing rules are selectively activated only when specific failure conditions are detected, avoiding unnecessary resource consumption during normal operation.
3Productivity
If backup routing rules are configured at upstream nodes, then leaf node failure is protected, but root node intervention is eliminated
Solution Approach 1:
The patent implements self-service by enabling upstream nodes to autonomously detect leaf node failures and activate backup routing rules without requiring root node intervention or centralized control. The upstream nodes perform their own failure detection and routing decisions, making the system self-managing at the edge nodes while reducing the burden on central network controllers.
Solution Approach 2:
The patent uses preliminary action by pre-configuring backup routing rules at upstream nodes with specific activation conditions. When a leaf node failure is detected, the pre-configured rules are automatically activated without requiring real-time computation or root node involvement, enabling rapid response while simplifying centralized management.
Data Source
AI summary
A technique protects, in a communications network, a point-to-multipoint primary tree between a root node and primary leaf nodes of the network if a failure occurs affecting one of the primary leaf nodes. One network node receives from another upstream network node a request to protect the primary tree via a backup branch leading to a backup leaf node situated downstream from said node, if a failure affecting one of the primary leaf nodes to be protected occurs, the backup leaf node being associated with the primary leaf node to be protected. If the node is connected directly to the downstream primary leaf node to be protected, it configures a backup routing rule for routing packets from an upstream primary branch to the downstream backup branch and, possibly, to the downstream primary branch(es) and is activated in the event of a failure affecting the primary leaf node to be protected.