Digital video recorders (DVRs) allow users to record television programs for later viewing. Typically, users set recording timers to record particular television programs at specified times. Recording conflicts occur if two or more recording timers occur at the same time or otherwise overlap. Recording conflict information is typically provided to the user in a list format, and the user is provided with options for resolving the time conflict. However, the list format is difficult for some users to review and determine the best option for resolving the recording conflict. The problem is further exacerbated by the availability of multiple tuner DVRs that allow recording timers to be assigned to multiple television tuners of the DVR
The same number represents the same element or same type of element in all drawings.
The various embodiments described herein generally provide apparatus, systems and methods which facilitate the display of television recording information to users. More particularly, television recording information is presented visually to a user in a visual recording information menu. The visual recording information menu includes a time axis, and recording timers associated with particular television programs are presented visually along the time axis. A user may scroll along the time axis to view the recording timers for the DVR. In short, the various embodiments described herein generally provide apparatus, systems and methods for visually displaying recording timer information.
In at least one embodiment, a DVR identifies a recording conflict between two or more television programs and visually displays the recording conflict in the recording information menu. For example, a portion of a visual representation of a first recording timer corresponding with a time period of the recording conflict may be overlaid on a portion of a visual representation of the second recording timer to indicate the existence of the recording conflict. A user may then provide input to resolve the recording conflict.
In some embodiments, the recording information menu presents recording information regarding multiple television tuners utilized to record television programs. For example, an interface menu may include both a time axis and a resource axis, with the resource axis separately presenting visual representations of recording timers associated with each television tuner of the DVR. In one embodiment, the recording information is presented in a grid, with rows of the grid corresponding with particular television tuners, and columns of the grid corresponding with recording time slots. A user may then view recording timers, identify recording conflicts and provide input to resolve the conflicts, such as switching a recording timer to a different television tuner.
The DVR 102 is operable to receive content from one or more content sources (not shown in
Responsive to particular recording timers, the DVR 102 coordinates the reception of video signals associated with a television program through a television receiving resource (e.g., a television tuner) and storage of the video signal onto a storage medium (e.g., a hard drive). The DVR 102 may include any number of television receiving resources utilized for receiving television programs. A DVR 102 minimally includes at least one television receiving resource to receive and record video signals associated with a television program. The DVR 102 may include multiple television receiving resources to record multiple television programs simultaneously. In at least one embodiment, the DVR 102 may include multiple types of television receiving resources, such as an over-the-air (ATA) tuner and a satellite and/or cable television tuner. In some embodiments, the DVR 102 may be operable to assign a recording timer associated with a particular program to a specified television receiving resource. For example, a first television program, broadcast between 7:00 P.M. and 8:00 P.M., may be assigned to a first satellite television tuner of the DVR 102, and a second television program, broadcast between 7:00 P.M. and 9:00 P.M., may be assigned to a second satellite television tuner of the DVR 102.
Priorities may also be assigned to particular recording timers to provide the DVR 102 with information for resolving recording conflicts. Thus, if a recording conflict occurs between two or more recording timers, then the DVR 102 may apply rules to the priority information to determine which program to record absent input by the user 108 resolving the conflict. For example, the earliest set recording timer may have the highest priority for recording. Similarly, a more recently set recording timer may have the highest priority for recording. In some embodiments, a user 108 may provide a recording priority for a particular timer when selecting the timer for recording. Thus, the particular rules applied by the DVR 102 for resolving recording conflicts may be determined based on desired design criteria.
The display device 104 may comprise any type of device capable of receiving and outputting a video signal in any format. Exemplary embodiments of the display device 104 include a television, a computer monitor, a liquid crystal display (LCD) screen, a touch screen and a projector. The display device 104 and the DVR 102 may be communicatively coupled through any type of wired or wireless interface. For example, the display device 104 may be communicatively coupled to the DVR 102 through a coaxial cable, component or composite video cables, an HDMI cable, a VGA or SVGA cable, a Bluetooth or WiFi wireless connection or the like. In at least one embodiment, the DVR 102 and the display device 104 may be integrated as a device combining the functionality of a display device and a DVR/television receiver.
The remote control 106 may comprise any system or apparatus configured to remotely control the output of content by the DVR 102. The remote control 106 may minimally include a transmitter, an input device (e.g., a keypad) and a processor for controlling the operation of the remote control 106. The remote control 106 may communicate commands to the DVR 102 requesting to playback content, temporally move through content (e.g., fast-forward or reverse), adjust the volume, access electronic programming guides, set or edit recording timers and the like. In some embodiments, the remote control 106 may additionally be configured to remotely control the display device 104. The remote control 106 may communicate with the DVR 102 and/or the display device 104 through any type of wireless communication medium, such as infrared (IR) signals or radio-frequency (RF) signals.
The remote control 106 may include any type of man-machine interface for receiving input from the user 108. For example, the remote control 106 may include buttons for receiving input from the user 108. In at least one embodiment, the remote control 106 includes a touch pad for receiving input from the user 108. The remote control 106 may further include a trigger, utilized in association with the touch pad, for allowing the user to input information associated with the menus displayed on-screen.
During a viewing session, the user 108 requests to record one or more television programs receivable by the DVR 102. For example, a user 108 may access an electronic programming guide through the DVR 102 to view upcoming television programs and select one or more of the television programs for recording.
Occasionally, recording conflicts occur on a DVR 102 if two or more programs are to be recorded at the same time or during overlapping time periods. For example, a first program may be set for recording between 7:30 P.M. and 8:00 P.M., and a second program may be set for recording between 7:00 P.M. and 8:00 P.M. Thus, if the DVR 102 has only a single television receiving resource, then one of the television shows may not be recorded.
Another common problem occurs if a recording timer includes a buffer period at the beginning and/or ending of the time period to account for programs that start early and/or run past the allotted time. For example, a recording timer for a program that runs from 7:00 P.M. to 8:00 P.M. may be set for 6:57 P.M. to 8:03 P.M. If another program is set for recording from 8:00 P.M. to 9:00 P.M., then the buffer period for the first program may prevent recording of the entire second program depending on the priority rules applied by the DVR 102.
Thus, in accordance with at least one embodiment, the DVR 102 is operable to output a recording timer user interface for displaying recording timer information visually to the user 108.
As illustrated in
When generating the user interface menu 300, the DVR 102 identifies recording conflicts between multiple timers corresponding with multiple television programs. More particularly, a recording conflict occurs during a conflict time period if the recording timers for each television program overlap. In the illustrated example of
To assist the user 108 in identifying the recording conflict, the DVR 102 presents the visual representation 304A and the visual representation 304B simultaneously along the time axis 302. The DVR 102 further overlays a portion of the visual representation 304A over a portion of the visual representation 304B corresponding with the conflict time period. In other words, the visual representation 304A is overlaid over the visual representation 304B along the 1:27 P.M. to 2:03 P.M. portion of the time axis 302.
To further accentuate the recording conflict, the DVR 102 offsets the visual representation 304A along the vertical axis of the user interface menu 300, which is disparate from the time axis 302. Thus, because the visual representation 304B is offset from the other visual representations 304A, 304C and 304D, the user 108 may recognize right away that the Superhero television program will not be recorded by the DVR 102 because of the time conflict. The DVR 102 may optionally display a visual indicator on the visual representation 304B that indicates the Superhero television program will not be recorded. As illustrated in
To resolve the recording conflict, the user 108 may provide additional user input to change parameters of the recording timers associated with the recording conflict. The DVR 102 updates the particular recording timers responsive to the user input. For example, the user 108 may decide that they would rather record the Superhero television program. Thus, they may change the priority of the conflicted recording timers. In at least one embodiment, the user 108 utilizes the remote control 106 to swap the positions of the visual representations 304A and 304B, changing the recording priorities of the associated recording timers.
In at least one embodiment, the DVR 102 may include multiple television receiving resources, such as multiple satellite or cable television tuners, that allow the DVR 102 to record multiple television programs simultaneously. Each television program may be selectively assigned for reception by one or more of the television receiving resources based on input by the user 108 and/or rules applied by the DVR 102.
Like the user interface menus 300 and 400, the recording timer user interface menu 500 includes a plurality of visual representations 506A-506C that are associated with recording timers for various television programs. More particularly, each recording timer is assigned to a particular television receiving resource. Thus, visual representations of recording timers associated with the first television receiving resource are presented along a first portion of the resource axis 504. Similarly, visual representations of recording timers associated with the second television receiving resource are presented along a second portion of the resource axis 504. The visual representations 506A-506C are also positioned along a portion of the time axis associated with a beginning time and an ending time of the associated recording timer.
In
Even though the DVR 102 includes multiple television receiving resources, recording conflicts may still occur for the same reasons as when the DVR 102 includes one television receiving resource. However, multiple television receiving resources give the user 108 more flexibility in resolving recording conflicts to achieve more optimal recording solutions, e.g., to record more television programs. The user interface menu 500 is advantageously useful to the user 108 for easily identifying recording conflicts to determine optimal solutions for recording the most number of television programs.
The multiple television receiving resource embodiment of the DVR 102 may operate similarly to the single television receiving resource embodiment of the DVR 102 described in regard to
As indicated in
However, the user 108 may decide that the buffer periods of each recording timer are not as important as recording the Iron Judge. Thus, the user 108 may provide input requesting to modify the time boundary of one or both recording timers to resolve the recording conflict such that each television program is recorded. For example, the user 108 may drag the edges of one or both of visual representations 606A and 606B to modify the time boundaries of the associated recording timer. The user 108 may also click on either visual representation 606A to 606B to modify the parameters of the associated recording timer. Thus, in at least one embodiment, the DVR 102 may present the user with a parameter editing menu, responsive to the user 108 clicking on a particular visual representation, that allows the user 108 to modify the parameters of the associated recording timer.
As further illustrated in
In at least one embodiment, the visual representations of recording timers may include pictures associated with a particular television program.
The tuner 1002 is operable to receive an audio/video input 1010 from a content source. More particularly, the tuner 1002 receives and tunes a television signal including television programming. The tuner 1002 may receive an over-the-air broadcast, a direct broadcast satellite signal, a cable television signal or an internet protocol television (IPTV) signal and tune the audio/video input 1010 to extract the selected television programming. In at least one embodiment, the DVR 102A may include multiple tuners 1002, utilized by the user 108, to view and/or record multiple television programs simultaneously.
The storage medium 1004 is operable to persistently store video signals recorded by the DVR 102A. The storage medium 1004 may comprise any type of non-volatile memory appropriate for storing video signals recorded by the DVR 102A. Exemplary storage mediums 1004 include hard drives (e.g., magnetic memory), flash memory and the like. In at least one embodiment, the storage medium 1004 may be internally located within the DVR 102A. In other embodiments, the storage medium 1004 may be located external with respect to the DVR 102A. The DVR 102A may also utilize a combination of internal and external storage mediums 1004 for storage of video signals.
The processor 1006 is operable to control the operation of the DVR 102A. The processor 1006 may be a single processing device or a plurality of processing devices that cooperatively operate to control the operation of the DVR 102A. The processor 1006 may include various components or modules for processing and outputting audio/video content. Exemplary components or modules for processing audio/video content include a demodulator, a decoder, a decompressor, a conditional access module and a transcoder module.
The processor 1006 coordinates storage of the audio/video input 1010 onto the storage medium 1004. The processor 1006 may also be operable to generate an audio/video output stream based on the audio/video input 1010, e.g. pass through the signal for display by an associated display device 104. The processor 1006 is also operable to retrieve stored video content to generate an audio/video output stream for display by the display device 104. An audio/video output stream is outputted to the display device 104 (see
To coordinate the storage of the audio/video input 1010, the processor 1006 is operable to receive user input requesting to record one or more television programs. Responsively, the processor 1006 sets recording timers associated with the television programs. The processor 1006 is further operable to output user interface menus, such as the user interface menus 200-900 illustrated in
The interface module 1008 is operable to wirelessly receive data from the remote control 106. The interface module 1008 may communicate with the remote control 106 utilizing any type of IR or RF communication link. In at least one embodiment, the interface module 1008 receives a key code from the remote control 106, and responsively provides the key code to the processor 1006. In some embodiments, the interface module 1008 may receive positional information from a scrolling device of the remote control 106, e.g., a touch pad, scroll wheel or the like. Some of the data received by the interface module 1008 may request to set and/or modify recording timers as described above. The processor 1006 processes the data received by the interface module 1008 to set and update recording timers in accordance with the embodiments described above.
Those of ordinary skill in the art will appreciate that the various functional elements 1002 through 1008 shown as operable within the DVR 102A may be combined into fewer discrete elements or may be broken up into a larger number of discrete functional elements as a matter of design choice. Thus, the particular functional decomposition suggested by
The process includes receiving first user input requesting to record a first television program (operation 1102). For example, a user may select a program for recording via an electronic programming guide menu. The process further includes receiving second user input requesting to record a second television program (operation 1104).
The process further includes identifying a recording conflict between a first television program and a second television program during a conflict time period (operation 1106). In at least one embodiment, identifying the recording conflict may be performed responsive to the second user input received in operation 1104. In other embodiments, identifying the recording conflict may be performed responsive to other events, such as modification of a recording timer or user input requesting to view a recording timer schedule.
In at least one embodiment, a DVR may initially apply priority rules to determine which television program to record given the recording conflict. For example, the higher priority television program may be set for recording. In some embodiments, the DVR prompts the user to resolve the conflict rather than automatically applying priority rules to determine which program should be recorded given the recording conflict.
The process further includes displaying a user interface menu including visual representations of the television programs and the associated recording timers (operation 1108). More particularly, the user interface menu includes a time axis, a first visual representation of the first television program and a second visual representation of the second television program. At least a portion of the first visual representation is overlaid on a portion of the second visual representation along the time axis corresponding to the conflict time period. In some embodiments, the second visual representation may be offset from the first visual representation along an axis of the user interface menu disparate from the time axis. Still further, the second visual representation may include a visual indicator that indicates the second television program will not be recorded. In some embodiments, the first and/or second visual representations may be displayed with pictures corresponding to the first and second television programs.
In at least one embodiment, the user interface menu may be displayed to the user responsive to identifying the recording conflict in operation 1108. In other words, a DVR identifies a recording conflict and displays the user interface menu as a prompt for the user to resolve the recording conflict. In other embodiments, the user interface menu may be displayed responsive to a request by a user to view a television recording timer schedule.
The process further includes receiving third user input requesting to resolve the recording conflict (operation 1110). In at least one embodiment, a user may request to modify a time boundary of a recording time associated with the first and/or second television program. For example, if the first recording timer for the first television program ends at 7:01 P.M. and the recording timer for the second television program starts at 7:00 P.M., then the user may modify the first recording timer to end at 7:00 P.M. such that no overlap between the recording timers occurs.
In some embodiments, the third user input may request to swap positions of the first and second visual representations. In other words, the user may request to change the relative priorities of the recording timers associated with the first and second television programs. Thus, the process may further include displaying a portion of the second visual representation overlaid over a portion of the first visual representation, indicating that the second television program has a higher recording priority than the first television program. In at least one embodiment, the user interface menu may include recording timer information associated with multiple television receiving resources, and the third user input may request to swap the television receiving resource associated with the first or second television program and a third television program associated with a disparate television receiving resource. Thus, for example, the first television program may be recorded using a second television receiving resource whereas the third television program may be recorded using the television receiving resource originally associated the first television receiving resource.
The process further includes updating at least one recording timer, associated with the recording conflict, based on the third user input (operation 1112). For example, if the user input requests modification of a time boundary of one of the recording timers, then the process may include updating a recording time of a recording timer associated with the television program based on the modified time boundary. In another embodiment, operation 1112 may include modifying a recording priority of the second recording timer based on the third user input.
The process includes receiving user input requesting to record a plurality of television programs (operation 1202). In at least one embodiment, user input may be provided separately to request recording of each separate television program. Further, in at least one embodiment, the user input indicates which television receiving resource to utilize for recording each distinct television program. The user input may also indicate a recording priority for each of the plurality of recording timers.
The process further includes setting a plurality of recording timers associated with the plurality of television programs (operation 1204). A first portion of the recording timers are associated with a first television receiving resource and a second portion of the recording timers are associated with a second television receiving resource.
The process further includes displaying a visual interface menu (operation 1206). The visual interface menu includes a time axis presenting various time slots along a first axis, e.g., a vertical axis. The visual interface menu also includes a resource axis that separately presents the recording timers associated with each of the first and second television receiving resources.
The process further includes displaying a plurality of visual representations of the recording timers (operation 1208). A first portion of the recording timers are presented along a first portion of the resource axis associated with the first television receiving resource. Similarly, a second portion of the recording timers are presented along a second portion of the resource axis associated with the second television receiving resource. Each of the visual representations is positioned along a portion of the time axis associated with a beginning time and an ending time of an associated recording timer.
In the case of recording conflicts, the process may optionally include displaying information indicating the recording conflict. For example, a recording conflict may be identified during a conflict time period between first and second recording timers associated with a first television receiving resource. A first visual representation of a first recording timer may be displayed overlaid on a portion of the second visual representation along the time axis corresponding to the conflict time period. A visual indicator may also be presented on the second visual representation indicating that the second television program will not be recorded. The process may then optionally include receiving user input for resolving recording conflicts in accordance with the embodiments described above.
Although specific embodiments were described herein, the scope of the invention is not limited to those specific embodiments. The scope of the invention is defined by the following claims and any equivalents therein.
Number | Name | Date | Kind |
---|---|---|---|
4450477 | Lovett | May 1984 | A |
4725888 | Hakamada | Feb 1988 | A |
4739510 | Jeffers et al. | Apr 1988 | A |
4799056 | Hattori et al. | Jan 1989 | A |
4852019 | Vinberg et al. | Jul 1989 | A |
4868785 | Jordan et al. | Sep 1989 | A |
5021974 | Pisculli et al. | Jun 1991 | A |
5187776 | Yanker | Feb 1993 | A |
5260778 | Kauffman et al. | Nov 1993 | A |
5428734 | Haynes et al. | Jun 1995 | A |
5438372 | Tsumori et al. | Aug 1995 | A |
5450536 | Rosenberg et al. | Sep 1995 | A |
5453796 | Duffield et al. | Sep 1995 | A |
5539478 | Bertram et al. | Jul 1996 | A |
5539479 | Bertram | Jul 1996 | A |
5545857 | Lee et al. | Aug 1996 | A |
5548340 | Bertram | Aug 1996 | A |
5559961 | Blonder | Sep 1996 | A |
5585866 | Miller et al. | Dec 1996 | A |
5589893 | Gaughan et al. | Dec 1996 | A |
5594469 | Freeman et al. | Jan 1997 | A |
5594509 | Florin et al. | Jan 1997 | A |
5602597 | Bertram | Feb 1997 | A |
5604544 | Bertram | Feb 1997 | A |
5606374 | Bertram | Feb 1997 | A |
5650827 | Tsumori et al. | Jul 1997 | A |
5652630 | Bertram et al. | Jul 1997 | A |
5659369 | Imaiida | Aug 1997 | A |
5677708 | Matthews, III et al. | Oct 1997 | A |
5682489 | Harrow et al. | Oct 1997 | A |
5721815 | Ottesen et al. | Feb 1998 | A |
5721878 | Ottesen et al. | Feb 1998 | A |
5742286 | Kung et al. | Apr 1998 | A |
5751883 | Ottesen et al. | May 1998 | A |
5754258 | Hanaya et al. | May 1998 | A |
5767840 | Selker | Jun 1998 | A |
5768158 | Adler et al. | Jun 1998 | A |
5774186 | Brodsky et al. | Jun 1998 | A |
5786805 | Barry | Jul 1998 | A |
5801747 | Bedard | Sep 1998 | A |
5805235 | Bedard | Sep 1998 | A |
5809265 | Blair et al. | Sep 1998 | A |
5815216 | Suh | Sep 1998 | A |
5825361 | Rubin et al. | Oct 1998 | A |
5831591 | Suh | Nov 1998 | A |
5831607 | Brooks | Nov 1998 | A |
5867162 | O'Leary et al. | Feb 1999 | A |
5874953 | Webster et al. | Feb 1999 | A |
5898431 | Webster et al. | Apr 1999 | A |
5905496 | Lau et al. | May 1999 | A |
5917489 | Thurlow et al. | Jun 1999 | A |
5978043 | Blonstein et al. | Nov 1999 | A |
5999228 | Matsuura et al. | Dec 1999 | A |
6005565 | Legall et al. | Dec 1999 | A |
6008735 | Chiloyan et al. | Dec 1999 | A |
6008860 | Patton et al. | Dec 1999 | A |
6020930 | Legrand | Feb 2000 | A |
6064376 | Berezowski et al. | May 2000 | A |
6118498 | Reitmeier | Sep 2000 | A |
6125374 | Terry et al. | Sep 2000 | A |
6141003 | Chor et al. | Oct 2000 | A |
6147714 | Terasawa et al. | Nov 2000 | A |
6173112 | Gruse et al. | Jan 2001 | B1 |
6191773 | Maruno et al. | Feb 2001 | B1 |
6208341 | van Ee et al. | Mar 2001 | B1 |
6208804 | Ottesen et al. | Mar 2001 | B1 |
6215417 | Krass et al. | Apr 2001 | B1 |
6233389 | Barton et al. | May 2001 | B1 |
6266098 | Cove et al. | Jul 2001 | B1 |
6281940 | Sciammarella | Aug 2001 | B1 |
6334217 | Kim | Dec 2001 | B1 |
6493036 | Fernandez | Dec 2002 | B1 |
6498628 | Iwamura | Dec 2002 | B2 |
6526577 | Knudson et al. | Feb 2003 | B1 |
6529685 | Ottesen et al. | Mar 2003 | B2 |
6556252 | Kim | Apr 2003 | B1 |
6650248 | O'Donnell et al. | Nov 2003 | B1 |
6678009 | Kahn | Jan 2004 | B2 |
6697123 | Janevski et al. | Feb 2004 | B2 |
6750803 | Yates et al. | Jun 2004 | B2 |
6750887 | Kellerman et al. | Jun 2004 | B1 |
6774914 | Benayoun | Aug 2004 | B1 |
6804824 | Potrebic et al. | Oct 2004 | B1 |
6816442 | Heiman et al. | Nov 2004 | B1 |
6822698 | Clapper | Nov 2004 | B2 |
6882712 | Iggulden et al. | Apr 2005 | B1 |
6934963 | Reynolds et al. | Aug 2005 | B1 |
6943845 | Mizutome et al. | Sep 2005 | B2 |
7046161 | Hayes | May 2006 | B2 |
7061544 | Nonomura et al. | Jun 2006 | B1 |
7148909 | Yui et al. | Dec 2006 | B2 |
7171622 | Bhogal | Jan 2007 | B2 |
7196733 | Aratani et al. | Mar 2007 | B2 |
7206029 | Cohen-Solal | Apr 2007 | B2 |
7225456 | Kitsukawa et al. | May 2007 | B2 |
7231603 | Matsumoto | Jun 2007 | B2 |
7268830 | Lee | Sep 2007 | B2 |
7370284 | Andrea et al. | May 2008 | B2 |
7420620 | Habas et al. | Sep 2008 | B2 |
7434246 | Florence | Oct 2008 | B2 |
7440036 | Onomatsu et al. | Oct 2008 | B2 |
7584492 | Terakado et al. | Sep 2009 | B2 |
7600201 | Endler et al. | Oct 2009 | B2 |
7620966 | Kitamori | Nov 2009 | B2 |
7636131 | Hsieh et al. | Dec 2009 | B2 |
7707599 | Groff et al. | Apr 2010 | B1 |
7743398 | DeYonker et al. | Jun 2010 | B2 |
7746332 | Le Leannec et al. | Jun 2010 | B2 |
7876382 | Imaizumi | Jan 2011 | B2 |
7880813 | Nakamura et al. | Feb 2011 | B2 |
8001566 | Jang | Aug 2011 | B2 |
8005826 | Sahami et al. | Aug 2011 | B1 |
8239784 | Hotelling et al. | Aug 2012 | B2 |
20010011953 | Shintani et al. | Aug 2001 | A1 |
20010017672 | Verhaeghe | Aug 2001 | A1 |
20020054062 | Gerba et al. | May 2002 | A1 |
20020057382 | Yui | May 2002 | A1 |
20020059599 | Schein et al. | May 2002 | A1 |
20020060754 | Takeuchi | May 2002 | A1 |
20020070957 | Trajkovic et al. | Jun 2002 | A1 |
20020075333 | Dutta et al. | Jun 2002 | A1 |
20020075407 | Cohen-Solal | Jun 2002 | A1 |
20020097229 | Rose et al. | Jul 2002 | A1 |
20020122027 | Kim | Sep 2002 | A1 |
20020122079 | Kamen et al. | Sep 2002 | A1 |
20020129366 | Schein et al. | Sep 2002 | A1 |
20020174430 | Ellis et al. | Nov 2002 | A1 |
20020178446 | Sie et al. | Nov 2002 | A1 |
20020191954 | Beach et al. | Dec 2002 | A1 |
20030001908 | Cohen-solal | Jan 2003 | A1 |
20030005443 | Axelsson et al. | Jan 2003 | A1 |
20030005445 | Schein et al. | Jan 2003 | A1 |
20030018973 | Thompson | Jan 2003 | A1 |
20030025716 | Colavin | Feb 2003 | A1 |
20030066079 | Suga | Apr 2003 | A1 |
20030086694 | Davidsson | May 2003 | A1 |
20030115589 | D'Souza et al. | Jun 2003 | A1 |
20030126607 | Phillips et al. | Jul 2003 | A1 |
20030131356 | Proehl et al. | Jul 2003 | A1 |
20030191947 | Stubblefield et al. | Oct 2003 | A1 |
20030193426 | Vidal | Oct 2003 | A1 |
20030208751 | Kim et al. | Nov 2003 | A1 |
20040041723 | Shibamiya et al. | Mar 2004 | A1 |
20040070593 | Neely et al. | Apr 2004 | A1 |
20040107439 | Hassell et al. | Jun 2004 | A1 |
20040111744 | Bae et al. | Jun 2004 | A1 |
20040168191 | Jerding et al. | Aug 2004 | A1 |
20040172651 | Wasilewski et al. | Sep 2004 | A1 |
20040201780 | Kim | Oct 2004 | A1 |
20040218905 | Green et al. | Nov 2004 | A1 |
20040230843 | Jansen | Nov 2004 | A1 |
20040250280 | Allport | Dec 2004 | A1 |
20040255336 | Logan et al. | Dec 2004 | A1 |
20050002649 | Boyle et al. | Jan 2005 | A1 |
20050010949 | Ward et al. | Jan 2005 | A1 |
20050015803 | Macrae et al. | Jan 2005 | A1 |
20050076361 | Choi et al. | Apr 2005 | A1 |
20050084233 | Fujii et al. | Apr 2005 | A1 |
20050128366 | Cha | Jun 2005 | A1 |
20050188402 | de Andrade et al. | Aug 2005 | A1 |
20050190280 | Haas et al. | Sep 2005 | A1 |
20050251826 | Orr | Nov 2005 | A1 |
20050268100 | Gasparini et al. | Dec 2005 | A1 |
20060037047 | DeYonker et al. | Feb 2006 | A1 |
20060051058 | Rudolph et al. | Mar 2006 | A1 |
20060061668 | Ise | Mar 2006 | A1 |
20060061688 | Choi | Mar 2006 | A1 |
20060064700 | Ludvig et al. | Mar 2006 | A1 |
20060084409 | Ghadiali | Apr 2006 | A1 |
20060095401 | Krikorian et al. | May 2006 | A1 |
20060236342 | Kunkel et al. | Oct 2006 | A1 |
20070019111 | Won | Jan 2007 | A1 |
20070039019 | Collier | Feb 2007 | A1 |
20070039020 | Cansler, Jr. et al. | Feb 2007 | A1 |
20070039021 | Lee | Feb 2007 | A1 |
20070061724 | Slothouber et al. | Mar 2007 | A1 |
20070074254 | Sloo | Mar 2007 | A1 |
20070079334 | Silver | Apr 2007 | A1 |
20070115391 | Anderson | May 2007 | A1 |
20070130607 | Thissen et al. | Jun 2007 | A1 |
20070186231 | Haeuser et al. | Aug 2007 | A1 |
20070192791 | Sullivan et al. | Aug 2007 | A1 |
20070195197 | Seong et al. | Aug 2007 | A1 |
20070199022 | Moshiri et al. | Aug 2007 | A1 |
20070266397 | Lin | Nov 2007 | A1 |
20070277198 | Yasukawa et al. | Nov 2007 | A1 |
20070277224 | Osborn et al. | Nov 2007 | A1 |
20080010518 | Jiang et al. | Jan 2008 | A1 |
20080024682 | Chen | Jan 2008 | A1 |
20080034314 | Louch et al. | Feb 2008 | A1 |
20080052245 | Love | Feb 2008 | A1 |
20080066102 | Abraham et al. | Mar 2008 | A1 |
20080074550 | Park | Mar 2008 | A1 |
20080088495 | Kawakita | Apr 2008 | A1 |
20080129886 | Ishihara | Jun 2008 | A1 |
20080147803 | Krzyzanowski et al. | Jun 2008 | A1 |
20080184324 | Yun et al. | Jul 2008 | A1 |
20080205847 | Yanagita et al. | Aug 2008 | A1 |
20080222523 | Fox et al. | Sep 2008 | A1 |
20080229254 | Warner | Sep 2008 | A1 |
20080231762 | Hardacker et al. | Sep 2008 | A1 |
20080235735 | Wroblewski | Sep 2008 | A1 |
20080263595 | Sumiyoshi et al. | Oct 2008 | A1 |
20090007209 | Kawai | Jan 2009 | A1 |
20090031335 | Hendricks et al. | Jan 2009 | A1 |
20090031343 | Sharkey | Jan 2009 | A1 |
20090070815 | Barrett et al. | Mar 2009 | A1 |
20090141024 | Lee et al. | Jun 2009 | A1 |
20090241145 | Sharma | Sep 2009 | A1 |
20100037180 | Elias et al. | Feb 2010 | A1 |
20100050199 | Kennedy | Feb 2010 | A1 |
20100071004 | Wightman | Mar 2010 | A1 |
20100077432 | VanDuyn et al. | Mar 2010 | A1 |
20100079671 | VanDuyn et al. | Apr 2010 | A1 |
20100079681 | Coburn et al. | Apr 2010 | A1 |
20100083309 | White et al. | Apr 2010 | A1 |
20100083310 | VanDuyn et al. | Apr 2010 | A1 |
20100083312 | White et al. | Apr 2010 | A1 |
20100083313 | White et al. | Apr 2010 | A1 |
20100083315 | White et al. | Apr 2010 | A1 |
20100083319 | Martch et al. | Apr 2010 | A1 |
20100100909 | Arsenault et al. | Apr 2010 | A1 |
20100115550 | Minnick et al. | May 2010 | A1 |
20100118211 | Carlsgaard et al. | May 2010 | A1 |
20100169958 | Werner et al. | Jul 2010 | A1 |
20100231525 | Chen | Sep 2010 | A1 |
20110018817 | Kryze et al. | Jan 2011 | A1 |
Number | Date | Country |
---|---|---|
1063797 | Dec 2000 | EP |
1158793 | Nov 2001 | EP |
200729167 | Jan 2007 | TW |
0001142 | Jan 2000 | WO |
0145395 | Jun 2001 | WO |
0178054 | Oct 2001 | WO |
0178383 | Oct 2001 | WO |
02087243 | Oct 2002 | WO |
03043320 | May 2003 | WO |
2006119269 | Nov 2006 | WO |
20060127211 | Nov 2006 | WO |
2007015047 | Feb 2007 | WO |
2008013350 | Jan 2008 | WO |
Entry |
---|
USPTO “Non-Final Office Action” mailed Dec. 21, 2010; U.S. Appl. No. 12/235,476, filed Sep. 22, 2008. |
USPTO “Non-Final Office Action” mailed Mar. 31, 2011; U.S. Appl. No. 12/241,556, filed Sep. 30, 2008. |
USPTO “Non-Final Office Action” mailed Jul. 6, 2011; U.S. Appl. No. 12/241,571, filed Sep. 30, 2008. |
USPTO “Non-Final Office Action” mailed Jul. 12, 2011; U.S. Appl. No. 12/241,604, filed Sep. 30, 2008. |
USPTO “Final Office Action” mailed Jun. 23, 2011; U.S. Appl. No. 12/241,580, filed Sep. 30, 2008. |
USPTO “Final Office Action” mailed May 13, 2011; U.S. Appl. No. 12/235,476, filed Sep. 22, 2008. |
USPTO “Non-Final Office Action” mailed Nov. 24, 2010; U.S. Appl. No. 12/242,587, filed Sep. 30, 2008. |
USPTO “Non-Final Office Action” mailed Jan. 12, 2011; U.S. Appl. No. 12/241,580, filed Sep. 30, 2008. |
USPTO “Non-Final Office Action” mailed Jan. 28, 2011; U.S. Appl. No. 12/236,430, filed Sep. 23, 2008. |
USPTO “Non-Final office Action” mailed Feb. 4, 2011; U.S. Appl. No. 12/241,599, filed Sep. 30, 2008. |
USPTO “Non-Final Office Action” mailed Feb. 9, 2011; U.S. Appl. No. 12/241,608, filed Sep. 30, 2008. |
The International Bureau of WIPO “International Preliminary Report on Patentability” mailed Apr. 14, 2011; International Appln. No. PCT/US2009/058236, filed Sep. 24, 2009. |
USPTO “Final Office Action” mailed May 13, 2011; U.S. Appl. No. 12/242,587, filed Sep. 30, 2008. |
European Patent Office, International Searching Authority, “International Search Report” mailed Nov. 10, 2009; International Appln. No. PCT/EP2009/061499. |
USPTO “Non-Final Office Action” mailed Jan. 31, 2011; U.S. Appl. No. 12/233,274, filed Sep. 18, 2008. |
USPTO “Non-Final Office Action” mailed Dec. 6, 2011; U.S. Appl. No. 12/241,580, filed Sep. 30, 2008. |
USPTO “Final Office Action” mailed Dec. 7, 2011; U.S. Appl. No. 12/241,599, filed Sep. 30, 2008. |
USPTO “Final Office Action” mailed Oct. 21, 2011; U.S. Appl. No. 12/241,571, filed Sep. 30, 2008. |
USPTO “Final Office Action” mailed Oct. 5, 2011; U.S. Appl. No. 12/241,556, filed Sep. 30, 2008. |
USPTO “Non-Final Office Action” mailed Nov. 23, 2011; U.S. Appl. No. 12/242,614, filed Sep. 30, 2008. |
USPTO “Final Office Action” mailed Jul. 28, 2011; U.S. Appl. No. 12/241,608, filed Sep. 30, 2008. |
USPTO “Final Office Action” mailed Aug. 18, 2011; U.S. Appl. No. 12/233,274, filed Sep. 18, 2008. |
International Searching Authority, European Patent Office, “International Search Report,” mailed Feb. 4, 2010; International Application No. PCT/US2009/058937, filed Sep. 30, 2009. |
International Searching Authority, Euopean Patent Office, “International Search Report,” mailed Feb. 16, 2010; International Application No. PCT/US2009/057582, filed Sep. 18, 2009. |
Wightman, Robert Edward “Methods and Apparatus for Providing Multiple Channel Recall on a Television Receiver,” U.S. Appl. No. 12/233,274, filed Sep. 18, 2008. |
USPTO “Final Office Action” mailed Jan. 20, 2012; U.S. Appl. No. 12/241,604, filed Sep. 30, 2008. |
United States Patent and Trademark Office, Final Office Action for U.S. Appl. No. 12/241,599, dated Aug. 26, 2011. |
International Searching Authority, European Patent Office, “International Search Report,” mailed Dec. 7, 2009; International Application No. PCT/US2009/058457, filed Sep. 25, 2009. |
International Searching Authority, European Patent Office, “International Search Report and Written Opinion,” mailed Dec. 18, 2009; International Application No. PCT/US2009/058456, filed Sep. 25, 2009. |
International Searching Authority, European Patent Office, “International Search Report and Written Opinion,” mailed Dec. 21, 2009; International Application No. PCT/US2009/058454 filed Sep. 25, 2009. |
Anonymous “ZigBee,” Wikipedia, the Free Encyclopedia [online], Sep. 26, 2008, XP002558439; retrieved from the Internet: <URL:http://en.wikipedia.org/w/index.php?title=ZigBee&oldid=241085798> [retrieved on Dec. 2, 2009]. |
Nintendo, “Wii Operations Manual System Setup,” 2007. |
Wikipedia, the free encyclopedia, “Dashboard (Software,” Retrieved from the Internet on Oct. 6, 2008, http://en.wikipedia.org/w/index.php?title=Dashboard—(software)&printable=yes. |
International Searching Authority, European Patent Office, “International Search Report,” mailed Jan. 20, 2010; International Application No. PCT/US2009/057825 filed Sep. 22, 2009. |
Minnick, Danny Jean et al., “Graphical Interface Navigation Based on Image Element Proximity,” U.S. Appl. No. 12/609,860, filed Oct. 30, 2009. |
White, James Matthew et al. “Systems and Methods for Configuration of a Remote Control Device,” U.S. Appl. No. 12/241,550, filed Sep. 30, 2008. |
White, James Matthew et al. “Systems and Methods for Graphical control of User Interface Features Provided by a Television Receiver,” U.S. Appl. No. 12/241,556, filed Sep. 30, 2008. |
VanDuyn, Luke et al. “Systems and Methods for Graphical Control of Picture-In-Picture Windows,” U.S. Appl. No. 12/241,571, filed Sep. 30, 2008. |
White, James Matthew et al. “Systems and Methods for Providing Customer Service Features Via a Graphical User Interface in a Television Receiver,” U.S. Appl. No. 12/241,580, filed Sep. 30, 2008. |
Martch, Henry Gregg “Systems and Methods for Automatic Configuration of a Remote Control Device,” U.S. Appl. No. 12/242,089, filed Sep. 30, 2008. |
White, James Matthew et al. “Systems and Methods for Graphical Control of User Interface Features in a Television Receiver,” U.S. Appl. No. 12/241,599, filed Sep. 30, 2008. |
Coburn, Matthew et al. “Systems and Methods for Graphical Control of Symbol-Based Features in a Television Receiver,” U.S. Appl. No. 12/241,604, filed Sep. 30, 2008. |
White, James Matthew et al. “Systems and Methods for Graphical Adjustment of an Electronic Program Guide,” U.S. Appl. No. 12/241,608, filed Sep. 30, 2008. |
VanDuyn, Luke et al. “Methods and Apparatus for Presenting Supplemental Information in an Electronic Programming Guide,” U.S. Appl. No. 12/235,476, filed Sep. 22, 2008. |
VanDuyn, Luke et al. “Methods and Apparatus for Providing Multiple Channel Recall on a Television Receiver,” U.S. Appl. No. 12/242,587, filed Sep. 30, 2008. |
Martch, Henry Gregg et al. “Methods and Apparatus for Locating Content in an Electronic Programming Guide,” U.S. Appl. No. 12/242,614, filed Oct. 17, 2008. |
Taxier, Karen Michelle et al. “Apparatus and Methods for Dynamic Pictorial Image Authentication,” U.S. Appl. No. 12/236,430, filed Sep. 23, 2008. |
USPTO Non-Final Office Action mailed Apr. 17, 2012; U.S. Appl. No. 12/241,608, filed Sep. 30, 2008. |
USPTO Non-Final Office Action mailed Mar. 22, 2012; U.S. Appl. No. 12/241,556, filed Sep. 30, 2008. |
USPTO Final Office Action mailed Apr. 25, 2012; U.S. Appl. No. 12/242,614, filed Sep. 30, 2008. |
USPTO Non-Final Office Action mailed Apr. 24, 2012; U.S. Appl. No. 12/235,476, filed Sep. 22, 2008. |
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 12/242,587, dated Jun. 5, 2012. |
USPTO Final Office Action mailed Aug. 8, 2012 for U.S. Appl. No. 12/241,556, filed Sep. 30, 2008. |
USPTO Non-Final Office Action mailed Jun. 28, 2012 for U.S. Appl. No. 12/241,571, filed Sep. 30, 2008. |
USPTO Non-Final Office Action mailed Jul. 26, 2012 for U.S. Appl. No. 12/609,860, filed Oct. 30, 2008. |
USPTO Final Office Action mailed Aug. 2, 2012 for U.S. Appl. No. 12/241,599, filed Sep. 30, 2008. |
USPTO Final Office Action mailed Jul.17, 2012 for U.S. Appl. No. 12/241,580, filed Sep. 30, 2008. |
USPTO Final Office Action mailed Aug. 1, 2012 for U.S. Appl. No. 12/241,608, filed Sep. 30, 2008. |
USPTO Final Office Action mailed Aug. 9, 2012 for U.S. Appl. No. 12/241,476, filed Sep. 22, 2008. |
USPTO “Final Office Action” mailed Sep. 14, 2012 for U.S. Appl. No. 12/242,587, filed Sep. 30, 2008. |
Intellectual Property Office “Office Action” issued Oct. 25, 2012 for Taiwan Patent Appln. No. 098127906. |
Ntellectual Property Office “Office Action” issued Oct. 30, 2012 for Taiwan Patent Appln. No. 098127902. |
USPTO “Notice of Allowance” mailed Nov. 6, 2012 for U.S. Appl. No. 12/24,599, filed Sep. 30, 2008. |
USPTO “Final Office Action” mailed Nov. 13, 2012 for U.S. Appl. No. 12/609,860, filed Oct. 30, 2009. |
USPTO “Final Office Action” mailed Nov. 13, 2012 for U.S. Appl. No. 12/24,571, filed Sep. 30, 2008. |
USPTO “Non'Final Office Action” mailed Nov. 15, 2012 for U.S. Appl. No. 12/241,608, filed Sep. 30, 2008. |
USPTO “Non-Final Office Action” mailed Dec. 5, 2012 for U.S. Appl. No. 12/24,556, filed Sep. 30, 2008. |
USPTO “Final Office Action” mailed Jan. 23, 2013 for U.S. Appl. No. 12/241,604, filed Sep. 30, 2008. |
USPTO “Non'Final Office Action” mailed Feb. 12, 2013 for U.S. Appl. No. 12/235,476. |
USPTO, “Notice of Allowance and Fee(s) Due” mailed May 7, 2013 for U.S. Appl. No. 12/241,608, filed Sep. 30, 2008. |
USPTO, “Final Office Action” mailed Jun. 7, 2013 for U.S. Appl. No. 12/241,556. |
USPTO, “Office Action” mailed Aug. 9, 2013 for U.S. Appl. No. 12/241,580. |
USPTO, “Notice of Allowance and Fee(s) Due” mailed Aug. 14, 2013 for U.S. Appl. No. 12/235,476. |
USPTO, “Office Action” mailed Aug. 19, 2013 for U.S. Appl. No. 12/241,604. |
USPTO, Non-Final Office Action, dated Sep. 11, 2013 for U.S. Appl. No. 12/241,556. |
USPTO, Non-Final Office Action, dated Sep. 17, 2103 for U.S. Appl. No. 12/242,587. |
Number | Date | Country | |
---|---|---|---|
20100074592 A1 | Mar 2010 | US |