Multipoint-to-Multipoint MPLS Tree Stitching Across Service Providers
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Businesses with large computer networks spanning multiple service providers face challenges in managing multicast communications across third-party provider networks, as it is unclear where to place the root node for an MP2MP MPLS tree, and maintaining control over root nodes across different service providers is difficult, leading to inefficiencies in network stitching.
Innovation Solution
The solution involves placing a root node in each service provider's domain, creating separate MP2MP MPLS trees, and stitching them together to form a super-MP2MP MPLS tree, using directed Label Distribution Protocol (LDP) sessions to connect and manage multicast traffic between these trees, allowing for seamless communication across multiple provider networks.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a single root node is placed for an MP2MP MPLS tree spanning multiple service providers, then multicast communications can be established across providers, but control over the root node cannot be maintained by individual service providers
Solution Approach 1:
The patent divides the single root node concept into multiple root nodes, with each service provider maintaining control over their own root node. This segmentation allows each provider to independently manage their portion of the MP2MP MPLS tree while still enabling end-to-end multicast communications across multiple providers through the stitched trees.
2Ease of operation
If separate MP2MP MPLS trees are created in each service provider's domain, then each provider maintains control over their root node, but network stitching becomes complex
Solution Approach 1:
The patent introduces directed LDP sessions as intermediary communication channels between root nodes of different service providers. These directed sessions simplify the stitching process by providing a standardized mechanism for root nodes to exchange control information and establish connections, reducing the overall network stitching complexity.
Solution Approach 2:
The patent makes root nodes multi-functional by enabling them to perform both local tree management and inter-provider coordination. Each root node can independently manage its local MP2MP MPLS tree while simultaneously participating in directed LDP sessions with other root nodes, allowing a single node type to handle multiple functions across different operational domains.
3Adaptability or versatility
If multiple root nodes are placed in different service provider domains, then each provider can control their own root node, but it is unclear where to place the root node for a unified tree
Solution Approach 1:
The patent inverts the traditional approach by not trying to determine where to place a single root node, but rather placing root nodes in each service provider domain and having them self-organize through directed LDP sessions. This inversion eliminates the complexity of root node placement determination while maintaining unified multicast functionality across providers.
Data Source
AI summary
In one embodiment, a method is provided. A first root node of a first Multipoint-to-Multipoint (MP2MP) Multi-Protocol Label Switching (MPLS) tree, advertises to a second root node of a second MP2MP MPLS tree a first label for the second root node to use to send multicast traffic to the first MP2MP MPLS tree. The first root node receives a second label from the second root node for the first root node to use to send multicast traffic to the second MP2MP MPLS tree. Communications are carried out between the first MP2MP MPLS tree and the second MP2MP MPLS tree using the first label and the second label. In another embodiment, apparatus are also provided.


