Method for distributing update modules for computer software over a network

• US 8,539,050 B2
• Filed: 04/28/2008
• Issued: 09/17/2013
• Est. Priority Date: 04/28/2008
• Status: Active Grant

• Current Assignee: Applied OLAP Incorporated
• Original Assignee: Applied OLAP Incorporated
• Inventors: Tow, Timothy N., Tate, Amelia C.
• Primary Examiner(s): Donabed, Ninos
• Application Number:
  US12/110,980
• Publication Number:
  US 20090271777A1
• Time in Patent Office: 1,968 Days
• Field of Search: 709221-225
• US Class Current: 709/221
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57

Abstract

A method for distributing update modules for computer software has been developed. The method includes requesting and receiving a list of updated software modules stored on a network server. The user then determines if each updated module is presently installed on the user'"'"'s system. If the updated module is not installed, the user requests a runtime artifact from the server for the module which is then installed on the user'"'"'s system.

Claims

1. A method for distributing updated executable add-in modules for computer software, comprising:

sending a first query request from a network client for a list of updated executable add-in modules stored on a server;

receiving the first query request at the server and sending a response to the network client comprising the list of updated executable add-in modules stored on the server;

testing to determine if each updated executable add-in module on the list is installed for a pre-existing software application on the network client, where the testing comprises using a checksum value stored on the server;

sending a second query request to the server from the network client for a module package comprising,

an xml representation of a dynamically loaded library module, and

an xml representation of a related metadata describing an executable content of a dynamically loaded library module, for an updated executable add-in module that is not installed on the network client;

receiving the second query request at the server and sending a response to the network client comprising the module package comprising,

the xml representation of the dynamically loaded library module, and

the xml representation of the related metadata describing the executable content of the dynamically loaded library module, for the updated executable add-in module that is not installed on the network client;

decoding and installing the module package, comprising a runtime dynamically loaded library module in machine code format and the xml representation of the related metadata describing the executable content of the dynamically loaded library module, in corresponding runtime directories on the network client;

where the module package comprises a tenant field that uniquely defines a set of metadata for the module package and the updated executable add-in module;

where the module package comprises a category field that identifies the category of metadata for the module package and the updated executable add-in module;

where the module package comprises an identification field that is a unique name for an object in a category of metadata for the module package and the update executable add-in module; and

where the updated executable add-in module is a compressed, base 64-encoded representation of the dynamically loaded library module in machine code format along with the xml representation of the related metadata describing the executable content of the dynamically loaded library module.

2. The method of claim 1, where the first query request, second query request, and responses are transported via HTTP/S in XML format.

3. The method of claim 1, where the installation of the updated executable add-in module on the network is determined by checking the existence of a metadata directory.

4. The method of claim 3, where the installation of the updated executable add-in module on the network is further determined by checking to see if the checksum value of the module package match a module manifest file.

5. The method of claim 1, wherein the module package comprises a version that is a sequential version number for the module package and for the updated executable add-in module.