PIM Olist Validation for Nonstop Multicast Forwarding

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

PIM device failures cause disruptions in multicast traffic flow due to the erasure of pathing information during recovery processes, leading to incomplete Olists being overwritten in the centralized database and resulting in traffic disruptions for end-users.

Innovation Solution

A controlled method for updating mroutes that prevents overwriting the centralized database with incomplete Olists from the PIM cache during recovery by comparing Olists in the PIM cache with those in the centralized database and only publishing when they match, ensuring traffic continuity.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the PIM cache is erased during device recovery, then the device can rebuild its routing information, but the centralized database is overwritten with incomplete Olists causing traffic disruption

Engineering Contradiction:
Improvetraffic continuityVSAvoidcomplete Olist information
Core Design Contradiction:
ReliabilityVSLoss of information

Solution Approach 1:

The system performs preliminary actions by comparing the PIM cache Olist with the centralized database Olist before publishing updates during recovery. This pre-check prevents incomplete information from being written to the database, ensuring traffic continuity is maintained while rebuilding routing information.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements feedback mechanisms by continuously monitoring and comparing Olist information between the PIM cache and centralized database during recovery processes. This feedback loop ensures that only complete and accurate Olist information is published, preventing traffic disruption while enabling successful recovery.

Inventive Principle:
Principle #23Feedback

2Productivity

If the PIM cache is rebuilt during recovery, then the device restores routing functionality, but traffic flow is disrupted due to incomplete Olist overwrites

Engineering Contradiction:
Improverouting recovery speedVSAvoidtraffic flow stability
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

Before publishing updated Olist information during recovery, the system performs a preliminary comparison to verify completeness. This pre-validation step allows the device to rebuild routing functionality at full speed while preventing any traffic flow disruptions from incomplete overwrites.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system introduces an intermediary comparison step between the PIM cache rebuilding process and the centralized database publishing process. This intermediary mechanism acts as a gatekeeper that ensures only complete Olist information is published, allowing rapid recovery without compromising traffic stability.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Stability of the object's composition

If the centralized database is updated with PIM cache information, then the routing information is synchronized, but incomplete Olists cause traffic loss during recovery

Engineering Contradiction:
ImproveOlist information consistencyVSAvoidtraffic delivery continuity
Core Design Contradiction:
Stability of the object's compositionVSLoss of energy

Solution Approach 1:

The system uses feedback from comparing PIM cache Olists with centralized database Olists to control the publishing process during recovery. This feedback mechanism ensures information consistency is maintained while preventing any traffic delivery interruptions from incomplete updates.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The comparison process serves as an intermediary between the PIM cache and centralized database, ensuring that only complete and consistent Olist information is synchronized. This intermediary step maintains information consistency while protecting traffic delivery continuity from incomplete updates.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS12445374B2Nonstop forwarding for routed multicast traffic
Publication Date: 2025.10.14 HEWLETT PACKARD ENTERPRISE DEV LP
  • US12445374B2 patent drawing
  • US12445374B2 patent drawing
  • US12445374B2 patent drawing

AI summary

A programmed network device and corresponding method are provided for rebuilding a multicast state upon experiencing a failure in a network using a protocol independent multicast (PIM) protocol. The method includes receiving updates to an outgoing list (Olist) for a given multicast route (mroute) at the network component and updating a PIM cache Olist in the network component with the received updates. During a state of recovering from the failure, the method includes determining whether the PIM cache Olist matches a centralized database Olist located in a centralized database. When a match is found, the method includes publishing an mroute state from the PIM cache to the centralized database.