IP Library Granted Patent US 8,619,605
Granted Patent B2
US 8,619,605 · App. 12/772,457 · Granted Dec 31, 2013

Method and apparatus for maintaining port state tables in a forwarding plane of a network element

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,619,605
App. No.
12/772,457
Granted
Dec 31, 2013
Kind
B2
Abstract

A method, apparatus and computer program product for maintaining port state tables in a forwarding plane of a network element are presented. The state of a first set of ports associated with a first Forwarding Data Unit (FDU) are periodically determined, the first FDU being one of a plurality of FDUs. The determined state is used to update a first port state table of the port state database associated with the first FDU. The determined state is transmitted to each other FDUs on the network element to enable each of the other FDUs to store the state of the first set of ports in a port state database local to each of the other FDUs. The port state database is used by the forwarding plane to perform fast reroute of packets.

Claims (34)

1. A method of maintaining a port state database in a forwarding plane of a network element, the method comprising the steps of:

periodically determining, by the network element, a state of a first set of ports associated with a first Forwarding Data Unit (FDU), the first FDU being one of a plurality of FDUs implementing forwarding functions within the forwarding plane of the network element;

using, by the network element, the determined state to update a first port state table of the port state database associated with the first FDU; and

transmitting the determined state to each other FDUs on the network element to enable each of said other FDUs to store the state of the first set of ports in a port state database local to each of said other FDUs.

2. The method of claim 1 further comprising maintaining, by the network element, physical link states and connection states for local ports and remote ports in said first port state database.

3. The method of claim 2 wherein said first port state database includes a local port data table and a remote port data table, and wherein physical link states and connection states for local ports are maintained in said local port data table and wherein physical link states and connection states for remote ports are maintained in said remote port data table.

4. The method of claim 3 further comprising maintaining, by the network element, Multi-Link Trunk (MLT) port member state that are on said first FDU within said local port data table and maintaining Multi-Link Trunk (MLT) port member state that are on said other FDUs within said remote port data table.

5. The method of claim 1 further comprising receiving a heartbeat packet containing local physical link status of ports on a line card containing said first FDU and wherein said first FDU uses the local physical link status of ports on the line card of said heartbeat packet to update said port state database.

6. The method of claim 5 further comprising maintaining a timer for each of said other FDUs to determine if heartbeat packets are received from said other FDUs, wherein in the event a timer expires before receiving a heartbeat packet from the FDU associated with that timer, each port associated with that FDU is determined to be in the DOWN state so that packets are not sent to ports having the DOWN state until that FDU is restored.

7. The method of claim 6 further comprising maintaining a pair of local timers per attached port of said first FDU, the attached port configured in a logical/virtual connection wherein one of said local timers is used to generate heartbeat packets to be sent over said attached port and wherein another of said local timers is used to detect connection failure of the attached port when a connection failure exists when the sent heartbeat packet is not received.

8. The method of claim 7 wherein said first FDU updates its port state database with the arrival of heartbeat packets and timer expirations.

9. The method of claim 1 further comprising using, by the network element, the port state database by said forwarding plane to perform fast reroute of packets.

10. A network element 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 maintaining a port state database, that when performed on the processor, provides a process for processing information, the process causing the network element to perform the operations of:

periodically determining a state of a first set of ports associated with a first Forwarding Data Unit (FDU), the first FDU being one of a plurality of FDUs implementing forwarding functions within the forwarding plane of the network element;

using the determined state to update a first port state table of the port state database associated with the first FDU; and

transmitting the determined state to each other FDUs on the network element to enable each of said other FDUs to store the state of the first set of ports in a port state database local to each of said other FDUs.

11. The network element of claim 10 further comprising performing the operation of maintaining physical link states and connection states for local ports and remote ports in said first port state database.

12. The network element of claim 11 wherein said first port state database includes a local port data table and a remote port data table, and wherein physical link states and connection states for local ports are maintained in said local port data table and wherein physical link states and connection states for remote ports are maintained in said remote port data table.

13. The network element of claim 12 further comprising performing the operation of maintaining Multi-Link Trunk (MLT) port member state that are on said first FDU within said local port data table and maintaining Multi-Link Trunk (MLT) port member state that are on said other FDUs within said remote port data table.

14. The network element of claim 10 further comprising performing the operation of receiving a heartbeat packet containing local physical link status of ports on a line card containing said first FDU and wherein said first FDU uses the local physical link status of ports on the line card of said heartbeat packet to update said port state database.

15. The network element of claim 14 further comprising performing the operation of maintaining a timer for each of said other FDUs to determine if heartbeat packets are received from said other FDUs, wherein in the event a timer expires before receiving a heartbeat packet from the FDU associated with that timer, each port associated with that FDU is determined to be in the DOWN state so that packets are not sent to ports having the DOWN state until that FDU is restored.

16. The network element of claim 15 further comprising performing the operation of maintaining a pair of local timers per attached port of said first FDU, the attached port configured in a logical/virtual connection wherein one of said local timers is used to generate heartbeat packets to be sent over said attached port and wherein another of said local timers is used to detect connection failure of the attached port when a connection failure exists when the sent heartbeat packet is not received.

17. The network element of claim 16 wherein said first FDU updates its port state database with the arrival of heartbeat packets and timer expirations.

18. The network element of claim 10 further comprising performing the operation of using the port state database by said forwarding plane to perform fast reroute of packets.

19. A non-transitory computer readable storage medium having computer readable code thereon for maintaining a port state database, the medium including instructions in which a computer system performs operations comprising:

periodically determining a state of a first set of ports associated with a first Forwarding Data Unit (FDU), the first FDU being one of a plurality of FDUs implementing forwarding functions within the forwarding plane of the network element;

using the determined state to update a first port state table of the port state database associated with the first FDU; and

transmitting the determined state to each other FDUs on the network element to enable each of said other FDUs to store the state of the first set of ports in a port state database local to each of said other FDUs.

20. The non-transitory computer readable storage medium of claim 19 further comprising instructions for performing the operation of maintaining physical link states and connection states for local ports and remote ports in said first port state database, wherein said first port state database includes a local port data table and a remote port data table, and wherein physical link states and connection states for local ports are maintained in said local port data table and wherein physical link states and connection states for remote ports are maintained in said remote port data table, and using the port state database by said forwarding plane to perform fast reroute of packets.

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: ASSARPOUR, HAMID
To: AVAYA INC.
Reel/Frame 024324/0525 →