Remotely monitoring a data processing system via a communications network

• US 8,769,081 B2
• Filed: 01/15/2008
• Issued: 07/01/2014
• Est. Priority Date: 01/31/2001
• Status: Expired due to Fees

• Current Assignee: Accenture Global Services Limited (Accenture PLC)
• Original Assignee: Accenture Global Services Limited (Accenture PLC)
• Inventors: Cornelius, Shawn S., Donoughe, Clifford, Huffman, Arnold Z., Krahn, Richard R., Sweeney, Michael S.
• Primary Examiner(s): Tiv, Backhean
• Application Number:
  US12/008,846
• Publication Number:
  US 20080183728A1
• Time in Patent Office: 2,359 Days
• Field of Search: 370/216, 370/241, 709/223, 709/224
• US Class Current: 709/224
• CPC Class Codes: G06F 11/0715 in a system implementing multitasking multitasking per se G06F9/46
• CPC Class Codes: G06F 11/0751 Error or fault detection not based on redundancy power supply failures G06F1/30; network fault management H04L41/06
• CPC Class Codes: G06F 11/079 Root cause analysis, i.e. error or fault diagnosis in a hardware test environment G06F11/22; in a software test environment G06F11/36
• CPC Class Codes: G06F 11/2294 by remote test
• CPC Class Codes: G06F 11/3017 where the computing system is implementing multitasking multiprogramming arrangements G06F9/46; allocation of resources G06F9/50
• CPC Class Codes: G06F 11/302 where the computing system component is a software system
• CPC Class Codes: G06F 11/3051 Monitoring arrangements for monitoring the configuration of the computing system or of the computing system component, e.g. monitoring the presence of processing resources, peripherals, I/O links, software programs verification or detection of system hardware configuration G06F11/2247
• CPC Class Codes: G06F 11/3055 Monitoring arrangements for monitoring the status of the computing system or of the computing system component, e.g. monitoring if the computing system is on, off, available, not available error or fault processing without redundancy G06F11/0703; error detection or correction by redundancy in data representation G06F11/08; error detection or correction by redundancy in operation G06F11/14; error detection or correction by redundancy in hardware G06F11/16
• CPC Class Codes: H04L 41/0681 Configuration of triggering conditions
• CPC Class Codes: H04L 41/082 the condition being updates or upgrades of network functionality
• CPC Class Codes: H04L 41/083 for increasing network speed
• CPC Class Codes: H04L 41/0836 to enhance reliability, e.g. reduce downtime
• CPC Class Codes: H04L 41/22 comprising specially adapted graphical user interfaces [GUI]
• CPC Class Codes: H04L 43/00 Arrangements for monitoring or testing data switching networks
• CPC Class Codes: H04L 43/08 Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
• CPC Class Codes: H04L 43/0817 by checking functioning

Abstract

A remote data processing system facilitates monitoring of the remote data processing system. The remote data processing system receives a data message via a communications network. The remote data processing system cascades at least a first stage software component and a second stage software component to form an installed remote software module for accepting the received data message. The remote data processing system detects the data message or a derivative at a group of logical nodes within the installed remote software module to determine flow of the data message, or a derivative thereof, between the logical nodes. The remote data processing system identifies a deficient software component of the installed remote software module as any of said software stage components that blocks or disrupts the flow of the data message between two adjacent logical nodes.

Claims

1. A remote data processing system including a hardware component, comprising:

a data receiver for receiving a data message;

a remote software module arranged to receive the data message from the data receiver, the remote software module including at least a first stage software component cascaded with a second stage software component; and

a fault detector coupled to the data receiver and further connected before and after the first software stage component and connected before and after the second software stage component to detect a fault in the remote software module by detecting whether the data message flows from the data receiver to and through the first stage software component, the second stage software component, or both.

2. The system according to claim 1 further comprising a remote status reporter for reporting a status message on at least one of the remote software module and hardware of the remote data processing system.

3. The system according to claim 1 further comprising a database for storing detected faults, stage identifiers, and fault descriptions outputted by the fault detector.

4. The system according to claim 1 further comprising a database for storing status data on corresponding components of a remote data processing system.

5. The system according to claim 1 further comprising a database, the fault detector logging one or more error messages into the database.

6. The system of claim 1 further comprising a feedback generator associated with the remote software module, the feedback generator receiving a status code outputted from the remote software module and forwarding the status code to a transmitter for transmission via a communications network.

7. The system according to claim 1 further comprising a feedback generator associated with the remote software module, the feedback generator generating a status code for a transmitter upon detection of a status code from the remote software module.

8. The system according to claim 1 wherein the fault detector has logical connections including a connection with an input of the first software stage component, an output of the first software stage component, and an output of the second software stage component.

9. The system according to claim 8 wherein the fault detector identifies the first software stage component as a faulty software component if the data message is present at an input of the first software stage component, but not the output of the first software stage component.

10. The system according to claim 8 wherein the fault detector identifies the second software stage component as a faulty software component if the data message is present at an input of the second software stage component, but not the output of the second software stage component.

11. The system according to claim 8 wherein the fault detector identifies the first software stage component as a faulty software component if a derivative of the data message is present at an input of the first software stage component, but not the output of the first software stage component.

12. The system according to claim 8 wherein the fault detector identifies the second software stage component as a faulty software component if a derivative of the data message is present at an input of the second software stage component, but not the output of the second software stage component.

13. A method for monitoring a remote data processing system, the method comprising:

receiving with a data receiver a data message from a base data processing system via a communications network that is external to the remote data processing system;

cascading at least a first stage software component and a second stage software component to form an installed remote software module of the remote data processing system for accepting the received data message;

detecting the data message at a group of logical nodes arranged before and after the first stage software component and before and after the second stage software component without interrupting the flow of the data message through at least a portion of the installed remote software module to determine flow of the data message between the logical nodes and, hence, flow through the first stage software component, the second stage software component, or both;

connecting a fault detector to the data receiver and to each of the group of logical nodes and detecting with the fault detector whether the data message flows from the data receiver to and through the first stage software component, the second stage software component, or both; and

identifying a deficient software component of the installed remote software module as any of said software stage components that blocks or disrupts the flow of the data message between two adjacent logical nodes.

14. The method of claim 13 further comprising:

passing a status code, distinct from the data message, from at least an input of the installed remote software module to an output of the installed remote software module to indicate that the installed remote software module is operational.

15. The method of claim 13 further comprising:

passing a status code from at least an input of the communications network to an output of the communications network to indicate that the communications network is operational.

16. The method of claim 13 further comprising:

routing the status code from the base data processing system via the communications network to the remote data processing system; and

routing the status code from the remote data processing system to the base data processing system via the communications network to indicate the continuity of at least one logic data path traversed by the status code.

17. The method according to claim 13 further comprising:

tapping into a logical data path between the first stage software component and the second stage software component to detect whether each of the first and second stage software components are functioning.

18. The method according to claim 13 further comprising:

determining that one of the at least a first stage software component and a second stage software component immediately following the last detected data message is at fault.

19. The method according to claim 13 further comprising:

assigning stage identifiers to distinguish the at least a first stage software component and a second stage software component from one another and to identify a faulty stage.

20. The method according to claim 19 further comprising:

associating a fault description with each of the stage identifiers for transmission to a management system via a communications network.

21. The method according to claim 13 further comprising:

archiving a fault analysis report in a database associated with the remote processing system.

22. A remote data processing system including a hardware component, comprising:

a data receiver for receiving a data message;

a remote software module in communication with the data receiver via a first pathway so as to receive the data message from the data receiver, the remote software module including at least a first stage software component cascaded with a second stage software component, wherein the first stage software component is in communication with the second stage software component via a second pathway; and

a fault detector in communication with the first pathway via a third pathway that does not extend coincidentally with and along a length of the first pathway and in communication with the second pathway via a fourth pathway that does not extend coincidentally with and along a length of the second pathway, wherein the fault detector detects a fault in the remote software module by detecting whether the data message flows from the data receiver to and through at least one of the first stage software component and the second stage software component by detecting whether the data message is present in the third pathway and the fourth pathway.

23. The system according to claim 22 further comprising a fifth pathway in communication with an output of the second stage software component and the fault detector, wherein the fifth pathway does not overlap the output and the fault detector detects a fault in the remote software module by detecting whether the data message flows entirely through at least one of the first stage software component and the second stage software component by detecting whether the data message is present in the fifth pathway.

24. The system according to claim 22 further comprising a remote status reporter for reporting a status message on at least one of the remote software module and hardware of the remote data processing system.

25. The system according to claim 22 further comprising a database for storing detected faults, stage identifiers, and fault descriptions outputted by the fault detector.

26. The system according to claim 22 further comprising a database for storing status data on corresponding components of a remote data processing system.

27. The system according to claim 22 further comprising a database, the fault detector logging one or more error messages into the database.

28. The system of claim 22 further comprising a feedback generator associated with the remote software module, the feedback generator receiving a status code outputted from the remote software module and forwarding the status code to a transmitter for transmission via a communications network.

29. The system according to claim 22 further comprising a feedback generator associated with the remote software module, the feedback generator generating a status code for a transmitter upon detection of a status code from the remote software module.

30. The system according to claim 22 wherein the fault detector has logical connections including a connection with an input of the first software stage component, an output of the first software stage component, and an output of the second software stage component.

31. The system according to claim 30 wherein the fault detector identifies the first software stage component as a faulty software component if the data message is present at an input of the first software stage component, but not the output of the first software stage component.

32. The system according to claim 30 wherein the fault detector identifies the second software stage component as a faulty software component if the data message is present at an input of the second software stage component, but not the output of the second software stage component.

33. The system according to claim 30 wherein the fault detector identifies the first software stage component as a faulty software component if a derivative of the data message is present at an input of the first software stage component, but not the output of the first software stage component.

34. The system according to claim 30 wherein the fault detector identifies the second software stage component as a faulty software component if a derivative of the data message is present at an input of the second software stage component, but not the output of the second software stage component.

35. A method for monitoring a remote data processing system, the method comprising:

receiving a data message with a data receiver from a base data processing system via a communications network that is external to the remote data processing system;

cascading at least a first stage software component and a second stage software component to form an installed remote software module of the remote data processing system for accepting the received data message and having the data message flow along a pathway from an input of the first stage software component to an output of the second stage software component;

detecting the data message at a first node before the first stage software component and at a second node after the first stage software component to determine flow of the data message between the first and the second nodes and, hence, flow through the first stage software component;

detecting the data message at a third node before the second stage software component and at a fourth node after the second stage software component to determine the flow of the data message between the third and the fourth nodes and, hence, flow through the second stage software component;

connecting a fault detector to the data receiver and to first node, the second node, the third node and the fourth node and detecting with the fault detector whether the data message flows from the data receiver to the first node, the second node, the third node, the fourth node, or a combination thereof and through the first stage software component, the second stage software component, or both; and

identifying a deficient software component of the installed remote software module as any of said software stage components that blocks or disrupts the flow of the data message between the first and the second nodes and between the third and the fourth nodes.

36. The method of claim 35 further comprising:

passing a status code, distinct from the data message, from at least an input of the installed remote software module to an output of the installed remote software module to indicate that the installed remote software module is operational.

37. The method of claim 35 further comprising:

passing a status code from at least an input of the communications network to an output of the communications network to indicate that the communications network is operational.

38. The method of claim 35 further comprising:

routing the status code from the base data processing system via the communications network to the remote data processing system; and

routing the status code from the remote data processing system to the base data processing system via the communications network to indicate the continuity of at least one logic data path traversed by the status code.

39. The method according to claim 35 further comprising:

tapping into a logical data path between the first stage software component and the second stage software component to detect whether each of the first and second stage software components are functioning.

40. The method according to claim 35 further comprising:

determining that one of the at least a first stage software component and a second stage software component immediately following the last detected data message is at fault.

41. The method according to claim 35 further comprising:

assigning stage identifiers to distinguish the at least a first stage software component and a second stage software component from one another and to identify a faulty stage.

42. The method according to claim 41 further comprising:

associating a fault description with each of the stage identifiers for transmission to a management system via a communications network.

43. The method according to claim 35 further comprising:

archiving a fault analysis report in a database associated with the remote processing system.