IP Library Granted Patent US 7,080,161
Granted Patent B2
US 7,080,161 · App. 09/903,441 · Granted Jul 18, 2006

Routing information exchange

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 7,080,161
App. No.
09/903,441
Granted
Jul 18, 2006
Kind
B2
Abstract

Network architectures and protocols to support enhancements to the decision making process of standard routing protocols are described. Embodiments allow decisions to be exchanged between networks, or autonomous systems, about which internetwork paths have been chosen for outbound traffic. Some embodiments of the invention allow information about the measured performance of internetwork paths to be exchanged between autonomous systems. Embodiments allow additional policy information to be communicated between networks, including but not limited to information about why local policy decisions have been made; requests of policies from remote networks; performance information about particular paths; and informational status. Such information may be exchanged dynamically between networks.

Claims (85)

1. In an internetwork comprising a plurality of coupled autonomous systems, wherein the plurality of coupled autonomous systems communicate routing information via a Border Gateway Protocol (BGP), and the internetwork includes a routing overlay network to communicate routing parameters between the plurality of coupled autonomous systems, a BGP update message comprising:

a Network Layer Reachability Information (NLRI) field, the NLRI field including:

a first network prefix; and

a first network mask;

an origin attribute, the origin attribute including an identifier for the routing overlay network; and

a first community attribute, the first community attribute including:

an identifier for a private autonomous system from the plurality of autonomous systems.

2. The BGP update message of claim 1 , wherein the BGP update message is transmitted from the routing overlay network to one or more points of presence in the plurality of coupled autonomous systems.

3. The BGP update message of claim 1 , wherein the first network prefix and the first network mask comprise a first classless address, the first classless address identifying a first internetwork destination.

4. The BGP update message of claim 3 , wherein the first classless address is a member of an equivalence class of addresses, the equivalence class including a plurality of classless network addresses, wherein the plurality of classless network addresses are in geographical proximity.

5. The BGP update message of claim 3 , wherein the first classless address is a member of an equivalence class of addresses, the equivalence class including a plurality of classless network addresses, wherein the plurality of classless network addresses have jitter statistics within a pre-defined threshold.

6. The BGP update message of claim 3 , wherein the first classless address is a member of an equivalence class of addresses, the equivalence class including a plurality of classless network addresses, wherein the plurality of classless network addresses have packet loss statistics within a pre-defined threshold.

7. The BGP update message of claim 3 , wherein the first classless address is a member of an equivalence class of addresses, the equivalence class including a plurality of classless network addresses, wherein the plurality of classless network addresses have packet delay statistics within a predefined threshold.

8. The BGP update message of claim 3 , wherein the first classless address is a member of an equivalence class of addresses, the equivalence class including a plurality of classless network addresses, wherein the plurality of classless network addresses have similar jitter, delay, and loss statistics within a pre-determined threshold.

9. The BGP update message of claim 8 , wherein the equivalence class includes a second classless address, the second classless address including:

a second network prefix; and

a second network mask.

10. The BGP update message of claim 9 , wherein the second classless address identifies a second internetwork destination.

11. The BGP update message of claim 10 , further comprising:

a second community attribute, the second community attribute including:

the identifier for the private autonomous system; and

a scalar identifier for the equivalence class.

12. The BGP update message of claim 11 , wherein the identifier for the routing overlay network is 65534.

13. The BGP update message of claim 12 , wherein the identifier for the private autonomous system has the value 65001.

14. In an internetwork comprising a plurality of coupled autonomous systems, wherein the plurality of coupled autonomous systems communicate routing information via a Border Gateway Protocol (BGP), and the internetwork includes a routing overlay network to communicate routing parameters between the plurality of coupled autonomous systems, a method of identifying a classless network address as a member of an equivalence class, the equivalence class comprising a plurality of classless addresses, wherein a route for the classless address has already been advertised to the plurality of coupled autonomous systems, the method comprising:

generating a BGP update message, the BGP update message including:

a destination network for the classless address;

a network mask for the classless address;

an Autonomous System (AS) Path attribute, the AS Path attribute having a value of the route for the network destination; and

a first community attribute, the community attribute including:

an identifier for a private autonomous system from the plurality of coupled autonomous systems; and

forwarding the BGP update message from the routing overlay network to the plurality of coupled autonomous systems.

15. The method of claim 14 , wherein the first community attribute is a scalar with a value 65001.

16. The method of claim 15 , wherein the first community attribute further includes a value 0.

17. The method of claim 14 , wherein the plurality of classless addresses in the equivalence class have similar network performance characteristics.

18. The method of claim 17 , wherein the plurality of classless addresses are in geographic proximity.

19. The method of claim 17 , wherein the similar network performance characteristics include one or more of delay statistics, jitter statistics, and loss statistics.

20. The method of claim 17 , wherein the BGP update message further includes a second community attribute, the second community attribute including:

the scalar with the value 65001; and

a unique scalar identifier for the equivalence class.

21. In an internetwork comprising a plurality of coupled autonomous systems, wherein the plurality of coupled autonomous systems communicate routing information via a Border Gateway Protocol (BGP) and the internetwork includes a routing overlay network to communicate routing parameters between the plurality of coupled autonomous systems, a method of communicating network performance parameters for a route in the internetwork, the method comprising:

advertising a BGP update message from a point of presence in the internetwork to the routing overlay network; and

prior to advertising the BGP update message, generating the BGP update message, the BGP update message including:

a classless address for a network destination of the route, the classless address further including:

an identifier for the network destination; and

a mask for the network destination;

an autonomous system path attribute, indicating a chain of autonomous systems from the plurality of coupled autonomous systems traversed by the route; and

a community string including:

a first hop autonomous system indicating an ISP coupled to the point of presence; and

one or more value pairs including:

a type, indicating a type of performance measurement of the route; and

an argument, indicating a value of the performance measurement of the route.

22. The method of claim 21 , wherein the one or more value pairs includes a value pair indicating jitter measurements for the route, such that the type identifies the jitter measurement as jitter for the route, and the argument indicates the value for the jitter.

23. The method of claim 21 , wherein the one or more value pairs includes a value pair indicating packet drop measurement for the route, such that the type identifies the measurement as packet drop for the route, and the argument indicates the value for the packet drop.

24. The method of claim 21 , wherein the one or more value pairs includes a value pair indicating delay measurement for the route, such that the type identifies the measurement as delay for the route, and the argument indicates the value for the delay as delay.

25. The method of claim 21 , wherein the autonomous path attribute includes an identifier for the routing overlay network.

26. The method of claim 25 , wherein the identifier for the routing overlay network is 65534.

27. In an internetwork comprising a plurality of coupled autonomous systems, wherein the plurality of coupled autonomous systems (ASs) communicate routing information via a Border Gateway Protocol (BGP) and the internetwork includes a routing overlay network to communicate routing parameters between the plurality of coupled autonomous systems, a method of exchanging routing information between a source network and a destination network coupled to the internetwork, the method comprising:

inserting a BGP community into a BGP feed, the BGP community including:

a cooperative private autonomous system field, the cooperative private autonomous system field being between 65001 and 65100; and

a corresponding value corresponding to the cooperative private autonomous system field; and

exchanging the BGP feed between the source network and the destination network via the routing overlay network.

28. The method of claim 27 , wherein the cooperative private autonomous system field has a value of 65001, indicating that the value is an identifier of an equivalence class, the equivalence class including a group of network addresses.

29. The method of claim 28 , wherein the group of network addresses exhibit similar network performance characteristics.

30. The method of claim 28 , wherein the group of network addresses have similar measurements for jitter.

31. The method of claim 28 , wherein the group of network addresses have similar measurements for packet loss.

32. The method of claim 28 , wherein the group of network addresses have similar measurements for packet delay.

33. The method of claim 28 , wherein the group of network addresses are geographically proximate.

34. The method of claim 27 , wherein the cooperative private autonomous system field is 65002, such that the cooperative private autonomous system field indicates a request for symmetric AS path routing.

35. The method of claim 34 , wherein the corresponding value is zero.

36. The method of claim 27 , wherein the corresponding value is an AS from the plurality of coupled ASs, and the cooperative private autonomous system field has a value 65003, indicating that paths with the AS are preferred with first priority.

37. The method of claim 27 , wherein the corresponding value is an AS from the plurality of coupled ASs, and the cooperative private autonomous system field has a value 65004, indicating that paths with the AS are preferred with second priority.

38. The method of claim 27 , wherein the corresponding value is an AS from the plurality of coupled ASs, and the cooperative private autonomous system field has a value 65005, indicating that paths with the AS are preferred with third priority.

39. The method of claim 27 , wherein the corresponding value is an AS from the plurality of coupled ASs, and the cooperative private autonomous system field has a value 65006, indicating that paths with the AS are to be avoided with first priority.

40. The method of claim 27 , wherein the corresponding value is an AS from the plurality of coupled ASs, and the cooperative private autonomous system field has a value 65007, indicating that paths with the AS are to be avoided with second priority.

41. The method of claim 27 , wherein the corresponding value is an AS from the plurality of coupled ASs, and the cooperative private autonomous system field has a value 65008, indicating that paths with the AS are to be avoided with third priority.

42. The method of claim 27 , wherein the cooperative private autonomous system field has a value 65009, indicating a black hole Denial of Service Attack.

43. The method of claim 27 , wherein the cooperative private autonomous system field has a value 650010 indicating a rate limit Denial of Service Attack.

44. The method of claim 27 , wherein the cooperative private autonomous system field has a value 65011, indicating an informational Denial of Service Attack.

45. The method of claim 27 , wherein the cooperative private autonomous system field has a value 65012, indicating unacceptable packet loss.

46. The method of claim 45 , wherein the corresponding value indicates a packet loss number.

47. The method of claim 27 , wherein the cooperative private autonomous system field has a value 65013, indicating unacceptable jitter.

48. The method of claim 47 , wherein the corresponding value indicates a jitter number.

49. The method of claim 27 , wherein the cooperative private autonomous system field has a value 65014, indicating a performance metric.

50. The method of claim 49 , wherein the corresponding value is a scalar value of the performance metric.

Assignments (26)
(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 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 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 045034/0001) Recorded May 18, 2023
From: GOLDMAN SACHS BANK USA., AS COLLATERAL AGENT
To: ZANG, INC. (FORMER NAME OF AVAYA CLOUD INC.); AVAYA INC.; INTELLISIST, INC.; AVAYA INTEGRATED CABINET SOLUTIONS LLC; OCTEL COMMUNICATIONS LLC; VPNET TECHNOLOGIES, 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 →
BANKRUPTCY COURT ORDER RELEASING THE SECURITY INTEREST RECORDED AT REEL/FRAME 020156/0149 Recorded Jul 25, 2022
From: CITIBANK, N.A., AS ADMINISTRATIVE AGENT
To: AVAYA, INC.; AVAYA TECHNOLOGY LLC; OCTEL COMMUNICATIONS LLC; VPNET TECHNOLOGIES
Reel/Frame 060953/0412 →
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 →
RELEASE OF SECURITY INTEREST Recorded Jan 9, 2018
From: CITICORP USA, INC.
To: AVAYA, INC.; SIERRA HOLDINGS CORP.; AVAYA TECHNOLOGY, LLC; OCTEL COMMUNICATIONS LLC; VPNET TECHNOLOGIES, INC.
Reel/Frame 045032/0213 →
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 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 025863/0535 Recorded Dec 15, 2017
From: THE BANK OF NEW YORK MELLON TRUST, NA
To: AVAYA INC.
Reel/Frame 044892/0001 →
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 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 →
CONVERSION FROM CORP TO LLC Recorded Dec 29, 2008
From: AVAYA TECHNOLOGY CORP.
To: AVAYA TECHNOLOGY LLC
Reel/Frame 022071/0420 →
REASSIGNMENT Recorded Jun 27, 2008
From: AVAYA TECHNOLOGY LLC
To: AVAYA INC
Reel/Frame 021158/0319 →
SECURITY AGREEMENT Recorded Nov 28, 2007
From: AVAYA, INC.; AVAYA TECHNOLOGY LLC; OCTEL COMMUNICATIONS LLC; VPNET TECHNOLOGIES, INC.
To: CITICORP USA, INC., AS ADMINISTRATIVE AGENT
Reel/Frame 020166/0705 →
SECURITY AGREEMENT Recorded Nov 27, 2007
From: AVAYA, INC.; AVAYA TECHNOLOGY LLC; OCTEL COMMUNICATIONS LLC; VPNET TECHNOLOGIES, INC.
To: CITIBANK, N.A., AS ADMINISTRATIVE AGENT
Reel/Frame 020156/0149 →
RECORD TO CORRECT THE ASSIGNEE ON REEL 016132 FRAME 0744 Recorded Aug 1, 2005
From: ROUTESCIENCE TECHNOLOGIES, INC.
To: AVAYA TECHNOLOGY CORP.
Reel/Frame 016406/0134 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 10, 2005
From: ROUTESCIENCE TECHNOLOGIES, INC.
To: AVAYA INC.
Reel/Frame 016132/0744 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 22, 2001
From: LEDDY, JOHN G.; LLOYD, MICHAEL A.; FINN, SEAN P.; MCGUIRE, JAMES G.; BALDONADO, OMAR C.; MADAN, HERBERT S.
To: ROUTESCIENCE TECHNOLOGIES, INC.
Reel/Frame 012493/0743 →