Methods for Reliable Acceptance of User Non-Contact Gesture Inputs for a Mobile Device

BACKGROUND

Electronic devices such as smartphones, wearable computers, and tablets, are regularly relied upon for both business and personal use. Users communicate with them via voice and touch and treat them like a virtual assistant to schedule meetings and events, consume digital media, and share presentations and documents. The processing power of these devices is augmented by machine-learning, which helps the devices anticipate their users' preferences. For all this computing power and artificial intelligence, however, these devices are still reactive communicators. That is, however “smart” a smartphone is, and however much the user talks to it like it is a person, the electronic device is still dependent on being activated before it can provide feedback. To activate the mobile device, the user typically has to first pick up the device to make it aware of the user's intention to use the electronic device. Only after this physical interaction can the device make applications and functionality available for the user. Consequently, many electronic devices provide poor user experiences prior to explicit interaction by the user.

SUMMARY

This document describes techniques and systems that provide methods for reliable acceptance of user non-contact gesture inputs for a mobile device. The techniques and systems use a radar field to enable an electronic device to accurately determine the presence or absence of a user near the electronic device and to detect a reach or other gesture the user makes. Further, the electronic device can determine whether an application that can receive input through radar-based touch-independent gestures (radar gestures) is stored or operating on the electronic device. Using these techniques, the electronic device can present a gesture-confirmation element on a display of the electronic device when the user successfully makes a radar gesture while the user's hand is within a gesture zone around the electronic device. The gesture-confirmation element lets the user know that the radar gesture has been successfully received. This allows the device to provide the user with feedback, which can educate the user about what the electronic device is capable of and allow the user to take advantage of the additional functionality and features provided by the availability of the radar gesture.

Aspects described below include a method implemented in an electronic device that includes a display and a radar system. The method comprises receiving radar data from the radar system, the radar data determined based on reflections of a portion of the user moving within a gesture zone of the electronic device and determining a radar gesture based on the radar data, or receiving a radar gesture. The method also includes determining that the radar gesture corresponds to a control input of an application on the electronic device. The method additionally includes providing a gesture-confirmation element on the display of the electronic device, the gesture-confirmation element indicating that the movement of the portion of the user within the gesture zone of the electronic device is determined to comprise the radar gesture and that the radar gesture corresponds to the control input of the application. The method also includes causing the application to respond to the control input.

Aspects described below also include an electronic device comprising a computer processor, a radar system, and a computer-readable media. The radar system is implemented at least partially in hardware and provides a radar field. The radar system also senses reflections from a user in the radar field, analyzes the reflections from the user in the radar field, and provides radar data based on the analysis of the reflections. The computer-readable media include stored instructions that can be executed by the computer processors to implement a radar-based gesture-feedback manager. The radar-based gesture-feedback manager receives the radar data from the radar system, the radar data determined based on reflections of a portion of the user moving within a gesture zone of the electronic device and determine a radar gesture based on the radar data, or receives a radar gesture. The radar-based gesture-feedback manager also determines that the radar gesture corresponds to a control input of an application on the electronic device. The radar-based gesture-feedback manager also provides a gesture-confirmation element on a display of the electronic device, the gesture-confirmation element indicating that the movement of the portion of the user within the gesture zone of the electronic device is determined to comprise the radar gesture and that the radar gesture corresponds to the control input of the application. The radar-based gesture-feedback manager further causes the application to respond to the control input.

Aspects described below include a system comprising a display, and an electronic device that includes, or is associated with means for providing a radar field that provides radar data, the radar data based on sensing and analyzing reflections from an object in the radar field. The system also includes means for receiving the radar data from the radar system, the radar data determined based on reflections of a portion of the user moving within a gesture zone of the electronic device and determine a radar gesture based on the radar data, or means for receiving a radar gesture. The system also includes means for determining that the radar gesture corresponds to a control input of an application on the electronic device. The system also includes means for providing a gesture-confirmation element on the display of the electronic device, the gesture-confirmation element indicating that the movement of the portion of the user within the gesture zone of the electronic device is determined to comprise the radar gesture and that the radar gesture corresponds to the control input of the application. The system also includes means for causing the application to respond to the control input.

This summary is provided to introduce simplified concepts concerning the methods for reliable acceptance of user non-contact gesture inputs for a mobile device, which is further described below in the Detailed Description and Drawings. This summary is not intended to identify essential features of the claimed subject matter, nor is it intended for use in determining the scope of the claimed subject matter.

BRIEF DESCRIPTION OF THE DRAWINGS

The details of one or more aspects of methods for reliable acceptance of user non-contact gesture inputs for a mobile device are described in this document with reference to the following drawings. The same numbers are used throughout the drawings to reference like features and components:

FIG. 1 illustrates an example environment in which techniques enabling the methods for reliable acceptance of user non-contact gesture inputs for a mobile device can be implemented.

FIG. 2 illustrates an example implementation of an electronic device, including a radar system, that can implement the methods for reliable acceptance of user non-contact gesture inputs for a mobile device.

FIG. 3 illustrates an example implementation of the radar system of FIGS. 1 and 2.

FIG. 4 illustrates example arrangements of receiving antenna elements for the radar system of FIG. 3.

FIG. 5 illustrates additional details of an example implementation of the radar system of FIGS. 1 and 2.

FIG. 6 illustrates an example scheme that can be implemented by the radar system of FIGS. 1 and 2.

FIG. 7 depicts an example method that enables the methods for reliable acceptance of user non-contact gesture inputs for a mobile device.

FIGS. 8-15 illustrate visual elements, including a gesture-confirmation element, which can be presented on the display of the electronic device of FIGS. 1 and 2 when a radar-gesture application is running on the electronic device.

FIGS. 16-18 illustrate the electronic device of FIGS. 1 and 2 operating in multiple modes with examples of the visual elements that can be presented on the display in the different modes.

FIG. 19 illustrates an example computing system that can be implemented as any type of client, server, and/or electronic device as described with reference to FIGS. 1-18 to implement, or in which techniques may be implemented that enable, the methods for reliable acceptance of user non-contact gesture inputs for a mobile device.

DETAILED DESCRIPTION

Overview

This document describes techniques and systems that enable methods for reliable acceptance of user non-contact gesture inputs for a mobile device. The described techniques employ a radar system that detects and determines radar-based touch-independent gestures made by the user. The techniques also determine when the device is running an application that can receive input through radar-based touch-independent gestures. When the device is running one of these applications (or has one stored that can be run) and a user is present, the techniques provide a gesture-confirmation element, giving the user feedback when a radar gesture has been successfully made or received to control an application on the electronic device.

In this description, the terms “radar-based touch-independent gesture,” “3D gesture,” or “radar gesture” refer to the nature of a gesture in space, away from the electronic device (e.g., the gesture does not require the user to touch the device, though the gesture does not preclude touch). The radar gesture itself may often only have an active informational component that lies in two dimensions, such as a radar gesture consisting of an upper-left-to-lower-right swipe in a plane, but because the radar gesture also has a distance from the electronic device (a “third” dimension), the radar gestures discussed herein can be generally be considered three-dimensional.

Using these techniques, the electronic device can provide feedback and a notification to make the user aware of the available radar gestures and their corresponding ability to control an application, and provide feedback regarding the use, success, failure, and results of the radar gestures. In some cases, a determination of the user's absence, presence, or location can also be used to provide a more-responsive and more-efficient authentication process. For example, the techniques enable the device to anticipate when the user is ready to be authenticated and to more-accurately determine when to lock the device when the user is away. Because the described techniques allow the electronic device to provide the user with useful feedback about available input modes, interactions may be more convenient and less frustrating because the user is aware of the input modes and can be confident about different ways in which the device can interact and receive input.

Consider an example smartphone that includes the described radar system. In this example, an application that has a capability to receive input through radar gestures is operating on the electronic device. This type of application will be referred to as a radar-gesture application. Examples of radar-gesture applications include music players, media players, and applications or features of an electronic device that provide alerts or a reminder, such as a calendar. In this example, a gesture-feedback manager causes the electronic device to present a gesture-confirmation element on a display of the device when the user successfully performs a radar gesture. The radar gesture is determined to be successful based on various criteria that may change depending on factors such as the type of radar-gesture application or the type of radar gesture. For example, the criteria may include the shape of the radar gesture, the velocity of the radar gesture, or whether the user's hand is within a gesture zone around the electronic device during the completion of the radar gesture. Similarly, when the gesture-feedback manager detects a user's motion in the gesture zone that does not meet the criteria for a successful radar gesture, the gesture-feedback manager causes the electronic device to present a visual feedback element on the display to indicate the failed gesture.

The gesture zone is a volume around the electronic device within which the gesture-feedback manager can determine a radar gesture (e.g., using radar data to determine various parameters of a user' motion within the gesture zone). The gesture zone may be a threshold distance, such as within three, five, seven, or nine inches. In some cases, the gesture zone may extend different threshold distances from the electronic device in different directions (e.g., it can have a wedged, oblong, ellipsoid, or asymmetrical shape). The size or shape of the gesture zone can also vary over time or be based on other factors such as a state of the electronic device (e.g., battery level, orientation, locked or unlocked), or an environment (such as in a pocket or purse, in a car, or on a flat surface).

The gesture-confirmation element, and the visual feedback element indicating a failed gesture, are user-perceivable elements (e.g., visual elements that are presented on the display of the electronic device) that indicate whether the user successfully performed a radar gesture. These elements can be used to inform the user that a radar gesture has been detected and whether the radar gesture was successful for interacting with a radar-gesture application. For example, when a radar-gesture application is running on the electronic device, the display may present an icon, a contrasted lighting area (e.g., an area that is brighter or dimmer than the surrounding area), or an area of different or contrasting color (including in some cases, a combination of one or more of these features). When a radar gesture is successfully completed, the gesture-confirmation element is presented and when the radar gesture fails, the visual feedback element indicating a failed gesture is presented.

The described techniques and systems employ a radar system, along with other features, to provide a useful and rewarding user experience, including visual feedback, based on the user's gestures and the operation of a radar-gesture application on the electronic device. Rather than relying only on the user's knowledge and awareness of a particular radar-gesture application, the electronic device can provide feedback to the user to indicate the success or failure of a radar gesture the user made.

Some conventional electronic devices may include sensors, such as cameras, proximity sensors (e.g., capacitive or infra-red sensors), or accelerometers to determine the location of the user and adjust various functions of the electronic device based on the proximity of the user. For example, the electronic device may provide additional privacy or aesthetic value by turning off a display unless the user is within a predetermined distance. The conventional electronic device, however, typically cannot provide a useful and rich ambient experience that can educate the user about the capabilities of the electronic device and the user's interactions with the electronic device. These are but a few examples of how the described techniques and devices may be used to enable the methods for reliable acceptance of user non-contact gesture inputs for a mobile device, other examples and implementations of which are described throughout this document. The document now turns to an example operating environment, after which example devices, methods, and systems are described.

Operating Environment

FIG. 1 illustrates an example environment 100 in which techniques enabling methods for reliable acceptance of user non-contact gesture inputs for a mobile device can be implemented. The example environment 100 includes an electronic device 102, which includes, or is associated with, a radar system 104, a persistent radar-based gesture-feedback manager 106 (gesture-feedback manager 106), and, optionally, one or more non-radar sensors 108 (non-radar sensor 108). The term “persistent,” with reference to the radar system 104 or the gesture-feedback manager 106, means that no user interaction is required to activate the radar system 104 (which may operate in various modes, such as a dormant mode, an engaged mode, or an active mode) or the gesture-feedback manager 106. In some implementations, the “persistent” state may be paused or turned off (e.g., by a user). In other implementations, the “persistent” state may be scheduled or otherwise managed in accordance with one or more parameters of the electronic device 102 (or another electronic device). For example, the user may schedule the “persistent” state such that it is only operational during daylight hours, even though the electronic device 102 is on both at night and during the day. The non-radar sensor 108 can be any of a variety of devices, such as an audio sensor (e.g., a microphone), a touch-input sensor (e.g., a touchscreen), or an image-capture device (e.g., a camera or video-camera).

In the example environment 100, the radar system 104 provides a radar field 110 by transmitting one or more radar signals or waveforms as described below with reference to FIGS. 3-6. The radar field 110 is a volume of space from which the radar system 104 can detect reflections of the radar signals and waveforms (e.g., radar signals and waveforms reflected from objects in the volume of space). The radar field 110 may be configured in multiple shapes, such as a sphere, a hemisphere, an ellipsoid, a cone, one or more lobes, or an asymmetric shape (e.g., that can cover an area on either side of an obstruction that is not penetrable by radar). The radar system 104 also enables the electronic device 102, or another electronic device, to sense and analyze reflections from an object in the radar field 110. The radar field 110 may be used to provide a recognition zone. The recognition zone is a volume around the radar system 104 that may extend any of a variety of distances from the radar system 104, such as approximately three, seven, ten, or fourteen feet (or approximately one, two, three, or four meters). The recognition zone may be the same or less than a maximum extent of the radar field 110. The recognition zone may be a static size or shape that is predefined, user-selectable, or determined via another method (e.g., based on power requirements, remaining battery life, or another factor).

In some cases, the recognition zone may be dynamically and automatically adjustable by the gesture-feedback manager 106 based on various factors, such as the velocity or location of the electronic device 102, a time of day, or a state of an application running on the electronic device 102. The threshold distance or recognition zone can be determined based on a number of relevant factors, such as battery level, location of the electronic device, velocity of the electronic device, or data received from one or more of the radar system, other sensors, or applications running on the electronic device.

Some implementations of the radar system 104 are particularly advantageous as applied in the context of smartphones, such as the electronic device 102, for which there is a convergence of issues such as a need for low power, a need for processing efficiency, limitations in a spacing and layout of antenna elements, and other issues, and are even further advantageous in the particular context of smartphones for which radar detection of fine hand gestures is desired. Although the implementations are particularly advantageous in the described context of the smartphone for which fine radar-detected hand gestures are required, it is to be appreciated that the applicability of the features and advantages of the present invention is not necessarily so limited, and other implementations involving other types of electronic devices (e.g., as described with reference to FIG. 2) are also within the scope of the present teachings.

The object may be any of a variety of objects from which the radar system 104 can sense and analyze radar reflections, such as wood, plastic, metal, fabric, a human body, or a portion of a human body (e.g., a foot, hand, or finger of a user of the electronic device 102). As shown in FIG. 1, the object is a hand 112 of a user of the electronic device 102. Based on the analysis of the reflections, the radar system 104 can provide radar data that includes various types of information associated with the radar field 110 and the reflections from the hand 112, as described with reference to FIGS. 3-6 (e.g., the radar system 104 can pass the radar data to other entities, such as the gesture-feedback manager 106).

The radar data can be continuously or periodically provided over time, based on the sensed and analyzed reflections from the object (e.g., the hand 112 in the radar field 110). A position of the hand 112 can change over time (e.g., the hand 112 may move within the radar field 110) and the radar data can thus vary over time corresponding to the changed positions, reflections, and analyses. Because the radar data may vary over time, the radar system 104 provides radar data that includes one or more subsets of radar data that correspond to different periods of time. For example, the radar system 104 can provide a first subset of the radar data corresponding to a first time-period, a second subset of the radar data corresponding to a second time-period, and so forth. In some cases, different subsets of the radar data may overlap, entirely or in part (e.g., one subset of the radar data may include some or all of the same data as another subset).

The electronic device 102 can also include a display 114 and an application manager 116. The display 114 can include any suitable display device, such as a touchscreen, a liquid crystal display (LCD), thin film transistor (TFT) LCD, an in-place switching (IPS) LCD, a capacitive touchscreen display, an organic light emitting diode (OLED) display, an active-matrix organic light-emitting diode (AMOLED) display, super AMOLED display, and so forth. The display 114 is used to display visual elements that are associated with various modes of the electronic device 102, which are described in further detail with reference to FIGS. 8-18. The application manager 116 can communicate and interact with applications operating on the electronic device 102 to determine and resolve conflicts between applications (e.g., processor resource usage, power usage, or access to other components of the electronic device 102). The application manager 116 can also interact with applications to determine the applications' available input modes, such as touch, voice, or radar gestures, and communicate the available modes to the gesture-feedback manager 106.

The gesture-feedback manager 106 can be used to interact with or control various components of the electronic device 102 (e.g., modules, managers, systems, interfaces, or one or more of the non-radar sensors 108). For instance, the gesture-feedback manager 106 (independently or through the application manager 116) can determine that an application on the electronic device has a capability to receive input through radar gestures (e.g., is a radar-gesture application). The radar-gesture application may be currently executing or operating on the electronic device or not currently executing or operating, but stored on the electronic device (e.g., by a memory device) or stored at another location that can be accessed by the electronic device. The radar gesture may be determined based on the radar data and received through the radar system 104 (e.g., based on radar data that is determined based on reflections of a portion of the user moving within a gesture zone of the electronic device). For example, the gesture-feedback manager 106 can use one or more subsets of the radar data received from the radar system 104 to detect a motion performed by the portion of the user, such as the hand 112 or an object, that is within a gesture zone 118 of the electronic device 102. The gesture-feedback manager 106 then determines, based on the radar data, whether the user's motion is a radar gesture. In other cases, another component of, or associated with, the electronic device can determine the radar gesture, or radar data that represents the radar gesture, and the gesture-feedback manager 106 can receive the radar gesture, or radar data that represents the radar gesture, from the other component.

The gesture zone 118 is a region or volume around the electronic device 102 within which the radar system 104 (or another module or application) can detect radar gestures and determine that the radar gesture corresponds to a control input of the application on the electronic device. For example, the gesture zone 118 can be a fixed volume around the electronic device that has a static size and/or shape (e.g., a threshold distance around the electronic device 102, such as within three, five, seven, nine, or twelve inches) that is predefined, user-selectable, or determined via another method (e.g., based on power requirements, remaining battery life, or another factor). In some other cases, the gesture zone 118 may be a volume around the electronic device that is dynamically and automatically adjustable by the interaction manager 106, based on factors such as the velocity or location of the electronic device 102, a time of day, a state of an application running on the electronic device 102, or another factor. While the radar system 104 can detect objects within the radar field 110 at greater distances, the gesture zone 118 helps the electronic device 102 and the radar-gesture applications to distinguish between intentional radar gestures by the user and other kinds of motions that may resemble radar gestures, but are not intended as such by the user.

The gesture-feedback manager 106 can determine whether the motion is a radar gesture in any suitable manner. For example, the gesture-feedback manager 106 can use radar data (e.g., one or more subsets of the radar data) to determine whether the motion meets one or more criteria to be considered a radar gesture. The criteria can include various parameters of the motion, such as a path, shape, length, velocity, or distance from the electronic device. In some cases, the gesture-feedback manager 106 determines the parameters for the motion and compares them to gesture data in a gesture library 120 to determine whether the user's motion matches a known radar gesture.

When the motion meets the criteria, (e.g., is determined to be a radar gesture), the gesture-feedback manager 106 (or another component associated with the electronic device 102) determines whether the radar gesture corresponds to a control input of the application. The control input is an input, such as control signal, that corresponds to an action of the application. For example, the control input can correspond to an instruction to dismiss an alert or notification on the display of the electronic device, silence a ringer or alarm, or skip to a next or previous media item. In some cases, the gesture library 120, or another component, can store relationships between control inputs and radar gestures, and the gesture-feedback manager 106 can use the relationships in the gesture library 120 to determine whether the radar gesture corresponds to a control input of the application. Thus, a radar gesture may be successful if it is properly made (e.g., meets the criteria), when it corresponds to a control input of the application, or when the application receives and responds to the control input.

The gesture-feedback manager 106 also provides a gesture-confirmation element 122 on the display 114. The appearance of the gesture-confirmation element 122 indicates that the movement of the portion of the user within the gesture zone of the electronic device is the radar gesture and/or that the radar gesture corresponds to the control input of the application on the electronic device. In some cases, the gesture-confirmation element 122 can also or instead indicate that the application received the radar gesture, control input, and/or the control signal. In a similar way, when the user's motion does not meet the criteria (e.g., is determined not to be a radar gesture) or if the radar gesture is not one used by the application on the electronic device, the gesture-feedback manager 106 causes the display 114 to present another visual feedback element on the display 114. The appearance of the other visual feedback element indicates that the movement of the portion of the user within the gesture zone of the electronic device is determined not to be the radar gesture and/or that the radar gesture does not correspond to the control input of the application (or that the application did not receive the control signal).

In some implementations, the gesture-feedback manager 106 provides the gesture-confirmation element 122 on the display 114 (or causes the display 114 to present the gesture-confirmation element 122) in response to the determination that the motion of the portion of the user is a radar gesture. In this implementation, the feedback element may be presented just after, or simultaneously with, the determination that the motion of the portion of the user is a radar gesture.

In some implementations, the gesture-feedback manager 106 may also cause the application to respond to the control input. For example, in implementations in which the application is currently executing, the gesture-feedback manager 106 can send the control input to the application. In implementations in which the application is not currently executing, gesture-feedback manager 106 can cause the application to begin executing and send the control input to the application.

The described techniques can inform the user when a motion, such as a reach, a swipe gesture (a motion that is generally horizontal or vertical with respect to content on the display 114), or an “omni-gesture” (a gesture without a particular orientation with respect to the content) is successful. When a radar gesture is attempted, the gesture-feedback manager 106 provides the user with visual feedback that indicates whether the user's motion was determined to be a radar gesture or whether the application successfully received the radar gesture. This can help the user understand how radar gestures can be used to interact with applications and whether the gesture was successful.

The gesture-confirmation element 122 is a user-perceivable element, such as a visual element that appears on an active area of the display 114. The gesture-confirmation element 122 can also be (or include) a light element that is not on the display (e.g., a light-emitting diode (LED) or an LED array mounted on a housing or bezel of the electronic device), a haptic element (e.g., a vibration element), and/or an audio element (e.g., a user-perceivable sound). In some cases, the gesture-confirmation element 122 may be presented at or along an edge of the display 114. In this document, the phrases “at an edge” and “along an edge” refer to being near or adjacent to an edge (e.g., adjacent to the edge with no gap or with a gap such as one pixel, two pixels, three pixels, and so forth). The gesture-confirmation element 122 may have any of a variety of shapes, sizes, colors, and other visual parameters or properties. Examples of the other visual parameters or properties include luminosity, color, contrast, shape, saturation, or opaqueness. Luminosity refers to the brightness of an object as perceived by a human. Modifying the luminosity may include modifying luminance (e.g., brightness), contrast, and/or opaqueness.

The visual element may have an area that is a portion of the active area of the display 114 that has a luminosity or other visual property that is different from a luminosity or other visual property of another portion of the display 114 that is proximate to the visual element. In this case, the visual element may also have a segment of an exterior border that is within a threshold distance from an edge of the active area of the display (e.g., adjacent to the edge with no gap or with a gap such as one pixel, two pixels, three pixels, one millimeter, two millimeters, three millimeters). While some of these examples describe the gesture-confirmation element 122 as presented at or along an edge of the display 114, the gesture-confirmation element 122 may appear at a location on the display 114 that is not an edge. For example, the edge of the display 114 may include an area beginning at a border of the active area of the display 114 and extending a distance from the border that is no more than approximately 15 percent of a total length of the border of the display 114.

In some implementations, the luminosity (or other visual parameter) of the gesture-confirmation element 122 may vary as the gesture-confirmation element 122 extends across a distance from the edge of the active area of the display 114 (e.g., have a luminosity at or along the edge of the display 114 that decreases as the shape extends away from the edge, or vice versa). For example, the gesture-confirmation element 122 may be presented as an area of the display 114 that has a different luminosity than another area of the display 114 (e.g., an area surrounding or near to the gesture-confirmation element 122) and that is adjacent to the edge of the display 114. In another example, the gesture-confirmation element 122 may be presented as a line, with a predetermined thickness, that has a different luminosity than the display 114 and that is adjacent to the edge of the display 114.

As described above, the gesture-confirmation element 122 can indicate that the application received the radar gesture. In some implementations, the gesture-confirmation element 122 can also provide feedback indicating the kind of radar gesture that was detected and accepted. Consider a radar-gesture application that can receive radar gestures that are directional and/or proportional. For example, the application can receive left-to-right, right-to-left, top-to-bottom, and bottom-to-top gestures (e.g., a swipe gesture). In some cases, the interaction with the application that is associated with the gesture can depend on the criteria described above. Thus, a gesture that goes from left to right within the gesture zone may skip to the next song or photo if it meets some criteria for distance and velocity. The same kind of gesture may instead adjust the volume or zoom if it meets other criteria. Similarly, the velocity of a gesture may determine whether the resultant interaction is to scroll within a webpage or move to a different level of a website.

In these cases, the gesture-confirmation element 122 may also be presented in a different way to indicate the type of interaction or the specific interaction that is associated with the gesture. For example, the visual element (e.g., the gesture-confirmation element 122) can move on the active area of the display in a way that corresponds to the radar gesture (or the movement of the user within the gesture zone). Thus, if the radar gesture is a swipe from left to right or bottom to top, the visual element can move on the display, from left to right or bottom to top, respectively. Other examples of how the gesture-confirmation element 122 can indicate the type of gesture are described in additional detail with reference to FIGS. 1 and 8-15.

Further, when the user's motion does not meet the criteria (e.g., is determined not to be a radar gesture), the gesture-feedback manager 106 causes the display 114 to present another visual feedback element on the display 114. The other visual feedback element indicates that the motion was determined not be a radar gesture or that the application did not receive the control input. Examples of how the gesture-confirmation element 122 can indicate the type of gesture are described with additional details below with reference to FIGS. 1 and 8-15.

Consider an example illustrated in FIG. 1. A detail view 100-1 shows the hand 112 within the gesture zone 118. In the detail view 100-1, a visual feedback element 124 is presented on an example display 114-1 (e.g., to indicate that the gesture-feedback manager 106 has detected the hand 112 within the gesture zone 118 and that at least one radar-gesture application is operating on the electronic device 102). In this example, a user makes a motion from left to right with the hand 112, as shown by an arrow 126. For this example, assume that the gesture-feedback manager 106 has used the radar data to determine that the motion meets the criteria to be considered a radar gesture.

Another detail view 100-2 shows the display 114 in response to the motion of the hand 112. In the detail view 100-2, the gesture-confirmation element 122 is presented on an example display 114-2. The gesture-confirmation element 122 has started to move to the right relative to the position of the visual feedback element 124, corresponding to the movement of the hand 112. The detail view 100-2 also shows an example display 114-3, in which the gesture-confirmation element 122 has started to move around a corner of the example display 114-3. While not shown in the detail view 100-2, the gesture-confirmation element 122 may continue down the edge of the example display 114-3 and disappear or reappear at the top of the example display 114-3 (e.g., in a similar position as the visual feedback element 124). In other implementations (not shown in FIG. 1), the gesture-confirmation element 122 may continue down the edge of the example display 114-3 and disappear. The visual feedback element 124 may then reappear at or near its original position.

In the example shown in FIG. 1, the gesture-confirmation element 122 and the visual feedback element 124 are both shown as a glowing area located at or near a top edge of the display 114. In other implementations, the gesture-confirmation element 122 and/or the visual feedback element 124 may be another size, another shape, or be presented at another location. This example shows how the gesture-confirmation element 122 allows the user to see whether the radar-gesture application successfully received the radar gesture and provides dynamically responsive visual feedback that corresponds to the movement of the user's hand 112 (e.g., left to right) when successfully performing the radar gesture.

In some implementations, the gesture-confirmation element 122 and the visual feedback element 124 may be the same visual element (e.g., the visual properties are the same or similar, and only the feedback functions are different). In other implementations, the gesture-confirmation element 122 may be presented as an adjustment to a visual element that is already being presented at or along the edge of the active area of the display (e.g., the visual feedback element 124). For example, in the example shown in FIG. 1, the visual feedback element 124 is already being presented. When the user's hand 112 moves as shown by the arrow 126 and the motion is determined to meet the criteria to be considered a radar gesture, the visual feedback element 124 may be adjusted to become the example gesture-confirmation element 122, such as by changing size, shape, color, or another visual property.

The color of the gesture-confirmation element 122 may be any suitable color that can be visually differentiated from the background of the display 114 on which it is presented. The color of the gesture-confirmation element 122 may change based on any of a variety of factors, such as an operational state of the electronic device 102 or an ambient background color of the display 114. In some implementations, the gesture-feedback manager 106 can determine a background color of a region of the display 114 on which the gesture-confirmation element 122 is, or will be, displayed. In response to determining the background color, the gesture-feedback manager 106 can cause the display 114 to present the gesture-confirmation element 122 in another color that is different from the background color. The different color of the gesture-confirmation element 122 can provide human-discernable contrast between the gesture-confirmation element 122 and the background color to make it easier for the user to see the gesture-confirmation element 122. In some cases, the gesture-feedback manager 106 can continuously, automatically, and dynamically adjust the color of the gesture-confirmation element 122, based on changes to the background color.

The gesture-confirmation element 122, in some implementations, may appear, at least in part, as a brief animation. For example, the gesture-confirmation element 122 may appear at the edge of the active display and then grow or shrink before taking on a default appearance. Similarly, the color, luminosity, or shape may change as the gesture-confirmation element 122 appears or disappears (e.g., if the radar-gesture application stops operating) before taking on the default appearance.

In some cases, the gesture-confirmation element 122 may be an image that appears on the display 114, rather than an element that appears in a region of the display 114. The image may have visual parameters that are different from the parameters of an ambient background of the display 114, such as luminosity, saturation, color, and so forth. In other cases, the ambient background may be an image, and the gesture-confirmation element 122 is the same image, with different visual parameters, such as luminosity, saturation, color, and so forth. In this way, the gesture-confirmation element 122 can improve the user's experience by communicating to the user that the electronic device is operating in a mode in which radar gestures are available for interacting with the electronic device 102. Additional details and examples of the gesture-confirmation element 122 are described with reference to FIGS. 8-15.

The location of the gesture-confirmation element 122 may be determined based on an orientation of content on the display 114. For example, the gesture-feedback manager 106 may obtain the orientation of the content on the display 114 from the application manager 116 (or from another source). The gesture-feedback manager 106 can also determine, based on the orientation of the content, a direction of the radar gesture that can be used to interact with the content. Based on the direction of the radar gesture, the gesture-feedback manager 106 can cause the display to present the gesture-confirmation element 122 at a particular edge of the active area of the display 114 that corresponds to the direction of the radar gesture. Thus, if the context of the displayed content is horizontal (e.g., the direction of the radar gesture would be left-to-right or right-to-left), the gesture-confirmation element 122 is displayed at a top or bottom edge, to help indicate to the user that the radar gestures are horizontal. Similarly, if the context of the displayed content is vertical (e.g., the direction of the radar gestures would be bottom-to-top or top-to-bottom), the gesture-confirmation element 122 is displayed at a side edge (e.g., a left edge), to help indicate to the user that the radar gestures are vertical.

Further, the gesture-feedback manager 106 may also be able to detect a change in an orientation of the electronic device 102 with respect to the user. For example, the user may rotate the device from a vertical to a horizontal orientation to watch a video or from a horizontal to a vertical orientation to read an article. Based on the change in orientation, the gesture-feedback manager 106 can cause the display 114 to present the gesture-confirmation element 122 on a different edge of the active display. This different edge can maintain an orientation and location of the gesture-confirmation element 122 with respect to the user (e.g., the gesture-confirmation element 122 moves or relocates as the orientation of the user to the device changes). Thus, if the gesture-confirmation element 122 is positioned on a top edge of the display 114 and the user rotates the electronic device 102, the location of the gesture-confirmation element 122 changes from one edge to another so that it remains on “top” with reference to the user. As noted, the gesture-feedback manager 106 also takes into account the orientation of the content, and these features can be used in conjunction with each other to present the gesture-confirmation element 122 on the display 114 at the location appropriate for the orientation of both the content on the display 114 and the orientation of the display 114 with respect to the user.

In some implementations, the gesture-feedback manager 106 can determine that the radar-gesture application that is operating on the electronic device 102 is operating in an immersive mode, such as a full-screen mode without any presented controls. In response to this determination, the gesture-feedback manager 106 can cause the display 114 to periodically present the gesture-confirmation element 122. For example, the display 114 can present the gesture-confirmation element 122 for a presentation time duration and then stop presenting the gesture-confirmation element 122 for a non-presentation time duration. Both the presentation time duration and the non-presentation time duration may be predetermined or selectable. In some cases, the time durations may be user-selectable (e.g., by the user) or selected by the gesture-feedback manager 106 based on various factors, such as the type of radar-gesture application running in the immersive mode (e.g., a game or a streaming media player), the status of the radar-gesture application, or the frequency with which the user employs a radar gesture.

The gesture-confirmation element 122 may fade or disappear entirely when the user interacts with the electronic device 102 using input other than a radar gesture (e.g., a touch or voice input). For example, while a radar-gesture application is operating on the electronic device 102, the user may decide to start another application using a touch command. In this case, the gesture-confirmation element 122 may fade or disappear when the user picks up the electronic device 102 or touches the display 114. When the user stops touching the display 114 or puts down the electronic device 102, the gesture-confirmation element 122 reappears (or brightens) if one or more radar-gesture applications are operating on the electronic device 102. The gesture-confirmation element 122 may reappear or brighten immediately when the touch or voice input ends, or after a selectable time duration. Similarly, when the radar-gesture application is an application that provides an alert or notification, the gesture-confirmation element 122 appears when an alert or notification is displayed, such as when a calendar reminder is displayed. When the user interacts with the alert or notification using a radar gesture (e.g., dismisses or resets the alert or notification), the gesture-confirmation element 122 disappears, unless other radar-gesture applications are running.

The gesture-confirmation element 122 may be presented while the electronic device 102 is in a locked state or an unlocked state. For example, the electronic device 102 may present the gesture-confirmation element 122 (to indicate that the hand 112 is within the gesture zone 118 and that the radar-gesture application is running) when a user is nearby (e.g., within the recognition zone), but not authenticated, or when an authenticated user is nearby. The locked and unlocked states refer to a level of access to the electronic device 102. A locked state may be a state in which no user in authenticated and anyone using the device will have less than full rights or access (e.g., no access or rights, or limited access or rights). Examples of the locked state may include the aware and engaged modes of the electronic device 102 as described herein. Similarly, an unlocked state can be a state in which at least one user is authenticated and that user has full rights and/or access to the device. An example of the unlocked state is the active mode of the electronic device 102, as described herein. In some cases, the locked or unlocked state may have varying characteristics, depending on the type, configuration, or status (e.g., a battery level or a connectivity status) of the electronic device 102. Accordingly, characteristics of the locked and unlocked states for different devices or for the same device in different contexts may overlap, or include similar features, depending on those factors.

When the user is interacting with a radar-gesture application operating on the electronic device 102 and the user receives a phone call, alarm, or notification, the gesture-feedback manager 106 (or another component) can manage the way the radar gestures and visual feedback are processed. For example, the most recent application may take priority for a reach or swipe. Thus, if the ringer, alert, or alarm is played while the user is interacting, and the user reaches or swipes, the gesture is interpreted as a direction-independent gesture (e.g., an omni-gesture), which mutes or dims the volume or dismisses the ringer, alarm, or notification. The priority for gestures then returns to the radar-gesture application that was operating.

In these cases, the described techniques can provide visual feedback that can enhance the user's experience with the electronic device 102. For example, if a user receives a phone call while the ringer is on or if an application plays an audible alarm, the user can simply reach for the electronic device 102. The radar system 104 can detect the reach and the gesture-feedback manager 106 can lower the volume of the ringer or alarm. Optionally, the user can make a radar gesture, such as a swipe, to mute the ringer or alarm. Similarly, when an application presents a notification on the display of the electronic device (e.g., a calendar reminder), the radar system 104 can detect the user's reach and keep the incoming notification on the display (e.g., rather than the notification disappearing after a time-out period). In some cases, the notification can become interactive when the reach is detected (e.g., the size of the notification can increase and interactive options, such as “reply” or “snooze” may be displayed).

When an application provides an alert that can be dismissed or muted (e.g., a ring, alarm, or notification), the gesture-feedback manager 106 can also present the gesture-confirmation element 122 (or another visual feedback element) when the user reaches for the device. When the muting or dismissing is complete, or when the user stops reaching or withdraws the reach, the gesture-confirmation element 122 ceases to be presented. In this way, the user's experience with alarms and ringers can be enhanced by detection of a reach or swipe, which can improve the user's experience with the electronic device. Additionally, the user receives feedback (e.g., the gesture-confirmation element 122) that the radar system and gesture-feedback manager 106 are operating to modify the alert or alarm, rather than merely dismissing or muting the alarm or ringer, which further improves the user's experience.

In more detail, consider FIG. 2, which illustrates an example implementation 200 of the electronic device 102 (including the radar system 104, the gesture-feedback manager 106, the non-radar sensor 108, the display 114, the application manager 116, and the gesture library 120) that can implement the methods for reliable acceptance of user non-contact gesture inputs for a mobile device. The electronic device 102 of FIG. 2 is illustrated with a variety of example devices, including a smartphone 102-1, a tablet 102-2, a laptop 102-3, a desktop computer 102-4, a computing watch 102-5, a gaming system 102-6, computing spectacles 102-7, a home-automation and control system 102-8, a smart refrigerator 102-9, and an automobile 102-10. The electronic device 102 can also include other devices, such as televisions, entertainment systems, audio systems, drones, track pads, drawing pads, netbooks, e-readers, home security systems, and other home appliances. Note that the electronic device 102 can be wearable, non-wearable but mobile, or relatively immobile (e.g., desktops and appliances).

In some implementations, exemplary overall lateral dimensions of the electronic device 102 can be approximately eight centimeters by approximately fifteen centimeters. Exemplary footprints of the radar system 104 can be even more limited, such as approximately four millimeters by six millimeters with antennas included. This requirement for such a limited footprint for the radar system 104 is to accommodate the many other desirable features of the electronic device 102 in such a space-limited package (e.g., a fingerprint sensor, the non-radar sensor 108, and so forth). Combined with power and processing limitations, this size requirement can lead to compromises in the accuracy and efficacy of radar-gesture detection, at least some of which can be overcome in view of the teachings herein.

The electronic device 102 also includes one or more computer processors 202 and one or more computer-readable media 204, which includes memory media and storage media. Applications and/or an operating system (not shown) implemented as computer-readable instructions on the computer-readable media 204 can be executed by the computer processors 202 to provide some or all of the functionalities described herein. For example, the processors 202 can be used to execute instructions on the computer-readable media 204 to implement the radar-based gesture-feedback manager 106 and/or the application manager 116. The electronic device 102 may also include a network interface 206. The electronic device 102 can use the network interface 206 for communicating data over wired, wireless, or optical networks. By way of example and not limitation, the network interface 206 may communicate data over a local-area-network (LAN), a wireless local-area-network (WLAN), a personal-area-network (PAN), a wide-area-network (WAN), an intranet, the Internet, a peer-to-peer network, point-to-point network, or a mesh network.

Various implementations of the radar system 104 can include a System-on-Chip (SoC), one or more Integrated Circuits (ICs), a processor with embedded processor instructions or configured to access processor instructions stored in memory, hardware with embedded firmware, a printed circuit board with various hardware components, or any combination thereof. The radar system 104 can operate as a monostatic radar by transmitting and receiving its own radar signals.

In some implementations, the radar system 104 may also cooperate with other radar systems 104 that are within an external environment to implement a bistatic radar, a multistatic radar, or a network radar. Constraints or limitations of the electronic device 102, however, may impact a design of the radar system 104. The electronic device 102, for example, may have limited power available to operate the radar, limited computational capability, size constraints, layout restrictions, an exterior housing that attenuates or distorts radar signals, and so forth. The radar system 104 includes several features that enable advanced radar functionality and high performance to be realized in the presence of these constraints, as further described below with respect to FIG. 3. Note that in FIG. 1 and FIG. 2, the radar system 104, the gesture-feedback manager 106, the application manager 116, and the gesture library 120 are illustrated as part of the electronic device 102. In other implementations, one or more of the radar system 104, the gesture-feedback manager 106, the application manager 116, or the gesture library 120 may be separate or remote from the electronic device 102.

These and other capabilities and configurations, as well as ways in which entities of FIG. 1 act and interact, are set forth in greater detail below. These entities may be further divided, combined, and so on. The environment 100 of FIG. 1 and the detailed illustrations of FIG. 2 through FIG. 19 illustrate some of many possible environments and devices capable of employing the described techniques. FIGS. 3-6 describe additional details and features of the radar system 104. In FIGS. 3-6, the radar system 104 is described in the context of the electronic device 102, but as noted above, the applicability of the features and advantages of the described systems and techniques are not necessarily so limited, and other implementations involving other types of electronic devices may also be within the scope of the present teachings.

FIG. 3 illustrates an example implementation 300 of the radar system 104 that can be used to enable the methods for reliable acceptance of user non-contact gesture inputs for a mobile device. In the example 300, the radar system 104 includes at least one of each of the following components: a communication interface 302, an antenna array 304, a transceiver 306, a processor 308, and a system media 310 (e.g., one or more computer-readable storage media). The processor 308 can be implemented as a digital signal processor, a controller, an application processor, another processor (e.g., the computer processor 202 of the electronic device 102) or some combination thereof. The system media 310, which may be included within, or be separate from, the computer-readable media 204 of the electronic device 102, includes one or more of the following modules: an attenuation mitigator 314, a digital beamformer 316, an angle estimator 318, or a power manager 320. These modules can compensate for, or mitigate the effects of, integrating the radar system 104 within the electronic device 102, thereby enabling the radar system 104 to recognize small or complex gestures, distinguish between different orientations of the user, continuously monitor an external environment, or realize a target false-alarm rate. With these features, the radar system 104 can be implemented within a variety of different devices, such as the devices illustrated in FIG. 2.

Using the communication interface 302, the radar system 104 can provide radar data to the gesture-feedback manager 106. The communication interface 302 may be a wireless or wired interface based on the radar system 104 being implemented separate from, or integrated within, the electronic device 102. Depending on the application, the radar data may include raw or minimally processed data, in-phase and quadrature (I/Q) data, range-Doppler data, processed data including target location information (e.g., range, azimuth, elevation), clutter map data, and so forth. Generally, the radar data contains information that is usable by the gesture-feedback manager 106 for the methods for reliable acceptance of user non-contact gesture inputs for a mobile device.

The antenna array 304 includes at least one transmitting antenna element (not shown) and at least two receiving antenna elements (as shown in FIG. 4). In some cases, the antenna array 304 may include multiple transmitting antenna elements to implement a multiple-input multiple-output (MIMO) radar capable of transmitting multiple distinct waveforms at a time (e.g., a different waveform per transmitting antenna element). The use of multiple waveforms can increase a measurement accuracy of the radar system 104. The receiving antenna elements can be positioned in a one-dimensional shape (e.g., a line) or a two-dimensional shape for implementations that include three or more receiving antenna elements. The one-dimensional shape enables the radar system 104 to measure one angular dimension (e.g., an azimuth or an elevation) while the two-dimensional shape enables two angular dimensions to be measured (e.g., both azimuth and elevation). Example two-dimensional arrangements of the receiving antenna elements are further described with respect to FIG. 4.

FIG. 4 illustrates example arrangements 400 of receiving antenna elements 402. If the antenna array 304 includes at least four receiving antenna elements 402, for example, the receiving antenna elements 402 can be arranged in a rectangular arrangement 404-1 as depicted in the middle of FIG. 4. Alternatively, a triangular arrangement 404-2 or an L-shape arrangement 404-3 may be used if the antenna array 304 includes at least three receiving antenna elements 402.

Due to a size or layout constraint of the electronic device 102, an element spacing between the receiving antenna elements 402 or a quantity of the receiving antenna elements 402 may not be ideal for the angles at which the radar system 104 is to monitor. In particular, the element spacing may cause angular ambiguities to be present that make it challenging for conventional radars to estimate an angular position of a target. Conventional radars may therefore limit a field of view (e.g., angles that are to be monitored) to avoid an ambiguous zone, which has the angular ambiguities, and thereby reduce false detections. For example, conventional radars may limit the field of view to angles between approximately −45 degrees to 45 degrees to avoid angular ambiguities that occur using a wavelength of 5 millimeters (mm) and an element spacing of 3.5 mm (e.g., the element spacing being 70% of the wavelength). Consequently, the conventional radar may be unable to detect targets that are beyond the 45-degree limits of the field of view. In contrast, the radar system 104 includes the digital beamformer 316 and the angle estimator 318, which resolve the angular ambiguities and enable the radar system 104 to monitor angles beyond the 45-degree limit, such as angles between approximately −90 degrees to 90 degrees, or up to approximately −180 degrees and 180 degrees. These angular ranges can be applied across one or more directions (e.g., azimuth and/or elevation). Accordingly, the radar system 104 can realize low false-alarm rates for a variety of different antenna array designs, including element spacings that are less than, greater than, or equal to half a center wavelength of the radar signal.

Using the antenna array 304, the radar system 104 can form beams that are steered or un-steered, wide or narrow, or shaped (e.g., as a hemisphere, cube, fan, cone, or cylinder). As an example, the one or more transmitting antenna elements (not shown) may have an un-steered omnidirectional radiation pattern or may be able to produce a wide beam, such as the wide transmit beam 406. Either of these techniques enable the radar system 104 to illuminate a large volume of space. To achieve target angular accuracies and angular resolutions, however, the receiving antenna elements 402 and the digital beamformer 316 can be used to generate thousands of narrow and steered beams (e.g., 2000 beams, 4000 beams, or 6000 beams), such as the narrow receive beam 408. In this way, the radar system 104 can efficiently monitor the external environment and accurately determine arrival angles of reflections within the external environment.

Returning to FIG. 3, the transceiver 306 includes circuitry and logic for transmitting and receiving radar signals via the antenna array 304. Components of the transceiver 306 can include amplifiers, mixers, switches, analog-to-digital converters, filters, and so forth for conditioning the radar signals. The transceiver 306 can also include logic to perform in-phase/quadrature (I/Q) operations, such as modulation or demodulation. The transceiver 306 can be configured for continuous wave radar operations or pulsed radar operations. A variety of modulations can be used to produce the radar signals, including linear frequency modulations, triangular frequency modulations, stepped frequency modulations, or phase modulations.

The transceiver 306 can generate radar signals within a range of frequencies (e.g., a frequency spectrum), such as between 1 gigahertz (GHz) and 400 GHz, between 4 GHz and 100 GHz, or between 57 GHz and 63 GHz. The frequency spectrum can be divided into multiple sub-spectra that have a similar bandwidth or different bandwidths. The bandwidths can be on the order of 500 megahertz (MHz), 1 GHz, 2 GHz, and so forth. As an example, different frequency sub-spectra may include frequencies between approximately 57 GHz and 59 GHz, 59 GHz and 61 GHz, or 61 GHz and 63 GHz. Multiple frequency sub-spectra that have a same bandwidth and may be contiguous or non-contiguous may also be chosen for coherence. The multiple frequency sub-spectra can be transmitted simultaneously or separated in time using a single radar signal or multiple radar signals. The contiguous frequency sub-spectra enable the radar signal to have a wider bandwidth while the non-contiguous frequency sub-spectra can further emphasize amplitude and phase differences that enable the angle estimator 318 to resolve angular ambiguities. The attenuation mitigator 314 or the angle estimator 318 may cause the transceiver 306 to utilize one or more frequency sub-spectra to improve performance of the radar system 104, as further described with respect to FIGS. 5 and 6.

A power manager 320 enables the radar system 104 to conserve power internally or externally within the electronic device 102. In some implementations, the power manager 320 communicates with the gesture-feedback manager 106 to conserve power within either or both of the radar system 104 or the electronic device 102. Internally, for example, the power manager 320 can cause the radar system 104 to collect data using a predefined power mode or a specific gesture-frame update rate. The gesture-frame update rate represents how often the radar system 104 actively monitors the external environment by transmitting and receiving one or more radar signals. Generally speaking, the power consumption is proportional to the gesture-frame update rate. As such, higher gesture-frame update rates result in larger amounts of power being consumed by the radar system 104.

Each predefined power mode can be associated with a particular framing structure, a particular transmit power level, or particular hardware (e.g., a low-power processor or a high-power processor). Adjusting one or more of these affects the radar system's 104 power consumption. Reducing power consumption, however, affects performance, such as the gesture-frame update rate and response delay. In this case, the power manager 320 dynamically switches between different power modes such that gesture-frame update rate, response delay, and power consumption are managed together based on the activity within the environment. In general, the power manager 320 determines when and how power can be conserved, and incrementally adjusts power consumption to enable the radar system 104 to operate within power limitations of the electronic device 102. In some cases, the power manager 320 may monitor an amount of available power remaining and adjust operations of the radar system 104 accordingly. For example, if the remaining amount of power is low, the power manager 320 may continue operating in a lower-power mode instead of switching to a higher-power mode.

The lower-power mode, for example, may use a lower gesture-frame update rate on the order of a few hertz (e.g., approximately 1 Hz or less than 5 Hz) and consume power on the order of a few milliwatts (mW) (e.g., between approximately 2 mW and 4 mW). The higher-power mode, on the other hand, may use a higher gesture-frame update rate on the order of tens of hertz (Hz) (e.g., approximately 20 Hz or greater than 10 Hz), which causes the radar system 104 to consume power on the order of several milliwatts (e.g., between approximately 6 mW and 20 mW). While the lower-power mode can be used to monitor the external environment or detect an approaching user, the power manager 320 may switch to the higher-power mode if the radar system 104 determines the user is starting to perform a gesture. Different triggers may cause the power manager 320 to dynamically switch between the different power modes. Example triggers include motion or the lack of motion, appearance or disappearance of the user, the user moving into or out of a designated region (e.g., a region defined by range, azimuth, or elevation), a change in velocity of a motion associated with the user, or a change in reflected signal strength (e.g., due to changes in radar cross section). In general, the triggers that indicate a lower probability of the user interacting with the electronic device 102 or a preference to collect data using a longer response delay may cause a lower-power mode to be activated to conserve power.

Each power mode can be associated with a particular framing structure. The framing structure specifies a configuration, scheduling, and signal characteristics associated with the transmission and reception of the radar signals. In general, the framing structure is set up such that the appropriate radar data can be collected based on the external environment. The framing structure can be customized to facilitate collection of different types of radar data for different applications (e.g., proximity detection, feature recognition, or gesture recognition). During inactive times throughout each level of the framing structure, the power-manager 320 can turn off the components within the transceiver 306 in FIG. 3 to conserve power. The framing structure enables power to be conserved through adjustable duty cycles within each frame type. For example, a first duty cycle can be based on a quantity of active feature frames relative to a total quantity of feature frames. A second duty cycle can be based on a quantity of active radar frames relative to a total quantity of radar frames. A third duty cycle can be based on a duration of the radar signal relative to a duration of a radar frame.

Consider an example framing structure (not illustrated) for the lower-power mode that consumes approximately 2 mW of power and has a gesture-frame update rate between approximately 1 Hz and 4 Hz. In this example, the framing structure includes a gesture frame with a duration between approximately 250 ms and 1 second. The gesture frame includes thirty-one pulse-mode feature frames. One of the thirty-one pulse-mode feature frames is in the active state. This results in the duty cycle being approximately equal to 3.2%. A duration of each pulse-mode feature frame is between approximately 8 ms and 32 ms. Each pulse-mode feature frame is composed of eight radar frames. Within the active pulse-mode feature frame, all eight radar frames are in the active state. This results in the duty cycle being equal to 100%. A duration of each radar frame is between approximately 1 ms and 4 ms. An active time within each of the active radar frames is between approximately 32 μs and 128 μs. As such, the resulting duty cycle is approximately 3.2%. This example framing structure has been found to yield good performance results. These good performance results are in terms of good gesture recognition and presence detection while also yielding good power efficiency results in the application context of a handheld smartphone in a low-power state. Based on this example framing structure, the power manager 320 can determine a time for which the radar system 104 is not actively collecting radar data. Based on this inactive time period, the power manager 320 can conserve power by adjusting an operational state of the radar system 104 and turning off one or more components of the transceiver 306, as further described below.

The power manager 320 can also conserve power by turning off one or more components within the transceiver 306 (e.g., a voltage-controlled oscillator, a multiplexer, an analog-to-digital converter, a phase lock loop, or a crystal oscillator) during inactive time periods. These inactive time periods occur if the radar system 104 is not actively transmitting or receiving radar signals, which may be on the order of microseconds (μs), milliseconds (ms), or seconds (s). Further, the power manager 320 can modify transmission power of the radar signals by adjusting an amount of amplification provided by a signal amplifier. Additionally, the power manager 320 can control the use of different hardware components within the radar system 104 to conserve power. If the processor 308 comprises a lower-power processor and a higher-power processor (e.g., processors with different amounts of memory and computational capability), for example, the power manager 320 can switch between utilizing the lower-power processor for low-level analysis (e.g., implementing the idle mode, detecting motion, determining a location of a user, or monitoring the environment) and the higher-power processor for situations in which high-fidelity or accurate radar data is requested by the gesture-feedback manager 106 (e.g., for implementing the aware mode, the engaged mode, or the active mode, gesture recognition or user orientation).

Further, the power manager 320 can determine a context of the environment around the electronic device 102. From that context, the power manager 320 can determine which power states are to be made available and how they are configured. For example, if the electronic device 102 is in a user's pocket, then although the user is detected as being proximate to the electronic device 102, there is no need for the radar system 104 to operate in the higher-power mode with a high gesture-frame update rate. Accordingly, the power manager 320 can cause the radar system 104 to remain in the lower-power mode, even though the user is detected as being proximate to the electronic device 102, and cause the display 114 to remain in an off or other lower-power state. The electronic device 102 can determine the context of its environment using any suitable non-radar sensor 108 (e.g., gyroscope, accelerometer, light sensor, proximity sensor, capacitance sensor, and so on) in combination with the radar system 104. The context may include time of day, calendar day, lightness/darkness, number of users near the user, surrounding noise level, speed of movement of surrounding objects (including the user) relative to the electronic device 102, and so forth).

FIG. 5 illustrates additional details of an example implementation 500 of the radar system 104 within the electronic device 102. In the example 500, the antenna array 304 is positioned underneath an exterior housing of the electronic device 102, such as a glass cover or an external case. Depending on its material properties, the exterior housing may act as an attenuator 502, which attenuates or distorts radar signals that are transmitted and received by the radar system 104. The attenuator 502 may include different types of glass or plastics, some of which may be found within display screens, exterior housings, or other components of the electronic device 102 and have a dielectric constant (e.g., relative permittivity) between approximately four and ten. Accordingly, the attenuator 502 is opaque or semi-transparent to a radar signal 506 and may cause a portion of a transmitted or received radar signal 506 to be reflected (as shown by a reflected portion 504). For conventional radars, the attenuator 502 may decrease an effective range that can be monitored, prevent small targets from being detected, or reduce overall accuracy.

Assuming a transmit power of the radar system 104 is limited, and re-designing the exterior housing is not desirable, one or more attenuation-dependent properties of the radar signal 506 (e.g., a frequency sub-spectrum 508 or a steering angle 510) or attenuation-dependent characteristics of the attenuator 502 (e.g., a distance 512 between the attenuator 502 and the radar system 104 or a thickness 514 of the attenuator 502) are adjusted to mitigate the effects of the attenuator 502. Some of these characteristics can be set during manufacturing or adjusted by the attenuation mitigator 314 during operation of the radar system 104. The attenuation mitigator 314, for example, can cause the transceiver 306 to transmit the radar signal 506 using the selected frequency sub-spectrum 508 or the steering angle 510, cause a platform to move the radar system 104 closer or farther from the attenuator 502 to change the distance 512, or prompt the user to apply another attenuator to increase the thickness 514 of the attenuator 502.

Appropriate adjustments can be made by the attenuation mitigator 314 based on pre-determined characteristics of the attenuator 502 (e.g., characteristics stored in the computer-readable media 204 of the electronic device 102 or within the system media 310) or by processing returns of the radar signal 506 to measure one or more characteristics of the attenuator 502. Even if some of the attenuation-dependent characteristics are fixed or constrained, the attenuation mitigator 314 can take these limitations into account to balance each parameter and achieve a target radar performance. As a result, the attenuation mitigator 314 enables the radar system 104 to realize enhanced accuracy and larger effective ranges for detecting and tracking the user that is located on an opposite side of the attenuator 502. These techniques provide alternatives to increasing transmit power, which increases power consumption of the radar system 104, or changing material properties of the attenuator 502, which can be difficult and expensive once a device is in production.

FIG. 6 illustrates an example scheme 600 implemented by the radar system 104. Portions of the scheme 600 may be performed by the processor 308, the computer processors 202, or other hardware circuitry. The scheme 600 can be customized to support different types of electronic devices and radar-based applications (e.g., the gesture-feedback manager 106), and also enables the radar system 104 to achieve target angular accuracies despite design constraints.

The transceiver 306 produces raw data 602 based on individual responses of the receiving antenna elements 402 to a received radar signal. The received radar signal may be associated with one or more frequency sub-spectra 604 that were selected by the angle estimator 318 to facilitate angular ambiguity resolution. The frequency sub-spectra 604, for example, may be chosen to reduce a quantity of sidelobes or reduce an amplitude of the sidelobes (e.g., reduce the amplitude by 0.5 dB, 1 dB, or more). A quantity of frequency sub-spectra can be determined based on a target angular accuracy or computational limitations of the radar system 104.

The raw data 602 contains digital information (e.g., in-phase and quadrature data) for a period of time, different wavenumbers, and multiple channels respectively associated with the receiving antenna elements 402. A Fast-Fourier Transform (FFT) 606 is performed on the raw data 602 to generate pre-processed data 608. The pre-processed data 608 includes digital information across the period of time, for different ranges (e.g., range bins), and for the multiple channels. A Doppler filtering process 610 is performed on the pre-processed data 608 to generate range-Doppler data 612. The Doppler filtering process 610 may comprise another FFT that generates amplitude and phase information for multiple range bins, multiple Doppler frequencies, and for the multiple channels. The digital beamformer 316 produces beamforming data 614 based on the range-Doppler data 612. The beamforming data 614 contains digital information for a set of azimuths and/or elevations, which represents the field of view for which different steering angles or beams are formed by the digital beamformer 316. Although not depicted, the digital beamformer 316 may alternatively generate the beamforming data 614 based on the pre-processed data 608 and the Doppler filtering process 610 may generate the range-Doppler data 612 based on the beamforming data 614. To reduce a quantity of computations, the digital beamformer 316 may process a portion of the range-Doppler data 612 or the pre-processed data 608 based on a range, time, or Doppler frequency interval of interest.

The digital beamformer 316 can be implemented using a single-look beamformer 616, a multi-look interferometer 618, or a multi-look beamformer 620. In general, the single-look beamformer 616 can be used for deterministic objects (e.g., point-source targets having a single phase center). For non-deterministic targets (e.g., targets having multiple phase centers), the multi-look interferometer 618 or the multi-look beamformer 620 are used to improve accuracies relative to the single-look beamformer 616. Humans are an example of a non-deterministic target and have multiple phase centers 622 that can change based on different aspect angles, as shown at 624-1 and 624-2. Variations in the constructive or destructive interference generated by the multiple phase centers 622 can make it challenging for conventional radars to accurately determine angular positions. The multi-look interferometer 618 or the multi-look beamformer 620, however, perform coherent averaging to increase an accuracy of the beamforming data 614. The multi-look interferometer 618 coherently averages two channels to generate phase information that can be used to accurately determine the angular information. The multi-look beamformer 620, on the other hand, can coherently average two or more channels using linear or non-linear beamformers, such as Fourier, Capon, multiple signal classification (MUSIC), or minimum variance distortion less response (MVDR). The increased accuracies provided via the multi-look beamformer 620 or the multi-look interferometer 618 enable the radar system 104 to recognize small gestures or distinguish between multiple portions of the user.

The angle estimator 318 analyzes the beamforming data 614 to estimate one or more angular positions. The angle estimator 318 may utilize signal-processing techniques, pattern-matching techniques, or machine-learning. The angle estimator 318 also resolves angular ambiguities that may result from a design of the radar system 104 or the field of view the radar system 104 monitors. An example angular ambiguity is shown within an amplitude plot 626 (e.g., amplitude response).

The amplitude plot 626 depicts amplitude differences that can occur for different angular positions of the target and for different steering angles 510. A first amplitude response 628-1 (illustrated with a solid line) is shown for a target positioned at a first angular position 630-1. Likewise, a second amplitude response 628-2 (illustrated with a dotted line) is shown for the target positioned at a second angular position 630-2. In this example, the differences are considered across angles between −180 degrees and 180 degrees.

As shown in the amplitude plot 626, an ambiguous zone exists for the two angular positions 630-1 and 630-2. The first amplitude response 628-1 has a highest peak at the first angular position 630-1 and a lesser peak at the second angular position 630-2. While the highest peak corresponds to the actual position of the target, the lesser peak causes the first angular position 630-1 to be ambiguous because it is within some threshold for which conventional radars may be unable to confidently determine whether the target is at the first angular position 630-1 or the second angular position 630-2. In contrast, the second amplitude response 628-2 has a lesser peak at the second angular position 630-2 and a higher peak at the first angular position 630-1. In this case, the lesser peak corresponds to the target's location.

While conventional radars may be limited to using a highest peak amplitude to determine the angular positions, the angle estimator 318 instead analyzes subtle differences in shapes of the amplitude responses 628-1 and 628-2. Characteristics of the shapes can include, for example, roll-offs, peak or null widths, an angular location of the peaks or nulls, a height or depth of the peaks and nulls, shapes of sidelobes, symmetry within the amplitude response 628-1 or 628-2, or the lack of symmetry within the amplitude response 628-1 or 628-2. Similar shape characteristics can be analyzed in a phase response, which can provide additional information for resolving the angular ambiguity. The angle estimator 318 therefore maps the unique angular signature or pattern to an angular position.

The angle estimator 318 can include a suite of algorithms or tools that can be selected according to the type of electronic device 102 (e.g., computational capability or power constraints) or a target angular resolution for the gesture-feedback manager 106. In some implementations, the angle estimator 318 can include a neural network 632, a convolutional neural network (CNN) 634, or a long short-term memory (LSTM) network 636. The neural network 632 can have various depths or quantities of hidden layers (e.g., three hidden layers, five hidden layers, or ten hidden layers) and can also include different quantities of connections (e.g., the neural network 632 can comprise a fully-connected neural network or a partially-connected neural network). In some cases, the CNN 634 can be used to increase computational speed of the angle estimator 318. The LSTM network 636 can be used to enable the angle estimator 318 to track the target. Using machine-learning techniques, the angle estimator 318 employs non-linear functions to analyze the shape of the amplitude response 628-1 or 628-2 and generate angular probability data 638, which indicates a likelihood that the user or a portion of the user is within an angular bin. The angle estimator 318 may provide the angular probability data 638 for a few angular bins, such as two angular bins to provide probabilities of a target being to the left or right of the electronic device 102, or for thousands of angular bins (e.g., to provide the angular probability data 638 for a continuous angular measurement).

Based on the angular probability data 638, a tracker module 640 produces angular position data 642, which identifies an angular location of the target. The tracker module 640 may determine the angular location of the target based on the angular bin that has a highest probability in the angular probability data 638 or based on prediction information (e.g., previously-measured angular position information). The tracker module 640 may also keep track of one or more moving targets to enable the radar system 104 to confidently distinguish or identify the targets. Other data can also be used to determine the angular position, including range, Doppler, velocity, or acceleration. In some cases, the tracker module 640 can include an alpha-beta tracker, a Kalman filter, a multiple hypothesis tracker (MHT), and so forth.

A quantizer module 644 obtains the angular position data 642 and quantizes the data to produce quantized angular position data 646. The quantization can be performed based on a target angular resolution for the gesture-feedback manager 106. In some situations, fewer quantization levels can be used such that the quantized angular position data 646 indicates whether the target is to the right or to the left of the electronic device 102 or identifies a 90-degree quadrant the target is located within. This may be sufficient for some radar-based applications, such as user proximity detection. In other situations, a larger number of quantization levels can be used such that the quantized angular position data 646 indicates an angular position of the target within an accuracy of a fraction of a degree, one degree, five degrees, and so forth. This resolution can be used for higher-resolution radar-based applications, such as gesture recognition, or in implementations of the gesture zone, recognition zone, aware mode, engaged mode, or active mode as described herein. In some implementations, the digital beamformer 316, the angle estimator 318, the tracker module 640, and the quantizer module 644 are together implemented in a single machine-learning module.

These and other capabilities and configurations, as well as ways in which entities of FIG. 1-6 act and interact, are set forth below. The described entities may be further divided, combined, used along with other sensors or components, and so on. In this way, different implementations of the electronic device 102, with different configurations of the radar system 104 and non-radar sensors, can be used to implement the methods for reliable acceptance of user non-contact gesture inputs for a mobile device. The example operating environment 100 of FIG. 1 and the detailed illustrations of FIGS. 2-6 illustrate but some of many possible environments and devices capable of employing the described techniques.

Example Methods

FIG. 7 depicts example method 700, which enables methods for reliable acceptance of user non-contact gesture inputs for a mobile device. The method 700 can be performed with an electronic device that includes a display and a radar system that can provide a radar field. The radar system and radar field can provide radar data, based on reflections of the radar field from objects in the radar field, such as a user of the electronic device. For example, the radar data may be generated by, and/or received through, the radar system 104, as described with reference to FIG. 1. The radar data is used to determine interactions of the user with the electronic device, such as a presence of the user in the radar field, gestures made by the user in the radar field, and movement of the user relative to the electronic device. Based on the determination of the user's presence, movements, and gestures, the electronic device can enter and exit different modes of functionality and present different visual elements on the display. The visual elements provide feedback to the user to indicate the user's posture with respect to the device, the availability of different functionalities for the electronic device, and the user's interactions with the electronic device. Additional examples of the visual elements are described with respect to FIGS. 8-15.

The method 700 is shown as a set of blocks that specify operations performed but are not necessarily limited to the order or combinations shown for performing the operations by the respective blocks. Further, any of one or more of the operations may be repeated, combined, reorganized, or linked to provide a wide array of additional and/or alternate methods. In portions of the following discussion, reference may be made to the example operating environment 100 of FIG. 1 or to entities or processes as detailed in FIGS. 2-6, reference to which is made for example only. The techniques are not limited to performance by one entity or multiple entities operating on one device.

At 702, radar data is received from the radar system. A radar gesture is determined, based on the radar data. The radar data is determined based on reflections of a portion of the user moving within a gesture zone of the electronic device. Alternatively, the radar gesture based on the radar data is received. For example, the gesture-feedback manager 106 can use one or more subsets of the radar data received from the radar system 104 to detect a motion performed by the portion of the user, such as the hand 112 or an object, that is within a gesture zone 118 of the electronic device 102, as described with reference to FIG. 1. The user may perform the motion with an object that can be detected by the radar system, such as a ring, a bracelet or watch, or another item. The gesture-feedback manager 106 then determines, based on the radar data, whether the user's motion is a radar gesture. In other cases, another component of, or associated with, the electronic device can determine the radar gesture, or radar data that represents the radar gesture, and the gesture-feedback manager 106 can receive the radar gesture, or radar data that represents the radar gesture, from the other component.

As described with reference to FIG. 1, the gesture zone is a region or volume around the electronic device 102 within which the radar system 104 (or another module or application) can detect the user's hand. The gesture zone can be any suitable distance within which the radar system can recognize the user's hand, such as within three, five, seven, or nine inches. While the radar system 104 and gesture-feedback manager 106 may be able to recognize a radar gesture and determine an action associated with the radar gesture from greater distances, the gesture zone helps enable the electronic device to distinguish between intentional gestures and other user movements that are not intended to be used to interact with applications on the electronic device. As noted, the gesture zone can have various sub-zones with different shapes and sizes within the gesture zone and the visual properties of the gesture-confirmation element may vary in the different sub-zones.

The gesture-feedback manager (e.g., the gesture-feedback manager 106) can use any of a variety of techniques to determine the radar gesture based on the radar data (e.g., one or more subsets of the radar data). For example, based on the radar data, the gesture-feedback manager 106 can determine whether the motion of the portion of the user meets one or more criteria to be considered a radar gesture. The criteria can include various parameters of the motion, such as a path, shape, length, velocity, or distance from the electronic device. In some cases, the gesture-feedback manager 106 determines the parameters for the motion and compares them to gesture data in a gesture library 120, as described with reference to FIG. 1, to determine whether the motion matches a known radar gesture.

At 704, it is determined that the radar gesture corresponds to a control input of an application on the electronic device. The application may be currently executing or operating on the electronic device or not currently executing, but stored on the electronic device (e.g., by a memory device) or stored at another location that can be accessed by the electronic device. For example, as described with reference to FIG. 1, the gesture library 120, or another component, can store relationships between control inputs and radar gestures, and the gesture-feedback manager 106 can use the relationships in the gesture library 120 to determine whether the radar gesture corresponds to a control input of the application. Examples of the control input of the application include instructions (or a control signal) that cause the application to dismiss an alert or notification on the display of the electronic device, silence a ringer or alarm, or skip to a next or previous media item (such as a song, video, and so forth).

At 706, a gesture-confirmation element is provided on the display of the electronic device. The gesture-confirmation element indicates that the movement of the portion of the user within the gesture zone of the electronic device is determined to be the radar gesture and that the radar gesture corresponds to the control input of the application. For example, the gesture-feedback manager 106 can provide the gesture-confirmation element 122 on the display 114. In some cases, the gesture-confirmation element 122 can also or instead indicate that the application received the radar gesture, control input, and/or the control signal. In some implementations, as described with reference to FIG. 1, the gesture-feedback manager 106 provides the gesture-confirmation element 122 on the display 114 (or causes the display 114 to present the gesture-confirmation element 122) in response to the determination that the motion of the portion of the user is a radar gesture. In this implementation, the feedback element may be presented just after, or simultaneously with, the determination that the motion of the portion of the user is a radar gesture.

At 708, the application is caused to respond to the control input. For example, in implementations in which the application is currently executing, the gesture-feedback manager 106 can send the control input to the application. In implementations in which the application is not currently executing, gesture-feedback manager 106 can cause the application to begin executing and send the control input to the application.

Generally, as described with reference to FIG. 1, the gesture-confirmation element is a user-perceivable element, such as a visual element that appears on an active area of the display or an element that is not on the display (e.g., an LED, a haptic element, and/or an audio element). When the gesture-confirmation element is a visual element that appears on the active area of the display, the gesture-confirmation element may be provided at or along an edge of the display, as described with reference to FIG. 1, and may take any of a variety of shapes, sizes, colors, and other visual parameters or properties (e.g., luminosity, color, contrast, shape, saturation, or opaqueness). As described with reference to FIG. 1, the gesture-confirmation element 122 may be presented in different ways to indicate the type of interaction or the specific interaction that is associated with the gesture. For example, the visual element (e.g., the gesture-confirmation element 122) can move on the active area of the display in a way that corresponds to the radar gesture (or the movement of the user within the gesture zone). Thus, if the radar gesture is a swipe from left to right or bottom to top, the visual element can move on the display, from left to right or bottom to top, respectively.

In some implementations, as described with reference to FIG. 1, the visual element may have an area that is a portion of the active area of the display that has a luminosity or other visual property that is different from a luminosity or other visual property of another portion of the display that is proximate to the visual element. In this case, the visual element may also have a segment of an exterior border that is within a threshold distance from an edge of the active area of the display (e.g., adjacent to the edge with no gap or with a gap such as one pixel, two pixels, three pixels, one millimeter, two millimeters, three millimeters). Additionally, the luminosity (or other visual parameter) of the gesture-confirmation element may vary as the gesture-confirmation element extends across a distance from the edge of the active area of the display (e.g., have a luminosity at or along the edge of the display that decreases or increases as the shape extends away from the edge). In other implementations, the gesture-confirmation element may appear at a location on the display that is not an edge (e.g., the gesture-confirmation element may be presented in an interior region of the display and not be adjacent to or touch an edge of the display).

In some implementations of the method 700, the gesture-confirmation element may be presented as an adjustment to a visual element that is already being presented at or along the edge of the active area of the display (e.g., a previously presented visual element indicating that the application operating on the electronic device has the capability to receive a radar gesture). For example, in the example shown in FIG. 1, the detail view 100-1 shows a visual feedback element 124 already being presented on the example display 114-1. When the user's hand 112 moves left to right within the gesture zone 118, the visual feedback element 124 may be adjusted to become the example gesture-confirmation element 122, as shown in the detail view 100-2. The adjustment to the previously presented visual element can be a change to one or more visual properties of the previously presented visual element, such as a change to a size, shape, luminosity, color, contrast, shape, saturation level, or opaqueness.

The color of the gesture-confirmation element may be any suitable color that can be visually differentiated from the background of the display on which it is presented. The color may change based on any of a variety of factors, as described with reference to FIG. 1. In some implementations of the method 700, a component of the electronic device (e.g., the gesture-feedback manager 106), can determine a background color of a region of the display on which the gesture-confirmation element is displayed. In response to determining the background color, the gesture-confirmation element may be presented in another color that is different from the background color, which provides human-discernable contrast between the gesture-confirmation element and the background color, as described with reference to FIG. 1. In some cases, the color of the gesture-confirmation element can be continuously, automatically, and dynamically adjusted, based on changes to the background color.

As described with reference to FIG. 1, the gesture-confirmation element may appear, at least in part, as a brief animation. For example, the gesture-confirmation element may appear at the edge of the active display and then grow or shrink before taking on a default appearance. Similarly, the color, luminosity, or shape may change as the gesture-confirmation element appears or disappears (e.g., if the radar-gesture application stops operating) before taking on the default appearance. Further, the gesture-confirmation element may be an image that appears on the display, rather than an element that appears in a region of the display. The image may have visual parameters that are different from the parameters of an ambient background of the display, such as luminosity, saturation, or color. In other cases, the ambient background may be an image, and the gesture-confirmation element is the same image, with different visual parameters, such as luminosity, saturation, color, and so forth. In this way, the gesture-confirmation element can improve the user's experience by communicating to the user that a radar-gesture application is operating on the electronic device.

In some implementations of the method 700, the location of the gesture-confirmation element may be determined based on an orientation of content on the display and/or a direction of the radar gesture that is used to interact with the content. For example, as described with reference to FIG. 1, a component of the electronic device, such as the gesture-feedback manager 106, may obtain the orientation of the content on the display (e.g., from the application manager 116). Based on the orientation of the content, the display can determine the direction of the radar gesture that can be used to interact with the content and provide the gesture-confirmation element at a particular edge of the active area of the display that corresponds to the direction of the radar input. Thus, if the context of the displayed content is horizontal, the gesture-confirmation element is displayed at a top edge and, if the context of the displayed content is vertical, the gesture-confirmation element is displayed at a side edge.

Further, a change in an orientation of the electronic device with respect to the user may be detected and, based on the change in orientation, the gesture-confirmation element may be provided on a different edge of the display, in order to maintain the orientation and location of the gesture-confirmation element with respect to the user. For example, as described with reference to FIG. 1, the user may rotate the device from a vertical to a horizontal orientation to watch a video or from a horizontal to a vertical orientation to read an article. Based on the change in orientation, the gesture-feedback manager 106 can cause the display 114 to provide the gesture-confirmation element 122 on a different edge of the active display, in order to maintain an orientation and location of the gesture-confirmation element 122 with respect to the user. As noted, the orientation of the content may also be accounted for, and these features can be used in conjunction with each other to provide the gesture-confirmation element on the display at the location appropriate for the orientation of both the content on the display and the orientation of the display with respect to the user.

In some cases, it can be determined that the radar-gesture application running on the electronic device is operating in an immersive mode (e.g., in a full-screen mode without any presented controls). In response to this determination, the display can periodically provide the gesture-confirmation element. For example, as described with reference to FIG. 1, the gesture-confirmation element can be provided on the display for a presentation time duration and then stop being provided for a non-presentation time duration. Both the presentation time duration and the non-presentation time duration may be predetermined or selectable. The time durations may be selectable (e.g., by the user or by the gesture-feedback manager 106 based on various factors, such as the type of radar-gesture application running in the immersive mode, the status of the radar-gesture application, or the frequency with which the user employs a radar gesture).

The gesture-confirmation element may fade or disappear entirely when the user interacts with the electronic device using input other than a radar gesture (e.g., a touch or voice input). For example, as described with reference to FIG. 1, the user may decide to start an application using a touch command on the electronic device, while a radar-gesture application is also running. In this case, the gesture-confirmation element may fade or disappear when the user picks up the electronic device or touches the display. The gesture-confirmation element restarts when the user stops touching the display or puts down the electronic device (if one or more radar-gesture applications are still operating). The gesture-confirmation element may reappear or brighten immediately when the touch or voice input ends, or after a selectable default time duration. Similarly, when the radar-gesture application is an application that provides an alert or notification, the gesture-confirmation element appears when an alert or notification is displayed and, when the user interacts with the alert or notification using a radar gesture, the gesture-confirmation element disappears, unless other radar-gesture applications are running.

The gesture-confirmation element can be provided while the electronic device 102 is in a locked state or an unlocked state. Thus, the electronic device may provide the gesture-confirmation element when a part of the user is within the gesture zone (and a radar-gesture application is running), whether the user is authenticated or not authenticated. As described with reference to FIG. 1, the locked and unlocked states refer to a level of access to the electronic device. A locked state may be a state in which no user is authenticated and anyone using the device will have less than full rights or access (e.g., no access or rights, or limited access or rights). Examples of the locked state may include the aware and engaged modes of the electronic device as described herein. Similarly, an unlocked state can be a state in which at least one user is authenticated and that user has full rights and/or access to the device. An example of the unlocked state is the active mode of the electronic device, as described herein.

These techniques for the methods for reliable acceptance of user non-contact gesture inputs for a mobile device may be more secure than other authentication and feedback techniques. For example, a user's position, orientation, or use of radar gestures (especially user-defined gestures, micro-gestures, and posture or position-based gestures) are typically not duplicable or obtainable by an unauthorized person (unlike, for example, a password). Further, a radar image of the user (e.g., based on the radar data described above), even if it includes the user's face, does not visually identify the user like a photograph or video may do. Even so, further to the descriptions above, the user may be provided with controls allowing the user to make an election as to both whether and when any of the systems, programs, managers, modules, or features described in this document may enable collection of user information (e.g., images of the user, radar data describing the user, information about a user's social network, social actions or activities, profession, a user's preferences, or a user's current location), and whether and when the user is sent content or communications from a server. In addition, certain data may be treated in one or more ways before it is stored or used, so that personally identifiable information is removed. For example, a user's identity may be treated so that no personally identifiable information can be determined for the user, or a user's geographic location may be generalized where location information is obtained (such as to a city, zip/postal code, or state level), so that a particular location of a user cannot be determined. Thus, the user may have control over what information is collected about the user, how that information is used, and what information is provided to or about the user.

Example Visual Elements

As noted, the techniques and systems described herein can enable the electronic device 102 to provide feedback and notification to make the user aware that at least one application on the electronic device can receive input via radar gestures, and, in some cases, provide additional feedback regarding the use and results of the radar gestures. The feedback and notification are provided by one or more user-perceivable elements, such as visual elements that are presented on the display 114. The techniques and systems can also enable a determination of the user's absence, presence, and location, which can be used to provide a more-responsive and more-efficient authentication process. For example, the techniques enable the electronic device to anticipate when the user is ready to be authenticated and to more-accurately determine when to lock the device when the user is away. The feedback, visual elements, and other features enable interactions that are more convenient and less frustrating because the user is aware of the input modes and can be confident about different ways in which the device can interact and receive input. FIGS. 8-18 illustrate examples of the electronic device 102 running a radar-gesture application and describe examples of the visual elements that can be presented on the display to provide feedback to the user. Examples of the electronic device operating in multiple different modes and examples of the visual elements that can be presented on the display in the different modes are also described.

Consider FIG. 8, which illustrates generally, at 800, an example of a visual feedback element that can be used to indicate that a radar-gesture application is running on the electronic device 102. In FIG. 8, a detail view 800-1 shows an example display 114-4 to indicate a state of the electronic device 102 with no radar-gesture application running Another state of the electronic device 102, in which at least one radar-gesture application is running, is shown on another example display 114-5. A visual element 802 at the top of the example display 114-5 indicates that the electronic device 102 can receive input through radar gestures, as described above. The visual element 802 is shown as an illuminated line, but, as noted above, may be presented at another location, at a different illumination level (e.g., only partially illuminated), or as another shape or type of element. For example, in another detail view 800-2, an example display 114-6 is shown to indicate the state of the electronic device 102 with no radar-gesture application running Another state of the electronic device 102, in which at least one radar-gesture application is running, is shown on another example display 114-7. A visual element 804 at the top of the example display 114-7 indicates that the electronic device 102 can receive input through radar gestures, as described above. The visual element 804 is shown as an illuminated area (e.g., a glowing area). As with the visual element 802, the visual element 804 could be presented at another location on the display 114-7, at a different illumination level (e.g., more-illuminated or less-illuminated), or as another shape or type of element. Note that for clarity, no other elements (e.g., time, date, or application launch icons) are shown on the example displays 114-4 through 114-7. In other implementations, however, the visual elements 802 or 804 may be displayed along with other content on the display. Further, the visual elements 802 or 804 may be displayed while the electronic device 102 is in the aware mode, the engaged mode, the active mode, or another mode.

In some implementations, the electronic device 102 can also provide more-detailed visual feedback that is related to the availability of radar gestures. For example, the gesture-feedback manager 106 may cause the display 114 to present other visual elements that provide feedback regarding input received through radar gestures. FIGS. 918 illustrate additional details of some of the ways that visual elements can be used to provide the feedback related to the use of radar gestures.

For instance, consider FIGS. 9A-9D, which illustrate generally, at 900, examples of a visual feedback element that may be used to indicate that a user's hand is within a gesture zone that enables a radar-gesture application to receive a radar gesture (e.g., the gesture zone 118). The gesture zone 118 is an area around the electronic device 102 (or the radar system 104) (and within the radar field) within which the electronic device 102 can receive, interpret, and act on radar gestures, such as a swipe or a pinch. The gesture zone can extend any suitable distance from the electronic device 102 (e.g., approximately three, approximately five, approximately seven, or approximately nine inches).

In FIG. 9A, an example display 114-8 is shown in a state in which at least one radar-gesture application is running (e.g., similar to the example display 114-7 described with reference to FIG. 8). A user's hand 902 is shown near the example display 114-8, but outside the gesture zone 118 (the border of the gesture zone is shown as a dotted line 904). An example visual element 906 is shown as a glowing area (e.g., an area or shape with varying brightness, color, or other properties) near the top of the example display 114-8 with a luminosity that changes with distance from the top. In other implementations, the visual element 906 could be presented at another location or as another shape or type of element (e.g., a line, as shown in the detail view 800-1 of FIG. 8). In FIG. 9B, the user's hand 902 moves toward the electronic device and crosses the border 904 of the gesture zone, as shown by the arrow 908. In response to the electronic device detecting the movement 908, another visual element 910 replaces the visual element 906, as shown on an example display 114-9. In this example, the visual element 910 is a glowing area that is larger than the visual element 906 and has a different brightness or luminosity (e.g., less-, more-, or fully-illuminated). In other implementations, the visual element 910 could also be presented at another location or as another shape or type of element.

As shown in FIG. 9C, when the user's hand 902 is within the border 904 of the gesture zone, the visual element 910 can, in some implementations, be used to provide feedback that indicates smaller, non-gesture motion of the user's hand 902, which are represented by a double-ended arrow 912. For example, as shown on an example display 114-10, the visual element can move to indicate the user's hand movements by moving back and forth with the user's hand, as shown by an arrow 914. In FIG. 9D, the user's hand 902 is withdrawn outside the border 904 of the gesture zone, as shown by an arrow 916. In response to the motion of the user's hand, the display 114 returns to the state as shown in the example display 114-8, in which the visual element 906 is displayed near the top edge of the display 114.

In some implementations (not shown in FIG. 9A-9D), the non-gesture motions can be represented by other visual elements or changes to the visual elements. For example, a size and/or shape can change, or a center or focal point of the shape can move to represent the motions (while the shape itself remains stationary). Additionally or alternatively, changes to an intensity of the brightness or color can be used to represent the motion (e.g., the brightness or color of the shape, or part of the shape, change in accordance with the non-gesture motions. The visual elements 906 and 910, along with the motion of the visual element 910, can help the user understand when gestures are available, and provide feedback that indicates the electronic device 102 is aware of the relative position of the user's hand, which can improve the user's experience with the electronic device 102.

As described with reference to FIG. 9C, the electronic device 102 can provide visual feedback to represent smaller, non-gesture motion of the user's hand in the gesture zone, such as moving a visual element back and forth on the display, corresponding to the motion of the user's hand. Similarly, when the user makes a radar gesture (e.g., a swiping gesture to skip a song or an omni-gesture to dismiss an alert or notification), the electronic device 102 can provide feedback to notify the user that the gesture has been successfully received or that a gesture attempt was received but it was not clear enough to be confirmed as a radar gesture or did not correspond to a radar gesture for a radar-gesture application on the electronic device. For example, FIGS. 10 and 11 illustrate generally, at 1000 and 1100, sequences of example visual elements that can be used to notify the user that a gesture has been successfully received.

Generally, a visual feedback element, such as the gesture-confirmation element 122 can be used to provide feedback when the radar gesture is a left-to-right or right-to-left swipe (or when the radar gesture is a motion that includes a component in a left-to-right or right-to-left direction). In the case of a left-to-right motion, the movement of the gesture-confirmation element 122 that corresponds to the radar gesture is a movement from an initial position on the active display to another position on the active display, in which the other position is to a right side of the initial position. Similarly, in the case of a right-to-left motion, the movement of the gesture-confirmation element 122 that corresponds to the radar gesture is a movement from an initial position on the active display to another position on the active display, in which the other position is to a left side of the initial position.

The gesture-confirmation element 122 can also provide feedback when the radar gesture is a top-to-bottom or bottom-to-top swipe (or when the radar gesture is a motion that includes a component in a top-to-bottom direction or in a bottom-to-top direction). In the case of a top-to-bottom motion, the movement of the gesture-confirmation element 122 that corresponds to the radar gesture is a movement from an initial position on the active display to another position on the active display, in which the other position is to a lower side of the initial position. In the case of a bottom-to-top motion, the movement of the gesture-confirmation element 122 that corresponds to the radar gesture is a movement from an initial position on the active display to another position on the active display, in which the other position is to an upper side of the initial position.

In some implementations, the movement of the gesture-confirmation element 122 from the initial position on the active display to the other position on the active display (e.g., left-to-right, right-to-left, top-to-bottom, or bottom-to-top) includes a movement around a corner of the active area of the display. For example, the gesture-confirmation element 122 can start at an initial position along a top edge of the display and the movement can be a movement to the left or right and around a corner of the display. After moving around the corner, the gesture-confirmation element 122 may disappear indefinitely or disappear temporarily and reappear near the initial position (e.g., as if the gesture-confirmation element 122 went around the display).

Consider FIG. 10, which illustrates an example display 114-11 in a state in which at least one radar-gesture application is running and a user's hand 1002 is within a boundary of a gesture zone (e.g., similar to the state represented by the example display 114-9 described with reference to FIG. 9B). The example display 114-11 is presenting a visual element 1004, shown as a glowing area (e.g., an area or shape with varying brightness, color, or other properties) near the top of the example display 114-11 with a luminosity that changes with distance from the top. In this example, the visual element 1004 indicates the availability of input via radar gestures and that the user's hand is in the gesture zone. Continuing the example, the user makes a successful sliding or swiping gesture from left to right, as shown by the arrow 1006 (e.g., a gesture that meets the criteria for a radar gesture as described with reference to FIG. 1, corresponds to a control input of the application, and/or results in the application receiving or responding to the control signal). In response to the motion 1006 of the user's hand 1002, the visual element 1004 also moves, as shown in a sequence 1008 (shown within a dashed-line rectangle). An example display 114-12 illustrates the beginning of the sequence 1008, as the visual element 1004 begins moving to the right, as shown by an arrow 1010.

The sequence 1008 continues in another example display 114-13, in which the visual element 1004 bends around a corner of the example display 114-13, as shown by an arrow 1012. The visual element 1004 can continue down a side of the display 114 for a variable distance (e.g., as soon as a trailing end of the visual element completes the bend or after the trailing end has traveled a particular distance along the side) and then disappear. Continuing the sequence 1008 in another example display 114-14, the visual element 1004 reappears or regenerates from the left side of the example display 114-14 and moves toward the center position, as shown by an arrow 1014.

In some implementations, the visual element 1004 can reappear or regenerate at the initial position (as shown in the example display 114-11), rather than from the left side. When the sequence 1008 is complete, the display returns to the state as shown in the example display 114-11, with the visual element 1004 displayed near the top of the display 114 and may subtly track the user's hand 1002 while the hand remains within the boundary of the gesture zone. Note that in the example of FIG. 10, the sequence 1008 begins when the user begins the gesture. In other cases, the gesture and the sequence 1008 may be completed at different times or begin at another location on the display 114 and proceed in another direction, such as right to left, top to bottom, or bottom to top (e.g., if a radar gesture moved from right to left, top to bottom, or bottom to top).

Further, while the visual element 1004 of FIG. 10 is shown as a glowing area near the top of the display 114, the visual element could be presented at another location or as another shape or type of element. For example, FIG. 11 shows another example visual element 1102 as an illuminated line near the top edge of the display 114. In response to a left-to-right motion of the user's hand 1104 (shown by an arrow 1106), the visual element 1102 also moves, as shown in a sequence 1108 (shown within a dashed-line rectangle). An example display 114-15 illustrates the beginning of the sequence 1108, as the visual element 1102 begins moving to the right, as shown by an arrow 1110.

The sequence 1108 continues in another example display 114-16, in which the visual element 1102 bends around a corner of the example display 114-16, as shown by an arrow 1112. As noted, the visual element 1102 may continue down a side of the display for a variable distance and then disappear. Continuing the sequence 1108 in another example display 114-17, the visual element 1102 reappears or regenerates from the left side of the example display 114-17 (or reappears at the initial position) and moves toward the center position, as shown by an arrow 1114. When the sequence 1108 is complete, the display returns to a state in which the visual element 1102 is displayed near the top of the display 114.

In some implementations, the visual elements 1004 and 1102 can move in the horizontal direction (e.g., as shown in the example displays 114-12 and 114-15) while the radar gesture is being processed. When the radar gesture is successfully received (e.g., the control signal is sent and/or the application responds), the motion of the visual elements 1004 and 1102 changes direction (e.g., goes around the corner as shown in the example displays 114-13 and 114-16). This is particularly advantageous for the human visual system as the change in direction registers very quickly as compared, for example, to the element simply reaching the right edge of the screen.

Consider another example (not illustrated), in which a user is listening to music with a radar-gesture application on a smartphone (e.g., the electronic device 102). Assume the user decides to skip a track and makes a radar gesture over the smartphone. The radar gesture may be a swipe in either direction (e.g., left-to-right to skip to the next track or right-to-left to restart the current track or skip to a previous track). When the user's hand enters the gesture zone, a visual element, such as the gesture-confirmation element 122, is presented. As the user begins the radar gesture, the smartphone (e.g., through the gesture-feedback manager 106) presents the visual element in the sequence 1008 or 1108, as described with reference to FIGS. 10 and 11, respectively.

Other examples of visual feedback elements that can indicate a successful radar gesture include a visual element that bends or flexes (e.g., at one end, both ends, in the middle, or at another location) to show a successful radar gesture, such as a gesture made in a direction perpendicular to the display 114 or a gesture with a component that is perpendicular to the display 114. In other cases, the visual element 1004 may disappear at or before it reaches the corner, or it may continue down a side of the display 114 around the corner, or even move all the way around the display 114.

In some implementations, a visual feedback element, such as the gesture-confirmation element 122, can provide feedback that is independent of the motion of the radar gesture. For example, the feedback can be a sequence of changes to the gesture-confirmation element 122. Consider an example sequence in which the gesture-confirmation element 122 increases from an initial size to another size (e.g., become larger) and a luminosity (or other visual property) of at least a part of the gesture-confirmation element 122 increases from an initial luminosity to another luminosity (e.g., become brighter). Continuing the sequence, the gesture-confirmation element 122 then decreases in size until the gesture-confirmation element 122 is not visible. The gesture-confirmation element 122 then returns to the initial size and initial luminosity. Other sequences are also possible. For instance, the gesture-confirmation element 122 can begin the sequence with a decrease from an initial size to another size and have a corresponding increase or decrease in luminosity for at least a part of the gesture-confirmation element 122. The gesture-confirmation element 122 then changes in size again, becoming larger until it returns to the initial size.

FIG. 12 illustrates generally, at 1200, sequences of example visual elements that can be used to notify the user that a direction-independent radar gesture has been successfully received. In FIG. 12, an example display 114-18 is shown in a state in which at least one radar-gesture application is operating on the electronic device 102 and a user's hand 1202 is within a boundary of a gesture zone (e.g., similar to the state represented by the example display 114-9 described with reference to FIG. 9B). The example display 114-18 is presenting a visual element 1204, shown as a glowing area (e.g., an area or shape with varying brightness, color, or other properties) near the top of the example display 114-18 with a luminosity that changes with distance from the top. In this example, the visual element 1204 indicates the availability of input via radar gestures and that the user's hand is in the gesture zone. Continuing the example, assume that the radar-gesture application is presenting an alert on the display and that the user has decided to dismiss the alert. To do so, the user makes an omni-gesture toward the electronic device 102, as shown by the arrow 1206. In some implementations, the omni-gesture is a direction-independent radar gesture (e.g., because the omni-gesture is not intended to move content in a direction or skip/replay music, the direction of the gesture does not matter to its function).

In response to the motion 1206 of the user's hand 1202, the visual element 1204 changes, as shown in a sequence 1208 (shown within a dashed-line rectangle). An example display 114-19 illustrates the beginning of the sequence 1208, as the visual element 1204 becomes larger and brighter (e.g., increases in luminosity), and includes a bright line 1210 proximate to the edge of the display 114-19. The sequence 1208 continues in another example display 114-20, in which the visual element 1204 begins to decrease in size, as shown by a double-ended arrow 1212. Continuing the sequence 1208 in another example display 114-21, the visual element 1204 continues to decrease in size, shrinking toward the center of the upper edge example display 114-21, as shown by a double-ended arrow 1214. The sequence 1208 continues until the visual element 1204 disappears (not illustrated).

When the sequence 1208 is complete, the display returns to the state as shown in the example display 114-18, with the visual element 1204 displayed near the top of the display 114 and subtly tracking the user's hand 1202 while the hand remains within the boundary of the gesture zone. Note that while the sequence 1208 in the example of FIG. 12 begins when the user begins the gesture, the gesture and the sequence 1208 may be completed at different times or begin at another location on the display 114 and proceed in another manner or direction, such as shrinking then growing or changing color and/or brightness without changing size. The examples of visual feedback elements shown in FIGS. 10-12 illustrate just some of the ways in which the gesture-confirmation element 122 can be employed to help the user understand when a radar gesture has been accepted and when the gesture is complete, which can improve the user's experience with the electronic device 102.

FIG. 13 illustrates generally, at 1300, a sequence of example visual elements that can be used to notify the user that a gesture has failed to be successfully made or received. In FIG. 13, an example display 114-22 is shown in a state in which at least one radar-gesture application is running and in which a user's hand 1302 is within the boundary of a gesture zone (e.g., similar to the state represented in the example display 114-9 described with reference to FIG. 9B). The example display 114-22 is presenting a visual element 1304, shown as a glowing area (e.g., an area or shape with varying brightness, color, or other properties), near the top of the example display 114-22, with a luminosity that changes with distance from the top. In this example, the visual element 1304 indicates the availability of input via radar gestures and that the user's hand 1302 is within the gesture zone.

In the example of FIG. 13, assume that the user attempts to make a sliding or swiping gesture from left to right, but fails to meet the criteria for a swiping gesture or did not correspond to a radar gesture for a radar-gesture application on the electronic device, as described above. For example, as shown by a curved arrow 1306, the user's hand 1302 may fail to travel sufficient distance in a relevant direction before withdrawing. In this case, when the electronic device 102 (or the radar system 104) detects the motion 1306 of the user's hand 1302, which lacks sufficient definition to be successfully determined to be a radar gesture, the visual element 1304 moves as shown in a sequence 1308 (shown within a dashed-line rectangle). An example display 114-23 illustrates the beginning of the sequence 1308, as the visual element 1304 begins moving to the right, as shown by an arrow 1310.

Continuing the sequence 1308 in another example display 114-24, the visual element 1304 has stopped before reaching an opposite edge of the example display 114-24. In some cases, when the visual element 1304 stops, it may also shrink in size compared to its starting length as shown in the example display 114-22. The sequence 1308 continues in another example display 114-25, in which the visual element 1304 reverses direction and begins to move back toward its original location (the center in this example), as shown by another arrow 1312. If the visual element 1304 decreased in size as it stopped its movement to the right, then it also begins to grow back to its original length in this step of the example sequence 1308. In other implementations, rather than stopping (and, in some cases, shrinking), the visual element 1304 may slow and bounce before reversing direction.

When the sequence 1308 is complete, the display returns to the state as shown in the example display 114-22, with the visual element 1304 displayed near the top of the example display 114 and subtly tracking the user's hand 1302 while it remains within the boundary of the gesture zone (e.g., as shown in FIG. 9A-9D). The motion of the visual element 1304 can help the user understand when a gesture has not been successfully completed so that the user can learn techniques for making successful radar gestures and become aware when an attempted gesture fails (e.g., so it can be attempted again, if necessary), which can improve the user's experience with the electronic device 102.

Note that the sequence 1308 may begin when the electronic device 102 (or the gesture-feedback manager 106) detects (e.g., using one or more subsets of the radar data) that the user has attempted a radar gesture, but also determines that the gesture fails to meet at least one criterion that is necessary for acceptance. Accordingly, the attempted gesture and the sequence 1308 may be completed at different times, depending on the nature of the attempted gesture and the speed of the sequence 1308. Further, as described above, while the visual element 1304 is shown as a glowing area near the top of the display 114, the visual element 1304 may be presented at another location or as another shape or type of element (e.g., an illuminated line, as shown in the detail view 800-1 of FIG. 8). The sequence 1308 could also begin at another location on the display 114 and proceed in another direction, such as right to left, top to bottom, or bottom to top (e.g., if an attempted radar gesture moved from right to left, top to bottom, or bottom to top). Other examples of sequences that show an unsuccessful radar-gesture attempt include a visual element that partially collapses on itself, such as by briefly shrinking, and then returns to its original size and position.

In some implementations, the electronic device 102 includes a gesture-paused mode that can turn off or suspend the radar-gesture capabilities of the electronic device 102 when conditions indicate that the system may be inefficient or ineffective at receiving or interpreting the gestures. For example, when the electronic device 102 is moving at a velocity above a threshold, or when the direction in which the electronic device 102 is moving changes rapidly and repeatedly, the electronic device can enter the gesture-paused mode and provide visual feedback to the user. The electronic device 102 may determine to enter the gesture-paused mode based on input from any of a variety of sensors, including a radar sensor (e.g., the radar system 104), an inertial measurement unit (IMU), a proximity sensor (e.g., an active infrared proximity sensor), and so forth. For example, if the user is walking and listening to audio content with the electronic device 102 in the user's hand, swinging back and forth, the motion may be similar to a radar-based swipe gesture, but the user does not intend to skip tracks or adjust the volume. Accordingly, because the motion of the electronic device 102 can introduce ambiguity into the gesture interpretation process, the electronic device 102 may determine to enter the gesture-paused mode until the ambiguity is resolved (e.g., the user stops walking).

FIG. 14 illustrates generally, at 1400, example visual elements that may be used to indicate that a radar-gesture application is available to receive radar gestures, but that feature is currently paused. The gesture-paused mode may be activated whenever radar gestures are available, whether the user's hand is in or out of the gesture zone. In FIG. 14, an example display 114-26 is shown in a state in which at least one radar-gesture application is running and a user's hand is within the boundary of a gesture zone (e.g., similar to the state represented in the example display 114-9 described with reference to FIG. 9B). The example display 114-26 is presenting a visual element 1402, shown as an illuminated line near the top of the example display 114-26, to indicate the availability of input via radar gestures and that the user's hand is within the gesture zone. If the user takes an action that causes the electronic device 102 to enter the gesture-paused mode (e.g., the user's hand begins moving back and forth as the user is walking, as shown by an arrow 1404), the visual element 1402 can change, as shown in a sequence 1406 (within a dashed-line rectangle).

An example display 114-27 illustrates the beginning of the sequence 1406 as another visual element 1408 replaces the visual element 1402, in response to the electronic device 102 detecting the movement 1404. As shown on the example display 114-27, the visual element 1408 is another line that is shorter and dimmer than the visual element 1402. In implementations in which the visual element 1402 has a particular color, the visual element 1408 may have a different color from that of the visual element 1402 (e.g., the color may change from the particular color to another color, such as grey or white). The sequence 1406 continues in another example display 114-28, in which the visual element 1408 begins moving to the right, as shown by an arrow 1410. Continuing the sequence 1406 in another example display 114-29, the visual element 1408 moves to the left as shown by an arrow 1412. In the sequence 1406, the visual element 1408 may stop and reverse direction before it reaches a side of the display or go all the way to the edge before reversing direction. In some implementations, the visual element 1408 may further shrink when it stops to reverse directions and then return to another size when, after, or as, it begins moving in the opposite direction. Further, the oscillation of the visual element 1408 may match the condition upon which the gesture-paused mode is based. For example, in the case of the user's arms swinging, the velocity or frequency of the oscillation of the visual element 1408 may approximately match the velocity or frequency of the user's hand moving.

As described above, while the visual element 1408 is shown as an illuminated line near the top of the display 114, the visual element 1408 can be presented at another location or as another shape or type of element (e.g., as shown in FIGS. 9A-9D or in the detail view 800-2 of FIG. 8). The sequence 1406 can also begin at another location on the display 114 and proceed in another direction, such as right to left, top to bottom, or bottom to top (e.g., depending on the orientation of content on the display 114, the direction of the a radar gesture, or another factor).

For example, FIG. 15 shows, generally at 1500, another example sequence 1502 that describes visual feedback that can be used to show a user that the electronic device 102 is in the gesture-paused mode. The example sequence 1502 (shown within a dashed-line rectangle) begins with an example display 114-30, which shows an example visual element 1504 as a glowing area near the top edge of the display 114. In response to an action that causes the electronic device 102 to enter the gesture-paused mode (e.g., the back-and-forth motion shown by the arrow 1404 in FIG. 14), the visual element 1504 dims in brightness and shrinks, as shown in an example display 114-31 by an arrow 1506. The sequence 1502 continues in another example display 114-32, in which the visual element 1504 has stopped shrinking and is displayed near the center of the top edge of the display 114. When the electronic device 102 exits the gesture-paused mode, the display returns to a state in which the visual element 1504 is displayed near the top of the display 114.

In some cases, the example visual element 1504 can have a color (e.g., blue, green, or a combination of more than one color). In these cases, the step described with reference to the example display 114-31 includes a change in color. The change may be to another color, such as blue to yellow. In other cases, the visual element 1504 becomes colorless, and is merely a contrasting glowing area, so that against a dark background it is a lighter area and against a light background it is a darker area.

When the electronic device 102 exits the gesture-paused mode, the sequence 1406 (or 1502) is complete and the display 114 returns to an appropriate state, depending on whether there are radar-gesture applications running and on the location of the user's hand. The sequence 1406 (or 1502) can help the user understand when gestures may be paused and allow the user to adjust how the electronic device 102 is used to avoid or take advantage of the gesture-paused mode, which can improve the user's experience with the electronic device 102.

In some cases (not shown in FIG. 14 or FIG. 15), the user's motion may not introduce ambiguity, such as a situation in which the user is walking with the electronic device and holding it steady in front of the user. In these cases, the electronic device does not enter the gesture-paused mode and the visual element 1402 (or 1504) may change one or more visual parameters to alert the user that radar gestures are available, even while the user and the electronic device are in motion. For example, the visual element 1402 (or 1504) may change from a default color to another color (e.g., from grey to blue, grey to white, or white to blue).

In some implementations, the electronic device 102 can determine that the radar-gesture application running on the electronic device 102 is operating in an immersive mode (e.g., in a full-screen mode without any presented controls). In response to this determination, the display can periodically provide the visual elements described with reference to FIGS. 8-15 (e.g., the visual elements 802, 804, 906, 910, 1004, 1102, 1204, 1304, 1402, 1408, 1504, and/or the gesture-confirmation element 122). For example, the visual element can be provided on the display for a time duration and then stop being provided for another time duration. The time durations may be selectable (e.g., by a user or by the electronic device 102, based on factors such as the type of radar-gesture application running in the immersive mode, the status of the radar-gesture application, or the frequency with which the user employs a radar gesture).

Further, the visual elements described above with reference to FIGS. 8-15 (e.g., the visual elements 802, 804, 906, 910, 1004, 1102, 1204, 1304, 1402, 1408, 1504, and/or the gesture-confirmation element 122), may be presented in any suitable color that can be visually differentiated from the background of the display on which it is presented. Further, the color of the visual elements may change based on any of a variety of factors, such as an operational state of the electronic device or an ambient background color of the display. For example, the gesture-feedback manager 106 (or another entity, module, or manager) can determine a background color of a region of the display on which the visual element is, or will be, displayed. In response to determining the background color, the visual element may be presented in another color that is different from the background color. The different color can provide human-discernable contrast between the visual element and the background color to make it easier for the user to see the visual element. In some cases, the color of the visual element can be continuously, automatically, and dynamically adjusted, based on changes to the background color.

In some cases, as described herein, the visual element may be hidden even when radar gestures are available (e.g., because the user interacted with a voice or touch input, or in order to reduce the risk of screen burn-in). In this situation, the visual element (e.g., the example visual elements illustrated in FIGS. 8-15), may still be shown when the appropriate conditions are met (e.g., the user makes a successful or unsuccessful radar gesture or the gesture-paused mode is activated). Consider a variation of the music player example above, in which the visual element is hidden while the user is listening to music and using a voice input to open another application. In this example, the user performs a radar gesture to skip a song, and the display presents the sequence 1008 (or 1108) to notify the user that the radar gesture was successful.

The user's location and movements can also be used to detect user actions that are categorized as indications of the user's intention to interact (or not interact) with the electronic device. For example, the electronic device may have access to a library (e.g., in a memory device) of actions that are categorized as indicators of a user's intent to interact or not interact with the device (e.g., reaching for the electronic device, turning or walking toward or away from the electronic device, leaning toward or looking at the electronic device). In some cases, the electronic device may also include machine-learning technology that can add, remove, or modify the actions stored in the library. Based on the detection of the user's presence, movements, and intention, the electronic device can cause the electronic device to enter and exit different modes of functionality and present different visual elements on a display, based on the modes. These modes can enable different functionalities for the electronic device, and help the user understand the mode the electronic device is operating in, and the services and functions that are available. FIGS. 16-18 illustrate the electronic device operating in the multiple modes and describe examples of the visual elements that can be presented on the display in the different modes.

For instance, when the user is not detected near the electronic device (e.g., within the radar field 110 or the recognition zone), the device operates in a dormant mode. In the dormant mode, the display (e.g., the display 114) may present fewer visual elements than in other modes, or no visual elements and the display may be on or off. When the electronic device determines the presence of the user within the recognition zone (e.g., using radar data, or one or more subsets of the radar data, from the radar system 104), the electronic device exits the dormant mode and enters an aware mode. In the aware mode, the display presents one or more visual elements that can indicate a status or functionality level of the electronic device.

While the electronic device is in the aware mode, the electronic device can detect a user action that is categorized as an indication of a user intent to interact with the electronic device. In response to detecting this user action, the electronic device can prepare an authentication system to perform an authentication process. In some implementations, when the electronic device detects the indication of the user's intent to interact, the electronic device also exits the aware mode and enters an engaged mode. In the engaged mode, the display presents additional or alternate visual elements that can indicate changes in the status or functionality level of the electronic device. The electronic device can also detect a trigger event and, based on the trigger event, cause the authentication system to authenticate the user. In response to the user being authenticated, the electronic device exits the aware or engaged mode and enters an active mode. In the active mode, the display presents additional or alternate visual elements that can indicate changes in the status or functionality level of the electronic device.

FIG. 16 illustrates an example 1600 of an electronic device transitioning from the dormant mode to the aware mode. A detail view 1600-1 shows the electronic device 102 in the dormant mode while a user 1602 is outside of a recognition zone 1604. In this example, the recognition zone 1604 has a wedge shape, but as noted, the recognition zone 1604 can take any suitable shape or size. Continuing the example, in this case the display 114 is not presenting any visual elements in the dormant mode, as shown on an example display 114-33. In another detail view 1600-2, the user 1602 is closer to the electronic device 102, which has determined that the user 1602 has entered the recognition zone 1604. Based on this determination, the electronic device 102 exits the dormant mode and enters the aware mode, as shown by an arrow 1606.

In the detail view 1600-2, multiple visual elements are presented on an example display 114-34. For example, in the aware mode, the example display 114-34 presents a time-of-day element 1608 (a clock), a date element 1610, a connectivity status element 1612 (e.g., Wi-Fi, cellular, or other network connectivity), and a battery-level indicator element 1614 (including a graphical element and a percentage indicator). In the detail view 1600-2, the remainder of the example display 114-34 is blank. In some implementations, however, additional elements may be displayed, including a background image, such as a wallpaper or other image. Though not shown in FIG. 16, if the user 1602 exits the recognition zone 1604, the electronic device 102 may stop displaying the visual elements and return to the dormant mode (immediately or after the user 1602 has been outside the recognition zone 1604 for a selectable predetermined amount of time).

FIG. 17 illustrates an example 1700 of an electronic device transitioning from the aware mode to the optional engaged mode. A detail view 1700-1 shows the user 1602 within the recognition zone 1604 and the electronic device 102 in the aware mode, as described with reference to FIG. 16, including displaying multiple visual elements (1608, 1610, 1612, 1614) on an example display 114-35. Another detail view 1700-2 shows the user 1602 reaching for the electronic device 102. The electronic device 102 detects the reach (e.g., using one or more subsets of the radar data) as a user action that is an indication of a user intent to interact with the electronic device 102. In response to detecting this user action indicating intent, the electronic device 102 exits the aware mode and enters the engaged mode, as shown by an arrow 1702.

In the detail view 1700-2, additional visual elements are presented on an example display 114-36. For example, in the engaged mode, the example display 114-36 presents a background image 1704 (in this case, an image of the Golden Gate Bridge). The background image 1704 may have dynamic features that adjust with the context of the user, such as animation, or varying brightness or transparency levels that change depending on the distance or speed of the reach. While in the engaged mode, the electronic device 102 also prepares an authentication system to perform an authentication process (note that in some cases, the electronic device 102 does not enter the engaged mode and instead prepares the authentication system while in the aware mode, in response to the user action that indicates user intent). Accordingly, the example display 114-36 also presents a lock icon 1706, which indicates that full access to the electronic device 102 is unavailable until the user 1602 is authenticated. In some implementations, additional visual elements may be displayed on the example display 114-36, and some or all of the visual elements presented on the example display 114-35 may cease being presented. Though not shown in FIG. 17, if the user 1602 withdraws the reach gestures, the electronic device 102 may exit the engaged mode and return to the aware mode (immediately or after the reach has been withdrawn for a selectable predetermined amount of time).

FIG. 18 illustrates an example 1800 of an electronic device transitioning from the engaged mode to the active mode after the user 1602 is authenticated (note that in some implementations, the electronic device can transition to the active mode from the aware mode). A detail view 1800-1 shows the user 1602 within the recognition zone 1604 and the electronic device 102 in the engaged mode, as described with reference to FIG. 17, including displaying multiple visual elements on an example display 114-37 (1608, 1610, 1612, 1614, 1704, 1706). As noted with reference to FIG. 17, when the user reaches for the electronic device 102, the authentication system prepares to authenticate the user 1602. In FIG. 18, another detail view 1800-2 shows that the user 1602 has picked up the electronic device 102. The electronic device 102 determines that being picked up is a trigger event, as described above, and authenticates the user 1602. When the user 1602 is authenticated, the electronic device 102 exits the engaged mode (or the aware mode) and enters an active mode, as shown by an arrow 1802.

Additional visual elements associated with the active mode may also be presented on an example display 114-38, as shown in the detail view 1800-2. For example, in the active mode, the example display 114-38 continues to present the visual elements associated with the aware mode, but the background image 1704 (associated with the engaged mode) has changed to another background image 1804, a beach silhouette (note that because the background image 1804 has a different color scheme, some of the visual elements have changed contrast or color so that they remain visible to the user 1602). Additionally, the engaged mode lock icon 1706 has transitioned to an unlock icon 1806, which indicates that the user 1602 is authenticated. In some implementations, the unlock icon 1806 may be presented for a duration of time and then fade. While not illustrated in FIG. 18, additional visual elements may be displayed on the example display 114-38 after the unlock icon 1806 fades, such as an instruction (e.g., “Swipe or tap to open”), one or more application launch icons, or other visual elements available to the electronic device 102.

In some implementations, the user 1602 may remain authenticated as long as the user 1602 remains within the recognition zone (e.g., the recognition zone 1604) or within another defined area within which the radar system can detect the presence of the user 1602. In these implementations, the display 114 may remain powered and able to receive input and present content, or the screen may turn off to save battery power. Because the user 1602 remains authenticated, even if the screen is off, the user can access the electronic device 102 by touching the screen, picking up the device, or another action, without having to be re-authenticated. In this way, the user's enjoyment and experience with the electronic device 102 can be improved while preserving battery power.

Further, the described progression between modes (e.g., from the dormant mode, through the aware and engaged modes, to authentication and the active mode), may instead run in an opposite direction. For example, when the electronic device 102 is in the active mode and the user 1602 sets it down (e.g., another trigger event occurs), the electronic device may enter a locked state (e.g., de-authenticate the user 1602), and/or place the electronic device 102 in the engaged or aware mode, as described above. Accordingly, if the user's hand remains near the electronic device 102 (e.g., remains in a “reach” position), the electronic device 102 may remain in the engaged mode. Conversely, if the user's hand is withdrawn, the electronic device 102 may enter the aware mode. Then, as noted, the electronic device 102 may remain in the aware mode while the user is in the recognition zone. During this progression between zones, the display 114 may present the visual elements described above for each zone, to indicate the changing status of the electronic device 102 to the user 1602.

As noted, in some implementations, applications running on the electronic device 102 may be able to receive input through radar-based touch-independent gestures (radar gestures). In these cases, the radar system 104 may detect a reach by the user and perform actions, based on the context of the electronic device 102. For example, when the electronic device is in any of the modes described above, the user may receive a phone call, receive an alarm, alert, or notification, or play music through the electronic device. In these situations, the user may reach toward the electronic device to respond to the action. Thus, a reach may reduce or silence the ringer or notification during an incoming call or an alarm. Further, if the user notices an alert or notification is being displayed, and reaches toward the electronic device, the notification may be dismissed or become interactive. For example, upon detecting the user's reach, the electronic device may display the notification in a mode that allows the user to respond by dismissing or postponing the alert/notification, replying (in the case of a message or email notification), or in another manner. In some cases, the displayed notification may change color or size as well. In the example of the user listening to music, a reach may cause the electronic device to present a control screen for the music player, so that the user can control the track, volume, or other parameter.

Some or all of these features may be available in different modes, and which features are available may be user-selectable. For example, the user may allow volume silencing and music control in all modes but allow responding to alerts and notifications only in the active mode (e.g., when the user has been authenticated and has not left the recognition zone). Other combinations of features and permission levels may also be selected by the user.

Among the advantages of the described implementations, including implementations in which radar sensing is used to detect the presence of the user within a recognition zone, and further including implementations in which radar is used to detect user action that is categorized as an indication of a user intent to interact with the electronic device, either of which might alternatively be achievable using the on-device camera that is provided with most modern smartphones, is that the power usage of the radar facility is substantially less than the power usage of the camera facility, while the propriety of the results can often be better with the radar facility than with the camera facility. For example, using the radar facility described hereinabove, the desired user-state or user-intention detection can be achieved at average power ranging from single-digit milliwatts to just a few dozen milliwatts (e.g., 10 mW, 20 mW, 30 mW or 40 mW), even including the processing power for processing the radar vector data to make the determinations. At these low levels of power, it would be readily acceptable to have the radar facility in an always-on state. As such, for example, with the smartphone radar facility in the always-on state, the desired delightful and seamless experience presently described can still be provided for a user that has been sitting across the room from their smartphone for many hours.

In contrast, the optical cameras provided with most of today's smartphones typically operate at hundreds of milliwatts of power (e.g., an order of magnitude higher than 40 mW, which is 400 mW). At such power rates, optical cameras would be disadvantageous because they would significantly reduce the battery life of most of today's smartphones, so much so as to make it highly impractical, if not prohibitive, to have the optical camera in an always-on state. An additional advantage of the radar facility is that the field of view can be quite large, readily enough to detect a user walking up from any direction even when lying flat and face-up on a table (for many typical implementations in which the radar chip is facing outward in the same general direction as the selfie camera) and, furthermore, by virtue of its Doppler processing ability can be highly effective (especially at operating frequencies near 60 GHz) in detecting even relatively subtle movements of moving bodies from the variety of directions.

Additionally, the radar facility can operate in environments in which the performance of the camera facility is reduced or restricted. For example, in lower-light environments, the camera facility may have a reduced ability to detect shape or movement. In contrast, the radar facility performs as well in lower-light as in full light. The radar facility can also detect presence and gestures through some obstacles. For instance, if the smartphone is in a pocket of a jacket or pair of pants, a camera facility cannot detect a user or a gesture. The radar facility, however, can still detect objects in its field, even through a fabric that would block the camera facility. An even further advantage of using a radar facility over an onboard video camera facility of a smartphone is privacy, because a user can have the advantages of the herein described delightful and seamless experiences while at the same time not needing to be worried that there is a video camera taking video of them for such purposes.

Example Computing System

FIG. 19 illustrates various components of an example computing system 1900 that can be implemented as any type of client, server, and/or electronic device as described with reference to the previous FIGS. 1-18 to implement methods for reliable acceptance of user non-contact gesture inputs for a mobile device.

The computing system 1900 includes communication devices 1902 that enable wired and/or wireless communication of device data 1904 (e.g., radar data, authentication data, reference data, received data, data that is being received, data scheduled for broadcast, and data packets of the data). The device data 1904 or other device content can include configuration settings of the device, media content stored on the device, and/or information associated with a user of the device (e.g., an identity of a person within a radar field or customized gesture data). Media content stored on the computing system 1900 can include any type of radar, biometric, audio, video, and/or image data. The computing system 1900 includes one or more data inputs 1906 via which any type of data, media content, and/or inputs can be received, such as human utterances, interactions with a radar field (e.g., a radar gesture), touch inputs, user-selectable inputs or interactions (explicit or implicit), messages, music, television media content, recorded video content, and any other type of audio, video, and/or image data received from any content and/or data source.

The computing system 1900 also includes communication interfaces 1908, which can be implemented as any one or more of a serial and/or a parallel interface, a wireless interface, any type of network interface, a modem, and as any other type of communication interface. The communication interfaces 1908 provide a connection and/or communication links between the computing system 1900 and a communication network by which other electronic, computing, and communication devices communicate data with the computing system 1900.

The computing system 1900 includes one or more processors 1910 (e.g., any of microprocessors, controllers, or other controllers) that can process various computer-executable instructions to control the operation of the computing system 1900 and to enable techniques for, or in which can be implemented, the methods for reliable acceptance of user non-contact gesture inputs for a mobile device. Alternatively or additionally, the computing system 1900 can be implemented with any one or combination of hardware, firmware, or fixed logic circuitry that is implemented in connection with processing and control circuits, which are generally identified at 1912. Although not shown, the computing system 1900 can include a system bus or data transfer system that couples the various components within the device. The system bus can include any one or combination of different bus structures, such as a memory bus or memory controller, a peripheral bus, a universal serial bus, and/or a processor or local bus that utilizes any of a variety of bus architectures. Also not shown, the computing system 1900 can include one or more non-radar sensors, such as the non-radar sensors 108.

The computing system 1900 also includes computer-readable media 1914, such as one or more memory devices that enable persistent and/or non-transitory data storage (e.g., in contrast to mere signal transmission), examples of which include random access memory (RAM), non-volatile memory (e.g., any one or more of a read-only memory (ROM), flash memory, EPROM, EEPROM, etc.), and a disk storage device. A disk storage device may be implemented as any type of magnetic or optical storage device, such as a hard disk drive, a recordable and/or rewriteable compact disc (CD), any type of a digital versatile disc (DVD), and the like. The computing system 1900 can also include a mass storage media device (storage media) 1916.

The computer-readable media 1914 provides data storage mechanisms to store the device data 1904, as well as various device applications 1918 and any other types of information and/or data related to operational aspects of the computing system 1900. For example, an operating system 1920 can be maintained as a computer application with the computer-readable media 1914 and executed on the processors 1910. The device applications 1918 may include a device manager, such as any form of a control application, software application, signal-processing and control modules, code that is native to a particular device, an abstraction module, a gesture recognition module, and/or other modules. The device applications 1918 may also include system components, engines, modules, or managers to implement the methods for reliable acceptance of user non-contact gesture inputs for a mobile device, such as the radar system 104, the gesture-feedback manager 106, the application manager 116, or the gesture library 120. The computing system 1900 may also include, or have access to, one or more machine-learning systems.

Several examples are described below.

Example 1

A method implemented in an electronic device comprising a display and a radar system, the method comprising: receiving radar data from the radar system, the radar data determined based on reflections of a portion of a user moving within a gesture zone of the electronic device and determining a radar gesture based on the radar data, or receiving a radar gesture; determining that the radar gesture corresponds to a control input of an application on the electronic device; providing a gesture-confirmation element on the display of the electronic device, the gesture-confirmation element indicating that the movement of the portion of the user within the gesture zone of the electronic device is determined to comprise the radar gesture and that the radar gesture corresponds to the control input of the application; and causing the application to respond to the control input.

Example 2

The method of example 1, wherein the application on the electronic device is currently executing and causing the application to respond to the control input comprises sending the control input to the application.

Example 3

The method of example 1, wherein the application on the electronic device is not currently executing and wherein causing the application to respond to the control input comprises: executing the application; and sending the control input to the application.

Example 4

The method of any of examples 1-3, wherein the gesture-confirmation element is a visual element that appears on an active area of the display.

Example 5

The method of example 4, wherein the visual element moves on the active area of the display, the movement of the visual element corresponding to the movement of the portion of the user within the gesture zone.

Example 6

The method of example 5, wherein the radar gesture is a first motion that includes a component in a left-to-right direction and the movement of the gesture-confirmation element comprises moving from a first position on the active display to a second position on the active display, the second position to a right side of the first position; or the a radar gesture is a second motion that includes a component in a right-to-left direction and the movement of the gesture-confirmation element comprises moving from a third position on the active display to a fourth position on the active display, the fourth position to a left side of the third position.

Example 7

The method of example 5, wherein: the radar gesture is a first motion that includes a component in a top-to-bottom direction and the movement of the gesture-confirmation element comprises moving from a first position on the active display to a second position on the active display, the second position to a lower side of the first position; or the radar gesture is a second motion that includes a component in a bottom-to-top direction and the movement of the gesture-confirmation element comprises moving from a third position on the active display to a fourth position on the active display, the fourth position to an upper side of the third position.

Example 8

The method of example 6 or example 7, wherein the moving from the first position on the active display to the second position on the active display or from the third position on the active display to the fourth position on the active display, includes: moving around a corner of the active area of the display; and disappearing from the active area of the display.

Example 9

The method of example 5, wherein the movement of the gesture-confirmation element comprises: an increase from a first size of the gesture-confirmation element to a second size of the gesture-confirmation element, the second size larger than the first size; an increase from a first luminosity of at least part of the gesture-confirmation element to a second luminosity of the at least part of the gesture-confirmation element, the second luminosity greater than the first luminosity; a decrease from the second size of the gesture-confirmation element, the decrease continuing until the gesture-confirmation element is not visible; and a return to the first size and first luminosity of the gesture-confirmation element.

Example 10

The method of example 4, wherein the gesture-confirmation element is a visual element that includes: a visual property, the visual property comprising at least one of a luminosity, a color, a contrast, a shape, a saturation, or an opaqueness that is different from the visual property of another portion of the display that is proximate to the visual element; and a segment of an exterior border that is within a threshold distance of an edge of the active area of the display.

Example 11

The method of example 10, wherein the visual property of the visual element varies across the area of the visual element.

Example 12

The method of any of the preceding examples, further comprising: determining a background color of a region of the display on which the gesture-confirmation element is displayed; and responsive to determining the background color of the region of the display on which the gesture-confirmation element is displayed, causing the display to present the gesture-confirmation element in another color that is different from the background color, the different color effective to provide human-discernable contrast between the gesture-confirmation element and the region of the display on which the gesture-confirmation element is displayed.

Example 13

An electronic device comprising: a computer processor; a radar system, implemented at least partially in hardware, configured to: provide a radar field; sense reflections from a user in the radar field; analyze the reflections from the user in the radar field; and provide, based on the analysis of the reflections, radar data; and a computer-readable media having instructions stored thereon that, responsive to execution by the computer processor, implement a radar-based gesture-feedback manager configured to: receive the radar data from the radar system, the radar data determined based on reflections of a portion of the user moving within a gesture zone of the electronic device and determine a radar gesture based on the radar data, or receive a radar gesture; determine that the radar gesture corresponds to a control input of an application on the electronic device; provide a gesture-confirmation element on a display of the electronic device, the gesture-confirmation element indicating that the movement of the portion of the user within the gesture zone of the electronic device is determined to comprise the radar gesture and that the radar gesture corresponds to the control input of the application; and cause the application to respond to the control input.

Example 14

The electronic device of example 13, wherein the application on the electronic device is currently executing and causing the application to respond to the control input comprises sending the control input to the application.

Example 15

The electronic device of example 13, wherein the application on the electronic device is not currently executing and wherein causing the application to respond to the control input comprises: executing the application; and sending the control input to the application.

Example 16

The electronic device of any of examples 13-15, wherein the gesture-confirmation element is a visual element that appears on an active area of the display of the electronic device.

Example 17

The electronic device of example 16, wherein the visual element moves on the active area of the display, the movement corresponding to the movement of the portion of the user within the gesture zone.

Example 18

The electronic device of example 17, wherein: the radar gesture is a first motion that includes a component in a left-to-right direction and the movement of the gesture-confirmation element comprises moving from a first position on the active display to a second position on the active display, the second position to a right side of the first position; or the radar gesture is a second motion that includes a component in a right-to-left direction and the movement of the gesture-confirmation element comprises moving from a third position on the active display to a fourth position on the active display, the fourth position to a left side of the third position.

Example 19

The electronic device of example 17, wherein: the radar gesture is a first motion that includes a component in a top-to-bottom direction and the movement of the gesture-confirmation element comprises moving from a first position on the active display to a second position on the active display, the second position to a lower side of the first position; or the radar gesture is a second motion that includes a component in a bottom-to-top direction and the movement of the gesture-confirmation element comprises moving from a third position on the active display to a fourth position on the active display, the fourth position to an upper side of the third position.

Example 20

The electronic device of example 18 or example 19, wherein the moving from the first position on the active display to the second position on the active display or from the third position on the active display to the fourth position on the active display, includes: moving around a corner of the active area of the display; and disappearing from the active area of the display.

Example 21

The electronic device of example 17, wherein the movement of the gesture-confirmation element comprises: an increase from a first size of the gesture-confirmation element to a second size of the gesture-confirmation element, the second size larger than the first size; an increase from a first luminosity of at least part of the gesture-confirmation element to a second luminosity of the at least part of the gesture-confirmation element, the second luminosity greater than the first luminosity; a decrease from the second size of the gesture-confirmation element, the decrease continuing until the gesture-confirmation element is not visible; and a return to the first size and first luminosity of the gesture-confirmation element.

Example 22

The electronic device of example 16, wherein the gesture-confirmation element is a visual element that includes: a visual property, the visual property comprising at least one of a luminosity, a color, a contrast, a shape, a saturation, or an opaqueness that is different from the visual property of another portion of the display that is proximate to the visual element; and a segment of an exterior border that is within a threshold distance of the edge of the active area of the display.

Example 23

The electronic device of example 22, wherein the visual property of the visual element varies across the area of the visual element.

Example 24

The electronic device of any of examples 13-23, wherein the control input of the application is effective to cause the application to respond by: dismissing an alert or notification on the display of the electronic device; silencing a ringer or alarm; or skipping to a next or previous media item.

CONCLUSION

Although implementations of techniques for, and apparatuses enabling, methods for reliable acceptance of user non-contact gesture inputs for a mobile device have been described in language specific to features and/or methods, it is to be understood that the subject of the appended claims is not necessarily limited to the specific features or methods described. Rather, the specific features and methods are disclosed as example implementations enabling the methods for reliable acceptance of user non-contact gesture inputs for a mobile device.

	Number	Date	Country
Parent	PCT/US2019/049225	Aug 2019	US
Child	16912534		US

Methods for Reliable Acceptance of User Non-Contact Gesture Inputs for a Mobile Device

Information

Publication Number

Date Filed

Date Published

Inventors

Original Assignees

CPC

International Classifications

Abstract

Description

Claims

RELATED APPLICATIONS

Continuations (1)