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

• US 8,966,468 B2
• Filed: 07/22/2013
• Issued: 02/24/2015
• 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/947,490
• Publication Number:
  US 20130305235A1
• Time in Patent Office: 582 Days
• Field of Search: 717169-176, 709/203
• 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 computer server configured to transfer system update files to a remotely located 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 computer server comprising:

a network connection to the receiving jukebox device; and

processing resources, including at least one processor, configured to send a new file to said receiving jukebox device over the network connection;

wherein

the new file, when received by the receiving jukebox device, includes data programmed to cause 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.

2. The server 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 server 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 server of claim 3, wherein the processing resources of the server are further configured to at least:

receive a copy of said generated file;

read said copy; and

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

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

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

7. The server 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 server 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 server 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. The server of claim 1, wherein the jukebox device is configured to receive and cause at least some updates to operating files and/or parts of a program executable thereon without having to reinitialize the jukebox device.

11. A digital jukebox device provided with an operating system in which different tasks are broken down into a plurality of interconnected modules and further comprising libraries, the jukebox device being configured to receive system update files in connection with at least one processor and a memory that cooperate with one another to at least:

receive a new file from a remote loading source;

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 jukebox device using said new file in dependence on said verifying.

12. The device of claim 11, 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

wherein said verifying is repeated until a highest level of dependency associated with said new file is reached.

13. The device of claim 11, wherein the at least one processor and the memory are further configured to at least 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.

14. The device of claim 13, wherein the at least one processor and the memory are further configured to at least:

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

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

15. The device of claim 11, wherein the modules are interconnected by dynamic links.

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

17. The device of claim 11, wherein the at least one processor and the memory are further configured to at least maintain a backup of a previous version of said new file.

18. The device of claim 17, wherein the at least one processor and the memory are further configured to at least change an execution level of the files of the jukebox device once an update has been accomplished.

19. The device of claim 11, wherein the at least one processor and the memory are further configured to at least change an execution level of the files of the jukebox device once an update has been accomplished.

20. The device of claim 11, wherein the at least one processor and the memory are further configured to at least cause some updates to operating files and/or parts of a program executable on the jukebox device without having to reinitialize the jukebox device.