Patent Description:
Motion detection systems have been used to detect movement, for example, of objects in a room or an outdoor area. In some example motion detection systems, infrared or optical sensors are used to detect movement of objects in the sensor's field of view. Motion detection systems have been used in security systems, automated control systems and other types of systems. <CIT> discloses a method that includes providing wireless service to a mobile leaf node using at least one first infrastructure node in an industrial control or monitoring system. The method also includes detecting movement of the mobile leaf node away from the at least one first infrastructure node. The method further includes handing off the mobile leaf node to at least one second infrastructure node in the industrial control or monitoring system so that the at least one second infrastructure node provides the wireless service to the mobile leaf node. The wireless service provided to the mobile leaf node remains deterministic. Various techniques can be used to detect the movement of the mobile leaf node. Also, the first and second infrastructure nodes could be in different clusters of nodes, and various techniques can be used to support handoffs between infrastructure nodes in different clusters.

As an overview, a motion detection system may be configured to detect motion in a space based on changes in wireless signals transmitted between devices through a space over a communication channel. In some instances, a motion detection device in the motion detection system may communicate with one or more other devices, which may or may not be part of the motion detection system, e.g. leaf nodes, via wireless signals to acquire channel information that may then be used to perform motion sensing. In some cases, it may be advantageous for the motion detection system to choose from which available devices it collects channel information that will be used in motion sensing applications.

Aspects of the present disclosure may provide certain technical advantages and improvements. In some cases, controlling which devices from which channel information is obtained improves the quality of data to be used in motion sensing applications, thus improving the motion sensing results. In some cases, according to aspects of the present disclosure, collecting channel information from certain select devices may further improve the operation of motion detection systems, such as monitoring and alarm systems, to provide more accurate and useful assessments of motion and more accurately determine a status of the space, in addition to other technical improvements to the operation of monitoring and alarm systems. In some instances, the motion detection system determines which devices to select using existing features of wireless communication devices and networks.

In some aspects of what is described here, a motion detection system may select which leaf node devices will be used for collecting channel information. In some instances, the motion detection system selects only fixed, or static, leaf nodes. In some cases, a fixed leaf node device may be selected based on link quality compared with other fixed leaf node devices. In other aspects, fixed leaf node devices are identified and/or selected during a calibration window.

<FIG> illustrates an example wireless communication system <NUM>. The example wireless communication system <NUM> includes three wireless communication devices-a first wireless communication device 102A, a second wireless communication device 102B, and a third wireless communication device 102C. The example wireless communication system <NUM> may include additional wireless communication devices <NUM> and/or other components (e.g., one or more network servers, network routers, network switches, cables, or other communication links, etc.).

The example wireless communication devices 102A, 102B, 102C can operate in a wireless network, for example, according to a wireless network standard or another type of wireless communication protocol. For example, the wireless network may be configured to operate as a Wireless Local Area Network (WLAN), a Personal Area Network (PAN), a metropolitan area network (MAN), or another type of wireless network. Examples of WLANs include networks configured to operate according to one or more of the <NUM> family of standards developed by IEEE (e.g., Wi-Fi networks), and others. Examples of PANs include networks that operate according to short-range communication standards (e.g., BLUETOOTH®, Near Field Communication (NFC), ZigBee), millimeter wave communications, and others.

In some implementations, the wireless communication devices 102A, 102B, 102C may be configured to communicate in a cellular network, for example, according to a cellular network standard. Examples of cellular networks include networks configured according to <NUM> standards such as Global System for Mobile (GSM) and Enhanced Data rates for GSM Evolution (EDGE) or EGPRS; <NUM> standards such as Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Universal Mobile Telecommunications System (UMTS), and Time Division Synchronous Code Division Multiple Access (TD-SCDMA); <NUM> standards such as Long-Term Evolution (LTE) and LTE-Advanced (LTE-A); <NUM> standards, and others. In the example shown in <FIG>, the wireless communication devices 102A, 102B, 102C can be, or may include, standard wireless network components. For example, the wireless communication devices 102A, 102B, 102C may be commercially-available Wi-Fi devices.

In some cases, the wireless communication devices 102A, 102B, 102C may be Wi-Fi access points (APs) or another type of wireless access point (AP). The wireless communication devices 102A, 102B, 102C may be configured to perform one or more operations as described herein that are embedded as instructions (e.g., software or firmware) on the wireless communication devices. In some cases, the wireless communication devices 102A, 102B, 102C may be nodes of a wireless mesh network. A wireless mesh network may refer to a decentralized wireless network whose nodes (e.g. wireless communication devices <NUM>) communicate directly in a point-to-point manner without using a central access point, base station or network controller, for example. Wireless mesh networks may include mesh clients, mesh routers, or mesh gateways. The mesh network may be based on a commercially-available mesh network system (e.g. GOOGLE Wi-Fi). In some instances, a wireless mesh network is based on the IEEE <NUM> standard. In some instances, a wireless mesh network is based on Wi-Fi ad hoc or another standardized technology. In some cases, another type of standard or conventional Wi-Fi transceiver device may be used by wireless communication devices <NUM>. The wireless communication devices 102A, 102B, 102C may perform motion detection using types of wireless protocols for wireless communication, either standard or non-standard, other than Wi-Fi protocols.

In the example shown in <FIG>, the wireless communication devices, e.g., 102A, 102B transmit wireless signals over a communication channel (e.g., according to a wireless network standard, a motion detection protocol, a presence detection protocol, or other standard or non-standard protocol). For example, the wireless communication devices may generate motion probe signals for transmission to probe a space to detect motion or presence of an object. In some implementations, the motion probe signals may include standard signaling or communication frames that include standard pilot signals used in channel sounding (e.g., channel sounding for beamforming according to the IEEE <NUM>. 11ac-<NUM> standard). In some cases, the motion probe signals include reference signals known to all devices in the network. In some instances, one or more of the wireless communication devices may process motion detection signals, which are signals received based on motion probe signals transmitted through the space. For example, the motion detection signals may be analyzed to detect motion of an object in a space, lack of motion in the space, or presence or absence of an object in the space, based on changes (or lack thereof) detected in the communication channel.

The wireless communication devices transmitting motion probe signals, e.g. 102A, 102B, may operate as source devices. In some cases, wireless communication devices 102A, 102B may broadcast the wireless motion probe signals (e.g., described above). In other cases, the wireless communication devices 102A, 102B may send wireless signals addressed to other wireless communication device 102C and other devices (e.g., a user equipment, a client device, a server, etc.). The wireless communication device 102C as well as the other devices (not shown) may receive the wireless signals transmitted by the wireless communication devices 102A, 102B. In some cases, the wireless signals transmitted by the wireless communication devices 102A, 102B are repeated periodically, for example, according to a wireless communication standard or otherwise.

In some examples, the wireless communication device 102C, operating as a sensor device, processes the wireless signals received from the wireless communication devices 102A, 102B to detect motion of an object in a space accessed by the wireless signals. In some examples, another device or computing system processes the wireless signals received by the wireless communication device 102C from the wireless communication devices 102A, 102B to detect motion of an object in a space accessed by the wireless signals. In some cases, the wireless communication device 102C (or another system or device) processes the wireless signals to detect presence or absence of an object in a space when lack of motion is detected. In some instances, the wireless communication device 102C (or another system or device) may perform one or more operations as described below with respect to any of <FIG> or in the example processes described with respect to <FIG>, or another type of process for identifying and selecting fixed leaf nodes, and updating the motion detection system to use the selected fixed leaf nodes for motion detection. In an example, the wireless communication device 102C, e.g. an AP, transmits wireless signals, e.g. sounding signals, and the wireless communication devices 102A, 102B, e.g. leaf nodes, receive and process the wireless signals, and return channel response information to the wireless communication device 102C.

The wireless signals used for motion detection can include, for example, a beacon signal (e.g., Bluetooth Beacons, Wi-Fi Beacons, other wireless beacon signals), pilot signals (e.g., pilot signals used for channel sounding, such as in beamforming applications, according to the IEEE <NUM>. 11ac-<NUM> standard), or another standard signal generated for other purposes according to a wireless network standard, or non-standard signals (e.g., random signals, reference signals, etc.) generated for motion detection or other purposes. In some cases, the wireless signals used for motion detection are known to all devices in the network.

In some examples, the wireless signals may propagate through an object (e.g., a wall) before or after interacting with a moving object, which may allow the moving object's movement to be detected without an optical line-of-sight between the moving object and the transmission or receiving hardware. Conversely, the wireless signals may indicate the absence of an object in the space when lack of motion is detected. For example, based on the received wireless signals, the wireless communication device 102C may generate motion data, presence data, or both. In some instances, the wireless communication device 102C may communicate the motion detection data, to another device or system, such as a security system, that may include a control center for monitoring movement within a space, such as a room, building, outdoor area, etc..

In some implementations, the wireless communication devices 102A, 102B may be configured to transmit motion probe signals (e.g., as described above) on a separate wireless communication channel (e.g., a frequency channel or coded channel) from wireless network traffic signals. For example, the modulation applied to the payload of a motion probe signal and the type of data or data structure in the payload may be known by the wireless communication device 102C, which may reduce the amount of processing that the wireless communication device 102C performs for motion and presence detection. The header may include additional information such as, for example, an indication of whether motion was detected by another device in the communication system <NUM>, an indication of the modulation type, an identification of the device transmitting the signal, etc..

In some instances, wireless signals received at each of the wireless communication devices <NUM> may be analyzed to determine channel information for the different communication links in the network (e.g. between respective pairs of wireless communication devices in the network). The channel information may be representative of a physical medium that applies a transfer function to wireless signals that traverse the space. In some instances, the channel information includes channel response information. Channel response information may refer to known channel properties of a communication link, and may describe how a wireless signal propagates from a transmitter to a receiver, representing the combined effect of, for example, scattering, fading, and power decay within the space between the transmitter and receiver. In particular, a link may correspond to a receive (Rx) /transmit (Tx) antenna pair. Various configurations of the Rx/Tx antennas may be supported. For example, for a <NUM> Rx antenna/<NUM> Tx antenna (e.g. 3x3) configuration, a total of <NUM> channel responses may be observed; for a 3x2 configuration, <NUM> channel responses may be observed; for a 2x2 configuration, <NUM> channel responses may be observed; for a 2x1 configuration, <NUM> channel responses may be observed. In some instances, a 4x4 or 8x8 configuration may be possible, thus providing <NUM> or <NUM> channel responses, respectively.

In some instances, the channel information includes beamforming state information. Beamforming (or spatial filtering) may refer to a signal processing technique used in multi antenna (multiple-input/multiple-output (MIMO)) radio systems for directional signal transmission or reception. Beamforming can be achieved by combining elements in an antenna array in such a way that signals at particular angles experience constructive interference while others experience destructive interference. Beamforming can be used at both the transmitting and receiving ends in order to achieve spatial selectivity. In some cases (e.g., the IEEE <NUM>. 11ac standard), a beamforming steering matrix is used by a transmitter. The beamforming steering matrix may include a mathematical description of how the antenna array should use each of its individual antenna elements to select a spatial path for transmission. While certain aspects are described herein with respect to channel response information or beamforming state information, other types of channel information may also be used in the aspects described as well.

In the example shown in <FIG>, the wireless communication system <NUM> is illustrated as a wireless mesh network, with wireless communication links between each of the respective wireless communication devices <NUM>. In the example shown, the wireless communication link between the wireless communication device 102C and the wireless communication device 102A can be used to probe a first motion detection zone 110A, the wireless communication link between the wireless communication device 102C and the wireless communication device 102B can be used to probe a second motion detection zone 110B, and the wireless communication link between the wireless communication device 102A and the wireless communication device 102B can be used to probe a third motion detection zone 110C. In some instances, each wireless communication device <NUM> may be configured to detect motion in each of the motion detection zones <NUM> accessed by that device by processing received signals that are based on wireless signals transmitted on links between the wireless communication devices <NUM> in the motion detection zones <NUM>. For example, when object <NUM> shown in <FIG> moves between the first motion detection zone 110A and the third motion detection zone 110C, the wireless communication devices <NUM> may detect the motion based on signals received that are based on wireless signals transmitted through the respective motion detection zones <NUM>. For instance, the wireless communication device 102A can detect motion of the person in both the first and third motion detection zones 110A, 110C, the wireless communication device 102B can detect motion of the person <NUM> in the second and third motion detection zones 110B, 110C, and the wireless communication device 102C can detect motion of the person <NUM> in the first and second motion detection zones 110A, 110B.

In some instances, the motion detection zones <NUM> can include, for example, air, solid materials, liquids, or another medium through which wireless electromagnetic signals may propagate. In the example shown in <FIG>, the first motion detection zone 110A provides a wireless communication channel between the first wireless communication device 102A and the third wireless communication device 102C, the second motion detection zone 110B provides a wireless communication channel between the second wireless communication device 102B and the third wireless communication device 102C, and the third motion detection zone 110C provides a wireless communication channel between the first wireless communication device 102A and the second wireless communication device 102B. In some aspects of operation, wireless signals transmitted on a wireless communication channel (separate from or shared with the wireless communication channel for network traffic) are used to detect movement. The objects can be any type of static or moveable object, and can be living or inanimate. For example, the object can be a human (e.g., as depicted <FIG>), an animal, an inorganic object, or another device, apparatus, or assembly, an object that defines all or part of the boundary of a space (e.g., a wall, door, window, etc.), or another type of object. In some implementations, motion information from the wireless communication devices may trigger further analysis to determine presence or absence of an object when motion of the object is not detected.

In some implementations, the wireless communication system <NUM> may be, or may include, a motion detection system. The motion detection system may include one or more of the wireless communication devices 102A, 102B, 102C and possibly other components. One or more wireless communication devices 102A, 102B, 102C, in the motion detection system may be configured for motion detection. The motion detection system may include a database that stores signals. The stored signals may include respective measurements or metrics (e.g., channel response information, beamforming state information or other channel information) for each received signal, and the stored signals may be associated with a channel state, e.g. motion, lack of motion, etc. In some instances, one of the wireless communication devices <NUM> of the monitoring system may operate as a central hub or server for processing received signals and other information to detect motion. A wireless communication device <NUM>, or other similar wireless communication device, of the monitoring system may identify fixed, or static, leaf nodes communicating with the wireless communication device <NUM>, or the other similar wireless communication device of the monitoring system. In some implementations, a wireless communication device <NUM>, or other device or computing system, of the motion detection system may classify and rank fixed, or static, leaf nodes communicating with the wireless communication device <NUM>, or with the other similar wireless communication devices <NUM>. The storage of data related to processes for identifying fixed leaf nodes, and/or classifying and selecting fixed leaf nodes for sounding in the monitoring system may be performed on a wireless communication device <NUM> configured as an AP device (e.g. gateway device), another type of computing device, in the motion detection system, or in some cases, may be performed in the cloud.

<FIG> shows a diagram showing an example architecture of an example motion detection system <NUM>. In some cases, the devices in motion detection system <NUM> communicate according to one or more aspects of an IEEE <NUM> wireless communication standard, or another type of standard or non-standard protocol. In the example shown in <FIG>, the motion detection system <NUM> includes a wireless access point (AP) <NUM> (e.g. wireless communication device <NUM>), one or more leaf devices <NUM> that may communicate with the AP <NUM>, and in some instances, additional AP or leaf devices, or other types of devices, such as servers. In some instances, the motion detection system includes multiple APs <NUM> (e.g. wireless communication devices <NUM> described in <FIG>) communicating according to a wireless mesh protocol, with one or more leaf nodes <NUM> connected to each of the APs <NUM>, as shown in <FIG>.

In some instances, each device-to-device wireless connection in the motion detection system <NUM> may constitute a motion link <NUM> from which motion measurements are taken. The motion link between an AP <NUM> and a leaf node <NUM> is referred to herein as an AP-leaf node link. A leaf node <NUM> may be a Wi-Fi device that is used for sounding by an AP <NUM> in the motion detection system <NUM>. In some instances, leaf nodes <NUM> are not configured with proprietary motion detection software or hardware, but operate normally according to a particular wireless standard. For example, a leaf node <NUM> may process a sounding request from an AP <NUM> as part of normal operations under its operating standard (e.g., the leaf node <NUM> operating as a smartphone, a smart thermostat, a laptop computer, a tablet device, a set-top-box or streaming device, etc.). In some cases, the APs <NUM> and the leaf nodes <NUM> conform to a standard (e.g., the IEEE <NUM>) protocol and, as such, do not require motion detection-specific hardware or software to act as a leaf node of the motion detection system <NUM>. Generally, the motion detection system <NUM> may use any of the leaf nodes <NUM> in <FIG> as sounding nodes to obtain channel information (e.g., channel response information, beamforming state information, etc.) for motion detection. In some cases, it is preferable that leaf nodes <NUM> used for sounding by an AP <NUM> have certain characteristics, for example, that they be stationary over time and have a steady power supply, e.g. a smart phone that is plugged in.

In one example, the motion detection system <NUM> implements a beamforming protocol, e.g. to generate and transmit beamforming information from one wireless device to another wireless device. For example, the wireless communication device <NUM> can implement a beamforming protocol as described above. In some instances, the AP(s) <NUM> can detect motion of the objects <NUM> based on analyzing beamforming matrices (e.g., steering or feedback matrices). In some examples, sounding and and/or beamforming are performed on a motion link, e.g. motion link 250A between AP <NUM> and a leaf device 204A, and motion is detected at the AP <NUM> by observing changes in a beamforming matrix (e.g., the steering or feedback matrix) associated with the motion link. Motion may also be localized by the AP <NUM> based on changes in the respective beamforming matrices for each connection with a leaf device <NUM>. In a mesh configuration (e.g., the motion detection system <NUM> with multiple APs <NUM> interconnected- not shown in <FIG>), sounding and beamforming is performed between APs <NUM> and their respective leaf devices <NUM>, and motion information is determined at each of the APs <NUM>. The motion information can then be sent to a hub device (e.g., one of the APs <NUM>) or another device, such as a server, to analyze the motion information and make an overall determination of whether motion has occurred in the space, detect a location of detected motion, or both.

In some implementations of the example motion detection system <NUM> shown in <FIG>, the number of leaf nodes <NUM> communicating with AP <NUM> is unknown or varies over time. In some instances, the number of leaf nodes <NUM> communicating with AP <NUM> changes as mobile leaf nodes <NUM> move in and/or out of communication with the AP <NUM>. For example, a user carrying a mobile device, e.g. leaf node 204B, may enter a space and the mobile device may begin communicating with AP <NUM> which is performing motion sensing activities. However, generally in a mesh configuration, a leaf node is able to choose any of the mesh APs and is additionally free to switch between them at any time, thus affecting the number of leaf nodes communicating with any particular AP <NUM>. While the mobile device is communicating with the AP <NUM>, the AP <NUM> may collect information from the mobile device and/or perform sounding with the mobile devices. The user may subsequently leave the space with the mobile device, and the mobile device moves out of range of the AP <NUM>, but later comes into range of AP <NUM> again. In some contexts, data gathered by the AP <NUM> from this mobile device may not be stable enough to use for making determinations on motion.

In some cases, using leaf nodes in a motion detection system may affect the performance of the system. For example, resources necessary to perform sounding on motion links between devices, e.g. motion links <NUM> between AP <NUM> and leaf nodes <NUM>, in order to collection channel information, may be limited. In some instances, central processing unit (CPU) and memory usage rise linearly with the number of active AP-leaf node links used for sounding in the motion detection system. In some cases, the motion detection system may be communicating with leaf nodes that are static (with a fixed location), and with leaf nodes that are mobile (with variable location), but cannot differentiate the fixed leaf nodes from the mobile leaf nodes. In some instances, the location of the leaf nodes may affect the performance of the motion detection system. In some cases, the motion detection system observes that some leaf nodes sound poorly during the sounding process to collect channel information, resulting in bad channel information being provided to the motion detection system. In some instances, the bad channel information received from a poor sounding leaf node may cause overall system degradation. In some instances, the poor sounding leaf node may be due to the fact that it is a mobile leaf node, and not a fixed leaf node. In other instances, the motion detection system can be overwhelmed in situations in which a large number of leaf nodes appear all at once or within a short-time period, e.g. on system initialization, after rebooting the system, etc. In some cases, the user may also be overwhelmed with notifications from the system, e.g. when a user is notified and asked to confirm that a leaf node is added to the system.

As described herein, a closed-loop continuous link health measurement and classification system for AP-leaf node links is provided to address one or more of these issues and improve the operation of the motion detection system. In some instances, the system may be applied to AP-AP mesh links or other types of motion links in a motion detection system.

<FIG> is a diagram showing an example of AP-leaf node link classification. In an implementation, the example link classification <NUM> classifies each AP-leaf node link in the motion detection system (e.g. motion detection system <NUM>) as a fixed, or static, leaf node or as a mobile leaf node. In some instances, a leaf node (e.g. leaf node <NUM> in <FIG>) is communicatively coupled to one or more APs <NUM> of the motion detection system at various points in time. In some instances, the motion detection system periodically receives a network status report <NUM> from each AP <NUM> for a defined time interval, e.g. every minute, every two or three minutes, every hour, etc. The time interval for receiving network status reports may be adjustable. In systems comprising multiple APs <NUM>, one of the APs <NUM> may act as a hub to collect network status reports <NUM> from each of the other APs <NUM>. In some implementations, the motion detection system may have only one AP <NUM> and, in that case, will not need to receive network status reports <NUM> from other APs. The network status report <NUM> for each AP in the motion detection system comprises statistics for each active AP-leaf node link during the defined time interval.

In an implementation, active AP-leaf node links are identified based on the machine address, e.g. medium access control (MAC) address, of the underlying wireless interfaces for the AP and the leaf node. A network status report <NUM> is provided for each AP-leaf node link. In some instances, an AP-leaf node link is determined to be active during a defined time interval if the leaf node communicates wirelessly with the AP during the time interval. For example, if a leaf node responds to a beacon signal or other signal from an AP during sounding, the AP will mark the leaf node as active in the network status report <NUM> for that time interval. In some instances, the status reports <NUM> from multiple time intervals are aggregated to derive statistics for each AP-leaf node link over a calibration period. In some implementations, for each active AP-leaf node link, various metrics in the status reports are tracked and/or calculated for a calibration period, e.g. one hour. In the example classification <NUM> shown in <FIG>, the statistics received in <NUM> network status reports are aggregated over a calibration period of one hour. As shown in <FIG>, the metrics include a presence information metric <NUM>, a successful sounding metric <NUM>, a failed sounding metric <NUM>, an average received signal strength indicator (RSSI) metric <NUM>, and motion detection failure rate metric <NUM>. In some implementations, other metrics may be used classify a link. In some instances, for a calibration period, a presence information metric <NUM> indicates the number of status reports <NUM> during which a particular AP-leaf node link was active. As an example, for a calibration period of one hour with status reports <NUM> reported every minute, the presence information metric <NUM> may have an integer value ranging from zero to sixty (<NUM>-<NUM>). In some implementations, for each AP-leaf node link, a successful sounding metric <NUM> is calculated indicating the average successful channel frequency response (CFR) sounding rate (range <NUM>-<NUM>%), and the failed sounding metric <NUM> is calculated indicating the average failed CFR sounding rate (range <NUM>-<NUM>%). These statistics are related to an AP's attempts to sound a leaf node by sending a sounding request, and whether the leaf node responded (e.g. successful) or did not respond (e.g. unsuccessful). In some cases, an average RSSI metric <NUM> and motion detection failure rate <NUM> may be calculated and used to classify an AP-leaf node link. In some instances, a calibration result is calculated (e.g. as described in <FIG> or otherwise) for each calibration period, and each active AP-leaf node link is classified <NUM> based on the calibration result. For example, an active AP-leaf node link may be classified as passed, noisy, or sleeping, described below.

In the examples described here, AP-leaf node links are denoted by an AP number and a Leaf number pair. In the example described in <FIG> and <FIG>, the motion detection system includes three APs - AP0, AP1, and AP2, and two leaf nodes - LeafO and Leaf1, communicate with one or more of the APs during the calibration event. Thus, each AP reports status for up to two links, e.g. AP0-Leaf0 and AP0-Leaf1. On the other hand, a leaf node may be associated with one, two, or all three of the APs, and therefore, may be associated with three links, e.g. AP0-Leaf0, AP1-Leaf0, and AP2-Leaf0. The AP and leaf node numbering user here is solely for illustration, as the actual AP-leaf node link pairs are identified by MAC address, described above.

In some implementations, first, an active leaf node is determined to be fixed (e.g. static) or mobile using the presence information metric <NUM>. During experimentation in some example systems, it was observed that an approach of monitoring whether a leaf node jumps from one AP to another is not necessarily indicative of whether the leaf node is fixed or mobile, for example, fixed leafs were observed jumping for various non-obvious reasons. Further, observations of received signal strength indicator (RSSI) measurements of the leaf node alone do not necessarily provide a reliable indication of whether a leaf node was fixed or mobile, in some contexts.

<FIG> is a diagram showing an example of evaluating links over a calibration window <NUM>. A calibration window <NUM> includes multiple calibration periods <NUM>. In this example, each row of table <NUM> illustrates calibration results <NUM> (e.g. obtained as described in <FIG>, or otherwise) for each calibration period <NUM> in the calibration window <NUM> for a particular AP-leaf node link <NUM>. In the example shown in <FIG>, activity of an AP-leaf node link during the calibration window <NUM> is represented by either a highlighted or greyed-out calibration period <NUM> in each respective row for that AP-leaf node link. In particular, a greyed-out calibration period <NUM> (e.g. NODATA 470a) in any calibration window <NUM> indicates that, based on the presence information metric <NUM>, a particular AP-leaf node link <NUM> was not detected as being active (or active enough) in that calibration period <NUM>, while other highlighted calibration periods <NUM> (e.g. PASS 470b, NOISY470c, and SLEEP 470d) indicate that, based on the presence information metric <NUM>, a particular AP-leaf node link <NUM> was detected as active (or active enough) in that calibration period <NUM>. The assignment of additional qualifications (e.g. PASS 470b, NOISY470c, and SLEEP 470d, although other qualifications <NUM> are available as described in <FIG>) to active AP-leaf node links are discussed in <FIG> For example, a leaf node is marked as present, or active, when the the presence information metric <NUM> for an AP-leaf node link during the calibration period <NUM> exceeds a threshold (e.g. presence metric <NUM> >= PRES_THRES (<NUM>)), as described in decision <NUM> in <FIG>). In this example, the presence information metric <NUM> is a value from <NUM> to <NUM>, so an AP-leaf node link <NUM> with a presence information metric <NUM> with a value of <NUM> or higher, will be determined active (or active enough) for the calibration period <NUM> based on a threshold of <NUM>%, while the AP-leaf node link will be determined not active (or active enough) if the value is less than <NUM> for the calibration period <NUM>. The threshold may be adjustable so, in some instances, a leaf node may be determined to be present/active for a lesser or greater percentage of time during the calibration window <NUM>. In this example, each calibration period <NUM> is one hour and the calibration window <NUM> is five hours, meaning there are five calibration reports <NUM> for each AP-leaf node link <NUM> to be examined. In an implementation, each AP-leaf node link <NUM> is assigned a number of points <NUM> for the calibration window <NUM>. In some instances, the points are assigned based on whether its presence activity exceeded the presence threshold in each calibration period <NUM>. In the example shown, the total points <NUM> for each AP-leaf node link <NUM> is derived by adding a point for each highlighted calibration period <NUM> in the calibration window <NUM>.

In this example, an AP-leaf node link <NUM> is assigned points <NUM> in each calibration period <NUM> of the calibration window <NUM>. In this example, an AP-leaf node link <NUM> is assigned <NUM> points if the AP-leaf node link <NUM> is determined to be `not active' during the calibration period <NUM> (e.g. in <FIG>, the `not active' link is greyed, not highlighted) or is assigned <NUM> point if the AP-leaf node link <NUM> is determined to be 'active' during the calibration period <NUM> (e.g. in <FIG>, the 'active' link is highlighted), although values other than <NUM> or <NUM> may be assigned to denote presence activity or lack thereof in other implementations. As noted previously, the AP-leaf node link's presence activity may be determined in decision box <NUM> in <FIG>, described below.

Returning to calculating points <NUM>, in table <NUM>, AP0-Leaf0 is assigned <NUM> point for each of the highlighted one-hour calibration periods <NUM> (e.g. for the most recent calibration periods in which statistics are available for the link - <NUM>, <NUM>, <NUM>, and <NUM>) and <NUM> points for the non-highlighted one-hour calibration period (e.g. the calibration period <NUM> in which no data is available for the link) for a total of <NUM> points shown in table <NUM>. In some instances, an AP-leaf node link <NUM> may not have any data available for any calibration period, e.g. no data is available for AP0-Leaf1, and is assigned <NUM> total points <NUM> in table <NUM>. In some cases, the overall assigned points <NUM> assigned to an AP-leaf node link <NUM> for the calibration window <NUM> provides an indication of the AP-leaf node link's presence activity level, and in some instances, may further provide an indication whether the leaf node is a fixed leaf node or a mobile leaf node. However, points alone may not be sufficient to determine with confidence whether the leaf node is fixed or mobile, at least in some contexts.

In some implementations, the total points <NUM> for an AP-leaf node link <NUM> is an indication of presence activity, but does not indicate when the data in each calibration period <NUM> was collected, and consequently, when the link <NUM> was last active. For example, a calibration event may be initiated once a day, or every <NUM> hours, which means there are potentially <NUM> one-hour network status reports <NUM> for each AP-leaf node link to choose from for the calibration window, with the '<NUM>' being the most recent network status report and '<NUM>' being the oldest network status report. In the example in <FIG>, the calibration window is five hours, and therefore, the network status reports <NUM> for five calibration periods will be selected for each AP-leaf node link. The most recent calibration period <NUM> for which data is available in a network status report <NUM>, is the first report for each AP-leaf node link, and then the network status reports <NUM> for the previous four calibration periods will be used to complete the dataset for the <NUM>-hour calibration window <NUM>. For example, AP0-Leaf0, AP1-Leaf0, and AP2-Leaf0 link pairs <NUM> were most recently active in the latest calibration period, e.g. '<NUM>'; AP1-Leaf1 was most recently active in the sixth oldest calibration period '<NUM>'. AP2-Leaf1 <NUM> was most recently active in the sixteenth and seventeenth oldest calibration periods '<NUM>' and '<NUM>', but no data is available for the next three oldest calibration periods so for illustration, these periods <NUM> are denoted by the next oldest calibration period '<NUM>' and greyed out.

In some instances, if the most recent presence information metric <NUM> for an AP-leaf node link <NUM> is old, the presence activity information for a link <NUM> is also not current which lowers its relevance when determining whether a leaf node is fixed or mobile. In some cases, a range value <NUM> is used as an indication of the age of the presence activity data. For example, the presence activity data represented in <FIG> for AP0-Leaf0 was collected over the most recent <NUM> hours (e.g. <NUM>, <NUM>, <NUM>, and <NUM>). On the other hand, the most current presence activity data for AP1-Leaf1 was collected <NUM>-<NUM> hours ago (e.g. <NUM>, <NUM>, <NUM>, <NUM>, and <NUM>), which indicates that no data is available for the <NUM>-<NUM> most recent hours. The data for AP2-Leaf1 was collected even earlier (e.g. at <NUM> and <NUM>), which indicates that no data is available for the most recent <NUM>-<NUM> hours.

In an implementation, the range <NUM> for an AP-leaf node link is determined by the age of the oldest calibration period <NUM> for which data is available to use in the calibration window <NUM>, relative to the most recent calibration period. For example, referring to table <NUM>, the most recent calibration period is '<NUM>', so the range for AP0-Leaf0 is <NUM>-<NUM>, or <NUM>; the range for AP1-Leaf1 is <NUM>-<NUM>, or <NUM>; and the range for AP2-Leaf <NUM> is <NUM>-<NUM>, or <NUM>. The range <NUM> for each AP-leaf node link is illustrated in table <NUM>. The range <NUM> information, along with the presence activity points <NUM> may then be used to identify a link as fixed or mobile.

In instances in which the calibration window shifts to accommodate results and statistics for a next calibration period, if there is no additional activity report for an AP-leaf node link, then the score <NUM> and points <NUM> for the AP-leaf node link will not change. Referring again to AP2-Leaf1, while the score <NUM> and points <NUM> will not change for subsequent hours <NUM> to <NUM>. However, the range <NUM> will increase by <NUM> each subsequent calibration period in which there is no activity on the AP-leaf node link. An increase in the range <NUM> value thereby decreases the relevance of its historical data while providing additional context as to whether the leaf node is mobile or static.

In an implementation, a leaf node is determined to be a static leaf node when the number of presence activity points <NUM> equals the range <NUM> for all links of a leaf node. In the example shown in table <NUM>, each of AP0-Leaf0, AP1-Leaf0, and AP2-Leaf0 link pairs have points <NUM> that equal its range <NUM>. In this instance, LeafO may be identified as a static leaf node because all of its links' points <NUM> equal its range <NUM>. In some instances, a leaf node may not establish a link with every available AP (e.g. no data is available for an AP0-Leaf1 link pair). In this situation, only links which have data available will be used to make the static or mobile determination for the leaf node; links with no data (e.g. range <NUM> equals <NUM>) will be ignored. Other (additional or different) criteria may be used to determine that a leaf node is a static leaf node in some cases.

In an implementation, when a leaf node is determined to be a static leaf node, e.g. LeafO, the motion detection system adds that node as a sounding node. However, when a leaf node is determined to be a mobile node, the motion detection system removes (or does not add) the leaf node as a sounding node. For example, AP0 may select LeafO to perform sounding and use the resulting data for motion detection; Leaf1 appears to be mobile based on the example data shown in the table <NUM>, therefore, AP0 may determine not use Leaf1 for motion detection.

In some implementations, the motion detection system classifies the quality of each AP-leaf node link by determining a score <NUM> (also referred to as a `health score' herein) for each link, shown in table <NUM>. For example, each AP-leaf node link may be assigned a value based on the link quality data in each network status report <NUM> for each calibration period <NUM>. In the example shown in <FIG>, the score <NUM> for each AP-leaf node link is compiled by adding the link quality values for each calibration period <NUM> across the calibration window <NUM> for the AP-leaf node link. In some instances, link quality values are assigned as described in <FIG>. In the example of <FIG>, the quality of a link is higher when the score is higher. However, in other implementations, other values may be assigned to represent link quality and the score may be calculated in a different manner, e.g. a lower score may represent a higher quality. In <FIG>, the AP-leaf node links are ranked according to their quality scores <NUM>. In some instances, only the scores <NUM> of leaf nodes identified as static are analyzed. For example, LeafO was identified as a static leaf node, and the AP0-LeafO link pair has the highest score, indicating that link has the best quality over AP1-LeafO and AP2-Leaf0. In some cases, AP0 will add the leaf node LeafO as a sounding node, or LeafO is already a sounding node, AP0 will keep it as a sounding node. In this example, Leaf1 was identified as a static node, therefore its scores are not considered.

<FIG> is a flow diagram showing an example process <NUM> of classifying AP-leaf node links. In some implementations, the classification process <NUM> is performed for each AP-leaf node link in each calibration period <NUM>, e.g. when aggregating statistics as described in <FIG>. In this example, there are several possible calibration result <NUM> categories (e.g. NOT_SOUNDED, NOT_PRESENT, SLEEPING, PASS, NOISY, BROKEN, NO_DATA), although in some instances, more or fewer categories may be used for classifying a leaf node. Each calibration result <NUM> carries a numeric weight based on how desirable the leaf node is from a sounding priority perspective. The numeric weights are summed over a calibration window to derive a score (e.g., the score <NUM> shown in table <NUM> in <FIG>). In some instances, a negative score indicates that sounding that leaf node is undesirable, while a positive score indicates that sounding the leaf node would contribute positively to the performance of the motion detection system. In some cases, the leaf nodes are ranked in priority based on the magnitude of the score, e.g. highest to lowest.

In example process <NUM>, the statistics aggregated for each AP-leaf node link for each calibration period <NUM> are used to determine a score for that link. At <NUM>, a leaf node that was skipped, e.g. not selected by an AP for sounding, in a particular round (e.g. a calibration period) is classified as NOT_SOUNDED 560a and assigned a base value 570a (e.g. +<NUM> points). If the device has been sounded by the AP, then at <NUM>, it is determined whether the device was present enough (e.g. communicated sufficiently) during the calibration period <NUM>. In an implementation, it may be determined whether the presence of the AP-leaf node link exceeds a presence threshold, e.g. using the presence information metric <NUM> in <FIG>. In this example, the presence threshold, PRES_THRES, is set at <NUM>, which indicates that a link <NUM> must be active for at least <NUM>% of the calibration period <NUM>. In some instances, the leaf node's presence indicates whether the motion detection system has enough information to properly analyze the link for that calibration period, denoted by the presence threshold. In this example, at <NUM>, a device's presence that does not meet the presence threshold for the calibration period is classified as NOT_PRESENT 560b and assigned a value 570b (e.g. <NUM> points) indicating the AP-leaf node link was not fully present during the calibration period <NUM>.

When a leaf node meets or exceeds the presence threshold, then at <NUM>, it is determined whether the device is sleeping. In an implementation, the successful sounding metric <NUM> (represented as "prate" in <FIG>) and the failed sounding metric <NUM> (represented as "frate" in <FIG>), described in <FIG>, are summed and the result is evaluated against a sleep threshold, SLEEP_THRES. If the result is less than the sleep threshold, the device is determined to be asleep. In this example, sleep threshold, SLEEP_THRES, is set at <NUM>, although other values may be used. When the result is less than the sleep threshold for the calibration period, the leaf node is classified as SLEEPING 560c and assigned a value 570c (e.g. -<NUM> points) indicating the AP-leaf node link was sleeping during the calibration period <NUM>.

When a leaf node meets or exceeds the sleep threshold, e.g. it is not sleeping, then at <NUM>, it is determined whether the device performed sounding successfully during the calibration widow. In an implementation, the successful sounding metric <NUM> (e.g. prate) is evaluated against a passing threshold, GOOD_THRES. If the 'prate' is greater than the passing threshold, the device is determined to be sounding successfully during the calibration period. In this example, the passing threshold, GOOD_THRES, is set at <NUM>. When 'prate' is greater than the passing threshold for the calibration period, the leaf node is classified as PASS 560d and assigned a value 570d (e.g. +<NUM> points) indicating the AP-leaf node link was successfully sounding during the calibration period <NUM>.

When a leaf node does not meet the passing threshold, then at <NUM>, it is determined whether the device performed sounding successfully but with interference and/or noise during the calibration period <NUM>. In an implementation, the successful sounding metric <NUM> ('prate') is evaluated against a lower passing threshold, OK_THRES, of sounding successfully during the calibration period. If 'prate' is greater than the lower passing threshold, OK_THRES, the device is determined to be sounding successfully during the calibration period. In this example, the passing threshold, OK_THRES, is set at <NUM>, which is a lower quality than GOOD_THRES. When 'prate' is greater than the lower passing threshold for the calibration period, the leaf node is classified as NOISY 560e and assigned a value 570e (e.g. +. <NUM> points) indicating the AP-leaf node link was successfully sounding but noisy during the calibration period.

When a leaf node does not meet the lower passing threshold, OK_THRES, then at <NUM>, it is determined that the device is not sounding properly. For example, when 'prate' is less than the lower passing threshold for the calibration period, the leaf node is classified as BROKEN 560f and assigned a value 570f (e.g. -<NUM> point) indicating the AP-leaf node link is broken during the calibration period. In cases when there is no history data available for a leaf node in a calibration period, the AP-leaf node link is classified as NO_DATA <NUM> and assigned a default value <NUM> (e.g. +.

In some implementations, after performing the example process <NUM>, each AP-leaf node link in each calibration period <NUM> of a calibration window <NUM> will be classified as to the quality of the link and assigned a score. In some cases, the points assigned to the link for each calibration period <NUM> are summed across the calibration window <NUM> to derive a score, e.g. score <NUM> in table <NUM> of <FIG>. In some instances, the scores of fixed leaf nodes may be used to rank each of its AP-leaf node links to prioritize which links will provide the motion detection system the best quality sounding data.

<FIG> is a block diagram showing an example of a closed-loop control flow <NUM> for updating leaf nodes in a motion detection system. In some implementations the example control flow <NUM> is performed by the motion detection system. In some cases, the example control flow <NUM> may be performed by the only AP in the motion detection system, by one of a plurality of APs in the motion detection system, or by a separate server using the data reported by a designated AP in the motion detection system. In some instances, the process <NUM> is performed for each AP in which it selects the leaf node(s) to be used to for motion detection. In this example process <NUM>, network status is reported every minute, and a calibration period is every hour (e.g. as described in <FIG>). Other calibration periods and network reporting intervals may be used.

At <NUM>, the motion detection system waits to enter guardian status during which it obtains network status for each AP. At <NUM>, it is determined if a calibration period has completed by checking if it is the next calibration period, e.g. the next hour. If an hour has lapsed and a calibration period <NUM> has been completed, then at <NUM>, a calibration event is run in which statistics for each AP-leaf node link are aggregated (e.g. as described in <FIG> and <FIG>). At <NUM>, each AP-leaf node link is scored based on the history window. In this example, the history window comprises data and scores for each AP-leaf node link for the last <NUM> calibration periods.

At <NUM>, the fixed leaf nodes for sounding are selected. For example, the motion detection system may select a maximum of number of leaf nodes to be sounded per AP (e.g. as denoted MAX_LEAFS_PER_AP=<NUM>) from the identified fixed leaf nodes for the current calibration event. In some implementations, the leaf nodes are selected based on the scores <NUM> for each leaf node as described in <FIG>. In some instances, the location of the leaf node is used in combination with the scores <NUM>. For example, once a static leaf node has proven itself qualified for sounding by achieving a minimum score, it may potentially become its own localizer result location, e.g. detected motion may be localized to the location of the fixed leaf node. In some instances, this option may be offered via an event sent to a user interface of the user's device, e.g. via motion detection application on a user's smartphone. Once a user provides a location of a static leaf via the user interface, the selection of static leaf nodes for sounding may be biased based on the uniqueness of the leaf node locations. In an example, if a unique location has a single leaf and its quality is considered 'ok', then sounding that leaf node will have better motion results than sounding two 'good' leafs in a single zone.

After the maximum number of leaf nodes for each AP are selected, at <NUM>, it is determined whether at least one of the candidate leaf nodes is a newly identified static leaf node with a link quality that exceeds minimum link quality score (e.g. SCORE_THRES). An example of the scores for each AP-leaf node link are described in <FIG> (e.g. scores <NUM> in table <NUM>). In some instances, no static leaf nodes meet the quality score criteria, in which case, at <NUM>, the accumulators are reset (e.g. scores <NUM>, points <NUM>, and range <NUM> in <FIG>), and at <NUM>, aggregate statistics for the just-completed calibration period are updated for all AP-leaf node links, such as, presence, successful sounding rate ('prate'), and failed sounding rate ('frate'), and any other link statistics being tracked, such as average RSSI and motion detection failure rate. After the accumulators are updated, the system waits to receive the next status report at <NUM>.

In some implementations, when a new static leaf node has been identified that exceeds the minimum quality score, at <NUM>, it is determined if a global static leaf cooldown process is active. For example, the motion detection system may designate a time (i.e. a cooldown period) when new leaf nodes cannot be added to the motion detection system. In some instances, the static leaf cooldown period may be implemented to provide stability to the system and to prevent a cycling in and out of newly selected static leaf nodes. In an example, the cooldown period may be <NUM> hours. In instances in which the cooldown period is active, the process advances to <NUM>, where the accumulators are reset, statistics for the calibration period are updated at <NUM>, and the system waits to receive the next status report at <NUM>.

In instances where the cooldown period is not active, a new fixed leaf node may be added to the motion detection system. In that case, at <NUM>, an event is generated to report the newly identified and selected static leaf node. For example, the motion detection system may generate a 'ZoneCreatedEvent' to report the new static leaf node, which associates the leaf node and its sounding data with a particular motion zone. As described above, the opportunity to create a new zone is offered to a user via a user interface. In some instances, at <NUM>, the new static leaf node is marked as being a potential unique localizer zone, e.g. depending on whether the user indicates a new zone via the user interface.

After the new leaf node has been selected for sounding, the cooldown timer is started, or reset if still running, at <NUM>. In this example, the cooldown timer, MIN LEAF_INTERVAL, is set to <NUM> hours so that newly identified fixed leaf nodes cannot be added to the motion detection system during that time. The process then advances to <NUM> where the accumulators are reset, statistics for the calibration period are updated at <NUM>, and the system waits to receive the next status report at <NUM>. In cases when a calibration period is not complete at <NUM> (e.g. one hour of network status reports have not been received), the statistics for the current calibration period are updated at <NUM>, and the system waits to receive the next status report at <NUM>.

<FIG> is a block diagram showing an example process for a fixed leaf node disconnection event. For example, a fixed leaf node being used for sounding by an AP in the motion detection system may lose connectivity with the AP, e.g. the device is disconnected from the network, power is lost, the device is moved out of the area, etc. This example process <NUM> is performed when an AP receives a link disconnect event at <NUM> indicating that a fixed leaf node is no longer communicating with the AP. In some implementations, at <NUM>, the system determines whether the AP has at least one other fixed leaf node with a positive quality score (e.g. score <NUM> in <FIG>). If so, at <NUM>, the AP is directed to begin sounding the available top scoring fixed leaf node candidate immediately. Otherwise, at <NUM>, the AP takes no action to replace the fixed leaf node at this time.

<FIG> is a block diagram showing an example process for a leaf node connection event. In some implementations, this process <NUM> is performed when an AP receives a link connected event at <NUM> indicating that an AP-leaf node link has been established. The AP may detect the connected event at any time. In some implementations, at <NUM>, it is determined whether the AP has prior history data associated with this new link, e.g. presence information metric <NUM> and quality statistics <NUM>-<NUM> data within the last <NUM> hours. If no history data is available for the AP-leaf node link, then at <NUM>, the past history over the calibration window is set to default values, e.g. initialized to NO_DATA. An example of this is shown in <FIG> by the greyed boxes for certain AP-leaf node links <NUM> in certain calibration periods <NUM>, e.g. AP0-Leaf1 has no prior historical data, therefore, each calibration period in the calibration window is defaulted to NODATA. At <NUM>, the decision on whether the leaf node will be used for sounding is deferred until the next calibration period (e.g. as described in <FIG>). On the other hand, if history is available for the AP-leaf node link, then at <NUM>, if the AP-leaf node link has a positive quality score (e.g. score <NUM> in <FIG>) and the AP is currently sounding less than its maximum number of leaf nodes (e.g. MAX_LEAFS_PER_AP <<NUM>), then at <NUM>, the AP starts sounding the leaf node immediately. Otherwise, in instances that the AP is already sounding the maximum number of leaf nodes, then at <NUM>, the decision on whether the leaf node will be used for sounding is deferred until the next calibration period (e.g. as described in <FIG>).

<FIG> is a block diagram showing an example process <NUM> for identifying a static leaf node. In some cases, one or more of the operations shown in <FIG> are implemented as processes that include multiple operations, sub-processes or other types of routines. In some cases, operations can be combined, performed in another order, performed in parallel, iterated, or otherwise repeated or performed another manner.

At <NUM>, presence information is obtained for a plurality of AP-leaf node links for a number of calibration periods. As described in <FIG>, the presence information in a calibration period refers to the number of times during a calibration period when an AP-leaf node link is active.

In an implementation, a leaf node may be associated with links to one or more APs. In some instances, the presence information represents, or includes data that indicates, the number of times an AP-leaf node link is active in the motion detection system during a calibration period (e.g. an hour or other period of time), such as presence information <NUM> described in <FIG>. In some cases, the AP is a hub for the motion detection system, and the AP obtains reports (e.g. network reports described in <FIG>), from one or more other APs in the motion detection system (e.g. AP nodes <NUM> described in <FIG>), containing presence information for each of the other AP-leaf node links.

At <NUM>, presence activity is determined for each AP-leaf node link based on its respective presence information. In some instances, an AP-leaf node link is determined to be present, or active, during a calibration period when presence information, e.g. presence information <NUM>, for the AP-leaf node link exceeds a presence threshold for the calibration period. For example, when the AP-leaf node link is active for a certain percentage of time in the calibration period (e.g. presence information >= PRES_THRES (e.g. <NUM>) in decision box <NUM> in <FIG>), then the AP-leaf node link is determined to have sufficient presence activity to be considered present, or active for that calibration period (e.g. as shown in <FIG>, the AP-leaf node links <NUM> that are determined to be present, or active, for a calibration period <NUM> are shown highlighted).

At <NUM>, static leaf nodes are identified based on the presence activity of the plurality of AP-leaf node links in a calibration window. In an implementation, the AP-leaf node link is determined to be static when the AP-leaf node link is present for a number of calibration periods equal to the range of the calibration periods (e.g. the range <NUM> for AP0-LeafO, AP1-Leaf0, and AP2-Leaf0, as illustrated in <FIG>). For example, the presence activity of the AP-leaf node link is determined by calculating points <NUM> for each AP-leaf node link over the calibration window, as described in <FIG>.

At <NUM>, the motion detection system is updated to use at least one of the identified static leaf nodes as a sounding node for motion detection. The motion detection system can then use signals communicated to or from the sounding nodes to obtain channel information (e.g., channel response information, beamforming state information, etc.) that is used for motion detection.

In an implementation, one of the identified static leaf nodes is selected to add as a sounding node to the motion detection system, and a zone creation event is transmitted to the user for the selected static leaf node. In some cases, a unique local zone associated with the selected static leaf node is marked. In some cases, a static leaf node is selected by deriving a link quality score for each static AP-leaf node link for the calibration window (e.g. the score for each calibration period are assigned in <FIG> and summed for the calibration window in the table in <FIG>). In some instances, the static AP-leaf node links are prioritized according to their respective link quality scores, and the static leaf node having a static AP-leaf node link with the highest link quality score is selected (e.g. AP0-LeafO in <FIG>). In some implementations, the maximum number of leaf nodes per AP are selected to sound for a next time period based on a link quality score and location of identified static leaf nodes. In some instances, a static leaf node timer is started after updating the motion detection system to use at least one of the identified static leaf nodes as a sounding node for the motion detection system (e.g. the global static leaf cooldown described in <FIG>).

<FIG> is a block diagram showing an example process <NUM> for classifying link quality of static leaf nodes. In some cases, one or more of the operations shown in <FIG> are implemented as processes that include multiple operations, sub-processes or other types of routines. In some cases, operations can be combined, performed in another order, performed in parallel, iterated, or otherwise repeated or performed another manner.

At <NUM>, static leaf nodes are identified based on presence activity of each leaf node in a calibration window. In some instances, the static leaf nodes may be identified as described in <FIG> and/or using the process described in <FIG>.

At <NUM>, a health score is determined for each AP-leaf node link of each static leaf node for each calibration window based on AP-leaf node link quality information. The AP-leaf node link quality information may include a success rate of sounding operations during a calibration period and a failure rate of sounding operations during a calibration period, as described in <FIG>. In some instances, the AP-leaf node link quality information may include an average link received signal strength indicator (RSSI), and a motion detection failure rate. In some implementations, determining a health score may include assigning each AP-leaf node link a classification based on its link quality information in each of the number of calibration periods. In some cases, the classification indicates a link quality is passing, noisy, or sleeping. A value may be assigned to each AP-leaf node link corresponding to its classification, and a health score is derived for each AP-leaf node link based on the assigned values in each of the number of calibration periods in the calibration window (e.g. as described in <FIG>). In an example, the health of the AP-link is passing when the success rate of sounding operations during the calibration period is above a first threshold and the failure rate of sounding operations during the calibration period is below a second threshold. In another example, the health of the AP-link is noisy when the success rate of sounding operations during the calibration period is below a third threshold and the failure rate of sounding operations during the calibration period is above a fourth threshold.

At <NUM>, one or more static leaf nodes are selected to use in the motion detection system based on the health scores of each AP-leaf node link. In some cases, during selection of static leaf nodes, an AP-leaf node link with a negative health score is disabled, and therefore, not considered. In some cases, an AP-leaf node link with a positive health score is prioritized with other AP-leaf node links having positive health scores. In some implementations, the static leaf node with the highest AP-leaf node link health score is selected to use for sounding with the motion detection system.

At <NUM>, the motion detection system is updated to use the selected one or more static leaf nodes for motion detection. In some instances, the motion detection system is updated by determining that the motion detection system allows adding a new leaf node at this time. Then a zone creation event is transmitted to the user (e.g., to a user device) for the selected fixed leaf node. In some implementations, the selected leaf node is marked as a unique local zone. In some implementations, the AP obtains presence and link quality information for a plurality of AP-leaf node links for the number of calibration periods, and initiates a calibration event for the calibration window. In some cases, the AP is a hub for the motion detection system and, the AP obtains reports from one or more other APs in the motion detection system containing presence and link quality information for each of the other AP-leaf node links.

<FIG> is a block diagram showing an example wireless communication device <NUM>. As shown in <FIG>, the example wireless communication device <NUM> includes an interface <NUM>, a processor <NUM>, a memory <NUM>, and a power unit <NUM>. For example, any of the wireless communication devices 102A, 102B, 102C in the wireless communication system <NUM> illustrated in <FIG> may include the same, additional or different components, and the components may be configured to operate as shown in <FIG> or in another manner. In some instances, the example wireless communications device may be configured as an access point (AP), or as a hub in a mesh network comprising multiple APs. In some implementations, the interface <NUM>, processor <NUM>, memory <NUM>, and power unit <NUM> of a wireless communication device are housed together in a common housing or other assembly. In some implementations, one or more of the components of a wireless communication device can be housed separately, for example, in a separate housing or other assembly.

The example interface <NUM> can communicate (receive, transmit, or both) wireless signals. For example, the interface <NUM> may be configured to communicate radio frequency (RF) signals formatted according to a wireless communication standard (e.g., Wi-Fi or Bluetooth). In some cases, the example interface <NUM> may be implemented as a modem. In some implementations, the example interface <NUM> includes a radio subsystem and a baseband subsystem. In some cases, the baseband subsystem and radio subsystem can be implemented on a common chip or chipset, or they may be implemented in a card or another type of assembled device. The baseband subsystem can be coupled to the radio subsystem, for example, by leads, pins, wires, or other types of connections.

In some cases, a radio subsystem in the interface <NUM> can include one or more antennas and radio frequency circuitry. The radio frequency circuitry can include, for example, circuitry that filters, amplifies or otherwise conditions analog signals, circuitry that up-converts baseband signals to RF signals, circuitry that down-converts RF signals to baseband signals, etc. Such circuitry may include, for example, filters, amplifiers, mixers, a local oscillator, etc. The radio subsystem can be configured to communicate radio frequency wireless signals on the wireless communication channels. As an example, the radio subsystem may include a radio chip, an RF front end, and one or more antennas. A radio subsystem may include additional or different components. In some implementations, the radio subsystem can be or include the radio electronics (e.g., RF front end, radio chip, or analogous components) from a conventional modem, for example, from a Wi-Fi modem, pico base station modem, etc. In some implementations, the antenna includes multiple antennas.

In some cases, a baseband subsystem in the interface <NUM> can include, for example, digital electronics configured to process digital baseband data. As an example, the baseband subsystem may include a baseband chip. A baseband subsystem may include additional or different components. In some cases, the baseband subsystem may include a digital signal processor (DSP) device or another type of processor device. In some cases, the baseband system includes digital processing logic to operate the radio subsystem, to communicate wireless network traffic through the radio subsystem, to detect motion based on motion detection signals received through the radio subsystem or to perform other types of processes. For instance, the baseband subsystem may include one or more chips, chipsets, or other types of devices that are configured to encode signals and deliver the encoded signals to the radio subsystem for transmission, or to identify and analyze data encoded in signals from the radio subsystem (e.g., by decoding the signals according to a wireless communication standard, by processing the signals according to a motion detection process, or otherwise).

In some cases, the example interface <NUM> can communicate wireless network traffic (e.g., data packets, including network reports described in <FIG>) and other types of signals (e.g., motion probe signals, such as sounding signals). In some instances, the interface <NUM> generates motion probe signals for transmission, for example, to probe a space to detect motion or lack of motion. In some implementations, the motion probe signals include standard signaling or communication frames that include standard pilot signals used in channel sounding (e.g., channel sounding for beamforming according to the IEEE <NUM>. 11ac-<NUM> standard). In some cases, the motion probe signals include reference signals known to all devices in the network. In some instances, the baseband subsystem may process received signals, for example, to detect connection and disconnection events from leaf nodes, to detect presence activity, and to detect motion of an object in a space. For example, the interface <NUM> may analyze aspects of standard signaling protocols (e.g., channel sounding for beamforming according to the IEEE <NUM>. 11ac-<NUM> standard, such as, based on the steering or other matrix generated) to detect changes in the channel as a result of motion in the space.

The example processor <NUM> can execute instructions, for example, to generate output data based on data inputs. The instructions can include programs, codes, scripts, modules, or other types of data stored in memory <NUM>, e.g. database <NUM>. Additionally or alternatively, the instructions can be encoded as pre-programmed or re-programmable logic circuits, logic gates, or other types of hardware or firmware components or modules. The processor <NUM> may be or include a general-purpose microprocessor, as a specialized co-processor or another type of data processing apparatus. In some cases, the processor <NUM> performs high level operation of the wireless communication device <NUM>. For example, the processor <NUM> may be configured to execute or interpret software, scripts, programs, modules, functions, executables, or other instructions stored in the memory <NUM>. In some implementations, the processor <NUM> be included in the interface <NUM>.

The example memory <NUM> may include computer-readable storage media, for example, a volatile memory device, a non-volatile memory device, or both. The memory <NUM> may include one or more read-only memory devices, random-access memory devices, buffer memory devices, or a combination of these and other types of memory devices. In some instances, one or more components of the memory can be integrated or otherwise associated with another component of the wireless communication device <NUM>. The memory <NUM> may store instructions that are executable by the processor <NUM>. For example, the instructions may include instructions for the example wireless communication device <NUM> (e.g. an AP) to obtain presence information for a plurality of AP-leaf node links for a number of calibration periods. The instructions, when executed, may cause the device to determine presence activity for each AP-leaf node link in each calibration period based on its respective presence information and identify static leaf nodes based on the presence activity for the plurality of AP-leaf node links in a calibration window, where the calibration window includes a number of the plurality of calibration periods. The instructions may further update the motion detection system to use at least one of the identified static leaf nodes as a sounding node for motion detection, such as through one or more of the operations as described in <FIG> or in the example process <NUM> described in <FIG>. In another example, the instructions may include instructions for the example wireless communication device <NUM> (e.g. an AP) to identify one or more static leaf nodes based on presence activity of each leaf node in a calibration window comprising a number of calibration periods. The instructions may further cause the device to determine a health score for each AP-leaf node link of each static leaf node for each calibration window based on AP-leaf node link quality information, select one or more of the static leaf nodes to use for sounding in the motion detection system based on the health scores for each of the AP-leaf node links. The instructions may further cause the device to update the motion detection system to use the selected one or more static leaf nodes for motion detection, such as through one or more of the operations as described in <FIG> or in the example process <NUM> described in <FIG>. In some instances, the memory <NUM> may include one or more instruction sets or modules, for example, to identify static leaf nodes <NUM>, select static leaf nodes <NUM>, and/or update new leaf nodes in the motion detection system <NUM>, comprising the instructions described above.

The example power unit <NUM> provides power to the other components of the wireless communication device <NUM>. For example, the other components may operate based on electrical power provided by the power unit <NUM> through a voltage bus or other connection. In some implementations, the power unit <NUM> includes a battery or a battery system, for example, a rechargeable battery. In some implementations, the power unit <NUM> includes an adapter (e.g., an AC adapter) that receives an external power signal (from an external source) and coverts the external power signal to an internal power signal conditioned for a component of the wireless communication device <NUM>. The power unit <NUM> may include other components or operate in another manner.

Some of the subject matter and operations described in this specification can be implemented in digital electronic circuitry, or in computer software, firmware, or hardware, including the structures disclosed in this specification and their structural equivalents, or in combinations of one or more of them. Some of the subject matter described in this specification can be implemented as one or more computer programs, i.e., one or more modules of computer program instructions, encoded on a computer storage medium for execution by, or to control the operation of, data-processing apparatus. A computer storage medium can be, or can be included in, a computer-readable storage device, a computer-readable storage substrate, a random or serial access memory array or device, or a combination of one or more of them. Moreover, while a computer storage medium is not a propagated signal, a computer storage medium can be a source or destination of computer program instructions encoded in an artificially generated propagated signal.

Some of the operations described in this specification can be implemented as operations performed by a data processing apparatus on data stored on one or more computer-readable storage devices or received from other sources.

A program can be stored in a portion of a file that holds other programs or data (e.g., one or more scripts stored in a markup language document), in a single file dedicated to the program, or in multiple coordinated files (e.g., files that store one or more modules, sub programs, or portions of code).

Processors suitable for the execution of a computer program include, by way of example, both general and special purpose microprocessors, and processors of any kind of digital computer. Generally, a processor will receive instructions and data from a read-only memory or a random-access memory or both. Elements of a computer can include a processor that performs actions in accordance with instructions, and one or more memory devices that store the instructions and data. A computer may also include, or be operatively coupled to receive data from or transfer data to, or both, one or more mass storage devices for storing data, e.g., magnetic disks, magneto optical disks, or optical disks. Moreover, a computer can be embedded in another device, e.g., a phone, an electronic appliance, a mobile audio or video player, a game console, a Global Positioning System (GPS) receiver, or a portable storage device (e.g., a universal serial bus (USB) flash drive). Devices suitable for storing computer program instructions and data include all forms of non-volatile memory, media and memory devices, including by way of example semiconductor memory devices (e.g., EPROM, EEPROM, flash memory devices, and others), magnetic disks (e.g., internal hard disks, removable disks, and others), magneto optical disks, and CD ROM and DVD-ROM disks. In some cases, the processor and the memory can be supplemented by, or incorporated in, special purpose logic circuitry.

A computer system may include a single computing device, or multiple computers that operate in proximity or generally remote from each other and typically interact through a communication network. Examples of communication networks include a local area network ("LAN") and a wide area network ("WAN"), an inter-network (e.g., the Internet), a network comprising a satellite link, and peer-to-peer networks (e.g., ad hoc peer-to-peer networks). A relationship of client and server may arise by virtue of computer programs running on the respective computers and having a client-server relationship to each other.

In a general aspect of the examples described here, a motion detection system identifies static leaf nodes for motion detection.

In a first example, a method according to claim <NUM> is provided. An access point (AP) obtains presence information for a plurality of AP-leaf node links, for a number of calibration periods. Presence activity is determined for each AP-leaf node link in each calibration period based on its respective presence information. Static leaf nodes are identified based on the presence activity for the plurality of AP-leaf node links in a calibration window, the calibration window comprising a number of the plurality of calibration periods. The motion detection system is updated to use at least one of the identified static leaf node as a sounding node for motion detection.

Implementations of the first example may include one or more of the following features. Identifying static leaf nodes comprises identifying leaf nodes that have fixed locations. A leaf node is associated with one or more AP-leaf node links. Presence information comprises the number of times an AP-leaf node link node is active in the motion detection system during a calibration period. Identifying static leaf nodes includes determining that an AP-leaf node link is present during a calibration period when presence activity for the AP-leaf node link exceeds a presence threshold during the calibration period, and determining an AP-leaf node link is static when the AP-leaf node link is present for a number of calibration periods equal to the range of the calibration periods. Updating the motion detection system includes selecting one of the identified static leaf nodes to add as a sounding node to the motion detection system, transmitting a zone creation event to the user for the selected static leaf node, and marking a unique local zone associated with the selected static leaf node. In some instances, selecting a static node includes deriving a link quality score for each static AP-leaf node link for the calibration window, prioritizing the static AP-leaf node links according to their respective link quality scores, and selecting the static leaf node having a static AP-leaf node link with the highest link quality score. Starting a static leaf node timer after updating the motion detection system to use at least one of the identified static leaf nodes as a sounding node for the motion detection system. The AP is a hub for the motion detection system, and the AP obtains reports from one or more other APs in the motion detection system containing presence information for each of the other AP-leaf node links.

In a second example, an access point (AP) of a motion detection system identifies one or more static leaf nodes based on presence activity of each leaf node in a calibration window, the calibration window comprising a number of calibration periods. A health score is determined for each AP-leaf node link of each static leaf node for each calibration window based on AP-leaf node link quality information. One or more of the static leaf nodes are selected to use for sounding in the motion detection system based on the health scores for each of the AP-leaf node links. The motion detection system is updated to use the selected one or more static leaf nodes for motion detection.

Implementations of the second example may include one or more of the following features. Identifying static leaf nodes comprises identifying leaf nodes that have fixed locations. The AP-leaf node link quality information includes one or more of a success rate of sounding operations during a calibration period, a failure rate of sounding operations during a calibration period, an average link received signal strength indicator (RSSI), and a motion detection failure rate. Determining a health score includes assigning each AP-leaf node link a classification based on its link quality information in each of the number of calibration periods, assigning a value to each AP-leaf node link corresponding to its classification, and deriving a health score for each AP-leaf node link based on the assigned values The classification indicates a link quality is passing, noisy, or sleeping in each of the number of calibration periods in the calibration window. The health of the AP-link is passing when the success rate of sounding operations during the calibration period is above a first threshold and the failure rate of sounding operations during the calibration period is below a second threshold, and the health of the AP-link is noisy when the success rate of sounding operations during the calibration period is below a third threshold and the failure rate of sounding operations during the calibration period is above a fourth threshold. Selecting static leaf nodes includes when an AP-leaf node link health score is negative, disabling the AP-leaf node link, when an AP-leaf node link health score is positive, prioritizing the AP-leaf node link with other AP-leaf node links having positive health scores, and then selecting the static leaf node with the highest AP-leaf node link health score to use for sounding with the motion detection system. Updating the motion detection system includes determining the motion detection system allows adding a new leaf node, transmitting a zone creation event to the user for the selected static leaf node, mark the selected leaf node as a unique local zone. Obtaining presence and link quality information for a plurality of AP-leaf node links for the plurality of calibration periods, and initiating a calibration event for the calibration window. The AP is a hub for the motion detection system, and the AP obtains reports from one or more other APs in the motion detection system containing presence information for each of the other AP-leaf node links.

In a third example, a non-transitory computer readable medium according to claim <NUM> is provided.

In a fourth example, a device for managing nodes in a motion detection system is provided according to claim <NUM>.

While this specification contains many details, these should not be understood as limitations on the scope of what may be claimed, but rather as descriptions of features specific to particular examples. Certain features that are described in this specification or shown in the drawings in the context of separate implementations can also be combined. Conversely, various features that are described or shown in the context of a single implementation can also be implemented in multiple embodiments separately or in any suitable subcombination.

Claim 1:
A method for managing nodes in a motion detection system, comprising:
obtaining, by an access point "AP" (<NUM>) of the motion detection system (<NUM>), presence information for a plurality of AP-leaf node links (<NUM>), the presence information obtained for a plurality of calibration periods;
determining presence activity for each AP-leaf node link (<NUM>) in each calibration period based on its respective presence information;
identifying static leaf nodes based on the presence activity for the plurality of AP-leaf node links (<NUM>) in a calibration window, the calibration window comprising a subset of the plurality of calibration periods, wherein the static leaf nodes are leaf nodes with fixed locations; and
updating the motion detection system (<NUM>) to use at least one of the identified static leaf node as a sounding node for motion detection.