Multicast Topology Fast Failover via Pre-calculated Paths

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing multicast technologies experience service interruptions when network faults occur, as they require the recreation of a new multicast forwarding path, leading to temporary disruptions in traffic transmission.

Innovation Solution

The implementation of a method that creates multiple multicast topologies using Protocol Independent Multicast (PIM) protocol packets, where a standby topology is identified by a specific identifier and enabled only when the active topology becomes faulty, allowing for fast switching and continuous service operation.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a unicast routing protocol performs calculation to implement convergence and a multicast routing protocol reselects an inverse path when network topology changes, then the multicast forwarding path can be updated, but the multicast traffic transmission is interrupted during the path recreation process

Engineering Contradiction:
Improveservice continuityVSAvoidpath recreation time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent pre-calculates and establishes multiple RPF paths (primary and backup paths) before network faults occur. When a fault is detected, the system can immediately switch to the pre-prepared backup path without performing time-consuming recalculation, thus eliminating service interruption while maintaining reliability

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent prepares backup RPF paths in advance as a cushion against potential network faults. These backup paths are maintained ready-to-use, providing a safety buffer that allows immediate failover when the primary path fails, preventing service interruption and ensuring continuous multicast traffic transmission

Inventive Principle:
Principle #11Beforehand cushioning (Prior cushioning)

2Reliability

If multiple multicast topologies are created and maintained for fast switching, then service continuity is improved during faults, but network resource occupation increases

Engineering Contradiction:
Improveservice continuityVSAvoidnetwork resource occupation
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent applies different states to different topologies: the active topology is fully maintained and used for normal traffic, while standby topologies are pre-calculated but not fully activated. This local differentiation allows fast switching capability without the overhead of maintaining multiple fully-active topologies, thus balancing reliability with resource efficiency

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The patent maintains only the necessary backup paths without creating excessive redundant topologies. By calculating and storing alternative RPF paths selectively (only when needed for failover capability rather than continuously activating all possible paths), the system achieves service continuity while avoiding excessive network resource occupation

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS9160616B2Multicast packet transmission method, related device and system
Publication Date: 2015.10.13 HUAWEI TECH CO LTD
  • US9160616B2 patent drawing
  • US9160616B2 patent drawing
  • US9160616B2 patent drawing

AI summary

Embodiments of the present invention disclose a multicast packet transmission method, and also a related device and system. A multicast packet transmission method may include receiving a first Protocol Independent Multicast (PIM) protocol packet; creating an active multicast topology according to the first PIM protocol packet; receiving a second PIM protocol packet; creating a standby multicast topology according to the second PIM protocol packet, where the second PIM protocol packet carries a standby multicast identifier; setting the standby multicast topology to a disabled state; determining the active multicast topology as faulty; and enabling the standby multicast topology after the active topology is determined as faulty.