System for maintaining data

• US 20060156129A1
• Filed: 11/15/2005
• Published: 07/13/2006
• Est. Priority Date: 12/15/2004
• Status: Abandoned Application

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Noble, Gary P., Midgley, Nicholas J.
• Application Number:
  US11/280,111
• Publication Number:
  US 20060156129A1
• Time in Patent Office: Days
• US Class Current: 714/732
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57

Abstract

The invention provides a method for maintaining data stored in a processing device the method comprising the steps of: generating a signature indicative of the data stored in the processing device; communicating the signature to a maintenance node; and receiving updated data from the maintenance node, the updated data being generated by the maintenance node in dependence of the maintenance node comparing the communicated signature with lookup data to determine an update to the data stored in the processing device.

Claims

1. A method for maintaining data stored in a data processing device, the method comprising the steps of:

(a) generating a signature indicative of the data stored in the data processing device;

(b) communicating the signature to a maintenance node; and

(c) receiving updated data from the maintenance node depending upon the maintenance node determining if the signature is expected from the data processing device.

2. A method as claimed in claim 1, wherein the signature is generated by a hash function.

3. A method as claimed in claim 2, wherein the hash function is an MD5 hashing algorithm.

4. A method as claimed in claim 1, wherein the data is indicative of a configuration of the data processing device.

5. A method as claimed in claim 4, wherein the configuration of the data processing device is determined by identifying the hardware and software components installed on the data processing device.

6. A method as claimed in claim 5, wherein a hash value for each identified hardware and software component is generated and a further hash value is generated from each of the generated hash values for communicating to the maintenance node.

7. A method as claimed in claim 1, wherein the received signature is processing by a publish/subscribe mechanism.

8. A method for identifying a data update for communicating to a processing device, the method comprising the steps of:

(a) receiving a signature from the processing node, the received signature being indicative of data stored on the processing device;

(b) comparing the received signature with lookup data to determine an update to the data stored on the processing device.

9. A method as claimed in claim 8, wherein the update is communicated to the processing device.

10. A system for maintaining data stored in a processing device, the system comprising:

(a) a generator component for generating a signature indicative of the data stored in the processing device;

(b) the generator component communicating the signature to a maintenance processing node; and

(c) a receiver for receiving updated data from the maintenance node, the updated data being generated by the maintenance node in dependence of the maintenance node comparing the communicated signature with lookup data to determine an update to the data stored on the processing device.

11. A system as claimed in claim 10, wherein the signature is generated by a hash function.

12. A system as claimed in claim 11, wherein the hash function is an MD5 hashing algorithm.

13. A system as claimed in claim 10, wherein the data is indicative of a configuration of the data processing device.

14. A system as claimed in claim 13 further comprises an identifier component for identifying the configuration of the data processing device by determining the hardware components and the software components installed on the data processing device.

15. A system as claimed in claim 14, wherein the generator component generates a hash value for each identified hardware component and software component and generates a further hash value from the combination of each of the generated hash values for communicating to the maintenance node.

16. A system as claimed in claim 10, wherein a receiver component processed the received signature by a publish/subscribe mechanism.

17. A system for identifying a data update for communication to a processing device, the system comprising:

(a) a receiver component for receiving a signature from the processing node, the received signature being indicative of data stored on the processing device; and

(b) a comparator component for comparing the received signature with lookup data to determine an update to the data stored in the processing device.

18. A system as claimed in claim 17, further comprises a communicator component for communicating the update to the processing device.

19. A computer program product comprising a computer usable medium having computer usable program code, wherein when the computer usable program code is loadable into the internal memory of a processing device, causes the processing device to:

(a) generate a signature indicative of the data stored in the data processing device;

(b) communicate the signature to a maintenance node across a network;

(c) receive updated data from the maintenance node if the maintenance node determines the signature is expected from the data processing device.

20. The computer program product of 19, wherein the program code causes the data processing device to generate the signature using a hash function.

21. The computer program product of claim 20, wherein the program code causes the data processing device to generate the signature indicative of a configuration of the data processing by identifying the hardware and software components installed on the data processing device.

22. The computer program product of claim 21, wherein a hash value for each identified hardware and software component is generated, and a further hash value is generated from each of the generated hash values.

23. The computer program product of claim 22, wherein the received signature is processing by a publish/subscribe mechanism.

24. A service contract for managing service transactions between at least one microprocessor device and a maintenance mode coupled to a communication network, the at least one microprocessor device having processing hardware and/or software, the service contract comprising:

(a) a plurality of hash values generated by the service contract, one of the plurality of hash values pertaining to each of the hardware and/or software configuration of the at least one microprocessor device;

(b) a configuration hash value generated by the service contract, the configuration hash value generated from the combination of the plurality of hash values pertaining to each of the at least one microprocessor devices;

(c) a signature file unique to each of the at least one microprocessor devices, the signature file generated by the service contract indicative of the configuration hash value of the at least one microprocessor device.

25. The service contract of claim 24, further comprising:

(a) a maintenance node coupled to the at least one processing device, the maintenance node receiving a signature for each of the plurality of processing devices;

the maintenance node comprising;

(i) a pre-registered signature component having expected signatures of each of the plurality of processing devices;

(ii) a comparator component having a rules engine that compares the received signature with the expected signature;

(iii) an update configuration component that transmits updated data to one of the plurality of processing devices when the received signature matches the expected signature and when updated data for the processing device are available.

26. The service contract of claim 25, further comprising a target configuration stored in the maintenance node, the target configuration indicative of the updated data to be transmitted to one of the plurality of processing devices.