Software deployment system and method

• US 7,801,947 B2
• Filed: 12/28/2004
• Issued: 09/21/2010
• Est. Priority Date: 12/28/2004
• Status: Expired due to Fees

• Current Assignee: Taiwan Semiconductor Manufacturing Company Limited
• Original Assignee: Taiwan Semiconductor Manufacturing Company Limited
• Inventors: Huang, Ting-Yuan, Yeh, Fu-Kun
• Primary Examiner(s): DOAN, DUYEN MY
• Application Number:
  US11/023,753
• Publication Number:
  US 20060143599A1
• Time in Patent Office: 2,093 Days
• Field of Search: 709/203, 709/219, 717168-178
• US Class Current: 709/203
• 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 server having a first server application and a second server application, the second server application being a newer version application of the first server application to be upgraded; and

at least one client controlling a first equipment tool, wherein the first equipment tool has a run manager and an equipment information recording whether the first equipment tool is idle or not, and 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 second client application being a newer version application of the first client application to be upgraded, and further the at least one client executes the first client application to connect with the first server application on the server, and receives information from the first server application to control operations of the first equipment tool according to the received information, the at least one client retrieves the equipment information from the run manager of the first equipment tool, determines whether the first equipment tool is idle or not according to the retrieved equipment information, and when the first equipment tool controlled by the client is idle, terminates the execution of the first client application, executes the second client application to connect with the second server application on the server, and receives information from the second server application to control operations of the first equipment tool according to the received information.

2. The system of claim 1 wherein the first and second server applications are executed simultaneously on the server.

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 equipment information records whether the first equipment tool is idle or not.

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

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

9. A method to deploy software, comprising the steps of:

providing at least one client comprising a first client application and a second client application, wherein the second client application being a newer version application of the first client application to be upgraded;

the client executing the first client application to connect with a first server application on a server, and receiving information from the first server application to control operations of a first equipment tool according to the received information, wherein the first equipment tool has a run manager, and has equipment information recording whether the first equipment tool is idle;

the client retrieving the equipment information from the rum manager of the first equipment tool, and determining whether the first equipment tool controlled by the client is idle according to the retrieved equipment information; and

when the first equipment tool controlled by the client is idle, the client terminating the execution of the first client application, executing the second client application to connect to a second server application on the server, and receiving information from the second server application to control operations of the first equipment tool according to the received information, wherein the second server application is a newer version application of the first server application to be upgraded.

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

11. The method of claim 10 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.

12. The method of claim 10 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.

13. The method of claim 9 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.

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

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

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

17. A software deployment system, comprising:

a server comprising a first server application and a second server application, wherein the second server application is a newer version application of the first server application to be upgraded; and

at least one client controlling operations of at least one equipment tool, wherein the first equipment tool has a run manager, and has equipment information recording whether the first equipment tool is idle, and the at least one client having a client application connected to the first server application on the server;

wherein the at least one client executes the client application, receives equipment information from the run manager of the equipment tool, determines whether the equipment tool controlled by the client is idle according to the received equipment information, and when the controlled equipment tool is idle, upgrades the client application and directs the upgraded client application to connect to the second server application.

18. The system of claim 17 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.