This invention generally relates to portable electronic devices having a display and communication capabilities. Exemplary devices include personal digital assistants (“PDAs”), Web Tablets, touch screen remote controls, lap-top computers, and the like.
In accordance with the description that follows, a system and method is provided for navigating a program guide and/or for using a program guide to command operation of an appliance. An understanding of the objects, advantages, features, properties and relationships of the invention will be obtained from the following detailed description and accompanying drawings which set forth illustrative embodiments and which are indicative of the various ways in which the principles of the invention may be employed.
For a better understanding of the various aspects of the invention, reference may be had to preferred embodiments shown in the attached drawings in which:
A universal remote control and program guide application are provided for executing on a portable electronic device 10. By way of example, representative platforms for the device 10 include, but are not limited to, devices such as remote controls, lap-top computers, Web Tablets and/or PDAs manufactured by HP/Compaq (such as the iPAQ brand PDA), Palm, Visor, Sony, etc. Thus, a preferred underlying platform includes a processor coupled to a memory system comprising a combination of ROM memory, non-volatile read/write memory, and RAM memory (a memory system); a key matrix in the form of physical buttons; an internal clock and timer; a transmission circuit; a power supply; a touch screen display to provide visible feedback to and accept input from a consumer; and I/O circuitry for allowing the device to exchange communications with an external computer such as server and/or client. Additional input circuitry, such as a barcode reader, may also be utilized.
To control the operation of the device 10, the memory system includes executable instructions that are intended to be executed by the processor. In this manner, the processor may be programmed to control the various electronic components within the device 10, e.g., to monitor power, to cause the transmission of signals, etc. Within the memory system, the ROM portion of memory is preferably used to store fixed programming and data that remains unchanged for the life of the product. The nonvolatile read/write memory, which may be FLASH, EEPROM, battery-backed up RAM, “Smart Card,” memory stick, or the like, is preferably provided to store consumer entered setup data and parameters, downloaded data, etc., as necessary. RAM memory may be used by the processor for working storage as well as to hold data items which, by virtue of being backed up or duplicated on an external computer (for example, a client device) are not required to survive loss of battery power. While the described memory system comprises all three classes of memory, it will be appreciated that, in general, the memory system can be comprised of any type of computer-readable media, such as ROM, RAM, SRAM, FLASH, EEPROM, or the like in combination. Preferably, however, at least part of the memory system should be non-volatile or battery backed such that basic setup parameters and operating features will survive loss of battery power. In addition, such memories may take the form of a chip, a hard disk, a magnetic disk, and/or an optical disk without limitation.
For commanding the operation of appliances of different makes, models, and types, the memory system may also include a command code library. The command code library is comprised of a plurality of command codes that may be transmitted from the device 10 under the direction of application(s) for the purpose of controlling the operation of an appliance. The memory system may also includes instructions which the processor uses in connection with the transmission circuit to cause the command codes to be transmitted in a format recognized by an identified appliance. While the transmission circuit preferably utilizes infrared transmissions, it will be appreciated that other forms of wired or wireless transmissions, such as radio frequency, may also be used.
To identify appliances by type and make (and sometimes model) such that application(s) of the device 10 are adapted to cause the transmission of command codes in the format appropriate for such identified appliances, information may be entered into the device 10. Since methods for setting up an application to cause the transmissions of commands to control the operation of specific appliances are well-known, they will not be described in greater detail herein. Nevertheless, for additional details pertaining to remote control setup, the reader may turn to U.S. Pat. Nos. 6,225,938, 4,623,887, 5,872,562, 5,614,906, 4,959,810, 4,774,511, and 4,703,359 which are incorporated herein by reference in their entirety.
To cause the device 10 to perform an action, the device 10 is adapted to be responsive to events, such as a sensed consumer interaction with one or more keys on the key matrix, a sensed consumer interaction with the touch screen display, or a sensed signal from an external source such as a remote computer. In response to an event, appropriate instructions within the memory system are executed. For example, when a hard or soft command key associated with a remote control application is activated on the device 10, the device 10 may read the command code corresponding to the activated command key from the memory system and transmit the command code to an appliance in a format recognizable by the appliance. It will be appreciated that the instructions within the memory system can be used not only to cause the transmission of command codes to appliances but also to perform local operations. While not limiting, local operations that may be performed by the device that are related to the remote control functionality include favorite channel setup, macro button setup, command function key relocation, etc. Examples of such local operations can be found in U.S. Pat. Nos. 5,481,256, 5,959,751, 6,014,092, which are incorporated herein by reference in their entirety.
As discussed, the platform of the device 10 preferably comprises a general purpose, processor system which is controllable by software. The software may include routines, programs, objects, components, and/or data structures that perform particular tasks that can be viewed as an operating system together with one or more applications. The operating system, such as the “Windows CE” brand operating system or the like, provides an underlying set of management and control functions which are utilized by applications to offer the consumer functions such as a calendar, address book, spreadsheet, notepad, Internet browsing, etc., as well as control of appliances. Thus, it is to be understood that applications in addition to or complimentary with the remote-control-like application can also be supported by the device 10 and, as such, in terms of the internal software architecture, the remote-control-like application may be but one of several possible applications which may co-exist within the device 10.
In terms of providing operating system functionality, it should also be understood that the demarcation between the device 10 and a host/client computer, described in greater detail hereinafter, may vary considerably from product to product. For example, at one extreme the device 10 may be nothing more than a slave display and input device in wireless communication with a computer that performs all computational functions. At the other extreme, the device 10 may be a fully-functional computer system in its own right complete with local mass storage. It is also to be appreciated that a hardware platform similar to that described above may be used in conjunction with a scaled-down operating system to provide remote control functionality only, i.e., as a standalone application. In all cases, however, the principles expressed herein remain the same.
To provide a means by which an consumer can interact with the device 10, the device 10 is preferably provided with software that implements a graphical user interface. The graphical user interface software may also provide access to additional software, such as a browser application, that is used to display information that may be received from an external computer. Such a graphical user interface system is described in pending U.S. application Ser. Nos. 09/905,396, 60/334,774, and 60/344,020 all of which are incorporated herein by reference in their entirety.
For simplifying the process of navigating a downloaded program guide, which would be comprised of a grip of channels, times, and program information, the device 10 utilizes a program guide interface that takes advantage of the touch-screen style display. In particular, the program guide interface is designed to overcome one of the more annoying aspects associated with presently known program guides which results when consumers attempt to step from one channel (or time) to another channel (or time) that is relatively far away within a program guide. In particular, to navigate within presently known program guides, the consumer must repetitively press a navigation key, such as up/down, page up/down, time +/−, day forward/back, etc. As will be appreciated, navigation in this manner becomes increasingly tedious and frustrating to consumers as the number of entries within the program guide expands (e.g., with the addition of digital cable channels, satellite channels, etc.).
To address this problem, the user interface of the device 10 provides a horizontal slider 2 and a vertical slider 3 that, as illustrated in
When a slider 2/3 is moved, the information in the banner 4 is preferably, continuously updated to display the relative position of the slider 2/3 within the slider bar so as to provide an indication of the guide information that would be displayed relative to the entirety of information within a given program guide that is displayable should the slider 2/3 be released. For example, the banner 4 might indicate a channel corresponding to the current position of the slider 3 (e.g., channel program information that would be displayed at the top of the display as the starting point of the displayed information) or the banner 4 might indicate a time corresponding to the current position of the slider 2 (e.g., program information for a time period that would be displayed at a side of the display as the starting point of the displayed information). It is further preferred that the underlying information that is displayed not be changed as a slider 2/3 is moved until the slider 2/3 is released (e.g., the stylus is lifted off the slider as a second user input) as illustrated in
To accommodate consumers that who prefer the old way of navigating through the information in the program guide, the interface allows the consumer to tap the arrows 6 at the ends of each slider bar to move/scroll the information one logical page either vertically or horizontally. In the illustrated example, a logical page vertically would comprise 5 rows of channels and one logical page horizontally would comprise a one hour time period. When moving thorough the program guide grid in this manner, the position of the sliders 2/3 should be updated to reflect the current, relative information being displayed. During this procedure, it is not necessary for a banner 4 to be displayed.
To allow the consumer to change the time period for the entirety of the displayable program guide information, e.g., to change days, the interface may provide two options. First, if the time slider (e.g., horizontal slider 2) is moved all the way to its slider bar limit (e.g., the right which is illustrated as corresponding to 11:00 PM—i.e., the end of the current displayable information) and the arrow 6 on the slider bar adjacent to the limit is clicked, the guide information rolls over to the next time period (e.g., 00:00 AM) and the time slider is automatically repositioned to the start of the slider bar (e.g., the extreme left hand side). A similar procedure performed in the reverse direction would be utilized to change the program guide information that is displayable to an earlier time period.
Alternatively, the consumer may activate (i.e., touch) a “calendar” icon 8 which is illustrated at the bottom left of the display to the left of the date. When the calendar icon 8 is touched, a calendar display 11 can be caused to appear as illustrated in
Once the consumer has positioned the program guide to the desired time/channel information, touching a channel button 13 (e.g., the left column) can cause the device 10 to instruct an appliance to immediately switch to that channel (i.e., to send the IR command(s) to switch to that channel.) Furthermore, touching a program name 15, “Friends” in the example shown, can cause the display of additional information in a window 17, for example, regarding that program. When information for a program that is scheduled to air some time in the future is displayed, a “Remind me” checkbox 19, or other known GUI element, can also be presented to the consumer. Selecting this checkbox 19 can be used to cause a reminder to be automatically entered into a calendar application supported by the device 10.
For improving the visibility of programming information contained within the program guide, particularly for consumers with imperfect eyesight, and/or on devices such as high-resolution Web tablets capable of displaying a large amount of information on a relatively small screen area, the device 10 can provide a means for accessing an enlarged or zoomed representation of a portion of the program guide. To this end, as illustrated in
The portion of the program guide displayed as the enlarged portion 30 may be used to display a predetermined amount of programming information to the user (e.g., programming information related to a predetermined range of channels and/or predetermined time periods) or simply contain as much programming information as can be fit into the enlarged display based upon the font size, etc. selected for use in the zooming application. Furthermore, the specific programming information that is contained within the enlarged portion 30 of the program guide may also be predetermined (e.g., based only upon the portion of the program guide that is visible within the display prior to enlargement—see
For the purpose of demonstrating to the consumer that the device 10 is in zoom mode, i.e., the display is showing an enlarged portion of the program guide, the appearance of the icon 12 may be changed. By way of example, the icon 12 can be presented with a line through it to show an activated condition as illustrated by the icon 32 of
The programming information contained within the enlarged portion 30 of the program guide may also be determined based upon interaction with the un-enlarged program guide by the consumer. For example, the consumer may indicate a desire to enter the zoom mode (e.g., by touching the zoom icon which readies the device for zooming, which readiness may be indicated to the user by the display of an icon having a changed or changing appearance) followed by the consumer indicating a location within the un-enlarged program guide that the consumer wishes to have enlarged. The indication of the location may be provided by the consumer using the graphical user interface (e.g., touching a location on the display with a finger or stylus as illustrated in
To change the programming information that is presented within the enlarged portion 30 of the program guide, the user can exit the zoom mode, by retouching the icon 32 for example, and then reinitiating the zoom feature at a different location within the un-enlarged program guide, for example, when a two-step process is utilized. Alternatively, the graphical user interface may be used in manner that indicates to the device that the user wishes to scroll the program guide within the enlarged display area 30 thus changing the portion of the program guide shown there within. This indication can be performed using standard GUI techniques such as associating scroll bars with the display of the enlarged portion 30, scrolling as a result of following the movement of a finger or stylus within the display, etc. In this manner, the consumer may conveniently navigate within the enlarged display portion 30 just as a consumer can navigate within the un-enlarged display portion.
It is to be further understood that the zooming feature may also be used to present control function icons and/or other aspects of the graphical user interface in a larger, more prominent manner without limitation. An example of an enlarged icon is illustrated as icon 12 in
To transmit command codes to an appliance (or perform local operations), a consumer may activate hard keys 70, for example, at the bottom of the device 10 in the exemplary platform illustrated in
Referring now to
Turning to
To transmit commands to tune a target appliance to a specified channel using a program guide, an example of which is illustrated in
When transmitting a command to cause the appliance to tune to a specified channel, the default channel changing operation comprises sending the desired channel digits (a minimum of two, i.e., single digit numbers are prefixed with a leading zero) as a sequence of IR data commands in the format of the channel changing device specified in the Master Control Setup. Accordingly, the actual physical transmission of the sequence of commands is no different than playing back a user-programmed macro. The consumer may be provided, however, with the capability to adjust this default sequence described above if necessary to suit his particular equipment. Any such adjustment may be performed, for example, by touching a “setup” command button 88 (e.g., the wrench icon in the lower left corner of the guide display screen). Activation of the setup command button 88 can be used to present to the consumer a pop-up, setup menu 90 as illustrated in
Using the configuration screen, the consumer may change the master channel tuning device which may offer the same list of appliances and would affect the same parameter as the “Master Control Setup” wizard described earlier in connection with
It will be appreciated that setup menus can also be provided to allow a consumer to specify a target device for command(s) transmitted by interacting with the program guide that need not be tied to the intended target appliance associated with the hard keys 70. Additionally, provision may be made for specifying multiple target appliances for use with the program guide. For example, when the platform is setup in a mode to command appliances in a first room, a first target appliance can be associated with the program guide and when the platform is setup in a mode to command appliances in a second room, a second target appliance can be specified to be associated with the program guide. Similarly, different target appliances can be specified to be the intended target for commands transmitted as a result of interacting with the program guide for each individual consumer setup to use the platform. Still further, if the program guide is adapted to show information from multiple sources, e.g., cable and satellite, different target appliances can be associated with different listing within the program guide as a function of the programming source.
While specific embodiments of the invention have been described in detail, it will be appreciated by those skilled in the art that various modifications and alternatives to those details could be developed in light of the overall teachings of the disclosure. For example, the programming grid need not be limited to channels being displayed in horizontal rows and times in columns. Rather, the principles expressed herein would be useful in connection with any manner for displaying program information that allows the information displayed to be changed or scrolled. Accordingly, the particular arrangement disclosed is meant to be illustrative only and not limiting as to the scope of the invention which is to be given the full breadth of the appended claims and any equivalents thereof.
All of the cited references are incorporated herein by reference in their entirety.
This application is a continuation of U.S. application Ser. No. 10/287,389, filed on Nov. 4, 2002, which, in turn, claims the benefit of U.S. Provisional Patent Application Nos. 60/334,774 filed on Nov. 20, 2001, 60/344,020 filed on Dec. 20, 2001, 60/371,223 filed on Apr. 9, 2002, 60/374,556 filed on Apr. 22, 2002, and 60/390,167, filed on Jun. 20, 2002. Through U.S. application Ser. No. 10/287,389, this application also claims the benefit of and is a continuation-in-part of U.S. patent application Ser. No. 09/905,396. All of these prior applications are incorporated herein by reference in their entirety.
Number | Name | Date | Kind |
---|---|---|---|
4894789 | Yee | Jan 1990 | A |
5005084 | Skinner | Apr 1991 | A |
5293357 | Hallenbeck | Mar 1994 | A |
5307055 | Baskin et al. | Apr 1994 | A |
5410326 | Goldstein | Apr 1995 | A |
5450079 | Dunaway | Sep 1995 | A |
5565888 | Selker | Oct 1996 | A |
5574964 | Hamlin | Nov 1996 | A |
5630119 | Aristides et al. | May 1997 | A |
5635989 | Rothmuller | Jun 1997 | A |
5648760 | Kumar | Jul 1997 | A |
5652613 | Lazarus et al. | Jul 1997 | A |
5671267 | August et al. | Sep 1997 | A |
5710605 | Nelson | Jan 1998 | A |
5724106 | Autry et al. | Mar 1998 | A |
5751372 | Forson | May 1998 | A |
5754348 | Soohoo | May 1998 | A |
5761606 | Wolzien | Jun 1998 | A |
5793438 | Bedard | Aug 1998 | A |
5801787 | Schein et al. | Sep 1998 | A |
5828419 | Bruette et al. | Oct 1998 | A |
5835864 | Diehl et al. | Nov 1998 | A |
5838775 | Montalbano | Nov 1998 | A |
5855006 | Huemoeller et al. | Dec 1998 | A |
5900875 | Haitani et al. | May 1999 | A |
5901366 | Nakano et al. | May 1999 | A |
5915026 | Mankovitz | Jun 1999 | A |
5956025 | Goulden et al. | Sep 1999 | A |
5970206 | Yuen et al. | Oct 1999 | A |
5974222 | Yuen et al. | Oct 1999 | A |
5978043 | Blonstein et al. | Nov 1999 | A |
6002394 | Schein et al. | Dec 1999 | A |
6002450 | Darbee et al. | Dec 1999 | A |
6018372 | Etheredge | Jan 2000 | A |
6020881 | Naughton et al. | Feb 2000 | A |
6028599 | Yuen et al. | Feb 2000 | A |
6037933 | Blonstein et al. | Mar 2000 | A |
6037939 | Kashiwagi et al. | Mar 2000 | A |
6040829 | Croy et al. | Mar 2000 | A |
6097441 | Allport | Aug 2000 | A |
6104334 | Allport | Aug 2000 | A |
6127941 | Van Ryzin | Oct 2000 | A |
6130726 | Darbee et al. | Oct 2000 | A |
6133909 | Schein et al. | Oct 2000 | A |
6137549 | Rasson et al. | Oct 2000 | A |
6151059 | Schein et al. | Nov 2000 | A |
6172674 | Etheredge | Jan 2001 | B1 |
6177931 | Alexander et al. | Jan 2001 | B1 |
6195589 | Ketcham | Feb 2001 | B1 |
6211856 | Choi et al. | Apr 2001 | B1 |
6219694 | Lazaridis et al. | Apr 2001 | B1 |
6256019 | Allport | Jul 2001 | B1 |
6278499 | Darbee et al. | Aug 2001 | B1 |
6285357 | Kushiro et al. | Sep 2001 | B1 |
6341374 | Schein et al. | Jan 2002 | B2 |
6369840 | Barnett et al. | Apr 2002 | B1 |
6407779 | Herz | Jun 2002 | B1 |
6408435 | Sato | Jun 2002 | B1 |
6437836 | Huang et al. | Aug 2002 | B1 |
6463463 | Godfrey et al. | Oct 2002 | B1 |
6532589 | Proehl et al. | Mar 2003 | B1 |
6563430 | Kemink et al. | May 2003 | B1 |
6577350 | Proehl et al. | Jun 2003 | B1 |
6597374 | Baker et al. | Jul 2003 | B1 |
6636273 | Weber | Oct 2003 | B1 |
6742184 | Finseth et al. | May 2004 | B1 |
6978472 | Nashida et al. | Dec 2005 | B1 |
7831930 | Dresti et al. | Nov 2010 | B2 |
20010042247 | Inoue | Nov 2001 | A1 |
20020092023 | Kaizu et al. | Jul 2002 | A1 |
20020122080 | Kunii et al. | Sep 2002 | A1 |
20020154173 | Etgen et al. | Oct 2002 | A1 |
20020184625 | Allport | Dec 2002 | A1 |
Number | Date | Country |
---|---|---|
0561435 | Sep 1993 | EP |
0967797 | Dec 1999 | EP |
0987888 | Mar 2000 | EP |
1204275 | May 2002 | EP |
2343073 | Apr 2000 | GB |
0021286 | Apr 2000 | WO |
0040016 | Jul 2000 | WO |
0058935 | Oct 2000 | WO |
0120572 | Mar 2001 | WO |
Number | Date | Country | |
---|---|---|---|
20090113478 A1 | Apr 2009 | US |
Number | Date | Country | |
---|---|---|---|
60344020 | Dec 2001 | US | |
60371223 | Apr 2002 | US | |
60374556 | Apr 2002 | US | |
60390167 | Jun 2002 | US | |
60334774 | Nov 2001 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 10287389 | Nov 2002 | US |
Child | 12327875 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 09905396 | Jul 2001 | US |
Child | 10287389 | US |