Multicast Distribution Tree Versioning for Traffic Disruption
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In source packet in routing (SPRING) networks, multicast distribution trees (MDTs) face significant packet loss and redundancy due to changes in network topology or membership, which disrupt traffic delivery and require complex state management.
Innovation Solution
A method is introduced to optimize MDTs by using a process that simplifies the graph of potential components of a given S,G tree through iterative graph pruning, ensuring each leaf has a unique shortest path to the root, and implementing a versioning system for MDT updates to allow 'make before break' paradigm, minimizing packet loss and redundancy.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If MDT updates are performed in traditional SPRING networks, then network topology changes can be accommodated, but significant packet loss and traffic disruption occur
Solution Approach 1:
The patent applies preliminary action by pre-computing and installing the next version of the multicast distribution tree before the current tree is torn down. The controller computes the next MDT version in advance, installs it on network nodes, and only then switches traffic to the new version. This ensures that a valid replacement tree is already in place before the old tree is removed, preventing packet loss during topology adaptation.
Solution Approach 2:
The patent uses copying by creating a complete duplicate of the next MDT version and installing it across all relevant network nodes before switching. The new MDT is fully replicated and validated in advance, serving as a ready-to-use copy that can immediately take over traffic delivery when the current tree is decommissioned, thus maintaining reliability during transitions.
2Productivity
If MDT updates are performed frequently to maintain optimal routing, then routing efficiency improves, but control plane overhead and convergence complexity increase
Solution Approach 1:
The patent applies segmentation by dividing MDT management into distinct functional segments: the controller handles MDT computation and version management, while network nodes handle MDT installation and traffic forwarding. This segmentation allows frequent MDT updates to be orchestrated centrally without overwhelming individual nodes, maintaining routing efficiency while managing control plane complexity through clear separation of concerns.
Solution Approach 2:
The patent introduces an intermediary controller that acts as a mediator between the network topology changes and the MDT updates. The controller computes optimal MDT versions, manages version numbering, coordinates installations across nodes, and triggers switches when appropriate. This intermediary absorbs the complexity of frequent updates and presents a simplified interface to network nodes, enabling routing efficiency improvements without proportionally increasing overall control plane complexity.
3Reliability
If versioning is implemented for MDT updates, then packet loss is minimized through make-before-break paradigm, but state management complexity in the network increases
Solution Approach 1:
The patent applies merging by combining multiple MDT versions (current and next) temporarily in the network during the transition period. Both versions coexist with their respective version identifiers, allowing the system to maintain packet delivery reliability through the make-before-break paradigm while managing state through version-based differentiation. The merging is temporary and controlled, with the old version being removed only after the new version is fully operational.
Solution Approach 2:
The patent uses parameter changes by introducing version identifiers as an additional parameter for MDT state management. Each MDT version is distinguished by a version number, allowing nodes to maintain and switch between versions based on this parameter. This parameter-based approach enables reliable transitions through make-before-break while managing state complexity through systematic version tracking rather than complex structural changes.
4Ease of operation
If a new MDT version is installed before the current version is torn down, then in-service modification is enabled, but temporary duplication of state occurs in the network
Solution Approach 1:
The patent applies dynamics by making the MDT version lifecycle dynamic and flexible. The system allows the next MDT version to be installed and activated while the current version is still operational, enabling in-service modifications. The version transition is dynamic rather than static, with the network adapting to have multiple versions coexist temporarily. This dynamic approach enables ease of operation for in-service modifications while the temporary state duplication is managed through systematic version control and automatic cleanup of old versions.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A method is implemented by a network device to minimize multicast traffic loss or duplication in response to an update to multicast group membership in a network where multicast group membership changes can disrupt multicast traffic delivery to other members of the multicast group. The method receives a registration for the multicast group including a member since version number that is greater than the version number currently advertised by the root for a multicast distribution tree (MDT) that serves the multicast group. The root advertises a new MDT identifier (ID) with a new version number for the MDT that serves the multicast group in the network, and switches distribution of multicast group traffic from the current version of the MDT that serves the multicast group to the new version of the MDT that serves the multicast group after a pre-determined time.