BFD Session for PIM-SM DR Failure Detection

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current multicast networking technologies face challenges in detecting Designated Router (DR) failures in Protocol Independent Multicast Sparse Mode (PIM-SM) networks, leading to delays in failure detection, which can result in data loss and increased re-transmissions due to the default Neighbor Liveness Timer setting of 105 seconds.

Innovation Solution

Implementing a Bidirectional Forwarding Detection (BFD) session with a multipoint configuration that allows for sub-second failure detection by using a DR as the MultipointHead to control packet transmission intervals, enabling faster detection of DR failures through BFD Discriminator Type-Length-Value (TLV) messages within PIM Hello messages.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the default Neighbor Liveness Timer setting of 105 seconds is used, then the network operation is simple, but the failure detection time is delayed

Engineering Contradiction:
Improvefailure detection capabilityVSAvoidfailure detection time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent implements preliminary failure detection mechanisms by establishing BFD sessions before actual failures occur. The BFD control packets are exchanged periodically in advance, allowing the network to detect failures much faster than the traditional 105-second timer would allow, thereby reducing failure detection time while maintaining simple network operation.

Inventive Principle:
Principle #10Preliminary action

2Loss of time

If BFD session with sub-second detection is implemented, then failure detection time is reduced, but device complexity increases

Engineering Contradiction:
Improvefailure detection timeVSAvoidsession management complexity
Core Design Contradiction:
Loss of timeVSDevice complexity

Solution Approach 1:

The patent uses BFD as an intermediary mechanism between the traditional multicast routing protocols and failure detection requirements. The BFD session acts as a mediator that provides fast failure detection without requiring changes to the core multicast routing logic, thus reducing failure detection time while limiting the increase in device complexity to just the BFD session management layer.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the failure detection function into a separate BFD session layer, distinct from the traditional Neighbor Liveness Timer mechanism. This segmentation allows the fast BFD detection to operate independently alongside the existing routing protocols, reducing overall system complexity by isolating the complex timing and packet exchange logic to a dedicated BFD module.

Inventive Principle:
Principle #1Segmentation

3Reliability

If traditional Neighbor Liveness Timer is used, then configuration is simple, but data loss occurs due to delayed detection

Engineering Contradiction:
Improvedata integrityVSAvoiddetection delay
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent implements continuous feedback through periodic BFD control packet exchanges between neighbors. This feedback mechanism allows the network to immediately detect when a neighbor stops responding, preventing data loss by triggering failover before significant data loss can occur, thus improving data integrity while reducing detection delay compared to the traditional timer approach.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS10771312B2Failure detection in a data network
Publication Date: 2020.09.08 ZTE CORP
  • US10771312B2 patent drawing
  • US10771312B2 patent drawing
  • US10771312B2 patent drawing

AI summary

A first network node generates a message to be transmitted to a second network node. The message can include a value that identifies a type of the operational session, an identifier of the first network node that can control transmission of packets used during the operational session, and a length of the identifier. Further, the first and second network nodes can operate in an operational session in which the second network node can detect a failure.