Multicast Convergence via Unicast Synchronization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In IP Multicast networks, the Multicast control plane often converges before the Unicast control plane has updated the network topology, leading to routing loops, unnecessary control plane churn, delayed convergence, traffic storms, and Make Before Break issues due to independent protocols managing IP Multicast traffic.
Innovation Solution
A method involving a query/acknowledge process that links the Multicast control plane with the Unicast control plane to ensure synchronized topology information, preventing loops and unnecessary churn by verifying the propagation of updates through the multicast tree before making changes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Speed
If the Multicast control plane acts independently to restore connectivity after network failure, then connectivity restoration speed is improved, but routing loops and control plane churn occur due to acting before Unicast control plane convergence
Solution Approach 1:
The patent implements a feedback mechanism where the Multicast control plane receives convergence status information from the Unicast control plane. Before the Multicast control plane restores connectivity, it waits for confirmation that the Unicast control plane has converged. This feedback loop prevents routing loops by ensuring both control planes have consistent topology information before acting, while still allowing relatively fast restoration once convergence is confirmed.
Solution Approach 2:
The patent applies preliminary action by having the Multicast control plane wait for Unicast control plane convergence before initiating connectivity restoration. This preliminary check ensures that the topology information is up-to-date and consistent, preventing routing loops and control plane churn. The system performs this convergence verification in advance of the actual restoration action, balancing speed with reliability.
2Adaptability or versatility
If multiple independent protocols manage IP Multicast traffic, then protocol independence and flexibility are improved, but convergence synchronization and network stability deteriorate
Solution Approach 1:
The patent merges the operation of independent Multicast and Unicast control planes by introducing a coordination mechanism. While the protocols remain independent in their respective functions, their convergence processes are combined through a synchronization point where the Multicast control plane waits for Unicast convergence status. This merging of convergence timing ensures stability while preserving protocol independence for their respective traffic management functions.
3Loss of time
If the Multicast control plane converges quickly without waiting for Unicast control plane updates, then convergence time is reduced, but topology accuracy and network stability worsen
Solution Approach 1:
The patent uses preliminary action by having the Multicast control plane perform a convergence status check before initiating restoration. This preliminary verification ensures topology information is accurate by confirming Unicast control plane convergence, preventing decisions based on stale data. The system accepts the minimal time delay this check introduces as necessary for maintaining topology accuracy and network stability.
Solution Approach 2:
The patent implements feedback where the Multicast control plane continuously monitors convergence status information from the Unicast control plane. This feedback mechanism ensures that the Multicast control plane only acts when topology information is accurate and up-to-date, preventing routing loops and instability while maintaining relatively fast convergence once the accuracy condition is met.
Data Source
AI summary
In one embodiment, a device connected to a network as part of a multicast tree receives a revised unicast routing and distributes the revised unicast routing and a query packet to a downstream device in the multicast tree. The device receives an acknowledgement message from the downstream device based on the query packet and determines a new multicast route based on the revised unicast routing and the acknowledgement message from the downstream device.