IP Library Granted Patent US 8,005,006
Granted Patent B2
US 8,005,006 · App. 12/478,775 · Granted Aug 23, 2011

Discovery of multiple-parent dependencies in network performance analysis

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,005,006
App. No.
12/478,775
Granted
Aug 23, 2011
Kind
B2
Abstract

Multiple parent-dependencies are identified for messages that are received on a network that includes nodes that are configured to avoid the conventional strictly-sequential communications techniques and protocols, in order to accelerate network performance. If a network is known, or assumed, to include intermediate/proxy nodes that are configured to provide acceleration, access control, and other services, the system that analyzes traffic on the network is configured to assume that these nodes may/will provide such features, and thereby introduce multiple dependencies among the messages communicated across the network. For each message transmitted from a forwarding node, messages received at the forwarding node are assessed to distinguish messages from the destination node and messages from an other node, and a dependency is defined for each.

Claims (40)

1. A method comprising:

receiving trace data at a network analysis system, the trace data corresponding to messages communicated among nodes of a network,

identifying dependencies between transmissions from an intermediate node of the network and receptions at the intermediate node, and

providing the dependencies to an analysis process of the network analysis system to enable the analysis process to avoid infeasible event sequences,

wherein identifying the dependencies includes identifying a transmission that has a plurality of dependency paths based on each of at least two receptions from different nodes.

2. The method of claim 1 , wherein the transmission is to a destination node, and the at least two receptions include a first reception from the destination node and a second reception that is from other than the destination node.

3. The method of claim 2 , wherein the first reception is a most recent reception from the destination before the transmission to the destination.

4. The method of claim 3 , wherein the second reception is a most recent reception from other than the destination before the transmission to the destination.

5. The method of claim 2 , wherein the second reception is a most recent reception from other than the destination before the transmission to the destination.

6. The method of claim 1 , wherein identifying the at least two dependencies includes identifying a correspondence between the transmission and at least one of the receptions.

7. The method of claim 6 , wherein the correspondence is based at least in part on information in headers of the transmission and the at least one reception.

8. The method of claim 1 , wherein identifying the at least two dependencies includes comparing a time of arrival of at least one of the receptions to a time of the transmission.

9. The method of claim 1 , wherein identifying the at least two dependencies includes assuring that times of arrival of the at least two receptions are within a given time span of a time of the transmission.

10. The method of claim 1 , including adding information to each transmission to facilitate determination of the dependencies.

11. A system comprising:

a traffic collator that is configured to receive trace data corresponding to messages communicated among nodes of a network,

a dependency determinator that is configured to identify dependencies between transmissions from an intermediate node of the network and receptions at the intermediate node, and

a network analysis component that is configured to avoid infeasible event sequences based on the dependencies,

wherein identifying the dependencies includes identifying a transmission that has a plurality of dependency paths based on each of at least two receptions from different nodes.

12. The system of claim 11 , wherein the transmission is to a destination node, and the at least two receptions include a first reception from the destination node and a second reception that is from other than the destination node.

13. The system of claim 12 , wherein the first reception is a most recent reception from the destination before the transmission to the destination.

14. The system of claim 13 , wherein the second reception is a most recent reception from other than the destination before the transmission to the destination.

15. The system of claim 12 , wherein the second reception is a most recent reception from other than the destination before the transmission to the destination.

16. The system of claim 11 , wherein the dependency determinator is configured to identify the at least two dependencies based on a correspondence between the transmission and at least one of the receptions.

17. The system of claim 16 , wherein the correspondence is based at least in part on information in headers of the transmission and the at least one reception.

18. The system of claim 11 , wherein the dependency determinator is configured to identify the at least two dependencies based on a comparison of a time of arrival of at least one of the receptions to a time of the transmission.

19. The system of claim 11 , wherein the dependency determinator is configured to identify the at least two dependencies subject to times of arrival of the at least two receptions being within a given time span of a time of the transmission.

20. A computer program stored on a computer-readable medium that, when executed, is configured to cause a processor to:

receive trace data corresponding to messages communicated among nodes of a network,

identify dependencies between transmissions from an intermediate node of the network and receptions at the intermediate node, and

provide the dependencies to a network analysis system that is configured to avoid infeasible event sequences based on the dependencies,

wherein identifying the dependencies includes identifying a transmission that has a plurality of dependency paths based on each of at least two receptions from different nodes.

21. The computer program of claim 20 , wherein the program causes the processor to identify the dependencies subject to times of arrival of the at least two receptions being within a given time span of a time of the transmission.

22. The computer program of claim 20 , wherein the transmission is to a destination node, and the at least two receptions include a first reception from the destination node and a second reception that is from other than the destination node.

23. The computer program of claim 22 , wherein the first reception is a most recent reception from the destination before the transmission to the destination.

24. The computer program of claim 23 , wherein the second reception is a most recent reception from other than the destination before the transmission to the destination.

25. The computer program of claim 22 , wherein the second reception is a most recent reception from other than the destination before the transmission to the destination.

26. The computer program of claim 20 , wherein the program causes the processor to identify the at least two dependencies based on a correspondence between the transmission and at least one of the receptions.

27. The computer program of claim 26 , wherein the correspondence is based at least in part on information in headers of the transmission and the at least one reception.

28. The computer program of claim 20 , wherein the program causes the processor to identify the at least two dependencies based on a comparison of a time of arrival of at least one of the receptions to a time of the transmission.

Assignments (20)
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: 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 →
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 →
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/0290 →
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 Jul 7, 2009
From: NIEMCZYK, STEVE; DUNN, ANTOINE; ELSNER, RUSSELL MARK; MALLOY, PATRICK J.; ZNAMOVA, DANA
To: OPNET TECHNOLOGIES, INC
Reel/Frame 022924/0140 →