Data Center Multicast Tree Allocation for Capability-Aware Data MDTs
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing multicast data transmission methods result in unnecessary flooding and bandwidth consumption due to the indiscriminate distribution of multicast traffic to PE routers without active receivers, leading to packet drops and inefficient use of resources.
Innovation Solution
Implementing a flag in the I-PMSI BGP message to indicate Data MDT capability and capacity, allowing head nodes to dynamically allocate Data MDTs based on tail node capabilities, and utilizing a network controller for periodic re-optimization of Data MDT assignments to minimize unnecessary bandwidth consumption and processing.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If a head node PE router instantiates Data MDTs without considering tail node capabilities, then the head node can dynamically allocate Data MDTs for high bandwidth traffic, but tail nodes may receive traffic they cannot support causing black-holing and service outages
Solution Approach 1:
The system performs preliminary capability assessment by collecting and storing tail node Data MDT capability information before allocating new Data MDTs. The head node checks whether tail nodes can support additional Data MDTs based on pre-collected capability data, preventing allocation of tunnels that tail nodes cannot handle and avoiding service outages.
2Ease of manufacture
If round robin method is used to assign overlay flows to underlay MDTs, then the allocation process is simple, but unnecessary bandwidth is consumed and packets are dropped at leaf PE routers with no local receivers
Solution Approach 1:
The system implements feedback mechanisms where tail nodes send I-PMSI BGP messages containing capability information back to head nodes. The head node uses this feedback to make informed allocation decisions, assigning overlay flows to underlay MDTs based on actual tail node capabilities and receiver presence, thereby avoiding unnecessary bandwidth consumption and packet drops.
Solution Approach 2:
The system changes the allocation parameter from simple round-robin indexing to capability-based selection. The head node evaluates tail node Data MDT capability parameters and selects appropriate underlay MDTs accordingly, optimizing bandwidth utilization by assigning flows only to MDTs where tail nodes can properly receive and process the traffic.
3Adaptability or versatility
If PE routers distribute multicast traffic to all members of the multicast domain, then complete coverage is achieved, but bandwidth is wasted on dormant PE routers without active receivers
Solution Approach 1:
The system applies local quality by differentiating treatment based on individual tail node characteristics. Instead of uniform distribution to all domain members, the head node assesses each tail node's local capability and receiver status, then selectively assigns Data MDTs only to tail nodes that can support them and have active receivers, optimizing bandwidth usage while maintaining necessary coverage.
Data Source
AI summary
In an example method, a head node connected to a source device transmits a multicast data flow from the source device to receiving devices connected to tail nodes using Default MDT. The example method further includes determining that requirements have been met to begin transmitting the multicast data flow using Data MDT. The method may further include determining whether the tail nodes are able to receive the multicast data flow using Data MDT. In response to determining that all the tail nodes are able to receive the multicast data flow using Data MDT, switch to transmitting the multicast data flow to the tail nodes using Data MDT. In response to determining that at least one of the tail nodes is unable to receive the multicast data flow using the Data MDT, continue transmitting the multicast data flow using Data MDT.