System and method for updating an executing application software in a module manner

• US 20020144250A1
• Filed: 08/27/2001
• Published: 10/03/2002
• Est. Priority Date: 03/28/2001
• Status: Abandoned Application

• Current Assignee: SYNQ Technology Incorporated
• Original Assignee: Acermsoft Incorporated
• Inventors: Yen, Hsiang Tsun
• Application Number:
  US09/938,602
• Publication Number:
  US 20020144250A1
• Time in Patent Office: Days
• US Class Current: 717/168
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57

Abstract

A client executes a first application and raises a request. Accordingly, server sends a second configuration file. Client performs following steps: (a) receiving second configuration file; (b) determining whether versions of second and first application are the same, executing first application if yes, going to (c) if no; (c) determining whether second module of second application is updated, going to (d) if yes, going to (e) if no; (d) determining whether any unprocessed second module exists, going to (c) if yes, going to (f) if no; (e) connecting storage device for downloading and storing second module, and going to (d); (f) first module duplicating second module to second location; (g) first module stored in first location starting first module stored in second location; (h) ending first module stored in first location; and (i) first module duplicating second module to first location.

Claims

1. A method for updating an executing application software in a module manner, comprising:

a client computer executing a first application software and raising a request, the first application software including a plurality of first function modules, the client computer storing a first configuration file, the first configuration file further having a first application software version identification code respective to the first application software and a plurality of first function module version identification codes, each of the first function module version identification codes being respective to one of first function modules, the client computer further having a first storage location and a second storage location, the first function modules being divided into a first group and a second group, the first function modules of the first group being stored in the first storage location, and the first function modules of the second group being stored in the second storage location;

a server accepting the request and sending out a second configuration file to the client computer according to the request, the second configuration file having an application software name, a file location, a second application software version identification code and a plurality of second function module version identification codes, the file location being respective to a storage device, the storage device storing a second application software respective to the application software name, the second application software version identification code being respective to the second application software, the second application software including a plurality of second function modules, each of the second function module version identification codes being respective to a second function module, and each of the first function modules being respective to a second function module; and

the client computer executing following steps;

(a) the first application software receiving the second configuration file;

(b) the first application software determining whether or not the second application software version identification code is the same as the first application software version identification code;

if yes, keeping executing the first application software;

if no, going to step (c);

(c) the first application software determining whether or not the second function module version identification code is the same as the respective first function module version identification code;

if yes, going to step (d);

if no, going to step (e);

(d) the first application software determining whether or not any unprocessed second function module version identification code exists;

if yes, going to step (c) for determining the next second function module version identification code;

if no, going to step (f);

(e) the first application software following the file location of the second configuration file to connect the respective storage device for downloading and storing the second function module respective to the second function module version identification code;

then, going to step (d);

(f) the first function module stored in the first storage location duplicating the second function module respective to the first function module stored in the second storage location to the second storage location for replacing the respective first function module;

(g) the first function module stored in the first storage location starting the first function module stored in the second storage location;

(h) ending the first function module stored in the first storage location; and

(i) the first function module stored in the second storage location duplicating the second function module respective to the first function module stored in the first storage location to the first storage location for replacing the respective first function module.

2. The method for updating an executing application software in a module manner according to claim 1, wherein said step (h) includes:

said first function module stored in said first storage location ending by itself.

3. The method for updating an executing application software in a module manner according to claim 1, wherein said step (h) includes:

said first function module stored in said second storage location ending said first function module stored in said first storage location.

4. The method for updating an executing application software in a module manner according to claim 1, wherein said storage device is an external server.

5. The method for updating an executing application software in a module manner according to claim 1, wherein said server includes said storage device.

6. The method for updating an executing application software in a module manner according to claim 1, wherein said client computer replaces said first configuration file with said second configuration file while said second application software version identification code is not the same as said first application software version identification code.

7. A system for updating an executing application software in a module manner, comprising:

a server, further including a plurality of second configuration files, each of the second configuration files having an application software name, a file location, a second application software version identification code and a plurality of second function module version identification codes, the file location being respective to a storage device, the storage device storing a second application software respective to the application software name, the second application software version identification code being respective to the second application software, the second application software including a plurality of second function modules, each of the second function module version identification codes being respective to one of the second function modules; and

a client computer, further including;

a first configuration file, stored in a client storage device, further having a first application software version identification code and a plurality of first function module version identification codes;

a first application software, being respective to the first application software version identification code, further including a plurality of first function modules, each of the first function modules being respective to one of the first function module version identification codes, and each of the first function modules being respective to one of the second function modules; and

the client storage device, further having a first storage location and a second storage location, the first function modules being divided into a first group and a second group, the first function modules of the first group being stored in the first storage location, and the first function modules of the second group being stored in the second storage location.

8. The system for updating an executing application software in a module manner according to claim 7, wherein said storage device is an external server.

9. The system for updating an executing application software in a module manner according to claim 7, wherein said server includes said storage device.

10. The system for updating an executing application software in a module manner according to claim 7, wherein said client computer replaces said first configuration file with said second configuration file while said second application software version identification code is not the same as said first application software version identification code.