Ambidextrous mouse

Information

  • Patent Grant
  • 9785258
  • Patent Number
    9,785,258
  • Date Filed
    Friday, August 8, 2008
    15 years ago
  • Date Issued
    Tuesday, October 10, 2017
    6 years ago
Abstract
An ambidextrous mouse is disclosed. The ambidextrous mouse is configured for both left and right handed use. The mouse may include right handed buttons on the front side of the mouse and left handed buttons on the back side of the mouse. The user may change the handedness of the mouse by rotating the mouse about a vertical axis of the mouse such that the left hand can use the left hand buttons and the right hand can use the right hand buttons. The mouse may include a handedness selection system for configuring the mouse for right handed or left handed use even though the mouse has the capability for both right and left hands.
Description
BACKGROUND OF THE INVENTION

1. Field of the Invention


The present invention relates generally to an input device for use in a computer system. More particularly, the present invention relates to an ambidextrous mouse.


2. Description of the Related Art


Most computer systems, as for example general purpose computers such as portable computers and desktop computers, receive input from a user via an input device such as a mouse. As is generally well known, the mouse allows a user to move an input pointer (e.g., cursor) and to make selections with respect to a graphical user interface (GUI) on a display screen. The mouse typically includes a trackball or optical sensor (located at the bottom side of the mouse) for translating the motion of the users hand into signals that the computer system can use. For example, by positioning the mouse on a desktop and moving it thereon, the user can move an input pointer or cursor in similar directions within the GUI. The mouse also conventionally includes one or more buttons, which are located on the top side of the mouse. These one or more buttons, when selected, can initiate a GUI action such as menu or object selections. The one or more buttons are typically provided by on or more button caps that move relative to the housing (e.g., through an opening in the housing). Mice may also include a scroll wheel to give the user scrolling functionality. The scroll wheel saves time and steps, and allows a user to move through documents by physically rolling the wheel forward or backward-instead of clicking on the scroll bar displayed on the GUI. In the past, scrolling was implemented by selecting the scroll bar with the mouse, and moving the scroll bar on the GUI by moving the mouse up or down. Furthermore, many popular mice offer an asymmetric shape that fits the asymmetric shape of the hand. Unfortunately, an asymmetric mouse is handed, i.e., it can only be used by a right or left hand.


Although mice designs such as those described above work well, there are continuing efforts to improve their form, feel and functionality.


SUMMARY OF THE INVENTION

The invention relates, in one embodiment, to an ambidextrous mouse configured for left and right handed use. The handedness of the mouse is changed by rotating the mouse about a vertical axis of the mouse by 180 degrees.


The invention relates, in another embodiment, to a touch sensitive mouse comprising a touch sensitive surface that senses a user's touch when the user grabs the mouse.


The invention relates, in another embodiment, to a computing system. The computing system includes a computer. The computing system also includes a mouse operatively coupled to the computer. The mouse includes a position sensing device and a touch sensing device. The position sensing device is configured to generate tracking signals when the mouse is moved relative to a surface. The touch sensing device is configured to generate hand signals when a hand is placed over the mouse.


The invention relates, in another embodiment, to a method for operating a mouse having one or more buttons. The method includes determining if a user is touching the mouse. The method also includes determining the user based on the user's touch. The method additionally includes configuring the mouse based on the user.


The invention relates, in another embodiment, to a user determination method for a mouse. The method includes providing baseline hand signals. The method also includes generating a current hand signal when a user grabs the mouse. The method further includes comparing the current hand signal to at least one baseline hand signal. The method additionally includes determining a characteristic of the user based on the current and baseline hand signals.


The invention relates, in another embodiment, to a method for operating a mouse. The method includes determining if a user is touching the mouse. The method also includes determining the handedness of the user based on the user's touch. The method further includes configuring the motion axes of the mouse based on the handedness of the user. The method additionally includes generating position signals based on mouse movement and the motion axes. Moreover, the method includes sending the position signals to a host. The method also includes forming previous and current hand images and calculating the difference between the previous and current hand images. Thereafter, the method further includes generating control signals based on the difference between the previous and current hand images and sending the control signal to the host.





BRIEF DESCRIPTION OF THE DRAWINGS

The invention will be readily understood by the following detailed description in conjunction with the accompanying drawings, wherein like reference numerals designate like structural elements, and in which:



FIG. 1 is a perspective diagram of a mouse, in accordance with one embodiment of the present invention.



FIG. 2A is perspective diagram of a unibody ambidextrous mouse, in accordance with one embodiment of the present invention.



FIG. 2B is front or back view of the unibody ambidextrous mouse shown in FIG. 2A, in accordance with one embodiment of the present invention.



FIG. 2C is right side view of a unibody ambidextrous mouse shown in FIG. 2A, in accordance with one embodiment of the present invention.



FIG. 2D is a left side view of a unibody ambidextrous mouse shown in FIG. 2A, in accordance with one embodiment of the present invention.



FIG. 2E is a side view of the unibody ambidextrous mouse shown of FIG. 2A in use, in accordance with one embodiment of the present invention.



FIG. 2F is a side view of the unibody ambidextrous mouse shown of FIG. 2A in use, in accordance with one embodiment of the present invention.



FIG. 2G is a front view of the unibody ambidextrous mouse shown of FIG. 2A in use, in accordance with one embodiment of the present invention.



FIG. 3A is a side elevation view, in cross section of a mouse, in accordance with one embodiment of the present invention.



FIG. 3B is a top view of the mouse shown in FIG. 3A, in accordance with one embodiment of the present invention.



FIG. 3C is a broken away side elevation view, in cross section of the mouse shown in FIG. 3A, in accordance with one embodiment of the present invention.



FIG. 3D is a broken away side elevation view, in cross section of the mouse shown in FIG. 3A, in accordance with one embodiment of the present invention.



FIG. 4 is a top view of a mouse, in accordance with another embodiment of the present invention.



FIG. 5 is block diagram of a computer system, in accordance with one embodiment of the present invention.



FIG. 6 is a perspective diagram of a touch sensitive mouse, in accordance with one embodiment of the present invention.



FIG. 7A is a top view of the touch sensitive mouse of FIG. 6 producing a first hand signal, in accordance with one embodiment of the present invention.



FIG. 7B is a top view of the touch sensitive mouse of FIG. 6 producing a second hand signal, in accordance with one embodiment of the present invention.



FIG. 8 is a perspective diagram of a mouse, in accordance with one embodiment of the present invention.



FIG. 9 is a mouse operational method, in accordance with one embodiment of the present invention.



FIG. 10 is a handedness determination method, in accordance with one embodiment of the present invention.



FIG. 11 is an actual user determination method, in accordance with one embodiment of the present invention.



FIG. 12 is an absolute mapping method, in accordance with one embodiment of the present invention.



FIG. 13 is a relative mapping method, in accordance with one embodiment of the present invention.



FIG. 14 is a mouse operational method, in accordance with one embodiment of the present invention.





DETAILED DESCRIPTION OF THE INVENTION

The invention generally pertains to an ambidextrous mouse that can be used equally by both left and right hands. One aspect of the invention corresponds to a mouse that has the same feel and function for both the left and right hands. Another aspect of the invention corresponds to a mouse having a handedness selection system for configuring the mouse for right and left hand use. Another aspect of the invention corresponds to a mouse having a touch sensing device capable of sensing a user's touch when a user positions their hand over the mouse. The sensed user's touch may be used to determine characteristics of the user as well as to identify the user. The sensed user's touch may also be used to perform button functions.


These and other embodiments of the invention are discussed below with reference to FIGS. 1-14. However, those skilled in the art will readily appreciate that the detailed description given herein with respect to these figures is for explanatory purposes as the invention extends beyond these limited embodiments.



FIG. 1 is a perspective diagram of a mouse 20, in accordance with one embodiment of the invention. The mouse 20 is a handheld device for providing user commands to a host system. In most cases, the mouse is configured to control movements and/or performing actions on a graphical user interface of a display screen associated with a computer system. The mouse may be coupled to the host system via a wired or wireless connection. In the case of wired connections, the mouse may include a cable for connecting to the host system. In the case of wireless connections, the mouse may include a radio frequency (RF) link, optical infrared (IR) link, Bluetooth link or the like in order to eliminate the cable. In the illustrated embodiment, the mouse includes a wireless link, thus there are no cables or cords extending therefrom.


The mouse 20 generally includes a housing 22 that provides a structure for moving the mouse 20 along a surface and for gripping the mouse 20 for movement thereof. The housing 22 also helps to define the shape or form of the mouse 20. That is, the contour of the housing 22 embodies the outward physical appearance of the mouse 20. The contour may be rectilinear, curvilinear or both. In most cases, a bottom member 24 of the housing has an external contour that substantially conforms to the contour of a flat surface such as a desktop. In addition, a top member 26 of the mouse housing 22 generally has an external contour that substantially conforms to the contour of the inside surface of a hand. The top member 26 may be symmetric and/or asymmetric. Asymmetric mice are typically handed (e.g., dedicated to either the left or right hand) and symmetric mice are typically ambidextrous (e.g., capable of being used by both the left and right hand). In the illustrated embodiment, the lateral shape of the top member 26 (e.g., cross section in the X-Z plane) is asymmetric in order to provide ergonomic comfort to the asymmetric hand and the longitudinal shape of the top member 26 (e.g., cross section in the Y-Z plane) is symmetric in order to allow the mouse to be used by either hand (ambidextrous). With regards to ambidextrous, the mouse 20 may be rotated about the vertical axis by 180 degrees to change usage from right handed to left handed (or vice versa).


The housing 22 also provides a structure for enclosing, containing and/or supporting the components of the mouse 20. Although not shown, the components may correspond to electrical and/or mechanical components for operating the mouse 20. For example, the components may include a track ball or optical assembly for monitoring the movement of the mouse 20 along a surface and for sending signals corresponding to the movements to the host system. In most cases, the signals produced by these components direct an input pointer to move on a display screen in a direction similar to the direction of the mouse 20 as it is moved across a surface. For example, when the mouse 20 is moved forward or backwards, the input pointer is moved vertically up or down, respectively, on the display screen. In addition, when the mouse 20 is moved from side to side, the input pointer is moved from side to side on the display screen.


The mouse 20 also includes one or more buttons 28 for performing actions on the display screen. In most cases, the user simply presses on the button 28 in order to perform the action. By way of example, the actions may include selecting an item on the screen, opening a file or document, executing instructions, starting a program, viewing a menu, and/or the like. The button functions may also include functions that make it easier to navigate through the host system, as for example, zoom, scroll, open different menus, home the input pointer, perform keyboard related actions such as enter, delete, insert, page up/down, and the like.


The buttons 28 generally include one or more actuators (not shown in FIG. 1) for sensing and/or detecting when a user's finger has pressed on the button 28. The actuators may be configured to detect when the button 28 moves and/or they may be configured to detect the presence of the user's hand on the button 28. The actuators may also be capable of sensing the amount of pressure being exerted on a button 28 by the user's hand. The actuators may be switches, sensors and/or the like. By way of example, the switches may correspond to tact switches, optical switches, and the like. In addition, the sensors may correspond to optical sensors, resistive sensors, surface acoustic wave sensors, pressure sensors (e.g., strain gauge), capacitive sensors and the like.


The position of the buttons 28 relative to the mouse housing 22 may be widely varied. For example, the buttons 28 may be positioned almost anywhere (e.g., top, side, front, or back) on the mouse housing 22 so long as they are accessible to a user during manipulation of the mouse 20. Any number of buttons may be used. In most cases, the number of buttons correspond to the number of button functionalities offered by the mouse. For handed mice, a single button is typically provided if a single click is desired, and two buttons are provided if right and left clicks are desired. In some cases, more than two buttons are provided if a center click or scroll function is further desired. For ambidextrous mice, the mouse includes one or more buttons on opposing sides of the mouse, as for example on both the front and back of the mouse (e.g., 180 degrees opposite). This is done to ensure that both the left and right hands have a button(s). Like handed mice, each side of the ambidextrous mouse may include multiple buttons (e.g., right click, left click, center click, scroll, etc.). Furthermore, the buttons may be formed from almost any shape (e.g., squares, circles, ovals, triangles, rectangles, polygons, and the like). The shape of multiple buttons may have identical shapes or they may have different shapes. In addition, the size of the buttons may vary according to the specific needs of each device. In most cases, the size of the buttons corresponds to a size that allows them to be easily manipulated by a user (e.g., the size of a finger tip or larger).


In the illustrated embodiment, the mouse 20 is an ambidextrous mouse and therefore it includes a separate button 28A and 28B on both the front and back of the mouse. The ambidextrous mouse also includes a button 28C on the side of the mouse. The front button 28A may be actuated by a right handed user, the back button 28B may be actuated by a left handed user and the side button 28C may be actuated by the thumb of both the left and right hands. As should be appreciated, the mouse configuration shown in FIG. 1 allows for the same “feel” and the same “function” (e.g., left and right handed buttons as well as a thumb button) for both the right handed and left handed users. That is, the mouse contour provides the user with asymmetric comfort to both the left and right handed users while the button configuration allows similar button functionality to both the left and right handed users. As mentioned above, the “handedness” is switched by turning the mouse 180 degrees.


The manner in which the buttons 28 may be implemented can be widely varied. For example, they may be selected from button caps, wheels, unified button housings, touch sensitive button housings and/or the like. Button caps or wheels typically work independent of and move relative to the housing 22. For example, the button cap may pivot or translate relative to the top member 26 and the wheel may rotate relative to the top member 26. In most cases, the movement of the button cap or wheel actuates one or more switches or sensors enclosed within the housing 22. For example, the button cap may actuate a tact switch located within the housing and the wheel may actuate an encoder located within the housing. The moving button cap or wheel may or may not produce a mechanical clicking action. As should be appreciated, a mechanical clicking action typically gives audible and tactile feedback to the user when the user presses on the button. In cases where there is no mechanical clicking action, the mouse may include audible and tactile feedback generators so that a user knows when the button has been actuated.


Additionally or alternatively, the buttons 28 may be provided by a unified button/housing that incorporates the functionality of a button (or buttons) directly into the housing 22 of the mouse 20, i.e., the button functionality and a substantial portion of the housing are combined (as opposed to attaching separate button caps or wheels to or through the housing). In a unified button housing, the housing 22 includes a movable member so as to actuate one or more switches or sensors enclosed within the housing 22. For example, the top member 26 may move relative to the bottom member 24 thus initiating the button function. The manner in which the top member 26 moves relative to the bottom member 24 may be widely varied. For example, the top member 26 may pivot, translate or rotate relative to the bottom member 24. In a unified button housing, the areas of the housing 22 that move generally take the form of button zones that represent regions of the mouse housing 22 that may be pressed on to implement one or more button functions. In essence, the housing 22 serves as a button (or buttons) of the mouse 20. Like the button cap and wheel, the unified button housing may or may not produce a clicking action. By way of example, a description of unified button housing such as that described in this paragraph may be found in commonly owned U.S. Pat. No. 6,373,470 and patent application Ser. No. 10/060,712, both of which are herein incorporated by reference.


Additionally or alternatively, the buttons 28 may be provided by touch sensitive surfaces on the housing 22. In this implementation, the switches and/or sensors of the button 28 produce working areas in the form of button zones that activate when a finger sits on, presses, or passes over them. The sensors may be contained within the housing 22 or they may be embedded in the housing 22 itself. Furthermore, the touch sensitive surfaces may be placed on stationary or moving parts of the mouse 20. In the case of stationary, they may be placed on a mouse where the top member and bottom member are fixed to one another thereby preventing movements therebetween. In the case of moving, they may be placed on a button cap that moves relative to the top member 26, or a top member 26 that moves relative to the bottom member 24 (e.g., unified button housing).


Although not shown in FIG. 1, the mouse 20 may further include a handedness selection system for configuring the mouse for right handed or left handed use even though the mouse 20 has the capability for both right and left hands. In one embodiment, the handedness selection system is a user actuated system that allows a user to select which hand configuration is desired (e.g., left or right). The user actuated system may be widely varied. For example, it may include a mechanism or switch arrangement that activates and deactivates the opposing buttons. In one implementation, the mechanism is a shuttle member that includes a tab that physically prevents button movement (or actuation of the corresponding indicator) on one side of the mouse 20 while allowing button movement on the other side of the mouse 20. In another implementation, the switch is a mechanical, electrical or optical switch that activates or deactivates the indicators associated with the buttons, i.e., opens or closes the circuits associated with the actuators. In both implementations, the right handed button can be turned on and the left handed button off or the right handed button can be turned off the left handed button turned on. As should be appreciated, this is generally done to prevent the palm of the hand from actuating the opposing zone when positioned thereon during use In most cases, the mouse 20 is set as a right handed mouse (e.g., factory default). The switch, however, allows the user to quickly and easily reconfigure the mouse 20 for left handed use if needed. Alternatively, the handedness of the mouse 20 may be selected via software as for example through a control panel located on a graphical user interface.


In another embodiment, the handedness selection system is a mouse actuated system that allows the mouse 20 (or system connected thereto) to automatically configure the mouse 20 for right handed or left handed use based on how the user grabs the mouse 20 (e.g., position and pressure). If a left handed user grabs the mouse, then the mouse configures itself to be a left handed mouse during use. If a right handed user grabs the mouse, then the mouse configures itself to be a right handed mouse. Like the user actuated system, the mouse actuated system may be widely varied. For example, the system may include a sensor arrangement arranged to detect the hand on the surface of the mouse when a user grabs the mouse and thereafter make a determination as to whether the hand is left or the right hand based on what was detected. For example, if sensors detect the presence of fingers on area 28A and a palm on area 28B then the mouse can determine that the mouse is being used by a right handed user. Once the determination is made, the mouse 20 can turn on the functionality of the buttons 28 corresponding to the hand being used and turn off the functionality of the buttons corresponding to the hand not in use.


The sensor arrangement may also be configured to help make a determination as to how the user is holding the mouse. As should be appreciated, each user holds the mouse in a different manner and thus there may be discrepancies between how the user perceives the actuation of a button and how the mouse interprets the actuation of a button. By way of example, the sensor arrangement may help determine that the fingers are positioned in a particular manner with a particular amount of pressure therefore the user is trying to initiate a particular type of action (e.g., make a right click rather than a left click or vice versa). The sensor arrangement may also double as the actuator of a button (e.g., touch sensitive button housing). By way of example, the sensor arrangement may include touch sensitive sensors such as resistive sensors, surface acoustic wave sensors, pressure sensors (e.g., strain gauge), capacitive sensors and the like. An example of touch sensitive mice, which contain sensor arrangements, can be found in commonly owned U.S. patent application Ser. No. 10/157,343, which is herein incorporated by reference.



FIGS. 2A-2F are diagrams of a unibody ambidextrous mouse 50, in accordance with one embodiment of the present invention. By way of example, the mouse 50 may correspond to the mouse 20 shown in FIG. 1. The term “unibody” herein refers to a mouse that integrates at least one button function directly into the mouse housing 52, i.e., unified button/housing. The term “ambidextrous” herein refers to a mouse that is capable of being used by both a left and right hand 51, i.e., the mouse is not handed.


The unibody ambidextrous mouse 50 generally includes a mouse housing 52 that contains the circuitry of the mouse 50 as well as defines the shape or form of the mouse 50. With regards to the unibody design, the mouse housing 52 includes a base 54 and a movable button body 56. The base 54, which defines the lower portion of the mouse, provides a structure for supporting the various components of the mouse as well as for making moving contact with a surface such as a desktop or mouse pad. By way of example, the base 54 may support a trackball mechanism or an optical sensor so as to track the position of the mouse 50 as it is moved along the surface. The base may also support printed circuit boards (PCB), processors, transmitters, encoders, indicators, and the like.


The movable button body 56, which defines the upper portion of the mouse 50, provides a structure for moving the mouse 50 along a surface, for gripping the mouse 50 for movement thereof and for implementing the button functions of the mouse 50. Since the mouse 50 is ambidextrous, the button body 56 is configured to receive either a right or left hand 51R and 51L (e.g., ambidextrous). As shown in FIG. 2B, the lateral shape of the button body 56 is asymmetric. This is generally done to provide ergonomic comfort to the asymmetric hand 51 whether right or left. With regards to the asymmetric lateral shape, the top side 58 of the body 56 includes a slope that tapers from a high point 60 to a low point 62 thus enabling the hand 51 to curve over the body in a natural manner (See FIG. 2G). The top side 58 that defines slope may be widely varied. For example, it may be rectilinear, curvilinear or both. The top side 58 may also be substantially convex (protrudes outwardly), concave (protrudes inwardly) or flat. In FIG. 2B, the top side 58 has a convex shape. The lateral sides 66 of the body 56 may be varied similarly to the top side 58 of the body 56 although the lateral sides 66 are substantially vertical as compared to the horizontal top side 58. The lateral sides 66 are generally configured to receive the thumb and the outermost finger or fingers during use (See FIG. 2G). In some cases, at least the thumb lateral side has a concave shape thus creating a thumb cove for receiving the thumb during use of the mouse 50


Unlike the lateral shape, the longitudinal shape of the button body 56 as shown in FIGS. 2C and 2D is symmetric. This allows the mouse 50 to be used by either hand 51R or 51L (ambidextrous). With regards to the symmetric longitudinal shape, the top side 58 of the body 56 is convex as shown in FIGS. 2C and 2D. That is, it equally slopes from a high point 68 to a low point 70 on both the front and back sides 72F and 72B of the mouse 50 thus enabling the hand 51 to curve over the body 56 in a natural manner (See FIGS. 2E and 2F). The mouse 50 may be rotated about the vertical axis by 180 degrees to change usage from right handed to left handed or vice versa (See FIGS. 2E and 2F).


Because the mouse 50 is a unibody mouse, the button body 56 is configured to move relative to the base 54. The portions of the body 56 that move generally take the form of button zones 75 that represent regions of the body 56 that may be pressed on to implement one or more button functions. The movement of the body 56 relative to the base 54 may be provided through one or more degrees of freedom (DOF). The degrees of freedom may be implemented through one or more rotations, pivots, translations, flexes relative to the base 54. By way of example, the button body 56 may be coupled to the base 54 via one or more pin joints, slider joints, ball and socket joints, flexure joints and/or the like. In addition, the mouse may include combinations such as pivot/translating joint, pivot/flexure joint, pivot/ball and socket joint, translating/flexure joint, a flexure joint, a ball and socket joint, and the like.


In the illustrated embodiment, the mouse 50 includes a pair of button zones 75 on both the front and back side 72F and 72B of the mouse 50. The button zones 75A and 75B on the front side 72F are used by right handed users and the button zones 75C and 75D on the back side 72B are used for left handed users. As should be appreciated, the pair of button zones may provide a right and left click similar to that of conventional mice. In order to provide this configuration of button zones 75, the body 56 is configured to have four movements: front left tilt, front right tilt, back left tilt, and back right tilt. In order to provide these movements, the body 56 is configured to pivot in two directions relative to a base 54. As shown by the arrows, the body 56 can pivot about a first axis 80 and a second axis 82. The positions of the two axis 80, 82 may be widely varied so long as they allow the four movements described above. In the illustrated embodiment, the two axes 80, 82 are orthogonal (or perpendicular) to one another and centrally located relative to the mouse 50. As such, the shape of the button zones 75A-D are somewhat similar.


During right handed use, the body 56 is capable of moving between an initial position (no pivot) and a left tilt position (pivot about both axis) when a force is applied to a left front portion 75B of the body 56 and between an initial position and a right tilt position (pivot about both axis) when a force is applied to a right front portion 75A of the body 56. During left handed use, the body 56 is capable of moving between an initial position (no pivot) and a left tilt position (pivot about both axis) when a force is applied to a left back portion 75C of the body 56 and between an initial position and a right tilt position (pivot about both axis) when a force is applied to a right back portion 75D of the body 56. The force may be any downward force on the mouse 50, whether from a finger, palm or hand. The button body 56 may be spring biased so as to place the button body 56 in the initial position.


The button functions of the button zones 75A-D are implemented via actuators located underneath the button zones 75A-D. The actuators may be any combination of switches and sensors. Switches are generally configured to provide pulsed or binary data such as activate (on) or deactivate (off). The sensors, on the other hand, are generally configured to provide continuous or analog data. In one implementation, when the user presses on the particular button zone 75 an underside portion of the body 56 is configured to contact or engage (and thus activate) a switch located underneath the particular button zone 75. By way of example, the switch may correspond to a tact switch. In another implementation, when a user presses on the button zone 75 one or more sensors are configured to monitor the pressure exerted by the finger(s) on the surface of the mouse 50 proximate the button zone 75 as well as the position of the finger(s) on the surface of the mouse 50 proximate the button zone 75. By way of example, the sensors may be capacitance sensors. These and other embodiments will be described in greater detail below.


In addition to buttons 75, the mouse 50 includes a wheel 86 configured to generate a control function when rotated. In general, the wheel 86 is arranged to rotate around an axis 88 in order to implement the control function. The position of the wheel 86 relative to the mouse housing 52 may be widely varied. For example, the wheel 86 may be placed at any external surface of the mouse housing 52 that is accessible to a user during manipulation of the mouse 50 (e.g., top, side, front, or back). In the illustrated embodiment, the wheel 86 is positioned on the side 66A of the body 56 in a location proximate the middle of the mouse 50 (e.g., between the front and back 72F and 72B) so that it can receive the thumb of either hand (e.g., left or right) when the hand 51 is placed on the top side 58 of the mouse 50. When the thumb is received, the thumb may be used to rotate the wheel 86 in order to generate the control function. As should be appreciated, this position allows ambidextrous use.


The wheel 86 may be widely varied. For example, the wheel 86 may be configured to rotate about a horizontal (e.g., X or Y) or vertical axis (e.g., Z). Furthermore, the wheel 86 may protrude outwardly from the housing 52, be flush with the housing 52 or it may even be recessed within the housing 52. In the embodiment of FIG. 2, the wheel 86 protrudes from housing 52 thus making it easily accessible to a user's thumb. The wheel 86 also rotates about the Y axis so that the thumb can be moved up and down along the side of the mouse in order to operate the scroll wheel (e.g., moving forwards to back in the case of the X and Z axis is generally more difficult to manage with the thumb). The wheel 86 may also include tactile features 90, which provide tangible surfaces that help the user manipulate the wheel 86 (e.g., knurl). Although not shown, the wheel 86 may further include a clicking action that inform the user of its rotatable position during rotation thereof. Another example of a wheel 86 which may be used can be found in commonly owned patent application Ser. No. 10/060,712, which is herein incorporated by reference.


The control function initiated by the wheel may be widely varied. The control function may be implemented incrementally or continuously during rotation of the wheel 86. For example, the control function may be used to control various applications associated with the computer system to which the mouse is connected. The control function may correspond to a scrolling feature. The term “scrolling” as used herein generally pertains to moving displayed data or images (e.g., text or graphics) across a viewing area on a display screen so that a new set of data (e.g., line of text or graphics) is brought into view in the viewing area. In most cases, once the viewing area is full, each new set of data appears at the edge of the viewing area and all other sets of data move over one position. That is, the new set of data appears for each set of data that moves out of the viewing area. In essence, the scrolling function allows a user to view consecutive sets of data currently outside of the viewing area. The viewing area may be the entire viewing area of the display screen or it may only be a portion of the display screen (e.g., a window frame).


The direction of scrolling may be widely varied. For example, scrolling may be implemented vertically (up or down) or horizontally (left or right). In the case of vertical scrolling, when a user scrolls down, each new set of data appears at the bottom of the viewing area and all other sets of data move up one position. If the viewing area is full, the top set of data moves out of the viewing area. Similarly, when a user scrolls up, each new set of data appears at the top of the viewing area and all other sets of data move down one position. If the viewing area is full, the bottom set of data moves out of the viewing area. The scrolling feature may also be used to move a Graphical User Interface (GUI) vertically (up and down), or horizontally (left and right) in order to bring more data into view on a display screen. By way of example, the scrolling feature may be used to help perform internet browsing, spreadsheet manipulation, viewing code, computer aided design, and the like. The direction that the wheel 86 rotates may be arranged to control the direction of scrolling. For example, the wheel 86 may be arranged to move the GUI vertically up when rotated counterclockwise, and vertically down when the rotated clockwise (or vice versa).



FIGS. 3A-3D are diagrams of a unibody mouse 100, in accordance with one embodiment of the present invention. By way of example the mouse may correspond to any of the mice previously described. The mouse generally includes a base 102 and a button body 104. The button body 104 is pivotally coupled to the base 102 about an axis 106. As such, the button body 104 may pivot forwards in order to actuate a first button zone or backwards to actuate a second button zone. When pivoted forward, a front portion 108 of the button body 104 engages a first switch 110A located within the space 112 defined by the base 102 and the button body 104. When pivoted backwards, a back portion 114 of the button body 104 engages a second switch 110B located within the space 112 defined by the base 102 and button body 104. More particularly, nubs 116 of the button body 104 contacts an actuator 118 that protrudes from the switches 110. When the actuator 118 is pushed down, the switch 110 is configured to generate a control signal. The first switch 110A generates a first control signal associated with the first button zone and the second switch 110B generates a second button signal associated with the second button zone. Both switches 110 are typically attached to the base 102.


The mouse 100 further includes a button zone selection mechanism 120 for configuring the button zones of the mouse 100. The mechanism 120 allows the user to activate and/or deactivate the button zones 100. This particular feature is advantageous in ambidextrous mice where it would be beneficial to turn off right handed button zones when using the mouse as a left handed mouse and to turn off left handed button zones when using the mouse as a right handed button. In the illustrated embodiment, the mechanism 120 is configured to activate one of the button zones while deactivating the other button zone. The mechanism generally includes a shuttle plate 122 that translates relative to the base 102 or button body 104. In FIG. 3, the shuttle plate 122 is slidably coupled to the base 102. The shuttle plate 122 includes a first cantilever 124A and a second cantilever 124B, which are disposed at opposing ends of the shuttle plate 122. The shuttle plate 122 additionally includes first and second abutment stops 126A and 126B disposed at opposing ends of the shuttle plate 122. As shown, the cantilevers 124 are spatially separated from the abutment stops 126 thereby forming voids therebetween.


The cantilevers 124 and abutment stops 126 are configured to slide between the switches 110 and the nubs 116 on each side of the mouse 100. In order to turn off a button zone, the abutment stop 126 is slid between the housing of the switch 110 and the nub 116. The abutment stop 126 therefore prevents the nub 116 from contacting the actuator 118 when the corresponding button zone is selected. That is, the abutment stop 126 stops the motion of the nub 116 before it reaches the actuator 118. Because the actuator 118 cannot be contacted, no control signals can be generated and thus the button zone is deactivated. In order to activate a button zone, the cantilever 124 is slid between the nub 116 and the actuator 118. The cantilever 124 is an intermediate member that is capable of transmitting motion from the nub 116 to the actuator 118 of the switch 110. Because the actuator 118 may be actuated via the nub/cantilever 116/124, control signals can be generated and thus the button zone is activated.


To elaborate further, the shuttle plate 122 is connected to a support arm 128 and the support arm 128 is connected to a user actuated switch 130. The switch 130 is configured to move between a first position and a second position and the support arm 128 is configured to transmit the motion of the switch 130 to the shuttle plate 122. The switch 130 can therefore be used to slide the shuttle plate 122 to its various locations within the mouse 100 in order to activate and deactivate the button zones. In the illustrated embodiment, the switch 130 is capable of moving the shuttle plate 122 relative to both switches 110 and both nubs 116 so that the shuttle plate 122 turns off one of the button zones while turning on the other button zone. That is, the user simply moves the switch 130 to a the first position in order to activate the first button zone and deactivate the second button zone, and to the second position in order to activate the second button zone and deactivate the first button zone. For example, when the switch 130 is moved to the first position, the support arm 128 causes the shuttle plate 122 to translate towards the front of the mouse 100 thereby placing the abutment stop 126A between the nub 116A and the housing of switch 110A and the cantilever 124B between the actuator 118B and the nub 116B. Furthermore, when the switch 130 is moved to the second position, the support arm 128 causes the shuttle plate 122 to translate towards the back of the mouse 100 thereby placing the abutment stop 126B between the nub 116B and the housing of switch 110B and the cantilever 124A between the actuator 118A and the nub 116A.


The mechanism may be widely varied. For example, the components may be integrally formed as a unit or they may be separate components that work together (e.g., linkage). Furthermore, the components may be substantially free moving or they may be movably restrained. For example, the shuttle plate 122 may move within a guide formed by the base or body. Moreover, the switch 130 may be configured to translate, or rotate in order to move the shuttle plate. In the illustrated embodiment, the switch 130 translates within a recess 132 formed in the bottom side of the base 102. The recess 132 is generally longer than the switch 130 so that the switch 130 can be slid therein. In most cases, the switch 130 is recessed within the bottom side of the base 102 so that the switch 130 won't protrude therefrom. As should be appreciated, the bottom side of the base 102 is generally moved along a surface and therefore any protrusions would impede its motion or cause unwanted switches. In some cases, the switch 130 may include tactile surfaces such as a knurled surface.



FIG. 4 is top view of a unibody mouse 140, in accordance with an alternate embodiment of the present invention. Unlike the unibody mouse of FIG. 3 that includes two button zones, the unibody mouse of FIG. 4 includes four button zones. In this embodiment, the button body 104 is configured to pivot about two axis 106 and 107 in order to cause a front tilt right, front tilt left, back tilt right and back tilt left. Each tilt causes the body 104 to contact one of four switches 110A-D in a manner similar to that described above. In this embodiment, the shuttle plate 142 includes an abutment stop 144 and a pair of cantilevers 146 on each side. Each of the cantilevers 146 corresponds to a different switch 110 while the abutment stops 144 each correspond to the switches 110 on each side of the mouse 100. As such, when the shuttle plate 142 translates towards the front of the mouse 140 the abutment stop 144B is placed between the nub (not shown) and the housing of switches 110C and 110D thereby deactivating the button zones in the back of the mouse 140, and the pair of cantilevers 146A and 146B are placed between the nub and actuator 118 of switches 110A and 110B thereby activating the button zones in the front of the mouse 140. Furthermore, when the shuttle plate 142 translates towards the back of the mouse 140 the abutment stop 144A is placed between the nub and housing of switches 110A and 110B thereby deactivating the button zones in the front of the mouse, and the pair of cantilevers 146C and 146D are placed between the nub and the actuator 118 and of switches 110C and 110D thereby activating the button zones in the back of the mouse 140.



FIG. 5 is a block diagram of a computing system 150, in accordance with one embodiment of the present invention. The system 150 includes a mouse 152 and a computer 154, including but not limited to, a desktop computer, lap top computer, hand held computer, and the like. By way of example, the computer 154 may correspond to any Apple or PC based computer. The computer 154 generally includes a processor 156 configured to execute instructions and to carry out operations associated with the computer system 150. For example, using instructions retrieved for example from memory, the processor 156 may control the reception and manipulation of input and output data between components of the computing system 150. The processor 156 can be a single-chip processor or can be implemented with multiple components.


In most cases, the processor 156 together with an operating system operates to execute computer code and produce and use data. The computer code and data may reside within a program storage 158 block that is operatively coupled to the processor 156. Program storage block 158 generally provides a place to hold data that is being used by the computer system 150. By way of example, the program storage block 158 may include Read-Only Memory (ROM), Random-Access Memory (RAM), hard disk drive and/or the like. The computer code and data could also reside on a removable program medium and loaded or installed onto the computer system when needed. Removable program mediums include, for example, CD-ROM, PC-CARD, floppy disk, magnetic tape, and a network component.


The computer 154 also includes an input/output (I/O) controller 160 that is operatively coupled to the processor 156. The (I/O) controller 160 may be integrated with the processor 156 or it may be a separate component as shown. The I/O controller 160 is generally configured to control interactions with one or more I/O devices (e.g., mouse 152) that can be coupled to the computer 154. The I/O controller 160 generally operates by exchanging data between the computer 154 and the I/O devices that desire to communicate with the computer 154. The I/O devices and the computer 154 typically communicate through a data link 162. The data link 162 may be a one way link or two way link. In some cases, the I/O devices may be connected to the I/O controller 160 through wired connections. In other cases, the I/O devices may be connected to the I/O controller 160 through wireless connections. By way of example, the data link 162 may correspond to PS/2, USB, IR, RF, Bluetooth or the like.


The computer 154 also includes a display controller 164 that is operatively coupled to the processor 156. The display controller 164 may be integrated with the processor 156 or it may be a separate component as shown. The display controller 164 is configured to process display commands to produce text and graphics on a display device 166. The display device 166 may be integral with the computer or it may be a separate component of the computer 154. By way of example, the display device may be a monochrome display, color graphics adapter (CGA) display, enhanced graphics adapter (EGA) display, variable-graphics-array (VGA) display, super VGA display, liquid crystal display (e.g., active matrix, passive matrix and the like), cathode ray tube (CRT), plasma displays and the like.


The mouse 152, on the other hand, generally includes a position sensing device 170 and a touch sensing device 172, both of which are operatively coupled to a microcontroller 174. The position sensing device 170 is configured to generate tracking signals when the mouse 152 is moved along a surface. The tracking signals may be used to control the movement of a pointer or cursor on the display screen 166. The tracking signals may be associated with a Cartesian coordinate system (x and y) or a Polar coordinate system (r, θ). By way of example, the position sensing device 170 may correspond to a conventional trackball or optical assembly.


The touch sensing device 172 is configured to generate hand signals when the hand is positioned over or on the mouse 152. The hand signals may be used to initiate button functions or to make a determination as to which user is using the mouse 152. By way of example, the button functions may include moving an object on the display screen, selecting an item on the display screen, opening a file or document, launching a program, executing instructions, viewing a menu on the display screen, and/or the like. The button functions may also include functions associated with keyboard related actions such as enter, delete, insert, page up/down, and the like. The button functions may further include gesturing. With regards to the determination, the user may correspond to the identity of the user (e.g., Bob or Carol) or to a type of user (e.g., left or right handed user). These and other embodiments will be described in greater detail below.


The touch sensing device 172 generally includes one or more sensors for detecting the proximity of the finger thereto and/or the pressure exerted thereon. By way of example, the sensors may be based on resistive sensing, surface acoustic wave sensing, pressure sensing (e.g., strain gauge), optical sensing, capacitive sensing and the like. Depending on the type of sensor used, the hand signals may be in the form of position signals as for example when the sensors are set up in a grid or pixilated format. In one particular embodiment, the touch sensing device uses capacitance sensors. As should be appreciated, whenever two electrically conductive members come close to one another without actually touching, their electric fields interact to form capacitance. In one configuration, the first electrically conductive member is one or more electrodes or wires and the second electrically conductive member is the finger of the user. Accordingly, as the finger approaches the surface of the mouse, a tiny capacitance forms between the finger and the electrodes/wires in close proximity to the finger. The capacitance in each of the electrodes/wires is measured by the microcontroller 174. By detecting changes in capacitance at each of the electrodes/wires, the microcontroller 174 can determine the user type and button selections when the finger or palm is placed on the mouse 152.


The microcontroller 174 is configured to acquire the data from the sensing devices 170 and 172 and to supply the acquired data to the processor 156 of the computer 154. In one embodiment, the microcontroller 174 is configured to send raw data to the processor 156 so that the processor 156 processes the raw data. For example, the processor 156 receives data from the microcontroller 174 and then determines how the data is to be used within the computer system 152. In another embodiment, the microcontroller 174 is configured to process the raw data itself. That is, the microcontroller 174 reads the pulses from the sensors of the sensing devices 170 and 172 and turns them into data that the computer 154 can understand. By way of example, the microcontroller 174 may place the data in a HID format (Human Interface Device). The microcontroller 174 may also convert the acquired signals into other forms of signals before sending them to the processor 156. For example, the microcontroller 174 may convert hand signals into button signals. With regards to button signals, the microcontroller 174 may set the distribution of button zones. The button zones generally represent a more logical range of user inputs than the sensors themselves. The microcontroller 174 may also be used to perform user type recognition, i.e., recognizes if the mouse is being used as a right or left hand by distinguishing fingers and palm of hand. The microcontroller 174 typically includes an application specific integrated circuit (ASIC) that is configured to monitor the signals from the sensing devices 170 and 172, to process the monitored signals and to report this information to the processor (e.g., x, y, button, left, right, etc.). By way of example, this may be implemented through Firmware.


In one embodiment, program storage block 158 is configured to store a mouse program for controlling information from the mouse 152. Alternatively or additionally, a mouse program or some variation thereof may be stored in the mouse 152 itself (e.g., Firmware). The mouse program may contain hand profiles associated with hand actions. The hand profiles generally describe how the mouse 152 is held while the hand actions describe what type of action to perform based on the hand profile. In one implementation, the hand profiles may be accessed by a user through a hand menu, which may be viewed on the display device as part of a GUI interface. The hand menu may include hand settings pertaining to the hand profiles and hand actions. In fact, the hand menu may serve as a control panel for reviewing and/or customizing the hand settings, i.e., the user may quickly and conveniently review the hand settings and make changes thereto. Once changed, the modified hand settings will be automatically saved and thereby employed to handle future mouse processing. The hand menu may also be used as part of a training sequence for training the mouse 152 to a particular user type.



FIG. 6 is a perspective diagram of a touch sensitive mouse 180, in accordance with one embodiment of the present invention. The touch sensitive mouse 180 includes a touch sensitive surface 182 that senses surface contact so that the mouse 180 (or host) knows where and when the fingers and palm are touching the mouse 180 and how much pressure there is at each point. The touch sensitive surface 182 is generally provided by the mouse housing 184 and a sensor arrangement 186. The sensor arrangement 186 may be integrally formed into the wall of the mouse housing 184 or they may be located behind the wall within the enclosed space defined by the mouse housing 184 (e.g., adjacent the interior wall). The sensor arrangement 186 is configured to detect the presence of an object such as a finger or palm of the hand as for example when the hand grasps the mouse housing 184. The sensor arrangement 186 may also detect the pressure being exerted on the mouse by the finger or palm of the hand. By way of example, the sensor arrangement 186 may be based on resistive sensing, surface acoustic wave sensing, pressure sensing (e.g., strain gauge, pressure plates, piezoelectric transducers or the like), heat sensing, optical sensing, capacitive sensing and/or the like.


As shown, the sensor arrangement 186 is divided into several independent and spatially distinct sensing points (or regions) 188 that are positioned around the periphery of the mouse 180. The sensing points 188 are generally dispersed about the mouse 180 with each sensing point 188 representing a different position on the surface of the mouse 180. The sensing points 188 may be positioned in a grid or a pixel array where each pixilated sensing point 188 is capable of generating a signal. The number and configuration of the sensing points 188 may be widely varied. The number and configuration of sensing points 188 generally depends on the desired resolution of the touch sensitive surface 182. In the simplest case, a signal is produced each time the finger is positioned over a sensing point 188. When an object is placed over multiple sensing points 188 or when the object is moved between or over multiple sensing points 188, multiple position signals are generated. In most cases, the signals are monitored by a control system (not shown) that converts the number, combination and frequency of the signals into control information. As should be appreciated, the number, combination and frequency of signals in a given time frame may indicate size, location, direction, speed, acceleration and the pressure of the finger or palm on the mouse 180. By way of example, the control system may be a microcontroller located on the mouse and/or a processor of a host device such as a computer.


In the illustrated embodiment, the sensing points 188 are based on capacitance. As should be appreciated, whenever two electrically conductive objects come near one another without touching, their electric fields interact to form capacitance. By detecting when the capacitance changes (e.g., increase, decreases) the mouse's electronics can determine when and where the finger and palm of the hand are touching. Any conventional form of capacitance sensing may be used, including but not limited to capacitive sensing methods as found in touch pads, key boards, and the like. The simplicity of capacitance allows for a great deal of flexibility in design and construction of the sensor arrangement (e.g., mutual capacitance sensing, capacitance to ground sensing, etc.).


In the illustrated embodiment, the sensor arrangement 186 includes a two layer grid of spatially separated electrodes or wires 190 and 192 that are connected to a microcontroller (not shown). The upper layer includes electrodes 190 in rows while the lower layer includes electrodes 192 in columns (e.g., orthogonal). As should be appreciated, when a portion of a hand nears the intersection of two electrodes 190 and 192, the capacitance at the electrodes 190 and 192 changes since the hand has very different dielectric properties than air. These changes can be used to determine the positions of the finger and/or palm when they grab the mouse 180. In some cases, the amount of capacitance to each of the electrodes 190 and 192 can be measured by the microcontroller when a portion of a hand nears the intersection of two electrodes 190 and 192 (e.g., sensing point). In other cases, capacitance from each of the row electrodes 190 to each of the column electrodes 192 can be measured by the microcontroller when a portion of a hand nears the intersection of two electrodes 190 and 192 (e.g., sensing point).


The signals generated at the sensing points 188 may be used to determine how the user is holding the mouse 180. By way of example and referring to FIGS. 7A and 7B, each portion of the hand in contact with the mouse produces a contact patch area 196. Each of the contact patch areas 196 covers several sensing points 188 thus generating several position signals. The position signals may be grouped together to form a hand signal that represents how the user is holding the mouse 180. In essence, the hand signal is a pixilated image of the hand in contact with the mouse 180. A first hand signal may be compared to a second hand signal to determine button selection or user type. For example, the hand signal generated in FIG. 7A may be compared to the hand signal generated in FIG. 7B. The first hand signal generally corresponds to the most current hand signal while the second hand signal generally corresponds to a previous hand signal. The previous hand signal may be an in use hand signal or a baseline hand signal that was preset or trained before use. In most cases, the in use hand signal is the last hand signal before the current hand signal.


In one embodiment, the difference between a current hand signal (FIG. 7A) and a last hand signal (FIG. 7B) may indicate the user's desire to implement a button function. As should be appreciated, when a user presses on the surface of the mouse the area of some of the contact patch areas 196 increases thereby activating more sensing points 188 than previously activated. A significant difference indicates the user's desire to implement a button function. Changes between contact patch areas may further indicate the particular button function.


In relative mapping, the difference at each particular contact patch area 196 is compared relative to the other particular contact patch areas 196. For example, if the contact patch area for the right finger grows more significantly than the contact patch area for the left finger between first and second signals then the particular button function may be a right click. Furthermore, if the contact patch area for the left finger grows more significantly than the contact patch area for the right finger between first and second signals then the particular button function may be a left click.


In absolute mapping, the mouse 180 includes one or more button zones that represent regions of the mouse 180 that when selected implement the particular button function associated with the button zone (e.g., right click, left click). The button zone having the contact patch area 196 with the most significant change between first and second hand signals is the one that is typically implemented. The user may customize the mouse 180 by setting the configuration of button zones before use. For example, the mouse 180 may be configured as a one button mouse, two button mouse, three button mouse or the like. The mouse 180 may also be configured with scrolling zones. The position and size of the button zones may also be customizable. For example, the mouse 180 may be configured with button zones on only the front or back of the mouse (e.g., left hand or right hand button) or on the side of the mouse (e.g., thumb button). The customization may be performed by the user and/or the mouse 180.


In another embodiment, the similarity between a baseline hand signal and a current hand signal may indicate the user's desire to implement a control function (e.g., gesturing). For example, if the baseline hand signal corresponds to a right click and the current hand signal is similar to the baseline hand signal then the mouse can implement a right click. The user may customize the mouse by setting the baseline hand signal before use (e.g., calibration).


In another embodiment, the similarity between a baseline hand signal and a current hand signal may also indicate the user type (e.g., handedness of the user or the identity of the user). For example, if the baseline hand signal corresponds to a left hand user and the current hand signal is similar to the baseline hand signal then the mouse knows that the user is left handed. The user may customize the mouse by setting the baseline hand signal before use (e.g., calibration).



FIG. 8 is a perspective diagram of a mouse 200, in accordance with one embodiment of the present invention. As shown, the mouse 200 includes a body 202 that moves relative to base 204. In particular, the body 202 is capable of pivoting about a pair or axes 206 and 208. The pivoting nature allows for a plurality of tilting actions, i.e., a front right tilt, a front left tilt, a back right tilt and a back left tilt. The mouse 200 also includes a pair of capacitance sensing devices 210 located at the front and back of the mouse 200. The capacitance sensing devices 210 are configured to monitor a user's touch. Each of the capacitance sensing devices includes a plurality of electrodes 212 that generate signals when the hand nears the body 202.


The signals generated from the electrodes 212 may be used by the mouse to perform button functions as well as to determine the user type. For example, the electrodes 212 may generate a first group of signals for a right handed user and a second set of signals for a left handed user. As should be appreciated, right handed users typically place their fingers on the front and their palm on the back of the mouse while left handed users typically place their fingers on the back and the palm on the front of the mouse. Furthermore, the electrodes 212 may generate a different group of signals for each tilting action. These signals may be processed by the mouse system to determine what button function to implement for the tilting action. For example, when the mouse 200 is tilted to the front right, the signals may be used to generate a right click for a right handed user and when the mouse 200 is tilted to the front left, the signals may be used to generate a left click for a right handed user. Furthermore, when the mouse 200 is tilted to the back right, the signals may be used to generate a right click for a left handed user and when the mouse 200 is tilted to the back left, the signals may be used to generate a left click for a left handed user.


Because the mouse 200 does not produce a click for each tilt, it may include a tactile click generator electrically controlled for example using a solenoid actuator on the inside of the mouse housing. When the mouse (e.g., firmware) decides a click has been made, the plunger of the solenoid actuator taps a rib inside the mouse housing which provides tactile and audible feedback to the user (e.g., simulates a clicking action). A buzzer may also be used to give audio feedback.


It should be noted that a dual pivoting body is not a limitation. In some cases, the body may be configured to pivot about a single axis, i.e., pivoting about axis 206 is eliminated. In other cases, other movements other than pivoting may be implemented. Furthermore, the body may be configured to not move at all.



FIG. 9 is a mouse operational method 220 in accordance with one embodiment of the present invention. By way of example the method 220 may be performed using the system shown in FIG. 5. The method 220 generally begins at block 222 where the mouse is in standby. Standby generally implies that the mouse is in a state of readiness waiting for something to happen, i.e., a user initiating an action therewith. Following block 222, the process flow proceeds to block 224 where a determination is made as to whether the user is touching the mouse. This is generally accomplished with touch sensing device capable of generating signals when a hand nears the mouse and a control system configured to monitor the activity of the touch sensing device. If it is determined that the user is not touching the mouse, then the process flow proceeds back to block 222 thereby keeping the mouse in standby. If it is determined that the user is touching the mouse, then the process flow proceeds to block 226 where the user is determined.


In one embodiment, block 226 includes determining the handedness of the user. In another embodiment, block 226 includes determining the actual user (e.g., Bob or Carol). The determination may be performed automatically or it may be selective, i.e., user initiated. Once the user is determined, the process flow proceeds to block 228 where the mouse is configured based on the user. In one embodiment, the motion axes of the mouse are configured based on the handedness of the user. In another embodiment, the button zones of the mouse are configured based on the handedness of the user. In other embodiments, the motion axes as well as the button zones are configured based on the actual user (e.g., Bob or Carol). The button zones may be based on relative mapping or absolute mapping.


Following block 228 the process flow proceeds to simultaneously occurring blocks 230 and 232. In block 230, the movement of the mouse is monitored. This may be accomplished with a position sensing device such as a track ball or optical sensor. In block 232, the hand action of the user is monitored. This may be accomplished by a touch sensing device that senses user touch and generates hand signals based on the user's touch. Following block 230, the process flow proceeds to block 234 where position signals are generated based on the mouse movement. For example, in the case of a Cartesian coordinate based system the position sensing device may generate X, Y signals. Following block 232, the process flow proceeds to block 236 where button signals are generated based on the hand action. For example a first hand signal may be compared to a second hand signal and differences or similarities therebetween can be used to determine what button signal to generate. After blocks 234 and 236, the position and button signals may be used to perform actions in a host system. For example, the position signals may be used to move a cursor and the button signals may be used to make selections in a graphical user interface.



FIG. 10 is a handedness determination method 240, in accordance with one embodiment of the present invention. By way of example, the method may be included in block 226 of FIG. 9. The method generally begins at block 242 where a current hand signal is generated. The hand signal is typically generated by a touch sensing device of the mouse. Following block 242 the process flow proceeds to block 244 where the current hand signal is compared to baseline left and/or right hand signals. This is typically accomplished by the mouse microcontroller (174), but it may also be processed by the host system (154) as well. Following block 244 the process flow proceeds to block 246 where a determination is made as whether the current hand signal is similar to the baseline left hand signal. Similar to the previous block, this may be accomplished by the mouse microcontroller (174) or the host system (154). If the current hand signal is similar, then the process flow proceeds to block 248 where the mouse is configured for left hand use. That is, the motion axes and button zones are set for the left handed user. If the current hand signal is not similar to the left hand profile, then the process flow proceeds to block 250 where a determination is made as to whether the current hand signal is similar to a baseline right hand signal. If the current hand signal is similar then the process flow proceeds to block 252 where the mouse is configured for right hand use. If the current hand signal is not similar to the right hand profile then the process flow proceeds back to block 242 or in some cases one configuration may be chosen as a default (e.g., right hand may be the default)



FIG. 11 is an actual user determination method 260, in accordance with one embodiment of the present invention. By way of example, the method may be included in block 226 of FIG. 9. The method is generally performed in multiple steps including a calibration step 262 and an in use step 264. The calibration step 262 is performed before the use step 264. The calibration step is generally performed once while the use step is continuously used during mouse use. The calibration step 262 generally begins at block 266 where baseline hand signals are generated for each user. Following block 266 the process flow proceeds to block 268 where the user settings (e.g., motion axis, button zones) for the baseline hand signal are configured. Following block 268, the process flow proceeds to block 270 where the baseline hand signal and user settings are stored in a user profile database.


The use step 264 generally begins at block at block 272 where a current hand signal is generated. Following block 272, the process flow proceeds to block 274 where the current hand signal is compared to the baseline hand signals stored in the user profile database. Following block 274, the process flow proceeds to block 276 where the baseline hand signal most similar to the current hand signal is selected. If there is no signal similar to the current signal then the user may be prompted to go through the calibration step 262. Following block 276, the process flow proceeds to block 268 where the mouse is configured according to the user settings associated with the selected baseline hand signal.



FIG. 12 is an absolute mapping method 280, in accordance with one embodiment of the present invention. By way of example, the method 280 may be included in block 232 of FIG. 9. The method 280 generally begins at block 282 where one or more button zones are provided. Button zones are area of the mouse that may be actuated by a user to implement an action. The button zones may be based on a training sequence, selected from a menu, or they may be preset. Following block 282 the process flow proceeds to block 284 where a hand signal is generated. Following block 284, the process flow proceeds to block 286 where a determination is made as to which button zone was selected based on the hand signal. For example, position coordinates generated by touch may correspond to a particular button zone. Following block 286, the process flow proceeds to block 288 where a button signal is generated based on the selected button zone.



FIG. 13 is a relative mapping method 290, in accordance with one embodiment of the present invention. By way of example, the method may be included in block 232 of FIG. 9. The method 290 generally begins at block 292 where a first hand signal is generated. Following block 292, the process flow proceeds to block 294 where a second hand signal is generated. In this embodiment, the first hand signal generally corresponds to a hand signal generated before the second hand signal. For example, the first hand signal may be the last hand signal while the second hand signal may be the current hand signal. Following block 294, the process flow proceeds to block 296 where the difference between the current hand signal and the baseline hand signal is determined. If the difference is within a threshold value, then the process flow proceeds back to block 294. This serves as a filter element or noise reduction. As should be appreciated, the user tends to continuously adjust hand position during use even if they are not making a selection (e.g., noise). If the difference is outside a threshold value then the process flow proceeds to block 298 where a button signal is generated based on the difference between the first hand signal and the second hand signal.



FIG. 14 is a mouse operational method 300, in accordance with one embodiment of the present invention. By way of example the method 300 may be performed using the system shown in FIG. 5. The method 300 generally begins at block 302 where the mouse is in standby. Following block 302, the process flow proceeds to block 304 where a determination is made as to whether the user is touching the mouse. If it is determined that the user is not touching the mouse, then the process flow proceeds back to block 302 thereby keeping the mouse in standby. If it is determined that the user is touching the mouse, then the process flow proceeds to block 306 where the handedness of user is determined. By way of example, this may be accomplished using the method described in FIG. 10.


Following block 306, the process flow proceeds to block 308 where the motion axes are configured based on the handedness determined in block 306. Motion axes generally refer to which portion of the mouse will be used for button selection as well as which direction of mouse motion is positive X motion and which direction of mouse motion is positive Y motion. The direction of the motion axes are important if the mouse is rotated 180 degrees between left and right handed users as in the mouse configuration shown in FIG. 2.


Thereafter, the process flow proceeds along two routes. The first route proceeds with block 310 where position signals are generated based on mouse movement. Thereafter in block 312, a position signal is sent to a host based on the mouse movement and the motion axis set in block 308. The second route proceeds with a relative mapping sequence including blocks 314-320. In block 314, a previous hand image is formed based on user touch. Following block 314, the process flow proceeds to block 316 where a current hand image is formed based on user touch. Thereafter, in block 318 a difference between the current hand image and the previous hand image is determined. Following block 318, the process flow proceeds to block 320 where a determination is made as to whether a click (e.g., button selection) was made by the user based on the difference. If a click or button selection was not made, then the process flow proceeds back to block 314. If a click of button selection was made then the process flow proceeds to block 322 where a button signal associated with the button selection is sent to the host.


The methods described above can be used alone or in various combinations. The methods may be implemented singularly or by a combination of hardware, software, and/or firmware. The methods can also be embodied as computer readable code on a computer readable medium. The computer readable medium is any data storage device that can store data, which can thereafter be read by a computer system. The computer readable medium can also be distributed over a network coupled computer systems so that the computer readable code is stored and executed in a distributed fashion.


While this invention has been described in terms of several preferred embodiments, there are alterations, permutations, and equivalents, which fall within the scope of this invention. It should also be noted that there are many alternative ways of implementing the methods and apparatuses of the present invention. It is therefore intended that the following appended claims be interpreted as including all such alterations, permutations, and equivalents as fall within the true spirit and scope of the present invention.

Claims
  • 1. A user configurable mouse, comprising: a buttonless touch sensitive surface divided into an array of buttonless sensing points, each buttonless sensing point being configured to generate a signal when the buttonless sensing point detects that an object is touching the buttonless sensing point, the signal including information identifying the particular location of the buttonless sensing point, wherein signals from one or more buttonless sensing points of the array of buttonless sensing points are combined to form a buttonless hand signal that defines a two-dimensional image of an object in contact with the buttonless touch sensitive surface of the mouse; anda processor configured to: receive the buttonless hand signal;determine from the buttonless hand signal which touch zone amongst one or more touch zones in the touch sensitive surface was selected, wherein each of the one or more touch zones is associated with a plurality of buttonless sensing points; andgenerate a function signal based on the selected touch zone, wherein each touch zone corresponds to a particular function.
  • 2. The mouse as recited in claim 1, wherein the buttonless sensing points are capacitive buttonless sensing points.
  • 3. The mouse as recited in claim 1, wherein the processor is further configured to compare the buttonless hand signal to a plurality of baseline hand signals, determine a handedness of a user holding the mouse based on the comparison, and configure the touch zones of the mouse in accordance with the determined handedness of the user holding the mouse.
  • 4. The mouse as recited in claim 3, further comprising motion axes that define directions of movement of the mouse, the motion axes configurable based on the determined handedness of the user.
  • 5. The mouse as recited in claim 1, wherein the signal generated by each buttonless sensing point further includes information indicating how much pressure the object is exerting on the buttonless sensing point.
  • 6. The mouse as recited in claim 1, wherein the buttonless hand signal is compared to a plurality of baseline hand signals to determine an identity of a user holding the mouse, each baseline hand signal associated with a unique user profile.
  • 7. The mouse as recited in claim 6, wherein the touch zones of the mouse are configured in accordance with the identity of the user holding the mouse.
  • 8. The mouse as recited in claim 6, further comprising motion axes that define directions of movement of the mouse, the motion axes configurable based on the determined identity of the user.
  • 9. A method for operating a user configurable mouse having a buttonless touch sensitive surface, the method comprising: providing one or more touch zones in the buttonless touch sensitive surface, each touch zone configurable for actuating a particular function;dividing the buttonless touch sensitive surface into an array of buttonless sensing regions, wherein each of the one or more touch zones is associated with a plurality of the buttonless sensing regions;configuring each buttonless sensing region to generate a signal when the buttonless sensing region detects that an object is touching the buttonless touch sensitive surface of the buttonless sensing region, the signal including information identifying a particular location of the buttonless sensing region in the buttonless touch sensitive surface;combining signals from one or more buttonless sensing regions of the array of buttonless sensing regions to form a buttonless hand signal that defines a two dimensional image of an object in contact with the mouse;determining which touch zone was selected based on the buttonless hand signal; andgenerating a function signal based on the selected touch zone.
  • 10. The method as recited in claim 9, wherein the buttonless sensing regions are configured with capacitive touch sensors.
  • 11. The method as recited in claim 9, wherein the buttonless hand signal is compared to a plurality of baseline hand signals to determine a handedness of a user holding the mouse, and wherein the touch zones of the mouse are configured in accordance with the determined handedness of the user holding the mouse.
  • 12. The method as recited in claim 11, further comprising motion axes that define directions of movement of the mouse, the motion axes configurable based on the determined handedness of the user.
  • 13. The method as recited in claim 9, wherein the signal generated by each buttonless sensing point further includes information indicating how much pressure the object is exerting on the buttonless sensing point.
  • 14. The method as recited in claim 9, wherein the buttonless hand signal is compared to a plurality of baseline hand signals to determine an identity of the user holding the mouse, each baseline hand signal associated with a unique user profile.
  • 15. The method as recited in claim 14, wherein the touch zones of the mouse are configured in accordance with the identity of the user holding the mouse.
  • 16. The method as recited in claim 14, further comprising motion axes that define directions of movement of the mouse, the motion axes configurable based on the determined identity of the user.
CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a division of U.S. patent application Ser. No. 10/654,108 filed Sep. 2, 2003 now U.S. Pat. No. 7,808,749, the entire disclosure of which is incorporated herein by reference.

US Referenced Citations (566)
Number Name Date Kind
3333160 Gorski Jul 1967 A
3541541 Englebart Nov 1970 A
3662105 Hurst et al. May 1972 A
3798370 Hurst Mar 1974 A
4110749 Janko et al. Aug 1978 A
4246452 Chandler Jan 1981 A
4264903 Bigelow Apr 1981 A
4550221 Mabusth Oct 1985 A
4566001 Moore et al. Jan 1986 A
4672364 Lucas Jun 1987 A
4672558 Beckes et al. Jun 1987 A
4692809 Beining et al. Sep 1987 A
4695827 Beining et al. Sep 1987 A
4719524 Morishima et al. Jan 1988 A
4733222 Evans Mar 1988 A
4734685 Watanabe Mar 1988 A
4736191 Matzke et al. Apr 1988 A
4746770 McAvinney May 1988 A
4771276 Parks Sep 1988 A
4788384 Bruere-Dawson et al. Nov 1988 A
4806846 Kerber Feb 1989 A
4866602 Hall Sep 1989 A
4891508 Campbell Jan 1990 A
4896370 Kasparian et al. Jan 1990 A
4898555 Sampson Feb 1990 A
4917516 Retter Apr 1990 A
4922236 Heady May 1990 A
4933660 Wynne, Jr. Jun 1990 A
4968877 McAvinney et al. Nov 1990 A
5003519 Noijean Mar 1991 A
5017030 Crews May 1991 A
5027690 Wachi et al. Jul 1991 A
5125077 Hall Jun 1992 A
5178477 Gambaro Jan 1993 A
5179648 Hauck Jan 1993 A
5186646 Pederson Feb 1993 A
5189403 Franz et al. Feb 1993 A
5194862 Edwards Mar 1993 A
5224151 Bowen et al. Jun 1993 A
5224861 Glass et al. Jul 1993 A
5237311 Mailey et al. Aug 1993 A
5241308 Young Aug 1993 A
5252951 Tannenbaum et al. Oct 1993 A
5281966 Walsh Jan 1994 A
5305017 Gerpheide Apr 1994 A
D349280 Kaneko Aug 1994 S
5339213 O'Callaghan Aug 1994 A
5345543 Capps et al. Sep 1994 A
5355148 Anderson Oct 1994 A
5376948 Roberts Dec 1994 A
5379057 Clough et al. Jan 1995 A
5398310 Tchao et al. Mar 1995 A
5404152 Nagai Apr 1995 A
5414445 Kaneko et al. May 1995 A
5438331 Gilligan et al. Aug 1995 A
5442742 Greyson et al. Aug 1995 A
D362431 Kaneko et al. Sep 1995 S
5463388 Boie et al. Oct 1995 A
5463696 Beernink et al. Oct 1995 A
5473343 Kimmich et al. Dec 1995 A
5473344 Bacon et al. Dec 1995 A
5483261 Yasutake Jan 1996 A
5488204 Mead et al. Jan 1996 A
5495077 Miller et al. Feb 1996 A
5495566 Kwatinetz Feb 1996 A
5510813 Makinwa et al. Apr 1996 A
5513309 Meier et al. Apr 1996 A
5523775 Capps Jun 1996 A
5528265 Harrison Jun 1996 A
5530455 Gillick et al. Jun 1996 A
5541372 Baller et al. Jul 1996 A
5543590 Gillespie et al. Aug 1996 A
5543591 Gillespie et al. Aug 1996 A
5559943 Cyr et al. Sep 1996 A
5561445 Miwa et al. Oct 1996 A
5563632 Roberts Oct 1996 A
5563996 Tchao Oct 1996 A
5565658 Gerpheide et al. Oct 1996 A
5565887 McCambridge et al. Oct 1996 A
5578817 Bidiville et al. Nov 1996 A
5579036 Yates, IV Nov 1996 A
5581681 Tchao et al. Dec 1996 A
5583946 Gourdol Dec 1996 A
5585823 Duchon et al. Dec 1996 A
5590219 Gourdol Dec 1996 A
5592566 Pagallo et al. Jan 1997 A
5594471 Deeran et al. Jan 1997 A
5594810 Gourdol Jan 1997 A
5596347 Robertson et al. Jan 1997 A
5596694 Capps Jan 1997 A
5598183 Robertson et al. Jan 1997 A
5598527 Debrus et al. Jan 1997 A
5611040 Brewer et al. Mar 1997 A
5611060 Belfiore et al. Mar 1997 A
5612719 Beernink et al. Mar 1997 A
5631805 Bonsall May 1997 A
5633955 Bozinovic et al. May 1997 A
5634102 Capps May 1997 A
5636101 Bonsall et al. Jun 1997 A
5642108 Gopher et al. Jun 1997 A
5644657 Capps et al. Jul 1997 A
D382550 Kaneko et al. Aug 1997 S
5661505 Livits Aug 1997 A
5666113 Logan Sep 1997 A
5666502 Capps Sep 1997 A
5666552 Greyson et al. Sep 1997 A
D385542 Kaneko et al. Oct 1997 S
5675361 Santilli Oct 1997 A
5675362 Clough et al. Oct 1997 A
5677710 Thompson-Rohrlich Oct 1997 A
5686720 Tullis Nov 1997 A
5689253 Hargreaves et al. Nov 1997 A
5710844 Capps et al. Jan 1998 A
5726687 Belfiore et al. Mar 1998 A
5729219 Armstrong et al. Mar 1998 A
5729250 Bishop et al. Mar 1998 A
5730165 Philipp Mar 1998 A
5736976 Cheung Apr 1998 A
5741990 Davies Apr 1998 A
5745116 Pisutha-Arnond Apr 1998 A
5745716 Tchao et al. Apr 1998 A
5748185 Stephan et al. May 1998 A
5748269 Harris et al. May 1998 A
5751274 Davis May 1998 A
5754890 Holmdahl et al. May 1998 A
5764818 Capps et al. Jun 1998 A
5766493 Shin Jun 1998 A
5767457 Gerpheide et al. Jun 1998 A
5767842 Korth Jun 1998 A
5786804 Gordon Jul 1998 A
5786818 Brewer et al. Jul 1998 A
5790104 Shieh Aug 1998 A
5790107 Kasser et al. Aug 1998 A
5802516 Shwarts et al. Sep 1998 A
5808567 McCloud Sep 1998 A
5808602 Sellers Sep 1998 A
5809267 Moran et al. Sep 1998 A
5812114 Loop Sep 1998 A
5816225 Koch et al. Oct 1998 A
5821690 Martens et al. Oct 1998 A
5821930 Hansen Oct 1998 A
5823782 Marcus et al. Oct 1998 A
5825351 Tam Oct 1998 A
5825352 Bisset et al. Oct 1998 A
5825353 Will Oct 1998 A
5828364 Siddiqui Oct 1998 A
5835079 Shieh Nov 1998 A
5838304 Hall Nov 1998 A
5841425 Zenz, Sr. Nov 1998 A
5841426 Dodson et al. Nov 1998 A
D402281 Ledbetter et al. Dec 1998 S
5850213 Imai et al. Dec 1998 A
5854625 Frisch et al. Dec 1998 A
5856822 Du et al. Jan 1999 A
5880411 Gillespie et al. Mar 1999 A
5880715 Garrett Mar 1999 A
5883619 Hoe et al. Mar 1999 A
5886687 Gibson Mar 1999 A
5889236 Gillespie et al. Mar 1999 A
5898434 Small et al. Apr 1999 A
5900848 Haneda et al. May 1999 A
5903229 Kishi May 1999 A
5907152 Dändliker et al. May 1999 A
5907318 Medina May 1999 A
5909211 Combs et al. Jun 1999 A
5910799 Carpenter et al. Jun 1999 A
5914706 Kono Jun 1999 A
5920309 Bisset et al. Jul 1999 A
5923319 Bishop et al. Jul 1999 A
5931906 Fidelibus, Jr. et al. Aug 1999 A
5933134 Shieh Aug 1999 A
5943044 Martinelli et al. Aug 1999 A
5956019 Bang et al. Sep 1999 A
5959611 Smailagic et al. Sep 1999 A
5977869 Andreas Nov 1999 A
5977952 Francis Nov 1999 A
5982302 Ure Nov 1999 A
5991431 Borza et al. Nov 1999 A
5996080 Silva et al. Nov 1999 A
5999166 Rangan Dec 1999 A
6002389 Kasser et al. Dec 1999 A
6002808 Freeman Dec 1999 A
6005299 Hengst Dec 1999 A
6020881 Naughton et al. Feb 2000 A
6031518 Adams et al. Feb 2000 A
6031524 Kunert Feb 2000 A
6037882 Levy Mar 2000 A
6049328 Vanderheiden Apr 2000 A
6050825 Nichol et al. Apr 2000 A
6052339 Frenkel et al. Apr 2000 A
6064370 Wang et al. May 2000 A
6069648 Suso et al. May 2000 A
6072471 Lo Jun 2000 A
6072494 Nguyen Jun 2000 A
6075533 Chang Jun 2000 A
6084574 Bidiville Jul 2000 A
6084576 Leu et al. Jul 2000 A
6097372 Suzuki Aug 2000 A
6107997 Ure Aug 2000 A
6111563 Hines Aug 2000 A
6115028 Balakrishnan et al. Sep 2000 A
6124587 Bidiville et al. Sep 2000 A
6128003 Smith et al. Oct 2000 A
6128006 Rosenberg et al. Oct 2000 A
6130664 Suzuki Oct 2000 A
6131047 Hayes, Jr. et al. Oct 2000 A
6131299 Raab et al. Oct 2000 A
6135958 Mikula-Curtis et al. Oct 2000 A
6144380 Shwarts et al. Nov 2000 A
6163312 Furuya Dec 2000 A
6166721 Kuroiwa et al. Dec 2000 A
6179496 Chou Jan 2001 B1
6181322 Nanavati Jan 2001 B1
6188389 Yen Feb 2001 B1
6188391 Seely et al. Feb 2001 B1
6188393 Shu Feb 2001 B1
6191774 Schena et al. Feb 2001 B1
6198473 Armstrong Mar 2001 B1
6198515 Cole Mar 2001 B1
6208329 Ballare Mar 2001 B1
6211861 Rosenberg Apr 2001 B1
6219038 Cho Apr 2001 B1
6222465 Kumar et al. Apr 2001 B1
6222528 Gerpheide et al. Apr 2001 B1
D442592 Ledbetter et al. May 2001 S
6225976 Yates et al. May 2001 B1
6225980 Weiss et al. May 2001 B1
6226534 Aizawa May 2001 B1
6232957 Hinckley May 2001 B1
6239790 Martinelli et al. May 2001 B1
D443616 Fisher et al. Jun 2001 S
6243071 Shwarts et al. Jun 2001 B1
6243078 Rosenberg Jun 2001 B1
6246862 Grivas et al. Jun 2001 B1
6249606 Kiraly et al. Jun 2001 B1
6256011 Culver Jul 2001 B1
6262717 Donohue et al. Jul 2001 B1
6266050 Oh et al. Jul 2001 B1
6288707 Philipp Sep 2001 B1
6289326 LaFleur Sep 2001 B1
6292178 Bernstein et al. Sep 2001 B1
6297795 Kato et al. Oct 2001 B1
6297811 Kent et al. Oct 2001 B1
6310610 Beaton et al. Oct 2001 B1
6323843 Giles et al. Nov 2001 B2
6323845 Robbins Nov 2001 B1
6323846 Westerman et al. Nov 2001 B1
6327011 Kim Dec 2001 B2
6333734 Rein Dec 2001 B1
6337919 Dunton Jan 2002 B1
6340800 Zhai et al. Jan 2002 B1
6347290 Bartlett Feb 2002 B1
D454568 Andre et al. Mar 2002 S
6356287 Ruberry et al. Mar 2002 B1
6356524 Aratani Mar 2002 B2
6362811 Edwards et al. Mar 2002 B1
6369797 Maynard Apr 2002 B1
6373470 Andre et al. Apr 2002 B1
6377009 Philipp Apr 2002 B1
6377530 Burrows Apr 2002 B1
6380931 Gillespie et al. Apr 2002 B1
6384743 Vanderheiden May 2002 B1
6392632 Lee May 2002 B1
6392634 Bowers et al. May 2002 B1
6392636 Ferrari et al. May 2002 B1
6411287 Scharff et al. Jun 2002 B1
6413233 Sites et al. Jul 2002 B1
6414671 Gillespie et al. Jul 2002 B1
6421234 Ricks et al. Jul 2002 B1
6433780 Gordon et al. Aug 2002 B1
6452514 Philipp Sep 2002 B1
6457355 Philipp Oct 2002 B1
6466036 Philipp Oct 2002 B1
6466203 Van Ee Oct 2002 B2
6469693 Chiang et al. Oct 2002 B1
6489947 Hesley et al. Dec 2002 B2
6492979 Kent et al. Dec 2002 B1
6504530 Wilson et al. Jan 2003 B1
6505088 Simkin et al. Jan 2003 B1
6513717 Hannigan Feb 2003 B2
6515669 Mohri Feb 2003 B1
6525749 Moran et al. Feb 2003 B1
6535200 Philipp Mar 2003 B2
6543684 White et al. Apr 2003 B1
6543947 Lee Apr 2003 B2
6545665 Rodgers Apr 2003 B2
6559830 Hinckley et al. May 2003 B1
6559831 Armstrong May 2003 B1
6567073 Levin May 2003 B1
6570557 Westerman et al. May 2003 B1
6587091 Serpa Jul 2003 B2
6587093 Shaw et al. Jul 2003 B1
6593916 Aroyan Jul 2003 B1
6597347 Yasutake Jul 2003 B1
6597384 Harrison Jul 2003 B1
6610936 Gillespie et al. Aug 2003 B2
6614422 Rafii et al. Sep 2003 B1
6624803 Vanderheiden et al. Sep 2003 B1
6624833 Kumar et al. Sep 2003 B1
6636197 Goldenberg et al. Oct 2003 B1
6639577 Eberhard Oct 2003 B2
6639584 Li Oct 2003 B1
6650319 Hurst et al. Nov 2003 B1
6650975 Ruffner Nov 2003 B2
6658994 McMillan Dec 2003 B1
6661410 Casebolt et al. Dec 2003 B2
6670894 Mehring Dec 2003 B2
6677927 Bruck et al. Jan 2004 B1
6677932 Westerman Jan 2004 B1
6677934 Blanchard Jan 2004 B1
6686904 Sherman et al. Feb 2004 B1
6690387 Zimmerman et al. Feb 2004 B2
6700564 McLoone Mar 2004 B2
6703550 Chu Mar 2004 B2
6703599 Casebolt et al. Mar 2004 B1
6707027 Liess et al. Mar 2004 B2
6717569 Gruhl et al. Apr 2004 B1
6724366 Crawford Apr 2004 B2
6724817 Simpson et al. Apr 2004 B1
6727889 Shaw Apr 2004 B2
6738045 Hinckley et al. May 2004 B2
6740860 Kobayashi May 2004 B2
6757002 Oross et al. Jun 2004 B1
D493157 Yang Jul 2004 S
D493158 Yang Jul 2004 S
6762751 Kuan Jul 2004 B2
6788288 Ano Sep 2004 B2
6791533 Su Sep 2004 B2
6795056 Norskog et al. Sep 2004 B2
6795057 Gordon Sep 2004 B2
D497606 Yang Oct 2004 S
6803906 Morrison et al. Oct 2004 B1
6816149 Alsleben Nov 2004 B1
6816150 Casebolt et al. Nov 2004 B2
D500298 Yang Dec 2004 S
6828958 Davenport Dec 2004 B2
6833825 Farag et al. Dec 2004 B1
6834195 Brandenberg et al. Dec 2004 B2
6842672 Straub et al. Jan 2005 B1
6844871 Hinckley et al. Jan 2005 B1
6844872 Farag et al. Jan 2005 B1
6847352 Lantigua Jan 2005 B2
6848014 Landron et al. Jan 2005 B2
6853850 Shim et al. Feb 2005 B2
6856259 Sharp Feb 2005 B1
6865718 Levi Mar 2005 B2
6873715 Kuo et al. Mar 2005 B2
6888532 Wong et al. May 2005 B2
6888536 Westerman et al. May 2005 B2
6900795 Knight, III et al. May 2005 B1
6909424 Liebenow et al. Jun 2005 B2
6924789 Bick Aug 2005 B2
6927761 Badaye et al. Aug 2005 B2
D509819 Yang Sep 2005 S
D509833 Yang Sep 2005 S
D510081 Yang Sep 2005 S
6942571 McAllister et al. Sep 2005 B1
6943779 Satoh Sep 2005 B2
6950094 Gordon et al. Sep 2005 B2
D511512 Yang Nov 2005 S
D511528 Yang Nov 2005 S
6965375 Gettemy et al. Nov 2005 B1
D512403 Yang Dec 2005 S
D512435 Yang Dec 2005 S
6972401 Akitt et al. Dec 2005 B2
6977666 Hedrick Dec 2005 B1
6985801 Straub et al. Jan 2006 B1
6992656 Hughes Jan 2006 B2
6995744 Moore et al. Feb 2006 B1
7013228 Ritt Mar 2006 B2
7015894 Morohoshi Mar 2006 B2
7031228 Born et al. Apr 2006 B2
7034802 Gettemy et al. Apr 2006 B1
D520516 Yang May 2006 S
7046230 Zadesky et al. May 2006 B2
7051291 Sciammarella et al. May 2006 B2
7068256 Gettemy et al. Jun 2006 B1
7109978 Gillespie et al. Sep 2006 B2
7113196 Kerr Sep 2006 B2
7119792 Andre et al. Oct 2006 B1
7129416 Steinfeld et al. Oct 2006 B1
7142193 Hayama Nov 2006 B2
7145552 Hollingsworth Dec 2006 B2
7164412 Kao Jan 2007 B2
7168047 Huppi Jan 2007 B1
7170488 Kehlstadt et al. Jan 2007 B2
7170496 Middleton Jan 2007 B2
7183948 Roberts Feb 2007 B2
7184064 Zimmerman et al. Feb 2007 B2
7233318 Farag Jun 2007 B1
7236159 Siversson Jun 2007 B1
7239800 Bilbrey Jul 2007 B2
7240289 Naughton Jul 2007 B2
7312981 Carroll Dec 2007 B2
RE40153 Westerman et al. Mar 2008 E
7366995 Montague Apr 2008 B2
7388578 Tao Jun 2008 B2
7423636 Sano et al. Sep 2008 B2
7452098 Kerr Nov 2008 B2
7453439 Kushler et al. Nov 2008 B1
7495659 Marriot Feb 2009 B2
7499038 Nishikawa et al. Mar 2009 B2
7499040 Zadesky Mar 2009 B2
7505785 Callaghan et al. Mar 2009 B2
D592665 Andre et al. May 2009 S
7629961 Casebolt et al. Dec 2009 B2
7652589 Autor Jan 2010 B2
7663607 Hotelling et al. Feb 2010 B2
7683889 Rimas Ribikauskas Mar 2010 B2
7800592 Kerr et al. Sep 2010 B2
7808479 Hotelling et al. Oct 2010 B1
8479122 Hotelling et al. Jul 2013 B2
8537115 Hotelling et al. Sep 2013 B2
8665209 Rimas-Ribikauskas Mar 2014 B2
8704769 Hotelling et al. Apr 2014 B2
8704770 Hotelling et al. Apr 2014 B2
9047009 King et al. Jun 2015 B2
9335868 Hotelling et al. May 2016 B2
20010011991 Wang et al. Aug 2001 A1
20010011995 Hinckley et al. Aug 2001 A1
20010043189 Brisebois et al. Nov 2001 A1
20010043545 Aratani Nov 2001 A1
20010050673 Davenport Dec 2001 A1
20010051046 Watanabe et al. Dec 2001 A1
20020008691 Hanajima et al. Jan 2002 A1
20020015024 Westerman et al. Feb 2002 A1
20020033848 Sciammarella et al. Mar 2002 A1
20020063688 Shaw et al. May 2002 A1
20020084986 Armstrong Jul 2002 A1
20020089545 Levi Jul 2002 A1
20020093487 Rosenberg Jul 2002 A1
20020093492 Baron Jul 2002 A1
20020118169 Hinckley et al. Aug 2002 A1
20020118174 Rodgers Aug 2002 A1
20020118848 Karpenstein Aug 2002 A1
20020130839 Wallace et al. Sep 2002 A1
20020130841 Scott Sep 2002 A1
20020140676 Kao Oct 2002 A1
20020154090 Lin Oct 2002 A1
20020158838 Smith et al. Oct 2002 A1
20020164156 Bilbrey Nov 2002 A1
20030006974 Clough et al. Jan 2003 A1
20030011574 Goodman Jan 2003 A1
20030025735 Polgar et al. Feb 2003 A1
20030043121 Chen Mar 2003 A1
20030043174 Hinckley et al. Mar 2003 A1
20030050092 Yun Mar 2003 A1
20030063072 Brandenberg et al. Apr 2003 A1
20030074977 Doemens et al. Apr 2003 A1
20030076301 Tsuk et al. Apr 2003 A1
20030076303 Huppi Apr 2003 A1
20030076306 Zadesky et al. Apr 2003 A1
20030085870 Hinckley May 2003 A1
20030085882 Lu May 2003 A1
20030095095 Pihlaja May 2003 A1
20030095096 Robbin et al. May 2003 A1
20030098851 Brink May 2003 A1
20030098858 Perski et al. May 2003 A1
20030107551 Dunker Jun 2003 A1
20030107552 Lu Jun 2003 A1
20030142855 Kuo et al. Jul 2003 A1
20030179223 Ying et al. Sep 2003 A1
20030184517 Senzui et al. Oct 2003 A1
20030184520 Wei Oct 2003 A1
20030206202 Moriya Nov 2003 A1
20030210286 Gerpheide et al. Nov 2003 A1
20030222848 Solomon et al. Dec 2003 A1
20030234768 Rekimoto et al. Dec 2003 A1
20040003947 Kesselman et al. Jan 2004 A1
20040012572 Sowden et al. Jan 2004 A1
20040021643 Hoshino et al. Feb 2004 A1
20040046741 Low et al. Mar 2004 A1
20040125086 Hagermoser et al. Jul 2004 A1
20040156192 Kerr Aug 2004 A1
20040212586 Denny, III Oct 2004 A1
20040239622 Proctor et al. Dec 2004 A1
20040242269 Fadell Dec 2004 A1
20040242295 Ghaly Dec 2004 A1
20040246231 Large Dec 2004 A1
20040252109 Trent et al. Dec 2004 A1
20040263483 Aufderheide Dec 2004 A1
20040263484 Mantysalo et al. Dec 2004 A1
20050012723 Pallakoff Jan 2005 A1
20050030278 Fu Feb 2005 A1
20050035955 Carter et al. Feb 2005 A1
20050043060 Brandenberg et al. Feb 2005 A1
20050052425 Zadesky et al. Mar 2005 A1
20050068322 Falcioni Mar 2005 A1
20050084138 Inkster et al. Apr 2005 A1
20050104867 Westerman et al. May 2005 A1
20050110768 Marriott et al. May 2005 A1
20050115816 Gelfond et al. Jun 2005 A1
20050135053 Carroll Jun 2005 A1
20050146509 Geaghan et al. Jul 2005 A1
20050146513 Hill et al. Jul 2005 A1
20050154798 Nurmi Jul 2005 A1
20050168488 Montague Aug 2005 A1
20050183035 Ringel et al. Aug 2005 A1
20050190158 Casebolt et al. Sep 2005 A1
20050212760 Marvit et al. Sep 2005 A1
20050219228 Alameh Oct 2005 A1
20050228320 Klinghult Oct 2005 A1
20050253818 Nettamo Nov 2005 A1
20050259077 Adams Nov 2005 A1
20050275637 Hinckley et al. Dec 2005 A1
20060010400 Dehlin et al. Jan 2006 A1
20060022955 Kennedy Feb 2006 A1
20060022956 Lengeling et al. Feb 2006 A1
20060026521 Hotelling et al. Feb 2006 A1
20060026535 Hotelling et al. Feb 2006 A1
20060026536 Hotelling et al. Feb 2006 A1
20060032680 Elias et al. Feb 2006 A1
20060033724 Chaudhri et al. Feb 2006 A1
20060044259 Hotelling et al. Mar 2006 A1
20060050011 Kamio Mar 2006 A1
20060053387 Ording Mar 2006 A1
20060066582 Lyon et al. Mar 2006 A1
20060073272 Carel Apr 2006 A1
20060079969 Seguin Apr 2006 A1
20060085757 Andre et al. Apr 2006 A1
20060097991 Hotelling et al. May 2006 A1
20060109252 Kolmykov-Zotov et al. May 2006 A1
20060109256 Grant et al. May 2006 A1
20060181517 Zadesky et al. Aug 2006 A1
20060181518 Shen et al. Aug 2006 A1
20060183505 Willrich Aug 2006 A1
20060197750 Kerr et al. Sep 2006 A1
20060197753 Hotelling Sep 2006 A1
20060232567 Westerman et al. Oct 2006 A1
20060238517 King et al. Oct 2006 A1
20060238518 Westerman et al. Oct 2006 A1
20060238519 Westerman et al. Oct 2006 A1
20060238520 Westerman et al. Oct 2006 A1
20060238521 Westerman et al. Oct 2006 A1
20060238522 Westerman et al. Oct 2006 A1
20060244733 Geaghan Nov 2006 A1
20060267953 Peterson et al. Nov 2006 A1
20060284855 Shintome Dec 2006 A1
20070046646 Kwon et al. Mar 2007 A1
20070063923 Koenig Mar 2007 A1
20070075968 Hall et al. Apr 2007 A1
20070136064 Carroll Jun 2007 A1
20070229464 Hotelling et al. Oct 2007 A1
20070236466 Hotelling Oct 2007 A1
20070247429 Westerman Oct 2007 A1
20070257890 Hotelling et al. Nov 2007 A1
20080012835 Rimon et al. Jan 2008 A1
20080012838 Rimon Jan 2008 A1
20080088602 Hotelling Apr 2008 A1
20080158172 Hotelling et al. Jul 2008 A1
20080211772 Loucks Sep 2008 A1
20080238879 Jaeger et al. Oct 2008 A1
20080266257 Chiang Oct 2008 A1
20080278450 Lashina Nov 2008 A1
20080297476 Hotelling et al. Dec 2008 A1
20080297477 Hotelling et al. Dec 2008 A1
20090066670 Hotelling et al. Mar 2009 A1
20090085894 Gandhi et al. Apr 2009 A1
20090096757 Hotelling et al. Apr 2009 A1
20090096758 Hotelling et al. Apr 2009 A1
20090295738 Chiang Dec 2009 A1
20100164878 Bestle et al. Jul 2010 A1
20110012835 Hotelling et al. Jan 2011 A1
20150153895 Hotelling Jun 2015 A1
20150261362 King et al. Sep 2015 A1
20160070399 Hotelling Mar 2016 A1
Foreign Referenced Citations (102)
Number Date Country
1243096 Oct 1988 CA
1173672 Feb 1998 CN
1343330 Apr 2002 CN
1397870 Feb 2003 CN
1588432 Mar 2005 CN
1720499 Jan 2006 CN
1737827 Feb 2006 CN
1942853 Apr 2007 CN
4125049 Jan 1992 DE
19722636 Dec 1998 DE
10022537 Nov 2000 DE
10201193 Jul 2003 DE
102 51 296 May 2004 DE
0 288 692 Nov 1988 EP
0 464 908 Jan 1992 EP
0 498 540 Jan 1992 EP
0653725 May 1995 EP
0 664 504 Jul 1995 EP
0768619 Apr 1997 EP
0795837 Sep 1997 EP
0 880 Q91 Nov 1998 EP
1 026 713 Aug 2000 EP
1 014 295 Jan 2002 EP
1 241 557 Sep 2002 EP
1 505 484 Feb 2005 EP
0 899 650 Jun 2011 EP
2 380 583 Apr 2003 GB
2 393 688 Jan 2006 GB
63-257824 Oct 1988 JP
63-292774 Nov 1988 JP
03237520 Oct 1991 JP
07-064725 Mar 1995 JP
07-182101 Jul 1995 JP
07-319001 Dec 1995 JP
08-161138 Jun 1996 JP
08-211992 Aug 1996 JP
09-006525 Jan 1997 JP
09-244810 Sep 1997 JP
09-305262 Nov 1997 JP
63106826 May 1998 JP
10-228350 Aug 1998 JP
10326149 Dec 1998 JP
11-143606 May 1999 JP
11-194863 Jul 1999 JP
11-194872 Jul 1999 JP
11-194883 Jul 1999 JP
11-215217 Aug 1999 JP
2000-163031 Jun 2000 JP
2000-215549 Aug 2000 JP
2000-242428 Sep 2000 JP
2000242424 Sep 2000 JP
2000-330946 Nov 2000 JP
2001-051790 Feb 2001 JP
2001-356878 Dec 2001 JP
2002-501271 Jan 2002 JP
2002-062972 Feb 2002 JP
2002-185630 Jun 2002 JP
2002-229719 Aug 2002 JP
EP 1241558 Sep 2002 JP
2002-342033 Nov 2002 JP
2002-342034 Nov 2002 JP
2003-058316 Feb 2003 JP
2003280807 Feb 2003 JP
2003-122506 Apr 2003 JP
2003-241872 Aug 2003 JP
2003-271309 Sep 2003 JP
2003-330611 Nov 2003 JP
2004-021933 Jan 2004 JP
2004-070920 Mar 2004 JP
2004-226715 Aug 2004 JP
2004-527847 Sep 2004 JP
2004-340991 Dec 2004 JP
2005-006259 Jan 2005 JP
2001-0047975 Jun 2001 KR
431607 Apr 2001 TW
WO 9005972 May 1990 WO
WO-9210823 Jun 1992 WO
WO 9417494 Aug 1994 WO
WO-9718547 May 1997 WO
WO-9723738 Jul 1997 WO
WO 9814863 Apr 1998 WO
WO 9926330 May 1999 WO
WO-9938149 Jul 1999 WO
WO 9949443 Sep 1999 WO
WO 0039907 Jul 2000 WO
WO-0235461 May 2002 WO
WO 02052494 Jul 2002 WO
WO-03001576 Jan 2003 WO
WO-03001576 Jan 2003 WO
WO-03065192 Aug 2003 WO
WO 03077110 Sep 2003 WO
WO-03088176 Oct 2003 WO
WO-2004111816 Dec 2004 WO
WO-2004111816 Dec 2004 WO
WO-2006023569 Mar 2006 WO
WO-2006094308 Sep 2006 WO
WO-2006094308 Sep 2006 WO
WO-2006096501 Sep 2006 WO
WO 2006132817 Dec 2006 WO
WO-2007103631 Sep 2007 WO
WO-2007103631 Sep 2007 WO
WO-2010014560 Feb 2010 WO
Non-Patent Literature Citations (185)
Entry
Non-Final Office Action mailed Dec. 28, 2010, for U.S. Appl. No. 12/890,437, filed Sep. 24, 2010, 16 pages.
Final Office Action mailed Feb. 2, 2007, for U.S. Appl. No. 10/654,108, filed Sep. 2, 2003, 16 pages.
Final Office Action mailed Nov. 16, 2007, for U.S. Appl. No. 10/654,108, filed Sep. 2, 2003, 12 pages.
Final Office Action mailed Feb. 18, 2009, for U.S. Appl. No. 10/654,108, filed Sep. 2, 2003, 12 pages.
Non-Final Office Action mailed Jun. 16, 2006, for U.S. Appl. No. 10/654,108, filed Sep. 2, 2003, 7 pages.
Non-Final Office Action mailed Jul. 6, 2007, for U.S. Appl. No. 10/654,108, filed Sep. 2, 2003, 13 pages.
Non-Final Office Action mailed Oct. 28, 2008, for U.S. Appl. No. 10/654,108, filed Sep. 2, 2003, 10 pages.
“About Quicktip®” www.logicad3d.com/docs/qt.html, downloaded Apr. 8, 2002.
“OEM Touchpad Modules” website www.glidepoint.com/sales/modules.index.shtml, downloaded Feb. 13, 2002.
“Product Overview—ErgoCommander®”, www.logicad3d.com/products/ErgoCommander.htm, downloaded Apr. 8, 2002.
“Product Overview—SpaceMouse® Classic”, www.logicad3d.com/products/Classic.htm, downloaded Apr. 8, 2002.
Sylvania, “Intellivision™ Intelligent Television Master Component Service Manual,” pp. 1, 2 and 8, 1979.
Gadgetboy, “Point and click with the latest mice”, CNETAsia Product Review, www.asia.cnet.com/reviews...are/gadgetboy/0,39001770,38023590,00.htm, downloaded Dec. 5, 2001.
Tessler et al. “Touchpads Three new input devices”, website www.macworld.com/1996/02/review/1806.html, download Feb. 13, 2002.
“Synaptics Tough Pad Interfacing Guide” Second Edition, Mar. 25, 1998, Synaptics, Inc. San Jose, CA, pp. 1 to 90.
Fiore, Andrew, “Zen Touchpad”, Cornell University, May 2000.
Flaminio, Michael, “IntelliMouse Explorer”, IGM Review, Oct. 4, 1999.
Grevstad, Eric, “Microsoft Wireless IntelliMouse Explorer Review the Ultimate Pointing Machine”, HardwareCentral Review, Jun. 24, 2003.
Grevstad, Eric, “Microsoft Wireless IntelliMouse Explorer Review the Ultimate Pointing Machine”, HardwareCentral Review, Oct. 9, 2001.
Dreier, Troy, “The Comfort Zone”, PC Magazine, Mar. 12, 2002.
Apple Computer, Inc., “Apple Pro Mouse,” Jul. 2000, Apple Pro Mouse Design Innovations product specification, pp. 1-11.
David Nagel, “More Details on the New Pro Keyboard and ButtonLess Mouse,” Jul. 2000, http://www.creativemac.com/HTM/News/07—00/detailskeyboardmouse,htm pp. 1-2.
John Siracusa, “MacWorld Expo NY 2000,” Jul. 2000, http://www.arstechnic.com/wanderdesk/3q00/macworld2k/mwny-2.html pp. 1-6.
Microsoft Inc., “Scroll and zoom on a Microsoft Excel sheet by using the Microsoft Intellimouse pointing device” 1999, pp. 1-3.
“System Service and Troubleshooting Manual”, www.dsplib.com/intv/Master, downloaded Dec. 11, 2002.
“Der Klangmeister,” Connect Magazine, Aug. 1998.
Bang & Olufsen Telecom a/s, “BeoCom 6000 User Guide 2000”.
BeoCom 6000, Sales Training Brochure, date unknown.
Chapweske, Adam, “PS/2 Mouse/Keyboard Protocol”, 1999, http://panda.cs.ndsu.nodak.edu/˜achapwes/PICmicro/PS2/ps2.htm.
De Meyer, Kevin, Crystal Optical Mouse, Feb. 14, 2002, Heatseekerz, Web Article 19.
Ken Hinckley et al. “Touch-Sensing Input Devices” CHI 1999 pp. 223-230.
Letter re: Bang & Olufsen A/S, by David Safran, Nixon Peabody, LLP, May 21, 2004.
Photographs of Innovations 2000 Best of Show award presented at the 2000 International CES Innovations 2000 Design & Engineering Showcase, 1 pg.
International Search Report from related application No. PCT/US2006/020341 dated Jun. 12, 2007.
EPO Form 1507 in related EP Application No. 02761784.4 dated Nov. 19, 2004.
“Neuros MP3 Digital Audio Computer”, www.neurosaudio.com, downloaded Apr. 9, 2003.
“Apple Unveils Optical Mouse and New Pro Keyboard,” Press Release, Jul. 19, 2000.
U.S. Appl. No. 29/231,465, filed Jun. 3, 2005.
U.S. Appl. No. 60/364,400, filed Mar. 13, 2002.
“Logitech's MX Air is No Longer Vapor,” Gizmodo Australia, retrieved from http://www.gizmodo.com.au/2007/07/logitechs—mx—air—is—no—longer.html on Jan. 11, 2008.
Final Office Action mailed Jan. 19, 2010, for U.S. Appl. No. 10/654,108, filed Sep. 2, 2003, 16 pages.
Lee, S.K. et al. (Apr. 1985). “A Multi-Touch Three Dimensional Touch-Sensitive Tablet,” Proceedings of CHI: ACM Conference on Human Factors in Computing Systems, pp. 21-25.
Non-Final Office Action mailed Jul. 14, 2009, for U.S. Appl. No. 10/654,108, filed Sep. 2, 2003, 16 pages.
Notice of Allowance mailed Jun. 1, 2010, for U.S. Appl. No. 10/654,108, filed Sep. 2, 2003, six pages.
Rubine, D.H. (Dec. 1991). “The Automatic Recognition of Gestures,” CMU-CS-91-202, Submitted in Partial Fulfillment of the Requirements of the Degree of Doctor of Philosophy in Computer Science at Carnegie Mellon University, 285 pages.
Rubine, D.H. (May 1992). “Combining Gestures and Direct Manipulation,” CHI ' 92, pp. 659-660.
Westerman, W. (Spring 1999). “Hand Tracking, Finger Identification, and Chordic Manipulation on a Multi-Touch Surface,” A Dissertation Submitted to the Faculty of the University of Delaware in Partial Fulfillment of the Requirements for the Degree of Doctor of Philosophy in Electrical Engineering, 364 pages.
Final Office Action mailed Apr. 19, 2011, for U.S. Appl. No. 12/890,437, filed Sep. 24, 2010, 19 pages.
Non-Final Office Action mailed May 6, 2011, for U.S. Appl. No. 12/188,948, filed Aug. 8, 2008, 10 pages.
Non-Final Office Action mailed May 16, 2011, for U.S. Appl. No. 12/188,988, filed Aug. 8, 2008, 14 pages.
Final Office Action mailed Dec. 7, 2011, for U.S. Appl. No. 12/188,948, filed Aug. 8, 2008, 13 pages.
Final Office Action mailed Dec. 8, 2011, for U.S. Appl. No. 12/188,988, filed Aug. 8, 2008, 15 pages.
Chinese Search Report mailed Sep. 27, 2016, for CN Application No. 201410259240.3, with English Translation, four pages.
Final Office Action mailed Feb. 4, 2016, for U.S. Appl. No. 14/535,101, filed Nov. 6, 2014, seven pages.
Final Office Action mailed Aug. 23, 2016, for U.S. Appl. No. 14/940,010, filed Nov. 12, 2015, 11 pages.
Final Office Action mailed Nov. 25, 2016, for U.S. Appl. No. 14/724,753, filed May 28, 2015, sixteen pages.
Non-Final Office Action mailed May 12, 2015, for U.S. Appl. No. 14/535,101, filed Nov. 6, 2014, seven pages.
Non-Final Office Action mailed Aug. 11, 2016, for U.S. Appl. No. 14/535,101, filed Nov. 6, 2014, eight pages.
Non-Final Office Action mailed Nov. 10, 2016, for U.S. Appl. No. 11/367,749, filed Mar. 3, 2006, ten pages.
Anonymous. “Touch Technologies Overview” 2001, 3M Touch Systems, Massachusetts.
Anonymous. (Apr. 13, 2004). Proximity Sensor Demo Kit, User Guide, Version 0.62—Preliminary, Integration Associates, Inc., 14 pages.
Anonymous. “4-Wire Resistive Touchscreens” obtained from http://www.touchscreens.com/intro-touchtypes-4resistive.html generated Aug. 5, 2005.
Anonymous. “5-Wire Resistive Touchscreens” obtained from http://www.touchscreens.com/intro-touchtypes-resistive.html generated Aug. 5, 2005.
Anonymous. “A Brief Overview of Gesture Recognition” obtained from http://www. Dai. Ed. Ac.uk/Cvonline/LOCA—COPIES/COHEN/gesture— overview. Html, generated Apr. 20, 2004.
Anonymous. “Capacitive Position Sensing” obtained from http://www.synaptics.com/technology/cps.cfin generated Aug. 5, 2005.
Anonymous. “Capacitive Touchscreens” obtained from http://www.touchscreens.com/intro- touchtypes-capacitive.html generated Aug. 5, 2005.
Anonymous. “Comparing Touch Technologies” obtained from http://www.touchscreens.com/intro-touchtypes.html generated Oct. 10, 2004.
Anonymous. “FingerWorks—Gesture Guide—Application Switching,” obtained from http://www.fingerworks.com/gesture—guide—apps.html, generated on Aug. 27, 2004, 1-pg.
Anonymous. “FingerWorks—Gesture Guide—Editing,” obtained from http://www.fingerworks.com/gesure—guide—editing.html, generated on Aug. 27, 2004, 1-pg.
Anonymous. “FingerWorks—Gesture Guide—File Operations,” obtained from http://www.fingerworks.com/gesture—guide—files.html, generated on Aug. 27, 2004, 1-pg.
Anonymous. “FingerWorks—Gesture Guide—Text Manipulation,” obtained from http://www.fingerworks.com/gesture—guide—text—manip.html, generated on Aug. 27, 2004, 2-pg.
Anonymous. “FingerWorks—Gesture Guide—Tips and Tricks,” obtained from http://www.fingerworks.com/gesture—guide—tips.html, generated Aug. 27, 2004, 2-pgs.
Anonymous. “FingerWorks—Gesture Guide—Web,” obtained from http://www.fingerworks.com/gesture—guide—web.html, generated on Aug. 27, 2004, 1-pg.
Anonymous. “FingerWorks—Guide to Hand Gestures for USB Touchpads,” obtained from http://www.fingerworks.com/igesture—userguide.html, generated Aug. 27, 2004, 1-pg.
Anonymous. “FingerWorks—iGesture—Technical Details,” obtained from http://www.fingerworks.com/igesture—tech.html, generated Aug. 27, 2004, 1-pg.
Anonymous. “FingerWorks—The Only Touchpads with Ergonomic Full-Hand Resting and Relaxation!” obtained from http://www.fingerworks.com/resting.html, Copyright 2001, 1-pg.
Anonymous. “FingerWorks—Tips for Typing on the Mini,” obtained from http://www.fingerworks.com/mini—typing.html, generated on Aug. 27, 2004, 2-pgs.
Anonymous. “Gesture Recognition” http://www.fingerworks.com/gesture—recognition.htm1>, Jul. 2, 2006.
Anonymous. “GlidePoint®” obtained from http://www.cirque.com/technology/technology—gp.html generated Aug. 5, 2005.
Anonymous. “How do touchscreen monitors know where you're touching?” obtained from http://www.electronics.howstuffworks.com/question716.html generated Aug. 5, 2005.
Anonymous. “How does a touchscreen work?” obtained from http://www.touchscreens.com/intro-anatomy.html generated Aug. 5, 2005.
Anonymous. “iGesture Pad—the MultiFinger USB TouchPad with Whole-Hand Gestures,” obtained from http://www.fingerworks.com/igesture.html, generated Aug. 27, 2004, 2-pgs.
Anonymous. “iGesture Products for Everyone (learn in minutes) Product Overview” FingerWorks.com downloaded Aug. 30, 2005.
Anonymous. “Infrared Touchscreens” obtained from http://www.touchscreens.com/intro-touchtypes-infrared.html generated Aug. 5, 2005.
Anonymous. “Mouse Emulation” FingerWorks obtained from http://www.fingerworks.com/gesture—guide—mouse.html generated Aug. 30, 2005.
Anonymous. “Mouse Gestures in Opera” obtained from http://www.opera.com/products/desktop/mouse/index.dml generated Aug. 30, 2005.
Anonymous. “Mouse Gestures,” Optim oz, May 21, 2004.
Anonymous. “MultiTouch Overview” FingerWorks obtained from http://www.fingerworks.com/multoverview.html generated Aug. 30, 2005.
Anonymous. “Near Field Imaging Touchscreens” obtained from http://www.touchscreens.com/intro-touchtypes-nfi.html generated Aug. 5, 2005.
Anonymous. “PenTouch Capacitive Touchscreens” obtained from http://www.touchscreens.com/intro-touchtypes-pentouch.html generated Aug. 5, 2005.
Anonymous. “Surface Acoustic Wave Touchscreens” obtained from http://www.touchscreens.com/intro-touchtypes-saw.html generated Aug. 5, 2005.
Anonymous. “Symbol Commander” obtained from http://www.sensiva.com/symbolcommander/, generated Aug. 30, 2005.
Anonymous. “Wacom Components—Technology” obtained from http://www.wacom-components.com/english/tech.asp generated on Oct. 10, 2004.
Anonymous. “Watershed Algorithm” http://rsb.info.nih.gov/ij/plugins/watershed.html generated Aug. 5, 2005.
Bier et al., “Toolglass and Magic Lenses: The see-through interface” In James Kijiya, editor, Computer Graphics (SIGGRAPH '93 Proceedings), vol. 27, pp. 73-80, Aug. 1993.
Chinese Search Report mailed Jan. 14, 2016, for CN Application No. 201310264394.7, with English Translation, four pages.
Douglas et al., The Ergonomics of Computer Pointing Devices (1997).
European Search Report received in EP 1 621 989 (@ Beyer Weaver & Thomas, LLP) dated Mar. 27, 2006.
European Examination Report mailed Apr. 21, 2008, for EP Application No. 06737515.4, filed Mar. 3, 2006, five pages.
European Search Report mailed Nov. 9, 2010, for EP Application No. 10010075.9, filed Mar. 3, 2006, six pages.
European Search Report mailed Nov. 7, 2013, for EP Application No. 09170572.3, eight pages.
European Search Report mailed Jul. 7, 2014, for EP Application No. 14169441.4, three pages. (93.75).
EVB Elektronik “TSOP6238 IR Receiver Modules for Infrared Remote Control Systems” dated Jan. 2004 1-pg.
Final Office Action mailed Nov. 21, 2008, for U.S. Appl. No. 11/115,539, filed Apr. 26, 2005, 23 pages.
Final Office Action mailed Aug. 25, 2009, for U.S. Appl. No. 11/367,749, filed Mar. 3, 2006, 12 pages.
Final Office Action mailed Oct. 14, 2009, for U.S. Appl. No. 11/115,539, filed Apr. 26, 2005, 10 pages.
Final Office Action mailed Jun. 30, 2010, for U.S. Appl. No. 11/367,749, filed Mar. 3, 2006, 10 pages.
Final Office Action mailed Jul. 1, 2011, for U.S. Appl. No. 12/486,710, filed Jun. 17, 2009, 19 pages.
Final Office Action mailed Jul. 13, 2011, for U.S. Appl. No. 11/966,948, filed Dec. 28, 2007, 10 pages.
Final Office Action mailed Sep. 4, 2012, for U.S. Appl. No. 12/486,710, filed Jun. 17, 2009, 25 pages.
Final Office Action mailed Nov. 8, 2012, for U.S. Appl. No. 12/184,190, filed Jul. 31, 2008, 20 pages.
Final Office Action mailed Jan. 2, 2014, for U.S. Appl. No. 12/486,710, filed Jun. 17, 2009, 30 pages.
Final Office Action mailed Jan. 17, 2014, for U.S. Appl. No. 11/367,749, filed Mar. 3, 2006, 12 pages.
Final Office Action mailed Oct. 9, 2014, for U.S. Appl. No. 11/966,948, filed Dec. 28, 2007, 11 pages.
Final Office Action mailed Aug. 3, 2015, for U.S. Appl. No. 14/595,032, filed Jan. 12, 2105, nine pages.
Final Office Action mailed Jan. 8, 2016, for U.S. Appl. No. 11/367,749, filed Mar. 3, 2006, 10 pages.
Final Office Action mailed Mar. 10, 2016, for U.S. Appl. No. 11/966,948, filed Dec. 28, 2007, 14 pages.
Fisher et al., “Repetitive Motion Disorders: The Design of Optimal Rate—Rest Profiles,” Human Factors, 35(2):283-304 (Jun. 1993).
Fukumoto and Yoshinobu Tonomura, “Body Coupled Fingering: Wireless Wearable Keyboard,” CHI97, pp. 147-154 (Mar. 1997).
Fukumoto et al., “ActiveClick: Tactile Feedback for Touch Panels,” In CHI 2001 Summary, pp. 121-122, 2001.
Gear Live Review: iRiver clix Review, obrained from http://www.gearlive.com/index.php/news/article/gear-live-review-iriver-clix-review-713400/, dated Jul. 13, 2006, 8 pages.
Hardy, “Fingerworks” Mar. 7, 2002; BBC World on Line.
Hillier and Gerald J. Lieberman, Introduction to Operations Research (1986).
Hinckley et al., “Touch-Sensing Input Devices,” in CHI '99 Proceedings, pp. 223-230, 1999. (“Kinkley” by previous counsel.).
International Search Report dated Mar. 3, 2006 (PCT/US 05/03325).
International Search Report dated Jul. 25, 2006, from corresponding International Application No. PCT/US2006/007585 with Written Opinion, nine pages.
International Search Report mailed Oct. 6, 2006, for PCT Application No. PCT/US2006/08349, filed Mar. 3, 2006, three pages.
International Search Report mailed Jan. 3, 2008, for PCT Application No. PCT/US2007/062474, filed Feb. 21, 2007, three pages.
International Search Report mailed Nov. 27, 2009, for PCT Application No. PCT/US2009/051874, Filed Jul. 27, 2009, three pages.
iriver clix Product Guide, copyright 1999-2006, 38 pages.
iriver clix Quick Start Guide, undated, 2 pages.
Jacob et al., “Integrality and Separability of Input Devices,” ACM Transactions on Computer-Human Interaction, 1:3-26 (Mar. 1994).
Kionx “KXP84 Series Summary Data Sheet” copyright 2005, dated Oct. 21, 2005, 4-pgs.
Lee, “A Fast Multiple-Touch-Sensitive Input Device,” Master's Thesis, University of Toronto (1984).
Matsushita et al., “HoloWall: Designing a Finger, Hand, Body and Object Sensitive Wall,” In Proceedings of UIST '97, Oct. 1997.
Non-Final Office Action mailed Jul. 2, 2008, for U.S. Appl. No. 11/115,539, filed Apr. 26, 2005, 18 pages.
Non-Final Office Action mailed Feb. 26, 2009, for U.S. Appl. No. 11/367,749, filed Mar. 3, 2006, 10 pages.
Non-Final Office Action mailed Apr. 2, 2009, for U.S. Appl. No. 11/426,078, filed Jun. 23, 2006, 21 pages.
Non-Final Office Action mailed Apr. 6, 2009, for U.S. Appl. No. 11/115,539, filed Apr. 26, 2005, 31 pages.
Non-Final Office Action mailed Jan. 12, 2010, for U.S. Appl. No. 11/367,749, filed Mar. 3, 2006, eight pages.
Non-Final Office Action mailed Jan. 15, 2010, for U.S. Appl. No. 11/115,539, filed Apr. 26, 2005, 10 pages.
Non-Final Office Action mailed Jan. 28, 2011, for U.S. Appl. No. 11/966,948, filed Dec. 28, 2007, 11 pages.
Non-Final Office Action mailed Mar. 9, 2011, for U.S. Appl. No. 12/486,710, filed Jun. 17, 2009, 13 pages.
Non-Final Office Action mailed Dec. 2, 2011, for U.S. Appl. No. 12/184,190, filed Jul. 31, 2008, 21 pages.
Non-Final Office Action mailed Mar. 28, 2012, for U.S. Appl. No. 12/486,710, filed Jun. 17, 2009, 25 pages.
Non-Final Office Action mailed Jul. 5, 2012, for U.S. Appl. No. 12/184,190, filed Jul. 31, 2008, 19 pages.
Non-Final Office Action mailed Jun. 6, 2013, for U.S. Appl. No. 12/486,710, filed Jun. 17, 2009, 28 pages.
Non-Final Office Action mailed Jul. 5, 2013, for U.S. Appl. No. 11/367,749, filed Mar. 3, 2006, eight pages.
Non-Final Office Action mailed Aug. 14, 2013, for U.S. Appl. No. 12/188,988, filed Aug. 8, 2008, 17 pages.
Non-Final Office Action mailed Aug. 21, 2013, for U.S. Appl. No. 12/188,948, filed Aug. 8, 2008, 13 pages.
Non-Final Office Action mailed Feb. 27, 2014, for U.S. Appl. No. 11/966,948, filed Dec. 28, 2007, 10 pages.
Non-Final Office Action mailed Aug. 25, 2014, for U.S. Appl. No. 12/486,710, filed Jun. 17, 2009, 28 pages.
Non-Final Office Action mailed Apr. 10, 2015, for U.S. Appl. No. 14/595,032, filed Jan. 12, 2105, eleven pages.
Non-Final Office Action mailed May 14, 2015, for U.S. Appl. No. 11/367,749, filed Mar. 3, 2006, 14 pages.
Non-Final Office Action mailed Aug. 26, 2015, for U.S. Appl. No. 11/966,948, filed Dec. 28, 2007, ten pages.
Non-Final Office Action mailed Feb. 2, 2016, for U.S. Appl. No. 14/940,010, filed Nov. 12, 2015, eight pages.
Non-Final Office Action mailed Apr. 20, 2016, for U.S. Appl. No. 14/724,753, filed May 28, 2015, fifteen pages.
Non-Final Office Action mailed Jun. 27, 2016, for U.S. Appl. No. 14/595,032, filed Jan. 12, 2105, eight pages.
Notice of Allowance mailed Sep. 25, 2009, for U.S. Appl. No. 11/426,078, filed Jun. 23, 2006, 14 pages.
Notice of Allowance mailed Jun. 2, 2010, for U.S. Appl. No. 11/115,539, filed Apr. 26, 2005, eight pages.
Notice of Allowance mailed Jun. 18, 2013, for U.S. Appl. No. 12/890,437, filed Sep. 24, 2010, 11 pages.
Notice of Allowance mailed Dec. 30, 2013, for U.S. Appl. No. 12/188,988, filed Aug. 8, 2008, nine pages.
Notice of Allowance mailed Jan. 2, 2014, for U.S. Appl. No. 12/188,948, filed Aug. 8, 2008, six pages.
Notice of Allowance mailed Jan. 29, 2015, for U.S. Appl. No. 12/486,710, filed Jun. 17, 2009, five pages.
Notice of Allowance mailed Jan. 11, 2016, for U.S. Appl. No. 12/184,190, filed Jul. 31, 2008, seven pages.
Press Release, “iriver clix Delivers Complete Package for Portable Entertainment Fans,” obtained from www.iriveramerican.com/images.pdf/iriv—clix.pdf, dated May 17, 2006, 3 pages.
Quantum Research Group “QT510 / Qwheel™ Touch Slider IC” copyright 2004-2005, 14-pgs.
Quek, “Unencumbered Gestural Interaction,” IEEE Multimedia, 3:36-47 (Winter 1996).
Radwin, “Activation Force and Travel Effects on Overexertion in Repetitive Key Tapping,” Human Factors, 39(1):130-140 (Mar. 1997).
Rekimoto et al., “ToolStone: Effective Use of the Physical Manipulation Vocabularies of Input Devices,” In Proc. of UIST 2000, 2000.
Rekimoto, J. (2002). “SmartSkin: An Infrastructure for Freehand Manipulation on Interactive Surfaces,” CHI 2002, Apr. 20-25, 2002. [(Apr. 25, 2002). 4(1):113-120].
Rubine et al., “Programmable Finger-Tracking Instrument Controllers,” Computer Music Journal, vol. 14, No. 1 (Spring 1990).
Rutledge et al., “Force-To-Motion Functions for Pointing,” Human-Computer Interaction—Interact (1990).
Subatai Ahmad, “A Usable Real-Time 3D Hand Tracker,” Proceedings of the 28th Asilomar Conference on Signals, Systems and Computers—Part 2 (of 2), vol. 2 (Oct. 1994).
Texas Instruments, “TSC2003/12C Touch Screen Controller,” Data Sheet SBAS 162, dated Oct. 2001, 20 pages.
U.S. Appl. No. 10/789,676, filed Feb. 27, 2004 entitled “Shape Detecting Input Device”.
Wellner, “The Digital Desk Calculators: Tangible Manipulation on a Desk Top Display” In ACM UIST '91 Proceedings, pp. 27-34, Nov. 1991.
Williams, “Applications for a Switched-Capacitor Instrumentation Building Block” Linear Technology Application Note 3, Jul. 1985, pp. 1-16.
Yamada et al., “A Switched-Capacitor Interface for Capacitive Pressure Sensors” IEEE Transactions on Instrumentation and Measurement, vol. 41, No. 1, Feb. 1992, pp. 81-86.
Yeh et al., “Switched Capacitor Interface Circuit for Capacitive Transducers” 1985 IEEE.
Zhai et al., “Dual Stream Input for Pointing and Scrolling,” Proceedings of CHI' 97 Extended Abstracts (1997).
Zimmerman et al., “Applying Electric Field Sensing to Human-Computer Interfaces,” In CHI '85 Proceedings, pp. 280-287, 1995.
Final Office Action mailed Feb. 15, 2017, for U.S. Appl. No. 14/595,032, filed Jan. 12, 2015, nine pages.
Non-Final Office Action mailed Apr. 6, 2017, for U.S. Appl. No. 11/966,948, filed Dec. 28, 2007, 13 pages.
Non-Final Office Action mailed May 17, 2017, for U.S. Appl. No. 14/940,010, filed Nov. 12, 2015, ten pages.
Related Publications (1)
Number Date Country
20080297478 A1 Dec 2008 US
Divisions (1)
Number Date Country
Parent 10654108 Sep 2003 US
Child 12189030 US