System and method for incremental software installation

• US 9,552,201 B2
• Filed: 08/31/2011
• Issued: 01/24/2017
• Est. Priority Date: 08/31/2011
• Status: Active Grant

• Current Assignee: Arlington Technologies, LLC (Dominion Harbor Enterprises, LLC)
• Original Assignee: Avaya Incorporated
• Inventors: Hyndman, Arn Close, Walls, Gordon Frederick
• Primary Examiner(s): Bodden, Evral E
• Application Number:
  US13/222,392
• Publication Number:
  US 20130055231A1
• Time in Patent Office: 1,973 Days
• Field of Search: None
• US Class Current: 1/1
• CPC Class Codes: G06F 8/658 Incremental updates; Differential updates

Abstract

Disclosed herein are systems, methods, and non-transitory computer-readable storage media for performing incremental software installations. The system identifies a set of files associated with one or more software programs. Each file can be a component of a software program, or any file accessed by the software program or system when the software program is executed. The system receives a list of files associated with a software version that is not installed on the system. The system determines the differences between the set of files and the list of files, and receives a missing file from the list of files based on the differences. Finally, the system builds the software version on the system using the set of files and the missing file. In building the software version, the system does not assume a linear progression of updates and is able to reuse existing files to create nonlinear variations of software.

Claims

1. A method comprising:

identifying, by a target device of a software installation, a first file and a second file that are stored on the target device, wherein the first file is required to execute a first software program previously installed on the target device and the second file is required to execute a second software program previously installed on the target device;

receiving, by the target device, a list of files that are required to execute a third software program on the target device, the list of files comprising the first file, the second file, and a third file;

generating, by the target device during runtime, a unique identifier for each of the first file, second file, and third file, wherein the unique identifier is generated using a hash function applied to contents of the first file, second file, and third file to generate a first unique identifier, a second unique identifier, and a third unique identifier, respectively;

determining, by the target device, whether files included in the list of files are present on the device to yield a determination, wherein the determination includes an analysis of the first unique identifier, second unique identifier, and third unique identifier;

based on the determination, receiving the third file at the target device; and

building, by the target device, the third software program on the target device using the first file, the second file, and the third file.

2. The method of claim 1, wherein the first file is not required to execute the second software program and the second file is not required to execute the first software program.

3. The method of claim 1, wherein the list of files further comprises a fourth file, wherein the fourth file is required to execute the first software program and the second software program.

4. The method of claim 1, wherein determining whether the files included in the list of files are present on the target device comprises comparing the first unique identifier, the second unique identifier, and third unique identifier with identifiers contained in the list of files.

5. The method of claim 1, wherein the hash function comprises a cryptographic hash function.

6. The method of claim 1, further comprising:

digitally signing the first unique identifier, the second unique identifier, and the third unique identifier with a key.

7. The method of claim 1, further comprising receiving, from an incremental installer object, a determination that the third software program is required at the target device.

8. The method of claim 1, wherein the third file is received from a second device having transmitted the third file in a manner resistant to tampering.

9. The method of claim 1, further comprising:

using the hash function to further ensure file integrity of the first file, the second file, and the third file.

10. A system comprising:

a processor; and

a non-transitory computer-readable storage medium storing instructions configured to when executed by the processor, cause the processor to perform an incremental software installation on the system;

accessing a first file and a second file that are stored at the system, wherein the first file is required to execute a first software program previously installed on the system and the second file is required to execute a second software program previously installed on the system;

receiving a list of files that are required to execute a third software program, the list comprising the first file, the second file, and a third file;

generating, during runtime, a unique identifier for each of the first file, second file, and third file, wherein the unique identifier is generated using a hash function applied to contents of the first file, second file, and third file to generate a first unique identifier, a second unique identifier, and a third unique identifier, respectively;

determining whether files included in the list of files are present on the device to yield a determination, wherein the determination includes an analysis of the first unique identifier, second unique identifier, and third unique identifier;

based on the difference, receiving the third file at the system; and

building the third software program on the system using the first file, the second file, and the third file.

11. The system of claim 10, wherein the hash function comprises a cryptographic hash function.

12. The system of claim 11, wherein the first unique identifier, the second unique identifier, and the third unique identifier are further digitally signed with a key.

13. The system of claim 10, wherein the contents upon which the hash function is applied includes portions of the first file, second file, and third file that are relevant to use for execution of the first file, second file, and third file and wherein the contents upon which the hash function is applied excludes portions of the first file, the second file, and the third file that change from build to build.

14. The system of claim 10, further comprising deleting one file from the system based on a least recently used basis.

15. A non-transitory computer-readable storage device storing instructions which, when executed by a processor, cause the processor to perform an incremental software installation on a device by:

identifying, by the device, a first file and a second file that are stored on the device, wherein the first file is required to execute a first software program previously installed on the device and the second file is required to execute a second software program previously installed on the device;

receiving, by the device, a list of files that are required to execute a third software program, the list of files comprising the first file, the second file, and a third file;

generating, by the device during runtime, a unique identifier for each of the first file, second file, and third file, wherein the unique identifier is generated using a hash function applied to contents of the first file, second file, and third file to generate a first unique identifier, a second unique identifier, and a third unique identifier, respectively;

determining, by the device, whether files included in the list of files are present on the device to yield a determination, wherein the determination includes an analysis of the first unique identifier, second unique identifier, and third unique identifier;

based on the determination, receiving the third file at the device; and

building, by the device, the third software program at the device using the first file, the second file, and the third file.

16. The non-transitory computer-readable storage device of claim 15, wherein the third file is received from a second device that transmitted the third file using data compression.

17. The non-transitory computer-readable storage device of claim 15, wherein the third file is received using multithreading communications with overlapped decompression.

18. The non-transitory computer-readable storage device of claim 15, wherein determining whether the files included in the list of files are present on the device comprises comparing the first unique identifier, the second unique identifier, and third unique identifier with identifiers contained in the list of files.

19. The non-transitory computer-readable storage device of claim 15, wherein the first file is not required to execute the second software program and the second file is not required to execute the first software program.

20. The non-transitory computer-readable storage device of claim 15, wherein the list of files further comprises a fourth file, wherein the fourth file is required to execute the first software program and the second software program.