PIM Join Entropy Grouping Multicast Flows
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current multicast routing protocols face challenges in efficiently managing and routing large numbers of multicast flows, particularly in scenarios where thousands of flows share the same source but are divided across multiple paths, leading to scaling issues and difficulties in performing fast failovers due to the need to monitor and manage each flow individually.
Innovation Solution
The introduction of a PIM join attribute with an 'entropy' field, or flow attribute value, allows network devices to group related multicast flows and select a common path for all flows with the same attribute value, enabling statistics to be determined for the grouping rather than individual flows and facilitating fast failover when health criteria are not met.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If multicast routing protocols manage each flow individually, then flow monitoring precision is improved, but device complexity and computational resources increase significantly
Solution Approach 1:
The patent groups multiple multicast flows into a single flow by using the same source address, group address, and RPF interface for different multicast groups. This merging allows the router to treat multiple flows as one, reducing the number of individual flow entries in the forwarding table and decreasing device complexity while maintaining adequate monitoring precision through the use of flow buckets that aggregate traffic statistics.
Solution Approach 2:
The patent creates a universal flow bucket structure that can accommodate multiple multicast flows with the same characteristics. This flow bucket serves multiple functions: it aggregates traffic from multiple flows, provides a single point for monitoring and statistics collection, and enables unified fast failover decisions for all flows within the bucket, thereby reducing device complexity while maintaining monitoring capability.
2Manufacturing precision
If multicast routing protocols monitor thousands of individual flows, then traffic management accuracy is improved, but scalability deteriorates
Solution Approach 1:
The patent merges multiple multicast flows that share the same source, group, and RPF interface characteristics into a single flow bucket. This consolidation reduces the number of flow entries from thousands to a manageable number, significantly improving scalability while maintaining traffic management accuracy through aggregated monitoring and control mechanisms.
Solution Approach 2:
The patent segments the large set of multicast flows into smaller groups based on common characteristics (source address, group address, RPF interface). Each segment is represented by a single flow bucket, allowing the system to manage thousands of flows through a much smaller number of bucket entries, thereby improving both scalability and traffic management accuracy.
3Reliability
If multicast routing protocols perform fast failover for each individual flow, then network reliability is improved, but computational overhead increases
Solution Approach 1:
The patent merges multiple flows into a single flow bucket for fast failover purposes. When a failure is detected in the RPF interface or source reachability, the router performs a single fast failover operation for the entire bucket rather than individually for each flow. This approach maintains network reliability by ensuring all flows in the bucket are protected, while significantly reducing computational overhead by eliminating redundant failover operations.
4Measurement precision
If multicast routing protocols manage flows with different paths separately, then routing precision is improved, but device complexity increases
Solution Approach 1:
The patent applies local quality by allowing different flow buckets to have different RPF interfaces and paths based on their specific routing requirements. Each flow bucket maintains its own routing characteristics locally, ensuring routing precision for flows that require different paths, while the overall device complexity is reduced by grouping flows with identical characteristics into single buckets.
Data Source
Figure 1A
Figure 1B
Figure 1C
AI summary
Techniques are described for grouping related flows using a flow attribute value indicated by a modified protocol independent multicast (PIM) join request. According to techniques of this disclosure, a network device is configured to receive, from a downstream network device, two or more first PIM join requests indicating two or more multicast groups. In response to determining that each first PIM join request of the two or more first PIM join requests indicates a common first flow attribute value, the network device is configured to select a common path. The network device is further configured to send two or more second PIM join requests indicating the two or more multicast groups to an upstream network device along the selected common path and toward the source. Each second PIM join request of the two or more second PIM join requests includes a common second flow attribute value.