IP Library Granted Patent US 10,164,886
Granted Patent B2
US 10,164,886 · App. 15/429,231 · Granted Dec 25, 2018

Route optimization using measured congestion

Inventors: Jozef Babiarz (Ontario, CA); Bakul Khanna (Lexington, MA)
Assignee: Avaya Inc.
H04L47/125H04L41/5022H04L43/08H04L45/10H04L45/125H04L45/22H04L45/38H04L47/17H04L41/5087
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 10,164,886
App. No.
15/429,231
Granted
Dec 25, 2018
Kind
B2
Abstract

A flow based routing method and apparatus selects a path from a plurality of different paths for assignment to a flow. The path is selected based on traffic performance measurements which identify relative congestion and performance of the different paths, so that traffic flows can be diverted away from network congestion points, thereby allowing network resources to be load balanced at a flow granularity. The present invention may be configured on physical or virtual links on an NE to enhance the forwarding of packets using the primary link and one or more alternate links to any given destination.

Claims (33)

1. A method for selecting a path for a flow comprising a plurality of packets, said method comprising:

performing, by a network element, traffic performance measurements on a primary path to determine congestion, Quality of Service (QoS), and connectivity; and

selectively routing, by the network element, the flow to an outbound link around the primary path in response to a comparison of the congestion, QoS, and connectivity of the primary path with congestion, QoS, and connectivity of an alternate path.

2. The method of claim 1 , wherein the traffic performance measurements indicate that the primary path is in a blackout condition indicating a failure in the primary path.

3. The method of claim 2 , wherein the failure is one of a link failure or a node failure.

4. The method of claim 1 , wherein the flow traverses one of a local area network or a wide area network.

5. The method of claim 1 , further comprising:

identifying, by the network element, traffic performance measurements on all paths to a destination of the flow; and

selectively routing, by the network element, a new flow onto the primary path based on the traffic performance measurements of all paths.

6. The method of claim 1 , further comprising:

storing, by the network element, for each known endpoint, a primary next hop node identifier and one or more alternate next hop node identifiers.

7. The method of claim 6 , wherein the outbound link is identified using a list of primary and alternate next hop identifiers.

8. The method of claim 1 , further comprising:

receiving, by the network element, a packet;

generating, by the network element, a key using information in the packet;

determining, by the network element, using the key, whether the outbound link for forwarding the packet has been previously identified; and

in response to a determination that the outbound link has not been previously identified, identifying and selecting the outbound link.

9. The method of claim 8 , wherein determining whether the outbound link has been previously identified comprises indexing a flow cache using the key, wherein a flow state stores the outbound link.

10. The method of claim 9 , wherein generating the key comprises use of at least one of a Source IP address (SRC IP), a Destination IP address (DST IP), a Differentiated Service Code Point (DSCP), a Source Port, or a Destination Port included in the packet.

11. A network element comprising:

real-time traffic performance measurement logic for performing traffic performance measurements on a primary path to determine congestion, Quality of Service (QoS), and connectivity; and

first packet processing logic for selectively routing a flow to an outbound link around the primary path in response to a comparison of the congestion, QoS, and connectivity of the primary path with congestion, QoS, and connectivity of an alternate path.

12. The network element of claim 11 , wherein the traffic performance measurements indicate that the primary path is in a blackout condition indicating a failure in the primary path.

13. The network element of claim 12 , wherein the failure is one of a link failure or a node failure.

14. The network element of claim 11 , wherein the flow traverses one of a local area network or a wide area network.

15. The network element of claim 11 , wherein the real-time traffic performance measurement logic:

identifies traffic performance measurements on all paths to a destination of the flow; and

selectively routes a new flow onto the primary path based on the traffic performance measurements of all paths.

16. The network element of claim 11 , further comprising: a memory for storing, for each known endpoint, a primary next hop node identifier and one or more alternate next hop node identifiers.

17. The network element of claim 16 , wherein the outbound link is identified using a list of primary and alternate next hop identifiers.

18. The network element of claim 11 , further comprising: packet classification logic for receiving a packet, generating a key using information in the packet, and determining, using the key, whether the outbound link for forwarding the packet has been previously identified, wherein the first packet processing logic identifies and selects the outbound link in response to a determination that the outbound link has not been previously identified.

19. The network element of claim 18 , wherein determining whether the outbound link has been previously identified comprises indexing a flow cache using the key, wherein a flow state stores the outbound link.

20. The network element of claim 19 , wherein generating the key comprises use of at least one of a Source IP address (SRC IP), a Destination IP address (DST IP), a Differentiated Service Code Point (DSCP), a Source Port, or a Destination Port included in the packet.

Assignments (11)
(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 →
Continuity (5)
Division 11530579 · Sep 11, 2006
Continuation In Part 11251252 · Oct 14, 2005
Provisional Application 60716181 · Sep 12, 2005
Provisional Application 60708963 · Aug 17, 2005
Related Publication 20170155589A1 · Jun 1, 2017