|Publication number||US20020016956 A1|
|Application number||US 09/948,821|
|Publication date||7 Feb 2002|
|Filing date||7 Sep 2001|
|Priority date||27 Nov 1995|
|Also published as||US5845077, US6073214, US6327617, US7925718, US8612551, US20060155737, US20060218246, US20110185351, US20140109073|
|Publication number||09948821, 948821, US 2002/0016956 A1, US 2002/016956 A1, US 20020016956 A1, US 20020016956A1, US 2002016956 A1, US 2002016956A1, US-A1-20020016956, US-A1-2002016956, US2002/0016956A1, US2002/016956A1, US20020016956 A1, US20020016956A1, US2002016956 A1, US2002016956A1|
|Original Assignee||Microsoft Corporation|
|Export Citation||BiBTeX, EndNote, RefMan|
|Patent Citations (60), Referenced by (80), Classifications (5), Legal Events (2)|
|External Links: USPTO, USPTO Assignment, Espacenet|
 This is a continuation of U.S. patent application Ser. No. 09/558,957, entitled “METHOD AND SYSTEM FOR IDENTIFYING AND OBTAINING COMPUTER SOFTWARE FROM A REMOTE COMPUTER,” filed Apr. 25, 2000, which is a continuation of U.S. patent application Ser. No. 09/149,993, entitled “METHOD AND SYSTEM FOR IDENTIFYING AND OBTAINING COMPUTER SOFTWARE FROM A REMOTE COMPUTER,” filed Sep. 9, 1998, which has since issued as U.S. Pat. No. 6,073,214 and is a continuation of application Ser. No. 08/562,929, entitled “METHOD AND SYSTEM FOR IDENTIFYING AND OBTAINING COMPUTER SOFTWARE FROM A REMOTE COMPUTER,” filed Nov. 27, 1995, which has since issued as U.S. Pat. No. 5,845,077 and is hereby incorporated by reference.
 The present invention relates to a system for automatically identifying software that may be appropriate for installation on a computer and for making that software available to that computer. In particular the invention relates to a remote system that inventories software installed on a computer, identifies additional software that may be appropriate for the computer (e.g. patches, fixes, new versions of existing software, new software, etc.), and makes the identified software available to that computer.
 The continual and rapid development of computers, computer software and related technology has revealed many problems with the typical distribution channels for computer software. For example, computer software, the coded instructions that control a computer's operation, are constantly and incrementally being upgraded and improved. The computer hardware and operating system environment on which the computer software is used is continually being changed, which requires additional changes in the computer software (e.g. new device drivers, new operating system calls, etc.).
 A computer software developer will typically release an initial version of a software product. Thereafter, as new and improved computers and peripherals are developed, the software product will commonly be upgraded so as to take full advantage of the increased capabilities of the hardware. In addition, a software developer, to remain competitive, will often upgrade the software product to provide new features and functionality.
 With the ever increasing pace of advancement in computer related technologies, software developers compete to be the first to offer a new feature or upgrade. As a result, sometimes software products are made available to the public with unknown errors or defects. Similarly, software products that work as intended on a particular computer with a particular configuration, may fail when installed on a different computer having a different configuration (e.g. different hardware, peripherals, operating systems, etc.). Software developers frequently provide fixes for their software products to correct defects that were undetected or unanticipated at the time the software product was released. Fixes are also provided to allow the software product to function correctly on a new computer or with a different operating system environment.
 However, it is often difficult for software developers to make upgrades and fixes available to users. This difficulty not only deprives the user of access to the most reliable and up-to-date software products, it can result in lost sales to the software developer and can damage the goodwill and the development of a long term relationship with a customer by releasing a flawed or deficient software product.
 Commonly, mass distribution of commercial software products is accomplished by copying the software product onto storage media (e.g. CD-ROMs, floppy disks, magnetic tapes, etc.). To take advantage of economies of scale, typically a large number of copies of the software product are made during the manufacture of a particular software product. Then, the storage media containing the software product is provided to distributors and retailers for sale to users. However, given the rapid pace of software development, this manner of distribution is frequently insufficient. For example, it is not uncommon that defects are detected and fixes created shortly after a software product is introduced to the public. However, the software products that remain in the distribution chain contain the defect without the fix. This situation is frustrating for users who subsequently purchase the software product that is already obsolete (i.e. because of the defects).
 Software can also be distributed over electronic bulletin board systems, the Internet, etc. In such systems, a user connects to the bulletin board and then selects and downloads desired software. Such systems allow for rapid updating of software by simply supplying a new updated version of the software to the bulletin board. However, such systems also require a degree of user sophistication and technical expertise in the selection, downloading and installation of the new software. Moreover, such systems do not provide a user that has already obtained a software product with a simple, automatic way of learning of or obtaining upgrades or fixes for that product. The software provider may also have updated help files and other help utilities about which a user would have no way of knowing.
 In accordance with an illustrated embodiment of the present invention, many of the problems associated with obtaining computer software are overcome. A user, with a user computer is allowed to access (e.g. with a modem, an Internet connection, etc.) an update service at a remote location on which is stored a variety of computer software. When a user accesses the remote update service, an update service computer conducts an automatic inventory of the computer software on the user computer. The data collected from the inventory of the user computer software is then used to make comparisons to database entries from a database on the update service computer. The database entries contain information about computer software available on the update service computer. The comparison is conducted to identify software available from the remote update service that might be appropriate for installation on the user computer (i.e. new computer software, new versions of existing computer software, patches or fixes for existing computer software, new help files, etc.). After the comparison is completed, the update service computer makes the computer software stored at the remote update service computer available to the user.
 In one aspect of the invention, available computer software can be downloaded from the remote update service computer and installed immediately on the user computer. Another aspect of the invention allows the update service computer to contact the user computer at a later, more convenient time, re-establish two-way communications, then download and install available computer software on the user computer. If a delayed download is requested, the user will provide access information (e.g. phone number, network address, a file of commands to execute to logon the user computer, etc.) to the update service computer which allows the remote update service computer to re-connect to the user computer. The transfer may use an encryption scheme to permit safe transfer of the software to the user computer.
 In yet another aspect of the invention, the system will allow a user to purchase the available computer software electronically. The user, for example, provides credit card information, debit card information, an account number to bill, etc. to the update service computer. Secure transaction technology and/or digital signatures are used to safeguard the payment information. After verifying the payment information, the update service computer permits transfer of the computer software.
 The update service has several advantages. A user is automatically provided with information about the available versions of computer software as a result of the inventory conducted by the update center computer. If the version of the computer software on the user computer has defects that are known and have been corrected, the user is alerted to this fact and is offered an up-to-date version of the computer software. The user is also alerted to the availability of new computer software, or enhanced versions of existing computer software, and can purchase them electronically. In either case, the most up-to-date versions of computer software are available for downloading to users.
 The available versions of the computer software can also be automatically installed on the user computer. Since it is no longer necessary for the user to install the computer software, the incidence of user related installation problems is greatly reduced. It is also not necessary for the user to obtain or save any storage media since the computer software is downloaded directly to the user computer. If the computer software installed on the user computer ever gets corrupted, the user can call the update service (e.g. for some limited number of iterations) and download a new (and up-todate) copy of the computer software.
 In addition to providing benefits for the user, the illustrated embodiment of the invention provides benefits to the developers of the software. The developers of the computer software save support, distribution, and advertising costs. A user who calls the update service automatically obtains up-to-date versions of available computer software, and may never encounter defects which would have been encountered using an earlier, defective version of the computer software. As a result, a user will require less support from the developers of the software, be more satisfied, and be more willing to purchase future versions of computer software. Since the computer software is downloaded to the user computer, the developers of the computer software may save distribution costs as fewer versions of the computer software have to be copied to storage media and distributed. In addition, since the user is also alerted when new computer software, and/or new versions of existing computer software are available, the software developers may also save advertising costs.
 The foregoing and other features and advantages of the illustrated embodiment of the present invention will be more readily apparent from the following detailed description, which proceeds with reference to the accompanying drawings.
FIG. 1 is a block diagram of a computer system used to implement an illustrated embodiment of the present invention.
FIG. 2 is a block diagram showing the update service center and the remote user computers.
FIG. 3 is a block diagram showing the access processes on the user and update service computers.
 FIGS. 4A-4B are a flow chart showing an illustrative sequence which is followed when a user calls the update service.
FIG. 5 is a flow chart showing an illustrative sequence followed when the update service re-connects to a user computer.
 Referring to FIG. 1, an operating environment for the illustrated embodiment of the present invention is a computer system 10 with a computer 12 that comprises at least one high speed processing unit (CPU) 14, in conjunction with a memory system 16, an input device 18, and an output device 20. These elements are interconnected by a bus structure 22.
 The illustrated CPU 14 is of familiar design and includes an ALU 24 for performing computations, a collection of registers 26 for temporary storage of data and instructions, and a control unit 28 for controlling operation of the system 10. Any of a variety of processors, including those from Digital Equipment, Sun, MIPS, IBM, Motorola, NEC, Intel, Cyrix, AMD, Nexgen and others are equally preferred for CPU 14. Although shown with one CPU 14, computer system 10 may alternatively include multiple processing units.
 The memory system 16 includes main memory 30 and secondary storage 32. Illustrated main memory 30 is high speed random access memory (RAM) and read only memory (ROM). Main memory 30 can include any additional or alternative high speed memory device or memory circuitry. Secondary storage 32 takes the form of long term storage, such as ROM, optical or magnetic disks, organic memory or any other volatile or non-volatile mass storage system. Those skilled in the art will recognize that memory 16 can comprise a variety and/or combination of alternative components.
 The input and output devices 18, 20 are also familiar. The input device 18 can comprise a keyboard, mouse, pointing device, sound device (e.g. a microphone, etc.), or any other device providing input to the computer system 10. The output device 20 can comprise a display, a printer, a sound device (e.g. a speaker, etc.), or other device providing output to the computer system 10. The input/output devices 18, 20 can also include network connections, modems, or other devices used for communications with other computer systems or devices.
 As is familiar to those skilled in the art, the computer system 10 further includes an operating system and at least one application program. The operating system is a set of software which controls the computer system's operation and the allocation of resources. The application program is a set of software that performs a task desired by the user, making use of computer resources made available through the operating system. Both are resident in the illustrated memory system 16.
 In accordance with the practices of persons skilled in the art of computer programming, the present invention is described below with reference to symbolic representations of operations that are performed by computer system 10, unless indicated otherwise. Such operations are sometimes referred to as being computer-executed. It will be appreciated that the operations which are symbolically represented include the manipulation by CPU 14 of electrical signals representing data bits and the maintenance of data bits at memory locations in memory system 16, as well as other processing of signals. The memory locations where data bits are maintained are physical locations that have particular electrical, magnetic, optical, or organic properties corresponding to the data bits.
 As is shown in FIG. 2, the illustrated embodiment of the invention consists of one or more user computers 34 which are connected over communications links 36 to an update service center 38. The update service center consists of one or more second remote computer(s) 40, one or more communications links 36, and one or more databases 42.
 The update service center 38 consists of one or more computers 40 (e.g. the computer that was described in FIG. 1) which are capable of simultaneous access by a plurality of user computers. If a plurality of update service computers are used, then the update service computers may be connected by a local area network (LAN) 44 or any other similar connection technology. However, it is also possible for an update service center to have other configurations. For example, a smaller number of larger computers (i.e. a few mainframe, mini, etc. computers) with a number of internal programs or processes running on the larger computers capable of establishing communications links to the user computers. The update service center may also be connected to a remote network (e.g. the Internet) or a remote site (e.g. a satellite) (which is not shown in FIG. 2). The remote network or remote site allows the update service center to provide a wider variety of computer software than could be stored at the update service center. One or more databases 42 connected to the update center computer(s) 40 are used to store database entries consisting of computer software available on the update service computer(s). The update service computer(s) also contain a plurality of communications links 36 such as telecommunications connections (e.g. modem connections, ISDN connections, ATM connection, frame relay connections, etc.), network connections (e.g. Internet, etc.), satellite connections (e.g. Digital Satellite Services, etc.), wireless connections, two way paging connections, etc., to allow one or more user computers to simultaneously connect to the update service computer(s). The connections are managed by an update server 46.
 After a user computer establishes two-way communications with the update service computer, an inventory of computer software on the user computer is completed without interaction from the user, sent to the update service computer, and compared to database entries on the update service computer. The database entries from the database connected to the update service computer contain information about computer software which is available to a user. After the comparison, the user computer is sent back a summary of available computer software which is displayed for the user. The summary contains information such as the availability of patches and fixes for existing computer software, new versions of existing computer software, and brand new computer software, new help files, etc. The user is then able to make one or more choices from the summary of available computer software, and have the computer software transferred from the update service computer to the user computer. The user may choose to update on the fly, or store update information for future update needs.
 As is shown in FIG. 3, running on the update service computer(s) 40 is one or more service update applications (SUA) 48 that will communicate with a user update application (UUA) 50 on the user computer when the update service is contacted by the a user with a user computer. The user update application 50 is a computer software program that is capable of initiating, establishing and terminating two-way communications with an update service application on the update service computer. The service update application 48 is a computer software program which is also capable of initiating, establishing and terminating two-way communications with a user update application on a user computer.
 To access the update service center 38, a user starts a user update application (UUA) 50 on the user computer 34 to begin the access process. The user update application 50 tries to establish a two-way communications link 36 with an update service computer 40 using a modem, a network connection (e.g. Internet), etc. However, this access can also be completed by a variety of other methods which provide two-way data transfer. As the user update application 48 on the user computer 34 tries to establish a two-way communications link 36 to the update service computer 40, the update service computer starts a service update application (SUA) 48. The service update application on the update service computer then tries to establish a two-way communications link to the user update application on the user computer. This is shown by the dashed lines 52 in FIG. 3. This communications link can be established with a network protocol stack, (e.g. TCP/IP) through sockets, or any other two-way communications technique known in the art.
 After establishing a two-way communications link, the service update application conducts an automatic inventory (i.e. without input from the user) of the computer software on the user computer. The data collected during the inventory is sent from the user computer to the remote update service computer. The service update application on the update service computer compares the inventory data collected from the user computer to data stored in a database on the update service computer. The database contains information on available computer software available from the update service. The update service computer then creates a summary and sends the summary to the user computer. The summary 54 is then presented to the user by the user computer. The summary contains information about computer software available on the update service computer such as the availability of patches and fixes for existing computer software, new versions of existing computer software, and brand new computer software, etc. In addition, the availability of agent help files, wizards, inference engines, and other operating system components will be listed in the summary.
 The illustrated embodiment of the invention is implemented in the Microsoft Windows 95 operating system by the Microsoft Corporation of Redmond, Wash. using a modem, or an Internet network connection, for access to the update service computer. The invention can likewise be practiced with other operating systems and other access technologies that allow two-way data transfer.
 As is shown in the flowchart in FIG. 4A, a user begins the access sequence (56) to an update service by launching a user update application included in the Windows 95 operating system. However, the user update application can also be any application that is capable of two-way communications, and run under other operating systems. The user update application allows the user computer to establish a two-way communications path for access to the update service computer.
 When the user update application starts (58), the user is shown optional help information which instructs the user on how to establish a connection between the user computer and the update service computer. The actual connection configuration is completed by allowing a user to choose the appropriate connection method (60). For example, the user may choose to establish the connection with a modem. If a modem is chosen, the phone number to dial, modem (e.g. speed, line type, etc.) and communications parameters (e.g. parity, stop bits, etc.) are then configured. If the user chooses to make a network connection (e.g. Internet, etc.) to access the update service, the network address of the update service and other network parameters are configured. A similar sequence would be completed for other connection technologies.
 When the user update application attempts to make the desired connection (60), the update service computer launches a service update application (64). A two-way communications path (66) is set up between the service update application on the update service computer and the user update application on the user computer. The service update application on the update service computer then requests that the user update application on the user computer conduct an automatic inventory of all computer software installed (68) on the user computer.
 In the illustrated system, this inventory is done automatically (i.e. without input from the user), and is completed by assigning the inventory task to a Windows 95 operating system process thread on the user computer. The operating system thread completes the task in the “background” while the user is performing other activities in the “foreground” (e.g. choosing options from the user update application). In reality, there are no real background and foreground processes, just a number of operation system process and process threads which are run for some specified time interval by the operating system. Threads are well known in the art and are used in other operating systems such as Windows NT by Microsoft, and OS/2 by IBM. However, other operating system techniques could also be used to accomplish the inventory on the user computer.
 During the inventory, data is collected about all computer software installed on the user computer. Data such as the software title, date, version, file size, file checksum, directory location on the user computer, etc. are collected. After the inventory is complete, the user update application sends (70) the inventory data from the user computer to the service update application on the update service computer. The service update application compares the user inventory data from the user computer to database entries in the computer software database to automatically analyze the computer software stored on the user computer (72). The database connected to the update service computer has entries which contain information about available computer software. The database entries also identify and describe, for example, components of the computer software, including new computer software, patches, fixes, new help files, wizards, inference engines, other operating system components, updates as well as enhancements and new features of existing computer software. The database entries describing new computer software may also include entries describing brand new computer software (i.e. computer software that is newly created, and not previously existing).
 Any computer software installed on the user computer which is listed in the database on the update service computer (e.g. out-of-date and/or require a maintenance update, etc.) is flagged as available (74). The user computer may also contain computer software that is not known by the update service. If the user computer contains computer software which is unknown to the update service computer, this computer software is marked as unknown by the update service computer. After the service update application completes the analysis of user computer software, a summary report is sent back to the user computer from the update service computer (76).
 In the illustrated system, the user can choose from several update service options. One option may be to check for maintenance updates for all computer software installed on the user computer that is known by the update service. A second option may be to check only specific computer software, or a specific group of computer software stored on the user computer for maintenance updates. For example, if the user wanted to check and see if there were any maintenance updates for a particular word processing program, option two would be selected. A third option may be to check whether there are any new or enhanced versions of computer software available from the update service. A fourth option may be to check only for new versions of specific computer software or groupings of computer software installed on the user computer. A fifth option may be to check the update service computer for information on new computer software (i.e. brand new products, not new or enhanced versions of existing products). A sixth option may be to check only if there are new help files, or other new support data available. This list of options is not intended to be all inclusive, as other options can be added to provide additional update service functionality. Based on user input, the user update application creates an output report (78) (FIG. 4B) based on the option(s) chosen by the user and the summary report created by the service update application. The service update application can also create the output report directly, using default choices with no input at all from a user.
 If the output report is not empty (80), a second optional report is created and displayed for the user providing a short description that summarizes the computer software available from the update service (82). This second optional report is used by the user to determine what computer software on the user computer will be updated, if any. If the output report is empty, the computer software on the user computer is current and up-to-date (84), so no further action by either the update service computer or the user computer is required.
 If the output report is not empty, then the user is asked to choose which available computer software shown in the output report, if any, will be downloaded and installed on the user computer (86). No software is downloaded without the user's permission. If one or more computer software components (i.e. pieces or parts of the available computer software) are chosen by the user, the user update application is instructed to make backup copies of all of the computer software components on the user computer that will be affected, and create a log for the user documenting which computer software will be replaced (88). The backup copies and the log can be used by the user to restore the original version of the computer software components on the user computer if a need arises to do so.
 The user has the option of choosing none, one, or a number of computer software components to download and install. If the list of available computer software to be downloaded and installed is large, the user also has the option of delaying the update to a later time (90). If the user chooses an immediate download, the user is asked if the service update center should also install the computer software chosen by the user (92) after downloading.
 If immediate installation is chosen, the service update application on the update service computer downloads the available software to the user computer and installs the software in the proper place (e.g. in the proper directory or subdirectory) on the user computer (94). A log is also created that records what computer software was downloaded to the user computer. If immediate installation is not chosen by the user, the user can save any update information, and continue with other tasks before deciding when to download any software chosen by the user.
 If the user chooses a delayed update, the user provides re-connect information (98) that allows the update service computer to re-connect to the user computer at a more convenient time (e.g. midnight, etc.) and complete the downloading and installation at that time.
 As part of the re-connect information, the user may create a logon script using an automated macro language to provide the logon sequence to be used, and the directory to be used to download the software chosen by the user. The logon script and the time the user wishes to have the chosen software downloaded are then sent to the update service computer, and stored in an update service computer database. At the appropriate time chosen by the user, the update service will execute the logon script to re-connect to the user computer, and download the chosen software in the proper directory. An encryption scheme may also be used to permit safe transfer of the software to the user computer.
 The user also has the option of choosing a logon method different then the one they are currently connected to the update service center with. For example, if a user is connected to the update service center with a modem, the user may choose to have the chosen software downloaded at a later time using a network connection (e.g. Internet, etc.). However, the user's computer must be capable of accepting software with a different connection method.
 To allow a re-connection using a modem, the user would enter the phone number of the phone line attached to the user computer and send this information to the update service computer. The user would leave the user computer and modem on, and set the communications software in an answer mode to answer any incoming calls. For a network re-connection, the user would provide the update service computer the user network address and set the network software in a host mode to process any network connection attempts.
 The delayed downloading is illustrated in the flow chart in FIG. 5. To complete the delayed downloading, the update service computer launches a service update application that tries to re-connect (100) to the user computer. The update service application will use the information provided at an earlier time by a user (e.g. modem logon information, network logon information, a logon script, etc.). If the connection is successful, a service update application on the update service computer asks the user computer to launch a user update application to re-establish a two-way communications path (102). The re-connect to the user computer may be completed using a different access method than was used during the original user computer-update service computer connection. For example, the update service computer may request a digital satellite system re-connect to the user computer instead of the update service computer. A different access method is typically chosen to provide the most efficient and greatest bandwidth data transfer between the update service computer and the user computer.
 After establishing a new two-way communications path, the user update application creates a new directory (104) on the user computer, where the computer software is transferred and stored (106). A log is also created to document what available computer software was transferred to the user computer. Included with the downloaded computer software is an installation application that will be used later by the user to install the computer software. When the transfers are complete, the update service computer terminates the connection to the user computer (108). An encryption scheme may also be used to permit safe automated transfer of the software to the user computer.
 When the user is ready to install the computer software (e.g. the next morning if the computer software was transferred and installed in the middle of the night), the user simply launches the installation application supplied by update service computer.
 Leaving the user an installation application to execute is an added safety and security measure for both the user and the update service. The user computer is not updated unless the user personally starts the installation process. However, the user can also choose to have the computer software automatically installed by the update service when it re-connects to the user computer (but, user permission is always obtained and recorded first). In this case, the installation application is not downloaded to the user computer. However, a log is created so a user can determine what available computer software was downloaded and installed.
 As was described above, the third, fourth, and fifth options allow a user to check for new versions of existing computer software, or new computer software available from the update service. If a new version of existing computer software, or new computer software is available, the user is asked if she wishes to purchase the computer software. If so, the appropriate fee is requested from the user. The user can pay the fee electronically by transmitting credit card information, debit card information, billing account information, etc. to the update service computer from the user computer. Digital signatures, secure transaction technology, or an encryption scheme may also be used to collect payment information from the user. Once the fee information is collected by the update service computer and is verified, the user can choose between immediate or delayed downloading of the new, or new version of the computer software following steps (88-98) (FIG. 4B) described above.
 Since new versions of computer software are typically very large, the user will be informed that a delayed installation is probably most efficient for the user. If a delayed installation of a new product is chosen, the update service computer will then re-connect to the user computer at a later time and download the new version of the computer software as was shown in FIG. 5. In the illustrated embodiment, the update service uses a digital satellite service link, or some other higher bandwidth connection to transfer the computer software to the user computer whenever possible.
 If the user chooses not to pay for a new version of computer software when the update service is called, additional data from which the user can obtain more information on the new computer software is displayed. For example, the information may contain a summary of the features of the new computer software and the information may also contain a list of retail outlets close to the user where the user may then purchase a new version of computer software on storage media if desired. Some users may prefer to obtain the computer software on storage media and call the update service to obtain up-to-date versions of the computer software.
 With automatic downloading and installation of computer software from the update service, the user is relieved from the burden of obtaining computer software (e.g. on storage media, by downloading from a bulletin board or on-line service, etc.), and installing the computer software on the user computer. Once a user purchases computer software, periodic calls to the update service will keep the user current and up-to-date.
 It should be understood that the programs, processes, or methods described herein are not related or limited to any particular type of computer apparatus, unless indicated otherwise. Various types of general purpose or specialized computer apparatus may be used with or perform operations in accordance with the teachings described herein.
 Having illustrated and described the principles of the present invention in an illustrated embodiment, it should be apparent to those skilled in the art that the embodiment can be modified in arrangement and detail without departing from such principles. For example, elements of the illustrated embodiment shown in software may be implemented in hardware and vice versa. Similarly, hardware and software components can be interchanged with other components providing the same functionality.
 In view of the wide variety of embodiments to which the principles of this invention can be applied, it should be understood that the illustrated embodiments are exemplary only, and should not be taken as limiting the scope of my invention. Rather, I claim as my invention all such embodiments as come within the scope and spirit of the following claims and equivalents thereto.
|Cited Patent||Filing date||Publication date||Applicant||Title|
|US4558413 *||21 Nov 1983||10 Dec 1985||Xerox Corporation||Software version management system|
|US4796181 *||24 Oct 1986||3 Jan 1989||Wiedemer John D||Billing system for computer software|
|US4953209 *||31 Oct 1988||28 Aug 1990||International Business Machines Corp.||Self-verifying receipt and acceptance system for electronically delivered data objects|
|US4982430 *||24 Apr 1985||1 Jan 1991||General Instrument Corporation||Bootstrap channel security arrangement for communication network|
|US5003591 *||25 May 1989||26 Mar 1991||General Instrument Corporation||Functionally modifiable cable television converter system|
|US5047928 *||3 Jan 1989||10 Sep 1991||Wiedemer John D||Billing system for computer software|
|US5142680 *||26 Apr 1989||25 Aug 1992||Sun Microsystems, Inc.||Method for loading an operating system through a network|
|US5155484 *||13 Sep 1991||13 Oct 1992||Salient Software, Inc.||Fast data compressor with direct lookup table indexing into history buffer|
|US5155680 *||27 Apr 1989||13 Oct 1992||Signal Security Technologies||Billing system for computing software|
|US5155847 *||3 Aug 1988||13 Oct 1992||Minicom Data Corporation||Method and apparatus for updating software at remote locations|
|US5247683 *||19 Jun 1991||21 Sep 1993||International Business Machines Corporation||System and method for installing software and updating configuration files|
|US5267171 *||19 Mar 1991||30 Nov 1993||Brother Kogyo Kabushiki Kaisha||Computer software vending machine|
|US5337360 *||5 Jan 1994||9 Aug 1994||Fischer Addison M||Method and apparatus for creating, supporting, and using travelling programs|
|US5338211 *||6 Nov 1992||16 Aug 1994||Yazaki Corporation||Connector cover structure|
|US5367621 *||6 Sep 1991||22 Nov 1994||International Business Machines Corporation||Data processing method to provide a generalized link from a reference point in an on-line book to an arbitrary multimedia object which can be dynamically updated|
|US5367686 *||12 Apr 1993||22 Nov 1994||International Business Machines Corporation||Method for automated complex multilevel softward installation in a data processing system|
|US5390247 *||20 Sep 1993||14 Feb 1995||Fischer; Addison M.||Method and apparatus for creating, supporting, and using travelling programs|
|US5421009 *||22 Dec 1993||30 May 1995||Hewlett-Packard Company||Method of remotely installing software directly from a central computer|
|US5473772 *||2 Sep 1993||5 Dec 1995||International Business Machines Corporation||Automatic update of static and dynamic files at a remote network node in response to calls issued by or for application programs|
|US5493682 *||26 Oct 1994||20 Feb 1996||International Business Machines Corporation||Object based system for software maintenance|
|US5495411 *||22 Dec 1993||27 Feb 1996||Ananda; Mohan||Secure software rental system using continuous asynchronous password verification|
|US5496177 *||15 Mar 1994||5 Mar 1996||International Business Machines Corporation||Method and apparatus for presenting new computer software functions to a user based upon actual usage|
|US5528490 *||10 Apr 1992||18 Jun 1996||Charles E. Hill & Associates, Inc.||Electronic catalog system and method|
|US5548645 *||7 Jul 1994||20 Aug 1996||Ananda; Mohan||Secure software rental system using distributed software|
|US5555416 *||17 Aug 1994||10 Sep 1996||Sun Microsystems, Inc.||Automated software installation and operating environment configuration for a computer system based on classification rules|
|US5586304 *||8 Sep 1994||17 Dec 1996||Compaq Computer Corporation||Automatic computer upgrading|
|US5586322 *||2 Jun 1995||17 Dec 1996||Beck; Robert E.||Workgroup organized network manager with workstation comparison system|
|US5634056 *||6 Oct 1995||27 May 1997||Runtime Design Automation||Run time dependency management facility for controlling change propagation utilizing relationship graph|
|US5638446 *||28 Aug 1995||10 Jun 1997||Bell Communications Research, Inc.||Method for the secure distribution of electronic files in a distributed environment|
|US5654746 *||1 Dec 1994||5 Aug 1997||Scientific-Atlanta, Inc.||Secure authorization and control method and apparatus for a game delivery service|
|US5654901 *||30 Jan 1995||5 Aug 1997||Telefonaktiebolaget Lm Ericsson||Loading software into field test equipment|
|US5678002 *||18 Jul 1995||14 Oct 1997||Microsoft Corporation||System and method for providing automated customer support|
|US5689711 *||21 Apr 1995||18 Nov 1997||Bardasz; Theodore||Method and apparatus for representing data dependencies in software modeling systems|
|US5694546 *||31 May 1994||2 Dec 1997||Reisman; Richard R.||System for automatic unattended electronic information transport between a server and a client by a vendor provided transport software with a manifest list|
|US5701451 *||7 Jun 1995||23 Dec 1997||International Business Machines Corporation||Method for fulfilling requests of a web browser|
|US5706502 *||25 Mar 1996||6 Jan 1998||Sun Microsystems, Inc.||Internet-enabled portfolio manager system and method|
|US5710918 *||7 Jun 1995||20 Jan 1998||International Business Machines Corporation||Method for distributed task fulfillment of web browser requests|
|US5717930 *||14 Sep 1995||10 Feb 1998||Seiko Epson Corporation||Installation system|
|US5721824 *||19 Apr 1996||24 Feb 1998||Sun Microsystems, Inc.||Multiple-package installation with package dependencies|
|US5742829 *||10 Mar 1995||21 Apr 1998||Microsoft Corporation||Automatic software installation on heterogeneous networked client computer systems|
|US5748960 *||18 Dec 1996||5 May 1998||Fischer; Addison M.||Method and apparatus for validating travelling object-oriented programs with digital signatures|
|US5764992 *||6 Jun 1995||9 Jun 1998||Apple Computer, Inc.||Method and apparatus for automatic software replacement|
|US5838906 *||17 Oct 1994||17 Nov 1998||The Regents Of The University Of California||Distributed hypermedia method for automatically invoking external application providing interaction and display of embedded objects within a hypermedia document|
|US5845077 *||27 Nov 1995||1 Dec 1998||Microsoft Corporation||Method and system for identifying and obtaining computer software from a remote computer|
|US5845090 *||30 Sep 1996||1 Dec 1998||Platinium Technology, Inc.||System for software distribution in a digital computer network|
|US5860012 *||19 May 1997||12 Jan 1999||Intel Corporation||Installation of application software through a network from a source computer system on to a target computer system|
|US5909581 *||30 Dec 1996||1 Jun 1999||Samsung Electronics Co., Ltd.||Automatic software updating method|
|US5913040 *||22 Aug 1995||15 Jun 1999||Backweb Ltd.||Method and apparatus for transmitting and displaying information between a remote network and a local computer|
|US5999740 *||29 Sep 1997||7 Dec 1999||International Computers Limited||Updating mechanism for software|
|US6016520 *||14 Jul 1995||18 Jan 2000||Microsoft Corporation||Method of viewing at a client viewing station a multiple media title stored at a server and containing a plurality of topics utilizing anticipatory caching|
|US6073214 *||9 Sep 1998||6 Jun 2000||Microsoft Corporation||Method and system for identifying and obtaining computer software from a remote computer|
|US6125388 *||1 Dec 1997||26 Sep 2000||Reisman; Richard R.||System for transporting information objects between a user station and multiple remote sources based upon user modifiable object manifest stored in the user station|
|US6332217 *||8 May 1998||18 Dec 2001||Hearme||Software inventory control system|
|US6529784 *||29 Feb 2000||4 Mar 2003||Caldera Systems, Inc.||Method and apparatus for monitoring computer systems and alerting users of actual or potential system errors|
|US6557054 *||20 Apr 2000||29 Apr 2003||Richard R. Reisman||Method and system for distributing updates by presenting directory of software available for user installation that is not already installed on user station|
|US6611862 *||20 Apr 2000||26 Aug 2003||Richard R. Reisman||User station software that controls transport and presentation of content from a remote source|
|US6658464 *||20 Apr 2000||2 Dec 2003||Richard R. Reisman||User station software that controls transport, storage, and presentation of content from a remote source|
|US6769009 *||20 Apr 2000||27 Jul 2004||Richard R. Reisman||Method and system for selecting a personalized set of information channels|
|US6769099 *||12 Apr 2002||27 Jul 2004||Sun Microsystems, Inc.||Method to simplify and speed up design rule/electrical rule checks|
|US20040015833 *||1 Nov 2001||22 Jan 2004||Dellarocas Chrysanthos Nicholas||Computer system and computer implemented process for representing software system descriptions and for generating executable computer programs and computer system configurations from software system descriptions|
|Citing Patent||Filing date||Publication date||Applicant||Title|
|US6711676||15 Oct 2002||23 Mar 2004||Zomaya Group, Inc.||System and method for providing computer upgrade information|
|US6938250||12 Jun 2002||30 Aug 2005||Microsoft Corporation||Image-based software installation|
|US7062764||17 Jun 2002||13 Jun 2006||Microsoft Corporation||System and method for manipulating offline software|
|US7117355||10 Aug 2004||3 Oct 2006||Upgradedetect, Inc.||System and method for providing computer upgrade information|
|US7219148||3 Mar 2003||15 May 2007||Microsoft Corporation||Feedback loop for spam prevention|
|US7249162||25 Feb 2003||24 Jul 2007||Microsoft Corporation||Adaptive junk message filtering system|
|US7251812||11 Jan 2002||31 Jul 2007||Microsoft Corporation||Dynamic software update|
|US7272853||4 Jun 2003||18 Sep 2007||Microsoft Corporation||Origination/destination features and lists for spam prevention|
|US7305585||23 May 2003||4 Dec 2007||Exludus Technologies Inc.||Asynchronous and autonomous data replication|
|US7409708||28 May 2004||5 Aug 2008||Microsoft Corporation||Advanced URL and IP features|
|US7464264||25 Mar 2004||9 Dec 2008||Microsoft Corporation||Training filters for detecting spasm based on IP addresses and text-related features|
|US7483947||2 May 2003||27 Jan 2009||Microsoft Corporation||Message rendering for identification of content features|
|US7519668||20 Jun 2003||14 Apr 2009||Microsoft Corporation||Obfuscation of spam filter|
|US7543053||13 Feb 2004||2 Jun 2009||Microsoft Corporation||Intelligent quarantining for spam prevention|
|US7558832||2 May 2007||7 Jul 2009||Microsoft Corporation||Feedback loop for spam prevention|
|US7577948||10 Aug 2004||18 Aug 2009||Upgradedetect, Inc.||System and method for providing computer upgrade information|
|US7581217||7 Jan 2005||25 Aug 2009||Microsoft Corporation||Dynamic software update|
|US7660865||12 Aug 2004||9 Feb 2010||Microsoft Corporation||Spam filtering with probabilistic secure hashes|
|US7664819||29 Jun 2004||16 Feb 2010||Microsoft Corporation||Incremental anti-spam lookup and update service|
|US7665131||9 Jan 2007||16 Feb 2010||Microsoft Corporation||Origination/destination features and lists for spam prevention|
|US7707457||28 Oct 2007||27 Apr 2010||Exludus Technologies, Inc.||Completing an interrupted data replication operation|
|US7711779||20 Jun 2003||4 May 2010||Microsoft Corporation||Prevention of outgoing spam|
|US7853609 *||12 Mar 2004||14 Dec 2010||Microsoft Corporation||Update distribution system architecture and method for distributing software|
|US7853943 *||20 Apr 2005||14 Dec 2010||Dell Marketing Usa, L.P.||Intelligent patch checker|
|US7904517||9 Aug 2004||8 Mar 2011||Microsoft Corporation||Challenge response systems|
|US7925718||26 May 2006||12 Apr 2011||Microsoft Corporation||Method and system for identifying and obtaining computer software from a remote computer|
|US7930353||29 Jul 2005||19 Apr 2011||Microsoft Corporation||Trees of classifiers for detecting email spam|
|US8046832||26 Jun 2002||25 Oct 2011||Microsoft Corporation||Spam detector with challenges|
|US8055096 *||10 May 2006||8 Nov 2011||Research In Motion Limited||Method and system for incremental patching of binary files|
|US8065370||3 Nov 2005||22 Nov 2011||Microsoft Corporation||Proofs to filter spam|
|US8214438||1 Mar 2004||3 Jul 2012||Microsoft Corporation||(More) advanced spam detection features|
|US8224905||6 Dec 2006||17 Jul 2012||Microsoft Corporation||Spam filtration utilizing sender activity data|
|US8250159||23 Jan 2009||21 Aug 2012||Microsoft Corporation||Message rendering for identification of content features|
|US8346897||28 Aug 2008||1 Jan 2013||Jon Jaroker||System and method for deploying and maintaining software applications|
|US8533270||23 Jun 2003||10 Sep 2013||Microsoft Corporation||Advanced spam detection techniques|
|US8584113 *||25 Mar 2010||12 Nov 2013||Bank Of America Corporation||Cross-updating of software between self-service financial transaction machines|
|US8612551||11 Apr 2011||17 Dec 2013||Microsoft Corporation||Method and system for identifying and obtaining computer software from a remote computer|
|US8626146||27 Oct 2004||7 Jan 2014||Qualcomm Incorporated||Method, software and apparatus for performing actions on a wireless device using action lists and versioning|
|US8671402 *||25 Mar 2010||11 Mar 2014||Bank Of America Corporation||Network-enhanced control of software updates received via removable computer-readable medium|
|US8930934 *||2 Mar 2009||6 Jan 2015||Time Warner Cable Enterprises Llc||Technique for updating a resident application and associated parameters in a user terminal through a communications network|
|US8938523||13 Dec 2012||20 Jan 2015||Jon Jaroker||System and method for deploying and maintaining software applications|
|US8972974||25 Mar 2010||3 Mar 2015||Bank Of America Corporation||Multiple invocation points in software build task sequence|
|US9092286||18 Dec 2003||28 Jul 2015||Qualcomm Incorporated||System to automatically process components on a device|
|US9122558||25 Mar 2010||1 Sep 2015||Bank Of America Corporation||Software updates using delta patching|
|US9128799||25 Mar 2010||8 Sep 2015||Bank Of America Corporation||Programmatic creation of task sequences from manifests|
|US9134989 *||31 Jan 2002||15 Sep 2015||Qualcomm Incorporated||System and method for updating dataset versions resident on a wireless device|
|US9143560||19 Jun 2008||22 Sep 2015||Qualcomm Incorporated||Methods and apparatus for dataset synchronization in a wireless environment|
|US20040003283 *||26 Jun 2002||1 Jan 2004||Goodman Joshua Theodore||Spam detector with challenges|
|US20040167964 *||25 Feb 2003||26 Aug 2004||Rounthwaite Robert L.||Adaptive junk message filtering system|
|US20040177110 *||3 Mar 2003||9 Sep 2004||Rounthwaite Robert L.||Feedback loop for spam prevention|
|US20040188511 *||18 Dec 2003||30 Sep 2004||Sprigg Stephen A.||System to automatically process components on a device|
|US20040215977 *||13 Feb 2004||28 Oct 2004||Goodman Joshua T.||Intelligent quarantining for spam prevention|
|US20040221062 *||2 May 2003||4 Nov 2004||Starbuck Bryan T.||Message rendering for identification of content features|
|US20040231647 *||5 Mar 2004||25 Nov 2004||Jorn Mey||Method for the operation of a fuel system for an LPG engine|
|US20040260776 *||23 Jun 2003||23 Dec 2004||Starbuck Bryan T.||Advanced spam detection techniques|
|US20040260922 *||25 Mar 2004||23 Dec 2004||Goodman Joshua T.||Training filters for IP address and URL learning|
|US20050010749 *||10 Aug 2004||13 Jan 2005||Zomaya Christ J.||System and method for providing computer upgrade information|
|US20050021649 *||20 Jun 2003||27 Jan 2005||Goodman Joshua T.||Prevention of outgoing spam|
|US20050022008 *||4 Jun 2003||27 Jan 2005||Goodman Joshua T.||Origination/destination features and lists for spam prevention|
|US20050022031 *||28 May 2004||27 Jan 2005||Microsoft Corporation||Advanced URL and IP features|
|US20050060608 *||16 Jul 2004||17 Mar 2005||Benoit Marchand||Maximizing processor utilization and minimizing network bandwidth requirements in throughput compute clusters|
|US20050118991 *||27 Oct 2004||2 Jun 2005||Koganti Sudheer B.||Method, software and apparatus for performing actions on a wireless device using action lists and versioning|
|US20050193386 *||20 Apr 2005||1 Sep 2005||Everdream Corporation||Intelligent patch checker|
|US20050203968 *||12 Mar 2004||15 Sep 2005||Microsoft Corporation||Update distribution system architecture and method for distributing software|
|US20050204006 *||12 Mar 2004||15 Sep 2005||Purcell Sean E.||Message junk rating interface|
|US20050216910 *||24 Feb 2005||29 Sep 2005||Benoit Marchand||Increasing fault-tolerance and minimizing network bandwidth requirements in software installation modules|
|US20060015561 *||29 Jun 2004||19 Jan 2006||Microsoft Corporation||Incremental anti-spam lookup and update service|
|US20060019646 *||21 Jul 2004||26 Jan 2006||Benco David S||Network support for mobile handset application customization|
|US20060031338 *||9 Aug 2004||9 Feb 2006||Microsoft Corporation||Challenge response systems|
|US20060037012 *||10 Aug 2004||16 Feb 2006||Zomaya Christ J||System and method for providing computer upgrade information|
|US20060168576 *||27 Jan 2005||27 Jul 2006||Dell Products L.P.||Method of updating a computer system to a qualified state prior to installation of an operating system|
|US20060218246 *||26 May 2006||28 Sep 2006||Microsoft Corporation||Method and system for identifying and obtaining computer software from a remote computer|
|US20070038705 *||29 Jul 2005||15 Feb 2007||Microsoft Corporation||Trees of classifiers for detecting email spam|
|US20100050166 *||22 Aug 2008||25 Feb 2010||Inventec Corporation||Updating system and method of portable executable programs|
|US20110113417 *||25 Mar 2010||12 May 2011||Bank Of America Corporation||Network-Enhanced Control Of Software Updates Received Via Removable Computer-Readable Medium|
|US20110113418 *||25 Mar 2010||12 May 2011||Bank Of America Corporation||Cross-Updating Of Software Between Self-Service Financial Transaction Machines|
|US20130111458 *||2 May 2013||Research In Motion Limited||Method and system for on-demand patch generation and management|
|US20130247055 *||16 Mar 2012||19 Sep 2013||Mikael Berner||Automatic Execution of Actionable Tasks|
|US20140109079 *||30 Aug 2013||17 Apr 2014||William Cheng||Software uninstallation system, method and computer program product|
|US20140189675 *||27 Dec 2013||3 Jul 2014||William Cheng||Software uninstallation system, method and computer program product|
|International Classification||G06F9/44, G06F9/445|
|7 Sep 2001||AS||Assignment|
Owner name: MICROSOFT CORPORATION, WASHINGTON
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:FAWCETT, PHILIP E.;REEL/FRAME:012161/0062
Effective date: 19951120
|15 Jan 2015||AS||Assignment|
Owner name: MICROSOFT TECHNOLOGY LICENSING, LLC, WASHINGTON
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MICROSOFT CORPORATION;REEL/FRAME:034766/0001
Effective date: 20141014