IP Library Granted Patent US 9,054,965
Granted Patent B2
US 9,054,965 · App. 14/062,489 · Granted Jun 9, 2015

Managing captured network traffic data

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 9,054,965
App. No.
14/062,489
Granted
Jun 9, 2015
Kind
B2
Abstract

A system and method for managing captured network traffic data is provided. The invention comprises a plurality of capture agents, each being configured to capture the network traffic associated with one or more applications. Each application is associated with one or more capture agents according to an application profile that is stored and maintained in a capture server. When analysis of an application's network traffic is required, the capture server contacts the corresponding capture agents according to the application profile. The capture server then effects the identification and archiving of the network traffic that corresponds to a user-defined capture condition. A database at the capture server maintains a record that associates the corresponding network traffic with the user-defined capture condition such that the corresponding network traffic can later be retrieved and analyzed using an analysis engine.

Claims (41)

1. A non-transitory computer readable medium that includes a computer program that, when executed by a processor, causes the processor to:

receive an identification of a problem on a network;

identify a set of capture components based on the identified problem;

archive at least a portion of traffic captured by the identified set of capture components during a period before the problem was identified; and

display information based on the at least portion of the traffic captured to facilitate diagnosis of the identified problem.

2. The medium of claim 1 , wherein the program causes the processor to archive at least a second portion of the traffic captured by the set of capture components during a period after the problem was identified, and the information displayed is also based on the second portion of the traffic captured.

3. The medium of claim 1 , wherein the program causes the processor to identify the set of capture components via a process that includes identifying a capture condition associated with the identified problem and accessing a database that identifies the set of capture components based on the identified capture condition.

4. The medium of claim 1 wherein the program causes the processor to archive the at least portion of the traffic captured by the set of capture components via a process that includes sending one or more commands to the set of capture components that cause the capture components to archive the at least portion of the traffic captured.

5. The medium of claim 4 , wherein the program causes the processor to archive the at least portion of the traffic captured by the set of capture components via a process that includes retrieving, from one or more of the set of capture components, at least a portion of the archived portion of the traffic captured by the set of capture components.

6. The medium of claim 1 , wherein the program causes the processor to archive the at least portion of the traffic captured by the set of capture components via a process that includes storing the at least portion of the traffic in a memory that is directly accessible by the processor.

7. The medium of claim 1 wherein the program causes the processor to receive a plurality of identifications of problems on the network, and, for each of the plurality of identified problems:

identify a set of capture components associated with the identified problem, and archive of at least a portion of the traffic captured by the set of capture components during a period before the problem was identified.

8. The medium of claim 7 , wherein the program causes the processor to:

display an indication of each of the plurality of identified problems,

receive a user selection of a selected problem of the plurality of identified problems,

display information based on the at least portion of the traffic captured for the selected problem to facilitate diagnosis of the selected problem.

9. The medium of claim 1 , wherein the identification of the problem on the network includes an identification of an application.

10. The medium of claim 9 , wherein the program causes the processor to enable a user to: define the set of capture agents associated with the application, and directly control one or more of the capture agents to facilitate capture of the traffic by the one or more controlled capture agents.

11. A system comprising:

a capture server that includes a processor and a memory:

an interface that receives an identification of a problem on a network;

a notification utility that identifies a set of capture components associated with based on the identified problem; a repository that archives at least a portion of traffic captured by the identified set of capture components during a period before the problem was identified; and

analysis engine that creates a display of information based on the at least portion of the traffic captured to facilitate diagnosis of the identified problem.

12. The system of claim 11 , including a database that identifies the set of capture components based on a capture condition associated with the identified problem.

13. The system of claim 11 wherein the notification utility is configured to send one or more commands to the set of capture components that cause the capture components to archive the at least portion of the traffic captured.

14. The system of claim 11 , wherein the repository retrieves at least a portion of the archived portion of the traffic captured from the set of capture components.

15. The system of claim 11 wherein the interface:

receives a plurality of identifications of problems on the network, and,

for each of the plurality of identified problems:

the notification utility identifies a set of capture components based on the identified problem, and

the repository archives at least a portion of the traffic captured by the identified set of capture components during a period before the problem was identified; and

the system displays an indication of each of the plurality of identified problems, receives a user selection of a selected problem of the plurality of identified problems, and displays information based on the at least portion of the traffic captured for the selected problem to facilitate diagnosis of the selected problem.

16. The system of claim 11 , wherein the identification of the problem on the network includes an identification of an application, and the system enables a user to define the set of capture agents associated with the application, and directly control one or more of the capture agents to facilitate capture of the traffic by the one or more controlled capture agents.

17. A method comprising:

receiving, at a server, an identification of a problem on a network;

identifying, by the server, a set of capture components based on the identified problem;

archiving, in one or more storage devices, at least a portion of traffic captured by the identified set of capture components during a period before the problem was identified; and

displaying, on a display device, information based on the at least portion of the traffic captured to facilitate diagnosis of the identified problem.

18. The method of claim 17 , wherein identifying the set of capture components includes identifying a capture condition associated with the identified problem and accessing a database that identifies the set of capture components based on the identified capture condition.

19. The method of claim 17 including sending one or more commands to the set of capture components, to cause the capture components to archive the at least portion of the traffic captured.

20. The method of claim 17 , including enabling a user to define the set of capture agents associated with an application that is included in the identification of the problem, and directly control one or more of the capture agents to facilitate capture of the traffic by the one or more controlled capture agents.

Assignments (19)
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: 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: 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: 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 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 22, 2019
From: OPNET TECHNOLOGIES LLC
To: RIVERBED TECHNOLOGY, INC.
Reel/Frame 048680/0374 →
CHANGE OF NAME Recorded Mar 14, 2019
From: OPNET TECHNOLOGIES, INC.
To: OPNET TECHNOLOGIES LLC
Reel/Frame 048597/0803 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 6, 2019
From: MALLOY, PATRICK J.; CANNEY, MICHAEL; GEHL, RYAN; COHEN, MARC A.; NUDELMAN, ERIC S.; ELSNER, RUSSELL MARK; SCHNEIDER, MARC I.
To: OPNET TECHNOLOGIES, INC.
Reel/Frame 048519/0654 →
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 →