Method of Operating a Computing Device

• US 20080196008A1
• Filed: 05/18/2005
• Published: 08/14/2008
• Est. Priority Date: 05/20/2004
• Status: Abandoned Application

• Current Assignee: Nokia Corporation
• Original Assignee: Symbian Software Limited (Accenture PLC)
• Inventors: Taylor, Adrian, Luchford, Lee, Branton, Joe
• Application Number:
  US11/569,283
• Publication Number:
  US 20080196008A1
• Time in Patent Office: Days
• US Class Current: 717/120
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management

Abstract

An incremental release to a body of software is carried out by using automated tools on a computing device. The tools are provided with access to the files comprising a whole body of software to be released, the files comprising the last release of the whole body of software, and also to a component database storing details which include but are not limited to the name, component, and time/date stamp of the files comprising the contents of each one of the components included in the release. The tools are made aware of the set of updated components that need releasing but only release the software after checking that each file in the set of files included in the components that aren'"'"'t being updated is identical with the same file in the set of files that haven'"'"'t changed since the last release, that the set of files which are either new or have changed since the last release is identical to the set of files included in the components that are being updated, and also that each of the files comprising the whole body of software to be released is included in exactly one component. The tools also update the component database for each component and each changed file as part of the release of the software.

Claims

1. ) A method of operating a computing device using automated tools for releasing an update to a body of data comprising a plurality of components, the method comprising:

enabling access to files comprising the body of data to be released;

enabling access to files comprising the last release of the body of data;

advising a set of updated components to be released;

enabling access to a component database comprising the name, component, and time/date stamp of the files for each component of the update;

checking that the files included in those components not being updated are identical with the corresponding files in the last release of the body of data;

checking that the files which are new or changed since the last release are identical to the corresponding files of the components being released;

checking that each of the files to be released is included in only a single component; and

updating the component database.

2. ) A method according to claim 1 wherein:

the tools are arranged to have access to the files comprising the whole body of data that has been released; and

the tools are arranged to interrogate the component database and only take those components of the release that have changed since the last release of the data.

3. ) A method according to claim 1 wherein:

the component database for each file in the body of data includes a message digest of only the functionally significant portions of the file;

the step of updating the component database includes calculating and storing a new message digest of only the functionally significant portions of each changed file; and

the step of checking that the each file included in the components that are not being updated is identical with the same file in the previous release is performed by calculating a message digest of only the functionally significant portions of the file and checking that it is identical to a digest for that previous release of that file stored in the component database.

4. ) A method according to claim 3 comprising verifying the integrity of the release of the body of data by calculating message digests of only those functionally significant portions of each of the files and checking that these message digests are identical with the message digests for each file in the component database.

5. ) A method according to claim 1 comprising copying, storing or updating information relating to the body of data on to a shared access medium such as a networked computer disk and the method of obtaining a release or an update to a release is by copying, storing or updating information taken from the shared access medium.

6. ) A method according to claim 1 comprising copying, storing or updating information relating to the body of data on to a distributed medium such as a computer tape or compact disk or digital video disk and the method of obtaining a release or an update to a release is by copying, storing or updating information taken from the distributed medium.

7. ) A method according to claim 1 wherein all or part of the steps are carried out by operating the computing device in a debug mode for simulating what would happen without either releasing or obtaining any data.

8. ) A method according to claim 1 wherein the body of data comprises an operating system for a computing and/or telecommunications device.

9. ) A method according to claim 1 wherein the body of data comprises a body of digital or numerical information.

10. ) A computing device arranged to operate in accordance with a method as defined in claim 1.

11. ) Computer software arranged to cause a computing device to operate in accordance with a method as claimed in claim 1.