Technique for installing software by producing an access code and installation key

This application is a continuation (and claims the benefit of priority under 35 USC 120) of U.S. application Ser. No. 09/695,570, filed Oct. 24, 2000 (now U.S. Pat. No. 6,754,823). The disclosure of the prior application is considered part of (and is incorporated by reference in) the disclosure of this application.

BACKGROUND

This invention is directed to techniques to distribute software and prevent its unauthorized transfer.

It is desirable to distribute software electronically and still license it in some manner. Traditionally there were two ways of doing this licensing. One was shipping a CD with a software that required a license key. All CD's for a given product would have the same software, except for the license key that was required. This is a common way of distributing software for desktop applications. A second mechanism has a licensing software library built into the software. Both mechanisms are often used to down load software from the Internet.

One approach is a product Flex1M offered by Globetrotter. With this product a distributor buys the software, bundles the software with application software, and uses the bundled mechanism for generating keys.

SUMMARY

According to an aspect of the present invention, a method of downloading software over a network includes downloading the software and installing. Installing the software includes generating an installation key by using a random number generated from a seed that is the value of a client system internal clock at the exact moment in time to the millisecond at which the software installation program was run on the client, and producing an access code by combining the installation key and user name and performing a modulo operation on the result.

According to an additional aspect of the present invention, a computer program product residing on a computer readable medium for installing downloaded software on a client system over a network, includes instructions to cause a computer to generate an access key by receiving an installation key produced using a random number generated from a seed that is the value of a client system internal clock at the exact moment in time to the millisecond at which a software installation program was run on the client produce the access code by modulo combining the installation key and user name received by the client system.

One or more of the following advantages are provided by one or more aspects of the invention.

The invention obviates the need to ship software on a CD, allowing for a purely electronic distribution method. The invention also avoids the complexity of licensing libraries built into the software. The invention delivers software that requires a key that can only work on one computer.

BRIEF DESCRIPTION OF THE DRAWINGS

<figref idref="DRAWINGS">FIG. 1</figref> is a block diagram of networked systems.

<figref idref="DRAWINGS">FIG. 2</figref> is a block diagram of a server in the system of <figref idref="DRAWINGS">FIG. 1</figref>.

<figref idref="DRAWINGS">FIGS. 3A and 3B</figref> are flow charts of processes in the server of <figref idref="DRAWINGS">FIG. 2</figref>.

<figref idref="DRAWINGS">FIG. 4</figref> is a flow chart.

DESCRIPTION

Referring to <figref idref="DRAWINGS">FIG. 1</figref>, a networked system <b>10</b> is shown for delivery of software over, e.g., the Internet. The networked system <b>10</b> includes a client system <b>12</b> connected to a server <b>14</b>, via a network, e.g., the Internet <b>18</b>. The networked system <b>10</b> is implemented as a Web-style system that is used to facilitate communications between users at client computers such as client system <b>12</b> and the server <b>14</b> over the network <b>18</b>. In a Web implementation, the network <b>18</b> can be the “Internet” and the server <b>14</b> a Web server. Private networks can also be used.

More particularly, a user at client system <b>12</b> surfs via a Web browser <b>20</b>, to the Web server <b>14</b>. At the web server <b>14</b> the client can download software. In some implementations, the software can be an application program whereas in other implementations the software can be a program such as a screen saver. In addition the software can be offered with basic features for one price, e.g., freely distributed, or can be distributed with additional optional features by having the user pay for the features with a credit card.

The Web browser <b>20</b> renders display output in the form of hypertext markup language (HTML) pages. The Web browser <b>20</b> may be any commercially available browser, such as Microsoft Internet Explorer or Netscape Navigator.

Referring to <figref idref="DRAWINGS">FIG. 2</figref>, processes that run on the server <b>14</b> are shown. The server <b>14</b> executes a server process <b>30</b>. The server <b>14</b> can include a web server process, which among other functions produces web pages <b>32</b>, as well as a server that executes requests for client systems. The server <b>14</b> stores information organized into distributed web pages. For example, the pages are stored as information encoded into HTML or other techniques. The manner in which the HTML and equivalent pages are produced is well known and therefore not discussed herein. The server <b>14</b> also stores the software <b>34</b> that is made available for distribution, via the Internet. The software <b>34</b> includes basic features that can be supplied for free to a user as well as features that are not activated at download unless or until a fee is paid for the additional features. The features are unlocked by an access key <b>36</b> that also makes the software fixed to one client system <b>12</b>.

Referring to <figref idref="DRAWINGS">FIG. 3A</figref>, the server <b>14</b> delivers an executable of the software <b>34</b> to the client system <b>12</b> with certain features turned off. The user freely downloads this basic version of the executable from the server <b>14</b>. That executable runs in “basic mode.” To access premium features, which are turned off, the user enters an access key <b>36</b> (<figref idref="DRAWINGS">FIG. 2</figref>) through a dialog box that can pop up under any of a number of circumstances, e.g., trying to access a premium feature, as a reminder to upgrade or as an invitation to upgrade. The access key <b>36</b> is produced from information supplied by the user after or as part of upgrading the product, as described below.

When the user downloads the software <b>42</b> and runs the installation <b>44</b>, the installation generates <b>46</b> an installation key, which is a piece of information that will be used to generate the access key <b>36</b>. Another piece of information is the user name under which operating system registered on the client system <b>12</b>. For example, with the Windows based operating systems, when a user installs Windows 2000®, (Microsoft) Windows asks for an installation name. The name is stored inside the windows registry as the so called registered owner. This feature is available on Windows 95®, 98®, NT®, and so forth. The registered name stays on the client system <b>12</b> until the operating system is changed.

The installation key is an N digit key, e.g., 12 to 16 characters that is randomly generated. The mechanism that is used to generate the N digit key is a random number generator. As known, a random number generator is only as random as the seed used to generate it. The seed used in the preferred embodiment is the value of the client system internal clock at the exact moment in time to the millisecond at which the software installation program was run on the client. If two users downloaded the software and ran the installation program at the exact moment in time (to the millisecond) they would get the same installation key. However this is highly unlikely. However, since the names on the system, i.e., the registered owner, are likely different the key that is generated is likewise different.

Referring to <figref idref="DRAWINGS">FIG. 3B</figref>, a user desires to upgrade <b>60</b> to the premium features. During upgrade <b>60</b>, the user can be prompted by a dialog box to enter the access code. Initially, the user does not have the access code and instead can select an option to upgrade the basic software. The program connects the user to the server <b>14</b>. The program embeds the installation key and the user name in the information that is sent to the server, e.g., website by the user.

As part of the upgrade process the user is prompted to fill in information <b>64</b>, via web pages that are delivered from the server. The information includes name, e-mail address, address, demographics, and so forth, items that the distributor of the software would want for marketing etc, to be stored in a database (not shown). When the user comes to the site, the user fills in the information and supplies a credit card number for a credit card transaction. Once the distributor receives acknowledgment of the transaction <b>66</b>. The server <b>14</b> receives the information from the client <b>12</b>, e.g., installation key and user name, and based on the information generates <b>68</b> the access code. The access code is generated <b>68</b> based on the algorithm described below and supplied <b>70</b> to the user.

Referring now to <figref idref="DRAWINGS">FIG. 4</figref>, the installation key has 16 digits, the user name could have any number of digits. The process <b>68</b> (<figref idref="DRAWINGS">FIG. 3B</figref>) to produce the access key goes through each digit and adds <b>82</b> the installation key and the user name digit by digit. In this implementation the installation key is always 16 digits and since the user name can be any number, the registered user name is expanded (or shrunk) to make the length of the registered user be the same as the length of the installation key, e.g., 16 digits. That is, if the registered user length is greater than 16 digits, everything after the 16th digit is simply discarded. Conversely, if the registered user length is less than 16 digits, the string is recycled.

For example, if the registered user is “Fred Smith”. This string is expanded to “Fred SmithFred S” (16 digits including spaces). With the two strings (the installation key &amp; the registered user), which are both 16 digits, the algorithm adds the two strings, digit by digit. For example, given an installation code of <ul id="ul0001" list-style="none"><li id="ul0001-0001" num="0000"><ul id="ul0002" list-style="none"><li id="ul0002-0001" num="0024">abcdefghijklmnop</li></ul></li></ul>

and a registered user of “Fred Flintstone”, the algorithm adds each digit (“a”+“F”; “b”+“r”; “c”+“e”; “d”+“d”; and so on . . . ) to get an array of numbers. The array of numbers is 16 digits in length. Each number in the array is converted back to a letter by applying 84 mathematical “modulo” operations. In this case, (number) MODULO 48.

For example, if the registered user is “Fred Smith”. This string is expanded to “Fred SmithFred S” (16 digits including spaces). With the two strings (the installation key &amp; the registered user), which are both 16 digits, the algorithm adds the two strings, digit by digit. For example, given an installation code of <ul id="ul0003" list-style="none"><li id="ul0003-0001" num="0000"><ul id="ul0004" list-style="none"><li id="ul0004-0001" num="0027">abcdefghijklmnop <br /> and a registered user of “Fred Flintstone”, the algorithm adds each digit (“a”+“F”; “b”+“r”; “c”+“e”; “d”+“d”; and so on . . . ) to get an array of numbers. The array of numbers is 16 digits in length. Each number in the array is converted back to a letter by applying mathematical “modulo” operations. In this case, (number) MODULO 48, since 48 is the ascii representation of the letter “a.” </li></ul></li></ul>

The upgrade process <b>60</b> generates the access key <b>68</b> and sends <b>70</b> the access key back to the person via two methods. One method used to return the key to the user is to display the key in the Web browser so that the user can cut and paste it back into the dialog box that was opened when the user initially decided to upgrade. The distributor will also send an e-mail to the e-mail address supplied by the user. The e-mail will include the key that is placed in the Windows registry, or elsewhere.

In order to execute the software, the software retrieves the name of the registered owner and the generated installation code, which are stored on the client system, e.g., in the Windows registry or elsewhere, and produces the access key, which is compared to the access key entered by the user during the upgrade process. If the access codes are the same, the software executes. If they are not the same, the software does not execute, or alternatively the software can execute only in basic mode without the premium features, or a user can be prompted to upgrade.

Thus, this process combines the user ID or other identifier, e.g., a serial number of a processor or a hard drive with a customized installation key to lock the downloaded software to a particular machine.

Other embodiments are within the scope of the appended claims.