Method and apparatus for updating software at remote locations

• US 5,155,847 A
• Filed: 08/03/1988
• Issued: 10/13/1992
• Est. Priority Date: 08/03/1988
• Status: Expired due to Term

• Current Assignee: Dot Assets No 9 LLC (Intellectual Ventures LLC)
• Original Assignee: Minicom Data Corporation
• Inventors: Porrett, William A., Kirouac, Donald L., Czerwinski, Marek J.
• Primary Examiner(s): Hecker, Stuart N.
• Assistant Examiner(s): WHITFIELD, MICHAEL
• Application Number:
  US07/227,799
• Time in Patent Office: 1,532 Days
• Field of Search: 364/300, 364/200 MS File, 364/900 MS File, 395/600, 395/650, 395/200
• US Class Current: 709/221
• CPC Class Codes: G06F 11/0748 in a remote unit communicating with a single-box computer node experiencing an error/fault remote testing G06F11/2294
• CPC Class Codes: G06F 11/0793 Remedial or corrective actions recovery from an exception in an instruction pipeline G06F9/3861; by retry G06F11/1402; for recovering from a failure of a protocol instance or entity H04L69/40
• CPC Class Codes: G06F 11/2289 by configuration test
• CPC Class Codes: G06F 11/2294 by remote test
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57

Abstract

A method and system are provided for updating the software used in remote computer systems from a central computer system. The method includes storing in the central computer system, copies of the software executable used in each remote computer system. When the copies of the software in the central computer system are upgraded, for example, to correct the software, to add new facilities, to change user interfaces, to make cosmetic changes, to improve performance, etc., each change made to the software is monitored and stored. The remote computer systems are permitted access to the central computer system via communication links and the software in the remote computer systems and the corresponding software in the central computer system are compared. All of the changes that have been made to the software at the central computer system which have not been made to the corresponding software at the remote computer system accessing the central computer are detected. The detected changes are then transmitted to the remote computer system and applied to the software therein in order to upgrade the software in the remote computer system. The upgraded software in the remote computer system is examined to ensure that the software has been changed correctly. The method allows the software at the remote computer systems to be upgraded even while the software at the remote site is being used. The system and method also allow the software used in the remote computer systems to be upgraded when the remote computer systems use different versions of the software and allow the software to be upgraded in a variety of hardware environments and operating systems.

Claims

1. A method of upgrading, from a central computer system, the executable code used in at least one remote computer system, comprising the steps of:

storing in said central computer system a record of the executable code in use at said at least one remote computer system and executable code corresponding to the executable code used in said at least one remote computer system;

upgrading the corresponding executable code and recording the changes made to said corresponding executable code at said central computer system, wherein said changes are in the form of patches, each patch including at least one change to said corresponding executable code;

assigning first and second checksums to each said patch, said first checksum representing an image of the corresponding executable code before the patch is applied thereto and said second checksum representing an image of the corresponding executable code after the patch has been applied thereto;

establishing a communications link between said at least one remote computer system and said central computer system, said central computer system identifying said at least one remote computer system and examining said record to determine the executable code used therein;

examining said record to determine the changes that have been made to said corresponding executable code that have not been made to the executable code used at said at least one remote computer system;

transmitting the changes made to said corresponding executable code to said at least one remote computer system to upgrade the executable code therein; and

verifying transmission of the changes and examining the upgraded executable code used at said at least one remote computer system to ensure that the executable code used therein has been properly upgraded.

2. A method as defined in claim 1 further comprising the step of assigning a patch number to each of said patches, said patch number indicating the total number of patches made to the corresponding executable code stored at said central computer system.

3. A method as defined in claim 2 including a plurality of remote computer systems wherein each remote computer system is assigned a threshold value, said threshold value capable of being different for each remote computer system, the threshold value being used to allow remote computer systems to receive patches having patch numbers less than or equal to said threshold value.

4. A method as defined in claim 3 further comprising the steps of testing said patches at said central computer system prior to making said patches available for release to said plurality of remote computer systems, said patches being tested in numerical order as determined by said patch number, said threshold values assigned to said plurality of remote computer systems being determined by the numbers assigned to said patches.

5. A method as defined in claim 4 wherein said patches can be tested out of numerical order, said threshold values being equal to a number less than or equal to the highest patch number assigned to a patch that has been tested and wherein all patches having a patch number less than the highest patch number have also been tested.

6. A method as defined in claim 5 further comprising the step of allowing said central computer system to transmit priority patches to said remote computer systems having patch numbers exceeding said threshold value, said central computer system transmitting said priority patches, any patches related to the priority patches and any patches made to the corresponding executable code at said central computer system having patch numbers of a value between the threshold value and the priority patch number.

7. A method as defined in claim 1 further comprising the steps of examining each patch made to the corresponding executable code stored at the central computer system to determine if a patch is related to a previous patch made to said corresponding executable code and coding the related patches to ensure that said at least one remote computer system being upgraded receives all related patches when the executable code therein is being upgraded.

8. A method as defined in claim 7 wherein the patches made to the corresponding executable code are manually coded as being related to previous patches.

9. A method as defined in claim 1 wherein there are at least two remote computer systems, each of said remote computer systems have a mandatory set of executable code, each of said remote computer systems being capable of having a different version of said mandatory set of executable code and wherein at least one of said remote computer systems is supplied with at least one additional set of executable code which co-operates with said mandatory set of executable code being of the same version in said at least one remote computer system, said mandatory and additional sets of executable code constituting said corresponding executable code and being upgraded at said central computer system.

10. A method as defined in claim 9 further comprising the steps of:

determining at said central computer system the mandatory and additional sets of executable code used at said at least one remote computer system and the version thereof once a communication link has been established and said at least one remote computer system has been identified and prior to transmitting said patches; and

transmitting automatically said patches from said central computer system to said remote computer system relating to said mandatory and additional sets of executable code used at said one remote computer system.

11. A method as defined in claim 1 further comprising the steps of:

examining each patch made to the corresponding executable code stored at said central computer system to detect whether said patch is applicable to other versions of the same executable code and

applying the patch to the other versions of the same executable code stored at said central computer when said patch is detected as being applicable thereto.

12. A method as defined in claim 11 wherein said other versions of the same executable code are detected automatically by said central computer system, said method further comprising the step of the said central computer system applying said patches to the other versions of the same executable code stored at said central computer automatically upon an input confirmation.

13. A method as defined in claim 1 further comprising the steps of:

comparing automatically at said central computer system the first checksum assigned to a patch to be applied to said corresponding executable code with the second checksum assigned to the previous patch made to the corresponding executable code to ensure that the checksums are identical; and

recording the patches at said central computer system when said checksum are identical.

14. A method as defined in claim 13 wherein said central computer system stores a first version of executable code and at least one different of the same executable code, said at least one different version being used in said remote computer systems, and wherein a patch made to said first version can be applied to said at least one different version, further comprising the steps of:

comparing automatically at said central computer system the first checksum assigned to said patch with the second checksum of the last patch applied to said at least one different version;

applying said patch to said at least one different version when said first and second checksums correspond;

making a copy of said at least one different version and applying said patch to said copy, when said checksums do not correspond;

determining a first set of differences between said copy and a patched first version;

determining a second set of differences between the unpatched first version and said at least one different version; and

applying the patch to said at least one different version when said first and second sets of differences are equivalent.

15. A method as defined in claim 1 wherein the step of verifying transmission of said patches further comprises the step of transmitting said first and second checksums to said remote computer system, said remote computer system examining the checksums assigned to said patches to determine if the transmission of the patches is correct.

16. A method as defined in claim 15 wherein the step of verifying transmission of said patches further comprises the steps of making a copy at said at least one remote computer system of the executable code used at said at least one remote computer system and applying the transmitted patch thereto;

said remote computer assigning a checksum to the copy of the executable code with the patch applied thereto and comparing said checksum to said transmitted second checksum; and

replacing the executable code with the copy of the executable code having the patch applied thereto when said assigned and said transmitted second checksum are equivalent.

17. A method as defined in claim 1 wherein there are a plurality of said remote computer systems and further comprising the step of allowing two or more of said plurality of remote computer systems to gain access to said central computer system at the same time.

18. A method as defined in claim 17 further comprising the steps of assigning at least one of said plurality of remote computer system with access priority;

providing said central computer system with a predetermined number of reserved communication inputs;

inhibiting remote computer systems without priority access from establishing a communication link via said reserved inputs; and

allowing said at least one of said plurality of remote computer systems assigned access priority to establish a communication link with said central computer system via one of said reserved inputs when the other inputs to said central computer system are occupied.

19. A method as defined in claim 1 further comprising the step of releasing said patches to different remote computer systems at different times.

20. A method as defined in claim 19 wherein the times at which said patches are released to said at least one remote computer system are based on a predetermined logical grouping of said remote computer systems.

25. A system as defined in claim 2 wherein at least one remote computer system is given access priority to said central computer system, said central computer system further including at least one predetermined input reserved to allow said at least one remote computer system assigned access priority to establish a communication link via said at least one predetermined input when the other inputs to said central computer system are occupied.

21. A system for upgrading, from a central computer system, the executable code used in at least one remote computer system comprising:

storage means located in said central computer system for storing a record of the executable code in use at said at least one remote computer system and executable code corresponding to the executable code used in said at least one remote computer system;

input means located at said central computer system for allowing the corresponding executable code stored therein to be upgraded;

upgrade detection means located in said central computer system for detecting and recording automatically each change made to the corresponding executable code stored therein, wherein said changes are in the form of patches with each patch including at least one change to said corresponding executable code;

checksum assignor means in said central computer system and said at least one remote computer system for assigning each patch a pair of checksums, said checksums representing an image of the corresponding executable code with and without the patch applied thereto;

communication means for establishing a communication link between said at least one remote computer system and the central computer system;

first identifying means located in said central computer system to identify said at least one remote computer system and to examine said record to determine the executable code used therein;

second identifying means for examining said record to identify the changes that have been made to the corresponding executable code stored in said central computer system which have not been made tot he executable code in said at least one remote computer system;

transmission means for transmitting the identified changes from said central computer system to said at least one remote computer system; and

verification means at one of said central computer system and said at least one remote computer system for comparing the checksums assigned to said patch by said central computer system with those assigned by said at least one remote computer system thereby to ensure that each patch is received at said at least one computer system correctly.

22. A system as defined in claim 21 wherein the input means includes at least one computer terminal.

23. A system as defined in claim 21 wherein said communication link is in the form of a packet switching network, said transmission means transmitting said patches from the central computer system to said at least one remote computer system over said packet switching network.

24. A system as defined in claim 21 wherein there are a plurality of remote computer systems and said central computer system includes multi-taking capabilities and a plurality of inputs to allow at least two of said plurality of remote computer systems to gain access to the central computer system at the same time.

26. A system as defined in claim 21 wherein said central computer system assigns a patch number to each patch made to said corresponding executable code said patch number increasing consecutively with each patch made.

27. A system as defined in claim 26 further comprising a related patch detector in said central computer system for detecting and coding patches which are related to previous patches made to the corresponding executable code to ensure that said at least one remote computer system receives all related patches when the executable code used therein is being upgraded.

28. A system as defined in claim 27 further comprising a plurality of remote computer systems and threshold assigning means at said central computer system for assigning a threshold value to each of said plurality of remote computer systems, said threshold value capable of being different for each of said plurality of remote computer systems, said threshold value being used to allow each of said plurality of remote computer systems to receive patches having patch numbers and related patch numbers less than or equal to said threshold value.

29. A system as defined in claim 28 wherein said central computer system tests said patches before making them available for release to said remote computer systems, said threshold values being equal to a number less than or equal to the highest number assigned to a patch tested by said central computer system and wherein all patches having a number below said highest number have also been tested.

30. A system as defined in claim 29 further comprising means for allowing patches having a number greater than said threshold value to be transmitted to predetermined ones of said remote computer systems.

31. A system as defined in claim 21 wherein said central computer system releases patches to different remote computer systems at different times.

32. A system as defined in claim 31 wherein the times at which said patches are released to said at least one remote computer system are based on a predetermined logical grouping of said remote computer systems.