Radar gesture sensing using existing data protocols

Description

BACKGROUND

Use of gestures to interact with computing devices has become increasingly common. Gesture recognition techniques have successfully enabled gesture interaction with devices when these gestures are made to device surfaces, such as touch screens for phones and tablets and touch pads for desktop computers. Users, however, are more and more often desiring to interact with their devices through gestures not made to a surface, such as a person waving an arm to control a video game. These in-the-air gestures can be sensed using radar techniques by devices that emit a radar field and analyze reflections of that radar field. The device emitting the radar field controls modulation and transmission of the radar field, which enables the device to correlate radar reflections to the modulations of the radar field. In some applications, multiple devices may benefit from radar gesture recognition, but another device, which does not emit the radar field, lacks access to the control information for the modulation and transmission of the radar field to perform radar gesture sensing.

SUMMARY

This document describes techniques and devices for radar gesture sensing using existing data protocols. These techniques and devices can accurately recognize gestures that are made in three dimensions, such as in-the-air gestures. These in-the-air gestures can be made from varying distances, such as from a person sitting on a couch to control a television, a person standing in a kitchen to control an oven or refrigerator, or millimeters from a desktop computer's display.

Data protocols used for wireless communication define information included in transmissions, such as a training sequence that is used for receiver synchronization and/or channel estimation. All radios using the data protocol transmit the training sequence as a part of each data transmission. By modulating a radar field according to an existing data protocol, the known data pattern of the training sequence can be used to correlate reflections of the radar field for radar gesture sensing, while concurrently using the radar field for data transmission.

In addition to the transmitting device using the radar field for gesture sensing, any receiving device that uses the same existing data protocol can use the reflections of the radar field, which are modulated with the training sequence, for radar gesture recognition. The receiving device may be receiving data transmissions from the transmitting device using the data protocol, or may simply be using the radar field for gesture sensing. For example the data protocol may be used for point-to-point communication between the transmitting device and the receiving device, the transmitting device may be an access point that provides a radar field that multiple receiving devices can use for gesture sensing, and so forth.

This summary is provided to introduce simplified concepts concerning radar gesture sensing using existing data protocols, 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.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments of techniques and devices for radar gesture sensing using existing data protocols are described 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 that employs radar gesture sensing using existing data protocols in accordance with one or more implementations.

FIG. 2 illustrates an example implementation of a computing device of FIG. 1 in greater detail in accordance with one or more implementations.

FIG. 3 illustrates example structures of data packets usable for radar gesture sensing using existing data protocols.

FIG. 4 illustrates an example of general signal properties of radar signals.

FIG. 5 illustrates an additional example of general signal properties of radar signals for radar gesture sensing using existing data protocols.

FIG. 6 illustrates an additional example of general signal properties of radar signals using multiple antennas.

FIG. 7 illustrates an example of a pipeline in accordance with one or more implementations.

FIG. 8 illustrates an example flow diagram in accordance with one or more implementations.

FIG. 9 illustrates another example flow diagram in accordance with one or more implementations.

FIG. 10 illustrates an example device in which gesture detection can be employed in accordance with one or more implementations.

DETAILED DESCRIPTION

Overview

This document describes techniques using, and devices embodying, radar gesture sensing using existing data protocols. These techniques and devices can enable a great breadth of gestures and uses for those gestures, such as gestures to use, control, and interact with various devices, from desktop computers to refrigerators. The techniques and devices are capable of providing a radar field that can sense gestures from multiple actors at one time and through obstructions, thereby improving gesture breadth and accuracy over many conventional techniques. These devices incorporate gesture recognition with the transmission and/or reception of data using an existing data protocol. This approach allows a device to use a single radio to both transmit data to another device and to emit a radar field for gesture sensing, eliminating the need for dedicated radios for data transmission and for gesture sensing.

Additionally radar gesture sensing is employed in a device that analyzes reflections of radio waves corresponding to known patterns of a data protocol used to receive data. By analyzing the reflections of these known patterns, such as a training sequence in a transmitted data packet, radar-gesture recognition is enabled in a device without requiring the device to include a radar emitter.

Example Environment

FIG. 1 is an illustration of example environment 100 in which techniques using, and an apparatus including, radar gesture sensing using existing data protocols may be embodied. Environment 100 includes example computing devices 102 devices that each include a gesture component 104. In computing device 102-1, the gesture sensor component 104 provides a near radar field to interact with the computing device 102-1 and in computing device 102-2, the gesture sensor component 104 provides an intermediate radar field (e.g., a room size) to interact with computing device 102-2. The gesture sensor components 104 in the computing devices 102-1 and 102-2 provide radar fields 106, near radar field 106-1 and intermediate radar field 106-2, and are described below.

The gesture sensor component 104 in computer system 102-1 improves user interaction with desktop computer 102-1. Assume, for example, that computer system 102-1 includes a touch screen 108 through which display and user interaction can be performed. This touch screen 108 can present some challenges to users, such as needing a person to sit in a particular orientation, such as upright and forward, to be able to touch the screen. Further, the size for selecting controls through touch screen 108 can make interaction difficult and time-consuming for some users. Consider, however, computer system 102-1, which provides near radar field 106-1 enabling a user's hands to interact with computer system 102-1, such as with small or large, simple or complex gestures, including those with one or two hands, and in three dimensions. As is readily apparent, a large volume through which a user may make selections can be substantially easier and provide a better experience over a flat surface, such as that of touch screen 108.

Similarly, consider computer system 102-2, which provides intermediate radar field 106-2, which enables a user to interact with computer system 102-2 from a distance and through various gestures, from hand gestures, to arm gestures, to full-body gestures. By so doing, user selections can be made simpler and easier than a flat surface (e.g., touch screen 108), a remote control (e.g., a gaming or television remote), and other conventional control mechanisms.

The gesture sensor component 104 can interact with applications or an operating system of the computing devices 102, or remotely through a communication network by transmitting input responsive to recognizing gestures. Gestures can be mapped to various applications and devices, thereby enabling control of many devices and applications. Many complex and unique gestures can be recognized by gesture sensor component 104, thereby permitting precise and/or single-gesture control, even for multiple applications. Gesture sensor component 104, whether integrated with a computing device, having computing capabilities, or having few computing abilities, can each be used to interact with various devices and applications.

FIG. 2 depicts a system 200 in an example implementation in which the gesture component 104 is shown in greater detail. The gesture sensor component 104 is part of one of the computing devices 102. Computing device 102 is illustrated with various non-limiting example devices, such as a smartphone, a laptop computer, a television, a desktop computer, a tablet, a digital camera, a refrigerator, and a microwave oven, though other devices may also be used, such as home automation and control systems, entertainment systems, audio systems, other home appliances, security systems, netbooks, smartphones, and e-readers. Note that computing device 102 can be wearable, non-wearable but mobile, or relatively immobile (e.g., desktops and appliances).

Note also that the gesture sensor component 104 can be used with, or embedded within, many different computing devices or peripherals, such as in walls of a home to control home appliances and systems (e.g., automation control panel), in automobiles to control internal functions (e.g., volume, cruise control, or even driving of the car), or as an attachment to a laptop computer to control computing applications on the laptop.

Computing device 102 includes one or more computer processors 202 and computer-readable media 204, which includes memory media and storage media. Application(s) 206, gesture sensor APIs 208 and/or an operating system (not shown) are embodied as computer-readable instructions on computer-readable media 204 can be executed by processors 202 to provide some of the functionalities described herein.

Computing device 102 may also include network interface(s) 210 for communicating data over wired, wireless, or optical networks. By way of example and not limitation, network interface 210 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.

Computing device 102 also includes I/O ports 212. I/O ports 212 can include a variety of ports, such as by way of example and not limitation, high-definition multimedia (HDMI), digital video interface (DVI), display port, fiber-optic or light-based, audio ports (e.g., analog, optical, or digital), Universal Serial Bus (USB) ports, serial advanced technology attachment (SATA) ports, peripheral component interconnect (PCI) express based ports or card slots, serial ports, parallel ports, or other legacy ports.

Results are output from the gesture sensor component 104 to applications 206 via the gesture sensor APIs 208 and may be configured in a variety of ways. In a first such example, the result references the identified gesture, but not how the gesture was detected. In this way, detection of the gesture by the gesture sensor component 104 may be abstracted away from the applications 206 such that the applications 206 are not aware of how the gesture is detected, but may leverage detection of the gesture to control operations of the computing device 102.

In some implementations, gesture sensor APIs 208 provide high-level access into the gesture component 104 in order to abstract implementation details and/or hardware access from a calling application 206, request notifications related to identified events, query for results, and so forth. Gesture sensor APIs 208 can also provide low-level access to gesture component 104, where a calling application 206 can control direct or partial hardware configuration of the gesture component 104. In some cases, gesture sensor APIs 208 provide programmatic access to input configuration parameters that configure transmit signals (e.g., signals as described in relation to FIG. 4) and/or select gesture recognition algorithms.

These gesture sensor APIs 208 enable applications 206 to incorporate the functionality provided by the gesture component 104 into executable code. For instance, applications 206 can call or invoke gesture sensor APIs 208 to register for, or request, an event notification when a particular gesture has been detected, enable or disable wireless gesture recognition in computing device 102, and so forth. At times, gesture sensor APIs 208 can access and/or include low level hardware drivers that interface with hardware implementations of gesture component 104. Alternately or additionally, gesture sensor APIs 208 can be used to access various algorithms that reside on gesture component 104 to perform additional functionality or extract additional information, such as 3D tracking information, angular extent, reflectivity profiles from different aspects, correlations between transforms/features from different channels, and so forth.

In an example, the gesture sensor component 104 employs the gesture sensor APIs 208 to expose a result that describes an operation that is to be performed by the computing device 102. In an implementation, this may be performed to identify the operation and even an amount to which the operation is to be performed. Further, this may be done so without indication of the gesture used to specify this operation. For example, the gesture sensor component 104 detects a gesture performed by a hand that mimics the turning of a physical knob. Detection of the gesture by the gesture sensor component 104 includes positioning of fingers of the user's hand in three-dimensional space as well as detection of movement, which in this instance involves rotational movement to the left or right.

The result output by the gesture sensor component 104 via the APIs 208 to the application 206 may be configured in a variety of ways. In a first such example, the result references the identified gesture, but not how the gesture was detected. In this way, detection of the gesture by the gesture sensor component 104 may be abstracted away from the applications 206 such that the applications 206 are not aware of how the gesture is detected, but may leverage detection of the gesture to control operations of the computing device 102.

Gesture sensor component 104, as noted above, is configured to sense gestures. To enable this, the gesture sensing component 104 includes antennas 214, digital signal processing component 216, machine-learning component 218, and output logic component 220. In some implementations, gesture sensor component 104 uses these various components in concert (such as a pipeline) to wirelessly detect gestures using radar techniques based on multiple signals, such as micro-gestures.

Antennas 214, for instance, are used transmit and receive RF signals, such as emitting a radar field and receiving reflections of the radar field. This is achieved by converting electrical signals into electromagnetic waves for transmission, and vice versa for reception. The gesture sensor component 104 can include any suitable number of antennas 214 in any suitable configuration. For instance, any of the antennas 214 can be configured as a dipole antenna, a parabolic antenna, a helical antenna, a monopole antenna, and so forth. In some examples, antennas 214 are constructed on-chip (e.g., as part of an SoC), while in other examples, antennas 214 are components, metal, hardware, and so forth that attach to the gesture sensor component 104. The placement, size, and/or shape of antennas 214 can be chosen to enhance a specific transmission pattern or diversity scheme, such as a pattern or scheme designed to capture information about a micro-gesture performed by the hand, as further described above and below. The antennas 214 can be physically separated from one another by a distance that allows the gesture sensor component 104 to collectively transmit and receive signals directed to a target object (e.g., a hand) over different channels, different radio frequencies, and different distances. In some instances, antennas 214 are spatially distributed to support triangulation techniques, while in others the antennas are collocated to support beamforming techniques. While not illustrated, each antenna 214 can correspond to a respective transceiver path that physically routes and manages the outgoing signals for transmission and the incoming signals for capture and analysis.

Digital signal processing component 216 generally represents functionality that digitally captures and processes a signal. For instance, digital signal processing component 216 performs sampling on RF signals received by antennas 214 to generate digital samples that represent the RF signals, and processes the digital samples to extract information about the target object. Alternately or additionally, digital signal processing component 216 controls the configuration of signals transmitted via antennas 214, such as configuring a plurality of signals to form a specific diversity scheme, such as a beamforming diversity scheme. In some cases, digital signal processing component 216 receives input configuration parameters that control an RF signal's transmission parameters (e.g., frequency channel, power level, etc.), such as through gesture sensor APIs 208. In turn, digital signal processing component 216 modifies the RF signal based upon the input configuration parameter. At times, the signal processing functions of digital signal processing component 216 are included in a library of signal processing functions or algorithms that are also accessible and/or configurable via gesture sensor APIs 208. Digital signal processing component 216 can be implemented in hardware, software, firmware, or any combination thereof.

Additionally or alternatively, the digital signal processing component 216 modulates data for transmission on the RF signals that are transmitted and/or demodulates data on received RF signals. The emitted radiation by the antennas 214 provides the radar field for gesture sensing, as well as transmitting wireless data. By way of example and not limitation, the protocol may a wireless local area network (WLAN) protocol, a personal area network (PAN) protocol, a wide area network (WAN) protocol, a peer-to-peer network protocol, point-to-point network protocol, a mesh network protocol, and the like.

Among other things, machine-learning component 218 receives information processed or extracted by digital signal processing component 216, and uses that information to classify or recognize various aspects of the target object, as further described below. In some cases, machine-learning component 218 applies one or more algorithms to probabilistically determine which gesture has occurred given an input signal and previously learned gesture features by leveraging the gesture sensor APIs 208. As in the case of digital-signal processing component 216, machine-learning component 218 can include a library of multiple machine-learning algorithms as part of the gesture sensor APIs 208, such as a Random Forrest algorithm, deep learning algorithms (e.g., artificial neural network algorithms, convolutional neural net algorithms, etc.), clustering algorithms, Bayesian algorithms, and so forth.

Machine-learning component 218 can be trained on how to identify various gestures using input data that consists of example gestures to learn. In turn, machine-learning component 218 uses the input data to learn what features can be attributed to a specific gesture. These features are then used to identify when the specific gesture occurs. An operation may also be assigned to the gesture as part of the gesture sensor APIs 208 to expose this operation to the applications 206 as previously described in relation to FIG. 2. In some examples, gesture sensor APIs 208 can be used to configure machine-learning component 218 and/or its corresponding algorithms.

Output logic component 220 represents functionality that uses logic to filter output information generated by digital signal processing component 216 and machine-learning component 218. In some cases, output logic component 220 uses knowledge about the target object to further filter or identify the output information. For example, consider a case where the target object is a hand repeatedly performing a tap gesture. Depending upon its configuration, output logic component 220 can filter the repeated tap gesture into a single output event indicating a repeated tap gesture, or repeatedly issue a single-tap gesture output event for each tap gesture identified. This can be based on knowledge of the target object, user input filtering configuration information, default filtering configuration information, and other information defined as part of the gesture sensor APIs 208. In some implementations, the filtering configuration information of output logic component 220 can be modified via the gesture sensor APIs 208.

Having described computing device 102 in accordance with one or more embodiments, now consider a discussion of using wireless detection of an object in accordance with one or more examples.

Generally, antennas 214 are configured to emit a radar field, in some cases one that is configured to penetrate fabric or other obstructions and reflect from human tissue. These fabrics or obstructions can include wood, glass, plastic, cotton, wool, nylon and similar fibers, and so forth, while reflecting from human tissues, such as a person's hand In some cases, the radar field configuration can include the modulation of data on the emitted radar field according to a data protocol as further described below.

This radar field can be a small size, such as zero or one or so millimeters to 1.5 meters, or an intermediate size, such as about one to about 30 meters. In the intermediate size, antennas 214 or digital signal processing component 216 are configured to receive and process reflections of the radar field to provide large-body gestures based on reflections from human tissue caused by body, arm, or leg movements, though smaller and more-precise gestures can be sensed as well. Example intermediate-sized radar fields include those in which a user makes gestures to control a television from a couch, change a song or volume from a stereo across a room, turn off an oven or oven timer (a near field would also be useful here), turn lights on or off in a room, and so forth.

Antennas 214 can instead be configured to provide a radar field from little if any distance from a computing device or its display. An example near field is illustrated in FIG. 1 at near radar field 106-1 and is configured for sensing gestures made by a user using a laptop, desktop, refrigerator water dispenser, and other devices where gestures are desired to be made near to the device.

Antennas 214 can be configured to emit continuously modulated radiation, ultra-wideband radiation, or sub-millimeter-frequency radiation. Antennas 214, in some cases, is configured to form radiation in beams, the beams aiding digital signal processing component 216 to determine which of the beams are interrupted, and thus locations of interactions within the radar field.

In an example in FIG. 1, the computer system 102-2 is configured to emit a radar field and to transmit wireless data modulated on the radar field (shown by the dashed line at 110) to computer system 102-3. In computer system 102-3, a gesture sensing component 104 or a transceiver is configured to receive wireless data and the gesture sensor component 104 is configured to use reflected portions of the transmitted wireless data signal to sense gestures, as described in detail above and below. Since the computer system 102-3 uses radio signals emitted by the computer system 102-2, the computer system 102-3 may be configured with or without the capability to radiate a radar field.

Additionally or alternately, the computer system 102-3 can transmit an indication of the gesture determined by the computer system 102-3 to the computer system 102-2 that emitted the radar field. The indication can be transmitted in any suitable way, such as via a network connection, as a part of or in addition to acknowledging the receipt of wireless data according to the data protocol in use, and so forth.

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

Data Protocols

FIG. 3 illustrates an example packet structures 300 used for wireless data communication for the example environment 100 in which various embodiments of radar gesture sensing using existing data protocols can be implemented. Generally, wireless packet data communication systems are defined using a layered model or network stack, such as the Open Systems Interconnection (OSI) model. Functions of the communication system are defined with respect to these layers to specify the protocols for how communications between devices are implemented. Layered models and network stacks are well known and a detailed discussion is beyond the scope of this application. The use of a layered model for communication results in transmitting data packets that include a number of fields. Each layer in the model receives data from the layer above, processes the received data, and adds additional information, typically as a header before passing the header and received data to the next lower layer.

For example, a data packet 302 includes a preamble field 304, a physical layer (PHY) header field 306, a media access layer (MAC) header field 308, a network layer header field 310, a data payload field 312 and a frame check sequence (FCS) field 314. The preamble field 304 includes information such as a training sequence that is a known bit or symbol pattern transmitted with every packet. The training sequence is used in various purposes, such as synchronizing the receiver to the timing of the received data packet, estimating channel conditions to compensate for fading conditions between the transmitter and receiver, and so forth.

The PHY header 306 includes information useful to the receiver in receiving and demodulating the data packet, such as the length of the data packet 302. The MAC header 308 includes encoding/decoding information that describes how the data packet being transmitted are encoded and decoded into bits as part of a transmission protocol. The network header 310 includes information that specifies how the data being transferred to a destination node is routed. The data payload field 312 includes data, such as data from an application that is being transferred in the data packet 302. The FCS field 314 includes integrity check information, such as a checksum, a cyclical redundancy check (CRC), or a message integrity check hash value, that is used by the receiving device to determine if the data payload 312 was corrupted during transmission.

The order, type, and presence/absence of particular fields may differ between communication systems without affecting the ability of the gesture sensing component 104 to use a data protocol for gesture recognition. For example, a data packet 316 includes a beginning sequence field 318, data fields 320, a midamble 322, and an ending sequence 324. The midamble 322 includes information similar to the preamble 304, such as the training sequence.

Propagation of RF Signals

FIG. 4 illustrates a simple example of RF wave propagation, and a corresponding reflected wave propagation. It is to be appreciated that the following discussion has been simplified, and is not intended to describe all technical aspects of RF wave propagation, reflected wave propagation, or detection techniques.

Environment 400 includes source device 402 and object 404. Source device 402 includes antenna 406, which is configured to transmit and receive electromagnetic waves in the form of an RF signal. In this example, source device 402 transmits a series of RF pulses, illustrated here as RF pulse 408a, RF pulse 408b, and RF pulse 408c. As indicated by their ordering and distance from source device 402, RF pulse 408a is transmitted first in time, followed by RF pulse 408b, and then RF pulse 408c. For discussion purposes, these RF pulses have the same pulse width, power level, and transmission periodicity between pulses, but any other suitable type of signal with alternate configurations can be transmitted without departing from the scope of the claimed subject matter.

Generally speaking, electromagnetic waves can be characterized by the frequency or wavelength of their corresponding oscillations. Being a form of electromagnetic radiation, RF signals adhere to various wave and particle properties, such as reflection. When an RF signal reaches an object, it will undergo some form of transition. Specifically, there will be some reflection off the object. Environment 400 illustrates the reflection of RF pulses 408a-408c reflecting off of object 404, where RF pulse 410a corresponds to a reflection originating from RF pulse 408a reflecting off of object 404, RF pulse 410b corresponds to a reflection originating from RF pulse 410b, and so forth. In this simple case, source device 402 and object 404 are stationary, and RF pulses 408a-408c are transmitted via a single antenna (antenna 406) over a same RF channel, and are transmitted directly towards object 404 with a perpendicular impact angle. Similarly, RF pulses 410a-410c are shown as reflecting directly back to source device 402, rather than with some angular deviation. However, as one skilled in the art will appreciate, these signals can alternately be transmitted or reflected with variations in their transmission and reflection directions based upon the configuration of source device 402, object 404, transmission parameters, variations in real-world factors, and so forth. Upon receiving and capturing RF pulses 410a-410c, source device 402 can then analyze the pulses, either individually or in combination, to identify characteristics related to object 404. For example, source device 402 can analyze all of the received RF pulses to obtain temporal information and/or spatial information about object 404. Accordingly, source device 402 can use knowledge about a transmission signal's configuration (such as pulse widths, spacing between pulses, pulse power levels, phase relationships, and so forth), and further analyze a reflected RF pulse to identify various characteristics about object 404, such as size, shape, movement speed, movement direction, surface smoothness, material composition, and so forth.

As discussed above, the source device 402 can be configured to emit continuously modulated radiation, ultra-wideband radiation, or sub-millimeter-frequency radiation for radar gesture sensing. The source device 402 can also be configured to use a data protocol to transmit data, in which case one or more portions of the transmitted data is used for radar gesture sensing. For example at 412, the source device 402 transmits a source wave modulated with the data packet 302. Upon receiving and capturing RF pulses 410a-410c, source device 402 can then analyze the entire pulses or the one or more portions of the pulses, such as analyzing the portion that corresponds to the preamble 304 of the data packet, to identify characteristics related to object 404.

FIG. 5 illustrates another example of RF wave propagation, and a corresponding reflected wave propagation. It is to be appreciated that the following discussion has been simplified, and is not intended to describe all technical aspects of RF wave propagation, reflected wave propagation, or detection techniques.

Environment 500 includes source device 402, object 404, and destination device 502. Source device 402 is configured to transmit data to destination device 502 using a known data protocol (shown at 504) such as a data protocol that uses the data packet 302. The beamwidth of RF signals transmitted from the source device 402 are sufficiently wide to transmit data to the destination device 502, as well as to illuminate the object 404 for radar gesture sensing.

Environment 500 illustrates the reflection of RF pulses 408a-408c reflecting off of object 404, where RF pulse 410a corresponds to a reflection originating from RF pulse 408a reflecting off of object 404, RF pulse 410b corresponds to a reflection originating from RF pulse 410b, and so forth. Similarly, RF pulses 410a-410c are shown as reflecting off the object 404 with angular deflection toward the destination device 502. Upon receiving and capturing RF pulses 410a-410c, destination device 502 can then analyze the pulses, either individually or in combination, to identify characteristics related to object 404. Additionally, RF pulses 410a-410c may also be reflected back to the source device 402 (not shown for visual brevity) and analyzed as described above with respect for FIG. 4.

Destination device 502 can also be configured to use a data protocol to receive data and/or use one or more portions of the reflections of a transmitted data for radar gesture sensing. The source device 402 and the destination device 502 communicate using a common data protocol. Although many fields in the data packets will vary in each packet, such as the data payload 312 and the FCS 314, there are fields that are identical in each packet, such as the preamble 304 or a training sequence. For example, the destination device 502 can use the training sequence in the RF pulses 410a-410c for radar gesture sensing, as the training sequence is identical in each data packet transmitted in accordance with the data protocol.

The training sequence of a data protocol can be modified to improve gesture sensing performance. By way of example and not limitation, parameters of the training sequence, such as the length of the training sequence, the modulation code, the chip rate, the number of repetitions of the sequence, and so forth, can be modified to achieve a desired radar resolution and signal-to-noise ratio (SNR) that optimize gesture sensing performance.

Additionally or alternatively, a field can be added to the fields defined by the existing data protocol to improve gesture sensing performance. For example, a postamble field can be added following the FCS field 314 of the data packet 302. To receive data, a receiver uses the fields defined by the existing data protocol and ignores the postamble. The postamble can be used for gesture sensing and the bit pattern in the postamble can be optimized for gesture sensing performance, as described above.

The destination device may use a combination of fields within a data packet for radar gesture recognition. For example, the source device 402 and destination device 502 are communicating in a session in an environment where other devices are also transmitting with the same data protocol. The destination device 502 may use portions of the data packet 302 to differentiate the transmissions and reflections related to the source device 402 from those of the other devices. The data protocol defines addressing information, such as source and/or destination addresses. The data protocol also defines the location of the addressing information in the data packet, such as in the PHY header 306, MAC header 308, or network header 310. For example, the destination device 502 may use the training sequence along with source and/or destination addressing information in the data packet to identify that the reflected RF pulses 410a-410c correspond to transmissions from the source device 402 and are not reflections from transmissions by another device.

Now consider FIG. 6, which builds upon the above discussion of FIG. 4. FIG. 6 illustrates example environment 600 in which multiple antenna are used to ascertain information about a target object. Environment 600 includes source device 602 and a target object, shown here as hand 604. Generally speaking, source device 602 includes antennas 606a-606d to transmit and receive multiple RF signals. In some embodiments, source device 602 includes gesture component 104 of FIGS. 1 and 2 and antennas 606a-606d correspond to antennas 214. While source device 602 in this example includes four antennas, it is to be appreciated that any suitable number of antennas can be used. Each antenna of antennas 606a-606d is used by source device 602 to transmit a respective RF signal (e.g., antenna 606a transmits RF signal 608a, antenna 606b transmits RF signal 608b, and so forth). As discussed above, these RF signals can be configured to form a specific transmission pattern or diversity scheme when transmitted together. For example, the configuration of RF signals 608a-608d, as well as the placement of antennas 606a-606d relative to a target object, can be based upon beamforming techniques to produce constructive interference or destructive interference patterns, or alternately configured to support triangulation techniques. At times, source device 602 configures RF signals 608a-608d based upon an expected information extraction algorithm, as further described below.

When RF signals 608a-608d reach a hand 604, the signals generate reflected RF signals 610a-610d. Similar to the discussion of FIGS. 4 and 5 above, source device 602 and/or destination device 502 captures these reflected RF signals, and then analyzes them to identify various properties or characteristics of hand 604, such as a micro-gesture. For instance, in this example, RF signals 608a-608d are illustrated with the bursts of the respective signals being transmitted synchronously in time. In turn, and based upon the shape and positioning of hand 604, reflected signals 610a-610d return to source device 602 at different points in time (e.g., reflected signal 610b is received first, followed by reflected signal 610c, then reflected signal 610a, and then reflected signal 610d). Reflected signals 610a-610d can be received by source device 602 in any suitable manner. For example, antennas 606a-606d can each receive all of reflected signals 610a-610d, or receive varying subset combinations of reflected signals 610a-610d (i.e. antenna 606a receives reflected signal 610a and reflected signal 610d, antenna 606b receives reflected signal 610a, reflected signal 610b, and reflected signal 610c, etc.). Thus, each antenna can receive reflected signals generated by transmissions from another antenna. By analyzing the various return times of each reflected signal, source device 602 can determine shape and corresponding distance information associated with hand 604. When reflected pulses are analyzed over time, source device 602 can additionally discern movement. Thus, by analyzing various properties of the reflected signals, as well as the transmitted signals, various information about hand 604 can be extracted, as further described below. It is to be appreciated that the above example has been simplified for discussion purposes, and is not intended to be limiting.

As in the case of FIG. 4, FIG. 6 illustrates RF signals 608a-608d as propagating at a 90° angle from source device 602 and in phase with one another. Similarly, reflected signals 610a-610d each propagate back at a 90° angle from hand 604 and, as in the case of RF signals 608a-608d, are in phase with one another. However, as one skilled in the art will appreciate, more complex transmission signal configurations, and signal analysis on the reflected signals, can be utilized, examples of which are provided above and below. In some embodiments, RF signals 608a-608d can each be configured with different directional transmission angles, signal phases, power levels, modulation schemes, RF transmission channels, and so forth. These differences result in variations between reflected signals 610a-610d. In turn, these variations each provide different perspectives of the target object which can be combined using data fusion techniques to yield a better estimate of hand 604, how it is moving, its three dimensional (3D) spatial profile, a corresponding micro-gesture, and so forth.

Having described general principles of RF signals which can be used in gesture detection, now consider a discussion of various forms of information extraction that can be employed in accordance with one or more embodiments.

Wireless Detection of Gestures

The above discussion describes simple examples of RF signal transmission and reflection. In the case of using multiple antenna, it can be seen how transmitting a plurality of RF signals that have variations from one another results in receiving diverse information about a target object from the corresponding reflected signals. The diverse information can then be combined to improve detecting a characteristic or gesture associated with the target object. Accordingly, the system as a whole can exploit or optimize which signals are transmitted to improve the amount of information that can be extracted from the reflected signals. Some embodiments of a gesture sensor component 104 capture raw data representative of signals reflected off a target object. In turn, digital-signal processing algorithms extract information from the raw data, which can then be fed to a machine-learning algorithm to classify a corresponding behavior of the target object. At times, the gesture sensor component utilizes a pipeline to identify or classify a gesture.

FIG. 7 illustrates the various stages employed by an example pipeline 700 to identify gestures and expose operations to be controlled by those gestures to applications. In some implementations, pipeline 700 can be implemented by various components of gesture component 104 of FIGS. 1 and 2, such as antennas 214, digital signal processing component 216, machine-learning component 218, and/or output logic component 220. It is to be appreciated that these stages have been simplified for discussion purposes, and are not intended to be limiting.

From one viewpoint, the stages can be grouped into two classifications: transmit side functionality 702 and receive side functionality 704. Generally speaking, the transmit side functionality in the pipeline does not feed directly into the receive side functionality. Instead, the transmit side functionality generates transmit signals which contribute to the reflected signals captured and processed by the receive side functionality, as further described above. Accordingly, the relationship between the transmit side functionality and the receive side functionality is indicated in pipeline 700 through the use of a dotted line to connect stage 706 of the pipeline with stage 708, rather than a solid line, since in various embodiments they are not directly connected with one another. As illustrated in FIG. 5 the transmit side of the pipeline 700 may be in a transmitting device, such as source device 402 and the receive side of the pipeline may be in a receiving device, such as destination device 502.

Stage 706 of the pipeline configures the RF transmit signals. In some cases, various transmission parameters are determined in order to generate the RF transmit signals. At times, the transmission parameters can be based upon an environment in which they are being used. For instance, the transmission parameters can be dependent upon a number of antenna available, the types of antenna available, a target object being detected, directional transmission information, a requested detection resolution, a long range object detection mode, a short range object detection mode, an expected receive-side digital signal processing algorithm, an expected receive-side machine-learning algorithm, physical antenna placement, and so forth. As noted above, the configuration of the RF transmit signals can be dependent upon an expected analysis on the receive side. Thus, the configuration of the RF transmit signals can change to support triangulation location detection methods, beamforming detection methods, and so forth. In some examples, the transmission parameters are automatically selected or loaded at startup (e.g., the RF transmit signal configurations are fixed). In other examples, these parameters are modifiable, such as through gesture sensor APIs 208.

Additionally, stage 706 of the pipeline configures the RF signals to transmit data according to a data protocol. For example, stage 706 modulates the RF signals with data for transmission according to the modulation and transmission parameters specified by the data protocol. Control of the data transmissions and providing data for transmission from applications is provided through APIs, such as the gesture sensor APIs 208.

At the start of receive side functionality 704, stage 708 performs signal pre-processing on raw data. For example, as an antenna receives reflected signals (e.g., antennas 606a-606d receiving some or all of reflected signals 610a-610d of FIG. 6), some instances sample the signals and generate a digital representation of the raw incoming signals. Upon generating the raw data, stage 708 performs pre-processing to clean up the signals or generate versions of the signals in a desired frequency band, or in a desired format. In some cases, pre-processing includes filtering the raw data to reduce a noise floor or remove aliasing, resampling the data to obtain to a different sample rate, generating a complex representation of the signal(s), and so forth. In some cases, stage 708 automatically pre-processes the raw data based upon default parameters, while in other cases the type of pre-processing is modifiable, such as through gesture sensor APIs 208.

Stage 710 transforms the received signal data into one or more different representations. Here, the signals pre-processed by stage 708 are fed into stage 710. At times, stage 710 combines data from multiple paths (and corresponding antenna). The combined data can be any combination of “transmit paths,” “receive paths,” and “transmit and receive paths.” Any suitable type of data fusion technique can be used, such as weighted integration to optimize a heuristic (e.g., signal-to-noise (SNR) ratio, minimum mean square error (MMSE), etc.), beamforming, triangulation, and so forth. All respective paths can be combined together, or various sub-combinations of paths can be made, to generate combined signal data.

Additionally, stage 708 and/or stage 710 of the pipeline recovers data modulated on the RF signals according to the data protocol. For example, stage 708 and/or stage 710 demodulate the RF signals to recover transmitted data according to parameters specified by the data protocol. Control of the data reception and providing data received data to applications is provided through APIs, such as the gesture sensor APIs 208.

In some implementations, stage 710 generates multiple combinations of signal data for different types of feature extraction, and/or transforms the signal data into another representation as a precursor to feature extraction. For example, some embodiments process the combined signal data to generate a three dimensional (3D) spatial profile of the target object. However, any suitable type of algorithm can be used to generate a transformed view or version of the raw data, such as an I/Q transformation that yields a complex vector containing phase and amplitude information related to the target object, a beamforming transformation that yields a spatial representation of target objects within range of a gesture sensor device, a Range-Doppler algorithm that yields target velocity and direction, a Range profile algorithm that yields target recognition information, a Micro-Doppler algorithm that yields high-resolution target recognition information, a Spectogram algorithm that yields a visual representation of the corresponding frequencies, and so forth.

As described above, raw data can be processed in several ways to generate several transformations or combined signal data. At times, the same data can be analyzed or transformed in multiple ways. For instance, a same capture of raw data can be processed to generate a three-dimensional profile, target velocity information, and target directional movement information. In addition to generating transformations of the raw data, stage 710 can perform basic classification of the target object, such as identifying information about its presence, a shape, a size, an orientation, a velocity over time, and so forth. For example, some implementations use stage 710 to identify a basic orientation of a hand by measuring an amount of reflected energy off of the hand over time. These transformations and basic classifications can be performed in hardware, software, firmware, or any suitable combination. At times, the transformations and basic classifications are performed by digital signal processing component 216 and/or machine-learning component 218 of FIG. 2. In some cases, stage 710 automatically transforms the raw data or performs a basic classification based upon default parameters, while in other cases the transformations or classifications are modifiable, such as through gesture sensor APIs 208.

Stage 712 receives the transformed representation of the data from stage 710, and extracts or identifies features using the data. At times, feature extraction builds upon a basic classification identified in stage 710. Consider the above example in which stage 710 classifies a target object as a hand Stage 712 can build from this basic classification to extract lower resolution features of the hand In other words, if stage 712 is provided information identifying the target object as a hand, then stage 712 uses this knowledge to look for hand-related features (e.g., finger tapping, shape gestures, swipe movements, etc.) instead of head-related features, (e.g., an eye blink, mouthing a word, a head-shaking movement, etc.).

As another example, consider a scenario where stage 710 transforms the raw signal data into a measure of the target object's velocity-over-time. In turn, this information can used by stage 712 to identify a finger fast-tap motion by using a threshold value to compare the target object's velocity of acceleration to the threshold value, a slow-tap feature, and so forth. Any suitable type of algorithm can be used to extract a feature, such as machine-learning algorithms implemented by machine-learning component 218, and/or digital signal processing algorithms implemented by digital signal processing component 216 of FIG. 2. Some implementations simply apply a single algorithm to extract, identify, or classify a feature, while other embodiments apply multiple algorithms to extract a single feature or multiple features. Thus, different algorithms can be applied to extract different types of features on a same set of data, or different sets of data. In some cases, stage 712 searches for a default feature using default algorithms, while in other cases the applied algorithms and/or the feature being searched for is modifiable, such as through gesture senor APIs 208.

Using feature extraction information generated by stage 712, stage 714 performs gesture recognition using a gesture library. For instance, consider a case where a finger tap feature has been extracted. Stage 714 uses this information and compares it to descriptions of gestures to identify the feature as a double-click micro-gesture. At times, gesture recognition can be a probabilistic determination of which gesture has most likely occurred based upon the input information and how this information relates to one or more previously learned characteristics or features of various gestures. For example, a machine-learning algorithm can be used to determine how to weight various received characteristics to determine a likelihood these characteristics correspond to particular gestures (or components of the gestures). As in the case above, some implementations apply a single algorithm to recognize a gesture, while other embodiments apply multiple algorithms to identify a single gesture or multiple gestures. This can include micro-gestures or macro-gestures. Further, any suitable type of algorithm can be used to identify a gesture, such as machine-learning algorithms implemented by machine-learning component 218, and/or digital signal processing algorithms implemented by digital signal processing component 216 of FIG. 2. In some examples, stage 714 uses default algorithms to identify a gesture, while in other cases the applied algorithms and/or the gesture being identified is modifiable, such as through gesture sensor APIs 208.

From the identified gesture, stage 714 may also identify an operation that corresponds to the gesture and even a degree to which the gesture is to be performed for operations having quantitative features. The gesture library, for instance, may map the gestures to respective operations to be performed upon detection of the gesture. This may also be used to map amounts that are to be used to perform the operations, such as to raise or lower volume, a scrolling amount, and so forth. Stage 716 then exposes an indication of this operation, as well as the mapped amount as appropriate, via the gesture sensor APIs 208 for receipt by the applications 206 of FIG. 2. The applications 206 may then control performance of the operations of the computing device 102, e.g., to initiate or continue an operation, set an amount in which to perform an operation, and so forth.

Pipeline 700 provides an ability to detect gestures, e.g., micro-gestures or macro-gestures. This can include movements based on portions of a target object, rather than the whole target object. Consider again the example case of a target object that is a hand. On a whole, the hand, or portions of the hand, can be in a stationary position while other portions of the hand, such as one or more fingers, are moving. The above described techniques can be used to not only identify a stationary hand, but portions of the hand that are moving, such as two fingers rubbing together. Thus, a micro-gesture can entail identifying a first portion of the hand as being stationary, and identifying a second portion of the hand as having movement relative to the stationary portion.

Example Methods

Example methods 800 and 900 are described with reference to respective FIGS. 8 and 9 in accordance with one or more embodiments of the radar gesture sensing using existing data protocols. Generally, any of the components, modules, methods, and operations described herein can be implemented using software, firmware, hardware (e.g., fixed logic circuitry), manual processing, or any combination thereof. Some operations of the example methods may be described in the general context of executable instructions stored on computer-readable storage memory that is local and/or remote to a computer processing system, and implementations can include software applications, programs, functions, and the like. Alternatively or in addition, any of the functionality described herein can be performed, at least in part, by one or more hardware logic components, such as, and without limitation, Field-programmable Gate Arrays (FPGAs), Application-specific Integrated Circuits (ASICs), Application-specific Standard Products (ASSPs), System-on-a-chip systems (SoCs), Complex Programmable Logic Devices (CPLDs), and the like.

FIG. 8 illustrates example method(s) 800 of radar gesture sensing using existing data protocols as generally related to sensing gestures from radar reflections. The order in which the method blocks are described are not intended to be construed as a limitation, and any number of the described method blocks can be combined in any order to implement a method, or an alternate method.

At 802 radio frequency (RF) signals are modulated with data. For example, the gesture sensor component 104 or the transmit side functionality 702 of the pipeline 700 modulate the RF output signals according to an existing data protocol used for communication.

At 804, a radar field is emitted using the modulated RF signals. For example, the gesture sensor component 104 or the transmit side functionality 702 of the pipeline 700 configure RF signals for the radar field. The antennas 214 emit the radar field using the modulated RF signals configured by the gesture sensor component 104 or the transmit side functionality 702 of the pipeline 700.

At 806, reflections of the modulated radar field are received. For example, the antennas 214 receive reflections of the modulated radar field for an interaction that occurs in the radar field. The antennas 214 provide RF signals from the received reflections to the receive side functionality 704 of the pipeline 700 or the digital signal processing component 216.

At 808, the received reflections are analyzed. For example, the receive side functionality 704 of the pipeline 700 or the digital signal processing component 216 captures and processes the RF signals. For instance, digital signal processing component 216 performs sampling on RF signals received by antennas 214 to generate digital samples that represent the RF signals, and processes the digital samples to extract information about the target that caused the reflections. The digital signal processing component 216 or the receive side functionality 704 of the pipeline 700 can process the RF signals to identify fields of the data packet 302 that were modulated onto the radar field. The digital signal processing component 216 or the receive side functionality 704 of the pipeline 700 can selectively provide digital samples corresponding to one or more of the identified fields for successive processing to determine a gesture.

At 810, the gesture is determined using a portion of the received reflections. For example, the receive side functionality 704 of the pipeline 700 or the machine-learning component 218 uses that information in the processed signals to classify or recognize various aspects of the target object. The output logic component 220 may further filter output information generated by digital signal processing component 216 and machine-learning component 218 to further refine the gesture determination.

FIG. 9 illustrates example method(s) 900 of radar gesture sensing using existing data protocols as generally related to sensing gestures from radar reflections. The order in which the method blocks are described are not intended to be construed as a limitation, and any number of the described method blocks can be combined in any order to implement a method, or an alternate method.

At 902, a radar field that is modulated with data is received. For example, the antennas 214 receive reflections of the modulated radar field for an interaction in the radar field. The antennas 214 provide RF signals from the received reflections to the receive side functionality 704 of the pipeline 700 or the digital signal processing component 216.

At 904, addressing information in the received data is decoded. For example, the receive side functionality 704 of the pipeline 700 or the digital signal processing component 216 captures and processes the RF signals. For instance, digital signal processing component 216 performs sampling on RF signals received by antennas 214 to generate digital samples that represent the RF signals, and processes the digital samples to decode fields of the data packet 302 that were modulated onto the radar field.

At 906, addressing information is determined to correspond to a desired transmitter of the radar field. For example, the digital signal processing component 216 or the receive side functionality 704 of the pipeline 700 compares decoded addressing information in the decoded data packet 302 and compare the addressing information, such as a source address of the source device 402 to a desired source address. If the decoded source address matches the desired source address, the digital signal processing component 216 or the receive side functionality 704 of the pipeline 700 selectively provides digital samples for one or more of the identified fields for successive processing to determine a gesture. Otherwise the digital samples may be discarded.

At 908, the received reflections are analyzed. For example, the receive side functionality 704 of the pipeline 700 or the digital signal processing component 216 processes the provided digital samples to extract information about the target that caused the reflections for successive processing to determine a gesture.

At 910, the gesture is determined using a portion of the received reflections. For example, the receive side functionality 704 of the pipeline 700 or the machine-learning component 218 uses that information in the processed signals to classify or recognize various aspects of the target object. The output logic component 220 may further filter output information generated by digital signal processing component 216 and machine-learning component 218 to further refine the gesture determination.

Example Computing Device

FIG. 10 illustrates various components of an example computing device 1000 that incorporates radar gesture sensing using existing data protocols as described with reference to FIGS. 1-9. Computing device 1000 may be implemented as any type of a fixed or mobile device, in any form of a consumer, computer, portable, user, communication, phone, navigation, gaming, audio, camera, messaging, media playback, and/or other type of electronic device, such as computing device 102 described with reference to FIGS. 1 and 2. In light of this, it is to be appreciated that various alternate embodiments can include additional components that are not described, or exclude components that are described, with respect to computing device 1000.

Computing device 1000 includes communication devices 1002 that enable wired and/or wireless communication of device data 1004 (e.g., received data, data that is being received, data scheduled for broadcast, data packets of the data, etc.). The device data 1004 or other device content can include configuration settings of the device and/or information associated with a user of the device.

Computing device 1000 also includes communication interfaces 1006 that 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. The communication interfaces 1006 provide a connection and/or communication links between computing device 1000 and a communication network by which other electronic, computing, and communication devices communicate data with computing device 1000.

Computing device 1000 includes one or more processors 1008 (e.g., any of microprocessors, controllers, and the like) which process various computer-executable instructions to control the operation of computing device 1000 and to implement embodiments of the techniques described herein. Alternatively or in addition, computing device 1000 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 1010. Although not shown, computing device 1000 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.

Computing device 1000 also includes computer-readable media 1012, such as one or more memory components, 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.

An implementation of the described modules and techniques may be stored on or transmitted across some form of computer-readable media. The computer-readable media may include a variety of media that may be accessed by the computing device 1000. By way of example, and not limitation, computer-readable media may include “computer-readable storage media” and “computer-readable signal media.”

“Computer-readable storage media” may refer to media and/or devices that enable persistent and/or non-transitory storage of information in contrast to mere signal transmission, carrier waves, or signals per se. Thus, computer-readable storage media refers to non-signal bearing media. The computer-readable storage media includes hardware such as volatile and non-volatile, removable and non-removable media and/or storage devices implemented in a method or technology suitable for storage of information such as computer readable instructions, data structures, program modules, logic elements/circuits, or other data. Examples of computer-readable storage media may include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical storage, hard disks, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or other storage device, tangible media, or article of manufacture suitable to store the desired information and which may be accessed by a computer.

“Computer-readable signal media” may refer to a signal-bearing medium that is configured to transmit instructions to the hardware of the computing device 1000, such as via a network. Signal media typically may embody computer readable instructions, data structures, program modules, or other data in a modulated data signal, such as carrier waves, data signals, or other transport mechanism. Signal media also include any information delivery media. The term “modulated data signal” means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media include wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared, and other wireless media.

Computer-readable media 1012, when configured as computer-readable storage media, provides data storage mechanisms to store the device data 1004, as well as various applications 1014 and any other types of information and/or data related to operational aspects of computing device 1000. The applications 1014 can include a device manager (e.g., 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, etc.).

Computing device 1000 also includes audio and/or video processing system 1016 that processes audio data and/or passes through the audio and video data to audio system 1018 and/or to display system 1020 (e.g., a screen of a smart phone or camera). Audio system 1018 and/or display system 1020 may include any devices that process, display, and/or otherwise render audio, video, display, and/or image data. Display data and audio signals can be communicated to an audio component and/or to a display component via an RF link, S-video link, HDMI, composite video link, component video link, DVI, analog audio connection, or other similar communication link, such as media data port 1022. In some implementations, audio system 1018 and/or display system 1020 are external components to computing device 1000. Alternatively or additionally, display system 1020 can be an integrated component of the example electronic device, such as part of an integrated touch interface.

Computing device 1000 also includes a gesture component 1024 (e.g., the gesture sensing component 104) that wirelessly identifies one or more features of a target object, such as a micro-gesture performed by a hand as further described above. Gesture component 1024 can be implemented as any suitable combination of hardware, software, firmware, and so forth. In some embodiments, gesture component 1024 is implemented as an SoC. Among other things, gesture component 1024 includes antennas 1026, digital signal processing component 1028, machine-learning component 1030, and output logic component 1032.

Antennas 1026 transmit and receive RF signals under the control of gesture sensor component. Each respective antenna of antennas 1026 can correspond to a respective transceiver path internal to gesture sensor component 1024 that physical routes and manages outgoing signals for transmission and the incoming signals for capture and analysis as further described above.

Digital signal processing component 1028 digitally processes RF signals received via antennas 1026 to extract information about the target object. This can be high-level information that simply identifies a target object, or lower level information that identifies a particular micro-gesture performed by a hand In some embodiments, digital signal processing component 1028 additionally configures outgoing RF signals for transmission on antennas 1026. Some of the information extracted by digital signal processing component 1028 is used by machine-learning component 1030. Digital signal processing component 1028 at times includes multiple digital signal processing algorithms that can be selected or deselected for an analysis, examples of which are provided above. Thus, digital signal processing component 1028 can generate key information from RF signals that can be used to determine what gesture might be occurring at any given moment.

Machine-learning component 1030 receives input data, such as a transformed raw signal or high-level information about a target object, and analyzes the input date to identify or classify various features contained within the data. As in the case above, machine-learning component 1030 can include multiple machine-learning algorithms that can be selected or deselected for an analysis. Among other things, machine-learning component 1030 can use the key information generated by digital signal processing component 1028 to detect relationships and/or correlations between the generated key information and previously learned gestures to probabilistically decide which gesture is being performed.

Output logic component 1032 logically filters output information generated by digital signal processing component 1028 and/or machine-learning component 1030. Among other things, output logic component 1032 identifies when received information is redundant, and logically filters the redundancy out to an intended recipient.

Computing device 1000 also includes gesture sensor APIs 1034, which are illustrated as being embodied on computer-readable media 1012. Gesture sensor APIs 1034 provide programmatic access to gesture sensor component 1024, examples of which are provided above. The programmatic access can range from high-level program access that obscures underlying details of how a function is implemented, to low-level programmatic access that enables access to hardware. In some cases, gesture sensor APIs 1034 can be used to send input configuration parameters associated with modifying operation of digital signal processing component 1028, machine-learning component 1030, output logic component 1032, or any combination thereof, examples of which are provided above.

Although the embodiments have been described in language specific to structural features and/or methodological acts, it is to be understood that the various embodiments defined in the appended claims are not necessarily limited to the specific features or acts described. Rather, the specific features and acts are disclosed as example forms of implementing the various embodiments.

Claims

1. A computer-implemented method comprising: modulating a radio frequency (RF) signal with data according to a data protocol, the data comprising a training sequence in accordance with the data protocol;emitting a radar field using the modulated RF signal, the radar field including the training sequence;receiving one or more reflection signals caused by a reflection of the radar field off an object performing a gesture within the radar field, the reflection signals containing portions corresponding to the training sequence; andanalyzing the portions of the reflection signals corresponding to the training sequence to determine the gesture.
2. The computer-implemented method as described in claim 1, wherein the data protocol defines fields of a data packet used for transmission of the data and wherein the training sequence is included in a preamble field of the data packet.
3. The computer-implemented method as described in claim 2, further comprising: transmitting the data to a device using the radar field, the transmitting being effective to enable the device to receive the data using the data protocol.
4. The computer-implemented method as described in claim 3, wherein the emitting the radar field is effective to enable the device to: receive one or more other reflection signals caused by the reflection of the radar field off the object performing the gesture within the radar field, the other reflection signals containing portions corresponding to the training sequence; andanalyze the portions of the other reflection signals corresponding to the training sequence to determine the gesture.
5. The computer-implemented method as described in claim 3, wherein the device uses the training sequence to estimate channel conditions in order to adjust parameters of a receiver in the device.
6. The computer-implemented method as described in claim 1, the method further comprising: analyzing portions of the reflection signals not corresponding to the training sequence to determine the gesture.
7. A radar system comprising: a first device configured to: modulate a radio frequency (RF) signal with data formatted according to a data protocol, the data comprising at least a training sequence in accordance with the data protocol;emit a radar field using the modulated RF signal, the radar field including the training sequence;a second device configured to: receive one or more reflection signals caused by a reflection of the radar field off an object performing a gesture within the radar field, the reflection signals containing portions corresponding to the training sequence; andanalyze the portions of the reflection signals corresponding to the training sequences to determine the gesture.
8. The radar system as described in claim 7, wherein the data protocol defines fields of a data packet used for transmission of the data and wherein the training sequence is included in a preamble field of the data packet.
9. The radar system as described in claim 8, the first device further configured to transmit the data to the second device using the radar field, and the second device further configured to receive the transmitted data using the data protocol.
10. The radar system as described in claim 7, wherein the second device uses the training sequence to estimate channel conditions between the first device and the second device and wherein the second device uses the estimated channel conditions to adjust parameters of a receiver in the second device.
11. The radar system as described in claim 7, the second device further configured to transmit an indication of the determined gesture to the first device.
12. The radar system as described in claim 7, the first device further configured to: receive one or more other reflection signals caused by the reflection of the radar field off the object performing the gesture within the radar field, the other reflection signals containing portions corresponding to the training sequence; andanalyze the portions of the other reflection signals corresponding to the training sequence to determine the gesture.
13. The radar system as described in claim 12, the first device further configured to: analyze other portions of the other reflection signals to determine the gesture.
14. A device comprising a gesture sensing component, the gesture sensing component configured to: modulate a radio frequency (RF) signal with data formatted according to a data protocol, the data comprising at least a training sequence in accordance with the data protocol;emit a radar field using the modulated RF signal, the radar field including the training sequence;receive one or more reflection signals caused by a reflection of the radar field off an object performing a gesture within the radar field, the reflection signals containing portions corresponding to the training sequence; andanalyze the portions of the reflection signals corresponding to the training sequence to determine the gesture.
15. The device as described in claim 14, wherein the data protocol defines fields of a data packet used for transmission of the data and wherein the training sequence is included in a preamble field of the data packet.
16. The device as described in claim 15, the device further configured to transmit the data to an additional device using the radar field, the transmission being effective to enable the additional device to receive the transmitted data using the data protocol.
17. The device as described in claim 16, wherein the emission of the radar field is effective to enable the additional device to: receive one or more other reflection signals caused by the reflection of the radar field off the object performing the gesture within the radar field, the other reflection signals containing portions corresponding to the training sequence; andanalyze the portions of the reflection signals corresponding to the training sequence to determine the gesture.
18. The device as described in claim 14, the device further configured to: analyze other portions of the reflection signals to determine the gesture.
19. The device as described in claim 14, the gesture sensing component comprising one or more antennas, and wherein the device is configured to emit the radar field using the one or more antennas.
20. The device as described in claim 14, the gesture sensing component comprising a digital signal processing component, and wherein the device is configured to modulate the RF signal using the digital signal processing component.

PRIORITY APPLICATION

This application claims priority under 35 U.S.C. § 119(e) to U.S. Provisional Patent Application No. 62/237,975, entitled “Signal Processing and Gesture Recognition” and filed on Oct. 6, 2015, the disclosure of which is incorporated in its entirety by reference herein.

US Referenced Citations (538)

Number	Name	Date	Kind
3610874	Gagliano	Oct 1971	A
3752017	Lloyd et al.	Aug 1973	A
3953706	Harris et al.	Apr 1976	A
4104012	Ferrante	Aug 1978	A
4654967	Thenner	Apr 1987	A
4700044	Hokanson et al.	Oct 1987	A
4795998	Dunbar et al.	Jan 1989	A
4838797	Dodier	Jun 1989	A
5016500	Conrad et al.	May 1991	A
5121124	Spivey et al.	Jun 1992	A
5298715	Chalco et al.	Mar 1994	A
5341979	Gupta	Aug 1994	A
5410471	Alyfuku et al.	Apr 1995	A
5468917	Brodsky et al.	Nov 1995	A
5564571	Zanotti	Oct 1996	A
5656798	Kubo et al.	Aug 1997	A
5724707	Kirk et al.	Mar 1998	A
5798798	Rector et al.	Aug 1998	A
6032450	Blum	Mar 2000	A
6037893	Lipman	Mar 2000	A
6080690	Lebby et al.	Jun 2000	A
6101431	Niwa et al.	Aug 2000	A
6210771	Post et al.	Apr 2001	B1
6254544	Hayashi	Jul 2001	B1
6313825	Gilbert	Nov 2001	B1
6340979	Beaton et al.	Jan 2002	B1
6386757	Konno	May 2002	B1
6440593	Ellison et al.	Aug 2002	B2
6492980	Sandbach	Dec 2002	B2
6493933	Post et al.	Dec 2002	B1
6513833	Breed et al.	Feb 2003	B2
6513970	Tabata et al.	Feb 2003	B1
6524239	Reed et al.	Feb 2003	B1
6543668	Fujii et al.	Apr 2003	B1
6616613	Goodman	Sep 2003	B1
6711354	Kameyama	Mar 2004	B2
6717065	Hosaka et al.	Apr 2004	B2
6802720	Weiss et al.	Oct 2004	B2
6833807	Flacke et al.	Dec 2004	B2
6835898	Eldridge et al.	Dec 2004	B2
6854985	Weiss	Feb 2005	B1
6929484	Weiss et al.	Aug 2005	B2
6970128	Dwelly et al.	Nov 2005	B1
6997882	Parker et al.	Feb 2006	B1
7019682	Louberg et al.	Mar 2006	B1
7134879	Sugimoto et al.	Nov 2006	B2
7164820	Eves et al.	Jan 2007	B2
7194371	McBride et al.	Mar 2007	B1
7223105	Weiss et al.	May 2007	B2
7230610	Jung et al.	Jun 2007	B2
7249954	Weiss	Jul 2007	B2
7266532	Sutton et al.	Sep 2007	B2
7299964	Jayaraman et al.	Nov 2007	B2
7310236	Takahashi et al.	Dec 2007	B2
7317416	Flom et al.	Jan 2008	B2
7348285	Dhawan et al.	Mar 2008	B2
7365031	Swallow et al.	Apr 2008	B2
7421061	Boese et al.	Sep 2008	B2
7462035	Lee et al.	Dec 2008	B2
7528082	Krans et al.	May 2009	B2
7544627	Tao et al.	Jun 2009	B2
7578195	DeAngelis et al.	Aug 2009	B2
7644488	Aisenbrey	Jan 2010	B2
7647093	Bojovic et al.	Jan 2010	B2
7670144	Ito et al.	Mar 2010	B2
7677729	Vilser et al.	Mar 2010	B2
7691067	Westbrook et al.	Apr 2010	B2
7698154	Marchosky	Apr 2010	B2
7791700	Bellamy	Sep 2010	B2
7834276	Chou et al.	Nov 2010	B2
7941676	Glaser	May 2011	B2
7952512	Delker	May 2011	B1
7999722	Beeri et al.	Aug 2011	B2
8062220	Kurtz et al.	Nov 2011	B2
8063815	Valo et al.	Nov 2011	B2
8169404	Boillot	May 2012	B1
8179604	Prada Gomez et al.	May 2012	B1
8193929	Siu et al.	Jun 2012	B1
8199104	Park et al.	Jun 2012	B2
8282232	Hsu et al.	Oct 2012	B2
8289185	Alonso	Oct 2012	B2
8301232	Albert et al.	Oct 2012	B2
8314732	Oswald	Nov 2012	B2
8334226	Nhan et al.	Dec 2012	B2
8341762	Balzano	Jan 2013	B2
8344949	Moshfeghi	Jan 2013	B2
8367942	Howell et al.	Feb 2013	B2
8475367	Yuen et al.	Jul 2013	B1
8505474	Kang et al.	Aug 2013	B2
8509882	Albert et al.	Aug 2013	B2
8514221	King et al.	Aug 2013	B2
8527146	Jackson et al.	Sep 2013	B1
8549829	Song et al.	Oct 2013	B2
8560972	Wilson	Oct 2013	B2
8562526	Heneghan et al.	Oct 2013	B2
8569189	Bhattacharya et al.	Oct 2013	B2
8614689	Nishikawa et al.	Dec 2013	B2
8655004	Prest et al.	Feb 2014	B2
8700137	Albert	Apr 2014	B2
8758020	Burdea et al.	Jun 2014	B2
8759713	Sheats	Jun 2014	B2
8764651	Tran	Jul 2014	B2
8785778	Streeter et al.	Jul 2014	B2
8790257	Libbus et al.	Jul 2014	B2
8814574	Selby et al.	Aug 2014	B2
8819812	Weber et al.	Aug 2014	B1
8854433	Rafii	Oct 2014	B1
8860602	Nohara et al.	Oct 2014	B2
8921473	Hyman	Dec 2014	B1
8948839	Longinotti-Buitoni et al.	Feb 2015	B1
9055879	Selby et al.	Jun 2015	B2
9093289	Vicard et al.	Jul 2015	B2
9125456	Chow	Sep 2015	B2
9141194	Keyes et al.	Sep 2015	B1
9148949	Zhou et al.	Sep 2015	B2
9229102	Wright et al.	Jan 2016	B1
9230160	Kanter	Jan 2016	B1
9235241	Newham	Jan 2016	B2
9316727	Sentelle et al.	Apr 2016	B2
9331422	Nazzaro et al.	May 2016	B2
9335825	Rautianinen et al.	May 2016	B2
9346167	O'Connor et al.	May 2016	B2
9354709	Heller et al.	May 2016	B1
9508141	Khachaturian et al.	Nov 2016	B2
9569001	Mistry et al.	Feb 2017	B2
9575560	Poupyrev et al.	Feb 2017	B2
9588625	Poupyrev	Mar 2017	B2
9594443	Vanblon et al.	Mar 2017	B2
9600080	Poupyrev	Mar 2017	B2
9693592	Robinson et al.	Jul 2017	B2
9746551	Scholten et al.	Aug 2017	B2
9766742	Papakostas	Sep 2017	B2
9778749	Poupyrev	Oct 2017	B2
9811164	Poupyrev	Nov 2017	B2
9817109	Saboo	Nov 2017	B2
9837760	Karagozler et al.	Dec 2017	B2
9848780	DeBusschere et al.	Dec 2017	B1
9921660	Poupyrev	Mar 2018	B2
9933908	Poupyrev	Apr 2018	B2
9947080	Nguyen et al.	Apr 2018	B2
9971414	Gollakota et al.	May 2018	B2
9971415	Poupyrev et al.	May 2018	B2
9983747	Poupyrev	May 2018	B2
9994233	Diaz-Jimenez et al.	Jun 2018	B2
10016162	Rogers et al.	Jul 2018	B1
10034630	Lee et al.	Jul 2018	B2
10073590	Dascola et al.	Sep 2018	B2
10080528	DeBusschere et al.	Sep 2018	B2
10082950	Lapp	Sep 2018	B2
10088908	Poupyrev et al.	Oct 2018	B1
10139916	Poupyrev	Nov 2018	B2
10155274	Robinson et al.	Dec 2018	B2
10175781	Karagozler et al.	Jan 2019	B2
10203763	Poupyrev et al.	Feb 2019	B1
10222469	Gillian et al.	Mar 2019	B1
10241581	Lien et al.	Mar 2019	B2
20010035836	Miceli et al.	Nov 2001	A1
20020009972	Amento et al.	Jan 2002	A1
20020080156	Abbott et al.	Jun 2002	A1
20020170897	Hall	Nov 2002	A1
20030005030	Sutton et al.	Jan 2003	A1
20030071750	Benitz	Apr 2003	A1
20030093000	Nishio et al.	May 2003	A1
20030100228	Bungo et al.	May 2003	A1
20030119391	Swallow et al.	Jun 2003	A1
20030122677	Kail	Jul 2003	A1
20040009729	Hill et al.	Jan 2004	A1
20040102693	Jenkins	May 2004	A1
20040249250	McGee et al.	Dec 2004	A1
20040259391	Jung et al.	Dec 2004	A1
20050069695	Jung et al.	Mar 2005	A1
20050128124	Greneker et al.	Jun 2005	A1
20050148876	Endoh et al.	Jul 2005	A1
20050231419	Mitchell	Oct 2005	A1
20060035554	Glaser et al.	Feb 2006	A1
20060040739	Wells	Feb 2006	A1
20060047386	Kanevsky et al.	Mar 2006	A1
20060061504	Leach, Jr. et al.	Mar 2006	A1
20060125803	Westerman et al.	Jun 2006	A1
20060136997	Telek et al.	Jun 2006	A1
20060139162	Flynn	Jun 2006	A1
20060139314	Bell	Jun 2006	A1
20060148351	Tao et al.	Jul 2006	A1
20060157734	Onodero et al.	Jul 2006	A1
20060166620	Sorensen	Jul 2006	A1
20060170584	Romero et al.	Aug 2006	A1
20060209021	Yoo et al.	Sep 2006	A1
20060258205	Locher et al.	Nov 2006	A1
20070024488	Zemany et al.	Feb 2007	A1
20070026695	Lee et al.	Feb 2007	A1
20070027369	Pagnacco et al.	Feb 2007	A1
20070118043	Oliver et al.	May 2007	A1
20070161921	Rausch	Jul 2007	A1
20070164896	Suzuki et al.	Jul 2007	A1
20070176821	Flom et al.	Aug 2007	A1
20070192647	Glaser	Aug 2007	A1
20070197115	Eves et al.	Aug 2007	A1
20070197878	Shklarski	Aug 2007	A1
20070210074	Maurer et al.	Sep 2007	A1
20070237423	Tico et al.	Oct 2007	A1
20080001735	Tran	Jan 2008	A1
20080002027	Kondo	Jan 2008	A1
20080015422	Wessel	Jan 2008	A1
20080024438	Collins et al.	Jan 2008	A1
20080039731	McCombie et al.	Feb 2008	A1
20080059578	Albertson et al.	Mar 2008	A1
20080065291	Breed	Mar 2008	A1
20080134102	Movold et al.	Jun 2008	A1
20080136775	Conant	Jun 2008	A1
20080168396	Matas et al.	Jul 2008	A1
20080194204	Duet et al.	Aug 2008	A1
20080194975	MacQuarrie et al.	Aug 2008	A1
20080211766	Westerman et al.	Sep 2008	A1
20080233822	Swallow et al.	Sep 2008	A1
20080278450	Lashina	Nov 2008	A1
20080282665	Speleers	Nov 2008	A1
20080291158	Park et al.	Nov 2008	A1
20080303800	Elwell	Dec 2008	A1
20080316085	Rofougaran	Dec 2008	A1
20080320419	Matas et al.	Dec 2008	A1
20090018408	Ouchi et al.	Jan 2009	A1
20090018428	Dias et al.	Jan 2009	A1
20090033585	Lang	Feb 2009	A1
20090053950	Surve	Feb 2009	A1
20090056300	Chung et al.	Mar 2009	A1
20090058820	Hinckley	Mar 2009	A1
20090113298	Jung et al.	Apr 2009	A1
20090115617	Sano et al.	May 2009	A1
20090118648	Kandori et al.	May 2009	A1
20090149036	Lee et al.	Jun 2009	A1
20090177068	Stivoric et al.	Jul 2009	A1
20090203244	Toonder et al.	Aug 2009	A1
20090226043	Angell et al.	Sep 2009	A1
20090253585	Diatchenko et al.	Oct 2009	A1
20090270690	Roos et al.	Oct 2009	A1
20090278915	Kramer et al.	Nov 2009	A1
20090288762	Wolfel	Nov 2009	A1
20090295712	Ritzau	Dec 2009	A1
20090319181	Khosravy et al.	Dec 2009	A1
20100045513	Pett et al.	Feb 2010	A1
20100050133	Nishihara et al.	Feb 2010	A1
20100053151	Marti et al.	Mar 2010	A1
20100060570	Underkoffler et al.	Mar 2010	A1
20100065320	Urano	Mar 2010	A1
20100069730	Bergstrom et al.	Mar 2010	A1
20100071205	Graumann et al.	Mar 2010	A1
20100094141	Puswella	Apr 2010	A1
20100109938	Oswald et al.	May 2010	A1
20100152600	Droitcour et al.	Jun 2010	A1
20100179820	Harrison et al.	Jul 2010	A1
20100201586	Michalk	Aug 2010	A1
20100204550	Heneghan et al.	Aug 2010	A1
20100205667	Anderson et al.	Aug 2010	A1
20100208035	Pinault et al.	Aug 2010	A1
20100225562	Smith	Sep 2010	A1
20100234094	Gagner et al.	Sep 2010	A1
20100241009	Petkie	Sep 2010	A1
20100002912	Solinsky	Oct 2010	A1
20100281438	Latta et al.	Nov 2010	A1
20100292549	Schuler	Nov 2010	A1
20100306713	Geisner et al.	Dec 2010	A1
20100313414	Sheats	Dec 2010	A1
20100324384	Moon et al.	Dec 2010	A1
20100325770	Chung et al.	Dec 2010	A1
20110003664	Richard	Jan 2011	A1
20110010014	Oexman et al.	Jan 2011	A1
20110018795	Jang	Jan 2011	A1
20110029038	Hyde et al.	Feb 2011	A1
20110073353	Lee et al.	Mar 2011	A1
20110083111	Forutanpour et al.	Apr 2011	A1
20110093820	Zhang et al.	Apr 2011	A1
20110118564	Sankai	May 2011	A1
20110119640	Berkes et al.	May 2011	A1
20110166940	Bangera	Jul 2011	A1
20110181509	Rautiainen et al.	Jul 2011	A1
20110181510	Hakala	Jul 2011	A1
20110193939	Vassigh et al.	Aug 2011	A1
20110197263	Stinson, III	Aug 2011	A1
20110202404	van der Riet	Aug 2011	A1
20110213218	Weiner et al.	Sep 2011	A1
20110221666	Newton et al.	Sep 2011	A1
20110234492	Ajmera	Sep 2011	A1
20110239118	Yamaoka et al.	Sep 2011	A1
20110245688	Arora et al.	Oct 2011	A1
20110279303	Smith, Jr.	Nov 2011	A1
20110286585	Hodge	Nov 2011	A1
20110303341	Meiss et al.	Dec 2011	A1
20110307842	Chiang et al.	Dec 2011	A1
20110316888	Sachs et al.	Dec 2011	A1
20110318985	McDermid	Dec 2011	A1
20120001875	Li et al.	Jan 2012	A1
20120019168	Noda et al.	Jan 2012	A1
20120029369	Icove et al.	Feb 2012	A1
20120047468	Santos et al.	Feb 2012	A1
20120068876	Bangera	Mar 2012	A1
20120092284	Rofougaran et al.	Apr 2012	A1
20120123232	Najarian et al.	May 2012	A1
20120127082	Kushler et al.	May 2012	A1
20120144934	Russell et al.	Jun 2012	A1
20120150493	Casey et al.	Jun 2012	A1
20120154313	Au et al.	Jun 2012	A1
20120156926	Kato et al.	Jun 2012	A1
20120174299	Balzano	Jul 2012	A1
20120174736	Wang et al.	Jul 2012	A1
20120193801	Gross et al.	Aug 2012	A1
20120220835	Chung	Aug 2012	A1
20120248093	Ulrich et al.	Oct 2012	A1
20120254810	Heck et al.	Oct 2012	A1
20120268416	Pirogov et al.	Oct 2012	A1
20120280900	Wang	Nov 2012	A1
20120298748	Factor et al.	Nov 2012	A1
20120310665	Xu et al.	Dec 2012	A1
20130016070	Starner et al.	Jan 2013	A1
20130027218	Schwarz et al.	Jan 2013	A1
20130035563	Angellides	Feb 2013	A1
20130046544	Kay et al.	Feb 2013	A1
20130053653	Cuddihy et al.	Feb 2013	A1
20130078624	Holmes et al.	Mar 2013	A1
20130082922	Miller	Apr 2013	A1
20130083173	Geisner et al.	Apr 2013	A1
20130086533	Stienstra	Apr 2013	A1
20130096439	Lee et al.	Apr 2013	A1
20130102217	Jeon	Apr 2013	A1
20130104084	Mlyniec et al.	Apr 2013	A1
20130113647	Sentelle et al.	May 2013	A1
20130113830	Suzuki	May 2013	A1
20130117377	Miller	May 2013	A1
20130132931	Bruns et al.	May 2013	A1
20130147833	Aubauer et al.	Jun 2013	A1
20130150735	Cheng	Jun 2013	A1
20130161078	Li	Jun 2013	A1
20130169471	Lynch	Jul 2013	A1
20130176161	Derham et al.	Jul 2013	A1
20130194173	Zhu et al.	Aug 2013	A1
20130195330	Kim et al.	Aug 2013	A1
20130196716	Muhammad	Aug 2013	A1
20130207962	Oberdorfer et al.	Aug 2013	A1
20130229508	Li et al.	Sep 2013	A1
20130241765	Kozma et al.	Sep 2013	A1
20130245986	Grokop et al.	Sep 2013	A1
20130253029	Jain et al.	Sep 2013	A1
20130260630	Ito et al.	Oct 2013	A1
20130278499	Anderson	Oct 2013	A1
20130278501	Bulzacki	Oct 2013	A1
20130283203	Batraski et al.	Oct 2013	A1
20130322729	Mestha et al.	Dec 2013	A1
20130332438	Li et al.	Dec 2013	A1
20130345569	Mestha et al.	Dec 2013	A1
20140005809	Frei et al.	Jan 2014	A1
20140022108	Alberth et al.	Jan 2014	A1
20140028539	Newham	Jan 2014	A1
20140049487	Konertz et al.	Feb 2014	A1
20140050354	Heim et al.	Feb 2014	A1
20140051941	Messerschmidt	Feb 2014	A1
20140070957	Longinotti-Buitoni et al.	Mar 2014	A1
20140072190	Wu et al.	Mar 2014	A1
20140073486	Ahmed et al.	Mar 2014	A1
20140073969	Zou et al.	Mar 2014	A1
20140081100	Muhsin et al.	Mar 2014	A1
20140095480	Marantz et al.	Apr 2014	A1
20140097979	Nohara et al.	Apr 2014	A1
20140121540	Raskin	May 2014	A1
20140135631	Brumback et al.	May 2014	A1
20140139422	Mistry et al.	May 2014	A1
20140139616	Pinter et al.	May 2014	A1
20140143678	Mistry et al.	May 2014	A1
20140149859	Van Dyken et al.	May 2014	A1
20140184496	Gribetz et al.	Jul 2014	A1
20140184499	Kim	Jul 2014	A1
20140191939	Penn et al.	Jul 2014	A1
20140200416	Kashef et al.	Jul 2014	A1
20140201690	Holz	Jul 2014	A1
20140208275	Mongia et al.	Jul 2014	A1
20140215389	Walsh et al.	Jul 2014	A1
20140239065	Zhou et al.	Aug 2014	A1
20140244277	Krishna Rao et al.	Aug 2014	A1
20140246415	Wittkowski	Sep 2014	A1
20140247212	Kim	Sep 2014	A1
20140250515	Jakobsson	Sep 2014	A1
20140253431	Gossweiler et al.	Sep 2014	A1
20140253709	Bresch et al.	Sep 2014	A1
20140262478	Harris et al.	Sep 2014	A1
20140275854	Venkatraman et al.	Sep 2014	A1
20140280295	Kurochikin et al.	Sep 2014	A1
20140281975	Anderson	Sep 2014	A1
20140282877	Mahaffey et al.	Sep 2014	A1
20140297006	Sadhu	Oct 2014	A1
20140298266	Lapp	Oct 2014	A1
20140300506	Alton et al.	Oct 2014	A1
20140306936	Dahl et al.	Oct 2014	A1
20140309855	Tran	Oct 2014	A1
20140316261	Lux et al.	Oct 2014	A1
20140318699	Longinotti-Buitoni et al.	Oct 2014	A1
20140324888	Xie	Oct 2014	A1
20140329567	Chan et al.	Nov 2014	A1
20140333467	Inomata	Nov 2014	A1
20140343392	Yang	Nov 2014	A1
20140347295	Kim et al.	Nov 2014	A1
20140357369	Callens et al.	Dec 2014	A1
20140368378	Crain et al.	Dec 2014	A1
20140368441	Touloumtzis	Dec 2014	A1
20140376788	Xu et al.	Dec 2014	A1
20150002391	Chen	Jan 2015	A1
20150009096	Lee et al.	Jan 2015	A1
20150026815	Barrett	Jan 2015	A1
20150029050	Driscoll et al.	Jan 2015	A1
20150030256	Brady et al.	Jan 2015	A1
20150040040	Balan et al.	Feb 2015	A1
20150046183	Cireddu	Feb 2015	A1
20150062033	Ishihara	Mar 2015	A1
20150068069	Tran et al.	Mar 2015	A1
20150077282	Mohamadi	Mar 2015	A1
20150085060	Fish et al.	Mar 2015	A1
20150091820	Rosenberg et al.	Apr 2015	A1
20150091858	Rosenberg et al.	Apr 2015	A1
20150091859	Rosenberg et al.	Apr 2015	A1
20150091903	Costello et al.	Apr 2015	A1
20150095987	Potash et al.	Apr 2015	A1
20150099941	Tran	Apr 2015	A1
20150100328	Kress et al.	Apr 2015	A1
20150109164	Takaki	Apr 2015	A1
20150112606	He et al.	Apr 2015	A1
20150133017	Liao et al.	May 2015	A1
20150143601	Longinotti-Buitoni et al.	May 2015	A1
20150145805	Liu	May 2015	A1
20150162729	Reversat et al.	Jun 2015	A1
20150177866	Hwang et al.	Jun 2015	A1
20150185314	Corcos et al.	Jul 2015	A1
20150199045	Robucci et al.	Jul 2015	A1
20150205358	Lyren	Jul 2015	A1
20150223733	Al-Alusi	Aug 2015	A1
20150226004	Thompson	Aug 2015	A1
20150229885	Offenhaeuser	Aug 2015	A1
20150256763	Niemi	Sep 2015	A1
20150261320	Leto	Sep 2015	A1
20150268027	Gerdes	Sep 2015	A1
20150268799	Starner et al.	Sep 2015	A1
20150277569	Sprenger	Oct 2015	A1
20150280102	Tajitsu et al.	Oct 2015	A1
20150285906	Hooper et al.	Oct 2015	A1
20150287187	Redtel	Oct 2015	A1
20150301167	Sentelle et al.	Oct 2015	A1
20150312041	Choi	Oct 2015	A1
20150314780	Stenneth et al.	Nov 2015	A1
20150317518	Fujimaki et al.	Nov 2015	A1
20150323993	Levesque et al.	Nov 2015	A1
20150332075	Burch	Nov 2015	A1
20150341550	Lay	Nov 2015	A1
20150346820	Poupyrev et al.	Dec 2015	A1
20150350902	Baxley et al.	Dec 2015	A1
20150351703	Phillips et al.	Dec 2015	A1
20150375339	Sterling et al.	Dec 2015	A1
20160018948	Parvarandeh et al.	Jan 2016	A1
20160026253	Bradski et al.	Jan 2016	A1
20160038083	Ding et al.	Feb 2016	A1
20160041617	Poupyrev	Feb 2016	A1
20160041618	Poupyrev	Feb 2016	A1
20160042169	Polehn	Feb 2016	A1
20160048235	Poupyrev	Feb 2016	A1
20160048236	Poupyrev	Feb 2016	A1
20160048672	Lux et al.	Feb 2016	A1
20160054792	Poupyrev	Feb 2016	A1
20160054803	Poupyrev	Feb 2016	A1
20160054804	Gollakata	Feb 2016	A1
20160055201	Poupyrev et al.	Feb 2016	A1
20160090839	Stolarcyzk	Mar 2016	A1
20160098089	Poupyrev	Apr 2016	A1
20160100166	Dragne et al.	Apr 2016	A1
20160103500	Hussey et al.	Apr 2016	A1
20160106328	Mestha et al.	Apr 2016	A1
20160131741	Park	May 2016	A1
20160140872	Palmer et al.	May 2016	A1
20160145776	Roh	May 2016	A1
20160170491	Jung	Jun 2016	A1
20160171293	Li et al.	Jun 2016	A1
20160186366	McMaster	Jun 2016	A1
20160206244	Rogers	Jul 2016	A1
20160213331	Gil et al.	Jul 2016	A1
20160216825	Forutanpour	Jul 2016	A1
20160220152	Meriheina et al.	Aug 2016	A1
20160249698	Berzowska et al.	Sep 2016	A1
20160252607	Saboo et al.	Sep 2016	A1
20160252965	Mandella et al.	Sep 2016	A1
20160253044	Katz	Sep 2016	A1
20160259037	Molchanov et al.	Sep 2016	A1
20160262685	Wagner et al.	Sep 2016	A1
20160282988	Poupyrev	Sep 2016	A1
20160283101	Schwesig et al.	Sep 2016	A1
20160284436	Fukuhara et al.	Sep 2016	A1
20160287172	Morris et al.	Oct 2016	A1
20160299526	Inagaki et al.	Oct 2016	A1
20160320852	Poupyrev	Nov 2016	A1
20160320853	Lien et al.	Nov 2016	A1
20160320854	Lien et al.	Nov 2016	A1
20160321428	Rogers	Nov 2016	A1
20160338599	DeBusschere et al.	Nov 2016	A1
20160345638	Robinson et al.	Dec 2016	A1
20160349790	Connor	Dec 2016	A1
20160349845	Poupyrev et al.	Dec 2016	A1
20160377712	Wu et al.	Dec 2016	A1
20170029985	Tajitsu et al.	Feb 2017	A1
20170052618	Lee et al.	Feb 2017	A1
20170060254	Molchanov et al.	Mar 2017	A1
20170060298	Hwang et al.	Mar 2017	A1
20170075481	Chou et al.	Mar 2017	A1
20170075496	Rosenberg et al.	Mar 2017	A1
20170097413	Gillian et al.	Apr 2017	A1
20170097684	Lien	Apr 2017	A1
20170115777	Poupyrev	Apr 2017	A1
20170124407	Micks et al.	May 2017	A1
20170125940	Karagozler et al.	May 2017	A1
20170192523	Poupyrev	Jul 2017	A1
20170192629	Takada et al.	Jul 2017	A1
20170196513	Longinotti-Buitoni et al.	Jul 2017	A1
20170232538	Robinson et al.	Aug 2017	A1
20170233903	Jeon	Aug 2017	A1
20170249033	Podhajny et al.	Aug 2017	A1
20170322633	Shen et al.	Nov 2017	A1
20170325337	Karagozler et al.	Nov 2017	A1
20170325518	Poupyrev et al.	Nov 2017	A1
20170329412	Schwesig et al.	Nov 2017	A1
20170329425	Karagozler et al.	Nov 2017	A1
20180000354	DeBusschere et al.	Jan 2018	A1
20180000355	DeBusschere et al.	Jan 2018	A1
20180004301	Poupyrev	Jan 2018	A1
20180005766	Fairbanks et al.	Jan 2018	A1
20180046258	Poupyrev	Feb 2018	A1
20180095541	Gribetz et al.	Apr 2018	A1
20180106897	Shouldice et al.	Apr 2018	A1
20180113032	Dickey et al.	Apr 2018	A1
20180157330	Gu et al.	Jun 2018	A1
20180160943	Fyfe et al.	Jun 2018	A1
20180177464	DeBusschere et al.	Jun 2018	A1
20180196527	Poupyrev et al.	Jul 2018	A1
20180256106	Rogers et al.	Sep 2018	A1
20180296163	DeBusschere et al.	Oct 2018	A1
20180321841	Lapp	Nov 2018	A1
20190033981	Poupyrev	Jan 2019	A1

Foreign Referenced Citations (83)

Number	Date	Country
1462382	Dec 2003	CN
101751126	Jun 2010	CN
102414641	Apr 2012	CN
102782612	Nov 2012	CN
102893327	Jan 2013	CN
202887794	Apr 2013	CN
103076911	May 2013	CN
103502911	Jan 2014	CN
102660988	Mar 2014	CN
104035552	Sep 2014	CN
103355860	Jan 2016	CN
102011075725	Nov 2012	DE
102013201359	Jul 2014	DE
0161895	Nov 1985	EP
1785744	May 2007	EP
1815788	Aug 2007	EP
2417908	Feb 2012	EP
2637081	Sep 2013	EP
2770408	Aug 2014	EP
2953007	Dec 2015	EP
3201726	Aug 2017	EP
3017722	Aug 2015	FR
2070469	Sep 1981	GB
2443208	Apr 2008	GB
113860	Apr 1999	JP
11168268	Jun 1999	JP
2003280049	Oct 2003	JP
2006234716	Sep 2006	JP
2007011873	Jan 2007	JP
2007132768	May 2007	JP
2008287714	Nov 2008	JP
2009037434	Feb 2009	JP
2011102457	May 2011	JP
201218583	Sep 2012	JP
2012198916	Oct 2012	JP
2013196047	Sep 2013	JP
2014532332	Dec 2014	JP
1020080102516	Nov 2008	KR
100987650	Oct 2010	KR
1020140055985	May 2014	KR
101914850	Oct 2018	KR
201425974	Jul 2014	TW
9001895	Mar 1990	WO
WO-0130123	Apr 2001	WO
WO-2001027855	Apr 2001	WO
WO-0175778	Oct 2001	WO
WO-2002082999	Oct 2002	WO
2004004557	Jan 2004	WO
WO-2005033387	Apr 2005	WO
2007125298	Nov 2007	WO
WO-2008061385	May 2008	WO
WO-2009032073	Mar 2009	WO
2009083467	Jul 2009	WO
WO-2010032173	Mar 2010	WO
2010101697	Sep 2010	WO
WO-2012026013	Mar 2012	WO
2012064847	May 2012	WO
WO-2012152476	Nov 2012	WO
WO-2013082806	Jun 2013	WO
WO-2013084108	Jun 2013	WO
2013192166	Dec 2013	WO
WO-2013186696	Dec 2013	WO
WO-2013191657	Dec 2013	WO
WO-2014019085	Feb 2014	WO
2014085369	Jun 2014	WO
WO-2014116968	Jul 2014	WO
2014124520	Aug 2014	WO
WO-2014136027	Sep 2014	WO
WO-2014138280	Sep 2014	WO
WO-2014160893	Oct 2014	WO
WO-2014165476	Oct 2014	WO
WO-2014204323	Dec 2014	WO
WO-2015017931	Feb 2015	WO
WO-2015022671	Feb 2015	WO
2016053624	Apr 2016	WO
2016118534	Jul 2016	WO
2016176471	Nov 2016	WO
2016178797	Nov 2016	WO
2017019299	Feb 2017	WO
2017062566	Apr 2017	WO
2017200571	Nov 2017	WO
20170200949	Nov 2017	WO
2018106306	Jun 2018	WO

Non-Patent Literature Citations (282)

Entry
“Corrected Notice of Allowance”, U.S. Appl. No. 15/362,359, dated Sep. 17, 2018, 10 pages.
“Final Office Action”, U.S. Appl. No. 14/504,121, dated Jul. 9, 2018, 23 pages.
“Final Office Action”, U.S. Appl. No. 15/166,198, dated Sep. 27, 2018, 33 pages.
“Foreign Office Action”, Japanese Application No. 2018-501256, dated Jul. 24, 2018, 11 pages.
“Non-Final Office Action”, U.S. Appl. No. 15/287,253, dated Sep. 7, 2018, 20 pages.
“Non-Final Office Action”, U.S. Appl. No. 14/504,139, dated Oct. 5, 2018, 16 pages.
“Non-Final Office Action”, U.S. Appl. No. 15/286,512, dated Jul. 19, 2018, 15 pages.
“Non-Final Office Action”, U.S. Appl. No. 15/142,829, dated Aug. 16, 2018, 15 pages.
“Notice of Allowance”, U.S. Appl. No. 15/362,359, dated Aug. 3, 2018, 8 pages.
“Notice of Allowance”, U.S. Appl. No. 14/874,955, dated Oct. 4, 2018, 8 pages.
“Notice of Allowance”, U.S. Appl. No. 15/142,619, dated Aug. 13, 2018, 9 pages.
“Notice of Allowance”, U.S. Appl. No. 15/595,649, dated Sep. 14, 2018, 8 pages.
“Notice of Allowance”, U.S. Appl. No. 15/586,174, dated Sep. 24, 2018, 5 pages.
“Pre-Interview Communication”, U.S. Appl. No. 15/286,495, dated Sep. 10, 2018, 4 pages.
“Pre-Interview Communication”, U.S. Appl. No. 15/287,359, dated Jul. 24, 2018, 2 pages.
“Restriction Requirement”, U.S. Appl. No. 15/286,537, dated Aug. 27, 2018, 8 pages.
“Corrected Notice of Allowance”, U.S. Appl. No. 14/312,486, dated Jan. 23, 2017, 4 pages.
“Corrected Notice of Allowance”, U.S. Appl. No. 14/504,061, dated Dec. 27, 2016, 2 pages.
“Corrected Notice of Allowance”, U.S. Appl. No. 14/582,896, dated Feb. 6, 2017, 2 pages.
“Corrected Notice of Allowance”, U.S. Appl. No. 14/582,896, dated Dec. 19, 2016, 2 pages.
“Non-Final Office Action”, U.S. Appl. No. 14/504,121, dated Jan. 9, 2017, 13 pages.
“Non-Final Office Action”, U.S. Appl. No. 14/504,139, dated Jan. 27, 2017, 10 pages.
“Non-Final Office Action”, U.S. Appl. No. 14/959,799, dated Jan. 27, 2017, 10 pages.
“Notice of Allowance”, U.S. Appl. No. 14/930,220, dated Feb. 2, 2017, 8 pages.
“Pre-Interview Communication”, U.S. Appl. No. 14/494,863, dated Jan. 27, 2017, 5 pages.
“Pre-Interview Communication”, U.S. Appl. No. 14/959,901, dated Feb. 10, 2017, 3 pages.
“Corrected Notice of Allowance”, U.S. Appl. No. 14/582,896, dated Feb. 23, 2017, 2 pages.
“International Preliminary Report on Patentability”, Application No. PCT/US2015/043963, dated Feb. 16, 2017, 12 pages.
“International Preliminary Report on Patentability”, Application No. PCT/US2015/030388, dated Dec. 15, 2016, 12 pages.
“International Preliminary Report on Patentability”, Application No. PCT/US2015/043949, dated Feb. 16, 2017, 13 pages.
“International Preliminary Report on Patentability”, Application No. PCT/US2015/044774, dated Mar. 2, 2017, 8 pages.
“International Search Report and Written Opinion”, Application No. PCT/US2016/062082, dated Feb. 23, 2017, 12 pages.
“International Search Report and Written Opinion”, Application No. PCT/US2016/055671, dated Dec. 1, 2016, 14 pages.
“Non-Final Office Action”, U.S. Appl. No. 14/513,875, dated Feb. 21, 2017, 9 pages.
“Non-Final Office Action”, U.S. Appl. No. 14/874,955, dated Feb. 27, 2017, 8 pages.
“Non-Final Office Action”, U.S. Appl. No. 15/398,147, dated Mar. 9, 2017, 10 pages.
“Pre-Interview Communication”, U.S. Appl. No. 14/959,730, dated Feb. 15, 2017, 3 pages.
“Final Office Action”, U.S. Appl. No. 15/142,619, dated Feb. 8, 2018, 15 pages.
“Final Office Action”, U.S. Appl. No. 15/093,533, dated Mar. 21, 2018, 19 pages.
“First Action Interview Office Action”, U.S. Appl. No. 15/286,152, dated Mar. 1, 2018, 5 pages.
“Foreign Office Action”, Chinese Application No. 201721290290.3, dated Mar. 9, 2018, 2 pages.
“Non-Final Office Action”, U.S. Appl. No. 15/267,181, dated Feb. 8, 2018, 29 pages.
“Non-Final Office Action”, U.S. Appl. No. 14/874,955, dated Feb. 8, 2018, 7 pages.
“Notice of Allowance”, U.S. Appl. No. 14/959,730, dated Feb. 22, 2018, 8 pages.
“Pre-Interview Communication”, U.S. Appl. No. 15/166,198, dated Mar. 8, 2018, 8 pages.
“Pre-Interview First Office Action”, U.S. Appl. No. 15/286,152, dated Feb. 8, 2018, 4 pages.
“Cardiio”, Retrieved from: <http://www.cardiio.com/> Apr. 15, 2015 App Information Retrieved From: <https://itunes.apple.com/us/app/cardiio-touchless-camera-pulse/id542891434?Is=1&mt=8> Apr. 15, 2015, Feb. 24, 2015, 6 pages.
“Extended European Search Report”, EP Application No. 15170577.9, dated Nov. 5, 2015, 12 pages.
“Final Office Action”, U.S. Appl. No. 14/312,486, dated Jun. 3, 2016, 32 pages.
“Final Office Action”, U.S. Appl. No. 14/504,038, dated Sep. 27, 2016, 23 pages.
“Final Office Action”, U.S. Appl. No. 14/504,061, dated Mar. 9, 2016, 10 pages.
“Frogpad Introduces Wearable Fabric Keyboard with Bluetooth Technology”, Retrieved From: <http://www.geekzone.co.nz/content.asp?contentid=3898> Mar. 16, 2015, Jan. 7, 2005, 2 pages.
“International Search Report and Written Opinion”, Application No. PCT/US2015/044774, dated Nov. 3, 2015, 12 pages.
“International Search Report and Written Opinion”, Application No. PCT/US2016/024267, dated Jun. 20, 2016, 13 pages.
“International Search Report and Written Opinion”, Application No. PCT/US2016/024273, dated Jun. 20, 2016, 13 pages.
“International Search Report and Written Opinion”, Application No. PCT/US2016/032307, dated Aug. 25, 2016, 13 pages.
“International Search Report and Written Opinion”, Application No. PCT/US2016/029820, dated Jul. 15, 2016, 14 pages.
“International Search Report and Written Opinion”, Application No. PCT/US2016/030177, dated Aug. 2, 2016, 15 pages.
“International Search Report and Written Opinion”, Application No. PCT/US2015/043963, dated Nov. 24, 2015, 16 pages.
“International Search Report and Written Opinion”, Application No. PCT/US2015/050903, dated Feb. 19, 2016, 18 pages.
“International Search Report and Written Opinion”, Application No. PCT/US2016/030115, dated Aug. 8, 2016, 18 pages.
“International Search Report and Written Opinion”, Application No. PCT/US2015/043949, dated Dec. 1, 2015, 18 pages.
“Non-Final Office Action”, U.S. Appl. No. 14/312,486, dated Oct. 23, 2015, 25 pages.
“Non-Final Office Action”, U.S. Appl. No. 14/504,038, dated Feb. 26, 2016, 22 pages.
“Non-Final Office Action”, U.S. Appl. No. 14/504,061, dated Nov. 4, 2015, 8 pages.
“Non-Final Office Action”, U.S. Appl. No. 14/582,896, dated Jun. 29, 2016, 9 pages.
“Non-Final Office Action”, U.S. Appl. No. 14/666,155, dated Aug. 24, 2016, 9 pages.
“Non-Final Office Action”, U.S. Appl. No. 14/681,625, dated Aug. 12, 2016, 9 pages.
“Non-Final Office Action”, U.S. Appl. No. 14/930,220, dated Sep. 14, 2016, 15 pages.
“Notice of Allowance”, U.S. Appl. No. 14/312,486, dated Oct. 7, 2016, 15 pages.
“Notice of Allowance”, U.S. Appl. No. 14/504,061, dated Sep. 12, 2016, 7 pages.
“Philips Vital Signs Camera”, Retrieved From: <http://www.vitalsignscamera.com/> Apr. 15, 2015, Jul. 17, 2013, 2 pages.
“Restriction Requirement”, U.S. Appl. No. 14/666,155, dated Jul. 22, 2016, 5 pages.
“The Instant Blood Pressure app estimates blood pressure with your smartphone and our algorithm”, Retrieved at: http://www.instantbloodpressure.com/—on Jun. 23, 2016, 6 pages.
Arbabian,“A 94GHz mm-Wave to Baseband Pulsed-Radar for Imaging and Gesture Recognition”, 2012 IEEE, 2012 Symposium on VLSI Circuits Digest of Technical Papers, 2012, 2 pages.
Balakrishnan,“Detecting Pulse from Head Motions in Video”, In Proceedings: CVPR '13 Proceedings of the 2013 IEEE Conference on Computer Vision and Pattern Recognition Available at: <http://people.csail.mitedu/mrub/vidmag/papers/Balakrishnan_Detecting_Pulse_from_2013_CVPR_paper.pdf>, Jun. 23, 2013, 8 pages.
Couderc,“Detection of Atrial Fibrillation using Contactless Facial Video Monitoring”, In Proceedings: Heart Rhythm Society, vol. 12, Issue 1 Available at: <http://www.heartrhythmjournal.com/article/S1547-5271(14)00924-2/pdf>, Jan. 2015, 7 pages.
Espina,“Wireless Body Sensor Network for Continuous Cuff-less Blood Pressure Monitoring”, International Summer School on Medical Devices and Biosensors, 2006, Sep. 2006, 5 pages.
Godana,“Human Movement Characterization in Indoor Environment using GNU Radio Based Radar”, Retrieved at: http://repository.tudelft.nl/islandora/object/uuid:414e1868-dd00-4113-9989-4c213f1f7094?collection=education, Nov. 30, 2009, 100 pages.
He,“A Continuous, Wearable, and Wireless Heart Monitor Using Head Ballistocardiogram (BCG) and Head Electrocardiogram (ECG) with a Nanowatt ECG Heartbeat Detection Circuit”, In Proceedings: Thesis, Department of Electrical Engineering and Computer Science, Massachusetts Institute of Technology Available at: <http://dspace.mitedu/handle/1721.1/79221>, Feb. 2013, 137 pages.
Holleis,“Evaluating Capacitive Touch Input on Clothes”, Proceedings of the 10th International Conference on Human Computer Interaction, Jan. 1, 2008, 10 pages.
Nakajima,“Development of Real-Time Image Sequence Analysis for Evaluating Posture Change and Respiratory Rate of a Subject in Bed”, In Proceedings: Physiological Measurement, vol. 22, No. 3 Retrieved From: <http://iopscience.iop.org/0967-3334/22/3/401/pdf/0967-3334_22_3_401.pdf> Feb. 27, 2015, Aug. 2001, 8 pages.
Patel,“Applications of Electrically Conductive Yarns in Technical Textiles”, International Conference on Power System Technology (POWECON), Oct. 30, 2012, 6 pages.
Poh,“A Medical Mirror for Non-Contact Health Monitoring”, In Proceedings: ACM SIGGRAPH Emerging Technologies Available at: <http://affect.media.mit.edu/pdfs/11.Poh-etal-SIGGRAPH.pdf>, 2011, 1 page.
Poh,“Non-contact, Automated Cardiac Pulse Measurements Using Video Imaging and Blind Source Separation.”, In Proceedings: Optics Express, vol. 18, No. 10 Available at: <http://www.opticsinfobase.org/view_article.cfm?gotourl=http%3A%2F%2Fwww%2Eopticsinfobase%2Eorg%2FDirectPDFAccess%2F77B04D55%2DBC95%2D6937%2D5BAC49A426378C02%5F199381%2Foe%2D18%2D10%2D10762%2EP, May 7, 2010, 13 pages.
Pu,“Whole-Home Gesture Recognition Using Wireless Signals”, MobiCom '13 Proceedings of the 19th annual international conference on Mobile computing & networking, Aug. 27, 2013, 12 pages.
Wang,“Exploiting Spatial Redundancy of Image Sensor for Motion Robust rPPG”, In Proceedings: IEEE Transactions on Biomedical Engineering, vol. 62, Issue 2, Jan. 19, 2015, 11 pages.
Wang,“Micro-Doppler Signatures for Intelligent Human Gait Recognition Using a UWB Impulse Radar”, 2011 IEEE International Symposium on Antennas and Propagation (APSURSI), Jul. 3, 2011, pp. 2103-2106.
Wijesiriwardana,“Capacitive Fibre-Meshed Transducer for Touch & Proximity Sensing Applications”, IEEE Sensors Journal, IEEE Service Center, Oct. 1, 2005, 5 pages.
Zhadobov,“Millimeter-wave Interactions with the Human Body: State of Knowledge and Recent Advances”, International Journal of Microwave and Wireless Technologies, Mar. 1, 2011, 11 pages.
Zhang,“Study of the Structural Design and Capacitance Characteristics of Fabric Sensor”, Advanced Materials Research (vols. 194-196), Feb. 21, 2011, 8 pages.
“Final Office Action”, U.S. Appl. No. 14/959,799, dated Jan. 4, 2018, 17 pages.
“Final Office Action”, U.S. Appl. No. 14/959,730, dated Nov. 22, 2017, 16 pages.
“International Search Report and Written Opinion”, PCT/US2017/047691, dated Nov. 16, 2017, 13.
“International Search Report and Written Opinion”, PCT Application No. PCT/US2017/051663, dated Nov. 29, 2017, 16 pages.
“Non-Final Office Action”, U.S. Appl. No. 14/504,121, dated Jan. 2, 2018, 19 pages.
“Non-Final Office Action”, U.S. Appl. No. 14/959,901, dated Jan. 8, 2018, 21 pages.
“Non-Final Office Action”, U.S. Appl. No. 14/504,139, dated Oct. 18, 2017, 12 pages.
“Non-Final Office Action”, U.S. Appl. No. 15/595,649, dated Oct. 31, 2017, 16 pages.
“Non-Final Office Action”, U.S. Appl. No. 14/862,409, dated Dec. 14, 2017, 17 pages.
“Notice of Allowance”, U.S. Appl. No. 15/403,066, dated Jan. 8, 2018, 18 pages.
“Notice of Allowance”, U.S. Appl. No. 14/874,955, dated Oct. 20, 2017, 7 pages.
“Notice of Allowance”, U.S. Appl. No. 15/398,147, dated Nov. 15, 2017, 8 pages.
“Notice of Publication”, U.S. Appl. No. 15/703,511, dated Jan. 4, 2018, 1 page.
“Restriction Requirement”, U.S. Appl. No. 15/362,359, dated Jan. 8, 2018, 5 pages.
Bondade, et al., “A linear-assisted DC-DC hybrid power converter for envelope tracking RF power amplifiers”, 2014 IEEE Energy Conversion Congress and Exposition (ECCE), IEEE, Sep. 14, 2014, pp. 5769-5773, XP032680873, DOI: 10.1109/ECCE.2014.6954193, Sep. 14, 2014, 5 pages.
Fan, et al., “Wireless Hand Gesture Recognition Based on Continuous-Wave Doppler Radar Sensors”, IEEE Transactions on Microwave Theory and Techniques, Plenum, USA, vol. 64, No. 11, Nov. 1, 2016 (Nov. 1, 2016), pp. 4012-4012, XP011633246, ISSN: 0018-9480, DOI: 10.1109/TMTT.2016.2610427, Nov. 1, 2016, 9 pages.
Lien, et al., “Soli: Ubiquitous Gesture Sensing with Millimeter Wave Radar”, ACM Transactions on Graphics (TOG), ACM, Us, vol. 35, No. 4, Jul. 11, 2016 (Jul. 11, 2016), pp. 1-19, XP058275791, ISSN: 0730-0301, DOI: 10.1145/2897824.2925953, Jul. 11, 2016, 19 pages.
Martinez-Garcia, et al., “Four-quadrant linear-assisted DC/DC voltage regulator”, Analog Integrated Circuits and Signal Processing, Springer New York LLC, US, vol. 88, No. 1, Apr. 23, 2016 (Apr. 23, 2016) , pp. 151-160, XP035898949, ISSN: 0925-1030, DOI: 10.1007/S10470-016-0747-8, Apr. 23, 2016, 10 pages.
Skolnik, “CW and Frequency-Modulated Radar”, In: “Introduction to Radar Systems”, Jan. 1, 1981 (Jan. 1, 1981), McGraw Hill, XP055047545, ISBN: 978-0-07-057909-5 pp. 68-100, p. 95-p. 97, Jan. 1, 1981, 18 pages.
Zheng, et al., “Doppler Bio-Signal Detection Based Time-Domain Hand Gesture Recognition”, 2013 IEEE MTT-S International Microwave Workshop Series on RF and Wireless Technologies for Biomedical and Healthcare Applications (IMWS-BIO), IEEE, Dec. 9, 2013 (Dec. 9, 2013), p. 3, XP032574214, DOI: 10.1109/IMWS-BIO.2013.6756200, Dec. 9, 2013, 3 Pages.
“Combined Search and Examination Report”, GB Application No. 1620892.8, dated Apr. 6, 2017, 5 pages.
“Corrected Notice of Allowance”, U.S. Appl. No. 14/930,220, dated Mar. 20, 2017, 2 pages.
“Corrected Notice of Allowance”, U.S. Appl. No. 14/930,220, dated May 11, 2017, 2 pages.
“Final Office Action”, U.S. Appl. No. 14/518,863, dated May 5, 2017, 18 pages.
“First Action Interview Office Action”, U.S. Appl. No. 14/959,901, dated Apr. 14, 2017, 3 pages.
“International Preliminary Report on Patentability”, Application No. PCT/US2015/050903, dated Apr. 13, 2017, 12 pages.
“International Search Report and Written Opinion”, Application No. PCT/US2016/060399, dated Jan. 30, 2017, 11 pages.
“Non-Final Office Action”, U.S. Appl. No. 14/504,038, dated Mar. 22, 2017, 33 pages.
“Non-Final Office Action”, U.S. Appl. No. 15/403,066, dated May 4, 2017, 31 pages.
“Pre-Interview Communication”, U.S. Appl. No. 15/343,067, dated Apr. 19, 2017, 3 pages.
“Textile Wire Brochure”, Retrieved at: http://www.textile-wire.ch/en/home.html, Aug. 7, 2004, 17 pages.
Stoppa,“Wearable Electronics and Smart Textiles: A Critical Review”, In Proceedings of Sensors, vol. 14, Issue 7, Jul. 7, 2014, pp. 11957-11992.
“Advisory Action”, U.S. Appl. No. 14/504,139, dated Aug. 28, 2017, 3 pages.
“Final Office Action”, U.S. Appl. No. 14/959,901, dated Aug. 25, 2017, 19 pages.
“Final Office Action”, U.S. Appl. No. 15/403,066, dated Oct. 5, 2017, 31 pages.
“Non-Final Office Action”, U.S. Appl. No. 15/093,533, dated Aug. 24, 2017, 18 pages.
“Non-Final Office Action”, U.S. Appl. No. 15/142,619, dated Aug. 25, 2017, 16 pages.
“Non-Final Office Action”, U.S. Appl. No. 14/959,799, dated Sep. 8, 2017, 16 pages.
“Non-Final Office Action”, U.S. Appl. No. 15/398,147, dated Sep. 8, 2017, 7 pages.
“Non-Final Office Action”, U.S. Appl. No. 14/518,863, dated Sep. 29, 2017, 20 pages.
“Non-Final Office Action”, U.S. Appl. No. 15/142,689, dated Oct. 4, 2017, 18 pages.
“Pre-Interview Office Action”, U.S. Appl. No. 14/862,409, dated Sep. 15, 2017, 16 pages.
“Written Opinion”, PCT Application No. PCT/US2016/055671, dated Apr. 13, 2017, 8 pages.
“Written Opinion”, PCT Application No. PCT/US2017/032733, dated Jul. 26, 2017, 5 pages.
“Final Office Action”, U.S. Appl. No. 14/518,863, dated Apr. 5, 2018, 21 pages.
“Final Office Action”, U.S. Appl. No. 14/504,139, dated May 1, 2018, 14 pages.
“Final Office Action”, U.S. Appl. No. 15/595,649, dated May 23, 2018, 13 pages.
“Final Office Action”, U.S. Appl. No. 15/142,689, dated Jun. 1, 2018, 16 pages.
“Final Office Action”, U.S. Appl. No. 14/874,955, dated Jun. 11, 2018, 9 pages.
“Final Office Action”, U.S. Appl. No. 14/959,901, dated Jun. 15, 2018, 21 pages.
“Final Office Action”, U.S. Appl. No. 15/286,152, dated Jun. 26, 2018, 25 pages.
“Final Office Action”, U.S. Appl. No. 15/267,181, dated Jun. 7, 2018, 31 pages.
“First Action Interview Office Action”, U.S. Appl. No. 15/166,198, dated Apr. 25, 2018, 8 pages.
“Foreign Office Action”, European Application No. 16784352.3, dated May 16, 2018, 3 pages.
“Foreign Office Action”, Chinese Application No. 201721290290.3, dated Jun. 6, 2018, 3 pages.
“Non-Final Office Action”, U.S. Appl. No. 15/287,253, dated Apr. 5, 2018, 17 pages.
“Non-Final Office Action”, U.S. Appl. No. 15/586,174, dated Jun. 18, 2018, 7 pages.
“Notice of Allowance”, U.S. Appl. No. 14/862,409, dated Jun. 6, 2018, 7 pages.
“Pre-Interview Communication”, U.S. Appl. No. 15/362,359, dated May 17, 2018, 4 pages.
“Preliminary Report on Patentability”, PCT Application No. PCT/US2016/055671, dated Apr. 10, 2018, 9 pages.
“Written Opinion”, PCT Application No. PCT/US2017/032733, dated Jul. 24, 2017, 5 pages.
“Combined Search and Examination Report”, GB Application No. 1620891.0, dated May 31, 2017, 9 pages.
“Final Office Action”, U.S. Appl. No. 15/398,147, dated Jun. 30, 2017, 11 pages.
“Final Office Action”, U.S. Appl. No. 14/874,955, dated Jun. 30, 2017, 9 pages.
“Final Office Action”, U.S. Appl. No. 14/959,799, dated Jul. 19, 2017, 12 pages.
“Final Office Action”, U.S. Appl. No. 14/504,121, dated Aug. 8, 2017, 16 pages.
“International Search Report and Written Opinion”, Application No. PCT/US2016/063874, dated May 11, 2017, 19 pages.
“Non-Final Office Action”, U.S. Appl. No. 14/862,409, dated Jun. 22, 2017, 15 pages.
“Non-Final Office Action”, U.S. Appl. No. 14/959,730, dated Jun. 23, 2017, 14 pages.
“Notice of Allowance”, U.S. Appl. No. 14/513,875, dated Jun. 6, 2017, 7 pages.
“Notice of Allowance”, U.S. Appl. No. 15/343,067, dated Jul. 27, 2017, 9 pages.
“Notice of Allowance”, U.S. Appl. No. 14/504,038, dated Aug. 7, 2017, 17 pages.
“Notice of Allowance”, U.S. Appl. No. 14/494,863, dated May 30, 2017, 7 pages.
“Corrected Notice of Allowance”, U.S. Appl. No. 14/312,486, dated Oct. 28, 2016, 4 pages.
“International Search Report and Written Opinion”, Application No. PCT/US2016/024289, dated Aug. 25, 2016, 17 pages.
“Non-Final Office Action”, U.S. Appl. No. 14/518,863, dated Oct. 14, 2016, 16 pages.
“Notice of Allowance”, U.S. Appl. No. 14/582,896, dated Nov. 7, 2016, 5 pages.
“Pre-Interview Communication”, U.S. Appl. No. 14/513,875, dated Oct. 21, 2016, 3 pages.
Cheng,“Smart Textiles: From Niche to Mainstream”, IEEE Pervasive Computing, Jul. 2013, pp. 81-84.
Farringdon,“Wearable Sensor Badge & Sensor Jacket for Context Awareness”, Third International Symposium on Wearable Computers, Oct. 1999, 7 pages.
Pu,“Gesture Recognition Using Wireless Signals”, Oct. 2014, pp. 15-18.
Schneegass,“Towards a Garment OS: Supporting Application Development for Smart Garments”, Wearable Computers, ACM, Sep. 2014, 6 pages.
“Final Office Action”, U.S. Appl. No. 15/286,512, dated Dec. 26, 2018, 15 pages.
“International Preliminary Report on Patentability”, PCT Application No. PCT/US2017/032733, dated Nov. 29, 2018, 7 pages.
“Non-Final Office Action”, U.S. Appl. No. 14/959,901, dated Oct. 11, 2018, 22 pages.
“Non-Final Office Action”, U.S. Appl. No. 15/287,308, dated Oct. 15, 2018, 18 pages.
“Non-Final Office Action”, U.S. Appl. No. 15/286,152, dated Oct. 19, 2018, 27 pages.
“Non-Final Office Action”, U.S. Appl. No. 15/286,537, dated Nov. 19, 2018, 18 pages.
“Non-Final Office Action”, U.S. Appl. No. 15/287,155, dated Dec. 10, 2018, 12 pages.
“Notice of Allowance”, U.S. Appl. No. 15/142,689, dated Oct. 30, 2018, 9 pages.
“Notice of Allowance”, U.S. Appl. No. 15/287,200, dated Nov. 6, 2018, 19 pages.
“Written Opinion”, PCT Application No. PCT/US2017/051663, dated Oct. 12, 2018, 8 pages.
Gürbüz, et al., “Detection and Identification of Human Targets in Radar Data”, Proc. SPIE 6567, Signal Processing, Sensor Fusion, and Target Recognition XVI, 656701, May 7, 2007, 12 pages.
“Apple Watch Used Four Sensors to Detect your Pulse”, retrieved from http://www.theverge.com/2014/9/9/6126991 / apple-watch-four-back-sensors-detect-activity on Sep. 23, 2017 in PCT search report for PCT Application No. PCT/US2016/026756 dated Nov. 10, 2017; The Verge, paragraph 1, Sep. 9, 2014, 4 pages.
“Clever Toilet Checks on Your Health”, CNN.Com; Technology, Jun. 28, 2005, 2 pages.
“Final Office Action”, U.S. Appl. No. 14/681,625, dated Dec. 7, 2016, 10 pages.
“Final Office Action”, U.S. Appl. No. 14/731,195, dated Oct. 11, 2018, 12 pages.
“Final Office Action”, U.S. Appl. No. 14/715,454, dated Sep. 7, 2017, 14 pages.
“Final Office Action”, U.S. Appl. No. 14/720,632, dated Jan. 9, 2018, 18 pages.
“Final Office Action”, U.S. Appl. No. 14/715,454, dated Apr. 17, 2018, 19 pages.
“Final Office Action”, U.S. Appl. No. 14/599,954, dated Aug. 10, 2016, 23 pages.
“Final Office Action”, U.S. Appl. No. 14/699,181, dated May 4, 2018, 41 pages.
“Final Office Action”, U.S. Appl. No. 14/715,793, dated Sep. 12, 2017, 7 pages.
“Final Office Action”, U.S. Appl. No. 14/809,901, dated Dec. 13, 2018, 7 pages.
“First Action Interview OA”, U.S. Appl. No. 14/715,793, dated Jun. 21, 2017, 3 pages.
“First Action Interview Office Action”, U.S. Appl. No. 15/142,471, dated Feb. 5, 2019, 29 pages.
“First Action Interview Office Action”, U.S. Appl. No. 14/731,195, dated Jun. 21, 2018, 4 pages.
“First Action Interview Pilot Program Pre-Interview Communication”, U.S. Appl. No. 14/731,195, dated Aug. 1, 2017, 3 pages.
“First Examination Report”, GB Application No. 1621332.4, dated May 16, 2017, 7 pages.
“Foreign Office Action”, Chinese Application No. 201580034536.8, dated Oct. 9, 2018.
“Foreign Office Action”, KR Application No. 10-2016-7036023, dated Aug. 11, 2017, 10 pages.
“Foreign Office Action”, Chinese Application No. 201580036075.8, dated Jul. 4, 2018, 14 page.
“Foreign Office Action”, JP App. No. 2016-567813, dated Jan. 16, 2018, 3 pages.
“Foreign Office Action”, Korean Application No. 10-2016-7036015, dated Oct. 15, 2018, 3 pages.
“Foreign Office Action”, Japanese Application No. 2016-567839, dated Apr. 3, 2018, 3 pages.
“Foreign Office Action”, KR Application No. 10-2016-7035397, dated Sep. 20, 2017, 5 pages.
“Foreign Office Action”, Korean Application No. 1020187012629, dated May 24, 2018, 6 pages.
“Foreign Office Action”, EP Application No. 15170577.9, dated May 30, 2017, 7 pages.
“Foreign Office Action”, Korean Application No. 10-2016-7036396, dated Jan. 3, 2018, 7 pages.
“Foreign Office Action”, JP Application No. 2016567813, dated Sep. 22, 2017, 8 pages.
“Foreign Office Action”, Japanese Application No. 2018021296, dated Dec. 25, 2018, 8 pages.
“Foreign Office Action”, EP Application No. 15754323.2, dated Mar. 9, 2018, 8 pages.
“Foreign Office Action ”, CN Application No. 201580034908.7, dated Jul. 3, 2018, 12 pages.
“International Preliminary Report on Patentability”, PCT Application No. PCT/US2016/026756, dated Oct. 19, 2017, 8 pages.
“International Search Report and Written Opinion”, PCT Application No. PCT/US2016/065295, dated Mar. 14, 2017, 12 pages.
“International Search Report and Written Opinion”, Application No. PCT/US2016/042013, dated Oct. 26, 2016, 12 pages.
“International Search Report and Written Opinion”, Application No. PCT/US2016/034366, dated Nov. 17, 2016, 13 pages.
“International Search Report and Written Opinion”, Application No. PCT/US2016/033342, dated Oct. 27, 2016, 20 pages.
“Life:X Lifestyle eXplorer”, Retrieved from <https://web.archive.org/web/20150318093841/http://research.microsoft.com/en-us/projects/lifex >, Feb. 3, 2017, 2 pages.
“Non-Final Office Action”, U.S. Appl. No. 15/596,702, dated Jan. 4, 2019, 10 pages.
“Non-Final Office Action”, U.S. Appl. No. 14/666,155, dated Feb. 3, 2017, 12 pages.
“Non-Final Office Action”, U.S. Appl. No. 14/809,901, dated May 24, 2018, 13 pages.
“Non-Final Office Action”, U.S. Appl. No. 14/720,632, dated Jun. 14, 2017, 16 pages.
“Non-Final Office Action”, U.S. Appl. No. 14/715,454, dated Jan. 11, 2018, 16 pages.
“Non-Final Office Action”, U.S. Appl. No. 14/599,954, dated Jan. 6, 2017, 16 pages.
“Non-Final Office Action”, U.S. Appl. No. 14/599,954, dated Feb. 2, 2016, 17 pages.
“Non-Final Office Action”, U.S. Appl. No. 14/720,632, dated May 18, 2018, 20 pages.
“Non-Final Office Action”, U.S. Appl. No. 14/699,181, dated Oct. 18, 2017, 33 pages.
“Non-Final Office Action”, U.S. Appl. No. 14/681,625, dated Mar. 6, 2017, 7 pages.
“Non-Invasive Quantification of Peripheral Arterial Volume Distensibilitiy and its Non-Lineaer Relationship with Arterial Pressure”, Journal of Biomechanics, Pergamon Press, vol. 42, No. 8; in the search report for PCT/US2016/013968 the whole document, but in particular the abstract, dated May 29, 2009, 2 pages.
“Notice of Allowance”, U.S. Appl. No. 14/599,954, dated May 24, 2017, 11 pages.
“Notice of Allowance”, U.S. Appl. No. 14/715,793, dated Jul. 6, 2018, 5 pages.
“Notice of Allowance”, U.S. Appl. No. 15/286,495, dated Jan. 17, 2019, 5 pages.
“Notice of Allowance”, U.S. Appl. No. 15/595,649, dated Jan. 3, 2019, 5 pages.
“Notice of Allowance”, U.S. Appl. No. 14/715,793, dated Dec. 18, 2017, 5 pages.
“Notice of Allowance”, U.S. Appl. No. 14/666,155, dated Feb. 20, 2018, 5 pages.
“Notice of Allowance”, U.S. Appl. No. 14/666,155, dated Jul. 10, 2017, 7 pages.
“Notice of Allowance”, U.S. Appl. No. 14/681,625, dated Jun. 7, 2017, 7 pages.
“Notice of Allowance”, U.S. Appl. No. 14/681,625, dated Oct. 23, 2017, 8 pages.
“Notice of Allowance”, U.S. Appl. No. 15/142,829, dated Feb. 6, 2019, 8 pages.
“Notice of Allowance”, U.S. Appl. No. 14/504,137, dated Feb. 6, 2019, 9 pages.
“Pre-Interview Communication”, U.S. Appl. No. 15/142,471, dated Dec. 12, 2018, 3 pages.
“Pre-Interview Communication”, U.S. Appl. No. 14/715,793, dated Mar. 20, 2017, 3 pages.
“Pre-Interview Communication”, U.S. Appl. No. 14/715,454, dated Apr. 14, 2017, 3 pages.
“Pre-Interview Office Action”, U.S. Appl. No. 14/731,195, dated Dec. 20, 2017, 4 pages.
“Preliminary Report on Patentability”, PCT Application No. PCT/US2016/065295, dated Jul. 24, 2018, 18 pages.
“Preliminary Report on Patentability”, PCT Application No. PCT/US2016/042013, dated Jan. 30, 2018, 7 pages.
“Preliminary Report on Patentability”, PCT Application No. PCT/US2016/032307, dated Dec. 7, 2017, 9 pages.
“Pressure-Volume Loop Analysis in Cardiology”, retrieved from https://en.wikipedia.org/w/index.php?t itle=Pressure-volume loop analysis in card iology&oldid=636928657 on Sep. 23, 2017; Obtained per link provided in search report from PCT/US2016/01398 dated Jul. 28, 2016, Dec. 6, 2014, 10 pages.
“Restriction Requirement”, U.S. Appl. No. 15/462,957, dated Jan. 4, 2019, 6 pages.
“Restriction Requirement”, U.S. Appl. No. 15/352,194, dated Feb. 6, 2019, 8 pages.
“The Dash smart earbuds play back music, and monitor your workout”, Retrieved from < http://newatlas.com/bragi-dash-tracking-earbuds/30808/>, Feb. 13, 2014, 3 pages.
“Thermofocus No Touch Forehead Thermometer”, Technimed, Internet Archive. Dec. 24, 2014. https://web.archive.org/web/20141224070848/http://www.tecnimed.it:80/thermofocus-forehead-thermometer-H1N1-swine-flu.html, Dec. 24, 2018, 4 pages.
“Written Opinion”, PCT Application No. PCT/US2016/042013, dated Feb. 2, 2017, 6 pages.
“Written Opinion”, PCT Application No. PCT/US2016/026756, dated Nov. 10, 2016, 7 pages.
“Written Opinion”, PCT Application No. PCT/US2016/065295, dated Apr. 13, 2018, 8 pages.
“Written Opinion”, PCT Application PCT/US2016/013968, dated Jul. 28, 2016, 9 pages.
Antonimuthu, “Google's Project Soli brings Gesture Control to Wearables using Radar”, YouTube[online], Available from https://www.youtube.com/watch?v=czJfcgvQcNA as accessed on May 9, 2017; See whole video, especially 6:05-6:35.
Duncan, David P. “Motion Compensation of Synthetic Aperture Radar”, Microwave Earth Remote Sensing Laboratory, Brigham Young University, Apr. 15, 2003, 5 pages.
Ishijima, Masa “Unobtrusive Approaches to Monitoring Vital Signs at Home”, Medical & Biological Engineering and Computing, Springer, Berlin, DE, vol. 45, No. 11 in search report for PCT/US2016/013968 dated Jul. 28, 2016, Sep. 26, 2007, 3 pages.
Klabunde, Richard E. “Ventricular Pressure-Volume Loop Changes in Valve Disease”, Retrieved From <https://web.archive.org/web/20101201185256/http://cvphysiology.com/Heart%20Disease/HD009.htm>, Dec. 1, 2010, 8 pages.
Kubota, Yusuke et al., “A Gesture Recognition Approach by using Microwave Doppler Sensors”, IPSJ SIG Technical Report, 2009 (6), Information Processing Society of Japan, Apr. 15, 2010, pp. 1-8, Apr. 15, 2010, 13 pages.
Matthews, Robert J. “Venous Pulse”, Retrieved at: http://www.rjmatthewsmd.com/Definitions/venous_pulse.htm—on Nov. 30, 2016, Apr. 13, 2013, 7 pages.
Otto, Chris et al., “System Architecture of a Wireless Body Area Sensor Network for Ubiquitous Health Monitoring”, Journal of Mobile Multimedia; vol. 1, No. 4, Jan. 10, 2006, 20 pages.
Palese, et al., “The Effects of Earphones and Music on the Temperature Measured by Infrared Tympanic Thermometer: Preliminary Results”, ORL—head and neck nursing: official journal of the Society of Otorhinolaryngology and Head-Neck Nurses 32.2, Jan. 1, 2013, pp. 8-12.
Pu, Qifan et al., “Whole-Home Gesture Recognition Using Wireless Signals”, MobiCom'13, Sep. 30-Oct. 4, Miami, FL, USA, 2013, 12 pages.
Pu, Qifan et al., “Whole-Home Gesture Recognition Using Wireless Signals”, Proceedings of the 19th annual international conference on Mobile computing & networking (MobiCom'13), US, ACM, Sep. 30, 2013, pp. 27-38, Sep. 30, 2013, 12 pages.
Zhadobov, Maxim et al., “Millimeter-Wave Interactions with the Human Body: State of Knowledge and Recent Advances”, International Journal of Microwave and Wireless Technologies, p. 1 of 11, Cambridge University Press and the European Microwave Association, 2011; doi:10.1017/S1759078711000122, 2011.
“Final Office Action”, U.S. Appl. No. 15/287,308, dated Feb. 8, 2019, 23 pages.
“Final Office Action”, U.S. Appl. No. 15/287,155, dated Apr. 10, 2019, 11 pages.
“Final Office Action”, U.S. Appl. No. 15/287,253, dated Apr. 2, 2019, 10 pages.
“Foreign Office Action”, Japanese Application No. 2018501256, dated Feb. 26, 2019, 3 pages.
“Non-Final Office Action”, U.S. Appl. No. 15/166,198, dated Feb. 21, 2019, 48 pages.
“Non-Final Office Action”, U.S. Appl. No. 15/287,394, dated Mar. 22, 2019, 39 pages.
“Non-Final Office Action”, U.S. Appl. No. 16/238,464, dated Mar. 7, 2019, 15 pages.
“Notice of Allowance”, U.S. Appl. No. 15/286,152, dated Mar. 5, 2019, 23 pages.
“Notice of Allowance”, U.S. Appl. No. 15/703,511, dated Apr. 16, 2019, 5 pages.
“Notice of Allowance”, U.S. Appl. No. 15/286,512, dated Apr. 9, 2019, 14 pages.
“Pre-Interview Communication”, U.S. Appl. No. 15/703,511, dated Feb. 11, 2019, 5 pages.
Garmatyuk, et al., “Ultra-Wideband Continuous-Wave Random Noise Arc-SAR”, IEEE Transaction on Geoscience and Remote Sensing, vol. 40, No. 12, Dec. 2002, Dec. 2002, 10 pages.
Geisheimer, et al., “A Continuous-Wave (CW) Radar for Gait Analysis”, IEEE 2001, 2001, 5 pages.

Provisional Applications (1)

	Number	Date	Country
	62237975	Oct 2015	US

Radar gesture sensing using existing data protocols

Information

Patent Number

Date Filed

Date Issued

Inventors

Original Assignees

Examiners

Agents

CPC

Field of Search

CPC

International Classifications

Term Extension