Ovulation date estimation system and ovulation date estimation method
The system addresses the lack of versatility and ease of use in existing ovulation prediction systems by employing a wearable device and machine learning models to accurately estimate ovulation day using biometric data.
Patent Information
- Application Number
- PCT/JP2026/017060
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2025-05-14
- Filing Date
- 2026-04-30
- Publication Date
- 2026-11-19
AI Technical Summary
Existing ovulation prediction systems require bulky temperature sensor arrays, which lack versatility and ease of use.
A system comprising a wearable device, user terminal, and management server that uses a ring-shaped wearable device to acquire biometric information, including temperature and activity levels, and employs a menstrual cycle state estimation model to estimate ovulation day based on representative temperature information.
Provides a versatile and user-friendly method for predicting ovulation day by integrating wearable technology with machine learning models to accurately estimate ovulation using biometric data.
Smart Images

Figure JPOXMLDOC01-APPB-M000001 
Figure 00000043_0000 
Figure 00000044_0000
Abstract
Description
Ovulation day estimation system and ovulation day estimation method
[0001] [Related Applications] The present application claims priority based on Japanese Patent Application No. 2025-081079 entitled "Ovulation Day Estimation System and Ovulation Day Estimation Method" filed on May 14, 2025, the entire disclosure of which is incorporated herein by reference in its entirety. The present technology relates to an ovulation day estimation system and an ovulation day estimation method.
[0002] As background art in this technical field, JP 2022-032976 A (Patent Document 1) can be cited. This publication states that "The present invention is directed to systems and techniques for tracking the menstrual cycle, and the temperature sensing device 102 may include receiving temperature measurements from an array of temperature sensors 104 disposed on a bed 103. The usage period of the array can be determined when a temperature measurement from at least one of the one or more temperature sensors exceeds a first temperature threshold. In some embodiments, for each usage period in a set of two or more usage periods, the user's body temperature can be determined using the set of temperatures from the respective usage period. After determining the user's body temperature for each usage period in the set of two or more usage periods, at least one change in the user's body temperature between different usage periods can be identified. The user's ovulation day can be estimated based on at least one change in the user's body temperature." (see the abstract).
[0003] JP 2022-032976 A
[0004] This Patent Document 1 uses one or more temperature sensors in an array of temperature sensors arranged on a bed and under the user to reliably predict the user's ovulation day. However, in one aspect, a bulky temperature sensor array is required for predicting the ovulation day, which poses a problem of lacking versatility and ease of use.
[0005] The present technology provides a new mechanism for estimating an ovulation day.
[0006] To solve the above problems, for example, the configuration described in the claims is adopted. The present application includes multiple means for solving the above problems, but to give one example, it is characterized by providing an ovulation day estimation system comprising: an acquisition unit for acquiring temperature information of a living organism over time; a representative temperature acquisition unit for acquiring representative temperature information based on the temperature information over time; and an ovulation day estimation unit for estimating the ovulation day based on the representative temperature information.
[0007] This technology provides a new mechanism for estimating ovulation. Other issues, configurations, and effects will be clarified by the following description of the embodiments.
[0008] Figure 1 shows an example configuration of an ovulation day estimation system 100 according to one embodiment. Figure 2 shows an example hardware configuration of a wearable device 101. Figure 3 shows an example hardware configuration of a user terminal 102. Figure 4 shows an example hardware configuration of a management server 103. Figure 5 shows an example of health management information according to one embodiment. Figure 6 shows an example of other health management information according to one embodiment. Figure 7 shows an example of a transition matrix (for example, an example of model information) according to one embodiment. Figure 8 shows an example of another output matrix (for example, an example of model information) according to one embodiment. Figure 9 is an overall control flow diagram of an ovulation day estimation method according to one embodiment. Figure 10 is a sleep-wake evaluation flow diagram according to one embodiment. Figure 11 is a temperature information acquisition flow diagram according to one embodiment. Figure 12 is a representative temperature information acquisition flow diagram according to one embodiment. Figure 13 is an ovulation day estimation flow diagram according to one embodiment. Figure 14 is an example of a menstrual cycle tracker screen (partial) according to one embodiment. Figure 15 is an example of a menstrual cycle tracker screen (other partial) according to one embodiment.
[0009] The following description of this technology will be based on an ovulation estimation system and ovulation estimation method according to one embodiment, with reference to the drawings as appropriate. In each drawing, components having the same function may not be denoted by reference numerals or described again.
[0010] [Ovulation Estimation System and Ovulation Estimation Method] Figure 1 shows an example configuration of an ovulation estimation system 100 according to one embodiment. The ovulation estimation system 100 and ovulation estimation method according to this technology are typically a system and method that monitors a user's biometric information using a wearable device 101 and estimates the ovulation day. The ovulation estimation system 100 includes one or more wearable devices 101, one or more user terminals 102, and one or more management servers 103. The ovulation estimation system 100 may also include one or more chargers 104.
[0011] In one embodiment, the wearable device 101, user terminal 102, management server 103, and charger 104 are configured to send and receive information from each other via a network, for example. Furthermore, the wearable device 101, user terminal 102, and charger 104 are configured to connect via short-range wireless communication such as Bluetooth®. These wearable devices 101, user terminal 102, management server 103, and charger 104 may be configured to send and receive information from each other via a network, for example, but only among themselves. Also, any two or more of the functional elements of the wearable device 101, user terminal 102, management server 103, and charger 104 may be integrated, or any of them may be separated into two or more units.
[0012] The wearable device 101 is a terminal that a user (an example of a living organism) wears on their own body. The user terminal 102 is a terminal used by the user who uses the wearable device 101 or the user who uses the ovulation estimation system 100. The management server 103 is a terminal used by, for example, the administrator who manages the ovulation estimation system 100.
[0013] Each terminal and management server 103 in the ovulation estimation system 100 may be a mobile device such as a smartphone, tablet, mobile phone, or personal digital assistant (PDA), or a wearable device such as glasses (including goggles), a wristwatch, or clothing. The management server and terminals may also be stationary or portable computers, or servers located in the cloud or on a network. From a functional standpoint, they may also be VR (Virtual Reality), AR (Augmented Reality), or MR (Mixed Reality) terminals. Alternatively, the management server and terminals may be combinations of multiple such terminals. For example, a combination of one smartphone and one wearable device can logically function as a single terminal. Each terminal may also be an information processing terminal other than those mentioned above.
[0014] Each terminal and management server 103 of the ovulation estimation system 100 may optionally be equipped with a processor that runs an operating system, applications, and programs; a main memory such as RAM (Random Access Memory); an auxiliary memory such as an IC card, hard disk drive, SSD (Solid State Drive), and flash memory; a communication control unit such as a network card, wireless communication module, or mobile communication module; an input device such as a touch panel, keyboard, mouse, voice input device, motion controller, or motion detection device using a camera; an output device such as a monitor, display, printer, audio output device, or oscillator; and a timing device. The input device may also be equipped with sensors such as GPS, gyro sensors, and acceleration sensors. The output device may be a device or terminal that transmits information for output to an external monitor, display, printer, or other device.
[0015] The main memory stores various programs and applications (software modules), and the processor executes these programs and applications to realize each functional element of the overall system. These modules may be implemented by one or more programs or applications. Furthermore, each module may be implemented by an independent program or application, or as a subprogram or function within a single integrated program or application. These modules may also be implemented in hardware (hardware modules) by integrating circuits or employing a microcomputer.
[0016] Furthermore, each module may be implemented by a single processor or by multiple processors. Also, each module may be installed in a single terminal (including a management server) or divided among two or more terminals (including management servers) interconnected via a network. Furthermore, each module may be installed in each, or one or more, of the two or more terminals (including management servers) interconnected via a network. Consideration is also given to cases where some modules are implemented in different countries from others.
[0017] In this specification, each module is described as the entity (subject) that performs the processing; however, in reality, processing is carried out by the processor executing various programs and applications.
[0018] The auxiliary storage device stores various databases (DBs). A "database" is a collection of data organized and gathered to accommodate arbitrary data operations (e.g., extraction, addition, deletion, overwriting, etc.) from a processor or external computer. The auxiliary storage device is a functional element (storage unit) that stores one or more data collections. The implementation method of a database is not limited; for example, it may be a database management system, spreadsheet software, or text files such as XML or JSON. The database may be independently provided and connectable to a processor, etc. The database is intended, but not limited to, storing some or all of the information constituting the data collection in JSON format files. The database may be configured to store various types of information as a relational database or a non-relational database.
[0019] [Management Server] Figure 4 shows an example of the hardware configuration of the management server 103. The management server 103 is composed of a computer server located, for example, on the cloud. The management server 103 includes a main memory 401 and an auxiliary memory 402. The management server 103 also includes the processor 403 as described above, an input device 404, an output device 405, and a communication control unit 406.
[0020] The main memory 401 stores programs and applications such as the execution module 411, health management module 412, health information evaluation module 413, pre-processing module 414, post-processing module 415, and model adjustment module 416. The processor 403 executes these programs and applications to realize each functional element of the management server 103.
[0021] The execution module 411 controls the basic operation of the management server 103 for providing services by the ovulation day estimation system 100. For example, the execution module 411 works in conjunction with the execution module 311 of the user terminal 102 to control the basic operation for causing the user terminal 102 to perform the menstrual cycle status evaluation service (ovulation day estimation service). The execution module 411 can also support the operation of each module, as described later, and the coordination between each module. The execution module 411 may also be configured to work in conjunction with the execution module 211 of the wearable device 101, for example.
[0022] The health management module 412 acquires the user's biometric information. For example, the health management module 412 acquires the user's activity level information and temperature information over time. The activity level information and temperature information can be associated with each other, for example, through time information. The health management module 412 also acquires menstrual information, which is information related to the user's menstrual state. Furthermore, the health management module 412 outputs, for example, the results of the user's health evaluation evaluated by the health information evaluation module 413 to the user terminal 102. The health management module 412 is an example of an acquisition unit and a menstrual information acquisition unit in this technology.
[0023] The preprocessing module 414 is an element that processes (preprocesses) various biometric detection information of the user prior to estimating the menstrual cycle state. The preprocessing module 414 preprocesses various biometric detection information of the user, which is the input, so that the health information evaluation module 413, described later, can perform a more appropriate evaluation (including estimation). For example, the preprocessing module 414 acquires representative temperature information that better represents the user's body temperature as input information for the health information evaluation module 413. The preprocessing module 414 is an example of a representative temperature acquisition unit in this technology.
[0024] The health information evaluation module 413 evaluates the user's health status. The health information evaluation module 413 estimates and evaluates the user's health status based on various biometric detection information of the user acquired by the wearable device 101, for example. In this embodiment, the health information evaluation module 413 estimates the user's ovulation day based on representative temperature information and menstrual information, for example, using a menstrual cycle state estimation model. The health information evaluation module 413 is an example of a representative temperature acquisition unit and an ovulation day estimation unit in this technology. Hereinafter, the ovulation day estimated by the health information evaluation module 413 may simply be referred to as the "estimated ovulation day."
[0025] The menstrual cycle state estimation model M is a machine learning model configured to output the menstrual cycle state of a living organism based on its representative temperature information. For example, the menstrual cycle state estimation model M is trained to take representative temperature information of one or more cycles of a living organism as input and output the menstrual cycle state for each day. For example, the menstrual cycle state estimation model M is trained to take representative temperature information of multiple menstrual cycles of a living organism as input and output the menstrual cycle state for each day.
[0026] The menstrual cycle state estimation model M may be trained to classify the day for which the menstrual state is estimated into one of several (e.g., at least four) menstrual states based on the representative temperature information of that day. In this technology, a classification model is used as the machine learning model. While not limited to this, a hidden Markov model can be used as the classification model. Details of the classification model will be described later.
[0027] The post-processing module 415 is an element that performs additional processing (post-processing) on the output of the health information evaluation module 413. For example, the post-processing module 415 performs post-processing using the output from the menstrual cycle state estimation model M (for example, the menstrual cycle state estimated to correspond to the target day) so that the output of the health information evaluation module 413 is easier for the user to understand. For example, the post-processing module 415 acquires at least one selected from the group consisting of the next estimated ovulation date, the next estimated menstruation date, and the fertile days as cycle information based on the estimation results from the menstrual cycle state estimation model M. The post-processing module 415 is an example of a menstrual cycle state acquisition unit in this technology.
[0028] The model adjustment module 416 is an element that adjusts the menstrual cycle state estimation model M. The model adjustment module 416 readjusts (including updating) the parameters of the menstrual cycle state estimation model M, for example. The model adjustment module 416 retrains the menstrual cycle state estimation model M based on previously acquired temperature information and menstrual information, and newly acquired temperature information and menstrual information, for example. The model adjustment module 416 also stores the adjusted parameters of the menstrual cycle state estimation model M in the auxiliary storage device 402, for example. The model adjustment module 416 is an example of a model adjustment unit in this technology.
[0029] The auxiliary storage device 402 stores various types of information necessary for realizing the above-mentioned functions of the management server 103. For example, the auxiliary storage device 402 stores user information 410, health management information 420, model information 430, etc. The implementation method of each type of information stored in the auxiliary storage device 402 is not limited to this embodiment, and each type of information may be implemented in a distributed manner across multiple database servers or cloud applications.
[0030] User information 410 is, for example, information about a user of the ovulation date estimation system 100. User information 410 is typically a user of the wearable device 101. User information 410 is not limited to this, but may include, for example, user identification information, information about the user's attributes such as gender and age, and information from a health questionnaire about the user. Each piece of information is stored, for example, linked to user identification information.
[0031] Figures 5 and 6 show an example of health management information 420 according to one embodiment. Health management information 420 is information acquired, calculated, or estimated by the ovulation date estimation system 100. The figures illustrate, for example, the information of health management information 420 that is stored in an auxiliary storage device. Health management information 420 may include, for example, menstrual information shown in (A), sleep / wake flag information (sleep / wake information) shown in (B), temperature information shown in (C), representative temperature information shown in (D), estimated ovulation date information, etc. Health management information 420 may also include, for example, information such as the next estimated ovulation date, the next estimated menstrual date, and fertile days. Each of these pieces of information is associated with time (time) information. The contents of each piece of information will be described later. The auxiliary storage device can store information other than the information shown in the figures.
[0032] Model information 430 is information necessary for using the menstrual cycle state estimation model M in the ovulation day estimation system 100. Model information 430 may include, for example, the entire menstrual cycle state estimation model M, i.e., the model function and parameters and the program for operating it, or it may include parameters for operating a machine learning model stored on an external server, etc. In this embodiment, the model information may include, for example, the transition matrix and output matrix in a hidden Markov model. Model information 430 will be described later.
[0033] [User Terminal] Figure 3 shows an example of the hardware configuration of the user terminal 102. The user terminal 102 is composed of a terminal such as a smartphone, tablet, notebook PC, or desktop PC. The user terminal 102 includes a main memory 301 and an auxiliary memory 302. The user terminal 102 also includes a processor 303 as described above, an input device 304, an output device 305, a camera 306, and a communication control unit 307.
[0034] The main memory 301 of the user terminal 102 stores programs and applications such as the execution module 311, health management module 312, health information evaluation module 313, pre-processing module 314, post-processing module 315, and model adjustment module 316. The processor 303 executes these programs and applications to realize each functional element of the user terminal 102. In other words, the main memory 301 of the user terminal 102 stores the same functional modules as the main memory 401 of the management server 103, and the user terminal 102 can perform the same processing as the management server 103.
[0035] As will be described later, the main memory 301 of the user terminal 102 stores a health management application program that manages the user's health based on sensor data acquired from the ring-shaped wearable device 101. This health management application program includes, for example, a sleep detection program that detects the user's sleep state, and an application program for evaluating the menstrual cycle and estimating the ovulation day.
[0036] The functions of each of these modules are the same as those described above, so their explanation will be omitted. Note that the main memory 301 does not necessarily have to store all of the same functional modules as the management server 103; it may store only some of the functional modules (for example, the execution module 311 and the health management module 312).
[0037] The auxiliary storage device 302 stores various types of information necessary for realizing the above-mentioned functions of the user terminal 102. The auxiliary storage device 302 can store, for example, user information 310, health management information 320, model information 330, etc. Each of these pieces of information may be, for example, a part of the information stored in the management server 103 (for example, health management information including menstrual information, sleep-wake information, temperature information, and information on the menstrual cycle state related to the user).
[0038] [Wearable Device] The wearable device 101 is a device that can be attached to a living body such as a human being and non-invasively acquire the living body's biological information as digital information. The wearable device 101 according to this embodiment is a ring-shaped device that is attached to a human finger, for example, as shown in Figure 1. Figure 2 is an example of the hardware configuration of the wearable device 101 according to one embodiment.
[0039] The wearable device 101 includes a main memory 201 and an auxiliary memory 202. The management server 103 also includes the processor 203 as described above, a sensor module 204, a gyro sensor / accelerometer module 205, a charge management module 206, and a communication control unit 207. The sensor module 204 and the gyro sensor / accelerometer module 205 are examples of input devices.
[0040] The processor 203 is a digital signal processing device that controls the operation of, for example, the sensor module 204, the gyro sensor / accelerometer module 205, the charge management module 206, and the communication control unit 207. The processor 203 can be, for example, an MCU (Micro Controller Unit) or an MPU (Micro Processor Unit). The storage device can be, for example, flash memory or EEPROM (Electrically Erasable Programmable Read-Only Memory). The wearable device 101 may also include an output device (not shown).
[0041] The sensor module 204 controls, for example, the operation of various sensors provided in the wearable device 101 and the sensor signals. The sensor module 204 also controls, for example, the operating conditions of the sensors. The sensor module 204 may also include digital processing functions such as a Digital Signal Controller (DSC), Digital Signal Processor (DSP), or FPGA (Field Programmable Gate Array) that process sensor data acquired by the sensors in real time. The sensor module 204 includes, for example, any combination of resistors, capacitors, coils, diodes, transistors, etc., and can optionally include circuits such as amplifiers, clocks, bandgap references, digital isolators, RC filters (e.g., low-pass filters, high-pass filters), band-pass filters, band-elimination filters, and analog-to-digital converters. Furthermore, the sensor module 204 may include analog circuit blocks such as an RMS-DC converter circuit, an average value detection circuit, an RMS detection circuit, a signal monitoring circuit, and an adaptive threshold setting circuit that process signals acquired via the sensors. Furthermore, the sensor module 204 can be configured to perform various signal processing operations using any combination of analog circuits and / or digital processing functions.
[0042] The wearable device 101 includes, for example, a pulse wave sensor S1, a temperature sensor S2, a microwave sensor S3, an electrocardiogram sensor S4, etc., and the sensor module 204 is connected to these sensors S1 to S4. These sensors S1 to S4 are, for example, examples of signal detection devices (sensors) for detecting various kinds of biological information, and are examples of input devices for the wearable device 101. Each sensor S1 to S4 may also be equipped with a digital signal controller (DSC) that processes sensor data in real time.
[0043] The pulse wave sensor S1 is a photoplethysmogram (PPG) sensor that detects volume changes in a biological blood vessel (for example, an artery). In the ring-type wearable device 101, the pulse wave sensor S1 can typically be a reflective pulse wave sensor composed of a light-emitting element that emits light of a predetermined wavelength toward the living body, and a light-receiving element that detects the light reflected inside the living body. The light-emitting element can be configured by, for example, various types of light-emitting diodes (LEDs), and the light-receiving element can be configured by, for example, various types of photodiodes (PDs).
[0044] Various types of biological information can be obtained by analyzing the PPG signal acquired by the PPG sensor. Specifically, for example, the light-emitting element can include a green LED that generates light with a central wavelength of 500 nm or more and 600 nm or less. Green light has a high absorption rate by hemoglobin in blood and is less affected by disturbance light such as sunlight, so a relatively stable photoplethysmogram can be measured. Based on the pulsation of the photoplethysmogram from this green light, for example, highly reliable heart rate and heart rate variability information can be obtained.
[0045] In addition, oxyhemoglobin, deoxyhemoglobin (also referred to as reduced hemoglobin), and glycated hemoglobin may each have different extinction coefficients (typically, absorption spectra) for wavelengths of red light to near-infrared light. Therefore, as a preferred example, the light-emitting element can include, for example, a combination of a red LED with a central wavelength of 630 nm or more and 690 nm or less, and an infrared LED with a central wavelength of 810 nm or more and 990 nm or less. Based on the difference in extinction coefficients of oxyhemoglobin and deoxyhemoglobin for these two types of light, SpO2 (Peripheral Blood Oxygen Saturation: percutaneous arterial oxygen saturation) and blood oxygen concentration heart rate can be obtained.
[0046] As another preferred example, the light-emitting element may include, for example, a combination of LEDs that generate three or more (for example, three or four) different light beams with a central wavelength of 600 nm to 990 nm. Based on the difference in the absorption coefficients of oxyhemoglobin, deoxyhemoglobin, and glycated hemoglobin, the blood hemoglobin concentration, the blood glycated hemoglobin concentration, and the like can be calculated.
[0047] Furthermore, the light-emitting element may include an LED that generates light of a wavelength different from those described above. Since information on hemodynamics is embedded in the shape of the pulse wave, blood pressure can be estimated by analyzing the shape of the volume pulse wave. In addition, by analyzing the shape of the volume pulse wave, the viscosity of blood can be estimated, and the blood glucose level can be detected from the viscosity of blood. Regarding the measurement of blood glucose level, a spectroscopic method (for example, near-infrared spectroscopy, Raman spectroscopy, infrared spectroscopy, etc.) may be adopted. For example, the light-emitting element may include a combination of LEDs that generate two or more (for example, two or three) different near-infrared light beams with a central wavelength of approximately 1200 nm to 1600 nm. Thereby, the blood glucose level can be calculated based on the light absorption spectrum derived from glucose.
[0048] The temperature sensor S2 is an optionally provided sensor, and can detect temperature (body temperature) information of the living body. The temperature sensor S2 can typically detect information related to the skin temperature (also referred to as skin surface temperature) or the core body temperature of the living body. The temperature sensor S2 is not limited thereto, and for example, a thermopile type infrared sensor can be used.
[0049] The microwave sensor S3 is an optionally provided sensor, and can detect frequency characteristics around the resonance frequency by, for example, radiating microwaves to the living body. By analyzing these frequency characteristics, information related to the skin moisture content, perspiration amount, blood glucose level, and the like can be obtained.
[0050] The electrocardiogram sensor S4 is an optional sensor capable of detecting electrical activity associated with the movement of the heart. The electrocardiogram sensor S4 can be used as one of the measurement electrodes in various lead methods. Therefore, for example, the electrocardiogram sensor S4 may be configured to obtain electrocardiogram information in cooperation with other electrocardiogram sensors S4 provided on other wearable devices 101. As an example, electrocardiogram information can be obtained using the bipolar lead method with two ring-shaped wearable devices 101 worn on the fingers of both the left and right hands. Alternatively, electrocardiogram information may be obtained by a combination of a ring-shaped wearable device 101 worn on the finger of one hand, a wristwatch-shaped wearable device 101 worn on the wrist of the other hand, a user terminal 102 (smartphone, etc.), or a medical device, etc.
[0051] The gyro sensor / accelerometer module 205 is equipped with a gyro sensor and an accelerometer. The gyro sensor / accelerometer module 205 can detect the angular velocity and acceleration of the wearable device 101 and can detect changes in the position of the wearable device 101 (displacement, tilt, movement, etc.). In addition, the gyro sensor / accelerometer module 205 can acquire information regarding the posture, activity level, activity intensity, calories burned, steps taken, and behavioral discrimination of the person wearing the wearable device 101.
[0052] Furthermore, the gyro sensor / accelerometer module 205, like the sensor module 204 described above, can optionally be equipped with digital processing functions such as a DSC, DSP, FPGA, etc., for processing the sensor data acquired by the sensor in real time, as well as various analog circuits.
[0053] The charge management module 206 is an element that manages charging in the charging system provided in the wearable device 101. Figure 2 shows an example of a wireless charging system that charges the secondary battery 208 from the charger 104 without physical contact via a wireless charging receiver 209. However, the wearable device 101 may be configured to include, in place of and / or in addition to the wireless charging receiver 209, contact electrodes (not shown) for contact charging with the charger 104.
[0054] The wireless charging system includes, for example, a charge management module 206, a secondary battery 208, and a wireless charging receiver 209 provided in a wearable device 101, and an external charger 104. The charge management module 206 manages the charging process to prevent overcurrent, overvoltage, overheating, etc., of the secondary battery 208. The secondary battery 208 is not particularly limited, but examples include lithium-ion batteries, lithium polymer batteries, and all-solid-state lithium-ion batteries.
[0055] Furthermore, various charging systems can be employed as wireless charging systems, such as electromagnetic induction, magnetic field resonance, electric field coupling, and radio wave reception. For example, a wireless charging system compatible with Near Field Communication (NFC) standards or Qi standards can be preferably adopted in this embodiment. Among these, a system compatible with NFC standards is particularly preferable because it allows for miniaturization and cost reduction.
[0056] The communication control unit 207 is configured to connect to other terminals (for example, user terminal 102) via a network. The network can be wired or wireless, and each terminal can send and receive information from each other via the network. In the case of wireless communication, communication devices conforming to standards such as Bluetooth®, Wi-Fi®, or LTE® can be used. In this embodiment, the communication control unit 207 connects to the user terminal 102 via BLE (Bluetooth Low Energy) communication.
[0057] The wearable device 101 stores programs and applications such as an execution module 211, a health management module 212, a health information evaluation module 213, a pre-processing module 214, a post-processing module 215, and a model adjustment module 216 in its main memory 201. The processor 203 then executes these programs and applications to realize each functional element of the wearable device 101. In other words, by storing the same functional modules in the main memory 201 of the wearable device 101 as in the main memory 401 of the management server 103, the wearable device 101 can perform the same processing as the management server 103.
[0058] The functions of each of these modules are the same as described above, and their explanation will be omitted. Note that the main memory 201 does not necessarily have to store all of the same functional modules as the management server 103. Alternatively, it may store only some of the same functional modules as the management server 103 (for example, the pre-processing module 214). Furthermore, each functional module may be composed of analog circuits, either partially or entirely. As will be described later, as an example, the main memory 201 stores the pre-processing module 214.
[0059] The auxiliary storage device 202 stores various types of information necessary for realizing the above-mentioned functions of the wearable device 101. The auxiliary storage device 202 can store, for example, user information, health management information, model information, etc. In this embodiment, the auxiliary storage device 202 stores, for example, a portion of the information stored in the management server 103 (for example, health management information including temperature information and sleep-wake information).
[0060] [Ovulation Day Estimation Method] Next, an ovulation day estimation method according to one embodiment will be described. The ovulation day estimation system 100 is configured to evaluate the health status of the user wearing the wearable device 101 in relation to the menstrual cycle by operating the wearable device 101 in "ovulation day estimation mode".
[0061] In ovulation estimation mode, for example, the following information related to "ovulation estimation" is obtained / estimated: • Estimation of daily menstrual cycle status • Daily changes in skin temperature
[0062] Figure 9 is an overall control flow diagram of an ovulation date estimation method according to one embodiment. When the user terminal 102 receives a selection (i.e., an operation instruction) to turn "ovulation date estimation mode" to "ON" through user operation, the execution module 311 of the user terminal 102 sends an instruction to the wearable device 101 to operate in ovulation date estimation mode. The execution module 311 of the user terminal 102 may also send information to the management server 103 indicating that it has received an instruction from the user to turn on the ovulation date estimation mode.
[0063] In ovulation estimation mode, the wearable device 101 (ring) generally (1) acquires menstrual information from the user, (2) performs sleep / wake assessment, and (3) acquires temperature information. Then, for example, when the user wakes up, the wearable device 101, user terminal 102, and management server 103 work together to transmit the acquired information to the management server 103 via the user terminal 102. Based on this information, the management server 103, for example, (4) acquires representative temperature information and (5) estimates the ovulation day based on the acquired representative temperature information. In addition, the management server 103 also estimates (6) other menstrual cycle states. The management server 103 adjusts (7) the menstrual cycle state estimation model M. Then, the management server 103 transmits the ovulation day estimation result to the user terminal 102, and the user terminal 102 provides the ovulation day estimation result to the user. The following describes each process. However, this technology does not require all of the above processes (1) to (6).
[0064] (1) Acquisition of Menstrual Information Figure 14 is an example of a menstrual cycle tracker screen 1400 (partial) according to one embodiment. The execution module 411 of the management server 103, for example when the "ovulation day estimation mode" is ON, works in cooperation with the execution module 311 of the user terminal 102 to display the menstrual cycle tracker screen 1400 on the output device 305 such as the display of the user terminal 102. The health management module 412 of the management server 103, for example, works in cooperation with the health management module 312 of the user terminal 102 to acquire the user's past and present menstrual information via this menstrual cycle tracker screen 1400.
[0065] The health management module 312 displays, for example, a menstrual cycle tracker screen 1400, a menstrual cycle prediction field 1410, an ovulation day prediction field 1420, and a menstrual calendar 1430. The health management module 312, for example, in the menstrual calendar 1430, accepts the user's selection of a date and menstrual information, and stores this menstrual information in association with the date. The contents of the menstrual information include, for example, the day of menstruation, the start date of menstruation, the end date of menstruation, etc. The health management module 312, for example, in the menstrual calendar 1430, outputs a display 1432 indicating that it is a menstrual day for a day on which menstrual information has been received from the user. Here, the health management module 312 displays the number representing the date of menstruation in white within a dark circle, and smoothly connects consecutive dark circles with a band of a different color. The health management module 312, for example, highlights today's date with a circle 1440, etc. Furthermore, the health management module 312 displays menstrual information acquisition fields, such as a menstrual flow level acquisition field 1434 and a menstrual pain level acquisition field 1436. The menstrual information acquisition fields allow the user to input the menstrual state level for each day, for example, when the menstrual state is represented in multiple stages (four stages in the diagram). The health management module 312 acquires menstrual information for each day by accepting the user's input of menstrual information (menstrual flow level, menstrual pain level, etc.) in these menstrual information acquisition fields. The health management module 312 displays the day on which the user entered the menstrual flow level as the menstrual day.
[0066] Furthermore, the health management module 312 may, for example, determine the first day of a series of consecutive days as the start date of menstruation and the last day of a series of consecutive days as the end date of menstruation when the user associates menstrual cycle information with multiple consecutive days. The health management module 312 may also determine the number of days from the start date to the end date of menstruation as the number of menstrual days. The health management module 312 may acquire information about the menstrual cycle based on, for example, the start date of menstruation and the start date of menstruation in the previous cycle. The health management module 312 may also be configured to accept information such as the amount of menstrual blood and the degree of menstrual pain as menstrual information. The health management module 312 stores this information, for example, as menstrual information (an example of health management information 320) in the auxiliary storage device 302.
[0067] The health management module 312 transmits the menstrual information, associated with the user ID, to the management server 103, for example, each time it receives menstrual information input from the user, or at predetermined times each day. The health management module 412 of the management server 103 stores the menstrual information obtained from the user terminal 102 as the user's health management information 420 in the auxiliary storage device 402.
[0068] (2) Sleep-Wake Evaluation Diagram 10 is a sleep-wake evaluation flowchart according to one embodiment. The execution module 211 of the wearable device 101 operates each module in ovulation estimation mode based on instructions from, for example, the user terminal 102. In ovulation estimation mode, the health management module 212 and the pre-processing module 214 of the wearable device 101 execute the sleep-wake evaluation flowchart 1000.
[0069] The sleep-wake evaluation flow 1000 includes, for example, the following steps: acquiring acceleration sensor information (S1010), evaluating sleep or wakefulness per unit time (S1020), and assigning sleep flags or wakefulness flags (S1030, 1040, 1050).
[0070] The health management module 212 first acquires acceleration information from the gyro sensor / accelerometer module 205 (step S1010). Here, acceleration information is an example of user activity level information. The health management module 212, for example, sends an instruction to the gyro sensor / accelerometer module 205 to operate the acceleration sensor and acquire acceleration information over time at a predetermined sampling rate. Although the conditions for acquiring acceleration information are not strictly limited, for example, the sampling rate can be approximately 10 to 30 Hz (for example, approximately 12.5 Hz). Also, the acceleration information can be, for example, three-axis acceleration information in the x, y, and z axis directions.
[0071] The preprocessing module 214 evaluates whether the user wearing the wearable device 101 is in a sleep or wakeful state based on the acquired acceleration information (step S1020). For sleep / wake determination based on acceleration information (an example of activity level information), a sleep determination algorithm can be used, for example. Examples of sleep determination algorithms are not limited to this, but include the Cole-Kripke algorithm and the Sadeh algorithm.
[0072] In this embodiment, the Cole-Kripke algorithm is employed. The preprocessing module 214 obtains, for example, representative values of activity intensity data within a predetermined time interval (window) from the acquired acceleration information. Examples of representative values of activity intensity data for a predetermined time include the mean, median, and peak values of the vector norm (which may be a simplified norm with the square root omitted) for 0.5 to 5 minutes (for example, 1 minute). The preprocessing module 214 may, as an optional step, take a moving average of the representative values of the activity intensity data within a 1-minute window and average them. Next, the preprocessing module 214 calculates a weighted score for the representative values of the activity intensity data according to the Cole-Kripke algorithm. The weighted score can be calculated, for example, by applying the weights of the Cole-Kripke algorithm to the data in the preceding and succeeding windows (for example, 3 minutes before and after) and summing them with the data in the window of the time to be evaluated. The weights are not limited to these examples, but one example is to assign a weight of "1" to the time being evaluated, a weight of "0.20" to times within ±1 minute, and a weight of "0.04" to times within ±2 minutes.
[0073] The preprocessing module 214 then determines, for example, that the user is "sleeping" if the weighted score for the time period being evaluated is less than a predetermined threshold, and that the user is "awake" if the weighted score is greater than the predetermined threshold. The threshold for the weighted score cannot be generalized as it depends on the configuration of the acceleration sensor and how the weights are assigned, but it can be set based on pre-acquired weighted scores and the user's actual activity status. Furthermore, the threshold for the weighted score can be empirically set and updated, for example, according to the characteristics of the user's activity intensity.
[0074] Then, if the preprocessing module 214 evaluates the state as "sleep" (Y in S1030), it associates a "sleep flag" indicating sleep with the evaluation time (S1040). Also, if the preprocessing module 214 evaluates the state as "awake" (N in S1030), it associates an "awake flag" indicating wakefulness with the evaluation time (S1050). The preprocessing module 214 stores (outputs) sleep-wake information, which associates the evaluation time with sleep or wakefulness flags (sleep / wakefulness flag information), in the auxiliary storage device 202.
[0075] The processing steps S1010 to S1050 described above may be performed by the gyro sensor / accelerometer module 205, and the processing results (for example, sleep-wake information) may be acquired by the pre-processing module 214.
[0076] Furthermore, the execution module 311 of the user terminal 102 may be configured to execute the sleep-wake evaluation flow 1000 on the wearable device 101 when the "ovulation day estimation mode" is ON and a predetermined time (for example, the scheduled bedtime of 9 PM) or a predetermined time period (for example, from the scheduled bedtime of 9 PM to 6 AM the next day) has been set. Alternatively, the execution module 311 may send an instruction to the wearable device 101 to execute the sleep-wake evaluation flow 1000 when a predetermined time (for example, the scheduled bedtime of 9 PM) or a predetermined time period (for example, from the scheduled bedtime of 9 PM to 6 AM the next day) has been set.
[0077] (3) Acquisition of temperature information If the sleep-wake evaluation flow 1000 described above is evaluated as "sleep", the health management module 212 of the wearable device 101 executes the temperature information acquisition flow 1100 in parallel with the sleep-wake evaluation flow 1000. Figure 11 is a temperature information acquisition flow diagram according to one embodiment.
[0078] The temperature information acquisition flow 1100 includes, for example, the following steps: acquiring temperature sensor information (S1110), acquiring average skin temperature information (S1120), an awakening evaluation step (S1130), and a skin temperature information output step (S1140). Note that the awakening evaluation step (S1130) is an optional step and does not necessarily need to be performed.
[0079] The health management module 212 first acquires temperature sensor information from the sensor module 204 (S1110). The health management module 212, for example, sends an instruction to the sensor module 204 to operate the temperature sensor S2 and acquire temperature information of the living body's skin (typically the finger wearing the ring-type wearable device 101) over time at a predetermined sampling rate. The conditions for acquiring skin temperature information can be, for example, acquired over time at each first time window. Although not strictly limited, the health management module 212 can, for example, set the sampling rate to approximately 0.01 to 1 Hz (for example, every minute).
[0080] The preprocessing module 214 then acquires average skin temperature information based on the acquired skin temperature information (S1120). The preprocessing module 214 may, for example, cause the DSC of the sensor module 204 or temperature sensor S2 to perform part or all of the process of acquiring the average skin temperature from the acquired skin temperature information. In this embodiment, the preprocessing module 214 causes the DSC to perform an averaging process and acquires the calculated average skin temperature. For example, the DSC may take a moving average of the skin temperature information acquired in a 1-minute window over a second time window (e.g., 5 minutes) that is longer than the first time window (e.g., 1 minute), and use the averaged value as the average skin temperature. The preprocessing module 214 stores the acquired information regarding the average skin temperature in, for example, the auxiliary storage device 202.
[0081] The pre-processing module 214 checks whether the user is evaluated as "awake" in the sleep-wake evaluation flow 1000 (S1130). If the user is evaluated as "awake" (Y in S1130), the pre-processing module 214 moves on to the next step (S1140). If the user is not evaluated as "awake" (N in S1130), the pre-processing module 214 returns to step S1110, and the health management module 212 acquires skin temperature information for the next first time window. In other words, the pre-processing module 214 repeatedly executes steps S1110 to S1120 in the sleep-wake evaluation flow 1000 from the time the user is evaluated as "sleeping" until the time they are evaluated as "awake".
[0082] When the user is evaluated as "awake," the preprocessing module 214 stores the average skin temperature acquired for each second time window in the auxiliary storage device 202 as average skin temperature information, associating it with information about the second time window, for example as shown in Figure 5(C) (S1140). The preprocessing module 214 may also store (output) the average skin temperature acquired for each second time window in the auxiliary storage device 402 of the management server 103, for example via the user terminal 102.
[0083] In the sleep-wake evaluation flow 1000, if the user is evaluated as "sleeping," the pre-processing module 214, in cooperation with the pre-processing module 314 of the user terminal 102, transmits the average skin temperature information and sleep-wake information stored in the auxiliary storage device 202 to the user terminal 102. The pre-processing module 314 of the user terminal 102, in cooperation with the pre-processing module 414 of the management server 103, transmits the average skin temperature information and sleep-wake information acquired from the wearable device 101 to the management server 103. The pre-processing module 414 of the management server 103 stores the acquired average skin temperature information and sleep-wake information in the auxiliary storage device 402. Here, the information transmitted and received between the wearable device 101, the user terminal 102, and the management server 103 is flag information (sleep-wake information) associated with time information related to a predetermined time window, and skin temperature information (average skin temperature information) associated with time information related to a second time window, and the amount of information is reduced compared to raw data (or simply digitized data).
[0084] (4) Acquisition of representative temperature information Next, the preprocessing module 414 in the management server 103 acquires representative temperature information to be used to estimate the ovulation day. Here, representative temperature information is a temperature that can be considered as the basal body temperature of the body, and is information that will be used in the estimation step of the next step to estimate the ovulation day with greater accuracy.
[0085] Figure 12 is a flowchart illustrating the acquisition of representative temperature information according to one embodiment. The representative temperature information acquisition flow 1200 includes, for example, the following steps: an acquisition step of average skin temperature information (S1210), an acquisition step of sleep-wake information (S1220), an acquisition step of average skin temperature information when sleep is longer than a predetermined time (S1230), an exclusion step (S1240), an acquisition step of representative temperature information (S1250), and an output step of representative temperature information (S1260). However, the representative temperature information acquisition flow 1200 is an optional step, and the average skin temperature information can also be used as representative temperature information.
[0086] The preprocessing module 414 acquires, for example, average skin temperature information and sleep-wake information from the auxiliary storage device 402 (S1210, S1220). Then, based on the sleep-wake information, it extracts average skin temperature information when the sleep time is continuous and exceeds a predetermined time (S1230). The predetermined time that serves as the criterion for determining the continuity of sleep can be, for example, 3 hours or more, preferably 4 hours or more.
[0087] It is known that in living organisms (especially mammals), core body temperature (CBT) decreases at night (in the case of diurnal organisms), particularly during sleep. To achieve restful sleep and for the body's core body temperature to reach its lowest point, it is desirable to sleep continuously for three hours or more. On the other hand, during sleep, the activity of the sympathetic nervous system decreases, and peripheral blood vessels such as those in the skin dilate, making it easier for heat to dissipate into the surroundings. This heat loss from the skin is reflected as an increase in distal skin temperature. In other words, the skin temperature of the fingers, one of the body parts most distal to the heart, can increase during sleep as rest conditions are met (the parasympathetic nervous system becomes dominant). However, even during sleep, the fingers may move due to body movements rather than the rest of the body.
[0088] In this technology, taking these points into consideration, for example, the skin temperature of the fingers when rest conditions are better met by taking continuous sleep for a predetermined period of time (e.g., 3 hours or more, preferably 4 hours or more) is used to estimate the ovulation day.
[0089] The duration of sleep can be calculated, for example, by arranging sleep / wake flags in chronological order based on sleep-wake information and counting the number of consecutive sleep flags, using the following formula: Continuous sleep duration T = Σ (number of consecutive sleep flags) × (second time window) The preprocessing module 414 extracts average skin temperature information corresponding to the time when the duration of sleep exceeds a predetermined time.
[0090] Next, the preprocessing module 414 removes information that exceeds a first criterion from the extracted average skin temperature information (S1240). In the case of the ring-type wearable device 101, temperature information can fluctuate significantly if the user moves their arm relatively large while sleeping. As a result, the average skin temperature information may also include abnormal values. In contrast, abnormal values can be removed by removing information that exceeds a first criterion from the average skin temperature information. The first criterion as an indicator for removing abnormal values is not limited to this, but for example, values where the deviation from the average body temperature of the menstrual cycle is 1.5 to 2 times or more the standard deviation (for example, 1.8 times or more) can be considered abnormal values.
[0091] The preprocessing module 414 can acquire representative temperature information based on the remaining average skin temperature information from which abnormal values have been excluded in this manner (S1250). The representative temperature can be, for example, the average, median, peak, or maximum value of the remaining average skin temperature. In this embodiment, the maximum value of the remaining average skin temperature is adopted as the representative temperature. This makes it possible to use the skin temperature of the user in the state where the activity of the sympathetic nervous system is at its lowest, among the remaining average skin temperatures after removing abnormal values from the average skin temperature of the user's fingers during sleep on the day in question, for estimating the ovulation day. As a result, for example, the influence of body temperature when the user is about to wake up or enters REM sleep and the sympathetic nervous system becomes dominant can be suppressed. The preprocessing module 414 records (outputs) the acquired representative temperature information to the auxiliary storage device 402 (S1260).
[0092] (5) Estimation of Ovulation Day Subsequently, the health information evaluation module 413 in the management server 103 estimates the ovulation day. In this embodiment, the health information evaluation module 413 of the management server 103 estimates the ovulation day using the menstrual cycle state estimation model M (S1110). Figure 13 is a flowchart of the ovulation day estimation according to one embodiment. The ovulation day estimation flow 1300 includes, for example, the following steps: acquisition of representative temperature information (S1310), acquisition of menstrual state information for each day (S1320), estimation of the ovulation day (S1330), output step (S1340);
[0093] The health information evaluation module 413 acquires, for example, representative temperature information and menstrual status information from the auxiliary storage device 402 (S1310). The health information evaluation module 413 acquires, for example, (1) information that it is the start date of menstruation, (2) representative temperature information of the user for three days before and after the start date of menstruation (e.g., representative body surface temperature), and (3) menstrual status information for at least the most recent cycle.
[0094] The health information evaluation module 413 then inputs the acquired representative temperature information and menstrual status information (e.g., the start date of menstruation) into the menstrual cycle state estimation model M, thereby obtaining information about the menstrual status for each day as output (S1320). The menstrual cycle state estimation model M classifies each day corresponding to the input representative temperature information into one of the following 10 menstrual cycle states, for example.
[0095] 1) HM: First day of menstruation to days with heavy / moderate bleeding 2) LM: Days with light bleeding, end of menstruation 3) LE: Low estrogen phase 4) HE: High estrogen phase 5) Ovu: Ovulation day, only one day 6) Rise: Progesterone rising phase 7) HP: Progesterone peak 8) EP: Estrogen peak 9) LP: Low progesterone phase 10) End: End of menstrual cycle, day before the next menstruation begins
[0096] This allows the health information evaluation module 413 to obtain information about the menstrual cycle status for each day. As a result, the health information evaluation module 413 estimates the day classified as an "ovulation day" in the menstrual cycle status as the ovulation day (S1330). This allows the health information evaluation module 413 to evaluate, for example, whether the current day is an "ovulation day". In addition, the health information evaluation module 413 can estimate, for example, the most recent "ovulation day" in the past.
[0097] The health information evaluation module 413 stores (outputs) to the auxiliary storage device 402 any day classified as an "ovulation day" as an ovulation day (S1340). The health information evaluation module 413 may also be configured to cooperate with the health information evaluation module 313 of the user terminal 102 to display (output) information on the user terminal 102 indicating that any day classified as an "ovulation day" is an ovulation day (S1340).
[0098] Furthermore, research has shown that even in the same individual, or even when the menstrual cycle length appears constant, the actual menstrual cycle can vary. For example, it has been reported that over 42% of women experience a difference of 7 days or more in their cycle length. The applicants of this invention have also confirmed such variability in cycle length and ovulation date through ovulation tests. Therefore, this technology does not focus on predicting future ovulation dates, but rather on enabling highly accurate detection of ovulation, given the large variability in actual menstrual cycles and the difficulty in predicting the impact of external factors such as illness and stress on future ovulation.
[0099] <About the Menstrual Cycle State Estimation Model M> The menstrual cycle state estimation model M used in this embodiment is a hidden Markov model (HMM) with the above 10 menstrual cycle states as hidden states. This menstrual cycle state estimation model M estimates these state transitions over time. Specifically, it outputs which of the 10 menstrual cycle states (hidden states) the day corresponding to the input representative body temperature information is in.
[0100] The menstrual cycle state estimation model M (i.e., each matrix) can be obtained, for example, by analyzing the temperature distribution of the representative temperature information acquired using the wearable device 101, modeling the temperature characteristics for each state as a probability distribution using a probability distribution function (PDF), and then optimizing (learning) it based on the periodic data (observational data) of the representative temperature information obtained for each user.
[0101] In the modeling process, for the temporal (periodic) temperature data based on representative temperature information, for example, (1) reference values for "TL (low temperature)" and "TH (high temperature)" are set, and (2) the difference between TL and TH is defined as "DT". Using these TL, TH, and DT, a normalized probability distribution function (PDF) is created for each state (states 1 to 9 above). TL and TH can be, for example, the lower 25th percentile (25% of the value from the bottom) and the upper 80th percentile (80% of the value from the bottom) of the representative temperature, respectively. The temperature range below TL can be considered the "low temperature region," and the temperature range above TH can be considered the "high temperature region." The probability distribution function (x, y) can be, for example, one where x is the representative temperature and y represents the probability density in the range of 0 to 1. As a result, each of the nine states will have a different temperature distribution, and this distribution can be used to identify or estimate each state (especially state 5: ovulation day).
[0102] The menstrual cycle state estimation model M has the following probability parameters set, for example: (a) Initial state probability - Information on which day is the first day of menstruation (HM) (and consequently, information on which day is the end of the menstrual cycle (End)) - Information on which day is the end day of menstruation (LM) (b) Transition probability - Represents the probability of transitioning from one state to the next in the menstrual cycle state. The transition probability is defined, for example, as a transition matrix as shown in Figure 7. (c) Observation probability - Represents the probability that each menstrual cycle state (hidden state) is obtained (appears) based on the observed value (representative body temperature information in this technology). The observation probability is defined, for example, as an output matrix (also called an observation probability matrix) as shown in Figure 8.
[0103] <Reliability Evaluation 1> It is known that women's menstrual cycles are prone to irregularities. Therefore, the post-processing module 415 can additionally evaluate the ovulation date estimation results by the health information evaluation module 413 using a reliability score. For example, the reliability of the estimated ovulation date can be shown by equation (1) below. Each term in the numerator of the right-hand side of equation (1) is as shown in equations (2) to (7) below.
[0104]
[0105] The post-processing module 415 calculates reliability, for example, according to formulas (1) to (7) above. The post-processing module 415 may also be configured to evaluate whether the calculated reliability value is equal to or greater than a predetermined standard (for example, 0.75), and to determine that the reliability of the estimated ovulation day is high if the reliability value is equal to or greater than the predetermined standard, and to determine that the reliability of the estimated ovulation day is low if the reliability value falls below the predetermined standard.
[0106] In this case, the health information evaluation module 413 may be configured to output the estimated ovulation date to the user terminal 102 if the post-processing module 415 determines that the estimated ovulation date is highly reliable, and not to output the estimated ovulation date to the user terminal 102 if the post-processing module 415 determines that the estimated ovulation date is unreliable. This makes it possible to provide the user with more reliable information regarding the estimated ovulation date.
[0107] <Reliability Evaluation 2> The post-processing module 415 may also be configured to evaluate, for example, whether the ovulation date estimated by the health information evaluation module 413 falls within a predetermined low-reliability region, and to determine that the estimated ovulation date is highly reliable if it does not fall within the low-reliability region, and to determine that it is unreliable if it does fall within the low-reliability region. The low-reliability region is exemplified by the period before the 10th day of the menstrual cycle, from the start of menstruation to the day before the next menstruation.
[0108] In this case as well, the health information evaluation module 413 may be configured to output the estimated ovulation date to the user terminal 102 if the post-processing module 415 determines that the estimated ovulation date is highly reliable, and not to output the estimated ovulation date to the user terminal 102 if the post-processing module 415 determines that the estimated ovulation date is unreliable. Even with such a configuration, it is possible to provide the user with more reliable information regarding the estimated ovulation date.
[0109] Furthermore, if the estimated ovulation date falls within the low-confidence region, the health information evaluation module 413 may re-estimate the ovulation date by using the average or median of the average skin temperature as the representative temperature, instead of the highest value of the remaining average skin temperature after removing outliers. This configuration also allows for the provision of more reliable information regarding the estimated ovulation date to the user.
[0110] (6) Menstrual cycle estimation process Next, the post-processing module 415 of the management server 103 may be configured to estimate future menstrual cycles according to, for example, pre-set conditions. For example, the post-processing module 415 may be configured to obtain, for example, future ovulation dates (next estimated ovulation date), expected menstruation dates (next menstruation start date, next menstruation end date, etc.), and fertile days in the next cycle, based on the estimation results of the menstrual cycle status for each day by the health information evaluation module 413 (including the estimation results of the ovulation date).
[0111] Furthermore, the post-processing module 415 may be configured to calculate the average menstrual cycle and average menstrual length (average number of days) for the user's menstrual cycle based on previously acquired data.
[0112] Although not limited to this, the post-processing module 415 can, for example, obtain the expected date of the next menstruation (the start date of the next menstruation, the end date of the next menstruation, etc.), the expected date of the next ovulation, the fertile days of the next cycle, etc., based on representative values of past menstrual length and menstrual cycles (e.g., mean, median, etc.).
[0113] (7) Provision of health management information Figure 14 is an example of a menstrual cycle tracker screen (part) 1400 according to one embodiment. Figure 15 is an example of a menstrual cycle tracker screen (another part) 1500 according to one embodiment. When the estimated ovulation date is obtained, the health information evaluation module 413 transmits various menstrual information such as the estimated ovulation date and future menstrual cycles to the user terminal 102. The health information evaluation module 313 of the user terminal 102 stores the acquired information in the auxiliary storage device 302.
[0114] Furthermore, the execution module 411 of the management server 103, for example, works in conjunction with the execution module 311 of the user terminal 102 to display the menstrual cycle tracker screens 1400 and 1500 on the output device 305 of the user terminal 102, such as a display. The health management module 312 displays various menstrual information, including the estimated ovulation date, on these menstrual cycle tracker screens 1400 and 1500.
[0115] The health management module 312 displays an ovulation prediction field 1420 on the menstrual cycle tracker screen 1400. The health management module 312 may also display, for example, the estimated ovulation day along with the reliability value of the estimated ovulation day (which may be converted to a percentage) in the ovulation prediction field 1420. The health management module 312 may also display an indicator 1422 (here, a flower-shaped mark) on the corresponding day in the menstrual calendar 1430 of the menstrual cycle tracker screen 1400 to indicate that it is the estimated ovulation day. Furthermore, the health management module 312 may also predict and display fertile days 1442 (for example, two days before and after the estimated ovulation day) based on the estimated ovulation day.
[0116] The health management module 312 also displays a menstrual cycle prediction field 1410 for the next menstruation on the menstrual cycle tracker screen 1400. In the menstrual cycle prediction field 1410, the health management module 312 outputs information about the next menstruation, such as the next menstrual start date, average menstrual cycle, and average menstrual length (average number of days). The next menstrual information may include, for example, the number of days until the next menstrual start date, an evaluation result of whether the average menstrual cycle is longer or shorter, and an evaluation result regarding the length of the average menstrual length. For example, the health management module 312 evaluates the average menstrual cycle as "slightly unwell (longer)" if it is longer than a predetermined standard (e.g., 35 days), and as "slightly unwell (shorter)" if it is shorter than a predetermined standard (e.g., 21 days). Furthermore, the health management module 312 evaluates, for example, that the average menstrual period length is "somewhat unwell (longer)" if it is above a predetermined standard (e.g., 7 days), and "somewhat unwell (shorter)" if it is below a predetermined standard (e.g., 2 days).
[0117] The health management module 312 may display an indication 1444 on the menstrual calendar 1430 of the menstrual cycle tracker screen 1400 that it is the next menstrual period. Here, a circle of a different color is placed on the day in question, and consecutive circles are smoothly connected by a band. The health management module 312 may also display an indication (not shown) on the menstrual calendar 1430 that it is the next menstrual period. The health management module 312 may also be configured to accept user input via the menstrual cycle tracker screen 1400 to obtain information such as the user's mood for the day, whether or not they have had sexual intercourse, other physical symptoms, and other useful information.
[0118] The health management module 312 displays the trend 1510 of the representative temperature for each day of the most recent menstrual cycle on the menstrual cycle tracker screen 1500, based on the representative temperature information stored in the main memory 301. The trend 1510 of the representative temperature may be displayed as a graph showing the deviation of the representative temperature for each day from the average value, with the average value of the representative temperature for the most recent cycle as the baseline (± zero). The health management module 312 may also display, for example, the deviation from the average value of the representative temperature (e.g., skin temperature) during the most recent sleep (e.g., sleep from the previous night to the morning of the current day) as "latest change" 1520. This technology makes it possible to appropriately detect and provide daily changes in skin temperature at a level of ±0.1℃, in other words, changes in physical condition.
[0119] In the ovulation estimation system 100, while operating in ovulation estimation mode, estimated ovulation date and other menstrual information are acquired each time a representative body temperature is obtained, in other words, each time the user wakes up from sleep. Therefore, according to this technology, it is possible to obtain more accurate estimated ovulation date and other menstrual information that takes into account the influence of the user's current lifestyle.
[0120] In this technology, regarding the acquisition of average skin temperature information, for example, if the first time window is set to 1 minute, the second time window to 5 minutes, and the sleep time to 8 hours, the average skin temperature information for one day's sleep generally includes 96 temperature data points. Therefore, for example, when sending average skin temperature information from the wearable device 101 to the user terminal 102 when the user wakes up, a smaller amount of data can be transmitted in a shorter time, while suppressing power consumption. As a result, even a small wearable device 101, such as a ring, with limited battery capacity, can monitor the user's health status during sleep at a high frequency of 25 Hz, enabling health management and highly accurate health assessment during sleep. This is an extremely advantageous configuration for a wearable device 101 that is intended to acquire various other information in conjunction with sleep.
[0121] (7) The model adjustment module 416 of the adjustment management server 103 for the menstrual cycle state estimation model M can adjust the menstrual cycle state estimation model M in a timely manner. The adjustment of the menstrual cycle state estimation model M may be one or more of the following: additional learning, retraining, fine tuning, transfer learning, etc.
[0122] The model tuning module 416 can, for example, retrain the menstrual cycle state estimation model M using all or part of past data. Alternatively, the model tuning module 416 can perform additional training on the menstrual cycle state estimation model M using methods such as the Baum-Welch algorithm, parameter saving and recalculation, online learning incorporating forgetting, and additional training with model reconstruction.
[0123] The above describes specific examples of the present technology, but these are merely illustrative and do not limit the scope of the claims. The technology described in the claims includes various modifications and changes to the specific examples described above. For example, the above-described examples are described in detail to make the present technology easy to understand and are not necessarily limited to those having all the described configurations. Furthermore, it is possible to replace parts of the configuration of one embodiment with other configurations, and it is also possible to add other configurations to the configuration of one embodiment. In addition, it is possible to add, delete, or replace parts of the configuration of each embodiment with other configurations.
[0124] The health management module 412 may be configured to manage information related to the user's health in addition to the health management information related to the prediction of the menstrual cycle state described above. Specifically, the health management module 412 may, for example, work in conjunction with the health management module 312 of the user terminal 102 to acquire biometric information obtained from the user terminal 102 by the wearable device 101. The health management module 412 also analyzes the acquired biometric information using volume plethysmography and calculates at least one piece of health management information, such as heart rate, heart rate variability, blood oxygen saturation, blood pressure, and blood glucose level. The health management module 412 may also be configured to calculate the user's posture and displacement, activity level, calories burned, steps taken, behavioral discrimination, body temperature (skin temperature and core temperature), skin moisture content and sweating, blood glucose level, electrocardiogram, heart rate, heart rate variability, respiratory rate, and other health management information based on the acquired biometric information. The health management information may include management indicators for disease prevention, defined as necessary, such as a vascular health index, activity level, stress level, depression level, and lifestyle-related disease risk. Furthermore, the health management module 412 may use data obtained from various biological signals such as displacement, body temperature, heart rate, heart rate variability, and respiratory rate to perform analysis, evaluation, etc., on any health item. The health management module 412 outputs (stores) the calculated health management information to, for example, the health management information 420 in the auxiliary storage device 402 for management.
[0125] Furthermore, the health management module 412, for example, works in conjunction with the health management module 312 of the user terminal 102 to output (display) the calculated health management information on the display of the user terminal 102 (an example of an output device 305).
[0126] The health management module 412 may also be configured to notify the health management module if it finds any of the specified characteristics in the calculated health management information. The notification method is not particularly limited and may be, for example, displayed on the display of the user terminal 102, or sent via email or message to a designated recipient.
[0127] This technology provides a program for executing each step of the ovulation date estimation method in the wearable device 101, the user terminal 102, and the management server 103. This program may be stored, for example, in the main memory of the wearable device 101, the user terminal 102, and the management server 103. By executing this program, the processors of the wearable device 101, the user terminal 102, and the management server 103 can use the services of the ovulation date estimation system 100.
[0128] In this embodiment, the above preprocessing is performed by the preprocessing module 214 of the wearable device 101 and the preprocessing module 414 of the management server 103. However, the processing performed by the preprocessing module 214 of the wearable device 101 may also be performed by the preprocessing module of the user terminal 102 or the management server 103. Similarly, the main entity performing the processing in the above embodiment is not limited to that shown in the embodiment, and may be performed by any of the wearable device 101, the user terminal 102, or the management server 103.
[0129] Furthermore, each of the above configurations, functions, processing units, processing means, etc., may be implemented in hardware, in whole or in part, for example, by designing them as integrated circuits. Alternatively, each of the above configurations, functions, etc., may be implemented in software by having the processor interpret and execute programs that realize each function. Information such as programs, tables, and files that realize each function can be stored in memory, a recording device such as a hard disk or SSD (Solid State Drive), or a recording medium such as an IC card, SD card, or DVD (which may be a non-temporary computer-readable medium).
[0130] Furthermore, in the diagrams showing the hardware configuration, control lines and information lines are shown only if deemed necessary for explanation, and not all control lines and information lines are necessarily shown in the actual product. In reality, it can be assumed that almost all components are interconnected. Note that the above-described embodiment discloses at least the configuration described in the claims. The claims include at least the following configurations.
[0131] 100... Ovulation day estimation system, 101... Wearable device, 102... User terminal, 211... Execution module, 212... Health management module, 213... Health information evaluation module, 214... Preprocessing module, 311... Execution module, 312... Health management module, 313... Health information evaluation module, 411... Execution module, 412... Health management module, 413... Health information evaluation module, 414... Preprocessing module, 415... Postprocessing module, 416... Model adjustment module
Claims
1. An ovulation day estimation system comprising: a biological information acquisition unit that acquires temperature information of a living organism over time; a menstrual information acquisition unit that acquires menstrual information which is information relating to the menstrual state of a living organism; a representative temperature acquisition unit that acquires representative temperature information based on the temperature information over time; and an ovulation day estimation unit that estimates the ovulation day based on the representative temperature information and the menstrual information.
2. The ovulation day estimation system according to claim 1, wherein the biological information acquisition unit acquires temperature sensor information at a first time interval, acquires first representative temperature information at a second time interval longer than the first time interval, and the representative temperature acquisition unit acquires representative temperature information based on the first representative temperature information.
3. The ovulation day estimation system according to claim 1, wherein the biological information acquisition unit acquires activity level information corresponding to the activity level of the biological body, evaluates whether the biological body is in a sleeping state or an awake state based on the activity level information, and acquires temperature information when the biological body is evaluated to be in a sleeping state.
4. The ovulation day estimation system according to claim 1, wherein the biological information acquisition unit acquires activity level information corresponding to the activity level of the organism in association with the temperature information, the representative temperature acquisition unit evaluates whether the organism is in a sleep state or an awakened state based on the activity level information, and acquires representative temperature information based on the temperature information for the period during which the organism was evaluated to be in a sleep state.
5. The ovulation day estimation system according to claim 4, wherein the representative temperature acquisition unit acquires the representative temperature information based on the temperature information when the time for which the living organism is evaluated to be in a sleep state is longer than a predetermined time.
6. The ovulation date estimation system according to claim 1, wherein the menstrual information acquisition unit acquires the start date of menstruation and the end date of menstruation, and acquires information regarding the menstrual cycle based on the start date of menstruation and the start date of menstruation of the previous cycle.
7. The ovulation day estimation system according to claim 1, wherein the ovulation day estimation unit is configured to estimate the ovulation day based on the representative temperature information of one or more days, using a machine learning model that has been trained to take representative temperature information of the body for one or more days as input and output the menstrual cycle state for each day.
8. The ovulation day estimation system according to claim 7, wherein the ovulation day estimation unit uses a classification model as the machine learning model, which is trained to classify the menstrual cycle state of each day into one of a predetermined number of menstrual cycle states based on the input, and the number of menstrual cycle states includes an ovulation day, and the day corresponding to the representative temperature information classified as an ovulation day is estimated to be an ovulation day.
9. The machine learning model is trained to classify the menstrual cycle state of each day into one of a predetermined number of menstrual cycle states based on the input, wherein the number of menstrual cycle states includes at least four states, and the four states include the ovulation day, as described in claim 8.
10. The machine learning model is trained to classify the menstrual cycle state of each day into one of a predetermined number of menstrual cycle states based on the input, wherein the number of menstrual cycle states includes 10 states, starting from a first state defined as the first day of a menstrual cycle and ending with a tenth state defined as the day before the start of the next menstrual cycle, and the 10 states include the ovulation day, as described in claim 8.
11. The ovulation date estimation system according to claim 7, wherein the machine learning model is trained on a hidden Markov model.
12. The ovulation date estimation system according to claim 1, further comprising a menstrual cycle state acquisition unit that acquires at least one selected from the group consisting of the next estimated ovulation date, the next estimated menstrual period date, and the fertile day, based on the ovulation date estimation result by the ovulation date estimation unit.
13. The ovulation day estimation system according to claim 1, wherein the biological information acquisition unit is provided in a wearable ring attached to the finger of the living body, and the representative temperature acquisition unit is provided in a computer other than the wearable ring.
14. A method for estimating the ovulation day, comprising: obtaining temperature information of a living organism over time; obtaining representative temperature information based on the temperature information over time; and estimating the ovulation day based on the representative temperature information.
15. A program for causing a computer to perform each step of the ovulation date estimation method described in claim 14.
