IP Library Granted Patent US 7,593,351
Granted Patent B1
US 7,593,351 · App. 11/173,758 · Granted Sep 22, 2009

Method and system for collecting and consolidating network traffic information

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,593,351
App. No.
11/173,758
Granted
Sep 22, 2009
Kind
B1
Abstract

A distributed network monitoring system includes a central monitoring device configured to fetch network traffic information from one or more remote monitoring devices in response to receiving a notification from the remote monitoring devices that the network traffic information is available, the remote monitoring devices being communicatively coupled to the central monitoring device. The network traffic information is associated with a timestamp which indicates a time period at which the network traffic information was collected by the remote monitoring devices. The central monitoring device further synchronizes the network traffic information from the remote monitoring devices by comparing the timestamp of the network traffic information with a system timestamp provided by a system clock or network time protocol (NTP) server. The network traffic information is identified as unavailable if the timestamp cannot be located when compared to the system timestamp. In addition, the central monitoring device starts a timeout wait period for the remote monitoring device with the unavailable network traffic information and further ceases collecting the network traffic information if the timeout wait period expires. The synchronized network traffic information is further consolidated to provide information regarding the overall performance of a network system.

Claims (36)

1. A method for execution at a central monitoring device, comprising:

fetchling network traffic information from one or more remote monitoring devices in a network;

synchronizing the network traffic information collected from the remote monitoring devices;

identifying available and unavailable network traffic information, based on an absence of expected reporting;

storing available network traffic information in a buffer;

starting a timeout period to await receipt of as yet unavailable network traffic information for each corresponding unavailable remote monitoring device;

ceasing collection of network traffic information from each unavailable remote monitoring device after expiration of each corresponding timeout period;

resuming collection of network traffic information from a previously unavailable one of the remote monitoring devices in response to receipt of a notification from the previously unavailable remote monitoring device indicating that some or all of the previously unavailable network traffic information is available; and

consolidating the network traffic information to provide information regarding the overall network performance.

2. The method of claim 1 , including receiving a notification provided by the one or more remote monitoring devices that the network traffic information is available for fetching.

3. The method of claim 1 , wherein the network traffic information is associated with a timestamp indicating a time period at which the network traffic information was collected by the remote monitoring devices.

4. The method of claim 3 , wherein the synchronizing includes comparing the timestamp of the network traffic information with a system time provided by at least one of a system clock or a network time protocol server to produce a system timestamp of the network traffic information.

5. The method of claim 4 , wherein the unavailable network traffic information is identified if the system timestamp of the network traffic information cannot be located when compared to the system time within an expected reporting interval.

6. The method of claim 1 , including fetching the previously unavailable network traffic information and synchronizing the previously unavailable network traffic information with the available network traffic information in the buffer.

7. The method of claim 1 , including marking network traffic information stored in the buffer as incomplete.

8. The method of claim 1 , wherein fetching the network traffic information is based on one or more performance metrics, the performance metrics including one or more of: average delay from the remote monitoring devices to the central monitoring device, loads on the remote monitoring devices or the central monitoring device, and reliability of a path from the remote monitoring devices to the central monitoring device and available bandwidth of the path.

9. The method of claim 1 , including resuming collection of network traffic information from a previously unavailable one of the remote monitoring devices in response to receipt of a notification from the previously unavailable remote monitoring device before the expiration of the corresponding timeout period, indicating that some or all of the previously unavailable network traffic information is available, and terminating the corresponding timeout period.

10. The method of claim 9 , including fetching the previously unavailable network traffic information and synchronizing the previously unavailable network traffic information with the available network traffic information in the buffer.

11. A distributed network monitoring system, comprising a central monitoring device that is configured to:

fetch network traffic information from one or more remote monitoring devices,

synchronize and consolidate the network traffic information to provide information regarding the overall network performance,

identify available and unavailable network traffic information based on an expectation of reporting,

store the available network traffic information in a buffer,

start a timeout period for each remote monitoring device associated with the unavailable network traffic information,

cease collecting network traffic information from each of the remote monitoring devices with unavailable network traffic information upon expiration of an associated timeout period, and

resume collecting network traffic information from any of the remote monitoring devices with previously unavailable network traffic information in response to receipt of notification that some or all of the previously unavailable network traffic information is now available.

12. The distributed network monitoring system of claim 11 , wherein the central monitoring device is configured to fetch the network traffic information from one or more remote monitoring devices in response to receiving a notification from the remote monitoring devices that the network traffic information is available.

13. The distributed network monitoring system of claim 12 , wherein at least one of the remote monitoring devices is configured to provide its associated notification according to a performance metrics, the performance metrics including one or more of: average delay from the remote monitoring devices to the central monitoring device, loads on the remote monitoring devices or the central monitoring device, and reliability of a path from the remote monitoring devices to the central monitoring device and available bandwidth of the path.

14. The distributed network monitoring system of claim 11 , wherein the network traffic information is associated with a timestamp indicating one or more time periods at which the network traffic information was collected by the remote monitoring devices.

15. The distributed network monitoring system of claim 14 , wherein the central monitoring device is configured to synchronize the network traffic information by comparing the timestamps of the network traffic information with a system time provided by at least one or more of a system clock or a network time protocol server to provide a system timestamp of the network traffic information.

16. The distributed network monitoring system of claim 15 , wherein the network traffic information is identified as unavailable if one or more of the system timestamps of the network traffic information cannot be located when compared to the system time associated with an expected reporting interval.

17. The distributed network monitoring system of claim 11 , wherein the central monitoring device is configured to fetch the previously unavailable network traffic information and to synchronize the previously unavailable network traffic information with the network traffic information stored in the buffer.

18. The distributed network monitoring system of claim 11 , wherein the central monitoring device is configured to mark network traffic information stored in the buffer as incomplete.

19. The distributed network monitoring system of claim 11 , wherein the central monitoring device is configured to the fetch the network traffic information based on one or more performance metrics, the performance metrics including one or more of: average delay from the remote monitoring devices to the central monitoring device, loads on the remote monitoring devices or the central monitoring device, and reliability of a path from the remote monitoring devices to the central monitoring device and available bandwidth of the path.

20. The distributed network monitoring system of claim 11 , wherein the central monitoring device is configured to resume collecting network traffic information from any of the remote monitoring devices with previously unavailable network traffic information in response to receipt, before the expiration of the timeout period, of notification that some or all of the previously unavailable network traffic information is now available, and terminating the timeout period.

21. The distributed network monitoring system of claim 20 , wherein the central monitoring device is configured to fetch the previously unavailable network traffic information and to synchronize the previously unavailable network traffic information with the network traffic information stored in the buffer.

Assignments (22)
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: 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 →
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 →
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 - 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 →
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 →
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 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 21, 2013
From: OPNET TECHNOLOGIES LLC
To: RIVERBED TECHNOLOGY, INC.
Reel/Frame 030462/0148 →
CHANGE OF NAME Recorded May 14, 2013
From: OPNET TECHNOLOGIES, INC.
To: OPNET TECHNOLOGIES LLC
Reel/Frame 030411/0273 →
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 Oct 19, 2007
From: NETWORK PHYSICS, INC.
To: OPNET TECHNOLOGIES, INC.
Reel/Frame 019984/0376 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 30, 2005
From: ZIOULAS, GEORGE; DING, WENJIE
To: NETWORK PHYSICS
Reel/Frame 016758/0289 →