Dynamic P2MP LSP Leaf Node Management via Encapsulated Requests
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current solutions for dynamically provisioning and managing Point-to-Multipoint (P2MP) Label Switched Paths (LSPs) using RSVP-TE lack mechanisms for dynamically adding or removing leaf nodes, requiring manual configuration and heavy overhead, which is not supported by open standard protocols.
Innovation Solution
A method and system that allows leaf nodes to request updates to multicast groups by encapsulating join or leave requests within pre-configured tunnels, enabling dynamic addition or removal of nodes from P2MP LSPs using RSVP-TE, without specifying destination addresses, and allowing root nodes to manage membership and establish or terminate P2MP LSPs as needed.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If RSVP-TE is used to establish P2MP LSP with Traffic Engineering parameters, then network performance and Quality of Experience are optimized, but manual configuration overhead increases and dynamic leaf node addition/removal becomes impossible
Solution Approach 1:
The patent enables leaf nodes to autonomously detect when they need to join or leave a multicast group and automatically trigger the addition or removal process without requiring manual configuration. The root node receives join/leave requests from leaf nodes and automatically updates the P2MP LSP tree structure, eliminating the need for operators to manually configure each leaf node's participation status.
Solution Approach 2:
The patent transforms the static P2MP LSP configuration into a dynamic system where leaf nodes can be added or removed in real-time based on their multicast group membership status. The system continuously monitors leaf node status changes and automatically updates the LSP tree structure, allowing the network to adapt dynamically to changing requirements without recalculating the entire tree.
2Ease of operation
If mLDP is used for dynamic leaf node joining/leaving, then ease of operation improves, but Traffic Engineering parameters cannot be provisioned
Solution Approach 1:
The patent combines the dynamic membership management capabilities of mLDP with the Traffic Engineering provisioning capabilities of RSVP-TE into a unified system. The root node uses RSVP-TE to establish P2MP LSPs with TE parameters while simultaneously supporting dynamic join/leave requests from leaf nodes through a standardized interface, achieving both dynamic operation and TE provisioning in a single system.
3Reliability
If entire LSP tree is recalculated when leaf node is added/removed, then effective bandwidth management is achieved, but system complexity and overhead increase
Solution Approach 1:
The patent segments the P2MP LSP tree into a static backbone path from the root node to branch nodes and a dynamic leaf node attachment layer. When a leaf node joins or leaves, only the local attachment point at the branch node needs to be updated, not the entire tree structure. This segmentation allows bandwidth management at the leaf level without requiring global tree recalculation.
Solution Approach 2:
The patent pre-establishes the P2MP LSP tree structure and TE parameters in advance through RSVP-TE signaling. When a leaf node needs to join or leave, the system only needs to add or remove the leaf node from the pre-configured tree at the appropriate branch node, rather than recalculating the entire tree structure. This preliminary setup reduces the complexity of dynamic updates.
Data Source
AI summary
A request to add or remove a leaf node to a multicast group in a Point-to-Multipoint Label Switched Path is detected, and the leaf node can select a pre-configured tunnel in accordance with the requested multicast group. The leaf node encapsulates the received request and transmits it through the selected pre-configured tunnel. A root node for the multicast group receives the request through the tunnel and can identify the leaf node responsible for transmitting the message by the tunnel header. The root can determine if a Point-to-Multipoint Label Switched Path exists for the request multicast group and can update the membership of the multicast group by adding or removing the leaf node to the multicast group.