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

• US 8,032,879 B2
• Filed: 04/02/2007
• Issued: 10/04/2011
• Est. Priority Date: 07/21/1998
• Status: Expired due to Term

• 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:
  US11/730,449
• Publication Number:
  US 20070204263A1
• Time in Patent Office: 1,646 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 modules being interconnected by dynamic links and further comprising libraries represented by dynamic link libraries organized among themselves according to a plurality of dependence levels, the method comprising:

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

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

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

maintaining a backup of a previous version of said new file;

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

changing an execution level of the files of the jukebox device once an update has been accomplished.

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 further comprising;

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

3. The method of claim 1, further including generating a file when a missing dependence is detected, said missing dependence being determined by the failure of the verifying to verify that an existing file corresponds to said minimum version information requirements.

4. The method of claim 3, further including:

sending 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 dependence was determined.