Channel control system for exiting from an interactive program guide

An apparatus and method for browsing and viewing television programs while viewing a television program guide. In other words, a user is able to remain inside the program guide while viewing various television programs. In another aspect, a server system operator is provided an interface with flexible options for configuring user controls for viewing television programs while inside program guides in client devices.

Skip to: Description  ·  Claims  ·  References Cited  · Patent History  ·  Patent History
Description
CROSS-REFERENCE TO RELATED APPLICATION

This application is a divisional of U.S. patent application Ser. No. 09/590,925, filed Jun. 9, 2000, now U.S. Pat. No. 6,817,028 issued on Nov. 9, 2004, which claims the benefit of U.S. Provisional Application Ser. No. 60/138,757, filed Jun. 11, 1999, which is hereby incorporated by reference herein in its entirety.

FIELD OF THE INVENTION

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

BACKGROUND OF THE INVENTION

Historically, television services have been comprised of analog broadcast audio and video signals. Cable television systems now receive broadcasts and retransmit them with other programming to subscribers over land-line networks, typically comprising fiber optic cable and/or coaxial cable. With the recent advent of digital transmission technology, cable television systems are now capable of providing much more than the traditional analog broadcast video. In addition, two-way and advanced one-way communications between a subscriber and a cable system headend are now possible.

In implementing enhanced programming, the home communication terminal (“HCT”), otherwise known as the settop box, has become an important computing device for accessing video services and navigating a subscriber through a maze of services available. In addition to supporting traditional analog broadcast video and functionality, digital HCTs (or “DHCTs”) now also support an increasing number of services which are not analog, but rather digital; are not basic broadcast, but rather two-way communication such as video-on-demand; and are not basic video, such as e-mail or web browsers. These are all in addition to the host of other television services which are increasingly being demanded by consumers, examples of which include audio and audio/visual programming, advance navigation controls, impulse pay-per-view technology, and on-line commerce. In addition to the interactive services, the increased bandwidth available through a digital television system has made it possible for a subscriber to have access to hundreds, or even thousands, of channels and/or services. Thus, in order to provide these more powerful and complex features, the simple conventional channel abstractions need to be extended beyond those which have traditionally been provided.

Each HCT and DHCT (collectively hereinafter “DHCT”) are typically connected to a cable or satellite television network. The DHCTs generally include hardware and software necessary to provide the functionality of the digital television system at the client's site. Preferably, some of the software executed by a DHCT is downloaded and/or updated via the cable television network. Each DHCT typically includes a processor, a communication component and memory, and is connected to a television or other display device, such as a personal computer. 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.

As more and more services and applications are provided, cable television systems are providing television program information to the DHCT so that the subscriber can view the program information on the DHCT display such as the television. This program information has traditionally been organized for presentation purposes into a program guide format that presents the program information by time and channel only. The program guide can, for instance, automatically scroll the available television channels to present the program information such as name and title, by time.

Many cable system operators include one or more dedicated channels that scroll through the channel list displaying the programs that not only are currently on, but also are scheduled to be on in the future. These types of passive displays do not rely on a terminal for presentation of the programming data and also lack the interactive functionality of permitting a subscriber to scroll to a desired channel for a desired time. For example, the subscriber typically must view the programming information as it scrolls on the display and wait for either the desired channel and/or the desired time to search for the program that may be available for viewing.

With the advent of program guide “browsers” for use in cable television systems, viewers (also referred to as “subscribers” or “users”) can literally scan program information by time and channel while watching the tuned channel. In analog systems that offer a limited number of cable television channels, these browsers enable the viewer to easily scan available programs one-by-one in order of channel number. However, many digital systems can provide hundreds or even thousands of channels. In such systems, viewers may be only familiar with a small fraction of the television programs available for viewing. As a result, viewers may end up spending significant amounts of time browsing through on-screen program guides in order to determine which program they would enjoy watching the most. This may be inconvenient since either the viewer browsing the program guide or other viewers in the same room may be missing a desirable alternative program while the program guide is being browsed. In addition, program descriptions in on-screen program guides often do not provide a viewer with enough information to be able to determine whether he or she would enjoy watching a particular program.

SUMMARY OF THE INVENTION

Briefly described, one preferred embodiment of the present invention provides an apparatus and method for browsing and viewing different television programs while browsing a television program guide. In other words, a user is able to remain inside the program guide while viewing various television programs. In another aspect of a preferred embodiment of the present invention, a server system operator is provided an interface with flexible options for configuring user controls for viewing television programs while inside program guides in client devices.

Other objects, features, and advantages of the present invention will become apparent to one with skill in the art upon examination of the following drawings and detailed description.

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 to scale, emphasis instead being placed upon clearly illustrating the principles of the present invention. In the drawings, like reference numerals designate corresponding parts or screen areas throughout the several views.

FIG. 1 is a block diagram of a cable television system in accordance with one preferred embodiment of the present invention.

FIG. 2 is a block diagram of a DHCT and related equipment, in accordance with one preferred embodiment of the present invention depicted in FIG. 1.

FIG. 3 is a diagram depicting files that are transferred from the headend of the cable television system across to the DHCT depicted in FIG. 2.

FIG. 4 is a diagram of a control menu for a system operator at the headend to configure how the reduced screen area of an interactive program guide will be tuned by a client device in accordance with the present invention as depicted in FIG. 2.

FIG. 5 is an example screen diagram that illustrates an initial guide arrangement in a time format that the DHCT as depicted in FIG. 2 presents to the subscriber.

FIG. 6 is an example screen diagram that illustrates how the tuning of the reduced screen display area does not follow the in-focus television program as the screen transitions from that shown in FIG. 5.

FIG. 7 is an example screen diagram that illustrates the tuning of a reduced screen display area to the channel of the in-focus television program in FIG. 6.

FIG. 8 is an example screen diagram that illustrates the tuning of a reduced screen display area to the next higher numbered channel than the channel of the in-focus program in FIG. 7.

FIG. 9 is an example screen diagram that illustrates the tuning of a reduced screen display area to a channel number specified through user input received by the DHCT as depicted in FIG. 2.

FIG. 10 is a block diagram of an example of a remote control device for use with the DHCT depicted in FIG. 2.

 DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

FIG. 1 is a block diagram of a cable television system 10 including a headend 11 for receiving television signals, such as satellite television signals, and converting the signals into a format for transmitting the signals over the system 10. The transmitted signals can, for example, be radio frequency (RF) signals or optical signals, as shown, transmitted over fiber optic cable 12. When the optical signals are transmitted by the headend 11, one or more optical nodes 13 are included in the system 10 for converting the optical signals to RF signals that are thereafter routed over other media, such as coaxial cables 14. Taps 15 are provided within the cable system 10 for splitting the RF signal off, via cables 17, to subscriber equipment such as DHCTs 16, cable-ready television sets, video recorders, or computers. Thus, headend 11 is connected through a network 20 to multiple DHCTs 16.

FIG. 2 is a block diagram illustrating the DHCT 16 and other system equipment. The DHCT 16 is typically situated within the residence or business of a subscriber. It may be integrated into a device that has a display 21, such as a television set, or it may be a stand-alone unit that couples to an external display 21, such as a display included in a computer or a television, and that processes television signals for presentation to a subscriber. The terminal 16 preferably comprises a communications interface 22 for receiving the RF signals, which can include video, audio and data information, from the tap 15 and for providing any reverse information to the tap 15 for transmission back to the headend 11 (FIG. 1). The DHCT 16 further includes a processor 24 for controlling operations of the DHCT 16, a video output port such as an RF output system 28 for driving the display 21, and a tuner system 25 for tuning into a particular television channel to be displayed and for sending and receiving various types of data from the headend 11. The tuner system includes in one implementation, an out-of-band tuner for bi-directional quadrature phase shift keying (QPSK) data communication and a quadrature amplitude modulation (QAM) tuner for receiving television signals. Additionally, DHCT 16 includes a receiver 26 for receiving externally-generated information, such as subscriber inputs or commands from other devices. The DHCT 16 may also include one or more wireless or wired communication interfaces, also called ports, for receiving and/or transmitting data to other devices. For instance, the DHCT may feature USB (Universal Serial Bus), Ethernet (for connection to a computer), IEEE-1394 (for connection to media devices in an entertainment center), and serial, and/or parallel ports. The subscriber inputs may, for example, be provided by a computer or transmitter with buttons or keys located on the exterior of the terminal, by a hand-held remote control device 27 (an example of which is shown in FIG. 10), or by a keyboard that includes subscriber-actuated buttons. With brief reference to FIG. 10, among other keys, examples of keys on the remote control device 27 include, without limitation, numeric channel indication keys, or buttons, e.g., keys labeled “0”-“9”, non-numeric channel indication keys (channel increment (CH+), channel decrement (CH−), favorite channel (FAV), last channel (LAST)), and directional keys with arrows (UP, DOWN, LEFT, RIGHT), a SELECT (SEL) key, and a GUIDE key.

Memory 30, such as a non-volatile and dynamic random access memory, is coupled to the processor 24 and stores operational parameters, such as commands that are recognized by the processor 24. The most basic functionality of the DHCT 16 is provided by an operating system 31 that operates in memory 30. One or more programmed software applications, herein referred to as applications, are executed by utilizing the computing resources in the DHCT 16. The executable application program stored in memory 30 is executed by processor 24 (e.g., a central processing unit or digital signal processor) under the auspices of the operating system 31. Data required as input by the application program is stored in memory 30 and read by processor 24 from memory 30 as need be during the course of application program execution. Input data may be data stored in memory 30 by a secondary application or other source, either internal or external to the DHCT 16, or may have been created with the application program at the time it was generated as a software application program. Data may be received via any of the communication ports of the DHCT 16, from the headend 11 via the DHCT's network interface (i.e., the QAM or out-of-band tuners) or as subscriber input via receiver 26. A type of input data fulfills and serves the purpose of parameters as described below. Data generated by application program is stored in memory 30 by processor 24 during the course of application program execution. Availability, location and amount of data generated by a first application for consumption by a secondary application is communicated by messages as described below. Messages are communicated through the services of the operating system 31, such as interrupt or polling mechanisms or through data sharing mechanisms such as semaphores.

A Navigator (application) 33 is responsible for providing the subscriber the capability to select services and also provides a core functionality of the DHCT 16, including volume and settings. To implement its functionality, the Navigator 33 communicates with a platform 35, which is a collection of functionality such as the services application manager (SAM) 36, a Configuration Manager 42, and a Window Manager 45 that is useful to the applications. The platform 35 may also include such functionality as a Timer Manager, a Compression Manager, an HTML Parser, a Database Manager, A Widget Toolkit, and other utilities (not shown).

In one implementation, the Window Manager 45 maintains, among other things, a user input registry 32 so that when a subscriber enters a key or a command via the remote device 27 or another input device such as a keyboard or mouse, the user input registry 32 is accessed to determine which of various applications running on the DHCT 16 should receive the inputted key and in what order. The Navigator 33 registers for certain user input commands with the Window Manager 45 so that when the subscriber hits a key corresponding to one of the commands on the remote 27, the command is received by the receiver 26 and relayed to the processor 24. The processor 24 dispatches the event to the operating system 31 where it is forwarded to the Window Manager 45, which ultimately accesses the user input registry 32 and routes the incoming command to the Navigator 33. The Navigator 33 registers for user input commands that correspond to service navigation functions such as selecting a channel (channel increment, channel decrement, favorite, last) and those for other reserved functionality such as a key to activate the program guide, e.g., a GUIDE key.

After the Navigator 33 is activated by the remote 27, it sends a command to a services application manager (“SAM”) component 36 part of the platform 35. The SAM 36 maintains a services database 37 of all services available on the DHCT 16 that the subscriber may access. A service is a pairing of an application and a parameter, such as a WatchTV application (not shown) and the television program to tune (e.g. NBC), or an Email application (not shown) and the IP address of the Email server. When the SAM 36 receives a query from the Navigator 33, it accesses the service database 37 and informs the Navigator 33 about the existence and status of the requested service. The Navigator 33 can further query the SAM 36 to determine if the service is authorized for the DHCT 16 and, if so, subsequently command the SAM to activate the service. In response, the SAM 36 initiates an activate service message to the application identified in the service database as the provider of the desired service. As a non-limiting example, the subscriber pressing a “GUIDE” key on the remote 27 would activate the interactive program guide (application) 38. That is, the subscriber presses a first key that invokes display of an interactive program guide (IPG) 38 presentation session.

The IPG 38 displays a program guide to the subscriber and populates the guide with program data for selection. Contained in the IPG 38 is a user interface component 39 that controls the screen display presented to the subscriber on display 21. When the user interface 39 receives the activation message from the SAM 36, the user interface 39 proceeds in accessing an IPG database 40 and a configuration module 41 to determine the appropriate program guide configuration (initial guide arrangement or view) to present to the subscriber on the display 21. The IPG database 40 contains program data files of current and future television programs. An IPG configuration module 41 stores settings that the user interface 39 will implement in creating the display for the subscriber. According to the preferred embodiment of the present invention, the IPG configuration module 41 includes a configuration database 43 of all configurations relevant to the IPG 38. The configuration library 42 allows applications to access configurations stored in other applications, such as the IPG configuration database 43. Some of these configurations are pre-loaded into DHCT 16 non-volatile memory before it is released to a subscriber for use in viewing television services. Additionally, configurations can be updated, added, or replaced in the DHCT 16 by communicating the configuration data files 54 (FIG. 3) from the headend 11 to Configuration Daemon 44 which writes the configuration data files 54 to the various application configuration databases, such as the IPG configuration database 43. Although the IPG configuration database 43 provides a variety of initial configurations that the IPG user interface 39 may implement, one of these is denoted as the selected configuration that is ultimately implemented by the user interface 39. The configuration daemon 44 on the platform 35 will update the application configuration databases, such as IPG configuration database 43, whenever the DHCT 16 is powered up or when the configuration daemon 44 receives an update message from the headend 11 with new settings for the configurations.

When the IPG user interface 39 receives the activate service command from the SAM 36 responsive to a user selecting the IPG from the remote 27, the IPG user interface 39 accesses the IPG configuration module 41 to determine which viewing arrangement to present to the subscriber on the display 21. Based on the configuration information stored in the configuration module 41, the user interface 39 utilizes the window manager 45 and other graphics utilities provided by the operating system 31 to draw the screen on the display 21. The window manager 45 is a component that in one embodiment is part of the platform 35, but in other embodiments may be part of the operating system 31. In addition to the user input registry mentioned previously, it contains functionality for managing screen real-estate and synchronizing the drawing done by multiple applications. The operating system 31 provides primitives to the user interface 39 to, for example, to create a rectangular region on display 21 and to draw into that rectangle graphics utilities such as lines, shadings and strings.

As a window is created on display 21 for presentation to the subscriber, the IPG user-interface 39 registers with the window manager 45 for particular user input commands that are required by the newly-created window on the display 21. The IPG 38 also contains a daemon 46 that receives program data files 53 from the headend 11, and the daemon 46 stores the program data files 53 in the database 40 for utilization by the user interface 39.

The Navigator application 33, IPG 38, and all other applications executed by the resources of the DHCT 16 comprise an ordered listing of 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 the instructions from the instruction execution system, apparatus, or device 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 is not limited to, an electronic, solid-state, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, device, or propagation medium, either internal to the DHCT 16 or externally connected to the DHCT 16 via one or more communication ports or network interfaces. More specific examples (a nonexhaustive 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 hard drive storage device (magnetic) a random access memory (RAM) (solid-state device), a read-only memory (ROM) (solid-state device), an erasable programmable read-only memory (EPROM or Flash memory) (multiple devices), 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 if necessary, and then stored in a computer memory. Furthermore, any process descriptions or blocks in flow charts should be understood as representing modules, segments, or portions of code or programmed software which include one or more executable instructions for implementing specific logical functions or steps in the process, and alternate implementations are included within the scope of the preferred embodiment of the present invention in which functions 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 of the present invention.

FIG. 3 is a diagram of selected components resident on the headend 11 and their interaction with the DHCT 16 on the client side of the network 20. An IPG server 51 is contained on the headend 11 and assembles program data files 53 for transmission across the network 20 to the IPG daemon 46 (FIG. 2) in the DHCT 16. The program data files 53 are the data files that contain information about current and of future programs, including their prospective viewing times, descriptive information, channels etc. The IPG server 51 allows the system operator to configure how many days in advance for which the program data files 53 will contain programming information. A configuration server 52 maintains and transmits across network 20 configuration data files 54 that comprise a plurality of program guide arrangement definitions, as well as indication of a selected initial program guide arrangement for the display 21.

With reference to FIG. 2, the configuration daemon 44 receives the configuration information and stores it in the IPG configuration database 43 from which configuration module 41 accesses the information, as discussed above. The program data files 53 (FIG. 3) created by the IPG server 51 on the headend 11 are received by the IPG Daemon 46 which populates the IPG database 40 in memory 30 with the program data files 53 for utilization by the user interface 39 when commanded by the subscriber. Alternatively, the IPG database 40, or parts thereof may be stored in a storage device that is internal to the DHCT 16 or externally connected to the DHCT 16 via a communication port such as USB or IEEE-1394.

In FIG. 2 and FIG. 3, functionality of the various layers of software, including the operating system 31, platform 35, and applications such as the IPG 38 and Navigator 33 are generally present on both the client side and the server side of the cable television system. The Navigator 33 assists in providing basic cable services and navigation framework to the subscriber. The services available can include watching television and pay-per-view events, listening to digital music, and viewing the interactive program guide 38 (FIG. 2). The Navigator 33 also allows subscribers to access the settings in the DHCT 16 (FIG. 2), including volume, parental control, VCR commands, etc. The operating system 31 is a resident operating system on the DHCT 16 and is provisioned for reception of multi-media data over the broadcast and interactive cable networks and uses an open and modular platform to allow flexibility and customization. As a result, some features of the operating system 31 include real time multi-media data reception, streaming and processing, as well as multi-tasking capability, and an open platform. The operating system 31 also provisions the communication of data among different entities such as a multiplicity of applications executing in the DHCT 16. The application interface system (AIS) or Platform 35 is a collection of end-to-end software interfaces enabling applications on the cable televisions system network 10. The SAM 36 provides an interface and mechanism through which applications can be developed, introduced on the network, defined as a service, downloaded to the DHCT 16, executed on the DHCT 16 and removed from the network. The AIS is an end layer of application and service management software components that an application must utilize to exist in the cable television system network 10. It also consists of resource access and management components generally required by applications in the cable television system network 10. None of the AIS components have any client-side subscriber-interfaces, although graphical subscriber interfaces can exist to access server-side components.

FIG. 4 is a diagram of a control menu 64 for a system operator at the headend 11 to configure how a reduced screen display area of the IPG user interface 39 will be controlled, in accordance with the present invention as depicted in FIG. 2. In one implementation, a system operator can use the menu to select the desired settings for the reduced screen display area. These settings will determine how the reduced screen display area will be tuned in relation to the television program information that will be presented to a subscriber and in relation to input received by the DHCT 16 (FIG. 2) from a subscriber. These selections are communicated across the system network 20 to each individual DHCT 16. The settings and factors that determine which channel a reduced screen display area is tuned to are discussed in more detail below. Of course, many other arrangements and expressions of the options shown in FIG. 4 are considered to be within the scope of the present invention. In addition, an alternative embodiment of the present invention permits the subscriber to determine how the reduced screen display area will be tuned in relation to the television program information that is to be presented to a subscriber and in relation to subsequent subscriber input.

Regarding the implementation shown in FIG. 4, as discussed in more detail below, settings are first included for determining whether and how “in-focus” (highlighted) or “selected” (responsive to a SELECT key being pressed) program titles in the interactive program guide affect the reduced screen. A user typically moves a highlighted cursor around the interactive program guide using the arrow keys (UP, DOWN, RIGHT, LEFT) on the remote control 27, thus changing the “in-focus” program. In addition, the interactive program guide can be configured to use numeric and/or non-numeric channel keys to exit the interactive program guide and turn to the requested channel, tune the reduced screen to the requested channel, or make the requested channel the “in-focus” channel within the interactive program guide (which would then cause such keys to defer to the setting of the above selection regarding the effect of the “in-focus” indication.

FIG. 5 is an example screen diagram of the IPG display 70 that illustrates an initial guide arrangement in a time format that the DHCT 16 as depicted in FIG. 2 presents the user. The top left portion of the main IPG display 70 is a detailed focus area 71 that includes detailed channel information (channel number, channel name (ABC), program name, program description, duration, any episode information or rating, etc.) for an “in-focus” program corresponding to highlighted program area 72 in a main program display area 76. Video showing on the channel to which the DHCT 16 is currently tuned (for which audio is also playing, and which is typically the program occupying the full screen before the IPG 38 is activated) is displayed in a roughly one-quarter screen reduced screen display area 73 in the IPG display 70. Immediately below the reduced screen display area 73 is an information banner 74 depicting the channel to which the DHCT 16 is currently tuned, the current day and date, and the current time. The middle left portion of the IPG display 70 includes a channel area 78 that is related to the selected ordering format and is described in more detail below. The middle portion of the IPG display 70 includes a heading area 77 that contains headings related to the information displayed in the channel area 78 and the main program display area 76. The main program display area 76 contains television program titles corresponding to television programs that are or will be available for viewing during the time periods listed the heading area 77. The highlighted program area 72 is centered in the main program display area 76 enabling the subscriber to scroll up and down to the various program titles listed in the main program display area 76.

The main program display area 76 includes program names, or titles, organized in a grid of rows of channels and columns of time. The channel area 78 includes a vertical list of channels organized sequentially from top to bottom by increasing channel number. The main program display area 76 can be scrolled with the arrow keys on the remote control 27 in both time and channel number dimensions. The time dimensions are a horizontal array of program names categorized in columns of times in which they are broadcast. As the subscriber scrolls in time across a calendar day boundary, the selected day displayed in various areas is automatically updated.

When the IPG 38 (FIG. 2) is first activated by the subscriber and the time view is configured to be the initial view, the first, or lowest, channel, including channel name and number, in the channel lineup is centered in the channel area 78 of the IPG display 70. In this non-limiting example, the lowest channel in this channel list displayed in the channel area 78 is ABC, which is shown as channel 2. Continuing with this non-limiting example, the left-most time column in the main program display area 76 is set to include titles of programs scheduled to be broadcast about two hours into the future with the middle title being “in-focus” and corresponding to a program on the lowest available channel. Therefore, in this example, the program ABC news which is on channel 2, is centered in the highlighted program area 72. It should be noted that the current program shown in reduced screen display area 73 and referenced in information banner 74, corresponds to channel 10 and not to the in-focus program on channel 2. The bottom area 75 of IPG display 70 indicates the selected day for which program data is being displayed as well as the options for the “A”, “B”, and “C” keys on the remote 27 (FIG. 2). The “A” key is assigned to invoke a “Browse-by” menu which would enable subscribers to select alternative program guide arrangement views such as, for example, program guides containing television program information arranged on the basis of title or theme. The “B” key enables the subscriber to select an alternative date for which television program information is presented. Operation of the “C” key results in the program currently showing on the channel to which the DHCT is tuned becoming the “in-focus” program; thus, the displaying of television program titles in the main program display area 76 which correspond to television programs that are or will be playing during an aggregate time period that includes the current time. The time periods listed in the heading area 77 are updated accordingly so that the time period listed above the left most column of the main display area 76 includes the current time.

FIG. 6 is an example screen diagram of the IPG display 80 that illustrates how the tuning of the reduced screen display area 73 operates when the “REDUCED SCREEN TUNING UNRELATED TO IN-FOCUS CHANNEL” option in FIG. 4 is selected by a system operator at the headend. Under this scenario, by pressing a down arrow on the remote 27 (FIG. 2), a subscriber can cause the DHCT 16 to scroll through the IPG display 70 (FIG. 5) so that, in effect, the IPG display 80 as shown in FIG. 6 is displayed. Therefore, in this example, the program The Drew Carey Show, which is on channel 3, is centered in the highlighted program area 72. Notice that the channel number in information banner 74 still indicates channel number 10. This indicates that the reduced screen display area 73 is still tuned to channel 10 and that merely scrolling through the channel area 78 by the subscriber did not affect the tuning of the reduced screen display area 73. A similar result would occur if the “SELECTED IN-FOCUS CHANNEL DETERMINES REDUCED SCREEN” option were instead selected by the system operator. However, the results would change to those shown in FIG. 7 if the user then pressed the SELECT key on the remote 27 (FIG. 2). According to the shown embodiment, the current program is not the same as the “in-focus” program since they are approximately two hours apart. In other embodiments, an additional notice or menu will appear notifying and requesting confirmation that the user wishes to tune the reduced display area 73 to the current program on the selected channel.

FIG. 7 is also an example of the IPG display 90 that illustrates how the tuning of the reduced screen display area 73 operates while the “IN-FOCUS CHANNEL DETERMINES REDUCED SCREEN” option as illustrated in FIG. 4 is the active selection. Under this scenario, moving between FIG. 5 and FIG. 7 with the use of a down arrow on remote 27 (FIG. 2), the reduced screen display area 73 is tuned to channel 3 as indicated in the information banner 74 after the subscriber scrolls down to channel 3 in the channel area 78. It should be noted that if a subscriber scrolls quickly through the channels in the channel area 78, the reduced screen display portion 73 will not tune to the channel corresponding to the television program in the highlighted area 72 until after the subscriber has stopped scrolling for a predetermined amount of time, e.g., half a second.

FIG. 8 is an example of the IPG display 100 that illustrates how the tuning of the reduced screen display area 73 operates while the “NON-NUMERIC CHANNEL SIGNALS: TUNE REDUCED SCREEN TO REQUESTED CHANNEL” option in FIG. 4 is active, as transitioned from FIG. 7. Under this example scenario, after a subscriber uses the remote 27 (FIG. 2) to send the non-numeric channel key signal for “channel up,” such as a CH+ key on the remote, to the DHCT 16 as depicted in FIG. 2, the reduced screen display area 73 is tuned to channel 4 to display the current program on that channel as indicated in the information banner 74. If a subscriber were to send a “channel down” signal instead of a “channel up” signal, then the reduced screen display area would be tuned to channel 2 instead of channel 4. Likewise, the LAST and FAV keys would cause the last and favorite channels, as tracked by the navigator application 33 in the DHCT 16 (FIG. 2), to be tuned to display the current program on that channel in the reduced screen display area 73. Of course, if the “NON-NUMERIC CHANNEL SIGNALS: EXIT IPG AND TUNE TO REQUESTED CHANNEL” option in FIG. 4 is active, pushing the “channel up” key, for example, on the remote 27 (FIG. 2) would cause the IPG display 90 to disappear, and channel 4 would be tuned in full screen. Other non-numeric channel keys would likewise prompt similar results. However, if the “NON-NUMERIC CHANNEL SIGNALS: CHANGE IN-FOCUS CHANNEL TO REQUESTED CHANNEL” option in FIG. 4 is active, operation of any of the non-numeric channel keys would cause the current program on that requested channel to become the “in-focus” program, which may or may not affect the reduced screen display area 73 depending on the setting of the “IN-FOCUS CHANNEL DETERMINES REDUCED SCREEN” option, as discussed above.

FIG. 9 is an example of the IPG display 110 that illustrates how the tuning of the reduced screen display area 73 operates while the “NUMERIC CHANNEL SIGNALS: TUNE REDUCED SCREEN TO REQUESTED CHANNEL” option in FIG. 4 is active, as transitioned from FIG. 7. Under this scenario, after the subscriber uses the numeric “6” and “2” keys on the remote 27 (FIG. 2) to select channel 62, the reduced screen display area 73 is tuned to channel 62 as indicated in the information banner 74. Likewise, if the “NUMERIC CHANNEL SIGNALS: EXIT IPG AND TUNE TO REQUESTED CHANNEL” option in FIG. 4 is active, entering any channel numbers will cause the IPG display 90 to be removed from the screen, leaving the full screen tuned to the entered channel number. Furthermore, if the “NUMERIC CHANNEL SIGNALS: CHANGE IN-FOCUS CHANNEL TO REQUESTED CHANNEL” option is active, the program currently on that requested channel will become the “in-focus” channel, with the “IN-FOCUS CHANNEL DETERMINES REDUCED SCREEN” option determining whether such change in focus affects the reduced screen area 73.

An alternate embodiment of the invention provides a menu display accessed via the remote to allow the user to swap the position of the reduced screen area 73 and “in-focus” program information area 71 such that 71 is on the right and 73 on the left.

Additionally, an alternate embodiment of the invention includes the navigator application 33 applying the configurations for FIG. 4 “NON-NUMERIC CHANNEL SIGNALS” and “NUMERIC CHANNEL SIGNALS” to other applications that display on a portion of the screen with a reduced screen area showing the DHCT 16 channel as in reduced screen area 73. In a non-limiting example, an email application may be activated via the SAM and the current channel displayed reduced in the upper right ¼ screen. If the “NON-NUMERIC CHANNEL SIGNALS: TUNE REDUCED SCREEN TO REQUESTED CHANNEL” is selected by the system operator, subsequent user remote input for non-numeric channel keys such as CH+, CH−, LAST, FAV will change the channel in the reduced screen as directed via the remote command. Or, if “NON-NUMERIC CHANNEL SIGNALS: EXIT IPG AND TUNE TO REQUESTED CHANNEL” is selected by the system operator, subsequent user remote input for non-numeric channel keys such as CH+, CH−, LAST, FAV will exit the application and change the channel in the reduced screen as directed via the remote command. Similarly, the numeric channel signals configuration is interpreted by the navigator 33 as well.

It should be emphasized that the above-described embodiments of the present invention, particularly, any “preferred embodiments” are merely possible examples of the implementations, merely set forth for a clear understanding of the principles of the inventions. Many variations and modifications may be made to the above-described embodiments of the invention without departing substantially from the spirit of 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.

Claims

1. A method for providing video content via a television, comprising the steps of:

providing a user with a menu that includes a plurality of options corresponding to respective control settings for controlling functionality of a channel navigation key, wherein the menu is displayed via the television;
receiving a first user input corresponding to one of the plurality of options that is configured to a first conditional terminate provision of an interactive program guide (IPG) having a plurality of television program listings;
providing the IPG;
receiving a second conditional user input corresponding to the channel navigation key; and
responsive to receiving the second conditional user input and responsive to having previously received the first conditional user input:
terminating providing of the IPG; and
providing a video presentation.

2. The method of claim 1, wherein a video display area is provided in conjunction with the IPG, and wherein the video presentation that is provided responsive to receiving the second conditional user input is different from a video presentation that is displayed in the video display area immediately prior to receiving the second conditional user input.

3. A method for providing video content via a television, comprising the steps of:

providing a user with a menu that includes a plurality of options corresponding to respective control settings for controlling functionality of numeral input keys, wherein the menu is displayed via the television;
receiving a first user input corresponding to one of the plurality of options that is configured to a first conditional terminate provision of an interactive program guide (IPG) having a plurality of television program listings;
providing the IPG;
receiving a second conditional user input corresponding to at least one of the numeral input keys; and
responsive to receiving the second conditional user input and responsive to having previously received the first conditional user input:
terminating provision of the IPG; and
providing a video presentation.

4. The method of claim 3, wherein a video display area is provided in conjunction with the IPG, and wherein the video presentation that is provided responsive to receiving the second conditional user input is different from a video presentation that is displayed in the video display area immediately prior to receiving the second conditional user input.

5. A television set-top terminal (STT) configured to output video signals to a television, the STT comprising:

at least one tuner configured to receive video signals corresponding to video presentations;
memory having stored therein program code; and
at least one processor that is programmed by the program code to enable the STT to:
provide a user with a menu that includes a plurality of options corresponding to respective control settings for controlling functionality of a channel navigation key, wherein the menu is displayed via the television;
receive a first user input corresponding to one of the plurality of options that is configured to a first conditional terminate provision of an interactive program guide (IPG) having a plurality of television program listings;
provide the IPG;
receive a second conditional user input corresponding to the channel navigation key; and
responsive to receiving the second conditional user input and responsive to having previously received the first conditional user input:
terminate provision of the IPG; and
provide a video presentation.

6. The television STT of claim 5, wherein a video display area is provided in conjunction with the IPG, and wherein the video presentation that is provided responsive to receiving the second user input is different from a video presentation that is displayed in the video display area immediately prior to receiving the second user input.

7. A television set-top terminal (STT) configured to output video signals to a television, the STT comprising:

at least one tuner configured to receive video signals corresponding to video presentations;
memory having stored therein program code; and
at least one processor that is programmed by the program code to enable the STT to:
provide a user with a menu that includes a plurality of options corresponding to respective control setting for controlling functionality of numeral input keys, wherein the menu is displayed via the television;
receive a first user input corresponding to one of the plurality of options that is configured to a first conditional terminate provision of an interactive program guide (IPG) having a plurality of television program listings;
provide the IPG;
receive a second conditional user input corresponding to at least one of the numeral input keys; and
responsive to receiving the second conditional user input and responsive to having previously received the first conditional user input:
terminate provision of the IPG; and
provide a video presentation.

8. The television set-top terminal of claim 7, wherein a video display area is provided in conjunction with the IPG, and wherein the video presentation that is provided responsive to receiving the second conditional user input is different from a video presentation that is displayed in the video display area immediately prior to receiving the second user input.

Referenced Cited
U.S. Patent Documents
3676580 July 1972 Beck
4586158 April 29, 1986 Brandle
4706121 November 10, 1987 Young
4751578 June 14, 1988 Reiter et al.
4821097 April 11, 1989 Robbins
4827250 May 2, 1989 Stallkamp
4885775 December 5, 1989 Lucas
4908713 March 13, 1990 Levine
4930158 May 29, 1990 Vogel
4949187 August 14, 1990 Cohen
4963994 October 16, 1990 Levine
4984152 January 8, 1991 Muller
4991011 February 5, 1991 Johnson et al.
5038211 August 6, 1991 Hallenbeck
5172413 December 15, 1992 Bradley et al.
5253066 October 12, 1993 Vogel
5291554 March 1, 1994 Morales
5293357 March 8, 1994 Hallenbeck
5317391 May 31, 1994 Banker et al.
5329590 July 12, 1994 Pond
5353121 October 4, 1994 Young et al.
5357276 October 18, 1994 Banker et al.
5359362 October 25, 1994 Lewis et al.
5371551 December 6, 1994 Logan et al.
5398071 March 14, 1995 Gove et al.
5410326 April 25, 1995 Goldstein
5410343 April 25, 1995 Coddington et al.
5410344 April 25, 1995 Graves et al.
5414455 May 9, 1995 Hooper et al.
5418622 May 23, 1995 Takeuchi
5448313 September 5, 1995 Kim et al.
5477262 December 19, 1995 Banker et al.
5479268 December 26, 1995 Young et al.
5481542 January 2, 1996 Logston et al.
5483277 January 9, 1996 Granger
5493638 February 20, 1996 Hooper et al.
5508815 April 16, 1996 Levine
5512958 April 30, 1996 Rzeszewski
5515495 May 7, 1996 Ikemoto
5521631 May 28, 1996 Budow et al.
5530754 June 25, 1996 Garfinkle
5532735 July 2, 1996 Blahut et al.
5532754 July 2, 1996 Young et al.
5544354 August 6, 1996 May et al.
5555441 September 10, 1996 Haddad
5557541 September 17, 1996 Schulhof et al.
5562732 October 8, 1996 Eisenberg
5568272 October 22, 1996 Levine
5583560 December 10, 1996 Florin et al.
5583995 December 10, 1996 Gardner et al.
5585821 December 17, 1996 Ishikura et al.
5585838 December 17, 1996 Lawler et al.
5589892 December 31, 1996 Knee et al.
5592551 January 7, 1997 Lett et al.
5594509 January 14, 1997 Florin et al.
5598524 January 28, 1997 Johnston, Jr. et al.
5600364 February 4, 1997 Hendricks et al.
5600573 February 4, 1997 Hendricks et al.
5614940 March 25, 1997 Cobbley et al.
5619247 April 8, 1997 Russo
5619249 April 8, 1997 Billock et al.
5621456 April 15, 1997 Florin et al.
5623613 April 22, 1997 Rowe et al.
5625405 April 29, 1997 DuLac et al.
5625864 April 29, 1997 Budow et al.
5629732 May 13, 1997 Moskowitz et al.
5631693 May 20, 1997 Wunderlich et al.
5632681 May 27, 1997 Bakoglu et al.
5635979 June 3, 1997 Kostreski et al.
5635980 June 3, 1997 Lin et al.
5635989 June 3, 1997 Rothmuller
5650831 July 22, 1997 Farwell
5659350 August 19, 1997 Hendricks et al.
5666293 September 9, 1997 Metz et al.
5671411 September 23, 1997 Watts et al.
5675752 October 7, 1997 Scott et al.
5682206 October 28, 1997 Wehmeyer et al.
5682597 October 28, 1997 Ganek et al.
5684918 November 4, 1997 Abecassis
5686954 November 11, 1997 Yoshinobu et al.
5687331 November 11, 1997 Volk et al.
5689641 November 18, 1997 Ludwig et al.
5694176 December 2, 1997 Bruette et al.
5694546 December 2, 1997 Reisman
5699107 December 16, 1997 Lawler et al.
5715169 February 3, 1998 Noguchi
5715515 February 3, 1998 Akins, III et al.
5721827 February 24, 1998 Logan et al.
5721829 February 24, 1998 Dunn et al.
5721897 February 24, 1998 Rubinstein
5724106 March 3, 1998 Autry et al.
5724521 March 3, 1998 Dedrick
5724646 March 3, 1998 Ganek et al.
5727060 March 10, 1998 Young
5729549 March 17, 1998 Kostreski et al.
5732216 March 24, 1998 Logan et al.
5734853 March 31, 1998 Hendricks et al.
5737028 April 7, 1998 Bertram et al.
5740304 April 14, 1998 Katsuyama et al.
5740549 April 1998 Reilly et al.
5745837 April 28, 1998 Fuhrmann
5748493 May 5, 1998 Lightfoot et al.
5751282 May 12, 1998 Girard et al.
5752160 May 12, 1998 Dunn
5754773 May 19, 1998 Ozden et al.
5764873 June 9, 1998 Magid et al.
5764899 June 9, 1998 Eggleston et al.
5771435 June 23, 1998 Brown
5774170 June 30, 1998 Hite et al.
5778077 July 7, 1998 Davidson
5790170 August 4, 1998 Suzuki
5790176 August 4, 1998 Craig
5790935 August 4, 1998 Payton
5790940 August 4, 1998 Laborde et al.
5796828 August 18, 1998 Tsukamoto et al.
5798785 August 25, 1998 Hendricks et al.
5799063 August 25, 1998 Krane
5801747 September 1, 1998 Bedard
5801787 September 1, 1998 Schein et al.
5802502 September 1, 1998 Gell et al.
5808608 September 15, 1998 Young et al.
5808611 September 15, 1998 Johnson et al.
5809204 September 15, 1998 Young et al.
5812123 September 22, 1998 Rowe et al.
5812124 September 22, 1998 Eick et al.
5812786 September 22, 1998 Seazholtz et al.
5822123 October 13, 1998 Davis et al.
5826110 October 20, 1998 Ozden et al.
5828419 October 27, 1998 Bruette et al.
5828845 October 27, 1998 Jagadish et al.
5835843 November 10, 1998 Haddad
5838314 November 17, 1998 Neel et al.
5844620 December 1, 1998 Coleman et al.
5848352 December 8, 1998 Dougherty et al.
5850218 December 15, 1998 LaJoie et al.
5856975 January 5, 1999 Rostoker et al.
5859641 January 12, 1999 Cave
5861906 January 19, 1999 Dunn et al.
5877756 March 2, 1999 Um
5880768 March 9, 1999 Lemmons et al.
5886690 March 23, 1999 Pond et al.
5886732 March 23, 1999 Humpleman
5895454 April 20, 1999 Harrington
5898456 April 27, 1999 Wahl
5900905 May 4, 1999 Shoff et al.
5905522 May 18, 1999 Lawler
5905942 May 18, 1999 Stoel et al.
5907323 May 25, 1999 Lawler et al.
5913040 June 15, 1999 Rakavy et al.
5914712 June 22, 1999 Sartain et al.
5914746 June 22, 1999 Matthews, III et al.
5915068 June 22, 1999 Levine
5917822 June 29, 1999 Lyles et al.
5929849 July 27, 1999 Kikinis
5930493 July 27, 1999 Ottesen et al.
5935206 August 10, 1999 Dixon et al.
5936659 August 10, 1999 Viswanathan et al.
5940073 August 17, 1999 Klosterman et al.
5943047 August 24, 1999 Suzuki
5956024 September 21, 1999 Strickland et al.
5956716 September 21, 1999 Kenner et al.
5960411 September 28, 1999 Hartman et al.
5961603 October 5, 1999 Kunkel et al.
5969748 October 19, 1999 Casement et al.
5978043 November 2, 1999 Blonstein et al.
5983273 November 9, 1999 White et al.
5986650 November 16, 1999 Ellis et al.
5987256 November 16, 1999 Wu et al.
5990881 November 23, 1999 Inoue et al.
5990890 November 23, 1999 Etheredge
5990927 November 23, 1999 Hendricks et al.
5995134 November 30, 1999 Hayashi
6002401 December 14, 1999 Baker
6005565 December 21, 1999 Legall et al.
6005631 December 21, 1999 Anderson et al.
6006257 December 21, 1999 Slezak
6008803 December 28, 1999 Rowe et al.
6008836 December 28, 1999 Bruck et al.
6014184 January 11, 2000 Knee et al.
6014694 January 11, 2000 Aharoni et al.
6016348 January 18, 2000 Blatter et al.
6018359 January 25, 2000 Kermode
6018372 January 25, 2000 Etheredge
6020912 February 1, 2000 De Lang
6023267 February 8, 2000 Chapuis et al.
6025837 February 15, 2000 Matthews, III et al.
6025868 February 15, 2000 Russo
6025869 February 15, 2000 Stas et al.
6026376 February 15, 2000 Kenney
6035281 March 7, 2000 Crosskey et al.
6037933 March 14, 2000 Blonstein et al.
6049831 April 11, 2000 Gardell et al.
6057872 May 2, 2000 Candelore
6061097 May 9, 2000 Satterfield
6064380 May 16, 2000 Swenson et al.
6064980 May 16, 2000 Jacobi et al.
6070186 May 30, 2000 Nishio
6072982 June 6, 2000 Haddad
6073105 June 6, 2000 Sutcliffe et al.
6075575 June 13, 2000 Schein et al.
6081263 June 27, 2000 LeGall et al.
6085185 July 4, 2000 Matsuzawa et al.
6094680 July 25, 2000 Hokanson
6097383 August 1, 2000 Gaughan et al.
6098082 August 1, 2000 Gibbon et al.
6101512 August 8, 2000 DeRose et al.
6108002 August 22, 2000 Ishizaki
6108042 August 22, 2000 Adams et al.
6118445 September 12, 2000 Nonomura et al.
6118976 September 12, 2000 Arias et al.
6124878 September 26, 2000 Adams et al.
6125259 September 26, 2000 Perlman
6133909 October 17, 2000 Schein et al.
6137539 October 24, 2000 Lownes et al.
6138139 October 24, 2000 Beck et al.
6141003 October 31, 2000 Chor et al.
6141488 October 31, 2000 Knudson et al.
6148332 November 14, 2000 Brewer et al.
6151059 November 21, 2000 Schein et al.
6157377 December 5, 2000 Shah-Nazaroff et al.
6157413 December 5, 2000 Hanafee et al.
6160546 December 12, 2000 Thompson et al.
6160989 December 12, 2000 Hendricks et al.
6163272 December 19, 2000 Goode et al.
6166730 December 26, 2000 Goode et al.
6169543 January 2, 2001 Wehmeyer
6172674 January 9, 2001 Etheredge
6172677 January 9, 2001 Stautner et al.
6177931 January 23, 2001 Alexander et al.
6181333 January 30, 2001 Chaney et al.
6181693 January 30, 2001 Maresca
6182287 January 30, 2001 Schneidewend et al.
6184877 February 6, 2001 Dodson et al.
6188684 February 13, 2001 Setoyama et al.
6195689 February 27, 2001 Bahlmann
6201540 March 13, 2001 Gallup et al.
6205485 March 20, 2001 Kikinis
6208335 March 27, 2001 Gordon et al.
6209130 March 27, 2001 Rector et al.
6216264 April 10, 2001 Maze et al.
6238290 May 29, 2001 Tarr et al.
6239845 May 29, 2001 Itagaki et al.
6240555 May 29, 2001 Shoff et al.
6243142 June 5, 2001 Mugura et al.
6249532 June 19, 2001 Yoshikawa et al.
6253375 June 26, 2001 Gordon et al.
6259733 July 10, 2001 Kaye et al.
6266814 July 24, 2001 Lemmons et al.
6268849 July 31, 2001 Boyer et al.
6272484 August 7, 2001 Martin et al.
6275268 August 14, 2001 Ellis et al.
6282713 August 28, 2001 Kitsukawa et al.
6289346 September 11, 2001 Milewski et al.
6289514 September 11, 2001 Link et al.
6292624 September 18, 2001 Saib et al.
6305019 October 16, 2001 Dyer et al.
6311011 October 30, 2001 Kuroda
6314572 November 6, 2001 LaRocca et al.
6314573 November 6, 2001 Gordon et al.
6314575 November 6, 2001 Billock et al.
6317777 November 13, 2001 Skarbo et al.
6317885 November 13, 2001 Fries
6323911 November 27, 2001 Schein et al.
6327628 December 4, 2001 Anuff et al.
6335936 January 1, 2002 Bossemeyer, Jr. et al.
6347400 February 12, 2002 Ohkura et al.
6349410 February 19, 2002 Lortz
6353448 March 5, 2002 Scarborough et al.
6357046 March 12, 2002 Thompson et al.
6359636 March 19, 2002 Schindler et al.
6360367 March 19, 2002 Yamamoto
6362841 March 26, 2002 Nykanen
6367078 April 2, 2002 Lasky
6378130 April 23, 2002 Adams
6381332 April 30, 2002 Glaab
6385614 May 7, 2002 Vellandi
6393585 May 21, 2002 Houha et al.
6396549 May 28, 2002 Weber
6400280 June 4, 2002 Osakabe
6401243 June 4, 2002 Suzuki
6405239 June 11, 2002 Addington et al.
6421067 July 16, 2002 Kamen et al.
6434748 August 13, 2002 Shen et al.
6441862 August 27, 2002 Yuen et al.
6442332 August 27, 2002 Knudson et al.
6442755 August 27, 2002 Lemmons et al.
6442756 August 27, 2002 Durden et al.
6446261 September 3, 2002 Rosser
6446262 September 3, 2002 Malaure et al.
6460181 October 1, 2002 Donnelly
6463585 October 8, 2002 Hendricks et al.
6476833 November 5, 2002 Moshfeghi
6480669 November 12, 2002 Tsumagari et al.
6481010 November 12, 2002 Nishikawa et al.
6481011 November 12, 2002 Lemmons
6486920 November 26, 2002 Arai et al.
6501902 December 31, 2002 Wang
6505348 January 7, 2003 Knowles et al.
6507949 January 14, 2003 Jonason et al.
6510556 January 21, 2003 Kusaba et al.
6515680 February 4, 2003 Hendricks et al.
6515710 February 4, 2003 Koshimuta
6519770 February 11, 2003 Ford
6526575 February 25, 2003 McCoy et al.
6526577 February 25, 2003 Knudson et al.
6532589 March 11, 2003 Proehl et al.
6536041 March 18, 2003 Knudson et al.
6539548 March 25, 2003 Hendricks et al.
6543053 April 1, 2003 Li et al.
6545669 April 8, 2003 Kinawi et al.
6557030 April 29, 2003 Hoang
6563515 May 13, 2003 Reynolds et al.
6564378 May 13, 2003 Satterfield et al.
6564379 May 13, 2003 Knudson et al.
6564383 May 13, 2003 Combs et al.
6571390 May 27, 2003 Dunn et al.
6574793 June 3, 2003 Ngo et al.
6578077 June 10, 2003 Rakoshitz et al.
6594699 July 15, 2003 Sahai et al.
6594825 July 15, 2003 Goldschmidt Iki et al.
6600496 July 29, 2003 Wagner et al.
6604240 August 5, 2003 Ellis et al.
6609253 August 19, 2003 Swix et al.
6611958 August 26, 2003 Shintani et al.
6614440 September 2, 2003 Bowen et al.
6614988 September 2, 2003 Sampsell
6628302 September 30, 2003 White et al.
6631413 October 7, 2003 Aggarwal et al.
6642939 November 4, 2003 Vallone et al.
6647548 November 11, 2003 Lu et al.
6651044 November 18, 2003 Stoneman
6662365 December 9, 2003 Sullivan et al.
6665869 December 16, 2003 Ellis et al.
6671328 December 30, 2003 Poon et al.
6675384 January 6, 2004 Block et al.
6675385 January 6, 2004 Wang
6678891 January 13, 2004 Wilcox et al.
6681395 January 20, 2004 Nishi
6681396 January 20, 2004 Bates et al.
6684025 January 27, 2004 Perlman
6684400 January 27, 2004 Goode et al.
6697376 February 24, 2004 Son et al.
6698023 February 24, 2004 Levitan
6701523 March 2, 2004 Hancock et al.
6701528 March 2, 2004 Arsenault et al.
6706311 March 16, 2004 Wong et al.
6708336 March 16, 2004 Bruette
6717590 April 6, 2004 Sullivan et al.
6718552 April 6, 2004 Goode
6725461 April 20, 2004 Dougherty et al.
6731310 May 4, 2004 Craycroft et al.
6732367 May 4, 2004 Ellis et al.
6732369 May 4, 2004 Leftwich et al.
6732372 May 4, 2004 Tomita et al.
6735572 May 11, 2004 Landesmann
6738982 May 18, 2004 Jerding
6757909 June 29, 2004 Maruo et al.
6760918 July 6, 2004 Rodriguez et al.
6769127 July 27, 2004 Bonomi et al.
6771290 August 3, 2004 Hoyle
6772209 August 3, 2004 Chernock et al.
6772433 August 3, 2004 LaJoie et al.
6782550 August 24, 2004 Cao
6791620 September 14, 2004 Elswick et al.
6792615 September 14, 2004 Rowe et al.
6801533 October 5, 2004 Barkley
6817028 November 9, 2004 Jerding et al.
6832386 December 14, 2004 Jerding et al.
6847969 January 25, 2005 Mathai et al.
6876628 April 5, 2005 Howard et al.
6898762 May 24, 2005 Ellis et al.
6901385 May 31, 2005 Okamoto et al.
6957386 October 18, 2005 Nishina et al.
6968372 November 22, 2005 Thompson et al.
6978310 December 20, 2005 Rodriguez et al.
6978475 December 20, 2005 Kunin et al.
6986156 January 10, 2006 Rodriguez et al.
6990676 January 24, 2006 Proehl et al.
6990677 January 24, 2006 Pietraszak et al.
6993782 January 31, 2006 Newberry et al.
7010801 March 7, 2006 Jerding et al.
7024681 April 4, 2006 Fransman et al.
7039944 May 2, 2006 Cho et al.
7062466 June 13, 2006 Wagner et al.
7076734 July 11, 2006 Wolff et al.
7086077 August 1, 2006 Giammaressi
7103903 September 5, 2006 Kydd
7110714 September 19, 2006 Kay et al.
7117440 October 3, 2006 Gordon et al.
7120926 October 10, 2006 Safadi et al.
7143430 November 28, 2006 Fingerman et al.
7150031 December 12, 2006 Rodriguez et al.
7155733 December 26, 2006 Rodriguez et al.
7185355 February 27, 2007 Ellis et al.
7188356 March 6, 2007 Miura et al.
7194757 March 20, 2007 Fish et al.
7200857 April 3, 2007 Rodriguez et al.
7237251 June 26, 2007 Oz et al.
7243364 July 10, 2007 Dunn et al.
7249366 July 24, 2007 Flavin
7324552 January 29, 2008 Galand et al.
7324553 January 29, 2008 Varier et al.
7334251 February 19, 2008 Rodriguez et al.
7340759 March 4, 2008 Rodriguez
7343614 March 11, 2008 Hendricks et al.
7356477 April 8, 2008 Allan et al.
7404200 July 22, 2008 Hailey et al.
7496943 February 24, 2009 Goldberg et al.
7496945 February 24, 2009 Rodriguez
7509267 March 24, 2009 Yarmolich et al.
7512964 March 31, 2009 Rodriguez et al.
7526788 April 28, 2009 Rodriguez
7647549 January 12, 2010 Denoual et al.
7673314 March 2, 2010 Ellis et al.
7685520 March 23, 2010 Rashkovskiy et al.
7707614 April 27, 2010 Krikorian et al.
20010003846 June 14, 2001 Rowe et al.
20010013125 August 9, 2001 Kitsukawa et al.
20010013127 August 9, 2001 Tomita et al.
20010029523 October 11, 2001 Mcternan et al.
20010030667 October 18, 2001 Kelts
20010032335 October 18, 2001 Jones
20010034763 October 25, 2001 Jacobs et al.
20010036271 November 1, 2001 Javed
20010044744 November 22, 2001 Rhoads
20020002642 January 3, 2002 Tyson et al.
20020007485 January 17, 2002 Rodriguez et al.
20020026496 February 28, 2002 Boyer et al.
20020026638 February 28, 2002 Eldering et al.
20020032638 March 14, 2002 Arora et al.
20020032728 March 14, 2002 Sako et al.
20020032905 March 14, 2002 Sherr et al.
20020042913 April 11, 2002 Ellis et al.
20020044762 April 18, 2002 Wood et al.
20020049804 April 25, 2002 Rodriguez et al.
20020049978 April 25, 2002 Rodriguez et al.
20020056098 May 9, 2002 White
20020056118 May 9, 2002 Hunter et al.
20020057336 May 16, 2002 Gaul et al.
20020062481 May 23, 2002 Slaney et al.
20020069105 June 6, 2002 do Rosario Botelho
20020069218 June 6, 2002 Sull et al.
20020069412 June 6, 2002 Philips
20020078176 June 20, 2002 Nomura et al.
20020083443 June 27, 2002 Eldering et al.
20020101367 August 1, 2002 Geiger et al.
20020104083 August 1, 2002 Hendricks et al.
20020108125 August 8, 2002 Joao
20020124249 September 5, 2002 Shintani et al.
20020128908 September 12, 2002 Levin et al.
20030002862 January 2, 2003 Rodriguez et al.
20030014753 January 16, 2003 Beach et al.
20030030679 February 13, 2003 Jain
20030037068 February 20, 2003 Thomas et al.
20030061619 March 27, 2003 Giammaressi
20030067554 April 10, 2003 Klarfeld et al.
20030074214 April 17, 2003 Kelliher
20030074257 April 17, 2003 Saveliev et al.
20030079227 April 24, 2003 Knowles et al.
20030088872 May 8, 2003 Maissel et al.
20030101451 May 29, 2003 Bentolila et al.
20030101454 May 29, 2003 Ozer et al.
20030126425 July 3, 2003 Yang et al.
20030131356 July 10, 2003 Proehl et al.
20030135853 July 17, 2003 Goldman et al.
20030154475 August 14, 2003 Rodriguez et al.
20030154486 August 14, 2003 Dunn et al.
20030159147 August 21, 2003 Young et al.
20030174243 September 18, 2003 Arbeiter et al.
20030188313 October 2, 2003 Ellis et al.
20030193486 October 16, 2003 Estrop
20030206553 November 6, 2003 Surcouf et al.
20030219228 November 27, 2003 Thiagarajan et al.
20030221194 November 27, 2003 Thiagarajan et al.
20040034867 February 19, 2004 Rashkovskiy et al.
20040049787 March 11, 2004 Maissel et al.
20040107436 June 3, 2004 Ishizaki
20040117831 June 17, 2004 Ellis et al.
20040128685 July 1, 2004 Hassell et al.
20040133907 July 8, 2004 Rodriguez et al.
20040163117 August 19, 2004 Rodriguez et al.
20040181801 September 16, 2004 Hagen et al.
20040221310 November 4, 2004 Herrington et al.
20040261112 December 23, 2004 Hicks et al.
20040261125 December 23, 2004 Ellis et al.
20050008074 January 13, 2005 van Beek et al.
20050028190 February 3, 2005 Rodriguez et al.
20050044565 February 24, 2005 Jerding et al.
20050044566 February 24, 2005 Jerding et al.
20050044577 February 24, 2005 Jerding et al.
20050071882 March 31, 2005 Rodriguez et al.
20050076360 April 7, 2005 Jerding et al.
20050091693 April 28, 2005 Amine et al.
20050111046 May 26, 2005 Kurumisawa et al.
20050138657 June 23, 2005 Leftwich
20050155056 July 14, 2005 Knee et al.
20050160468 July 21, 2005 Rodriguez et al.
20050188415 August 25, 2005 Riley
20050204387 September 15, 2005 Knudson et al.
20050204388 September 15, 2005 Knudson et al.
20050213506 September 29, 2005 Wakumoto et al.
20050216936 September 29, 2005 Knudson et al.
20050240961 October 27, 2005 Jerding et al.
20050251822 November 10, 2005 Knowles et al.
20050278741 December 15, 2005 Robarts et al.
20050283797 December 22, 2005 Eldering et al.
20050283810 December 22, 2005 Ellis et al.
20050289618 December 29, 2005 Hardin
20060020982 January 26, 2006 Jerding et al.
20060026080 February 2, 2006 Rodriguez et al.
20060026665 February 2, 2006 Rodriguez et al.
20060059525 March 16, 2006 Jerding et al.
20060070107 March 30, 2006 Renkis
20060088105 April 27, 2006 Shen et al.
20060112434 May 25, 2006 Banker et al.
20060206913 September 14, 2006 Jerding et al.
20060271933 November 30, 2006 Agassi et al.
20060271964 November 30, 2006 Rodriguez et al.
20060271973 November 30, 2006 Jerding et al.
20070019670 January 25, 2007 Falardeau
20070053293 March 8, 2007 McDonald et al.
20070094690 April 26, 2007 Rodriguez et al.
20070136748 June 14, 2007 Rodriguez et al.
20070186240 August 9, 2007 Ward, III et al.
20080010658 January 10, 2008 Abbott et al.
20080098421 April 24, 2008 Rodriguez et al.
20080098422 April 24, 2008 Rodriguez et al.
20080101460 May 1, 2008 Rodriguez
20080104637 May 1, 2008 Rodriguez et al.
20080137755 June 12, 2008 Onur et al.
20080155631 June 26, 2008 Liwerant et al.
20080229361 September 18, 2008 Jerding et al.
20080279217 November 13, 2008 McDonald et al.
20080281968 November 13, 2008 Rodriguez
20080282307 November 13, 2008 McDonald et al.
20080282308 November 13, 2008 McDonald et al.
20090141794 June 4, 2009 Rodriguez et al.
20090150958 June 11, 2009 Jerding et al.
20090158306 June 18, 2009 Rodriguez et al.
20090158324 June 18, 2009 Rodriguez et al.
20090158329 June 18, 2009 Rodriguez et al.
20090158331 June 18, 2009 Rodriguez et al.
20090158332 June 18, 2009 Rodriguez et al.
20090158335 June 18, 2009 Rodriguez et al.
20090158339 June 18, 2009 Rodriguez et al.
20090158352 June 18, 2009 Rodriguez et al.
20090158354 June 18, 2009 Rodriguez et al.
20090158355 June 18, 2009 Rodriguez et al.
20090158363 June 18, 2009 Rodriguez et al.
20090183081 July 16, 2009 Rodriguez et al.
20090190028 July 30, 2009 Rodriguez et al.
20090193468 July 30, 2009 Rodriguez
20090193471 July 30, 2009 Rodriguez
20090276808 November 5, 2009 Jerding et al.
20090282372 November 12, 2009 Jerding et al.
20090282440 November 12, 2009 Rodriguez
20100242063 September 23, 2010 Slaney et al.
Foreign Patent Documents
2 363 052 November 1995 CA
2 223 025 November 2001 CA
0 572 090 December 1993 EP
0 673 159 September 1995 EP
0 680 214 November 1995 EP
0 725 538 August 1996 EP
0 763 936 March 1997 EP
0 811 939 December 1997 EP
0 838 915 April 1998 EP
0 849 948 June 1998 EP
0 854 645 July 1998 EP
0 891 084 January 1999 EP
0 896 318 February 1999 EP
0 909 095 April 1999 EP
0 701 756 December 1999 EP
0 989 751 March 2000 EP
1 069 801 January 2001 EP
1 075 143 February 2001 EP
1 111 572 June 2001 EP
1 161 085 December 2001 EP
2 343 051 April 2000 GB
8-289219 November 1996 JP
9-322022 December 1997 JP
10-143734 May 1998 JP
11-73361 March 1999 JP
11-73394 March 1999 JP
11-164284 June 1999 JP
2000-101941 April 2000 JP
WO 92/22983 December 1992 WO
WO 94/14284 June 1994 WO
WO 96/17467 June 1996 WO
WO 96/33579 October 1996 WO
WO 96/34486 October 1996 WO
WO 96/34491 October 1996 WO
WO 96/41477 December 1996 WO
WO 96/41478 December 1996 WO
WO 97/34414 September 1997 WO
WO 98/03012 January 1998 WO
WO 98/26528 June 1998 WO
WO 98/31116 July 1998 WO
WO 98/37695 August 1998 WO
WO 98/39893 September 1998 WO
WO 98/48566 October 1998 WO
WO 98/56172 December 1998 WO
WO 98/56173 December 1998 WO
WO 98/56188 December 1998 WO
WO 99/01984 January 1999 WO
WO 99/04560 January 1999 WO
WO 99/04561 January 1999 WO
WO 99/12109 March 1999 WO
WO 99/14947 March 1999 WO
WO 99/35831 July 1999 WO
WO 99/45701 September 1999 WO
WO 99/49717 October 1999 WO
WO 99/52285 October 1999 WO
WO 99/57903 November 1999 WO
WO 99/60790 November 1999 WO
WO 99/66719 December 1999 WO
WO 00/02385 January 2000 WO
WO 00/04726 January 2000 WO
WO 00/05889 February 2000 WO
WO 00/30354 May 2000 WO
WO 00/40017 July 2000 WO
WO 00/46988 August 2000 WO
WO 00/49801 August 2000 WO
WO 00/59202 October 2000 WO
WO 00/60482 October 2000 WO
WO 00/78031 December 2000 WO
WO 00/78045 December 2000 WO
WO 00/78047 December 2000 WO
WO 00/78048 December 2000 WO
WO 01/06788 January 2001 WO
WO 01/20907 March 2001 WO
WO 01/24067 April 2001 WO
WO 01/56273 August 2001 WO
WO 01/67736 September 2001 WO
WO 01/72042 September 2001 WO
WO 01/76245 October 2001 WO
WO 01/77888 October 2001 WO
WO 01/84831 November 2001 WO
WO 02/097584 December 2002 WO
WO 03/003164 January 2003 WO
WO 03/003709 January 2003 WO
WO 03/014873 February 2003 WO
WO 03/024084 March 2003 WO
WO 03/042787 May 2003 WO
WO 03/069898 August 2003 WO
WO 2004/091219 October 2004 WO
WO 2004/100500 November 2004 WO
WO 2005/059202 June 2005 WO
WO 2005/071658 August 2005 WO
WO 2007/030370 March 2007 WO
Other references
  • “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 Jun. 1, 2010.
  • 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 Jun. 9, 2010.
  • 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.
  • Summons to attend oral proceedings pursuant to Rule 115(1) EPC in European Application No. 02737593.0-1241 mailed May 28, 2010.
  • 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 SerU.S. Appl. ial 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. 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. 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. Final Office Action cited in U.S. Appl. No. 09/896,231 mailed May 28, 2010.
  • 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. Non-Final Office Action cited in U.S. Appl. No. 10/934,253 mailed Apr. 27, 2010.
  • U.S. Final Office Action cited in U.S. Appl. No. 10/934,253 mailed Dec. 23, 2009.
  • U.S. Non-Final Office Action cited in U.S. Appl. No. 10/934,253 mailed Jun. 26, 2009.
  • U.S. Final Office Action cited in U.S. Appl. No. 10/934,253 mailed Dec. 26, 2008.
  • U.S. Non-Final Office Action cited in U.S. Appl. No. 10/934,253 mailed Jun. 17, 2008.
  • U.S. Final Office Action cited in U.S. Appl. No. 10/934,253 mailed Jul. 24, 2007.
  • U.S. Non-Final Office Action cited in U.S. Appl. No. 10/934,253 mailed Feb. 9, 2007.
  • U.S. Non-Final Office Action cited in U.S. Appl. No. 10/934,253 mailed Sep. 14, 2006.
  • 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. 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. 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. 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/678,653 mailed Dec. 16, 2009.
  • 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. 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. 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/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. Final Office Action cited in U.S. Appl. No. 12/372,917 mailed May 17, 2010.
  • U.S. Non-Final Office Action cited in U.S. Appl. No. 12/372,917 mailed Oct. 26, 2009.
  • 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/388,139 mailed Dec. 15, 2009.
  • 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/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. Final Office Action cited in U.S. Appl. No. 12/413,686 mailed Jun. 10, 2010.
  • 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. Final Office Action cited in U.S. Appl. No. 10/761,777 mailed Aug. 2, 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. 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. 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.
  • 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. 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.
  • U.S. Non-Final Office Action cited in U.S. Appl. No. 11/170,348 mailed Oct. 26, 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. 10/740,138 mailed Oct. 27, 2010, 23 pages.
  • U.S. Non-Final Office Action cited in U.S. Appl. No. 10/934,253 mailed Nov. 4, 2010, 10 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/179,763 mailed Jan. 4, 2011, 18 pages.
Patent History
Patent number: 7934235
Type: Grant
Filed: Feb 20, 2004
Date of Patent: Apr 26, 2011
Patent Publication Number: 20040168191
Inventors: Dean F. Jerding (Roswell, GA), Robert O. Banker (Cumming, GA), Arturo A. Rodriguez (Norcross, GA)
Primary Examiner: Joseph P Hirl
Assistant Examiner: Fred Peng
Attorney: Merchant and Gould, P.C.
Application Number: 10/783,235
Classifications
Current U.S. Class: Navigational Feature (725/52); Operator Interface (725/37); To Facilitate Tuning Or Selection Of Video Signal (725/38); Electronic Program Guide (725/39)
International Classification: G06F 3/00 (20060101); G06F 13/00 (20060101); H04N 5/445 (20060101);