IP Library Granted Patent US 8,345,683
Granted Patent B1
US 8,345,683 · App. 11/496,995 · Granted Jan 1, 2013

Data plane independent assert election

Assignee: Alcatel Lucent
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 8,345,683
App. No.
11/496,995
Granted
Jan 1, 2013
Kind
B1
Abstract

A data plane independent assert election is disclosed. A join message directed to a peer is received. An election procedure to avoid duplicative forwarding of multicast traffic is initiated based at least in part on a determination that the join message would result in duplicative forwarding of multicast traffic.

Claims (33)

1. A method of avoiding duplicative forwarding of multicast traffic, comprising:

receiving at a first router a join message directed to a peer router of the first router from a first downstream node of the first router and the peer router without passing through the peer router, the join message indicating that one or more downstream nodes of the peer desire to receive from the peer multicast traffic specified in the join message;

determining whether the join message from the first downstream node to the peer would result in duplicative forwarding by the peer of multicast traffic from an upstream source upstream of the peer and the first router based on the join message; and

initiating, based at least in part on a determination that the join message would result in duplicative forwarding of the multicast traffic, an election procedure to avoid such duplicative forwarding of the multicast traffic;

wherein determining whether the join message to the peer would result in duplicative forwarding of the multicast traffic comprises determining whether the join message would result in two or more routers being configured to forward the same multicast traffic onto a same network segment before the two or more routers are configured to forward the same multicast traffic onto the same network segment;

wherein determining whether the join message to the peer would result in duplicative forwarding of the multicast traffic comprises determining whether a previous join message associated with a multicast group with which the received join message is associated was received previously.

2. The method as recited in claim 1 wherein the network segment comprises one or more of the following: a local area network (LAN), a wide area network (WAN), an RFC 2547 based network, and a virtual private network.

3. The method as recited in claim 1 , wherein the join message comprises a PIM-SM join message.

4. The method as recited in claim 1 , wherein the election procedure comprises a PIM-SM assert election.

5. The method as recited in claim 1 , wherein determining whether the join message to the peer would result in duplicative forwarding of the multicast traffic comprises determining whether a routing entry associated with a multicast group with which the join message is associated exists.

6. The method as recited in claim 1 , wherein the election procedure is initiated with respect to the peer.

7. The method as recited in claim 1 , wherein initiating an election procedure comprises sending an assert message to the peer.

8. A computer system, comprising:

a communication interface; and

a processor configured to:

receive via the communication interface at a first router a join message directed to a peer router of the first router from a first downstream node of the first router and the peer router without passing through the peer router, the join message indicating that one or more downstream nodes of the peer desire to receive from the peer multicast traffic specified in the join message;

determine whether the join message from the first downstream node to the peer would result in duplicative forwarding by the peer of multicast traffic from an upstream source upstream of the peer and the first router based on the join message; and

initiate, based at least in part on a determination that the join message would result in duplicative forwarding of multicast traffic, an election procedure to avoid such duplicative forwarding of multicast traffic;

wherein determining whether the join message to the peer would result in duplicative forwarding of the multicast traffic comprises determining whether the join message would result in two or more routers being configured to forward the same multicast traffic onto a same network segment before the two or more routers are configured to forward the same multicast traffic onto the same network segment;

wherein the processor is configured to determine whether the join message to the peer would result in duplicative forwarding of the multicast traffic at least in part by determining whether a previous join message associated with a multicast group with which the received join message is associated was received previously.

9. The computer system as recited in claim 8 , wherein the communication interface and the processor comprise a router.

10. The computer system as recited in claim 8 , wherein the processor is configured to determine whether the join message to the peer would result in duplicative forwarding of the multicast traffic at least in part by determining whether the join message would result in two or more routers being configured to forward the same multicast traffic onto the network segment.

11. The computer system as recited in claim 8 , wherein the processor is configured to determine whether the join message to the peer would result in duplicative forwarding of the multicast traffic at least in part by determining whether a routing entry associated with a multicast group with which the join message is associated exists.

12. The computer system as recited in claim 8 , wherein the processor is configured to initiate the election procedure at least in part by sending an assert message to the peer.

13. A computer program product for avoiding duplicative forwarding of multicast traffic, the computer program product being embodied in a non-transitory tangible computer readable medium and comprising computer instructions for:

receiving at a first router a join message directed to a peer router of the first router from a first downstream node of the first router and the peer router without passing through the peer router, the join message indicating that one or more downstream nodes of the peer desire to receive from the peer multicast traffic specified in the join message;

determining whether the join message from the first downstream node to the peer would result in duplicative forwarding by the peer of multicast traffic from an upstream source upstream of the peer and the first router based on the join message; and

initiating based at least in part on a determination that the join message would result in duplicative forwarding of the multicast traffic an election procedure to avoid such duplicative forwarding of the multicast traffic;

wherein determining whether the join message to the peer would result in duplicative forwarding of the multicast traffic comprises determining whether the join message would result in two or more routers being configured to forward the same multicast traffic onto a same network segment before the two or more routers are configured to forward the same multicast traffic onto the same network segment;

wherein determining whether the join message to the peer would result in duplicative forwarding of the multicast traffic comprises determining whether a previous join message associated with a multicast group with which the received join message is associated was received previously.

14. The computer program product as recited in claim 13 , wherein determining whether the join message to the peer would result in duplicative forwarding of multicast traffic comprises determining whether the join message would result in two or more routers being configured to forward the same multicast traffic onto the network segment.

15. The computer program product as recited in claim 14 , wherein the network segment comprises one or more of the following: a local area network (LAN), a wide area network (WAN), an RFC 2547 based network, and a virtual private network.

16. The computer program product as recited in claim 13 , wherein determining whether the join message to the peer would result in duplicative forwarding of the multicast traffic comprises determining whether a routing entry associated with a multicast group with which the join message is associated exists.

Assignments (14)
PATENT SECURITY AGREEMENT Recorded Aug 6, 2024
From: RPX CORPORATION; RPX CLEARINGHOUSE LLC
To: BARINGS FINANCE LLC, AS COLLATERAL AGENT
Reel/Frame 068328/0674 →
RELEASE OF LIEN ON PATENTS Recorded Aug 5, 2024
From: BARINGS FINANCE LLC
To: RPX CORPORATION
Reel/Frame 068328/0278 →
PATENT SECURITY AGREEMENT Recorded Apr 22, 2023
From: RPX CORPORATION
To: BARINGS FINANCE LLC, AS COLLATERAL AGENT
Reel/Frame 063429/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 28, 2021
From: PROVENANCE ASSET GROUP LLC
To: RPX CORPORATION
Reel/Frame 059352/0001 →
RELEASE OF SECURITY INTEREST Recorded Nov 30, 2021
From: NOKIA US HOLDINGS INC.
To: PROVENANCE ASSET GROUP HOLDINGS LLC; PROVENANCE ASSET GROUP LLC
Reel/Frame 058363/0723 →
RELEASE OF SECURITY INTEREST Recorded Nov 30, 2021
From: CORTLAND CAPITAL MARKETS SERVICES LLC
To: PROVENANCE ASSET GROUP HOLDINGS LLC; PROVENANCE ASSET GROUP LLC
Reel/Frame 058983/0104 →
ASSIGNMENT AND ASSUMPTION AGREEMENT Recorded Feb 14, 2019
From: NOKIA USA INC.
To: NOKIA US HOLDINGS INC.
Reel/Frame 048370/0682 →
SECURITY INTEREST Recorded Sep 13, 2017
From: PROVENANCE ASSET GROUP HOLDINGS, LLC; PROVENANCE ASSET GROUP LLC
To: NOKIA USA INC.
Reel/Frame 043879/0001 →
SECURITY INTEREST Recorded Sep 13, 2017
From: PROVENANCE ASSET GROUP HOLDINGS, LLC; PROVENANCE ASSET GROUP, LLC
To: CORTLAND CAPITAL MARKET SERVICES, LLC
Reel/Frame 043967/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 13, 2017
From: NOKIA TECHNOLOGIES OY; NOKIA SOLUTIONS AND NETWORKS BV; ALCATEL LUCENT SAS
To: PROVENANCE ASSET GROUP LLC
Reel/Frame 043877/0001 →
RELEASE OF SECURITY INTEREST Recorded Sep 30, 2014
From: CREDIT SUISSE AG
To: ALCATEL LUCENT
Reel/Frame 033868/0001 →
SECURITY AGREEMENT Recorded Jan 30, 2013
From: ALCATEL LUCENT
To: CREDIT SUISSE AG
Reel/Frame 029821/0001 →
CHANGE OF NAME Recorded Oct 31, 2012
From: ALCATEL
To: ALCATEL LUCENT
Reel/Frame 029219/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 31, 2006
From: HEMIGE, VENUGOPAL V.
To: ALCATEL
Reel/Frame 018145/0516 →