Multicast Group Traffic Management via Dynamic Non-Anchor Controller Selection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current multicast traffic management architectures lead to inefficient bandwidth usage and load imbalance, as all multicast traffic flows through a single tunnel between switches and controllers, resulting in wasted bandwidth and uneven link utilization, especially when multiple switches with different user subscriptions are involved.
Innovation Solution
Implementing a dynamic segmentation approach where a switch forms multicast group-specific tunnels with non-anchor controllers serving the requested multicast groups, allowing for load balancing and optimizing bandwidth usage by selecting the most suitable non-anchor controller based on criteria like processing capacity, link bandwidth, and security scores.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of manufacture
If all multicast traffic flows through a single tunnel between switch and anchor controller, then the architecture is simple to implement, but bandwidth is wasted and link utilization becomes unbalanced
Solution Approach 1:
The patent segments multicast traffic by creating group-specific tunnels between switches and non-anchor controllers. Instead of a single tunnel handling all multicast traffic, multiple tunnels are established for different multicast groups, allowing traffic to be distributed across multiple paths and improving link utilization efficiency.
Solution Approach 2:
The patent implements dynamic tunnel selection where the switch controller dynamically determines which non-anchor controller to use for each multicast group based on current network conditions, link utilization, and controller load. This dynamic approach allows the system to adapt to changing traffic patterns and balance load effectively.
2Device complexity
If all multicast traffic flows through a single tunnel between switch and anchor controller, then the system architecture is simple, but load balancing across links is poor
Solution Approach 1:
The patent segments multicast traffic by creating group-specific tunnels between switches and non-anchor controllers. Instead of a single tunnel handling all multicast traffic, multiple tunnels are established for different multicast groups, allowing traffic to be distributed across multiple paths and improving link utilization efficiency.
Solution Approach 2:
The patent introduces non-anchor controllers as intermediary nodes between switches and the anchor controller. These non-anchor controllers receive and forward multicast traffic, distributing the load across multiple controllers and improving overall system productivity without requiring complex changes to the core anchor controller architecture.
3Adaptability or versatility
If multiple switches with different user subscriptions are involved, then network coverage is improved, but bandwidth wastage increases due to redundant traffic flow
Solution Approach 1:
The patent segments multicast traffic by creating group-specific tunnels between switches and non-anchor controllers. Instead of a single tunnel handling all multicast traffic, multiple tunnels are established for different multicast groups, allowing traffic to be distributed across multiple paths and improving link utilization efficiency.
Solution Approach 2:
The patent applies local quality by allowing each switch to have customized multicast group subscriptions based on its local users' needs. Each switch can independently join or leave multicast groups, and the system creates optimized tunnels for each switch's specific requirements, reducing redundant traffic flow while maintaining comprehensive network coverage.
Data Source
AI summary
Some examples relate to managing multicast group traffic. In an example, a switch anchor controller receives a request for a multicast group from an associated network switch in a multicast-capable network. The associated network switch registers to the switch anchor controller in the multicast-capable network. In response to the request, the switch anchor controller selects a non-anchor controller in the multicast-capable network to serve the multicast group to the associated network switch. The switch anchor controller provides the information related to the non-anchor controller to the associated network switch, which in response creates a specific multicast tunnel between the associated network switch and the non-anchor controller to transfer multicast traffic related to the multicast group.