Centralized Database Multicast Convergence

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing multicast network management systems face challenges in efficiently managing multicast protocols and configuring parameters, particularly during failovers, which can result in delays for newly joined hosts and interrupted active multicast flows.

Innovation Solution

The implementation of a centralized database-based multicast convergence method using an Open Virtual Switch Database (OVSDB) that employs a restart timer to validate entries, sends data packets to maintain service, and dynamically updates configuration parameters, enabling zero-touch configuration and faster convergence of multicast protocols.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If existing multicast network management systems are used to manage multicast protocols and configure parameters, then multicast service can be provided, but delays occur for newly joined hosts and active multicast flows are interrupted during failovers

Engineering Contradiction:
Improvemulticast flow continuityVSAvoidconvergence time during failover
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by pre-configuring a standby management card with multicast protocol handling capabilities and maintaining a hot standby state. The standby card continuously synchronizes with the master card and prepares forwarding tables in advance, so that during failover, the transition can occur immediately without waiting for protocol re-learning or configuration, thus eliminating convergence delays and maintaining flow continuity.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If a standby management card is implemented to take over during master card failure, then network resilience is improved, but configuration complexity and resource requirements increase

Engineering Contradiction:
Improvenetwork resilience during failoverVSAvoidmulticast management system complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system creates a copy of the master management card's functionality in a standby card, which maintains identical multicast protocol handling capabilities, configuration data, and forwarding tables. This copying approach ensures that the standby card can immediately assume the master's role during failover without requiring complex reconfiguration or additional intelligence, thereby improving reliability while keeping the system architecture relatively simple and resource-efficient.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS10742431B2Centralized database based multicast converging
Publication Date: 2020.08.11 HEWLETT PACKARD ENTERPRISE DEV LP
  • US10742431B2 patent drawing
  • US10742431B2 patent drawing
  • US10742431B2 patent drawing

AI summary

Examples herein are directed to centralized database based multicast converging. For instance, in various examples centralized database based multicast converging can include starting a restart timer having a value greater than a time to validate stored entries in a centralized database, sending data packets at least to hosts on the network corresponding to the stored entries in the centralized database to maintain service to the hosts while the restart timer is running, sending query packets to validate a host corresponding to an entry of the stored entries in the centralized database, and responsive to the restart timer expiring, sending data packets to a converged group of hosts including at least the validated host.