Loop Avoidance Technique for Multicast Control Plane

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Multicast protocols face challenges in avoiding loops during network convergence, leading to traffic storms and bandwidth inefficiencies due to transient forwarding inconsistencies and stale routing information.

Innovation Solution

Implementing a loop avoidance technique that uses an upstream neighbor check to detect forwarding inconsistencies by maintaining an upstream neighbor list and holding multicast control plane messages until routing information converges, thereby preventing loop creation.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Speed

If multicast control plane messages are processed immediately during network convergence, then message processing speed is improved, but forwarding inconsistencies cause loop creation and traffic storms

Engineering Contradiction:
Improvemessage processing speedVSAvoidloop avoidance
Core Design Contradiction:
SpeedVSReliability

Solution Approach 1:

The system performs preliminary actions by pre-calculating and storing the upstream neighbor list before messages arrive. When a message is received, the upstream neighbor check can immediately compare against this pre-prepared list, enabling fast loop detection without delaying message processing. This resolves the contradiction by preparing the detection mechanism in advance so it can operate at full speed without compromising reliability.

Inventive Principle:
Principle #10Preliminary action

2Measurement precision

If upstream neighbor check is performed for every received message, then loop detection accuracy is improved, but processing overhead and message delay increase

Engineering Contradiction:
Improveloop detection accuracyVSAvoidmessage processing delay
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The system creates a copy of the upstream neighbor list and uses it for rapid comparison checks. Instead of performing complex path analysis for each message, the system copies the pre-determined upstream neighbor information and performs simple lookups. This maintains high detection accuracy while significantly reducing processing time per message, resolving the contradiction between precision and speed.

Inventive Principle:
Principle #26Copying

3Measurement precision

If routing information is updated frequently during network topology changes, then routing accuracy is improved, but transient inconsistencies increase loop risk

Engineering Contradiction:
Improverouting accuracyVSAvoidforwarding consistency
Core Design Contradiction:
Measurement precisionVSStability of the object's composition

Solution Approach 1:

The upstream neighbor list acts as an intermediary between routing information updates and forwarding decisions. When routing information changes during network convergence, the upstream neighbor list provides a stable reference that mediates between the new routing data and active forwarding operations. This allows routing information to be updated frequently for accuracy while the intermediary list maintains forwarding consistency by providing a consistent view for loop detection.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS9288069B2Loop avoidance technique for the multicast control plane
Publication Date: 2016.03.15 CISCO TECHNOLOGY INC
  • US9288069B2 patent drawing
  • US9288069B2 patent drawing
  • US9288069B2 patent drawing

AI summary

The present disclosure provides for a loop avoidance technique that implements an upstream neighbor check to detect any forwarding inconsistencies. When a message is received from a neighbor routing element, an upstream neighbor check is performed to determine whether the neighbor routing element is an upstream neighbor toward a content provider of a datastream identified in the message. If the check determines that the neighbor routing element is not an upstream neighbor, then a forwarding inconsistency is not detected. If the check determines that the neighbor routing element is an upstream neighbor, then a forwarding inconsistency is detected.