Patent Application
20120208639
1. Field of Invention
The invention is generally related to the area of man machine interface for electronic devices, and more particularly:
2. Description of Related Art
In the industrial design of man-machine interaction, user interface is a space where interaction between humans and machines occurs. The goal of man-machine interaction is to produce a user interface which makes it easy, efficient, and enjoyable to operate a machine in the way which produces the desired result. This generally means that an operator needs to provide minimal input to achieve the desired output, and also that the machine minimizes undesired outputs to the human. The design considerations applicable when creating practical user interfaces are related to or involve such disciplines as ergonomics and psychology.
A touch-screen is one of the most successful man-machine interfaces ever designed and is mostly commonly seen on many electronic devices. They are present in devices such as computers, tablets, and smart phones. A touch-screen is an electronic visual display that can detect the presence and location of a touch within the display area of the touch-screen. The term generally refers to touching the display of the device with a finger or hand. A touch-screen device can also sense other passive objects, such as a stylus.
In some applications, it is desired to control a touch-screen device remotely through the use of a hand-held motion sensitive controller, where that motion sensitive controller may include a combination of the following sensors:
1) accelerometers;
2) gyroscopes;
3) electronic compasses or magnetometers;
4) buttons;
5) joysticks;
6) microphones,
and transmitters:
1) light emitting diodes;
2) wireless communication devices.
Likewise, the input device for remotely controlling a touch-screen device might include control signals coming from a 2D camera, or a 3D camera such as stereoscopic imaging from two cameras, or a single time of flight-based camera.
It may be desirable to connect a touch-screen controlled device to a large-screen television and control some or all of its functions from the comfort of a couch while the graphical output of the device is displayed on the large screen. Similarly, it may be desirable to remotely control some or all of the functions of a smart television (supporting a broader range of content, including videos, games, applications originally configured for touch-screen devices, web browsing, and etc.). In this case, a desirable interaction with the device is not the touch-screen of the device, but an alternate (non-touch-screen) device. However, modules (e.g., software components) running on the controlled device may need to receive touch-surface-like signals (or signals customarily derived from touch-surface-like signals) in order to control their functions. Thus there is a need for techniques that facilitate such an alternate device to readily control the controlled device or the modules running thereon with or without a touch-screen device coupled thereto.
This section summarizes some aspects of the present disclosure and briefly introduces some preferred embodiments. Simplifications or omissions in this section as well as in the abstract or the title of this description may be made to avoid obscuring the purpose of this section, the abstract and the title. Such simplifications or omissions are not intended to limit the scope of the present disclosure.
Generally speaking, this invention describes techniques for using a variety of motion sensitive inputs to remotely control an existing electronic device or system (a.k.a., controlled device or controlled system), which is running applications previously configured for taking inputs from a pre-defined controlling device (such as a particular touch-screen device). Output signals from the input device may be in a different form from the pre-defined controlling device. The output signals may be generated by a motion sensitive controller, a 2D or 3D camera, or a combination thereof. According to one aspect of the present invention, the controlled device is designed to respond to signals from a touch screen or touch screen-like signals. Examples of these controlled devices include but are not limited to electronic consumer devices (e.g., TVs and entertainment devices) including a large display, where the devices may be or may not be coupled to smart phones and tablet PCs. The output signals from the input device are motion sensitive inputs to a controlled device and converted into touch-screen like signals that are then sent to the controlled device or programs being executed in the controlled device, subsequently causing the behavior of the controlled device to change or respond thereto, without reconfiguration of the applications running on the controlled device.
According to another aspect of the present invention, signals from the motion controller include sensor signals some or all of which are generated from inertial sensors enclosed in the motion controller. The signals are converted to a set of control signals including some signals substantially similar to the signals from a touch-screen device to subsequently control the controlled device. Depending on implementation, the control signals may include translational and angular positions of the motion controller with respect to the controlled device, and a series of interactions by a user with the motion controller. In one case, the control signals may include output signals from other motion controllers (used by the same user or a different user).
According to another aspect of the present invention, signals from the input device include sensor signals some or all of which are generated from one or more cameras which may be located on or near the controlled device. The image signals are converted to a set of control signals including some signals substantially similar to the signals from a touch screen device to subsequently control the controlled device. Depending on implementation, the control signals may be computed by transforming or projecting the 2D or 3D image plane to a virtual touch pad, and transmitting the “touched” positions of that virtual touch pad.
The present invention may be implemented as a method, an apparatus of a part of a device or a software module to be executed in a designated device. According to one embodiment, the present invention is a system for motion-based control, the system comprises a controlled device including at least one application preconfigured to be responsive to input signals from a touch-screen device; an input device including a plurality of sensors generating sensor signals responsive to human motion; and a processing unit configured to facilitate the input device to control the at least one application on the controlled device by converting the sensor signals from the input device to a second set of signals, the second set of signals including some signals substantially similar to the touch-screen input signals from the touch-screen device.
According to another embodiment, the present invention is a method for motion-based control of a controlled device, the method comprises generating a control signal from an input device, the control signal including sensor signals from a plurality of sensors responsive to human motion, causing the control signal to be received by a controlled device including at least one application preconfigured to be responsive to input signals from a touch-screen device, converting the control signal from the input device to a first set of signals including some signals substantially similar to the touch-screen input signals from the touch-screen device, and causing the device to be responsive to the control signal.
One of the objects, advantages and benefits of the present invention is to enable an alternative device (e.g., a motion controller) or input mechanism to control applications on a controlled device originally designed to be working with a predefined device (e.g., a touch-screen device).
Other objects, advantages and benefits of the present disclosure will become more apparent from the following detailed description of preferred embodiment when taken in conjunction with the accompanying drawings.
These and other features, aspects, and advantages of the present invention will become better understood with regard to the following description, appended claims, and accompanying drawings where:
The detailed description of the invention is presented largely in terms of procedures, steps, logic blocks, processing, and other symbolic representations that directly or indirectly resemble the operations of data processing devices. These process descriptions and representations are typically used by those skilled in the art to most effectively convey the substance of their work to others skilled in the art. Numerous specific details are set forth in order to provide a thorough understanding of the present invention. However, it will become obvious to those skilled in the art that the invention may be practiced without these specific details. In other instances, well known methods, procedures, components, and circuitry have not been described in detail to avoid unnecessarily obscuring aspects of the present invention.
Reference herein to “one embodiment” or “an embodiment” means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one embodiment of the invention. The appearances of the phrase “in one embodiment” in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. Further, the order of blocks in process flowcharts or diagrams representing one or more embodiments of the invention do not inherently indicate any particular order nor imply any limitations in the invention.
As used herein, a (user) input device is a control or controlling device that allows a user to interactively control some or all of the functions of another device. Some common examples of a controlling device include: mice, keyboards, joysticks, touch sensitive surfaces, motion controllers (such as the Wii Remote™, or PlayStation Move controller, and air mice) and television remote controllers. Passive sensors, such as video cameras and microphones are also examples of user input devices. The controlling device used in the present invention is largely related to a controller including a plurality of inertial sensors, where the controller generates a control signal including sensor signals from the inertial sensors and signals from other sources (e.g., a joystick, an action button or detected positions of a finger in a grid).
A controller, a controlling device and an input device are interchangeably used herein, a relative term with respect to a controlled device. An example of such an input device includes, but may not be limited to, a (video game) controller originally designed for video gaming, a smart phone (e.g., iPhone) with at least one inertial sensor, and a portable computing device producing sensor signals. As a result of some actions from the user, signals are transmitted from an input device to a controlled device in order to cause a change in the behavior of the controlled device or system. There are many examples of controlled devices. Some common examples include various combinations of: video game systems, televisions, digital video recorders (DVRs), DVD players, video cassette recorders, personal computers, laptop computers, tablet computers, home audio systems, cell phones, smart phones, personal music players, graphical displays, and projected graphics systems. Commonly, these controlled devices run modules (e.g., software components) that receive signals from designated input devices, or indirectly process the signals received from the input devices. Some examples of such software components include: applications, games, operating systems, drivers, firmware, kernels, user interface (APIs), and etc. These software components are configured to ‘listen for and respond to signals of specific types. Broadly, these signals may be categorized as either:
More broadly, these devices may be categorized by type and designed to listen for, and respond to, signals of specific types. In this way, a device, such as a trackball, may be used in place of a mouse by implementing a communication protocol (such as USB 1.1) through which it is indicated that the device is “mouse-like” and subsequently provides “mouse-like” button-presses and change of position signals.
As a result of the actions by a user, signals are transmitted from the user input device to a controlled device in order to cause a change in the behavior of the controlled device. Commonly, these abstract signals are provided as a convenience to application programmers who are freed from having to consider a large variety of possible input devices. In this way it is possible, by the implementation of a software component (such as a “driver”), to map signals from new alternative input devices providing new (a-priori unknown) categories of input signal into the “listened-for” signals expected by the software components. In this way, the provision is made by operating system makers or API developers to write and install software components that output signals received from a conceivable source and subsequently use the signals to control existing applications.
However, these existing models do not meet some practical needs in a satisfactory manner. Applications are usually written to ‘listen-for’ signals of a particular type (e.g. “touch-surface-like”). For example, in the case of the Android operating system, there are many applications that have been written for it. Presently, the majority of Android devices use a touch-screen as the primary mode of user input, and applications (and other software components) are often written specifically to ‘listen-for’ touch-surface-like signals.
If one wishes to control all the touch-surface functions of the controlled device using a new and non “touch-surface-like” input device, such as a motion sensitive device or controller, there are practical problems that must be overcome. For example, many software components are written to “listen-for” and respond specifically to “touch-surface-like” signals. Similarly, software components may be written to “listen-for” higher level signals, such as “Zoom-In” or “Scroll-Down” signals which are generated indirectly by additional software components (such as an operating systems, drivers, APIs, etc. . . . ) similarly expecting (or “listening for”) “touch-surface-like” signals. The type of acceptable and expected input may be coupled into existing software components by various means including: (a) its design, (b) through the use of a compiler; or (c) through its dependence upon one or more additional software components (e.g.: a driver, operating system, APIs).
These input devices may not be “touch-surface-like” devices or readily provide “touch-surface-like” signals. In particular, according to one embodiment, none of the sensors in an input device directly or obviously provide touch-surface-like signals. Their application and use in lieu of a touch-surface-like input device are therefore not easily implemented or conceived of.
One aspect of this invention is related to the transformation of sensor signals from an input device into touch-surface-like signals. Touch-surface-like signals contain information representing 2D coordinates on a 2D surface. In one embodiment, an input device is being used by a user to point directly at items shown on a graphical display and configured to estimate the pointed position (e.g., being the intersection of the major axis of the device and the graphical display). Such estimation of the pointed position is referred to as ‘drift-free’ ‘down-the-barrel’ pointing. Signals for the such drift-free down-the-barrel pointing are a suitable source of ‘touch-screen-like’ signals because a user can directly correlate the position of orientation of a hand-held device with a position and orientation on a display without the need for graphical feedback (e.g.: a graphical mouse-pointer, crosshair or cursor).
Some of the objects, benefits and advantages of the present invention may be appreciated in the following exemplary applications. First, in the case of a mouse-like device, a mouse is not capable of providing “down the barrel” pointing signals as mouse-like devices provide a measure of linear velocity in a 2D plane but not an absolute position on 2D plane. Additionally, a mouse provides “mouse-like-signals” received by applications listening for “mouse-like-signals”. A source of such “mouse-like-signals” may not directly be used with software listening for “touch-surface-like” signals. Furthermore, a user cannot reliably correlate the physical position of a mouse with a position on a graphical display without the use of graphical feedback (e.g. a mouse-pointer);
Second, further to the need for graphical feedback, mouse-like-devices (devices providing sources of mouse signals) also differ in that they are a source of a single stream of 2D values, whereas multi-touch surfaces may generate multiple streams of 2D values. One aspect of this invention is the use of a controlling device contemplated in the present invention to provide multi-touch-like signals. Third, In the case of an air mouse, a point on a plane is determined through the integration over time of angular orientation signals from a gyroscope to obtain a relative measure of the angular position. This measure is subsequently transformed into a point on a 2D plane. Drawbacks of this approach are that:
After an initial calibration step, such as the measurement of the orientation of the input device while the device is pointed at a graphical display, it may be initially possible to provide down-the-barrel pointing. However, over-time, due to the above drawbacks, the accumulation of deduced reckoning errors (or “drift”), or other limitations of the device sensors (e.g., railing (“maxing out”), scaling errors, non-linearity, or offset errors) mean that calculated orientation of the device may eventually be misaligned with its actual orientation. These drawbacks make gyroscope air-mouse devices unsuitable for applications in which one would like “drift free” “down-the-barrel pointing” without the need for graphical feedback. In one embodiment, an input device is configured to overcome the limitation by continuous recalibration with respect to a fixed reference. In one embodiment, the fixed reference is an electronic compass. In another embodiment, the fixed reference is an external camera. Furthermore, it has not been previously conceived that such a motion sensitive device can provide usable “touch-surface-like” signals (which, among other attributes, represent absolute positions on a 2D surface) which are qualitatively different from “mouse-like” signals (e.g., 2D velocity). “Touch-surface-like” signals have additional characteristics not shared by “mouse-like” signals. These additional characteristics include the ability to distinguish tracing a path along a set of points and individually touching those points in sequence as well as the ability to touch multiple points at once on some devices (a.k.a., multi-touch”).
In the case of the motion sensitive Wii Remote controller, an unstable form of down the barrel pointing is achieved. However, in order to do so, the device contains an infra-red sensitive camera to detect the location of infra-red LEDs near a graphical display. As described herein, one embodiment of the present invention does not require the use of a camera in the handheld device or LEDs at the display.
In the case of the motion-sensitive PlayStation Move™ controller:
Examples of external game controllers containing joysticks and buttons, such as the Zeemote™, are already used to control software components running on touch-screen devices. However, the signals from game controller devices are not used in place of touch-screen-signals, but are instead provided as joystick-like, game-controller-like or direction-pad-like signals and usable only by the subset of software components that explicitly listen for those types of signals. In contrast, one aspect of this invention is the ability to provide an alternative source of touch surface signals that can be used to control all of the functions of software components listening to touch-surface-like signals.
Another aspect of this invention relates to the transformation of joystick and button signals to replace or augment a touch surface. A touch surface is commonly overlaid over a graphical display. The position of a touch is highly important, as is the association of the touched position with respect to the frame of the graphical display. In the case of an alternative input device, visual feedback to the user to indicate where on the graphical display an action will occur or has occurred may be missing, neither might there be a provision in an operating system of the device or application to receive the signals from the alternative input device and present them graphically.
Still another aspect of this invention is the graphical presentation of a pointed position of an alternative input device on the display. This aspect differs from:
There may be no single transformation of signals from a new input device that works appropriately as input for a multitude of contexts (e.g., home screens, settings for a display screens, games, operating system functions, etc.) without the knowledge of which transformation should be applied in which context. For one software component, one may desire to use a joystick in order to cause a touch-surface-like signal that simulates the touching of the surface at a specific location in order to simulate the press of a graphical on-screen button. For a different software component, the joystick signals may be transformed to cause the scrolling of an on-screen list by the generation of a time-series of touch-surface-like signals that simulate the signals of an upwards stroke of the touch surface. In either case, the sending of the signals for one case in the context of the other may yield undesired effects.
More broadly, this aspect of the present invention differs from related art concerning the transformation of signals from one type into another in that:
Generally speaking, this invention describes techniques for using a motion controller as an input device for an existing electronic device, the controlled device, running applications previously configured for taking inputs in a different form. The signals from the input device may be in a different form from the controlling device. According to one aspect of the present invention, the controlled device was designed to host applications that respond to signals from a touch screen or touch screen-like signals. The inputs from the motion controller are converted into touch-screen like signals that are then sent to the controlled device or programs being executed in the controlled device to cause the behavior of the controlled device to change or respond thereto.
Referring now to the drawings,
In one embodiment, the controlling device 101 includes motion sensors (not shown) and none, one or more LEDs that are housed in a body intended to be hand held by a user 109, shown here in his or her living room, seated comfortably on a couch 110. For this purpose, in one embodiment, the controlling device 101 also contains a communication device and a self-contained power source. This communication device is a Bluetooth radio device in one embodiment, but could be replaced by an infra-red communication device or any other form of wireless communication device in alternate embodiments. In one embodiment, a rechargeable battery is used as the power source.
In another embodiment, the motion signals of the controlling device 101 may be replaced or complemented by signals derived from an external camera that is not attached to the controlling device 101, along with one or more LEDs or other point light sources on the controlling device 101 in view of the camera and the motion sensors in the controlling device 101.
The controlling device 101 may also be interchangeably referred to herein as a motion controller when describing various embodiments. In one embodiment, the controlled device 102 is an electronic device configured to execute some modules (e.g., software components) communicating with or controlled by at least a touch-sensitive input device (e.g. a touch screen) or touch-surface-like input device signals (e.g., the touch surface input device 104). Examples of the touch-sensitive input devices include resistive or capacitive touch panels over a graphical display. Two examples, a smart phone with a touch screen 201 and a tablet computer 202, are shown in
The controlled device 102 may be additionally controlled by any combination of button sensors, keyboard or keypad inputs, joystick sensors, camera or video inputs, microphone inputs, or motion sensors. In one embodiment, the controlled device 102 includes a large display 103 such as a television, computer monitor, or projected display device along with at least one touch surface input device 104 attached directly to the display 103 by means of a cable 105, such as an HDMI cable. In another embodiment 300 shown in
In yet another alternate embodiment 400 shown in
In each of the embodiments shown in
Signals from the controlling devices 604-607 are used to control software components running in the controlled system 603. The software components are configured to listen for signals of particular types or identifiable categories. Examples include:
In each case, the source of the signals may be unknown, but the software components running in the controlled system are configured to “listen-for” or are otherwise controlled by signals of specific types or of identifiable categories. As used herein, signals that are “X-like” are referred to as the signals received by the software components that cause the behavior change of the device running the software components as if the device is controlled by an input device X, but not necessarily originating from the device X.
One aspect of this invention is to allow one or more software components to be controlled by signals of specific types or of identifiable signal categories:
in the absence of the physical device of the indicated category; and/or
in addition to the physical device of the indicated category; and/or
as an alternative mechanism to the physical device of the indicated category.
As an example, in one embodiment of this invention, the invention permits the remote control of a plurality of software components running on a controlled device, where a touch screen is the primary source of input, and the software components are controllable by the touch screen or touch-surface-like signals.
The controlling device(s) may be used as a method to control those software components by transforming its signals (being not touch-surface-like) into touch-surface-like signals usable to control those software components.
Depending on implementation, a wide variety of transformations are possible and appropriate for the categories of input signals available from the controlling device and categories of signals the software components in the controlled device are responsive to. Exemplary transformations include:
There are many parts of a user that could be tracked in place of a finger, for example, a hand, or a pen, or an LED on the tip of a motion controlled device that is on when pressed, and off when not pressed. The material elements to this embodiment is the formation of a virtual window 803 and camera-based tracking of an object to create a virtual touchpad that can be used to augment or replace the control signals being used to drive the controlled device.
In another embodiment, the transformation occurs on the controlling device and the output signals thereof are transmitted directly to the controlled device. In a preferred embodiment, the controlled device is a network-enabled television, being a device capable of receiving and showing video received from an Internet source, or running games, or other networked applications. In the exemplary embodiment shown in
In one embodiment of this invention shown in
One embodiment of this invention is a method for transforming sensor signals from a motion controller, when used as described above, into touch-surface-like signals. The graphical display shows a “pointed position” as an on-screen element (such as a cursor). The pointed position follows the motion of the motion device by the transformation of the motion signals from the motion device into points on a 2D plane.
There are several methods for transforming the motion signals of the controller into positions on the screen exist. In one embodiment, the inventors use a ray-casting method as described in co-pending U.S. application Ser. No. 12/835,750 which is hereby incorporated by reference. In order to properly achieve “Down the Barrel” pointing, two main kinds of information are needed. First, an accurate absolute orientation of the controller in the world frame is derived, where the world frame is defined with respect to the direction of the gravity field of the Earth and magnetic north. Second, a mapping from the reference frame of the controller to the display is defined. This mapping includes the relative position of the display in relation to the controller as well as the relative rotation of the display with respect to the world frame. This second set of information can be obtained with an initial setup calibration stage. One method of doing this is described in the co-pending U.S. application Ser. No. 12/835,750, where the user points at multiple positions on the display screen with the controller in order to establish the mapping.
In one embodiment, the controlling device generates sensor signals corresponding to at least three orthogonal accelerometer readings, three orthogonal gyroscope readings, and a compass reading with at least one measurement orthogonal to the gravity vector of the Earth. When the controller is at rest, two of the three components of its orientation can be calculated by measuring the direction of the gravity vector using the accelerometers as described in U.S. Pat. No. 7,953,246, which is hereby incorporated by reference. The third component is the rotation around the gravity vector and can be measured directly from the compass. It is understood that these direct measurements of the orientation will not always be available, so the gyroscope sensors provide accurate measurements of angular velocities around each of the three axes over time. These velocities can be integrated to calculate the changes in orientation over time between estimates from gravity and the compass. It is noted that the cumulative integration of the gyroscope readings will accumulate error, known as drift, over a period of time. In order to keep an accurate “Down the Barrel” estimate of orientation, it will be necessary to regularly adjust the orientations back towards the direct estimates available from gravity and the compass. In practice, the gravity and compass readings tend to have lower precision and more noise than the gyroscope readings, resulting in less accuracy in their estimation of the orientation, but are not subject to accumulated error over time or drift. To get the best estimate of orientation, it is necessary to blend these two types of data. A simple method for handling this blending is to smooth the corrections to the integrated orientations by moving them in small increments towards the gravity and compass estimates. More complex methods are available to practitioners including Kalman filters and other known methods for filtering and combining noisy signals.
Alternately, all three components of orientation can be calculated from the compass if a three-axis compass is present within the controlling device. In another embodiment, a compass with at least three orthogonal readings is used in place of the gyroscope. For an accurate enough compass, the readings can be used as a direct estimate of orientation of the controller in the world frame. Errors in the orientation can be reduced by smoothing (averaging) the outputs of multiple readings in order to prevent the user experiencing a jittery cursor when trying to point.
In still another embodiment, both the orientation and relative location of the display to the controller can be jointly obtained and updated over time with the use of an external camera in a defined relationship to the display and a light source on the controller visible to that camera as described in co-pending US application serial No.: 13/105,863 which is hereby incorporated by reference.
Given the orientation and relative position of the controller, ray-casting provides a straightforward operation to find the intersection point between the ray originating at the controller and aligned along its orientation with the display. In one embodiment, when only more limited sensors are available, relative pointing is used instead of “down-the-barrel” pointing. In this embodiment, the gyroscope readings from the Motion Controller are mapped directly to relative changes in the location of a cursor on the screen in order to generate the pointed positions, removing the need to have accelerometers, compass sensors, LEDs, or an external camera.
As shown in
In each case, the source of the signals may be unknown, but the software components 905 running in the controlled device are configured to “listen-for” or are otherwise controlled by signals of specific types or of identifiable categories. As used herein, signals that are “X-like” are referred to as the signals received by the software components that cause the behavior change of the device running the software components as if the device is controlled by an input device X, but not necessarily originating from the device X.
One aspect of this invention is to allow one or more software components to be controlled by signals of specific types or of identifiable signal categories:
in the absence of the physical device of the indicated category; and/or
in addition to the physical device of the indicated category; and/or
as an alternative mechanism to the physical device of the indicated category.
As an example, in one embodiment of this invention, the invention permits the remote control of a plurality of software components running on the controlled device 904, where a touch screen device 910 is the primary source of input, and the software components 905 are controllable by the touch screen device 910 or the touch-surface-like signals therefrom.
According to one embodiment, the controlling device 901 may be used to control those software components 905 by transforming its signals 907 (being not touch-surface-like) into touch-surface-like signals 908 usable to control the software components 905. In the embodiment, a transformation is performed by a module 906 (e.g., a software module or a circuit module), referred to as a transformer herein, to perform make the signals 907 usable to the controlled device 904.
In another embodiment, the transformer 906 is able to perform additional transformations on signals. A transformation is specifically related to input signals directly or indirectly derived from the controlling device 901 (including, in some embodiments, signals derived in part from an external camera, but still requiring signals from the controlled device), into output signals of types useable to control the software components and applications running on the controlled device 904.
Depending on implementation, a wide variety of transformations are possible and appropriate for the categories of input signals available from the controlling device and categories of signals the software components in the controlled device are responsive to. Exemplary transformations include:
In many of the cases above, the incoming signals from the controlling device 901 are transformed in the controlled device 904. The transformations may not prevent in all cases the control of the software components by other physical devices (e.g., the touch screen device 910), but instead to allow the remote control of the software components by the controlling device 904. The remote control may be initially enabled by detecting some event indicating a desire of the user to use such an alternate controller. Example possible events include:
In another embodiment, the transformation occurs on the controlling device and the output signals thereof are transmitted directly to the controlled device. According to one embodiment, the controlled device is a network-enabled television, being a device capable of receiving and showing video received from an Internet source, or running games, or other networked applications. In the embodiment shown in
One embodiment of this invention is a method for transforming sensor signals from a motion controller, when used as described herein, into touch-surface-like signals. The graphical display shows a “pointed position” as an on-screen element (such as a cursor). The pointed position follows the motion of the motion device by the transformation of the motion signals from the motion device into points on a 2D plane.
There are several methods for transforming the motion signals of the controller into positions on the screen exist. In one embodiment, the inventors use a ray-casting method as described in co-pending U.S. application Ser. No. 12/835,750 which is hereby incorporated by reference. In order to properly achieve “Down the Barrel” pointing, two main kinds of information are needed. First, an accurate absolute orientation of the controller in the world frame is derived, where the world frame is defined with respect to the direction of the gravity field of the Earth and magnetic north. Second, a mapping from the reference frame of the controller to the display is defined. This mapping includes the relative position of the display in relation to the controller as well as the relative rotation of the display with respect to the world frame. This second set of information can be obtained with an initial setup calibration stage. One method of doing this is described in the co-pending U.S. application Ser. No. 12/835,750, where the user points at multiple positions on the display screen with the controller in order to establish the mapping.
In one embodiment, the controlling device generates sensor signals corresponding to at least three orthogonal accelerometer readings, three orthogonal gyroscope readings, and a compass reading with at least one measurement orthogonal to the gravity vector of the Earth. When the controller is at rest, two of the three components of its orientation can be calculated by measuring the direction of the gravity vector using the accelerometers as described in U.S. Pat. No. 7,953,246, which is hereby incorporated by reference. The third component is the rotation around the gravity vector and can be measured directly from the compass. It is understood that these direct measurements of the orientation will not always be available, so the gyroscope sensors provide accurate measurements of angular velocities around each of the three axes over time. These velocities can be integrated to calculate the changes in orientation over time between estimates from gravity and the compass. It is noted that the cumulative integration of the gyroscope readings will accumulate error, known as drift, over a period of time. In order to keep an accurate “Down the Barrel” estimate of orientation, it will be necessary to regularly adjust the orientations back towards the direct estimates available from gravity and the compass. In practice, the gravity and compass readings tend to have lower precision and more noise than the gyroscope readings, resulting in less accuracy in their estimation of the orientation, but are not subject to accumulated error over time or drift. To get the best estimate of orientation, it is necessary to blend these two types of data. A simple method for handling this blending is to smooth the corrections to the integrated orientations by moving them in small increments towards the gravity and compass estimates. More complex methods are available to practitioners including Kalman filters and other known methods for filtering and combining noisy signals.
Alternately, all three components of orientation can be calculated from the compass if a three-axis compass is present within the controlling device. In another embodiment, a compass with at least three orthogonal readings is used in place of the gyroscope. For an accurate enough compass, the readings can be used as a direct estimate of orientation of the controller in the world frame. Errors in the orientation can be reduced by smoothing (averaging) the outputs of multiple readings in order to prevent the user experiencing a jittery cursor when trying to point.
In still another embodiment, both the orientation and relative location of the display to the controller can be jointly obtained and updated over time with the use of an external camera in a defined relationship to the display and a light source on the controller visible to that camera as described in co-pending U.S. application Ser. No. 13/105,863 which is hereby incorporated by reference.
Given the orientation and relative position of the controller, ray-casting provides a straightforward operation to find the intersection point between the ray originating at the controller and aligned along its orientation with the display. In one embodiment, when only more limited sensors are available, relative pointing is used instead of “down-the-barrel” pointing. In this embodiment, the gyroscope readings from the Motion Controller are mapped directly to relative changes in the location of a cursor on the screen in order to generate the pointed positions, removing the need to have accelerometers, compass sensors, LEDs, or an external camera.
Next we describe how to combine these 2D intersection points, pointed positions, with other signals (e.g., action signals) from the controlling device in order to generate touch-surface-like signals according to one embodiment.
The details of the operation modes described below are intended to be illustrative rather than limiting in their application. When holding a button is described, similar methods such as depressing a trigger or covering a touch, light, or capacitive sensor may be used instead. When a rotation around an axis is described, a different choice of axis or rotation direction may be used if felt to be more comfortable or natural for the user given the input device.
In one embodiment, the pointed position on the display device is mapped back to its corresponding position on the touch surface input device when generating touch surface signals. For embodiments without a touch screen device, the 2D pointed position on the display is used directly to generate a touch-like signal for the software components. Additional transformations and methods of user interaction with the program will be used in alternate embodiments including some subset of the following:
Graphical Overlay While Button Held and Select At Release: Pressing and holding a button causes the appearance of various graphical elements (buttons, lists, texts, boxes, etc. . . . ), generated and displayed by the Display Overlay software component 609. At the release of the button any graphical element represented at the pointed position has its function activated and the graphical overlay disappears.
Volume control: pressing and holding a button on the controlling device enters a volume change mode. Rotating the tip of the controller to the right (when viewed from above, looking down) causes the volume to increase. Rotating the tip of the controller to the left (when viewed from above, looking down) causes the volume to decrease.
Scrolling left and right: Pressing and holding a button on the controlling device causes a change in the position of displayed graphical elements. Horizontal motions of the tip Motion Controller (i.e. the left/right motion of the tip of the controller, when viewed from above), cause the horizontal motion of graphical elements.
Scrolling up and down: Pressing and holding a button causes a change in the position of displayed graphical elements. Vertical motions of the tip of the motion controller (i.e. the up/down motion of the tip of the controller, when viewed from the side), cause the vertical motion of graphical elements.
Gesture control: If the user makes a motion of a recognizable type, it may generate a corresponding simulated signal for a software event or request such as “Press Home button”, “Scroll Up”, “Save Changes”, “Cancel”, or similar recognizable signals previously defined for the software component.
Gesture control to touch: If the user makes a motion of a recognizable type, it may generate a series of touch-surface signals corresponding to a pre-defined series of pointed positions. The series of positions could be defined either by the application, or a previous set of generated touch-signals by the user. For example the user could specify a sequence of pointed positions using one of the single or multi-touch methods detailed above and then specify that that sequence should be associated with motions similar to an example motion or set of motions they provide.
Audio control: If the user makes a recognizable audible signal generate a corresponding simulated software event or request signal such as “Press Home button”, “Scroll Up”, “Save Changes”, “Cancel”, or similar recognizable signals previously defined for the software component.
Audio Volume Control: Use the volume of the audio input from the user to control the output volume of the controlled device. For example, one could decide to match the decibel level of the two.
Audio to Text Input: The transformation of audio signals from the controlling device to provide or replace text input to software components running on the controlled device. In one embodiment the transformation is implemented using an existing Text to Speech API, such as the Google Android Text To Speed API.
Motion to Keyboard-like Input: The transformation of motion control signals from the controlling device to provide or replace touch input providing text input to software components running on the controlled device. In one embodiment the transformation is from button and motion signals into touch-surface-like signal simulating the selection of the keys shown on an on-screen keyboard.
Motion to Text Input: In another embodiment, the transformation is from button and motion signals into touch-surface-like signal simulating the drawing of words by passing the pointed position through the on-screen symbols representing elements of the chosen word. A disambiguation method is required. In one embodiment existing software components, such as Swype, are used.
A profile further represents the dynamic application of the transformation within a specified Context. That is to say, if the Context applies, take the sensor signals from the controlling device, apply the transformation, and provide the resulting signals to software components running on the controlled device.
Examples of the contexts include, but are not limited, to:
the status of identified graphical user interface elements (windows, screens, boxes, buttons, sliders, etc. . . . )
IF (A scroll bar element is currently displayed) THEN Transform the joystick signals from the controlling device into touch surface signals causing Scroll Up or Scroll Down.
IF (Photo Gallery Photo Viewer Application is Running) THEN Transform motion sensor signals into touch surface signals causing Zoom In or Zoom Out.
or,
IF (Photo Gallery Photo Viewer Application is Running) THEN Transform motion sensor signals into touch high level signals explicitly representing Zoom In or Zoom Out.
IF (some game is currently running) THEN Transform (motion signals from the controlling device into simulated motion signals of the controlled device).
Example Profile:
IF (controlling device is detected AND any other conditions) THEN Transform joystick signals of the controlling device representing a forward push into a touch surface signals simulating an upwards stroke.
IF (controlling device motion was detected)
THEN (Transform A into B)
IF (controlling device motion was detected AND other contexts detected)
THEN (Transform A into B);
IF (A display graphical element for text input is selected)
THEN Transform audio signals from the controlling device into text input.
IF (the controlling device is held in a vertical orientation)
THEN Transform audio signals from the controlling device into text input.
In one embodiment, a Profile is implemented as programming code, which may (possibly after compilation and linking steps), be executed on the Controlled or controlling device.
In the preferred embodiment, Profiles are represented as computer data and so are readily stored, copied, edited, modified, entered into databases or transmitted electronically. In this case, the functions of the Profile are performed by an additional software component 611 that may load the Profile.
According to one embodiment of the present invention,
At 1002, the process 1000 checks if a controlling device (e.g., iPhone) is able to communicate with a controlled device (e.g., a smart TV). The communication may be conducted in one of many ways, such as WiFI, Bluetooth, or infrared. The purpose is to ensure that signals from the controlling device can be received by the controlled device. The process 1000 can proceed when the signals from the controlling device can be received by the controlled device. At 1004, a user of the controlling device moves the controlling device around. As described above, the controlling device includes a set of sensors, at least some of them are inertial sensors that generate motion signals. At 1006, the controlling device is calibrated, such as the measurement of the orientation of the controlling device while the device is pointed at a display of the controlled device. Thus it is initially possible to provide down-the-barrel pointing.
The sensor signals are transformed according to a transformation. Depending on implementation, the transformation may be implemented in different ways, some of which have been described above. One of the functions for the transformation is to transform the sensor signals (along with action signals) to substantially similar to the control signals the controlled device is designed for. For example, the controlled device is designed to be controlled by control signals from a touch-screen device or to receive input signals from a touch-screen device. The transformation can be designed in one embodiment to transform some or all of the sensor signals to substantially similar to the control signals from the touch-screen device. As a result, the controlling device can be used to control the controlled device.
To fairly accurately point at the display, the absolute positions of the controlling device on the 2D surface of the display are calculated at 1010 with respect to a reference frame (e.g., with respect to the display). On the other side, the controlling device may also generate other signals. Typically, the controlling device can be interfaced with a user to receive a command and an input at 1012. The device may also include one or more keys or buttons to activate an action. Thus, besides the sensor signals from the sensors in the controlling device, there are action signals that may also from the controlling device at 1014. Similar to 1008, the action signals are transformed to substantially similar to the action signals the controlled device can accept at 1016. In one embodiment, both the sensor signals and the action signals are transmitted to the controlled device at the same time depending on how the user desires to control the controlled device. Together with the pointing positions from 1010, the action signals can cause a behavior change to the controlled device at 1018.
For example, a user needs to scroll a menu with a few items, where the menu is displayed on the controlled device. Thus it is necessary to determine the pointing positions of the controlling device on the display so as to determine which item is being pointed at. An action (e.g., a click) on the controlling device causes the controlling device to send out an action signal that shall be transformed to an action acceptable by the controlled device. With the determine locations, the controlled device is configured to determine which item in the menu is being selected and shall be activated.
The above description of the invention has focused on the transformation of signals from the controlling device to the software components running on the controlled device. In may be desirable to additionally alter the outputs from the software components before displaying them to the user. For some controlled devices additional transformations of the output data could be used to improve the user experience given the new controller. Examples of additional transformations of the graphical data include adding additional displayed controls (such as buttons, sliders, or menus) into unused portions of the display. For graphical data coming from a device such as a smart phone in portrait display mode, there may be large unused areas in a display such as a television screen or monitor that can be used to provide additional areas for the user to generate Pointed Points used in output touch-surface signals. Additionally, graphical elements could be removed from the output of the touch-sensitive device and either placed in new configurations (such as to the side of the main display), or removed entirely. Consider a game application with a virtual game-pad at the bottom of the screen. If the input controller has a joystick, there may be no need to display the virtual joypad to the user, making a clearer picture for the user, while still allowing the input joystick signals of the controlling device to be mapped to touch-surface signals corresponding to the position of the controls on the original touch-surface device.
The invention is preferably implemented in software, but can also be implemented in hardware or a combination of hardware and software. The invention 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. Examples of the computer readable medium include read-only memory, random-access memory, CD-ROMs, DVDs, magnetic tape, optical data storage devices, and carrier waves. The computer readable medium can also be distributed over network-coupled computer systems so that the computer readable code is stored and executed in a distributed fashion.
The present invention has been described in sufficient details with a certain degree of particularity. It is understood to those skilled in the art that the present disclosure of embodiments has been made by way of examples only and that numerous changes in the arrangement and combination of parts may be resorted without departing from the spirit and scope of the invention as claimed. Accordingly, the scope of the present invention is defined by the appended claims rather than the foregoing description of embodiment.
This application is: a continuation-in-part of U.S. application Ser. No. 13/249,251, entitled “Motion control used as controlling device” and filed Sep. 30, 2011, which claims the benefits of the provisional application, No. 61/500,581, entitled “Motion control used as controlling device”, filed Jun. 23, 2011, which is hereby incorporated by reference for all purposes;a continuation-in-part of co-pending U.S. application Ser. No. 12/709,523, entitled “Systems and methods for utilizing personalized motion control in virtual environment”, filed Feb. 22, 2010, which is a continuation-in-part of co-pending U.S. application Ser. No. 11/486,997, entitled “Generating Motion Recognizers for Arbitrary Motions”, filed Jul. 14, 2006, now U.S. Pat. No. 7,702,608, and co-pending U.S. application Ser. No. 12/020,431, entitled “Self-Contained Inertial Navigation System for Interactive Control Using Movable Controllers”, filed Jan. 25, 2008, which is a continuation-in-part of co-pending U.S. application Ser. No. 11/486,997, filed Jul. 14, 2006, entitled “Generating Motion Recognizers for Arbitrary Motions”, now U.S. Pat. No. 7,702,608, and U.S. application Ser. No. 11/820,207, filed Jun. 18, 2007, entitled “Self-contained Inertial navigation system for interactive control using movable controllers”, now U.S. Pat. No. 7,636,645;a continuation-in-part of co-pending U.S. application Ser. No. 13/105,863, entitled “Method and system for tracking motion-sensing device”, filed May 11, 2010, which is a continuation-in-part of co-pending U.S. application Ser. No. 12/935,750, entitled “Method and system for controlling objects within a virtual environment”, filed on Jul. 14, 2010, which is a continuation-in-part of co-pending U.S. application Ser. No. 12/020,431, entitled “Self-Contained Inertial Navigation System for Interactive Control Using Movable Controllers”, which claims the priority of a provisional application Ser. No. 60/990,898, filed Nov. 28, 2007, and is a continuation-in-part of U.S. application Ser. No. 11/486,997, filed Jul. 14, 2006, now U.S. Pat. No. 7,702,608; anda continuation-in-part of U.S. application Ser. No. 12/984,606, entitled “Method and system for head tracking and pose estimation” and filed Jan. 5, 2011.
| Number | Date | Country | |
|---|---|---|---|
| 61500581 | Jun 2011 | US | |
| 60990898 | Nov 2007 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 13249251 | Sep 2011 | US |
| Child | 13309326 | US | |
| Parent | 12709523 | Feb 2010 | US |
| Child | 13249251 | US | |
| Parent | 11486997 | Jul 2006 | US |
| Child | 12709523 | US | |
| Parent | 12020431 | Jan 2008 | US |
| Child | 11486997 | US | |
| Parent | 11486997 | Jul 2006 | US |
| Child | 12020431 | US | |
| Parent | 11820207 | Jun 2007 | US |
| Child | 11486997 | US | |
| Parent | 13105863 | May 2011 | US |
| Child | 11820207 | US | |
| Parent | 12935750 | Dec 2010 | US |
| Child | 13105863 | US | |
| Parent | 12020431 | Jan 2008 | US |
| Child | 12935750 | US | |
| Parent | 11486997 | Jul 2006 | US |
| Child | 12020431 | US | |
| Parent | 12984606 | Jan 2011 | US |
| Child | 11486997 | US |
