IP Library Granted Patent US 7,245,619
Granted Patent B1
US 7,245,619 · App. 10/160,141 · Granted Jul 17, 2007

Method and apparatus for managing routes

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,245,619
App. No.
10/160,141
Granted
Jul 17, 2007
Kind
B1
Abstract

A method and apparatus for managing routes. A route manager receives a route to a destination, the route having been discovered by a routing protocol application. The route manager maintains the route in a route table and distributes the route to a second routing protocol application. In addition, the route manager maintains a subset of the routes in a second route table and distributes routes to a subsidiary application not having access to the routing protocol applications. The route manager recovers routes when a routing protocol application becomes inoperable by setting a timer when the routing protocol application becomes inoperable and purging routes when the route manager cannot confirm the routes upon expiration of the timer.

Claims (76)

1. A method for managing routes in a packet switched network, the method comprising:

receiving in a user space of a network device in a packet switched network a route to a destination, the route having been discovered by a routing protocol application;

maintaining the route in a route table in the user space; and

distributing the route from the route table in the user space to a second routing protocol application.

2. The method of claim 1 , further comprising:

maintaining a subset of routes in a second route table in a high-speed forwarding space of the network device.

3. The method of claim 2 , wherein the subset comprises routes determined to be the best route to each of the destinations.

4. The method of claim 1 , further comprising:

distributing the route from the route table in the user space to a subsidiary application not having access to the routing protocol applications.

5. The method of claim 4 , wherein the subsidiary application maintains the distributed route in a subsidiary route table in the user space.

6. The method of claim 4 , wherein distributing the route further comprises distributing a subset of routes in bulk from the route table in the user space to the subsidiary application.

7. The method of claim 6 , wherein the subset of routes comprises routes determined to be the best route to each of the destinations.

8. The method of claim 6 , wherein the subset of routes comprises routes associated with the same routing protocol application.

9. The method of claim 6 , wherein the subset of routes comprises routes associated with at least one of a group of destinations.

10. The method of claim 6 , wherein the subset of routes comprises routes associated with a best route to at least one of a group of destinations.

11. The method of claim 1 , further comprising recovering the route when the routing protocol application is inoperable.

12. The method of claim 11 , wherein recovering includes:

setting a timer when the routing protocol application becomes inoperable; and

purging the route from the route table in the user space when the route cannot be confirmed upon expiration of the timer.

13. The method of claim 12 , wherein the route cannot be confirmed when the route is not rediscovered upon expiration of the timer.

14. The method of claim 12 , wherein the route cannot be confirmed when a time stamp of the route is not updated after setting the timer.

15. A method for managing routes in a packet switched network, the method comprising:

receiving in a user space of a network device in a packet switched network a route to a destination, the route having been discovered by a routing protocol application;

maintaining the route in a route table in the user space; and

distributing the route from the route table in the user space to a subsidiary application not having access to the routing protocol application.

16. The method of claim 15 , wherein the subsidiary application maintains the distributed route in a subsidiary route table in the user space.

17. The method of claim 15 , wherein distributing the route further comprises distributing a subset of routes in bulk from the route table in the user space to the subsidiary application.

18. The method of claim 17 , wherein the subset of routes comprises routes determined to be the best route to each of the destinations.

19. The method of claim 17 , wherein the subset of routes comprises routes associated with the same routing protocol application.

20. The method of claim 17 , wherein the subset of routes comprises routes associated with at least one of a group of destinations.

21. A method for managing routes in a packet switched network the method comprising:

receiving in a user space of a network device in a packet switched network a route to a destination, the route having been discovered by a routing protocol application;

maintaining the route in a route table in the user space; and

recovering the route in the route table in the user space when the routing protocol application is inoperable.

22. The method of claim 21 , wherein recovering includes:

setting a timer when the routing protocol application becomes inoperable; and

purging the route from the route table in the user space when the route cannot be confirmed upon expiration of the timer.

23. The method of claim 22 , wherein the route cannot be confirmed when the route is not rediscovered upon expiration of the timer.

24. The method of claim 22 , wherein the route cannot be confirmed when a time stamp of the route is not updated after setting the timer.

25. A system for managing routes in a packet switched network, the system comprising:

an input receiver to receive, in a user space of a switching device in a packet switched network, a route to a destination in the network, the route having been discovered by a routing protocol application;

a processing system to generate a route table in the user space of the switching device based on a received route and to distribute the received route from the route table in the user space to a second routing protocol application.

26. The system of claim 25 , wherein the processing system maintains a subset of routes in a second route table in a high-speed forwarding space of the switching device.

27. The system of claim 26 , wherein the subset of routes comprises routes determined to be the best route to each of the destinations.

28. The system of claim 25 , wherein the processing system distributes the route from the route table in the user space to a subsidiary application not having access to the routing protocol application.

29. The system of claim 28 , wherein the processing system maintains the distributed route in a subsidiary route table in the user space.

30. The system of claim 28 , wherein distributing the route further comprises distributing a subset of routes in bulk from the route table in the user space to the subsidiary application.

31. The system of claim 30 , wherein the subset of routes comprises routes determined to be the best route to each of the destinations.

32. The system of claim 30 , wherein the subset of routes comprises routes associated with the same routing protocol application.

33. The system of claim 30 , wherein the subset of routes comprises routes associated with at least one of a group of destinations.

34. The system of claim 30 , wherein the subset of routes comprises routes associated with a best route to at least one of a group of destinations.

35. The system of claim 25 , wherein the processing system recovers the route when the routing protocol application is inoperable.

36. The system of claim 35 , wherein recovering includes:

setting a timer when the routing protocol application becomes inoperable; and

purging the route from the route table in the user space when the route cannot be confirmed upon expiration of the timer.

37. The system of claim 36 , wherein the route cannot be confirmed when the route is not rediscovered upon expiration of the timer.

38. The system of claim 36 , wherein the route cannot be confirmed when a time stamp of the route is not updated after setting the timer.

39. An apparatus for managing routes in a packet switched network, the apparatus comprising:

a route manager operating in a user space of the apparatus to receive a route to a destination, the route having been discovered by a routing protocol application, maintain the route in a route table in the user space, and distribute the route from the route table in the user space to a second routing protocol application; and

the route table in the user space containing the route.

40. The apparatus of claim 39 , further comprising:

a second route table in a fast switching space of the apparatus containing a subset of routes present in the route table in the user space, the subset of routes having been determined by the route manager.

41. The apparatus of claim 40 , wherein the subset of routes comprises routes determined to be the best route to each of the destinations.

42. The apparatus of claim 39 , further comprising:

a subsidiary application not having access to the routing protocol application, the route manager distributing the route from the route table in the user space to the subsidiary application.

43. The apparatus of claim 42 , further comprising:

a subsidiary route table in the user space containing the distributed route, the subsidiary route table being maintained by the subsidiary application.

44. The apparatus of claim 42 , wherein the route manager distributes a subset of routes in bulk from the route table in the user space to the subsidiary application.

45. The apparatus of claim 44 , wherein the subset of routes comprises routes determined to be the best route to each of the destinations.

46. The apparatus of claim 44 , wherein the subset of routes comprises routes associated with the same routing protocol application.

47. The apparatus of claim 44 , wherein the subset of routes comprises routes associated with at least one of a group of destinations.

48. The apparatus of claim 39 , wherein the route manager recovers the route when the routing protocol application is inoperable.

49. The apparatus of claim 48 , further comprising:

a timer, the route manager to start the timer when the routing protocol application becomes inoperable and purge the route from the route table in the user space when the route cannot be confirmed upon expiration of the timer.

50. The apparatus of claim 49 , wherein the route cannot be confirmed when the route is not rediscovered upon expiration of the timer.

51. The apparatus of claim 49 , wherein the route cannot be confirmed when a time stamp of the route is not updated after the route manager starts the timer.

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 →
RELEASE OF SECURITY INTEREST Recorded Oct 26, 2020
From: JEFFERIES FINANCE LLC
To: RPX CORPORATION
Reel/Frame 054486/0422 →
PATENT SECURITY AGREEMENT Recorded Oct 23, 2020
From: RPX CLEARINGHOUSE LLC; RPX CORPORATION
To: BARINGS FINANCE LLC, AS COLLATERAL AGENT
Reel/Frame 054198/0029 →
PATENT SECURITY AGREEMENT Recorded Oct 23, 2020
From: RPX CLEARINGHOUSE LLC; RPX CORPORATION
To: BARINGS FINANCE LLC, AS COLLATERAL AGENT
Reel/Frame 054244/0566 →
SECURITY INTEREST Recorded Aug 15, 2019
From: RPX CORPORATION
To: JEFFERIES FINANCE LLC
Reel/Frame 050064/0326 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 24, 2019
From: EXTREME NETWORK, INC
To: RPX CORPORATION
Reel/Frame 049852/0800 →
PARTIAL RELEASE OF SECURITY INTEREST IN PATENTS Recorded Jun 28, 2019
From: BANK OF MONTREAL
To: EXTREME NETWORKS, INC.
Reel/Frame 049630/0240 →
RELEASE OF SECURITY INTEREST Recorded May 1, 2018
From: SILICON VALLEY BANK
To: EXTREME NETWORKS, INC.
Reel/Frame 046051/0775 →
SECURITY INTEREST Recorded May 1, 2018
From: EXTREME NETWORKS, INC.
To: BANK OF MONTREAL
Reel/Frame 046050/0546 →
THIRD AMENDED AND RESTATED PATENT AND TRADEMARK SECURITY AGREEMENT Recorded Oct 31, 2017
From: EXTREME NETWORKS, INC.
To: SILICON VALLEY BANK
Reel/Frame 044639/0300 →
SECOND AMENDED AND RESTATED PATENT AND TRADEMARK SECURITY AGREEMENT Recorded Jul 14, 2017
From: EXTREME NETWORKS, INC.
To: SILICON VALLEY BANK
Reel/Frame 043200/0614 →
AMENDED AND RESTATED PATENT AND TRADEMARK SECURITY AGREEMENT Recorded Oct 31, 2016
From: EXTREME NETWORKS, INC.
To: SILICON VALLEY BANK
Reel/Frame 040521/0762 →
SECURITY AGREEMENT Recorded Jul 27, 2015
From: EXTREME NETWORKS, INC.
To: SILICON VALLEY BANK
Reel/Frame 036189/0284 →