Software deployment system and method

• US 20060143599A1
• Filed: 12/28/2004
• Published: 06/29/2006
• Est. Priority Date: 12/28/2004
• Status: Active Grant

• Current Assignee: Taiwan Semiconductor Manufacturing Company Limited
• Original Assignee: Taiwan Semiconductor Manufacturing Company Limited
• Inventors: Huang, Ting-Yuan, Yeh, Fu-Kun
• Granted Patent: US 7,801,947 B2
• Time in Patent Office: Days
• US Class Current: 717/168
• CPC Class Codes: G06F 8/656 while running

Abstract

A software deployment system and method are provided. The system includes a server and at least one client. The server executes a first server application and a second server application simultaneously. The client controls at least one equipment tool, executes a first client application connected to the first server application, and has a second client application. In response to a deployment signal, the client first deletes the first client application and executes the second client application to connect to the second server application if all equipment tools controlled by the client are idle. The client then transmits a completion signal to the server. If software deployment on each client is complete, the server deletes the first server application.

Claims

1. A software deployment system, comprising:

a first server application and a second server application; and

at least one client controlling a first equipment tool, the at least one client having a first client application used to connect to the first server application and a second client application used to connect to the second server application;

wherein the at least one client executes the first client application, and executes the second client application if the first equipment tool is idle.

2. The system of claim 1 further comprising a server on which the first and second server applications are executed simultaneously.

3. The system of claim 2 wherein the client begins execution of the second client application in response to a deployment signal sent from the server.

4. The system of claim 2 wherein the client further transmits a completion signal to the server after the second client application is executed, and the server deletes the first server application in response to the completion signal.

5. The system of claim 1 wherein the client further controls a second equipment tool, and executes the second client application when both the first and second equipment tools are idle.

6. The system of claim 1 wherein the client determines whether the first equipment tool is idle by retrieving equipment information from the first equipment tool.

7. The system of claim 6 wherein the equipment information records whether the first equipment tool is idle or not.

8. The system of claim 6 wherein the equipment information records the length of time the first equipment will be idle.

9. The system of claim 1 wherein the client further deletes the first client application before the second client application has executed.

10. A software deployment method, comprising the steps of:

providing at least one client, which controls a first equipment tool, and executes a first client application connected to a first server application, and has a second client application; and

executing the second client application to connect to a second server application if the first equipment tool is idle.

11. The method of claim 10 wherein the first and second server applications are executed on a server simultaneously.

12. The method of claim 11 further comprising receiving a deployment signal sent from the server, and beginning execution of the second client application in response to the deployment signal from the server.

13. The method of claim 11 further comprising transmission of a completion signal to the server by the client after the second client application is executed, and deleting the first server application in response to the completion signal.

14. The method of claim 10 further comprising execution of the second client application by the client when both the first equipment tool and a second equipment tool are idle if the client further controls the second equipment tool.

15. The method of claim 10 further comprising retrieving equipment information from the first equipment tool to determine whether the first equipment tool is idle.

16. The method of claim 15 wherein the equipment information records whether the first equipment tool is idle or not.

17. The method of claim 15 wherein the equipment information records the length of time for the first equipment tool will be idle.

18. The method of claim 10 further comprising deletion of the first client application by the client before the second client application has executed.

19. A software deployment system, comprising:

a first server application and a second server application; and

at least one client controlling at least one equipment tool, the at least one client having a client application connected to the first server application;

wherein the at least one client executes the client application, upgrades the client application and directs the upgraded client application to connect to a second server application if the equipment tool is idle.

20. The system of claim 19 wherein the client determines whether the equipment tool is idle by analyzing equipment information recording whether the equipment tool is idle or not and the length of time for the equipment tool will be idle.