Patent Grant
7506144
This disclosure relates to display of dynamic content in a pre-boot environment.
Internet cafés that provide public access to the Internet are popular, especially in Asian countries, with thousands of Internet cafés providing access to the Internet through millions of computers. For example, China has more than 130,000 Internet cafes with over 6 million computers. Typically, the customers of Internet cafés cannot afford a personal computer. The customer pays a fee to use a computer in the Internet café.
To defray the cost of purchasing the computers to provide access to the Internet and thus reduce the fee paid by customers, the owners of Internet cafés typically provide fee-based advertising services. These advertisements are delivered through the use of pop-ups during run-time while the customer is accessing the Internet. However, the advertisements use run-time resources and are annoying to customers because they interrupt the customer's use of the Internet and they continue to be displayed until they are terminated by the user.
Features of embodiments of the claimed subject matter will become apparent as the following detailed description proceeds, and upon reference to the drawings, in which like numerals depict like parts, and in which:
Although the following Detailed Description will proceed with reference being made to illustrative embodiments of the claimed subject matter, many alternatives, modifications, and variations thereof will be apparent to those skilled in the art. Accordingly, it is intended that the claimed subject matter be viewed broadly, and be defined only as set forth in the accompanying claims.
According to an embodiment of the invention, dynamic content such as a screen image may be retrieved over a communication network and displayed for a selectable time period prior to booting the operating system. In an embodiment the screen image is an advertisement that is displayed on a client system in an Internet café. By displaying the advertisement prior to booting the operating system, the advertising time period is limited so that it does not annoy the user. Also, the advertisement is displayed prior to run-time while the user cannot use the computer system. Furthermore, the user does not have to terminate the advertisement because it is automatically terminated after the selected time period by the process of booting the operating system.
In an embodiment, each client system 108 has firmware stored in non-volatile memory and one or more operating systems stored in a secondary storage device such as a disk drive. The firmware performs initialization functions to allow the client system 108 to access the communications network 106. After a client system 108 has booted an operating system, the server 102 may download applications to client systems over the communications network.
A version of EFI is described in “Extensible Firmware Interface Specification”, Version. 1.10, Dec. 1, 2002 available at www.intel.com/technology/efi. The hardware layer is the lowest layer of the framework. In an embodiment, the hardware layer may include a CPU module 308 and a chipset module 310 that provide the functionality of the client system 108 shown in
Boot refers to the process of starting or resetting a computer by turning the power on, by pressing a reset button on the computer, or by issuing a software command to restart. The computer executes the software that loads and starts the operating system and prepares the operating system for use.
The EFI framework includes two main parts, the Pre-EFI (PEI) phase 306 and the Driver Execution Environment (DXE) phase 304, that operate sequentially. The Pre-EFI (PEI) phase discovers and initializes memory. The Driver Execution Environment (DXE) initializes other components in the client system and provides support for EFI drivers 302. Together, the PEI phase 306, the DXE phase 304 and the EFI drivers 302 provide a standard environment for booting an operating system and running pre-boot applications. Code executed during the PEI phase 306 and DXE phase 304 may be stored in nonvolatile memory along with drivers to access storage devices that store EFI drivers 302.
An EFI driver 302 is a modular piece of code that runs during the DXE phase. EFI drivers may manage devices in the client system 108 or provide services for the pre-boot environment. The EFI drivers are single-threaded and provide basic support for a console and network support for the pre-boot environment, that is, support to boot the operating system and manage the client system 108 in the pre-boot environment. The minimum support includes support for a control unit, such as a terminal (console), through which a user communicates with a computer. The console includes an input device such as a keyboard and an output device such as a display. The console may provide Cathode Ray Tube (CRT)-terminal like text support or graphics support on a Video Graphics Array (VGA) or Universal Graphics Adapter (UGA) device. Other EFI drivers for security, wireless and audio drivers may also be provided.
During the security (SEC) phase which begins with power on, the first opcode that will be executed in the client system is inspected to determine if the firmware has been tampered with.
During the pre-EFI initialization environment (PEI) phase, memory in the platform is discovered and a resource map is prepared for the DXE phase.
During the driver execution environment (DXE) phase, the boot manger and EFI drivers are loaded. The DXE phase provides a set of boot services, runtime services and DXE services. The DXE dispatcher is responsible for discovering and executing DXE drivers and EFI drivers. These drivers may be executed in a predefined order. The EFI drivers may comply with the EFI Version 1.10 driver model available at www.intel.com/technology/efi. The boot manager determines what operating system is to be loaded and the required boot devices. All of the EFI drivers may be loaded or just those that are needed for the boot operation. Boot services provide interfaces for devices and system functionality that can be used during boot time.
After the EFI drivers for the network, console and a billboard service driver 400 have been initialized, the client system 108 is ready to receive content sent from the server 102 over the communications network 106 and to display this content on the display of the console. The content to be displayed may be include text, graphics and video, that is, any content that is typically provided through a world wide web (www) page accessible over the Internet. In an embodiment, in addition to content to be displayed, the downloaded content may also include audio that includes speech and music. The receipt of the content to be displayed and the display of the received content for a controllable time period may be handled by the billboard service driver 400 which will be described in greater detail later in conjunction with
After the time period for displaying the screen image on the display has expired, a boot dispatcher 402 selects an operating system to boot during the boot device selection phase (BDS). The BDS phase locates and loads applications that execute in the pre-boot environment. For example, the applications may include an operating system boot loader or extended pre-boot services such as setup configuration, extended diagnostics, flash update support and operating system boot code.
At the start of this phase, the operating system takes control of the display on the console device and typically blanks the display by resetting a display buffer storing the screen image.
The Transient System Load (TSL) phase allows service interfaces to be available to operating system loaders before the platform is taken over by the operating system kernel. During the transient system load (TSL) phase, the operating system is booted by the operating system boot loader.
The Runtime (RT) phase provides a means to have EFI drivers present during operating system execution to support the operating system. During run-time, the final operating system environment is running and applications can be executed. The client system remains in the runtime phase until a shutdown is detected.
The AfterLife (AL) phase, that is, post operating system, allows firmware to execute after the operating system is terminated (voluntarily or involuntarily).
At block 500, the client system 108 is powered on or rebooted. In an Internet café environment, a client system is rebooted on a regular basis prior to giving a user access to the client system. A reboot or “power on” command can be sent remotely from the server 102 to the client system 108. By cycling power or rebooting the client system 108, any data stored in volatile memory in the client system by the previous user may be erased prior to giving access to the client system to the next user.
At block 502, the hardware (platform) in the client system 108 is initialized during the PEI phase and DXE phase as discussed in conjunction with the timeline shown in
At block 504, a setup or configuration parameter is checked to determine if billboard service has been enabled. Enabling or disabling billboard service may be customized by end-users, for example, the owner of the Internet café. The configuration parameter may be stored in non-volatile memory such as flash memory in the client system 108. A configuration utility may be used to modify the configuration parameter to enable billboard service. If billboard service is enabled, processing continues with block 506. If not, processing continues with block 536.
At block 506, the last updated advertisement to be displayed by the console is obtained and displayed. If this is the first time that the platform has been initialized, the default logo stored in the client system 108 will be displayed. If an advertisement has previously been downloaded, it may be stored in non-volatile memory or on a storage device in the client system 108. In this case, the previously downloaded and stored advertisement is displayed on the console. Storing the previously downloaded advertisement for display during the pre-boot period ensures efficient use of the pre-boot advertisement period. This advertisement may be displayed while a new advertisement is downloaded from the server. Processing continues with block 508.
At block 508, the network interface is setup to allow content to be displayed on the client system to be downloaded from the server over the communications network. The related DXE network drivers are loaded into memory. In an embodiment that uses the Transmission Control Protocol/Internet Protocol (TCP/IP), the network stack is set up. Processing continues with block 510.
At block 510, if the network setup fails, processing continues with block 536 to display a logo stored in the client system and boot the operating system. If not, processing continues with block 512 to connect to the server over the communications network.
At block 512, the client system 108 connects to the server 102 over the communications network 106 to obtain content to be displayed prior to booting the operating system. Methods for connecting to a server over the communications network are well-known to those skilled in the art.
At block 514, if the connection to the communications network fails, processing continues with block 536, otherwise processing continues with block 516.
At block 516, a timer is initialized with a default value for a time period for displaying content received from the server over the communications network prior to booting the operating system. This default value is controllable and may be modified by the end user of the client system through the use of a configuration utility.
At block 518, the billboard service checks to see if there is new content available to be displayed. Advertisements are stored in a database in the server and downloaded to a client system during the pre-boot advertising phase which is part of the DXE phase. In one embodiment, the advertisement is a screen image that is stored in the server. If there is a new advertisement to be downloaded to this client system, processing continues with block 520 to download the new advertisement for display on the console of the client system during the pre-boot advertising phase. If not, processing continues with block 534.
At block 520, the billboard service determines if there is a breakpoint that was stored during a prior download of an advertisement indicating that the prior download did not complete. If the download of the advertisement cannot be completed due to expiration of the time period for displaying advertisements prior to booting the operating system, a breakpoint is set and stored in the client system. The breakpoint indicates the data offset within the advertisement file at which the download should start during the next pre-boot phase. The breakpoint stores the data offset point at which the first data transmission stopped and the next data transmission starts from this recorded point. For example, if the advertisement is stored in a file having a total size of 1024 octets, but the first data transmission only downloads 500 octets, the breakpoint 500 is recorded for this file. When the next download begins, the next request to download the file starts from the next octet at offset 501 within the file.
The next time that the client system is booted, the download of the content to be displayed on the console continues from the breakpoint. This increases the time that the advertisement is displayed on the console by reducing the download time. The previously downloaded portion of the advertisement is retrieved from non-volatile memory for display on the console together with the currently downloaded portion of the advertisement. This reduces the download time for this advertisement during the current boot phase. If there is a breakpoint that was set during a prior download that did not complete, processing continues with block 523. If not, processing continues with block 522.
At block 522, the name associated with the advertisement to be displayed is obtained. Processing continues with block 523.
At block 523, the advertisement to be displayed is downloaded from the server over the communications network. Processing continues with block 524.
At block 524, the timer is checked to determine if the time period to display content has expired. If so, processing continues with block 528. If not, processing continues with block 526.
At block 526, the download process is checked to determine if the download of the new advertisement to be displayed has completed. If so, processing continues with block 528 to display the new advertisement. If not, processing continues with block 523 to continue to download the new advertisement to be displayed.
At block 528, the new advertisement is displayed on the console. Processing continues with block 530.
At block 530, the new advertisement is set to the default advertisement to be displayed during the next pre-boot phase. Processing continues with block 532.
At block 532, the downloaded content is displayed until the time period expires. Upon detecting that the time period has expired, processing continues with block 538 to boot an operating system.
At block 534, the timer has expired and the advertisement that has been downloaded is stored in the client system. The advertisement is stored in non-volatile memory or a storage device. A breakpoint is set so that the download of the contents can resume at this point during the next reboot or “power on” cycle. Processing continues with block 538 to start to boot the operating system.
At block 536, the billboard service is not enabled for the client system, static contents stored in non-volatile memory in the client system may be displayed on the console prior to starting to boot the operating system. The static contents may be a particular logo, that is, a name, symbol, or trademark designed for easy and definite recognition. The static contents may be displayed while the hardware is initialized prior to starting the boot process at block 538.
At block 538, the operating system boot process begins. This may begin by selecting a device from which to boot the operating system. After control is transferred to the operating system boot process, the display contents are no longer under control of the billboard service.
In order to be compliant with a particular operating system, for example, to receive certification for the Microsoft windows operating system, a client system must start the boot of the operating system within a specified amount of time. The firmware in the computer must start launching the operating system within a prescribed period of time to pass hardware qualification testing in order to receive certification for the Microsoft windows operating system. However, this time restriction only applies prior to the purchase of the computer by the end-user. Subsequent to the sale, the owner of the computer may customize the pre-boot environment, for example, the owner may vary the pre-boot time to allow additional time for the display of dynamic content such as advertisements.
In an embodiment, the time period may be selectable by the owner of the Internet café. The time period may be selected through a setup option in a pre-operating system configuration utility. For example, the setup page may be part of a system configuration utility that may be invoked on a personal computer by selecting a particular function key on a keyboard.
In an embodiment, the selected time period to display the downloaded advertisement is 10 seconds. During the 10 seconds, the advertisement attracts the user's attention but does not annoy the user because it does not occur during run-time. As this time period is configurable per user, this time period may be shorter or longer than 10 seconds. For example, the time period may be 10 seconds for normal users and shorter for a different category of user.
The display of advertisements is operating system independent because it is performed prior to the boot of the operating system. Also, because the advertisement is displayed during the system initialization time it does not consume runtime resources.
The advertisements that are displayed prior to booting the operating system may be tailored to the particular user who is currently accessing the client system. For example, prior to providing access to the client system, the Internet café operator can register each user with demographic information such as age, job title, or college major so that the advertisements that are displayed are targeted to that type of user.
An embodiment of the invention has been described for the EFI interface which includes network capability allowing the dynamic content to be downloaded prior to booting the operating system. An embodiment of the invention may also be included in other systems that support dynamic download over a network prior to booting an operating system. For example, an embodiment may be included in a legacy BIOS system that provides network capability prior to booting the operating system.
An embodiment of the invention has been described for downloading advertisements for display prior to booting the operating system. Other embodiments of the invention may download other content to be displayed prior to booting the operating system. For example, in a non-Internet café environment, a corporate web page may be downloaded to every client system in a corporation or a home user may select a particular web page to be downloaded to the user's system each time the system is powered on or reset. The user can also select the time period for which the web page is displayed prior to starting to boot the operating system to give adequate time to read the contents.
The ability to display dynamic content prior to booting the operating system also allows Original Equipment Manufacturers (OEMs), that is, vendors who sell computers customized for a particular application and Independent BIOS Vendors (IBVs) to communicate with users.
It will be apparent to those of ordinary skill in the art that methods involved in embodiments of the present invention may be embodied in a computer program product that includes a computer usable medium. For example, such a computer usable medium may consist of a read only memory device, such as a CD ROM disk or conventional ROM devices, or a computer diskette, having a computer readable program code stored thereon.
While embodiments of the invention have been particularly shown and described with references to embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the scope of embodiments of the invention encompassed by the appended claims.
| Number | Name | Date | Kind |
|---|---|---|---|
| 6564318 | Charda et al. | May 2003 | B1 |
| 20020019901 | Shin | Feb 2002 | A1 |
| 20030122864 | Jenne et al. | Jul 2003 | A1 |
| 20050021393 | Bao et al. | Jan 2005 | A1 |
| 20070022282 | Chang | Jan 2007 | A1 |
| Number | Date | Country |
|---|---|---|
| 2004021781 | Jan 2004 | JP |
| Number | Date | Country | |
|---|---|---|---|
| 20070118728 A1 | May 2007 | US |
