Computer network and connection method for connecting a personal computer and a content delivery system using a disk drive which includes a network address and server-contacting program

A computer network connects a personal computer system to a content delivery system for delivering digital content to the personal computer. The personal computer comprises a disk drive which includes a network address for the content delivery system and a server-contacting program. The disk drive comprises firmware installed during manufacturing of the drive which initiates execution of the server-contacting program to enable the network connection and facilitate delivery of content to a large number of personal computers.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The field of the invention relates to computer networks. More particularly, the field of the invention relates to a computer network which connects a content delivery server and a personal computer.

2.Background Information

A content data provider is a company that creates or transmits digital content, e.g., music, games, software utility, and advertisements. To be a successful content data provider it is necessary to obtain customer awareness with respect to the company itself, as well as to the content data provider's products.

To achieve this awareness, the content data provider may rely upon one of several known advertising mediums. Historically, there have been a number of advertising and distribution channels to promote digital content. For example, maintaining a website, direct mailing, and renting billboards are each alternative forms of advertisement that may be relied up to further promote brand recognition and other promote other advertising. Of recent advent, content delivery networks have been developed to deploy promotional materials. However, as is discussed below, each of these forms of advertisement has associated limitations and drawbacks.

With respect to direct mail campaigns, many users never open, use, or install promotional CD packages that are sent. Another problem with direct mail campaigns is that due to the lack of ability to obtain feedback, it is difficult to gauge the successfulness of such campaigns.

Problems with billboards include: (i) the can be costly; (ii) there is no guarantee that individuals will see the billboard when driving by; (iii) it is difficult to determine the number of individuals that viewed the advertisement; and (iv) self evidently, there is not an “interactive” experience between the user and the billboard.

Recently, content delivery networks have been developed to transport the content data of others. The providers of content delivery network license others the right to store promotional materials on the network. The content delivery network can include either a website on the Internet or, alternatively, a client program that runs on the user's personal computer and that periodically receives content data from a content data server. An example of latter is described in U.S. patent application Ser. No. 5,913,040 to Rakavy, et al.

However, one problem is that, depending on the type of network, consumers need to take an affirmative step of either downloading software to view information provided by the content delivery network, or, alternatively, navigate to the content delivery website that is provided in the network. Thus, as in maintaining a website, other forms of advertisement are required to promote consumer's user of the content delivery network.

Using the Internet, a content data provider can maintain a website whereby users can directly download and view advertising materials on their personal computer. However, one disadvantage of advertising on the Internet is that consumers need to know about the existence of the content data provider's website. In this regard, the content data provider needs to advertise its website or rely on search engines to provide the user with the Internet address of the user's company. Furthermore, to access the website the consumer needs to take an affirmative step and “navigate” to the web site. The term navigate is often referred to as the process of accessing a selected web page on the Internet. Disadvantageously, if the user never navigates to the content data provider's website, the content data provider is never given the opportunity to sell its products.

Thus, computer network providers are in need of an advertisement and distribution channel that allows them a guarantee that their content data can be received by a large number of personal computer users.

One embodiment of the invention comprises a method of establishing a connection between a personal computer system and a content delivery server. The personal computer system includes a computing subsystem and a disk drive. The method comprises providing a network address for the content delivery server and providing a server-contacting program. The network address and the server-contacting program are then stored in the disk drive. Firmware is installed in the disk drive to initiate execution of the server-contacting program after the disk drive is connected to the computing subsystem in the personal computer system. Upon execution, the server-contacting program uses the network address to connecting the personal computer system with the content delivery server.

Another embodiment of the invention comprises a computer network. The computer network comprises a content delivery server having a network address and a personal computer system comprising a computing subsystem and a disk drive. The disk drive comprises a network address, a server-contacting program, and a disk controller circuit. The disk controller circuit initiates execution of the server-contacting program after the disk drive is connected to the computing subsystem in the personal computer system. Upon execution, the server-contacting program uses the network address to connect the personal computer system with the content delivery server.

DETAILED DESCRIPTION OF THE EMBODIMENTS OF THE INVENTION

FIG. 1is a flowchart illustrating one embodiment of a content delivery process. Alternatively, selected steps of the flowchart may be omitted and others may be added. Furthermore, depending on the embodiment, the ordering of the steps may be varied.

Starting at a step100, a manufacturer manufactures a number of disk drives516(FIG.5). The process of manufacturing the disk drives516is described in further detail below with respect to FIG.2. However, in summary with respect to one embodiment of the manufacturing process, a first operating system604, a server contacting program608and a network address612are stored in a protected area628in the disk drives516(all shown in FIG.6). As is discussed further below, the network address612is a link or pointer to a server in the network. In one embodiment of the invention, the network address612is either a domain name, an URL, or an IP address. Furthermore, as part of the manufacturing process, firmware616on the disk drives516is adapted to detect when the disk drives516are connected in a personal computer system and to initiate the loading of the first operating system604. Upon being loaded, the first operating system604, or an installation program executing under the first operating system, installs the server-contacting program608on the personal computer system for use with a second operating system620.

For convenience of description, the following text will refer to a single disk drive516. However, it is to be appreciated that the same process may be performed with respect to manufacturing and using any number of disk drives. Furthermore, the disk drive516may be integrated with one of several personal computers502A-502M (FIG.5). A personal computer may take the form of a laptop, desktop, palmtop, or other configuration suitable for a single user. Although the disk drive516may be integrated with any of the personal computers502A-502M, for convenience of description, the following text assumes that the disk drive516will eventually be integrated with the personal computer502M.

Referring again toFIG. 1, at a step104, the disk drive516is shipped to the consumer via one or more distribution channels. The disk drive516may be sold to an original equipment manufacturer (OEM) integrator, a distributor, a retailer, or directly to a consumer. Before sale to the consumer, the OEM integrator, the distributor and the retailer, may load a second operating system620and one or more application programs624on the disk drive516. The second operating system620can include, for example: UNIX, LINUX, OS/2, PalmOS, Windows 98, Windows NT, and Windows CE. Since the first operating system604provides limited functionality, the second operating system620may be needed by the consumer to run the consumer's application programs.

Continuing to a step108, the disk drive516is installed in the personal computer502M. At the step108, the disk drive516is physically connected to an adapter connector that is associated with a computing subsystem518(FIG. 5) of the personal computer502M. The second operating system620is then configured for operation with the disk drive512. Furthermore, as will be described in further detail below with respect toFIG. 3, upon the occurrence of one or more selected conditions, the disk drive516initiates the execution of the first operating system604which then installs the server contacting program608for operation with the second operating system620. During the installation of the server-contacting program608, the user may be requested to provide user information, such as a name, an address, demographic information, and billing information.

Proceeding to a step112, a content delivery server512is configured to receive user information, if the user agrees, from the personal computer502M and to transmit content data to the personal computer502M once the disk drive516is installed (described above with respect to step108). At this step, the content delivery server512is connected to a network520. The network address612in the disk drive516identifies the content delivery server.

Next, at step116, the server contacting program608contacts the content delivery server512. Furthermore, at the step116, the content delivery server512stores the provided user information.

Moving to a step120, the content delivery server512delivers content data to the personal computer502M. The type of content data can vary greatly depending on the embodiment. Content data may include any type of digital file. For example, the content data can include: a content display program, a game, an entertainment program, a utility program, a product support program, entertainment data, advertisement data, music data, pictures or a movie. Furthermore, as non-limiting examples, the content data can be in any one of the following data formats: DHTML, .AVI, MPEG, QuickTime, a template, a static file, a Joint Photographic Experts Group (JPEG) file, an animated GIF, a Hypertext Markup Layout page, a .wav file, or a Macromedia flash file.

In one embodiment of the invention, the content data is displayed to the user during the boot process of the personal computer502M. As defined herein, a boot process includes executing one or more programs to configure a personal computer to a state wherein the personal computer can execute an application program specified by the user after booting. In another embodiment of the invention, the content data is displayed to the user during a shutdown phase of the personal computer502M. In yet another embodiment of the invention, the content data is displayed to the user during periods of low activity on the personal computer502M.

Preferably, the personal computer502M monitors the number of times that ads are displayed during boot and reports this number to a reporting server, e.g., the content delivery server. Advantageously, content data providers can accurately determine the number of times that the advertisements are viewed by the consumer.

FIG. 2illustrates in further detail certain steps that occur in step100of FIG.1. It is to be appreciated that depending on the embodiment, selected steps of the flowchart may be omitted and that others may be added. Furthermore, depending on the embodiment, the ordering of the steps may be varied.

Starting at a step200, a protected area628(FIG. 6) is created on the disk drive516. In one embodiment, the protected area628is written to and read from using proprietary commands that are provided by the manufacturer of the disk drive516.

Next, at a step204, the network address612for the content delivery server512is stored in the protected area628. The network address612can include any type of identifier for an accessible device or content data in a network. Depending on the embodiment, more than one network address may be stored in the protected area628.

Continuing to a step208, the first operating system604and the server-contacting program608are stored in the protected area628. Advantageously, since the first operating system604, the server contacting program608, and the network address612are stored in the protected area628in the disk drive516, they cannot be easily deleted from the disk drive516by subsequent integration in the personal computer, if at all. The first operating system604can be any off-the-shelf or proprietary operating system. As non-limiting examples, the first operating system604can be any one of the following operating systems, for example: UNIX, LINUX, and Disk Operating System (DOS).

Moving to a step212, firmware616is installed in the disk drive516. Firmware616is generally microprocessor executable code which is stored in the disk drive in non-volatile memory and executed by a disk drive microprocessor (not shown). In one embodiment of the invention, the firmware616resides in a disk controller circuit632. Disk controller circuit632comprises a microprocessor (not shown) suitable for executing firmware code616. Under certain conditions, the firmware616is adapted to initiate execution of the first operating system604instead of the second operating system620. In this regard, in one embodiment, of the invention, the firmware616is adapted to recognize when the computing subsystem518has requested a boot sector address stored on the disk drive516. The boot sector governs the behavior of the overall system during boot when control passes from POST Basic Input Output Services (BIOS) code. If the selected conditions, described below, are met and if the computing subsystem518has requested the boot sector address that is associated with the second operating system620, the firmware616substitutes a boot sector associated with the first operating system604for the requested sector. An exemplary is more fully described in U.S. application Ser. No. 09/507,121 titled “Disk Drive for Selectively Satisfying a Read Request From a Host Computer For A First Valid Data Block With A Second Valid Data Block”, filed on Feb. 17, 2000 and which is incorporated by reference herein in its entirety. In another embodiment, the firmware616may read the boot sector requested by the BIOS from disk and modify the code prior to transmitting the sector to the host computer system. The code modification may be accomplished by modifying data read from the sector using an algorithm or by “patching” the boot sector data with data stored elsewhere on the disk or embedded in the firmware code. In another embodiment, the firmware616may bypass reading the boot sector from the disk and substitute an entire sector stored in non-volatile memory or otherwise embedded in the firmware code. The process flow then returns to step104ofFIG. 1(discussed above).

FIG. 3is a flowchart illustrating one embodiment of a process for installing the server-contacting program608for operation with the second operating system620.FIG. 3illustrates in further detail certain steps that occur in steps108and116of FIG.1. It is to be appreciated that depending on the embodiment, selected steps of the flowchart may be omitted and that others may be added. Furthermore, depending on the embodiment, the ordering of the steps may be varied.

Starting at a step300, the user boots the personal computer502M. When the system is powered on, a BIOS program is read from a read only memory in the computing subsystem518. During its execution, the BIOS issues a plurality of read requests to the disk drive516. As part of the boot process, the BIOS requests the disk drive516to provide a predetermined sector, i.e., the boot sector, to begin the process for loading an operating system.

Next, at a step304, in response to each read request, the firmware616determines whether the read request is for the boot sector. During the step304, the firmware616attempts to activate the first operating system604at a point in time after the disk drive516is installed at the consumer's personal computer502M. If the process of installing the server-contacting program608is initiated prematurely, the first operating system604and/or server-contacting program608may be overwritten, or alternatively, notice of the presence of the server-contacting program608may be disadvantageously disclosed. For example, often after manufacture, OEM integrator install and test application programs on the disk drive516. If the process of installing the server contacting program608is initiated when the disk drive is in the possession of the OEM integrator, the OEM integrator may disadvantageously uninstall the server contacting program608.

If the read request is for the boot sector, the firmware616determines whether a selected condition has been met and delays initiating execution of the server-contacting program unless the selected conditions are met. As shown inFIG. 9, the process900of determining when the selected condition is satisfied can be any one or more of a number of alternatives. The selected conditions can include, among other things, counting902a number of bootloads of the computing subsystem518or counting906until the number of power cycles performed by the disk drive516has exceeded a predetermined threshold. If either number exceeds the threshold, it can be assumed by the firmware616that the disk drive516is in the consumer's possession and is not in the hands of the OEM integrator or other individual that is in the shipping channel of the disk drive516. This process is further described below with respect to FIG.7.

Another way of determining when the disk drive516has been installed with the personal computer502M is to adapt the firmware616to always initiate execution of the first operating system604. In one embodiment, a program is loaded by the first operating system604which reads (step910) a system clock from the personal computer502M. If a sufficient period of time has elapsed, it may be assumed that the disk drive516is in use by a consumer.

In another embodiment, firmware616may “scan” (step912) data sectors on the disk to determine whether a bootable system image or operating system has been installed on the disk to determine if the drive has progressed through the channel to a point where the server-contacting program may be initiated. By employing knowledge of conventional assignment of logical block addresses and a comparison of expected to recorded data, the firmware616may determine that a suitable operating environment exists for initiating execution of the server-contacting program. In one embodiment, the firmware616may comprise an embedded operating system such as Linux. When the selected condition is satisfied, the firmware616initiates (step914) execution of the server-contacting program.

Moving to a step308, the first operating system604, or alternatively, an installation program running under the first operating system604, installs the server-contacting program608for use with the user's personal computer502M. As part of the installation process, the user may, depending on the embodiment, be requested to register to use the server-contacting program608. In one embodiment of the invention, after being installed, the server contacting program608and the network address612each reside in the non-protected area of the disk drive632. After being installed for use with the second operating system620, the second operating system620automatically executes the server-contacting program608each time the second operating system620is executed.

Next, at a step312, the second operating system620is executed. In one embodiment, to accomplish this step, a soft reboot is issued and during the reboot the firmware616initiates the loading of the second operating system620. The second operating system620then executes the server-contacting program608. In one embodiment of the invention, an exemplary server contacting program608is described in U.S. application Ser. No. 5,913,040 to Rakavy, et al.

Continuing to a step316, the server contacting program608reads the network address612that is stored in the disk drive516. Moving to a step320, the server-contacting program608uses the network address to contact the content delivery server512(the device identified by the network address612). The process flow then returns step120ofFIG. 1(discussed above).

FIG. 4is a block diagram illustrating certain distribution channels for the disk drive516. After being manufactured, the disk drive516comprises the first operating system604, the server contacting program608, and the network address612. Preferably, a display content engine610may be included. Display content engine610provides executable code for displaying a variety of digital content such as AVI, JPEG, MPEG, MP3 and other media standards. After manufacture, the disk drive516may then be shipped to a PC OEM integrator (block404), to a distributor (block408), or to a retailer (block412). The distributor may further distribute the disk drive516to a VAR integrator or a second tier OEM (block416). The retailer may sell the disk drive516to a consumer who installs the disk drive516for use with the consumer's personal computer. A process of installing the disk drive516is described above with respect to FIG.3. After installation, the consumer is then able to use the installed disk drive516.

It is noted that the PC OEM integrator, the distributor, the retailer, the VAR integrator or second tier OEM, or the consumer may install the second operating system620and other application programs624on the disk drive516.

FIG. 5is a block is a block diagram illustrating an exemplary content delivery system500. The content delivery system comprises a content delivery server512that is operably connected to personal computers502A-502M via a network520. In one embodiment of the invention, the content delivery server512comprises a plurality of geographic servers each having a unique IP address and having a common domain name. The content delivery server512is operably connected to a content preprarer514which formats content data from the content provider800for use by the content delivery server512. The operation of the content preparer514is described below in further detail with respect to FIG.8.

The personal computers502A-502M each have a system unit506, a display device508, and an input device510. The system unit506comprises a disk drive516, a computing subsystem518, and a display generator522. In one embodiment, the computing subsystem518communicates with the disk drive516via a disk drive interface. The disk drive interface can be any standard or propriety storage interface. For example, the disk drive interface can be an Intelligent Drive Electronics (IDE) or AT Attachment (ATA) interface.

The computing subsystem518may include, among other elements, a processor, random access memory (RAM), read only memory (ROM), a BIOS stored in the ROM, and a system clock. The processor, may be one or more conventional general purpose microprocessors such as a Pentium® processor, a MIPS® processor, a Power PC® processor, or an ALPHA® processor. The network520may include any type of electronically connected group of computers including, for instance, the following networks: Internet, Intranet, Local Area Networks (LAN) or Wide Area Networks (WAN). In addition, the connectivity to the network may be, for example, remote modem, Ethernet (IEEE 802.3), Token Ring (IEEE 802.5), Fiber Distributed Datalink Interface (FDDI) or Asynchronous Transfer Mode (ATM). As used herein, an Internet includes network variations such as public internet, a private internet, a secure internet, a private network, a public network, a value-added network, an intranet, and the like. The network520may include multiple network technologies including both high and low bandwidth connections. The network520may include non-persistent connections that are only available at intervals, e.g., dial up telephone lines, and may also include persistent connections.

The input device510may be a keyboard, rollerball, pen and stylus, mouse, or voice recognition system. The input device510may also be a touch screen associated with the display device508. The user may respond to prompts on the display by touching the screen. Textual or graphic information may be entered by the user through the input device510.

FIG. 6is a representational block diagram illustrating certain elements of the disk drive516. The disk drive516comprises a disk controller circuit632and a storage area636. The disk controller circuit632comprises conventional disk controller components (not shown) such as a read channel device, formatter/controller, host interface logic and buffer controller as well as a microprocessor suitable for executing firmware616that is used to initiate the installation of the server contacting program608for use with the second operating system620. Suitably, an ST10microprocessor from ST microelectronics or an Intel x86 family microprocessor can be used although other equivalent devices or “cores” are available for integration in the disk controller circuitry. It is noted that the process of installing the server-contacting program608is described above with respect to FIG.3.

The storage area636comprises a protected area628and a non-protected area632. During manufacture, the first operating system604, the server-contacting program608, and the network address612are stored in the protected area628. After manufacture, the second operating system620and the application program624may be stored by an OEM or the consumer in the non-protected area632. In one embodiment, the protected area may be implemented by partitioning the disk into two sets of addressable locations—a “protected set” and a “user accessible” set. A “protected” set of addressable locations is addressable only by sending commands or command protocols that are proprietary to the disk drive manufacturer. Data in the protected area may then only be accessed by the firmware or by a host executable program that is entrusted with knowledge of the proprietary commands. The user accessible area is available using standard access methods recognized by the disk drive such as ATA or SCSI standards. In another embodiment, the protected area may be created using standard ATA commands such as SET MAX and READ MAX which allow an area of the drive to be hidden from the host operating system. Other suitable protection may be employed to ensure that the programs in the protected area survive post manufacturing distribution channels.

FIG. 7is a flowchart illustrating in further detail certain steps of the installation process of FIG.3. It is to be appreciated that depending on the embodiment, selected steps of the flowchart may be omitted and that others may be added. Furthermore, depending on the embodiment, the ordering of the steps may be varied.

Starting at step708, upon being accessed, the firmware616determines whether operating system substitution is disabled. The process of determining whether the operating system substitution is disabled is described above in further detail with respect to the description of step304ofFIG. 3, i.e., determining whether the selected conditions have been met. If substitution is disabled, the process flow proceeds to a step728, wherein the firmware616performs the normal boot sequence and initiates the loading of the second operating system620.

Referring again to step708, if substitution is not disabled, the process flow proceeds to a step712, wherein the firmware606reads the master boot record (conventionally the first logical block address) that is stored in the disk drive516.

Next at a step716, the firmware616determines whether the disk drive516contains a second operating system620that is compatible for use with the server contacting program608. In one embodiment of the invention, to make this determination, the firmware616performs pattern matching of expected sequences in the master boot record. Depending on the embodiment, the boot record may contain: jump instructions to other routines, a version number of the operating system, a boot signature, or a magic number. By matching the values of these fields to expected values that are stored either in the firmware616or in the protected area628, the firmware616determines whether the second operating620that was installed by the user or other party is supported for use with the server contacting program608. In such event that the second operating system620is unknown and is not compatible for use with the server-contacting program608, the process proceeds to the step728.

Referring again to the step716, if it is determined that the disk drive516contains a second operating system620that is compatible for use with server contacting program608, the process proceeds to a step720, wherein the firmware616determines whether the disk drive516is in a supported embodiment of system unit506. At this step, the firmware616determines whether the system unit506is compatible for use with the first operating system604and the server-contacting program608. In one embodiment of the invention, at this step, the firmware616analyzes the BIOS calls to the disk drive516to see if sequence corresponds to an expected pattern. If the BIOS calls of the computing system518conform to the expected pattern, the firmware616assumes that the system unit506is compatible for use with the first operating system604and the server contacting program616.

If the disk drive516is in a supported embodiment of system unit506, the process flow proceeds to a step732wherein the firmware616substitutes the boot record for the first operating system604with the boot record of the second operating system620. This substitution initiates the loading of the first operating system604.

Next, at a step736, the first operating system604, or an installation program executing under the first operating system604, copies the server contacting program608and the network address612from the protected area628into the non-protected area632.

Continuing to a step740, the first operating system604, or an installation program executing under the first operating system604, modifies a system registry of the second operating system620to include a reference to the server contacting program. The system registry identifies application programs that should be automatically executed by the second operating system620after the second operating system620is executed.

Proceeding to a step744, the firmware616disables substitution for subsequent booting of the second operating system620. Next, at a step748, the first operating system604, or alternatively, an installation program executing under the first operating system604, issues a soft boot, thereby initiating the execution of the second operating system120and, subsequently, the server contacting program608.

FIG. 8is a block diagram illustrating in further detail certain components of one embodiment of the content preparer514of FIG.5. As is shown inFIG. 8, the content preparer5142comprises a content repository804, a content database808, a publishing module812, a publishing database816, and a packaging module820.

A content provider800can submit content data to the content preparer514via an on-line submission process that uses a web interface. As part of the submission process, a content provider800submits content data and meta-data characterizing the content data to the content preparer514. The content data is stored in the content repository804. The meta-data is stored in the content database808. Periodically, a publishing module812extracts the meta-data from the content database804and the content from the content repository804and formats the material for distribution to the personal computer502M. The reformatted data content is stored in a publishing database816. Upon the occurrence of selected conditions, the packaging module820accesses the publishing database to determine which materials should be published and delivers the reformatted data content to the personal computer502M.

Advantageously, the present invention allows disk drive manufacturers to provide content delivery software to users. Since the first operating system604, the server contacting program608, and the network address612are stored in a protected area628, these files cannot be easily deleted by other entities in the distribution channels. Furthermore, by including the server-contacting program608with each manufactured disk drive516, the server-contacting program608is received by large numbers of personal computer users.