Non-Line-of-Sight Radar-Based Gesture Recognition

[0001] This application is a non-provisional of and claims priority under 35 U.S.C. §119(e) to U.S. Patent Application Ser. No. 62/059,099, titled “Non-Line-of-Sight Radar-Based Gesture Recognition,” and filed on Oct. 2, 2014, the disclosure of which is incorporated by reference herein in its entirety.

[0002] As smart devices proliferate in homes, automobiles, and offices, the need to seamlessly and intuitively control these devices becomes increasingly important. For example, users desire to quickly and easily control their media players, televisions, and climate devices from wherever they happen to be. Current techniques for controlling smart devices, however, fail to provide seamless and intuitive control, instead relying on touch screens, hand-held remote controls, and clumsy audio interfaces.

[0003] This background description is provided for the purpose of generally presenting the context of the disclosure. Unless otherwise indicated herein, material described in this section is neither expressly nor impliedly admitted to be prior art to the present disclosure or the appended claims.

[0004] This document describes techniques and devices for non-line-of-sight radar-based gesture recognition. Through use of the techniques and devices described herein, users may control their devices through in-the-air gestures, even when those gestures are not within line-of-sight of their device's sensors. Thus, the techniques enable users to control their devices in many situations in which control is desired but conventional techniques do permit effective control, such as to turn the temperature down in a room when the user is obscured from a thermostat's gesture sensor, turn up the volume on a media player when the user is in a different room than the media player, or pause a television program when the user's gesture is obscured by a chair, couch, or other obstruction.

[0005] This summary is provided to introduce simplified concepts relating to non-line-of-sight radar-based gesture recognition, which is further described below in the Detailed Description. 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.

[0015] This document describes techniques and devices enabling non-line-of-sight radar-based gesture recognition. These techniques and devices enable greater control of smart devices through recognizing gestures when those gestures are made without being within line-of-sight of a smart device's sensors.

[0016] Consider, for example, a case where a user has many smart devices in his home. Assume that to control these devices he has numerous handheld remote controls; one for each device. Controlling these various smart devices is impractical due to the number of remote controls needed. Further, even if the user had one remote control capable of controlling multiple smart devices, he would still not be able to control all of multiple devices whenever he was not within line-of-sight of all of these various devices. And, even in the uncommon event of being in line-of-sight to many devices at once, the user still needs to carry around a remote control.

[0017] Consider other conventional ways in which to control smart devices, such as audio interfaces and line-of-sight cameras. Audio interfaces often fail to understand a user's intent and require the user to interrupt his or her ongoing conversations. Line-of-sight cameras, while allowing a user to forgo carrying a remote control in some cases, require line-of-sight and also can fail to provide robust and consistent gesture recognition. These are but three of many example controllers that fail to provide seamless and intuitive control.

[0018] In contrast, consider a case where a user is standing in her kitchen and desires to pause her television that is in her living room, turn off her microwave because her dinner is getting too hot, and turn up the heat in her home. Assume that the user's hands are blocked from her microwave by some hanging pots and pans and that her thermostat and television are within other rooms. The techniques described herein enable her to control all three of these devices, even though two are in other rooms and the third is obscured by various objects. None of these have line-of-sight to her, yet she can make a gesture to control each and every one of these three different devices seamlessly and intuitively.

[0019] This is but one way in which non-line-of-sight radar-based gesture recognition can be performed. This document now turns to an example environment, after which non-line-of-sight gesture recognition systems, example methods, and an example computing system are described.

[0020] FIG. 1 is an illustration of an example environment 100 in which techniques enabling non-line-of-sight radar-based gesture recognition can be performed. Environment 100 includes a room 102, a smart device 104, and a user 106. Room 102 includes obstructions 108, walls 110, a floor 112 (shown with squares), and a ceiling 114 (transparent in top-down view, show with circles), which are described in more detail below. Room 102 is shown in two identical illustrations (102-1 and 102-2) with the exception of one having a direct radar field and another having a reflected radar field, as noted below.

[0021] Smart device 104 includes non-line-of-sight gesture recognition system 116 (NLOS system 116), which provides a direct radar field 118. Direct radar field 118 does not have line-of-sight to some portions of room 102, here volumes 120. A first volume 120-1 does not have line-of-sight to NLOS system 116 due to couch 108-1, which is one of obstructions 108. A second volume 120-2 does not have line-of-sight to NLOS system 116 due to planter box 108-2, which is another of obstructions 108.

[0022] NLOS recognition system 116 is also capable of providing a reflected radar field 122 effective to enable recognition of gestures within some or all of volumes 120 in which direct line-of-sight is not available. This reflected radar field 122 is shown provided through radar transmission lines 124, though additional description of transmission lines is provided elsewhere herein. For visual clarity radar fields 118 and 122 are shown separately, though both radar fields can be used together.

[0023] While not shown in FIG. 1, NLOS system 116 can also provide a penetration radar field. This field is configured to penetrate various materials, such as wool, cotton, nylon, or leather, but reflect from human tissue, thereby further enabling recognition of gestures that are partially or fully not in line-of-sight or otherwise obscured from NLOS system 116.

[0024] In more detail, consider FIG. 2, which illustrates smart device 104. Smart device 104 includes one or more computer processors 202 and computer-readable media 204 (e.g., memory media and storage media). Applications and/or an operating system (not shown) embodied as computer-readable instructions on computer-readable media 204 can be executed by processors 202 to provide some of the functionalities described herein. Computer-readable media 204 also includes field manager 206 (described below).

[0025] Smart device 104 may also include network interfaces 208 for communicating data over wired, wireless, or optical networks. By way of example and not limitation, network interface 208 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, a mesh network, and the like. Smart device 104 may also include a display 210, though this is not required.

[0026] Smart device 104 also includes or has access to NLOS system 116, as noted above, which is configured to provide radar fields by which to sense gestures. To enable this, NLOS system 116 includes a microwave radio element 212, an antenna element 214, and a signal processor 216. Generally, microwave radio element 212 is configured to provide a radar field having a direct radar field and a reflected radar field as noted above, through a penetration radar field may also be included. While examples shown herein generally show one NLOS system 116 per device, multiples can be used, thereby increasing coverage of a volume (e.g., room 102), as well as a number, complexity, accuracy, resolution, and robust recognition of gestures.

[0027] Microwave radio element 212 can be configured to emit one or multiple sets of continuously modulated radiation, ultra-wideband radiation, or sub-millimeter-frequency radiation. Microwave radio element 212, in some cases, is configured to form radiation in beams, the beams aiding antenna element 214 and signal processor 216 to determine which of the beams are interrupted, and thus locations of interactions (e.g., by a hand) within the radar field. In more detail, microwave radio element 212 can be configured to emit microwave radiation in a 1 GHz to 300 GHz range, as well as 57 GHz to 63 GHz, to provide the radar field. This range affects antenna element 214's ability to sense interactions, such as to track locations of two or more targets to a resolution of about two to about 25 millimeters. Microwave radio element 212 can be configured, along with other entities of NLOS system 116, to have a relatively fast update rate, which can aid in resolution of the interactions. By selecting particular frequencies, NLOS system 116 can operate to provide a direct radar field to reflect from line-of-sight gestures, a reflected radar field to reflect first from some object or objects and then from non-line-of-sight gestures, and/or a penetration radar field to penetrate clothing and similar materials while reflecting from human tissue.

[0028] Antenna element 214 is configured to receive reflections of, or sense interactions in, the radar field, and signal processor 216 is configured to process the reflections or sensed interactions in the radar field sufficient to provide gesture data usable to determine a gesture from the sensed interactions. Antenna element 214 can include one or many sensors, such as an array of radiation sensors, the number in the array based on a desired resolution and whether the radar field is direct, reflected, or penetration. Alternately or additionally, antenna element 214 may include one or many antennas, such as an array of antennas, directional or otherwise, coupled with respective radiation sensors and/or signal processor 216.

[0029] Further, antenna element 214 or signal processor 216 can be configured to differentiate between interactions in the radar field that are from radar transmissions that are direct, through a material, or after being reflected. Thus, a media player having NLOS system 116 may differentiate between radar reflecting directly from a user's hand to radar that was first bounced off of a ceiling (e.g., a painted, gypsum drywall ceiling) and then reflected off of the user's hand.

[0030] The radar field provided by microwave radio element 212 can include one or multiple three-dimensional (3D) volumes, planes, or surfaces (e.g., a surface applied to a user's hand). In each of these cases, antenna element 214 is configured to sense interactions of one or multiple targets (e.g., two hands, fingers of one or two hands, etc.), and signal processor 216 is configured to process the sensed interactions sufficient to provide gesture data usable to determine gestures in three dimensions.

[0031] With the provided radar field, such as direct radar field 118 and reflected radar field 124 of FIG. 1, a user may perform complex or simple gestures with a hand or device (e.g., a stylus) that interrupts the field. Example gestures include the many gestures usable with current touch-sensitive displays, such as swipes, two-finger pinch and spread, tap, and so forth. Other gestures are enabled that are complex, or simple but three-dimensional, examples include the many sign-language gestures, e.g., those of American Sign Language (ASL) and other sign languages worldwide. A few of these include an up-and-down fist, which in ASL means “Yes”, an open index and middle finger moving to connect to an open thumb, which means “No”, a flat hand moving up a step, which means “Advance”, a flat and angled hand moving up and down, which means “Afternoon”, clenched fingers and open thumb moving to open fingers and an open thumb, which means “taxicab”, an index finger moving up in a roughly vertical direction, which means “up”, and so forth. These are but a few of many gestures that can be mapped to particular devices or applications, such as the “Advance” gesture to skip to another song being played by a media player through a non-line-of-sight gesture.

[0032] As noted above, NLOS system 116 can provide a penetration radar field capable of penetrating some objects and materials and then reflect off of human tissue. This is illustrated at FIG. 3, which shows hand 302 having a penetration radar field 304 contacting a surface 306 of hand 302. This penetration radar field 304 penetrates chair 308 to then be reflected from surface 306 and received back at antenna element 214 of NLOS system 116. Microwave radio element 212 (not shown) provides penetration radar field 304, while antenna element 214 is configured to receive a reflection caused by an interaction on surface 306 of hand 302 that penetrates and then reflects back through chair 308, at which point signal processor 216 is configured to process the received reflection sufficient to provide gesture data usable to determine a gesture.

[0033] Gestures can be associated with various smart devices, such as a device other than smart device 104. To do so, gestures can map to a pre-configured control gesture associated with a control input for an application associated with any of these devices. Thus, a gesture can be set to control the application and/or device based on the gesture itself, rather than first selecting which device or application to which the control is intended. For example, many complex and unique gestures can be recognized by NLOS system 116, thereby permitting precise and/or single-gesture control, even for multiple applications. Mapping these many gestures to various different devices and application permits control, with or without explicitly selecting (usually through a gesture) which device is intended to be controlled.

[0034] Smart device 104 is illustrated with various non-limiting example devices: smartphone 104-1, refrigerator 104-2, microwave oven 104-3, laptop 104-4, tablet 104-5, and television 104-6, though other devices may also be used, such as climate control devices (e.g., a thermostat or ceiling fan), wearable devices, desktop computers, netbooks, e-readers, cameras, automotive systems, and so forth.

[0035] NLOS system 116 also includes a transceiver 218 configured to transmit gesture data to a remote device, such as in cases where NLOS system 116 is not integrated with smart device 104. Gesture data can be provided in a format usable by the receiving device sufficient to recognize a gesture using the gesture data.

[0036] NLOS system 116 may also include one or more system processors 220 and system media 222 (e.g., one or more computer-readable storage media). System media 222 includes system manager 224, which can perform various operations, including determining a gesture based on gesture data from signal processor 216, mapping the determined gesture to a pre-configured control gesture associated with a control input for an application associated with a remote smart device, and causing transceiver 218 to transmit the control input to the remote smart device effective to enable control of the application or device. This is but one of the ways in which the above-mentioned control through NLOS system 116 can be enabled. Note also that while NLOS system 116 is shown integral with smart device 104, it can instead be part of a device having few or no computing capabilities and still provide gesture data to be recognized and/or mapped to a control input. Operations of NLOS system 116, system manager 224, and field manager 206 are provided in greater detail as part of methods 400 and 600 below.

[0037] These and other capabilities and configurations, as well as ways in which entities of FIGS. 1-3 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 FIGS. 2 and 3 illustrate some of many possible environments and devices capable of employing the described techniques.

[0038] FIGS. 4 and 6 depict methods 400 and 600. Method 400 enables non-line-of-sight radar-based gesture recognition using a reflected radar field, and can be performed separate from or integrated in whole or in part with method 600. Method 600 enables non-line-of-sight radar-based gesture recognition where a direct line-of-sight is not present for one radar system but a gesture is recognized through another radar system and then passed to the other radar system through direct or indirect radar fields.

[0039] These methods are shown as sets of operations (or acts) performed but are not necessarily limited to the order or combinations in which the operations are shown herein. 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 environment 100 of FIG. 1 and entities and examples detailed in FIGS. 2, 3, 5, and 7, 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.

[0040] At 402, a volume of a room in which there is no line-of-sight to a radar system is determined. The techniques may determine that there is such a volume in various manners, such as through tracking a moving entity, a camera, bounced (e.g., reflected) radar transmissions, and so forth.

[0041] For example, field manager 206 may track, with a radar transmission, a person or animal's movement in the room. If, during a portion of the person or animal's movement field manager 206 does not receive a reflection from the person or animal, field manager 206 may determine, based on the person or animal's projected path or a part of the person or animal no longer trackable (e.g., a person's legs walking behind a couch), that a volume in the room exists where direct line-of-sight is not available.

[0042] Field manager 206 may also or instead use a camera or other image sensor, using radar or otherwise. Field manager 206 captures an image using the camera to provide an image of the room from a perspective of NLOS system 116. Field manager 206 then receives or determines (e.g., through sonar or radar reflection) dimensions for the room (e.g., 4 meters wide, 7 meters deep, 3 meters high). With these dimensions and the image of the room, non-imaged but existing floor, wall, or ceiling areas can be determined. With this data, field manager 206 may then determine the volume of the room in which there is no line-of-sight to NLOS system 116.

[0043] Further still, field manager 206 may determine non-line-of-sight volumes based on obstructions. Thus, on providing a direct radar field to receive reflections from objects in the room, field manager 206 assumes that regions behind obstructions are likely to be volumes in which a potential gesture may be made, and in any case, these are very likely to part of the room and do not have line-of-sight. As part of this determination obstructions are objects other than floors, walls, or ceilings of the room. Some objects reflect radar and some are those through which radar may pass. Because of this, portions of the objects penetrated by the radar field can reduce the size of the volume.

[0044] At 404, a set of transmission paths sufficient to cause a reflected radar field to be provided within at least a portion of the volume is determined by providing radar transmissions from the radar system into the room. As noted in part above, determining a volume in which no line-of-sight is available may include radar reflection, in which case some transmission paths may be known. In many cases, however, while the volume is known the transmission paths to cause a reflected radar field are not yet known.

[0045] To determine these transmission path, field manager 206 may iteratively provide radar transmissions and receive reflections from the provided radar transmissions. Some of these radar transmissions may not pass through the determined volume, and thus are not needed. Some others, however, pass through one of the determined volumes and are then correlated with that volume. In still further cases, a person or animal passes through the determined volume and radar transmission are iteratively provided and then, on reflection from the person or animal, correlated to the volume. In so doing various types and frequencies of radar transmissions can be used, including narrow-beam transmission and reflection.

[0046] By way of example, consider FIG. 5, which illustrates room 102 of FIG. 1, including smart device 104, user 106, obstructions 108, walls 110, floor 112, ceiling 114, NLOS system 116, and volumes 120-1 and 120-2. Two transmission paths are shown, wall-and-object-reflection path 502 and ceiling-and-floor path 504. These illustrate but two of many different transmission paths capable of providing reflection radar field 122 (shown in FIG. 1 and omitted for clarity in FIG. 5).

[0047] Wall-and-object-reflection path 502 includes eight portions, each reflecting off of, or resulting from a reflection off of, a wall or object. Thus, path 502 proceeds from NLOS system 116 to one of walls 110, then again off of another of walls 110, then off of a back of couch 108-1, back to the other of walls 110, to couch 108-1, to the other of the walls 110, than off planter box 108-2, and then back to NLOS system 116. Some transmission paths do not result in a reflection returning, and thus can be forgone, while others pass only within volumes that are in line-of-site of NLOS system 116, and can also be forgone. Path 504 proceeds from NLOS system 116 to ceiling 114 (shown reflected at a circle), then to one of walls 110, off floor 112 (shown reflected at a square), off ceiling 114, and then back to NLOS system 116. These two paths 502, 504 provide but two example transmission paths by which NLOS system 116 and field manager 206 may provide a reflected radar field (e.g., 122 of FIG. 1) in a volume in which line-of-sight to NLOS system 116 is not available. As noted, this reflected radar field enables rejection of gestures made within some or all of volumes 120.

[0048] At 406, a radar field is provided within the one or more volumes within the room, the radar field including at least the reflected radar field. In some cases, the radar field also includes a direct radar field or a penetration radar field as noted herein. By so doing, a radar field usable to recognize gestures can be provided for gestures that do not have direct line-of-sight from a radar system.

[0049] At 408, a reflection of a gesture interaction made within the radar field within the room is received. This reflection enables capture of data about the gesture interaction that can then be used to determine the gesture being made. This reflection can be within a reflected, direct, or penetration radar field as noted above.

[0050] At 410, a gesture is determined based on captured data associated with the reflection of the gesture interaction. The gesture determined can be one of many gestures noted above, including those mapping directly to a device or application and a control command, such as to mute a television set.

[0051] At 412, the determined gesture is provided to a device or application effective to control the device or application. As part of this provision, field manager 206 may determine to which device or application to send the control, such as by analyzing a map of gestures to various devices and applications.

[0052] FIG. 6 illustrates method 600, which enables non-line-of-sight radar-based gesture recognition effective to control or communicate with a smart device that does not have line-of-sight to a user.

[0053] At 602, a radar field is provided, such as a field having one or more of a direct, reflected, or penetration radar field, as described above. This radar field can be provided by a radar system that does or does not have line-of-sight to a user making a gesture.

[0054] At 604, reflections from an interaction that is within the radar field are sensed through a radar system. This radar system is assumed to have line-of-sight, or is able to compensate for not having line-of-sight, effective to receive reflections from a user. Another smart device, however, which may or may not have a radar system, does not have line-of-sight to the user and is not able to compensate. Thus, both devices may not have line-of-sight to a user but one of those devices is able to sense reflections, such as through a penetration or reflection radar field.

[0055] By way of example, consider FIG. 7, which illustrates a ground floor 702 of a home. This home includes four rooms 704, media room 704-1, piano room 704-2, living room 704-3, and kitchen/dining room 704-4. As shown, there are five radar systems 706, a media-player 708's radar system 706-1, a thermostat 710's radar system 706-2, a television 712's radar system 706-3, an oven 714's radar system 706-4, and a microwave-oven 716's radar system 706-5. Multiple scenarios in which the techniques enable gesture recognition without line-of-sight to a smart device intended to be controlled are shown in FIG. 7, such as when user 718 wants to control television 712 while in kitchen 704-4. To do so, field manager 206 receives reflections from user 718 at an NLOS system 116 of one of radar systems 706 that is not in the same room as user 718.

[0056] By way of a particular example, assume that user 718 is in kitchen/dining room 704-4 and wants to turn down the heat in the house by controlling thermostat 710, which is in piano room 704-2. To do so, user 718 makes a gesture to turn down the heat while standing in kitchen/dining room 704-4, which, at operation 604, an NLOS system 116 operating in oven 714's radar system 706-4 receives. The gesture is received by receiving user 718's reflection within radar field 720 at an antenna of NLOS system 116.

[0057] At 606, a gesture is recognized based on the reflections received. This can be performed at a smart device associated with a radar system at which the reflection is received, or gesture data for the reflection can be received at a smart device intended to be controlled. Thus, field manager 206 or system manager 224 may receive the reflection and pass gesture data for the reflection to other smart devices, such as to all of the other radar systems and/or devices in a home or office. In such a case, the smart devices can determine if the control is intended for them based on the gesture determined from the gesture data, such as having received a prior gesture selecting to control that device or receiving a gesture associated with the smart device.

[0058] At 608, the gesture is determined to be associated with (or not associated with) a non-line-of-sight smart device. Generally, field manager 206 may determine that the gesture is associated with a non-line-of-sight smart device by mapping the gesture to a pre-configured gesture intended to establish communication with the non-line-of-sight smart device. In some cases this pre-configured gesture establishes communication with the non-line-of-sight smart device effective to enable a future gesture determined at the smart device to control the non-line-of-sight smart device. In some other cases, field manager 206 may determine that the gesture is associated with the non-line-of-sight smart device by mapping the gesture to a unique gesture. This unique gesture can be of a set of unique gestures uniquely mapped to each of a set of smart devices within some group, such as smart devices on ground floor 702 of FIG. 7.

[0059] Continuing the ongoing example of FIG. 7, assume that field manager 206 operating at NLOS system 116 of oven 714's radar system 706-4 recognizes a gesture made by user 718. This gesture may then be determined to indicate control of thermostat 710, after which another gesture is recognized and then determined to be associated with thermostat 710 based on the prior gesture indicating control of thermostat 710 is intended. Assume, for example, that a unique, complex gesture with a closed hand and exposed thumb that moves up and the down is associated with thermostat 710. A second gesture, here assumed to be a non-unique magnitude gesture of a cupped hand moving clockwise or counter-clockwise, indicates to turn up or down something, respectively. Because this second gesture is received soon after the first gesture indicating control of thermostat 710 is intended, it is then recognized by repeating steps of method 600 and then passed (at operation 610) to thermostat 710 effective to turn the heat up or down. This repetition is shown at a dashed arrow in FIG. 6.

[0060] Similarly, if the first gesture is associated with control of media player 708, the second gesture indicating to turn up or down, would instead turn up or turn down the volume of media player 708, all without line-of-sight from the intended smart device.

[0061] At 610, the gesture is passed to the non-line-of-sight smart device. Thus, the gesture can be passed from one smart device to another smart device effective to enable the gesture to control the non-line-of-sight smart device or establish communication with the non-line-of-sight smart device.

[0062] The preceding discussion describes methods relating to non-line-of-sight radar-based gesture recognition. Aspects of these methods may be implemented in hardware (e.g., fixed logic circuitry), firmware, software, manual processing, or any combination thereof. These techniques may be embodied on one or more of the entities shown in FIGS. 1-3, 5, 7, and 8 (computing system 800 is described with reference to FIG. 8 below), which may be further divided, combined, and so on. Thus, these figures illustrate some of the many possible systems or apparatuses capable of employing the described techniques. The entities of these figures generally represent software, firmware, hardware, whole devices or networks, or a combination thereof.

[0063] FIG. 8 illustrates various components of example computing system 800 that can be implemented as any type of client, server, and/or smart device as described with reference to the previous FIGS. 1-7 to implement non-line-of-sight radar-based gesture recognition. In embodiments, computing system 800 can be implemented as one or a combination of a wired and/or wireless wearable device, System-on-Chip (SoC), and/or as another type of device or portion thereof. Computing system 800 may also be associated with a user (e.g., a person) and/or an entity that operates the device such that a device describes logical devices that include users, software, firmware, and/or a combination of devices.

[0064] Computing system 800 includes communication devices 802 that enable wired and/or wireless communication of device data 804 (e.g., received data, data that is being received, data scheduled for broadcast, data packets of the data, etc.). Device data 804 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. Media content stored on computing system 800 can include any type of audio, video, and/or image data. Computing system 800 includes one or more data inputs 806 via which any type of data, media content, and/or inputs can be received, such as human utterances, interactions with a radar field, user-selectable inputs (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.

[0065] Computing system 800 also includes communication interfaces 808, which can be implemented as any one or more of a serial and/or parallel interface, a wireless interface, any type of network interface, a modem, and as any other type of communication interface. Communication interfaces 808 provide a connection and/or communication links between computing system 800 and a communication network by which other electronic, computing, and communication devices communicate data with computing system 800.

[0066] Computing system 800 includes one or more processors 810 (e.g., any of microprocessors, controllers, and the like), which process various computer-executable instructions to control the operation of computing system 800 and to enable techniques for, or in which can be embodied, non-line-of-sight radar-based gesture recognition. Alternatively or in addition, computing system 800 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 812. Although not shown, computing system 800 can include a system bus or data transfer system that couples the various components within the device. A 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.

[0067] Computing system 800 also includes computer-readable media 814, such as one or more memory devices that enable persistent and/or non-transitory data storage (i.e., 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. Computing system 800 can also include a mass storage media device 816.

[0068] Computer-readable media 814 provides data storage mechanisms to store device data 804, as well as various device applications 818 and any other types of information and/or data related to operational aspects of computing system 800. For example, an operating system 820 can be maintained as a computer application with computer-readable media 814 and executed on processors 810. Device applications 818 may include a device manager, such as any form of a control application, software application, signal-processing and control module, code that is native to a particular device, a hardware abstraction layer for a particular device, and so on.

[0069] Device applications 818 also include any system components, engines, or managers to implement non-line-of-sight radar-based gesture recognition. In this example, device applications 818 include field manager 206 and system manager 224.

[0070] Although embodiments of techniques using, and apparatuses enabling, non-line-of-sight radar-based gesture recognition 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 non-line-of-sight radar-based gesture recognition.