1. Field of the Invention
This invention generally relates to updating software and operating systems. More specifically, the invention relates to the automatic updating of software and operating systems on a target, client system.
2. Background Art
Software and operating systems are constantly being updated with new features or with fixes to solve defects. The applications and systems can be updated with full product releases or with incremental releases.
Presently, customers that own applications and systems are required to get the updates and upgrade their software. The customer can get updates from a vendor, either electronically over the Internet, or physically on a CD tape, etc. In some cases, the customer must prove their entitlement to a software product or operating system before they are allowed to retrieve an update.
Customers can have multiple products residing on one machine from multiple vendors, and can have multiple platforms at their sites. Some products can update themselves, while others cannot. It would be highly desirable to provide customers with a solution that could provide updates for a single machine, or for their entire IT network. In addition, some IT networks are behind firewalls and require secure access to automatic updates.
An object of this invention is to provide automated electronic software updates and services for systems and applications across disparate platforms.
Another object of the present invention is to create a layer, between a target and a host with the updates, that controls the updating of applications and systems without having to have the technology embedded into a product.
A further object of the invention is to provide a business intelligence for software updates and services that acts as a middle layer, or director, between a target system and a host that stores updates.
Another object of the invention is to provide an environment in which a client and a server can interact with mutual assurance that their transactions are secure.
These and other objectives are attained with a method and system for updating software applications or systems on a target client. The method comprises the steps of providing the target client with an update manager, and using the update manager initiate a procedure to compare the level of software or services on the target client with the level of software or services available on a specified server to determine if an update is available on the server for the software or services on the target client. If an update is available, the update is copied from the server to the target client. Preferably, the update manager registers with the server manager to have a specified one or more of the applications or systems updated.
The above-mentioned procedure that is initiated by the update manager to compare the level of software, may be performed by the server, or alternatively, this procedure may be performed by the update manager or the update manager and the server may work together to perform this procedure. Also, the preferred embodiment of the invention uses information that currently exists with the customer and vendor that can make the update process more automated. In particular, customers know (or the information exists in their systems) what software levels they have installed, and the vendor knows what they are entitled to. Instead of requiring the customer to access a site, determine if an update is available, then locate the update, and provide entitlement information, the preferred embodiment of the present invention provides a procedure that knows enough about the customers and their system or systems to navigate finding and retrieving an update on their behalf.
Further benefits and advantages of the invention will become apparent from a consideration of the following detailed description, given with reference to the accompanying drawings, which specify and show preferred embodiments of the invention.
With reference to
If an update exists, the user is notified that an update is available. The user can then select to have a director 20 retrieve the update using the proper credentials to identify the user and the target product to update. The director 20 then notifies the user 10 that the update has been retrieved and is ready to be installed. The director 20 controls the amount of data that needs to be shipped by the host by only shipping what is needed to the target.
More specifically, a customer 10 registers for an automated update service through a portal. Updates can include upgrades, services or publications. A certificate 22 is returned for each service. Customer information is stored at site 24. A module may be added onto director 20 to handle a specific platform. If needed, that module is downloaded and added.
Director 20 periodically checks for updates to registered products. Service and product availability are based on certificates 22. System checks system inventory for synchronization. System configuration is sent to server 16.
If an update is available, a notification is sent to the customer 10 informing him or her of the new update. If the customer wishes to, he or she can launch system 16 and send an automatic update request. Any necessary customer information, it may be noted, is already stored. If multiple updates are available, the customer can select individual ones to update.
Director 20 places an order for an upgrade, and the director periodically checks for a completed order. If the order is ready and the customer operating system 12 is validated, a ticket 24 is issued for the order and sent back to the client 12.
Director 20 notifies server 16 to retrieve the order. The ticket 24 sent to server 14 will automatically keep retrying in case of interrupted transfer until the download is completed. Once download is complete, a message is sent back to notify the customer 10. Customers can initiate installation through director 20 or by their own computer system.
The user 10 can configure director 20 to have various degrees of automation, with multiple checkpoints or none. In this way, the present invention can be used as a policy director for managing updates. For instance, as illustrated in
The preferred embodiment of the invention, as described above, provides a number of important advantages. The invention effectively addresses the problem of providing automatic updating of software and operating systems on a target, client system by creating a layer between the product installed on a client's system and the developer of the product. A program, installed on the client's system, can query the installed products and levels, and communicates that information to a server that can determine if an update is available. By solving the problem in this way, the product itself does not have to be modified to look for updates.
While it is apparent that the invention herein disclosed is well calculated to fulfill the objects stated above, it will be appreciated that numerous modifications and embodiments may be devised by those skilled in the art, and it is intended that the appended claims cover all such modifications and embodiments as fall within the true spirit and scope of the present invention.
Number | Name | Date | Kind |
---|---|---|---|
5835911 | Nakagawa et al. | Nov 1998 | A |
5870610 | Beyda | Feb 1999 | A |
5933646 | Hendrickson et al. | Aug 1999 | A |
5999947 | Zollinger et al. | Dec 1999 | A |
6061686 | Gauvin et al. | May 2000 | A |
6067582 | Smith et al. | May 2000 | A |
6151708 | Pedrizetti et al. | Nov 2000 | A |
6157940 | Marullo et al. | Dec 2000 | A |
6167567 | Chiles et al. | Dec 2000 | A |
6202207 | Donohue | Mar 2001 | B1 |
6282709 | Reha et al. | Aug 2001 | B1 |
6282712 | Davis et al. | Aug 2001 | B1 |
6314565 | Kenner et al. | Nov 2001 | B1 |
6332217 | Hastings | Dec 2001 | B1 |
6360255 | McCormack et al. | Mar 2002 | B1 |
6381741 | Shaw | Apr 2002 | B1 |
6467088 | alSafadi et al. | Oct 2002 | B1 |
6493871 | McGuire et al. | Dec 2002 | B1 |
6643669 | Novak et al. | Nov 2003 | B1 |
6751674 | Satagopan et al. | Jun 2004 | B1 |
6785716 | Nobakht | Aug 2004 | B1 |
6789255 | Pedrizetti et al. | Sep 2004 | B1 |
6832373 | O'Neill | Dec 2004 | B1 |
6898618 | Slaughter et al. | May 2005 | B1 |
6959320 | Shah et al. | Oct 2005 | B1 |
20020078142 | Moore et al. | Jun 2002 | A1 |
20020100035 | Kenyon et al. | Jul 2002 | A1 |
20020120725 | DaCosta et al. | Aug 2002 | A1 |
20020138567 | Ogawa | Sep 2002 | A1 |
Number | Date | Country |
---|---|---|
2001236210 | Aug 2001 | JP |
200202055839 | Feb 2002 | JP |
Number | Date | Country | |
---|---|---|---|
20040123283 A1 | Jun 2004 | US |