Stitching Heterogeneous Multicast Domains via Static Routes
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Heterogeneous multicast domains using different protocols are unable to efficiently share multicast traffic due to compatibility issues and visibility problems, leading to ineffective construction of multicast delivery trees across domains connected over public networks.
Innovation Solution
Implementing border gateway devices that utilize both traditional multicast protocols like PIM and static multicast routes to program and forward multicast traffic between domains, allowing for pre-configured static multicast routes to facilitate traffic sharing without relying on dynamic protocol discovery, and using virtual LAN tunnels to avoid sharing multicast control packets.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If traditional multicast protocols like PIM are used for routing multicast traffic across domains, then dynamic route discovery is enabled, but protocol compatibility issues prevent efficient sharing between heterogeneous domains
Solution Approach 1:
The patent introduces border gateway devices as intermediaries between heterogeneous multicast domains. These gateways run multiple multicast protocol instances (e.g., PIM-SM, PIM-DM, DVMRP) simultaneously and maintain protocol translation capabilities, allowing domains using different protocols to exchange multicast traffic efficiently without requiring end-to-end protocol compatibility.
Solution Approach 2:
Border gateway devices are designed with multi-functionality to handle multiple multicast protocols concurrently. They can receive multicast traffic from domains using one protocol, translate or forward it appropriately, and deliver it to domains using different protocols, thus serving as a universal interface for heterogeneous multicast networks.
2Ease of operation
If dynamic protocol discovery is used for multicast routing, then automatic path determination is achieved, but visibility problems prevent proper construction of multicast delivery trees across domains
Solution Approach 1:
The patent implements preliminary configuration of static multicast routes at border gateway devices. Administrators can pre-define multicast route information (such as multicast group addresses, source addresses, and next-hop interfaces) before actual multicast traffic needs to be forwarded. This eliminates the need for dynamic discovery across domain boundaries and ensures proper delivery tree construction from the outset.
Solution Approach 2:
Border gateway devices act as intermediaries that maintain visibility into multicast routes within their attached domains through static configuration. They compile this route information and use it to make informed forwarding decisions for inter-domain multicast traffic, compensating for the lack of end-to-end visibility that would otherwise be required.
3Productivity
If multicast control packets are shared across domains, then dynamic route optimization is possible, but unnecessary traffic forwarding increases network overhead
Solution Approach 1:
The patent segments multicast control packet handling by domain. Each domain maintains its own multicast control plane independently, and border gateway devices only forward necessary control packets between domains when explicitly configured to do so. This prevents the propagation of unnecessary control traffic across all domains while still allowing for localized route optimization within each domain.
Solution Approach 2:
The patent applies local quality by allowing each domain to optimize its own multicast routes independently using dynamic protocol discovery within the domain boundaries. Border gateway devices are configured to forward only specific, necessary control packets between domains, rather than universally sharing all control traffic, thus reducing overall network overhead while maintaining local optimization capabilities.
Data Source
AI summary
Programmed border gateway devices and a corresponding method are provided for stitching together heterogeneous multicast domains within a network. The method includes programming static multicast routes associated with a given multicast flow into border gateway devices. Based on the static multicast routes, the border gateway devices may send join requests to one or more network devices in their domains and receive a multicast stream in response. The border gateway devices may forward the received multicast stream to other border gateway devices, which may deliver the multicast stream to one or more receiving devices in their respective network domains.