Patent Grant
8156528
The present invention relates to personal video recorder (PVR) systems and, more particularly, to PVR systems that include user television equipment having an interactive television program guide (IPG) with PVR extensions implemented thereon.
Products have recently been developed that allow users to manage their viewing experiences and record media with increased flexibility. PVRs, such as those provided by TiVo™ and ReplayTV™, record programs on hard-disk drives configured for multi-media storage. Users may schedule programs to be recorded and may play back the recorded programs at a later time. These products also record what users are watching in real-time, allowing users to pause real-time programs when, for example, the user must leave the room. The product may continue recording and storing the program being broadcast while the displayed program is paused. Users may resume their viewing where they left off, and may fast forward through commercials until they reach the point at which the program is currently being provided.
Interactive television applications, such as IPGs, are now widely available to the general public. IPGs may be used to provide interactive television services. Interactive television services include services for allowing a user to tune to a program, set parental locks, record a program, set reminders, etc.
IPGs may allow users to record programs on digital or analog storage devices (e.g., videocassettes, hard disks, floppy discs, flash memory, recordable compact discs (CDs), and recordable digital versatile discs (DVDs)). Programs may also be recorded on a program guide server, Internet server, or other server. The program guide server may be located at, for example, the cable system headend. The program guide may be an on-line program guide, which may be implemented using a web server on the Internet.
However, in most cases, the IPGs that facilitate television viewing remain separate from the applications that offer PVR functionality. For example, PVRs may include IPGs that are separate from the IPGs provided by other user equipment (e.g., a set-top box) and may require input devices and graphic interfaces separate from those used with existing IPGs. Subsequently, users often experience difficulty integrating existing IPGs with video recording applications.
It would therefore be desirable to provide an interactive television system having PVR functionality in which the user may use an IPG seamlessly with PVR functionality.
In view of the foregoing, it is an object of the present invention to provide an interactive television system having PVR functionality in which the user may use an IPG seamlessly with PVR functionality.
This and other objects of the present invention are accomplished by providing a PVR-compliant media recording system with an architecture that may include, for example, a PVR device, PVR application programming interfaces (APIs), PVR extensions, storage devices, and any additional hardware or software, or combination thereof, for the purpose of integrating PVR functionality to an IPG.
The high-level hardware architecture may involve a PVR-compliant device and PVR equipment having a PVR device. The PVR-compliant device may include an IPG that provides a user with the ability to record television programming. The user may control the IPG functionality by sending a command to the PVR-compliant device. A signal corresponding to the command may be generated by the PVR-compliant device and may be communicated to and executed by the PVR device.
The PVR-compliant device may include software and hardware configured to implement an IPG, PVR extensions, and PVR APIs. The PVR device may be coupled to the PVR-compliant device, and the PVR APIs may be configured to facilitate communications between the PVR device and the PVR-compliant device. The PVR device may include software and hardware configured to implement an IPG, PVR extensions, and PVR APIS.
The PVR-compliant device may include hardware interfaces and software interfaces that may provide an IPG with PVR features. The PVR extensions and PVR APIs may be configured to provide a seamless integration of IPVR functionality with the IPG. For example, PVR-compliant applications may interface with existing IPGs implemented in other hardware, such as a set-top box, to perform the PVR functions.
When coupled to a PVR device, the PVR-compliant device may detect the PVR device being coupled, determine the type of PVR device being used based on information received from the PVR device, and establish communications with the PVR device based on the information received. This may be accomplished using intelligent PVR APIs implemented in the PVR-compliant device.
In a similar manner, the PVR device may detect the PVR-compliant device being coupled, determine the type of PVR-compliant device being used based on information received from the PVR-compliant device, and establish communications with the PVR-compliant device based on the information received. This may be accomplished using PVR APIs implemented in the PVR device.
A full-port of the IPG may be implemented in both the PVR equipment and the set-top box. A full-port of the IPG is a full implementation of the IPG application that includes of all features and functions associated with the IPG. In this dual-platform arrangement, where the IPG is implemented in both the PVR equipment and the set-top box, the integrated IPG may be used to provide PVR features and functionality when PVR equipment is being used. The dual-platform arrangement also allows either the PVR equipment or the set-top box to be used independently as a stand-alone system. Other configurations for integrating PVR features and functions may also be used.
The objects and advantages of the invention will be apparent upon consideration of the following detailed description, taken in conjunction with the accompanying drawings, in which like reference characters refer to like parts throughout, and in which:
An illustrative interactive television system in accordance with the principles of the present invention is shown in
Main facility 102 may include server 104 for storing and distributing IPG information from program guide database 106. Program guide database 106 may store program guide information such as television program listings information, service listings information, program-related information, VOD program information, pay-per-view ordering information, promotional information, or any other suitable program guide information. Main facility 102 may distribute the program guide information to distribution facility 110 via communications path 108.
Communications path 108 may be any suitable communications path, such as a satellite link, a cable link, a fiber-optic link, a microwave link, a telephone network link, an Internet link, or a combination thereof. If it is desired to transmit video signals (e.g., television programs) over communications path 108 in addition to data signals, a relatively high bandwidth link such as a satellite link may be preferable to a relatively low bandwidth link such as a telephone line. Only one distribution facility 110 is shown in
The program guide information or content transmitted by main facility 102 to distribution facility 110 may include television program listings data (such as program times, channels, titles, descriptions, program type, genre, actors) or any other suitable data.
The promotional information transmitted by main facility 102 to distribution facility 110 may include various promotional banners, promotional ads, promotional slogans, promotional advertisements, or any other suitable promotional material.
Distribution facility 110 may be a television distribution facility for broadcast television, a cable system headend, a satellite distribution facility, or any other suitable distribution facility for distributing signals to viewers. Distribution facility 110 may distribute program guide information, programming content, or any other suitable content or information to user equipment 122 via communications paths 114. Distribution facility 110 may include server 112 for storing such content and information. Server 112 may be used for distributing television programming, music, or any other suitable type of media in response, for example, to requests for such content and information. Server 112 may include a local database 116 for storing various information and content (e.g., program guide information) or for storing recorded programs remotely. Storing recorded programs remotely on a server at the distribution facility may be an alternative to a storage media in the user's home. Client-server based interactive television systems with remote server recording are illustratively described, for example, in Ellis, et al. U.S. patent application Ser. No. 09/332,244, filed Jun. 11, 1999, which is hereby incorporated by reference herein in its entirety. Additional techniques for storing programs and program information are illustratively described, for example, in Hassell, et al. U.S. patent application Ser. No. 09/157,256, filed Sep. 17, 1998 which is hereby incorporated by reference herein in its entirety. In addition, server 112 may be capable of providing other interactive services such as near video-on-demand and video-on-demand. Server 112 may include one or more computers.
If desired, some or all of the information distributed to distribution facility 110 may be provided using information sources other than main facility 102. For example, distribution facility 110 may receive information from wide area network 118 (e.g., the Internet) via communications path 120. Communications path 120 may be a T1 link, a digital subscriber line (DSL) link, a cable modem link, an analog modem link, or any other suitable link.
If desired, data may be provided to user equipment 122 using facilities other than main facility 102 and distribution facility 110. For example, user equipment 122 may receive data directly from wide area network 118 via communications path 62. Communications path 62 may be a T1 link, a DSL link, a cable modem link, an analog modem link, radio frequencies such as a paging system, or any other suitable link. In another example, a separate facility such as a satellite broadcasting system (not shown) may transmit data to user equipment 122, which may receive data via a satellite receiving system (not shown).
Communications path 114 may be any suitable type of link that allows distribution facility 110 to distribute program guide information, television programming, or any other suitable information, data, or media to user equipment 122. There may be more than one communications path 114 that couples each user equipment 122 to distribution facility 110. For example, if distribution facility 110 is a cable headend, user equipment 122 may receive information via a cable link and may transmit information to distribution facility 110 via a digital serial link, a dial-up modem connection, or any other suitable link. Each of communication paths 114 may be unidirectional or bi-directional.
User equipment 122 may be configured to send or receive e-mails via communication path 122 or communications path 120. User equipment 114 may receive e-mails that were sent by distribution facility 110 or by some other facility.
An interactive television application, in accordance with the embodiments described herein, may be implemented in user equipment 122 to provide interactive services to a user. Interactive services may enable a user to interact with television applications, for example, by setting particular channels as favorites, by changing channels, by ordering pay-per-view (PPV) movies, by selecting programs to be recorded, by playing recorded programs, etc. An interactive television application may be an IPG application, or an interactive personal video recorder application that may be used to provide interactive services to users.
User equipment 122 may be based on a television platform, a computer platform, or both. For example, user equipment 122 may include user television equipment (e.g., a television set, a PVR, and a set-top box), user computer equipment (e.g., a desktop computer, a laptop computer, a handheld computing device such as a personal digital assistant or any other small personal computing device, etc.), or any other suitable user equipment for implementing an IPG. User computer equipment may include a computer based receiver having integrated set-top box circuitry or a personal computer television (PC/TV). If desired, user television equipment may include computer equipment for receiving e-mails.
As shown in
Set-top box 302 may receive signals transmitted by distribution facility 110 (
Set-top box 302 may be coupled to recording device 304. Recording device 304 may include PVR 308, VCR 310, or any other suitable recording device. Recording device 304 may include one or both of PVR 308 and VCR 310. If the user desires to record a program, set-top box 302 may be manually or automatically tuned to a particular channel and control signals may be sent to recording device 304 to record that program. Data link 309 may couple PVR 308 and VCR 310, and may be a cable link or any other suitable data link. Data link 309 may be used to transfer audio/video signals for programs between PVR 308 and VCR 310.
Set-top box 302 may send audio/video signals and signals that are representative of graphics to display device 306 for presentation to the user. If desired, set-top box 302 may route signals to display device 306 through recording device 304. Display device 306 may be a television, a computer monitor, a computer system with a monitor and speakers, a flat panel display, or any other suitable display device.
Set-top box 302 may be arranged in a client/server relationship with PVR 308. In one embodiment of the present invention, set-top box 302 may function as a server and PVR 308 may function as a client. All requests for information received from remote control 312 or other input devices may be routed first through the set-top box 302. If, for example, a user requests PVR information or a PVR recording, the request may first be processed by set-top box 302 which may communicate with PVR 308 to obtain the information or recording. Set-top box 302 may send audio/video signals and signals that are representative of graphics to display device 306 based on the communications with PVR 308. Other arrangements for establishing communications and operations between PVR 308, set-top box 302, and display device 306 may also be used.
A user may interact with any of the components in user television equipment 300 and with an IPG using one or more input devices, such as remote control 312. Remote control 312 may have various buttons that may be pressed by the user to interact with portions of an IPG. For illustrative purposes, many aspects of the present invention are discussed primarily in the context of an input device that is a remote control. Other suitable input devices such as a conventional keyboard, a wireless keyboard, a touch screen display remote, a handheld computer, a mouse, a trackball, or a touch pad may also be used.
An IPG may be implemented locally on user equipment 300 or may be implemented using a client-server or distributed architecture where some of the program guide application is implemented locally on user equipment 300. Client-server program guides are illustratively described, for example, in Ellis et al. U.S. patent application Ser. No. 09/374,043, filed Aug. 13, 1999, which is hereby incorporated by reference herein in its entirety. If desired, an IPG for providing the features and functionalities discussed herein may be partly implemented in PVR 308, set-top box 302, or both.
Remote control 408 may include alphanumeric buttons 404 that may be used for entry of alphanumeric characters. Alphanumeric buttons 404 may further include last button 434 which may provide the user with the ability to return to the last channel that was watched or the last screen that was displayed.
Remote control 408 may include task buttons 406 that may provide means for directing a task to be performed by user equipment (e. g., user equipment 300 of
In one embodiment of the present invention, interactive television system 100 (
IPG 502 may be any IPG capable of displaying program information made available through distribution facility 110. PVR extensions 504 may include any suitable hardware, software, or both that may be used in conjunction with IPG 502 or any other suitable interactive television application. In one suitable approach, PVR extensions 504 may be implemented together with IPG 502 (e. g., as part of a single software component). In another suitable approach, PVR extensions 504 may be implemented separately from IPG 502 (e. g., as a separate software module), but may work in conjunction with IPG 502 as a separate functional component.
Whether separate from IPG 502 or integrated as part of IPG 502, PVR extensions 504 may enable a seamless integration of IPG 502 with PVR functionality. This seamless integration may include, for example, using the same interface motif for PVR-related functions as is used for IPG-related functions. By providing such add-on PVR-enabling features to IPG 502, PVR equipment may be combined with IPG 502 to provide a single interface with which to operate both IPG 502 and the PVR equipment.
In one suitable approach, PVR equipment having a PVR device may be coupled to PVR-compliant device 500 to provide PVR functionality. PVR equipment may include any combination of software, hardware, or both that provides PVR functionality using a PVR. PVR equipment may include, for example, a PVR sidecar, a PVR server, an integrated set-top box, or any other suitable hardware, software, or both that enables PVR functionality.
PVR APIs 506 may be used to facilitate communication between the IPG and the PVR equipment. PVR APIs 506 may provide a set of routines, protocols, tools, or a combination thereof, for communicating with the PVR device.
In one suitable approach, in the absence of an API standard for use with the PVR device, PVR APIs 506 may be vendor-specific. More particularly, in this approach, only certain PVR devices may be used in conjunction with PVR-compliant device 500. For example, PVR devices may be made to be compatible with a particular PVR-compliant device 500having vendor-specific PVR APIs 506. Alternatively, PVR-compliant device 500 having vendor-specific PVR APIs 506 may be made to be compatible with a particular PVR device. A PVR vendor may be responsible for implementing PVR APIs 506 for a specific PVR device.
In another suitable approach, PVR APIs 506 may be vendor-independent (e. g., based on industry standard or proprietary standard PVR APIs). Designing PVR APIs 506 in this way may allow IPG 502 to be developed independently from the PVR device, providing flexibility in the selection of the PVR device. Also, PVR devices may be developed independently from PVR APIs 506.
PVR APIs 506 may include functionality for determining the type (model, manufacturer, etc.) of PVR device being used. For example, PVR APIs 506 may include a library of multiple vendor-specific APIs, generic APIs, or both. In this approach, PVR APIs 506 may be used to determine which of the vendor-specific APIs should be used based on a determination of the type of PVR device coupled to PVR-compliant device 500 or by any other suitable criteria (e. g., using firmware 508, PVR extensions 504, or IPG 502).
In one suitable arrangement, PVR APIs 506 having a library of intelligent APIs may be implemented in PVR-compliant device 500. In this arrangement, PVR APIs 506 may automatically detect the PVR device when coupled to PVR-compliant device 500, test and diagnose the PVR device, and automatically generate the driver source code for the specific PVR device being used.
In another suitable arrangement, PVR APIs 506 having a library of intelligent APIs may be implemented in the PVR device. In this arrangement, PVR APIs 506 may automatically detect PVR-compliant device 500 when coupled to the PVR device, test and diagnose PVR-compliant device 500, and communicate with the specific PVR-compliant device 500 using the appropriate corresponding APIs.
The foregoing description of monitoring techniques that may be used by PVR-compliant device 500 and the PVR device are to illustrate embodiments where the PVR device is implemented in PVR equipment separate from the PVR-compliant device. Such monitoring and detection would not be necessary if the PVR device were integrated into PVR-compliant device 500. However, in another suitable arrangement, PVR-compliant device 500 may have peripheral component interconnect (PCI) interfaces, industry standard architecture (ISA) interfaces, integrated drive electronic (IDE) interfaces, small computer system interfaces (SCSI), or any other suitable interfaces that may be used to create an integrated device by way of the above-mentioned monitoring and detection.
After determining the appropriate PVR APIs to use in facilitating communication between the PVR device and PVR-compliant device 500, PVR APIs 506 may be used to execute any suitable functions, routines, or any other suitable programming constructs, to provide any suitable protocols, to provide any suitable tools, or to provide any combination thereof. For example, the following Tables 1-10 show illustrative programming constructs that may be provided by PVR APIs 506, such as general disk management, file support, video playback controls, video processing support, etc.
It will be understood that the PVR API programming constructs of Tables 1-10 are merely illustrative. Any other suitable API programming construct may be used instead of or in addition to those illustrated. It will further be understood that any suitable modification may be made to the APIs of Tables 1-10 in accordance with, for example, a particular arrangement of hardware, software, or both being used.
One suitable function of the PVR APIs is to facilitate communication between IPG 502 of PVR-compliant device 500 and the PVR device implemented in PVR equipment.
PVR device 802 may include any suitable hardware, software, or both including, for example, circuitry 804, memory 806 (e. g., random access memory a (RAM) or any other suitable solid state volatile or non-volatile memory devices), hardware interfaces 808 (e. g., serial interface (i. e. RS-232), parallel interface (i. e. high-performance parallel interface (HIPPI)), universal serial bus (USB) interface, FireWire (i. e. Institute of Electrical and Electronics Engineering (IEEE) 1394) interface, wireless interface (i. e. wireless application environment (WAE)), RGB component interface, RJ-45 interface, telephone line interface, Ethernet interface, coaxial cable interface, optical interface, or any other suitable interface), software drivers 810, processors 812, storage devices 814 (e. g., hard-drives or any other suitable magnetic storage devices, optical storage devices, or any other suitable storage devices), APIs 816, IPG or IPG-like applications 818, or any other suitable hardware or software. PVR device 802 may provide, among other things, functionality related to the recording, storage, scheduling, retrieval, and playback of television programming.
It will be understood that PVR-compliant device 500 and PVR device 802 may be used in any suitable arrangement with any suitable additional software, hardware, or both. For example, components of PVR-compliant device 500 and PVR device 802 may be interchanged or otherwise moved from one to the other in any suitable way.
In one suitable embodiment of the present invention, PVR-compliant device 500 may be used in conjunction with a PVR sidecar to provide PVR functionality as illustrated in
PVR sidecar 901 may communicate with set-top box 900 via communications path 910, which may be any suitable wired or wireless communications path. For example, if wire-based, communications path 910 may be a serial cable, parallel cable, telephone cable, fiber optic cable, coaxial cable, Ethernet cable, USB cable, FireWire cable, component video cables, composite cables, any other suitable wire-based communications path, or any combination thereof. If wireless, any suitable communications protocol or standard such as IEEE 802.11, wireless application protocol (WAP), radio frequency (RF), Bluetooth, (Extended) time division multiple access (TDMA), code-division multiple access (CDMA), global systems for mobile communications (GSM), or any other suitable wireless communications path or protocol may be used.
PVR extensions 902 may be combined with IPG 904 to create a single software component. If PVR extensions 902 are not implemented as part of IPG 904 (as shown herein), PVR extensions 902 may be independent software modules separate from IPG 904 and may communicate and function in conjunction with IPG 904. Programming modules that include PVR extensions 902 may be implemented locally using an installation device (e. g., a personal computer, personal digital assistant, USB installation device, etc.) or may be downloaded to set-top box 900 or PVR sidecar 901 from a remote location (e. g., a cable headend, a distribution facility (such as distribution facility 110), software support, a web server, or from any other suitable location) using a cable modem, an integrated services digital network (ISDN) modem, a DSL modem, a telephone modem, a virtual private network (VPN), wireless connection, or any other suitable communications path or protocol.
PVR device 802in PVR sidecar 901 may communicate with IPG 904 having PVR extensions 902 via PVR APIs 906. In
Communication between components implemented in the set-top box may occur via communications path 908, which may include serial connections, parallel connections, wireless connections, any suitable connection for communicating information, or any combination thereof.
In another suitable arrangement, as illustrated in
In
In
In the arrangement where the IPGs on the set-top box and PVR sidecar work in conjunction with one another, the set-top box port of the IPG may perform basic tuning functions, PPV functions, and authorization functions. The set-top box may receive out-of-band (OOB) data and may otherwise act as a pass-through for the PVR sidecar while the PVR sidecar may receive and process control commands from a remote control or any suitable user input device. A pass-through implies that, although the PVR sidecar is coupled to the set-top box, the PVR sidecar may be used as a communications medium for signals sent by the set-top box and may not provide any functionality. In this configuration, the PVR sidecar may generate all video overlays using, for example, a video overlay generator that may generate a user interface superimposed over programming being displayed.
In another suitable approach, set-top box 1400 may monitor any communication to and from PVR sidecar 1401 via communications path 1410. If PVR sidecar 1401 is not detected, the IPG may function as it does without PVR functionality, using its own port of the IPG to provide basic IPG features. If the PVR sidecar is detected, however, the IPG may support PVR functionality. If the sidecar is removed, the IPG may detect the change and function as though there is no sidecar present, causing the PVR sidecar to operate in pass-through mode.
In pass-through mode, the PVR sidecar may, for example, ignore all user commands from the IR remote control or may receive user commands and communicate them to the set-top box for execution. In pass-through mode, the PVR sidecar need not display programming or video overlays, but may rather pass this data directly from the set-top box to a display screen. In pass-through mode, the PVR sidecar may also perform passive functions such as accepting commands to purchase programming, maintaining in non-volatile memory all parental control settings, allowing parental control settings to be polled, checking whether a specific channel, rating, or title is locked, checking the validity of a parental control code or purchase code, or any other suitable function.
The IPG's PVR functions may be implemented using a set of generic PVR APIs to simplify the porting of the PVR-compliant device to the integrated set-top environment when it is available. PVR sidecar 1401 may also include a “porting layer” (not shown) that will simplify the porting of the IPG from set-top box 1400 to PVR sidecar 1401. This will be especially valuable if multiple sidecar platforms must be supported and may provide for a more seamless integration of the devices IPGs.
The PVR sidecar arrangement of
PVR sidecar 1504, set-top box 1502, or both may communicate with software support 1508 or any other remote site via communications path 1512. Software support 1508 may be for vendor-specific applications located at a remote software support site, with which the PVR-compliant device may communicate to download additional software applications, software upgrades or any other suitable component associated with the components implemented in PVR sidecar 1504, set-top box 1502, or both. Communications path 1512 may also be used to download information not specific to the PVR sidecar, such as program guide data. Communications path 1512 may be a serial connection, parallel connection, wireless connection, any other suitable connection, or any combination thereof.
PVR sidecar 1504, set-top box 1502, or both may upload user information to a remote site using communications path 1512. For example, PVR sidecar 1504 may be configured to communicate to with a remote site (such as a cable headend, distribution facility, software company, web server, or any other suitable location) information relating to a user's profile, preferred options, recorded programming, or any other information on PVR sidecar 1504 or set-top box 1502.
PVR sidecar 1504 may receive guide data from set-top box 1502 which may be passed from the IPG's data channel, such as an out-of-band (OOB) data channel. This approach may allow the system to be deployed without having to put a new data delivery infrastructure in place. The IPG data may be augmented to accommodate more data then could be supported by or would be needed by the set-top box alone (e. g., between 14 and 30 days of data, or any other suitable amount of data, may be stored). A separate data feed may be developed to support the PVR device. On a cold install, set-top box 1502 may tune to the non-PVR data channel until a sufficient amount of data is stored in local storage. The set-top may switch (under command from the sidecar) to the PVR feed. After a power outage, the set-top may tune immediately to the PVR feed because of data cached on the disk drive.
In certain arrangements, set-top box 1502 and PVR sidecar 1504 may communicate information using IR commands. For example, set-top box 1502 may receive an indication via an IR command from remote control 1516. Set-top box 1502 may then communicate the IR command to PVR sidecar 1504 via its own IR command. IR commands may be relayed from remote control 1516 to set-top box 1502 via PVR sidecar 1504 in other arrangements. In additional arrangements, IR commands may be sent to and from PVR sidecar 1504 and set-top box 1502 that do not originate from remote control 1516.
In the embodiment using the PVR sidecar, the PVR sidecar, set-top box, or both may also include third party applications to enable specific functionality or obtain a higher level of performance. Various classes of such third party applications may be used in conjunction with the PVR device. For example, applications may be independent of real-time video, or be time-dependant and rely on real-time video. These applications may be implemented in set-top box 1502 and launched by the IPG on PVR sidecar 1504 using commands sent over communications path 1510, which may be any suitable wired or wireless connection. When one of these applications launches, it may send a command to PVR device 802 (
In another embodiment of the present invention a PVR server may be used to implement PVR functionality as illustrated in
In
In
In another suitable arrangement, as shown in
In another embodiment of the present invention, shown in
By implementing PVR functionality to a PVR-compliant system in one of the foregoing manners, the IPG with PVR extensions may provide display screens with embedded PVR functions such as main menu display screen 2000 of
Main menu display screen 2000 may be provided by the IPG until the user selects an option such as an option from viewer services menu 2012 that may involve PVR functionality, for example recordings option 2018. In the embodiment where a set-top box is coupled to a PVR sidecar, the user may interact with main menu display screen 2000 using the IPG implemented in the set-top box. When the user selects recordings option 2018, the IPG may send a request for a display screen associated with the user's request to the PVR extensions, which may be provided by the set-top box or the PVR sidecar. The PVR extensions may then provide the IPG with a display screen associated with the user's request. If the PVR extensions are provided by the PVR sidecar, a communications path may be used for communications between the set-top box and the PVR sidecar. The IPG working in conjunction with the PVR extensions may provide the user with PVR functionality and information provided by a PVR device implemented in the PVR sidecar.
In one suitable arrangement, a full port of the IPG may be implemented in the set-top box, the PVR sidecar, or both. In this arrangement, display screens 2000, 2100 and 2200 may be provided by the PVR sidecar IPG while the set-top box IPG may perform functions in support of the PVR sidecar (i. e. managing PPV services).
In the embodiment using a PVR server, the IPG on the set-top box may send a request to the PVR extensions provided by the set-top box or the PVR server in response to the user selecting an option from viewer services menu 2012, such as recordings option 2018. The PVR extensions may then provide the IPG with a display screen associated with the user's request. If the PVR extensions are provided by the PVR server, a communications path may be used for communications between the set-top box and the PVR server. The IPG working in conjunction with the PVR extensions may provide the user with PVR functionality and information provided by a PVR device implemented in the PVR server.
In the embodiment using an integrated set-top box, both the IPG and the PVR extensions may be implemented in the set-top box. The IPG may send a request to the PVR extensions in response to the user selecting an option from viewer services menu 2012 such as recordings option 2018. The PVR extensions may then provide the IPG with a display screen associated with the user's request.
In a similar manner, search display screen 2100 of
Search display screen 2100 may be partially provided by the PVR device. For example, the program listings may include listings for both scheduled programs and recorded programs. The listings for the scheduled programs may be provided by the set-top box, and the listings for the recorded programs may be provided by the PVR device. The listings may include programs scheduled to be recorded, including an indication that they are to be recorded. The indication may be stored on the PVR device, and the set-top box may use the PVR device as a storage device to store program listings.
While interacting with search display screen 2100, the user may indicate a desire to record the given program using the IPG or an input device such as remote control 408 of
For example, the PVR extensions may provide the IPG with recording setup screen 2200, shown in
The user may modify the selected options by using left and right arrow keys on the remote control as indicated by scroll left 2214 and scroll right 2216 indicators. The user may select record option 2202 after modifying the various options available or may cancel the recording at any time by selecting cancel option 2212. If desired, the IPG may provide the user with the ability to set a manual recording by specifying a channel, date and time, and duration to record (not shown).
Recording setup display screen 2200 may be provided by an IPG working in conjunction with PVR extensions. The IPG may provide a seamless look and feel to the display screen while the PVR extensions may provide the selectable options. When the user submits finalized options to be recorded from recording setup display screen 2200, the IPG with PVR extensions may send a command to be executed by a PVR device. If the user selects to record a program that will occur at a later time, the IPG with PVR extensions may delay sending the command to the PVR device, or the PVR device may delay executing the command until the program occurs. PVR APIs may be used to facilitate communications between the IPG with PVR extensions and the PVR device.
The PVR device may be implemented in a PVR sidecar, PVR server, or an integrated set-top box. If located in a PVR server or sidecar, the PVR device may receive requests and provide functionality to the IPG and PVR extensions over a communications path via PVR APIS. Once the user selects record option 2202 and returns to screen 2100 of
The PVR-compliant device may allow the user to select quality at step 2310. The user may be able to select one of several recording qualities to control the amount of storage space required for recorded programs. For example, if the user selects higher quality more recording storage space may be required to record an individual program. By selecting lower recording quality, the user may be able to record more hours of programming in the same amount of storage space.
The user may then determine if the recording is a one-time or series recording at step 2312. A one-time recording may record a single occurrence of a program while a series recording may record all occurrences of the program. If the user selects a one-time recording 2318, the PVR-compliant device may then provide the user an opportunity to select the program buffers at step 2320. If the user selects a series recording 2314, the PVR-compliant device may first provide the user an opportunity to select other options at step 2316 before providing the user opportunity to select program buffers at step 2320. The additional options for a series recording may include the number of programs to keep on the PVR device, the channels to include in the recording (e. g., all channels or just a specific channel), etc.
Program buffers may be placed at the beginning and end of the scheduled program to ensure the entire program is recorded. The length of the buffer (s) may be selected by the user at step 2320. To help the viewer compensate for slight variations in broadcast times, the system may allow the viewer to specify an amount of time before and after the program to extend the recording time. For example, if the viewer knows that a program they watch regularly begins broadcasting two-minutes before the hour, the viewer may tell the IPG to begin recording two-minutes prior to the program's air-time to compensate for the early broadcast of the program. A detailed illustration of steps involved in applying buffers is later discussed in
When the user returns to the program listing at step 2322, the system may display program listings or other screen with record icons next to the programs that are scheduled to be recorded at step 2324. The recording process depicted in
It will be understood that the steps of the process depicted in
The PVR extensions have been designed to allow the viewer to initiate a recording with a single remote command anywhere a program appears in the IPG or while watching a program with no IPG screens or overlays. For example, the viewer may initiate a recording from a program listing screen, browse screen, flip bar, or program information screen simply by pressing the record key on the remote control (not shown).
When the viewer presses the record key while a program is selected on the user interface, the IPG may initiate a one-time recording and display an icon next to the program title indicating that a recording is currently scheduled for the program. Whenever the program listing appears on a display screen, the IPG may place the recording option next to the program title.
In response to the user initiating recording setup 2402, the system may provide the user an opportunity to allocate beginning and ending program buffers by selecting a time value in step 2404. In step 2406, the system may allocate the appropriate amount of storage space to accommodate the length of the buffers and the program being recorded. The system may then determine the time of recording in step 2408. In applying the beginning buffer 2410, the system may begin recording the program at the length of time selected by the user prior to the program's scheduled start time in step 2412. To apply the ending buffer 2414, the system may stop recording the program at the length of time selected by the user after the program is scheduled to end in step 2416.
Information may be provided to the IPG with PVR extensions by sending a request for information to a PVR device via PVR APIs. The PVR device may be located in, for example, an integrated set-top box, a PVR sidecar, or a PVR server. In response to receiving a request from the IPG and PVR extensions via PVR APIs, the PVR device may provide a list of programs scheduled to be recorded. The PVR device may also provide such information to designate each program scheduled to be recorded in the IPG with recording indicator 2108. In some embodiments, the IPG may store the information on programs to be recorded without using the PVR device.
The PVR-compliant device may provide access to scheduled recordings through a button on the main menu of the IPG. When the viewer wishes to modify the options for a scheduled recording or determine what recordings are scheduled, the viewer may access the scheduled recordings list such as the one depicted in
Once a program has been recorded by the PVR device, the IPG may provide recordings screen 2700, shown in
In another suitable approach (not shown), the list of recorded programs in display screen 2700 may be combined with the list of programs scheduled to be recorded in display screen 2500. The list of recorded programs and programs scheduled to be recorded may be further supplemented with all program listings that are scheduled to be presented by the IPG. Providing such integrated lists of programs may be an added convenience for the user.
Recordings screen 2700 may include a list of recorded programs 2704 that the user may select. Screen 2700 may present security icon 2702 to indicate that the listed program may only be viewed by certain users or by entering a control code. Users or control criteria may have been identified while the user modified other options 2316 in the recording setup process (
The user may view a previously recorded program by selecting the program from recordings display screen 2700. The IPG may send a request to the PVR extensions upon receiving indication from the user to view a recorded program and the PVR extensions may provide a display screen consistent with the user's indication. If desired, listings for recorded programs may be shown on other IPG screens.
In the embodiment where a set-top box is coupled to a PVR sidecar, the user may interact with recordings display screen 2700 using an IPG provided by the set-top box and PVR extensions provided by either the set-top box or the PVR sidecar. When the user selects a recording to view, the IPG and PVR extensions may send a request to a PVR device provided by the PVR sidecar to present the recording requested by the user. PVR APIs and a communications path between the set-top box and the PVR sidecar may be used to facilitate communications between the IPG, PVR extensions and the PVR device. Other embodiments may include an IPG provided wholly or partially by the PVR sidecar.
In the embodiment where a set-top box is coupled to a PVR server, the user may interact with recordings display screen 2700 using an IPG provided by the set-top box and PVR extensions provided by either the set-top box or the PVR server. When the user selects a recording to view, the IPG and PVR extensions may send a request to a PVR device provided by the PVR server to present the recording requested by the user. PVR APIs and a communications path between the set-top box and the PVR server may be used to facilitate communications between the IPG, PVR extensions, and the PVR device. Other suitable embodiments may include an IPG provided wholly or partially by the PVR server.
In the embodiment where an integrated set-top box is used, the user may interact with recordings display screen 2700 using an IPG and PVR extensions provided by the set-top box. When the user selects a recording to view, the IPG and PVR extensions may send a request to a PVR device provided by the set-top box to present the recording requested by the user. PVR APIs may be used to facilitate communications between the IPG, PVR extensions and the PVR device.
In any of these embodiments, in response to the IPG's request to present a recording, the PVR device may generate a presentation of the recording in display screen 2802 of
Video content of a recorded program may be provided by the PVR device and displayed in display screen 2802 of
It will be understood that the playback indicator may be smaller than flip bar 2816 and may not include all components illustrated in
The user may interact with the playback control functions using the IPG with PVR extensions or the remote control. The IPG may send commands to the PVR device based on the user's indication. For example, the user may pause the playback of a recorded program by selecting pause option 2812 on flip bar 2816 or by selecting pause button 440 on remote control 408 (
In
The foregoing is merely illustrative of the principles of this invention and various modifications may be made by those skilled in the art without departing from the scope and spirit of the invention. Those skilled in the art will appreciate that the present invention may be practiced by other than the described embodiments, which are presented for purposes of illustration and not of limitation, and the present invention is limited only by the claims.
This application claims the benefit of U.S. provisional patent application No. 60/278,079, filed Mar. 22, 2001, U.S. provisional patent application No. 60/284,951, filed Apr. 19, 2001, and U.S. provisional patent application No. 60/290,714, filed May 14, 2001, all of which are hereby incorporated by reference herein in their entireties.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4264924 | Freeman | Apr 1981 | A |
| 4264925 | Freeman et al. | Apr 1981 | A |
| 4573072 | Freeman | Feb 1986 | A |
| 4602279 | Freeman | Jul 1986 | A |
| 4706121 | Young | Nov 1987 | A |
| 4847698 | Freeman | Jul 1989 | A |
| 4847700 | Freeman | Jul 1989 | A |
| 4908707 | Kinghorn | Mar 1990 | A |
| 4945563 | Horton et al. | Jul 1990 | A |
| 4977455 | Young | Dec 1990 | A |
| 5038211 | Hallenbeck | Aug 1991 | A |
| 5047867 | Strubbe et al. | Sep 1991 | A |
| 5068733 | Bennett | Nov 1991 | A |
| 5151789 | Young | Sep 1992 | A |
| 5187589 | Kono et al. | Feb 1993 | A |
| 5195134 | Inoue | Mar 1993 | A |
| 5210611 | Yee et al. | May 1993 | A |
| 5223924 | Strubbe | Jun 1993 | A |
| RE34340 | Freeman | Aug 1993 | E |
| 5253066 | Vogel | Oct 1993 | A |
| 5285284 | Takashima et al. | Feb 1994 | A |
| 5296931 | Na | Mar 1994 | A |
| 5323234 | Kawasaki | Jun 1994 | A |
| 5353121 | Young et al. | Oct 1994 | A |
| 5410343 | Coddington et al. | Apr 1995 | A |
| 5410344 | Graves et al. | Apr 1995 | A |
| 5416508 | Sakuma et al. | May 1995 | A |
| 5459522 | Pint | Oct 1995 | A |
| 5475615 | Lin | Dec 1995 | A |
| 5479266 | Young et al. | Dec 1995 | A |
| 5479268 | Young et al. | Dec 1995 | A |
| 5483278 | Strubbe et al. | Jan 1996 | A |
| 5485197 | Hoarty | Jan 1996 | A |
| 5485219 | Woo | Jan 1996 | A |
| 5508732 | Bottomley et al. | Apr 1996 | A |
| 5515511 | Nguyen et al. | May 1996 | A |
| 5528281 | Grady et al. | Jun 1996 | A |
| 5532754 | Young et al. | Jul 1996 | A |
| 5534911 | Levitan | Jul 1996 | A |
| 5537141 | Harper et al. | Jul 1996 | A |
| 5539822 | Lett | Jul 1996 | A |
| 5541738 | Mankovitz | Jul 1996 | A |
| 5550576 | Klosterman | Aug 1996 | A |
| 5559548 | Davis et al. | Sep 1996 | A |
| 5559549 | Hendricks et al. | Sep 1996 | A |
| 5568272 | Levine | Oct 1996 | A |
| 5581800 | Fardeau et al. | Dec 1996 | A |
| 5585838 | Lawler et al. | Dec 1996 | A |
| 5585858 | Harper et al. | Dec 1996 | A |
| 5589892 | Knee et al. | Dec 1996 | A |
| 5592571 | Peters | Jan 1997 | A |
| 5600364 | Hendricks et al. | Feb 1997 | A |
| 5612729 | Ellis et al. | Mar 1997 | A |
| 5619274 | Roop et al. | Apr 1997 | A |
| 5629733 | Youman et al. | May 1997 | A |
| 5631995 | Weissensteiner et al. | May 1997 | A |
| 5632007 | Freeman | May 1997 | A |
| 5657414 | Lett et al. | Aug 1997 | A |
| 5684525 | Klosterman | Nov 1997 | A |
| 5694381 | Sako | Dec 1997 | A |
| 5699107 | Lawler et al. | Dec 1997 | A |
| 5724091 | Freeman et al. | Mar 1998 | A |
| 5727060 | Young | Mar 1998 | A |
| 5758257 | Herz et al. | May 1998 | A |
| 5790198 | Roop et al. | Aug 1998 | A |
| 5790202 | Kummer et al. | Aug 1998 | A |
| 5801787 | Schein et al. | Sep 1998 | A |
| 5805763 | Lawler et al. | Sep 1998 | A |
| 5808608 | Young et al. | Sep 1998 | A |
| 5809204 | Young et al. | Sep 1998 | A |
| 5812123 | Rowe et al. | Sep 1998 | A |
| 5812205 | Milnes et al. | Sep 1998 | A |
| 5812937 | Takahisa et al. | Sep 1998 | A |
| 5819156 | Belmont | Oct 1998 | A |
| 5828945 | Klosterman | Oct 1998 | A |
| 5838314 | Neel et al. | Nov 1998 | A |
| 5850218 | LaJoie et al. | Dec 1998 | A |
| 5886732 | Humpleman | Mar 1999 | A |
| 5940572 | Balaban et al. | Aug 1999 | A |
| 5956716 | Kenner et al. | Sep 1999 | A |
| 5959592 | Petruzzelli | Sep 1999 | A |
| 5963264 | Jackson | Oct 1999 | A |
| 5977964 | Williams et al. | Nov 1999 | A |
| 6057874 | Michaud | May 2000 | A |
| 6057890 | Virden et al. | May 2000 | A |
| 6072983 | Klosterman | Jun 2000 | A |
| 6133910 | Stinebruner | Oct 2000 | A |
| 6141488 | Knudson et al. | Oct 2000 | A |
| 6157413 | Hanafee et al. | Dec 2000 | A |
| 6163316 | Killian | Dec 2000 | A |
| 6177931 | Alexander et al. | Jan 2001 | B1 |
| 6208799 | Marsh et al. | Mar 2001 | B1 |
| 6233389 | Barton et al. | May 2001 | B1 |
| 6256390 | Okuyama et al. | Jul 2001 | B1 |
| 6275648 | Knudson et al. | Aug 2001 | B1 |
| 6289169 | Okuyama | Sep 2001 | B1 |
| 6324338 | Wood et al. | Nov 2001 | B1 |
| 6327418 | Barton | Dec 2001 | B1 |
| 6441862 | Yuen et al. | Aug 2002 | B1 |
| 6481013 | Dinwiddie et al. | Nov 2002 | B1 |
| 6717590 | Sullivan | Apr 2004 | B1 |
| 6748596 | Knudson et al. | Jun 2004 | B2 |
| 6754185 | Banerjee et al. | Jun 2004 | B1 |
| 6756997 | Ward et al. | Jun 2004 | B1 |
| 6879347 | French | Apr 2005 | B1 |
| 6882299 | Allport | Apr 2005 | B1 |
| 6976267 | Takano et al. | Dec 2005 | B1 |
| 6990676 | Proehl et al. | Jan 2006 | B1 |
| 20020059599 | Schein et al. | May 2002 | A1 |
| 20020095673 | Leung et al. | Jul 2002 | A1 |
| 20020154892 | Hoshen et al. | Oct 2002 | A1 |
| 20030044165 | Wood et al. | Mar 2003 | A1 |
| 20030142957 | Young et al. | Jul 2003 | A1 |
| 20080189742 | Ellis et al. | Aug 2008 | A1 |
| 20080189743 | Ellis et al. | Aug 2008 | A1 |
| Number | Date | Country |
|---|---|---|
| 0 682 452 | Nov 1995 | EP |
| 0 753 964 | Jan 1997 | EP |
| 0 836 320 | Apr 1998 | EP |
| 0 854 645 | Jul 1998 | EP |
| 0 969 661 | Jan 2000 | EP |
| 0 993 185 | Apr 2000 | EP |
| 2 227 622 | Aug 1990 | GB |
| 2 229 565 | Sep 1990 | GB |
| 2 346 251 | Aug 2000 | GB |
| WO 9323957 | Nov 1993 | WO |
| WO 9532587 | Nov 1995 | WO |
| WO 9626605 | Aug 1996 | WO |
| WO 9636172 | Nov 1996 | WO |
| WO 9637075 | Nov 1996 | WO |
| WO 9641478 | Dec 1996 | WO |
| WO 9713368 | Apr 1997 | WO |
| WO 9747136 | Dec 1997 | WO |
| WO 9748230 | Dec 1997 | WO |
| WO 9806219 | Feb 1998 | WO |
| WO 9847283 | Oct 1998 | WO |
| WO 9912346 | Mar 1999 | WO |
| WO 9945700 | Sep 1999 | WO |
| WO 9952279 | Oct 1999 | WO |
| WO 9957895 | Nov 1999 | WO |
| WO 9966725 | Dec 1999 | WO |
| WO 0008849 | Feb 2000 | WO |
| WO 0184834 | Nov 2001 | WO |
| WO 0193575 | Dec 2001 | WO |
| WO 0219691 | Mar 2002 | WO |
| Number | Date | Country | |
|---|---|---|---|
| 20020174433 A1 | Nov 2002 | US |
| Number | Date | Country | |
|---|---|---|---|
| 60278079 | Mar 2001 | US | |
| 60284951 | Apr 2001 | US | |
| 60290714 | May 2001 | US |
