IP Library › Granted Patent US 11,509,568
Granted Patent B2
US 11,509,568 · App. 16/585,321 · Granted Nov 22, 2022

Protocol independent multicast designated networking device election system

Inventor: Karthi Kaliyamoorthy (Tamilnadu, IN)
Assignee: Dell Products L.P.
H04L45/14H04L45/16H04L45/18
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 11,509,568
App. No.
16/585,321
Filed
Sep 27, 2019
Granted
Nov 22, 2022
Kind
B2
Art Unit
2468
USPC
370/390
Abstract

A Protocol Independent Multicast (PIM) designated networking device election system includes a first networking device and a second networking device that are coupled to the first edge device. The second networking device receives a first PIM message from the first networking device and determines that the first PIM message indicates that the first networking device supports designated networking device election based on an interface performance property. The second networking device then determines whether a first interface performance property indication indicates that a first interface performance property of the first networking device or a second interface performance property of the second networking device satisfy an interface performance property condition. In response to determining that the second interface performance property satisfies the interface performance property condition, the second networking device forwards first data traffic received at the second networking device toward the first edge device.

Claims (53)

1. A Protocol Independent Multicast (PIM) designated networking device election system, comprising:

an edge device;

a multicast group that includes at least one rendezvous networking device,

wherein a source device provides messages to the at least one rendezvous networking device to join the multicast group and generates and directs multicast data traffic to the at least one rendezvous networking device, and

wherein receiver networking devices provide messages to the at least one rendezvous networking device to join the multicast group and pull multicast data traffic received by the at least one rendezvous networking device from the source device;

a first receiver networking device that is included in the multicast group, that is coupled to the edge device via a first respective link, and that receives the multicast data traffic generated by the source device via the at least one rendezvous networking device; and

a second receiver networking device that is included in the multicast group, that is coupled to the edge device via a second respective link, and that receives the multicast data traffic generated by the source device via the at least one rendezvous networking device, wherein the second receiver networking device is configured to:

receive a first Protocol Independent Multicast (PIM) message from the first receiver networking device;

determine that the first PIM message indicates that the first receiver networking device supports designated networking device election based on an interface performance property, and identifies a first interface performance property of the first receiver networking device;

determine whether the first interface performance property of the first receiver networking device that is identified in the first PIM message, or a second interface performance property of the second receiver networking device, satisfy an interface performance property condition; and

forward, in response to determining that the second interface performance property of the second receiver networking device satisfies the interface performance property condition and the first interface performance property of the first receiver networking device does not satisfy the interface performance property condition, the multicast data traffic, which was generated by the source device and identical copies of which are received at both the first receiver networking device and the second receiver networking device, from the second receiver networking device via the second respective link and toward the edge device while the first receiver networking device prevents the forwarding of the multicast data traffic via the first respective link.

2. The system of claim 1 , wherein the first receiver networking device is configured to:

receive a second PIM message from the second receiver networking device; determine that the second PIM message indicates that the second receiver networking device supports designated networking device election based on the interface performance property, and identifies the second interface performance property of the first receiver networking device; and

prevent, in response to determining that the second interface performance property of the second receiver networking device identified in the second PIM message satisfies the interface performance property condition and that the first interface performance property of the first receiver networking device does not satisfy the interface performance property condition, the multicast data traffic, which was generated by the source device and identical copies of which are received at both the first receiver networking device and the second receiver networking device, from being forwarded from the first receiver networking device via the first respective link toward the edge device.

3. The system of claim 1 , wherein each of the first interface performance property and the second interface performance property are an interface speed property.

4. The system of claim 1 , wherein each of the first interface performance property and the second interface performance property are an interface bandwidth property.

5. The system of claim 4 , wherein each of the first interface performance property and the second interface performance property are an interface latency property.

6. The system of claim 1 , wherein the second receiver networking device is configured to:

transition to operating as a designated networking device in order to forward the multicast data traffic from the second receiver networking device via the second respective link and toward the edge device.

7. The system of claim 1 , wherein the first receiver networking device is configured to:

transition to operating as a non-designated networking device in order to prevent forwarding of the multicast data traffic from the first receiver networking device via the first respective link and toward the edge device.

8. The system of claim 1 , wherein the second receiver networking device is configured to receive the multicast data traffic from the source device independent of the first receiver networking device.

9. An Information Handling System (IHS), comprising:

a processing system that is configured as part of a multicast group that includes at least one rendezvous networking device, wherein a source device provides messages to the at least one rendezvous networking device to join the multicast group and generates and directs multicast data traffic to the at least one rendezvous networking device, and wherein receiver networking devices provide messages to the at least one rendezvous networking device to join the multicast group and pull multicast data traffic received by the at least one rendezvous networking device from the source device;

a communication subsystem that is coupled to the processing system, that is coupled to the edge device via a second respective link, and that is configured to receive the multicast data traffic generated by the source device via the at least one rendezvous networking device; and

a memory system that is coupled to the processing system and that includes instructions that, when executed by the processing system, cause the processing system to provide a forwarding engine that is configured to:

receive, via the communication subsystem from a first receiver networking device that is included in the multicast group, that is coupled to the edge device via a first respective link, and that is configured to receive the multicast data traffic generated by the source device via the at least one rendezvous networking device, a first Protocol Independent Multicast (PIM) message;

determine that the first PIM message indicates that the first receiver networking device supports designated networking device election based on an interface performance property, and identifies a first interface performance property of the first receiver networking device;

determine whether the first interface performance property of the first receiver networking device that is identified in the first PIM message, or a second interface performance property of the communication subsystem, satisfy an interface performance property condition; and

forward, in response to determining that the second interface performance property of the communication subsystem satisfies the interface performance property condition and the first interface performance property of the first receiver networking device does not satisfy the interface performance property condition, the multicast data traffic, which was generated by the source device and identical copies of which are received at both the first receiver networking device and the communication subsystem, from the communication subsystem via the second respective link and toward the edge device, wherein the second interface performance property satisfying the interface performance property condition and the first interface performance property not satisfying the interface performance property condition causes the first receiver networking device to prevent the forwarding of the multicast data traffic via the first respective link.

10. The IHS of claim 9 , wherein each of the first interface performance property and the second interface performance property are an interface speed property.

11. The IHS of claim 9 , wherein each of the first interface performance property and the second interface performance property are an interface bandwidth property.

12. The IHS of claim 9 , wherein each of the first interface performance property and the second interface performance property are an interface latency property.

13. The IHS of claim 9 , wherein the forwarding engine is configured to receive the multicast data traffic from the source device independent of the first receiver networking device.

14. The IHS of claim 9 , wherein the forwarding engine is configured to:

transition to operating as a designated networking device in order to forward the multicast data traffic from the communication system via the second respective link and toward the edge device.

15. A method for electing a designated networking device, comprising:

operating, by a second receiver networking device that is coupled to an edge device by a second respective link, as part of a multicast group that includes at least one rendezvous networking device that is coupled to the second receiver networking device, wherein a source device provides messages to the at least one rendezvous networking device to join the multicast group and generates and directs multicast data traffic to the at least one rendezvous networking device, and wherein a first receiver networking device and the second receiver networking device provided messages to the at least one rendezvous networking device to join the multicast group and pull multicast data traffic received by the at least one rendezvous networking device from the source device;

receiving, by the second receiver networking device via the at least one rendezvous networking device, the multicast data traffic generated by the source device;

receiving, by the second receiver networking device from the first receiver networking device that is coupled to the edge device by a first respective link and that receives the multicast data traffic generated by the source device via the at least one rendezvous networking device, a first Protocol Independent Multicast (PIM) message;

determining, by the second receiver networking device, that the first PIM message indicates that the first receiver networking device supports designated networking device election based on an interface performance property, and identifies a first interface performance property of the first receiver networking device;

determining, by the second receiver networking device, whether the first interface performance property of the first receiver networking device that is identified in the first PIM message, or a second interface performance property of the second receiver networking device, satisfy an interface performance property condition; and

forwarding, by the second receiver networking device and in response to determining that the second interface performance property of the second receiver networking device satisfies the interface performance property condition and the first interface performance property of the first receiver networking device does not satisfy the interface performance property condition, the multicast data traffic, which was generated by the source device and identical copies of which are received at both the first receiver networking device and the second receiver networking device, from the second receiver networking device via the second respective link toward the edge device, wherein the second interface performance property satisfying the interface performance property condition and the first interface performance property not satisfying the interface performance property condition causes the first receiver networking device to prevent the forwarding of the multicast data traffic via the first respective link.

16. The method of claim 15 , further comprising:

receiving, by the first receiver networking device from the second receiver networking device, a second PIM message;

determining, by the first receiver networking device, that the second PIM message indicates that the second receiver networking device supports designated networking device election based on the interface performance property, and identifies the second interface performance property of the first receiver networking device; and

preventing, by the first receiver networking device and in response to determining that the second interface performance property of the second receiver networking device identified in the second PIM message satisfies the interface performance property condition and that the first interface performance property of the first receiver networking device does not satisfy the interface performance property condition, the multicast data traffic, which was generated by the source device and identical copies of which are received at both the first receiver networking device and the second receiver networking device, from being forwarded from the first receiver networking device via the first respective link toward the edge device.

17. The method of claim 15 , wherein each of the first interface performance property and the second interface performance property are an interface speed property.

18. The method of claim 15 , wherein each of the first interface performance property and the second interface performance property are an interface bandwidth property.

19. The method of claim 15 , wherein each of the first interface performance property and the second interface performance property are an interface latency property.

20. The method of claim 15 , further comprising:

transitioning, by the second receiver networking device, to operating as a designated networking device in order to forward the multicast data traffic from the second receiver networking device via the second respective link and toward the edge device; and

transitioning, by the first receiver networking device, to operating as a non-designated networking device in order to prevent forwarding of the multicast data traffic from the first receiver networking device via the first respective link and toward the edge device.

Assignments (9)
RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (053546/0001) Recorded Jun 23, 2022
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT
To: DELL MARKETING L.P. (ON BEHALF OF ITSELF AND AS SUCCESSOR-IN-INTEREST TO CREDANT TECHNOLOGIES, INC.); DELL INTERNATIONAL L.L.C.; DELL PRODUCTS L.P.; DELL USA L.P.; EMC CORPORATION; DELL MARKETING CORPORATION (SUCCESSOR-IN-INTEREST TO FORCE10 NETWORKS, INC. AND WYSE TECHNOLOGY L.L.C.); EMC IP HOLDING COMPANY LLC
Reel/Frame 071642/0001 →
RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (051302/0528) Recorded Jun 23, 2022
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT
To: DELL PRODUCTS L.P.; EMC IP HOLDING COMPANY LLC; DELL MARKETING CORPORATION (SUCCESSOR-IN-INTEREST TO WYSE TECHNOLOGY L.L.C.); SECUREWORKS CORP.
Reel/Frame 060438/0593 →
RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (053311/0169) Recorded Jun 23, 2022
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT
To: DELL PRODUCTS L.P.; EMC CORPORATION; EMC IP HOLDING COMPANY LLC
Reel/Frame 060438/0742 →
RELEASE OF SECURITY INTEREST AT REEL 051449 FRAME 0728 Recorded Nov 2, 2021
From: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH
To: DELL PRODUCTS L.P.; EMC IP HOLDING COMPANY LLC; WYSE TECHNOLOGY L.L.C.; SECUREWORKS CORP.; EMC CORPORATION
Reel/Frame 058002/0010 →
SECURITY INTEREST Recorded Jun 5, 2020
From: DELL PRODUCTS L.P.; EMC CORPORATION; EMC IP HOLDING COMPANY LLC
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS COLLATERAL AGENT
Reel/Frame 053311/0169 →
SECURITY AGREEMENT Recorded Apr 22, 2020
From: CREDANT TECHNOLOGIES INC.; DELL INTERNATIONAL L.L.C.; DELL MARKETING L.P.; DELL PRODUCTS L.P.; DELL USA L.P.; EMC CORPORATION; FORCE10 NETWORKS, INC.; WYSE TECHNOLOGY L.L.C.; EMC IP HOLDING COMPANY LLC
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A.
Reel/Frame 053546/0001 →
SECURITY AGREEMENT Recorded Dec 31, 2019
From: DELL PRODUCTS L.P.; EMC IP HOLDING COMPANY LLC; WYSE TECHNOLOGY L.L.C.; SECUREWORKS CORP.; EMC CORPORATION
To: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH
Reel/Frame 051449/0728 →
PATENT SECURITY AGREEMENT (NOTES) Recorded Dec 16, 2019
From: DELL PRODUCTS L.P.; EMC IP HOLDING COMPANY LLC; WYSE TECHNOLOGY L.L.C.; SECUREWORKS CORP.
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS COLLATERAL AGENT
Reel/Frame 051302/0528 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 27, 2019
From: KALIYAMOORTHY, KARTHI
To: DELL PRODUCTS L.P.
Reel/Frame 050515/0091 →
Continuity (1)
Related Publication 20210099379A1 · Apr 1, 2021