Multicast Source Redundancy via Address Duplication
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current fault management systems in multicast networks are inadequate for handling source failures, as they cannot redirect data streams when the primary source fails, and resource-intensive solutions like MoFRR double bandwidth without addressing source failures.
Innovation Solution
Implementing multiple redundant sources with the same source address, where a network device monitors packet receipt and updates routing tables to switch to an active redundant source upon failure, ensuring continuous data stream delivery without duplicating packets across multiple sources.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If MoFRR is implemented to address link failures, then link failure recovery is improved, but bandwidth consumption doubles and source failures cannot be addressed
Solution Approach 1:
The system pre-establishes multiple routed paths to different sources in the routing table before failure occurs. When a source fails, the network device can immediately switch to an alternative source without requiring preliminary path establishment or packet duplication, thus avoiding the bandwidth overhead of MoFRR while maintaining fast failover capability.
2Loss of energy
If a single source is used to provide datastream, then bandwidth usage is optimized, but source failure results in complete datastream failure
Solution Approach 1:
The network device acts as an intermediary that monitors multiple sources and dynamically selects which source to receive packets from. This mediator approach allows the system to use a single active source for bandwidth efficiency while providing automatic failover to backup sources when the primary source fails, thus resolving the contradiction between bandwidth optimization and reliability.
3Reliability
If keep alive messages are used to detect source failure, then source aliveness can be monitored, but sources not configured with the protocol cannot be detected
Solution Approach 1:
Instead of requiring sources to actively send keep-alive messages, the network device passively monitors for packets from the source. The source essentially serves its own health monitoring function by simply continuing to send data packets, which the network device uses as implicit keep-alive signals. This eliminates the need for additional protocol configuration at the source while maintaining reliable failure detection.
4Reliability
If multiple redundant sources are established with same source address, then source failure can be addressed, but route management complexity increases
Solution Approach 1:
The routing table is pre-populated with multiple routed paths to different sources before any failure occurs. Each entry contains the source address, interface, and next-hop information. When a source fails, the network device simply selects a different pre-configured route from the table, avoiding complex real-time route calculation and reducing management overhead while maintaining high reliability.
Data Source
AI summary
Multiple redundant sources for a datastream can be established in a network, where the redundant sources are configured with the same source address. One of the redundant sources provides the datastream to a receiver of a multicast group. If the redundant source fails, another redundant source can be used in its place, ensuring the receiver continues to receive the datastream. A routing element coupled to a redundant source monitors the redundant source for failure and informs the rest of the network of the status of the coupled redundant source. The routing element can inform other routing elements of the status by advertising or withdrawing a route that reaches the coupled redundant source, which the other routing elements can use to update their routing tables.