Apparatus and method for scheduling of search for updates or downloads of a file

REFERENCE TO RELATED APPLICATIONS

[0001] The present application is a continuation-in-part of U.S. patent application Ser. No. 09/372,253, filed Aug. 11, 1999, and entitled “Apparatus and Method for Adaptive Fraud Screening for Electronic Commerce Transactions,” which is a continuation-in-part of provisional U.S. Patent Application Serial No. 60/110,952, filed Dec. 4, 1998, and entitled “Apparatus and Method for Providing Electronic Commerce,” both of which are incorporated herein by reference as if fully set forth.

[0002] The present application is related to the following applications, all of which are incorporated herein by reference as if fully set forth: United States Patent Application of Joel Ronning, Kelly Wical, and Marc Kukura, entitled “Apparatus and Method for Controlling Distribution of Files and File Updates,” and filed on even date herewith; United States Patent Application of Joel Ronning and Kelly Wical, entitled “Apparatus and Method for Secure Downloading of Files,” and filed on even date herewith; United States Patent Application of Joel Ronning and Kelly Wical, entitled “Cache Management for Dynamic Web Pages,” and filed on even date herewith; and United States Patent Application of Joel Ronning and Kelly Wical, entitled “Global Web Site Management,” and filed on even date herewith.

FIELD OF THE INVENTION

[0003] The present invention relates to an apparatus and method for controlling distribution of files and updates to files. automatically downloads files upon request by a user and can download a file in multiple portions by tracking an amount of a received portion of the file.

[0004] The method and apparatus include transmitting a request to download a file, the request including an identification of the file and an indication of starting point for transmission of the file. A serial transmission of digital information for the file is received beginning at the starting point, and the digital information is appended to a previously-received portion of the file, if present. The received digital information is also stored.

[0005] The agent can also search for updates to files by using application signatures to uniquely identify files stored on a user's machine and transmitting the application signatures to a server storing the updates. In addition, the agent uses a number of screens for displaying information to a user concerning the downloading of files and updates to files. The screens also permit the user to enter schedule information to control downloading of files and searching for updates to files.

BRIEF DESCRIPTION OF THE DRAWINGS

[0006]FIG. 1 is a block diagram of an environment for providing electronic commerce.

[0007]FIG. 2 is a block diagram of an electronic commerce system.

[0008]FIG. 3 is a block diagram of exemplary hardware components of an electronic commerce system.

[0009]FIG. 4 is a flow chart of processing for an electronic commerce system.

[0010]FIGS. 5<i>a </i>and <b>5</b><i>b </i>are a flow chart of a home screen routine for implementing an agent to manage distribution of digital information and file updates.

[0011]FIG. 6 is a flow chart of a downloads screen routine for the agent.

[0012]FIG. 7 is a flow chart of a downloads routine for distribution of digital information using the agent.

[0013]FIG. 8 is a flow chart of an updates screen routine for the agent.

[0014]FIGS. 9<i>a </i>and <b>9</b><i>b </i>are a flow chart of find updates routine for the agent to locate and download information concerning update to files.

[0015] FIGS. <b>10</b>-<b>24</b> are diagrams of exemplary screens supported by the routines shown in FIGS. <b>5</b>-<b>9</b> and used to implement an embodiment of an agent for distribution of digital information and file updates.

[0016]FIG. 10 is a diagram of a home screen.

[0017]FIG. 11 is a diagram of a news and deals screen.

[0018]FIG. 12 is a diagram of a shopping screen.

[0019]FIG. 13 is a diagram of a customer service screen.

[0020]FIG. 14 is a diagram of a privacy screen.

[0021]FIG. 15 is a diagram of a general settings screen.

[0022]FIG. 16 is a diagram of a tour screen.

[0023]FIG. 17 is a diagram of a downloads screen.

[0024]FIG. 18 is a diagram of an install screen.

[0025]FIG. 19 is a diagram of a schedule downloads screen.

[0026]FIG. 20 is a diagram of a download help screen.

[0027]FIG. 21A is a diagram of a download status screen.

[0028]FIG. 21B is a diagram of a continue download screen.

[0029]FIG. 22 is a diagram of an updates screen

[0030]FIG. 23 is a diagram of an updates help screen.

[0031]FIG. 24 is a diagram of an update status screen.

DETAILED DESCRIPTION

Overview

[0032] As shown in FIG. 1, an end user at computer <b>100</b> enters a particular client web site <b>102</b> through connection <b>101</b> in order to shop for products, which may include, but is not necessarily limited to, digital products. Digital products include any information capable of being represented in digital form; examples of digital products include, but are not limited to, the following: software applications; data, music, video, books, text, audio-visual information, multimedia information, graphical information, fonts, and artistic works.

[0033] The end user may view a page from the client's web site, for example, listing and describing various products. When the end user indicates a desire to purchase a product by, for example, selecting a purchase icon on the client's web page, the end user's connection <b>103</b> is transferred to a commerce network server providing the client's on-line web store <b>104</b>, and this typically occurs as a background process. The end user may make a secure purchase <b>105</b> through page <b>106</b> from a product library and, as represented by arrow <b>107</b>, the purchased product is delivered electronically over the network connection, physically such as by mail, or both electronically and physically.

[0034] The purchase typically involves the end user entering payment and related information, such as a credit card number and an associated name and address. In response, the commerce network server determines whether to accept the order and, if accepted, may provide a secure download of the purchased product to the end user's computer for digital products. Determining whether to accept or decline the order involves the use of accessing information concerning prior attempted purchases using information related to or associated with the information in the order, and determining from the related or associated information the likelihood that the order involves a fraudulent attempt to obtain products. Although only one computer <b>100</b> and web site <b>102</b> are shown, a commerce network server may provide multiple on-line web stores <b>104</b> and may interact with end users at multiple computers and multiple web sites.

Electronic Commerce System and Process

[0035]FIG. 2 is a block diagram of an electronic commerce system <b>200</b> illustrating interaction between an end user machine <b>201</b> and a server <b>205</b>, illustrating exemplary software modules, caches, and related databases. Server <b>205</b> may correspond with the commerce network server described above providing on-line web stores. As shown, end user machine <b>201</b> interacts through network <b>204</b>, such as the Internet or other type of network, with server <b>205</b>. End user machine <b>201</b> may also access a web page on an intermediate server and subsequently be transferred to server <b>205</b>. End user machine <b>201</b> may interact directly with server <b>205</b> or interact through an agent module <b>203</b>, which performs processing specific to a user at end user machine <b>201</b>. End user machine <b>201</b> transmits a request <b>228</b> or <b>229</b> to server <b>205</b> from agent module <b>203</b> or page <b>202</b>, possibly including a request for a particular web page, a request to purchase and download a digital product, or a request for a search for a particular product. Although only one end user machine <b>201</b> is shown, server <b>205</b> may interact via network <b>204</b> with multiple end user machines and multiple intermediate servers maintaining web sites accessed by users at the end user machines. Other examples of systems providing electronic commerce are disclosed in the following United States patents, all of which are incorporated herein by reference as if fully set forth: U.S. Pat. Nos. 5,907,617; 5,903,647; 5,887,060; 5,883,955; 5,883,954; and 5,870,543.

[0036] In server <b>205</b>, the request may be transmitted through a uniform resource locator (URL) spoofer module <b>206</b>, which performs initial processing of the URL. In particular, URL spoofer module <b>206</b> changes the URL so that if a user subsequently downloads a product, end user machine <b>201</b> by default saves the product under a file name associated with the product but gives no direct access to the physical location on the server. It may also misdirect the user in order to detect attempts to fraudulently obtain products. Alternatively, the request may be transmitted directly to a web server module <b>207</b>, which performs initial processing on the request.

[0037] A log in module <b>208</b> receives the request and records certain data associated with the request, such as the user's request, Internet Protocol (IP) address, date and time, and particular demographic information. The request is then transmitted to a security module <b>209</b>, which uses heuristics and other techniques in order to detect a person attempting to bypass particular steps of the process, or otherwise receive or access the products without providing payment.

[0038] A process request module <b>211</b> first checks a page/product cache <b>218</b> to determine if the requested web page has been previously requested or, if applicable, the relevant product has been previously requested. If so, process request module <b>211</b> accesses information in page/product cache <b>218</b> in order to avoid repeatedly generating the same information for the same or a similar request. If applicable, process request module <b>211</b> also checks a search cache <b>217</b> to determine if the requested search has been previously requested and, if so, it uses information in search cache <b>217</b> to generate particular output. A build cache module <b>212</b> within process request module <b>211</b>, if applicable, builds information for storage in either of the caches.

[0039] A fraud (payment) module <b>210</b>, typically within process request module <b>211</b>, performs processing necessary to conduct the payment transaction, including processing of credit card information. It also records payment-related information.

[0040] A build output module <b>213</b> next assembles information for the request. It first checks a graphical user interface (GUI) implementation cache <b>216</b> to determine if a requested web page has been previously constructed and provided. If so, it may use the information in GUI implementation cache <b>216</b> to avoid unnecessary repeated processing of the same information. If applicable, a build cache module <b>214</b> within build output module <b>213</b> creates information for storage in GUI implementation cache <b>216</b>.

[0041] A log completion module <b>215</b> performs final processing on the request. If the request is only for a web page or search, log completion module <b>215</b> transmits the web page or search information back to end user machine <b>201</b>. If end user machine <b>201</b> uses agent module <b>203</b>, log completion module <b>215</b> may transmit information to an agent transaction server <b>219</b>, which constructs and creates the web page based upon that information and transfers it back to agent module <b>203</b> for construction of the web page at page <b>202</b> on end user machine <b>201</b>.

[0042] If the request included a request for a product, log completion module <b>215</b> transmits the request to a download processor <b>224</b>, which checks with process request module <b>211</b> to verify the authenticity of the request and perform a security check If the request is valid, as determined by information transmitted back from process request module <b>211</b>, download processor <b>224</b> securely transmits the requested product from a product download database <b>225</b> to end user machine <b>201</b>. The transmitted product may be transmitted through agent transaction server <b>219</b> if end user machine <b>201</b> uses agent module <b>203</b>.

[0043] The following provides a description of each database shown in FIG. 2. A data warehouse database <b>221</b> provides log in information along with keys, which provides an index to associated information in a commerce database <b>223</b>. Commerce database <b>223</b> contains data tables storing information related to products and requests, such as a product table, order table, and other such tables. A summary database <b>220</b> provides information from the data warehouse database in summary form. Product download database <b>225</b> provides products in digital form for retrieval by the download processor. This configuration provides the advantage of storing the products without wrappers or associated passwords, and instead providing for a secure download of the products. Wrappers or associated passwords may still be used, if desired.

[0044] A site GUI/feature control database <b>226</b> and default GUI/feature control database <b>227</b> may be accessed by process request module <b>211</b> and build output module <b>213</b> for storage and retrieval of information related to web sites.

[0045] A credit card fraud database <b>222</b> stores credit card transaction information, including credit card processing history, and other information for adaptive fraud screening. Such information may thus be used in performing another security check. For example, the database may store a list of stolen credit card numbers.

[0046]FIG. 3 depicts an exemplary data processing system <b>300</b> with a computer <b>301</b> illustrating exemplary hardware components of end user machine <b>201</b>, server <b>205</b>, and an intermediate server, if used to transfer the end user's connection. Computer <b>301</b> includes a connection with a network <b>307</b> such as the Internet or other type of network, which may correspond with network <b>204</b>. Computer <b>301</b> typically includes a memory <b>302</b>, a secondary storage device <b>304</b>, a processor <b>305</b>, an input device <b>306</b>, a display device <b>303</b>, and an output device <b>308</b>.

[0047] Memory <b>302</b> may include random access memory (RAM) or similar types of memory, and it may store one or more applications <b>309</b> for execution by processor <b>305</b>. Applications <b>309</b> may correspond with the modules shown in FIG. 2. Secondary storage device <b>304</b> may include a hard disk drive, floppy disk drive, CD-ROM drive, or other types of non-volatile data storage, and it may correspond with the various databases shown in FIG. 2. Processor <b>305</b> may execute applications or programs stored in memory <b>302</b> or secondary storage <b>304</b>, or received from the Internet or other network <b>307</b>. Input device <b>306</b> may include any device for entering information into computer <b>301</b>, such as a keyboard, cursor-control device, or touch-screen. Display device <b>303</b> may include any type of device for presenting visual information such as, for example, a computer monitor or flat-screen display. Output device <b>308</b> may include any type of device for presenting a hard copy of information, such as a printer, and other types of output devices include speakers or any device for providing information in audio form.

[0048] Although computer <b>301</b> is depicted with various components, one skilled in the art will appreciate that this computer can contain additional or different components. In addition, although aspects of an implementation consistent with the present invention are described as being stored in memory, one skilled in the art will appreciate that these aspects can also be stored on or read from other types of computer program products or computer-readable media, such as secondary storage devices, including hard disks, floppy disks, or CD-ROM; a carrier wave from the Internet or other network; or other forms of RAM or. ROM. The computer-readable media may include instructions for controlling a computer system, such as computer <b>301</b>, to perform a particular method.

[0049]FIG. 4 illustrates high-level processing <b>400</b> through electronic commerce system <b>200</b>. In process <b>400</b>, web server module <b>207</b> receives a request from end user machine <b>201</b> (step <b>401</b>). Log-in module <b>208</b> processes the request to obtain log information (step <b>402</b>). Security module <b>209</b> performs a security check (step <b>403</b>). Process request module <b>211</b> checks page/product cache <b>218</b> (step <b>405</b>) and checks search cache <b>217</b>, if applicable (step <b>406</b>). Fraud module <b>210</b> performs payment-related functions and process request module <b>211</b> processes the request and uses build cache module <b>212</b> to build a cache, if applicable (step <b>407</b>). Build output module <b>213</b> checks GUI implementation cache <b>216</b> (step <b>408</b>), assembles information for responding to the request, and uses build cache module <b>214</b> to build a cache, if applicable (step <b>409</b>).

[0050] Log completion module <b>215</b> performs final processing of the request (step <b>410</b>), and it determines if the request is a purchase request (step <b>411</b>). If so, it transfers the request to download processor <b>224</b> (step <b>412</b>), which securely downloads the requested product and delivers it to the end user machine <b>201</b> (step <b>413</b>). If the request was not a purchase request as determined by step <b>411</b>, log completion module <b>215</b> delivers page and optional search information to end user machine <b>201</b> (step <b>414</b>).

Commerce System

[0051] This feature of electronic commerce system <b>200</b> involves providing a single transaction point for processing of electronic commerce, generally involving the series of modules shown in FIG. 2. Examples of the processing in this single transaction point include security, checking for fraud, on-line reporting, and processing orders. The benefits of providing such processing through a single transaction point typically include, for example, scalability, reliability of processing, simplicity of design by avoiding multiple disparate systems, and avoiding repeated processing.

Fraud Detection and Prevention

[0052] This feature of electronic commerce system <b>200</b> involves preventing fraud and ensuring security during electronic commerce transactions. An electronic commerce transaction involves a user electronically requesting purchase of a product and providing payment for the product. The user may receive the product electronically for digital products or may receive it by other means such as via mail service. The terms fraud and fraudulent refer to attempts by a user to obtain a product without providing proper payment, or otherwise not satisfying requirements for obtaining a product. For example, a user may attempt to use a stolen or false credit card number to obtain a product or attempt to tamper with the system so that the user obtains a product for less than the required price. As another example, certain information related to a user's order may tend to indicate that the user is likely to fail to provide payment, even if the credit card number used appears valid, and system <b>200</b> attempts to make that determination based on an analysis of the user's information and associated information.

[0053] The fraud detection and prevention may also involve preventing users or customers from having access to certain stored data such as credit card information and products. It involves preventing users from bypassing particular modules or processing in system <b>200</b>. Users typically interact with system <b>200</b> in a known manner for non-fraudulent transactions. Likewise, particular types of interaction tend to indicate that a user is attempting to circumvent system <b>200</b> and fraudulently obtain products. Therefore, system <b>200</b> analyzes a user's interaction, as well as a user's information submitted on an order typically using an order form and related information in a database, in order to determine a likelihood or probability that the user is engaging in attempted fraud during the transaction. That determination is used as a basis to either accept or decline the order.

[0054] The fraud detection and prevention features of system <b>200</b> generally include functions within the security and fraud (payment) modules <b>209</b> and <b>210</b>, as further explained below. System <b>200</b> may implement modules <b>209</b> and <b>210</b>, or a single module or any number of modules to implement the features, using software stored in memory <b>302</b> or secondary storage <b>304</b> for execution by processor <b>305</b>. Modules <b>209</b> and <b>210</b> may also be implemented using program products or a combination of software and specialized hardware components. In addition, the modules may be executed on multiple processors for processing a large number of transactions, if necessary or desired.

[0055] An exemplary implementation of modules <b>209</b> and <b>210</b> for fraud detection and prevention is disclosed in U.S. application Ser. No. 09/372,253, filed Aug. 11, 1999, and entitled “Apparatus and Method for Adaptive Fraud Screening for Electronic Commerce Transactions.”

Global Web Site Management

[0056] This feature of electronic commerce system <b>200</b> involves providing centralized management of host sites, managing all host sites through a central database. It may include, for example, extending a look and feel of a particular web site into another web site. For example, when an intermediate server transfers an end user's connection to a commerce network server, as described with respect to FIG. 1, the commerce network server may transmit a page having the same look and feel as the page on the intermediate server, thus providing an apparent seamless transition to the end user.

[0057] This feature also may include making local changes to a large number of managed web sites. Therefore, instead of making similar changes to each individual web site, system <b>200</b> may broadcast those particular changes and make the corresponding changes to the managed web sites. It thus provides an advantage, for example, of easily making changes to a large number of web sites. For example, it may automatically broadcast a few particular features every week to the managed web sites in order to regularly update the sites.

Security Area

[0058] This feature of electronic commerce system <b>200</b> provides for securely storing clients' products and providing a secure download process, typically without the use of wrappers or passwords. This feature generally involving the series of modules shown in FIG. 2. It includes a database type of security intended at least to simplify the purchase process for a user. A user typically need only enter a credit card number and in response receives a requested product.

Cache Management for Dynamic Web Pages

[0059] This feature of electronic commerce system <b>200</b> concerns a dynamic cache providing for a fast page response and dynamic pages, typically guaranteeing that pages contain current information. It generally involves caches <b>216</b>, <b>217</b> and <b>218</b> shown in FIG. 2, providing cache processing for three areas: product searching; GUI implementation (particular features on a web page); and static page building (a web page as a whole).

[0060] The complexity of product searching often affects speed of a response. Providing caching of information means that the same information need not be repeatedly retrieved from an external database and constructed into a responsive web page. Rather, the information may be cached locally and quickly retrieved in response to the same or a similar request. This feature maintains up-to-date information by knowing to create and destroy information interactively for the caches.

Intelligent Agent

[0061] An intelligent agent includes an application that resides locally on a client machine in order to perform processing specific to a user of the machine, generally involving agent module <b>203</b> and agent transaction server <b>219</b> shown in FIG. 2. It includes at least two aspects, a pull side and a push side. The pull side involves the agent obtaining information and knowing how to link to a server and provide the information to the user in a personal way, customized for that user. It shields the user from the order process, for example, in order to simplify it. The agent may also perform system management, for example, performing a background process that scans the user's system in order to manage licensed software, perform archival control, and perform other such processing.

[0062] The push side involves making special information available to the user through the agent. For example, if the user already ordered a particular product, the agent may inform the user of any bugs in the product, product upgrades, or related products. That information is “pushed” to the agent from the server. The server may provide initial filtering of information given to the agents, and the agents perform additional filtering in order to present the information in a specific way to the user.

[0063] Therefore, an agent manages distribution and download of files including digital products to a user's machine, as well as locating and downloading updates to files contained on the user's machine. The term “file” refers to any type of digital product. A file may include associated information concerning the file, such as a name and size, which is possibly useful for downloading purposes. Alternatively, a file may include only a digital product itself or a portion of a digital product.

[0064] The agent can thus assist a user in managing the downloading of particular digital information, as well as provide recommendations concerning updates to files on the user's machine. An embodiment consistent with the agent may be implemented in software or program products within agent module <b>203</b> in user machine <b>201</b>, and it may be included within agent modules on many particular end user machines interacting with server <b>205</b>. FIGS. <b>5</b>-<b>9</b> are flow charts of routines for implementing an agent in agent module <b>203</b>. The term “agent” refers to any software or other type of application for executing the functions in FIGS. <b>5</b>-<b>9</b>.

[0065] FIGS. <b>10</b>-<b>24</b> are diagrams of screens supported by the routines in FIGS. <b>5</b>-<b>9</b>. The term “screen” refers to any visual element or combinations of visual elements for displaying information; examples include, but are not limited to, user interfaces on a display device or information displayed in web pages or in windows on a display device. The screens may be formatted, for example, as web pages in HyperText Markup Language (HTML), or in any other suitable form for presentation on a display device depending upon applications used by users to interact with the system.

[0066] The screens include various sections, as explained below, to provide information or to receive information or commands. The term “section” with respect to screens refers to a particular portion of a screen, possibly including the entire screen. Sections are selected, for example, to enter information or commands or to retrieve information or access other screens. The selection may occur, for example, by using a cursor-control device to “click on” or “double click on” the section; alternatively, sections may be selected by entering a series of key strokes or in other ways such as through voice commands or use of a touch screen. In addition, although the screens shown in FIGS. <b>10</b>-<b>24</b> illustrate a particular arrangement and number of sections in each screen, other arrangements are possible and different numbers of sections in the screens may be used to accomplish the same or similar functions of displaying information and receiving information or commands. Also, the same section may be used for performing a number of functions, such as both displaying information and receiving a command.

[0067]FIGS. 5<i>a </i>and <b>5</b><i>b </i>are a flow chart of a home screen routine <b>500</b> for the agent. Routine <b>500</b> supports a home screen <b>700</b> shown in FIG. 10. Home screen <b>700</b> is a main screen shown to a user upon launching the agent. In routine <b>500</b>, the agent typically resides active as a background process on a user's machine (step <b>502</b>). By remaining active in the background, the agent may automatically execute certain functions, as scheduled by the user and further explained below. The user launches the agent, as determined by step <b>504</b>. The user may launch the agent in a number of ways such as, for example, selecting the agent from a start menu, executing a run command, or selecting the agent as represented by an icon in a system tray on the user's computer. If the user launches the agent, the agent displays home screen <b>700</b> (step <b>506</b>). The term “eBot” is a trademark of Digital River, Inc.

[0068] Home screen <b>700</b> includes a section <b>701</b> for use in providing information to the user and receiving information from the user. From home screen <b>700</b>, a user may select a function by selecting a particular section of home screen <b>700</b> shown in FIG. 10 (step <b>508</b>). Selection of home section <b>704</b> (step <b>510</b>) causes display of home screen <b>700</b> (step <b>530</b>). Selection of news and deals section <b>706</b> (step <b>512</b>) causes display of a news and deals screen <b>726</b> shown in FIG. 11 (step <b>532</b>). News and deals screen <b>726</b> illustrates an example of providing particular information in section 701 to users. News and deals screen 726 typically includes a section <b>727</b> by which a user may connect with a particular web site as related to the information within section <b>701</b>. The agent determines if the user selects section <b>727</b> (step <b>552</b>); if so, the agent launches a web browser on the user's machine and connects with the appropriate web site (step <b>554</b>). The agent may work with any type of web browser or other application executed by user machine <b>201</b> for network or Internet communication; examples of web browsers include the Netscape Navigator program and the Microsoft Internet Explorer program.

[0069] Selection in home screen <b>700</b> of a shopping section <b>708</b> (step <b>513</b>) causes display of a shopping screen <b>728</b> shown in FIG. 12 (step <b>534</b>). Shopping screen <b>728</b> permits display of information related to on-line shopping within section <b>701</b>. In addition, shopping screen <b>728</b> typically includes a connect section <b>730</b> by which a user may connect with a particular web site. From shopping screen <b>728</b>, the agent determines if the user selects connect section <b>730</b> (step <b>552</b>); if so, the agent launches the web browser and connects with the appropriate web site for on-line shopping (step <b>554</b>). The agent may store and associate connect section <b>730</b> with a URL or a uniform resource indicator (URI) for use in accessing a particular web site.

[0070] In home screen <b>700</b>, selection of a customer service section <b>710</b> (step <b>514</b>) causes display of a customer service screen <b>732</b> shown in FIG. 13 (step <b>536</b>). Customer service screen <b>732</b> provides for display of information to a user concerning operation of the agent. It typically includes a plurality of connect sections <b>734</b> for a selection by a user in order to connect with an appropriate web site in order to obtain customer service information. Therefore, from customer service screen <b>732</b> the agent determines if a user selects one of the connect sections <b>734</b> (step <b>552</b>); if so, the agent launches a web browser and connects with an appropriate web site for customer service information (step <b>554</b>).

[0071] From home screen <b>700</b>, selection of a privacy section <b>712</b> (step <b>516</b>) causes display of a privacy screen <b>736</b> shown in FIG. 14 (step <b>538</b>). Privacy screen <b>736</b> permits display of information to a user concerning the privacy of the information used by the agent for downloading information and providing for file updates. Privacy screen <b>736</b> also typically includes connect section <b>730</b> for connection with a web site to obtain information concerning privacy. From privacy screen <b>736</b> the agent determines if the user selects section <b>730</b> (step <b>552</b>), and if so, the agent launches a web browser and connects with an appropriate web site for providing privacy information to a user (step <b>554</b>).

[0072] From home screen <b>700</b>, selection of a general settings section <b>714</b> (step <b>518</b>) causes display of general settings screen <b>738</b> shown in FIG. 15 (step <b>540</b>). From general settings screen <b>738</b>, the agent receives and saves settings as entered by the user, including schedule information for finding updates (step <b>556</b>). In particular, general settings screen <b>738</b> includes a name section <b>739</b> in which a user may enter a name or other identifier. Selection of a section <b>740</b> permits the user to instruct the agent to search for updates on a periodic basis. In particular, the user may enter a number of days in section <b>741</b> by which they want the agent to automatically search for update to the files on the user's machine, as explained below. Using the information in section <b>741</b>, the agent automatically searches for updates to the files on the user's machine using a connection with server <b>205</b> based upon the days parameter in section <b>741</b>. Instead of using a number of days parameter, the agent may alternatively search for updates on a different periodic basis such as the first day of every month, or at a particular time and day each week or month.

[0073] Selection of a section <b>742</b> permits the user to specify a particular proxy server for downloads as entered in section <b>743</b> identifying a server and port for use with the web browser. Selection of a section <b>744</b> permits the user to specify automatic downloads such that the agent will automatically download a file without prompting the user for permission. Selection of a section <b>745</b> permits the user to instruct the agent to download from any web site on the Internet through server <b>205</b>. Selection of a section <b>746</b> permits the user to instruct that the agent software be activated upon system start-up of the user's machine.

[0074] From home screen <b>700</b>, a selection of a tour section <b>716</b> (step <b>520</b>) causes display of a tour screen <b>748</b> shown in FIG. 16 (step <b>542</b>). Tour screen <b>748</b> permits the agent to display information concerning its operation to the user. The user may typically obtain more information concerning operation of the agent by selecting connect section <b>730</b> in order to connect with an appropriate web site. Therefore, on tour screen <b>748</b> the agent determines if the user selects connect section <b>730</b> (step <b>552</b>); if so, the agent launches a web browser and connects with an appropriate web site in order to provide information concerning its operation (step <b>554</b>).

[0075] From home screen <b>700</b>, selection of a downloads section <b>718</b> (step <b>552</b>) causes execution of a downloads screen routine (step <b>554</b>), as further explained below. Selection of an updates section <b>720</b> in home screen <b>700</b> (step <b>524</b>) causes execution of an update screen routine (step <b>546</b>), as further explained below. A banner section <b>722</b> in home screen <b>700</b> permits the agent to display advertising or other information to a user. The user may select the banner in order to connect with a corresponding web site and obtain more information or shop on-line for products or services. Therefore, a selection of banner section <b>722</b> (step <b>526</b>) causes the agent to launch a web browser and connect with an appropriate web site as determined by network address information, such as a URL, associated with the banner (step <b>548</b>). If the user selects a close section <b>724</b> (step <b>528</b>), the agent closes home screen <b>700</b> (step <b>550</b>).

[0076] The agent may also be programmed or instructed by the user to automatically perform downloads of files and search for file updates using time parameter information. The agent monitors a current date and time, and compares it with schedule information to detect occurrence of a particular date and time (step <b>557</b>). The agent can monitor a current date and time by accessing an internal calendar and clock for user machine <b>201</b> on which it runs.

[0077] The agent determines if the user has scheduled a particular function (step <b>558</b>). That determination may be based upon comparing stored time parameter information as entered by a user with time information as determined by settings on a user's machine, as monitored in step <b>557</b>. If the user has scheduled a particular download for this time (step <b>560</b>), the agent executes a downloads routine based on the scheduled information (step <b>562</b>). If the user has scheduled an update for this time (step <b>564</b>), the agent executes a find updates routine based upon the scheduled information (step <b>566</b>). In order for the scheduled function to occur, the agent software typically must be active as a background process such that it is operational and the user's machine must maintain or provide for a network connection such that the agent may automatically perform the downloads and search for the file updates through the network connection without requiring further interaction by the user.

[0078]FIG. 6 is a flow chart of downloads screen routine <b>544</b> activated upon the user's selection of downloads section <b>718</b> in home screen <b>700</b>. Upon selection of downloads section <b>718</b>, the agent displays a downloads screen <b>750</b> shown in FIG. 17 (step <b>568</b>). Downloads screen <b>750</b> includes a number of sections for providing status information to a user concerning downloads <b>21</b>, and for a user to instruct the agent to perform certain operations concerning downloads. In routine <b>544</b>, a user selects a function within downloads screen <b>750</b> (step <b>570</b>), and the agent in response executes the selected function. Selection of a download section <b>752</b> causes execution of a downloads routine (step <b>584</b>), as further explained below. For the download information, downloads screen <b>750</b> provides a status section <b>764</b> having status information concerning files. In particular, a name column <b>766</b> provides a listing of file names, a status column <b>768</b> provides identification on the status of each file, a completion column <b>770</b> provides information concerning an amount of the file downloaded, if any, and a date section <b>772</b> provides date information concerning when the file was downloaded.

[0079] Status section <b>768</b>, as shown, provides various types of status information, such as the following: a ready status indicates that the selected file is ready to be downloaded; a downloaded status indicates that the selected file has been successfully downloaded; an in progress status indicates that the selected file is currently being downloaded with completion column <b>770</b> providing an indication of the percentage downloaded; a cancelled status indicates that a request to download the selected file has been cancelled. A details section <b>774</b> provides information concerning a particular selected file in section <b>764</b>. The highlighting indicates that a file in section <b>764</b> has been selected by a user, and the user may select the file in the same manner that a user selects a section.

[0080] In downloads screen <b>750</b>, selection of an open/install section <b>754</b> (step <b>574</b>) provides for the user to request installation of a particular file as selected in status section <b>764</b>. In response, the agent determines if the requested file has been downloaded (step <b>586</b>). If the file has not been downloaded, the agent may provide an error message to the user indicating that the file must first be downloaded before it can be installed (step <b>588</b>). If the file has been successfully downloaded, the agent installs the file (step <b>590</b>). Installation of the file typically requires any conventional installation permitting for execution of the file by user machine <b>201</b>. Prior to installation, the agent may display an install screen <b>776</b>, shown in FIG. 18, requesting that the user confirm whether to install the selected file or not through a selection of section <b>777</b> to confirm installation or selection of a section <b>778</b> cancel installation.

[0081] Selection of a scheduled section <b>756</b> in downloads screen <b>750</b> permits the user to schedule downloading of a file selected in status section <b>764</b>. Selection of schedule section <b>756</b> (step <b>576</b>) causes display of a schedule download screen <b>780</b> shown in FIG. 19 (step <b>592</b>). Using schedule download screen <b>780</b>, the agent receives and stores schedule information for the selected file for downloading a selected file (step <b>594</b>). Schedule information includes any type of date-based or time-based information for use in scheduling downloading of files or searching for file updates. For example, a user may enter a date in date section <b>781</b> and a time in time section <b>782</b> in order to schedule a download for the selected file. By selecting section <b>783</b> the user confirms the schedule and by selecting a section <b>784</b> the user cancels the function.

[0082] Selection of a remove section <b>758</b> in downloads screen <b>750</b> causes removal of a selected file in status section <b>764</b>. Upon selection of remove section <b>758</b> (step <b>577</b>), the agent removes the file indication from status section <b>764</b> if verified by the user (step <b>593</b>).

[0083] Selection of a help section <b>762</b> in downloads screen <b>750</b> (step <b>578</b>) causes display of a help screen <b>786</b> shown in FIG. 20 (step <b>596</b>). Downloads help screen <b>786</b> permits display of information concerning downloading of information to a user. It typically includes connect section <b>730</b> in order for the user to connect with the web site and obtain more help information. The agent determines if the user selects connect section <b>730</b> (step <b>598</b>); if so, the agent launches the web browser and connects with the appropriate web site to obtain more help information (step <b>600</b>).

[0084] In downloads screen <b>750</b>, selection of an updates section <b>720</b> (step <b>580</b>) causes execution of an updates screen routine (step <b>546</b>), as further explained below. Selection of home section <b>702</b> (step <b>582</b>) causes the agent to return to display home screen <b>700</b> and execute home screen routine <b>500</b>.

[0085]FIG. 7 is a flow chart of downloads routine <b>584</b> executed upon a user's selection of download section <b>752</b> in downloads screen <b>750</b> or based on schedule information as determined in steps <b>557</b> and <b>558</b>. Upon selection of download section <b>752</b>, the agent displays a download status screen <b>788</b> as shown in FIG. 21A. In downloads routine <b>584</b>, server <b>205</b> typically transmits a file list to the agent (step <b>606</b>). The file list provides for the identification of files in status section <b>764</b>. The list may be transmitted one time or repeatedly transmitted and updated. The user selects a file in the file list download (step <b>608</b>). Alternatively, the user may have preselected a file for downloading using schedule information. The agent sends a get file request to the server, including a URL and starting point of where to begin transmission of the file (step <b>610</b>). In this example, the starting point is a start byte; however, the starting point may include any type of indication of where to begin transmission of the file. The agent may optionally encrypt the request using any type of encryption routine.

[0086] If this was the first time the file is requested to be downloaded, the start byte will be zero. By tracking start bytes, the agent may maintain an indication of an amount of the file downloaded and therefore need only request to download an additional portion if the download is interrupted. In response to the get file request, server <b>205</b> downloads the requested file to the agent by serial transmission of digital information for the file using conventional Transmission Control Protocol/Internet Protocol (TCP/IP) transmission (step <b>612</b>). In this example, the serial transmission occurs through a stream of bytes for the file; however, it may occur through transmission of other forms of digital information such as, for example, bits, contiguous collections of bytes, or packets. The transmission may occur through any wireline or wireless network.

[0087] As the agent receives the file, it stores the file in a temporary folder on the user's machine such as “C:\temp\” on the hard disk drive for the user machine, and it uses a counter to track receives bytes. It also appends the bytes to a previously-received portion, if present in the temporary drive, for downloading the file in multiple portions (step <b>614</b>). It may store the bytes under a file name related to the file in order to detect a previously-received portion under the same name, if present. It may simultaneously store and append the bytes, or separately perform those steps. Also, instead of using the temporary drive, the agent may store the file in other drives or storage mediums.

[0088] Table 1 provides the levels of protocol used for the transmission. <tables id="TABLE-US-00001" num="1"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="1" colwidth="84PT" align="center" /><colspec colname="2" colwidth="133PT" align="left" /><thead><row><entry namest="1" nameend="2" align="center">TABLE 1</entry></row><row><entry /></row><row><entry namest="1" nameend="2" align="center" rowsep="1" /></row><row><entry>level</entry><entry>protocol</entry></row><row><entry namest="1" nameend="2" align="center" rowsep="1" /></row></thead><tbody valign="top"><row><entry>1</entry><entry>Agent Transfer Protocol (ATP)</entry></row><row><entry>2</entry><entry>encryption</entry></row><row><entry>3</entry><entry>TCP/IP</entry></row><row><entry namest="1" nameend="2" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

[0089] The ATP (level 1) includes the processing shown in downloads routine <b>584</b> (FIG. 7). The encryption protocol (level 2) provides for optional encryption of the transmitted bytes using various types of encryption such as triple Data Encryption Standard, referred to as 3DES. Level 3 includes the standard TCP/IP transmission of data over the Internet.

[0090] While the file is being downloaded, the agent displays and continually updates download status screen <b>788</b> (step <b>616</b>). Download status screen <b>788</b>, in particular, includes a file identification section <b>789</b> providing for identification of the file being downloaded, a status section <b>790</b> providing for an indication of the status of the file, whether a new download or a continued download, and a section <b>791</b> providing for additional status information such as a size of the file and an estimated remaining time to completion of the download. Section <b>791</b> also provides a visual indication of download in progress by continuously displaying the current number of bytes downloaded along with the total number to be downloaded. A section <b>792</b> provides for another visual indication of the download as in progress. In particular, it provides for an expanding status bar displaying essentially in realtime a relative indication of the amount that the file is downloaded. The status bar moves, for example, from left to right filling up section <b>792</b> until the file is completely downloaded. Selection of a cancel section <b>793</b> permits the user to cancel the download.

[0091] The agent may track a percentage or a relative amount downloaded by tracking received bytes and by knowing in advance a file size corresponding with the file. For example, conventional operating systems such as the Microsoft Windows program includes the ability to store file sizes in bytes associated with file names and potentially other information associated with the file such as a type of file and when the file was last modified. The agent continuously divides the received number of bytes by the file size in bytes to display the status bar and the percent downloaded.

[0092] Interruption of the transmission may occur in a number of ways such as, for example, through a user's selection of cancel section <b>793</b> in download status screen <b>788</b>, through any type of loss of the network connection, or through software or web browser failure. For example, transmission interruption may occur if a user turns off power to the user machine, if the user machine otherwise experiences a loss of power, if the user disconnects it from the network, if a server or router for network transmission fails, or through any other type of software or hardware failure.

[0093] If the transmission was interrupted (step <b>618</b>), the agent requests whether the user wishes to continue downloading (step <b>620</b>). For example, the agent may display a continue download screen <b>794</b> as shown in FIG. 21B. Continue download screen <b>794</b> includes a section <b>796</b> for the user to select in order to continue the download and a section <b>798</b> for the user to select in order to not continue the download at this time. If the agent continues to download the same file at another time, it may search for the same file name in the temporary folder, along with the associated start byte number, in order to download only the remaining portion and append it to the previously-received portion before the interruption occurred. Continue download screen <b>794</b> may alternatively include another option to cancel the download and delete the portion of the file already received.

[0094] If the user wants to continue transmission (step <b>622</b>), the agent sends another get file request including a URL of the file and start byte (step <b>610</b>). Since the agent tracks received bytes, it may now continue transmission by the next start byte following the last byte received. In particular, the agent sets the starting byte to the number of the last byte successfully received plus one. The download process then continues in steps <b>612</b>, <b>614</b>, and <b>616</b>, and the agent appends the remaining bytes to the previously-received portion of the file in the temporary folder, for example. If the downloading is not interrupted (step <b>618</b>), the agent monitors the download to determine if it receives an end of file (EOF) indication (step <b>626</b>); downloading continues while uninterrupted and until an EOF indication is received. The EOF may include any type of symbol, character, code, or other information providing an indication that t

[0095] Once the agent receives the EOF indication, it has successfully downloaded the file, and it requests whether the user wishes to install the file (step <b>628</b>). The agent may, for example, display installation screen <b>776</b> (FIG. 18) in order to request installation. If the user does not request installation, the agent stores the file on the desktop (step <b>632</b>), and the user may, at a later time, request installation. Otherwise, if installation is requested, the user installs the file by performing the necessary processing so that the file is executable by the user (step <b>630</b>).

[0096] Throughout the downloads routine, the agent saves and updates the status in download status section <b>764</b> in downloads screen <b>750</b> for the particular file being processed (step <b>624</b>). Updating the status provides for changing the status in status column <b>768</b> for the corresponding file in order to indicate its status, as well as providing an indication of the amount downloaded in completion column <b>770</b> and an indication of the date when last downloaded in date column <b>772</b>.

[0097]FIG. 8 is a flow chart of updates screen routine <b>546</b> executed upon a user's selection of updates section <b>720</b> in home screen <b>700</b> or downloads screen <b>750</b>. In routine <b>546</b>, the agent displays an updates screen <b>795</b>, shown in FIG. 22, upon a user's selection of updates section <b>720</b> (step <b>634</b>). Within updates screen <b>795</b>, the user selects a particular function (step <b>636</b>) and the agent in response executes the requested function. Updates screen <b>795</b> includes an update status section <b>802</b> providing for information concerning updates to particular files. In particular, a name column <b>803</b> provides an identification of a file name and, as shown indented, an indication of updates to the corresponding files. A price column <b>804</b> indicates a price for the particular update, and a type column <b>805</b> indicates that type of update such as an add-on. A details section <b>806</b> provides for information concerning the particular highlighted (selected) update in update status section <b>802</b>.

[0098] In updates screen routine <b>546</b>, selection of download section <b>797</b> (step <b>638</b>) causes execution of downloads routine <b>584</b> (FIG. 7) for the selected update (step <b>650</b>). A selected update is shown with highlighting, for example, and a user may select an update in the same manner as selecting a section. Selection of a find updates section <b>799</b> (step <b>640</b>) causes execution of a find updates routine as further explained below (step <b>652</b>). Selection of a remove section <b>801</b> (step <b>642</b>) causes the agent to remove a file or update selected by user, if the user verifies the removal (step <b>654</b>). Selection of a help section <b>807</b> (step <b>644</b>) causes display of a help screen <b>808</b> shown in FIG. 23 (step <b>656</b>). Help screen <b>808</b> provides for display of information to the user concerning finding updates for files. Help screen <b>808</b> specifically includes connect section <b>730</b> for a user to connect with an appropriate web site in order to obtain more help information. From help screen <b>808</b> the agent determines if the user selects connect section <b>730</b> (step <b>658</b>); if so, the agent launches the web browser and connects with the appropriate web site in order to obtain more help information (step <b>660</b>).

[0099] Selection of downloads section <b>718</b> in updates screen <b>795</b> (step <b>646</b>) causes the agent to execute downloads screen routine <b>544</b> (FIG. 6). Selection of home section <b>702</b> (step <b>648</b>) causes the agent to display home screen <b>700</b> and execute home screen routine <b>500</b> (FIGS. 5<i>a </i>and <b>5</b><i>b</i>).

[0100]FIGS. 9<i>a </i>and <b>9</b><i>b </i>are a flow chart of find updates routine <b>652</b> executed upon selection of find updates section <b>799</b> in updates screen <b>795</b> or based upon schedule information. Find updates routine <b>652</b> permits the agent through interaction with server <b>205</b> to automatically search for updates to particular files. The agent and server use application signatures in order to uniquely identify the files stored on a user system. By uniquely identifying those files, the server may determine whether updates exist for particular files. The use of application signatures is particularly useful when files have many different versions, as often exists for software applications, and the server must determine whether an update exists for a particular version of the file on a user machine. The term “application signature” refers to any information used to uniquely identify a file, an example of which is provided below.

[0101] In find updates routine <b>652</b>, the user selects find update section <b>799</b> (step <b>666</b>). The agent may include an end user license agreement for the user. If it has an end user agreement, the agent determines if this is the first time the user has requested to find updates (step <b>668</b>); if so, the agent displays an end user license agreement (step <b>670</b>) and determines if the user accepts the agreement (step <b>672</b>). The agent may be configured to only look for updates if the user has accepted the end user license agreement. Alternatively, the agent may operate without an end user license agreement or with varying versions of such agreement.

[0102] Based upon a user's selection of find updates section <b>799</b> or upon schedule information as determined in steps <b>557</b> and <b>558</b>, the agent searches for updates. The agent scans the hard disk drive on the user's machine in order to search for executable (.exe) files, dynamic link library (.dll) files, and driver (.drv) files, and the agent constructs a message including the directories and file names (step <b>674</b>). Executable files are identified by an “.exe” suffix, dynamic link library files are identified by a “.dll” suffix, and driver files are identified by a “.drv” suffix. The agent may alternatively look for other types of files; however, in the exemplary embodiment it generally searches for the executable, dynamic link library, and driver files. The agent returns a get file information message to server <b>205</b> with application signatures (step <b>676</b>).

[0103] In this example, the application signatures include a file name and corresponding size in bytes. Certain windows applications, for example, provide file name and size information, and the agent may obtain the file name and size information from such an application or generate the information itself. For certain files, different versions of the executable file may have the same size and, therefore, the executable file name plus size will not alone uniquely identify a particular version. In that case, the agent and server may also use corresponding dynamic link library file names plus associated sizes to construct the application signatures, and for that signature to match, both the executable file name and size, and dynamic link library file name and size, must match a stored signature. Driver files may be used in the application signature in the same manner, requiring a match between driver file names and sizes in addition to the matches between other types of file names and sizes. Therefore, an application signature in this example may include multiple file names and associated sizes for a particular file. Various types of files associated with a single file may be used to generate a unique application signature, depending upon application signatures already stored in the server database.

[0104] Server <b>205</b> uses the application signature to determine if updates exist for the corresponding files (step <b>678</b>). In particular, the server selects an application signature (step <b>680</b>) and determines if a match exists in an updates database by individually comparing the received file names and associated sizes with stored file names and associated sizes (step <b>682</b>). If a match exists, the server retrieves the corresponding update information (step <b>684</b>). Update information includes any type of indication of updates to files. The server may include links to a different database including the update information based upon the application signature. The server then determines if more application signatures exist to be processed (step <b>686</b>); if so, it returns to step <b>680</b> to process additional application signatures. After processing all of the application signatures, the server sends to the agent a file information-response with recommended updates from the retrieved update information (step <b>688</b>). The server also checks if the update recommendation is on the user's machine; if so, it skips the update.

[0105] The agent presents an indication of the recommended updates to the user, for example, as shown in update status section <b>802</b> in updates status screen <b>795</b> (step <b>689</b>). The agent determines if the user selects an update to be downloaded (step <b>690</b>). For example, user may select an update and then select download section <b>797</b> in order to download that update. If the user requests to download an update, the agent executes the download routine <b>584</b> (FIG. 7) to download the selected update (step <b>692</b>).

[0106] While the-agent executes processing to find the updates, it displays update information in an update status screen <b>810</b> shown in FIG. 24 (step <b>693</b>). In particular, update status screen <b>810</b> includes a section <b>811</b> for the agent to indicate status of preparing to search, a section <b>812</b> indicating that it is scanning the user system to obtain particular hardware information and file information, a section <b>813</b> to indicate that it is checking for updates with the server, and a section <b>814</b> indicating that it has received update information from the server and is compiling the results. In this example, the status of each section is indicated by a check-mark displayed in the corresponding box. A cancel section <b>815</b> permits the user to cancel the selected function.

[0107] In find updates routine <b>652</b>, steps <b>678</b>, <b>680</b>, <b>682</b>, <b>684</b>, <b>686</b>, and <b>688</b> are executed by the server, while the agent executes the other steps.

[0108] While the present invention has been described in connection with an exemplary embodiment, it will be understood that many modifications will be readily apparent to those skilled in the art, and this application is intended to cover any adaptations or variations thereof. For example, different labels for the various modules and databases, and various hardware embodiments for the servers and machines, may be used without departing from the scope of the invention. This invention should be limited only by the claims and equivalents thereof.