Patent Grant
8997020
This invention relates generally to user interfaces for electronic devices. Exemplary devices include personal digital assistants (“PDAs”), Web Tablets, touch screen remote controls, mobile phones, lap-top computers, and the like.
In accordance with the description that follows, a system and method is provided for enabling enhanced user interaction, information display, and interface selection for electronic devices having graphic display and touch screen capabilities. 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 application and associated interfacing methods 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, personal computers, lap-top computers, Smart Displays, Web Tablets and/or PDAs manufactured by HP/Compaq (such as the iPAQ brand PDA), Palm, Visor, Sony, etc., mobile phones (i.e., Microsoft based Smart Phones, Palm OS and/or Symbian OS based phones), personal gaming systems (i.e., Nintendo GameBoy, Nokia N-Gage), 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 screen to provide visible feedback to and accept input from a user (i.e., via virtual buttons or keys); and I/O circuitry for allowing the device to exchange communications with an external computer such as server and/or client and consumer appliances. Additional input/output circuitry, such as a IR transmitter(s) and/or receiver(s), microphone, loudspeaker or earphone jack, barcode or RFID reader, etc., may also be provided.
To control the operation of the device 10, the memory system includes stored programming 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 non-volatile read/write memory, which may be FLASH, EEPROM, battery-backed up RAM, “Smart Card,” memory stick, or the like, is preferably provided to store user 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 alone or in various combinations. 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 the stored programming instructions for the purpose of controlling the operation of an appliance. The memory system may also include 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 an exemplary 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, 6,157,319, 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 user interaction with one or more keys on the key matrix, a sensed user interaction with the touch screen display, a sensed user voice/sound input, a sensed gesture, a sensed movement, or other non-traditional command input methods, 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 underlying platform of the device 10 preferably comprises a general purpose, processor system which is controllable by stored programming instructions, i.e., 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, device drivers, and the like which are utilized by the various applications to offer the user 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 a user 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. Though described in the below embodiments in conjunction with remote control software applications, it will be understood and appreciated that the various user interface and interaction based features described herein may be used in conjunction with any software program or application and are thus not specifically limited to applications directed to control of consumer appliances.
Compact Status Indicator
For maximizing available display area on a user interface and for simplifying the process of indicating content status and/or browsing through a large content set, the device 10 utilizes a compact status indicator interface 11. In particular, the compact status indicator interface 11 is designed to overcome both size and functionality restraints of portable electronic devices, and present a full featured “scroll-bar” like interface and status indication to a user for browsing through a content set (i.e., a set of text or other displayed data referencing files, photos, music, videos, program guide information, etc., that cannot be conveniently displayed within the available display area of a device). In particular, presently to navigate within large data or content sets, the user must use a traditional scroll-bar type interface such as shown in
Looking now to
Compact status indicator 11 may also indicate the relative location of the then displayed content set on a display via the position of portion 112. For example, in 11a the content set as then displayed in content display area 12 is substantially one-quarter of the way through the amount of available content to be displayed, in 11b the content set as then displayed in content display area 12 is substantially one-half of the way through the amount of available content to be displayed, and in 11c the content set as then displayed in content display area 12 is substantially three-quarters of the way through the amount of available content to be displayed. In the event that portion 112 is not implemented in a specific embodiment and/or has been turned off by the user, it will be appreciated that a similar indication may be achieved by the relative position of the boundary between portions 110 and 114.
The inventive aspects of the present compact status indicator will be understood and appreciated by the foregoing description and associated drawings, however since in one exemplary method compact status indicator 11 is configured and operated to replace traditional scroll-bar 11′, reference to corresponding portions may be seen in
It will be understood and appreciated that the size, placement on a particular user interface or electronic device, shading, coloring, and other “look and feel” elements of the compact status indicator of the current invention may vary widely without departing from the spirit and scope of the current invention. Additionally, the particular methods and techniques for generating and allowing interaction with the compact status indicator will be apparent from the descriptions herein, as well within the routine skill of a programmer skilled in the art. For instance, when implemented in conjunction with a remote control application, the compact status indicator of the current invention can be configured to both provide status of displayed content sets, interaction with such content sets, as well as accomplish other desired user interactions with home appliances using the control methods described above. Thus, the compact status indicator may also be operable in a given device mode to not only indicate a relative position within an appliance state but also to provide interactive control of that state, such as volume control (wherein the pie-shaped indicator has a range from no volume to maximum volume), channel control/surfing (wherein the pie-shaped indicator has a range from the lowest available channel to the highest available channel), etc. In connection with operating the device 10 in this manner, interaction with the indicator may transmit appropriate commands such as volume up/down, channel up/down, etc. In certain circumstances, an absolute value may also be transmitted—such as a specific channel number if the device 10 is provided with a correspondence between a position of the indicator 112 within the pie-graph and a channel number within the range of channel numbers available.
Virtual Scroll Wheel
For further maximizing available display area on a user interface and for simplifying the process of browsing through a large content set, a device 10 may utilize a virtual scroll wheel interface 14. In particular, the virtual scroll wheel interface 14 is designed to overcome both size and functionality restraints of a small electronic device, and present a full featured “mechanical scroll-wheel” or “mechanical jog-dial” like interface to a user for browsing through a large content set (i.e., a set of text or other displayed data referencing files, photos, music, videos, etc. that cannot be conveniently displayed within the available display area of a device) using a finger, stylus, or other user interactivity element. In particular, presently to navigate within large data or content sets, the user must use a traditional scroll-bar type interface such as shown in
Looking now to
Other finger and stylus (and generally any user interactivity element) interactions are possible given the described method, for instance the stylus may be first caused to touch virtual scroll wheel 14 at a substantially middle location, whereby a movement dragging the stylus downward within virtual scroll wheel 14 causes increasingly accelerated upward scrolling of the content in content display area 12, and subsequent upward dragging of the stylus (generally without allowing the stylus to leave the surface of display 1) causes a gradual slowing, and then reversal of direction in the scrolling of content. Likewise, for interaction by a users finger in a manner similar to a scroll wheel on a mouse, virtual scroll wheel 14 may be configured (through programming on device 10) to respond to successive swipes or drags (e.g., touches and releases) of a users thumb in the direction of scroll bar orientation (as determined by programming in or available to device 10). For instance, downward vertical swipes or drags of a users thumb may cause upward scrolling of the content in content display area 12, while upward vertical swipes or drags of a users thumb may cause downward scrolling of the content in content display area 12. It will be understood and appreciated that distances and directions traveled within virtual scroll wheel 14 for scrolling and acceleration purposes, and the particular method and technique of monitoring and calculating stylus screen touch, drag, pause, and off points are the subject of design choices that may be dictated by, among other factors, device platform, operating system, programming language, etc., and are all well within the routine skill of a programmer skilled in the art. By way of example, with reference to
Scalable User Interface
For further maximizing available display area on a user interface and for providing quick transition between a number of available interface states or parameters, or a continuum of interfaces states available to a user, a device 10 may utilize a scalable user interface 200. In particular, the scalable user interface 200 is designed to overcome both size and functionality restraints of portable electronic devices, and present an easily modifiable user interface consisting of two or more interface states to a user for operating and interacting with an application or program on device 10. In particular, to presently modify the particular level of detail, resolution, or other user definable graphic user interface characteristics, the user must use a number of tedious steps and/or operations on the device or software application to effect the desired modifications. While methods such as skins, accessibility settings, and configurable toolbars have been used to allow a user to customize various aspects of a particular user interface, such methods are laborious as indicated above, and lack the immediacy of customization required for certain applications. As will be appreciated, for certain applications such as remote control user interfaces for electronic devices, the lack of immediately customizable user interfaces is problematic given that one main purpose of remote control applications is to save users time and effort when interacting with their home appliances and media content. As such, current user interface customization methods are lacking for multiple user interfaces, applications having multiple interface screens and elements, and for quickly switching between desired application interface states and parameters. The scalable user interface of the current invention overcomes these limitations while presenting an easily customizable, full function interface to a user.
Looking now to
In order to effect modification of interface 200 to interface 202 or 204, the user need not access any menus, settings pages, or the like according to the current invention. Rather, programming on or accessible to device 10 causes various interactions of an interactivity element with a predefined area of the screen to cause interface 200 to be reconfigured as interface 202 or 204. For example, as illustrated in
While not to be taken as limiting, the exemplary method described above involves interacting with a top portion of the display in order to modify one parameter (e.g., resolution, the enlarging or minimizing of interface elements) of interface 200. As shown in
It will be understood and appreciated that the actual shape, graphical elements, and other “look and feel” characteristics of interface states, the type and nature of modifiable interface parameters, as well as location and direction of defined display areas for interface customization purposes, and the particular method and technique of monitoring and calculating stylus screen touch, drag, pause, and off points are the subject of design choices that may be dictated by, among other factors, device platform, operating system, programming language, etc, and are all well within the routine skill of a programmer skilled in the art. As such, many methods of implementing and using the scalable user interface of the current invention are possible without departing from the spirit and scope of the current invention.
Virtual Gesture Pad
For providing an enhanced user interface to a user such that user movements and gestures on a touch screen display enable control and operation of a software application, the device 10 utilizes a virtual gesture pad interface 300. In particular, the virtual gesture pad interface 300 is designed to overcome both size and functionality restraints of portable electronic devices, and present an easily controllable interface such that predefined movements of a stylus, finger, cursor, or other user interactivity element may control operation of a software application, optimally without full attention of the user (i.e., single handed operation and/or operation while not viewing the display of device 10). For example, U.S. Pat. No. 6,396,523 describes a remote control device having a touch pad element adapted to receive gesture based input for initiation of various remote control functions. In this manner, gesture input is converted to command functions and control of the associated home entertainment equipment is effected.
While the system described in U.S. Pat. No. 6,396,523 performs adequately when implemented on a larger scale device having both physical buttons and touch pad elements to facilitate interaction with information presented on a separate display device such as a television screen, what is needed is a virtual gesture pad that functions to provide advanced control based features quickly and interchangeably with traditional soft button based controls for electronic devices having integrated touch sensitive screen displays. As will be appreciated, for certain applications such as touch screen based remote control user interfaces for electronic devices, the lack of easily accessible and intuitive gesture based user interfaces is problematic given that users often desire to operate the remote control application using a single hand or finger, and/or without directly viewing the display screen. As such, current gesture based methods for control and operation of software applications are lacking for integrated touch screen devices. The virtual gesture pad of the current invention overcomes these limitations while presenting an intuitive, interchangeable, gesture based interface to a user.
Looking now to
It will be understood and appreciated by those skilled in the art that various configurations of virtual gesture pads 302 and 304, including different shapes, sizes, and locations of the various gesture targets and the particular method and technique of monitoring and calculating finger or stylus screen touch, drag, pause, and off points are the subject of design choices that may be dictated by, among other factors, device platform, operating system, programming language, etc., and are all well within the routine skill of a programmer skilled in the art. For instance, using methods similar to those illustrated and described in reference to
Graphical Search Query Interface
For maximizing available display area on a user interface and for simplifying the process of indicating to a user the results of a search query and allowing the user to interact with the search query results, a device 10 may utilize a graphical search query interface 400 as shown in
Looking now to
Given the above disclosure and associated figures, it will be appreciated by those skilled in the art that the described results set constitute Venn diagrams as applied to Boolean search methods, however it is one object of the present invention to present these results sets to a user in a dynamic and interactive fashion. As shown in
It will be understood and appreciated that the size, placement on a particular user interface or electronic device, shading, coloring, and other “look and feel” elements of the graphical search query interface of the current invention may vary widely without departing from the spirit and scope of the current invention. Additionally, the particular methods and techniques for generating and allowing interaction with the graphical search query interface will be apparent from the descriptions herein, as well as well within the routine skill of a programmer skilled in the art. For instance, various algorithms for causing search terms or results sets to be modified can be implemented in conjunction with the graphical search query interface of the current invention to accomplish desired user experience goals for a specific device or software product without departing from the spirit and scope of the present invention.
Graphical Indication of Device Mode and State
Device 10 and associated application software may be configured to operate networked control environments wherein some or all of the home appliances and components are configured to be network enabled and interoperable, and which include one or more media server devices and media rendering devices (e.g., as defined and described in the UPnP and/or HAVi specifications which can be found at http://www.upnp.org and http://www.havi.org respectively and which are incorporated herein by reference in their entirety). Turning now to
It will be appreciated that in the case of servers offering multiple content types, switching between content types to be listed in area 12 may be accomplished by touching one of the sub-icons 506, 508, 510 with a stylus, finger, cursor, etc. Such interaction may occur directly within the area 500 illustrated, or alternatively an initial touch may cause an enlarged semi-transparent version of this area to overlay the display in a manner similar to that described earlier in connection with
In another aspect of the current invention, area 500 may provide information regarding a rendering device currently selected rather than a content server. In this case, icon 504 may be representative of a renderer such as a stereo amplifier, TV set, Smart Display, Linksys Digital Media Adapter, HP Digital Media Renderer, or other hardware or software based media renderer, and sub-icons 506, 508, 510 may indicate which types of content that rendering device is capable of processing. In a manner similar to that described above, one of the sub-icons may be highlighted to indicate the currently selected, or currently playing media type. Additionally, in order to indicate to a user that the rendering device represented by icon 504 is one of a plurality of available rendering devices for use, an alphanumeric indicator 505 may be associated with icon 504. Alphanumeric indicator 505 may represent the number of rendering devices available, or may represent the order of the particular rendering device being represented by icon 504 from a number of available rendering devices. Alphanumeric indicator 505 may be placed anywhere on or near icon 504 such that a user may associate indicator 505 with icon 504, and indicator 505 may be configured to respond to touch by a stylus, finger, cursor, or other interactivity element in order to switch to a different rendering device.
For situations where a selected renderer does not include certain media rendering functions, the icons 506, 508, or 510 may include an additional availability indicator 512 (i.e., an “X” placed next to the icon representing the unavailable media function as shown in
Similarly, as shown in
It will be appreciated that these concepts may be extended across multiple areas of the display surface in order to simultaneously present the status of both a server and a rendering device. For example, the space shown occupied by the setup “wrench” icon 520 could in certain circumstances be replaced by a display element similar to area 500, allowing simultaneous presentation of the capabilities of both a server and a rendering device using similar visual elements. In this instance it will be understood that in addition to the touch inputs previously described, switching and routing of media streams, and rendering devices may also be accomplished by dragging a stylus, finger, cursor, etc., from one of the sub-icons of a server representation into a renderer representation, and vice-versa. It will be further understood and appreciated that the size, placement on a particular user interface or electronic device, shading, coloring, and other “look and feel” elements of the described icons and indicators of the current invention may vary widely without departing from the spirit and scope of the current invention.
The system and process of the present invention has been described above via the use of illustrative graphical user interface elements and designs. It is understood that unless otherwise stated to the contrary herein, the functions and methods by which these are generated and rendered may be integrated in a single physical device or a software module in a software product, or may be implemented in separate physical devices or software modules, without departing from the scope and spirit of the present invention.
It is to be appreciated that detailed discussion of the actual implementation of each graphical display element and user interface method is not necessary for an enabling understanding of the invention. The actual implementation is well within the routine skill of a programmer and system engineer, given the disclosure herein of the system attributes, functionality, and inter-relationship of the various elements in the system. A person skilled in the art, applying ordinary skill can practice the present invention without undue experimentation.
While the invention has been described with respect to various illustrative examples, it will be apparent to those skilled in the art that various modifications and improvements may be made without departing from the scope and spirit of the invention. Accordingly, it is to be understood that the invention is not to be limited by these specifically illustrated examples.
All of the cited references are incorporated herein by reference in their entirety
This application claims the benefit of and is a Divisional of U.S. application Ser. No. 11/025,216. Through U.S. application Ser. No. 11/025,216, this application claims the benefit of U.S. Provisional Application Ser. No. 60/534,608 filed on Jan. 6, 2004 and, as a continuation-in-part application, the benefit of U.S. Published Patent Applications Nos. 2003/0103088 filed on Nov. 6, 2002, 2003/0117427 filed on Nov. 4, 2002, and 2002/0143805 filed Jul. 13, 2001. All of these prior applications are incorporated herein by reference in their entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4623887 | Welles, II | Nov 1986 | A |
| 4703359 | Rumbolt et al. | Oct 1987 | A |
| 4774511 | Rumbolt et al. | Sep 1988 | A |
| 4894789 | Yee | Jan 1990 | A |
| 4959810 | Darbee et al. | Sep 1990 | A |
| 5005084 | Skinner | Apr 1991 | A |
| 5293357 | Hallenbeck | Mar 1994 | A |
| 5307055 | Baskin et al. | Apr 1994 | A |
| 5410326 | Goldstein | Apr 1995 | A |
| 5481256 | Darbee et al. | Jan 1996 | A |
| 5515488 | Hoppe et al. | May 1996 | A |
| 5565888 | Selker | Oct 1996 | A |
| 5574964 | Hamlin | Nov 1996 | A |
| 5592604 | Marusak | Jan 1997 | A |
| 5614906 | Hayes et al. | Mar 1997 | 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 |
| 5872562 | McConnell et al. | Feb 1999 | 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 |
| 5959751 | Darbee 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 |
| 6014092 | Darbee et al. | Jan 2000 | 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 |
| 6157319 | Johns et al. | Dec 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 |
| 6225938 | Hayes et al. | May 2001 | B1 |
| 6256019 | Allport | Jul 2001 | B1 |
| 6278499 | Darbee et al. | Aug 2001 | B1 |
| 6285357 | Kushiro et al. | Sep 2001 | B1 |
| 6335725 | Koh et al. | Jan 2002 | B1 |
| 6341374 | Schein et al. | Jan 2002 | B2 |
| 6369840 | Barnett et al. | Apr 2002 | B1 |
| 6396523 | Segal et al. | May 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 |
| 6570583 | Kung et al. | May 2003 | B1 |
| 6577350 | Proehl et al. | Jun 2003 | B1 |
| 6742184 | Finseth et al. | May 2004 | B1 |
| 6798429 | Bradski | Sep 2004 | B2 |
| 6867764 | Ludtke | Mar 2005 | B2 |
| 6978472 | Nashida et al. | Dec 2005 | B1 |
| 7293244 | Randall | Nov 2007 | B2 |
| 7339573 | Andert et al. | Mar 2008 | 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 |
| 20030016248 | Hayes Ubillos | Jan 2003 | A1 |
| 20030025737 | Breinberg | Feb 2003 | A1 |
| 20040263484 | Mantysalo et al. | Dec 2004 | A1 |
| 20050091604 | Davis | Apr 2005 | A1 |
| Number | Date | Country |
|---|---|---|
| 0561435 | Sep 1993 | EP |
| 0967797 | Dec 1999 | EP |
| 0987888 | Mar 2000 | EP |
| 1204275 | May 2002 | EP |
| 2343073 | Apr 2000 | GB |
| 0040016 | Jul 2000 | WO |
| 0058935 | Oct 2000 | WO |
| 0120572 | Mar 2001 | WO |
| Entry |
|---|
| Jun Rekimoto, SmartSkin: An infrastructure for freehand manipulation on interactive surfaces, 2002, pp. 113-120. |
| Pronto User Guide, Universal Electronics Inc., 1999, pp. 1-56. |
| Palm, Inc., Handbook for the Palm Tungsten C Handhelds, 2003, 4 pages. |
| IBM, Technical Disclosure Bulletin, Radial Scale Object, Jul. 1995, pp. 533-535, vol. 38, No. 7. |
| Number | Date | Country | |
|---|---|---|---|
| 20080016467 A1 | Jan 2008 | US |
| Number | Date | Country | |
|---|---|---|---|
| 60534608 | Jan 2004 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 11025216 | Dec 2004 | US |
| Child | 11888238 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 10288727 | Nov 2002 | US |
| Child | 11025216 | US | |
| Parent | 10287389 | Nov 2002 | US |
| Child | 10288727 | US | |
| Parent | 09905396 | Jul 2001 | US |
| Child | 10287389 | US |
