Tracking of presented television advertisements

Information

  • Patent Grant
  • 8745656
  • Patent Number
    8,745,656
  • Date Filed
    Friday, September 3, 2004
    21 years ago
  • Date Issued
    Tuesday, June 3, 2014
    11 years ago
Abstract
A method for providing television advertising includes receiving user input for selecting an advertising parameter and providing a user with an advertisement corresponding to the advertising parameter.
Description
FIELD OF THE INVENTION

This invention relates in general to television systems, and more particularly, to the field of subscriber television systems.


BACKGROUND OF THE INVENTION

Cable television systems are now capable of providing many services in addition to analog broadcast video. In implementing enhanced programming, the home communication terminal (“HCT”), otherwise known as the settop box, has become an important computing device for accessing various video services. In addition to supporting traditional analog broadcast video functionality, digital HCTs (or “DHCTs”) now also support an increasing number of two-way digital services such as video-on-demand.


A DHCT is typically connected to a cable or satellite television network and includes hardware and software necessary to provide various services and functionality. Preferably, some of the software executed by a DHCT is downloaded and/or updated via the cable television network. Each DHCT also typically includes a processor, communication components and memory, and is connected to a television or other display device. While many conventional DHCTs are stand-alone devices that are externally connected to a television, a DHCT and/or its functionality may be integrated into a television or personal computer, as will be appreciated by those of ordinary skill in the art.


A DHCT provides users with television programming and television advertising. Many DHCT users, however, often avoid viewing television advertisements. Television advertisements may be avoided in a number of ways including, for example, by switching television channels during an advertisement or by recording a television program and then using trick mode functionality to skip recorded advertisements. One reason for why a viewer may avoid viewing an advertisement is because the viewer may not be interested in the product or service being advertised. Advertisement avoidance results in lower advertisement exposure for advertisers and, therefore, in lower potential revenue for television service providers. Therefore, there is a need for systems and methods for increasing the viewing of television advertisements.





BRIEF DESCRIPTION OF THE DRAWINGS

The invention can be better understood with reference to the following drawings. The components in the drawings are not necessarily drawn to scale, emphasis instead being placed upon clearly illustrating the principles of the present invention. In the drawings, like reference numerals designate corresponding parts throughout the several views.



FIG. 1 is a block diagram depicting a non-limiting example of a television services system.



FIG. 2 is a block diagram depicting a non-limiting example of the internal configuration of the DHCT depicted in FIG. 1.



FIG. 3 depicts a non-limiting example of a remote control device that may be used to provide user input to the DHCT depicted in FIG. 2.



FIG. 4 depicts a non-limiting example of an advertisement category selection screen which may be provided in response to user input such as, for example, the activation of the “ADS” key depicted in FIG. 3.



FIG. 5 depicts a non-limiting example of an advertisement sub-category selection screen which may, in one embodiment, be provided in response to the selection of an advertisement category via the advertisement category selection screen depicted in FIG. 4.



FIG. 6 depicts a non-limiting example of an advertisement source selection screen which may be provided in response to the selection of an advertisement sub-category via the advertisement sub-category selection screen depicted in FIG. 5.



FIG. 7 depicts a non-limiting example of a product preference selection screen which may be provided in response to the selection of an advertisement source option via the advertisement source selection screen depicted in FIG. 6.



FIG. 8 depicts a non-limiting example of an advertisement selection screen which may be provided during a television presentation.



FIG. 9 is a flow chart depicting a non-limiting example of steps for tracking the presentation of advertisements in accordance with one embodiment of the invention.



FIG. 10 is flow chart depicting a non-limiting example of a routine that may be used to determine a number of advertisements that are presented to a user.



FIG. 11 is a flow chart depicting a non-limiting example of steps for providing a user with advertisements in accordance with one embodiment of the invention.





DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

Systems and methods are provided herein for managing the presentation of television advertisements. As a non-limiting example, among others, a television advertisement may be an audio/video television commercial. In one embodiment of the invention, a DHCT receives user input for selecting an advertisement or type of advertisement, and then presents the user with an advertisement that corresponds to the user's selection. The advertisement may be presented to the user immediately after the user's selection or may be presented to the user at subsequent times during interruptions in television broadcast presentations.


In another embodiment, a DHCT may keep track of the number of times that an advertisement is presented to a user in order to determine whether the advertisement is to continue being presented. The DHCT may also keep track of the total number of advertisements that have been presented over a predetermined period of time in order to determine whether to present an additional advertisement at a current time.


In yet another embodiment of the invention, an advertisement or type of advertisement is assigned a value by a system operator. A user may then select advertisements and/or types of advertisements based their respective assigned values as shown via an advertisement selection screen. A DHCT may then manage the presentation of advertisements based on their individual and/or cumulative values. As a non-limiting example, the frequency and/or duration of an advertisement or plurality of advertisements may be inversely correlated to the value of the advertisement(s).


The preferred embodiments of the present invention now will be described more fully hereinafter with reference to the accompanying drawings. These embodiments are examples, among others, of systems and methods of the present invention. Therefore, the present invention, which may be embodied in many different forms, should not be construed as limited to the embodiments set forth herein.



FIG. 1 is a block diagram depicting a non-limiting example of a television services system 100. In this example, the television services system 100 includes a headend 110 and a DHCT 200 that are coupled via a network 130. The DHCT 200 is typically situated at a user's residence or place of business and may be a stand-alone unit or integrated into another device such as, for example, the television 140 or a personal computer (not shown). The DHCT 200 receives signals (video, audio and/or other data) from the headend 110 through the network 130 and provides any reverse information to the headend 110 through the network 130. The network 130 may be any suitable means for communicating television services data including, for example, a cable television network, a public switched telephone network (PSTN), a satellite communication network, the internet, etc. The headend 110 may include one or more server devices (not shown) for providing video, audio, and textual data to client devices such as DHCT 200. The headend 110 and the DHCT 200 cooperate to provide a user with television services including, for example, television programs, an interactive program guide (IPG), and/or video-on-demand (VOD) presentations. The television services may be provided via a television 140. Alternatively, the DHCT 200 may provide television services via a display device other than the television 140.


In one embodiment of the invention, an advertising counter may be used to track a number of times that a television advertisement is presented by a DHCT 200. In one implementation, an advertisement continues to be presented via a DHCT 200 until it has been presented a predetermined number of times via the DHCT 200 or via a plurality of DHCTs. If the advertisement is stored in a DHCT 200, then it may be deleted from the DHCT 200 after it is presented a predetermined number of times. An “electronic advertisement information” (EAI) database 228 may be used to keep track of advertisements that are to be stored in or deleted from a DHCT 200. If the advertisement is stored at the headend 110, then the headend 110 may discontinue broadcasting the advertisement after it is presented a predetermined number of times. For example, a certain advertisement may be deleted or discontinued after it is presented 10 times by a single DHCT 200 and/or after it is presented 15,000 times by a group of DHCTs. In one possible implementation, the advertising counter in a DHCT 200 may track the number of times that an advertisement is presented to a user or a group of users of a particular DHCT 200 by soliciting certain user input during, before, or after the presentation of the advertisement and then determining if the solicited input is received. In another implementation, the advertising counter may track the number of times that an advertisement is presented to a user based on whether the television 140 is turned on while the advertisement is being presented by the DHCT 200; if the television is not turned on, then the counter is not incremented. In one possible implementation, a television may be determined to be turned on if certain user input related to the operation of the television (e.g., volume control, channel navigation, among others) had been received by the DHCT 200 within a preceding predetermined period of time.


In another embodiment, a television advertisement continues to be presented intermittently via a DHCT 200 until it has been presented a predetermined number of times via the DHCT 200 or until an expiration date. In yet another embodiment, an advertisement is only shown during enabled viewing periods associated with the advertisement and/or according to the program category that the viewer is watching at a current time. Hence, an advertisement may feature a set of flags in an EAI database record that indicates when the respective advertisement is enabled for viewing. For example, a car or truck advertisement may be enabled for viewing during periods when a sports or news program is being watched and/or during certain times of the day. The enabled viewing periods occur between the advertisement's introduction date and the advertisement's expiration date. The enabled viewing periods, the introduction date, and the expiration date may be received from the headend 110 and stored in the EAI database 228 in DRAM 220.


A enabled viewing period associated with a television advertisement may have a recurring schedule such as, for example, among others, a daily recurring schedule and/or a weekly recurring schedule. As a non-limiting example, liquor or beer advertisements may have enabled viewing periods of 9:00 p.m. to 5:00 a.m. during weekdays and 2:00 p.m. to 5:00 a.m. during weekend days (weekly recurring schedule); adult movies and products advertisements may have enabled viewing periods from 10:00 p.m. to 5:00 a.m. every day (daily recurring scheduled); and football advertisements may have enabled viewing periods from 1:00 p.m. to 6:00 p.m. on weekend days only (weekly recurring schedule).


In another embodiment of the invention, a user is presented with an advertisement that corresponds to an advertisement or type of advertisement that is selected by the user. An advertisement or type of advertisement may be selected by a user significantly in advance (e.g., an hour, a day, a week, a month, or a year in advance) and/or immediately prior to the presentation of a corresponding advertisement. Furthermore, an advertisement selection screen may be provided to a user in response to user input and/or during an advertisement interruption in a television broadcast presentation. Selection options in an advertisement selection screen may be retrieved from the EAI database 228.


In yet another embodiment of the invention, an advertisement is associated with a value or weight. The DHCT 200 may keep track of the total value of the advertisements that are presented via DHCT 200 based on the value of the individual advertisements that are presented. For example, if the DHCT 200 presents ten advertisements having a value of 1, ten advertisements having a value of 2, and ten advertisements having a value of 3 over a certain period of time, then the total value of the advertisements presented over that period of time is equal to 60.


A user may be informed of the value of each of a plurality of advertisements and/or types of advertisements and may be provided with an option of selecting the advertisements and/or types of advertisements that the user desires to watch. In one implementation, the higher the total value of advertisements that are presented to a user over a certain period of time, the less the total number and/or duration of advertisements will be. For example, a user who is presented with advertisements having a total value of 1 V may be presented with advertisements having a total duration of 2T, and another user who is presented advertisements having a value of 2V may be presented with advertisements having a total duration of 1T, where V represents a certain total value and T represents a certain total duration. Although the total value of advertisements presented over a certain period of time may be inversely correlated to the total duration of the advertisements, the correlation coefficient is not necessarily −1. In this manner, a Multiple System Operator (MSO) may assign values to advertisements based on the levels of advertisement exposure that are desired by the respective advertisers. An MSO may charge advertisers based on the value that is associated with their respective advertisements and/or based on the estimated number of times that their respective advertisements are presented to viewers via DHCTs that receive the MSO's television programming. In one implementation, an estimated number of times that an advertisement is presented to a user may be based on user inputs that are received by the DHCTs confirming that the advertisement has been, is being, and/or will be viewed.



FIG. 2 is a block diagram depicting a non-limiting example of a DHCT 200. The DHCT 200 described herein is merely illustrative and should not be construed as implying any limitations upon the scope of the present invention. In an alternative embodiment, the DHCT 200 may have different, fewer, or additional components than those shown in FIG. 2. The DHCT 200 includes a communications interface 205 for receiving signals (video, audio and/or other data) from the headend 110, at least one processor 240 for controlling operations of the DHCT 200, an output system 280 for driving the television 140, and a tuner system 250 for tuning to a particular television channel to be displayed. The tuner system 250 includes, in one implementation, an out-of-band tuner for bidirectional quadrature phase shift keying (QPSK) data communication and a quadrature amplitude modulation (QAM) tuner for receiving television signals and data. Data received via either tuner may comprise electronic program information and/or EAI data A receiver 260 receives externally-generated user inputs or commands from an input device such as, for example, a remote control device.


The DHCT 200 may include one or more wireless or wired interfaces (not shown), also called ports, for receiving and/or transmitting data to other devices. For instance, the DHCT 200 may feature a USB (Universal Serial Bus), an Ethernet port (for connection to a computer), an IEEE-1394 connection (for connecting to consumer electronics equipment), a serial port, a parallel port, a radio frequency (RF) interface, and/or an infra-red (IR) interface. In this manner, user inputs may be provided via, for example, a personal computer, buttons or keys located on the exterior of the DHCT 200, a hand-held remote control device, and/or a keyboard that includes user-actuated keys, etc.


The DHCT 200 may include an advertisement storage unit 295 for storing advertisements. Stored advertisements are generally referred to herein as advertisement clips or advertisement media streams. The storage unit 295 may incorporate electronic, magnetic, optical, and/or other types of storage media. An advertisement management application 225 may be used for managing advertisements, including managing content stored in the storage unit 295. Advertisements may be received from a headend 110 (FIG. 1) and stored in the storage unit 295 based on instructions contained in the advertisement management application 225. Electronic advertisement information, or EAI data, associated with stored advertisements may be stored in DRAM 220 or in storage unit 295. Although shown as residing within the DHCT 200, the storage unit 295 may alternatively be located outside the DHCT 200 and coupled thereto using a wired or wireless connection. In an alternative embodiment, an advertisement storage unit 295 is not used in connection with the DHCT 200, in which case, an advertisement may be presented to a user as it is being received from the headend 110.


System memory 210 includes flash memory 230 and dynamic random access memory (DRAM) 220 for storing various applications, modules and data for execution and use by the processor 240. Basic functionality of the DHCT 200 is provided by an operating system 234 that is primarily stored in flash memory 230. The operating system 234 includes at least one resource manager 235 that provides an interface to and coordination of resources of the DHCT 200 such as, for example, computing resources.


One or more programmed software applications, herein referred to as applications, are executed by utilizing the computing resources in the DHCT 200. Applications stored in flash memory 230 or DRAM 220 are executed by processor 240 under the auspices of the operating system 234. Data required as input by an application is stored in DRAM 220 or flash memory 230 and read by processor 240 as needed during the course of the application's execution. Input data may be data stored in DRAM 220 by a secondary application or other source, either internal or external to the DHCT 200, or possibly anticipated by the application and thus created with the application at the time it was generated as a software application, in which case it is stored in flash memory 230. Data generated by an application is stored in DRAM 220 by processor 240 during the course of the application's execution.


An application referred to as navigator 236 is also resident in flash memory 230 and provides a navigation framework for services provided by the DHCT 200. The navigator 236 registers for and in some cases reserves certain user inputs related to navigational keys such as television channel up/down, last television channel, favorite television channel, etc. The client applications may be resident in flash memory 230 or downloaded into DRAM 220.


The flash memory 230 also contains a platform library 231. The platform library 231 is a collection of utilities useful to applications, such as a timer manager, a compression manager, a configuration manager, an HTML parser, a database manager, a widget toolkit, a string manager, and other utilities (not shown). These utilities are accessed by applications via application programming interfaces (APIs) as necessary so that each application does not have to contain these utilities. Two components of the platform library 231 that are shown in FIG. 2 are a window manager 233 and a service application manager (SAM) client 232.


The window manager 233 provides a mechanism for implementing the sharing of the screen regions and user input. The window manager 233 is also responsible for, as directed by one or more applications, implementing the creation, display, and allocation of the limited DHCT 200 screen resources. Window manager 233 allows multiple applications to share the screen by assigning ownership of screen regions, or windows. Window manager 233 communicates with resource manager 235 to coordinate available resources (such as display memory) among different resource-consuming processes. Such processes may be directly or indirectly invoked by one or more applications.


The window manager 233 also maintains, among other things, a user input registry 221 in DRAM 220 so that when a user enters a key or a command via a remote control device or another input device such as a keyboard or mouse, the user input registry 221 may be accessed to determine which of various applications running on the DHCT 200 should receive data corresponding to the input key and in which order. As an application is executed, it registers a request to receive certain user input keys or commands. When the user presses a key corresponding to one of the commands on the remote control device, the command is received by the receiver 260 and relayed to the processor 240. The processor 240 dispatches the event to the operating system 234 where it is forwarded to the window manager 233. The window manager 233 then accesses the user input registry 221 and routes data corresponding to the incoming command to the appropriate application.


The SAM client 232 is a client component of a client-server pair of components, with the server component being located on the headend 110 (FIG. 1). A SAM database 222 in DRAM 220 includes a data structure of services and a data structure of television channels that are created and updated by the headend 110. Many television services can be defined using the same application component, with different parameters. Television services include, without limitation and in accordance with one implementation, the presentation of television broadcast programs, video-on-demand (VOD), and interactive program guides (IPG). In general, the identification of a service includes the identification of an executable application that provides the service along with a set of application-dependent parameters that indicate to the application the service to be provided. As a non-limiting example, a service of presenting a television program could be executed with a set of parameters to view HBO or with a separate set of parameters to view CNN. Each association of the application component (tune video) and one parameter component (HBO or CNN) represents a particular service that has a unique service I.D.


Application clients can be downloaded into DRAM 220 at the request of the SAM client 232, typically in response to a request by the user or in response to a message from the headend. In this non-limiting example, DRAM 220 contains an interactive program guide (IPG) application 224 and an advertisement management application 225. The IPG application 224 may use IPG data stored in IPG database 227 to determine a program's category prior to creating and presenting a graphical user interface containing program information sorted by category. Similarly, the advertisement management application 225 may use EAI data stored in an EAI database 228 to select and present an advertisement based on a desired advertisement category previously selected by a user. It should be clear to one with ordinary skill in the art that these applications are not limiting and merely serve as examples for an embodiment of the invention. Furthermore, one or more DRAM based applications may, as an alternative embodiment, be resident in flash memory 230. These applications, and others provided by a television services system operator, are software entities for providing services to the user.


A broadcast file system (BFS) client 237 has a counterpart BFS server module (not shown) located at the headend 110. The BFS server repeatedly sends data that is received by the BFS client 237 and stored in DRAM 220. The data is sent on a data carousel over a period of time in cyclical repeated manner so that applications on a DHCT 200 can use the data as needed. For example, a BFS server may repeatedly send current IPG data and/or IPG data updates so that an IPG application 224 is able to provide a user with current television program listings. Likewise, a BFS server may repeatedly send current EAI data and/or EAI data updates so that advertisement management application 225 is able to present a user with updated and current advertisement information. The DHCT 200 may receive EAI data via an out-of-band channel or an in-band channel. Furthermore, EAI data may be received by the DHCT 200 as MPEG private data in an MPEG transport stream.


Advertisement management application 225 receives a plurality of media types that serve as television advertisements. Among others, a first type of advertisement comprises graphical and/or textual information that is overlaid on a displayed video picture. A second type of advertisement comprises video data that is displayed in a full-screen format or in a downscaled video window. A third type of advertisement comprises audio data A fourth type of advertisement comprises a combination of graphical, textual, audio, and/or video data.


A television advertisement may be packaged into a file and may be delivered to DHCT 200 via the BFS delivery mechanism. An advertisement that is received by a DHCT 200 may either be displayed immediately upon receipt or may be stored in the advertisement storage unit 295 for presentation at a later time. In one embodiment of the invention, a DHCT 200 receives an advertisement file that is broadcast by the BFS regardless of whether the advertisement corresponds to a user preference. In an alternative embodiment, a DHCT 200 only receives advertisement files that correspond to a user preference. For instance, subscribers that have indicated via preferences identified by the advertisement preference settings 229 that they wish to receive and view advertisements related to baby products, may receive BFS files corresponding to baby product advertisements whereas other subscribers may not. Advertisement preference settings 229 are preferably stored in DRAM 220, but may also be stored in non-volatile memory so that they may be retrieved in case of a power outage. The non-volatile memory may be flash memory 230 or memory that is external to the DHCT 200 such as, for example, the headend 110 or a storage device (not shown) that is coupled to the DHCT 200. Advertisement management application 225 interprets advertisement preferential settings stored in DRAM 220 and, in communication with BFS client 237, effects the opening of desired advertisement files on a periodic basis. Each advertisement category may be assigned a respective sub-directory. A DHCT 200 may open an advertisement category's sub-directory upon receiving a message from the headend 110 that an update to the advertisement category has occurred.


In one implementation, applications executing on the DHCT 200 work with the navigator 236 by abiding by several guidelines. First, an application utilizes the SAM client 232 for the provision, activation, and suspension of services and service enhancements. Second, an application shares DHCT 200 resources with other applications and abides by the resource management policies of the SAM client 232, the operating system 234, and the DHCT 200. Third, an application conforms to situations where shared resources are only accessible via the navigator 236. Fourth, when an application loses service authorization while providing a service, the application suspends the service via the SAM client 232 (the navigator 236 will reactivate an individual service application when it later becomes authorized). Finally, an application client is designed to not have access to certain user input keys reserved by the navigator 236 (e.g., power, channel +/−, volume +/−, etc.).


Data and software used in providing a DHCT service to a user may be stored in one or more of the following memory resources: a data storage device located at a headend, a data storage device located at a customer premises, a non-volatile memory internal to the DHCT 200, and/or a hard drive internal to the DHCT 200. For example, an executable program or algorithm corresponding to an operating system (OS) component, or to a client platform component, or to a client application (e.g. IPG application 224), or to respective parts thereof, may reside in and/or execute out of DRAM 220 and/or flash memory 230, or may reside in a local storage device connected to DHCT 200 and may be transferred into DRAM 220 for execution. Likewise, data input for an executable program or algorithm may reside in DRAM 220 or in flash memory 230, or may reside in a local storage device connected to the DHCT 200 and may be transferred into DRAM 220 for use by an executable program or algorithm. In addition, data output by an executable program or algorithm may be written into DRAM 220 by the executable program or algorithm and may be transferred to flash memory 230 or to a local storage device for storage purposes. It should be noted, however, that the present invention is not limited by where or how any data and/or applications are stored or retrieved.


Each of the above mentioned applications comprises executable instructions for implementing logical functions and can be embodied in any computer-readable medium for use by or in connection with an instruction execution system, apparatus, or device, such as a computer-based system, processor-containing system, or other system that can fetch and execute the instructions. In the context of this document, a “computer-readable medium” can be any means that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device. The computer readable medium can be, for example but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, device, or propagation medium. More specific examples (a non-exhaustive list) of the computer-readable medium would include the following: an electrical connection (electronic) having one or more wires, a portable computer diskette (magnetic), a random access memory (RAM) (electronic), a read-only memory (ROM) (electronic), an erasable programmable read-only memory (EPROM or Flash memory) (electronic), an optical fiber (optical), and a portable compact disc read-only memory (CDROM) (optical). Note that the computer-readable medium could even be paper or another suitable medium upon which the program is printed, as the program can be electronically captured, via for instance optical scanning of the paper or other medium, then compiled, interpreted or otherwise processed in a suitable manner, and then stored in a computer memory.



FIG. 3 depicts a non-limiting example of a remote control device 300 that may be used to provide user input to the DHCT 200. The remote control device 300 described herein is merely illustrative and should not be construed as implying any limitations upon the scope of the present invention. Four arrow keys 310 are provided including an up arrow key 311, a down arrow key 312, a left arrow key 313, and a right arrow key 314. The arrow keys 310 can be used to scroll through on-screen options and/or to highlight an on-screen option, whereas the select key 320 may be used to select a currently highlighted option. The advertisements key 395 may be used to request an advertisement or an advertisement selection menu. The function of the “A” key 371, the “B” key 372, and the “C” key 373 varies depending on the screen being presented to a user at the time of a key's activation. In one embodiment, the “A” key 371 can be used to access a browse-by list for requesting an IPG screen that contains a subset of television programs falling under a user selected browse-by category such as, for example, comedy, drama, action/adventure, sports, etc.; the “B” key 372 can be used to request an IPG screen containing program listings for a user selected date; and the “C” key 373 can be used to request an IPG that covers a time period that includes the current time.


In an alternative embodiment of the invention, different and/or additional systems and methods of providing user input may be used including, for example, a remote control device having different keys and/or key layouts, a keyboard device, a mouse, a voice activated input system, a touch-screen display, etc. The invention described herein is not limited by the type of device used to provide user input.



FIGS. 4-8 depict non-limiting examples of screens that may be used for selecting an advertisement or type of advertisement. It should become apparent to one skilled in the art in light of the following descriptions that additional, different, and/or fewer selections screens may be used in an alternative embodiment of the present invention.



FIG. 4 depicts a non-limiting example of an advertisement category selection screen 400 which may be provided in response to user input such as, for example, the activation of the “ADS” key 395 (FIG. 3). An advertisement category menu 401 includes advertising category options corresponding to categories of products and services that may be advertised via the DHCT 200. Advertising category options may include, for example, clothes, food, restaurants, hotels, airlines, softdrinks, cars & trucks, stores, beer, TV programs, movies, electronics, baby products, and toys (among others). In another embodiment of the invention, a television advertisement category selection menu 401 may contain fewer, additional, or different advertisement category options such as, for example, make-up, kitchen products, household products, furniture, health products, and VOD movies, etc. The advertisement category options may be used to determine user preferences regarding advertisements. A user may use the arrow keys 310 (FIG. 3) in order to highlight an option or to access additional options by scrolling up or down the advertisement category menu. The select key 320 may be used to select a currently highlighted option. An advertisement category option that is selected from the television advertisement category menu is added to an active selection list 403. After the user selects the desired advertisement categories, the user can provide additional input via the remote control 300 in order to confirm the selections. Such input may be provided via, for example, activation of the “A” key 371 (FIG. 3). User selections of on-screen options shown in other screen depictions may also be performed in a similar manner. However, the selection of any of the on-screen options discussed herein may alternatively be performed in a different manner including for example, the use of different user input devices.



FIG. 5 depicts a non-limiting example of an advertisement sub-category selection screen 500 which may, in one embodiment, be provided in response to the selection of an advertisement category via the advertisement category selection screen 400 (FIG. 4). An advertisement sub-category menu 501 includes advertising sub-category options corresponding to the user selected category which, in this example, is “Cars and Trucks” 402 (FIG. 4). In one embodiment, if a user had selected multiple categories via the category selection screen 400, then the sub-category menu may include options corresponding to respective sub-categories. In an alternative embodiment, the user may be provided with multiple sub-category menus in succession, where each sub-category menu corresponds to one of the multiple categories that were selected via the category selection screen 400. Advertisement sub-category options may be used to determine user preferences in relation to a specific category of advertisements (e.g., cars and trucks). Advertisement sub-category options corresponding to the cars and trucks category 402 may include, for example, SUV, pick-up, minivan, luxury, economy, sports, and family. A user may provide user input in order to select one or more sub-categories from the sub-category menu 501.



FIG. 6 depicts a non-limiting example of an advertisement source selection screen 600 which may be provided in response to the selection of an advertisement sub-category via the advertisement sub-category selection screen 500 (FIG. 5). In an alternative embodiment, the advertisement source selection screen 600 may be provided in response to the selection of the cars and trucks option 402 via the advertisement category selection screen 400 (FIG. 4). An advertisement source menu 601 includes advertising source options corresponding to the user selected sub-category which, in this example, is luxury (cars & trucks) 502 (FIG. 5). Advertisement source options may be used to determine user preferences in relation to a source or name-brand for a certain type of products. Advertising source options corresponding to the luxury cars and trucks option 502 may include, for example, Infinity, Lexus, Volvo, Acura, Audi, BMW, and Cadillac, among others.



FIG. 7 depicts a non-limiting example of a product preference selection screen 700 which may be provided in response to the selection of an advertisement source option via the advertisement source selection screen 600 (FIG. 6). A product preference menu 701 includes product preference options corresponding to the user selected advertisement source which, in this example, is Acura 602 (FIG. 6). Product preference options may be used to determine user preferences in relation to a specific product. Product preference options corresponding to the Acura option 602 may include, for example, the following Acura models: Integra, MDX, NSX, CL, and Legend.



FIG. 8 depicts a non-limiting example of an advertisement selection screen 800 which may be provided during a television presentation. The television presentation may be, for example, a television program, a video-on-demand presentation, or a pay-per-view presentation. In one embodiment, the advertisement selection screen 800 may be provided to a user in response to a specified user input such as, for example, the activation of the “ADS” key 395 (FIG. 3). An advertisement menu 801 includes advertisement options corresponding to products and services that may be advertised via the DHCT 200. A user may select an advertisement option in order to be presented with a corresponding advertisement. In one embodiment, a user may select several advertisements options before being presented the corresponding advertisements. This may achieved by, for example, providing the user with feedback that identifies the options that are currently selected. The feedback may be in the form of an icon, a background color, and/or text that is associated with a selected option. After selecting the desired advertisement options, the user may then provide input that initiates the presentation of the selected advertisements. In another embodiment of the invention, a value is associated with each of the advertisements. The value of an advertisement may be identified via an icon, a background color, and/or text that is associated with advertisement option. A user may be required to view, over a certain period of time, a number of advertisements that have a certain total value. Alternatively, a user may be rewarded for viewing advertisements having a relatively high total value by being presented with shorter and/or fewer advertisements and/or advertisement interruptions.



FIG. 9 is a flow chart 900 depicting a non-limiting example of steps for tracking the presentation of advertisements in accordance with one embodiment of the invention. In step 901, the DHCT 200 outputs an advertisement. Then, in step 902, the DHCT 200 determines whether the advertisement has been or is being viewed. The determination may be based on viewer input that is solicited by the DHCT 200 during, before, and/or after the presentation of the advertisement. In another embodiment, the determination may be based on whether the television is turned on during the presentation of the advertisement. A television may be determined to be turned on if, for example, certain user input related to the operation of the television (e.g., volume control, channel navigation, among others) had been received by the DHCT 200 within a preceding predetermined period of time. In yet another embodiment, step 902 is not implemented, and step 903 is performed after step 901.


After the DHCT 200 determines whether an advertisement has been or is being viewed, then the DHCT 200 in step 903 updates an advertisement tracking database accordingly. The advertising tracking database keeps track of the number, value, type and/or identity of the advertisements that were viewed by a household, and may be used to determine which advertisements to present to a user. For example, if an advertisement is viewed more than a certain number of times by a certain household, then it would no longer be presented by a DHCT 200 to that household.



FIG. 10 is flow chart depicting a non-limiting example of a routine 1000 that may be used to determine a number of advertisements that are presented to a user. The routine 1000 may be part of the advertisement management application 225. After the routine 1000 is initiated in step 1001, the routine 1000 determines in step 1002 whether an advertisement tracking score is greater than a predetermined value. The advertisement tracking score reflects a value associated with advertisements that have been presented to a user over a certain time period immediately prior to the implementation of step 1002, and may be determined using an advertisement tracking database. If the score is greater that a predetermined value, then the routine 1000 terminates as indicated in step 1003. However, if the score is not greater than a the predetermined value, then the routine 1000 initiates in step 1004 the presentation of an advertisement. In one embodiment, the advertisement may be selected in accordance with previously determined user preferences. After the routine 1000 initiates the presentation of the advertisement, then the routine 1000, in step 1005 updates an advertisement tracking database based on the value that is associated with the advertisement that was presented to the user. In an alternative embodiment, the database is only updated if the routine 1000 determines that the advertisement was viewed. Such a determination may be based on, for example, whether certain user input was received during the presentation of the advertisement or whether the television was turned on. After step 1005, the routine 1000 then returns to step 1002 and determines once again whether the advertisement tracking score is greater than the predetermined value.



FIG. 11 is a flow chart 1100 depicting a non-limiting example of steps for providing a user with advertisements in accordance with one embodiment of the invention. In step 1101, the DHCT 200 provides the user with an advertisement selection menu. The advertisement selection menu may be provided during the provision of a video presentation (e.g. a television program or a VOD movie) or in response to user input requesting the menu. The menu may have selections that identify specific advertisements or that identify types of products, services, and/or their sources, as discussed above in reference to FIGS. 4-8. In step 1102 the DHCT 200 receives user input identifying one or more selections from the advertisement selection menu. After the DHCT 200 receives the user input, it provides the user with one or more advertisements that correspond to advertisement selection(s) identified by the user input 1103. In one embodiment of the invention, an advertisement corresponding to a user selection is provided immediately after the advertisement selection process is complete. In another embodiment of the invention, the user selection(s) is/are used to determine the advertisements that are intermittently presented to the user over an extended period of time.


Steps or blocks shown in each of the flow charts illustrated in FIGS. 9-11 represent modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or steps in a process. Alternate implementations are included within the scope of the preferred embodiments of the present invention in which functions or steps may be executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those reasonably skilled in the art.


It will be appreciated by those skilled in the art that the functionality provided by each of the flow charts illustrated in FIGS. 9-11 can also be implemented through hardware and supporting circuitry. Each implementation has its advantages, however. For example, hardware enjoys a speed and, arguably, a reliability advantage over software because hardware testing and verification methods are currently more advanced than software verification methods. On the other hand, software can be less expensive than customized hardware and offers greater flexibility in adding or modifying product features. It will be also be appreciated by those skilled in the art that the functionality provided by each of the flow charts illustrated in FIGS. 9-11 may be implemented in a combination of software and hardware.


Further, the functionality provided by each of the flow charts illustrated in FIGS. 9-11, can be embodied in any computer-readable medium for use by or in connection with a computer-related system (e.g., an embedded system such as a modem) or method. In this context of this document, a computer-readable medium is an electronic, magnetic, optical, semiconductor, or other physical device or means that can contain or store a computer program or data for use by or in connection with a computer-related system or method. Also, the computer program or data may be transferred to another computer-readable medium by any suitable process such as by scanning the computer-readable medium. Thus, the computer-readable medium could be paper or other suitable medium upon which the computer program can be printed, scanned with an optical scanning device, and transferred into the computer's memory or storage.


It should be emphasized that the above-described embodiments of the present invention, particularly any “preferred embodiments”, are merely possible examples, among others, of the implementations, setting forth a clear understanding of the principles of the invention. Many variations and modifications may be made to the above-described embodiments of the invention without departing substantially from the principles of the invention. All such modifications and variations are intended to be included herein within the scope of the disclosure and present invention and protected by the following claims. In addition, the scope of the present invention includes embodying the functionality of the preferred embodiments of the present invention in logic embodied in hardware and/or software-configured mediums.

Claims
  • 1. A method implemented by a television set-top terminal (STT), comprising: determining by the STT whether a television is on; andresponsive to determining that the television is on and responsive to a counter value less than a predetermined value, the counter value corresponding to an amount of times an advertisement stored in a first local memory is output by the STT, outputting by the STT an advertisement to the television, wherein the advertisement corresponds to a category of advertisements, the category explicitly selected from among a plurality of selectable advertisement categories by a viewer of the television, wherein the advertisement comprises a corresponding weight, wherein the corresponding weight relates to a total advertisement display duration, wherein the television is determined to be on responsive to an STT-solicited viewer input associated with the advertisement, the solicitation notifying the user of the weight and provided as a predetermined query presented to the user within a predetermined period of time prior to the output of the advertisement; andtracking a plurality of advertisements to be stored and deleted from the first local memory in an electronic advertisement database separate from the first local memory, wherein the electronic advertisement database further stores a set of flags associated with each of the plurality of advertisements, the set of flags indicative of when each advertisement is enabled for viewing, wherein for each of the plurality of advertisements the electronic advertisement database further stores a viewing period, an introduction date, an expiration date, and a plurality of selection options capable of display.
  • 2. The method of claim 1, further comprising: incrementing a counter configured to count advertisements output by the STT.
  • 3. The method of claim 2, wherein the counter is incremented responsive to determining that the television is on and responsive to outputting the advertisement.
  • 4. The method of claim 2, further comprising: deleting the advertisement from the STT responsive to a value of the counter.
  • 5. The method of claim 1, further comprising tracking a number of times that the advertisement is presented to a user.
  • 6. The method of claim 5, wherein tracking further comprises determining whether the advertisement is being presented by the STT while the television is on.
  • 7. The method of claim 5, wherein tracking further comprises incrementing a counter when the advertisement is being presented by the STT while the television is on and abstaining from incrementing the counter if the television is not turned on.
  • 8. The method of claim 1, wherein responsive to the counter value reaching the predetermined value, ceasing the output of the advertisement to the television.
  • 9. The method of claim 1, further comprising: providing the user with an option to select the advertisement from a plurality advertisements.
  • 10. The method of claim 1, further comprising: decreasing a duration of the advertisement based on the weight of the advertisement.
  • 11. A system, comprising: a television;a first local memory;an electronic advertisement database configured to track a plurality of advertisements to be stored and deleted from the first local memory, wherein the electronic advertisement database further stores a set of flags associated with each of the plurality of advertisements, the set of flags indicative of when each advertisement is enabled for viewing, wherein for each of the plurality of advertisements the electronic advertisement database further stores a viewing period, an introduction date, an expiration date, and a plurality of selection options capable of display; anda set-top terminal (STT) coupled to the television, the STT configured to: receive an input signal corresponding to an explicit selection of an advertisement category from among a plurality of selectable advertisement categories, the selection by a viewer of the television;determine whether the television is on; andresponsive to determining that the television is on, output one of the plurality of advertisements to the television, wherein the advertisement corresponds to the explicitly selected advertisement category and comprises a corresponding weight, wherein the corresponding weight relates to a total advertisement display duration, wherein the television is determined to be on responsive to an STT-solicited viewer input associated with the one of the plurality of advertisements, the solicitation notifying the user of the weight and provided as a predetermined query presented to the user prior to the output of the one of the plurality of advertisements.
  • 12. The system of claim 11, wherein the STT is further configured to: track a number of times that the advertisement is output to the television.
  • 13. The system of claim 11, wherein the STT is further configured to: increment a counter responsive to the advertisement being output by the STT while the television is on; andabstain from incrementing the counter if the television is not turned on.
  • 14. The system of claim 11, wherein the STT is further configured to: increment a counter, responsive to the STT outputting the advertisement; anddelete the advertisement from the STT, responsive to a specific value of the counter.
  • 15. The system of claim 11, wherein responsive to the counter value reaching the predetermined value, the STT is configured to cease the output of the advertisement to the television.
  • 16. A set-top terminal (STT) comprising: a first local memory;an electronic advertisement database configured to track a plurality of advertisements to be stored and deleted from the first local memory, wherein the electronic advertisement database further stores a set of flags associated with each of the plurality of advertisements, the set of flags indicative of when each advertisement is enabled for viewing, wherein for each of the plurality of advertisements the electronic advertisement database further stores a viewing period, an introduction date, an expiration date, and a plurality of selection options capable of display; anda processor configured by executable instructions stored in the memory to; receive an explicit selection of an advertisement category from a viewer of the television;determine whether the television is on; andresponsive to determining that the television is on, output an advertisement to the television, wherein the advertisement is tracked in the electronic advertisement database, the advertisement corresponding to the advertisement category selection and comprising a weight, wherein the corresponding weight relates to a total advertisement display duration, wherein the television is determined to be on responsive to an STT-solicited viewer input associated with the advertisement, the solicitation notifying the user of the weight and provided as a predetermined query presented to the user immediately after completion of the output of the advertisement.
  • 17. The STT of claim 16, wherein the processor is further configured by the executable instructions to: track a number of times that the advertisement is output to the television.
  • 18. The STT of claim 16, wherein the processor is further configured by the executable instructions to: increment a counter responsive to the advertisement being output by the STT while the television is on; andabstain from incrementing the counter if the television is not turned on.
  • 19. The STT of claim 16, wherein the processor is further configured by the executable instructions to: increment a counter, responsive to the STT outputting the advertisement; anddelete the advertisement from the STT, responsive to a specific value of the counter.
RELATED APPLICATIONS

This application is a divisional of U.S. patent application Ser. No. 10/073,842 filed Feb. 11, 2002, now U.S. Pat. No. 7,334,251.

US Referenced Citations (573)
Number Name Date Kind
3676580 Beck Jul 1972 A
4586158 Brandle Apr 1986 A
4706121 Young Nov 1987 A
4751578 Reiter et al. Jun 1988 A
4821097 Robbins Apr 1989 A
4827250 Stallkamp May 1989 A
4885775 Lucas Dec 1989 A
4908713 Levine Mar 1990 A
4930158 Vogel May 1990 A
4949187 Cohen Aug 1990 A
4963994 Levine Oct 1990 A
4984152 Mueller Jan 1991 A
4991011 Johnson et al. Feb 1991 A
5038211 Hallenbeck Aug 1991 A
5172413 Bradley et al. Dec 1992 A
5191410 McCalley et al. Mar 1993 A
5253066 Vogel Oct 1993 A
5291554 Morales Mar 1994 A
5293357 Hallenbeck Mar 1994 A
5317391 Banker et al. May 1994 A
5329590 Pond Jul 1994 A
5353121 Young et al. Oct 1994 A
5357276 Banker et al. Oct 1994 A
5359362 Lewis et al. Oct 1994 A
5371551 Logan et al. Dec 1994 A
5398071 Gove et al. Mar 1995 A
5410326 Goldstein Apr 1995 A
5410343 Coddington et al. Apr 1995 A
5410344 Graves et al. Apr 1995 A
5414455 Hooper et al. May 1995 A
5418622 Takeuchi May 1995 A
5448313 Kim et al. Sep 1995 A
5477262 Banker et al. Dec 1995 A
5479268 Young et al. Dec 1995 A
5481542 Logston et al. Jan 1996 A
5483277 Granger Jan 1996 A
5485216 Lee Jan 1996 A
5493638 Hooper et al. Feb 1996 A
5508815 Levine Apr 1996 A
5512958 Rzeszewski Apr 1996 A
5515495 Ikemoto May 1996 A
5521631 Budow et al. May 1996 A
5530754 Garfinkle Jun 1996 A
5532735 Blahut et al. Jul 1996 A
5532754 Young et al. Jul 1996 A
5544354 May et al. Aug 1996 A
5555441 Haddad Sep 1996 A
5557541 Schulhof et al. Sep 1996 A
5562732 Eisenberg Oct 1996 A
5568272 Levine Oct 1996 A
5583560 Florin et al. Dec 1996 A
5583995 Gardner et al. Dec 1996 A
5585821 Ishikura et al. Dec 1996 A
5585838 Lawler et al. Dec 1996 A
5589892 Knee et al. Dec 1996 A
5592551 Lett et al. Jan 1997 A
5594509 Florin et al. Jan 1997 A
5598524 Johnston, Jr. et al. Jan 1997 A
5600364 Hendricks et al. Feb 1997 A
5600573 Hendricks et al. Feb 1997 A
5614940 Cobbley et al. Mar 1997 A
5619247 Russo Apr 1997 A
5619249 Billock et al. Apr 1997 A
5621456 Florin et al. Apr 1997 A
5623613 Rowe et al. Apr 1997 A
5625405 DuLac et al. Apr 1997 A
5625864 Budow et al. Apr 1997 A
5629732 Moskowitz et al. May 1997 A
5631693 Wunderlich et al. May 1997 A
5632681 Bakoglu et al. May 1997 A
5635979 Kostreski et al. Jun 1997 A
5635980 Lin et al. Jun 1997 A
5635989 Rothmuller Jun 1997 A
5650831 Farwell Jul 1997 A
5659350 Hendricks et al. Aug 1997 A
5666293 Metz et al. Sep 1997 A
5671411 Watts et al. Sep 1997 A
5675752 Scott et al. Oct 1997 A
5682206 Wehmeyer et al. Oct 1997 A
5682597 Ganek et al. Oct 1997 A
5684918 Abecassis Nov 1997 A
5686954 Yoshinobu et al. Nov 1997 A
5687331 Volk et al. Nov 1997 A
5689641 Ludwig et al. Nov 1997 A
5694176 Bruette et al. Dec 1997 A
5694546 Reisman Dec 1997 A
5699107 Lawler et al. Dec 1997 A
5715169 Noguchi Feb 1998 A
5715515 Akins, III et al. Feb 1998 A
5721827 Logan et al. Feb 1998 A
5721829 Dunn et al. Feb 1998 A
5721897 Rubinstein Feb 1998 A
5724106 Autry et al. Mar 1998 A
5724521 Dedrick Mar 1998 A
5724646 Ganek et al. Mar 1998 A
5727060 Young Mar 1998 A
5729549 Kostreski et al. Mar 1998 A
5732216 Logan et al. Mar 1998 A
5734853 Hendricks et al. Mar 1998 A
5737028 Bertram et al. Apr 1998 A
5740304 Katsuyama et al. Apr 1998 A
5740549 Reilly et al. Apr 1998 A
5745837 Fuhrmann Apr 1998 A
5748493 Lightfoot et al. May 1998 A
5751282 Girard et al. May 1998 A
5752160 Dunn May 1998 A
5754773 Ozden et al. May 1998 A
5764873 Magid et al. Jun 1998 A
5764899 Eggleston et al. Jun 1998 A
5771435 Brown Jun 1998 A
5774170 Hite et al. Jun 1998 A
5778077 Davidson Jul 1998 A
5790170 Suzuki Aug 1998 A
5790176 Craig Aug 1998 A
5790935 Payton Aug 1998 A
5790940 Laborde et al. Aug 1998 A
5796828 Tsukamoto et al. Aug 1998 A
5798785 Hendricks et al. Aug 1998 A
5799063 Krane Aug 1998 A
5801747 Bedard Sep 1998 A
5801787 Schein et al. Sep 1998 A
5802502 Gell et al. Sep 1998 A
5808608 Young et al. Sep 1998 A
5808611 Johnson et al. Sep 1998 A
5809204 Young et al. Sep 1998 A
5812123 Rowe et al. Sep 1998 A
5812124 Eick et al. Sep 1998 A
5812786 Seazholtz et al. Sep 1998 A
5822123 Davis et al. Oct 1998 A
5826110 Ozden et al. Oct 1998 A
5828419 Bruette et al. Oct 1998 A
5828845 Jagadish et al. Oct 1998 A
5835843 Haddad Nov 1998 A
5838314 Neel et al. Nov 1998 A
5844620 Coleman et al. Dec 1998 A
5848352 Dougherty et al. Dec 1998 A
5850218 LaJoie et al. Dec 1998 A
5856975 Rostoker et al. Jan 1999 A
5859641 Cave Jan 1999 A
5861906 Dunn et al. Jan 1999 A
5877756 Um Mar 1999 A
5880768 Lemmons et al. Mar 1999 A
5886690 Pond et al. Mar 1999 A
5886732 Humpleman Mar 1999 A
5895454 Harrington Apr 1999 A
5898456 Wahl Apr 1999 A
5900905 Shoff et al. May 1999 A
5905522 Lawler May 1999 A
5905942 Stoel et al. May 1999 A
5907323 Lawler et al. May 1999 A
5913040 Rakavy et al. Jun 1999 A
5914712 Sartain et al. Jun 1999 A
5914746 Matthews, III et al. Jun 1999 A
5915068 Levine Jun 1999 A
5917822 Lyles et al. Jun 1999 A
5929849 Kikinis Jul 1999 A
5930493 Ottesen et al. Jul 1999 A
5935206 Dixon et al. Aug 1999 A
5936659 Viswanathan Aug 1999 A
5940073 Klosterman et al. Aug 1999 A
5943047 Suzuki Aug 1999 A
5956024 Strickland et al. Sep 1999 A
5956716 Kenner et al. Sep 1999 A
5960411 Hartman et al. Sep 1999 A
5961603 Kunkel et al. Oct 1999 A
5969748 Casement et al. Oct 1999 A
5978043 Blonstein et al. Nov 1999 A
5983273 White et al. Nov 1999 A
5986650 Ellis et al. Nov 1999 A
5987256 Wu et al. Nov 1999 A
5990881 Inoue et al. Nov 1999 A
5990890 Etheredge Nov 1999 A
5990927 Hendricks et al. Nov 1999 A
5995134 Hayashi Nov 1999 A
6002401 Baker Dec 1999 A
6005565 Legall et al. Dec 1999 A
6005631 Anderson et al. Dec 1999 A
6006257 Slezak Dec 1999 A
6008803 Rowe et al. Dec 1999 A
6008836 Bruck et al. Dec 1999 A
6014184 Knee et al. Jan 2000 A
6014694 Aharoni et al. Jan 2000 A
6016348 Blatter et al. Jan 2000 A
6018359 Kermode Jan 2000 A
6018372 Etheredge Jan 2000 A
6020912 De Lang Feb 2000 A
6023267 Chapuis et al. Feb 2000 A
6025837 Matthews, III et al. Feb 2000 A
6025868 Russo Feb 2000 A
6025869 Stas et al. Feb 2000 A
6026376 Kenney Feb 2000 A
6035281 Crosskey et al. Mar 2000 A
6037933 Blonstein et al. Mar 2000 A
6049831 Gardell et al. Apr 2000 A
6057872 Candelore May 2000 A
6061097 Satterfield May 2000 A
6064380 Swenson et al. May 2000 A
6064980 Jacobi et al. May 2000 A
6070186 Nishio May 2000 A
6072982 Haddad Jun 2000 A
6073105 Sutcliffe et al. Jun 2000 A
6075575 Schein et al. Jun 2000 A
6081263 LeGall et al. Jun 2000 A
6085185 Matsuzawa et al. Jul 2000 A
6094680 Hokanson Jul 2000 A
6097383 Gaughan et al. Aug 2000 A
6098082 Gibbon et al. Aug 2000 A
6101512 DeRose et al. Aug 2000 A
6108002 Ishizaki Aug 2000 A
6108042 Adams et al. Aug 2000 A
6118445 Nonomura et al. Sep 2000 A
6118976 Arias et al. Sep 2000 A
6124878 Adams et al. Sep 2000 A
6125259 Perlman Sep 2000 A
6133909 Schein et al. Oct 2000 A
6137539 Lownes et al. Oct 2000 A
6138139 Beck et al. Oct 2000 A
6141003 Chor et al. Oct 2000 A
6141488 Knudson et al. Oct 2000 A
6145083 Shaffer et al. Nov 2000 A
6148332 Brewer et al. Nov 2000 A
6151059 Schein et al. Nov 2000 A
6157377 Shah-Nazaroff et al. Dec 2000 A
6157413 Hanafee et al. Dec 2000 A
6160546 Thompson et al. Dec 2000 A
6160989 Hendricks et al. Dec 2000 A
6163272 Goode et al. Dec 2000 A
6166730 Goode et al. Dec 2000 A
6169543 Wehmeyer Jan 2001 B1
6172674 Etheredge Jan 2001 B1
6172677 Stautner et al. Jan 2001 B1
6177931 Alexander et al. Jan 2001 B1
6181333 Chaney et al. Jan 2001 B1
6181693 Maresca Jan 2001 B1
6182287 Schneidewend et al. Jan 2001 B1
6184877 Dodson et al. Feb 2001 B1
6188684 Setoyama et al. Feb 2001 B1
6195689 Bahlmann Feb 2001 B1
6201540 Gallup et al. Mar 2001 B1
6205485 Kikinis Mar 2001 B1
6208335 Gordon et al. Mar 2001 B1
6209130 Rector et al. Mar 2001 B1
6216264 Maze et al. Apr 2001 B1
6238290 Tarr et al. May 2001 B1
6239845 Itagaki et al. May 2001 B1
6240555 Shoff et al. May 2001 B1
6243142 Mugura et al. Jun 2001 B1
6249532 Yoshikawa et al. Jun 2001 B1
6253375 Gordon et al. Jun 2001 B1
6259733 Kaye et al. Jul 2001 B1
6266814 Lemmons et al. Jul 2001 B1
6268849 Boyer et al. Jul 2001 B1
6272484 Martin et al. Aug 2001 B1
6275268 Ellis et al. Aug 2001 B1
6282713 Kitsukawa et al. Aug 2001 B1
6289346 Milewski et al. Sep 2001 B1
6289514 Link et al. Sep 2001 B1
6292624 Saib et al. Sep 2001 B1
6305019 Dyer et al. Oct 2001 B1
6311011 Kuroda Oct 2001 B1
6314572 LaRocca et al. Nov 2001 B1
6314573 Gordon et al. Nov 2001 B1
6314575 Billock et al. Nov 2001 B1
6317777 Skarbo et al. Nov 2001 B1
6317885 Fries Nov 2001 B1
6323911 Schein et al. Nov 2001 B1
6327628 Anuff et al. Dec 2001 B1
6335936 Bossemeyer, Jr. et al. Jan 2002 B1
6347400 Ohkura et al. Feb 2002 B1
6349410 Lortz Feb 2002 B1
6353448 Scarborough et al. Mar 2002 B1
6357046 Thompson et al. Mar 2002 B1
6359636 Schindler et al. Mar 2002 B1
6360367 Yamamoto Mar 2002 B1
6362841 Nykanen Mar 2002 B1
6367078 Lasky Apr 2002 B1
6378130 Adams Apr 2002 B1
6381332 Glaab Apr 2002 B1
6385614 Vellandi May 2002 B1
6393585 Houha et al. May 2002 B1
6396549 Weber May 2002 B1
6400280 Osakabe Jun 2002 B1
6401243 Suzuki Jun 2002 B1
6405239 Addington et al. Jun 2002 B1
6421067 Kamen et al. Jul 2002 B1
6429899 Nio et al. Aug 2002 B1
6434748 Shen et al. Aug 2002 B1
6441862 Yuen et al. Aug 2002 B1
6442332 Knudson et al. Aug 2002 B1
6442755 Lemmons et al. Aug 2002 B1
6442756 Durden et al. Aug 2002 B1
6446261 Rosser Sep 2002 B1
6446262 Malaure et al. Sep 2002 B1
6460181 Donnelly Oct 2002 B1
6463585 Hendricks et al. Oct 2002 B1
6476833 Moshfeghi Nov 2002 B1
6480669 Tsumagari et al. Nov 2002 B1
6481010 Nishikawa et al. Nov 2002 B2
6481011 Lemmons Nov 2002 B1
6486920 Arai et al. Nov 2002 B2
6501902 Wang Dec 2002 B1
6505348 Knowles et al. Jan 2003 B1
6507949 Jonason et al. Jan 2003 B1
6510556 Kusaba et al. Jan 2003 B1
6515680 Hendricks et al. Feb 2003 B1
6515710 Koshimuta Feb 2003 B1
6519770 Ford Feb 2003 B2
6526575 McCoy et al. Feb 2003 B1
6526577 Knudson et al. Feb 2003 B1
6532589 Proehl et al. Mar 2003 B1
6536041 Knudson et al. Mar 2003 B1
6539548 Hendricks et al. Mar 2003 B1
6543053 Li et al. Apr 2003 B1
6545669 Kinawi et al. Apr 2003 B1
6557030 Hoang Apr 2003 B1
6563515 Reynolds et al. May 2003 B1
6564378 Satterfield et al. May 2003 B1
6564379 Knudson et al. May 2003 B1
6564383 Combs et al. May 2003 B1
6571390 Dunn et al. May 2003 B1
6574793 Ngo et al. Jun 2003 B1
6578077 Rakoshitz et al. Jun 2003 B1
6594699 Sahai et al. Jul 2003 B1
6594825 Goldschmidt Iki et al. Jul 2003 B1
6600496 Wagner et al. Jul 2003 B1
6604240 Ellis et al. Aug 2003 B2
6609253 Swix et al. Aug 2003 B1
6611958 Shintani et al. Aug 2003 B1
6614440 Bowen et al. Sep 2003 B1
6614988 Sampsell Sep 2003 B1
6628302 White et al. Sep 2003 B2
6631413 Aggarwal et al. Oct 2003 B1
6642939 Vallone et al. Nov 2003 B1
6647548 Lu et al. Nov 2003 B1
6651044 Stoneman Nov 2003 B1
6662365 Sullivan et al. Dec 2003 B1
6665869 Ellis et al. Dec 2003 B1
6671328 Poon et al. Dec 2003 B1
6675384 Block et al. Jan 2004 B1
6675385 Wang Jan 2004 B1
6678891 Wilcox et al. Jan 2004 B1
6681395 Nishi Jan 2004 B1
6681396 Bates et al. Jan 2004 B1
6684025 Perlman Jan 2004 B1
6684400 Goode et al. Jan 2004 B1
6697376 Son et al. Feb 2004 B1
6698023 Levitan Feb 2004 B2
6701523 Hancock et al. Mar 2004 B1
6701528 Arsenault et al. Mar 2004 B1
6706311 Wong et al. Mar 2004 B2
6708336 Bruette Mar 2004 B1
6717590 Sullivan et al. Apr 2004 B1
6718552 Goode Apr 2004 B1
6725461 Dougherty et al. Apr 2004 B1
6731310 Craycroft et al. May 2004 B2
6732367 Ellis et al. May 2004 B1
6732369 Schein et al. May 2004 B1
6732372 Tomita et al. May 2004 B2
6735572 Landesmann May 2004 B2
6738982 Jerding May 2004 B1
6757909 Maruo et al. Jun 2004 B1
6760918 Rodriguez et al. Jul 2004 B2
6769127 Bonomi et al. Jul 2004 B1
6771290 Hoyle Aug 2004 B1
6772209 Chernock et al. Aug 2004 B1
6772433 LaJoie et al. Aug 2004 B1
6782550 Cao Aug 2004 B1
6791620 Elswick et al. Sep 2004 B1
6792615 Rowe et al. Sep 2004 B1
6801533 Barkley Oct 2004 B1
6817028 Jerding et al. Nov 2004 B1
6832386 Jerding et al. Dec 2004 B1
6847969 Mathai et al. Jan 2005 B1
6876628 Howard et al. Apr 2005 B2
6898762 Ellis et al. May 2005 B2
6901385 Okamoto et al. May 2005 B2
6957386 Nishina et al. Oct 2005 B2
6968372 Thompson et al. Nov 2005 B1
6978310 Rodriguez et al. Dec 2005 B1
6978475 Kunin et al. Dec 2005 B1
6986156 Rodriguez et al. Jan 2006 B1
6990676 Proehl et al. Jan 2006 B1
6990677 Pietraszak et al. Jan 2006 B1
6993782 Newberry et al. Jan 2006 B1
7010801 Jerding et al. Mar 2006 B1
7024681 Fransman et al. Apr 2006 B1
7039944 Cho et al. May 2006 B1
7062466 Wagner et al. Jun 2006 B2
7076734 Wolff et al. Jul 2006 B2
7086077 Giammaressi Aug 2006 B2
7103903 Kydd Sep 2006 B1
7110714 Kay et al. Sep 2006 B1
7117440 Gordon et al. Oct 2006 B2
7120926 Safadi et al. Oct 2006 B1
7143430 Fingerman et al. Nov 2006 B1
7150031 Rodriguez et al. Dec 2006 B1
7155733 Rodriguez et al. Dec 2006 B2
7180422 Milenkovic et al. Feb 2007 B2
7185355 Ellis et al. Feb 2007 B1
7188356 Miura et al. Mar 2007 B1
7194757 Fish et al. Mar 2007 B1
7200857 Rodriguez et al. Apr 2007 B1
7237251 Oz et al. Jun 2007 B1
7243364 Dunn et al. Jul 2007 B2
7249366 Flavin Jul 2007 B1
7324552 Galand et al. Jan 2008 B1
7324553 Varier et al. Jan 2008 B1
7334251 Rodriguez et al. Feb 2008 B2
7340759 Rodriguez Mar 2008 B1
7343614 Hendricks et al. Mar 2008 B1
7356477 Allan et al. Apr 2008 B1
7404200 Hailey et al. Jul 2008 B1
7496943 Goldberg et al. Feb 2009 B1
7496945 Rodriguez Feb 2009 B2
7509267 Yarmolich et al. Mar 2009 B1
7512964 Rodriguez et al. Mar 2009 B2
7526788 Rodriguez Apr 2009 B2
7647549 Denoual et al. Jan 2010 B2
7673314 Ellis et al. Mar 2010 B2
7685520 Rashkovskiy et al. Mar 2010 B2
7707614 Krikorian et al. Apr 2010 B2
7925534 Amano et al. Apr 2011 B2
7934232 Jerding et al. Apr 2011 B1
7961643 McDonald et al. Jun 2011 B2
7962370 Rodriguez et al. Jun 2011 B2
8005713 Sanz-Pastor et al. Aug 2011 B1
20010003846 Rowe et al. Jun 2001 A1
20010013125 Kitsukawa et al. Aug 2001 A1
20010013127 Tomita et al. Aug 2001 A1
20010029523 Mcternan et al. Oct 2001 A1
20010030667 Kelts Oct 2001 A1
20010032335 Jones Oct 2001 A1
20010034763 Jacobs et al. Oct 2001 A1
20010036271 Javed Nov 2001 A1
20010044744 Rhoads Nov 2001 A1
20020002642 Tyson et al. Jan 2002 A1
20020007485 Rodriguez et al. Jan 2002 A1
20020013836 Friedman et al. Jan 2002 A1
20020026496 Boyer et al. Feb 2002 A1
20020026638 Eldering et al. Feb 2002 A1
20020032638 Arora et al. Mar 2002 A1
20020032728 Sako et al. Mar 2002 A1
20020032905 Sherr et al. Mar 2002 A1
20020042913 Ellis et al. Apr 2002 A1
20020044762 Wood et al. Apr 2002 A1
20020049804 Rodriguez et al. Apr 2002 A1
20020049978 Rodriguez et al. Apr 2002 A1
20020056098 White May 2002 A1
20020056118 Hunter et al. May 2002 A1
20020057336 Gaul et al. May 2002 A1
20020062481 Slaney et al. May 2002 A1
20020069105 do Rosario Botelho et al. Jun 2002 A1
20020069218 Sull et al. Jun 2002 A1
20020069412 Philips Jun 2002 A1
20020078176 Nomura et al. Jun 2002 A1
20020083443 Eldering et al. Jun 2002 A1
20020087981 Daniels Jul 2002 A1
20020101367 Geiger et al. Aug 2002 A1
20020104083 Hendricks et al. Aug 2002 A1
20020108125 Joao Aug 2002 A1
20020124249 Shintani et al. Sep 2002 A1
20020128908 Levin et al. Sep 2002 A1
20020129362 Chang et al. Sep 2002 A1
20030002862 Rodriguez et al. Jan 2003 A1
20030014753 Beach et al. Jan 2003 A1
20030030679 Jain Feb 2003 A1
20030031465 Blake Feb 2003 A1
20030037068 Thomas et al. Feb 2003 A1
20030037332 Chapin et al. Feb 2003 A1
20030061619 Giammaressi Mar 2003 A1
20030067554 Klarfeld et al. Apr 2003 A1
20030074214 Kelliher Apr 2003 A1
20030074257 Saveliev et al. Apr 2003 A1
20030079227 Knowles et al. Apr 2003 A1
20030088872 Maissel et al. May 2003 A1
20030101451 Bentolila et al. May 2003 A1
20030101454 Ozer et al. May 2003 A1
20030124973 Sie et al. Jul 2003 A1
20030126425 Yang et al. Jul 2003 A1
20030131356 Proehl et al. Jul 2003 A1
20030135853 Goldman et al. Jul 2003 A1
20030154475 Rodriguez et al. Aug 2003 A1
20030154486 Dunn et al. Aug 2003 A1
20030159147 Young et al. Aug 2003 A1
20030174243 Arbeiter et al. Sep 2003 A1
20030188313 Ellis et al. Oct 2003 A1
20030193486 Estrop Oct 2003 A1
20030206553 Surcouf et al. Nov 2003 A1
20030219228 Thiagarajan et al. Nov 2003 A1
20030221194 Thiagarajan et al. Nov 2003 A1
20040034867 Rashkovskiy et al. Feb 2004 A1
20040049787 Maissel et al. Mar 2004 A1
20040107436 Ishizaki Jun 2004 A1
20040117831 Ellis et al. Jun 2004 A1
20040128685 Hassell et al. Jul 2004 A1
20040133907 Rodriguez et al. Jul 2004 A1
20040163117 Rodriguez et al. Aug 2004 A1
20040168191 Jerding et al. Aug 2004 A1
20040181801 Hagen et al. Sep 2004 A1
20040221310 Herrington et al. Nov 2004 A1
20040261112 Hicks et al. Dec 2004 A1
20040261125 Ellis et al. Dec 2004 A1
20050008074 van Beek et al. Jan 2005 A1
20050044565 Jerding et al. Feb 2005 A1
20050044566 Jerding et al. Feb 2005 A1
20050044577 Jerding et al. Feb 2005 A1
20050071882 Rodriguez et al. Mar 2005 A1
20050076360 Jerding et al. Apr 2005 A1
20050091693 Amine et al. Apr 2005 A1
20050111046 Kurumisawa et al. May 2005 A1
20050138657 Leftwich Jun 2005 A1
20050155056 Knee et al. Jul 2005 A1
20050160468 Rodriguez et al. Jul 2005 A1
20050188415 Riley Aug 2005 A1
20050204387 Knudson et al. Sep 2005 A1
20050204388 Knudson et al. Sep 2005 A1
20050213506 Wakumoto et al. Sep 2005 A1
20050216936 Knudson et al. Sep 2005 A1
20050240961 Jerding et al. Oct 2005 A1
20050251822 Knowles et al. Nov 2005 A1
20050278741 Robarts et al. Dec 2005 A1
20050283797 Eldering et al. Dec 2005 A1
20050283810 Ellis et al. Dec 2005 A1
20050289618 Hardin Dec 2005 A1
20060020982 Jerding et al. Jan 2006 A1
20060026080 Rodriguez et al. Feb 2006 A1
20060026665 Rodriguez et al. Feb 2006 A1
20060059525 Jerding et al. Mar 2006 A1
20060070107 Renkis Mar 2006 A1
20060088105 Shen et al. Apr 2006 A1
20060112434 Banker et al. May 2006 A1
20060206913 Jerding et al. Sep 2006 A1
20060271933 Agassi et al. Nov 2006 A1
20060271964 Rodriguez et al. Nov 2006 A1
20060271973 Jerding et al. Nov 2006 A1
20070019670 Falardeau Jan 2007 A1
20070053293 McDonald et al. Mar 2007 A1
20070094690 Rodriguez et al. Apr 2007 A1
20070136748 Rodriguez et al. Jun 2007 A1
20070186240 Ward, III et al. Aug 2007 A1
20080010658 Abbott et al. Jan 2008 A1
20080098421 Rodriguez et al. Apr 2008 A1
20080098422 Rodriguez et al. Apr 2008 A1
20080101460 Rodriguez May 2008 A1
20080104637 Rodriguez et al. May 2008 A1
20080137755 Onur et al. Jun 2008 A1
20080155631 Liwerant et al. Jun 2008 A1
20080229361 Jerding et al. Sep 2008 A1
20080279217 McDonald et al. Nov 2008 A1
20080281968 Rodriguez Nov 2008 A1
20080282307 McDonald et al. Nov 2008 A1
20080282308 McDonald et al. Nov 2008 A1
20090141794 Rodriguez et al. Jun 2009 A1
20090150958 Jerding et al. Jun 2009 A1
20090158306 Rodriguez et al. Jun 2009 A1
20090158324 Rodriguez et al. Jun 2009 A1
20090158329 Rodriguez et al. Jun 2009 A1
20090158331 Rodriguez et al. Jun 2009 A1
20090158332 Rodriguez et al. Jun 2009 A1
20090158335 Rodriguez et al. Jun 2009 A1
20090158339 Rodriguez et al. Jun 2009 A1
20090158352 Rodriguez et al. Jun 2009 A1
20090158354 Rodriguez et al. Jun 2009 A1
20090158355 Rodriguez et al. Jun 2009 A1
20090158363 Rodriguez et al. Jun 2009 A1
20090183081 Rodriguez et al. Jul 2009 A1
20090190028 Rodriguez et al. Jul 2009 A1
20090193468 Rodriguez Jul 2009 A1
20090193471 Rodriguez Jul 2009 A1
20090276808 Jerding et al. Nov 2009 A1
20090282372 Jerding et al. Nov 2009 A1
20090282440 Rodriguez Nov 2009 A1
20100242063 Slaney et al. Sep 2010 A1
Foreign Referenced Citations (93)
Number Date Country
2 363 052 Nov 1995 CA
2 223 025 Nov 2001 CA
2 475 723 Jan 2011 CA
0 572 090 Dec 1993 EP
0 673 159 Sep 1995 EP
0 680 214 Nov 1995 EP
0 725 538 Aug 1996 EP
0 763 936 Mar 1997 EP
0 811 939 Dec 1997 EP
0 838 915 Apr 1998 EP
0 849 948 Jun 1998 EP
0 854 645 Jul 1998 EP
0 891 084 Jan 1999 EP
0 896 318 Feb 1999 EP
0 909 095 Apr 1999 EP
0 701 756 Dec 1999 EP
0 989 751 Mar 2000 EP
1 069 801 Jan 2001 EP
1 075 143 Feb 2001 EP
1 111 572 Jun 2001 EP
1 161 085 Dec 2001 EP
2 343 051 Apr 2000 GB
8-289219 Nov 1996 JP
9-322022 Dec 1997 JP
10-143734 May 1998 JP
11-73361 Mar 1999 JP
11-73394 Mar 1999 JP
11-164284 Jun 1999 JP
2000-101941 Apr 2000 JP
WO 9222983 Dec 1992 WO
WO 9414284 Jun 1994 WO
WO 9617467 Jun 1996 WO
WO 9633579 Oct 1996 WO
WO 9634486 Oct 1996 WO
WO 9634491 Oct 1996 WO
WO 9641477 Dec 1996 WO
WO 9641478 Dec 1996 WO
WO 9734414 Sep 1997 WO
WO 9803012 Jan 1998 WO
WO 9826528 Jun 1998 WO
WO 9831116 Jul 1998 WO
WO 9837695 Aug 1998 WO
WO 9839893 Sep 1998 WO
WO 9848566 Oct 1998 WO
WO 9856172 Dec 1998 WO
WO 9856173 Dec 1998 WO
WO 9856188 Dec 1998 WO
WO 9901984 Jan 1999 WO
WO 9904560 Jan 1999 WO
WO 9904561 Jan 1999 WO
WO 9912109 Mar 1999 WO
WO 9914947 Mar 1999 WO
WO 9935831 Jul 1999 WO
WO 9945701 Sep 1999 WO
WO 9949717 Oct 1999 WO
WO 9952285 Oct 1999 WO
WO 9957903 Nov 1999 WO
WO 9960790 Nov 1999 WO
WO 9966719 Dec 1999 WO
WO 0002385 Jan 2000 WO
WO 0004726 Jan 2000 WO
WO 0005889 Feb 2000 WO
WO 0030354 May 2000 WO
WO 0040017 Jul 2000 WO
WO 0046988 Aug 2000 WO
WO 0049801 Aug 2000 WO
WO 0059202 Oct 2000 WO
WO 0060482 Oct 2000 WO
WO 0078031 Dec 2000 WO
WO 0078045 Dec 2000 WO
WO 0078047 Dec 2000 WO
WO 0078048 Dec 2000 WO
WO 0106788 Jan 2001 WO
WO 0120907 Mar 2001 WO
WO 0124067 Apr 2001 WO
WO 0156273 Aug 2001 WO
WO 0167736 Sep 2001 WO
WO 0172042 Sep 2001 WO
WO 0176245 Oct 2001 WO
WO 0177888 Oct 2001 WO
WO 0184831 Nov 2001 WO
WO 02097584 Dec 2002 WO
WO 03003164 Jan 2003 WO
WO 03003709 Jan 2003 WO
WO 03014873 Feb 2003 WO
WO 03024084 Mar 2003 WO
WO 03042787 May 2003 WO
WO 03069898 Aug 2003 WO
WO 2004091219 Oct 2004 WO
WO 2004100500 Nov 2004 WO
WO 2005059202 Jun 2005 WO
WO 2005071658 Aug 2005 WO
WO 2007030370 Mar 2007 WO
Non-Patent Literature Citations (363)
Entry
“A Brief History of the Trailer,” http://www.movietrailertrash.com/views/history.html, 11 pages (Publicly known at least as early as Dec. 20, 2003).
“Client User Interface Specification (Phase I) for Video-On-Demand Application Development on the Explorer 2000™ Digital Home Communications Terminal”, Revision 1.10 (Aug. 31, 1998).
“Evidence of illustrative movie release years,” Retrieved from the Internet Movie Database using Internet, http://www.imdb.com, 19 pages (Retrieved on Jun. 6, 2005).
“ISO/IEC 13818-6 Information technology—Generic coding of moving pictures and associated audio information—Part 6: Extensions for DSM-CC,” Chapter 4, 113 pages (Sep. 1, 1998).
“Netcaster Developer's Guide,” Devedge Online Documentation, Netscape Communications Corporation, http://developer.netscape.com/docs/manuals/netcast/devguide/ index.html, XP-002166370, 82 pages (Sep. 25, 1997).
“Netscape Navigator Help,” Netscape Navigator Software User Documentation, Netscape Communications Corporation, http://home.netscape.com, XP-002166369, pp. 1-63 (Aug. 10, 1997).
“Sez You . . . origin of word daemon,” Take Our Word For It, Issue 146, p. 4, http://www.takeourword.com/TOW146/page4.html (retrieved on Apr. 4, 2006).
Addington, Timothy H., “System Architecture Specification for Video-On-Demand Application Development on the Explorer 2000™ Digital Home Communications Terminal”, Revision 1.10r Review Copy (Mar. 4, 1999).
Alberico, G. et al., “Satellite Interactive Multimedia: A New Opportunity for Broadcasters,” International Broadcasting Convention, Conference Publication No. 447, pp. 18-23 (Sep. 12-16, 1997).
ATI Multimedia Center 7.9, User's Guide, ATI Technologies Inc., pp. i-vi and 1-96 (Copyright 2002).
Barth et al., “10 Fernsehen am PC”, Suse GMBH, XP-002324319, pp. 143-149 (2001).
BPAI Decision for U.S. Appl. No. 09/692,995, mailed Aug. 20, 2008.
BPAI Decision for U.S. Appl. No. 09/693,288, mailed Nov. 28, 2007.
Canadian Office Action cited in Application No. 2,376,556 mailed Sep. 30, 2008.
Canadian Office Action cited in Application No. 2,376,556 mailed Nov. 23, 2007.
Canadian Office Action cited in Application No. 2,376,556 mailed Dec. 6, 2005.
Canadian Office Action cited in Application No. 2,402,088 mailed May 30, 2006.
Canadian Office Action cited in Application No. 2,405,491 mailed Apr. 3, 2009.
Canadian Office Action cited in Application No. 2,405,491 mailed May 22, 2008.
Canadian Office Action cited in Application No. 2,405,491 mailed Jun. 20, 2007.
Canadian Office Action cited in Application No. 2,405,491 mailed Jan. 20, 2006.
Canadian Office Action cited in Application No. 2,408,289 mailed Aug. 27, 2008.
Canadian Office Action cited in Application No. 2,408,289 mailed May 30, 2006.
Canadian Office Action cited in Application No. 2,451,477 mailed Nov. 3, 2009.
Canadian Office Action cited in Application No. 2,456,318 mailed May 5, 2008.
Canadian Office Action cited in Application No. 2,456,318 mailed Mar. 27, 2007.
Canadian Office Action cited in Application No. 2,459,334 mailed Apr. 16, 2009.
Canadian Office Action cited in Application No. 2,466,667 mailed Apr. 15, 2009.
Canadian Office Action cited in Application No. 2,475,723 mailed Jul. 7, 2009.
Canadian Office Action cited in Application No. 2,554,208 mailed Apr. 1, 2010.
Canadian Office Action cited in Application No. 2,621,605 mailed Dec. 15, 2009.
Cunningham et al., “5 Das X Window System”., Suse GMBH, XP-002324320, pp. 129-180 (2001).
Decision on Appeal affirmed cited in U.S. Appl. No. 09/590,434 mailed May 28, 2008.
Definition of “flag”, Microsoft Press: Computer User's Dictionary, 3 pages (1998).
Definition of “renting”, Webster's II: New College Dictionary, 1995, Houghton Mifflin Company, p. 939.
European Examination Report cited in Application No. 00 938 251.6 mailed Mar. 2, 2010.
European Examination Report cited in Application No. 00 938 251.6 mailed Nov. 2, 2007.
European Examination Report cited in Application No. 00 939 759.7 mailed May 10, 2007.
European Examination Report cited in Application No. 01 905 058.2 mailed Dec. 19, 2006.
European Examination Report cited in Application No. 01 922 261.1 mailed Jul. 18, 2008.
European Examination Report cited in Application No. 01 922 261.1 mailed Nov. 2, 2007.
European Examination Report cited in Application No. 01 922 261.1 mailed Jan. 24, 2007.
European Examination Report cited in Application No. 01 922 261.1 mailed May 26, 2006.
European Examination Report cited in Application No. 01 923 092.9 mailed Jul. 20, 2009.
European Examination Report cited in Application No. 01 923 092.9 mailed Nov. 27, 2008.
European Examination Report cited in Application No. 01 937 209.3 mailed Mar. 16, 2010.
European Examination Report cited in Application No. 01 937 209.3 mailed Jun. 23, 2008.
European Examination Report cited in Application No. 02 737 593.0 mailed May 6, 2009.
European Examination Report cited in Application No. 02 750 416.6 mailed Aug. 4, 2008.
European Examination Report cited in Application No. 02 750 416.6 mailed Aug. 28, 2007.
European Examination Report cited in Application No. 02 761 572.3 mailed Apr. 20, 2009.
European Examination Report cited in Application No. 02 761 572.3 mailed Sep. 22, 2008.
European Examination Report cited in Application No. 02 761 572.3 mailed Jan. 22, 2008.
European Examination Report cited in Application No. 02 761 572.3 mailed Aug. 29, 2007.
European Examination Report cited in Application No. 06 802 683.0 mailed Jun. 26, 2008.
Examiner's Answer to Appeal Brief cited in U.S. Appl. No. 09/590,488 mailed Jan. 11, 2008.
Japanese Office Action cited in Application No. 2001-581527 mailed Feb. 10, 2010.
Japanese Office Action cited in Application No. 2001-581527 mailed Sep. 8, 2009.
Kevin, “Change Screen Resolution in Windows (Tips, Tricks, Tweaks, and Setting),” http://www.tacktech.com/display.cfm?ttid=207, pp. 1-3 (Oct. 26, 2002).
Leftwitch et al., “StarSight Interactive Television Program Guide—Functional/Interational Architecture Specification Document, Interaction Analysis and Design Project—Phase III,” 36 pages.
Little et al., “Prospects for Interactive Video-On-Demand”, IEEE Multimedia, IEEE Service Center, New York, NY US, vol. 1 No. 3, Sep. 1994, pp. 14-24, XP000476885 ISSN: 1070-986X.
McFedries, “The Complete Idiot's Guide to Windows 95,” Que, 2nd Edition, p. 49 (1997).
PCT Search Report cited in International Application No. PCT/US00/15952 mailed Jan. 16, 2001.
PCT Search Report cited in International Application No. PCT/US00/15963 mailed Sep. 1, 2000.
PCT Search Report cited in International Application No. PCT/US00/16000 mailed Oct. 2, 2000.
PCT Search Report cited in International Application No. PCT/US01/02490 mailed May 18, 2001.
PCT Search Report cited in International Application No. PCT/US01/06663 mailed Oct. 18, 2001.
PCT Search Report cited in International Application No. PCT/US01/10874 mailed Nov. 29, 2001.
PCT Search Report cited in International Application No. PCT/US01/14150 mailed Apr. 29, 2002.
PCT Search Report cited in International Application No. PCT/US02/20307 mailed Jan. 3, 2003.
PCT Search Report cited in International Application No. PCT/US02/20519 mailed Apr. 7, 2003.
PCT Search Report cited in International Application No. PCT/US02/24704 mailed Mar. 5, 2003.
PCT Search Report cited in International Application No. PCT/US02/28212 mailed Jan. 23, 2003.
PCT Search Report cited in International Application No. PCT/US02/36291 mailed May 23, 2003.
PCT Search Report cited in International Application No. PCT/US03/03391 mailed Jul. 14, 2003.
PCT Search Report and Written Opinion cited in International Application No. PCT/US2005/001812 mailed May 2, 2005.
PCT Search Report and Written Opinion cited in International Application No. PCT/US2006/033965 mailed Feb. 9, 2007.
PCT Search Report and Written Opinion cited in International Application No. PCT/US2006/033965 Feb. 19, 2007.
PCT Written Opinion cited in International Application No. PCT/US00/15952 mailed Jul. 25, 2001.
PCT Written Opinion cited in International Application No. PCT/US00/15963 mailed Jun. 22, 2001.
PCT Written Opinion cited in International Application No. PCT/US00/16000 mailed Oct. 25, 2001.
PCT Written Opinion cited in International Application No. PCT/US01/02490 mailed Oct. 23, 2001.
PCT Written Opinion cited in International Application No. PCT/US01/06663 mailed Jan. 3, 2002.
PCT Written Opinion cited in International Application No. PCT/US01/10874 mailed Jun. 4, 2002.
PCT Written Opinion cited in International Application No. PCT/US01/14150 mailed Sep. 30, 2004.
PCT Written Opinion cited in International Application No. PCT/US02/20307 mailed Aug. 8, 2003.
PCT Written Opinion cited in International Application No. PCT/US02/20519 mailed Apr. 6, 2004.
PCT Written Opinion cited in International Application No. PCT/US02/24704 mailed Nov. 20, 2003.
PCT Written Opinion cited in International Application No. PCT/US02/28212 mailed Dec. 4, 2003.
Petit et al., “Bandwidth Resource Optimization in Video-On-Demand Network Architectures”, Community Networking Integrated Multimedia Services to the Home, 1994, Proceedings of the 1st International Workshop on San Francisco, CA USA, Jul. 1994, New York, NY USA, IEEE, Jul. 1994, pp. 91-97, XP010124402 ISBN: 978-0-7803-2076-5.
Reid, Dixie, “Coming attractions before they hit the big screen, most films begin life as a trailer,” The Sacramento Bee, Sacramento, California, p. E.1 (Jul. 18, 1996).
Remote Wonder, ATI, Tweak 3D, pp. 1-5 (Sep. 30, 2002).
Reply Brief in U.S. Appl. No. 09/565,931 mailed on Sep. 17, 2007.
Rottentomatoes web archived site, http://web.archive.org/web/20000301122211/http://rottentomatoes.com, Mar. 1, 2000, pp. 1-2.
Supplementary European Search Report cited in European Application No. 02737593.0 mailed Mar. 3, 2009.
Supplementary European Search Report cited in European Application No. 02744705.1 mailed Feb. 19, 2010.
Supplementary European Search Report cited in European Application No. 02750416.6 mailed Jan. 2, 2007.
Supplementary European Search Report cited in European Application No. 02761572.3 mailed Mar. 20, 2007.
Supplementary European Search Report cited in European Application No. 02797096.1 mailed Oct. 14, 2005.
Supplementary European Search Report cited in European Application No. 03713364.2 mailed Jul. 6, 2005.
U.S. Final Office Action cited in U.S. Appl. No. 09/518,041 mailed Jul. 7, 2008.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/518,041 mailed Jan. 10, 2008.
U.S. Final Office Action cited in U.S. Appl. No. 09/518,041 mailed Aug. 24, 2007.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/518,041 mailed Feb. 6, 2007.
U.S. Final Office Action cited in U.S. Appl. No. 09/518,041 mailed Aug. 28, 2006.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/518,041 mailed Apr. 4, 2006.
U.S. Final Office Action cited in U.S. Appl. No. 09/518,041 mailed Sep. 15, 2005.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/518,041 mailed Apr. 22, 2005.
U.S. Final Office Action cited in U.S. Appl. No. 09/518,041 mailed Oct. 20, 2004.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/518,041 mailed Feb. 11, 2004.
U.S. Final Office Action cited in U.S. Appl. No. 09/518,041 mailed Aug. 27, 2003.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/518,041 mailed Mar. 18, 2003.
U.S. Final Office Action cited in U.S. Appl. No. 09/542,484 mailed Jun. 17, 2008.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/542,484 mailed Dec. 7, 2007.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/542,484 mailed Mar. 12, 2007.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/542,484 mailed Sep. 7, 2006.
U.S. Final Office Action cited in U.S. Appl. No. 09/542,484 mailed Mar. 21, 2006.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/542,484 mailed Jul. 28, 2005.
U.S. Final Office Action cited in U.S. Appl. No. 09/542,484 mailed Mar. 22, 2005.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/542,484 mailed Apr. 1, 2004.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/565,931 mailed Oct. 28, 2009.
U.S. Final Office Action cited in U.S. Appl. No. 09/565,931 mailed Jul. 14, 2009.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/565,931 mailed Feb. 13, 2009.
U.S. Final Office Action cited in U.S. Appl. No. 09/565,931 mailed Jun. 15, 2006.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/565,931 mailed Jan. 11, 2006.
U.S. Final Office Action cited in U.S. Appl. No. 09/565,931 mailed Jul. 1, 2005.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/565,931 mailed Sep. 10, 2004.
U.S. Final Office Action cited in U.S. Appl. No. 09/590,434 mailed May 11, 2006.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/590,434 mailed Nov. 21, 2005.
U.S. Final Office Action cited in U.S. Appl. No. 09/590,434 mailed Dec. 1, 2004.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/590,434 mailed Apr. 22, 2004.
U.S. Final Office Action cited in U.S. Appl. No. 09/590,434 mailed Dec. 18, 2003.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/590,434 mailed May 23, 2003.
U.S. Final Office Action cited in U.S. Appl. No. 09/590,488 mailed Feb. 27, 2007.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/590,488 mailed Oct. 26, 2006.
U.S. Final Office Action cited in U.S. Appl. No. 09/590,488 mailed Jul. 10, 2006.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/590,488 mailed Dec. 20, 2005.
U.S. Final Office Action cited in U.S. Appl. No. 09/590,488 mailed Jun. 30, 2005.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/590,488 mailed Nov. 16, 2004.
U.S. Final Office Action cited in U.S. Appl. No. 09/590,488 mailed Jun. 7, 2004.
U.S. Final Office Action cited in U.S. Appl. No. 09/590,488 mailed Dec. 16, 2003.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/590,488 mailed Jun. 10, 2003.
U.S. Final Office Action cited in U.S. Appl. No. 09/590,904 mailed Sep. 13, 2007.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/590,904 mailed Mar. 26, 2007.
U.S. Final Office Action cited in U.S. Appl. No. 09/590,904 mailed Nov. 15, 2006.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/590,904 mailed May 31, 2006.
U.S. Final Office Action cited in U.S. Appl. No. 09/590,904 mailed Jan. 24, 2006.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/590,904 mailed Jul. 13, 2005.
U.S. Final Office Action cited in U.S. Appl. No. 09/590,904 mailed Jan. 11, 2005.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/590,904 mailed Jun. 4, 2004.
U.S. Final Office Action cited in U.S. Appl. No. 09/591,356 mailed Apr. 13, 2006.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/591,356 mailed Dec. 20, 2005.
U.S. Final Office Action cited in U.S. Appl. No. 09/591,356 mailed Jun. 30, 2005.
U.S. Final Office Action cited in U.S. Appl. No. 09/591,356 mailed May 10, 2004.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/591,356 mailed Jan. 14, 2004.
U.S. Final Office Action cited in U.S. Appl. No. 09/591,356 mailed Sep. 26, 2003.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/591,356 mailed May 21, 2003.
U.S. Final Office Action cited in U.S. Appl. No. 09/692,920 mailed Jul. 22, 2008.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/692,920 mailed Jan. 17, 2008.
U.S. Final Office Action cited in U.S. Appl. No. 09/692,920 mailed Jun. 14, 2007.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/692,920 mailed Nov. 24, 2006.
U.S. Final Office Action cited in U.S. Appl. No. 09/692,920 mailed Jun. 21, 2006.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/692,920 mailed Feb. 16, 2006.
U.S. Final Office Action cited in U.S. Appl. No. 09/692,920 mailed Jun. 17, 2005.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/692,920 mailed Nov. 18, 2004.
U.S. Final Office Action cited in U.S. Appl. No. 09/692,995 mailed Sep. 4, 2009.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/692,995 mailed Jan. 23, 2009.
U.S. Final Office Action cited in U.S. Appl. No. 09/692,995 mailed Sep. 8, 2006.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/692,995 mailed Mar. 27, 2006.
U.S. Final Office Action cited in U.S. Appl. No. 09/692,995 mailed Sep. 21, 2005.
U.S. Final Office Action cited in U.S. Appl. No. 09/692,995 mailed May 3, 2005.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/692,995 mailed Oct. 21, 2004.
U.S. Final Office Action cited in U.S. Appl. No. 09/692,995 mailed Apr. 26, 2004.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/692,995 mailed Dec. 5, 2003.
U.S. Final Office Action cited in U.S. Appl. No. 09/693,115 mailed Jan. 25, 2005.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/693,115 mailed Jun. 16, 2004.
U.S. Final Office Action cited in U.S. Appl. No. 09/693,115 mailed Feb. 9, 2004.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/693,115 mailed Sep. 26, 2003.
U.S. Final Office Action cited in U.S. Appl. No. 09/693,288 mailed Dec. 1, 2005.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/693,288 mailed Jul. 19, 2005.
U.S. Final Office Action cited in U.S. Appl. No. 09/693,288 mailed Feb. 10, 2005.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/693,288 mailed Jul. 15, 2004.
U.S. Final Office Action cited in U.S. Appl. No. 09/693,288 mailed Feb. 26, 2004.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/693,288 mailed Oct. 27, 2003.
U.S. Final Office Action cited in U.S. Appl. No. 09/693,790 mailed Jul. 25, 2008.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/693,790 mailed Jan. 15, 2008.
U.S. Final Office Action cited in U.S. Appl. No. 09/693,790 mailed Jun. 19, 2007.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/693,790 mailed Dec. 28, 2006.
U.S. Final Office Action cited in U.S. Appl. No. 09/693,790 mailed Jun. 16, 2006.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/693,790 mailed Dec. 28, 2005.
U.S. Final Office Action cited in U.S. Appl. No. 09/693,790 mailed Jun. 21, 2005.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/693,790 mailed Oct. 6, 2004.
U.S. Final Office Action cited in U.S. Appl. No. 09/881,516 mailed Jun. 3, 2005.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/881,516 mailed Dec. 29, 2004.
U.S. Final Office Action cited in U.S. Appl. No. 09/881,516 mailed Jul. 26, 2004.
U.S. Final Office Action cited in U.S. Appl. No. 09/881,516 mailed Apr. 21, 2004.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/881,516 mailed Oct. 28, 2003.
U.S. Final Office Action cited in U.S. Appl. No. 09/894,508 mailed Sep. 17, 2009.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/894,508 mailed Feb. 4, 2009.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/894,508 mailed Jun. 13, 2008.
U.S. Final Office Action cited in U.S. Appl. No. 09/894,508 mailed Dec. 31, 2007.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/894,508 mailed Jul. 26, 2007.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/896,231 mailed Nov. 17, 2009.
U.S. Final Office Action cited in U.S. Appl. No. 09/896,231 mailed Jun. 3, 2009.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/896,231 mailed Dec. 23, 2008.
U.S. Final Office Action cited in U.S. Appl. No. 09/896,231 mailed Dec. 29, 2005.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/896,231 mailed Jun. 23, 2005.
U.S. Final Office Action cited in U.S. Appl. No. 09/924,111 mailed Aug. 7, 2008.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/924,111 mailed Jan. 29, 2008.
U.S. Final Office Action cited in U.S. Appl. No. 09/924,111 mailed Oct. 5, 2007.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/924,111 mailed Apr. 19, 2007.
U.S. Final Office Action cited in U.S. Appl. No. 09/924,111 mailed Sep. 18, 2006.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/924,111 mailed Mar. 15, 2006.
U.S. Final Office Action cited in U.S. Appl. No. 09/947,890 mailed Nov. 24, 2009.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/947,890 mailed Apr. 10, 2009.
U.S. Final Office Action cited in U.S. Appl. No. 09/947,890 mailed Nov. 6, 2008.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/947,890 mailed Jun. 25, 2008.
U.S. Final Office Action cited in U.S. Appl. No. 10/740,138 mailed Jan. 15, 2010.
U.S. Non-Final Office Action cited in U.S. Appl. No. 10/740,138 mailed Sep. 3, 2009.
U.S. Final Office Action cited in U.S. Appl. No. 10/740,138 mailed Mar. 19, 2009.
U.S. Non-Final Office Action cited in U.S. Appl. No. 10/740,138 mailed Sep. 15, 2008.
U.S. Final Office Action cited in U.S. Appl. No. 10/740,138 mailed Jun. 11, 2008.
U.S. Non-Final Office Action cited in U.S. Appl. No. 10/740,138 mailed Oct. 2, 2007.
U.S. Non-final Office Action cited in U.S. Appl. No. 10/761,777 mailed Jan. 21, 2010.
U.S. Non-Final Office Action cited in U.S. Appl. No. 10/761,777 mailed Jun. 11, 2009.
U.S. Final Office Action cited in U.S. Appl. No. 10/761,777 mailed Dec. 19, 2008.
U.S. Non-Final Office Action cited in U.S. Appl. No. 10/761,777 mailed Jul. 18, 2007.
U.S. Non-Final Office Action cited in U.S. Appl. No. 10/761,777 mailed Jan. 24, 2007.
U.S. Final Office Action cited in U.S. Appl. No. 10/778,494 mailed Jul. 25, 2008.
U.S. Non-Final Office Action cited in U.S. Appl. No. 10/778,494 mailed Jan. 16, 2008.
U.S. Final Office Action cited in U.S. Appl. No. 10/778,494 mailed May 22, 2007.
U.S. Non-Final Office Action cited in U.S. Appl. No. 10/778,494 mailed Feb. 2, 2007.
U.S. Final Office Action cited in U.S. Appl. No. 10/778,494 mailed Aug. 28, 2006.
U.S. Non-Final Office Action cited in U.S. Appl. No. 10/778,494 mailed Dec. 29, 2004.
U.S. Final Office Action cited in U.S. Appl. No. 10/783,235 mailed Oct. 2, 2008.
U.S. Non-Final Office Action cited in U.S. Appl. No. 10/783,235 mailed Feb. 25, 2008.
U.S. Final Office Action cited in U.S. Appl. No. 10/957,849 mailed Aug. 8, 2008.
U.S. Non-Final Office Action cited in U.S. Appl. No. 10/957,849 mailed Apr. 30, 2008.
U.S. Final Office Action cited in U.S. Appl. No. 10/957,854 mailed Apr. 1, 2010.
U.S. Non-Final Office Action cited in U.S. Appl. No. 10/957,854 mailed Sep. 28, 2009.
U.S. Final Office Action cited in U.S. Appl. No. 10/957,854 mailed Apr. 7, 2009.
U.S. Non-Final Office Action cited in U.S. Appl. No. 10/957,854 mailed Oct. 15, 2008.
U.S. Non-Final Office Action cited in U.S. Appl. No. 10/957,854 mailed Apr. 30, 2008.
U.S. Final Office Action cited in U.S. Appl. No. 10/957,942 mailed Jul. 28, 2009.
U.S. Non-Final Office Action cited in U.S. Appl. No. 10/957,942 mailed Jan. 14, 2009.
U.S. Final Office Action cited in U.S. Appl. No. 10/957,942 mailed Jul. 31, 2008.
U.S. Non-Final Office Action cited in U.S. Appl. No. 10/957,942 mailed May 1, 2008.
U.S. Final Office Action cited in U.S. Appl. No. 10/981,053 mailed Jan. 21, 2010.
U.S. Non-Final Office Action cited in U.S. Appl. No. 10/981,053 mailed Apr. 15, 2009.
U.S. Final Office Action cited in U.S. Appl. No. 10/981,053 mailed Aug. 6, 2008.
U.S. Non-Final Office Action cited in U.S. Appl. No. 10/891,053 mailed Jan. 2, 2008.
U.S. Final Office Action cited in U.S. Appl. No. 10/994,599 mailed Dec. 1, 2006.
U.S. Non-Final Office Action cited in U.S. Appl. No. 10/994,599 mailed May 16, 2006.
U.S. Final Office Action cited in U.S. Appl. No. 10/994,599 mailed Jan. 26, 2006.
U.S. Non-Final Office Action cited in U.S. Appl. No. 10/994,599 mailed Aug. 23, 2005.
U.S. Final Office Action cited in U.S. Appl. No. 11/162,345 mailed Mar. 16, 2010.
U.S. Non-Final Office Action cited in U.S. Appl. No. 11/162,345 mailed Aug. 21, 2009.
U.S. Final Office Action cited in U.S. Appl. No. 11/162,345 mailed Mar. 9, 2009.
U.S. Non-Final Office Action cited in U.S. Appl. No. 11/162,345 mailed Oct. 31, 2008.
U.S. Final Office Action cited in U.S. Appl. No. 11/170,348 mailed Feb. 1, 2010.
U.S. Non-Final Office Action cited in U.S. Appl. No. 11/170,348 mailed Sep. 30, 2009.
U.S. Final Office Action cited in U.S. Appl. No. 11/170,348 mailed May 28, 2009.
U.S. Non-Final Office Action cited in U.S. Appl. No. 11/170,348 mailed Dec. 11, 2008.
U.S. Final Office Action cited in U.S. Appl. No. 11/208,387 mailed Dec. 22, 2008.
U.S. Non-Final Office Action cited in U.S. Appl. No. 11/208,387 mailed Jun. 12, 2008.
U.S. Non-Final Office Action cited in U.S. Appl. No. 11/238,369 mailed Mar. 30, 2010.
U.S. Non-Final Office Action cited in U.S. Appl. No. 11/244,621 mailed Feb. 5, 2010.
U.S. Final Office Action cited in U.S. Appl. No. 11/244,621 mailed Sep. 17, 2009.
U.S. Non-Final Office Action cited in U.S. Appl. No. 11/244,621 mailed Mar. 19, 2009.
U.S. Non-Final Office Action cited in U.S. Appl. No. 11/244,621 mailed Sep. 19, 2008.
U.S. Non-Final Office Action cited in U.S. Appl. No. 11/275,245 mailed May 5, 2010.
U.S. Non-Final Office Action cited in U.S. Appl. No. 11/275,245 mailed Oct. 22, 2009.
U.S. Final Office Action cited in U.S. Appl. No. 11/275,245 mailed Jul. 29, 2009.
U.S. Non-Final Office Action cited in U.S. Appl. No. 11/275,245 mailed Sep. 22, 2008.
U.S. Final Office Action cited in U.S. Appl. No. 11/460,516 mailed Mar. 18, 2010.
U.S. Non-Final Office Action cited in U.S. Appl. No. 11/460,516 mailed Jun. 26, 2009.
U.S. Final Office Action cited in U.S. Appl. No. 11/460,516 mailed Feb. 13, 2009.
U.S. Non-Final Office Action cited in U.S. Appl. No. 11/460,516 mailed Sep. 17, 2008.
U.S. Non-Final Office Action cited in U.S. Appl. No. 11/496,303 mailed Mar. 2, 2010.
U.S. Non-Final Office Action cited in U.S. Appl. No. 11/496,303 mailed Sep. 29, 2009.
U.S. Final Office Action cited in U.S. Appl. No. 11/496,303 mailed Apr. 1, 2009.
U.S. Non-Final Office Action cited in U.S. Appl. No. 11/496,303 mailed Sep. 18, 2008.
U.S. Final Office Action cited in U.S. Appl. No. 11/564,431 mailed Jan. 4, 2010.
U.S. Non-Final Office Action cited in U.S. Appl. No. 11/564,431 mailed Aug. 24, 2009.
U.S. Non-Final Office Action cited in U.S. Appl. No. 11/678,653 mailed Dec. 16, 2009.
U.S. Non-Final Office Action cited in U.S. Appl. No. 12/127,968 mailed Mar. 31, 2010.
U.S. Final Office Action cited in U.S. Appl. No. 12/127,968 mailed Dec. 1, 2009.
U.S. Non-Final Office Action cited in U.S. Appl. No. 12/127,968 mailed Apr. 30, 2009.
U.S. Non-Final Office Action cited in U.S. Appl. No. 12/179,752 mailed Dec. 23, 2009.
U.S. Non-Final Office Action cited in U.S. Appl. No. 12/179,767 mailed Jan. 22, 2010.
U.S. Final Office Action cited in U.S. Appl. No. 12/372,887 mailed Apr. 14, 2010.
U.S. Non-Final Office Action cited in U.S. Appl. No. 12/372,887 mailed Oct. 16, 2009.
U.S. Non-Final Office Action cited in U.S. Appl. No. 12/372,894 mailed Oct. 27, 2009.
U.S. Non-Final Office Action cited in U.S. Appl. No. 12/372,917 mailed Oct. 26, 2009.
U.S. Non-Final Office Action cited in U.S. Appl. No. 12/388,139 mailed Dec. 15, 2009.
U.S. Final Office Action cited in U.S. Appl. No. 12/389,564 mailed Apr. 28, 2010.
U.S. Non-Final Office Action cited in U.S. Appl. No. 12/389,564 mailed Nov. 10, 2009.
U.S. Non-Final Office Action cited in U.S. Appl. No. 12/413,686 mailed Nov. 30, 2009.
U.S. Appl. No. 09/330,792, filed Jun. 11, 1999 entitled “Series Reminders and Series Recording from an Interactive Television program Guide”.
U.S. Appl. No. 09/378,533, filed Aug. 20, 1999 entitled “Electronic Program Guide with Advance Notification”.
U.S. Appl. No. 09/518,041, filed Mar. 2, 2000 entitled “Apparatus and Method for Providing a Plurality of Interactive Program Guide Initial Arrangements”.
U.S. Appl. No. 09/542,484, filed Apr. 3, 2000 entitled “System for Providing Alternative Services”.
U.S. Appl. No. 09/565,931, filed May 4, 2000 entitled “Navigation Paradigm for Access to Television Services”.
U.S. Appl. No. 09/590,434, filed Jun. 9, 2000 entitled “Video Promotional and Advertising Systems for Video on Demand System”.
U.S. Appl. No. 09/590,488, filed Jun. 9, 2000 entitled “User Interface Navigational System with Parental Control for Video on Demand System”.
U.S. Appl. No. 09/590,521, filed Jun. 9, 2000 entitled “Systems and Methods for Adaptive Scheduling and Dynamic Bandwidth Resource Allocation Management in a Digital Broadband Delivery System”.
U.S. Appl. No. 09/590,904, filed Jun. 9, 2000 entitled “Program Information Searching System for Interactive Program Guide”.
U.S. Appl. No. 09/591,356, filed Jun. 9, 2000 entitled “Future Program Options Menu System for Interactive Program Guide”.
U.S. Appl. No. 09/692,920, filed Oct. 20, 2000 entitled “Media-on-Demand Title Indexing System”.
U.S. Appl. No. 09/692,995, filed Oct. 20, 2000 entitled “Media-on-Demand Bookmark System”.
U.S. Appl. No. 09/693,115, filed Oct. 20, 2000 entitled “Media Services Window Configuration System”.
U.S. Appl. No. 09/693,288, filed Oct. 20, 2000 entitled “Media-on-Demand Rental Duration Management System”.
U.S. Appl. No. 09/693,790, filed Oct. 20, 2000 entitled “Integrated Searching System for Interactive Media Guide”.
U.S. Restriction Requirement cited in U.S. Appl. No. 11/162,345 mailed Jul. 3, 2008.
VESA Plug and Display Standard, Version 1, Video Electronics Standards Association, XP-002123075, 90 pages (Jun. 11, 1997).
W3C, Putting language attributes in HTML, www.w3.org.org/International/O-help-lang, 2 pages (Apr. 29, 1997).
U.S. Non-Final Office Action cited in U.S. Appl. No. 11/234,967 mailed Sep. 10, 2010.
U.S. Final Office Action cited in U.S. Appl. No. 11/238,369 mailed Aug. 31, 2010.
U.S. Final Office Action cited in U.S. Appl. No. 11/244,621 mailed Aug. 18, 2010.
U.S. Non-Final Office Action cited in U.S. Appl. No. 11/963,951 mailed Aug. 2, 2010.
U.S. Final Office Action cited in U.S. Appl. No. 12/127,968 mailed Sep. 14, 2010.
U.S. Final Office Action cited in U.S. Appl. No. 12/179,767 mailed Aug. 20, 2010.
U.S. Non-Final Office Action cited in U.S. Appl. No. 12/388,002 mailed Sep. 3, 2010.
U.S. Non-Final Office Action cited in U.S. Appl. No. 12/389,564 mailed Aug. 23, 2010.
U.S. Final Office Action cited in U.S. Appl. No. 12/372,917 mailed May 17, 2010.
U.S. Final Office Action cited in U.S. Appl. No. 09/896,231mailed May 28, 2010.
Canadian Office Action cited in Application No. 2,402,088 mailed Jun. 1, 2010.
Canadian Office Action cited in Application No. 2,405,491 mailed Jun. 9, 2010.
Summons to attend oral proceedings pursuant to Rule 115(1) EPC in European Application No. 02737593.0-1241 mailed May 28, 2010.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/693,288 mailed Jun. 21, 2010.
U.S. Final Office Action cited in U.S. Appl. No. 10/761,777 mailed Aug. 2, 2010.
U.S. Non-Final Office Action cited in U.S. Appl. No. 10/957,942 mailed Jun. 30, 2010.
U.S. Final Office Action cited in U.S. Appl. No. 11/496,303 mailed Jul. 22, 2010.
U.S. Non-Final Office Action cited in U.S. Appl. No. 11/564,431 mailed Jul. 20, 2010.
U.S. Final Office Action cited in U.S. Appl. No. 11/678,653 mailed Jun. 23, 2010.
U.S. Non-Final Office Action cited in U.S. Appl. No. 11/963,942 mailed Jun. 8, 2010.
U.S. Non-Final Office Action cited in U.S. Appl. No. 11/963,945 mailed Jul. 16, 2010.
U.S. Non-Final Office Action cited in U.S. Appl. No. 12/180,416 mailed Jun. 25, 2010.
U.S. Final Office Action cited in U.S. Appl. No. 12/388,139 mailed Jul. 6, 2010.
U.S. Non-Final Office Action cited in U.S. Appl. No. 12/389,128 mailed Jun. 2, 2010.
U.S. Final Office Action cited in U.S. Appl. No. 12/413,686 mailed Jun. 10, 2010.
Canadian Office Action cited in Application No. 2,456,318 mailed Nov. 17, 2010, 4 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 12/179,763 mailed Jan. 4, 2011, 18 pages.
U.S. Final Office Action cited in U.S. Appl. No. 12/389,128 mailed Nov. 9, 2010, 50 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 12/389,564 mailed Jan. 21, 2011, 13 pages.
“Industry Leading Software Vendors Endorse BroadVision's Next Generation of Retail and Business-To-Business E-Commerce Application Solutions,” PR Newswire, Jun. 14, 1999, 4 pages.
U.S. Final Office Action cited in U.S. Appl. No. 09/693,288 mailed Feb. 8, 2011, 28 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 11/162,345 mailed Feb. 1, 2011, 33 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 12/413,686 mailed Mar. 17, 2011, 20 pages.
Canadian Office Action cited in Application No. 2,408,289 mailed Sep. 2, 2010.
Canadian Office Action cited in Application No. 2,451,477 mailed Oct. 20, 2010.
U.S. Non-Final Office Action cited in U.S. Appl. No. 10/740,138 mailed Oct. 27, 2010.
U.S. Non-Final Office Action cited in U.S. Appl. No. 11/170,348 mailed Oct. 26, 2010.
U.S. Non-Final Office Action cited in U.S. Appl. No. 12/390,418 mailed Sep. 28, 2010.
U.S. Non-Final Office Action cited in U.S. Appl. No. 12/390,420 mailed Oct. 19, 2010.
U.S. Non-Final Office Action cited in U.S. Appl. No. 12/390,422 mailed Oct. 20, 2010.
Canadian Office Action cited in Application No. 2,459,334 mailed Mar. 4, 2011, 3 pages.
Summons to attend oral proceedings in EP Application No. 01937209.3 mailed Mar. 21, 2011, 7 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 10/761,777 mailed Apr. 12, 2011, 20 pages.
Canadian Office Action dated May 31, 2011 cited in Application No. 2,621,605, 2 pages.
U.S. Final Office Action cited in U.S. Appl. No. 12/389,564 mailed May 19, 2011, 15 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 10/740,138 mailed Jun. 8, 2011, 26 pages.
U.S. Final Office Action cited in U.S. Appl. No. 11/170,348 mailed Jun. 9, 2011, 14 pages.
Related Publications (1)
Number Date Country
20050028190 A1 Feb 2005 US
Divisions (1)
Number Date Country
Parent 10073842 Feb 2002 US
Child 10934253 US