Diagnosis of data transfer faults using constraints

• US 20030159093A1
• Filed: 02/19/2002
• Published: 08/21/2003
• Est. Priority Date: 02/19/2002
• Status: Active Grant

• Current Assignee: Keysight Technologies, Inc.
• Original Assignee: Agilent Technologies, Inc.
• Inventors: Barford, Lee A., Manley, Douglas R.
• Granted Patent: US 7,024,600 B2
• Time in Patent Office: Days
• US Class Current: 714/712
• CPC Class Codes: G01R 31/2846 using hard- or software simulation or using knowledge-based systems, e.g. expert systems, artificial intelligence or interactive algorithms

Abstract

Method for diagnosing faults in a system under test (SUT) are provided. A representative method includes identifying at least some portions of the data transmission paths of the SUT capable of introducing errors in data transfer; providing constraints defining relationships of at least some of the portions of the data transmission paths; and diagnosing the SUT with respect to the constraints. Systems, computer-readable media and other methods also are provided.

Claims

1. A method for diagnosing faults in a system under test (SUT), the SUT defining data transmission paths through which data are transferred, said method comprising:

identifying at least some portions of the data transmission paths of the SUT capable of introducing errors in data transfer;

providing constraints defining relationships of at least some of the portions of the data transmission paths identified; and

diagnosing the SUT with respect to the constraints.

2. The method of claim 1, wherein identifying comprises providing a dataflow model corresponding to the SUT, the dataflow model including edges, each of which corresponds to a portion of one of the data transmission paths of the SUT capable of introducing errors in data transfer.

3. The method of claim 2, wherein the dataflow model includes vertices, each of the edges being defined between two of the vertices.

4. The method of claim 3, wherein each of the vertices is at least one of a termination of an edge and representative of a location where an operation with respect to data can occur.

5. The method of claim 4, wherein the operation corresponding to a vertex includes at least one of dropping data, splitting data, routing data, replicating data and combining data.

6. The method of claim 4, further comprising:

receiving test results corresponding to the SUT; and

wherein diagnosing comprises analyzing the test results with respect to the dataflow model.

7. The method of claim 6, wherein the SUT includes counters corresponding to at least some of the edges of the dataflow model;

and

further comprising;

receiving information, corresponding to the test results, from at least some of the counters.

8. The method of claim 6, wherein the dataflow model is a directed graph.

9. The method of claim 6, wherein analyzing the test results comprises:

receiving information corresponding to failed data transfers; and

identifying portions of the SUT potentially associated with the failed data transfers.

10. The method of claim 9, wherein analyzing the test results comprises:

exonerating portions of the SUT initially identified as being associated with the failed data transfers if those portions of the SUT are determined not to have initiated at least one of the failed data transfers.

11. The method of claim 1, wherein diagnosing the SUT comprises:

receiving information regarding data transfers with respect to the portions identified, the information being obtained via cyclic redundancy checking.

12. The method of claim 1, wherein identifying comprises providing a dataflow model corresponding to the SUT, the dataflow model including edges and vertices, each of the edges corresponding to a portion of one of the data transmission paths of the SUT capable of introducing errors in data transfer, each of the edges being defined between two of the vertices;

and

wherein the constraints correspond to data flow characteristics of the SUT exhibited with respect to the vertices.

13. The method of claim 12, wherein at least one of the constraints of at least one of the vertices relates that an amount of data flowing into the vertex corresponds to an amount of data flowing from the vertex.

14. The method of claim 13, wherein the amount of data flowing into the vertex corresponds to an amount of at least one of:

good data, bad data and a particular type of data flowing into the vertex.

15. A method for diagnosing faults in a system under test (SUT), said method comprising:

providing a dataflow model representative of the SUT, the dataflow model including information corresponding to a relationship of error detection capabilities of the SUT; and

diagnosing the SUT with respect to the dataflow model.

16. The method of claim 15, wherein diagnosing the SUT comprises:

providing constraints defining relationships of at least some of the portions of the dataflow model.

17. The method of claim 15, wherein diagnosing the SUT comprises:

generating information indicative of a manner of failure of the SUT.

18. The method of claim 17, wherein the flow of data is a flow of data packets;

and

wherein diagnosing the SUT further comprises;

analyzing information acquired via cyclic redundancy checks performed at various locations associated with the flow of data.

19. The method of claim 15, wherein the dataflow model lacks procedural content and process calls.

21. The system of claim 19, wherein said dataflow model is a directed graph including edges and vertices, each of said edges corresponding to at least a portion of a data transmission path of the SUT through which an error can be introduced, each of said edges being defined by two of said vertices.

22. The system of claim 19, wherein said reasoning engine is adapted to evaluate the test results of the SUT with respect to constraints, the constraints defining relationships of at least some of the portions of the dataflow model.

23. The system of claim 19, wherein said reasoning engine is adapted to receive information corresponding to failed data transfers and identify portions of the SUT potentially associated with the failed data transfers.

24. The system of claim 19, further comprising:

an SUT communicatively coupled to at least one of said dataflow model and said reasoning engine.

20. A system for diagnosing faults in a system under test (SUT), said system comprising:

a dataflow model representative of error detection capabilities of the SUT; and

a reasoning engine associated with said dataflow model, said reasoning engine being adapted to evaluate test results corresponding to the SUT in relation to said dataflow model.

25. A system for diagnosing faults in a system under test (SUT), said system comprising:

means for receiving test results corresponding at least some portions of data transmission paths of the SUT; and

means for diagnosing the SUT with respect to constraints defining relationships of at least some of the portions of data transmission paths of the SUT.

26. The system of claim 25, wherein said means for diagnosing includes means for analyzing the SUT with respect to a dataflow model.

27. The system of claim 25, further comprising:

means for testing the SUT to generate test results.

28. A diagnosis system stored on a computer-readable medium, the diagnosis system being adapted to diagnose faults in a system under test (SUT), said diagnosis system comprising:

logic configured to identify at least some portions of the data transmission paths of the SUT capable of introducing errors in data transfer;

logic configured to provide constraints defining relationships of at least some of the portions of the data transmission paths; and

logic configured to diagnose the SUT with respect to the constraints.

29. The diagnosis system of claim 28, wherein said logic configured to diagnose comprises:

logic configured to provide a dataflow model; and

logic configured to analyze the SUT with respect to a dataflow model.

30. The diagnosis system of claim 28, wherein said logic configured to diagnose includes logic configured to generate information indicative of the flow of data associated with a time of error detection.

31. The diagnosis system of claim 28, wherein said logic configured to diagnose includes logic configured to identify portions of the SUT potentially associated with failed data transfers.

32. The diagnosis system of claim 31, wherein said logic configured to diagnose includes logic configured to exonerate components initially identified as being associated with the failed data transfers.