SYSTEMS FOR OPTIMIZING POWER CONSUMPTION OF A WEARABLE DEVICE USING SENSOR-BASED DETERMINATIONS OF POSITIONAL STATES OF A PORTION OF THE WEARABLE DEVICE, AND METHODS OF USE THEREOF

Abstract

Methods and wearable devices for optimizing power consumption using sensor-based position and use determinations are described here. One example method is performed at a device that includes a first sensor configured to operate with a first power consumption rate and a second sensor configured to operate with a second power consumption rate. The method includes, while a component associated with the second sensor is in an inactive state, receiving first sensor data, and determining whether the first sensor data indicates movement of the device. The method also includes, when movement of the device is indicated, operating the second sensor in an active state. The method further includes, after activating the second sensor, when second sensor data from the second sensor indicates that the device has been placed on a user’s body, continuing to operate the second sensor in the active state.

Claims

1. A method of optimizing power consumption in a wearable device, the method comprising: at a wearable device that includes a first sensor configured to operate with a first power consumption rate and a second sensor configured to operate with a second power consumption rate that is greater than the first power consumption rate: while a component associated with the second sensor is in an inactive state: receiving, from the first sensor, first sensor data; determining whether the first sensor data indicates movement of the wearable device; in accordance with a determination that the first sensor data indicates movement of the wearable device: operating the component of the second sensor in an active state in which the component associated with the second sensor is used to actively sense or process sensor data; after activating the component associated with the second sensor, receiving, from the second sensor, second sensor data; and in accordance with a determination that the second sensor data indicates that the wearable device has been placed on a user’s body, continuing to operate the component associated with the second sensor in the active state.

2. The method of claim 1, wherein: the first sensor is an inertial measurement unit (IMU) sensor that is configured to detect data indicating movements of the wearable device; and the second sensor is an electromyography (EMG) sensor that is configured to detect neuromuscular signals indicating muscular movements of a user.

3. The method of claim 1, wherein: the first sensor is a hall effect sensor (HES) that is configured to be used to check if a display portion of the wearable device is attached or detached to a cradle portion of the wearable device; and the second sensor is photoplethysmography (PPG) sensor that is configured to be used to detect changes in blood flow in a user.

4. The method of claim 1, wherein: the first sensor is a hall effect sensor (HES) that is configured to be used to check if a display portion of the wearable device is attached or detached to a cradle; and the second sensor is an inertial measurement unit (IMU) sensor that is configured to detect data indicating movements of the wearable device.

5. The method of claim 1, wherein the first sensor has a first power consumption rate between 2 to 5 mW/s (milliwatts per second).

6. The method of claim 1, wherein the second sensor has a second power consumption rate between 7 to 17 mW/s.

7. The method of claim 1, wherein the component associated with the second sensor is operated in the active state for a period of time, and, after the period of time, the method further comprises: while the component associated with the second sensor is in the inactive state: receiving, from the first sensor, new first sensor data; determining whether the new first sensor data indicates movement of the wearable device; in accordance with a determination that the first sensor data indicates that the wearable device has not moved, continuing to operate the component of the second sensor in the inactive state.

8. The method of claim 1, wherein the continuing to operate the component associated with the second sensor in the active state includes continuing to operate the component associated with the second sensor in the active state until a deactivation trigger is detected.

9. The method of claim 8, wherein the deactivation trigger is detected when data from the first sensor that indicates that the wearable device has been removed from the user’s body.

10. The method of claim 8, wherein the deactivation trigger is detected when data from the second sensor indicates that the wearable device has been remove from the user’s body.

11. The method of claim 1, wherein the determination that the second sensor data indicates that the wearable device has been placed on the user’s body includes determining that the second sensor data, as compared to subsequent sensor data from the second sensor, reflects a change in data sensed by the second sensor.

12. The method of claim 11, wherein: the second sensor data indicates that one or more sensing channels of the second sensor are receiving data at or above a noise threshold, and the subsequent sensor data indicates that the one or more sensing channels of the second sensor are receiving data below the noise threshold.

13. The method of claim 1, wherein operating the component of the second sensor in the active state includes causing an interrupt signal to be sent to the component associated with the second sensor to cause it to transition from the inactive to the active state.

14. The method of claim 1, wherein determining whether the first sensor data indicates movement of the wearable device includes determining whether the movement is consistent with one or more known movements associated with the user placing the wearable device on the user’s body.

15. The method of claim 1, wherein the wearable device is a wrist-wearable device or a head-worn wearable device.

16. The method of claim 1, comprising: while the wearable device has been placed on the user’s body: in accordance with a determination that a display portion of the wearable device has been detached from a cradle, locking the wearable device until an authentication input is received.

17. The method of claim 16, wherein the authentication input is a biometric input.

18. The method of claim 17, wherein the biometric input is a predefined movement pattern of a finger of the user in front of a camera of the wearable device or an image of the finger of the user that is captured by the camera of the wearable device to detect at least one unique biometric characteristic of the finger.

19. A wrist-wearable device that includes a first sensor configured to operate with a first power consumption rate and a second sensor configured to operate with a second power consumption rate that is greater than the first power consumption rate, and the wrist-wearable device is configured to perform or cause performance of: while a component associated with the second sensor is in an inactive state: receiving, from the first sensor, first sensor data; determining whether the first sensor data indicates movement of the wearable device; in accordance with a determination that the first sensor data indicates movement of the wearable device: operating the component of the second sensor in an active state in which the component associated with the second sensor is used to actively sense or process sensor data; after activating the component associated with the second sensor, receiving, from the second sensor, second sensor data; and in accordance with a determination that the second sensor data indicates that the wearable device has been placed on a user’s body, continuing to operate the component associated with the second sensor in the active state.

20. A non-transitory, computer-readable storage medium including instructions that, when executed by a wrist-wearable device that includes a first sensor configured to operate with a first power consumption rate and a second sensor configured to operate with a second power consumption rate that is greater than the first power consumption rate, cause the wrist-wearable device to: while a component associated with the second sensor is in an inactive state: receive, from the first sensor, first sensor data; determine whether the first sensor data indicates movement of the wearable device; in accordance with a determination that the first sensor data indicates movement of the wearable device: operate the component of the second sensor in an active state in which the component associated with the second sensor is used to actively sense or process sensor data; after activating the component associated with the second sensor, receive, from the second sensor, second sensor data; and in accordance with a determination that the second sensor data indicates that the wearable device has been placed on a user’s body, continue to operate the component associated with the second sensor in the active state.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0073] For a better understanding of the various described embodiments, reference should be made to the Detailed Description below, in conjunction with the following drawings in which like reference numerals refer to corresponding parts throughout the figures.

[0074] FIGS. 1A-1C illustrate a scenario in which a component of a sensor of a wearable device (e.g., Sensor 2 in the illustrated examples) is moved from an inactive to an active state based on sensor-based state determinations, in accordance with some embodiments.

[0075] FIGS. 1D-1E illustrate a scenario in which the component of the sensor is moved from the active state back to the inactive state based on sensor-based determinations indicated that the wearable device has been removed from the wrist of the user (which can occur upon the removal occur or at a later time such as when the wearable device is determined to have been placed back on a table), in accordance with some embodiments.

[0076] FIGS. 2A-2G illustrate a wearable device that includes three sensors (e.g., three sensors selected from: an inertial measurement unit (IMU) sensor, electromyography (EMG) sensor, hall effect (HES) sensor, photoplethysmography (PPG), infrared (IR) sensor, etc.) and these figures also illustrate scenarios under what conditions components of those sensors are placed in active or inactive modes, in accordance with some embodiments.

[0077] FIG. 3 illustrates a state-transition diagram showing state transitions for a wearable device based on data from different sensors of the wearable device, in accordance with some embodiments.

[0078] FIG. 4 illustrates a flow chart for how a wearable device, using state determination logic, places components of sensors in active or inactive states in response to the wearable device being removed from a wrist of the user, in accordance with some embodiments.

[0079] FIGS. 5A-5D related to repurposing of a metallic data-transmission component to serve multiple purposes, including a block diagram of a wrist-wearable device system and on-board logic for using a metallic data-transmission component, in accordance with some embodiments. In particular, FIG. 5A illustrates a block diagram of a metallic data-transmission component (e.g., an NFC coil) that is configured to transmit data and also configured to detect capacitance of nearby surfaces or objects, in accordance with some embodiments. And FIGS. 5B-5D illustrate scenarios in which the metallic-data transmission component is used for the capacitance-sensing purpose, in accordance with some embodiments.

[0080] FIGS. 6A-6C illustrate an example wrist-wearable device, in accordance with some embodiments.

[0081] FIG. 7 is a block diagram of a wrist-wearable device system, in accordance with some embodiments.

[0082] FIG. 8 shows a block diagram of a representative computing system usable to implement the present disclosure, in accordance with some embodiments.

[0083] FIGS. 9A-9D illustrate an example flow chart of a method for activating and deactivating sensors of a wearable device, in accordance with some embodiments.

[0084] FIGS. 10A-10C illustrate an example flow chart of a method for placing components of sensors of a wearable device that includes three different sensors in active and inactive states, in accordance with some embodiments.

[0085] FIGS. 11A-11C illustrate an example flow chart of a method of repurposing a metallic data-transmission component (e.g., an NFC coil) in a wearable device to perform an additional function (e.g., a capacitive-sensing function), in accordance with some embodiments.

[0086] FIGS. 12A-12E illustrate a method of unlocking a wearable device using a gesture, in accordance with some embodiments.

[0087] In accordance with common practice, the various features illustrated in the drawings may not be drawn to scale. Accordingly, the dimensions of the various features may be arbitrarily expanded or reduced for clarity. In addition, some of the drawings may not depict all of the components of a given system, method or device. Finally, like reference numerals may be used to denote like features throughout the specification and figures.

DETAILED DESCRIPTION

[0088] Reference will now be made in detail to embodiments, examples of which are illustrated in the accompanying drawings. In the following detailed description, numerous specific details are set forth to provide a thorough understanding of the various described embodiments. It will be apparent to one of ordinary skill in the art that the various described embodiments may be practiced without these specific details. In some instances, well-known methods, procedures, components, circuits, and networks have not been described in detail so as not to unnecessarily obscure aspects of the embodiments.

[0089] As will become apparent to a person of skill in this art upon reading this disclosure, the various embodiments provide systems and methods of providing optimized power (activating and deactivating sensors as needed to conserve power) consumption of a wearable device based on determined states of the wearable device.

[0090] An example method of optimizing power consumption in a wearable device, is performed at a wearable device (or at least a portion of the wearable device) that includes a first sensor configured to operate with a first power consumption rate and a second sensor configured to operate with a second power consumption rate that is greater than the first power consumption rate. The method includes, while a component associated with the second sensor is in an inactive state: receiving from the first sensor, first sensor data, and the wearable device determines whether the first sensor data indicates movement of the wearable device. The method also includes, in accordance with a determination that the first sensor data indicates movement of the wearable device, operating the component of the second sensor in an active state in which the component associated with the second sensor is used to actively sense or process sensor data. The method includes, after activating the component associated with the second sensor, receiving, from the second sensor, second sensor data. The method further includes, that in accordance with a determination that the second sensor data indicates that the wearable device has been placed on a user’s body, continuing to operate the component associated with the second sensor in the active state.

[0091] Another example method uses three types of sensors to determine cradle, wrist, and activity states of a wrist-wearable device, and is performed at a wrist-wearable device that includes a capsule portion that is configured to be removably coupled to a cradle portion of the wrist-wearable device, the wrist-wearable device including a first sensor of a first sensor type and a second sensor of a second sensor type distinct from the first sensor type. The method includes, determining, using sensor data from the first sensor of the first sensor type, whether the capsule portion of the wrist-wearable device is coupled with the cradle portion of the wrist-wearable device. The method includes, in accordance with a determination that the data from the first sensor of the first sensor type indicates that the capsule portion of the wrist-wearable device is coupled with the cradle portion of the wrist-wearable device, obtaining data from the second sensor of the second sensor type. The method also includes, in accordance with a determination that the data from the second sensor of the second sensor type indicates that the wrist-wearable device is worn on a wrist of a user, monitoring data from a third sensor of a third sensor type that is distinct from the first and second sensor types to determine an activity being performed by the user while the wrist-wearable device is worn on the user’s wrist.

[0092] In yet another example method, the method includes repurposing a metallic data-transmission component included in an electronic device, and the electronic device includes one or more processors. The method includes that the electronic device receives, via the metallic data-transmission component, operational data indicative of a current operation state of the metallic data-transmission component. The method includes, determining, based on the operational data, whether data-transmission criteria are present. The method includes, in accordance with a determination that the data-transmission criteria are present, operating the metallic data-transmission component in a first mode. In some embodiments, while in the first mode, the metallic data-transmission component is configured to be used as antenna in conjunction with transferring data between the electronic device and at least one other electronic device using the metallic data-transmission component. The method also includes, in accordance with a determination that the data-transmission criteria are not present, operating the metallic data-transmission component in a second mode, in which the metallic data-transmission component functions as a capacitive sensor.

[0093] Small portable devices, such as wearable devices, need to optimize their power usage to provide the best user experience, i.e., long periods of continuous use without needing a charge. The following figures illustrate how a wearable device activates and deactivates various sensors to improve battery life of small wearable devices.

[0094] FIGS. 1A-1E illustrate activating and deactivating sensors based on different determined activity states, in accordance with some embodiments. FIG. 1A illustrates an interaction between a wearable device 100 resting on a table 102 (e.g., a non-biological surface) and a user 104. FIG. 1A shows the wearable device 100 having at least two sensors (e.g., inertial measurement unit (IMU) sensor, electromyography (EMG) sensor, hall effect (HES) sensor, photoplethysmography (PPG), infrared (IR) sensor, etc.), as indicated by the chart 106 corresponding to data from a first sensor and chart 108 corresponding to data from the second sensor. As shown by chart 106, the first sensor is currently in a powered-on state, and is recording data indicative of the wearable device being in an inactive state. This inactive state is determined by state determination logic 110, which determines, using (only) the first sensor data, at least that the wearable device 100 is off the wrist of the user 104, the wearable device 100 is stationary. When these criteria are met, the wearable device 100 is kept in a low power mode. In some embodiments, the low power mode includes not powering on one or more sensors (e.g., the second sensor is powered off, which is indicated by no data being recording in chart 108). In some embodiments, the first sensor always remains powered on when the wearable device 100 is powered on.

[0095] FIG. 1B illustrates that the user 104 has picked up the wearable device 100, but has yet to don the watch on their wrist. Using (only) the first sensor data as indicated by chart 106, the state determination logic 110 is configured to determine that the wearable device 100 is off the wrist of the user 104, and that the wearable device 100 is moving. Based on fist sensor data, the wearable device 100 is still kept in a low power mode. In some embodiments, the low power mode includes not powering on one or more sensors (e.g., the second sensor is powered off, which is indicated by no data being recording in chart 108). In some embodiments, the device watches the first sensor data for activity for a predetermined amount of time before activating the second sensor, to confirm the device has been placed on the wrist of the user. Stated another way, the state determination logic 110 may determine the device is no longer stationary, but cannot confirm if the wearable device is on a wrist of the user until another sensor has been activated (e.g., a sensor for detecting whether the watch is in contact with a biological source).

[0096] FIG. 1C shows that the user 104 has placed the wearable device 100 on their wrist. After a predetermined amount of time has elapsed and/or a movement threshold has been met, the second sensor, indicated by chart 108, is activated.

[0097] Using a combination of the first sensor data and the second sensor data, the state determination logic 110 is configured to determine whether the wearable device 100 is on the wrist of the user 104. In accordance with a determination by the state determination logic 110 that the wearable is on the wrist of the user 104, the wearable device 100 continues to keep the second sensor activated. In some embodiments, having the second sensor activated is referred to as a high-power mode. In some embodiments, the high-power mode includes activating one or more sensors that draw more power than other sensors. In some embodiments, the low power sensor (e.g., the first sensor) can be configured to shut-off when the higher-power sensor (e.g., the second sensor) is in use and would otherwise be supplying redundant data.

[0098] While FIGS. 1A-1C illustrate a process of confirming the first sensor data that indicates the wearable device 100 is on a wrist of a user, using second sensor data, however, it is also possible to activate the second sensor at different times. For example, in another embodiments, any kind of data received from the first sensor (e.g., for a period of time) can be sufficient for activating the second sensor, which is used to determine if the wearable device 100 is on a wrist of a user.

[0099] FIGS. 1D-1E illustrate a process for removing the wearable device 100 from the wrist of the user 104 and placing it back on the table 102, in accordance with some embodiments. FIG. 1D shows that the user 104 has removed the wearable device 100 from their wrist, but is holding it in their hand. As a result, the second sensor is no longer able to retrieve the same data it was previously receiving (e.g., biometric information), as indicated by chart 108 showing a flat line. In some embodiments, the device watches the second sensor data for inactivity for a predetermined amount of time before deactivating the second sensor. In other words, when there is a lack of data coming from the second sensor (e.g., indicating the wearable device is off the wrist of the user 104), it remains powered on for a predetermined amount of time before determining it is no longer being used. For example, user 104 may be adjusting the wearable device 100 on their wrist, but not completely removing it. Thus, using a combination of the first sensor data and the second sensor data, the state determination logic 110 is configured to determine that the wearable device 100 is off the wrist of the user 104, the wearable device 100 is moving.

[0100] FIG. 1E shows that the user 104 has placed the wearable device 100 on the table 102 and is no longer moving. Chart 108 also shows that the second sensor has been placed in a low power mode, as the wearable device 100 has determined it is no longer needs to be activated while being placed on a table 102 (e.g., off the wrist of a user). Using a combination of the first sensor data and/or the second sensor data, the state determination logic 110 is configured to determine that the wearable device 100 is off the wrist of the user 104 aid is stationary. In accordance with a determination that the wearable device is off the wrist of the user and is stationary, the wearable device 100 switches to a low power mode, that includes powering off the second sensor to conserve battery of the wearable device 100. In some embodiments, the low power mode operates at a consumption rate between 2-5 mW/s and the high-power mode operates at 5-17 mW/s.

[0101] While FIGS. 1D-1E powering off the second sensor when it is put on the table, it is also possible that the second sensor is deactivated at a different time. For example, the second sensor can be deactivated when the wearable device 100 is removed from the wrist of the user. In other words, the second sensor can be deactivated while being in the hand of the user, but not yet placed on non-biological surface (e.g., a table).

[0102] FIGS. 2A-2D illustrate a wearable device 100 that includes three sensors (e.g., three sensors selected from: an inertial measurement unit (IMU) sensor, electromyography (EMG) sensor, hall effect (HES) sensor, photoplethysmography (PPG), infrared (IR) sensor, etc.,) and under what conditions they are activated or deactivated, in accordance with some embodiments. FIG. 2A illustrates that the wearable device 100 is composed of two parts a cradle 200 and a watch capsule 202, collectively referred to as the wearable device 100. As shown in FIG. 2A, the watch capsule 202 is disconnected from the cradle 200 that is presently on the wrist of the user. While the watch capsule 202 is not connected to the cradle 200, it can be placed on a charging pad 204. As shown in FIG. 2A, while the watch capsule 202 is on the charging pad 204, the watch capsule 202 using its state determination logic 206 to determine that the watch capsule 202 is off the wrist of a user 208, the watch capsule 202 is stationary, the watch capsule 202 is on the charging pad 204. In accordance with a determination that the watch capsule is capsule is off the wrist of a user 208, (i) the watch capsule 202 is stationary, (ii) and/or the watch capsule 202 is on the charging pad 204, the watch capsule operates in a low power mode (e.g., one or more sensors of the watch capsule and/or cradle are not in a powered-on state). FIG. 2A also shows that, in chart 210, that a constant data point (or a specific pattern) is being recorded by the watch capsule 202, which indicates that the watch capsule 202 is placed on the charging pad 204 (e.g., a hall effect sensor indicates that a magnetic field is present and constant near the watch capsule 202).

[0103] FIG. 2B illustrates the user 208 picking up the watch capsule 202, but not yet attaching the watch to cradle 200. Chart 210 indicates that in response to the capsule being removed from the charging the pad, the data being recorded from the first sensor has changed. Using the state determination logic, the watch capsule determines, based at least on the data from the first sensor, that the watch capsule 202 is off the charging pad 204. In response to determining that the watch capsule 202 is off the charging pad 204, the watch capsule activates the second sensor, indicated by chart 212, which can be configured to determine whether the watch capsule 202 is placed on a wrist of a user 208. As shown in chart 212, the second sensor is powered on (e.g., a medium power mode) and is outputting data (e.g., one of movement data, proximity data, or biometric data). Using data from at least the first and/or second sensor the state determination logic 206 is able to determine that (i) the watch capsule is off the wrist of a user 208, (ii) the watch capsule 202 is moving, and (iii) the watch capsule 100 is off the charging pad 204.

[0104] FIG. 2C illustrates the user having connected the watch capsule 202 to the cradle 200. The first sensor, as illustrated by chart 210, is configured to provide data that the state determination logic 206 can use to determine if the watch capsule 202 has been placed on the cradle. FIG. 2C shows that in accordance with a determination that first sensor provides data that indicates that the watch capsule 202 is connected to the cradle 200, the state determination logic 206 provides instructions for activating the second sensor to confirm whether the capsule 202 and cradle 200 are on a wrist of a user 208.

[0105] In some embodiments, the chart 210 shows another magnetic field being detected by a hall effect sensor. In some embodiments, the hall effect sensor is relied on to improve the security of the wearable device, by locking the device once the magnetic field is no longer present (e.g., when the capsule portion of the wearable device is detached from the cradle portion of the wearable device). By immediately locking, it ensures that if someone were to steal the capsule portion, they would not be able to access data, unless they unlocked the capsule device by providing authenticating information.

[0106] FIG. 2D shows the user 208 having connected the watch capsule 202 to the cradle 200, and the chart 212 indicating a pattern associated with capsule 202 to the cradle 200 being on the wrist of the user. In other words, chart 212 shows that the second sensor records a different pattern when the watch capsule 202 is on the wrist of the user 208 and/or connected to the cradle 200 than when the watch capsule 202 is not on the wrist of the user 208 and/or not connected to the cradle 200. Using data from at least the first and/or second sensor, the state determination logic 206 determines: (i) that the watch capsule 202 is on the wrist of a user 208, (ii) the watch capsule 202 is moving, and (iii) the watch capsule 202 is off the charging pad 204. In response to the state determination logic 206 determining that the watch is on the wrist of the user, the state determination logic 206 provides instructions for activating a third sensor, as indicated by the data in chart 214 being recorded. In some embodiments, a third sensor is configured to detect an activity being performed by the user (e.g., exercising, sleeping, etc.,). In some embodiments, the third sensor is an inertial movement unit (IMU).

[0107] FIG. 2E shows an alternative configuration, where the third sensor is an electromyography (EMG) sensor that measure electrical signals generated by a user. As indicated by the data in chart 214, there can be multiple sensors that have their data compiled together (e.g., multiple electrodes).

[0108] FIGS. 2F-2G illustrate that in some embodiments, the third sensor provides data for determining whether the user is performing a certain activity (e.g., exercising or sleeping).

[0109] FIG. 2F illustrates that the state determination logic 206 has determined that the user has begun exercising, based at least on the data from the three sensors. FIG. 2F also shows that in accordance with a determination that the user is exercising the second sensor operates at a first frequency (e.g., 15 Hz and 50 Hz).

[0110] FIG. 2G shows that the state determination logic 206 has determined that the user is sleeping, based on at least data recorded by the one or more sensors. In some embodiments, the second and third sensor provide data for determining whether the user is performing a certain activity (e.g., exercising or sleeping). FIG. 2G also shows that in accordance with a determination that the user is sleeping the second sensor operates at a second frequency (e.g., 100 Hz and 150 Hz).

[0111] FIG. 3 illustrates a flow chart 300 for when to enabled sensors on a wearable device (e.g., wearable device 100 or cradle 200 and a watch capsule 202) based on the devices activity status, in accordance with some embodiments. FIG. 3 shows, in step 302, that when the wearable device is on a charging pad, the wearable device using state determination logic has the rear-facing camera powered off, the front-facing camera powered on, and an optional analog front-end (AFE) powered off.

[0112] FIG. 3 also shows that the wearable device uses data from an optional hall effect sensor (HES) to determine if the device is on or off the cradle (e.g., a cradle 200). When the hall-effect sensor provides data indicating that the HES is off the cradle, as shown in step 304, the logic controlling the wearable device activates the rear-facing camera, deactivates the front-facing camera, and enables an optional AFE sensor, specifically the ambient light sensor and infrared sensor of the AFE.

[0113] When the hall-effect sensor provides data indicating that the HES is on the cradle, as shown in step 306, the logic controlling the wearable device deactivates the rear-facing camera, enables the front-facing camera, and AFE remains (the ambient light sensor and infrared sensor of the AFE remain enabled).

[0114] Alternatively, when a wearable device is not equipped with a HES, it can rely on inertial measurements sourced from an inertial measurement unit to determine if the wearable device is on or off the cradle.

[0115] Step 308A and 308B illustrate two possible paths the logic of the wearable device can follow, based on the configuration of the wearable device. Step 308A illustrates a first path that the state determination logic follows when a device is equipped with an IMU sensor and an EMG sensor, but not a AFE or a HES. Step 308B illustrates another branch of logic for a wearable device that includes an AFE and a HES.

[0116] In step 308A, the state determination logic uses IMU sensor information to detect active movement of the wearable device to determine whether the watch is on or off the wrist of a user. In some embodiments, the IMU data corresponds to a predetermined pattern that indicates a wrist off state and/or an off-charger state. After the state determination logic has determined that the wearable device is off wrist of a user, using data from the IMU sensor, the state determination logic activates the EMG. Using data from the activated EMG, the state determination logic determines, as shown in step 310, that the wearable device is on a wrist of a user.

[0117] Step 308B illustrates another branch of logic for a wearable device that includes an AFE and a HES. As shown in step 308B, when the data from the HES indicates that is off cradle, the state determination logic initiates an infrared (IR) sensor to determine if the watch is proximate to a wrist of a user.

[0118] Step 312 shows that when the state determination logic determines, using data from the IR sensor, that the wearable device is proximate to something, the state determination logic causes a PPG and/or EMG sensor to be activated. The PPG and/or EMG sensors are capable of providing data that can be used to determine if the wearable device is on a wrist of a user.

[0119] After step 312, the state determination logic can follow two branches depending on what the data from the ppg and/or EMG sensor indicate. Step 314 indicates the first logical branch, which is followed when the state determination logic determines, using data from the PPG and/or EMG sensor to determine if the wearable device is proximate to a wrist or something else (e.g., a tabletop, floor, desk mat (e.g., a surface that could be interpreted as wrist, unless a biometric sensor is used to confirm), etc.). Once the state determination logic determines, using data from the PPG and/or EMG sensor, that the wearable device is on a surface other than a wrist of the user, it forgoes any further operation until it detects that is on a wrist of a user.

[0120] Step 316 indicates the second logical branch, which is followed when the state determination logic determines, using data from the PPG and/or EMG sensor(s), that the wearable device is on a user’s wrist. When the wearable device is on the wrist of the user, the PPG and/or EMG sensor(s) remain operational, and track biometric data. In some embodiments, the sensors run at frequency of 25 Hz. In some embodiments, the frequency is variable depending on determined activity states and runs between 20 Hz-200 Hz.

[0121] After it has been determined that the wearable device has been place on a wrist of a user, the state determination logic then determines, using data from an IMU sensor, an activity being performed by a user. As shown in step 318, when the IMU sensor provides data that indicates the user is sleeping (e.g., the data provided by the IMU corresponds to a predetermined pattern that indicates a user wearing the wearable device is sleeping), the rear-facing camera is disabled, the front-facing camera is disabled, the red LED, the green LED, and the IR on the AFE are enabled, and the sensors are configured to operate at 128 Hz. Step 320 indicates another logical branch using the IMU sensor. When the IMU sensor provides data that indicates that the user is exercising (e.g., the data provided by the IMU corresponds to a predetermined pattern that indicates a user wearing the wearable device is exercising), one or more sensors are operated at 25 Hz, the green LED, and the IR on the AFE are enabled.

[0122] FIG. 4 illustrates a flow chart 400 for how a wearable device, using state determination logic, activates and deactivates sensors in response to the wearable device being removed from a wrist of the user, in accordance with some embodiments. FIG. 4 starts with first detecting motion 402, using one or more sensors (e.g., an IMU sensor). FIG. 4 shows at step 404, in accordance with a determination that the no motion is detected (or a motion level that does not exceed a threshold amount of movement) the wearable device remains asleep. Step 406 shows that, in accordance with a determination that motion is detected (e.g., motion meets or exceeds a minimum motion threshold) the wearable device activates its proximity mode for determining whether the wearable device is proximate to a possible wrist and/or another surface. Step 408 then checks whether a wearable device has been proximate to a possible wrist and/or other surface for threshold amount of time. Step 410 indicates the procedure for the state determination logic to follow when the wearable device has not been proximate to a possible wrist and/or other surface for threshold amount of time. The wearable device is configured to either (i) revert to a sleep mode, or (ii) reinitiate the proximity mode. In some embodiments, the device is put to sleep when no surface is detected in the proximity mode, and the device reinitiates the proximity mode when the wearable device detects a surface for some amount of time, but does not meet or exceed the threshold amount of time.

[0123] FIG. 4 shows at step 412 that, in response to the wearable device being proximate to a possible wrist and/or other surface for threshold amount of time, the state determination logic initiates the ScD algorithm to detect live tissue (e.g., a wrist of a user). In some embodiments, the ScD algorithm is illustrated by the flow chart shown in FIG. 3. Step 414 illustrates possible steps to follow when live tissue is detected. First, if no live tissue is detected, as indicated in step 416, then the state determination logic returns to step 408 (described above). In some embodiments, if live tissue is detected, but does not meet or exceed the minimum time threshold, the wearable device is configured to check for live tissue again (i.e., repeat step 414). Step 418 shows that, in accordance with a determination that the live tissue is detected (e.g., live tissue is detected for a time period long enough to meet or exceed a time threshold), the state determination logic is configured to initiate a PPG heart rate monitor sensor, and s ScD mode.

[0124] The following steps in FIG. 4 describe how the wearable device detects and handles the wearable device being removed from the wrist of a user. Step 420 shows that the wearable device relies on the ScD to detect whether the wearable device is off the wrist of the user. Step 420 also shows that, in accordance with a determination that the wearable device is not off the wrist of the user, the wearable device continues to operate the PPG heart rate sensor (i.e., reverts back to step 418).

[0125] Step 422 indicates that a proximity sensor is used to confirm whether an interrupt in receipt of biometric information from a biometric sensor is a wrist off event. In accordance with a determination that the interrupt occurs, and the proximity sensor indicates that the wearable device is not proximate to a surface (e.g., is beyond a threshold distance away from a surface), the state determination logic confirms that the wearable device is off the wrist of a user. Step 422 also shows that in accordance with a determination that the interrupt occurs, and the proximity sensor indicates that the wearable device is proximate to a surface (e.g., is not beyond a threshold distance away from a surface), the state determination logic confirms that the wearable device is still potentially on the wrist of a user and reverts to step 418.

[0126] FIGS. 5A-5C illustrate using a metallic data-transmission component (e.g., an NFC coil) that is configured to transmit data and also configured to detect capacitance of nearby surfaces, in accordance with some embodiments.

[0127] FIG. 5A is a block diagram of a wrist-wearable device system 100 and on-board logic for using a metallic data-transmission component, according to at least one embodiment of the present disclosure. The device 100 includes a metallic data-transmission component 900 (e.g., a communication device, such as an NFC 715, discussed in reference to FIG. 7). The metallic data-transmission component 900 can be configured to provide a dual purpose. The first purposed being to communicate as a near field communication component, and the second purposes being a component for detecting capacitance of a surrounding object (e.g., FIGS. 5A-5C illustrate an example of how the wearable device detects capacitance using the metallic data-transmission component 900 to determine whether the wearable device is on a wrist, off a wrist, or on a hand of a user).

[0128] FIG. 5A also includes a switch 902 for connecting sensor processing module 904 to the metallic data-transmission component 900 to be used as a capacitive sensor. Alternatively, the switch 902 also connects to NFC subsystem 906 to use the metallic data-transmission component 900 as a near-field communication radio.

[0129] FIG. 5B illustrates a graph 502 that shows capacitance sensed by an NFC coil over time. FIG. 5A illustrates that the capsule portion 202 of the wearable device is coupled to the cradle 200. When the capsule portion 202 of the wearable device is coupled to the cradle 200 and on the wrist of the user, a low level of capacitance is detected by an NFC coil 504 of the wearable device (also referred to as metallic data-transmission component 900 in FIG. 5A).

[0130] FIG. 5C illustrates capsule portion 202 being detached from the cradle portion 200, and in the hand of the user 104. As shown in graph 502 of FIG. 5C the sensed capacitance increases when the user holds the capsule portion 202 in their hand. This increased capacitance occurs as a result of the increased skin contact compared to wearing the capsule portion 202 on the user’s wrist.

[0131] FIG. 5D illustrates capsule portion 202 being placed on the charging pad 204 and no longer in contact with the user 104. As shown in graph 502 of FIG. 5D the sensed capacitance decreases when the user is no longer holding the capsule portion 202 in their hand. This decreased capacitance occurs as a result of there being no skin contact compared wearing the capsule portion 202 on the wrist of the user 104 or being placed in a hand of a user 104.

[0132] FIGS. 6A-6C illustrate an example wrist-wearable device 650, in accordance with some embodiments. The wearable device 100 shown and described in reference to FIGS. 1A-5C can be an instance of the wearable device 650 (also referred to as wrist-wearable device 650), including capsule portion 202 and cradle portion 200, such that capsule portion 202 and cradle portion 200 (also referred to as band portion 200) should be understood to have the features of the capsule portion 654 (also referred to as watch body 654) and band portion 662 (also referred to as watch body 662) of wearable device 650 and vice versa. FIG. 6A illustrates a perspective view of the wrist-wearable device 650 that includes a capsule portion 654 decoupled from a band portion 662. Capsule portion 654 and band portion 662 can have a substantially rectangular or circular shape and can be configured to allow a user to wear the wrist-wearable device 650 on a body part (e.g., a wrist). The wrist-wearable device 650 can include a retaining mechanism 663 (e.g., a buckle, a hook and loop fastener, etc.) for securing band portion 662 to the user’s wrist. The wrist-wearable device 650 can also include a coupling mechanism 660 (e.g., a cradle) for detachably coupling the capsule portion 654 (via a coupling surface 656 of the watch body 654) to band portion 662.

[0133] Functions executed by the wrist-wearable device 650 can include, without limitation, display of visual content to the user (e.g., visual content displayed on display screen 115), sensing user input (e.g., sensing a touch on button 658, sensing biometric data on sensor 664, sensing neuromuscular signals on neuromuscular sensor 665, etc.), messaging (e.g., text, speech, video, etc.), image capture, wireless communications (e.g., cellular, near field, WiFi, personal area network, etc.), location determination, financial transactions, providing haptic feedback, alarms, notifications, biometric authentication, health monitoring, sleep monitoring, etc. The wrist-wearable device 650 is configured to perform, without limitation, the functions described above in reference to FIGS. 1A-5C, such that the wrist-wearable device is able to make determinations about whether to make modifications to operating characteristics based on sensor data from at least two different sensors (as described above in reference to FIGS. 1A-5C) and can then, if it is determined that modifications to operating characteristics are needed, proceed to modify the operating characteristics based on the approaches and techniques. These functions can be executed independently in watch body 654, independently in watch band 662, and/or in communication between watch body 654 and watch band 662. In some embodiments, functions can be executed on the wrist-wearable device 650 in conjunction with an artificial-reality environment which includes, but is not limited to, virtual-reality (VR) environments (including non-immersive, semi-immersive, and fully-immersive VR environments), augmented-reality environments (including marker-based augmented-reality environments, markerless augmented-reality environments, location-based augmented-reality environments, and projection-based augmented-reality environments), hybrid reality, and other types of mixed-reality environments. As the skilled artisan will appreciate upon reading the descriptions provided herein, the novel wearable devices described herein can be used with any of these types of artificial-reality environments.

[0134] The watch band 662 can be configured to be worn by a user such that an inner surface of the watch band 662 is in contact with the user’s skin. When worn by a user, sensor 664 is in contact with the user’s skin. The sensor 664 can be a biosensor that senses a user’s heart rate, saturated oxygen level, temperature, sweat level, muscle intentions, or a combination thereof (any of these can be examples of the biometric sensor described above and used in conjunction with the positional-state determinations described herein, and can also be associated with the capsule portion instead of the band portion). The watch band 662 can include multiple sensors 664 that can be distributed on an inside and/or an outside surface of the watch band 662. Additionally, or alternatively, the watch body 654 can include the same or different sensors than the watch band 662 (or the watch band 662 can include no sensors at all in some embodiments). For example, multiple sensors can be distributed on an inside and/or an outside surface of watch body 654. The watch body 654 (e.g., a capsule portion) can include, without limitation, a magnetic field sensor 120 (as shown in FIG. 1A), antenna return loss sensor 124, front-facing image sensor 625A and/or rear-facing image sensor 625B, a biometric sensor (e.g., biometric sensor 126, as shown in FIG. 1A), an IMU, a heart rate sensor, a saturated oxygen sensor, a neuromuscular sensor(s), an altimeter sensor, a temperature sensor, a bioimpedance sensor, a pedometer sensor, an optical sensor, a touch sensor (e.g., capacitive sensor 122 shown in FIG. 1A), a sweat sensor, a sensor or component configured to detect capacitance, etc. The sensor 664 can also include a sensor that provides data about a user’s environment including a user’s motion (e.g., an IMU), altitude, location, orientation, gait, or a combination thereof. The sensor 664 can also include a light sensor (e.g., an infrared light sensor, a visible light sensor) that is configured to track a position and/or motion of watch body 654 and/or watch band 662. Watch band 662 can transmit the data acquired by the sensor 664 to watch body 654 using a wired communication method (e.g., a UART, a USB transceiver, etc.) and/or a wireless communication method (e.g., near field communication, Bluetooth TM, etc.). Watch band 662 can be configured to operate (e.g., to collect data using sensor 664) independent of whether watch body 654 is coupled to or decoupled from watch band 662.

[0135] The watch band 662 and/or watch body 654 can include a haptic device 666 (e.g., a vibratory haptic actuator) that is configured to provide haptic feedback (e.g., a cutaneous and/or kinesthetic sensation, etc.) to the user’s skin. The sensor 664 and/or haptic device 666 can be configured to operate in conjunction with multiple applications including, without limitation, health monitoring, social media, game playing, and artificial reality (e.g., the applications associated with artificial reality).

[0136] In some examples, the watch band 662 can include a neuromuscular sensor 665 (e.g., an electromyography (EMG) sensor, a mechanomyogram (MMG) sensor, a sonomyography (SMG) sensor, etc.). Neuromuscular sensor 665 can sense a user’s intention to perform certain motor actions (this sensor 665 can be another example of a sensor used as the biometric sensor in conjunction with the positional-state determinations described herein). The sensed muscle intention can be used to control certain user interfaces displayed on the display 115 of the device 102 and/or can be transmitted to device responsible for rendering an artificial-reality environment (e.g., a head-mounted display) to perform an action in an associated artificial-reality environment, such as to control the motion of a virtual device displayed to the user.

[0137] Signals from neuromuscular sensor 665 can be used to provide a user with an enhanced interaction with a physical object and/or a virtual object in an artificial-reality application generated by an artificial-reality system (e.g., user interface objects presented on the display 115, or another computing device (e.g., a head-mounted display)). Signals from neuromuscular sensor 665 can be obtained (e.g., sensed and recorded) by one or more neuromuscular sensors 665 of watch band 662. Although FIG. 6A shows one neuromuscular sensor 665, watch band 662 can include a plurality of neuromuscular sensors 665 arranged circumferentially on an inside surface of watch band 662 such that the plurality of neuromuscular sensors 665 contact the skin of the user. Watch band 662 can include a plurality of neuromuscular sensors 665 arranged circumferentially on an inside surface of watch band 662. Neuromuscular sensor 665 can sense and record neuromuscular signals from the user as the user performs muscular activations (e.g., movements, gestures, etc.). The muscular activations performed by the user can include static gestures, such as placing the user’s hand palm down on a table; dynamic gestures, such as grasping a physical or virtual object; and covert gestures that are imperceptible to another person, such as slightly tensing a joint by co-contracting opposing muscles or using sub-muscular activations. The muscular activations performed by the user can include symbolic gestures (e.g., gestures mapped to other gestures, interactions, or commands, for example, based on a gesture vocabulary that specifies the mapping of gestures to commands).

[0138] The wrist-wearable device 650 can include a coupling mechanism (also referred to as a cradle) for detachably coupling watch body 654 to watch band 662. A user can detach watch body 654 from watch band 662 to reduce the encumbrance of the wrist-wearable device 650 to the user. The wrist-wearable device 650 can include a coupling surface 656 on the watch body 654 and/or coupling mechanism(s) 660 (e.g., a cradle, a tracker band, a support base, a clasp). A user can perform any type of motion to couple watch body 654 to watch band 662 and to decouple watch body 654 from watch band 662. For example, a user can twist, slide, turn, push, pull, or rotate watch body 654 relative to watch band 662, or a combination thereof, to attach watch body 654 to watch band 662 and to detach watch body 654 from watch band 662.

[0139] As shown in the example of FIG. 6A, watch band coupling mechanism 660 can include a type of frame or shell that allows watch body 654 coupling surface 656 to be retained within watch band coupling mechanism 660. Watch body 654 can be detachably coupled to watch band 662 through a friction fit, magnetic coupling, a rotation-based connector, a shear-pin coupler, a retention spring, one or more magnets, a clip, a pin shaft, a hook and loop fastener, or a combination thereof. In some examples, watch body 654 can be decoupled from watch band 662 by actuation of release mechanism 670. The release mechanism 670 can include, without limitation, a button, a knob, a plunger, a handle, a lever, a fastener, a clasp, a dial, a latch, or a combination thereof.

[0140] The wrist-wearable device 650 can include a single release mechanism 670 or multiple release mechanisms 670 (e.g., two release mechanisms 670 positioned on opposing sides of the wrist-wearable device 650 such as spring-loaded buttons). As shown in FIG. 6A, the release mechanism 670 can be positioned on watch body 654 and/or watch band coupling mechanism 660. Although FIG. 6A shows release mechanism 670 positioned at a corner of watch body 654 and at a corner of watch band coupling mechanism 660, the release mechanism 670 can be positioned anywhere on watch body 654 and/or watch band coupling mechanism 660 that is convenient for a user of wrist-wearable device 650 to actuate. A user of the wrist-wearable device 650 can actuate the release mechanism 670 by pushing, turning, lifting, depressing, shifting, or performing other actions on the release mechanism 670. Actuation of the release mechanism 670 can release (e.g., decouple) the watch body 654 from the watch band coupling mechanism 660 and the watch band 662 allowing the user to use the watch body 654 independently from watch band 662. For example, decoupling the watch body 654 from the watch band 662 can allow the user to capture images using rear-facing image sensor 625B.

[0141] FIG. 6B is a side view and FIG. 6C is a perspective view of another example of the wrist-wearable device 650. The wrist-wearable devices 650 of FIGS. 6B and 6C can include a watch body interface 680 (another example of a cradle for the capsule portion of the device 102). The watch body 654 can be detachably coupled to the watch body interface 680. Watch body 654 can be detachably coupled to watch body interface 680 through a friction fit, magnetic coupling, a rotation-based connector, a shear-pin coupler, a retention spring, one or more magnets, a clip, a pin shaft, a hook and loop fastener, or a combination thereof.

[0142] In some examples, watch body 654 can be decoupled from watch body interface 680 by actuation of a release mechanism. The release mechanism can include, without limitation, a button, a knob, a plunger, a handle, a lever, a fastener, a clasp, a dial, a latch, or a combination thereof. In some examples, the wristband system functions can be executed independently in watch body 654, independently in watch body interface 680, and/or in communication between watch body 654 and watch body interface 680. Watch body interface 680 can be configured to operate independently (e.g., execute functions independently) from watch body 654. Additionally, or alternatively, watch body 654 can be configured to operate independently (e.g., execute functions independently) from watch body interface 680. Watch body interface 680 and/or watch body 654 can each include the independent resources required to independently execute functions. For example, watch body interface 680 and/or watch body 654 can each include a power source (e.g., a battery), a memory, data storage, a processor (e.g., a CPU), communications, a light source, and/or input/output devices.

[0143] In this example, watch body interface 680 can include all of the electronic components of watch band 662. In additional examples, one or more electronic components can be housed in watch body interface 680 and one or more other electronic components can be housed in portions of watch band 662 away from watch body interface 680.

[0144] FIG. 7 is a block diagram of a wrist-wearable device system 700, according to at least one embodiment of the present disclosure. The device 100 described in detail above is an example wrist-wearable device system 700, so device 100 will be understood to include the components shown and described for system 700 below. The wrist-wearable device system 700 can have a split architecture (e.g., a split mechanical architecture, a split electrical architecture) between a watch body 704 (e.g., a capsule 654/ capsule portion 202) and a watch band 712 (e.g., a band portion 662/ cradle portion 200), which was described above in reference to FIGS. 6A-6C. Each of watch body 704 and watch band 712 can have a power source, a processor, a memory, sensors, a charging device, and a communications device that enables each of watch body 704 and watch band 712 to execute computing, controlling, communication, and sensing functions independently in watch body 704, independently in watch band 712, and/or in communication between watch body 704 and watch band 712.

[0145] For example, watch body 704 can include capacitive sensor 122 (or a device such as an NFC sensor 715 that can in some embodiments act as a capacitive sensor), magnetic field sensor 120, antenna return-loss (RL) sensor 124, biometric sensor 126, battery 728, CPU 726, storage 702, heart rate sensor 758, EMG sensor 746, SpO.sub.2 sensor 754, altimeter 748, IMU 742, random access memory 703, charging input 730 and communication devices NFC 715, LTE 718, and WiFi/Bluetooth 720. Similarly, watch band 712 can include battery 738, microcontroller unit 752, memory 750, heart rate sensor 758, EMG sensor 746, SpO.sub.2 sensor 754, altimeter 748, IMU 742, charging input 734 and wireless transceiver 740. Memory 750 (and/or storage 702) may further include device state table, an example of which is shown in FIGS. 1A-2G and 5A-5C. In some examples, a level of functionality of at least one of watch band 712 or watch body 704 can be modified when watch body 704 is detached from watch band 712. The level of functionality that can be modified can include the functionality of at least one sensor (e.g., heart rate sensor 758, EMG sensor 746, etc.). Each of watch body 704 and watch band 712 can execute instructions stored in storage 702 and memory 750 respectively that enables at least one sensor (e.g., heart rate sensor 758, EMG sensor 746, etc.) in watch band 712 to acquire data when watch band 712 is detached from watch body 704 and when watch band 712 is attached to watch body 704.

[0146] Watch body 704 and watch band 712 can further execute instructions stored in storage 702 and memory 750 respectively that enables watch band 712 to transmit the acquired data to watch body 704 (or other computing device such as a head mounted display or other computing device) using wired communications 727 and/or wireless transceiver 740. For example, watch body 704 can display visual content to a user on touchscreen display 713 (e.g., an instance of display 115) and play audio content on speaker 125. Watch body 704 can receive user inputs such as audio input from microphone 127 and touch input from buttons 724. Watch body 704 can also receive inputs associated with a user’s location and/or surroundings. For example, watch body 704 can receive location information from GPS 716 and/or altimeter 748 of watch band 712.

[0147] Watch body 704 can receive image data from at least one image sensor 135 (e.g., a camera). Image sensor 135 can include front-facing image sensor 625A (FIG. 6A) and/or rear-facing image sensor 625B (FIG. 6B). Front-facing image sensor 625A and/or rear-facing image sensor 625B can capture wide-angle images of the area surrounding front-facing image sensor 625A and/or rear-facing image sensor 625B such as hemispherical images (e.g., at least hemispherical, substantially spherical, etc.), 180-degree images, 360-degree area images, panoramic images, ultra-wide area images, or a combination thereof. In some examples, front-facing image sensor 625A and/or rear-facing image sensor 625B can be configured to capture images having a range between 45 degrees and 360 degrees. Certain input information received by watch body 704 (e.g., user inputs, etc.) can be communicated to watch band 712. Similarly, certain input information (e.g., acquired sensor data, neuromuscular sensor data, etc.) received by watch band 712 can be communicated to watch body 704.

[0148] Watch body 704 and watch band 712 can receive a charge using a variety of techniques. In some embodiments, watch body 704 and watch band 712 can use a wired charging assembly (e.g., power cords) to receive the charge. Alternatively, or in addition, watch body 704 and/or watch band 712 can be configured for wireless charging. For example, a portable charging device can be designed to mate with a portion of watch body 704 and/or watch band 712 and wirelessly deliver usable power to a battery of watch body 704 and/or watch band 712.

[0149] Watch body 704 and watch band 712 can have independent power and charging sources to enable each to operate independently. Watch body 704 and watch band 712 can also share power (e.g., one can charge the other) via power management IC 732 in watch body 704 and power management IC 736 in watch band 712. Power management IC 732 and power management IC 736 can share power over power and ground conductors and/or over wireless charging antennas.

[0150] Wrist-wearable device system 700 can operate in conjunction with a health monitoring application that acquires biometric and activity information associated with the user. The health monitoring application can be designed to provide information to a user that is related to the user’s health. For example, wrist-wearable device system 700 can monitor a user’s physical activity by acquiring data from IMU 742 while simultaneously monitoring the user’s heart rate via heart rate sensor 758 and saturated blood oxygen levels via SpO.sub.2 sensor 754. CPU 726 can process the acquired data and display health related information to the user on touchscreen display 713.

[0151] Wrist-wearable device system 700 can detect when watch body 704 and watch band 712 are connected to one another (e.g., mechanically connected and/or electrically or magnetically connected) or detached from one another. For example, pin(s), power/ground connections 760, wireless transceiver 740, and/or wired communications 727, can detect whether watch body 704 and watch band 712 are mechanically and/or electrically or magnetically connected to one another (e.g., detecting a disconnect between the one or more electrical contacts of power/ground connections 760 and/or wired communications 727). In some examples, when watch body 704 and watch band 712 are mechanically and/or electrically disconnected from one another (e.g., watch body 712 has been detached from watch band 712 as described with reference to FIGS. 6A-6C), watch body 704 and/or watch band 712 can operate with modified level of functionality (e.g., reduced functionality) as compared to when watch body 704 and watch band 712 are mechanically and/or electrically connected to one another. The modified level of functionality (e.g., switching from full functionality to reduced functionality and from reduced functionality to full functionality) can occur automatically (e.g., without user intervention) when wrist-wearable device system 700 determines that watch body 704 and watch band 712 are mechanically and/or electrically disconnected from one another and connected to each other, respectively.

[0152] Modifying the level of functionality (e.g., reducing the functionality in watch body 704 and/or watch band 712) can reduce power consumption in battery 728 and/or battery 738. For example, any of the sensors (e.g., heart rate sensor 758, EMG sensor 746, SpO.sub.2 sensor 754, altimeter 748, etc.), processors (e.g., CPU 726, microcontroller unit 752, etc.), communications elements (e.g., NFC 715, GPS 716, LTE 718, WiFi/BluetoothTM 720, etc.), or actuators (e.g., haptics 722, 749, etc.) can reduce functionality and/or power consumption (e.g., enter a sleep mode) when watch body 704 and watch band 712 are mechanically and/or electrically disconnected from one another. Watch body 704 and watch band 712 can return to full functionality when watch body 704 and watch band 712 are mechanically and/or electrically connected to one another. The level of functionality of each of the sensors, processors, actuators, and memory can be independently controlled.

[0153] As described above, wrist-wearable device system 700 can detect when watch body 704 and watch band 712 are coupled to one another (e.g., mechanically connected and/or electrically connected) or decoupled from one another. In some examples, watch body 704 can modify a level of functionality (e.g., activate and/or deactivate certain functions) based on whether watch body 704 is coupled to watch band 712. For example, CPU 726 can execute instructions that detect when watch body 704 and watch band 712 are coupled to one another and activate front-facing image sensor 625A. CPU 726 can activate front-facing image sensor 625A based on receiving user input (e.g., a user touch input from touchscreen display 713, a user voice command from microphone 127, a user gesture recognition input from EMG sensor 746, etc.).

[0154] When CPU 726 detects that watch body 704 and watch band 712 are decoupled from one another, CPU 726 can modify a level of functionality (e.g., activate and/or deactivate additional functions). For example, CPU 726 can detect when watch body 704 and watch band 712 are decoupled from one another and activate rear-facing image sensor 625B. CPU 726 can activate rear-facing image sensor 625B automatically (e.g., without user input) and/or based on receiving user input (e.g., a touch input, a voice input, an intention detection, etc.). Automatically activating rear-facing image sensor 625B can allow a user to take wide-angle images without having to provide user input to activate rear-facing image sensor 625B.

[0155] In some examples, rear-facing image can be activated based on an image capture criterion (e.g., an image quality, an image resolution, etc.). For example, rear-facing image sensor 625B can receive an image (e.g., a test image). CPU 726 and/or rear-facing image sensor 625B can analyze the received test image data and determine whether the test image data satisfies the image capture criterion (e.g., the image quality exceeds a threshold, the image resolution exceeds a threshold, etc.). Rear-facing image sensor 625B can be activated when the test image data satisfies the image capture criterion. Additionally, or alternatively, rear-facing image sensor 625B can be deactivated when the test image data fails to satisfy the image capture criterion.

[0156] In some examples, CPU 726 can detect when watch body 704 is coupled to watch band 1012 and deactivate rear-facing image sensor 625B. CPU 726 can deactivate rear-facing image sensor 625B automatically (e.g., without user input) and/or based on receiving user input (e.g., a touch input, a voice input, an intention detection, etc.). Deactivating rear-facing image sensor 625B can automatically (e.g., without user input) reduce the power consumption of watch body 704 and increase the battery charge time in watch body 704. In some examples, wrist-wearable device system 700 can include a coupling sensor 707 that senses whether watch body 704 is coupled to or decoupled from watch band 712. Coupling sensor 707 can be included in any of watch body 704, watch band 712, or watch band coupling mechanism 660 of FIGS. 6A-6C. Coupling sensor 707 (e.g., a proximity sensor) can include, without limitation, an inductive proximity sensor, a limit switch, an optical proximity sensor, a capacitive proximity sensor, a magnetic proximity sensor, an ultrasonic proximity sensor, or a combination thereof. CPU 726 can detect when watch body 704 is coupled to watch band 712 or decoupled from watch band 712 by reading the status of coupling sensor 707.

[0157] Various operations described herein can be implemented on computer systems. FIG. 8 shows a block diagram of a representative computing system 814 usable to implement the present disclosure. In some embodiments, the wearable device 100 are implemented by the computing system 814. Computing system 814 can be implemented, for example, as a consumer device such as a smartphone, other mobile phone, tablet computer, wearable computing device (e.g., smart watch, eyeglasses, head wearable display), desktop computer, laptop computer, or implemented with distributed computing devices. The computing system 814 can be implemented to provide VR, AR, MR experience. In some embodiments, the computing system 814 can include conventional computer components such as processors 816, storage device 818, network interface 820, user input device 822, and user output device 824.

[0158] Network interface 820 can provide a connection to a wide area network (e.g., the Internet) to which WAN interface of a remote server system is also connected. Network interface 820 can include a wired interface (e.g., Ethernet) and/or a wireless interface implementing various RF data communication standards such as Wi-Fi, Bluetooth, or cellular data network standards (e.g., 3G, 4G, 5G, 60 GHz, LTE, etc.).

[0159] User input device 822 can include any device (or devices) via which a user can provide signals to computing system 814; computing system 814 can interpret the signals as indicative of particular user requests or information. User input device 822 can include any or all of a keyboard, touch pad, touchscreen, mouse or other pointing device, scroll wheel, click wheel, dial, button, switch, keypad, microphone, sensors (e.g., a motion sensor, an eye tracking sensor, etc.), and so on.

[0160] User output device 824 can include any device via which computing system 814 can provide information to a user. For example, user output device 824 can display images generated by or delivered to computing system 814 using a display. The display can incorporate various image generation technologies, e.g., a liquid crystal display (LCD), light-emitting diode (LED) including organic light-emitting diodes (OLED), projection system, cathode ray tube (CRT), or the like, together with supporting electronics (e.g., digital-to-analog or analog-to-digital converters, signal processors, or the like). A device such as a touchscreen that functions as both an input and output device can be used. Output device 824 can be provided in addition to or instead of a display. Examples include indicator lights, speakers, tactile “display” devices, printers, and so on.

[0161] Some implementations include electronic components, such as microprocessors, storage and memory that store computer program instructions in a computer readable storage medium (e.g., non-transitory computer readable medium). Many of the features described in this specification can be implemented as processes that are specified as a set of program instructions encoded on a computer readable storage medium. When these program instructions are executed by one or more processors, they cause the processors to perform various operations indicated in the program instructions. Examples of program instructions or computer code include machine code, such as is produced by a compiler, and files including higher-level codes that are executed by a computer, an electronic component, or a microprocessor using an interpreter. Through suitable programming, processor 816 can provide various functionalities for computing system 1814, including any of the functionalities described herein as being performed by a server or client, or other functionality associated with message management services.

[0162] It will be appreciated that computing system 814 is illustrative and that variations and modifications are possible. Computer systems used in connection with the present disclosure can have other capabilities not specifically described here. Further, while computing system 814 is described with reference to particular blocks, it is to be understood that these blocks are defined for convenience of description and are not intended to imply a particular physical arrangement of component parts. For instance, different blocks can be located in the same facility, in the same server rack, or on the same motherboard. Further, the blocks need not correspond to physically distinct components. Blocks can be configured to perform various operations, e.g., by programming a processor or providing appropriate control circuitry, and various blocks might or might not be reconfigurable depending on how the initial configuration is obtained. Implementations of the present disclosure can be realized in a variety of apparatus including electronic devices implemented using any combination of circuitry and software.

[0163] FIGS. 9A-9D illustrate an example flow chart of a method for activating and deactivating sensors of a wearable device, in accordance with some embodiments. The method 1000 is directed to optimizing power consumption in a wearable device. The method 1000 occurs at a wearable device that includes (1002) a first sensor configured to operate with a first power consumption rate and a second sensor configured to operate with a second power consumption rate that is greater than the first power consumption rate (e.g., FIGS. 1A-1E illustrated a wearable device 100 that has two sensors). The method includes, while a component associated with the second sensor is in an inactive state (1004) (e.g., EMG electrodes themselves, the circuitry used to process EMG signals (such as an analog front end), and/or a system-on-a-chip (SoC) for processing EMG signals can be in an inactive state (e.g., FIG. 1A shows the second sensor in a powered off state, which is indicated by no data being recording in chart 108)): receiving (1006), from the first sensor, first sensor data, and determines (1008) whether the first sensor data indicates movement of the wearable device (e.g., FIGS. 1A-1E illustrate a state determination logic 110 box that indicates the components that are used for making a determination about the state of the device based on sensor data). The method further includes, in accordance with a determination (1010) that the first sensor data indicates movement of the wearable device (e.g., the determination can include checking that the first sensor data matches a predetermined pattern of movement that is associated with a user moving the wearable device to be worn or donned by the user on their forearm or wrist): operating (1012) the component of the second sensor in an active state in which the component associated with the second sensor is used to actively sense or process sensor data (e.g., the description associated with FIG. 1B describes that the wearable device 100 watches the first sensor data before activating the second sensor). The method includes, after activating the component associated with the second sensor, receiving (1014), from the second sensor, second sensor data. The method includes, in accordance with a determination that the second sensor data indicates that the wearable device has been placed on a user’s body, continuing (1016) to operate the component associated with the second sensor in the active state (e.g., FIG. 1C illustrates wearable device 100 continues to keep the second sensor activated while it is determined the wearable device is on the wrist of the user).

[0164] Operations 1018 and the other operations shown on FIGS. 9B-9D show various optional features that can be included at various points in conjunction with the operations of FIG. 9A. For example, the first sensor can be selected from a group of many different sensors, and the second sensor can also be selected from a group of many different sensors.

[0165] In some embodiments, the first sensor is an inertial measurement unit (IMU) sensor that is configured to detect data indicating movements of the wearable device, and the second sensor is an electromyography (EMG) sensor that is configured to detect neuromuscular signals indicating muscular movements of a user (1018). In some embodiments, the first sensor is a different (i.e., not the same) sensor than the second sensor, and in some other embodiments the first sensor and second sensor are different components of the same sensor.

[0166] In some embodiments, the first sensor is a hall effect sensor (HES) that is configured to be used to check if a display portion of the wearable device is attached or detached to a cradle portion of the wearable device, and the second sensor is photoplethysmography (PPG) sensor that is configured to be used to detect changes in blood flow in a user (1020).

[0167] In some embodiments, the first sensor is a hall effect sensor (HES) that is configured to be used to check if a display portion of the wearable device is attached or detached to a cradle, and the second sensor is an inertial measurement unit (IMU) sensor that is configured to detect data indicating movements of the wearable device (1022).

[0168] In some embodiments, the first sensor has a first power consumption rate between 2 to 5 mW/s (milliwatts per second) (1024).

[0169] In some embodiments, the second sensor has a second power consumption rate between 7 to 17 mW/s (1026).

[0170] In some embodiments, the component associated with the second sensor is operated in the active state for a period of time, and, after the period of time, the method further comprises (1028): while the component associated with the second sensor is in the inactive state: receiving, from the first sensor, new first sensor data; and the wearable device determines whether the new first sensor data indicates movement of the wearable device. In some embodiments, the method includes in accordance with a determination that the first sensor data indicates that the wearable device has not moved, continuing to operate the component of the second sensor in the inactive state (e.g., FIG. 1E illustrates the wearable device is off the wrist of the user and is stationary, and the wearable device 100 being switched to a low power mode while the data from the first sensor indicates there is no movement).

[0171] In some embodiments, the continuing to operate the component associated with the second sensor in the active state includes continuing (1030) to operate the component associated with the second sensor in the active state until a deactivation trigger is detected.

[0172] In some embodiments, the deactivation trigger is detected when data from the first sensor that indicates that the wearable device has been removed from the user’s body (1032) (e.g., FIG. 1E illustrates the wearable device is off the wrist of the user and is stationary, and the wearable device 100 being switched to a low power mode while the data from the first sensor indicates there is no movement).

[0173] In some embodiments, the deactivation trigger is detected when data from the second sensor indicates that the wearable device has been remove from the user’s body (1034) (e.g., FIG. 1E illustrates the wearable device is off the wrist of the user and is stationary, and the wearable device 100 being switched to a low power mode based on no data being received from the second sensor).

[0174] In some embodiments, the determination that the second sensor data indicates (1036) that the wearable device has been placed on the user’s body includes determining that the second sensor data, as compared to subsequent sensor data from the second sensor, reflects a change in data sensed by the second sensor.

[0175] In some embodiments, the second sensor data indicates (1038) that one or more sensing channels of the second sensor are receiving data at or above a noise threshold (e.g., noise can include one or more of: inherent noise in the electronics equipment, ambient noise, motion artifact, inherent instability of signal, ECG artifacts, cross talk, electrode contact, transducer noise, or baseline shifts) (In some embodiments, receiving data above a noise threshold includes identifying a pattern identified as not noise for a predetermined amount of time), and the subsequent sensor data indicates that the one or more sensing channels of the second sensor are receiving data below the noise threshold (e.g., one or more sensing channels reflect stable signals (while device is on wrist) as compared to noisy signals (while device is moving and being attached to wrist)). For example, FIG. 2E illustrates a multichannel sensor, e.g., as indicated by the data in chart 214, there can be multiple sensors that have their data compiled together (e.g., multiple electrodes).

[0176] In some embodiments, operating (1040) the component of the second sensor in the active state includes causing an interrupt signal to be sent to the component associated with the second sensor to cause it to transition from the inactive to the active state.

[0177] In some embodiments, determining (1042) whether the first sensor data indicates movement of the wearable device includes determining whether the movement is consistent with one or more known movements associated with the user placing the wearable device on the user’s body. For example, the description associated with FIG. 1B discusses that the state determination logic 110 is configured to determine that the wearable device 100 is off the wrist of the user 104, and whether the wearable device 100 is moving. FIG. 2D also shows in chart 212 that a sensor records a different pattern when the watch capsule 202 is on the wrist of the user 208 and/or connected to the watchband 200, than when the watch capsule 202 is not on the wrist of the user 208 and/or not connected to the watchband 200. In one example, the one or more known movements are detected based on a pattern of signals present in the first sensor data.

[0178] In some embodiments, the component associated with the second sensor is a system-on-a-chip configured to process the second sensor data (1044).

[0179] In some embodiments, the component associated with the second sensor is a machine-learning model used to process and/or analyze the second sensor data (1046) (e.g., the state determination logic 110 in FIGS. 1A-1E). In some embodiments, the second sensor can be configured to use multiple different types of machine-learning models, some of which can process many types of gestures and others of which can process a more limited set of gestures. In the case of the former type of machine-learning models, these can operate with a higher power-consumption level given the additional computational complexities and associated power requirements to operate a model that can detect many different types of gestures. So, in some embodiments, the lower-power-consumption model(s) can be always on to detect a limited set of gestures, but it is advantageous (for properly preserving limited power and computing resources, especially for wrist-wearable devices) to only active the higher-power-consumption model(s) when they are known to be needed (e.g., when a wrist-wearable device moves from an off-wrist state to a state in which data from the first sensor can be used to determine that the device is moving but that data cannot be used to determine at a high enough level of certainty (e.g., above a confidence level of 85% approximately) whether the device has been placed on a wrist or not). Thus, the first sensor data can be used as a trigger to figure out when to activate the power-hungry components of the second sensor, resulting in a system that efficiently makes use of limited computing and power resources.

[0180] In some embodiments, the component is an electrode configured to sense the second sensor data (1048). In some embodiments, the component includes a channel of at least two electrodes configured to sense the second sensor data (1050). For example, FIG. 2E illustrates a multichannel sensor, e.g., as indicated by the data in chart 214, there can be multiple sensors that have their data compiled together (e.g., multiple electrodes).

[0181] In some embodiments, the component includes both at least one electrode configured to sense the second sensor data and a machine-learning model configured to process the second sensor data (1052). For example, this is similar to the different power-consumption levels for different types of machine-learning models, the underlying components used to sense the signals themselves (as compared to processing the signals after they are sensed) can also be activated at appropriate times to make efficient use of limited power and computing resources. These include individual electrodes, as well as groups of multiple electrodes (e.g., pairs) operating as sensor channels), such that individual sensors or groups of sensors can be activated at different points in time in accordance with the movement determinations made using the first sensor data. For example, the system can operate with a predetermined number of groups of sensors (e.g., 4 or 6) in an always on/active state and can determine when to activate a remaining number of groups of sensors (e.g., a remining 2-10 additional groups) for assisting with detection of a more complex set of gestures.

[0182] In some embodiments, the wearable device is a wrist-wearable device or a head-worn wearable device (1054).

[0183] In some embodiments, while the wearable device has been placed on the user’s body: in accordance with a determination that a display portion of the wearable device has been detached from a cradle, locking (1056) the wearable device until an authentication input is received (e.g., a waving of a finger detected by the rear-facing camera, as shown in FIGS. 13B-13C causes the wearable device to unlock). In some embodiments, a prompt is displayed at the wearable device informing the user that an authentication is required to unlock the device (e.g., user interface 1302 shown in FIGS. 13A-13C). In some embodiments, the authentication input is a biometric input (1058). In some embodiments, the biometric input is a predefined movement pattern of a finger of the user in front of a camera of the wearable device or an image of the finger of the user that is captured by the camera of the wearable device to detect at least one unique biometric characteristic of the finger (1060) (e.g., as shown in FIGS. 13B-13C).

[0184] FIGS. 10A-10C illustrate an example flow chart of a method for activating and deactivating sensors of a wearable device that includes three different sensors, in accordance with some embodiments. The method 1100 is directed to optimizing power consumption in a wearable device. The method 1100 occurs at a wrist-wearable device that includes a capsule portion that is configured to be removably coupled to a cradle portion of the wrist-wearable device (in some embodiments, the capsule portion magnetically connects to the cradle portion), the wrist-wearable device including a first sensor of a first sensor type and a second sensor of a second sensor type distinct from the first sensor type (and the wrist-wearable device includes a third sensor of a third type distinct from the first sensor of the first type and the second sensor of the second type) (1102).

[0185] The method includes determining (1104) (e.g., at the capsule portion of the wrist-wearable device or a separate third connected device (e.g., a phone)), using sensor data from the first sensor of the first sensor type, whether the capsule portion of the wrist-wearable device is coupled with the cradle portion of the wrist-wearable device (e.g., FIG. 2C illustrates that the first sensor, as illustrated by chart 210, is configured to provide data that the state determination logic 206 can use to determine if the watch capsule 202 has been placed on the cradle 200).

[0186] The method includes, in accordance with a determination that the data from the first sensor of the first sensor type indicates that the capsule portion of the wrist-wearable device is coupled with the cradle portion of the wrist-wearable device, (activating a second sensor from a powered-off state, and then) obtaining (1106) data from the second sensor of the second sensor type (e.g., FIG. 2D shows the user 208 having connected the watch capsule 202 to the cradle 200, and the chart 212 indicating a pattern associated with capsule 202 to the cradle 200 being on the wrist of the user).

[0187] The method includes, in accordance with a determination that the data from the second sensor of the second sensor type indicates that the wrist-wearable device is worn on a wrist of a user, (activating a third sensor from a powered-off state, and then) monitoring (1108) data from a third sensor of a third sensor type that is distinct from the first and second sensor types to determine an activity being performed by the user while the wrist-wearable device is worn on the user’s wrist (e.g., FIG. 2D shows that in response to the state determination logic 206 determining that the watch is on the wrist of the user, the state determination logic 206 provides instructions for activating a third sensor, as indicated by the data in chart 214 being recorded).

[0188] In some embodiments, the first sensor of the first type is integrated into the capsule portion of the wrist-wearable device. In some embodiments, the first sensor of the first type is integrated into the cradle portion (including a watchband of the cradle portion) of the wrist-wearable device. In some embodiments, the second sensor of the second type is integrated into the capsule portion of the wrist-wearable device. In some embodiments, the second sensor of the second type is integrated into the cradle portion (including a watchband of the cradle portion) of the wrist-wearable device. In some embodiments, the third sensor of the third type is integrated into the capsule portion of the wrist-wearable device. In some embodiments, the third sensor of the third type is integrated into the cradle portion (including a watchband of the cradle portion) of the wrist-wearable device.

[0189] Operations 1110 and the other operations shown on FIGS. 10A-10C show various optional features that can be included at various points in conjunction with the operations of FIG. 10A. For example, the first sensor can be selected from a group of many different sensors, the second sensor can also be selected from a group of many different sensors, and the third sensor can be selected from a group of many different sensors.

[0190] In some embodiments, the first sensor is a hall effect sensor (HES) that provides data that is used to check if the capsule portion of the wrist-wearable device is coupled or decoupled from the cradle portion of the wrist-wearable device, (e.g., the HES is used to sense the presence of the magnetic field of the cradle portion of the wearable device) and the second sensor is (i) photoplethysmography (PPG) sensor that provides data that is used to detect changes in blood flow in a user, (ii) electromyography (EMG) sensor that provides data that is used to determine muscular activities of a user, or (iii) an infrared (IR) sensor that provides data used to detect proximity to objects (1110).

[0191] In some embodiments, the method includes, after determining whether the capsule portion of the wrist-wearable device is on the wrist of the user, determining (1112) using a component of a third sensor whether the wrist-wearable device is being used during sleep or during exercise (e.g., FIG. 2F illustrates that the state determination logic 206 has determined that the user has begun exercising, based at least on the data from the three sensors, and FIG. 2G shows that the state determination logic 206 has determined that the user is sleeping, based on at least data recorded by the one or more sensors).

[0192] In some embodiments, the third sensor is an inertial measurement unit (IMU) sensor that is configured to provide data used to approximate or measure inertial parameters associated with motion of the wrist-wearable devices (1114) (e.g., FIG. 2D shows that in response to the state determination logic 206 determining that the watch is on the wrist of the user, the state determination logic 206 provides instructions for activating a third sensor, which in some embodiments is an IMU sensor).

[0193] In some embodiments, in accordance with a determination that the third sensor indicates that the wrist-wearable device is being used during exercise, operating (1116) the second sensor at a first frequency (e.g., FIG. 2F also shows that in accordance with a determination that the user is exercising the third sensor operates at a first frequency (e.g., 15 Hz and 50 Hz)), and in accordance with a determination that the third sensor indicates that the wrist-wearable device is being used during sleep, operating the second sensor at a second frequency (e.g., FIG. 2G also shows that in accordance with a determination that the user is sleeping the third sensor operates at a second frequency that is higher than the first frequency (e.g., 100 Hz and 150 Hz)).

[0194] In some embodiments, the first frequency is between 15 Hz and 50 Hz (e.g., FIG. 2F also shows that in accordance with a determination that the user is exercising the third sensor operates at a first frequency (e.g., 15 Hz and 50 Hz)), and the second frequency is between 100 Hz and 150 Hz (1118) (e.g., FIG. 2G also shows that in accordance with a determination that the user is sleeping the third sensor operates at a second frequency (e.g., 100 Hz and 150 Hz)).

[0195] In some embodiments, the method includes, in accordance with a determination that the third sensor indicates that the wrist-wearable device is being used during sleep, activating (1120) a first subset of components of the second sensor (e.g., as shown in step 318 of FIG. 3, when the IMU sensor provides data that indicates the user is sleeping (e.g., the data provided by the IMU corresponds to a predetermined pattern that indicates a user wearing the wearable device is sleeping), the rear-facing camera is disabled, the front-facing camera is disabled, the red LED, the green LED, and the IR on the AFE are enabled, and the sensors are configured to operate at 128 Hz). In some embodiments, the method includes, in accordance with a determination that the third sensor indicates that the wrist-wearable device is being used during exercise, activating a second subset of components of the second sensor, which is a different subset of components than the first subset of components (e.g., as shown in step 320 of FIG. 3, when the IMU sensor provides data that indicates that the user is exercising (e.g., the data provided by the IMU corresponds to a predetermined pattern that indicates a user wearing the wearable device is exercising), one or more sensors are operated at 25 Hz, the green LED, and the IR on the AFE are enabled).

[0196] In some embodiments, the first subset of components of the second sensor includes an IR sensor, a red light emitting diode (LED), and a green LED (e.g., as shown in step 318 of FIG. 3, when the IMU sensor provides data that indicates the user is sleeping (e.g., the data provided by the IMU corresponds to a predetermined pattern that indicates a user wearing the wearable device is sleeping), the rear-facing camera is disabled, the front-facing camera is disabled, the red LED, the green LED, and the IR on the AFE are enabled, and the sensors are configured to operate at 128 Hz); and the second subset of components of the second sensor includes an IR sensor and a green LED (1122) (e.g., as shown in step 320 of FIG. 3, when the IMU sensor provides data that indicates that the user is exercising (e.g., the data provided by the IMU corresponds to a predetermined pattern that indicates a user wearing the wearable device is exercising), one or more sensors are operated at 25 Hz, the green LED, and the IR on the AFE are enabled).

[0197] In some embodiments, the wrist-wearable device includes at least two cameras (e.g., see FIG. 3, illustrating when to activate and deactivate a front camera “Fcam” and a rear camera “Rcam”). In some embodiments, the method includes, in accordance with a determination that the third sensor indicates that the wrist-wearable device is being used during exercise, enabling (1124) a first camera of the at least two cameras (e.g., FIG. 3 illustrates in step 320 that the rear camera is off and the front camera is enabled); and in accordance with a determination that the third sensor indicates that the wrist-wearable device is being used during sleep, forgoing enabling the at least two cameras (e.g., FIG. 3 illustrates in step 318 that the rear camera and front camera are off).

[0198] In some embodiments, the at least two cameras include a front facing camera and a rear facing camera (e.g., the front facing camera is on the same face as the display, and the rear-facing camera is on the opposite surface (1126) (e.g., the surface that mates to the cradle)).

[0199] In some embodiments, the method includes, in accordance with a determination that the data from the first sensor of the first sensor type indicates that the capsule portion of the wrist-wearable device is not coupled with the cradle portion of the wrist-wearable device, enabling (1128) the rear facing camera (e.g., step 304 of FIG. 3 illustrates that the rear camera “Rcam” is enabled and the front camera “Fcam” is not enabled when the capsule device is off the cradle), and in accordance with a determination that the data from the first sensor of the first sensor type indicates that the capsule portion of the wrist-wearable device is coupled with the cradle portion of the wearable device, enabling the front facing camera (e.g., step 306 of FIG. 3 illustrates that the rear camera “Rcam” is not enabled and the front camera “Fcam” is enabled when the capsule device is on the cradle). In some embodiments, the wearable device includes an ambient light sensor (e.g., the ambient light sensor is on the same face as the display). While the example in FIG. 3 indicates that the ambient light sensor remains activated to improve PPG data (e.g., by filtering out ambient light noise), in some embodiments, the method includes, in accordance with a determination that the data from the first sensor of the first sensor type indicates that the capsule portion of the wrist-wearable device is coupled with the cradle portion of the wearable device, disabling the ambient light sensor.

[0200] Various examples discussed above related to use of data from a hall-effect sensor to make determinations as to whether or not a capsule is attached to a cradle portion on a band of a wearable device. As an alternative, or in addition, capacitively-sensed information about a user’s digits relative to the capsule can also be used to assist with the cradle on/off determinations. In one example, a metallic data-transmission component (e.g., an NFC coil) can be repurposed to be used for this capacitive-sensing application. A skilled artisan would also appreciate that repurposing of the metallic data-transmission component can be used as a capacitive sensor independent of whether or not it is for the cradle on/off example application. More details are provided below. In some embodiments, the camera is on the opposite surface (1126) (e.g., the surface that mates to the cradle)).

[0201] FIGS. 11A-11C illustrate an example flow chart of a method of using a metallic data-transmission component (e.g., an NFC coil) in a wearable device to also be used for this capacitive-sensing, in accordance with some embodiments. The method 1200 is directed to optimizing power consumption in a wearable device, and reduce the number of components in the device that use valuable resources (e.g., using a single component to do the job of another component). The method 1200 is a method of repurposing a metallic data-transmission component included in an electronic device, the electronic device including one or more processors (1202).

[0202] The method 1200 includes, receiving (1204), via the metallic data-transmission component, operational data indicative of a current operational state of the metallic data-transmission component. The method 1200 includes determining (1206), based on the operational data, whether data-transmission criteria are present.

[0203] The method 1200 also includes, in accordance with a determination that the data-transmission criteria are present, the electronic device operates (1208) the metallic data-transmission component in a first mode, wherein, while in the first mode, the metallic data-transmission component is configured to be used as antenna in conjunction with transferring data between the electronic device and at least one other electronic device using the metallic data-transmission component. In some embodiments, this first mode is a mode in which the metallic data-transmission component performs a first function and, as discussed below, when the metallic data-transmission component is operated in a second mode, it then performs a second function that is distinct from the first function.

[0204] The method 1200 includes that in accordance with a determination that the data-transmission criteria are not present, operating (1210) the metallic data-transmission component in a second mode, in which the metallic data-transmission component functions as a capacitive sensor.

[0205] Operations 1212 and the other operations shown on FIGS. 11B-11C show various optional features that can be included at various points in conjunction with the operations of FIG. 11A. For example, the data-transmission criteria includes one or more of a predefined idle time, predefined separation distance, predefined capacitance value, and predefined number of coupling attempts.

[0206] In some embodiments, the electronic device includes one or more sensors. In some embodiments, the method includes receiving (1212), via the one or more sensors, sensor data indicating a position of the metallic data-transmission component with respect to the electronic device; and determining whether data-transmission criteria are present based in part the sensor data.

[0207] In some embodiments, the one or more sensors include another capacitive sensor. In some embodiments, the method includes, while the metallic data-transmission component is operating in the second mode, receiving (1214), via the capacitive sensor, a first capacitance value. In some embodiments, the method includes, while the metallic data-transmission component is operating in the second mode, receiving, via the other capacitive sensor a second capacitance value. In some embodiments, the method includes, while the metallic data-transmission component is operating in the second mode, determining a true capacitance value based on a comparison of the first capacitance value and the second capacitance value. In some embodiments, the method includes, while the metallic data-transmission component is operating in the second mode, providing the true capacitance value to the electronic device to perform an action based on the true capacitance value (e.g., a touch screen input).

[0208] In some embodiments, the one or more sensors include another capacitive sensor that is disabled when the metallic data-transmission component is operating in a second mode (1216).

[0209] In some embodiments, the metallic data-transmission component is coupled to a switch. In some embodiments, the method includes, providing (1218) a switching signal to the switch to selectively couple the metallic data-transmission component with (i) data-communication circuitry while the metallic data-transmission component is operating in the first mode and (ii) sensor-processing circuitry while the metallic data-transmission component is operating in the second mode based on a determination whether the data-transmission criteria are present.

[0210] In some embodiments, capacitance detected via the metallic data-transmission component while it is operating in the second mode is used in conjunction with the methods of A1-A23 or G1-G11 (1220).

[0211] In some embodiments, the electronic device is a wrist-wearable device including a capsule and an accessory configured to couple with the capsule, and determining (1222) whether data-transmission criteria are present includes determining that the capsule is coupled to the accessory.

[0212] In some embodiments, the electronic device includes a communications component configured to communicatively coupled with at least one other device. In some embodiments, the communications components provides a beacon signal. In some embodiments, determining (1224) whether data-transmission criteria are present is further based on one or more communication signals transferred between the electronic device and the at least one other device. In some embodiments, a first signal transmitted by the metallic data-transmission component has a first wavelength and a second signal transmitted by the communications component has a second wavelength distinct from the first wavelength.

[0213] In some embodiments, the data-transmission criteria includes one or more of a predefined idle time, predefined separation distance, predefined capacitance value, and predefined number of coupling attempts (1226).

[0214] In some embodiments, the predefined separation distance is equal to or less than 5 millimeters (mm) (1230). In some embodiments, the metallic data-transmission component can detect capacitance up to a distance of at least 1 centimeter (cm), 2 cm, 3 cm.

[0215] In some embodiments, predefined capacitance value is within a range of values between 100-200 pF (1232).

[0216] In some embodiments, the predefined idle time is a nonzero value that is equal to or less than 5 ms seconds (1234).

[0217] In some embodiments, the predefined number of coupling attempts is a nonzero value that is equal to or less than three coupling attempts (1236).

[0218] In some embodiments, a wireless communications component of the wrist-wearable device (e.g., a BLUETOOTH radio) operates at a first frequency and the metallic data-transmission component operates at a second frequency lower than the first frequency (1238). In some embodiments, the metallic data-transmission component has an operations frequency of 13.5 MHz. In some embodiments, due to the frequency differences there is no interferences.

[0219] In some embodiments, the method includes, while operating the metallic data-transmission component in the second mode, receiving capacitance values at a first point and time and a second point in time, where a time between the first point in time and the second point in time is less than 300 ms (1240). In some embodiments, the method includes, receiving capacitance values in less than 200 ms, and in some other embodiments less than 150 ms. In some embodiments, pre-heating of a camera with SMA actuators takes about 300 to 500 ms, the metallic data-transmission component provides capacitance values quickly reducing the lag time between decoupling and activating the camera.

[0220] FIGS. 12A-12E illustrate a method of unlocking a wearable device using a gesture, in accordance with some embodiments. FIG. 12A illustrates the capsule portion 202 being held in a hand 1300 of a user. When the capsule portion is removed from the cradle portion, or the capsule portion has made a determination that the device needs to be locked for other security reasons, a user interface 1302 is displayed notifying a user how to unlock the device. As shown, the user is prompted to either insert a pass code on a display 1304 of the capsule or provide a finger gesture. The finger gesture is detected by a rear facing camera 1306 (occluded), which can be configured to recognize a biometric input of a finger (e.g., a fingerprint, a motion of the finger, and/or vascular structure or another identifying feature).

[0221] FIGS. 12B-12C illustrates a user of the device moving their middle finger 1308 in a waving manner 1310 to unlock the device using a gesture. While a waving gesture is shown, any number of other gestures can be used to unlock the device (e.g., curling a finger, articulating multiple fingers, etc.,). In some embodiments, the rear facing or front-facing camera can be used to detect a gesture performed by the hand not holding the capsule 202.

[0222] FIG. 12D illustrates that in accordance with a determination that the gesture matches a gesture stored on the wearable device, the device is unlocked, as indicated by user interface 1311. In an unlocked state the user has access to all the files associated with the user who unlocked the device, and access to previously inaccessible features.

[0223] FIG. 12E illustrates that in response to the device being unlocked, a front-facing camera 1312 is opened and a picture 1314 of the user is taken. In some embodiments, this picture 1314 is used for further verification that the user is the correct user unlocking the device (e.g., a two-step authentication).

[0224] It will be understood that, although the terms “first,” “second,” etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another.

[0225] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the claims. As used in the description of the embodiments and the appended claims, the singular forms “a,” “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the term “and/or” as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items. It will be further understood that the terms “comprises” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

[0226] As used herein, the term “if” can be construed to mean “when” or “upon” or “in response to determining” or “in accordance with a determination” or “in response to detecting,” that a stated condition precedent is true, depending on the context. Similarly, the phrase “if it is determined [that a stated condition precedent is true]” or “if [a stated condition precedent is true]” or “when [a stated condition precedent is true]” can be construed to mean “upon determining” or “in response to determining” or “in accordance with a determination” or “upon detecting” or “in response to detecting” that the stated condition precedent is true, depending on the context.

[0227] The foregoing description, for purpose of explanation, has been described with reference to specific embodiments. However, the illustrative discussions above are not intended to be exhaustive or to limit the claims to the precise forms disclosed. Many modifications and variations are possible in view of the above teachings. The embodiments were chosen and described to best explain principles of operation and practical applications, to thereby enable others skilled in the art.