This invention is directed to systems and methods for performing recordings with a network recording device when a user's equipment fails.
Recording devices, such as digital video recording (DVR) devices, are well known in the art. DVR devices use one or more hard drives to record programs that have been selected for recording. Such devices, however, can fail due to, for example, hard drive over-heating, software bugs, hardware component malfunction, power failure, or any other source of failure of the device. If the DVR device (or other equipment controlling the DVR device) fails during, prior or after to the transmission time of a program selected for recording, the DVR device will not perform the recording in its entirety for the user. If the selected program is not transmitted again in the near future, the user is left with no easy means of acquiring a copy of the program.
Accordingly, it would be desirable to provide digital recording systems and methods for performing recordings with a network recording device when a user's equipment fails.
This and other objects of the present invention are accomplished in accordance with the principles of the present invention by providing systems and methods for performing recordings with a network recording device when a user's equipment fails.
The user's equipment includes an interactive television application, such as an interactive program guide. The interactive television application performs recordings with a recording device, also included in the user's equipment. When the user's equipment fails, a network recording device determines that the user's equipment cannot perform one or more recordings and, in response, performs the one or more recordings on behalf of the user's equipment.
In some embodiments, the interactive television application may anticipate that the user's equipment will fail (e.g., that the hard drive of the DVR is overheating and will shut down). In response to the anticipation, the interactive television application may send the network recording device an indication of one or more recordings that were scheduled to be performed during the anticipated failure, as well as instructions to perform the one or more recordings on behalf of the user's equipment.
Once the failure of the user's equipment has been corrected, the network recording device may transfer the recordings it performed to the user's equipment. This may be conditioned on, for example, whether the user's equipment has sufficient resources (e.g., enough space and/or an available tuner) to record the programs transmitted from the network recording device. Alternatively, the network recording device may provide the recordings to the user's equipment as on-demand offerings.
The above and other features of the present invention, its nature and various advantages will be more apparent upon consideration of the following detailed description, taken in conjunction with the accompanying drawings in which:
Content source 120 may be any suitable content source such as, for example, a cable system headend, satellite television distribution facility, television broadcast facility, on-demand server (e.g., VOD server), or any other suitable facility or system for originating or distributing content. Content source 120 may be configured to transmit signals over any suitable communications path 122 including, for example, a satellite path, a fiber-optic path, a cable path, or any other suitable wired or wireless path. The signals may carry any suitable content such as, for example, television programs, games, music, news, web services, or any other suitable content.
User equipment 110 may include any equipment suitable for providing an interactive television experience. User equipment 110 may include television equipment such as a television, set-top box, recording device, video player, user input device (e.g., remote control, keyboard, mouse, touch pad, touch screen and voice recognition interface) or any other device suitable for providing an interactive television experience. For example, user equipment 110 may include a DCT 2000, 2500, 5100, 6208 or 6412 set-top box provided by Motorola, Inc. In some embodiments, user equipment 110 may include computer equipment, such as a personal computer with a television card (PCTV).
In the example of
Recording device 114 may be a personal video recorder (PVR), digital video recorder (DVR), video cassette recorder (VCR), DVD-recorder, or any other suitable video recorder. Recording device 114 may include one or more tuners.
Display device 112 may be any suitable device such as, for example, a television monitor or a computer monitor. Display device 112 may also be configured to provide for the output of audio.
Control circuitry 118 is adapted to receive user inputs from input device 116 and execute the instructions of the interactive television application. Control circuitry 118 may include one or more tuners (e.g., analog or digital tuners), encoders and decoders, processors (e.g., Motorola 68000 family processors), memory (i.e., RAM and hard disks), communications circuitry (e.g., cable modem circuitry), input/output circuitry (e.g., graphics circuitry), connections to the various devices of user equipment 110, and any other suitable component for providing analog or digital television programming, program recording, and interactive television features. In some embodiments, control circuitry 118 may be included as part of one of the devices of user equipment 110 such as, for example, part of recording device 114, display 112, or any other device (e.g., a set-top box, television and video player).
Any suitable number of users may have equipment, such as user equipment 110, connected to content source 120 and data source 124. But for the clarity of the figure, the equipment of only a single user is shown. The equipment of the plurality of users may be connected to content source 120 and data source 124 using a cable television network or any other suitable means. In some embodiments, the equipment of the plurality of users may be connected to each other using any suitable means.
User equipment 110 may receive interactive television application data from one or more data sources 124. Data sources 124 may provide data for a particular type of content or for a particular application. For example, one data source 124 may provide data for non-on-demand assets (e.g., non-pay and pay-per-view television programs), and another may provide data for on-demand assets (e.g., VOD programs). Or, for example, a single data source may provide both of these types of data. For example, one data source 124 may provide data for an interactive television program guide. Another data source 124 may, for example, provide data for another interactive television application running on user equipment 110 (e.g., a home shopping application). In some embodiments, data sources 124 may provide data to the interactive television application using a client/server approach. There may be one server per data source, one for all sources or, in some embodiments, a single server may communicate as a proxy between user equipment 110 and various data sources 124.
Illustrative interactive television system 100 includes network recording device 130. Network recording device 130 may be any suitable type of recording device including, for example, a PVR, DVR, VCR, DVD-recorder, hard-drive arrays, a server, or any other suitable video recorder. Network recording device 130 includes control circuitry 132 and memory 134 for executing, for example, recording operations. Control circuitry 132 may include one or more tuners, processors, communications circuitry, I/O circuitry connected to the various devices of interactive television system 100, or any other suitable component. In some embodiments, control circuitry 132 may direct tuners to tune to channels carrying programs requested for recording by other devices of interactive television system 100 (e.g., by user equipment 110) and record the programs in memory 134. In some embodiments, network recording device 130 has direct access to programs (e.g., via and internet protocol (e.g., file transfer protocol) connection to program content source 120). Memory 134 may be one or more of RAM, ROM, hard disks, or any other suitable memory. In the example of
In some embodiments, control circuitry 132 may receive instructions from the interactive television application or from content source 120. The instructions may include, for example, instructions to record programs, delete programs, transfer recorded programs, generate a stream to transmit programs (e.g., as a VOD offering), modify the deleting priorities or programs, or any other suitable instruction.
In some embodiments, network recording device 130 may be incorporated in content source 120 (e.g., at the head-end of a cable plant), data source 124, a VOD server (not shown), user equipment 110 (e.g., as a second recording device, or a hard drive on a home computer), an Internet server, or any other suitable device. In some embodiments, network recording device 130 may be a stand alone device (e.g., a commercial network recording device, or a DVR device in a home or neighborhood network).
To schedule a program or other suitable video for recording, a user may highlight a desired program, as shown in
Prior to choosing to record a program, the user may request additional information regarding the program. For example, the user may highlight a listing using highlight region 212 and press an “Information” key or key sequence on user input device 116. In response to receiving the user request, the interactive television application may display an information screen.
The user may be watching a program on display device 112 in a full screen view, for example full screen view 400 shown in
The interactive television application may prompt the user to set recording options for the program. For example, the interactive television application may display a screen or pop-up, such as recording options screen 500 shown in
It may occur that the user's equipment fails prior to or during a recording, thus preventing the user from having a suitable copy of the recording. The user's equipment may fail in any number of ways including, for example, failing to perform the recording and performing a recording that the user cannot play back fully or at all. Causes of such a failure may include, for example, loss of power to the user's equipment, failure of communications between the interactive television application and the recording device (e.g., recording device 114), failure of communications between the interactive television application and the content source (e.g., unplugged coax cable), malfunction of the control circuitry (e.g., control circuitry 118 or the control circuitry of recording device 114, including the recording device's I/O circuitry), recording device failure (e.g., overheating of hard drive or losing the address where the program is stored), interactive television application or recording device software error, or any other such failure. As another example, the user's equipment may receive an emergency alert signal (EAS) signal and be forced to tune away from a recording, causing the recording to fail.
Any suitable device from interactive television system 100 may determine that the user's equipment has failed, or will fail, to perform a local recording. For example, a remote device such as content source 120 or network recording device 130 may determine that the user's equipment has failed. As still another example, a local device associated with user equipment 100 (e.g., control circuitry 118) may determine that it has failed. For clarity, however, the following discussion will focus on the cases where the network recording device (e.g., network recording device 130) or the user's equipment, upon determining that the user's equipment has failed, or will fail, to perform a local recording.
The network recording device (e.g., network recording device 130) may determine whether the user's equipment has failed using any suitable approach. In some embodiments, the network recording device may determine that the user's equipment has failed by an interruption or fault in communications from the user's equipment. For example, network recording device 130 may request a communication from user equipment 120 and not receive a response. As another example, network recording device 130 may not receive a communication from user equipment 120 at a predefined or predetermined time at which user equipment 120 was supposed to send a communication. A suitable predefined or predetermined time may include, for example, just prior to when the user's equipment should start to perform a recording or while a recording is performed. The communications may include, for example, a “heartbeat” or “keep alive” signal, a status report, a report of user equipment 120's activity, or any other suitable communication.
If the communications take the form of status reports, the status reports may include status information for some or every component of the user's equipment (e.g., recording device 114, control circuitry 118, and display device 112). To prepare the status report, control circuitry 118 may, for example, receive reports from some or every component of user equipment 120, combine the reports, and transmit the combined report to network recording device 130. As another example, the one or more components of user equipment 120 may each transmit individual status reports to network recording device 130.
In some embodiments, instead of the interactive television application automatically providing the network recording device with status reports, the network recording device may request status reports from the interactive television application at scheduled or pre-defined times (e.g., at regular intervals or before the interactive television application is to start a recording).
In some embodiments, the user's equipment may anticipate a failure that will prevent it from performing one or more recordings. For example, the interactive television application may monitor the temperature of the recording device to determine whether the hard drive of the recording device will overheat. In some embodiments, a remote device (e.g., network recording device 130) may monitor the user's equipment and anticipate a failure (e.g., by remotely monitoring the temperature of the hard drive of recording device 114)
When the user's equipment anticipates a failure, it may send a communication to the network recording device to indicate the anticipated failure. Alternatively, if a remote device anticipates the failure, the remote device may send a communication to the user's equipment to inform it of the anticipated failure. The user's equipment may provide communications to the network recording device instructing it to perform one or more recordings that the user's equipment cannot perform because of the failure. The communication may identify which recordings to perform (e.g., based on how long the failure is expected to last, or recordings scheduled to be performed within a given time) and how to perform them (e.g., with what recording options). In some embodiments, the user's equipment may identify, either automatically or in response to a user instruction, only some of the initiated or scheduled recordings using any suitable criteria (e.g., recording options or recording theme).
When the user's equipment fails (e.g., a hard drive fails), but its communications circuitry (e.g., control circuitry 118) remains operational, the user's equipment may send a communication to the network recording device to indicate the failure. The user's equipment may also request that the network recording device perform recordings initiated or scheduled by the user's equipment that the user's equipment cannot perform, and identify such recordings and their associated recording options in the communication. The user's equipment may identify recordings scheduled to be performed within any suitable time (e.g., based on how long the failure is expected to last, or recordings scheduled to be performed within a given time). In some embodiments, the user's equipment may identify, either automatically or in response to a user instruction, only some of the initiated or scheduled recordings using any suitable criteria (e.g., recording options, priorities, cost of storage or recording theme). In response to the communication, the network recording device (e.g., network recording device 130) may perform the requested recordings.
When the user's equipment fails in such a way that communications are not possible with the network recording device, the network recording device must determine which programs to record. To identify the programs, prior to the failure, the user's equipment may send a communication to the network recording device indicating each recording that is initiated or scheduled by the user's equipment. The communication may include the recording options set for each recording. The user's equipment may send the communication to the network recording device at any suitable time such as, for example, when a recording is first initiated or scheduled, just prior to when a recording is to begin, during a recording, at regular intervals (e.g., every hour, every evening or every week), or at any other suitable time. When the user modifies the recording options or cancels a recording, the user's equipment may include the changes in its communication with the network recording device. Thus, when the network recording device determines that the user's equipment has failed, the network recording device already knows which recordings to perform for the user's equipment.
When the user's equipment fails after recordings have been performed in such a way that recordings are lost, the user's equipment may retrieve the recordings from other devices of interactive television system 100. One approach is for the network recording device (e.g., network recording device 130) to automatically record every recording that is initiated or scheduled by the user's equipment. The network recording device may conserve space for recording new programs by automatically deleting recordings based on any suitable priority scheme (e.g., deleting programs that the user has viewed or deleting programs with certain recording options).
In some embodiments, the interactive television application may direct the network recording device to perform failed recordings only when certain criteria are met. The criteria may include, for example, recording options (e.g., a recording priority), program attributes (e.g., a theme, an actor or the program is part of a series), or any other suitable criteria. In some embodiments, when the network recording device does not have sufficient resources to perform all of the failed recordings, the network recording device may perform only the recordings that satisfy certain criteria. To reduce the volume of communication between the user's equipment and the network recording device, the user's equipment may communicate to the network recording device only the recordings that satisfy the criteria.
The network recording device may hold the recordings that it performs for any suitable length of time. For example, the network recording device may hold recordings for a fixed time period (e.g., one week, one month), as long as the network recording device does not need the space to perform new recordings, until the user plays back the recording, or until the user's equipment instructs it to delete the recording. The network recording device (e.g., network recording device 130) may indicate that a recording is to be held by, for example, modifying an entry in memory 134 that is associated with the recording using control circuitry 132 to set the deleting priority of the recording to “do not delete”, “no flush,” or “save.”
In some cases, the network recording device may have already performed (e.g., on behalf of another user or in response to a previous instruction to perform the recording) a recording identified by the user's equipment. Rather than re-performing the recording, the network recording device may hold the recording for the user's equipment. For example, control circuitry 132 may modify an entry in memory 134 that is associated with the recording and set the deleting priority of the recording to “do not delete,” “do not flush,” or “save.”
The network recording device may determine that a failure of the user's equipment has been resolved in any suitable manner. In some embodiments, the network recording device may monitor its communications with the user's equipment. For example, the network recording device may periodically request status reports from the user's equipment, and determine that a failure has been resolved in response to receiving a status report that indicates that the user's equipment is operational. As another example, the network recording device may receive a communication automatically sent by the user's equipment that indicates that a failure has been resolved. In response to determining that the failure has been resolved, the network recording device may cancel recordings scheduled because of the user's equipment's failure and return the responsibility of performing the recordings to the user's equipment. The network recording device may, however, finish performing recordings that it has begun. In some embodiments, the network recording device may cancel the recordings only in response to an indication from the user's equipment that it will perform the recordings.
After a failure has been resolved and once the communications between the network recording device and the user's equipment have been reestablished, the network recording device may inform the user's equipment of the failure. This may be useful in cases where the user or the interactive television application did not know that the user's equipment failed to perform recordings.
In some embodiments, in response to determining that the user's equipment has failed (e.g., automatically, or in response to a notice from the network recording device), the interactive television application may display a failure notice to the user.
The user may transfer a recording from the network recording device to the user's equipment by selecting the listing associated with the recording (e.g., using highlight region 612) and selecting a transfer option (e.g., icon 620). In some embodiments, the interactive television application may mark the listing of a recording that is selected for transferring to the user's equipment in any suitable manner including, for example, placing an icon besides the listing (e.g., icon 614), placing a colored border around the listing, changing the color of the listing, changing the font of the listing, or any other suitable manner. In some embodiments, the user may cancel transferring a recording by selecting the listing associated with the recording and selecting a cancel option (e.g., icon 622).
In cases where the network recording device did not perform all of the initiated or scheduled recordings while the user's equipment had failed, the user may select an option (e.g., icon 604) to view the recordings that were not performed with the network recording device. The user may select an option to view all of the recordings performed by both the user's equipment and the network recording device (e.g., icon 606).
In response to selecting the option to view all of the performed recordings (e.g., icon 606), the interactive television application may display a recorded programs menu. One such menu is illustrative recorded programs menu 700, shown in
The listings may include both recordings performed with the user's equipment and recordings performed with the network recording device. In some embodiments, the interactive television application may differentiate the recordings performed with each recording device for the user. For example, the interactive television application may mark listings of recordings performed with one of the devices by placing an icon besides the listing (e.g., icon 708), placing a colored border around the listing, changing the color of the listing, changing the font of the listing, or by another suitable marking. In the example shown in
To play back a recording, the user may select the listing (e.g., using highlight region 712) associated with the recording from listings 702 and press a “play” key or key sequence on the user input device, select a play option from an interactive television application screen, or perform any other suitable step to initiate playback. If the selected recording was recorded by the user's equipment, the interactive television application may direct the user's equipment to play back the recording by, for example, directing the display device (e.g., display device 112) to display the selected recording.
If instead the selected recording was performed with the network recording device, the interactive television application may direct the network recording device to transmit the program to the user's equipment. For example, in response to a playback request, the network recording device may provide the recording to the user as a VOD offering (e.g., by generating and transmitting a video stream having the selected recording to the user's equipment). As another example, in response to the playback request, and provided the user's equipment has sufficient resources to store the recording (e.g., enough space and a tuner available for receiving the transmission), the network recorder may transfer the selected recording to the user's equipment. The user's equipment may play back the recording once the transfer is complete or while information is streaming to the user's equipment. The network recording device may delete a recording that has been transferred to the user's equipment to free resources.
Other uses for a combination of a network recording device and a user's equipment are described in commonly owned U.S. patent application Ser. No. 11/267,200, filed Nov. 4, 2005, entitled “SYSTEMS AND METHODS FOR RECORDING PROGRAMS USING A NETWORK RECORDING DEVICE AS SUPPLEMENTAL STORAGE,” and incorporated herein in its entirety.
The following flow charts serve to illustrate processes involved in some embodiments of this invention.
At step 820, network recording device 130 determines whether user equipment 110 has failed. Network recording device 130 may determine whether user equipment 110 has failed at any suitable time including, for example, at regular intervals, just prior to a recording beginning, during a recording (in which case a partial recording can be done by the network recording device and potentially combined with the pre-failure potion that was already recorded), or at any other suitable time. Network recording device 130 may determine whether user equipment 110 has failed in any suitable manner including, for example, requesting a communication from user equipment 110 and not receiving one.
If network recording device 130 determines that user equipment 110 has not failed, process 800 moves to step 830. At step 830, user equipment 820 performs recordings initiated or scheduled to be performed with user equipment 110 (e.g., recordings communicated at step 810). Process 800 then loops back to step 820 to determine whether, now at a later time, user equipment 110 has failed and is able to continue to perform recordings. Process 800 loops as long as user equipment 110 has recordings to perform.
If instead network recording device 130 determines that user equipment 110 has failed, process 800 moves to step 840. At step 840, network recording device 130 determines whether it has already performed a recording initiated or scheduled to be performed with user equipment 110 (e.g., a recording communicated to network recording device 130 at step 810). If network recording device 130 determines that it has previously performed a recording, process 800 moves to step 850. At step 850, network recording device 130 holds the recording for user equipment 110 (e.g., set the deleting priority of the programs to “do not delete,” “do not flush,” or “save”) rather than re-performing the same recording. Process 800 then, as in step 830, loops back to step 820 to determine whether, now at a later time, user equipment 110 has still failed or whether the failure has been resolved, and whether user equipment 110 can perform recordings again.
If instead network recording device 130 determines that it has not yet performed a recording, process 800 moves to step 860. At step 860, network recording device 130 performs the recording. Process 800 then, as in steps 830 and 850, loops back to step 820 to determine whether, now at a later time, user equipment 110 has still failed or whether the failure has been resolved, and whether user equipment 110 can perform recordings again.
At step 930, user equipment 110 identifies the recordings that were originally initiated or scheduled to be performed with user equipment 110, but that it will not be able to perform because of the anticipated failure. For example, user equipment 110 may identify all recordings that it was to perform in the next day, 2 days, or week. User equipment 110 may send network recording device 130 (
At step 940, user equipment 110 directs network recording device 130 to perform the recordings identified at step 930. For example, user equipment 110 may send network recording device 130 a communication with instructions to perform the recordings identified previously in another communication. Alternatively, user equipment 110 may identify which recordings to perform and direct network recording device 130 to perform the identified recordings in the same communication. If a recording has already been performed with network recording device 130, process 900 may skip step 940. Instead, network recording device 130 may hold the recording for user equipment 110 (e.g., set the deleting priority of the programs to “do not delete,” “do not flush,” or “save”) rather than re-performing the same recording. Process 900 then moves back to step 910 to determine whether user equipment 110 anticipates a new failure. Process 900 ends when user equipment 110 has no recordings left to perform.
If instead, at step 910, user equipment 110 determines that it is not anticipating a failure, process 900 moves to step 950. At step 950, user equipment 110 performs the recordings that it were initiated or scheduled for it to perform. Process 900 then moves back to step 910 to determine if, now at a later time, user equipment 110 anticipates a failure.
In some embodiments, instead of determining whether user equipment 110 anticipates a failure (i.e., step 910), user equipment 110 may determine whether it has failed but managed to maintain a communications link with network recording device 130. For example, user equipment 110 may determine whether control circuitry 118, including its communications circuitry, is operational, and recording device 114 (
If instead network recording device 130 determines that user equipment 110 has resolved the failure, process 1000 moves to step 1020. At step 1020, network recording device 130 sends a communication to user equipment 110 to inform it of the recordings that network recording device 130 performed while user equipment 110 had failed. In some cases, this communication may serve to indicate to user equipment 110 that it had failed.
At step 1030, user equipment 110 determines whether it has sufficient resources to store one or more recordings that were performed by network recording device 130. If user equipment 110 determines that it does not have sufficient resources to store one or more recordings, process 1000 moves to step 1040. At step 1040, network recording device 130 provides the recordings it performed to user equipment 110 as on-demand offerings. Process 1000 ends at step 1062.
If instead user equipment 110 determines that it has sufficient resources to store one or more recordings performed by network recording device 130, process 100 moves to step 1050. At step 1050, network recording device 130 transfers one or more recordings to user equipment 110. User equipment 110 stores the received recordings, for example with recording device 114 (
The above described embodiments of the present invention are presented for purposes of illustration and not of limitation, and the present invention is limited only by the claims which follow.
Number | Name | Date | Kind |
---|---|---|---|
4355415 | George et al. | Oct 1982 | A |
4605964 | Chard | Aug 1986 | A |
4694490 | Harvey et al. | Sep 1987 | A |
4706121 | Young | Nov 1987 | A |
4718107 | Hayes | Jan 1988 | A |
4847698 | Freeman | Jul 1989 | A |
4857999 | Welsh | Aug 1989 | A |
4908707 | Kinghorn | Mar 1990 | A |
4930158 | Vogel | May 1990 | A |
4959720 | Duffield et al. | Sep 1990 | A |
4977455 | Young | Dec 1990 | A |
5047867 | Strubbe et al. | Sep 1991 | A |
5109279 | Ando | Apr 1992 | A |
5134719 | Mankovitz | Jul 1992 | A |
5151789 | Young | Sep 1992 | A |
5172413 | Bradley et al. | Dec 1992 | A |
5200822 | Bronfin et al. | Apr 1993 | A |
5223924 | Strubbe | Jun 1993 | A |
5253066 | Vogel | Oct 1993 | A |
5335277 | Harvey et al. | Aug 1994 | A |
5353121 | Young et al. | Oct 1994 | A |
5412720 | Hoarty | May 1995 | A |
5442389 | Blahut et al. | Aug 1995 | A |
5461415 | Wolf et al. | Oct 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 |
5488409 | Yuen et al. | Jan 1996 | A |
5517257 | Dunn et al. | May 1996 | A |
5523794 | Mankovitz et al. | Jun 1996 | A |
5523796 | Marshall et al. | Jun 1996 | A |
5524195 | Clanton, III et al. | Jun 1996 | A |
5532754 | Young et al. | Jul 1996 | A |
5534911 | Levitan | Jul 1996 | A |
5537141 | Harper et al. | Jul 1996 | A |
5539449 | Blahut et al. | Jul 1996 | A |
5541738 | Mankovitz | Jul 1996 | A |
5543852 | Yuen et al. | Aug 1996 | A |
5550576 | Klosterman | Aug 1996 | A |
5581614 | Ng et al. | Dec 1996 | A |
5583561 | Baker et al. | Dec 1996 | A |
5583563 | Wanderscheid et al. | Dec 1996 | A |
5585838 | Lawler et al. | Dec 1996 | A |
5585858 | Harper et al. | Dec 1996 | A |
5585866 | Miller et al. | Dec 1996 | A |
5589892 | Knee et al. | Dec 1996 | A |
5592551 | Lett et al. | Jan 1997 | A |
5602582 | Wanderscheid et al. | Feb 1997 | A |
5619274 | Roop et al. | Apr 1997 | A |
5621579 | Yuen | Apr 1997 | A |
5630119 | Aristides et al. | May 1997 | A |
5632007 | Freeman | May 1997 | A |
5648824 | Dunn et al. | Jul 1997 | A |
5652613 | Lazarus et al. | Jul 1997 | A |
5654748 | Matthews, III | Aug 1997 | A |
5654886 | Zereski, Jr. et al. | Aug 1997 | A |
5657072 | Aristides et al. | Aug 1997 | A |
5659367 | Yuen | Aug 1997 | A |
5666645 | Thomas et al. | Sep 1997 | A |
5684525 | Klosterman | Nov 1997 | A |
5694163 | Harrison | Dec 1997 | A |
5701383 | Russo et al. | Dec 1997 | A |
5717452 | Janin et al. | Feb 1998 | A |
5724203 | Kwoh et al. | Mar 1998 | A |
5727060 | Young | Mar 1998 | A |
5745710 | Clanton, III et al. | Apr 1998 | A |
5751282 | Girard et al. | May 1998 | A |
5752159 | Faust et al. | May 1998 | A |
5754771 | Epperson et al. | May 1998 | A |
5758257 | Herz et al. | May 1998 | A |
5760821 | Ellis et al. | Jun 1998 | A |
5761607 | Gudesen | Jun 1998 | A |
5768528 | Stumm | Jun 1998 | A |
5778181 | Hidary et al. | Jul 1998 | A |
5778182 | Cathey et al. | Jul 1998 | A |
5781226 | Sheehan | Jul 1998 | A |
5781228 | Sposato | Jul 1998 | A |
5790198 | Roop et al. | Aug 1998 | A |
5796952 | Davis et al. | Aug 1998 | A |
5801787 | Schein et al. | Sep 1998 | A |
5802284 | Karlton et al. | Sep 1998 | A |
5805763 | Lawler et al. | Sep 1998 | A |
5805804 | Laursen 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 |
5818438 | Howe et al. | Oct 1998 | A |
5819019 | Nelson | Oct 1998 | A |
5828945 | Klosterman | Oct 1998 | A |
5850218 | LaJoie et al. | Dec 1998 | A |
5909212 | Nishina et al. | Jun 1999 | A |
5949954 | Young et al. | Sep 1999 | A |
5999688 | Iggulden et al. | Dec 1999 | A |
6052145 | Macrae et al. | Apr 2000 | A |
6058238 | Ng | May 2000 | A |
6091883 | Artigalas et al. | Jul 2000 | A |
6091884 | Yuen et al. | Jul 2000 | A |
6115057 | Kwoh et al. | Sep 2000 | A |
6122011 | Dias et al. | Sep 2000 | A |
6125231 | Yuen et al. | Sep 2000 | A |
6147715 | Yuen et al. | Nov 2000 | A |
6167188 | Young et al. | Dec 2000 | A |
6177931 | Alexander et al. | Jan 2001 | B1 |
6208335 | Gordon et al. | Mar 2001 | B1 |
6233389 | Barton et al. | May 2001 | B1 |
6240241 | Yuen | May 2001 | B1 |
6324338 | Wood et al. | Nov 2001 | B1 |
6441832 | Tao et al. | Aug 2002 | B1 |
6473559 | Knudson et al. | Oct 2002 | B1 |
6498895 | Young et al. | Dec 2002 | B2 |
6820278 | Ellis | Nov 2004 | B1 |
6850693 | Young et al. | Feb 2005 | B2 |
7298960 | Taylor et al. | Nov 2007 | B1 |
20020059621 | Thomas et al. | May 2002 | A1 |
20020141730 | Haken | Oct 2002 | A1 |
20030140148 | Kondo et al. | Jul 2003 | A1 |
20030149980 | Hassell et al. | Aug 2003 | A1 |
20030149988 | Ellis et al. | Aug 2003 | A1 |
20040008971 | Young et al. | Jan 2004 | A1 |
20040128686 | Boyer et al. | Jul 2004 | A1 |
20040181814 | Ellis et al. | Sep 2004 | A1 |
20050050578 | Ryal | Mar 2005 | A1 |
20050152669 | Kim et al. | Jul 2005 | A1 |
20100074600 | Putterman et al. | Mar 2010 | A1 |
Number | Date | Country |
---|---|---|
0424469 | May 1991 | EP |
0753964 | Jan 1997 | EP |
0762756 | Mar 1997 | EP |
0763938 | Mar 1997 | EP |
0843468 | May 1998 | EP |
0874524 | Oct 1998 | EP |
0940985 | Sep 1999 | EP |
10-042242 | Feb 1998 | JP |
10-112087 | Apr 1998 | JP |
10-164487 | Jun 1998 | JP |
WO 8804507 | Jun 1988 | WO |
WO 9000847 | Jan 1990 | WO |
WO 9100670 | Jan 1991 | WO |
WO 9107050 | May 1991 | WO |
WO 9204801 | Mar 1992 | WO |
WO 9222983 | Dec 1992 | WO |
WO 9304473 | Mar 1993 | WO |
WO 9308542 | Apr 1993 | WO |
WO 9501058 | Jan 1995 | WO |
WO 9504431 | Feb 1995 | WO |
WO 9511567 | Apr 1995 | WO |
WO 9518449 | Jul 1995 | WO |
WO 9531069 | Nov 1995 | WO |
WO 9532584 | Nov 1995 | WO |
WO 9532585 | Nov 1995 | WO |
WO 9532587 | Nov 1995 | WO |
WO 9609721 | Mar 1996 | WO |
WO 9613932 | May 1996 | WO |
WO 9625821 | Aug 1996 | WO |
WO 9627982 | Sep 1996 | WO |
WO 9633572 | Oct 1996 | WO |
WO 9634491 | Oct 1996 | WO |
WO 9636172 | Nov 1996 | WO |
WO 9641472 | Dec 1996 | WO |
WO 9641478 | Dec 1996 | WO |
WO 9713368 | Apr 1997 | WO |
WO 9731479 | Aug 1997 | WO |
WO 9732434 | Sep 1997 | WO |
WO 9734413 | Sep 1997 | WO |
WO 9734414 | Sep 1997 | WO |
WO 9740623 | Oct 1997 | WO |
WO 9742763 | Nov 1997 | WO |
WO 9746016 | Dec 1997 | WO |
WO 9746943 | Dec 1997 | WO |
WO 9747124 | Dec 1997 | WO |
WO 9748228 | Dec 1997 | WO |
WO 9748230 | Dec 1997 | WO |
WO 9749237 | Dec 1997 | WO |
WO 9749242 | Dec 1997 | WO |
WO 9801995 | Jan 1998 | WO |
WO 9806219 | Feb 1998 | WO |
WO 9807277 | Feb 1998 | WO |
WO 9810589 | Mar 1998 | WO |
WO 9812872 | Mar 1998 | WO |
WO 9816056 | Apr 1998 | WO |
WO 9817064 | Apr 1998 | WO |
WO 9826594 | Jun 1998 | WO |
WO 9826596 | Jun 1998 | WO |
WO 9838831 | Sep 1998 | WO |
WO 9839893 | Sep 1998 | WO |
WO 9847279 | Oct 1998 | WO |
WO 9847283 | Oct 1998 | WO |
WO 9847287 | Oct 1998 | WO |
WO 9847289 | Oct 1998 | WO |
WO 9903267 | Jan 1999 | WO |
WO 9960790 | Nov 1999 | WO |
WO 0016548 | Mar 2000 | WO |
Entry |
---|
U.S. Appl. No. 09/974,471, filed Oct. 9, 2001, Thomas et al. |
U.S. Appl. No. 11/267,200, filed Nov. 4, 2005, Craner. |
The New York Times, “2 Makers Plan Introductions of Digital VCR” by John Markoff, Mar. 29, 1999. |
Hofmann, Neumann, Oberlies, and Schadwinkel, “Videotext Programmiert Videorecorder,” Rundfunktechnische Mitteilungen, Nov.-Dec. 1982, pp. 254-257 (translation attached). |
“Electronic Programme Guide (EPG); Protocol for a TV Guide using electronic data Transmission” by European Telecommunication Standards Institute, May 1997, Valbonne, France, publication No. ETS 300 707. |
“Windows 98 Feature Combines TV, Terminal and the Internet,” New York Times, Aug. 18, 1998. |
“Digital Video Broadcasting (DVB); DVB specification for data broadcasting”, European Telecommunications Standards Institute, Draft EN 301 192 V1.2.1 (Jan. 1999). |
Rewind, replay and unwind with new high-tech TV devices, by Lawrence J. Magid, LA Times. This document was printed from the Internet on Jun. 6, 1999 and bears a date of May 19, 1999. |
Inside I-Guide User's Manual (Aug. 24, 2004). |
http://www.iapplianceweb.com/story/OEG20040510N0003BC.htm (May 11, 2004). |
TivoToGo (printed Mar. 8, 2006). |