System for remote loading of objects or files in order to update software

• US 8,522,230 B2
• Filed: 09/01/2011
• Issued: 08/27/2013
• Est. Priority Date: 07/21/1998
• Status: Expired due to Fees

• Current Assignee: TouchTunes Music Corporation (The Octave Music Group, Inc.)
• Original Assignee: TouchTunes Music Corporation (The Octave Music Group, Inc.)
• Inventors: Nathan, Guy, Dion, Dominique
• Primary Examiner(s): Khatri, Anil
• Application Number:
  US13/223,472
• Publication Number:
  US 20110321026A1
• Time in Patent Office: 726 Days
• Field of Search: 717168-177, 709203-204
• US Class Current: 717/169
• 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
• CPC Class Codes: G06F 9/4401 Bootstrapping security arrangements therefor G06F21/57
• CPC Class Codes: G06F 9/445 Program loading or initiating bootstrapping G06F9/4401; security arrangements for program loading or initiating G06F21/57

Abstract

A system for remote loading of objects or files in order to update software includes operating system architecture that calls for different tasks to be broken down into software modules that are connected to one another by dynamic links or are composed of executable subroutines that have main dependence links to other parts of the operating system. Each of the modules is composed of object files or libraries that are represented by dynamic link libraries among themselves according to a number of dependence levels that are described in their respective attributes.

Claims

1. A method of transferring system update files to a receiving jukebox device provided with an operating system wherein different tasks are broken down into a plurality of interconnected modules and further comprising libraries, the method comprising:

sending a new file to said receiving jukebox device from a remote loading source; and

causing the receiving jukebox device to at least;

check at least minimum version information required for execution of said new file;

verify that existing files required for the execution of said new file correspond to said minimum version information requirements; and

update the receiving jukebox device using said new file in dependence on said verifying;

wherein the jukebox device is configured to receive and cause updates to operating files and/or parts of a program executable thereon without having to reinitialize the jukebox device.

2. The method of claim 1, wherein said verifying includes verifying, starting at the lowest level of dependency associated with said new file, that any existing files required for the execution of said new file correspond to said minimum version information requirements, and

wherein the receiving jukebox device is further caused to repeat said verifying until a highest level of dependency associated with said new file is reached.

3. The method of claim 1, wherein the receiving jukebox device is further caused to generate a file when a missing dependency is detected, said missing dependency being determined by the receiving jukebox device failing to verify that an existing file corresponds to said minimum version information requirements.

4. The method of claim 3, further comprising:

receiving a copy of said generated file to said remote loading source;

reading said copy at said remote loading source; and

sending one or more new files, corresponding to said files from which said missing dependency was determined.

5. The method of claim 1, wherein the modules are interconnected by dynamic links.

6. The method of claim 5, wherein the libraries are dynamic link libraries organized among themselves according to a plurality of dependency levels.

7. The method of claim 1, wherein the receiving jukebox device is further caused to maintain a backup of a previous version of said new file.

8. The method of claim 7, wherein the receiving jukebox device is further caused to change an execution level of the files of the jukebox device once an update has been accomplished.

9. The method of claim 1, wherein the receiving jukebox device is further caused to change an execution level of the files of the jukebox device once an update has been accomplished.

10. A method of receiving system update files at a receiving jukebox device provided with an operating system wherein different tasks are broken down into a plurality of interconnected modules and further comprising libraries, the method comprising:

receiving a new file at said receiving jukebox device from a remote loading source;

checking at least minimum version information required for execution of said new file;

verifying that existing files required for the execution of said new file correspond to said minimum version information requirements;

updating the receiving jukebox device using said new file in dependence on said verifying; and

causing updates to operating files and/or parts of a program executable on the receiving jukebox without having to reinitialize the jukebox device.

11. The method of claim 10, wherein said verifying comprises verifying, starting at the lowest level of dependency associated with said new file, that any existing files required for the execution of said new file correspond to said minimum version information requirements, and

further comprising repeating said verifying until a highest level of dependency associated with said new file is reached.

12. The method of claim 10, further comprising generating a file when a missing dependency is detected, said missing dependency being determined by the receiving jukebox device failing to verify that an existing file corresponds to said minimum version information requirements.

13. The method of claim 12, further comprising:

transmitting a copy of said generated file to said remote loading source; and

receiving one or more new files, corresponding to said files from which said missing dependency was determined, from the remote load source.

14. The method of claim 10, wherein the modules are interconnected by dynamic links.

15. The method of claim 14, wherein the libraries are dynamic link libraries organized among themselves according to a plurality of dependency levels.

16. The method of claim 10, further comprising maintaining a backup of a previous version of said new file.

17. The method of claim 16, further comprising changing an execution level of the files of the jukebox device once an update has been accomplished.

18. The method of claim 10, further comprising changing an execution level of the files of the jukebox device once an update has been accomplished.