IP Library Granted Patent US 8,400,941
Granted Patent B2
US 8,400,941 · App. 12/023,026 · Granted Mar 19, 2013

Systems and methods for inferring services on a network

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,400,941
App. No.
12/023,026
Granted
Mar 19, 2013
Kind
B2
Abstract

Systems and methods are disclosed for managing services on a network. In one exemplary embodiment, the method includes receiving topologically relevant network information concerning nodes, interfaces, connections and/or protocols; resolving conflicts in the received information; determining and storing a network topology from the received and resolved information; and inferring one or more services based on the stored topology.

Claims (68)

1. A method for storing information associated with a network, the method comprising:

receiving and storing first network information at a first time;

monitoring protocol update information communicated between nodes of the network,

detecting a network event at a second time based on the protocol update information;

receiving and storing second network information based on the event;

determining one or more virtual private network services that are affected by the event based on the first network information and the second network information; and

displaying an indication of the one or more virtual private network services that are affected by the event, and at least one of: performance information and topology information based on at least one of the first network information and the second information.

2. The method of claim 1 , wherein receiving the first and second network information includes receiving, as the network information, at least one of the following types of information: performance, event, topology, service, and object.

3. The method of claim 1 , wherein receiving the first network information includes receiving network information periodically.

4. The method of claim 1 , including indicating that a failure is the event.

5. The method of claim 1 , including indicating that crossing a performance threshold is the event.

6. The method of claim 1 , including detecting a plurality of events.

7. The method of claim 6 , including storing a plurality of other network information based on the plurality of events.

8. The method of claim 1 , wherein storing the second network information based on the event includes storing the second network information from a time of the event until a time after the event.

9. The method of claim 8 , including displaying the second network information based on the time of the event and the time after the event.

10. The method of claim 1 , including estimating additional network information at one or more times for which there is no stored network information.

11. The method of claim 10 , including displaying the performance information based on the estimated additional network information.

12. The method of claim 10 , including determining and displaying other topology information based on the estimated additional network information.

13. The method of claim 1 , including structuring a database to represent the network.

14. The method of claim 13 , including correlating the first network information with the structured database, such that the correlated first network information is stored in the structured database.

15. The method of claim 13 , including displaying information based on the structured database.

16. The method of claim 15 , including displaying the information at a pace chosen by a user.

17. The method of claim 15 , including replaying the displayed information instantly.

18. The method of claim 1 , including compressing the first network information.

19. The method of claim 1 , wherein the displaying includes concurrently displaying the indication of the one or more virtual private network services that are affected by the event, the performance information, and the topology information.

20. The method of claim 1 , wherein monitoring the protocol update information includes configuring a processor to receive routing information by posing as a router.

21. A system for storing information associated with a network, the system comprising:

means for receiving and storing first network information at a first time;

means for monitoring protocol update information communicated between nodes of the network;

means for detecting a network event at a second time based on the protocol update information;

means for receiving second network information based on the event;

means for determining one or more virtual private network services that are affected by the event based on the first network information and the second network information; and

means for displaying an indication of the one or more virtual private network services that are affected by the event, and at least one of: performance information and topology information based on at least one of the first network information and the second information.

22. The means of claim 21 , wherein the means for displaying includes means for concurrently displaying the indication of the one or more virtual private network services that are affected by the event, the performance information, and the topology information.

23. A system for storing information associated with a network, the system including:

a processor, and

a memory,

wherein the processor is configured to:

receive first network information at a first time;

store the first network information in the memory;

monitor protocol update information communicated between nodes of the network;

detect a network event at a second time based on the protocol update information;

receive second network information based on the event;

determine one or more virtual private network services that are affected by the event based on the first network information and the second network information; and

display an indication of the one or more virtual private network services that are affected by the event, and at least one of: performance information and topology information based on at least one of the first network information and the second information.

24. The system of claim 23 , wherein the first and second network information includes at least one of performance, event, topology, service, and object.

25. The system of claim 23 , wherein the processor is configured to receive the first network information periodically.

26. The system of claim 23 , wherein the event includes a failure, and the processor is configured to provide an indication of the failure.

27. The system of claim 23 , wherein the event includes crossing a performance threshold, and the processor is configured to provide an indication of the crossing.

28. The system of claim 23 , wherein the processor is configured to detect a plurality of events.

29. The system of claim 23 , wherein the display includes a concurrent display of the indication of the one or more virtual private network services that are affected by the event, the performance information, and the topology information.

30. The system of claim 23 , wherein the processor monitors protocol update information by posing as a router and receiving routing information communicated from the nodes of the network.

31. A non-transitory computer-readable medium containing instructions to configure a data processor to perform a method for storing information associated with a network, including:

receiving and storing first network information at a first time;

monitoring protocol update information communicated between nodes of the network;

detecting a network event at a second time based on the protocol update information;

receiving second network information based on the event;

determining one or more virtual private network services that are affected by the event based on the first network information and the second network information; and

displaying an indication of the one or more virtual private network services that are affected by the event, and at least one of: performance information and topology information based on at least one of the first network information and the second information.

32. The system of claim 31 , wherein the processor is configured to receive and store further network information based on the plurality of events.

33. The computer-readable medium of claim 31 , wherein the first and second network information includes at least one of performance, event, topology, service, and object.

34. The computer-readable medium of claim 31 , wherein receiving the first network information includes receiving the first network information periodically.

35. The computer-readable medium of claim 31 , wherein the method includes indicating that a failure is the event.

36. The computer-readable medium of claim 31 , wherein the method includes indicating that crossing a performance threshold is the event.

37. The computer-readable medium of claim 31 , wherein the method includes detecting a plurality of events.

38. The computer-readable medium of claim 31 , wherein the method includes storing further network information based on the plurality of events.

39. The computer-readable medium of claim 31 , wherein the displaying includes concurrently displaying the indication of the one or more virtual private network services that are affected by the event, the performance information, and the topology information.

40. The computer-readable medium of claim 31 , wherein monitoring the protocol update information includes configuring a processor to receive routing information by posing as a router.

Assignments (23)
RELEASE OF SECURITY INTEREST Recorded Aug 11, 2023
From: ALTER DOMUS (US) LLC, AS COLLATERAL AGENT
To: RIVERBED TECHNOLOGY, INC.; ATERNITY LLC; RIVERBED HOLDINGS, INC.
Reel/Frame 064673/0739 →
CHANGE OF NAME Recorded Feb 18, 2022
From: RIVERBED TECHNOLOGY, INC.
To: RIVERBED TECHNOLOGY LLC
Reel/Frame 059232/0551 →
TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENTS Recorded Dec 27, 2021
From: MORGAN STANLEY SENIOR FUNDING, INC., AS COLLATERAL AGENT
To: RIVERBED TECHNOLOGY, INC.; ATERNITY LLC
Reel/Frame 058593/0046 →
TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENTS Recorded Dec 27, 2021
From: ALTER DOMUS (US) LLC, AS COLLATERAL AGENT
To: RIVERBED TECHNOLOGY, INC.; ATERNITY LLC
Reel/Frame 058593/0108 →
TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENTS Recorded Dec 27, 2021
From: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS U.S. COLLATERAL AGENT
To: RIVERBED TECHNOLOGY, INC.; ATERNITY LLC
Reel/Frame 058593/0169 →
SECURITY INTEREST Recorded Dec 10, 2021
From: RIVERBED TECHNOLOGY LLC (FORMERLY RIVERBED TECHNOLOGY, INC.); ATERNITY LLC
To: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS U.S. COLLATERAL AGENT
Reel/Frame 058486/0216 →
PATENT SECURITY AGREEMENT Recorded Oct 27, 2021
From: RIVERBED TECHNOLOGY, INC.; ATERNITY LLC
To: WILMINGTON TRUST, NATIONAL ASSOCIATION
Reel/Frame 057943/0386 →
PATENT SECURITY AGREEMENT SUPPLEMENT - SECOND LIEN Recorded Oct 14, 2021
From: RIVERBED HOLDINGS, INC.; RIVERBED TECHNOLOGY, INC.; ATERNITY LLC
To: ALTER DOMUS (US) LLC, AS COLLATERAL AGENT
Reel/Frame 057810/0559 →
PATENT SECURITY AGREEMENT SUPPLEMENT - FIRST LIEN Recorded Oct 14, 2021
From: RIVERBED HOLDINGS, INC.; RIVERBED TECHNOLOGY, INC.; ATERNITY LLC
To: MORGAN STANLEY SENIOR FUNDING, INC., AS COLLATERAL AGENT
Reel/Frame 057810/0502 →
RELEASE OF SECURITY INTEREST IN PATENTS RECORED AT REEL 056397, FRAME 0750 Recorded Oct 13, 2021
From: MACQUARIE CAPITAL FUNDING LLC
To: RIVERBED HOLDINGS, INC.; RIVERBED TECHNOLOGY, INC.; ATERNITY LLC
Reel/Frame 057983/0356 →
SECURITY INTEREST Recorded May 26, 2021
From: RIVERBED HOLDINGS, INC.; RIVERBED TECHNOLOGY, INC.; ATERNITY LLC
To: MACQUARIE CAPITAL FUNDING LLC
Reel/Frame 056397/0750 →
PATENT SECURITY AGREEMENT Recorded Mar 5, 2021
From: RIVERBED TECHNOLOGY, INC.
To: ALTER DOMUS (US) LLC, AS COLLATERAL AGENT
Reel/Frame 055514/0249 →
CORRECTIVE ASSIGNMENT TO CORRECT THE CONVEYING PARTY NAME PREVIOUSLY RECORDED ON REEL 035521 FRAME 0069. ASSIGNOR(S) HEREBY CONFIRMS THE RELEASE OF SECURITY INTEREST IN PATENTS. Recorded Jun 2, 2015
From: JPMORGAN CHASE BANK, N.A.
To: RIVERBED TECHNOLOGY, INC.
Reel/Frame 035807/0680 →
SECURITY INTEREST Recorded May 1, 2015
From: RIVERBED TECHNOLOGY, INC.
To: MORGAN STANLEY SENIOR FUNDING, INC., AS COLLATERAL AGENT
Reel/Frame 035561/0363 →
RELEASE OF SECURITY INTEREST IN PATENTS Recorded Apr 28, 2015
From: BARCLAYS BANK PLC
To: RIVERBED TECHNOLOGY, INC.
Reel/Frame 035521/0069 →
PATENT SECURITY AGREEMENT Recorded Dec 27, 2013
From: RIVERBED TECHNOLOGY, INC.
To: JPMORGAN CHASE BANK, N.A., AS ADMINISTRATIVE AGENT
Reel/Frame 032421/0162 →
RELEASE OF PATENT SECURITY INTEREST Recorded Dec 26, 2013
From: MORGAN STANLEY & CO. LLC, AS COLLATERAL AGENT
To: RIVERBED TECHNOLOGY, INC.
Reel/Frame 032113/0425 →
PATENT SECURITY AGREEMENT Recorded Sep 13, 2013
From: RIVERBED TECHNOLOGY, INC.
To: MORGAN STANLEY & CO. LLC
Reel/Frame 031216/0968 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 21, 2013
From: OPNET TECHNOLOGIES LLC
To: RIVERBED TECHNOLOGY, INC.
Reel/Frame 030459/0372 →
CHANGE OF NAME Recorded May 14, 2013
From: OPNET TECHNOLOGIES, INC.
To: OPNET TECHNOLOGIES LLC
Reel/Frame 030411/0310 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 30, 2013
From: GRAY, ERIC W.; KANNAN, NAVNEETH N.; WEST RIDGE NETWORKS, INC.; SQMWORKS, INC.
To: OPNET TECHNOLOGIES, INC
Reel/Frame 030119/0539 →
SECURITY AGREEMENT Recorded Dec 20, 2012
From: RIVERBED TECHNOLOGY, INC.; OPNET TECHNOLOGIES, INC.
To: MORGAN STANLEY & CO. LLC
Reel/Frame 029646/0060 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 8, 2010
From: SQMWORKS, INC.
To: OPNET TECHNOLOGIES, INC
Reel/Frame 025330/0505 →