Charging interface communication

Abstract

Portable device comprising: one or more memories that store processor-executable code; and one or more processors coupled to the one or more memories and operable individually or jointly to execute the code to cause the portable device to: Receiving, via inductive charging components, a sequence of gradually decreasing output power levels from a charging device, wherein the output power levels correspond to detected voltage levels on the portable device; activating a charging-based communication circuit within the portable device upon detecting a first output power level of the sequence of gradually decreasing output power levels falling below an overload protection threshold; Outputting, to the charging device and via the inductive charging components and the charging-based communication circuit, a first message; and Receiving, from the charging device and via the inductive charging components and the charging-based communication circuitry, a second message in response to the first message.

Description

FIELD OF TECHNOLOGY

[0001] The following refers to portable devices and data processing, including charging interface communication. background

[0002] Some wearable devices may be configured to collect data from users. Some wearable devices may be designed to include one or more elements that can facilitate charging via a charging device (e.g., a charger). Short description of the drawings Fig. 1 illustrates an example of a system supporting charging interface communication in accordance with aspects of the present disclosure. Fig. 2 illustrates an example of a system supporting charging interface communication in accordance with aspects of the present disclosure. Fig. 3 shows an example of a charging diagram supporting charging interface communication according to aspects of the present disclosure. Fig. 4 shows an example of a charging flow diagram supporting charging interface communication according to aspects of the present disclosure. Fig. 5 shows an example of a charging flow diagram supporting charging interface communication according to aspects of the present disclosure. Fig. 6 shows an example of a process flow diagram supporting charging interface communication according to aspects of the present disclosure. Fig. 7 shows a block diagram of a device that supports charging interface communication according to aspects of the present disclosure. Fig. 8 shows a block diagram of a portable device manager that supports charging interface communication according to aspects of the present disclosure. Fig. 9 shows a diagram of a system including a device that supports charging interface communication according to aspects of the present disclosure. Fig. 10 shows a block diagram of a device supporting charging interface communication according to aspects of the present disclosure. Fig. 11 shows a block diagram of a portable application that supports charging interface communication according to aspects of the present disclosure. Fig. 12 shows a diagram of a system including a device that supports charging interface communication in accordance with aspects of the present disclosure. Fig. 13 through 16 show flowcharts illustrating methods that support charging interface communication according to aspects of the present disclosure. Detailed description

[0003] A wearable device, such as a ring or watch, may be configured to measure data, such as biometric data, of a user and report the data to the user. The wearable device may be charged via a charging device (e.g., charger) and may be charged using contact-based (e.g., galvanic) charging. However, abrasion, chemicals, skin particles, and dirt can negatively impact the effectiveness of galvanic charging. Infrared signals may be used in addition to galvanic charging to transmit data, such as messages, between the wearable device and the charging device. However, infrared communications between the wearable device and the charging device may be inadvertently detected by nearby wearable devices, resulting in confusion and ineffectiveness in the communications.Additionally, for infrared communication between the charging device and the portable device to work, the materials or colors of the charging device or the portable device may be limited. The disadvantages of galvanic charging and the lack of flexibility, as well as the additional components required for infrared communication, represent additional manufacturing costs and complexity. Improving the communication method between the charging device and the portable device would be beneficial for production costs, design flexibility, and communication reliability.

[0004] Techniques described herein provide a charging interface communication method that implements inductive charging. Inductive charging or wireless charging may not require the charging device to have an infrared sensor or a specific material color or finish, and is not as negatively affected by the physical condition of the portable device (such as dirt, chemicals, abrasion, etc.) as galvanic charging. The portable device may communicate by modulating a power input detected by the charging device, and the charging device communicates by modulating the output power detected by the portable device. To establish a communication link, the output power of the charging device may match the input power of the portable device required by the portable device to be fully charged.This stationary charging power is variable because the portable device can be in different charging states depending on when the portable device is placed on the charging device. The charging device outputs power and listens for a message from the portable device. If no message is received, the charging device reduces the output power. The charging device continues listening and reducing the power until a message is received. Generally, the portable device communicates with the charging device by modulating the load current expressed at the charging device. At the same time, the portable device receives the power and waits until the power has been reduced below a threshold (e.g., an overload threshold), and then sends a message to the charging device by receiving power.Generally, the charging device communicates with the portable device by modulating the charging voltage expressed at the portable device. For example, the power input may be interpreted by the charging device as one or more bits indicating a first message, such as a connection setup message. The charging device may then modulate the output power, which may be interpreted by the portable device as one or more bits indicating a second message, such as a connection confirmation message.

[0005] Aspects of the disclosure are first described in the context of systems that support the collection of physiological data from users via wearable devices. Aspects of the disclosure are further illustrated by and described with reference to charging diagrams, charging flow diagrams, and process flow diagrams. Aspects of the disclosure are further illustrated by and described with reference to device diagrams, system diagrams, and flow diagrams related to charging interface communication.

[0006] Fig. Figure 1 illustrates an example of a system 100 that supports charging interface communication according to aspects of the present disclosure. The system 100 includes a plurality of electronic devices (e.g., wearable devices 104, user devices 106) that can be worn and / or operated by one or more users 102. The system 100 further includes a network 108 and one or more servers 110.

[0007] The electronic devices may include any electronic devices known in the art, including wearable devices 104 (e.g., wearable ring devices, wearable watch devices, etc.), user devices 106 (e.g., smartphones, laptops, tablets). The electronic devices associated with the respective users 102 may include one or more of the following functionalities: 1) measuring physiological data, 2) storing the measured data, 3) processing the data, 4) providing outputs (e.g., via GUls) to a user 102 based on the processed data, and 5) communicating data with each other and / or with other computing devices. Different electronic devices may perform one or more of the functionalities.

[0008] Example wearable devices 104 may include wearable computing devices, such as a ring computing device (hereinafter, a "ring") configured to be worn on a user's 102 finger, a wrist computing device (e.g., a smartwatch, fitness band, or bracelet) configured to be worn on a user's 102 wrist, and / or a head-worn computing device (e.g., glasses / goggles). Wearable devices 104 may also include bands, straps (e.g., flexible or inflexible bands or straps), adhesive sensors, and the like that can be positioned in other locations, such as bands around the head (e.g., a headband), the arm (e.g., a forearm band and / or bicep band), and / or the leg (e.g., a thigh or calf band), behind the ear, under the armpit, and the like. Wearable devices 104 may also be attached to or incorporated into clothing.For example, wearable devices 104 may be contained in pockets and / or pouches on clothing. As another example, wearable device 104 may be clipped and / or plugged into clothing or otherwise kept near user 102. Example items of clothing may include, but are not limited to, hats, shirts, gloves, pants, socks, outerwear (e.g., jackets), and underwear. In some implementations, wearable devices 104 may be combined with other types of equipment, such as exercise / sports equipment used during physical activity. For example, wearable devices 104 may be attached to or contained within a bicycle, skis, a tennis racket, a golf club, and / or training weights.

[0009] Much of the present disclosure may be described in the context of a wearable ring device 104. Accordingly, the terms "ring 104," "wearable device 104," and similar terms may be used interchangeably unless otherwise indicated herein. However, the use of the term "ring 104" is not intended to be limiting, as it is contemplated herein that aspects of the present disclosure may be performed using other wearable devices (e.g., wearable watch devices, wearable necklace devices, wearable bracelet devices, wearable earring devices, wearable anklet devices, and the like).

[0010] In some aspects, user devices 106 may include portable mobile computing devices such as smartphones and tablet computing devices. User devices 106 may also include personal computers such as laptop and desktop computing devices. Other example user devices 106 may include server computing devices that can communicate with other electronic devices (e.g., over the Internet). In some implementations, computing devices may include medical devices such as external portable computing devices (e.g., Holter monitors). Medical devices may also include implantable medical devices such as pacemakers and cardioverter defibrillators. Other example user devices 106 may include home computing devices such as Internet of Things (IoT) devices (e.g., IoT devices), smart TVs, smart speakers, smart displays (e.g., video call displays), hubs (e.g., wireless communication hubs), security systems, smart home appliances (e.g.,thermostats and refrigerators) and fitness equipment.

[0011] Some electronic devices (e.g., wearable devices 104, user devices 106) may measure physiological parameters of the respective users 102, such as photoplethysmography waveforms, continuous skin temperature, a pulse waveform, respiration rate, heart rate, heart rate variability (HRV), actigraphy, galvanic skin response, pulse oximetry, blood oxygen saturation (SpO2), blood glucose levels (e.g., glucose metrics), and / or other physiological parameters. Some electronic devices that measure physiological parameters may also perform some / all of the calculations described herein. Some electronic devices may not measure physiological parameters but may perform some / all of the calculations described herein. For example, a ring (e.g.,portable device 104), a mobile device application, or a server computing device may process received physiological data measured by other devices.

[0012] In some implementations, a user 102 may operate or be connected to multiple electronic devices, some of which measure physiological parameters and some of which process the measured physiological parameters. In some implementations, a user 102 may have a ring (e.g., wearable device 104) that measures physiological parameters. The user 102 may also have or be connected to a user device 106 (e.g., mobile device, smartphone), where the wearable device 104 and the user device 106 are communicatively coupled. In some cases, the user device 106 may receive data from the wearable device 104 and perform some / all of the calculations described herein. In some implementations, the user device 106 may also measure physiological parameters described herein, such as movement / activity parameters.

[0013] For example, as in Fig. 1, a first user 102a (User 1) may operate or be connected to a wearable device 104a (e.g., ring 104a) and a user device 106a that may operate as described herein. In this example, the user device 106a associated with user 102a may process / store physiological parameters measured by the ring 104a. Comparably, a second user 102b (User 2) may be connected to a ring 104b, a wearable watch device 104c (e.g., watch 104c), and a user device 106b, wherein the user device 106b associated with user 102b may process / store physiological parameters measured by the ring 104b and / or the watch 104c. Furthermore, an nth user 102n (user N) may be connected to an arrangement of electronic devices described herein (e.g., ring 104n, user device 106n). In some aspects, portable devices 104 (e.g.,Wearable devices (e.g., rings 104, watches 104), and other electronic devices may be communicatively coupled to the user devices 106 of the respective users 102 via Bluetooth, Wi-Fi, and other wireless protocols. Furthermore, in some cases, the wearable device 104 and the user device 106 may be included in (or constitute) the same device. For example, in some cases, the wearable device 104 may be configured to execute an application associated with the wearable device 104 and may be configured to display data via a GUI.

[0014] In some implementations, the rings 104 (e.g., wearable devices 104) of the system 100 may be configured to collect physiological data from the respective users 102 based on the arterial blood flow in the user's finger. In particular, a ring 104 may utilize one or more light-emitting components, such as LEDs (e.g., red LEDs, green LEDs), that emit light toward the palm side of a user's finger to collect physiological data based on the arterial blood flow in the user's finger. In general, the terms light-emitting components, light-emitting elements, and similar terms may include, but are not limited to, LEDs, micro-LEDs, mini-LEDs, laser diodes (LDs) (e.g., vertical cavity surface-emitting lasers (VCSELs)), and the like.

[0015] In some cases, system 100 may be configured to collect physiological data from respective users 102 based on the blood flow diffused into a skin microvascular bed of capillaries and arterioles. For example, system 100 may collect PPG data based on a measured amount of blood diffused into the microvascular system of capillaries and arterioles. In some implementations, ring 104 may collect the physiological data using a combination of green and red LEDs. The physiological data may include any physiological data known in the art, including, but not limited to, temperature data, accelerometer data (e.g., motion / exercise data), heart rate data, HRV data, blood oxygen level data, or any combination thereof.

[0016] The use of both green and red LEDs can offer several advantages over other solutions, as red and green LEDs have been found to have their own distinct advantages in collecting physiological data under different conditions (e.g., light / dark, active / inactive) and across different body parts, and the like. For example, green LEDs have been found to perform better during exercise. Furthermore, the use of multiple LEDs (e.g., green and red LEDs) distributed around the ring 104 has been found to have superior performance compared to wearable devices that use LEDs positioned close together, such as in a wearable watch device. Furthermore, the blood vessels in the finger (e.g., arteries, capillaries) are more easily accessible via LEDs compared to blood vessels in the wrist.In particular, arteries in the wrist are located on the underside of the wrist (e.g., palmar side of the wrist), meaning that only capillaries are accessible on the top of the wrist (e.g., dorsal side of the wrist), where wearable watch devices and similar devices are typically worn. Therefore, the use of LEDs and other sensors in a ring 104 has been found to have superior performance compared to wrist-worn wearable devices because the ring 104 can have better access to arteries (compared to capillaries), resulting in stronger signals and more valuable physiological data.

[0017] The electronic devices of system 100 (e.g., user devices 106, portable devices 104) may be communicatively coupled to one or more servers 110 via wired or wireless communication protocols. For example, as shown in Fig. 1, the electronic devices (e.g., user devices 106) may be communicatively coupled to one or more servers 110 via a network 108. The network 108 may implement the Transfer Control Protocol and the Internet Protocol (TCP / IP), such as the Internet, or implement other network protocols 108. Network connections between the network 108 and the respective electronic devices may facilitate the transport of data via email, web, text messages, mail, or any other suitable form of interaction within a computer network 108. For example, in some implementations, the ring 104a associated with the first user 102a may be communicatively coupled to the user device 106a, with the user device 106a being communicatively coupled to the servers 110 via the network 108. In additional or alternative cases, portable devices 104 (e.g.,Rings 104, watches 104) can be directly communicatively coupled to the network 108.

[0018] The system 100 may provide an on-demand database service between the user devices 106 and the one or more servers 110. In some cases, the servers 110 may receive data from the user devices 106 over the network 108 and store and analyze the data. Similarly, the servers 110 may provide data to the user devices 106 over the network 108. In some cases, the servers 110 may be located in one or more data centers. The servers 110 may be used for data storage, management, and processing. In some implementations, the servers 110 may provide a web-based interface to the user device 106 via web browsers.

[0019] In some aspects, the system 100 may detect periods of time during which a user 102 is sleeping and classify periods of time during which the user 102 is sleeping into one or more sleep stages (e.g., sleep stage classification). For example, as in Fig. 1, user 102a may be connected to a wearable device 104a (e.g., ring 104a) and a user device 106a. In this example, ring 104a may collect physiological data associated with user 102a, including temperature, heart rate, HRV, respiratory rate, and the like. In some aspects, data collected by ring 104a may be input to a machine learning classifier, where the machine learning classifier is configured to determine periods of time when user 102a is (or has been) asleep. Furthermore, the machine learning classifier may be configured to classify periods of time into different sleep stages, including a waking sleep stage, a rapid eye movement (REM) sleep stage, a light sleep stage (non-REM (NREM)), and a deep sleep stage (NREM). In some aspects, the classified sleep stages may be displayed to the user 102a via a GUI of the user device 106a.Sleep stage classification can be used to provide a user 102a with feedback regarding their sleep habits, such as recommended bedtimes, recommended wake-up times, and the like. Furthermore, in some implementations, sleep stage classification techniques described herein can be used to calculate scores for the respective user, such as sleep scores, readiness scores, and the like.

[0020] In some aspects, system 100 may utilize circadian rhythm-derived features to further enhance physiological data collection, data processing methods, and other techniques described herein. The term circadian rhythm may refer to a natural, internal process that regulates a person's sleep-wake cycle and repeats approximately every 24 hours. In this regard, techniques described herein may utilize circadian rhythm adaptation models to enhance the collection, analysis, and processing of physiological data. For example, a circadian rhythm adaptation model may be input into a machine learning classifier along with physiological data collected from user 102a via wearable device 104a.In this example, the circadian rhythm adaptation model may be configured to "weight" or adjust physiological data collected during a user's natural, approximately 24-hour circadian rhythm. In some implementations, the system may initially start with a "baseline" circadian rhythm adaptation model and modify the baseline model using physiological data collected from each user 102 to generate customized, individualized circadian rhythm adaptation models specific to each respective user 102.

[0021] In some aspects, the system 100 may utilize other biological rhythms to further enhance the collection, analysis, and processing of physiological data according to phases of those other rhythms. For example, if a weekly rhythm is detected in a person's baseline data, the model may be configured to adjust the "weights" of the data by day of the week. Biological rhythms that may require model adjustment using this method include: 1) ultradian (faster than daily rhythms, including sleep cycles in the sleep state and oscillations of less than one hour to several hours of periodicity in the measured physiological variables in the waking state); 2) circadian rhythms; 3) non-endogenous daily rhythms that are demonstrably superimposed on circadian rhythms, such as work schedules; 4) weekly rhythms or other artificial time periodicities imposed exogenously (e.g.,12-day rhythms could be used in a hypothetical culture with 12-day "weeks"); 5) multi-day ovarian rhythms in women and spermatogenesis rhythms in men; 6) lunar rhythms (relevant for individuals living with little or no artificial light); and 7) seasonal rhythms.

[0022] Biological rhythms are not always stationary. For example, many women experience variability in ovarian cycle length across cycles, and ultradian rhythms are not expected to occur at exactly the same time or with the same periodicity across days, even within a user. Therefore, signal processing techniques sufficient to quantify the frequency composition while preserving the temporal resolution of these rhythms in physiological data can be used to improve the detection of these rhythms, assign the phase of each rhythm to each measured time point, and thereby modify fitting models and comparisons of time intervals.The biological rhythm adaptation models and parameters can be added in linear or nonlinear combinations as needed to more accurately capture the dynamic physiological baselines of an individual or group of individuals.

[0023] In some aspects, the respective devices of system 100 may support charging interface communication techniques. The charging interface communication method described herein may implement messages transmitted via inductive charging. Portable device 104 may communicate by modulating a power input detected by the charging device, and the charging device may communicate by modulating the power output detected by portable device 104.

[0024] To establish a connection, the charging device detects the proximity of the portable device 104 and outputs an initial or first maximum power level. The charging device may then start a timer and wait for a message from the portable device 104. If no message is received before the timer expires, the charging device reduces the output power. The charging device continues to listen and reduce the power until a message is received from the portable device 104. At the same time, the portable device 104 receives the power and waits until the power is reduced below a threshold, then sends a message by modulating a power consumption. The threshold may be a power level or charge level of the portable device 104.

[0025] The power consumption modulation may be interpreted by the charging device as one or more bits indicating one or more messages, such as a connection establishment message. The charging device may then modulate the output power, which may be interpreted by the portable device as one or more bits indicating one or more messages, such as a connection confirmation message. After the connection is established, the portable device 104 and the charging device may communicate messages by modulating the output power and power consumption. For example, the portable device 104 may indicate to the charging device to increase or decrease the output power.

[0026] One skilled in the art should recognize that one or more aspects of the disclosure may be implemented in a system 100 to additionally or alternatively solve problems other than those described above. Furthermore, aspects of the disclosure may provide technical improvements over "conventional" systems or methods as described herein. However, the description and accompanying drawings contain only exemplary technical improvements resulting from the implementation of aspects of the disclosure and, accordingly, do not represent all of the technical improvements provided within the scope of the claims.

[0027] Fig. 2 illustrates an example of a system 200 that supports charging interface communication according to aspects of the present disclosure. System 200 may implement or be implemented by system 100. In particular, system 200 illustrates an example of a ring 104 (e.g., portable device 104), a user device 106, and a server 110, as described with reference to Fig. 1 described.

[0028] In some aspects, ring 104 may be configured to be worn around a user's finger and may determine one or more physiological parameters of the user when worn around the user's finger. Example measurements and determinations may include, but are not limited to, the user's skin temperature, pulse waveforms, respiratory rate, heart rate, HRV, blood oxygen level (SpO2), blood glucose levels (e.g., glucose metrics), and the like.

[0029] The system 200 further includes a user device 106 (e.g., a smartphone) in communication with the ring 104. For example, the ring 104 may be in wireless and / or wired communication with the user device 106. In some implementations, the ring 104 may send measured and processed data (e.g., temperature data, photoplethysmogram (PPG) data, motion / accelerometer data, ring input data, and the like) to the user device 106. The user device 106 may also send data to the ring 104, such as firmware / configuration updates for the ring 104. The user device 106 may process data. In some implementations, the user device 106 may transmit data to the server 110 for processing and / or storage.

[0030] The ring 104 may include a housing 205, which may include an inner housing 205a and an outer housing 205b. In some aspects, the housing 205 of the ring 104 may store or otherwise include various components of the ring, including, but not limited to, device electronics, a power source (e.g., battery 210 and / or capacitor), one or more substrates (e.g., circuit boards) interconnecting the device electronics and / or the power source, and the like. The device electronics may include device modules (e.g., hardware / software) such as: a processing module 230a, a memory 215, a communications module 220a, a power module 225, and the like. The device electronics may also include one or more sensors. Example sensors may include one or more temperature sensors 240, a PPG sensor array (e.g., PPG system 235), and one or more motion sensors 245.

[0031] The sensors may include associated modules (not shown) configured to communicate with the respective components / modules of the ring 104 and generate signals associated with the respective sensors. In some aspects, each of the components / modules of the ring 104 may be communicatively coupled to one another via wired or wireless connections. Furthermore, the ring 104 may include additional and / or alternative sensors or other components configured to collect physiological data from the user, including light sensors (e.g., LEDs), oximeters, and the like.

[0032] The one with reference to Fig. The ring 104 shown and described in Figure 2 is for illustrative purposes only. Therefore, the ring 104 may include additional or alternative components to those shown in Fig. 2. Other rings 104 that provide the functionality described herein may be manufactured. For example, rings 104 may be manufactured with fewer components (e.g., sensors). In one specific example, a ring 104 may be manufactured with a single temperature sensor 240 (or other sensor), a power source, and device electronics configured to read the single temperature sensor 240 (or other sensor). In another specific example, a temperature sensor 240 (or other sensor) may be attached to a user's finger (e.g., with adhesives, wraps, clips, spring-loaded clamps, etc.). In this case, the sensor may be wired to another computing device, such as a wrist-worn computing device, that reads the temperature sensor 240 (or other sensor).In other examples, a ring 104 may be manufactured that includes additional sensors and processing functions.

[0033] The housing 205 may include one or more housing components 205. The housing 205 may include an outer housing component 205b (e.g., a shell) and an inner housing component 205a (e.g., a molded part). The housing 205 may include additional components (e.g., additional layers) that may be Fig. 2 are not explicitly shown. For example, in some implementations, the ring 104 may include one or more insulating layers that electrically isolate the device electronics and other conductive materials (e.g., electrical traces) from the outer housing 205b (e.g., an outer metal housing 205b). The housing 205 may provide structural support for the device electronics, the battery 210, the substrate(s), and other components. For example, the housing 205 may protect the device electronics, the battery 210, and the substrate(s) from mechanical forces such as pressure and shock. The housing 205 may also protect the device electronics, the battery 210, and the substrate(s) from water and / or other chemicals.

[0034] The outer casing 205b may be made of one or more materials. In some implementations, the outer casing 205b may comprise a metal such as titanium, which may provide strength and abrasion resistance while being relatively lightweight. The outer casing 205b may also be made of other materials, such as polymers. In some implementations, the outer casing 205b may be both protective and decorative.

[0035] The inner housing 205a may be configured to contact the user's finger. The inner housing 205a may be formed from a polymer (e.g., a medical-grade polymer) or another material. In some implementations, the inner housing 205a may be transparent. For example, the inner housing 205a may be transparent to light emitted by the PPG light-emitting diodes (LEDs). In some implementations, the inner housing component 205a may be overmolded onto the outer housing 205b. For example, the inner housing 205a may comprise a polymer shaped (e.g., injection-molded) to fit within an outer metallic shell of the housing 205b.

[0036] The ring 104 may include one or more substrates (not shown). The device electronics and the battery 210 may be included on the one or more substrates. For example, the device electronics and the battery 210 may be mounted on one or more substrates. Example substrates may include one or more printed circuit boards (PCBs), such as flexible PCBs (e.g., polyimide). In some implementations, the electronics / battery 210 may include surface-mounted devices (e.g., surface mount technology (SMT) devices) on a flexible circuit board. In some implementations, the one or more substrates (e.g., one or more flexible circuit boards) may include electrical traces that enable electrical communication between the device electronics. The electrical traces may also connect the battery 210 to the device electronics.

[0037] The device electronics, battery 210, and substrates can be arranged in the ring 104 in a variety of ways. In some implementations, a substrate containing device electronics can be mounted along the underside of the ring 104 (e.g., the lower half) so that the sensors (e.g., PPG system 235, temperature sensors 240, motion sensors 245, and other sensors) contact the underside of the user's finger. In these implementations, the battery 210 can be contained along the upper portion of the ring 104 (e.g., on a different substrate).

[0038] The various components / modules of ring 104 represent functionalities (e.g., circuits and other components) that may be included in ring 104. Modules may include any discrete and / or integrated electronic circuit components that implement analog and / or digital circuits capable of generating the functions attributed to the modules herein. For example, the modules may include analog circuits (e.g., amplifier circuits, filter circuits, analog-to-digital converter circuits, and / or other signal conditioning circuits). The modules may also include digital circuits (e.g., combinational or sequential logic circuits, memory circuits, etc.).

[0039] The memory 215 (memory module) of the ring 104 may comprise any volatile, non-volatile, magnetic, or electrical media, such as random access memory (RAM), read-only memory (ROM), non-volatile RAM (NVRAM), electrically erasable programmable read-only memory (EEPROM), flash memory, or any other storage device. The memory 215 may store any of the data described herein. For example, the memory 215 may be configured to store data collected by the respective sensors and the PPG system 235 (e.g., motion data, temperature data, PPG data). Further, the memory 215 may include instructions that, when executed by one or more processing circuits, cause the modules to perform various functions attributed to the modules herein. The device electronics of the ring 104 described herein are merely exemplary device electronics.Therefore, the types of electronic components used to implement device electronics may vary depending on design considerations.

[0040] The functions attributed to the modules of ring 104 described herein may be implemented as one or more processors, hardware, firmware, software, or any combination thereof. The representation of various features as modules is intended to emphasize different functional aspects and does not necessarily imply that such modules must be implemented by separate hardware / software components. Rather, the functionality associated with one or more modules may be performed by separate hardware / software components or integrated into common hardware / software components.

[0041] The processing module 230a of the ring 104 may include one or more processors (e.g., processing units), microcontrollers, digital signal processors, systems-on-a-chip (SOCs), and / or other processing devices. The processing module 230a communicates with the modules included in the ring 104. For example, the processing module 230a may transmit / receive data to / from the modules and other components of the ring 104, such as the sensors. As described herein, the modules may be implemented by various circuit components. Accordingly, the modules may also be referred to as circuits (e.g., a communication circuit and a power circuit).

[0042] Processing module 230a may communicate with memory 215. Memory 215 may include computer-readable instructions that, when executed by processing module 230a, cause processing module 230a to perform the various functions attributed herein to processing module 230a. In some implementations, processing module 230a (e.g., a microcontroller) may include additional features associated with other modules, such as communication functions provided by communication module 220a (e.g., an integrated Bluetooth Low Energy transceiver) and / or additional onboard memory 215.

[0043] The communication module 220a may include circuitry enabling wireless and / or wired communication with the user device 106 (e.g., communication module 220b of the user device 106). In some implementations, the communication modules 220a, 220b may include wireless communication circuitry such as Bluetooth circuitry and / or Wi-Fi circuitry. In some implementations, the communication modules 220a, 220b may include wired communication circuitry such as Universal Serial Bus (USB) communication circuitry. Using the communication module 220a, the ring 104 and the user device 106 may be configured to communicate with each other. The processing module 230a of the ring may be configured to transmit / receive data to / from the user device 106 via the communication module 220a.Example data may include, but is not limited to, motion data, temperature data, pulse waveforms, heart rate data, HRV data, PPG data, and status updates (e.g., charging status, battery level, and / or configuration settings of the ring 104). The ring's processing module 230a may also be configured to receive updates (e.g., software / firmware updates) and data from the user device 106.

[0044] The ring 104 may include a battery 210 (e.g., a rechargeable battery 210). An example battery 210 may include a lithium-ion or lithium polymer battery 210, although a variety of battery 210 options are possible. The battery 210 may be wirelessly charged. In some implementations, the ring 104 may include a power source other than the battery 210, such as a capacitor. The power source (e.g., battery 210 or capacitor) may have a curved geometry that conforms to the curvature of the ring 104. In some aspects, a charging device or other power source may include additional sensors that may be used to collect data in addition to, or in addition to, the data collected by the ring 104 itself.Additionally, a charging device or other power source for the ring 104 may function as the user device 106, in which case the charging device or other power source for the ring 104 may be configured to receive data from the ring 104, store and / or process data received from the ring 104, and communicate data between the ring 104 and the servers 110.

[0045] In some aspects, the ring 104 includes a power module 225 that can control the charging of the battery 210. For example, the power module 225 can be connected to an external wireless charging device that charges the battery 210 when connected to the ring 104. The charging device can include a reference structure that mates with a reference structure of the ring 104 to create a specific alignment with the ring 104 during charging. The power module 225 can also regulate the voltage(s) of the device electronics, regulate the power output to the device electronics, and monitor the state of charge of the battery 210. In some implementations, the battery 210 can include a protection circuit module (PCM) that protects the battery 210 from high-current discharge, overvoltage during charging, and undervoltage during discharging. The power module 225 can also include electrostatic discharge (ESD) protection.

[0046] The one or more temperature sensors 240 may be electrically coupled to the processing module 230a. The temperature sensor 240 may be configured to generate a temperature signal (e.g., temperature data) indicative of a temperature read or sensed by the temperature sensor 240. The processing module 230a may determine a temperature of the user at the location of the temperature sensor 240. For example, in the ring 104, temperature data generated by the temperature sensor 240 may indicate a temperature of a user at the user's finger (e.g., skin temperature). In some implementations, the temperature sensor 240 may contact the user's skin. In other implementations, a portion of the housing 205 (e.g., the inner housing 205a) may form a barrier (e.g., a thin, thermally conductive barrier) between the temperature sensor 240 and the user's skin.In some implementations, portions of the ring 104 configured to contact the user's finger may include thermally conductive portions and thermally insulating portions. The thermally conductive portions may conduct heat from the user's finger to the temperature sensors 240. The thermally insulating portions may insulate portions of the ring 104 (e.g., the temperature sensor 240) from the ambient temperature.

[0047] In some implementations, temperature sensor 240 may generate a digital signal (e.g., temperature data) that processing module 230a may use to determine the temperature. As another example, in cases where temperature sensor 240 comprises a passive sensor, processing module 230a (or a temperature sensor module 240) may measure a current / voltage generated by temperature sensor 240 and determine the temperature based on the measured current / voltage. Example temperature sensors 240 may include a thermistor, such as a negative temperature coefficient (NTC) thermistor, or other types of sensors, including resistors, transistors, diodes, and / or other electrical / electronic components.

[0048] Processing module 230a may sample the user's temperature over time. For example, processing module 230a may sample the user's temperature according to a sampling rate. An example sampling rate may include one sample per second, although processing module 230a may be configured to sample the temperature signal at other sampling rates higher or lower than one sample per second. In some implementations, processing module 230a may sample the user's temperature continuously day and night. Sampling at a sufficient rate (e.g., one sample per second) throughout the day may provide sufficient temperature data for the analysis described herein.

[0049] The processing module 230a may store the sampled temperature data in the memory 215. In some implementations, the processing module 230a may process the sampled temperature data. For example, the processing module 230a may determine average temperature values ​​over a specific period of time. In one example, the processing module 230a may determine an average temperature value per minute by summing all temperature values ​​collected over the minute and dividing by the number of samples over the minute. In a specific example where the temperature is sampled at one sample per second, the average temperature may be a sum of all sampled temperatures for one minute divided by sixty seconds. The memory 215 may store the average temperature values ​​over time. In some implementations, the memory 215 may store average temperatures (e.g.,one per minute) instead of sampled temperatures to save memory 215.

[0050] The sampling rate that may be stored in memory 215 may be configurable. In some implementations, the sampling rate may be the same day and night. In other implementations, the sampling rate may be changed day / night. In some implementations, the ring 104 may filter / reject temperature readings, such as large temperature spikes that are not indicative of physiological changes (e.g., a temperature spike from a hot shower). In some implementations, the ring 104 may filter / reject temperature readings that may not be reliable due to other factors, such as excessive movement during exercise (e.g., as indicated by a motion sensor 245).

[0051] Ring 104 (e.g., communication module) may transmit the sampled and / or average temperature data to user device 106 for storage and / or further processing. User device 106 may transmit the sampled and / or average temperature data to server 110 for storage and / or further processing.

[0052] Although the ring 104 is illustrated as being equipped with a single temperature sensor 240, the ring 104 may include multiple temperature sensors 240 at one or more locations, for example, along the inner housing 205a near the user's finger. In some implementations, the temperature sensors 240 may be standalone temperature sensors 240. Additionally or alternatively, one or more temperature sensors 240 may be included with other components (e.g., packaged with other components), such as the accelerometer and / or processor.

[0053] The processing module 230a may collect and process data from multiple temperature sensors 240 in a similar manner as described with respect to a single temperature sensor 240. For example, the processing module 230 may individually sample, average, and store temperature data from each of the multiple temperature sensors 240. In other examples, the processing module 230a may sample the sensors at different rates and average / store different values ​​for the different sensors. In some implementations, the processing module 230a may be configured to determine a single temperature based on the average of two or more temperatures determined by two or more temperature sensors 240 at different locations on the finger.

[0054] The temperature sensors 240 on the ring 104 can sense distal temperatures on the user's finger (e.g., on each finger). For example, one or more temperature sensors 240 on the ring 104 can sense a user's temperature from the underside of a finger or at another location on the finger. In some implementations, the ring 104 can continuously sense the distal temperature (e.g., at a sampling rate). Although the distal temperature measured by a ring 104 on the finger is described herein, other devices can measure temperature at the same / different locations. In some cases, the distal temperature measured on a user's finger may be different from the temperature measured on a user's wrist or other external body location. Additionally, the distal temperature measured on a user's finger (e.g., a "shell" temperature) may be different from the user's core temperature.Therefore, the ring 104 can provide a useful temperature signal that may not be detected at other internal / external body locations. In some cases, continuous fingertip temperature measurement can detect temperature fluctuations (e.g., small or large fluctuations) that may not be evident in core temperature. For example, continuous fingertip temperature measurement can detect minute-by-minute or hourly temperature fluctuations, providing additional insight that may not be available from other temperature measurements elsewhere on the body.

[0055] The ring 104 may include a PPG system 235. The PPG system 235 may include one or more optical transmitters that emit light. The PPG system 235 may also include one or more optical receivers that receive light emitted by the one or more optical transmitters. An optical receiver may generate a signal (hereinafter, a "PPG" signal) indicative of an amount of light received by the optical receiver. The optical transmitters may illuminate an area of ​​the user's finger. The PPG signal generated by the PPG system 235 may indicate blood flow to the illuminated area. For example, the PPG signal may indicate blood volume changes in the illuminated area caused by a user's pulse pressure. The processing module 230a may sample the PPG signal and determine a user's pulse waveform based on the PPG signal.The processing module 230a may determine a variety of physiological parameters based on the user's pulse waveform, such as a user's respiratory rate, heart rate, HRV, oxygen saturation, and other circulatory parameters.

[0056] In some implementations, the PPG system 235 may be configured as a reflective PPG system 235, where the optical receiver(s) receive transmitted light reflected by the portion of the user's finger. In some implementations, the PPG system 235 may be configured as a transmissive PPG system 235, where the optical transmitter(s) and optical receiver(s) are positioned opposite each other, such that light is transmitted directly through a portion of the user's finger to the optical receiver(s).

[0057] The number and ratio of transmitters and receivers included in the PPG system 235 can vary. Example optical transmitters can include light-emitting diodes (LEDs). The optical transmitters can emit light in the infrared spectrum and / or other spectra. Example optical receivers can include, among others, photosensors, phototransistors, and photodiodes. The optical receivers can be configured to generate PPG signals in response to the wavelengths received by the optical transmitters. The position of the transmitters and receivers can vary. Additionally, a single device can include reflective and / or transmissive PPG systems 235.

[0058] The Fig. The PPG system 235 illustrated in Figure 2 may, in some implementations, include a reflective PPG system 235. In these implementations, the PPG system 235 may include a centrally located optical receiver (e.g., at the bottom of the ring 104) and two optical transmitters located on either side of the optical receiver. In this implementation, the PPG system 235 (e.g., the optical receiver) may generate the PPG signal based on light received from one or both of the optical transmitters. In other implementations, other placements, combinations, and / or configurations of one or more optical transmitters and / or optical receivers are contemplated.

[0059] Processing module 230a may control one or both optical transmitters to emit light while sampling the PPG signal generated by the optical receiver. In some implementations, processing module 230a may cause the optical transmitter with the stronger received signal to emit light while sampling the PPG signal generated by the optical receiver. For example, the selected optical transmitter may continuously emit light while sampling the PPG signal at a sampling rate (e.g., 250 Hz).

[0060] Sampling the PPG signal generated by PPG system 235 may result in a pulse waveform, which may be referred to as a "PPG." The pulse waveform may indicate blood pressure over time for multiple cardiac cycles. The pulse waveform may include peaks indicative of cardiac cycles. Additionally, the pulse waveform may include respiration-induced variations that may be used to determine respiratory rate. Processing module 230a may, in some implementations, store the pulse waveform in memory 215. Processing module 230a may process the pulse waveform during its generation and / or from memory 215 to determine user physiological parameters described herein.

[0061] Processing module 230a may determine the user's heart rate based on the pulse waveform. For example, processing module 230a may determine the heart rate (e.g., in beats per minute) based on the time between peaks in the pulse waveform. The time between peaks may be referred to as the interbeat interval (IBI). Processing module 230a may store the determined heart rate values ​​and IBI values ​​in memory 215.

[0062] The processing module 230a may determine the HRV over time. For example, the processing module 230a may determine the HRV based on the variation in the IBIs. The processing module 230a may store the HRV values ​​over time in the memory 215. In addition, the processing module 230a may determine the user's respiratory rate over time. For example, the processing module 230a may determine the respiratory rate based on frequency modulation, amplitude modulation, or baseline modulation of the user's IBI values ​​over a certain period of time. The respiratory rate may be calculated in breaths per minute or as another respiratory rate (e.g., breaths per 30 seconds). The processing module 230a may store the user's respiratory rate values ​​over time in the memory 215.

[0063] The ring 104 may include one or more motion sensors 245, such as one or more accelerometers (e.g., 6-D accelerometers) and / or one or more gyroscopes (gyros). The motion sensors 245 may generate motion signals indicative of motion of the sensors. For example, the ring 104 may include one or more accelerometers that generate acceleration signals indicative of acceleration of the accelerometers. As another example, the ring 104 may include one or more gyro sensors that generate gyro signals indicative of angular motion (e.g., angular velocity) and / or changes in orientation. The motion sensors 245 may be included in one or more sensor packages. An exemplary acceleration / gyro sensor is a Bosch BMI160 inertial microelectromechanical system (MEMS) sensor, which can measure angular velocities and accelerations in three perpendicular axes.

[0064] The processing module 230a may sample the motion signals at a sampling rate (e.g., 50 Hz) and determine the motion of the ring 104 based on the sampled motion signals. For example, the processing module 230a may sample acceleration signals to determine the acceleration of the ring 104. As another example, the processing module 230a may sample a gyro signal to determine angular motion. In some implementations, the processing module 230a may store motion data in the memory 215. Motion data may include sampled motion data as well as motion data calculated based on the sampled motion signals (e.g., acceleration and angle values).

[0065] Ring 104 can store a variety of data described herein. For example, ring 104 can store temperature data, such as raw sampled temperature data and calculated temperature data (e.g., average temperatures). As another example, ring 104 can store PPG signal data, such as pulse waveforms and data calculated based on the pulse waveforms (e.g., heart rate values, IBI values, HRV values, and respiratory rate values). Ring 104 can also store motion data, such as sampled motion data indicating linear and angular movement.

[0066] The ring 104 or other computing device may calculate and store additional values ​​based on the sampled / calculated physiological data. For example, the processing module 230 may calculate and store various metrics, such as sleep metrics (e.g., a sleep score), activity metrics, and readiness metrics. In some implementations, additional values / metrics may be referred to as "derived values." The ring 104 or other computing / wearable device may calculate a variety of values / metrics related to movement. Example derived values ​​for movement data may include, but are not limited to, movement amount values, regularity values, intensity values, task metabolic equivalents (METs), and orientation values. Movement amounts, regularity values, intensity values, and METs may indicate a measure of the user's movement (e.g., speed / acceleration) over time.Orientation values ​​may indicate how the ring 104 is oriented on the user's finger and whether the ring 104 is worn on the left or right hand.

[0067] In some implementations, movement amounts and regularity values ​​can be determined by counting a number of acceleration spikes within one or more time periods (e.g., one or more 30-second to 1-minute periods). Intensity values ​​can indicate a number of movements and the associated intensity (e.g., acceleration values) of the movements. The intensity values ​​can be categorized as low, moderate, and high depending on their associated threshold acceleration values. METs can be determined based on the intensity of the movements during a time period (e.g., 30 seconds), the regularity / irregularity of the movements, and the number of movements associated with the different intensities.

[0068] In some implementations, processing module 230a may compress the data stored in memory 215. For example, processing module 230a may delete sampled data after performing calculations based on the sampled data. As another example, processing module 230a may average data over longer periods of time to reduce the number of stored values. In a specific example, if average temperatures for a user over one minute are stored in memory 215, processing module 230a may calculate average temperatures over a five-minute period for storage and then delete the one-minute average temperature data.The processing module 230a may compress data based on a variety of factors, such as the total amount of used / available memory 215 and / or an elapsed time since the ring 104 last transmitted the data to the user device 106.

[0069] Although a user's physiological parameters may be measured by sensors included in a ring 104, other devices may measure a user's physiological parameters. For example, although a user's temperature may be measured by a temperature sensor 240 included in ring 104, other devices may measure a user's temperature. In some examples, other wearable devices (e.g., wrist devices) may include sensors that measure physiological parameters of the user. Additionally, medical devices, such as external medical devices (e.g., wearable medical devices) and / or implantable medical devices, may measure a user's physiological parameters. One or more sensors on any type of computer may be used to implement the techniques described herein.

[0070] The physiological measurements may be taken continuously during the day and / or night. In some implementations, the physiological measurements may be taken during parts of the day and / or parts of the night. In some implementations, the physiological measurements may be taken in response to determining that the user is in a particular state, such as an active state, a resting state, and / or a sleeping state. For example, the ring 104 may take physiological measurements in a resting / sleeping state to capture cleaner physiological signals. In one example, the ring 104 or another device / system may detect when a user is resting and / or sleeping and capture physiological parameters (e.g., temperature) for that detected state.The devices / systems may use the resting / sleep physiological data and / or other data when the user is in other states to implement the techniques of the present disclosure.

[0071] In some implementations, as previously described herein, the ring 104 may be configured to collect, store, and / or process data and to transmit any of the data described herein to the user device 106 for storage and / or processing. In some aspects, the user device 106 includes a wearable application 250, an operating system (OS), a web browser application (e.g., web browser 280), one or more additional applications, and a GUI 275. The user device 106 may further include other modules and components, including sensors, audio devices, haptic feedback devices, and the like. The wearable application 250 may be an example of an application (e.g., "app") that may be installed on the user device 106. The wearable application 250 may be configured to collect data from the ring 104, store the collected data, and process the collected data as described herein.For example, the portable application 250 may include a user interface (UI) module 255, a capture module 260, a processing module 230b, a communication module 220b, and a storage module (e.g., database 265) configured to store application data.

[0072] In some cases, portable device 104 and user device 106 may be included in (or constitute) the same device. For example, in some cases, portable device 104 may be configured to execute portable application 250 and configured to display data via GUI 275.

[0073] The various data processing operations described herein may be performed by ring 104, user device 106, servers 110, or any combination thereof. For example, in some cases, data collected by ring 104 may be preprocessed and transmitted to user device 106. In this example, user device 106 may perform some data processing operations on the received data, transmit the data to servers 110 for data processing, or both. For example, in some cases, user device 106 may perform processing operations that require relatively low computing power and / or operations that require relatively low latency, while user device 106 may transmit the data to servers 110 for processing operations that require relatively high computing power and / or operations that allow for relatively higher latency.

[0074] In some aspects, the ring 104, the user device 106, and the server 110 of the system 200 can be configured to evaluate sleep patterns for a user. In particular, the respective components of the system 200 can be used to collect data from a user via the ring 104 and generate one or more scores (e.g., sleep score, readiness score) for the user based on the collected data. For example, as previously mentioned herein, the ring 104 of the system 200 can be worn by a user to collect data from the user, including temperature, heart rate, HRV, and the like. Data collected by the ring 104 can be used to determine when the user is sleeping in order to evaluate the user's sleep for a particular "sleep day."In some aspects, scores may be calculated for the user for each respective sleep day, such that a first sleep day is associated with a first set of scores and a second sleep day is associated with a second set of scores. Scores may be calculated for each respective sleep day based on data collected by ring 104 during the respective sleep day. Scores may include, but are not limited to, sleep scores, readiness scores, and the like.

[0075] In some cases, "sleep days" may coincide with traditional calendar days, so that a given sleep day lasts from midnight to midnight of that calendar day. In other cases, sleep days may be offset relative to calendar days. For example, sleep days may last from 6:00 PM (6:00 p.m.) one calendar day to 6:00 PM (6:00 p.m.) the following calendar day. In this example, 6:00 PM may serve as a "cutoff date" where data collected from the user before 6:00 PM is counted for the current sleep day, and data collected from the user after 6:00 PM is counted for the following sleep day. Due to the fact that most people sleep the most at night, offsetting sleep days relative to calendar days may allow the system 200 to evaluate sleep patterns for users in a way that aligns with their sleep schedules.In some cases, users can selectively adjust the timing of sleep days relative to calendar days (e.g., via the GUI) so that the sleep days correspond to the amount of time that the respective users typically sleep.

[0076] In some implementations, each overall score for a user for each respective day (e.g., sleep score, readiness score) may be determined / calculated based on one or more "contributors," "factors," or "contributing factors." For example, a user's overall sleep score may be calculated based on a number of contributors, including: total sleep, efficiency, restfulness, REM sleep, deep sleep, latency, timing, or any combination thereof. The sleep score may include any number of contributors. The "total sleep" contributor may refer to the sum of all sleep periods of the sleep day. The "efficiency" contributor may reflect the percentage of time spent in bed asleep compared to time awake and may be calculated using the efficiency average of long sleep periods (e.g.,primary sleep period) of the sleep day, weighted by the duration of each sleep period. The "Restlessness" contributor can indicate how restful the user's sleep is and can be calculated using the average of all sleep periods of the sleep day, weighted by the duration of each period. The "Restlessness" contributor can be based on a "Wake-up Count" (e.g., sum of all wake-ups (when the user wakes up) detected during different sleep periods), excessive movement, and a "Get-up Count" (e.g., sum of all get-up events (when the user gets out of bed) detected during different sleep periods).

[0077] The "REM sleep" contributor may refer to the total sum of REM sleep durations across all sleep periods of the sleep day, including REM sleep. Similarly, the "deep sleep" contributor may refer to the total sum of deep sleep durations across all sleep periods of the sleep day, including deep sleep. The "latency" contributor may indicate how long (e.g., average, median, longest) it takes the user to fall asleep and may be calculated using the average of long sleep periods throughout the sleep day, weighted by the duration of each period and the number of such periods (e.g., the consolidation of a particular sleep stage or stages may be its own contributor or may weight other contributors).Finally, the contributor “timing” may refer to the relative timing of sleep periods within the sleep day and / or calendar day and may be calculated using the average of all sleep periods of the sleep day, weighted by the duration of each period.

[0078] As another example, a user's overall readiness score may be calculated based on a number of contributors, including: sleep, sleep balance, heart rate, HRV balance, recovery index, temperature, activity, activity balance, or any combination thereof. The readiness score may include any number of contributors. The "sleep" contributor may refer to the combined sleep score of all sleep periods within the sleep day. The "sleep balance" contributor may refer to the cumulative duration of all sleep periods within the sleep day. In particular, the sleep balance may indicate to a user whether the sleep the user has received over a specific period of time (e.g., the past two weeks) is in balance with the user's needs.Typically, adults need 7-9 hours of sleep per night to stay healthy and alert and perform at their best both mentally and physically. However, it's normal to occasionally have a poor night's sleep, so the Sleep Balance contributor considers long-term sleep patterns to determine if each user's sleep needs are being met. The Resting Heart Rate contributor can display a lowest heart rate from the longest sleep period of the sleep day (e.g., primary sleep period) and / or the lowest heart rate from naps that occur after the primary sleep period.

[0079] Further referring to the "contributors" (e.g., factors, contributing factors) of the readiness assessment, the "HRV Balance" contributor can display a highest HRV average from the primary sleep period and the naps occurring after the primary sleep period. The "HRV Balance" contributor can help users track their recovery status by comparing their HRV trend over an initial period (e.g., two weeks) with an average HRV over a second, longer period (e.g., three months). The "Recovery Index" contributor can be calculated based on the longest sleep period. The Recovery Index measures how long it takes for a user's resting heart rate to stabilize during the night.A sign of very good recovery is that the user's resting heart rate stabilizes during the first half of the night, at least six hours before the user awakens, allowing the body time to recover for the next day. The "body temperature" contributor can be calculated based on the longest sleep period (e.g., primary sleep period) or based on a nap that occurs after the longest sleep period, if the user's highest temperature during the nap is at least 0.5°C higher than the highest temperature during the longest period. In some aspects, the ring can measure a user's body temperature while the user is sleeping, and the system 200 can display the user's average temperature relative to the user's baseline temperature. If a user's body temperature is outside their normal range (e.g.,significantly above or below 0.0), the contributor's body temperature may be highlighted (e.g., enter an "attention" state) or otherwise generate a warning for the user.

[0080] In some aspects, system 200 may support techniques for charging interface communication. The charging interface communication method described herein may include messages transmitted via inductive charge modulation. Portable device 104 may communicate by modulating a power input that is detected by the charging device and interpreted as one or more bits, and the charging device may communicate by modulating the power output that is detected by portable device 104 and interpreted as one or more bits.

[0081] To establish a connection, the charging device detects the proximity of the portable device 104 and outputs an initial or first maximum power level. The charging device may then start a timer and wait for a message from the portable device 104. If no message is received before the timer expires, the charging device reduces the power and restarts the timer. The charging device continues to wait for a message and reduce the power until a message is received. At the same time, the portable device 104 receives and detects the power and waits until the power is reduced below a threshold, then sends a message by modulating a power consumption. The threshold may be a power level or charge level of the portable device 104.The message displayed by the portable device 104 when the power level meets the threshold may be a connection setup message or another message. The charging device may receive the connection setup message and send a connection confirmation message to establish the charging connection. Although examples herein describe messaging in the context of connection setup (e.g., connection setup message and corresponding connection confirmation message), it should be understood that the techniques described herein may apply to other types of messaging purposes in addition to, or alternatively to, connection setup. Once the connection is established, the charging device and the portable device 104 may communicate messages throughout the charging process (e.g.,Connection maintenance messages, charging status messages, messages related to physiological or environmental data collected by the portable device, messages related to physiological or environmental data collected by the charging device, etc.).

[0082] Fig. 3 shows an example of a charging diagram 300 that supports charging interface communication according to aspects of the present disclosure. The charging diagram 300 may illustrate a wearable device 305 and a charging device 310. The wearable device 305 may be charged via the charging device 310 according to the charging interface communication methods described herein. In some implementations, the charging diagram 300 may implement or be implemented by aspects of the system 100, the system 200, or a combination thereof. The wearable device 305 (e.g., device, wearable ring device, ring, wearable wrist-worn device) may be an example of the wearable device 104 (e.g., the ring 104), as described with reference to Fig. 12 described.

[0083] The charging device 310 (e.g., charger, charging station) may include a receiving portion 320 configured to receive and contact portable devices such as the portable device 305. Although depicted as a recessed portion, the receiving portion 320 may be a flat surface (e.g., disc-shaped) or a raised surface. In some examples, the receiving portion 320 may include one or more retaining subportions 315, also referred to as a magnetic subportion, which are magnetic. The one or more retaining subportions 315 may exert an attractive force on a portable device 305 such that the portable device 305 is more firmly fixed in the charging position, which may prevent the portable device 305 from being accidentally loosened. The retaining subportion 315 may be a single strip of magnetic material or one or more retaining subportions.

[0084] The charging device 310 may also include a docking post 325 configured to fit within the inner peripheral surface of the portable device 305. In some examples, the docking post 325 may be configured to fit within the inner peripheral surfaces of different sized portable devices 305. The docking post 325 may have any shape, such as circular or semicircular, and does not need to directly contact the portable device 305. In some examples, the charging device 310 may not include a docking post 325. The charging device may also include an indicator 330 that may indicate the charging status, for example, by changing color. For example, the indicator 330 may be green when charging is complete, red during charging, and flashing red when the portable device 305 is not properly connected to the charging device 310 or to indicate another error.The display 330 may be another sensor or other element related to charging. In some examples, the charging device 310 may not include the display 330.

[0085] The portable device 305 may include inductive charging components and charging-based communication circuitry that may be activated or otherwise implemented to charge and communicate with the charging device 310 during charging. The charging device 310 may include inductive charging components and charging-based communication circuitry that may be deployed to charge the portable device 305 and communicate with the portable device 305. Communications may include connection establishment, connection status, charging status, charging information, transmission of physiological data, transmission of environmental data, and other communications (e.g., charging errors or other investigation and remediation-related communications between the charging device 310 and the portable device 305, or other negotiations) between the devices that may be beneficial.

[0086] The charging device 310 and the portable device 305 can communicate various messages by modulating the output power and the power consumption. The charging device 310 can output power 335 and detect when power is being drawn by the portable device 305 (e.g., detected power consumption 340). The output power levels 335 can correspond to the voltage levels detected at the portable device 305. That is, when the charging device 310 outputs more power, the portable device 305 can detect increased voltage levels. The portable device 305 can draw additional power in short bursts and / or according to a predefined pattern to communicate messages. The charging device 310 can detect the additional power drawn by the portable device as detected power consumption 340 and transmit the modulations of the power consumption as one or more messages (e.g.,as a series of bits) from the portable device 305.

[0087] To communicate messages, the charging device 310 and the portable device 305 may perform an initial connection procedure or connection establishment procedure. The charging device 310 may detect that the portable device 305 is present (e.g., by detecting an initial power consumption). The charging device may output power 335 at gradually decreasing levels until the threshold 345 is reached. The portable device 305 may receive the output power 335 from the charging device 310 and wait until the output power 335 reaches a level that satisfies the threshold 345. Once the output power level 335 reaches the threshold 345, the portable device 305 may output a connection establishment message 350 (or other message) by modulating a power consumption.The charging device 310 can detect the modulations in power consumption, resulting in an increased detected power consumption 340.

[0088] After the connection is established, the charging device 310 and the portable device 305 may exchange additional messages or communications 355. The charging device may increase the output power 335 to output communications 355 and may detect power drawn by the portable device 305 to output communications 355. The power drawn and drawn may be interpreted as a series of bits and further as a message. The connection setup message and other messages may be functionally equivalent. That is, although referred to herein as "connection setup message" and "additional message" for clarity of timing and purpose, the method for message transmission may be applied to any type of message.

[0089] The threshold 345 may be an overload protection threshold, which may be based on the charge level of the portable device 305 or another statically or dynamically defined charge level. For example, if the portable device 305 is nearly fully charged, the portable device 305 may have a lower threshold 345. If the portable device 305 has no charge, the portable device 305 may display the connection setup message 350 after the first output power level 335 from the charging device 310.

[0090] Fig. 4 shows an example of a charging flowchart 400 that supports charging interface communication according to aspects of the present disclosure. The charging flowchart 400 may describe a process for communicating messages between a portable device 405 and a charging device 410. In one example, the charging flowchart 400 describes a communication process for establishing and maintaining a communication connection between a portable device 405 and a charging device 410. However, the charging flowchart 400 may also be applied to communicating generic messages in addition to, or alternatively to, connection establishment messages. In some implementations, the charging flowchart 400 may implement or be implemented by aspects of the system 100, the system 200, the charging diagram 300, or a combination thereof. The portable device 405 (e.g.,Device, wearable ring device, ring) may be an example of the wearable device 104 (e.g., the ring 104), as described with reference to FIG. Fig. 12. The charging device 410 may be an example of the charging device as described with reference to Fig. 3 described.

[0091] The charger 410 may be in a sleep state prior to detecting the portable device 405. For example, at 411, the sleep state may include starting the microcontroller unit (MCU) of the charger 410, activating other circuits, completing self-diagnostic tests, etc. At 412, the charger 410 may perform load detection. Performing load detection may include measuring a power consumption (e.g., from a connected portable device 405). For example, a parameter (e.g., output) may be activated (e.g., set to "ON"), which may trigger various other parameters. Other parameters may include setting VBOOST to 50%, setting COIL_SWITCH to oscillate between ON and OFF (e.g., 100 ms ON, 1000 ms OFF), and increasing the Monitor Booster Input Current.If no load is detected, the charging device 410 may repeat the load detection process at 412 with a configured periodicity. If a load is detected, the charging device 410 may set the output power to a maximum level, or "high," at 413.

[0092] At 413, the charging device 410 may set the output power to "high" in response to detecting the load or detecting the portable device 405. In some examples, the portable device 405 may also detect the charging device 410. The highest output power or maximum output power may be preconfigured or otherwise determined. Setting the output power may include changing the VBOOST_PWM parameter to 50%.

[0093] After setting and transmitting the high output power, the charging device 410 may wait at 414 and set a wait timer. The charging device 410 may wait until the portable device 405 completes an adaptation. The charging device 410 may also mute all data connections and set a wait timer. The wait timer may be a timer (e.g., BLANK_TIMER = 50 ms) that defines the wait time. At 415, the charging device 410 may check if the wait timer is greater than 0. If the wait timer is greater than zero, indicating that the wait timer has not expired, the charging device 410 may continue waiting. If the wait timer is not greater than 0, indicating that the wait timer has expired, the charging device may proceed to step 416.

[0094] At 416, after the timer expires, the charging device 410 may enable communication reception and start a receive timer. The receive timer may be CHARGER_RX_TIMEOUT and may define a time (e.g., 50 ms) that the charging device 410 waits to receive a message from the portable device 405. The message may be a first message, such as a connection setup message. The message may be detected at the charging device 410 based on the detection of a modulation (e.g., an increase) in power consumption by the portable device 405.

[0095] At 417, the charging device 410 may determine whether a connection setup message (or other message) was received before the receive timer expires. If the charging device 410 detected a power consumption modulation before the receive timer expires, the charging device 410 may determine that a message was received and proceed to step 418. If not, the charging device 410 may proceed to evaluate and modify the output power starting at 420.

[0096] Once the charging device 410 has received the connection establishment message, the charging device 410 may set power levels (e.g., voltage levels) for communication at 418. Such levels may be representative of the output power and may include various VBOOST voltage level parameters (e.g., VBOOST-NORMAL-PWM = VBOOST_PWM, VBOOST-COMM-PWM = VBOOST_PWM3). After setting the power or voltage levels for communication, the charging device 410 may output a message, such as a connection confirmation message. At 419, the charging device 410 may send or otherwise output a connection confirmation message. The message may be communicated by modulating the output power, for example, by rapidly increasing the output power in short bursts or according to another predefined pattern.The power changes may be interpreted as bits by the portable device 405 and converted into a message. Steps 417-419 may be part of a successful connection establishment with the portable device 405 and enable the communication of future messages over the established connection.

[0097] If the charging device 410 has not received a message (e.g., a connection setup message) at 417 before the receive timer expires, the charging device 410 may perform a series of steps to modulate the power and transmit gradually decreasing output power levels until a message is received from the portable device 405.

[0098] At 420, the charging device 410 may determine whether the output power (e.g., voltage level) was lower than a threshold. If the output power is too low or lower than the threshold, there may be a problem with the communication with the portable device 405. For example, if the charging device 410 has reduced the output power several times and has not received a message from the portable device 405, there may be a problem unrelated to the output power. The portable device 405 may not be in sufficient proximity, or there may be another problem preventing the connection from being established.

[0099] Thus, if the output power is too low at 420, the charging device 410 may re-initiate the communication test. The charging device 410 may re-initiate communication by repeating step 413, setting the output power to high, and going through the process again. However, the charging device 410 may only attempt to re-initiate communication a certain number of times (e.g., #). For example, the charging device 410 may attempt to re-initiate communication if the number of attempts (e.g., RETRY_COUNTER) is less than a specified maximum, for example, up to four times. On the fourth attempt, the charging device 410 may proceed to step 422.

[0100] At 422, the charging device 410 may determine whether the load has been re-detected or whether the portable device 405 has been reattached or otherwise reconnected. If so, the charging device 410 may attempt to initiate communication again by setting the output power to high at 413. If no reattachment of the portable device is detected, the charging device 410 may return to 412, load detection, until a load is detected.

[0101] Returning to step 420, if the output power does not meet a threshold or is not too low, the charging device 410 may decrease the output power (e.g., voltage) at 423. After decreasing the output power, the charging device 410 may wait (at 414) for a response from the portable device 405 until the wait timer expires. The decrease in output power may be an incremental step, such as a predefined step. If the charging device 410 does not receive a response while proceeding through steps 414-417, the charging device 410 continues to decrease the output power until the output power is too low (at 420).

[0102] In summary, the charging device 410 identifies (at 412) the portable device 405, outputs high power (at 413), and then loops (steps 414-417, 420, 423) waiting for a response from the portable device 405, decreasing the output power, and waiting again. The charging device 410 gradually decreases the output power until (at 417) the charging device 410 receives a message or until (at 420) the output power is too low. The charging device 410 then attempts to recognize the portable device 405 before initiating communication again.

[0103] The portable device 405 has a process flow that interacts with the process flow of the charging device 410. The portable device 405 receives the output power, determines whether the output power is greater than a threshold, and then either communicates a connection setup message (or another message) or waits until the charging device 410 reduces the output power.

[0104] At 424 and 425, the portable device 405 may wake up and detect the charging device 410. For example, at 424, the portable device 405 may have no charge and must first wake up or boot to interact with the charging device 410. In some examples, the portable device 405 may already be awake and able to detect the charging device 410. At 425, the portable device 405 may detect the charging device 410, and if the output power of the charging device (e.g., the power received by the portable device 405) is within a range, the portable device 405 may automatically begin establishing a connection with the charging device 410. The range may be a power range defined by the manufacturer or another standard.

[0105] After detecting charging device 410, portable device 405 may determine at 426 whether the power received and detected by charging device 410 is at a level suitable for communication. For example, portable device 405 may compare the received power level (e.g., input power) to a communication power threshold. The detected power may be VCHARGER and the threshold may be Vz. If the power level is not at a level suitable for communication or is higher than the threshold, portable device 405 may continue to wait.

[0106] If the detected power is at a suitable level for communication or lower than the threshold, the portable device 405 may proceed to 427 and configure a voltage transfer load (e.g., power or voltage load) or a communication power load. The communication power load may be a voltage, for example, 1 volt. The load may be represented by a parameter (e.g., V_TX_LOAD for an adjustable PMIC LDO L2OUT output). The portable device 405 may also mute all data connections and set a timer (e.g., BLANK_TIMER = 50 ms).

[0107] At 428, the portable device 405 may apply the load or voltage to a load resistor (e.g., 330R), which may enable an output parameter (e.g., L2OUT output). At 429, the portable device 405 may wait until the charging input (e.g., VCHARGER) has stabilized. The wait time may be defined (e.g., 2 ms).

[0108] After waiting for the charging input to stabilize, the portable device 405 may determine at 430 whether the input power is below a threshold. For example, the portable device 405 may compare the detected input power (e.g., charging input, detected voltage, VCHARGER) to a threshold. The threshold may be a maximum input charge value that the portable device 405 can receive. The threshold may depend on the state of charge of the portable device 405. If the portable device 405 has a higher state of charge, the threshold may be lower, and vice versa. If the input power is below the threshold, the portable device 405 may proceed to 434. If the input power is not below the threshold or is too high, the portable device 405 may proceed to 431 for further diagnosis.

[0109] At 431, if the input power is not below the threshold and is too high, the portable device 405 may determine whether the voltage is set to the maximum (e.g., V_TX_LOAD = 4V). If the load is not set to the maximum, the portable device 405 may increase the adjustable output voltage at 432 (e.g., V_TX_COMM = V_TX_LOAD + 0.3V) and then wait again at 429 until the charging input stabilizes. If the voltage is set to the maximum at 431, the portable device 405 may use the maximum load for communication (V_TX_COMM = V_TX_LOAD) at 433 and proceed to 435, disabling the communication load.

[0110] If at 430 the input power is below the threshold, the portable device 405 may proceed to 434. At 434, the portable device 405 may reduce a communication load. Reducing the communication load may implement a safety margin for the detected input power (e.g., V_TX_COMM = V_TX_LOAD - 0.3 V).

[0111] At 435, portable device 405 may deactivate the communication load (e.g., deactivate L2OUT output). At 436, portable device 405 may check whether the timer set at 427 is greater than zero. If the timer (e.g., BLANK_TIMER) is greater than 0 or has not expired, portable device 405 may wait until the timer expires.

[0112] If the timer is not greater than 0 or has expired, the portable device 405 may enable communication and send a message at 437. The message may be communicated by rapidly drawing power in one or more short bursts. The message may be a connection setup message. The portable device 405 may display the message using a predetermined communication level (e.g., V_TX_COMM level). Enabling communication may include enabling circuitry within the portable device 405 related to communication with the charging device 410.

[0113] At 438, after displaying the message, the portable device 405 may enable message reception and set a reception timer (e.g., RING_RX_TIMEOUT = 50 ms). At 439, the portable device 405 may determine whether a message is received from the charging device 410 before the reception timer expires. If the message is not received before the reception timer expires, the portable device 405 determines that the connection is not established at 440. If the portable device 405 receives a message from the charging device 410, the portable device 405 may determine that the connection is established at 441.

[0114] Fig. 5 shows an example of a charging flowchart 500 that supports charging interface communication according to aspects of the present disclosure. The charging flowchart 500 describes communications between a charging device 510 and a wearable device 505 after initial connection establishment. In some implementations, the charging flowchart 500 may implement or be implemented by aspects of the system 100, the system 200, the charging diagram 300, the charging flowchart 400, or a combination thereof. The wearable device 505 (e.g., device, wearable ring device, wearable wrist device, ring) may be an example of the wearable device 104 (e.g., the ring 104), as described with reference to Fig. 12. The charging device 510 (e.g., charger) may be an example of the charging device 310 as described with reference to Fig. 3 described.

[0115] After establishing a connection, the charging device 510 and the portable device 505 may communicate one or more additional messages. At 515, the charging device 510 may enable communications, such as receiving messages from the portable device 505 (e.g., RX ENABLE=TRUE). The charging device 510 may then set a receive timer at 516 (e.g., CHARGER_RX_TIMEROUT=5000 ms). The portable device 505 may be in a charging state at 519. The portable device 505 may periodically send messages to the charging device 510 at 520.

[0116] At 517, the charging device 510 may determine whether a message was received from the portable device 505 before the receive timer expires (e.g., CHARGER_RX_TIMEROUT > 0?). If the charging device 510 has not received a message and the timer has reached zero, the charging device 510 may proceed to step 518 and initiate load detection, as shown in Fig. 4. When the charging device 510 receives a message, the charging device 510 may reset the receive timer and wait for another message.

[0117] The message may be displayed via modulations (e.g., rapid bursts) of power from the portable device 505. Messages may include indicating to the charging device 510 to maintain the power level, increase the power level, or decrease the power level. In some examples, the portable device 505 may be set to send a message periodically, for example, every second.

[0118] Fig. 6 shows an example of a process flow diagram 600 that supports charging interface communication according to aspects of the present disclosure. The process flow diagram 600 illustrates and describes the communication of messages between a charging device 610 and a portable device 605. In some examples, the communication process may include establishing a communication connection between a charging device 610 and a portable device 605. In some implementations, the process flow diagram 600 may implement or be implemented by aspects of the system 100, the system 200, the charging diagram 300, the charging flow diagram 400, the charging flow diagram 500, or a combination thereof. The portable device 605 (e.g., device, portable ring device, ring) may be an example of the portable device 104 (e.g., the ring 104), as described with reference to Fig. 12. The charging device 610 may be an example of the charging device 305 as described with reference to Fig. 3 described.

[0119] In process flowchart 600, the operations between the wearable device 605 and the charging device 610 may be performed in different orders or at different times. Some operations may also be omitted from the process flowchart 600, or other operations may be added. Although the charging device 610 and the wearable device 605 are depicted as performing the operations of the process flowchart 600, some aspects of some operations may also be performed by one or more other devices. For example, the wearable device 605 may be a wearable ring device or a wearable wrist-worn device.

[0120] At 620, the charging device 610 may detect that the portable device 605 is attached to the charging device 610 based on a load detection method.

[0121] At 625, the portable device 605 may receive a sequence of gradually decreasing output power levels from the charging device 610 via inductive charging components, wherein the output power levels correspond to the voltage levels detected at the portable device 605. The charging device 610 may output a sequence of gradually decreasing output power levels to the portable device 605 via inductive charging components and charging-based communication circuitry.

[0122] Outputting the power levels may include outputting a first power level and outputting a second power level that is less than the first power level if the connection setup message is not received before a configured timer expires. The first power level may be an initial power level. For example, the charging device 610 may output an initial power level of the sequence of gradually decreasing output power levels based on the detection of the portable device 605.

[0123] At 630, the portable device 605 may activate a charging-based communication circuit within the portable device 605 when a first output power level of the sequence of gradually decreasing output power levels is detected to fall below an overload protection threshold. The overload protection threshold may be based on one of a plurality of charge levels of the portable device.

[0124] At 635, the portable device 605 may output a first message, such as a connection setup message or another type of message, to the charging device 610 via the inductive charging components and the charging-based communication circuitry. The charging device 610 may receive the connection setup message via the inductive charging components and the charging-based communication circuitry. At the charging device 610, receiving the connection setup message may include detecting a modulation of power consumption from the portable device with respect to a base charging voltage and converting the modulation of power consumption into a series of bits via the charging-based communication circuitry.

[0125] At the portable device 605, outputting the connection setup message may include modulating a power consumption with respect to a base charging voltage. After outputting the connection setup message, the portable device 605 may activate a receive timer.

[0126] In some examples, the portable device 605 may select a maximum voltage load based on the detected first output power level being greater than the overload protection threshold and output the connection setup message using the maximum voltage load.

[0127] At 640, the portable device 605 may receive a second message, such as a connection confirmation message or another message in response to the first message (e.g., a connection setup message), from the charging device and via the inductive charging components and the charging-based communication circuitry. The charging device 610 may output the connection confirmation message via the inductive charging components and the charging-based communication circuitry. Outputting the connection confirmation messages may include modulating an output power with respect to a base charging voltage.

[0128] At the portable device 605, receiving the connection confirmation message may include detecting a modulation of the output power from the charging device and converting the output power modulation into a series of bits via the charging-based communication circuitry. The portable device 605 may receive the connection confirmation message before the receive timer expires.

[0129] At 645, after outputting the connection establishment message to the charging device 610 and via the inductive charging components and the charging-based communication circuitry, the portable device 605 may output one or more additional messages based at least in part on modulations of power input relative to a base charging voltage. The portable device 605 may also receive, after receiving the connection confirmation message from the charging device and via the inductive charging components and the charging-based communication circuitry, one or more additional messages based at least in part on modulations of output power relative to a base charging voltage.

[0130] Similarly, the charging device 610 may receive and output one or more additional messages based at least in part on modulations of the output power with respect to a base charging voltage.

[0131] Fig. 7 shows a block diagram 700 of a device 705 that supports charging interface communication according to aspects of the present disclosure. The device 705 may include an input module 710, an output module 715, and a portable device manager 720. The device 705 or one or more components of the device 705 (e.g., the input module 710, the output module 715, and the portable device manager 720) may include at least one processor that may be coupled to at least one memory to support the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0132] For example, the portable device manager 720 may include a power level receiving component 725, a circuit activation component 730, a message output component 735, a message receiving component 740, or any combination thereof. In some examples, the portable device manager 720 or various components thereof may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise in cooperation with the input module 710, the output module 715, or both. For example, the portable device manager 720 may receive information from the input module 710, send information to the output module 715, or be integrated in combination with the input module 710, the output module 715, or both to receive information, transmit information, or perform various other operations described herein.

[0133] The power level receiving component 725 may be configured as, or otherwise support, means for receiving a sequence of gradually decreasing output power levels from a charging device via inductive charging components, wherein the output power levels correspond to the voltage levels detected at the portable device. The circuit activation component 730 may be configured as, or otherwise support, means for activating a charging-based communication circuit within the portable device upon detecting a first output power level of the sequence of gradually decreasing output power levels that falls below an overload protection threshold. The message output component 735 may be configured as, or otherwise support, means for outputting a connection setup message to the charging device and via the inductive charging components and the charging-based communication circuit.The message receiving component 740 may be configured to provide or otherwise support means for receiving a connection confirmation message from the charging device and via the inductive charging components and the charging-based communication circuitry in response to the connection setup message.

[0134] Fig. 8 shows a block diagram 800 of a portable device manager 820 that supports charging interface communication according to aspects of the present disclosure. The portable device manager 820 may be an example of aspects of a portable device manager or a portable device manager 720, or both, as described herein. The portable device manager 820 or various components thereof may be an example of means for performing various aspects of charging interface communication, as described herein. For example, the portable device manager 820 may include a power level receive component 825, a circuit enable component 830, a message output component 835, a message receive component 840, a timer enable component 845, a receive timer component 850, a load select component 855, or any combination thereof.Each of these components or components of subcomponents thereof (e.g., one or more processors, one or more memories) can communicate with each other directly or indirectly (e.g., via one or more buses).

[0135] The power level receiving component 825 may be configured as, or otherwise support, means for receiving a sequence of gradually decreasing output power levels from a charging device via inductive charging components, wherein the output power levels correspond to the voltage levels detected on the portable device. The circuit activation component 830 may be configured as, or otherwise support, means for activating a charging-based communication circuit within the portable device upon detecting a first output power level of the sequence of gradually decreasing output power levels that falls below an overload protection threshold. The message output component 835 may be configured as, or otherwise support, means for outputting a connection setup message to the charging device and via the inductive charging components and the charging-based communication circuit.The message receiving component 840 may be configured as a means for receiving, or otherwise supporting, a connection confirmation message from the charging device and via the inductive charging components and the charging-based communication circuitry in response to the connection setup message.

[0136] In some examples, the message output component 835 may be configured to support the output of the connection setup message as a means for modulating power consumption with respect to a base charging voltage or may otherwise support this.

[0137] In some examples, the message receiving component 840 may be configured to support receiving the connection confirmation message in response to the connection setup message, as a means for detecting or otherwise supporting output power modulation from the charging device. In some examples, the message receiving component 840 may be configured to support receiving the connection confirmation message in response to the connection setup message, as a means for converting the output power modulation into a series of bits via the charging-based communication circuitry.

[0138] In some examples, the overload protection threshold is based at least in part on a charge level of one of a plurality of charge levels of the portable device.

[0139] In some examples, the timer activation component 845 may be configured as, or otherwise support, means for activating a receive timer based at least in part on the issuance of the connection setup message. In some examples, the receive timer component 850 may be configured as, or otherwise support, means for receiving the connection confirmation message before the receive timer expires.

[0140] In some examples, the message output component 835 may be configured as, or otherwise support, means for outputting one or more additional messages after outputting the connection setup message to the charging device and via the inductive charging components and the charging-based communication circuitry based at least in part on modulations of a power consumption with respect to a base charging voltage.

[0141] In some examples, the message receiving component 840 may be configured as or otherwise support means for receiving one or more additional messages after receiving the connection confirmation message from the charging device and via the inductive charging components and the charging-based communication circuitry based at least in part on modulations of the output power with respect to a base charging voltage.

[0142] In some examples, load selection component 855 may be configured as, or otherwise support, means for selecting a maximum voltage load based at least in part on the detected first output power level being greater than the overload protection threshold. In some examples, message output component 835 may be configured as, or otherwise support, means for outputting the connection setup message using the maximum voltage load.

[0143] In some examples, the wearable device is a wearable ring device or a wearable wrist device.

[0144] Fig. 9 shows a diagram of a system 900 including a device 905 (e.g., wearable device) that supports charging interface communication according to aspects of the present disclosure. Device 905 may be an example of device 705 or include components thereof, as described herein. Device 905 may be an example of a wearable device 104, as previously described herein. Device 905 may include components for bidirectional communications, including components for sending and receiving communications with a user device 106 and a server 110, such as a wearable device manager 920, a communication module 910, an antenna 915, a sensor component 925, a power module 930, at least one memory 935, at least one processor 940, and a wireless device 950. These components may communicate electronically or be otherwise coupled (e.g.,operational, communicative, functional, electronic, electrical) via one or more buses (e.g. a bus 945).

[0145] For example, the portable device manager 920 may be configured as, or otherwise support, means for receiving a sequence of gradually decreasing output power levels from a charging device via inductive charging components, wherein the output power levels correspond to the voltage levels detected at the portable device. The portable device manager 920 may be configured as, or otherwise support, means for activating a charging-based communication circuit within the portable device upon detecting a first output power level of the sequence of gradually decreasing output power levels that falls below an overload protection threshold.The portable device manager 920 may be configured to provide or otherwise support means for outputting a connection setup message to the charging device and via the inductive charging components and the charging-based communication circuitry. The portable device manager 920 may be configured to provide or otherwise support means for receiving a connection confirmation message from the charging device and via the inductive charging components and the charging-based communication circuitry in response to the connection setup message.

[0146] By incorporating or configuring the portable device manager 920 according to the examples described herein, the device 905 may support charging interface communication techniques, which may result in various benefits, including, but not limited to: improved communication reliability, reduced latency, improved user experience associated with reduced processing, reduced power consumption, more efficient use of communication resources, improved coordination between devices, longer battery life, and improved use of processing capacity.

[0147] Fig. 10 shows a block diagram 1000 of a device 1005 (e.g., portable device, charger) that supports charging interface communication according to aspects of the present disclosure. The device 1005 may include an input module 1010, an output module 1015, and a portable application 1020. The device 1005 or one or more components of the device 1005 (e.g., the input module 1010, the output module 1015, and the portable application 1020) may include at least one processor that may be coupled to at least one memory to support the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0148] The input module 1010 may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to disease detection techniques). Information may be passed to other components of the device 1005. The input module 1010 may use a single antenna or a set of multiple antennas.

[0149] Output module 1015 may provide a means for transmitting signals generated by other components of device 1005. For example, output module 1015 may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to disease detection techniques). In some examples, output module 1015 may be combined with input module 1010 in a transceiver module. Output module 1015 may use a single antenna or a set of multiple antennas.

[0150] For example, the portable application 1020 may include a power output component 1025, a message reception component 1030, a message output component 1035, or any combination thereof. In some examples, the portable application 1020 or various components thereof may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise in cooperation with the input module 1010, the output module 1015, or both. For example, the portable application 1020 may receive information from the input module 1010, send information to the output module 1015, or be integrated in combination with the input module 1010, the output module 1015, or both to receive information, transmit information, or perform various other operations described herein.

[0151] The power output component 1025 may be configured as, or otherwise support, means for outputting a sequence of gradually decreasing output power levels to a portable device via inductive charging components and charging-based communication circuitry, wherein the output power levels correspond to the voltage levels detected at the portable device. The message receiving component 1030 may be configured as, or otherwise support, means for receiving a connection setup message from the portable device and via the inductive charging components and charging-based communication circuitry. The message output component 1035 may be configured as, or otherwise support, means for outputting a connection confirmation message to the portable device and via the inductive charging components and charging-based communication circuitry in response to the connection setup message.

[0152] Fig. 11 shows a block diagram 1100 of a portable application 1120 (e.g., charger) that supports charging interface communication according to aspects of the present disclosure. The portable application 1120 may be an example of aspects of a portable application or a portable application 1120, or both, as described herein. The portable application 1120 or various components thereof may be an example of means for performing various aspects of the charging interface communication as described herein. For example, the portable application 1120 may include a power output component 1125, a message reception component 1130, a message output component 1135, a portable device detection component 1140, or any combination thereof. Each of these components or components of subcomponents thereof (e.g., one or more processors, one or more memories) may communicate directly or indirectly with each other (e.g.,B. via one or more buses).

[0153] The power output component 1125 may be configured as, or otherwise support, means for outputting a sequence of gradually decreasing output power levels to a portable device via inductive charging components and charging-based communication circuitry, wherein the output power levels correspond to voltage levels detected at the portable device. The message receiving component 1130 may be configured as, or otherwise support, means for receiving a connection setup message from the portable device and via the inductive charging components and charging-based communication circuitry. The message output component 1135 may be configured as, or otherwise support, means for outputting a connection confirmation message to the portable device and via the inductive charging components and charging-based communication circuitry in response to the connection setup message.

[0154] In some examples, the power output component 1125 may be configured to support outputting the sequence of gradually decreasing output power levels, or may otherwise support outputting a first power level. In some examples, the power output component 1125 may be configured to support outputting the sequence of gradually decreasing output power levels, or may otherwise support outputting a second power level that is less than the first power level if the connection setup message is not received before the expiration of a configured timer.

[0155] In some examples, the portable device detection component 1140 may be configured as, or otherwise support, means for detecting that the portable device is attached to the charging device based at least in part on a load detection method. In some examples, the power output component 1125 may be configured as, or otherwise support, means for outputting an initial power level of the sequence of gradually decreasing output power levels based at least in part on detecting the portable device.

[0156] In some examples, the message receiving component 1130 may be configured to support receipt of the connection setup message as a means for detecting or otherwise supporting a power consumption modulation from the portable device with respect to a base charging voltage. In some examples, the message receiving component 1130 may be configured to support receipt of the connection setup message as a means for converting the power consumption modulation into a series of bits via the charging-based communication circuitry.

[0157] In some examples, the message output component 1135 may be configured to support the output of the connection confirmation message in response to the connection setup message, or may otherwise support the output of the connection confirmation message, as a means for modulating an output power with respect to a base charging voltage.

[0158] In some examples, the message receiving component 1130 may be configured as or otherwise support means for receiving one or more additional messages after receiving the connection setup message from the portable device and via the inductive charging components and the charging-based communication circuitry based at least in part on modulations of power consumption with respect to a base charging voltage.

[0159] In some examples, the message output component 1135 may be configured as, or otherwise support, means for outputting one or more additional messages after outputting the connection confirmation message to the portable device and via the inductive charging components and the charging-based communication circuitry based at least in part on modulations of the output power with respect to a base charging voltage.

[0160] Fig. 12 shows a diagram of a system 1200 with a charging device 1205 that supports charging interface communication according to aspects of the present disclosure. The charging device 1205 may be an example of a device 1005 or include its components, as described herein. The charging device 1205 may be an example of a user device 106, as previously described herein. The charging device 1205 may include components for bidirectional communications, including components for sending and receiving communications with a portable device 104 and a server 110, such as a portable application 1220, a communication module 1210, an antenna 1215, a user interface component 1225, a database (application data) 1230, at least one memory 1235, and at least one processor 1240. These components may communicate electronically or be otherwise coupled (e.g.,operational, communicative, functional, electronic, electrical) via one or more buses (e.g. a bus 1245).

[0161] The communication module 1210 may manage input and output signals for the charging device 1205 via the antenna 1215. The communication module 1210 may be an example of the communication module 220b of the Fig. 2. In this regard, the communication module 1210 may manage communications with the ring 104 and the server 110, as shown in Fig. 2. The communication module 1210 may also manage peripherals that are not integrated into the charging device 1205. In some cases, the communication module 1210 may represent a physical connection or port to an external peripheral device. In some cases, the communication module 1210 may use an operating system such as iOS®, ANDROID®, MS-DOS®, MS-WINDOWS®, OS / 2®, UNIX®, LINUX®, or another well-known operating system. In other cases, the communication module 1210 may represent or interact with a portable device (e.g., Ring 104), a modem, a keyboard, a mouse, a touchscreen, or a similar device. In some cases, the communication module 1210 may be implemented as part of the processor 1240.In some examples, a user may interact with the charging device 1205 via the communication module 1210, the user interface component 1225, or via hardware components controlled by the communication module 1210.

[0162] In some cases, the charging device 1205 may include a single antenna 1215. However, in some other cases, the charging device 1205 may have more than one antenna 1215 that can simultaneously transmit or receive multiple wireless transmissions. The communication module 1210 may communicate bidirectionally via the one or more antennas 1215, wired, or wireless connections, as described herein. For example, the communication module 1210 may be a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The communication module 1210 may also include a modem to modulate the packets, provide the modulated packets to one or more antennas 1215 for transmission, and demodulate packets received from the one or more antennas 1215.

[0163] The user interface component 1225 may manage data storage and processing in a database 1230. In some cases, a user may interact with the user interface component 1225. In other cases, the user interface component 1225 may operate automatically without user interaction. The database 1230 may be an example of a single database, a distributed database, multiple distributed databases, a data store, a data lake, or an emergency backup database.

[0164] Memory 1235 may include RAM and ROM. Memory 1235 may store computer-readable, computer-executable software, including instructions that, when executed, cause processor 1240 to perform various functions described herein. In some cases, memory 1235 may include, among other things, a BIOS that may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0165] Processor 1240 may comprise an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, processor 1240 may be configured to operate a memory array using a memory controller. In other cases, a memory controller may be integrated into processor 1240. Processor 1240 may be configured to execute computer-readable instructions stored in memory 1235 to perform various functions (e.g., functions or tasks that support a method and system for sleep phase algorithms).

[0166] For example, portable application 1220 may be configured or otherwise support means for outputting a sequence of gradually decreasing output power levels to a portable device via inductive charging components and charging-based communication circuitry, wherein the output power levels correspond to voltage levels detected at the portable device. Portable application 1220 may be configured or otherwise support means for receiving a connection setup message from the portable device and via the inductive charging components and charging-based communication circuitry. Portable application 1220 may be configured or otherwise support means for outputting a connection confirmation message to the portable device and via the inductive charging components and charging-based communication circuitry in response to the connection setup message.

[0167] By incorporating or configuring the portable application 1220 according to the examples described herein, the charging device 1205 may support charging interface communication techniques, which may result in various benefits, including, but not limited to: improved communication reliability, reduced latency, improved user experience associated with reduced processing, reduced power consumption, more efficient use of communication resources, improved coordination between devices, longer battery life, and improved utilization of processing capacity.

[0168] Portable application 1220 may include an application (e.g., "app"), program, software, or other component configured to facilitate communications with a ring 104, a server 110, other user devices 106, and the like. For example, portable application 1220 may include an application executable on a user device 106 that is configured to receive data (e.g., physiological data) from a ring 104, perform processing operations on the received data, send and receive data with the servers 110, and cause the presentation of data to a user 102.

[0169] Fig. 13 shows a flowchart illustrating a method 1300 that supports charging interface communication according to aspects of the present disclosure. The operations of method 1300 may be implemented by a portable device or its components, as described herein. For example, the operations of method 1300 may be performed by a portable device, as described with reference to Fig. 1 to 9. In some examples, a portable device may execute a set of instructions to control the functional elements of the portable device to perform the described functions. Additionally or alternatively, the portable device may perform aspects of the described functions using specialized hardware.

[0170] At 1305, the method may include receiving a sequence of gradually decreasing output power levels from a charging device via inductive charging components, wherein the output power levels correspond to the voltage levels detected at the portable device. The operations of block 1305 may be performed according to the examples disclosed herein. In some examples, aspects of the operations of 1305 may be performed by a power level receiving component 825, as described with reference to Fig. 8 described.

[0171] At 1310, the method may include activating a charging-based communication circuit within the portable device upon detecting a first output power level of the sequence of gradually decreasing output power levels that falls below an overload protection threshold. The operations of block 1310 may be performed according to the examples disclosed herein. In some examples, aspects of the operations of 1310 may be performed by a circuit activation component 830, as described with reference to Fig. 8 described.

[0172] At 1315, the method may include outputting a connection setup message to the charging device and via the inductive charging components and the charging-based communication circuitry. The operations of block 1315 may be performed according to the examples disclosed herein. In some examples, aspects of the operations of 1315 may be performed by a message output component 835, as described with reference to Fig. 8 described.

[0173] At 1320, the method may include receiving a connection confirmation message from the charging device and via the inductive charging components and the charging-based communication circuitry in response to the connection setup message. The operations of block 1320 may be performed according to the examples disclosed herein. In some examples, aspects of the operations of 1320 may be performed by a message receiving component 840, as described with reference to Fig. 8 described.

[0174] Fig. 14 shows a flowchart illustrating a method 1400 that supports charging interface communication according to aspects of the present disclosure. The operations of method 1400 may be implemented by a portable device or its components, as described herein. For example, the operations of method 1400 may be performed by a portable device, as described with reference to Fig. 1 to 9. In some examples, a portable device may execute a set of instructions to control the functional elements of the portable device to perform the described functions. Additionally or alternatively, the portable device may perform aspects of the described functions using specialized hardware.

[0175] At 1405, the method may include receiving a sequence of gradually decreasing output power levels from a charging device via inductive charging components, wherein the output power levels correspond to the voltage levels detected at the portable device. The operations of block 1405 may be performed according to the examples disclosed herein. In some examples, aspects of the operations of 1405 may be performed by a power level receiving component 825, as described with reference to Fig. 8 described.

[0176] At 1410, the method may include activating a charging-based communication circuit within the portable device upon detecting a first output power level of the sequence of gradually decreasing output power levels that falls below an overload protection threshold. The operations of block 1410 may be performed according to the examples disclosed herein. In some examples, aspects of the operations of 1410 may be performed by a circuit activation component 830, as described with reference to Fig. 8 described.

[0177] At 1415, the method may include outputting a connection setup message to the charging device and via the inductive charging components and the charging-based communication circuitry. The operations of block 1415 may be performed according to the examples disclosed herein. In some examples, aspects of the operations of 1415 may be performed by a message output component 835, as described with reference to Fig. 8 described.

[0178] At 1420, the method may include activating a receive timer based at least in part on the issuance of the connection setup message. The operations of block 1420 may be performed according to the examples disclosed herein. In some examples, aspects of the operations of 1420 may be performed by a timer activation component 845, as described with reference to Fig. 8 described.

[0179] At 1425, the method may include receiving a connection confirmation message from the charging device and via the inductive charging components and the charging-based communication circuitry in response to the connection setup message. The operations of block 1425 may be performed according to the examples disclosed herein. In some examples, aspects of the operations of 1425 may be performed by a message receiving component 840, as described with reference to Fig. 8 described.

[0180] At 1430, the method may include receiving the connection confirmation message before the receive timer expires. The operations of block 1430 may be performed according to the examples disclosed herein. In some examples, aspects of the operations of 1430 may be performed by a receive timer component 850, as described with reference to Fig. 8 described.

[0181] Fig. 15 shows a flowchart illustrating a method 1500 that supports charging interface communication according to aspects of the present disclosure. The operations of method 1500 may be implemented by a charging device or its components, as described herein. For example, the operations of method 1500 may be performed by a charging device, as described with reference to Fig. 1 to 6 and 10 to 12. In some examples, a charging device may execute a set of instructions to control the functional elements of the charging device to perform the described functions. Additionally or alternatively, the user device may perform aspects of the described functions using specialized hardware.

[0182] At 1505, the method may include outputting a sequence of gradually decreasing output power levels to a portable device via inductive charging components and a charging-based communication circuit, wherein the output power levels correspond to the voltage levels detected at the portable device. The operations of block 1505 may be performed according to the examples disclosed herein. In some examples, aspects of the operations of 1505 may be performed by a power output component 1125, as described with reference to Fig. 11 described.

[0183] At 1510, the method may include receiving a connection setup message from the portable device and via the inductive charging components and the charging-based communication circuitry. The operations of block 1510 may be performed according to the examples disclosed herein. In some examples, aspects of the operations of 1510 may be performed by a message receiving component 1130, as described with reference to Fig. 11 described.

[0184] At 1515, the method may include outputting a connection confirmation message to the portable device and via the inductive charging components and the charging-based communication circuitry in response to the connection setup message. The operations of block 1515 may be performed according to the examples disclosed herein. In some examples, aspects of the operations of 1515 may be performed by a message output component 1135, as described with reference to Fig. 11 described.

[0185] Fig. 16 shows a flowchart illustrating a method 1600 that supports charging interface communication according to aspects of the present disclosure. The operations of method 1600 may be implemented by a charging device or its components, as described herein. For example, the operations of method 1600 may be performed by a charging device, as described with reference to Fig. 1 to 6 and 10 to 12. In some examples, a charging device may execute a set of instructions to control the functional elements of the user device to perform the described functions. Additionally or alternatively, the charging device may perform aspects of the described functions using specialized hardware.

[0186] At 1605, the method may include detecting that the portable device is attached to the charging device based at least in part on a load detection method. The operations of block 1605 may be performed according to the examples disclosed herein. In some examples, aspects of the operations of 1605 may be performed by a portable device detection component 1140, as described with reference to Fig. 11 described.

[0187] At 1610, the method may include outputting a sequence of gradually decreasing output power levels to a portable device via inductive charging components and a charging-based communication circuit, wherein the output power levels correspond to the voltage levels detected at the portable device. The operations of block 1610 may be performed according to the examples disclosed herein. In some examples, aspects of the operations of 1610 may be performed by a power output component 1125, as described with reference to Fig. 11 described.

[0188] At 1615, the method may include outputting an initial power level of the sequence of gradually decreasing output power levels based at least in part on detecting the portable device. The operations of block 1615 may be performed according to the examples disclosed herein. In some examples, aspects of the operations of 1615 may be performed by a power output component 1125, as described with reference to Fig. 11 described.

[0189] At 1620, the method may include receiving a connection setup message from the portable device and via the inductive charging components and the charging-based communication circuitry. The operations of block 1620 may be performed according to the examples disclosed herein. In some examples, aspects of the operations of 1620 may be performed by a message receiving component 1130, as described with reference to Fig. 11 described.

[0190] At 1625, the method may include outputting a connection confirmation message to the portable device and via the inductive charging components and the charging-based communication circuitry in response to the connection setup message. The operations of block 1625 may be performed according to the examples disclosed herein. In some examples, aspects of the operations of 1625 may be performed by a message output component 1135, as described with reference to Fig. 11 described.

[0191] It should be noted that the methods described above describe possible implementations, and that the operations and steps may be rearranged or otherwise modified, and other implementations are possible. Furthermore, aspects of two or more of the methods may be combined.

[0192] A method by a portable device is described. The method may include receiving, via inductive charging components, a sequence of gradually decreasing output power levels from a charging device, wherein the output power levels correspond to detected voltage levels at the portable device; activating a charging-based communication circuit within the portable device upon detecting a first output power level of the sequence of gradually decreasing output power levels that falls below an overload protection threshold; outputting, to the charging device and via the inductive charging components and the charging-based communication circuit, a connection establishment message; and receiving, from the charging device and via the inductive charging components and the charging-based communication circuit, a connection confirmation message in response to the connection establishment message.

[0193] A portable device is described. The portable device may include one or more memories storing processor-executable code, and one or more processors coupled to the one or more memories. The one or more processors may be individually or collectively operable to execute the code to cause the portable device to receive, via inductive charging components, a sequence of gradually decreasing output power levels from a charging device, wherein the output power levels correspond to detected voltage levels at the portable device; to activate a charging-based communication circuit within the portable device upon detecting a first output power level of the sequence of gradually decreasing output power levels that falls below an overload protection threshold;to output a connection establishment message to the charging device and via the inductive charging components and the charging-based communication circuit, and to receive a connection confirmation message from the charging device and via the inductive charging components and the charging-based communication circuit in response to the connection establishment message.

[0194] Another portable device is described. The portable device may include means for receiving, via inductive charging components, a sequence of gradually decreasing output power levels from a charging device, the output power levels corresponding to detected voltage levels on the portable device; means for activating a charging-based communication circuit within the portable device upon detecting a first output power level of the sequence of gradually decreasing output power levels that falls below an overload protection threshold; means for outputting, to the charging device and via the inductive charging components and the charging-based communication circuit, a connection establishment message; and means for receiving, from the charging device and via the inductive charging components and the charging-based communication circuit, a connection confirmation message in response to the connection establishment message.

[0195] A non-transitory computer-readable medium that stores code is described.The code may include instructions executable by one or more processors to receive, via inductive charging components, a sequence of gradually decreasing output power levels from a charging device, the output power levels corresponding to detected voltage levels on the portable device, activate a charging-based communication circuit within the portable device upon detecting a first output power level of the sequence of gradually decreasing output power levels that falls below an overload protection threshold, output a connection setup message to the charging device and via the inductive charging components and the charging-based communication circuit, and receive, from the charging device and via the inductive charging components and the charging-based communication circuit, a connection confirmation message in response to the connection setup message.

[0196] In some examples of the method, portable devices, and non-transitory computer-readable medium described herein, issuing the connection setup message may include operations, features, means, or instructions for modulating power consumption with respect to a base charging voltage.

[0197] In some examples of the method, portable devices, and non-transitory computer-readable medium described herein, receiving the connection confirmation message in response to the connection setup message may include operations, features, means, or instructions for detecting a modulation of the output power from the charging device and converting, via the charging-based communication circuitry, the modulation of the output power into a series of bits.

[0198] In some examples of the method, portable devices, and non-transitory computer-readable medium described herein, the overload protection threshold may be based at least in part on a charge level of one of a plurality of charge levels of the portable device.

[0199] Some examples of the method, portable devices, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for activating a receive timer based at least in part on issuing the connection setup message and receiving the connection confirmation message before expiration of the receive timer.

[0200] Some examples of the method, portable devices, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for outputting, after outputting the connection setup message to the charging device and via the inductive charging components and the charging-based communication circuitry, one or more additional messages based at least in part on modulations of power consumption with respect to a base charging voltage.

[0201] Some examples of the method, portable devices, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving, after receiving the connection confirmation message from the charging device and via the inductive charging components and the charging-based communication circuitry, one or more additional messages based at least in part on modulations of the output power with respect to a base charging voltage.

[0202] Some examples of the method described herein, the portable devices of the non-transitory computer-readable medium may further include operations, features, means, or instructions for selecting a maximum voltage load based at least in part on the detected first output power level being greater than the overload protection threshold, and for outputting the connection setup message using the maximum voltage load.

[0203] In some examples of the method, wearable devices, and non-transitory computer-readable medium described herein, the wearable device may be a wearable ring device or a wrist-wearable device.

[0204] A method by a charging device is described. The method may include outputting, via inductive charging components and a charging-based communication circuit, a sequence of gradually decreasing output power levels to a portable device, wherein the output power levels correspond to sensed voltage levels at the portable device; receiving, from the portable device and via the inductive charging components and the charging-based communication circuit, a connection setup message; and outputting, to the portable device and via the inductive charging components and the charging-based communication circuit, a connection confirmation message in response to the connection setup message.

[0205] A loading device is described. The loading device may include one or more memories storing processor-executable code and one or more processors coupled to the one or more memories.The one or more processors may be individually or jointly operable to execute the code to cause the charging device to output a sequence of gradually decreasing output power levels to a portable device via inductive charging components and a charging-based communication circuit, wherein the output power levels correspond to sensed voltage levels at the portable device, to receive a connection setup message from the portable device and via the inductive charging components and the charging-based communication circuit, and to output a connection confirmation message to the portable device and via the inductive charging components and the charging-based communication circuit in response to the connection setup message.

[0206] Another charging device is described. The charging device may include means for outputting, via inductive charging components and a charging-based communication circuit, a sequence of gradually decreasing output power levels to a portable device, wherein the output power levels correspond to sensed voltage levels on the portable device; means for receiving, from the portable device and via the inductive charging components and the charging-based communication circuit, a connection setup message; and means for outputting, to the portable device and via the inductive charging components and the charging-based communication circuit, a connection confirmation message in response to the connection setup message.

[0207] A non-transitory computer-readable medium storing code is described. The code may include instructions executable by one or more processors to output, via inductive charging components and a charging-based communication circuit, a sequence of gradually decreasing output power levels to a portable device, wherein the output power levels correspond to sensed voltage levels at the portable device, receive a connection setup message from the portable device and via the inductive charging components and the charging-based communication circuit, and output, via the inductive charging components and the charging-based communication circuit, a connection confirmation message to the portable device in response to the connection setup message.

[0208] In some examples of the method, charging devices, and non-transitory computer-readable medium described herein, outputting the sequence of gradually decreasing output power levels may include operations, features, means, or instructions for outputting a first power level and for outputting a second power level, which may be lower than the first power level, if the connection setup message is not received before the expiration of a configured timer.

[0209] Some examples of the method, charging devices, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for detecting that the portable device is attached to the charging device based at least in part on a load sensing method, and for outputting a starting power level of the sequence of gradually decreasing output power levels based at least in part on detecting the portable device.

[0210] In some examples of the method, charging devices, and non-transitory computer-readable medium described herein, receiving the connection setup message may include operations, features, means, or instructions for detecting a modulation of power consumption from the portable device with respect to a base charging voltage and converting, via the charging-based communication circuitry, the modulation of power consumption into a series of bits.

[0211] In some examples of the method, charging devices, and non-transitory computer-readable medium described herein, issuing the connection confirmation message in response to the connection setup message may include operations, features, means, or instructions for modulating an output power with respect to a base charging voltage.

[0212] Some examples of the method, charging devices, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving, after receiving the connection setup message from the portable device and via the inductive charging components and the charging-based communication circuitry, one or more additional messages based at least in part on modulations of power consumption with respect to a base charging voltage.

[0213] Some examples of the method, charging devices, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for outputting, after outputting the connection confirmation message to the portable device and via the inductive charging components and the charging-based communication circuitry, one or more additional messages based at least in part on modulations of the output power with respect to a base charging voltage.

[0214] The description presented herein, in conjunction with the accompanying drawings, describes example configurations and does not represent all examples that may be implemented or that fall within the scope of the claims. As used herein, the term "exemplary" means "serving as an example, instance, or illustration" rather than "preferred" or "advantageous over other examples." The detailed description includes specific details for the purpose of understanding the described techniques. However, these techniques may be practiced without these specific details. In some cases, well-known structures and devices are shown in block diagram form so as not to obscure the concepts of the described examples.

[0215] In the accompanying figures, similar components or features may have the same reference numeral. Furthermore, different components of the same type may be distinguished by following the reference numeral with a hyphen and a second character distinguishing between the similar components. Where only the first reference numeral is used in the description, the description applies to each of the similar components having the same first reference numeral, regardless of the second character.

[0216] Information and signals described herein may be represented using a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips referred to in the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0217] The various illustrative blocks and modules described in connection with the description disclosed herein may be implemented or executed using a general-purpose processor, a DSP (Digital Signal Processor), an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof configured to perform the functions described herein. A general-purpose processor may be a microprocessor, but alternatively, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g.,a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration).

[0218] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. When implemented in software executed by a processor, the functions may be stored on or transmitted over a computer-readable medium as one or more instructions or code. Other examples and implementations are within the scope of the disclosure and the appended claims. For example, due to the nature of software, the functions described above may be implemented using software executed by a processor, hardware, firmware, hardwiring, or combinations thereof. Features that implement functions may also be located in various locations, including being distributed such that portions of functions are implemented in various physical locations.Also, as used herein, including in the claims, "or" as used in a list of items (for example, a list of items preceded by a phrase such as "at least one of" or "one or more of") indicates an inclusive list, such as, for example, a list of at least one of A, B, or CA, or B, or C, or AB, or AC, or BC, or ABC (i.e., A, B, and C). Also, as used herein, the phrase "based on" is not intended to be interpreted as indicating a closed set of conditions. For example, an exemplary step described as "based on Condition A" may be based on both Condition A and Condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase "based on" is intended to be interpreted in the same manner as the phrase "based at least in part on."

[0219] Computer-readable media includes both non-volatile computer storage media and communications media, including any medium that facilitates the transfer of a computer program from one location to another. A non-volatile storage medium can be any available medium that can be accessed by a general-purpose or special-purpose computer. By way of example and not limitation, non-volatile computer-readable media can include RAM (random access memory), ROM (read-only memory), electrically erasable programmable ROM (EEPROM), compact disc (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-volatile medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor.Also, any connection is properly referred to as a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source over a coaxial cable, fiber optic cable, twisted-pair cable, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted-pair cable, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. Disk and disc, as used herein, include CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk, and Blu-ray Disc, where disks typically reproduce data magnetically, while discs reproduce data optically using lasers. Combinations of the above are also included within the scope of computer-readable media.

[0220] The description provided herein is intended to enable a person skilled in the art to make or use the disclosure. Various modifications of the disclosure will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not limited to the examples and embodiments described herein, but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein.

Claims

[1] Portable device comprising: one or more memories that store processor-executable code; and one or more processors coupled to the one or more memories and operable individually or jointly to execute the code to cause the portable device to: Receiving, via inductive charging components, a sequence of gradually decreasing output power levels from a charging device, wherein the output power levels correspond to detected voltage levels on the portable device; activating a charging-based communication circuit within the portable device upon detecting a first output power level of the sequence of gradually decreasing output power levels falling below an overload protection threshold; Outputting, to the charging device and via the inductive charging components and the charging-based communication circuit, a first message; and Receiving, from the charging device and via the inductive charging components and the charging-based communication circuitry, a second message in response to the first message. [2] The portable device of claim 1, wherein to output the first message, the one or more processors are individually or collectively further operable to execute the code to cause the portable device to: Modulating a power consumption with respect to a base charging voltage. [3] The portable device of claim 1, wherein to receive the second message in response to the first message, the one or more processors are individually or collectively further operable to execute the code to cause the portable device to: detecting a modulation of the output power from the charging device; and Convert, via the load-based communication circuit, the modulation of the output power into a series of bits. [4] The portable device of claim 1, wherein the overload protection threshold is based at least in part on a charge level of one of a plurality of charge levels of the portable device. [5] The portable device of claim 1, wherein the one or more processors are individually or collectively further operable to execute the code to cause the portable device to: activating a receive timer based at least in part on outputting the first message; and Receive the second message before the receive timer expires. [6] The portable device of claim 1, wherein the one or more processors are individually or collectively further operable to execute the code to cause the portable device to: Outputting, after outputting the first message to the charging device and via the inductive charging components and the charging-based communication circuitry, one or more additional messages based at least in part on modulations of a power consumption with respect to a base charging voltage. [7] The portable device of claim 1, wherein the one or more processors are individually or collectively further operable to execute the code to cause the portable device to: Receiving, after receiving the second message from the charging device and via the inductive charging components and the charging-based communication circuitry, one or more additional messages based at least in part on modulations of the output power with respect to a base charging voltage. [8] The portable device of claim 1, wherein the one or more processors are individually or collectively further operable to execute the code to cause the portable device to: Selecting a maximum voltage load based at least in part on the detected first output power level being greater than the overload protection threshold; and Output the first message using the maximum voltage load. [9] A wearable device according to claim 1, wherein the wearable device is a wearable ring device or a wrist-worn device. [10] The portable device of claim 1, wherein the first message comprises a connection setup message and the second message comprises a connection confirmation message. [11] Charging device comprising: one or more memories that store processor-executable code; and one or more processors coupled to the one or more memories and operable individually or jointly to execute the code to cause the loading device to: Outputting, via inductive charging components and a charging-based communication circuit, a sequence of gradually decreasing output power levels to a portable device, the output power levels corresponding to sensed voltage levels at the portable device; Receiving, from the portable device and via the inductive charging components and the charging-based communication circuitry, a first message; and Outputting, to the portable device and via the inductive charging components and the charging-based communication circuitry, a second message in response to the first message. [12] The charging device of claim 11, wherein to output the sequence of gradually decreasing output power levels, the one or more processors individually or jointly are further operable to execute the code to cause the charging device to: Outputting a first power level; and Output a second power level that is lower than the first power level if the first message is not received before a configured timer expires. [13] The loading device of claim 11, wherein the one or more processors are individually or jointly further operable to execute the code to cause the loading device to: Detecting that the portable device is attached to the charging device based at least in part on a load sensing method; and Outputting a starting power level of the sequence of gradually decreasing output power levels based at least in part on detecting the portable device. [14] The loading device of claim 11, wherein to receive the first message, the one or more processors are individually or jointly further operable to execute the code to cause the loading device to: detecting a modulation of the power consumption of the portable device with respect to a base charging voltage; and Convert, via the load-based communication circuit, the modulation of the power consumption into a series of bits. [15] The loading device of claim 11, wherein to output the second message in response to the first message, the one or more processors are individually or jointly further operable to execute the code to cause the loading device to: Modulating an output power with respect to a base charging voltage. [16] The loading device of claim 11, wherein the one or more processors are individually or jointly further operable to execute the code to cause the loading device to: Receiving, after receiving the first message from the portable device and via the inductive charging components and the charging-based communication circuitry, one or more additional messages based at least in part on modulations of power consumption with respect to a base charging voltage. [17] The loading device of claim 11, wherein the one or more processors are individually or collectively further operable to execute the code to cause the loading device to: Outputting, after outputting the second message to the portable device and via the inductive charging components and the charging-based communication circuitry, one or more additional messages based at least in part on modulations of the output power with respect to a base charging voltage. [18] Charging device comprising: Means for outputting, via inductive charging components and a charging-based communication circuit, a sequence of gradually decreasing output power levels to a portable device, wherein the output power levels correspond to detected voltage levels on the portable device; Means for receiving, from the portable device and via the inductive charging components and the charging-based communication circuit, a connection setup message; and Means for outputting, to the portable device and via the inductive charging components and the charging-based communication circuitry, a connection confirmation message in response to the connection setup message. [19] Non-transitory computer-readable medium that stores code containing instructions executable by one or more processors to: Receiving, via inductive charging components, a sequence of gradually decreasing output power levels from a charging device, the output power levels corresponding to sensed voltage levels on a portable device; activating a charging-based communication circuit within the portable device upon detecting a first output power level of the sequence of gradually decreasing output power levels falling below an overload protection threshold; Outputting, to the charging device and via the inductive charging components and the charging-based communication circuit, a connection setup message; and Receiving, from the charging device and via the inductive charging components and the charging-based communication circuitry, a connection confirmation message in response to the connection establishment message. [20] Non-transitory computer-readable medium that stores code containing instructions executable by one or more processors to: Outputting, via inductive charging components and a charging-based communication circuit, a sequence of gradually decreasing output power levels to a portable device, wherein the output power levels correspond to detected voltage levels on the portable device; Receiving, from the portable device and via the inductive charging components and the charging-based communication circuitry, a connection setup message; and Outputting, to the portable device and via the inductive charging components and the charging-based communication circuitry, a connection confirmation message in response to the connection establishment message.

Images