TECHNIQUES FOR DETERMINING AN OPTIMAL BEDTIME OR WAKEUP TIME

FIELD OF TECHNOLOGY

The following relates to wearable devices and data processing, including techniques for determining an optimal bedtime or wakeup time.

BACKGROUND

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an example of a system that supports techniques for determining an optimal bedtime or wakeup time in accordance with aspects of the present disclosure.

FIG. 2 illustrates an example of a system that supports techniques for determining an optimal bedtime or wakeup time in accordance with aspects of the present disclosure.

FIG. 3 illustrates an example of a system that supports techniques for determining an optimal bedtime or wakeup time in accordance with aspects of the present disclosure.

FIG. 4 shows a block diagram of an apparatus that supports techniques for determining an optimal bedtime or wakeup time in accordance with aspects of the present disclosure.

FIG. 5 shows a block diagram of a wearable application that supports techniques for determining an optimal bedtime or wakeup time in accordance with aspects of the present disclosure.

FIG. 6 shows a diagram of a system including a device that supports techniques for determining an optimal bedtime or wakeup time in accordance with aspects of the present disclosure.

FIGS. 7 through 10 show flowcharts illustrating methods that support techniques for determining an optimal bedtime or wakeup time in accordance with aspects of the present disclosure.

DETAILED DESCRIPTION

Some wearable devices may be configured to recommend bedtimes, wakeup times, or both to a user so as to improve the user's sleep habits. In some cases, wearable devices may recommend bedtimes, wakeup times, or both based on a user's set alarm for the next morning. For example, the wearable device may recommend a bedtime a certain number of hours before the set alarm to assist the user. That is, the recommended bedtime may allow the user to acquire a recommended amount of sleep for the night (e.g., a preconfigured amount of sleep, such as a doctor recommended amount of sleep). In another example, based on when the user fell asleep the night before, the wearable device may recommend a wakeup time so that the user may obtain the recommended amount of sleep for the night (e.g., the recommended wakeup time may be a certain number of hours after the user fell asleep). Conventional methods for recommending a bedtime, wakeup time, or both to a user may fail to take into account physiological conditions of the user and may instead recommend bedtimes and wakeup times based on a standard recommended amount of sleep, such as the doctor recommended eight hours of sleep. However, different users may benefit from different amounts of sleep based on physiological parameters, sleep history, chronotype, etc. In addition, these standardized sleep times may fail to consider cyclical stages of sleep within that time, and therefore fail to optimize recommended wakeup times that coincide with those sleep cycles.

To improve techniques for aiding a user's sleep habits, a wearable device may be configured to recommend bedtimes, wakeup times, or both based on parameters associated with the user in combination with wakeup restrictions associated with the user. For example, a wearable device may be configured to collect data from a user. For example, the wearable device may be configured to periodically or continuously acquire physiological data associated with the user including temperature data, heart rate data, motion data, and the like. In some cases, the wearable device, or a system associated with the wearable device, may utilize the collected physiological data to determine one or more parameters associated with the user. For example, the collected physiological data may be used to determine a readiness level, stress level, activity level, sleep stage, etc. of the user.

Additionally, the wearable device may identify a wakeup time restriction for the user. For example, the wearable device may identify that the user has set an alarm for the next morning, identify a user's work schedule, identify a start time of the user's first meeting of the next day, identify that the user has a flight planned, etc., or some combination thereof. In some cases, the wearable device may be configured to recommend bedtimes and wakeup times based on events associated with the user, such as travel plans, time zone changes, time changes due to daylight savings time, planned events, etc., so as to prepare the user for the events. In some cases, the wearable device may identify the one or more parameters of the user, the wakeup time restrictions, the events based on data stored on the user's mobile device, computer, etc. For example, the wearable device may identify the parameters, restrictions, and events based on the user inputting such information into an application associated with the wearable device, or based on one or more applications downloaded on the user's mobile device (e.g., a calendar application, an airline application, a reminder application, a GPS related application, a weather application, etc.).

In some cases, the wearable device may identify a wakeup time restriction for the user once the user has fallen asleep for the night. In some examples, the user may be asleep and the wearable device may have set the wakeup time for the user based on the identified parameters, restrictions, and events based on the user inputting such information into one or more applications associated with the wearable device, or based on the one or more applications downloaded on the user's mobile device. However, the wearable device may identify that the user has received an alert from one or more applications downloaded on the user's mobile device (e.g., a weather application, a social media application) that may affect the wakeup time set for the user. For example, the wearable device may identify that a weather application has received a storm warning (e.g., a heavy wind warning, a heavy rain warning, a winter storm warning, etc.) that may affect the user's schedule. That is, the user may be required to wake up earlier than the scheduled wakeup time to avoid traffic or to adjust for added commute times on the way to an event. In other examples, the wearable device may identify a morning restriction from a social media application (e.g., a messaging application). For example, the user may be asleep and the wearable device may receive a message about an event via the social media application (e.g., a friend messaging the user to meet for coffee at 7 A.M., a coworker messaging the user to schedule an urgent meeting at 8 A.M., etc.). As such, the wearable device may adjust the scheduled wakeup time based off one or more wakeup restrictions received while the user is asleep.

In some implementations, the wearable device may recommend a bedtime, a wakeup time, or both based on long-term and/or short-term historical data associated with the user. For example, the wearable device may identify that the user routinely goes to sleep at or near a certain time at least most nights, and/or wakes up at or near a certain time at least most mornings (e.g., long-term historical data). Additionally, or alternatively, the wearable device may identify a typical quality and/or amount of sleep the user obtains most nights. Additionally, or alternatively, the wearable device may identify a recommended amount of sleep for the user based on the user's sleep history, physiological parameters associated with the user, etc. For example, the wearable device may identify that the user reaches optimal physiological parameters when the user obtains 7.5 hours of sleep. Additionally, or alternatively, the wearable device may identify that the user has obtained a poor quality of sleep, a low amount of sleep, or a combination thereof last night, for example (e.g., short-term historical data) and recommend sleep times accordingly.

In some implementations, the wearable device may recommend a bedtime, a wakeup time, or both based on inputs from the user. For example, the user may provide an input that the user prefers a certain number of hours for sleep, input a preferred range of number of hours for sleep, input a preferred range of times for sleep (e.g., between 10:00 μm and 7:00 am), input one or more conditions that user felt that day (e.g., the user felt tired, rested, anxious), etc. In some cases, the user may input an expected commute time for the next morning, an expected duration for preparing for the day, an event, a meeting, a flight, etc.

Accordingly, based on the wakeup time restriction, the parameters associated with the user, the events associated with the user, historical data with the user, inputs from the user, or a combination thereof, the wearable device may provide one or more sleep recommendations to the user (e.g., a recommend bedtime, wakeup time, sleep schedule, sleep goal, or a combination thereof) to improve the user's sleep habits and ensure the user has the opportunity to obtain a quality night's sleep within the bounds of the user's schedule.

For example, a wearable device may receive, at a first application associated with a user device, physiological data (e.g., motion data, heart rate data, temperature data) associated with a user that is collected via a set of sensors of a wearable device. In relation to recommending a bedtime, the wearable device may receive, at the first application and from a second application associated with the user device, information indicating a wakeup time restriction for the user, and determine, by the first application, a bedtime for the user based at least in part on the physiological data and the wakeup time restriction for the user from the second application. In some cases, the first application and the second application may be the same or different. The wearable device may cause a graphical user interface (GUI) associated with the first application of the user device to display a message or an alert based at least in part on the bedtime determined by the first application.

In relation to recommending a wakeup time, the wearable device may identify, by the first application, sleep staging information (e.g., the user is in a light sleep, deep sleep, rapid eye movement (REM) sleep stage) for the user while the user is sleeping based on the physiological data, and the wearable device may determine a wakeup time for the user based on the sleep staging information and the wakeup time restriction for the user from the second application. The wearable device may alert the user to wake up in accordance with the wakeup time. The techniques described herein may support improvements in providing sleep guidance to a user by accounting for parameters associated with the user, thereby improving the recommendations.

Aspects of the disclosure are initially described in the context of systems supporting physiological data collection from users via wearable devices. Aspects of the disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flowcharts that relate to techniques for determining an optimal bedtime or wakeup time.

FIG. 1 illustrates an example of a system 100 that supports techniques for determining an optimal bedtime or wakeup time in accordance with aspects of the present disclosure. The system 100 includes a plurality of electronic devices (e.g., wearable devices 104, user devices 106) that may 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.

The electronic devices may include any electronic devices known in the art, including wearable devices 104 (e.g., ring wearable devices, watch wearable 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 GUIs) to a user 102 based on the processed data, and 5) communicating data with one another and/or other computing devices. Different electronic devices may perform one or more of the functionalities.

Example wearable devices 104 may include wearable computing devices, such as a ring computing device (hereinafter “ring”) configured to be worn on a user's 102 finger, a wrist computing device (e.g., a smart watch, fitness band, or bracelet) configured to be worn on a user's 102 wrist, and/or a head mounted computing device (e.g., glasses/goggles). Wearable devices 104 may also include bands, straps (e.g., flexible or inflexible bands or straps), stick-on sensors, and the like, that may be positioned in other locations, such as bands around the head (e.g., a forehead headband), arm (e.g., a forearm band and/or bicep band), and/or 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 included in, articles of clothing. For example, wearable devices 104 may be included in pockets and/or pouches on clothing. As another example, wearable device 104 may be clipped and/or pinned to clothing, or may otherwise be maintained within the vicinity of the user 102. Example articles of clothing may include, but are not limited to, hats, shirts, gloves, pants, socks, outerwear (e.g., jackets), and undergarments. In some implementations, wearable devices 104 may be included with other types of devices such as training/sporting devices that are used during physical activity. For example, wearable devices 104 may be attached to, or included in, a bicycle, skis, a tennis racket, a golf club, and/or training weights.

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

In some aspects, user devices 106 may include handheld 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 examples of user devices 106 may include server computing devices that may communicate with other electronic devices (e.g., via the Internet). In some implementations, computing devices may include medical devices, such as external wearable 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 televisions, smart speakers, smart displays (e.g., video call displays), hubs (e.g., wireless communication hubs), security systems, smart appliances (e.g., thermostats and refrigerators), and fitness equipment.

Some electronic devices (e.g., wearable devices 104, user devices 106) may measure physiological parameters of 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, 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., wearable device 104), mobile device application, or a server computing device may process received physiological data that was measured by other devices.

In some implementations, a user 102 may operate, or may be associated with, multiple electronic devices, that may measure physiological parameters and may 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 associated with, a user device 106 (e.g., mobile device, smartphone), where the wearable device 104 and the user device 106 are communicatively coupled to one another. 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 motion/activity parameters.

For example, as illustrated in FIG. 1, a first user 102-a (User 1) may operate, or may be associated with, a wearable device 104-a (e.g., ring 104-a) and a user device 106-a that may operate as described herein. In this example, the user device 106-a associated with user 102-a may process/store physiological parameters measured by the ring 104-a. Comparatively, a second user 102-b (User 2) may be associated with a ring 104-b, a watch wearable device 104-c (e.g., watch 104-c), and a user device 106-b, where the user device 106-b associated with user 102-b may process/store physiological parameters measured by the ring 104-b and/or the watch 104-c. Moreover, an nth user 102-n (User N) may be associated with an arrangement of electronic devices described herein (e.g., ring 104-n, user device 106-n). In some aspects, wearable devices 104 (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.

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 arterial blood flow within the user's finger. In particular, a ring 104 may utilize one or more LEDs (e.g., red LEDs, green LEDs) that emit light on the palm-side of a user's finger to collect physiological data based on arterial blood flow within the user's finger. In some implementations, the ring 104 may acquire the physiological data using a combination of both 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., movement/motion data), heart rate data, HRV data, blood oxygen level data, or any combination thereof. In general, the terms light-emitting components, light-emitting elements, and like terms, may include, but are not limited to, LEDs, micro LEDs, mini LEDs, laser diodes (LDs), and the like.

In some cases, the system 100 may be configured to collect physiological data from the respective users 102 based on blood flow diffused into a microvascular bed of skin with capillaries and arterioles. For example, the 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, the ring 104 may acquire the physiological data using a combination of both 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., movement/motion data), heart rate data, HRV data, blood oxygen level data, or any combination thereof.

The use of both green and red LEDs may provide several advantages over other solutions, as red and green LEDs have been found to have their own distinct advantages when acquiring physiological data under different conditions (e.g., light/dark, active/inactive) and via different parts of the body, and the like. For example, green LEDs have been found to exhibit better performance during exercise. Moreover, using multiple LEDs (e.g., green and red LEDs) distributed around the ring 104 has been found to exhibit superior performance as compared to wearable devices that utilize LEDs that are positioned close to one another, such as within a watch wearable device. Furthermore, the blood vessels in the finger (e.g., arteries, capillaries) are more accessible via LEDs as compared to blood vessels in the wrist. In particular, arteries in the wrist are positioned on the bottom of the wrist (e.g., palm-side of the wrist), meaning only capillaries are accessible on the top of the wrist (e.g., back of hand side of the wrist), where wearable watch devices and similar devices are typically worn. As such, utilizing LEDs and other sensors within a ring 104 has been found to exhibit superior performance as compared to wearable devices worn on the wrist, as the ring 104 may have greater access to arteries (as compared to capillaries), thereby resulting in stronger signals and more valuable physiological data.

The electronic devices of the system 100 (e.g., user devices 106, wearable 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 transfer control protocol and internet protocol (TCP/IP), such as the Internet, or may implement other network 108 protocols. Network connections between the network 108 and the respective electronic devices may facilitate transport of data via email, web, text messages, mail, or any other appropriate form of interaction within a computer network 108. For example, in some implementations, the ring 104-a associated with the first user 102-a may be communicatively coupled to the user device 106-a, where the user device 106-a is communicatively coupled to the servers 110 via the network 108. In additional or alternative cases, wearable devices 104 (e.g., rings 104, watches 104) may be directly communicatively coupled to the network 108.

The system 100 may offer 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 via the network 108, and may store and analyze the data. Similarly, the servers 110 may provide data to the user devices 106 via the network 108. In some cases, the servers 110 may be located at 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.

In some aspects, the system 100 may detect periods of time that a user 102 is asleep, and classify periods of time during that the user 102 is asleep into one or more sleep stages (e.g., sleep stage classification). For example, as shown in FIG. 1, User 102-a may be associated with a wearable device 104-a (e.g., ring 104-a) and a user device 106-a. In this example, the ring 104-a may collect physiological data associated with the user 102-a, including temperature, heart rate, HRV, respiratory rate, and the like. In some aspects, data collected by the ring 104-a may be input to a machine learning classifier, where the machine learning classifier is configured to determine periods of time that the user 102-a is (or was) asleep. Moreover, the machine learning classifier may be configured to classify periods of time into different sleep stages, including an awake sleep stage, a 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 102-a via a GUI of the user device 106-a. Sleep stage classification may be used to provide feedback to a user 102-a regarding the user's sleeping patterns, such as recommended bedtimes, recommended wake-up times, and the like. Moreover, in some implementations, sleep stage classification techniques described herein may be used to calculate scores for the respective user, such as Sleep Scores, Readiness Scores, and the like.

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

In some aspects, the system 100 may utilize other biological rhythms to further improve physiological data collection, analysis, and processing by phase of these other rhythms. For example, if a weekly rhythm is detected within an individual's baseline data, then the model may be configured to adjust “weights” of data by day of the week. Biological rhythms that may require adjustment to the model by this method include: 1) ultradian (faster than a day rhythms, including sleep cycles in a sleep state, and oscillations from less than an hour to several hours periodicity in the measured physiological variables during wake state; 2) circadian rhythms; 3) non-endogenous daily rhythms shown to be imposed on top of circadian rhythms, as in work schedules; 4) weekly rhythms, or other artificial time periodicities exogenously imposed (e.g., in a hypothetical culture with 12 day “weeks”, 12 day rhythms could be used); 5) multi-day ovarian rhythms in women and spermatogenesis rhythms in men; 6) lunar rhythms (relevant for individuals living with low or no artificial lights); and 7) seasonal rhythms.

The biological rhythms are not always stationary rhythms. 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 periodicity across days even within a user. As such, signal processing techniques sufficient to quantify the frequency composition while preserving temporal resolution of these rhythms in physiological data may be used to improve detection of these rhythms, to assign phase of each rhythm to each moment in time measured, and to thereby modify adjustment models and comparisons of time intervals. The biological rhythm-adjustment models and parameters can be added in linear or non-linear combinations as appropriate to more accurately capture the dynamic physiological baselines of an individual or group of individuals.

In some aspects, the respective devices of the system 100 may support techniques for providing one or more sleep recommendations to a user 102 based on a wakeup time restriction of the user 102, parameters associated with the user 102, events associated with the user 102, historical data associated with the user 102, inputs from the user 102, or a combination thereof. For example, a wearable device 104 may receive, at a first application associated with a user device 106, physiological data (e.g., motion data, heart rate data, temperature data) associated with a user 102 that is collected via a set of sensors of a wearable device 104. In relation to recommending a bedtime, the wearable device may receive, at the first application and from a second application associated with the user device 106, information indicating a wakeup time restriction for the user 102, and determine, by the first application, a bedtime for the user 102 based on the physiological data and the wakeup time restriction for the user 102 from the second application. In some cases, the first application and the second application may be the same or different. In some examples, the wearable device may receive information indicating a wakeup restriction from an application associated with the user device 106 when the user 102 has fallen asleep. That is, the wearable device 104 may adjust a wakeup time for the user 102 that changes (e.g., adjusts, overwrites) the previous wakeup time determined by the wearable device 104. The wearable device 104 may cause a graphical user interface (GUI) associated with the first application of the user device 106 to display a message or an alert based on the bedtime determined by the first application.

In relation to recommending a wakeup time, the wearable device 104 may identify, by the first application, sleep staging information (e.g., the user is in a light sleep, deep sleep, or REM sleep stage) for the user 102 while the user is sleeping based on the physiological data and the wearable device 104 may determine a wakeup time for the user 102 based on the sleep staging information and the wakeup time restriction for the user 102 from the second application. The wearable device 104 may alert the user 102 to wake up in accordance with the wakeup time.

It should be appreciated by a person skilled in the art that one or more aspects of the disclosure may be implemented in a system 100 to additionally or alternatively solve other problems than those described above. Furthermore, aspects of the disclosure may provide technical improvements to “conventional” systems or processes as described herein. However, the description and appended drawings only include example technical improvements resulting from implementing aspects of the disclosure, and accordingly do not represent all of the technical improvements provided within the scope of the claims.

FIG. 2 illustrates an example of a system 200 that supports techniques for determining an optimal bedtime or wakeup time in accordance with aspects of the present disclosure. The system 200 may implement, or be implemented by, system 100. In particular, system 200 illustrates an example of a ring 104 (e.g., wearable device 104), a user device 106, and a server 110, as described with reference to FIG. 1.

In some aspects, the ring 104 may be configured to be worn around a user's finger, and may determine one or more user physiological parameters when worn around the user's finger. Example measurements and determinations may include, but are not limited to, user skin temperature, pulse waveforms, respiratory rate, heart rate, HRV, blood oxygen levels, and the like.

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 ring 104 firmware/configuration updates. 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.

The ring 104 may include a housing 205, that may include an inner housing 205-a and an outer housing 205-b. 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., printable circuit boards) that interconnect the device electronics and/or power source, and the like. The device electronics may include device modules (e.g., hardware/software), such as: a processing module 230-a, a memory 215, a communication module 220-a, 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 assembly (e.g., PPG system 235), and one or more motion sensors 245.

The sensors may include associated modules (not illustrated) 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. Moreover, the ring 104 may include additional and/or alternative sensors or other components that are configured to collect physiological data from the user, including light sensors (e.g., LEDs), oximeters, and the like.

The ring 104 shown and described with reference to FIG. 2 is provided solely for illustrative purposes. As such, the ring 104 may include additional or alternative components as those illustrated in FIG. 2. Other rings 104 that provide functionality described herein may be fabricated. For example, rings 104 with fewer components (e.g., sensors) may be fabricated. In a specific example, a ring 104 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) may be fabricated. In another specific example, a temperature sensor 240 (or other sensor) may be attached to a user's finger (e.g., using clamps, 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 that includes additional sensors and processing functionality may be fabricated.

The housing 205 may include one or more housing 205 components. The housing 205 may include an outer housing 205-b component (e.g., a shell) and an inner housing 205-a component (e.g., a molding). The housing 205 may include additional components (e.g., additional layers) not explicitly illustrated in FIG. 2. For example, in some implementations, the ring 104 may include one or more insulating layers that electrically insulate the device electronics and other conductive materials (e.g., electrical traces) from the outer housing 205-b (e.g., a metal outer housing 205-b). The housing 205 may provide structural support for the device electronics, battery 210, substrate(s), and other components. For example, the housing 205 may protect the device electronics, battery 210, and substrate(s) from mechanical forces, such as pressure and impacts. The housing 205 may also protect the device electronics, battery 210, and substrate(s) from water and/or other chemicals.

The outer housing 205-b may be fabricated from one or more materials. In some implementations, the outer housing 205-b may include a metal, such as titanium, that may provide strength and abrasion resistance at a relatively light weight. The outer housing 205-b may also be fabricated from other materials, such polymers. In some implementations, the outer housing 205-b may be protective as well as decorative.

The inner housing 205-a may be configured to interface with the user's finger. The inner housing 205-a may be formed from a polymer (e.g., a medical grade polymer) or other material. In some implementations, the inner housing 205-a may be transparent. For example, the inner housing 205-a may be transparent to light emitted by the PPG light emitting diodes (LEDs). In some implementations, the inner housing 205-a component may be molded onto the outer housing 205-a. For example, the inner housing 205-a may include a polymer that is molded (e.g., injection molded) to fit into an outer housing 205-b metallic shell.

The ring 104 may include one or more substrates (not illustrated). The device electronics and battery 210 may be included on the one or more substrates. For example, the device electronics and battery 210 may be mounted on one or more substrates. Example substrates may include one or more printed circuit boards (PCBs), such as flexible PCB (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 PCB. In some implementations, the one or more substrates (e.g., one or more flexible PCBs) may include electrical traces that provide electrical communication between device electronics. The electrical traces may also connect the battery 210 to the device electronics.

The device electronics, battery 210, and substrates may be arranged in the ring 104 in a variety of ways. In some implementations, one substrate that includes device electronics may be mounted along the bottom of the ring 104 (e.g., the bottom half), such that the sensors (e.g., PPG system 235, temperature sensors 240, motion sensors 245, and other sensors) interface with the underside of the user's finger. In these implementations, the battery 210 may be included along the top portion of the ring 104 (e.g., on another substrate).

The various components/modules of the ring 104 represent functionality (e.g., circuits and other components) that may be included in the ring 104. Modules may include any discrete and/or integrated electronic circuit components that implement analog and/or digital circuits capable of producing the functions attributed to the modules herein. For example, the modules may include analog circuits (e.g., amplification circuits, filtering circuits, analog/digital conversion circuits, and/or other signal conditioning circuits). The modules may also include digital circuits (e.g., combinational or sequential logic circuits, memory circuits etc.).

The memory 215 (memory module) of the ring 104 may include any volatile, non-volatile, magnetic, or electrical media, such as a random access memory (RAM), read-only memory (ROM), non-volatile RAM (NVRAM), electrically-erasable programmable ROM (EEPROM), flash memory, or any other memory device. The memory 215 may store any of the data described herein. For example, the memory 215 may be configured to store data (e.g., motion data, temperature data, PPG data) collected by the respective sensors and PPG system 235. Furthermore, 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 only example device electronics. As such, the types of electronic components used to implement the device electronics may vary based on design considerations.

The functions attributed to the modules of the ring 104 described herein may be embodied as one or more processors, hardware, firmware, software, or any combination thereof. Depiction of different features as modules is intended to highlight different functional aspects and does not necessarily imply that such modules must be realized by separate hardware/software components. Rather, functionality associated with one or more modules may be performed by separate hardware/software components or integrated within common hardware/software components.

The processing module 230-a 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 230-a communicates with the modules included in the ring 104. For example, the processing module 230-a 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 power circuit).

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

The communication module 220-a may include circuits that provide wireless and/or wired communication with the user device 106 (e.g., communication module 220-b of the user device 106). In some implementations, the communication modules 220-a, 220-b may include wireless communication circuits, such as Bluetooth circuits and/or Wi-Fi circuits. In some implementations, the communication modules 220-a, 220-b can include wired communication circuits, such as Universal Serial Bus (USB) communication circuits. Using the communication module 220-a, the ring 104 and the user device 106 may be configured to communicate with each other. The processing module 230-a of the ring may be configured to transmit/receive data to/from the user device 106 via the communication module 220-a. 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 charge level, and/or ring 104 configuration settings). The processing module 230-a of the ring may also be configured to receive updates (e.g., software/firmware updates) and data from the user device 106.

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 type 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 matches the curve of the ring 104. In some aspects, a charger or other power source may include additional sensors that may be used to collect data in addition to, or that supplements, data collected by the ring 104 itself. Moreover, a charger or other power source for the ring 104 may function as a user device 106, where the charger 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.

In some aspects, the ring 104 includes a power module 225 that may control charging of the battery 210. For example, the power module 225 may interface with an external wireless charger that charges the battery 210 when interfaced with the ring 104. The charger may include a datum structure that mates with a ring 104 datum structure to create a specified orientation with the ring 104 during 104 charging. The power module 225 may also regulate voltage(s) of the device electronics, regulate power output to the device electronics, and monitor the state of charge of the battery 210. In some implementations, the battery 210 may include a protection circuit module (PCM) that protects the battery 210 from high current discharge, over voltage during 104 charging, and under voltage during 104 discharge. The power module 225 may also include electro-static discharge (ESD) protection.

The one or more temperature sensors 240 may be electrically coupled to the processing module 230-a. The temperature sensor 240 may be configured to generate a temperature signal (e.g., temperature data) that indicates a temperature read or sensed by the temperature sensor 240. The processing module 230-a may determine a temperature of the user in 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 205-a) 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 have thermally conductive portions and thermally insulative portions. The thermally conductive portions may conduct heat from the user's finger to the temperature sensors 240. The thermally insulative portions may insulate portions of the ring 104 (e.g., the temperature sensor 240) from ambient temperature.

In some implementations, the temperature sensor 240 may generate a digital signal (e.g., temperature data) that the processing module 230-a may use to determine the temperature. As another example, in cases where the temperature sensor 240 includes a passive sensor, the processing module 230-a (or a temperature sensor 240 module) may measure a current/voltage generated by the 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.

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

The processing module 230-a may store the sampled temperature data in memory 215. In some implementations, the processing module 230-a may process the sampled temperature data. For example, the processing module 230-a may determine average temperature values over a period of time. In one example, the processing module 230-a may determine an average temperature value each 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 in order to conserve memory 215.

The sampling rate, that may be stored in memory 215, may be configurable. In some implementations, the sampling rate may be the same throughout the day and night. In other implementations, the sampling rate may be changed throughout the day/night. In some implementations, the ring 104 may filter/reject temperature readings, such as large spikes in temperature 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 motion during 104 exercise (e.g., as indicated by a motion sensor 245).

The ring 104 (e.g., communication module) may transmit the sampled and/or average temperature data to the user device 106 for storage and/or further processing. The user device 106 may transfer the sampled and/or average temperature data to the server 110 for storage and/or further processing.

Although the ring 104 is illustrated as including a single temperature sensor 240, the ring 104 may include multiple temperature sensors 240 in one or more locations, such as arranged along the inner housing 205-a near the user's finger. In some implementations, the temperature sensors 240 may be stand-alone 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 with the accelerometer and/or processor.

The processing module 230-a may acquire and process data from multiple temperature sensors 240 in a similar manner 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 230-a may sample the sensors at different rates and average/store different values for the different sensors. In some implementations, the processing module 230-a 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 in different locations on the finger.

The temperature sensors 240 on the ring 104 may acquire distal temperatures at the user's finger (e.g., any finger). For example, one or more temperature sensors 240 on the ring 104 may acquire a user's temperature from the underside of a finger or at a different location on the finger. In some implementations, the ring 104 may continuously acquire distal temperature (e.g., at a sampling rate). Although distal temperature measured by a ring 104 at the finger is described herein, other devices may measure temperature at the same/different locations. In some cases, the distal temperature measured at a user's finger may differ from the temperature measured at a user's wrist or other external body location. Additionally, the distal temperature measured at a user's finger (e.g., a “shell” temperature) may differ from the user's core temperature. As such, the ring 104 may provide a useful temperature signal that may not be acquired at other internal/external locations of the body. In some cases, continuous temperature measurement at the finger may capture temperature fluctuations (e.g., small or large fluctuations) that may not be evident in core temperature. For example, continuous temperature measurement at the finger may capture minute-to-minute or hour-to-hour temperature fluctuations that provide additional insight that may not be provided by other temperature measurements elsewhere in the body.

The ring 104 may include a PPG system 235. The PPG system 235 may include one or more optical transmitters that transmit light. The PPG system 235 may also include one or more optical receivers that receive light transmitted by the one or more optical transmitters. An optical receiver may generate a signal (hereinafter “PPG” signal) that indicates an amount of light received by the optical receiver. The optical transmitters may illuminate a region of the user's finger. The PPG signal generated by the PPG system 235 may indicate the perfusion of blood in the illuminated region. For example, the PPG signal may indicate blood volume changes in the illuminated region caused by a user's pulse pressure. The processing module 230-a may sample the PPG signal and determine a user's pulse waveform based on the PPG signal. The processing module 230-a 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.

In some implementations, the PPG system 235 may be configured as a reflective PPG system 235 where the optical receiver(s) receive transmitted light that is reflected through the region 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 arranged opposite to one another, such that light is transmitted directly through a portion of the user's finger to the optical receiver(s).

The number and ratio of transmitters and receivers included in the PPG system 235 may vary. Example optical transmitters may include light-emitting diodes (LEDs). The optical transmitters may transmit light in the infrared spectrum and/or other spectrums. Example optical receivers may include, but are not limited to, photosensors, phototransistors, and photodiodes. The optical receivers may be configured to generate PPG signals in response to the wavelengths received from the optical transmitters. The location of the transmitters and receivers may vary. Additionally, a single device may include reflective and/or transmissive PPG systems 235.

The PPG system 235 illustrated in FIG. 2 may include a reflective PPG system 235 in some implementations. 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 each side of the optical receiver. In this implementation, the PPG system 235 (e.g., 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.

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

Sampling the PPG signal generated by the PPG system 235 may result in a pulse waveform, that may be referred to as a “PPG.” The pulse waveform may indicate blood pressure vs time for multiple cardiac cycles. The pulse waveform may include peaks that indicate cardiac cycles. Additionally, the pulse waveform may include respiratory induced variations that may be used to determine respiration rate. The processing module 230-a may store the pulse waveform in memory 215 in some implementations. The processing module 230-a may process the pulse waveform as it is generated and/or from memory 215 to determine user physiological parameters described herein.

The processing module 230-a may determine the user's heart rate based on the pulse waveform. For example, the processing module 230-a may determine 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 an interbeat interval (IBI). The processing module 230-a may store the determined heart rate values and IBI values in memory 215.

The processing module 230-a may determine HRV over time. For example, the processing module 230-a may determine HRV based on the variation in the IBls. The processing module 230-a may store the HRV values over time in the memory 215. Moreover, the processing module 230-a may determine the user's respiratory rate over time. For example, the processing module 230-a may determine respiratory rate based on frequency modulation, amplitude modulation, or baseline modulation of the user's IBI values over a period of time. Respiratory rate may be calculated in breaths per minute or as another breathing rate (e.g., breaths per 30 seconds). The processing module 230-a may store user respiratory rate values over time in the memory 215.

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 that indicate motion of the sensors. For example, the ring 104 may include one or more accelerometers that generate acceleration signals that indicate acceleration of the accelerometers. As another example, the ring 104 may include one or more gyro sensors that generate gyro signals that indicate 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 example accelerometer/gyro sensor is a Bosch BM1160 inertial micro electro-mechanical system (MEMS) sensor that may measure angular rates and accelerations in three perpendicular axes.

The processing module 230-a 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 230-a may sample acceleration signals to determine acceleration of the ring 104. As another example, the processing module 230-a may sample a gyro signal to determine angular motion. In some implementations, the processing module 230-a may store motion data in memory 215. Motion data may include sampled motion data as well as motion data that is calculated based on the sampled motion signals (e.g., acceleration and angular values).

The ring 104 may store a variety of data described herein. For example, the ring 104 may store temperature data, such as raw sampled temperature data and calculated temperature data (e.g., average temperatures). As another example, the ring 104 may 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). The ring 104 may also store motion data, such as sampled motion data that indicates linear and angular motion.

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 with respect to motion. Example derived values for motion data may include, but are not limited to, motion count values, regularity values, intensity values, metabolic equivalence of task values (METs), and orientation values. Motion counts, regularity values, intensity values, and METs may indicate an amount of user motion (e.g., velocity/acceleration) over time. Orientation values may indicate how the ring 104 is oriented on the user's finger and if the ring 104 is worn on the left hand or right hand.

In some implementations, motion counts and regularity values may be determined by counting a number of acceleration peaks within one or more periods of time (e.g., one or more 30 second to 1 minute periods). Intensity values may indicate a number of movements and the associated intensity (e.g., acceleration values) of the movements. The intensity values may be categorized as low, medium, and high, depending on associated threshold acceleration values. METs may be determined based on the intensity of movements during a period of time (e.g., 30 seconds), the regularity/irregularity of the movements, and the number of movements associated with the different intensities.

In some implementations, the processing module 230-a may compress the data stored in memory 215. For example, the processing module 230-a may delete sampled data after making calculations based on the sampled data. As another example, the processing module 230-a may average data over longer periods of time in order 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, the processing module 230-a may calculate average temperatures over a five minute time period for storage, and then subsequently erase the one minute average temperature data. The processing module 230-a 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.

Although a user's physiological parameters may be measured by sensors included on 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 a 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 user physiological parameters. 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 computing device may be used to implement the techniques described herein.

The physiological measurements may be taken continuously throughout the day and/or night. In some implementations, the physiological measurements may be taken during 104 portions of the day and/or portions of the night. In some implementations, the physiological measurements may be taken in response to determining that the user is in a specific state, such as an active state, resting state, and/or a sleeping state. For example, the ring 104 can make physiological measurements in a resting/sleep state in order to acquire cleaner physiological signals. In one example, the ring 104 or other device/system may detect when a user is resting and/or sleeping and acquire 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 in order to implement the techniques of the present disclosure.

In some implementations, as described previously herein, the ring 104 may be configured to collect, store, and/or process data, and may transfer 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) 285, 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 include 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 acquire data from the ring 104, store the acquired data, and process the acquired data as described herein. For example, the wearable application 250 may include a user interface (UI) module 255, an acquisition module 260, a processing module 230-b, a communication module 220-b, and a storage module (e.g., database 265) configured to store application data.

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

In some aspects, the ring 104, user device 106, and server 110 of the system 200 may be configured to evaluate sleep patterns for a user. In particular, the respective components of the system 200 may 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 noted previously herein, the ring 104 of the system 200 may 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 may be used to determine when the user is asleep in order to evaluate the user's sleep for a given “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 the ring 104 during the respective sleep day. Scores may include, but are not limited to, Sleep Scores, Readiness Scores, and the like.

In some cases, “sleep days” may align with the traditional calendar days, such that a given sleep day runs from midnight to midnight of the respective calendar day. In other cases, sleep days may be offset relative to calendar days. For example, sleep days may run from 6:00 pm (18:00) of a calendar day until 6:00 pm (18:00) of the subsequent calendar day. In this example, 6:00 pm may serve as a “cut-off time,” 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 subsequent sleep day. Due to the fact that most individuals sleep the most at night, offsetting sleep days relative to calendar days may enable the system 200 to evaluate sleep patterns for users in such a manner that is consistent with their sleep schedules. In some cases, users may be able to selectively adjust (e.g., via the GUI) a timing of sleep days relative to calendar days so that the sleep days are aligned with the duration of time that the respective users typically sleep.

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 set of contributors, including: total sleep, efficiency, restfulness, REM sleep, deep sleep, latency, timing, or any combination thereof. The Sleep Score may include any quantity 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 asleep compared to time spent awake while in bed, and may be calculated using the efficiency average of long sleep periods (e.g., primary sleep period) of the sleep day, weighted by a duration of each sleep period. The “restfulness” contributor may indicate how restful the user's sleep is, and may be calculated using the average of all sleep periods of the sleep day, weighted by a duration of each period. The restfulness contributor may be based on a “wake up count” (e.g., sum of all the wake-ups (when user wakes up) detected during different sleep periods), excessive movement, and a “got up count” (e.g., sum of all the got-ups (when user gets out of bed) detected during the different sleep periods).

The “REM sleep” contributor may refer to a sum total of REM sleep durations across all sleep periods of the sleep day including REM sleep. Similarly, the “deep sleep” contributor may refer to a sum total of deep sleep durations across all sleep periods of the sleep day including deep sleep. The “latency” contributor may signify how long (e.g., average, median, longest) the user takes to go to sleep, and may be calculated using the average of long sleep periods throughout the sleep day, weighted by a duration of each period and the number of such periods (e.g., consolidation of a given sleep stage or sleep stages may be its own contributor or weight other contributors). Lastly, the “timing” contributor may refer to a 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 a duration of each period.

By way of another example, a user's overall Readiness Score may be calculated based on a set 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 quantity 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 a cumulative duration of all sleep periods within the sleep day. In particular, sleep balance may indicate to a user whether the sleep that the user has been getting over some duration of time (e.g., the past two weeks) is in balance with the user's needs. Typically, adults need 7-9 hours of sleep a night to stay healthy, alert, and to perform at their best both mentally and physically. However, it is normal to have an occasional night of bad sleep, so the sleep balance contributor takes into account long-term sleep patterns to determine whether each user's sleep needs are being met. The “resting heart rate” contributor may indicate 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 occurring after the primary sleep period.

Continuing with reference to the “contributors” (e.g., factors, contributing factors) of the Readiness Score, the “HRV balance” contributor may indicate a highest HRV average from the primary sleep period and the naps happening after the primary sleep period. The HRV balance contributor may help users keep track of their recovery status by comparing their HRV trend over a first time period (e.g., two weeks) to an average HRV over some second, longer time period (e.g., three months). The “recovery index” contributor may be calculated based on the longest sleep period. Recovery index measures how long it takes for a user's resting heart rate to stabilize during the night. A sign of a 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 wakes up, leaving the body time to recover for the next day. The “body temperature” contributor may be calculated based on the longest sleep period (e.g., primary sleep period) or based on a nap happening 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 may measure a user's body temperature while the user is asleep, and the system 200 may display the user's average temperature relative to the user's baseline temperature. If a user's body temperature is outside of their normal range (e.g., clearly above or below 0.0), the body temperature contributor may be highlighted (e.g., go to a “Pay attention” state) or otherwise generate an alert for the user.

In some aspects, the system 200 may support techniques for providing one or more sleep recommendations to a user based on a wakeup time restriction of the user, parameters associated with the user, events associated with the user, historical data associated with the user, inputs from the user, or a combination thereof. For example, a wearable device 104 may receive, at a first application associated with a user device 106, physiological data (e.g., motion data, heart rate data, temperature data) associated with a user that is collected via a set of sensors of a wearable device 104. In relation to recommending a bedtime, the wearable device may receive, at the first application and from a second application associated with the user device 106, information indicating a wakeup time restriction for the user, and determine, by the first application, a bedtime for the user based on the physiological data and the wakeup time restriction for the user from the second application. In some cases, the first application and the second application may be the same or different. In some examples, the wearable device may receive information indicating a wakeup restriction from an application associated with the user device 106 when the user 102 has fallen asleep. That is, the wearable device 104 may adjust a wakeup time for the user 102 that changes the previous wakeup time determined by the wearable device 104. The wearable device 104 may cause a graphical user interface (GUI) associated with the first application of the user device 106 to display a message or an alert based on the bedtime determined by the first application.

In relation to recommending a wakeup time, the wearable device 104 may identify, by the first application, sleep staging information (e.g., the user is in a light sleep, deep sleep, or REM sleep stage) for the user while the user is sleeping based on the physiological data, and the wearable device 104 may determine a wakeup time for the user based on the sleep staging information and the wakeup time restriction for the user from the second application. The wearable device 104 may alert the user to wake up in accordance with the wakeup time.

FIG. 3 illustrates an example of a system 300 that supports techniques for determining an optimal bedtime or wakeup time in accordance with aspects of the present disclosure. The system 300 may implement, or be implemented by, systems 100 and 200. In particular, system 300 illustrates an example of a ring 104 (e.g., wearable device 104), and a user device 106, as described with reference to FIGS. 1 and 2.

To improve techniques for aiding a user's sleep habits, a wearable device 104 may be configured to recommend bedtimes, wakeup times, a sleep schedule, a sleep goal, or a combination thereof (e.g., optimum bedtimes, optimum wakeup times) based on parameters associated with the user in combination with wakeup restrictions associated with the user. In some cases, a user may not have the option to wake up as late as they would like, as daily life and other obligations may force the user to wake up at specified times (e.g., wakeup restrictions). In such cases, the system 300 may recommend bedtimes based on when the user wants to and/or must wake up. For example, the system may identify a user-set wake-up alarm on the user device associated with the system 300, based on data pulled from an application on the user device, based on inputs from the user, historical data associated with the user, etc. Subsequently, the system 300 may use the identified wake up time and other data (e.g., physiological data, scores) to recommend an optimal bedtime. In other words, in some cases, a user's wake up time may be fixed, and the system may tailor recommended bedtimes based on the fixed wake up times. Additionally, or alternatively, the system 300 may adjust the user's wakeup time in relation to one or more wakeup restrictions. For example, the system 300 may configure the user to wake up before the wake up restriction based on the user being in a light sleep stage. In other examples, the system 300 may adjust the wakeup time for the user based on additional wakeup restrictions received from applications at the user device 106. In such cases, the user may be asleep and unaware that the previous wakeup time has changed due to the additional wakeup restrictions.

A wearable device 104 (e.g., a ring 104) may acquire physiological data associated with a user, including temperature data, HR data, motion data, etc. using one or more sensors 310 of the wearable device 104 (e.g., one or more of sensors 310-a, 310-b, 310-c, 310-d, and 310-e). Subsequently, the wearable device 104 may be configured to identify conditions (e.g., parameters, characteristics) associated with the user based on the acquired physiological data. For example, the wearable device 104 may determine a stress level, an activity level, a drowsiness level, a Sleep Score, Readiness Score, sleep stage (e.g., if the user is currently sleeping), etc. The wearable device 104 may be configured to continuously or periodically acquire physiological data throughout the day, the night, while the user is awake, while the user is sleeping, or a combination thereof.

Additionally, the wearable device 104 may identify a wakeup time restriction for the user. For example, the wearable device 104 may identify that the user has set an alarm for the next morning, identify a user's work schedule, identify a start time of the user's first meeting and/or appointment of the next day, identify that the user has a flight planned, identify a reminder, etc. In some cases, the wearable device 104 may determine the wakeup time restriction based on the user inputting such information into an application associated with the wearable device 104 (e.g., on a user device 106) and/or based on one or more other applications 305 downloaded on a user device 106 connected with the wearable device 104. For example, the wearable device 104 may be configured (e.g., allowed access) to obtain information from the user's calendar application 305-a, a to-do application 305-b (e.g., a reminder application 305), a workout subscription application 305-c, a weather application 305-e, a wallet application 305-g, an airline application 305-h, a social media application 305-i, etc. For example, the wearable device may identify from the workout subscription application 305-c that the user scheduled a workout class at 6:00 am the next morning. The wearable device 104 may schedule the wakeup time accordingly.

Similarly, the wearable device 104 may determine a bedtime restriction for the user. For example, the wearable device 104 may identify a user's work schedule begins or extends into the evening or night, identify a start time and/or end time of the user's last meeting and/or appointment of the day, identify a scheduled evening event, identify that the user has a flight planned, identify a reminder, etc. In some cases, the wearable device 104 may determine the bedtime restriction based on the user inputting such information into an application associated with the wearable device 104 (e.g., on a user device 106) and/or based on one or more other applications 305 downloaded on a user device 106 connected with the wearable device 104. For example, the wearable device 104 may identify that the user's wallet application 305-g includes concert tickets and may identify that the concert begins at 8:00 pm and/or ends at 12:00 am, for example. Therefore, the wearable device 104 may determine that the user is restricted to a bedtime after 12:00 am (e.g., assuming the user does not depart early from the concert). In this way, the wearable device 104 may be configured to adapt recommended or ideal bedtimes to account for the user's schedule, so as to identify a realistic and attainable bedtime.

The wearable device 104 may be configured to recommend bedtimes, wakeup times, a sleep schedule, etc. based on the parameters associated with the user, an identified wakeup time restriction, an identified bedtime restriction, or a combination thereof. The wearable device may recommend bedtimes, wakeup times, a sleep schedule, etc. to allow the user to have the opportunity to obtain a consistent amount of sleep, consistent quality of sleep, consistent bedtimes, consistent wakeup times, etc. For example, the system may suggest an earlier bedtime on days in that the user had a high Activity Score and a low Readiness Score. In another example, the wearable device may identify that the user is restricted to a wakeup time of 8:00 am (e.g., the user must wakeup by 8:00 am) based on a scheduled meeting, a set alarm, etc. and identify that, based on the user's previous night's sleep, physiological parameters, etc., that the user should go to bed by 11:00 μm. In some cases, the wearable device may determine a recommended wakeup time based on whether the user fell asleep by the previous night's recommended bedtime, or vice versa.

In some cases, the wearable device 104 may be configured to determine the wakeup time to be some time before a wakeup restriction (e.g., a range of time before an alarm, for example). In some cases, the wearable device 104 may be configured to monitor the user's sleep stages at least within the range of time before the wakeup restriction and determine a time to wake the user up based on the user's sleep stages. For example, the range may be 15 minutes before the wakeup restriction (e.g., the user's alarm) and the wearable device 104 may identify that within the 15 minutes, the user entered into a light sleep stage and accordingly may determine to wake the user up before the wakeup restriction and while the user is in the light sleep stage. In some cases, the wearable device 104 may determine that in the 15 minutes before the wakeup restriction the user is in a deep sleep, and accordingly, my wait until the wakeup restriction to wake up the user to provide the user with a maximum amount of sleep, despite the sleep stage being less than ideal. In some cases, the user may provide a secondary wakeup time, for example as a secondary option in the event that the primary wakeup time falls within a deep sleep stage. In this case, the range may be extended up to 15 minutes beyond the wakeup restriction, for example, to allow the user to enter a more ideal sleep stage (e.g., REM or light sleep).

In some cases, the wearable device 104 may be configured to recommend bedtimes and wakeup times based on past events, future events (e.g., upcoming events), or current events (e.g., events that are happening today) associated with the user, such as travel plans, time zone changes, time changes due to daylight savings time, planned events (e.g., weddings, concerts, workout events such as a marathon), etc. so as to prepare the user for the event, allow the user to recover from the event, etc. For example, the wearable device 104 may identify that the user is traveling to a different time zone than the current time zone in that the user is located in the coming days or weeks. The wearable device 104 may accordingly shift recommended wakeup times and bedtimes to slowly allow the user to become acclimated to the time zone in that the user is traveling. In these cases, the number of days before the planned travel event that the wearable device 104 starts acclimating the user may be based on how many time zones the user is crossing. The number of days of acclimation may be equal to the number of time zones being crossed. For example, if the user is traveling to a time zone 5 hours ahead, the wearable device 104 may start acclimating the user to the new time zone 5 days before the travel event. In another example, the wearable device may identify that the user is preparing for a big event (e.g., the user's wedding) and may recommend sleep schedules prior to and/or following the big event to allow the user to build up on sleep, catch up on sleep, or both. The wearable device may identify the past events, future events, or current events associated with the user based on inputs from the user into an application 305 associated with the wearable device 104, based on one or more other applications 305 stored on a user device 106 (e.g., a calendar application 305-a, a clock application 305-f, an airline application 305-h, etc.), or a combination thereof.

In some cases, the wearable device 104 may be configured to recommend bedtimes and wakeup times based on the work schedule of the user. For example, the wearable device 104 may identify a typical work schedule of the user (e.g., 9:00 am to 5:00 pm, Monday through Friday), such as a typical working day, typical non-working days, typical hours of work, etc. In some cases, the wearable device 104 may identify if the user's work schedule is changing (e.g., shifting from day shifts to night shifts, or vice versa), or remains constant (e.g., based on an input from the user, based on an application 305). The wearable device 104 may recommend a sleep schedule so as to prepare the user for the identified work schedule.

In some implementations, the wearable device 104 may recommend a bedtime, a wakeup time, or both based on long-term and/or short-term historical data associated with the user. For example, the wearable device 104 may identify that the user routinely goes to sleep at or near a certain time at least most nights, and/or wakes up at or near a certain time at least most mornings (e.g., long-term historical data). In some cases, the wearable device 104 may identify that the user usually adheres to a different sleep schedule during the weekdays versus the weekends and may adjust the recommended wakeup time and bedtime accordingly. In some cases, the wearable device 104 may determine a circadian rhythm of the user (e.g., based on long-term data). Additionally, or alternatively, the wearable device may identify habits of the user such as eating habits, sleeping habits, alcohol habits, etc. that may impact sleep. Additionally, or alternatively, the wearable device may identify a typical quality and/or amount of sleep the user obtains most nights. Additionally, or alternatively, the wearable device may identify a recommended amount of sleep for the user based on the user's sleep history, physiological parameters associated with the user, etc. For example, the wearable device may identify that the user reaches optimal physiological parameters when the user obtains 9 hours of sleep. Additionally, or alternatively, the wearable device may identify that the user has obtained a poor quality of sleep, a low amount of sleep, or a combination thereof last night, for example (e.g., short-term historical data).

In some implementations, the wearable device 104 may recommend a bedtime, a wakeup time, or both based on inputs from the user. For example, the user may provide an input that the user prefers a certain number of hours for sleep, input a preferred range of number of hours for sleep (e.g., 7 to 9 hours), input a preferred range of times for sleep (e.g., between 10:00 μm and 7:00 am), input one or more conditions that user felt that day (e.g., the user felt tired, rested, anxious), etc. In some cases, the user may input an expected commute time for the next morning, an expected duration for preparing for the day, an event, a meeting, a flight, etc. In some cases, the wearable device 104 may determine one or more other parameters of the user such as age and/or gender of the user (e.g., based on inputs from the user), a chronotype of the user (e.g., based on an input from the user and/or physiological data associated with the user), of the like, and may utilize such parameters to recommend a sleep time.

In some implementations, the wearable device 104 may recommend a bedtime, a wakeup time, or both based on improving a user sleep habits. For example, the wearable device 104 may suggest gradual changes in a user's typical bedtime, wake up time, or both to shift the user's sleep schedule. For example, a user may typical fall asleep around 1:00 am and may typically wakeup around 10:00 am. Rather than (unrealistically) recommending that the user start going to be at 9:30 pm and waking up at 6:30 am, the wearable device 104 may gradually build up to the recommended sleep schedule. Accordingly, the wearable device 104 may gradually change sleep suggestions to aid the user in sleeping in accordance with an ideal sleep schedule. The gradual suggestion progression may occur in days, weeks, months, etc. In some cases, the wearable device 104 may perform such a gradual recommendation based on being configured to do so, and/or may determine to perform such a gradual recommendation based on the user requesting that the wearable device 104 does so. For example, the user may input the sleep schedule the user is striving for, and accordingly, the wearable device 104 may develop a plan for reaching the inputted sleep schedule in a set amount of time.

In some implementations, the wearable device 104 may adjust a wakeup time from a previous wakeup time for the user. In some examples, the user may be asleep for the night and the wearable device 104 may have set the wakeup time for the user based on the identified parameters, restrictions, and events based on the user inputting such information into one or more applications 305 associated with the wearable device 104, or based on the one or more applications 305 downloaded on the user device 106. However, the wearable device 104 may identify that the user has received an alert from one or more applications 305 downloaded on the user device 106 (e.g., the weather application 305-e, the social media application 305-i) that may affect the wakeup time set for the user. For example, the wearable device 104 may identify that the weather application 305-e has received a storm warning (e.g., a heavy wind warning, a heavy rain warning, a winter storm warning, etc.) that may affect the user's schedule. That is, the user may be required to wake up earlier than the scheduled wakeup time to avoid traffic or to adjust for added commute times on the way to an event. In other examples, the wearable device 104 may identify a morning restriction from the social media application 305-i (e.g., a messaging application). For example, the user may be asleep and the wearable device 104 may receive a message about an event via the social media application 305-i (e.g., a friend messaging the user to meet for coffee at 7 A.M., a coworker messaging the user to schedule an urgent meeting at 8 A.M., etc.). As such, the wearable device 104 may adjust the scheduled wakeup time based off one or more wakeup restrictions received while the user is asleep.

Accordingly, based on a wakeup restriction, bedtime restriction, parameters associated with the user, events associated with the user, historical data associated with the user, inputs from the user, or a combination thereof, the wearable device may provide one or more sleep recommendations to the user (e.g., a recommend bedtime, wakeup time, sleep schedule, sleep goal, or a combination thereof) to improve the user's sleep habits and ensure the user has the opportunity to attain a quality night's sleep within the bounds of the user's schedule. For example, the wearable device 104 may recommend a wakeup time based on how well the user slept at least the night before compared to the user's baseline quality of sleep. In another example, the wearable device 104 may recommend a wakeup time based on a user's historical sleep pattern, the time the user fell asleep the night before, the quality of sleep the user received throughout the night, etc. to identify a likely wakeup time in that the user will be in a light sleep.

In some cases, the wearable device 104 may determine that the user wakeup restriction will not allow the user to get enough sleep, a quality sleep, and/or a consistent sleep, and may recommend one or more actions to the user to aid in recovery, waking up, etc. For example, the wearable device 104 may determine that the user woke up in a deep sleep, woke up in a way that does not align with the user's circadian rhythm, or chronotype, or a combination thereof and notify the user to “take it easy” today, to drink caffeine, to take a nap, to take deep breaths, to stretch, to mediate, to exercise, etc.

In some cases, the system may be able to leverage devices connected with one or more of the devices of system 300 to nudge a user to wake up or to go to bed, such as via an application on the user device 106 (e.g., home controls 305-d). For example, the system 300 may dim or turn off lights (e.g., of a user's home), turn off televisions and/or speakers (e.g., of a user's home), lower the temperature (e.g., of a user's home), place the user device 106 in a night mode and/or do not disturb mode, etc. when approaching and/or upon reaching a recommended bedtime. In another example, the system 300 may slowly brighten or turn on lights, open window shades, increase the temperature (e.g., of the user's home), place the user device 106 in a daytime mode and/or turn off the do not disturb mode, etc. when approaching and/or upon reaching a recommended wakeup time. Accordingly, the wearable device 104 may alert the user to wake up or go to sleep by gradually increasing an alert over time. Other techniques used to nudge users to go to bed or wake up may include haptics (e.g., a wearable device 104 vibrating, a charger of the wearable device 104 and/or user device 106 vibrating), sound (e.g., sound via the user device 106, charger, connected speakers), light (e.g., light via user device 106, charger, connected lights), guidance on a mobile device, etc. For example, the user device 104 may recommend that the user refrains from device usage leading up to bed, such as by notifying the user to put down the user's mobile device, turn off the television, etc. based on the device inhibiting the user's sleep. In some cases, the system 300 may alert the user to wake up by slowly increasing a volume of an alarm (e.g., gradually wake the user up), where a quiet alarm may start prior to the wakeup restriction and/or recommended wakeup time and may slowly increase to a high volume at the wakeup restriction and/or recommended wakeup time. In some cases, the wakeup strategy used by the device may be set by the user, such that the user indicates to the wearable device 104 how the user wants to be awoken (e.g., by sound, by haptics). In some cases, the wearable device 104 may determine a method for waking the user up based on information associated with the user, such as the user's current sleep stage approaching the wakeup restriction, whether the user shares a room with another person, the quality of sleep the user received, the physiological data of the user, historical data of the user regarding efficient methods of waking the user up, whether the user is deaf, whether the user is blind, etc.

In some implementations, the system 300 may implement a double layered alarm. For example, a user may attempt to snooze a wakeup alarm (e.g., an optimal wakeup alarm, or the alarm based on the wakeup restriction), and instead may turn off the alarm. In such cases, the wearable device 104 may detect whether the user falls back asleep, and in such cases may determine whether to sound the alarm again to ensure that the user wakes up for the wakeup restriction. In some cases, the system 300 may set another alarm for the user at the next closest ideal sleep stage (e.g., light sleep), or within the window of time requested to be awake, or both. For example, if the user falls back asleep, the system 300 may sound a second alarm when the user enters a light sleep stage, and/or within ten minutes of the first alarm, or both, for example. In some cases, there could be a setting that allows or disallows this double layered alarm. For example, if it is the weekend and the user sets an aspirational alarm but instead decides to sleep in, if the double layer alarm setting is turned off, then the system 300 may not sound a second alarm. In another example, if the user need to wake up for work, a flight, a meeting, etc., then the user may allow the double-layered alarm to ensure that the user will be woken up, even if the user turns off a first alarm, thereby providing a double layer of protection to the user.

It should be understood that the examples provided herein are merely examples and do not limit the techniques for recommending bedtimes and/or wakeup times to a user. Any of the techniques described herein may be combined in any way to provide recommended bedtimes and/or wakeup times to a user.

FIG. 4 shows a block diagram 400 of a device 405 that supports techniques for determining an optimal bedtime or wakeup time in accordance with aspects of the present disclosure. The device 405 may include an input module 410, an output module 415, and a wearable application 420. The device 405 may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses).

The input module 410 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 illness detection techniques). Information may be passed on to other components of the device 405. The input module 410 may utilize a single antenna or a set of multiple antennas.

The output module 415 may provide a means for transmitting signals generated by other components of the device 405. For example, the output module 415 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 sleep analysis techniques). In some examples, the output module 415 may be co-located with the input module 410 in a transceiver module. The output module 415 may utilize a single antenna or a set of multiple antennas.

For example, the wearable application 420 may include a physiological data component 425, a sleep stage identification component 430, a wakeup restriction component 435, a wakeup time determination component 440, a wakeup alert component 445, a bedtime determination component 450, a bedtime alert component 455, or any combination thereof. In some examples, the wearable application 420, 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 410, the output module 415, or both. For example, the wearable application 420 may receive information from the input module 410, send information to the output module 415, or be integrated in combination with the input module 410, the output module 415, or both to receive information, transmit information, or perform various other operations as described herein.

The physiological data component 425 may be configured as or otherwise support a means for receiving, at a first application associated with a user device, physiological data associated with a user that is collected via a set of sensors of a wearable device while the user is sleeping. The sleep stage identification component 430 may be configured as or otherwise support a means for identifying, by the first application, sleep staging information for the user while the user is sleeping based at least in part on the physiological data. The wakeup restriction component 435 may be configured as or otherwise support a means for receiving, at the first application and from a second application associated with the user device, information indicating a wakeup time restriction for the user. The wakeup time determination component 440 may be configured as or otherwise support a means for determining, by the first application, a wakeup time for the user based at least in part on the sleep staging information and the wakeup time restriction for the user from the second application. The wakeup alert component 445 may be configured as or otherwise support a means for alerting the user to wake up in accordance with the wakeup time.

The physiological data component 425 may be configured as or otherwise support a means for receiving, at a first application associated with a user device, physiological data associated with a user that is collected via a set of sensors of a wearable device. The wakeup restriction component 435 may be configured as or otherwise support a means for receiving, at the first application and from a second application associated with the user device, information indicating a wakeup time restriction for the user. The bedtime determination component 450 may be configured as or otherwise support a means for determining, by the first application, a bedtime for the user based at least in part on the physiological data and the wakeup time restriction for the user from the second application. The bedtime alert component 455 may be configured as or otherwise support a means for causing a graphical user interface associated with the first application of the user device to display a message or an alert based at least in part on the bedtime determined by the first application.

FIG. 5 shows a block diagram 500 of a wearable application 520 that supports techniques for determining an optimal bedtime or wakeup time in accordance with aspects of the present disclosure. The wearable application 520 may be an example of aspects of a wearable application or a wearable application 420, or both, as described herein. The wearable application 520, or various components thereof, may be an example of means for performing various aspects of techniques for determining an optimal bedtime or wakeup time as described herein. For example, the wearable application 520 may include a physiological data component 525, a sleep stage identification component 530, a wakeup restriction component 535, a wakeup time determination component 540, a wakeup alert component 545, a bedtime determination component 550, a bedtime alert component 555, an alarm identification component 560, a device manager 565, or any combination thereof. Each of these components may communicate, directly or indirectly, with one another (e.g., via one or more buses).

The physiological data component 525 may be configured as or otherwise support a means for receiving, at a first application associated with a user device, physiological data associated with a user that is collected via a set of sensors of a wearable device while the user is sleeping. The sleep stage identification component 530 may be configured as or otherwise support a means for identifying, by the first application, sleep staging information for the user while the user is sleeping based at least in part on the physiological data. The wakeup restriction component 535 may be configured as or otherwise support a means for receiving, at the first application and from a second application associated with the user device, information indicating a wakeup time restriction for the user. The wakeup time determination component 540 may be configured as or otherwise support a means for determining, by the first application, a wakeup time for the user based at least in part on the sleep staging information and the wakeup time restriction for the user from the second application. The wakeup alert component 545 may be configured as or otherwise support a means for alerting the user to wake up in accordance with the wakeup time.

In some examples, the alarm identification component 560 may be configured as or otherwise support a means for identifying an alarm set by the user via the user device, wherein the information indicating the wakeup time restriction comprises a time associated with the alarm.

In some examples, the second application comprises a calendar application, and the information indicating the wakeup time restriction for the user comprises a start time associated with one or more meetings, one or more appointments, one or more to-do items, or a combination thereof stored in the calendar application.

In some examples, to support determining the wakeup time for the user, the wakeup time determination component 540 may be configured as or otherwise support a means for determining an optimum time for the user to wake up based at least in part on historical sleep data collected by the first application, wherein the historical sleep data comprises historical wakeup times from one or more previous days, an amount of sleep from one or more previous days, a quality of sleep from one or more previous days, or a combination thereof.

In some examples, the information indicating the wakeup time restriction for the user comprises future travel plans, past travel, current travel, changes to time due to daylight savings, upcoming events, an age of the user, a gender of the user, a chronotype of the user, a circadian rhythm of the user, or a combination thereof.

In some examples, the information indicating the wakeup time restriction for the user comprises habits of the user collected by the second application.

In some examples, the habits of the user comprise a work schedule, eating habits, exercise habits, sleep habits on work nights, sleep habits on non-work nights, or a combination thereof.

In some examples, to support alerting the user to wake up, the wakeup alert component 545 may be configured as or otherwise support a means for alerting the user to gradually wake up based at least in part on the wakeup time by gradually increasing the alerting over time.

In some examples, to support alerting the user to wake up, the wakeup alert component 545 may be configured as or otherwise support a means for sounding an alarm prior to the wakeup time, or at the wakeup time, or both.

In some examples, to support alerting the user to wake up, the wakeup alert component 545 may be configured as or otherwise support a means for turning on a light prior to the wakeup time, or at the wakeup time, or both.

In some examples, to support receiving physiological data, the physiological data component 525 may be configured as or otherwise support a means for receiving temperature data, motion data, heart rate data, or a combination thereof via the set of sensors of the wearable device, wherein the sleep staging information is identified based at least in part on the temperature data, the motion data, the heart rate data, or a combination thereof.

In some examples, the physiological data component 525 may be configured as or otherwise support a means for receiving, at a first application associated with a user device, physiological data associated with a user that is collected via a set of sensors of a wearable device. In some examples, the wakeup restriction component 535 may be configured as or otherwise support a means for receiving, at the first application and from a second application associated with the user device, information indicating a wakeup time restriction for the user. The bedtime determination component 550 may be configured as or otherwise support a means for determining, by the first application, a bedtime for the user based at least in part on the physiological data and the wakeup time restriction for the user from the second application. The bedtime alert component 555 may be configured as or otherwise support a means for causing a graphical user interface associated with the first application of the user device to display a message or an alert based at least in part on the bedtime determined by the first application.

In some examples, the second application comprises a calendar application and the information indicating the wakeup time restriction for the user comprises a start time associated with one or more meetings, one or more appointments, one or more to-do items, or a combination thereof stored in the calendar application.

In some examples, to support determining the bedtime for the user, the bedtime determination component 550 may be configured as or otherwise support a means for determining an optimal time for the user to go to bed based at least in part on historical sleep data collected by the first application, wherein the historical sleep data comprises historical bedtimes from one or more previous days, an amount of sleep from one or more previous days, a quality of sleep from one or more previous days, or a combination thereof.

In some examples, the bedtime alert component 555 may be configured as or otherwise support a means for alerting the user to get ready for bed based at least in part on the bedtime by gradually dimming one or more lights over time, where the one or more lights are associated with a user's home, a user's mobile device, or a combination thereof.

In some examples, to support alerting the user to get ready for bed, the device manager 565 may be configured as or otherwise support a means for turning off one or more devices in use by the user that inhibit sleep, the one or more devices comprising a user's mobile device, a user's television, a user's computer, or a combination thereof.

In some examples, the information associated with the user comprises future travel plans, past travel, current travel, changes to time due to daylight savings, upcoming events, an age of the user, a gender of the user, a chronotype of the user, a circadian rhythm of the user, or a combination thereof.

In some examples, the information indicating the wakeup time restriction for the user comprises habits of the user, stored data associated with the user, or a combination thereof.

In some examples, the habits of the user comprise a work schedule, eating habits, exercise habits, sleep habits on work nights, sleep habits on non-work nights, or a combination thereof.

FIG. 6 shows a diagram of a system 600 including a device 605 that supports techniques for determining an optimal bedtime or wakeup time in accordance with aspects of the present disclosure. The device 605 may be an example of or include the components of a device 405 as described herein. The device 605 may include an example of a user device 106, as described previously herein. The device 605 may include components for bi-directional communications including components for transmitting and receiving communications with a wearable device 104 and a server 110, such as a wearable application 620, a communication module 610, an antenna 615, a user interface component 625, a database (application data) 630, a memory 635, and a processor 640. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 645).

The communication module 610 may manage input and output signals for the device 605 via the antenna 615. The communication module 610 may include an example of the communication module 220-b of the user device 106 shown and described in FIG. 2. In this regard, the communication module 610 may manage communications with the ring 104 and the server 110, as illustrated in FIG. 2. The communication module 610 may also manage peripherals not integrated into the device 605. In some cases, the communication module 610 may represent a physical connection or port to an external peripheral. In some cases, the communication module 610 may utilize an operating system such as iOS®, ANDROID®, MS-DOS®, MS-WINDOWS®, OS/2®, UNIX®, LINUX®, or another known operating system. In other cases, the communication module 610 may represent or interact with a wearable device (e.g., ring 104), modem, a keyboard, a mouse, a touchscreen, or a similar device. In some cases, the communication module 610 may be implemented as part of the processor 640. In some examples, a user may interact with the device 605 via the communication module 610, user interface component 625, or via hardware components controlled by the communication module 610.

In some cases, the device 605 may include a single antenna 615. However, in some other cases, the device 605 may have more than one antenna 615, that may be capable of concurrently transmitting or receiving multiple wireless transmissions. The communication module 610 may communicate bi-directionally, via the one or more antennas 615, wired, or wireless links as described herein. For example, the communication module 610 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver. The communication module 610 may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas 615 for transmission, and to demodulate packets received from the one or more antennas 615.

The user interface component 625 may manage data storage and processing in a database 630. In some cases, a user may interact with the user interface component 625. In other cases, the user interface component 625 may operate automatically without user interaction. The database 630 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.

The memory 635 may include RAM and ROM. The memory 635 may store computer-readable, computer-executable software including instructions that, when executed, cause the processor 640 to perform various functions described herein. In some cases, the memory 635 may contain, among other things, a BIOS that may control basic hardware or software operation such as the interaction with peripheral components or devices.

The processor 640 may include 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, the processor 640 may be configured to operate a memory array using a memory controller. In other cases, a memory controller may be integrated into the processor 640. The processor 640 may be configured to execute computer-readable instructions stored in a memory 635 to perform various functions (e.g., functions or tasks supporting a method and system for sleep staging algorithms).

For example, the wearable application 620 may be configured as or otherwise support a means for receiving, at a first application associated with a user device, physiological data associated with a user that is collected via a set of sensors of a wearable device while the user is sleeping. The wearable application 620 may be configured as or otherwise support a means for identifying, by the first application, sleep staging information for the user while the user is sleeping based at least in part on the physiological data. The wearable application 620 may be configured as or otherwise support a means for receiving, at the first application and from a second application associated with the user device, information indicating a wakeup time restriction for the user. The wearable application 620 may be configured as or otherwise support a means for determining, by the first application, a wakeup time for the user based at least in part on the sleep staging information and the wakeup time restriction for the user from the second application. The wearable application 620 may be configured as or otherwise support a means for alerting the user to wake up in accordance with the wakeup time.

For example, the wearable application 620 may be configured as or otherwise support a means for receiving, at a first application associated with a user device, physiological data associated with a user that is collected via a set of sensors of a wearable device. The wearable application 620 may be configured as or otherwise support a means for receiving, at the first application and from a second application associated with the user device, information indicating a wakeup time restriction for the user. The wearable application 620 may be configured as or otherwise support a means for determining, by the first application, a bedtime for the user based at least in part on the physiological data and the wakeup time restriction for the user from the second application. The wearable application 620 may be configured as or otherwise support a means for causing a graphical user interface associated with the first application of the user device to display a message or an alert based at least in part on the bedtime determined by the first application.

By including or configuring the wearable application 620 in accordance with examples as described herein, the device 605 may support techniques for improved techniques for determining recommended wakeup times, recommended sleep times, etc. to a user.

The wearable application 620 may include an application (e.g., “app”), program, software, or other component that is configured to facilitate communications with a ring 104, server 110, other user devices 106, and the like. For example, the wearable application 620 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, transmit and receive data with the servers 110, and cause presentation of data to a user 102.

FIG. 7 shows a flowchart illustrating a method 700 that supports techniques for determining an optimal bedtime or wakeup time in accordance with aspects of the present disclosure. The operations of the method 700 may be implemented by a user device or its components as described herein. For example, the operations of the method 700 may be performed by a user device as described with reference to FIGS. 1 through 6. In some examples, a user 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 user device may perform aspects of the described functions using special-purpose hardware.

At 705, the method may include receiving, at a first application associated with a user device, physiological data associated with a user that is collected via a set of sensors of a wearable device while the user is sleeping. The operations of 705 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 705 may be performed by a physiological data component 525 as described with reference to FIG. 5.

At 710, the method may include identifying, by the first application, sleep staging information for the user while the user is sleeping based at least in part on the physiological data. The operations of 710 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 710 may be performed by a sleep stage identification component 530 as described with reference to FIG. 5.

At 715, the method may include receiving, at the first application and from a second application associated with the user device, information indicating a wakeup time restriction for the user. The operations of 715 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 715 may be performed by a wakeup restriction component 535 as described with reference to FIG. 5.

At 720, the method may include determining, by the first application, a wakeup time for the user based at least in part on the sleep staging information and the wakeup time restriction for the user from the second application. The operations of 720 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 720 may be performed by a wakeup time determination component 540 as described with reference to FIG. 5.

At 725, the method may include alerting the user to wake up in accordance with the wakeup time. The operations of 725 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 725 may be performed by a wakeup alert component 545 as described with reference to FIG. 5.

FIG. 8 shows a flowchart illustrating a method 800 that supports techniques for determining an optimal bedtime or wakeup time in accordance with aspects of the present disclosure. The operations of the method 800 may be implemented by a user device or its components as described herein. For example, the operations of the method 800 may be performed by a user device as described with reference to FIGS. 1 through 6. In some examples, a user 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 user device may perform aspects of the described functions using special-purpose hardware.

At 805, the method may include receiving, at a first application associated with a user device, physiological data associated with a user that is collected via a set of sensors of a wearable device while the user is sleeping. The operations of 805 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 805 may be performed by a physiological data component 525 as described with reference to FIG. 5.

At 810, the method may include identifying, by the first application, sleep staging information for the user while the user is sleeping based at least in part on the physiological data. The operations of 810 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 810 may be performed by a sleep stage identification component 530 as described with reference to FIG. 5.

At 815, the method may include receiving, at the first application and from a second application associated with the user device, information indicating a wakeup time restriction for the user. The operations of 815 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 815 may be performed by a wakeup restriction component 535 as described with reference to FIG. 5.

At 820, the method may include identifying an alarm set by the user via the user device, wherein the information indicating the wakeup time restriction comprises a time associated with the alarm. The operations of 820 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 820 may be performed by an alarm identification component 560 as described with reference to FIG. 5.

At 825, the method may include determining, by the first application, a wakeup time for the user based at least in part on the sleep staging information and the wakeup time restriction for the user from the second application. The operations of 825 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 825 may be performed by a wakeup time determination component 540 as described with reference to FIG. 5.

At 830, the method may include alerting the user to wake up in accordance with the wakeup time. The operations of 830 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 830 may be performed by a wakeup alert component 545 as described with reference to FIG. 5.

FIG. 9 shows a flowchart illustrating a method 900 that supports techniques for determining an optimal bedtime or wakeup time in accordance with aspects of the present disclosure. The operations of the method 900 may be implemented by a user device or its components as described herein. For example, the operations of the method 900 may be performed by a user device as described with reference to FIGS. 1 through 6. In some examples, a user 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 user device may perform aspects of the described functions using special-purpose hardware.

At 905, the method may include receiving, at a first application associated with a user device, physiological data associated with a user that is collected via a set of sensors of a wearable device. The operations of 905 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 905 may be performed by a physiological data component 525 as described with reference to FIG. 5.

At 910, the method may include receiving, at the first application and from a second application associated with the user device, information indicating a wakeup time restriction for the user. The operations of 910 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 910 may be performed by a wakeup restriction component 535 as described with reference to FIG. 5.

At 915, the method may include determining, by the first application, a bedtime for the user based at least in part on the physiological data and the wakeup time restriction for the user from the second application. The operations of 915 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 915 may be performed by a bedtime determination component 550 as described with reference to FIG. 5.

At 920, the method may include causing a graphical user interface associated with the first application of the user device to display a message or an alert based at least in part on the bedtime determined by the first application. The operations of 920 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 920 may be performed by a bedtime alert component 555 as described with reference to FIG. 5.

FIG. 10 shows a flowchart illustrating a method 1000 that supports techniques for determining an optimal bedtime or wakeup time in accordance with aspects of the present disclosure. The operations of the method 1000 may be implemented by a user device or its components as described herein. For example, the operations of the method 1000 may be performed by a user device as described with reference to FIGS. 1 through 6. In some examples, a user 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 user device may perform aspects of the described functions using special-purpose hardware.

At 1005, the method may include receiving, at a first application associated with a user device, physiological data associated with a user that is collected via a set of sensors of a wearable device. The operations of 1005 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1005 may be performed by a physiological data component 525 as described with reference to FIG. 5.

At 1010, the method may include receiving, at the first application and from a second application associated with the user device, information indicating a wakeup time restriction for the user. The operations of 1010 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1010 may be performed by a wakeup restriction component 535 as described with reference to FIG. 5.

At 1015, the method may include determining, by the first application, a bedtime for the user based at least in part on the physiological data and the wakeup time restriction for the user from the second application. The operations of 1015 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1015 may be performed by a bedtime determination component 550 as described with reference to FIG. 5.

At 1020, the method may include causing a graphical user interface associated with the first application of the user device to display a message or an alert based at least in part on the bedtime determined by the first application. The operations of 1020 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1020 may be performed by a bedtime alert component 555 as described with reference to FIG. 5.

At 1025, the method may include turning off one or more devices in use by the user that inhibit sleep, the one or more devices comprising a user's mobile device, a user's television, a user's computer, or a combination thereof. The operations of 1025 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1025 may be performed by a device manager 565 as described with reference to FIG. 5.

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

A method is described. The method may include receiving, at a first application associated with a user device, physiological data associated with a user that is collected via a set of sensors of a wearable device while the user is sleeping, identifying, by the first application, sleep staging information for the user while the user is sleeping based at least in part on the physiological data, receiving, at the first application and from a second application associated with the user device, information indicating a wakeup time restriction for the user, determining, by the first application, a wakeup time for the user based at least in part on the sleep staging information and the wakeup time restriction for the user from the second application, and alerting the user to wake up in accordance with the wakeup time.

An apparatus is described. The apparatus may include a processor, memory coupled with the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to receive, at a first application associated with a user device, physiological data associated with a user that is collected via a set of sensors of a wearable device while the user is sleeping, identify, by the first application, sleep staging information for the user while the user is sleeping based at least in part on the physiological data, receive, at the first application and from a second application associated with the user device, information indicating a wakeup time restriction for the user, determine, by the first application, a wakeup time for the user based at least in part on the sleep staging information and the wakeup time restriction for the user from the second application, and alert the user to wake up in accordance with the wakeup time.

Another apparatus is described. The apparatus may include means for receiving, at a first application associated with a user device, physiological data associated with a user that is collected via a set of sensors of a wearable device while the user is sleeping, means for identifying, by the first application, sleep staging information for the user while the user is sleeping based at least in part on the physiological data, means for receiving, at the first application and from a second application associated with the user device, information indicating a wakeup time restriction for the user, means for determining, by the first application, a wakeup time for the user based at least in part on the sleep staging information and the wakeup time restriction for the user from the second application, and means for alerting the user to wake up in accordance with the wakeup time.

A non-transitory computer-readable medium storing code is described. The code may include instructions executable by a processor to receive, at a first application associated with a user device, physiological data associated with a user that is collected via a set of sensors of a wearable device while the user is sleeping, identify, by the first application, sleep staging information for the user while the user is sleeping based at least in part on the physiological data, receive, at the first application and from a second application associated with the user device, information indicating a wakeup time restriction for the user, determine, by the first application, a wakeup time for the user based at least in part on the sleep staging information and the wakeup time restriction for the user from the second application, and alert the user to wake up in accordance with the wakeup time.

Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for identifying an alarm set by the user via the user device, wherein the information indicating the wakeup time restriction comprises a time associated with the alarm.

In some examples of the method, apparatuses, and non-transitory computer-readable medium described herein, the second application comprises a calendar application, and the information indicating the wakeup time restriction for the user comprises a start time associated with one or more meetings, one or more appointments, one or more to-do items, or a combination thereof stored in the calendar application.

In some examples of the method, apparatuses, and non-transitory computer-readable medium described herein, determining the wakeup time for the user may include operations, features, means, or instructions for determining an optimum time for the user to wake up based at least in part on historical sleep data collected by the first application, wherein the historical sleep data comprises historical wakeup times from one or more previous days, an amount of sleep from one or more previous days, a quality of sleep from one or more previous days, or a combination thereof.

In some examples of the method, apparatuses, and non-transitory computer-readable medium described herein, the information indicating the wakeup time restriction for the user comprises future travel plans, past travel, current travel, changes to time due to daylight savings, upcoming events, an age of the user, a gender of the user, a chronotype of the user, a circadian rhythm of the user, or a combination thereof.

In some examples of the method, apparatuses, and non-transitory computer-readable medium described herein, the habits of the user comprise a work schedule, eating habits, exercise habits, sleep habits on work nights, sleep habits on non-work nights, or a combination thereof.

In some examples of the method, apparatuses, and non-transitory computer-readable medium described herein, alerting the user to wake up may include operations, features, means, or instructions for alerting the user to gradually wakeup based at least in part on the wakeup time by gradually increasing the alerting over time.

In some examples of the method, apparatuses, and non-transitory computer-readable medium described herein, alerting the user to wake up may include operations, features, means, or instructions for sounding an alarm prior to the wakeup time, or at the wakeup time, or both.

In some examples of the method, apparatuses, and non-transitory computer-readable medium described herein, alerting the user to wake up may include operations, features, means, or instructions for turning on a light prior to the wakeup time, or at the wakeup time, or both.

In some examples of the method, apparatuses, and non-transitory computer-readable medium described herein, receiving physiological data may include operations, features, means, or instructions for receiving temperature data, motion data, heart rate data, or a combination thereof via the set of sensors of the wearable device, wherein the sleep staging information may be identified based at least in part on the temperature data, the motion data, the heart rate data, or a combination thereof.

A method is described. The method may include receiving, at a first application associated with a user device, physiological data associated with a user that is collected via a set of sensors of a wearable device, receiving, at the first application and from a second application associated with the user device, information indicating a wakeup time restriction for the user, determining, by the first application, a bedtime for the user based at least in part on the physiological data and the wakeup time restriction for the user from the second application, and causing a graphical user interface associated with the first application of the user device to display a message or an alert based at least in part on the bedtime determined by the first application.

An apparatus is described. The apparatus may include a processor, memory coupled with the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to receive, at a first application associated with a user device, physiological data associated with a user that is collected via a set of sensors of a wearable device, receive, at the first application and from a second application associated with the user device, information indicating a wakeup time restriction for the user, determine, by the first application, a bedtime for the user based at least in part on the physiological data and the wakeup time restriction for the user from the second application, and cause a graphical user interface associated with the first application of the user device to display a message or an alert based at least in part on the bedtime determined by the first application.

Another apparatus is described. The apparatus may include means for receiving, at a first application associated with a user device, physiological data associated with a user that is collected via a set of sensors of a wearable device, means for receiving, at the first application and from a second application associated with the user device, information indicating a wakeup time restriction for the user, means for determining, by the first application, a bedtime for the user based at least in part on the physiological data and the wakeup time restriction for the user from the second application, and means for causing a graphical user interface associated with the first application of the user device to display a message or an alert based at least in part on the bedtime determined by the first application.

A non-transitory computer-readable medium storing code is described. The code may include instructions executable by a processor to receive, at a first application associated with a user device, physiological data associated with a user that is collected via a set of sensors of a wearable device, receive, at the first application and from a second application associated with the user device, information indicating a wakeup time restriction for the user, determine, by the first application, a bedtime for the user based at least in part on the physiological data and the wakeup time restriction for the user from the second application, and cause a graphical user interface associated with the first application of the user device to display a message or an alert based at least in part on the bedtime determined by the first application.

In some examples of the method, apparatuses, and non-transitory computer-readable medium described herein, the second application comprises a calendar application and the information indicating the wakeup time restriction for the user comprises a start time associated with one or more meetings, one or more appointments, one or more to-do items, or a combination thereof stored in the calendar application.

In some examples of the method, apparatuses, and non-transitory computer-readable medium described herein, determining the bedtime for the user may include operations, features, means, or instructions for determining an optimum time for the user to go to bed based at least in part on historical sleep data collected by the first application, wherein the historical sleep data comprises historical bedtimes from one or more previous days, an amount of sleep from one or more previous days, a quality of sleep from one or more previous days, or a combination thereof.

Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for alerting the user to get ready for bed based at least in part on the bedtime by gradually dimming one or more lights over time, where the one or more lights may be associated with a user's home, a user's mobile device, or a combination thereof.

In some examples of the method, apparatuses, and non-transitory computer-readable medium described herein, alerting the user to get ready for bed may include operations, features, means, or instructions for turning off one or more devices in use by the user that inhibit sleep, the one or more devices comprising a user's mobile device, a user's television, a user's computer, or a combination thereof.

In some examples of the method, apparatuses, and non-transitory computer-readable medium described herein, the information associated with the user comprises future travel plans, past travel, current travel, changes to time due to daylight savings, upcoming events, an age of the user, a gender of the user, a chronotype of the user, a circadian rhythm of the user, or a combination thereof.

The description set forth herein, in connection with the appended drawings, describes example configurations and does not represent all the examples that may be implemented or that are within the scope of the claims. The term “exemplary” used herein means “serving as an example, instance, or illustration,” and not “preferred” or “advantageous over other examples.” The detailed description includes specific details for the purpose of providing an understanding of the described techniques. These techniques, however, may be practiced without these specific details. In some instances, well-known structures and devices are shown in block diagram form in order to avoid obscuring the concepts of the described examples.

In the appended figures, similar components or features may have the same reference label. Further, various components of the same type may be distinguished by following the reference label by a dash and a second label that distinguishes among the similar components. If just the first reference label is used in the specification, the description is applicable to any one of the similar components having the same first reference label irrespective of the second reference label.

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

The various illustrative blocks and modules described in connection with the disclosure herein may be implemented or performed with a general-purpose processor, a DSP, an ASIC, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in the alternative, 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).

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

Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A non-transitory storage medium may be any available medium that can be accessed by a general purpose or special purpose computer. By way of example, and not limitation, non-transitory computer-readable media can comprise RAM, ROM, electrically erasable programmable ROM (EEPROM), compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code means 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 termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, 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 usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media.

The description herein is provided to enable a person skilled in the art to make or use the disclosure. Various modifications to 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 designs described herein, but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein.

TECHNIQUES FOR DETERMINING AN OPTIMAL BEDTIME OR WAKEUP TIME

Information

Publication Number

Date Filed

Date Published

Inventors

Original Assignees

CPC

International Classifications

Abstract

Description

Claims

CROSS REFERENCE

Provisional Applications (1)