US 7,489,299 B2Grant

User interface devices and methods employing accelerometers

Issue Date:2009-02-10

•11 Claims

•15 Drawing Sheets

Abstract

Systems and methods according to the present invention address these needs and others by providing a 3D pointing device and methods for 3D pointing which provide accurate translation of movement of the 3D pointing device into user interface commands, e.g., cursor movement. According to exemplary embodiments of the present invention, a 3D pointing device includes a plurality of accelerometers.

Metadata

Assignee

Hillcrest Laboratories, Inc.

Inventors

Matthew G. Liberty
Daniel S. Simpkins

Application Information

Application Number:US 10/970,811

Filing Date:2004-10-21

Priority Date:2003-10-23

Art Unit:2629

Classifications

IPC:

G09G5/08

Patent Drawings (15 sheets)

Description

Related Applications

[0001] This application is related to, and claims priority from, U.S. Provisional Patent Application Ser. No. 60/513,869 filed on Oct. 23, 2003, entitled “User Interface Device Employing Accelerometers”, the disclosure of which is incorporated here by reference. This application is also related to, and claims priority from, U.S. Provisional Patent Application Ser. No. 60/566,444 filed on Apr. 30, 2004, entitled “Freespace Pointing Device”, the disclosure of which is incorporated here by reference. Additionally, this application is related to, and claims priority from, U.S. Provisional Patent Application Ser. No. 60/612,571 Sep. 23, 2004, entitled “Free Space Pointing Devices and Methods”, the disclosure of which is incorporated here by reference.

Background

[0002] The present invention describes three-dimensional (hereinafter “3D”) pointing devices usable in a number of different applications including, for example, a framework for organizing, selecting and launching media items.

[0003] Technologies associated with the communication of information have evolved rapidly over the last several decades. Television, cellular telephony, the Internet and optical communication techniques (to name just a few things) combine to inundate consumers with available information and entertainment options. Taking television as an example, the last three decades have seen the introduction of cable television service, satellite television service, pay-per-view movies and video-on-demand. Whereas television viewers of the 1960s could typically receive perhaps four or five over-the-air TV channels on their television sets, today's TV watchers have the opportunity to select from hundreds, thousands, and potentially millions of channels of shows and information. Video-on-demand technology, currently used primarily in hotels and the like, provides the potential for in-home entertainment selection from among thousands of movie titles.

[0004] The technological ability to provide so much information and content to end users provides both opportunities and challenges to system designers and service providers. One challenge is that while end users typically prefer having more choices rather than fewer, this preference is counterweighted by their desire that the selection process be both fast and simple. Unfortunately, the development of the systems and interfaces by which end users access media items has resulted in selection processes which are neither fast nor simple. Consider again the example of television programs. When television was in its infancy, determining which program to watch was a relatively simple process primarily due to the small number of choices. One would consult a printed guide which was formatted, for example, as series of columns and rows which showed the correspondence between (1) nearby television channels, (2) programs being transmitted on those channels and (3) date and time. The television was tuned to the desired channel by adjusting a tuner knob and the viewer watched the selected program. Later, remote control devices were introduced that permitted viewers to tune the television from a distance. This addition to the user-television interface created the phenomenon known as “channel surfing” whereby a viewer could rapidly view short segments being broadcast on a number of channels to quickly learn what programs were available at any given time.

[0005] Despite the fact that the number of channels and amount of viewable content has dramatically increased, the generally available user interface, control device options and frameworks for televisions has not changed much over the last 30 years. Printed guides are still the most prevalent mechanism for conveying programming information. The multiple button remote control with up and down arrows is still the most prevalent channel/content selection mechanism. The reaction of those who design and implement the TV user interface to the increase in available media content has been a straightforward extension of the existing selection procedures and interface objects. Thus, the number of rows in the printed guides has been increased to accommodate more channels. The number of buttons on the remote control devices has been increased to support additional functionality and content handling, e.g., as shown in FIG. 1. However, this approach has significantly increased both the time required for a viewer to review the available information and the complexity of actions required to implement a selection. Arguably, the cumbersome nature of the existing interface has hampered commercial implementation of some services, e.g., video-on-demand, since consumers are resistant to new services that will add complexity to an interface that they view as already too slow and complex.

[0006] In addition to increases in bandwidth and content, the user interface bottleneck problem is being exacerbated by the aggregation of technologies. Consumers are reacting positively to having the option of buying integrated systems rather than a number of segregable components. An example of this trend is the combination television/VCR/DVD in which three previously independent components are frequently sold today as an integrated unit. This trend is likely to continue, potentially with an end result that most if not all of the communication devices currently found in the household will be packaged together as an integrated unit, e.g., a television/VCR/DVD/internet access/radio/stereo unit. Even those who continue to buy separate components will likely desire seamless control of, and interworking between, the separate components. With this increased aggregation comes the potential for more complexity in the user interface. For example, when so-called “universal” remote units were introduced, e.g., to combine the functionality of TV remote units and VCR remote units, the number of buttons on these universal remote units was typically more than the number of buttons on either the TV remote unit or VCR remote unit individually. This added number of buttons and functionality makes it very difficult to control anything but the simplest aspects of a TV or VCR without hunting for exactly the right button on the remote. Many times, these universal remotes do not provide enough buttons to access many levels of control or features unique to certain TVs. In these cases, the original device remote unit is still needed, and the original hassle of handling multiple remotes remains due to user interface issues arising from the complexity of aggregation. Some remote units have addressed this problem by adding “soft” buttons that can be programmed with the expert commands. These soft buttons sometimes have accompanying LCD displays to indicate their action. These too have the flaw that they are difficult to use without looking away from the TV to the remote control. Yet another flaw in these remote units is the use of modes in an attempt to reduce the number of buttons. In these “moded” universal remote units, a special button exists to select whether the remote should communicate with the TV, DVD player, cable set-top box, VCR, etc. This causes many usability issues including sending commands to the wrong device, forcing the user to look at the remote to make sure that it is in the right mode, and it does not provide any simplification to the integration of multiple devices. The most advanced of these universal remote units provide some integration by allowing the user to program sequences of commands to multiple devices into the remote. This is such a difficult task that many users hire professional installers to program their universal remote units.

[0007] Some attempts have also been made to modernize the screen interface between end users and media systems. However, these attempts typically suffer from, among other drawbacks, an inability to easily scale between large collections of media items and small collections of media items. For example, interfaces which rely on lists of items may work well for small collections of media items, but are tedious to browse for large collections of media items. Interfaces which rely on hierarchical navigation (e.g., tree structures) may be speedier to traverse than list interfaces for large collections of media items, but are not readily adaptable to small collections of media items. Additionally, users tend to lose interest in selection processes wherein the user has to move through three or more layers in a tree structure. For all of these cases, current remote units make this selection processor even more tedious by forcing the user to repeatedly depress the up and down buttons to navigate the list or hierarchies. When selection skipping controls are available such as page up and page down, the user usually has to look at the remote to find these special buttons or be trained to know that they even exist.

[0008] Of particular interest for this specification are the remote devices usable to interact with such frameworks, as well as other applications and systems. As mentioned in the above-incorporated application, various different types of remote devices can be used with such frameworks including, for example, trackballs, “mouse”-type pointing devices, light pens, etc. However, another category of remote devices which can be used with such frameworks (and other applications) is 3D pointing devices. The phrase “3D pointing” is used in this specification to refer to the ability of an input device to move in three (or more) dimensions in the air in front of, e.g., a display screen, and the corresponding ability of the user interface to translate those motions directly into user interface commands, e.g., movement of a cursor on the display screen. The transfer of data between the 3D pointing device may be performed wirelessly or via a wire connecting the 3D pointing device to another device. Thus “3D pointing” differs from, e.g., conventional computer mouse pointing techniques which use a surface, e.g., a desk surface or mousepad, as a proxy surface from which relative movement of the mouse is translated into cursor movement on the computer display screen. An example of a 3D pointing device can be found in U.S. Pat. No. 5,440,326.

[0009] The '326 patent describes, among other things, a vertical gyroscope adapted for use as a pointing device for controlling the position of a cursor on the display of a computer. A motor at the core of the gyroscope is suspended by two pairs of orthogonal gimbals from a hand-held controller device and nominally oriented with its spin axis vertical by a pendulous device. Electro-optical shaft angle encoders sense the orientation of a handheld controller device as it is manipulated by a user and the resulting electrical output is converted into a format usable by a computer to control the movement of a cursor on the screen of the computer display. However there continues to be a need for a cost-effective, accurate and user-friendly, 3D pointing device.

Summary

[0010] Systems and methods according to the present invention address these needs and others by providing a 3D pointing device and methods for 3D pointing which provide accurate translation of movement of the 3D pointing device into user interface commands, e.g., cursor movement. According to exemplary embodiments of the present invention, a 3D pointing device includes a plurality of accelerometers.

[0011] According to one exemplary embodiment of the present invention, a handheld, user interface device includes a plurality of accelerometers, each of which provide acceleration data associated with movement of the device, a processing unit for transforming the acceleration data into data from which two dimensional cursor movement data can be generated, wherein the processing unit further processes the acceleration data to determine when the handheld, user interface device is stationary and recalibrates the handheld, user interface device when the handheld, user interface device is stationary.

Brief Description of the Drawings

[0012] The accompanying drawings illustrate exemplary embodiments of the present invention, wherein:

[0013] FIG. 1 depicts a conventional remote control unit for an entertainment system;

[0014] FIG. 2 depicts an exemplary media system in which exemplary embodiments of the present invention can be implemented;

[0015] FIG. 3 shows a 3D pointing device according to an exemplary embodiment of the present invention;

[0016] FIG. 4 illustrates a cutaway view of the 3D pointing device in FIG. 4 including two rotational sensors and one accelerometer;

[0017] FIG. 4A illustrates a cutaway view of another embodiment of the 3D pointing device including four accelerometer devices arranged in a non-coplanar configuration, each accelerometer device containing three accelerometers;

[0018] FIG. 5 is a block diagram illustrating processing of data associated with 3D pointing devices according to an exemplary embodiment of the present invention;

[0019] FIGS. 6(a)-6(d) illustrate the effects of tilt;

[0020] FIG. 7 depicts a hardware architecture of a 3D pointing device according to an exemplary embodiment of the present invention;

[0021] FIG. 8 is a state diagram depicting a stationary detection mechanism according to an exemplary embodiment of the present invention;

[0022] FIG. 9 illustrates six degrees of freedom associated with another exemplary embodiment of the present invention;

[0023] FIG. 10 depicts an algorithm for processing acceleration data according to another exemplary embodiment of the present invention;

[0024] FIG. 11 depicts a hardware architecture of a 3D pointing device according to the exemplary embodiment of FIG. 10;

[0025] FIG. 12 depicts a software architecture of a 3D pointing device according to the exemplary embodiment of FIG. 10; and

[0026] FIG. 13 shows the exemplary embodiment of FIGS. 9 and 10 from an algorithmic perspective.

Detailed Description

[0027] The following detailed description of the invention refers to the accompanying drawings. The same reference numbers in different drawings identify the same or similar elements. Also, the following detailed description does not limit the invention. Instead, the scope of the invention is defined by the appended claims.

[0028] In order to provide some context for this discussion, an exemplary aggregated media system 200 in which the present invention can be implemented will first be described with respect to FIG. 2. Those skilled in the art will appreciate, however, that the present invention is not restricted to implementation in this type of media system and that more or fewer components can be included therein. Therein, an input/output (I/O) bus 210 connects the system components in the media system 200 together. The I/O bus 210 represents any of a number of different of mechanisms and techniques for routing signals between the media system components. For example, the I/O bus 210 may include an appropriate number of independent audio “patch” cables that route audio signals, coaxial cables that route video signals, two-wire serial lines or infrared or radio frequency transceivers that route control signals, optical fiber or any other routing mechanisms that route other types of signals.

[0029] In this exemplary embodiment, the media system 200 includes a television/monitor 212, a video cassette recorder (VCR) 214, digital video disk (DVD) recorder/playback device 216, audio/video tuner 218 and compact disk player 220 coupled to the I/O bus 210. The VCR 214, DVD 216 and compact disk player 220 may be single disk or single cassette devices, or alternatively may be multiple disk or multiple cassette devices. They may be independent units or integrated together. In addition, the media system 200 includes a microphone/speaker system 222, video camera 224 and a wireless I/O control device 226. According to exemplary embodiments of the present invention, the wireless I/O control device 226 is a 3D pointing device according to one of the exemplary embodiments described below. The wireless I/O control device 226 can communicate with the entertainment system 200 using, e.g., an IR or RF transmitter or transceiver. Alternatively, the I/O control device can be connected to the entertainment system 200 via a wire.

[0030] The entertainment system 200 also includes a system controller 228. According to one exemplary embodiment of the present invention, the system controller 228 operates to store and display entertainment system data available from a plurality of entertainment system data sources and to control a wide variety of features associated with each of the system components. As shown in FIG. 2, system controller 228 is coupled, either directly or indirectly, to each of the system components, as necessary, through I/O bus 210. In one exemplary embodiment, in addition to or in place of I/O bus 210, system controller 228 is configured with a wireless communication transmitter (or transceiver), which is capable of communicating with the system components via IR signals or RF signals. Regardless of the control medium, the system controller 228 is configured to control the media components of the media system 200 via a graphical user interface described below.

[0031] As further illustrated in FIG. 2, media system 200 may be configured to receive media items from various media sources and service providers. In this exemplary embodiment, media system 200 receives media input from and, optionally, sends information to, any or all of the following sources: cable broadcast 230, satellite broadcast 232 (e.g., via a satellite dish), very high frequency (VHF) or ultra high frequency (UHF) radio frequency communication of the broadcast television networks 234 (e.g., via an aerial antenna), telephone network 236 and cable modem 238 (or another source of Internet content). Those skilled in the art will appreciate that the media components and media sources illustrated and described with respect to FIG. 2 are purely exemplary and that media system 200 may include more or fewer of both. For example, other types of inputs to the system include AM/FM radio and satellite radio.

[0032] More details regarding this exemplary entertainment system and frameworks associated therewith can be found in the above-incorporated by reference U.S. patent application “A Control Framework with a Zoomable Graphical User Interface for Organizing, Selecting and Launching Media Items”. Alternatively, remote devices in accordance with the present invention can be used in conjunction with other systems, for example computer systems including, e.g., a display, a processor and a memory system or with various other systems and applications.

[0033] As mentioned in the Background section, remote devices which operate as 3D pointers are of particular interest for the present specification. Such devices enable the translation of movement, e.g., gestures, into commands to a user interface. An exemplary 3D pointing device 400 is depicted in FIG. 3. Therein, user movement of the 3D pointing can be defined, for example, in terms of a combination of x-axis attitude (roll), y-axis elevation (pitch) and/or z-axis heading (yaw) motion of the 3D pointing device 400. In addition, some exemplary embodiments of the present invention can also measure linear movement of the 3D pointing device 400 along the x, y, and z axes to generate cursor movement or other user interface commands. In the exemplary embodiment of FIG. 3, the 3D pointing device 400 includes two buttons 402 and 404 as well as a scroll wheel 406, although other exemplary embodiments will include other physical configurations. According to exemplary embodiments of the present invention, it is anticipated that 3D pointing devices 400 will be held by a user in front of a display 408 and that motion of the 3D pointing device 400 will be translated by the 3D pointing device into output which is usable to interact with the information displayed on display 408, e.g., to move the cursor 410 on the display 408. For example, rotation of the 3D pointing device 400 about the y-axis can be sensed by the 3D pointing device 400 and translated into an output usable by the system to move cursor 410 along the y₂axis of the display 408. Likewise, rotation of the 3D pointing device 408 about the z-axis can be sensed by the 3D pointing device 400 and translated into an output usable by the system to move cursor 410 along the x₂axis of the display 408. It will be appreciated that the output of 3D pointing device 400 can be used to interact with the display 408 in a number of ways other than (or in addition to) cursor movement, for example it can control cursor fading, volume or media transport (play, pause, fast-forward and rewind). Input commands may include operations in addition to cursor movement, for example, a zoom in or zoom out on a particular region of a display. A cursor may or may not be visible. Similarly, rotation of the 3D pointing device 400 sensed about the x-axis of 3D pointing device 400 can be used in addition to, or as an alternative to, y-axis and/or z-axis rotation to provide input to a user interface.

[0034] According to one exemplary embodiment of the present invention, two rotational sensors 502 and 504 and one accelerometer 506 can be employed as sensors in 3D pointing device 400 as shown in FIG. 4. The rotational sensors 502 and 504 can, for example, be implemented using ADXRS150 sensors made by Analog Devices. It will be appreciated by those skilled in the art that other types of rotational sensors can be employed as rotational sensors 502 and 504 and that the ADXRS150 is purely used as an illustrative example. Unlike traditional gyroscopes, the ADXRS150 rotational sensors use MEMS technology to provide a resonating mass which is attached to a frame so that it can resonate only along one direction. The resonating mass is displaced when the body to which the sensor is affixed is rotated around the sensor's sensing axis. This displacement can be measured using the Coriolis acceleration effect to determine an angular velocity associated with rotation along the sensing axis. If the rotational sensors 502 and 504 have a single sensing axis (as for example the ADXRS150s), then they can be mounted in the 3D pointing device 400 such that their sensing axes are aligned with the rotations to be measured. For this exemplary embodiment of the present invention, this means that rotational sensor 502 is mounted such that its sensing axis is parallel to the y-axis and that rotational sensor 504 is mounted such that its sensing axis is parallel to the z-axis as shown in FIG. 4. Note, however, that aligning the sensing axes of the rotational sensors 502 and 504 parallel to the desired measurement axes is not required since exemplary embodiments of the present invention also provide techniques for compensating for offset between axes.

[0035] One challenge faced in implementing exemplary 3D pointing devices 400 in accordance with the present invention is to employ components, e.g., rotational sensors 502 and 504, which are not too costly, while at the same time providing a high degree of correlation between movement of the 3D pointing device 400, a user's expectation regarding how the user interface will react to that particular movement of the 3D pointing device and actual user interface performance in response to that movement. For example, if the 3D pointing device 400 is not moving, the user will likely expect that the cursor ought not to be drifting across the screen. Likewise, if the user rotates the 3D pointing device 400 purely around the y-axis, she or he would likely not expect to see the resulting cursor movement on display 408 contain any significant x₂axis component. To achieve these, and other, aspects of exemplary embodiments of the present invention, various measurements and calculations are performed by the handheld device 400 which are used to adjust the outputs of one or more of the sensors 502, 504 and 506 and/or as part of the input used by a processor to determine an appropriate output for the user interface based on the outputs of the sensors 502, 504 and 506. These measurements and calculations are used to compensate for factors which fall broadly into two categories: (1) factors which are intrinsic to the 3D pointing device 400, e.g., errors associated with the particular sensors 502, 504 and 506 used in the device 400 or the way in which the sensors are mounted in the device 400 and (2) factors which are not intrinsic to the 3D pointing device 400, but are instead associated with the manner in which a user is using the 3D pointing device 400, e.g., linear acceleration, tilt and tremor. Exemplary techniques for handling each of these effects are described below.

[0036] A process model 600 which describes the general operation of 3D pointing devices according to exemplary embodiments of the present invention is illustrated in FIG. 5. The rotational sensors 502 and 504, as well as the accelerometer 506, produce analog signals which are sampled periodically, e.g., 200 samples/second. For the purposes of this discussion, a set of these inputs shall be referred to using the notation (x, y, z, ay, az), wherein x, y, z are the sampled output values of the exemplary three-axis accelerometer 506 which are associated with acceleration of the 3D pointing device in the x-axis, y-axis and z-axis directions, respectively, ay is a the sampled output value from rotational sensor 502 associated with the rotation of the 3D pointing device about the y-axis and az is the sampled output value from rotational sensor 504 associated with rotation of the 3D pointing device 400 about the z-axis.

[0037] The output from the accelerometer 506 is provided and, if the accelerometer 506 provides analog output, then the output is sampled and digitized by an A/D converter (not shown) to generate sampled accelerometer output 602. The sampled output values are converted from raw units to units of acceleration, e.g., gravities (g), as indicated by conversion function 604. The acceleration calibration block 606 provides the values used for the conversion function 604. This calibration of the accelerometer output 602 can include, for example, compensation for one or more of scale, offset and axis misalignment error associated with the accelerometer 506. Exemplary conversions for the accelerometer data can be performed using the following equation:
A=S*((M−P).*G(T)) (1)
wherein M is a 3×1 column vector composed of the sampled output values (x, y, z), P is a 3×1 column vector of sensor offsets, and S is a 3×3 matrix that contains both scale, axis misalignment, and sensor rotation compensation. G(T) is a gain factor that is a function of temperature. The “*” operator represents matrix multiplication and the “.*” operator represents element multiplication. The exemplary accelerometer 506 has an exemplary full range of +/−2 g. Sensor offset, P, refers to the sensor output, M, for an accelerometer measurement of 0 g. Scale refers to the conversion factor between the sampled unit value and g. The actual scale of any given accelerometer sensor may deviate from these nominal scale values due to, e.g., manufacturing variances. Accordingly the scale factor in the equations above will be proportional to this deviation.

[0038] Accelerometer 506 scale and offset deviations can be measured by, for example, applying 1 g of force along one an axis and measuring the result, R1. Then a −1 g force is applied resulting in measurement R2. The individual axis scale, s, and the individual axis offset, p, can be computed as follows:
s=(R1−R2)/2 (2)
p=(R1+R2)/2 (3)
In this simple case, P is the column vector of the p for each axis, and S is the diagonal matrix of the 1/s for each axis.

[0039] However, in addition to scale and offset, readings generated by accelerometer 506 may also suffer from cross-axes effects. Cross-axes effects include non-aligned axes, e.g., wherein one or more of the sensing axes of the accelerometer 506 as it is mounted in the 3D pointing device 400 are not aligned with the corresponding axis in the inertial frame of reference, or mechanical errors associated with the machining of the accelerometer 506 itself, e.g., wherein even though the axes are properly aligned, a purely y-axis acceleration force may result in a sensor reading along the z-axis of the accelerometer 506. Both of these effects can also be measured and added to the calibration performed by function 606.

[0040] The accelerometer 506 serves several purposes in exemplary 3D pointing devices according to exemplary embodiments of the present invention. For example, if rotational sensors 502 and 504 are implemented using the exemplary Coriolis effect rotational sensors described above, then the output of the rotational sensors 502 and 504 will vary based on the linear acceleration experienced by each rotational sensor. Thus, one exemplary use of the accelerometer 506 is to compensate for fluctuations in the readings generated by the rotational sensors 502 and 504 which are caused by variances in linear acceleration. This can be accomplished by multiplying the converted accelerometer readings by a gain matrix 610 and subtracting (or adding) the results from (or to) the corresponding sampled rotational sensor data 612. For example, the sampled rotational data ay from rotational sensor 502 can be compensated for linear acceleration at block 614 as:
ay′=ay−C*A (4)
wherein C is the 1×3 row vector of rotational sensor susceptibility to linear acceleration along each axis given in units/g and A is the calibrated linear acceleration. Similarly, linear acceleration compensation for the sampled rotational data az from rotational sensor 504 can be provided at block 614. The gain matrices, C, vary between rotational sensors due to manufacturing differences. C may be computed using the average value for many rotational sensors, or it may be custom computed for each rotational sensor.

[0041] Like the accelerometer data, the sampled rotational data 612 is then converted from a sampled unit value into a value associated with a rate of angular rotation, e.g., radians/s, at function 616. This conversion step can also include calibration provided by function 618 to compensate the sampled rotational data for, e.g., scale and offset. Conversion/calibration for both ay and az can be accomplished using, for example, the following equation:
arad/s=(a′−offset(T))*scale+dOffset (5)
wherein a′ refers to the value being converted/calibrated, offset(T) refers to an offset value associated with temperature, scale refers to the conversion factor between the sampled unit value and rad/s, and dOffset refers to a dynamic offset value. Equation (5) may be implemented as a matrix equation in which case all variables are vectors except for scale. In matrix equation form, scale corrects for axis misalignment and rotational offset factors. Each of these variables is discussed in more detail below.

[0042] The offset values offset(T) and dOffset can be determined in a number of different ways. When the 3D pointing device 400 is not being rotated in, for example, the y-axis direction, the sensor 502 should output its offset value. However, the offset can be highly affected by temperature, so this offset value will likely vary. Offset temperature calibration may be performed at the factory, in which case the value(s) for offset(T) can be preprogrammed into the handheld device 400 or, alternatively, offset temperature calibration may also be learned dynamically during the lifetime of the device. To accomplish dynamic offset compensation, an input from a temperature sensor 619 is used in rotation calibration function 618 to compute the current value for offset(T). The offset(T) parameter removes the majority of offset bias from the sensor readings. However, negating nearly all cursor drift at zero movement can be useful for producing a high-performance pointing device. Therefore, the additional factor dOffset, can be computed dynamically while the 3D pointing device 400 is in use. The stationary detection function 608 determines when the handheld is most likely stationary and when the offset should be recomputed. Exemplary techniques for implementing stationary detection function 608, as well as other uses therefore, are described below.

[0043] An exemplary implementation of dOffset computation employs calibrated sensor outputs which are low-pass filtered. The stationary output detection function 608 provides an indication to rotation calibration function 618 to trigger computation of, for example, the mean of the low-pass filter output. The stationary output detection function 608 can also control when the newly computed mean is factored into the existing value for dOffset. Those skilled in the art will recognize that a multitude of different techniques can be used for computing the new value for dOffset from the existing value of dOffset and the new mean including, but not limited to, simple averaging, low-pass filtering and Kalman filtering. Additionally, those skilled in the art will recognize that numerous variations for offset compensation of the rotational sensors 502 and 504 can be employed. For example, the offset(T) function can have a constant value (e.g., invariant with temperature), more than two offset compensation values can be used and/or only a single offset value can be computed/used for offset compensation.

[0044] After conversion/calibration at block 616, the inputs from the rotational sensors 502 and 504 can be further processed to rotate those inputs into an inertial frame of reference, i.e., to compensate for tilt associated with the manner in which the user is holding the 3D pointing device 400, at function 620. Tilt correction is another significant aspect of some exemplary embodiments of the present invention as it is intended to compensate for differences in usage patterns of 3D pointing devices according to the present invention. More specifically, tilt correction according to exemplary embodiments of the present invention is intended to compensate for the fact that users will hold pointing devices in their hands at different x-axis rotational positions, but that the sensing axes of the rotational sensors 502 and 504 in the 3D pointing devices 400 are fixed. It is desirable that cursor translation across display 408 is substantially insensitive to the way in which the user grips the 3D pointing device 400, e.g., rotating the 3D pointing device 400 back and forth in a manner generally corresponding to the horizontal dimension (x₂-axis) of the display 408 should result in cursor translation along the x₂-axis, while rotating the 3D pointing device up and down in a manner generally corresponding to the vertical dimension (y₂-axis) of the display 408 should result in cursor translation along the y₂-axis, regardless of the orientation in which the user is holding the 3D pointing device 400.

[0045] To better understand the need for tilt compensation according to exemplary embodiments of the present invention, consider the example shown in FIG. 6(a). Therein, the user is holding 3D pointing device 400 in an exemplary inertial frame of reference, which can be defined as having an x-axis rotational value of 0 degrees. The inertial frame of reference can, purely as an example, correspond to the orientation illustrated in FIG. 6(a) or it can be defined as any other orientation. Rotation of the 3D pointing device 400 in either the y-axis or z-axis directions will be sensed by rotational sensors 502 and 504, respectively. For example, rotation of the 3D pointing device 400 around the z-axis by an amount Δz as shown in FIG. 6(b) will result in a corresponding cursor translation Δx₂in the x₂axis dimension across the display 408 (i.e., the distance between the dotted version of cursor 410 and the undotted version).

[0046] If, on the other hand, the user holds the 3D pointing device 400 in a different orientation, e.g., with some amount of x-axis rotation relative to the inertial frame of reference, then the information provided by the sensors 502 and 504 would not (absent tilt compensation) provide an accurate representation of the user's intended interface actions. For example, referring to FIG. 6(c), consider a situation wherein the user holds the 3D pointing device 400 with an x-axis rotation of 45 degrees relative to the exemplary inertial frame of reference as illustrated in FIG. 6(a). Assuming the same z-axis rotation Δz by a user, the cursor 410 will instead be translated in both the x₂-axis direction and the y₂-axis direction by as shown in FIG. 6(d). This is due to the fact that the sensing axis of rotational sensor 502 is now oriented between the y-axis and the z-axis (because of the orientation of the device in the user's hand). Similarly, the sensing axis of the rotational sensor 504 is also oriented between the y-axis and the z-axis (although in a different quadrant). In order to provide an interface which is transparent to the user in terms of how the 3D pointing device 400 is held, tilt compensation according to exemplary embodiments of the present invention translates the readings output from rotational sensors 502 and 504 back into the inertial frame of reference as part of processing the readings from these sensors into information indicative of rotational motion of the 3D pointing device 400.

[0047] According to exemplary embodiments of the present invention, returning to FIG. 5, this can be accomplished by determining the tilt of the 3D pointing device 400 using the inputs y and z received from accelerometer 506 at function 622. More specifically, after the acceleration data is converted and calibrated as described above, it can be low pass filtered at LPF 624 to provide an average acceleration (gravity) value to the tilt determination function 622. Then, tilt θ can be calculated in function 622 as:

[0048]

\begin{matrix} θ = \tan^{- 1} (\frac{y}{z}) & (7) \end{matrix}

The value θ can be numerically computed as a tan 2(y,z) to prevent division by zero and give the correct sign. Then, function 620 can perform the rotation R of the converted/calibrated inputs ay and xz using the equation:

[0049]

\begin{matrix} R = [\begin{matrix} \cos θ \sin θ \\ - \sin θ \cos θ \end{matrix}] \cdot [\begin{matrix} α y \\ α z \end{matrix}] & (8) \end{matrix}

to rotate the converted/calibrated inputs ay and az to compensate for the tilt θ.

[0050] Once the calibrated sensor readings have been compensated for linear acceleration, processed into readings indicative of angular rotation of the 3D pointing device 400, and compensated for tilt, post-processing can be performed at blocks 626 and 628. Exemplary post-processing can include compensation for various factors such as human tremor. Although tremor may be removed using several different methods, one way to remove tremor is by using hysteresis. The angular velocity produced by rotation function 620 is integrated to produce an angular position. Hysteresis of a calibrated magnitude is then applied to the angular position. The derivative is taken of the output of the hysteresis block to again yield an angular velocity. The resulting output is then scaled at function 628 (e.g., based on the sampling period) and used to generate a result within the interface, e.g., movement of a cursor 410 on a display 408.

[0051] Having provided a process description of exemplary 3D pointing devices according to the present invention, FIG. 7 illustrates an exemplary hardware architecture. Therein, a processor 800 communicates with other elements of the 3D pointing device including a scroll wheel 802, JTAG 804, LEDs 806, switch matrix 808, IR photodetector 810, rotational sensors 812, accelerometer 814 and transceiver 816. The scroll wheel 802 is an optional input component which enables a user to provide input to the interface by rotating the scroll wheel 802 clockwise or counterclockwise. JTAG 804 provides the programming and debugging interface to the processor. LEDs 806 provide visual feedback to a user, for example, when a button is pressed. Switch matrix 808 receives inputs, e.g., indications that a button on the 3D pointing device 400 has been depressed or released, that are then passed on to processor 800. The optional IR photodetector 810 can be provided to enable the exemplary 3D pointing device to learn IR codes from other remote controls. Rotational sensors 812 provide readings to processor 800 regarding, e.g., the y-axis and z-axis rotation of the 3D pointing device as described above. Accelerometer 814 provides readings to processor 800 regarding the linear acceleration of the 3D pointing device 400 which can be used as described above, e.g., to perform tilt compensation and to compensate for errors which linear acceleration introduces into the rotational readings generated by rotational sensors 812. Transceiver 816 is used to communicate information to and from 3D pointing device 400, e.g., to the system controller 228 or to a processor associated with a computer. The transceiver 816 can be a wireless transceiver, e.g., operating in accordance with the Bluetooth standards for short-range wireless communication or an infrared transceiver. Alternatively, 3D pointing device 400 can communicate with systems via a wireline connection.

[0052] Stationary detection function 608, mentioned briefly above, can operate to determine whether the 3D pointing device 400 is, for example, either stationary or active (moving). This categorization can be performed in a number of different ways. One way, according to an exemplary embodiment of the present invention, is to compute the variance of the sampled input data of all inputs (x, y, z, ay, az) over a predetermined window, e.g., every quarter of a second. This variance is then compared with a threshold to classify the 3D pointing device as either stationary or active.

[0053] Another stationary detection technique according to exemplary embodiments of the present invention involves transforming the inputs into the frequency domain by, e.g., performing a Fast Fourier Transform (FFT) on the input data. Then, the data can be analyzed using, e.g., peak detection methods, to determine if the 3D pointing device 400 is either stationary or active. Additionally, a third category can be distinguished, specifically the case where a user is holding the 3D pointing device 400 but is not moving it (also referred to herein as the “stable” state. This third category can be distinguished from stationary (not held) and active by detecting the small movement of the 3D pointing device 400 introduced by a user's hand tremor when the 3D pointing device 400 is being held by a user. Peak detection can also be used by stationary detection function 608 to make this determination. Peaks within the range of human tremor frequencies, e.g., nominally 8-12 Hz, will typically exceed the noise floor of the device (experienced when the device is stationary and not held) by approximately 20 dB

[0054] In the foregoing examples, the variances in the frequency domain were sensed within a particular frequency range, however the actual frequency range to be monitored and used to characterize the status of the 3D pointing device 400 may vary. For example, the nominal tremor frequency range may shift based on e.g., the ergonomics and weight of the 3D pointing device 400, e.g., from 8-12 Hz to 4-7 Hz.

[0055] According to another exemplary embodiment of the present invention, stationary detection mechanism 608 can include a state machine. An exemplary state machine is shown in FIG. 12. Therein, the ACTIVE state is, in this example, the default state during which the 3D pointing device 400 is moving and being used to, e.g., provide inputs to a user interface. The 3D pointing device 400 can enter the ACTIVE state on power-up of the device as indicated by the reset input. If the 3D pointing device 400 stops moving, it may then enter the INACTIVE state. The various state transitions illustrated in FIG. 12 can be triggered by any of a number of different criteria including, but not limited to, data output from one or both of the rotational sensors 502 and 504, data output from the accelerometer 506, time domain data, frequency domain data or any combination thereof. State transition conditions will be generically referred to herein using the convention “Condition_stateA_→_stateB”. For example, the 3D pointing device 400 will transition from the ACTIVE state to the INACTIVE state when condition_active_→_inactiveoccurs. For the sole purpose of illustration, consider that condition_active_→_inactivecan, in an exemplary 3D pointing device 400, occur when mean and/or standard deviation values from both the rotational sensor(s) and the accelerometer fall below first predetermined threshold values for a first predetermined time period.

[0056] State transitions can be determined by a number of different conditions based upon the interpreted sensor outputs. Exemplary condition metrics include the variance of the interpreted signals over a time window, the threshold between a reference value and the interpreted signal over a time window, the threshold between a reference value and the filtered interpreted signal over a time window, and the threshold between a reference value and the interpreted signal from a start time can be used to determine state transitions. All, or any combination, of these condition metrics can be used to trigger state transitions. Alternatively, other metrics can also be used. According to one exemplary embodiment of the present invention, a transition from the INACTIVE state to the ACTIVE state occurs either when (1) a mean value of sensor output(s) over a time window is greater than predetermined threshold(s) or (2) a variance of values of sensor output(s) over a time window is greater than predetermined threshold(s) or (3) an instantaneous delta between sensor values is greater than a predetermined threshold.

[0057] The INACTIVE state enables the stationary detection mechanism 608 to distinguish between brief pauses during which the 3D pointing device 400 is still being used, e.g., on the order of a tenth of a second, and an actual transition to either a stable or stationary condition. This protects against the functions which are performed during the STABLE and STATIONARY states, described below, from inadvertently being performed when the 3D pointing device is being used. The 3D pointing device 400 will transition back to the ACTIVE state when condition_inactive_→_activeoccurs, e.g., if the 3D pointing device 400 starts moving again such that the measured outputs from the rotational sensor(s) and the accelerometer exceeds the first threshold before a second predetermined time period in the INACTIVE state elapses.

[0058] The 3D pointing device 400 will transition to either the STABLE state or the STATIONARY state after the second predetermined time period elapses. As mentioned earlier, the STABLE state reflects the characterization of the 3D pointing device 400 as being held by a person but being substantially unmoving, while the STATIONARY state reflects a characterization of the 3D pointing device as not being held by a person. Thus, an exemplary state machine according to the present invention can provide for a transition to the STABLE state after the second predetermined time period has elapsed if minimal movement associated with hand tremor is present or, otherwise, transition to the STATIONARY state.

[0059] The STABLE and STATIONARY states define times during which the 3D pointing device 400 can perform various functions. For example, since the STABLE state is intended to reflect times when the user is holding the 3D pointing device 400 but is not moving it, the device can record the movement of the 3D pointing device 400 when it is in the STABLE state e.g., by storing outputs from the rotational sensor(s) and/or the accelerometer while in this state. These stored measurements can be used to determine a tremor pattern associated with a particular user or users as described below. Likewise, when in the STATIONARY state, the 3D pointing device 400 can take readings from the rotational sensors and/or the accelerometer for use in compensating for offset as described above.

[0060] If the 3D pointing device 400 starts to move while in either the STABLE or STATIONARY state, this can trigger a return to the ACTIVE state. Otherwise, after measurements are taken, the device can transition to the SLEEP state. While in the sleep state, the device can enter a power down mode wherein power consumption of the 3D pointing device is reduced and, e.g., the sampling rate of the rotational sensors and/or the accelerometer is also reduced. The SLEEP state can also be entered via an external command so that the user or another device can command the 3D pointing device 400 to enter the SLEEP state.

[0061] Upon receipt of another command, or if the 3D pointing device 400 begins to move, the device can transition from the SLEEP state to the WAKEUP state. Like the INACTIVE state, the WAKEUP state provides an opportunity for the device to confirm that a transition to the ACTIVE state is justified, e.g., that the 3D pointing device 400 was not inadvertently jostled.

[0062] The conditions for state transitions may be symmetrical or may differ. Thus, the threshold associated with the condition_active_—_inactivemay be the same as (or different from) the threshold(s) associated with the condition_inactive_—_active. This enables 3D pointing devices according to the present invention to more accurately capture user input. For example, exemplary embodiments which include a state machine implementation allow, among other things, for the threshold for transition into a stationary condition to be different than the threshold for the transition out of a stationary condition.

[0063] Entering or leaving a state can be used to trigger other device functions as well. For example, the user interface can be powered up based on a transition from any state to the ACTIVE state. Conversely, the 3D pointing device and/or the user interface can be turned off (or enter a sleep mode) when the 3D pointing device transitions from ACTIVE or STABLE to STATIONARY or INACTIVE. Alternatively, the cursor 410 can be displayed or removed from the screen based on the transition from or to the stationary state of the 3D pointing device 400.

[0064] As mentioned above, the STABLE state can be used to memorize tremor data. Typically, each user will exhibit a different tremor pattern. This property of user tremor can also be used to identify users. For example, a user's tremor pattern can be memorized by the system (either stored in the 3D pointing device 400 or transmitted to the system) during an initialization procedure wherein the user is requested to hold the 3D pointing device as steadily as possible for, e.g., 10 seconds. This pattern can be used as the user's unique signature to perform a variety of user interface functions. For example, the user interface can identify the user from a group of user's by comparing a current tremor pattern with those stored in memory. The identification can then be used, for example, to retrieve preference settings associated with the identified user. For example, if the 3D pointing device is used in conjunction with the media systems described in the above-incorporated by reference patent application, then the media selection item display preferences associated with that user can be activated after the system recognizes the user via tremor pattern comparison. System security can also be implemented using tremor recognition, e.g., access to the system may be forbidden or restricted based on the user identification performed after a user picks up the 3D pointing device 400.

[0065] In the exemplary embodiment of FIG. 4, the 3D pointing device 400 includes two rotational sensors 502 and 504, as well as an accelerometer 506. However, according to another exemplary embodiment of the present invention, a 3D pointing device can alternatively include just one rotational sensor, e.g., for measuring angular velocity in the z-axis direction, and an accelerometer. For such an exemplary embodiment, similar functionality to that described above can be provided by using the accelerometer to determine the angular velocity along the axis which is not sensed by the rotational sensor. For example, rotational velocity around the y-axis can be computed using data generated by the accelerometer and calculating:

[0066]

\begin{matrix} ω_{Y} = \frac{\partial θ_{Y}}{\partial t} = \frac{\partial}{\partial t} \tan^{- 1} (\frac{x}{z}) & (9) \end{matrix}

In addition, the parasitic acceleration effects that are not measured by a rotational sensor should also be removed. These effects include actual linear acceleration, acceleration measured due to rotational velocity and rotational acceleration, and acceleration due to human tremor.

[0067] According to yet another exemplary embodiment of the present invention, a user interface device uses only accelerometers. As shown in FIG. 9, a 3-D handheld device according to this exemplary embodiment of the present invention measures six degrees of freedom (6DOF), i.e., x, y, z, yaw, pitch, and roll. Although FIG. 9 shows Euler angles (yaw, pitch, and roll), those skilled in the art will appreciate that this exemplary embodiment invention also includes other representations, such as quaternion. A 6DOF device enables a natural mapping between the display and the user input. For example, to move the pointer up the user moves the handheld device up. Handheld devices according to this exemplary embodiment also make object selection more intuitive. For example instead of clicking a button, the user can move the handheld device towards or away from the screen. Instead of the common forward and back on-screen buttons, the user can, for example, simply tilt the mouse forward or back.

[0068] The advent of accurate and inexpensive accelerometers based upon micro-electromechanical systems (MEMS) makes it possible to bring this technology to the home consumer. Unlike gyroscopes that measure angular rotation, accelerometers measure linear acceleration. Traditional inertial navigation relies on three gyroscopes and three accelerometers, one each for the six degrees of freedom. Unfortunately, the cost and size of a traditional inertial navigation system are prohibitive for a consumer handheld. This exemplary embodiment of the handheld device uses a constellation of three three-dimensional accelerometers to determine its location and orientation at all times. However, other quantities and arrangements of accelerometers could be used with the same algorithm. For example, as shown in FIG. 4A, a handheld device according to another exemplary embodiment of the present invention measures six degrees of freedom (6DOF). i.e. x, y, z, yaw, pitch, and roll, in the manner just described, but with much greater precision. This is due to the use of four sets 512, 514, 516, and 518 of accelerometer devices, with each accelerometer device containing three accelerometers arranged mutually perpendicularly in the x, y, and z axes. This exemplary embodiment provides redundant measurements of linear and angular acceleration which are converted into pointer/cursor movement as described before.

[0069] The handheld device according to the FIG. 9 exemplary embodiment relies upon the basic geometric principle that three points determine a plane. Additional points may be added to improve accuracy, such as in the FIG. 4A exemplary embodiment. Acceleration common to all three mutually perpendicular accelerometers indicates that the whole handheld is accelerating (movement in x, y, or z). Acceleration differences between the three mutually perpendicular accelerometers indicate a change in orientation of the handheld (movement in yaw, pitch or roll).

[0070] Several principles complicate the implementation of a 6DOF accelerometer-based system. First, acceleration measurement errors produce a squared positional measurement error due to the double integration of acceleration to calculate position. Second, the gravity vector must be accurately tracked, since gravity is a constant acceleration vector that changes relative to the handheld orientation. Regarding measurement error, the MEMS accelerometers are not absolutely accurate, and error will be introduced into the calculation of position. However, linear inaccuracies in the acceleration are not important. Although the positional error is squared, devices according to this exemplary embodiment can use both an absolute and a relative coordinate system. For the relative coordinate system, actual distance traveled (as measured by feet or meters) can be adjusted arbitrarily using a sensitivity setting, e.g., like that commonly found on mouse drivers. However, non-linear errors over time and temperature that do not average to zero (also known as “drift”, a characteristic of the MEMS accelerometers) will result in a constant acceleration of the mouse. Without appropriate processing, the pointer for the stationary handheld would appear to accelerate off the screen. To make the calculation more difficult, quantization introduces measurement error when converting from the raw analog acceleration signal to the digital representation.

[0071] Devices according to this exemplary embodiment of the present invention include an algorithm with both linear and non-linear components to tolerate and correct for the known error patterns of the accelerometer as seen in FIG. 10. Therein, the accelerometer data samples 1000 are provided in, for example, a 3×3 matrix to an error filtering function 1010. The filtered values are then converted (block 1020) from units of volts/unit gravity (V/g) to units of acceleration (g) based on calibration data associated with scale and/or offset, for example as described with respect to above-described exemplary embodiments. The coarse acceleration data is refined in block 1030 by subtracting gravity values and acceleration errors associated with the handheld device's orientation as computed by blocks 1040 and 1050, respectively. Gravity is a constant acceleration that changes relative to the handheld device when it is tilted by the user. If gravity is misinterpreted as an actual acceleration, the on-screen pointer will accelerate indefinitely. A runaway pointer results in an unusable user interface. This exemplary embodiment uses vector manipulations to process the raw accelerometer data into an orientation. The gravity vector is then computed and subtracted from the results. Error from the gravity vector measurements is calculated and subtracted from future measurements. The refined acceleration values are then geometrically transformed at block 1060 based on the handheld's geometry. The output of block 1060 is then corrected for positional error estimation (blocks 1070 and 1080) before calculating an actual position determined based on acceleration data at block 1090. The position data can then be differentiated (block 1100) and subjected to non-linear processing at block 1110 prior to being output as velocity information. The geometric transform unit 1060 can also output data to the orientation determination unit 1020 which determines the handheld devices orientation in, e.g., a manner similar to that described above, to provide inputs to the orientation error estimation unit 1050 and gravity vector computation unit 1040 as well as outputting an indication of the handheld device's angular orientation.

[0072] The algorithm can optionally incorporate a user interaction model that takes advantage of normal user interface actions to recalibrate the handheld device as indicated by blocks 1130 and 1140. For example, a user typically stops moving the pointer before selecting an object, or “clicking”. In this mode, the handheld algorithm uses a weighted average of the readings during the specified period to provide recalibration input for both gravity and position.

[0073] This exemplary embodiment of the present invention allows for the algorithm processing to be performed on the handheld device for a self-contained solution or on a host machine. The link between the handheld device and the host machine can be any one of a number of technologies, including, but not limited to, RF, Bluetooth, Zigbee, and IR, some of which are illustrated in the exemplary block diagram hardware and software platforms in FIGS. 11 and 12, respectively. In a self-contained solution, the handheld device sends the processed position and orientation information to the host. When the host machine performs the algorithm processing, the handheld sends the raw acceleration data to the host. FIG. 13 illustrates this exemplary embodiment of the present invention from an algorithmic perspective. Therein, the grey triangle 1300 represents the handheld device having three accelerometers (dots) at its corners. The accelerometers are measuring acceleration of the handheld device as described above and indicated by, for example, the arrows A₀-A₃. The axes pairs 1302 and 1304 depict the current orientation of the handheld device locally and relative to an arbitrary point of reference, respectively.

[0074] The above-described exemplary embodiments are intended to be illustrative in all respects, rather than restrictive, of the present invention. Thus the present invention is capable of many variations in detailed implementation that can be derived from the description contained herein by a person skilled in the art. For example, although the foregoing exemplary embodiments describe, among other things, the use of inertial sensors to detect movement of a device, other types of sensors (e.g., ultrasound, magnetic or optical) can be used instead of, or in addition to, inertial sensors in conjunction with the aforedescribed signal processing. All such variations and modifications are considered to be within the scope and spirit of the present invention as defined by the following claims. No element, act, or instruction used in the description of the present application should be construed as critical or essential to the invention unless explicitly described as such. Also, as used herein, the article “a” is intended to include one or more items.

Claims

What is claimed is:

1. A user interface device comprising:

a housing;

at least four accelerometer devices arranged in a non-coplanar configuration in said housing, each of said at least four accelerometer devices outputting respective accelerometer data; and

a processing unit in said housing comprising an algorithm that translates said accelerometer data from each of said at least four accelerometer devices into two-dimensional pointer movement,

wherein said algorithm reduces error by bounding device movement based on user movement characteristics.

2. The user interface device in claim 1 wherein each accelerometer device contains two accelerometers.

3. The user interface device in claim 1 wherein each accelerometer device contains three accelerometers.

4. The user interface device of claim 1 wherein said bounding device movement is performed using an extent of user movement for at least one of user's fingers, wrist, arm, and shoulder.

5. The user interface device of claim 1 wherein said bounding device movement is performed using user tremor.

6. The user interface device of claim 1 wherein said algorithm further interprets gestures to produce mouse buttons clicks.

7. The user interface device of claim 1 wherein said algorithm further interprets gestures to produce keystrokes or operating system messages.

8. A user interface device comprising:

a housing;

at least four accelerometer devices arranged in a non-coplanar configuration in said housing, each of said at least four accelerometer devices outputting respective accelerometer data,

wherein each accelerometer device contains three accelerometers; and

a processing unit in said housing comprising an algorithm with linear and non-linear components that translates said accelerometer data from each of said at least four accelerometer devices into two-dimensional pointer movement,

wherein said algorithm with linear and non-linear components reduces error introduced by gravitational drift, temperature drift and user created tremor accelerations.

9. The user interface device of claim 8, wherein said algorithm with linear and non-linear components includes a user interaction model to recalibrate said user interface device.

10. The user interface device of claim 8, wherein a user is recognized based upon user tremor pattern comparison.

11. The user interface device of claim 10, wherein user preferences are activated when said user is recognized based upon user tremor pattern comparison.

Patent Citations (67)

Patent	Date	Inventor	Cited By
US4787051(A)	1988-11-01	Olson	Applicant
US4839838(A)	1989-06-01	LaBiche et al.	Applicant
US5045843(A)	1991-09-01	Hansen	Applicant
US5128671(A)	1992-07-01	Thomas, Jr.	Examiner
US5138154(A)	1992-08-01	Hotelling	Applicant
US5181181(A)	1993-01-01	Glynn	Applicant
US5359348(A)	1994-10-01	Pilcher et al.	Applicant
US5396265(A)	1995-03-01	Ulrich et al.	Applicant
US5440326(A)	1995-08-01	Quinn	Applicant
US5453758(A)	1995-09-01	Sato	Applicant
US5484355(A)	1996-01-01	King, II et al.	Applicant
US5506605(A)	1996-04-01	Paley	Applicant
US5645077(A)	1997-07-01	Foxlin	Examiner
US5698784(A)	1997-12-01	Hotelling et al.	Applicant
US5703623(A)	1997-12-01	Hall et al.	Applicant
US5796354(A)	1998-08-01	Cartabiano et al.	Applicant
US5819206(A)	1998-10-01	Horton et al.	Applicant
US5825350(A)	1998-10-01	Case, Jr. et al.	Applicant
US5835156(A)	1998-11-01	Blonstein et al.	Applicant
US5898421(A)	1999-04-01	Quinn	Applicant
US5912612(A)	1999-06-01	DeVolpi	Applicant
US5955988(A)	1999-09-01	Blonstein et al.	Applicant
US6002394(A)	1999-12-01	Schein et al.	Applicant
US6016144(A)	2000-01-01	Blonstein et al.	Applicant
US6049823(A)	2000-04-01	Hwang	Applicant
US6069594(A)	2000-05-01	Barnes et al.	Applicant
US6115028(A)	2000-09-01	Balakrishnan et al.	Applicant
US6164808(A)	2000-12-01	Shibata et al.	Applicant
US6191774(B1)	2001-02-01	Schena et al.	Applicant
US6369794(B1)	2002-04-01	Sakurai et al.	Applicant
US6400996(B1)	2002-06-01	Hoffberg et al.	Applicant
US6466198(B1)	2002-10-01	Feinstein	Examiner
US6466831(B1)	2002-10-01	Shibata et al.	Applicant
US6473713(B1)	2002-10-01	McCall et al.	Applicant
US6492981(B1)	2002-12-01	Stork et al.	Applicant
US6544126(B2)	2003-04-01	Sawano et al.	Applicant
US6650313(B2)	2003-11-01	Levine et al.	Applicant
US6672962(B1)	2004-01-01	Ozaki et al.	Applicant
US6753849(B1)	2004-06-01	Curran et al.	Applicant
US6757446(B1)	2004-06-01	Li et al.	Applicant
US6766456(B1)	2004-07-01	McKeeth	Examiner
US6929548(B2)	2005-08-01	Wang	Applicant
US6933923(B2)	2005-08-01	Feinstein	Applicant
US6984208(B2)	2006-01-01	Zheng	Examiner
US6990639(B2)	2006-01-01	Wilson	Applicant
US6998966(B2)	2006-02-01	Pedersen et al.	Applicant
US7098891(B1)	2006-08-01	Pryor	Applicant
US7173604(B2)	2007-02-01	Marvit et al.	Examiner
US7262760(B2)	2007-08-01	Liberty	Applicant
US2002/0130835(A1)	2002-09-01	Brosnan	Examiner
US2002/0158843(A1)	2002-10-01	Levine et al.	Applicant
US2003/0107551(A1)	2003-06-01	Dunker	Applicant
US2003/0193572(A1)	2003-10-01	Wilson et al.	Applicant
US2004/0095317(A1)	2004-05-01	Zhang et al.	Applicant
US2004/0193413(A1)	2004-09-01	Wilson et al.	Applicant
US2004/0204240(A1)	2004-10-01	Barney	Applicant
US2004/0229693(A1)	2004-11-01	Lind et al.	Applicant
US2004/0239626(A1)	2004-12-01	Noguera	Applicant
US2004/0268393(A1)	2004-12-01	Hunleth et al.	Applicant
US2005/0125826(A1)	2005-06-01	Hunleth et al.	Applicant
US2005/0212767(A1)	2005-09-01	Marvit et al.	Applicant
US2005/0243061(A1)	2005-11-01	Liberty et al.	Applicant
US2005/0243062(A1)	2005-11-01	Liberty	Applicant
US2005/0253806(A1)	2005-11-01	Liberty et al.	Applicant
US2006/0028446(A1)	2006-02-01	Liberty et al.	Applicant
US2006/0092133(A1)	2006-05-01	Touma et al.	Applicant
WO178055(A1)	2001-10-01		Applicant

Non-Patent Literature (42)

Navarrete, P., et al., “Eigensapce-based Recognition of Faces: Comparisons and a new Approach,” Image Analysis and Processing, 2001, pp. 1-6.Applicant
Jakubowski, J., et al., “Higher Order Statistics and Neural Network for Tremor Recognition,” IEEE Transactions on Biomedical Engineering, vol. 49, No. 2, Feb. 2002, pp. 152-159.Applicant
Liu, C., et al., “Enhanced Fisher Linear Discriminant Models for Face Recognition,” Proc. 14th International Conference on Pattern Recognition, Queensland, Australia, Aug. 17-20, 1998, pp. 1-5.Applicant
International Search Report for PCT/US05/15096, mailed May 15, 2006.Applicant
Written Opinion for PCT/US05/15096, mailed May 15, 2006.Applicant
International Search Report for PCT/US04/35369, mailed May 11, 2006.Applicant
Written Opinion for PCT/US04/35369, mailed May 11, 2006.Applicant
Geen, J., et al., “New iMEMS Angular-Rate-Sensing Gyroscope,” Analog Dialogue, 37-03 (2003), pp. 1-4.Applicant
W. T. Ang, et al., “Design and Implementation of Active Error Canceling in Hand-held microsurgical Instrument” Proceedings of the 2001 IEEE/RSJ International Conference on Intelligent Robots and Systems, vol. 2, Oct. 2001, pp. 1106-1111.Applicant
W. T. Ang, et al., “Design of All-Accelerometer Inertial Measurement Unit for Tremor Sensing in Hand-held Microsurgical Instrument,” Proceedings of the 2003 IEEE International Conference on Robotics & Automation, Sep. 2003, pp. 1781-1786.Applicant
J. Jakubowski, et al., “Increasing Effectiveness of Human Hand Tremor Separation Process by Using Higher-Order Statistics,” Measurement Science Review, vol. 1, No. 1, 2001, pp. 43-46.Applicant
J. Raethjen, et al., “Tremor Analysis in Two Normal Cohorts,” Clinical Neurophysiology 115, 2004, pp. 2151-2156.Applicant
C. N. Riviere, et al., “Adaptive Canceling of Physiological Tremor for Improved Precision in Microsurgery,” IEEE Transactions on Biomedical Engineering, vol. 45, No. 7, Jul. 1998, pp. 839-846.Applicant
C. N. Riviere, et al., “Toward Active Tremor Canceling in Handheld Microsurgical Instruments,” IEEE Transactions on Robotics and Automation, vol. 19, No. 5, Oct. 2003, pp. 793-800.Applicant
J. Timmer, et al., “Characteristics of Hand Tremor Time Series,” Biological Cybernetics, vol. 70, 1993, pp. 75-80.Applicant
J. Timmer, et al., “Cross-Spectral Analysis of Physiological Tremor and Muscle Activity: I Theory and application to Unsynchronized Electromyogram,” Biological Cybernetics, vol. 78, 1998, pp. 349-357.Applicant
J. Timmer, et al., “Cross-Spectral Analysis of Physiological Tremor and Muscle Activity: II Application to Synchronized Electromyogram,” Biological Cybernetics, vol. 78, 1998, pp. 359-368.Applicant
J. Timmer, “Modeling Noisy Time Series: Physiological Tremor,” International Journal of Bifurcation and Chaos, vol. 8, No. 7, 1998, pp. 1505-1516.Applicant
J. Timmer, et al., “Cross-Spectral Analysis of Tremor Time Series,” International Journal of Bifurcation and Chaos, vol. 10, No. 11, 2000, pp. 2595-2610.Applicant
J. Timmer, et al., “Pathological Tremors: Deterministic Chaos or Nonlinear Stochastic Oscillators?” Chaos, vol. 10, No. 1, Mar. 2000, pp. 278-288.Applicant
V. Digalakis, et al., “ML Estimation of a Stochastic Linear System with the EM Algorithm and Its Application to Speech Recognition,” IEEE Transactions on Speech and Audio Processing, vol. 1, No. 4, Oct. 1993, pp. 431-442.Applicant
S. Haykin, et al., “Adaptive Tracking of Linear Time-Variant Systems by Extended RLS Algorithms,” IEEE Transactions on Signal Processing, vol. 45, No. 5, May 1997, pp. 1118-1128.Applicant
B. F. La Scala, et al., “Design of an Extended Kalman Filter Frequency Tracker,” IEEE Transactions on Signal Processing, vol. 44, No. 3, Mar. 1996, pp. 739-742.Applicant
K. Nishiyama, “Robust Estimation of a Single Complex Sinusoid in White Noise—H∞ Filtering Approach,” IEEE Transactions on Signal Processing, vol. 47, No. 10, Oct. 1999, pp. 2853-2856.Applicant
K. Nishiyama, “A Nonlinear Filter for Estimating a Sinusoidal Signal and its Parameters in White Noise: On the Case of a Single Sinusoid,” IEEE Transactions on Signal Processing, vol. 45, No. 4, Apr. 1997, pp. 970-981.Applicant
B. Widrow, et al., “Fundamental Relations Between the LMS Algorithm and the DFT,” IEEE Transactions on Circuits and Systems, vol. 34, No. CAS-7, Jul. 1987, pp. 814-820.Applicant
A. H. Sayed, “A Framework for State-Space Estimation with Uncertain Models,” IEEE Transactions on Automatic Control, vol. 46, No. 7, Jul. 2001, pp. 998-1013.Applicant
Website: J. Timmer, “Data Analysis and Modeling of Dynamic Processes in the Life Sciences,” Freiburg Center for Data Analysis and Modeling, http://webber.physik.uni-freiburg.de/˜jeti/, retrieved Aug. 17, 2007, pp. 1-2.Applicant
Website: “Freiburg Center for Data Analysis and Modeling—Publications,” http://www.fdm.uni-freiburg.de/cms/puplications/publications/, retrieved Aug. 17, 2007, pp. 1-11.Applicant
Website: C. Riviere, Robotics Institute, http://www.ri.cmu.edu/people/riviere—cameron.html, retrieved Aug. 17, 2007, pp. 1-4.Applicant
Website: A. Beuter, Publications, University of Quebec at Montreal, http://www.er.uqam.ca/nobel/r11040/publicat.htm, retrieved Aug. 17, 2007, pp. 1-7.Applicant
Website: R. Murray-Smith, Hamilton Institute, http://www.dcs.gla.ac.uk/˜rod/, retrieved Aug. 17, 2007, pp. 1-5.Applicant
Website: Z. Jian, et al., “Adaptive Noise Cancellation,” Rice University, http://www.ece.rice.edu/˜klwang/elec434/elec434.htm, retrieved Aug. 17, 2007, pp. 1-6.Applicant
Website: A. H. Sayed, “UCLA Adaptive Systems Laboratory-Home Page,” UCLA, http://asl.ee.ucla.edu/index.php?option=com—frontpage&itemid=1, retrieved Aug. 17, 2007, p. 1.Applicant
International Search Report for PCT/US05/15051 mailed Feb. 19, 2008.Applicant
Written Opinion for PCT/US05/15051 mailed Feb. 19, 2008.Applicant
Office Action for Chinese Application No. 200580021163.7 mailed Jan. 25, 2008.Applicant
International Search Report for PCT/US05/42558 mailed Nov. 30, 2006.Applicant
Written Opinion for PCT/US05/42558 mailed Nov. 30, 2006.Applicant
Appendices A, B and C, from U.S. Patent No. 6,069,594 to Barnes et al., pp. 1-104, May 30, 2000.Applicant
Supplemental European Search Report for Application No. EP 05 74 4089 mailed Mar. 6, 2008.Applicant
Supplemental European Search Report for Application No. EP 04 79 6360 mailed Apr. 2, 2008.Applicant

Abstract

Description

Related Applications

Background

Summary

Brief Description of the Drawings

[0012] The accompanying drawings illustrate exemplary embodiments of the present invention, wherein:

[0013] FIG. 1 depicts a conventional remote control unit for an entertainment system;

[0014] FIG. 2 depicts an exemplary media system in which exemplary embodiments of the present invention can be implemented;

[0015] FIG. 3 shows a 3D pointing device according to an exemplary embodiment of the present invention;

[0016] FIG. 4 illustrates a cutaway view of the 3D pointing device in FIG. 4 including two rotational sensors and one accelerometer;

[0018] FIG. 5 is a block diagram illustrating processing of data associated with 3D pointing devices according to an exemplary embodiment of the present invention;

[0019] FIGS. 6(a)-6(d) illustrate the effects of tilt;

[0020] FIG. 7 depicts a hardware architecture of a 3D pointing device according to an exemplary embodiment of the present invention;

[0021] FIG. 8 is a state diagram depicting a stationary detection mechanism according to an exemplary embodiment of the present invention;

[0022] FIG. 9 illustrates six degrees of freedom associated with another exemplary embodiment of the present invention;

[0023] FIG. 10 depicts an algorithm for processing acceleration data according to another exemplary embodiment of the present invention;

[0024] FIG. 11 depicts a hardware architecture of a 3D pointing device according to the exemplary embodiment of FIG. 10;

[0025] FIG. 12 depicts a software architecture of a 3D pointing device according to the exemplary embodiment of FIG. 10; and

[0026] FIG. 13 shows the exemplary embodiment of FIGS. 9 and 10 from an algorithmic perspective.

Detailed Description

[0048]

\begin{matrix} θ = \tan^{- 1} (\frac{y}{z}) & (7) \end{matrix}

[0049]

\begin{matrix} R = [\begin{matrix} \cos θ \sin θ \\ - \sin θ \cos θ \end{matrix}] \cdot [\begin{matrix} α y \\ α z \end{matrix}] & (8) \end{matrix}

to rotate the converted/calibrated inputs ay and az to compensate for the tilt θ.

[0066]

\begin{matrix} ω_{Y} = \frac{\partial θ_{Y}}{\partial t} = \frac{\partial}{\partial t} \tan^{- 1} (\frac{x}{z}) & (9) \end{matrix}