Multicast Rendezvous Point Deployment in Virtual Gateway Switches

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Deploying a multicast rendezvous point (RP) in a distributed tunnel fabric is challenging due to issues with encapsulation overhead and traffic management, especially when the RP is configured inside the fabric or far from the source, leading to inefficiencies and potential traffic loss.

Innovation Solution

Configuring the RP on one of the participating switches of the virtual gateway switch (VGS) and synchronizing multicast information among switches to facilitate efficient deployment and redundancy, while maintaining inter-switch links for sharing control and data packets, thus consolidating encapsulations and managing registration processes without modifying standard multicast protocols.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If the RP is configured inside the fabric or far from the source, then multicast traffic can be distributed to remote locations, but encapsulation overhead increases and network efficiency decreases

Engineering Contradiction:
Improvemulticast traffic distribution capabilityVSAvoidencapsulation overhead
Core Design Contradiction:
Ease of operationVSLoss of energy

Solution Approach 1:

The patent applies local quality by allowing different switches within the virtual gateway to have different roles - one switch is designated as the RP while others are not. This enables the RP function to be localized at the gateway boundary rather than requiring all switches to handle full encapsulation overhead, thus reducing overall network encapsulation burden while maintaining multicast distribution capability.

Inventive Principle:
Principle #3Local quality

2Device complexity

If the RP is configured inside the fabric, then traffic management is simplified, but potential traffic loss occurs and reliability decreases

Engineering Contradiction:
Improvetraffic management complexityVSAvoidtraffic delivery reliability
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The patent introduces an intermediary mechanism where the virtual gateway acts as a mediator between the external network and the fabric. The gateway boundary switches handle RP functions and traffic management, ensuring reliable traffic delivery while maintaining simplified internal fabric operations. This intermediary approach prevents traffic loss by properly managing packet forwarding at the gateway boundary.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If multiple switches operate as a single virtual gateway, then redundancy is improved, but coordination complexity and synchronization overhead increase

Engineering Contradiction:
Improvegateway redundancyVSAvoidswitch coordination complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent merges multiple physical switches into a single logical virtual gateway entity. The switches coordinate through standardized inter-switch links and protocols, presenting a unified gateway interface to the network. This merging approach provides redundancy while managing coordination complexity through protocol standardization and role assignment (one RP, multiple non-RP switches).

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS11855792B2Multicast rendezvous point deployment in a virtual gateway of a distributed tunnel fabric
Publication Date: 2023.12.26 HEWLETT PACKARD ENTERPRISE DEV LP
  • US11855792B2 patent drawing
  • US11855792B2 patent drawing
  • US11855792B2 patent drawing

AI summary

A system for multicast traffic management in an overlay tunnel fabric is provided. The system can operate a first switch and a second switch of the fabric as part of a virtual switch. The virtual switch can operate as a gateway for the fabric. The system can efficiently deploy a rendezvous point (RP) for a multicast group at the first switch. During operation, the system can determine whether to synchronize a registration packet associated with the multicast group with the second switch based on a type of a first ingress connection associated with the registration packet. The system can then determine whether to receive subsequent registration packets for the multicast group based on the type of the first ingress connection and reception of a join request for the multicast group. The type of a respective connection indicates whether the connection includes an overlay tunnel.