Multicast Flow Overlay for PIM and VxLAN Topologies
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current multicast routing technologies, such as BIER, lack a defined multicast flow overlay for certain deployments like PIM, VxLAN, and non-MVPN topologies where BGP-MVPN is not feasible, leading to inefficiencies in multicast data packet forwarding and scalability issues.
Innovation Solution
The implementation of a central routing device that uses targeted hello messages and reliable PIM register messages to establish and manage targeted neighbor connections between ingress and egress routing devices, enabling a multicast flow overlay that can handle incremental updates and interest management for multicast streams.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If BIER is used for multicast forwarding, then packet forwarding efficiency is improved, but scalability and adaptability to certain deployments (PIM, VxLAN, non-MVPN) deteriorate due to lack of defined multicast flow overlay
Solution Approach 1:
The patent introduces a multicast flow overlay as an intermediary layer between the BIER forwarding plane and various deployment topologies (PIM, VxLAN, non-MVPN). This overlay provides abstraction and adaptation mechanisms that enable BIER to work with diverse network architectures without requiring explicit tree-building protocols or per-flow states at intermediate nodes, thus resolving the contradiction between forwarding efficiency and deployability
2Manufacturing precision
If explicit tree-building protocols are used for multicast, then routing precision is improved, but device complexity and scalability deteriorate due to per-flow state requirements
Solution Approach 1:
The patent extracts the explicit tree-building protocol functionality from the core BIER forwarding plane and places it in the multicast flow overlay layer. This separation allows BIER to maintain simple, stateless forwarding at intermediate nodes while still achieving precise multicast routing through the overlay's registration and signaling mechanisms, thus resolving the contradiction between routing precision and device complexity
Data Source
Figure 1
Figure 2
Figure 3
AI summary
An example method includes exchanging targeted hello messages to establish a targeted neighbor connection between a first routing device and a second routing device, wherein one of the routing devices comprises a central routing device, and wherein another one of the routing devices comprises an ingress routing device. The example method further includes processing a source-active register message that specifies a source address and an identifier that are collectively associated with a multicast stream, and wherein the source-active register message further indicates whether the multicast stream is active or withdrawn. After processing the source-active register message, the example method further includes processing a list-of-receivers register message that specifies an egress routing device and at least the identifier that is associated with the multicast stream, wherein the list-of-receivers register message further indicates whether or not the egress routing device requests receipt of data associated with the multicast stream.