IP Library Granted Patent US 8,351,431
Granted Patent B2
US 8,351,431 · App. 12/772,504 · Granted Jan 8, 2013

Method and apparatus for providing fast reroute of a multicast packet within a network element to an available port associated with a multi-link trunk

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,351,431
App. No.
12/772,504
Granted
Jan 8, 2013
Kind
B2
Abstract

A method, apparatus and computer program product for providing a fast re-route of a multicast packet within a network element to an available port associated with a multi-link trunk is presented. A packet is received by a Forwarding Data Unit (FDU) in a data plane of a network element and a determination made that the packet is a multicast packet. The packet is forwarded to all egress FDUs having at least one port associated with at least one receiver of the multicast packet. A lookup is performed by each egress FDU in a synchronized local port state database to find a port for each receiver that is in an UP state. The packet is forwarded out the port to a receiver when the port is in the UP state and dropped when the port is in the DOWN state.

Claims (38)

1. A computer-implemented method in which a Forwarding Data Unit (FDU) performs operations providing a fast re-route of a multicast packet within a network element to an available port associated with a multi-link trunk, the method comprising the steps of:

receiving a packet by said FDU in a data plane of a network element;

determining that the packet is a multicast packet;

forwarding the packet to all egress FDUs having at least one port associated with at least one receiver of the multicast packet, said forwarding including determining if a receiver port is one of the group consisting of a stand alone port, a Multi Link trunk (MLT) group for a local FDU, and a MLT group for a remote FDU and forwarding a copy to each MLT member; and

performing a lookup by each egress FDU in a synchronized local port state database to find a port for each receiver that is in an UP state.

2. The method of claim 1 wherein when said receiver port is a standalone port then determining whether said standalone port is in an UP state or a DOWN state, forwarding said packet out said port to a receiver when said port is in the UP state and dropping said packet when said port is in the DOWN state.

3. The method of claim 1 wherein when said receiver port is an MLT group for a local FDU then locating a local port member from the local port state table that is in an UP state.

4. The method of claim 3 further comprising forwarding said packet out said port that is in an UP state and dropping said packet by all remote FDUs.

5. The method of claim 3 wherein a MLT Identifier (ID) and hash value are used to perform said lookup in said local port state database.

6. The method of claim 1 wherein when said receiver port is an MLT group for a remote FDU then checking remote port tables to determine whether any MLT ports on originating network element are in the UP state.

7. The method of claim 6 further comprising when one MLT port on the originating network element are in the UP state then dropping said packet by said remote FDUs.

8. The method of claim 6 further comprising when all MLT ports on the originating node are down then selecting one remote port to transmit said packet and dropping said packet by all other remote ports.

9. The method of claim 6 wherein a MLT Identifier (ID) and hash value are used to perform said lookup in said remote port state database.

10. A Forwarding Data Unit (FDU) comprising:

a memory;

a processor;

a communications interface;

an interconnection mechanism coupling the memory, the processor and the communications interface; and

wherein the memory is encoded with an application providing a fast re-route of a multicast packet within a network element to an available port associated with a multi-link trunk, that when performed on the processor, provides a process for processing information, the process causing the FDU to perform the operations of:

receiving a packet by said FDU in a data plane of a network element;

determining that the packet is a multicast packet;

forwarding the packet to all egress FDUs having at least one port associated with at least one receiver of the multicast packet, wherein said forwarding including determining if a receiver port is one of the group consisting of a stand alone port, a Multi Link trunk (MLT) group for a local FDU, and a MLT group for a remote FDU and forwarding a copy to each MLT member; and

performing a lookup by each egress FDU in a synchronized local port state database to find a port for each receiver that is in an UP state.

11. The FDU of claim 10 wherein when said receiver port is a standalone port then determining whether said standalone port is in an UP state or a DOWN state, forwarding said packet out said port to a receiver when said port is in the UP state and dropping said packet when said port is in the DOWN state.

12. The FDU of claim 10 wherein when said receiver port is an MLT group for a local FDU then locating a local port member from the local port state table that is in an UP state.

13. The FDU of claim 12 further comprising forwarding said packet out said port that is in an UP state and dropping said packet by all remote FDUs.

14. The FDU of claim 12 wherein a MLT Identifier (ID) and hash value are used to perform said lookup in said local port state database.

15. The FDU of claim 10 wherein when said receiver port is an MLT group for a remote FDU then checking remote port tables to determine whether any MLT ports on originating network element are in the UP state.

16. The FDU of claim 15 further comprising when one MLT port on the originating network element are in the UP state then dropping said packet by said remote FDUs.

17. The FDU of claim 15 further comprising when all MLT ports on the originating node are down then selecting one remote port to transmit said packet and dropping said packet by all other remote ports.

18. The FDU of claim 15 wherein a MLT Identifier (ID) and hash value are used to perform said lookup in said remote port state database.

19. A non-transitory computer readable storage medium having computer readable code thereon for providing a fast re-route of a multicast packet within a network element to an available port associated with a multi-link trunk, the medium including instructions in which a Forwarding Data Unit (FDU) performs operations comprising:

receiving a packet by said FDU in a data plane of a network element;

determining that the packet is a multicast packet;

forwarding the packet to all egress FDUs having at least one port associated with at least one receiver of the multicast packet, wherein said forwarding the packet to all egress FDUs having at least one port associated with at least one receiver of the multicast packet further comprises determining if a receiver port is one of the group consisting of a stand alone port, a Multi Link Trunk (MLT) group for a local FDU, and a MLT group for a remote FDU;

wherein when said receiver port is a standalone port then determining whether said standalone port is in an UP state or a DOWN state, and forwarding said packet out said port to a receiver when said port is in the UP state and dropping said packet when said port is in the DOWN state;

wherein when said receiver port is an MLT group for a local FDU then locating a local port member from the local port state table that is in an UP state, and forwarding said packet out said port to a receiver when said port is in the UP state and dropping said packet when a port in the UP state cannot be determined; and

wherein when said receiver port is an MLT group for a remote FDU then checking remote port tables to determine whether any MLT ports on originating network element are in the UP state; and forwarding said packet out said port to a receiver when said port is in the UP state and dropping said packet when a port in the UP state cannot be determined.

Assignments (20)
(SECURITY INTEREST) GRANTOR'S NAME CHANGE Recorded Sep 21, 2023
From: AVAYA INC.
To: AVAYA LLC
Reel/Frame 065019/0231 →
RELEASE OF SECURITY INTEREST IN PATENTS (REEL/FRAME 53955/0436) Recorded May 18, 2023
From: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS NOTES COLLATERAL AGENT
To: AVAYA MANAGEMENT L.P.; AVAYA INC.; INTELLISIST, INC.; AVAYA INTEGRATED CABINET SOLUTIONS LLC
Reel/Frame 063705/0023 →
RELEASE OF SECURITY INTEREST IN PATENTS (REEL/FRAME 61087/0386) Recorded May 18, 2023
From: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS NOTES COLLATERAL AGENT
To: AVAYA MANAGEMENT L.P.; AVAYA INC.; INTELLISIST, INC.; AVAYA INTEGRATED CABINET SOLUTIONS LLC
Reel/Frame 063690/0359 →
RELEASE OF SECURITY INTEREST IN PATENTS (REEL/FRAME 045034/0001) Recorded May 18, 2023
From: GOLDMAN SACHS BANK USA., AS COLLATERAL AGENT
To: AVAYA INC.; INTELLISIST, INC.; AVAYA INTEGRATED CABINET SOLUTIONS LLC; OCTEL COMMUNICATIONS LLC; VPNET TECHNOLOGIES, INC.; ZANG, INC. (FORMER NAME OF AVAYA CLOUD INC.); HYPERQUALITY, INC.; HYPERQUALITY II, LLC; CAAS TECHNOLOGIES, LLC; AVAYA MANAGEMENT L.P.
Reel/Frame 063779/0622 →
INTELLECTUAL PROPERTY SECURITY AGREEMENT Recorded May 4, 2023
From: AVAYA INC.; AVAYA MANAGEMENT L.P.; INTELLISIST, INC.
To: CITIBANK, N.A., AS COLLATERAL AGENT
Reel/Frame 063542/0662 →
INTELLECTUAL PROPERTY SECURITY AGREEMENT Recorded May 3, 2023
From: AVAYA MANAGEMENT L.P.; AVAYA INC.; INTELLISIST, INC.; KNOAHSOFT INC.
To: WILMINGTON SAVINGS FUND SOCIETY, FSB [COLLATERAL AGENT]
Reel/Frame 063742/0001 →
RELEASE OF SECURITY INTEREST IN PATENTS AT REEL 45124/FRAME 0026 Recorded Apr 26, 2023
From: CITIBANK, N.A., AS COLLATERAL AGENT
To: AVAYA HOLDINGS CORP.; AVAYA INC.; AVAYA MANAGEMENT L.P.; AVAYA INTEGRATED CABINET SOLUTIONS LLC
Reel/Frame 063457/0001 →
INTELLECTUAL PROPERTY SECURITY AGREEMENT Recorded Aug 5, 2022
From: AVAYA INC.; INTELLISIST, INC.; AVAYA MANAGEMENT L.P.; AVAYA CABINET SOLUTIONS LLC
To: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS COLLATERAL AGENT
Reel/Frame 061087/0386 →
SECURITY INTEREST Recorded Sep 25, 2020
From: AVAYA INC.; AVAYA MANAGEMENT L.P.; INTELLISIST, INC.; AVAYA INTEGRATED CABINET SOLUTIONS LLC
To: WILMINGTON TRUST, NATIONAL ASSOCIATION
Reel/Frame 053955/0436 →
SECURITY INTEREST Recorded Jan 23, 2018
From: AVAYA INC.; AVAYA INTEGRATED CABINET SOLUTIONS LLC; OCTEL COMMUNICATIONS LLC; VPNET TECHNOLOGIES, INC.; ZANG, INC.
To: CITIBANK, N.A., AS COLLATERAL AGENT
Reel/Frame 045124/0026 →
SECURITY INTEREST Recorded Jan 10, 2018
From: AVAYA INC.; AVAYA INTEGRATED CABINET SOLUTIONS LLC; OCTEL COMMUNICATIONS LLC; VPNET TECHNOLOGIES, INC.; ZANG, INC.
To: GOLDMAN SACHS BANK USA, AS COLLATERAL AGENT
Reel/Frame 045034/0001 →
BANKRUPTCY COURT ORDER RELEASING ALL LIENS INCLUDING THE SECURITY INTEREST RECORDED AT REEL/FRAME 041576/0001 Recorded Dec 15, 2017
From: CITIBANK, N.A.
To: AVAYA INC.; AVAYA INTEGRATED CABINET SOLUTIONS INC.; OCTEL COMMUNICATIONS LLC (FORMERLY KNOWN AS OCTEL COMMUNICATIONS CORPORATION); VPNET TECHNOLOGIES, INC.
Reel/Frame 044893/0531 →
BANKRUPTCY COURT ORDER RELEASING ALL LIENS INCLUDING THE SECURITY INTEREST RECORDED AT REEL/FRAME 030083/0639 Recorded Dec 15, 2017
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A.
To: AVAYA INC.
Reel/Frame 045012/0666 →
BANKRUPTCY COURT ORDER RELEASING ALL LIENS INCLUDING THE SECURITY INTEREST RECORDED AT REEL/FRAME 025863/0535 Recorded Dec 15, 2017
From: THE BANK OF NEW YORK MELLON TRUST, NA
To: AVAYA INC.
Reel/Frame 044892/0001 →
BANKRUPTCY COURT ORDER RELEASING ALL LIENS INCLUDING THE SECURITY INTEREST RECORDED AT REEL/FRAME 029608/0256 Recorded Dec 15, 2017
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A.
To: AVAYA INC.
Reel/Frame 044891/0801 →
SECURITY INTEREST Recorded Jan 27, 2017
From: AVAYA INC.; AVAYA INTEGRATED CABINET SOLUTIONS INC.; OCTEL COMMUNICATIONS CORPORATION; VPNET TECHNOLOGIES, INC.
To: CITIBANK, N.A., AS ADMINISTRATIVE AGENT
Reel/Frame 041576/0001 →
SECURITY AGREEMENT Recorded Mar 13, 2013
From: AVAYA, INC.
To: BANK OF NEW YORK MELLON TRUST COMPANY, N.A., THE
Reel/Frame 030083/0639 →
SECURITY AGREEMENT Recorded Jan 10, 2013
From: AVAYA, INC.
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A.
Reel/Frame 029608/0256 →
SECURITY AGREEMENT Recorded Feb 22, 2011
From: AVAYA INC., A DELAWARE CORPORATION
To: BANK OF NEW YORK MELLON TRUST, NA, AS NOTES COLLATERAL AGENT, THE
Reel/Frame 025863/0535 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 3, 2010
From: ASSAPOUR, HAMID
To: AVAYA INC.
Reel/Frame 024324/0733 →