Bedtime management system

Abstract

If a parent falls asleep while putting a child to sleep, this system will wake only the parent without waking the child. [Solution] The sleep-inducing management system 10 comprises a management device 20, a user terminal 30, a sleep detection sensor 60 attached to the bed 40, and a speaker 55. Based on the input of a start command through the user terminal 30, the management device 20 acquires detection information detected by the sleep detection sensor 60. Based on the detection information, the management device 20 determines the sleep state of the parent putting the child to sleep and the sleep state of the child being put to sleep. If the child being put to sleep is in a deep sleep state and the parent is awake or in a light sleep state, the management device 20 activates the speaker 55.

Description

Technical Field

[0001] The present invention relates to a bedtime management system used for putting a child to sleep.

Background Art

[0002] Patent Document 1 discloses a bedtime management system used when a parent puts a child to sleep. This bedtime management system includes a server, a sensor, and a display device. The server determines the sleep state of the child to be put to sleep and the sleep state of the parent who is putting the child to sleep based on the sensor detection value. When the server determines that the child's sleep state is a light sleep state, it causes the display device to display a message indicating that the child may wake up.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] There are cases where the parent who sleeps with the child to be put to sleep falls asleep. If there is still housework or the like remaining, the parent sets an alarm before putting the child to sleep to deal with the situation where they fall asleep. In some cases, this alarm may cause the child who has been put to sleep to wake up. Or, the parent may avoid setting an alarm because they are afraid that the child will wake up and may sleep until morning.

[0005] The present invention has been made in view of the above-described circumstances, and an object thereof is to provide a means for waking up a person who sleeps with the person to be put to sleep without waking up the person to be put to sleep.

Means for Solving the Problems

[0006] (1) The sleep management system according to the present invention comprises a controller, a memory, a sleep detection sensor, and a first wake-up device. The controller performs a sleep state determination process to determine the sleep state of the co-sleeper and the co-sleeper based on the detection information from the sleep detection sensor. The sleep states include an awake state, a light sleep state, and a deep sleep state. Based on the fact that the co-sleeper's sleep state is a deep sleep state and the co-sleeper's sleep state is a light sleep state, the controller performs a first wake-up process to activate the first wake-up device.

[0007] The first wake-up device is activated when the child sleeping next to the parent is in a deep sleep state and the parent sleeping next to the child is in a light sleep state. Therefore, the sleep management system according to the present invention can wake up the parent who has fallen asleep with the child sleeping next to the child without waking the child.

[0008] (2) The sleep management system described in (1) above may further include a blower, which is a second wake-up device. The first wake-up device is a speaker. The controller further performs a second wake-up process to drive the second wake-up device based on the fact that the sleep state of the person being co-slept with is the light sleep state and the sleep state of the co-sleeper is the awake state.

[0009] The airflow generated by the fan allows the awake co-sleep partner to recognize that the person being co-slept with is in a light sleep state. The co-sleep partner then moves away from the person being co-slept with to avoid waking them.

[0010] (3) In the sleep management system described in (1) or (2) above, the sleep detection sensor may be a sensor capable of detecting the timing of falling asleep, which is the timing when the co-sleeper and the person being co-slept with transition from the awake state to the light sleep state. The memory stores first sleep cycle information corresponding to the age of the co-sleeper and second sleep cycle information corresponding to the age of the person being co-slept with. The sleep state determination process includes a first process of acquiring the timing of falling asleep based on the detection information of the sleep detection sensor, and a second process of determining the sleep state of the co-sleeper and the sleep state of the person being co-slept with based on the elapsed time from the timing of falling asleep, the first sleep cycle information, and the second sleep cycle information.

[0011] The sleep cycles and the timing of light and deep sleep states differ between the parent who is co-sleeping and the child who is being put to sleep. Based on first sleep cycle information indicating the parent's sleep cycle and the aforementioned timings, the parent's sleep state is determined. Based on second sleep cycle information indicating the child's sleep cycle and the aforementioned timings, the child's sleep state is determined. Therefore, the sleep management system according to the present invention can determine the sleep states of the co-sleeper and the child by estimation without directly detecting their sleep states.

[0012] (4) In the sleep management system described in (3) above, the second sleep cycle information may include first information corresponding to the person sleeping with the other person who is aged 0 or older but less than 2 years old, and second information corresponding to the person sleeping with the other person who is aged 2 or older but less than 5 years old.

[0013] Generally, the sleep cycle of infants under 2 years old is 50 minutes, the sleep cycle of children aged 2 to under 5 years is 70 minutes, and the sleep cycle of people aged 5 years and older is 90 minutes. The sleep state of a child can be appropriately determined according to the age of the child being put to sleep.

[0014] (5) The bedtime management system described in any of (1) to (4) above may further include an input interface. The controller further performs an acquisition process through the input interface to acquire planned chore information indicating the chores that the person sleeping with the baby is to perform after putting the baby to sleep, and a wake-up determination process that determines whether or not to perform the first wake-up process based on the planned chore information.

[0015] The controller determines whether or not to wake the co-sleeper who is putting the baby to sleep, based on the planned household chore information. Therefore, it can appropriately wake the parent who is putting the baby to sleep, depending on whether or not they have any household chores planned to be done after putting the baby to sleep, as well as the amount and type of chores they will be doing.

[0016] (6) The sleep management system described in (2) above may include a bed on which the co-sleeper and the co-sleeper sleep, and which is equipped with the sleep detection sensor, the first wake-up device, and the second wake-up device.

[0017] The sleep detection sensor, the first wake-up device, and the second wake-up device are attached to the bed in which the person being co-slept is put to sleep. [Effects of the Invention]

[0018] The sleep management system according to the present invention can wake up a parent who has fallen asleep with a child who is sleeping next to them, without waking the child. [Brief explanation of the drawing]

[0019] [Figure 1] Figure 1 is a configuration diagram and functional block diagram of the sleep-inducing management system 10 according to an embodiment. [Figure 2] Figure 2 is a perspective view of a bed 40 equipped with a blower 50, a speaker 55, and a sleep detection sensor 60. [Figure 3]FIG. 3(A) is a diagram showing a user management database, FIG. 3(B) is a diagram showing a sleep determination table, FIG. 3(C) is a diagram showing a wake-up determination table, FIG. 3(D) is a diagram showing a first wake-up means determination table, FIG. 3(E) is a diagram showing a second wake-up means determination table, and FIG. 3(F) is a diagram showing an input information management database. [Figure 4] FIG. 4 is a flowchart showing a part of a registration process and a wake-up management process. [Figure 5] FIG. 5 is a flowchart showing the remaining part of the wake-up management process. [Figure 6] FIG. 6(A) is a diagram showing a registration screen, and FIG. 6(B) is a diagram showing a start screen. [Figure 7] FIG. 7(A) is a diagram showing a start screen, and FIG. 7(B) is a diagram showing a first notification screen. [Figure 8] FIG. 8(A) is a diagram showing a second notification screen, and FIG. 8(B) is a diagram showing an end notification screen.

Mode for Carrying Out the Invention

[0020] Hereinafter, embodiments of the present invention will be described. It should be noted that the embodiments described below are merely examples of the present invention, and it is needless to say that the embodiments of the present invention can be appropriately changed without departing from the gist of the present invention. In addition, the order of execution of each process (each step) shown in the flowcharts shown in FIGS. 4 and 5 may be appropriately changed, some may be omitted, other processes may be added, or they may be replaced with equivalent other processes, without departing from the gist of the present invention.

[0021] [Outline of the Bedtime Management System 10] The bedtime management system 10 shown in FIG. 1 described in this embodiment is a system that provides a service for waking up a parent when the parent who is putting a child to bed falls asleep with the child.

[0022] The bedtime management system 10 provides services using, for example, a management device attached to a residence. Alternatively, the bedtime management system 10 provides services using a personal computer or communication terminal owned by the resident. The provider of the service provides the service to the resident by implementing the management program 26 and application program 36 related to the bedtime management system 10 on the management device, personal computer, or communication terminal.

[0023] The service provider is, for example, a company that built a house. The service provider offers a service using the bedtime management system 10 as one of the various services it provides to the homeowner and their family. These various services include, for example, services related to home maintenance and services that support comfortable living in the home. The bedtime management system 10 is operated in conjunction with other systems that provide other services. For example, the bedtime management system 10 provides data used by other systems to those other systems. Alternatively, the bedtime management system 10 acquires data necessary for operation from other systems. In other words, the bedtime management system 10 also functions as a data collection system for other systems.

[0024] However, the bedtime management system 10 may be operated as a standalone system, or it may be provided to residents by a business other than the company that built the house.

[0025] [Configuration of the 10-part sleep training management system] As shown in Figure 1, the sleep management system 10 comprises a management device 20, a user terminal 30, a bed 40, a blower 50, a speaker 55, and a sleep detection sensor 60.

[0026] The bed 40 shown in Figure 2 is installed, for example, in a child's room or bedroom in a house. The bed 40 comprises a baseboard 41, a headboard 42, and a mattress 43.

[0027] The headboard 42 has an air vent 44 and an alarm opening 45. The air vent 44 and the alarm opening 45 are located on the right or left side of the bed 40 in the left-right direction 9. In the example shown in Figure 2, the air vent 44 and the alarm opening 45 are located on the right side of the bed 40. The alarm opening 45 is closed off by, for example, a sound-blocking mesh sheet or a grid. It is recommended that the parent putting the child to sleep lies on the right side of the bed 40 where the air vent 44 and the alarm opening 45 are located, and the child being put to sleep lies on the left side.

[0028] The blower 50 is positioned at the front of the headboard 42 in the front-to-back direction 8 and facing the air outlet 44. The air generated by the blower 50 is directed through the air outlet 44 towards the user lying on the mattress 43. The blower 50 is an example of a second wake-up device.

[0029] As shown in Figure 1, the blower 50 includes a fan 51, a louver 52, a drive unit 53, and a control unit 54. The drive unit 53 is connected to a commercial power supply (not shown) attached to the house. The control unit 54 is connected to a local area network 11 (hereinafter also referred to as LAN 11) attached to the house. LAN 11 is a so-called wired LAN or wireless LAN. LAN 11 includes a switching hub or router (not shown). The control unit 54 receives control signals output by the management device 20 via LAN 11. Based on the rotational speed of the fan 51 and the angle of the louver 52 indicated by the received control signals, the control unit 54 drives the fan 51 and louver 52, or stops the fan 51. In other words, the management device 20 can adjust the direction and speed of the wind generated by the blower 50.

[0030] As shown in Figure 2, the speaker 55 is positioned at the front of the headboard 42 in the front-to-back direction 8 and facing the alarm opening 45. The speaker 55 is an example of a first wake-up device.

[0031] As shown in Figure 1, speaker 55 is connected to LAN 11. Speaker 55 receives audio data output by management device 20 via LAN 11. Speaker 55 outputs audio such as alarm sounds indicated by the received audio data.

[0032] [Sleep detection sensor 60] The sleep detection sensor 60 shown in Figure 1 is a so-called body movement sensor. For example, a commercially available body movement sensor can be used as the sleep detection sensor 60. The sleep detection sensor 60 includes a control unit 61 and a pressure-sensitive sheet 62. The pressure-sensitive sheet 62 has multiple pressure-sensing elements, such as piezoelectric elements. The control unit 61 outputs detection information that associates the pressure detected by the pressure-sensitive sheet 62 with the location where the pressure was detected.

[0033] As shown in Figure 2, the pressure-sensitive sheet 62 of the sleep detection sensor 60 is positioned between the base plate 41 and the mattress 43. The pressure-sensitive sheet 62 covers the entire underside of the mattress 43. In other words, the sleep detection sensor 60 can detect the child and the parent regardless of where the child and parent are lying on the mattress 43.

[0034] As shown in Figure 1, the sleep detection sensor 60 is connected to the LAN 11. The detection information output by the sleep detection sensor 60 is periodically input to the management device 20 via the LAN 11 at a predetermined sampling period.

[0035] [User terminal 30] User terminal 30 is a communication device owned by the user. User terminal 30 is, for example, a smartphone (registered trademark) or a tablet (registered trademark). In Figure 1, only one user terminal 30 is shown. However, there may be two or more user terminals 30, including a user terminal 30 owned by the father and a user terminal 30 owned by the mother. The user of the sleep management system 10 may be only the mother, only the father, or both the mother and the father.

[0036] The user terminal 30 comprises a central processing unit (CPU) 31, terminal memory 32, a communication interface 33, a touch panel 34, and a communication bus (not shown). The communication bus connects the CPU 31 to the terminal memory 32, the communication interface 33, and the touch panel 34 in a communication manner.

[0037] The terminal memory 32 is composed of, for example, ROM, RAM, and EEPROM, and other memory elements. The terminal memory 32 may be composed of any type of memory element.

[0038] The terminal memory 32 stores the operating system OS 35, the downloaded application program 36 (hereinafter also referred to as app 36), and the identification ID. App 36 is provided to the user by the service provider. The user downloads app 36 to the user terminal 30, for example, from a website. The identification ID is identification information that identifies the user. The identification ID is downloaded together with app 36 and stored in the terminal memory 32. App 36, together with the management program 26 described later, executes the processes (flows) shown in Figures 4 and 5.

[0039] The communication interface 33 is, for example, a short-range wireless communication module such as Wi-Fi. The user terminal 30 communicates with the management device 20 via the LAN 11.

[0040] The touch panel 34 has a display and a transparent, film-like touch sensor superimposed on the display. The touch panel 34 is an example of an input interface. The user terminal 30 may also have a microphone that accepts voice input as an input interface.

[0041] [Management device 20] The management device 20 is, for example, a management terminal that manages air conditioning systems or entrance intercom systems installed in a house. Alternatively, the management device 20 is a computer, such as a personal computer, owned by the resident.

[0042] The management device 20 comprises a central processing unit (CPU) 21, a management memory 22, a communication interface 23, a clock module 24, and a communication bus (not shown). The communication bus connects the CPU 21 to the management memory 22, the communication interface 23, and the clock module 24 in a communicative manner. The CPU 21 is an example of a controller. Also, CPU 21 and CPU 31 are examples of controllers. The management memory 22 is an example of memory. Also, the management memory 22 and terminal memory 32 are examples of memory.

[0043] The communication interface 23 is connected to the LAN 11 by a communication cable or short-range wireless communication. The management device 20 communicates with the user terminal 30, the blower 50, the speaker 55, and the sleep detection sensor 60 through the communication interface 23 and the LAN 11.

[0044] The clock module 24 outputs date and time information.

[0045] The management memory 22 is composed of, for example, ROM, RAM, EEPROM, hard disk drives, solid-state drives, USB memory, and other memory elements and storage devices.

[0046] The management memory 22 stores the operating system OS 25, management programs 26, various screen formats, various thresholds, a management database, and various tables.

[0047] A screen format is format data for generating screen data. A screen format is, for example, a class or function that generates screen data as an object by receiving information. The generated screen data is, for example, HTML data containing JavaScript. A screen format can also be the screen data itself.

[0048] The management program 26, together with the application 36, executes the processes (flows) shown in Figures 4 and 5 based on the information registered in the management database and various tables.

[0049] The management database includes the user management database shown in Figure 3(A) and the input information management database shown in Figure 3(F). Various tables include the sleep determination table shown in Figure 3(B), the wake-up determination table shown in Figure 3(C), the first wake-up means determination table shown in Figure 3(D), and the second wake-up means determination table shown in Figure 3(E). The management database and tables have data that represents the tables and control programs that register information to the tables and read information from the tables. The management program 26 instructs the control program to read and register information through the OS 25. The control program may be part of the management program 26.

[0050] [User Management Database] The user management database shown in Figure 3(A) is a database that manages information about the user and their family.

[0051] The user management database has multiple columns named "Identification ID," "Name," "Gender," "Date of Birth," "Age," "Co-sleeper Flag," "Co-sleeper Flag," "Applicable Table," and "Weight," as well as records (rows).

[0052] The field in the column named "Identification ID" is where the identification ID that individually identifies each individual belonging to the family is registered. Each record, i.e., each individual, is individually identified by their identification ID. The identification ID is registered in the user management database by the aforementioned service provider.

[0053] The field in the column named "Name" will register the individual's name. The field in the column named "Gender" will register the individual's gender. The field in the column named "Date of Birth" will register the individual's date of birth. The field in the column named "Age" will register the individual's age. The name, gender, and date of birth are registered in the user management database by the service provider mentioned above. The age is updated daily by management program 26 based on the date of birth and the current date and time.

[0054] The column named "Sleeping Together Flag" is assigned either "1" to indicate a child who sleeps with their parents, or "0" to indicate a child who does not sleep with their parents. A sleeping together child is a child who is put to sleep by their parents. In the example shown in Figure 3(A), the sleeping together flag of "0" is registered for "Jiro Yamada," who is currently 8 years old. The sleeping together flag of "1" is also registered for "Kazumi Yamada," who is currently 3 years old, and "Saburo Yamada," who is currently 1 year old. The parents, "Taro Yamada" and "Hanako Yamada," are pre-registered with "-" to indicate that they do not sleep with their parents. The "Sleeping Together Flag" is registered by the management program 26 based on user input.

[0055] The column named "Sleeping Companion Flag" registers either a "1" indicating that the user is a sleeping companion, or a "0" indicating that the user is not a sleeping companion. A sleeping companion is a user who is also a parent who puts a child to sleep. For the children "Jiro Yamada," "Kazumi Yamada," and "Saburo Yamada," a "-" is pre-registered to indicate that they are not sleeping companions. The "Sleeping Companion Flag" is registered by the management program 26 based on user input.

[0056] In the example shown in Figure 3(A), the mother, "Yamada Hanako," has a co-sleeping flag of "1" registered, indicating that she is a co-sleeping partner. The father, "Yamada Taro," has a co-sleeping flag of "0" registered, indicating that he is not a co-sleeping partner.

[0057] The fields in the column named "Application Table" register one of three application types for sleep cycle information: "A", "B", or "C". "A" represents sleep cycle information for people aged 5 and over. "B" represents sleep cycle information for children aged 2 to under 5 years. "C" represents sleep cycle information for infants aged 0 to under 2 years. Sleep cycle information includes the sleep cycle, the start and end times of the first light sleep state, the start and end times of the deep sleep state, and the start and end times of the second light sleep state.

[0058] Sleep cycle information differs for each age group, designated as "A," "B," and "C" above. "A" is registered for "Yamada Taro," "Yamada Hanako," and "Yamada Jiro," who are in the age group of 5 years and older. "B" is registered for "Yamada Kazumi," who is in the age group of 2 years and older but under 5 years old. "C" is registered for "Yamada Saburo," who is in the age group of 0 years and older but under 2 years old. "A," "B," and "C," which indicate the application type of sleep cycle information, are registered by the management program 26 based on the "age" registered in the user management database.

[0059] Sleep cycle information for each type, "A," "B," and "C," is registered in the sleep assessment table described later.

[0060] The field in the column named "Weight" is used to register weight. The registered weight may be the weight measured during a health checkup, or it may be the national average weight for that age group. The registered weight is used to identify the positions of the parent and child lying in bed. Further details will be provided later.

[0061] [Sleep Assessment Table] The sleep determination table shown in Figure 3(B) is a table that registers sleep cycle information for each type, "A," "B," and "C." The sleep determination table is used to determine sleep states. Sleep states include wakefulness, the first light sleep state, deep sleep, and the second light sleep state. The first and second light sleep states are examples of light sleep states.

[0062] The sleep assessment table has multiple columns labeled with the names "Type," "Sleep Cycle (minutes)," "First Light Sleep," "Deep Sleep," and "Second Light Sleep," as well as records (rows).

[0063] The fields in the column named "Type" are registered in the order of "A", "B", and "C" as described above. The fields in the column named "Sleep Cycle (minutes)" are registered in the order of "90", "70", and "50".

[0064] The column named "First Light Sleep" has two sub-columns named "Start" and "End". The field in the sub-column named "Start" is set to "0", indicating the moment immediately after falling asleep. The field in the sub-column named "End" is set to "25", "16", and "6", respectively, indicating the timing of the end of the first light sleep state.

[0065] The column named "Deep Sleep" has two sub-columns named "Start" and "End". The fields in the sub-column named "Start" are registered in the order of "25", "16", and "6", indicating the timing when the deep sleep state begins. The fields in the sub-column named "End" are registered in the order of "43", "37", and "21", indicating the timing when the deep sleep state ends.

[0066] The column named "Second Light Sleep" has two sub-columns named "Start" and "End". The fields in the sub-column named "Start" are registered in order as "43", "37", and "21", indicating the timing when the second light sleep state begins. The fields in the sub-column named "End" are registered in order as "90", "70", and "50", indicating the timing when the second light sleep state ends.

[0067] The sleep determination table is a fixed table that does not change for each user. The sleep determination table is pre-stored in the management memory 22 by the service provider mentioned above.

[0068] As the sleep assessment table shows, the sleep cycle for people aged 5 and over, indicated by "A," is 90 minutes. In this age group, the period from immediately after falling asleep to 25 minutes later is the first light sleep state, from 25 minutes to 43 minutes later is the deep sleep state, and from 43 minutes to 90 minutes later is the second light sleep state.

[0069] The sleep cycle for toddlers, who are between 2 and 5 years old (indicated by "B"), is 70 minutes. In toddlers, the first light sleep state occurs from immediately after falling asleep until 16 minutes later, the deep sleep state occurs from 16 to 37 minutes after falling asleep, and the second light sleep state occurs from 37 to 70 minutes after falling asleep.

[0070] The sleep cycle for infants and toddlers, who are between 0 and 2 years old (indicated by "C"), is 50 minutes. In infants and toddlers, the first light sleep state occurs from immediately after falling asleep until 6 minutes later, the deep sleep state occurs from 6 minutes to 21 minutes later, and the second light sleep state occurs from 21 minutes to 50 minutes later.

[0071] For example, the sleep state of "Kazumi Yamada" 160 minutes after falling asleep is determined as follows. Note that the timing of falling asleep refers to the moment when a person transitions from an awakened state to the first light sleep state.

[0072] The sleep cycle information application type "B" for "Kazumi Yamada" is retrieved from the user management database. A sleep cycle of "70" associated with "B" is retrieved from the sleep judgment table. "70" is repeatedly subtracted from the elapsed time "160" until a value smaller than the sleep cycle of "70" is obtained. Specifically, "70" is subtracted twice from "160" to calculate "20". "20" is between "16" and "37", which are the start and end times of each sleep state associated with "B" in the sleep judgment table. "Deep sleep", associated with "16" and "37", is determined to be the sleep state of "Kazumi Yamada" 160 minutes after falling asleep.

[0073] In the sleep assessment table, sleep cycle information associated with type "A" is an example of first sleep cycle information. In the sleep assessment table, sleep cycle information associated with type "B" is an example of second sleep cycle information and second information. In the sleep assessment table, sleep cycle information associated with type "C" is an example of second sleep cycle information and first information.

[0074] [Wake-up determination table] The wake-up determination table shown in Figure 3(C) is a table used to determine whether or not to wake up a co-sleeper who has fallen asleep with a child, based on the type of household chores that will be performed after putting the child to sleep.

[0075] The wake-up determination table has multiple columns named "Household Chore ID," "Household Chore Name," "Wake-up Flag," and "Time Required (minutes)," as well as records (rows).

[0076] The field in the column named "Household Chore ID" is where the Household Chore ID, which identifies each household chore, is registered. Each record is individually identified by its Household Chore ID.

[0077] The field in the column named "Household Chore Name" will contain the name of the household chore. In the example shown in Figure 3(C), the household chore names "Washing Dishes," "Laundry," "Ironing," "Cleaning," "Studying," "Work," "Child-related," and "Necessary Runs" are registered in the field of the column named "Household Chore Name."

[0078] Common household chore names are pre-registered in the wake-up determination table by the service provider. Users may also enter household chore names other than those pre-registered. The management program 26 assigns a new chore ID to the entered chore name and registers it in the wake-up determination table. In other words, the wake-up determination table may be customized for each user.

[0079] The field in the column named "Wake-up Flag" registers a wake-up flag of "1" or "0". A wake-up flag of "1" indicates that the co-sleeper should be woken if they have fallen asleep with the child. A wake-up flag of "0" indicates that the co-sleeper should not be woken. In the example shown in Figure 3(C), "Work," "Child-related," and "Necessary Chores" are associated with a wake-up flag of "1". That is, if "Work," "Child-related," or "Necessary Chores" is scheduled to be performed after putting the child to sleep, the bedtime management system 10 decides to wake the co-sleeper based on a wake-up flag of "1". This schedule is entered into the bedtime management system 10 by the user. Wake-up flags associated with common household chore names are pre-registered by the service provider. Wake-up flags corresponding to household chore names entered by the user are registered by the user.

[0080] The field in the column named "Estimated Time (minutes)" registers the time required to perform household chores. The time required to perform a chore is registered only for chores associated with a wake-up flag of "0". In the example shown in Figure 3(C), "20" is registered for "washing dishes", "60" for "laundry", "20" for "ironing", "30" for "cleaning", and "60" for "studying". Note that the estimated time may also be registered for chores associated with a wake-up flag of "1". Estimated time associated with common chore names is pre-registered by the service provider. Estimated time corresponding to chore names entered by the user is registered by the user. Estimated time pre-registered by the service provider may be changed by the user.

[0081] The "required time," which is the time taken for household chores, is used to determine whether or not to wake the co-sleeper if they have fallen asleep with the child. For example, the management program 26 calculates the total required time for the household chores that the co-sleeper is scheduled to perform after putting the child to sleep. If the total required time is greater than or equal to a threshold time, the management program 26 decides to wake the co-sleeper; if the total required time is less than the threshold time, it decides not to wake the co-sleeper. In other words, if there are many chores remaining, the management program 26 decides to wake the co-sleeper; if there are few chores remaining, it decides not to wake the co-sleeper. Whether or not there are many chores remaining is determined by the threshold time mentioned above. This threshold time is stored in advance in the management memory 22. The co-sleeper's planned household chores are entered into the bedtime management system 10 by the user.

[0082] [Table for determining the first means of waking up] The first wake-up method determination table shown in Figure 3(D) is a table that associates the sleep state of the child being put to sleep (the person being co-slept with), the sleep state of the co-sleeper, and the wake-up method number. Furthermore, the first wake-up method determination table is the table for the case where there is only one child being put to sleep.

[0083] The first wake-up method determination table has multiple columns named "sleep state information" and "wake-up method number," and records (rows).

[0084] The column named "Sleep Status Information" has two sub-columns named "Sleeping Companion (Child)" and "Sleeping Companion (Parent)".

[0085] The sub-column field named "Sleeping Companion (Child)" registers either sleep state information of "1" indicating a light sleep state, or sleep state information of "2" indicating a deep sleep state. The sub-column field named "Sleeping Companion (Parent)" registers either sleep state information of "0" indicating an awake state, or the aforementioned sleep state information of "1".

[0086] The sub-column field labeled "Wake-up Method Number" is registered with a wake-up method number of "1", "2", or "0". A wake-up method number of "1" indicates that the blower 50 will be driven. A wake-up method number of "2" indicates that the speaker 55 will be driven. A wake-up method number of "0" indicates that neither the blower 50 nor the speaker 55 will be driven.

[0087] In the first wake-up method determination table, the sleep state information of the child being put to sleep ("1"), the sleep state information of the co-sleeper ("0"), and the wake-up method number ("1") are associated. That is, if the child being put to sleep is in a light sleep and the co-sleeper is awake, the fan 50 is activated. The co-sleeper, who is blown by the air generated by the fan 50, realizes that the child being put to sleep is in a light sleep. The co-sleeper quietly moves away from the bed 40 so as not to wake the lightly sleeping child. Alternatively, the co-sleeper waits until the child's sleep deepens before moving away from the bed 40.

[0088] In the first wake-up method determination table, the sleep state information of the child being put to sleep ("2"), the sleep state information of the co-sleeper ("0" and "1"), and the wake-up method number for "2" are associated. In other words, if the child being put to sleep is in a deep sleep and the co-sleeper is awake or in a light sleep state, an alarm will sound. The awake co-sleeper will recognize that the child is in a deep sleep from the alarm sound. The co-sleeper in a light sleep state will be woken by the alarm sound. The child, being in a deep sleep state, will not be woken by the alarm sound.

[0089] In the first wake-up method determination table, "Other," which indicates a correspondence other than the aforementioned correspondence of sleep state information for the child and co-sleeper, is associated with the wake-up method number "0". In other words, in correspondences other than the aforementioned correspondence of sleep state information for the child and co-sleeper, neither the fan 50 nor the speaker 55 is driven. Specifically, if the co-sleeper is in a deep sleep state, and the child being put to sleep is awake, neither the fan 50 nor the speaker 55 is driven.

[0090] [Second method of waking up determination table] The second wake-up method determination table shown in Figure 3(E) is a table used when putting two children to sleep at the same time. The second wake-up method determination table associates sleep state information indicating the sleep state of the first person being co-slept with, sleep state information indicating the sleep state of the second person being co-slept with, sleep state information indicating the sleep state of the co-sleeper, and a wake-up method number.

[0091] The second wake-up method determination table has multiple columns named "sleep state information" and "wake-up method number," as well as records (rows).

[0092] The column named "Sleep State Information" has three sub-columns named "First Co-sleeping Person (Child)", "Second Co-sleeping Person (Child)", and "Co-sleeping Person (Parent)". The fields in these sub-columns register the sleep state information of "0", "1", or "2" as described above. The field in the column named "Wake-up Method Number" registers the wake-up method number of "0", "1", or "2" as described above.

[0093] In the second wake-up method determination table, the sleep state information of the first child being put to sleep, the first co-sleeper, is associated with "1", the sleep state information of the second child being put to sleep, the second co-sleeper, the second co-sleeper, the sleep state information of the co-sleeper, the first co-sleeper, and the wake-up method number of "1". In other words, if both children being put to sleep are in a light sleep state and the co-sleeper is awake, the blower 50 is activated.

[0094] Furthermore, in the second wake-up method determination table, the sleep state information of the first person being co-slept with, "1", the sleep state information of the second person being co-slept with, "2", the sleep state information of the co-sleeper, "0", and the wake-up method number of "1" are associated. In other words, the sleep state information of the first person being co-slept with, "2", the sleep state information of the second person being co-slept with, "1", the sleep state information of the co-sleeper, "0", and the wake-up method number of "1" are associated.

[0095] Furthermore, in the second wake-up method determination table, the sleep state information of the first person being co-slept with, "2", the sleep state information of the second person being co-slept with, "2", the sleep state information of the co-sleeper, "0", and the wake-up method number of "2" are associated. In other words, if both children being put to sleep are in a deep sleep state and the parent is awake, an alarm will sound.

[0096] Furthermore, in the second wake-up method determination table, the sleep state information of the first person being co-slept with ("2"), the sleep state information of the second person being co-slept with ("2"), the sleep state information of the co-sleeper ("1"), and the wake-up method number of "2" are associated. In other words, if both children being put to sleep are in a deep sleep state and the parent is in a light sleep state, an alarm will sound.

[0097] The first wake-up method determination table and the second wake-up method determination table are fixed tables that are not changed for each user.

[0098] [Input Information Management Database] The input information management database shown in Figure 3(F) is a database that registers household fatigue information, which is entered by the person sleeping next to the person, in association with the date.

[0099] The input information management database has two columns named "Date" and "Household Fatigue Information," as well as records (rows).

[0100] The field in the column named "Date" will contain the year, month, and day.

[0101] The field in the column named "Household Chore Fatigue Information" has two sub-columns named "Household Chore ID" and "Fatigue Information".

[0102] A subcolumn named "Household Chore ID" has multiple subcolumns, each also named "Household Chore ID". The fields in the subcolumns named "Household Chore ID" are assigned a "Remaining Household Chore" flag of either "0" or "1". A "Remaining Household Chore" flag of "0" indicates that the chore is not planned to be done after putting the child to sleep. A "Remaining Household Chore" flag of "1" indicates that the chore is planned to be done after putting the child to sleep. In the example shown in Figure 3(F), on January 19, 2025, a "Remaining Household Chore" flag of "1" is registered for "Washing Dishes" (indicated by Household Chore ID "KA01") and "Child-Related" (indicated by Household Chore ID "KB02"). That is, on January 19, 2025, the co-sleeper plans to do the "Washing Dishes" and "Child-Related" chores after putting the child to sleep. The initial value of the remaining household chore flag is "0".

[0103] The field in the column named "Fatigue Information" will register either "Low" (indicating low fatigue) or "High" (indicating high fatigue) for the person helping the baby to sleep.

[0104] [Operation (processing) of management program 26 and application 36] The management program 26 and application 36 cause CPU 21 and CPU 31 to execute the registration process shown in Figure 4 and the wake-up management process shown in Figures 4 and 5. The processes that management program 26 causes CPU 21 to execute are processes that CPU 21 executes and processes that management device 20 executes. The processes that application 36 causes CPU 31 to execute are processes that CPU 31 executes and processes that user terminal 30 executes. The processes that CPU 21 and CPU 31 execute are processes that the controller of the sleep management system 10 executes. Note that in the flowcharts shown in Figures 4 and 5, the database is abbreviated as DB.

[0105] The user operates the user terminal 30 to launch the application 36 (S11). The user inputs a command to display the registration screen into the user terminal 30 (S12).

[0106] Based on the acceptance of user input (S12), application 36 transmits the identification ID stored in terminal memory 32 and a registration screen request to the management device 20 via LAN 11 (S13). The registration screen request is, for example, a command that includes screen specification information indicating a registration screen.

[0107] The management program 26 receives an identification ID and a registration screen request (S13). The management program 26 reads the screen format specified by the received registration screen request from the management memory 22. The management program 26 also reads information associated with the identification ID from the user management database. This information includes the user's name, "Yamada Hanako" and "Yamada Taro," and the names of their children, "Yamada Jiro," "Yamada Kazumi," and "Yamada Saburo." The management program 26 inputs the information read from the user management database into the screen format to generate registration screen data (S14). The management program 26 transmits the generated registration screen data to the user terminal 30 via the LAN 11 (S15).

[0108] App 36 receives registration screen data (S15). App 36 displays the registration screen indicated by the received registration screen data on the touch panel 34 (S16).

[0109] As shown in Figure 6(A), the registration screen displays the user's name, "Yamada Hanako," which is retrieved from the user management database. The registration screen also has a pull-down menu 71 associated with the text, "Who will be in charge of putting the baby to sleep?" The pull-down menu 71 includes options containing the text "Yamada Hanako" and "Yamada Taro," both retrieved from the user management database. The user, "Yamada Hanako," selects the person who will be putting the baby to sleep using the pull-down menu 71. In the example shown in Figure 6(A), the user, "Yamada Hanako," selects the option containing her own name as the person who will be putting the baby to sleep.

[0110] The registration screen has the text "Which child will you put to sleep?". The registration screen also has checkbox 72 corresponding to the text "Jiro Yamada", checkbox 73 corresponding to the text "Kazumi Yamada", and checkbox 74 corresponding to the text "Saburo Yamada", all of which are read from the user management database. The user, "Hanako Yamada", specifies which child will be put to sleep using the checkboxes. In the example shown in Figure 6(A), the user "Hanako Yamada" does not specify "Jiro Yamada", who is 8 years old, but instead specifies "Kazumi Yamada", who is 3 years old, and "Saburo Yamada", who is 1 year old, as the children to be put to sleep.

[0111] The registration screen also has a "Send" icon 75. The user, "Yamada Hanako," selects the "Send" icon 75 after specifying the person who will put the child to sleep and the child to be put to sleep. Note that the person who will put the child to sleep and the child to be put to sleep may also be specified by another user, "Yamada Taro," who is not the co-sleeper.

[0112] As shown in Figure 4, app 36 accepts the user's selection of the "Send" icon 75 (S17). App 36 transmits the identification ID and registration information to the management device 20 via LAN 11 (S18). The registration information includes the name of the person putting the child to sleep and the name of the child being put to sleep.

[0113] The management program 26 receives the identification ID and registration information (S18). The management program 26 registers the received registration information in the user management database (S19). In the example shown in Figure 3(A), the co-sleeper flag of "1" is registered in association with the identification ID of "Yamada Hanako". Also, the co-sleeper flag of "1" is registered in association with the identification ID of "Yamada Kazumi". Also, the co-sleeper flag of "1" is registered in association with the identification ID of "Yamada Saburo". The initial value of each flag is "0".

[0114] As shown in Figure 4, the management program 26 reads the registration completion screen data from the management memory 22 and transmits it to the user terminal 30 via the LAN 11 (S20).

[0115] The application 36 displays the received registration completion screen on the touch panel 34 (S21) and terminates the registration process (end).

[0116] Registration of co-sleeping partners and those being co-sleeped with in the user management database may be done daily, or at a frequency such as once a week or once a month. The management program 26 maintains previously registered information until new registrations are made.

[0117] Next, the wake-up management process will be explained.

[0118] The user operates the user terminal 30 to launch the application 36 (S31). The user operates the user terminal 30 to input a command to display the start screen (S32).

[0119] Application 36 sends an identification ID and a start screen request to the management device 20 via LAN 11 (S33). The start screen request is a command that includes screen specification information indicating the start screen, for example.

[0120] The management program 26 receives an identification ID and a start screen request (S33). The management program 26 reads the screen format specified by the received start screen request from the management memory 22. The management program 26 also reads the user's name from the user management database and the household chore name from the wake-up determination table. The management program 26 inputs the name and household chore name into the screen format and generates start screen data (S34). The management program 26 transmits the generated start screen data to the user terminal 30 via the LAN 11 (S35).

[0121] App 36 receives start screen data (S35). App 36 displays the start screen indicated by the received start screen data on the touch panel 34 (S36).

[0122] As shown in Figure 6(B), the start screen has the name of the person sleeping with the child, "Yamada Hanako," and a pull-down menu 76 associated with the words "Wake-up Settings." The pull-down menu 76 includes options with the words "Wake up," options with the words "Do not wake up," and options with the words "Automatic setting." If the person sleeping with the child wishes to wake them up after they have fallen asleep, they select the option with the words "Wake up" in the pull-down menu 76. If the person sleeping with the child is willing to sleep until morning, they select the option with the words "Do not wake up" in the pull-down menu 76. If the person sleeping with the child wishes to delegate the decision of whether or not to wake them up to the sleep management system 10, they select the option with the words "Automatic setting" in the pull-down menu 76.

[0123] App 36, based on the selection of an option containing the text "Automatic Settings" in the pull-down menu 76, displays the text "Things to do when you wake up" and other similar text on the start screen according to the JavaScript contained in the start screen data. The following explanation assumes that an option containing the text "Automatic Settings" has been selected.

[0124] The start screen has the words "Things to do when you wake up." The start screen also has checkboxes 77 corresponding to the words "Washing dishes," 78 corresponding to the words "Laundry," 79 corresponding to the words "Ironing," 80 corresponding to the words "Cleaning," and 81 corresponding to the words "Studying."

[0125] Figure 7(A) shows the start screen that is displayed by scrolling the start screen. As shown in Figure 7(A), the start screen has a checkbox 82 associated with the word "work", a checkbox 83 associated with the word "child-related", and a checkbox 84 associated with the word "errands".

[0126] The start screen also includes the text "Today's Fatigue Level," a radio button 85 corresponding to the text "High Fatigue," a radio button 86 corresponding to the text "Low Fatigue," and a "Start Bedtime Management" icon 87.

[0127] The user checks the checkbox corresponding to the name of the household chore to be performed after putting the child to sleep, and then selects either radio button 85 or radio button 86, and then selects the "Start bedtime management" icon 87.

[0128] As shown in Figure 4, app 36 accepts the selection of an option in the pull-down menu 76, the selection of one of the checkboxes from checkbox 77 to checkbox 84, the selection of radio button 85 or radio button 86, and the selection of the "Start Sleep Management" icon 87 (S37). App 36 transmits the identification ID, input information, and start request to the management device 20 via LAN 11 (S38).

[0129] The input information includes information indicating the type of option selected by the user in the pull-down menu 76. It also includes the household chore name or the corresponding household chore ID associated with the checkbox selected by the user from checkboxes 77 to 84. Furthermore, the input information includes a fatigue flag of "1" indicating high fatigue or "0" indicating low fatigue. The input information is an example of planned household chore information.

[0130] A start request is, for example, a command that instructs the system to start the wake-up management process.

[0131] The management program 26 receives the identification ID, input information, and start request (S38). The management program 26 registers the received input information in the input information management database (S39). The process in step S38 is an example of an acquisition process.

[0132] The management program 26 executes the processes from step S40 to step S46 based on the received input information and the wake-up determination table (see Figure 3(C)). More specifically, the management program 26 determines, based on the input information, which option the co-sleeper selected in the pull-down menu 76 (S40). If the management program 26 determines that the co-sleeper selected an option containing the word "wake up" in the pull-down menu 76 (S40: wake up), it generates the first notification screen data (S41). Specifically, the management program 26 generates the first notification screen data by entering the user's name into the screen format read from the management memory 22. The first notification screen data is screen data that shows the first notification screen. The first notification screen is a screen that notifies the user that the child will be woken up after falling asleep. Details of the first notification screen will be described later.

[0133] When the management program 26 determines that the user has selected an option containing the words "Do not wake" in the pull-down menu 76 (S40: Do not wake), it generates second notification screen data (S42). Specifically, the management program 26 generates the second notification screen data by inputting the user's name into the screen format read from the management memory 22. The second notification screen data is screen data that shows the second notification screen. The second notification screen is a screen that notifies the user that they will not wake the child even if they fall asleep with them. Details of the second notification screen will be described later.

[0134] When the management program 26 determines that the user has selected an option containing the words "Automatic setting" in the pull-down menu 76 (S40: Automatic setting), it determines, based on the wake-up determination table, whether or not there is a wake-up flag of "1" associated with the chore name included in the input information (S43). In other words, step S43 determines whether or not there is a chore that the co-sleeper must get up to do after putting the child to sleep. When the management program 26 determines that there is a wake-up flag of "1" associated with the chore name included in the input information (S43: Yes), it generates the first notification screen data (S41). In other words, if there is a chore that the co-sleeper must do after putting the child to sleep, it is decided to wake the co-sleeper.

[0135] If the management program 26 determines that there is no wake-up flag of "1" associated with the household chore name included in the input information (S43: No), it determines whether the co-sleeper's fatigue level is "high" or "low" based on the value of the fatigue flag included in the input information (S44). If the management program 26 determines that the co-sleeper's fatigue level is "high" (S44: High), it generates the second notification screen data (S42). In other words, if there are no household chores that must be done after putting the baby to sleep, and the co-sleeper is tired, it is decided not to wake the co-sleeper.

[0136] If the management program 26 determines that the co-sleeper's fatigue level is "low" (S44: low), it reads the time required for each chore, associated with the chore name included in the input information, from the wake-up determination table. The management program 26 calculates the amount of chore by summing up the read time required (S45). The management program 26 determines whether the calculated amount of chore is equal to or greater than the threshold amount of chore pre-stored in the management memory 22 (S46). If the management program 26 determines that the calculated amount of chore is equal to or greater than the threshold amount of chore (S46: Yes), it generates the first notification screen data (S41). If the management program 26 determines that the calculated amount of chore is not equal to or greater than the threshold amount of chore (S46: No), it generates the second notification screen data (S42). In other words, if there is no chore that the co-sleeper must do after putting the baby to sleep, the co-sleeper is not tired, and the amount of chore the co-sleeper plans to do after putting the baby to sleep is small, it is decided not to wake the co-sleeper. On the other hand, if there are no household chores that absolutely must be done after putting the baby to sleep, the co-sleeper is not tired, and the amount of household chores the co-sleeper plans to do after putting the baby to sleep is large, then it is decided to wake the co-sleeper. The processes in steps S43, S45, and S46 are examples of processes for deciding whether to wake the baby.

[0137] As shown in steps S40 to S46, the decision of whether or not to wake the co-sleeper who has fallen asleep with the child being put to sleep is made based on the co-sleeper's wishes, then on whether or not there are any household chores that the co-sleeper must do after putting the child to sleep, then on the co-sleeper's level of fatigue, and finally on the amount of household chores the co-sleeper has to do after putting the child to sleep.

[0138] As shown in Figure 5, the management program 26 transmits the generated first notification screen data or second notification screen data to the user terminal 30 via the LAN 11 (S47).

[0139] App 36 receives either the first notification screen data or the second notification screen data (S47). App 36 displays the first notification screen indicated by the received first notification screen data, or the second notification screen indicated by the received second notification screen data, on the touch panel 34 (S48).

[0140] As shown in Figure 7(B), the first notification screen has the name of the person sleeping next to the child, "Yamada Hanako," the text "I will wake the child when he / she falls asleep," an "OK" icon 88, and a "Don't wake him / her" icon 89. If the person sleeping next to the child, "Yamada Hanako," agrees to be woken, she selects the "OK" icon 88. If the person sleeping next to the child, "Yamada Hanako," wishes not to wake him / her, she selects the "Don't wake him / her" icon 89.

[0141] As shown in Figure 8(A), the second notification screen displays the name of the person sleeping next to the child, "Hanako Yamada," the text "Is it alright if I sleep with the child and not wake them?", an "OK" icon 90, and a "Wake them up" icon 91. If the person sleeping next to the child agrees not to wake them, they select the "OK" icon 90. If the person sleeping next to the child wishes to wake them, they select the "Wake them up" icon 91.

[0142] As shown in Figure 5, app 36 accepts the selection of either the "OK" icon 88 or the "Do not wake" icon 89 on the first notification screen (S49). Alternatively, app 36 accepts the selection of either the "OK" icon 90 or the "Wake up" icon 91 on the second notification screen (S49). App 36 transmits the identification ID and a designation flag of "0" or "1" to the management device 20 via LAN 11 (S50). A designation flag of "0" indicates that the user has selected "Do not wake up", and a designation flag of "1" indicates that the user has selected "Wake up".

[0143] The management program 26 receives the identification ID and the designation flag (S50). The management program 26 determines whether the value of the received designation flag is "0" or "1" (S51). If the management program 26 determines that the value of the designation flag is "0" and that the co-sleeping person does not want to be woken (S51: "0"), it terminates the wake-up management process (end).

[0144] If the management program 26 determines that the value of the specified flag is "1" and that the user wishes to be woken up (S51: "1"), it acquires the detection information output by the sleep detection sensor 60 multiple times at a predetermined sampling period (S52). The predetermined sampling period is, for example, between several tens of milliseconds and several seconds.

[0145] Furthermore, the management program 26 reads from the user management database the number of children to be put to sleep (the co-sleepers) and the weights of the co-sleepers and the children to be put to sleep (S53).

[0146] Based on the read information and acquired detection information, the management program 26 determines co-sleeping location information indicating the position of the co-sleeping person in the bed 40, infant location information indicating the position of the infant in the bed 40, and infant location information indicating the position of the baby in the bed 40 (S54). Note that if the person being co-sleeped with is only an infant, infant location information is not required.

[0147] For example, the management program 26 determines the group of position information associated with all pressure values ​​that are equal to or greater than the first threshold pressure from among the multiple pressure values ​​of the detection information acquired in step S52 as the co-sleeping person's position information (S54). The first threshold pressure is a value corresponding to the weight of the co-sleeping person read from the user management database.

[0148] Furthermore, the management program 26 determines the group of positional information associated with all pressure values ​​among the multiple pressure values ​​of the acquired detection information that are between the second threshold pressure and the first threshold pressure as the infant's positional information (S54). The second threshold pressure is a value corresponding to the weight of the infant who is sleeping next to the baby, read from the user management database.

[0149] Furthermore, the management program 26 determines the group of positional information associated with all pressure values ​​that are between the third threshold pressure and the second threshold pressure from among the multiple pressure values ​​of the acquired detection information as the infant's positional information (S54). The third threshold pressure is a value corresponding to the weight of the infant being co-slept with, read from the user management database.

[0150] Furthermore, if the positions where the co-sleeping person lies, the position where the infant lies, and the position where the baby lies are predetermined, the co-sleeping person's position information, the infant's position information, and the baby's position information may be stored in the management memory 22 as fixed values.

[0151] The following explanation covers the case where there are two children to be put to sleep: an infant and a toddler. The same process is followed when there is only one child (either an infant or toddler), when both children are infants, or when both children are toddlers.

[0152] The management program 26 stores the determined co-sleeping person location information, co-sleeping person pressure information, and time information in the management memory 22, associating them (S55). The co-sleeping person pressure information is a group of pressure information associated with the group of location information indicated by the co-sleeping person location information in the detection information. The time information may be a number indicating the acquisition order of multiple acquisitions of detection information.

[0153] Furthermore, the management program 26 stores the determined infant location information, infant pressure information, and time information in the management memory 22 in association with each other (S55). The infant pressure information is a group of pressure information associated with the group of location information indicated by the infant location information in the detection information.

[0154] Furthermore, the management program 26 stores the determined infant location information, infant pressure information, and time information in the management memory 22 in association with each other (S55). The infant pressure information is a group of pressure information associated with the group of location information indicated by the infant location information in the detection information.

[0155] The location information of the person sleeping with the child, the child's location information, and the infant's location information are determined and stored in the management memory 22 only for the first detection information (S54). From the second detection onward, the management program 26 obtains pressure information corresponding to the location information of the person sleeping with the child, the child's location information, and the infant's location information, and stores it in the management memory 22 in association with the time information (S54).

[0156] The management program 26 determines whether the co-sleeping person, infant, and baby are awake or not based on the multiple pressure information stored in the management memory 22 in step S55 (S56). The multiple pressure information includes the co-sleeping person's pressure information for each time period, or the infant's pressure information for each time period, or the baby's pressure information for each time period. In other words, the management program 26 determines whether the co-sleeping person, infant, and baby are awake or not based on the change in pressure information over time. The period of change over time used for the determination is determined by the number of times detection information is acquired periodically at the sampling period, for example, 1 minute. In other words, it is determined at 1-minute intervals whether the co-sleeping person, infant, and baby are awake or not.

[0157] People who are awake move a lot. For example, the management program 26 determines whether the co-sleeping person, infant, and toddler have moved a lot based on the time-dependent changes in pressure information, and determines that they are awake based on the presence of significant movement (S56: Yes). Note that the determination of whether or not they are awake is made individually for each co-sleeping person, infant, and toddler.

[0158] The next step S57 that the management program 26 executes is the process that responds when a co-sleeping person, infant, or toddler wakes up after falling asleep. That is, even if it is determined in step S58 (described later) that the person has fallen asleep and the timing of falling asleep is stored in the management memory 22 (S59), if the person wakes up (S56: Yes), the timing of falling asleep that has already been stored in the management memory 22 is deleted.

[0159] To explain in more detail, if the management program 26 determines that the co-sleeping person is awake (S56: Yes), it deletes the co-sleeping person's sleep onset timing stored in the management memory 22 (S57). Also, if the management program 26 determines that the infant is awake (S56: Yes), it deletes the infant's sleep onset timing stored in the management memory 22 (S57). Also, if the management program 26 determines that the baby is awake (S56: Yes), it deletes the baby's sleep onset timing stored in the management memory 22 (S57). If the management program 26 determines that the infant is not awake (S56: No), it skips the processing in step S57.

[0160] The management program 26 determines whether the co-sleeping person, infant, and baby have fallen asleep based on the multiple pressure information stored in the management memory 22 in step S55 (S58). The multiple pressure information includes the co-sleeping person's pressure information for each time period, or the infant's pressure information for each time period, or the baby's pressure information for each time period. In other words, the management program 26 determines whether the co-sleeping person, infant, and baby have fallen asleep based on the change in pressure information over time. The period of change over time is determined by the number of times detection information is acquired periodically at the sampling period, for example, 1 minute. In other words, it is determined at 1-minute intervals whether the co-sleeping person, infant, and baby have fallen asleep.

[0161] Humans make subtle body movements during light sleep. For example, the management program 26 determines whether the co-sleeper, infant, and toddler are making subtle body movements based on changes in pressure information over time, and determines that they have fallen asleep based on the presence of subtle body movements. The determination of whether or not they have fallen asleep is made individually for each co-sleeper, infant, and toddler.

[0162] When the management program 26 determines that the child has fallen asleep (S58: Yes), it stores the current time as the sleep-on time, associated with the identification ID, in the management memory 22 (S59). The process in step S59 is performed for each co-sleeper, infant, and baby. Specifically, the identification ID and sleep-on time of the co-sleeper "Yamada Hanako," the identification ID and sleep-on time of the infant "Yamada Kazumi," and the identification ID and sleep-on time of the baby "Yamada Saburo" are stored in the management memory 22. The process in step S59 is an example of the first process. Note that if the sleep-on time is already stored in the management memory 22, the management program 26 does not overwrite the sleep-on time.

[0163] If the management program 26 determines that the user has not fallen asleep (S58: No), it skips the process in step S59.

[0164] The management program 26 calculates the elapsed time since falling asleep for each co-sleeper, infant, and toddler, based on the time they fell asleep and the current time (S60).

[0165] The management program 26 determines whether the co-sleeper, infant, and toddler are in a light sleep state or a deep sleep state based on the calculated elapsed time and the sleep determination table (see Figure 3(B)) (S61). The management program 26 also determines the sleep state of those whose sleep onset time is not stored in the management memory 22 to be "awake". The management program 26 determines the sleep state for each co-sleeper, infant, and toddler and stores it in the management memory 22. Specifically, the management program 26 associates the sleep state information of "1" indicating a light sleep state, the sleep state information of "2" indicating a deep sleep state, and the sleep state information of "0" indicating an awake state with the identification ID of the co-sleeper, the identification ID of the infant, and the identification ID of the toddler, and stores them in the management memory 22. The processing from step S52 to step S61 is an example of the sleep state determination process. The processing in step S61 is an example of the second process.

[0166] The management program 26 obtains a wake-up method number based on the determined sleep state and the first wake-up method determination table (see Figure 3(D)) or the second wake-up method determination table (see Figure 3(E)) (S62). The management program 26 determines whether the obtained wake-up method number is "1", "2", or "0" (S63).

[0167] Based on its determination that the acquired wake-up method number is "1" (S63: "1"), the management program 26 drives the blower 50 (S64). That is, if one of the infants being put to sleep is in a light sleep state and the other is in a deep sleep state, or if both the infant and the toddler are in a light sleep state, the air is blown on the awake co-sleeper. The process in step S64 is an example of a second wake-up process.

[0168] In step S64, the management program 26 determines the amount of drive for the louvers 52 of the blower 50 and rotates the fan 51 based on the location information of the person sleeping next to the person, which was acquired in step S54. In other words, the management program 26 drives the blower 50 so that air blows on the person sleeping next to the person.

[0169] Based on its determination that the acquired wake-up method number is "2" (S63: "2"), the management program 26 inputs voice data to the speaker 55 and causes the speaker 55 to emit an alarm sound (S65). In other words, the alarm sound is emitted when both the infant and toddler being put to sleep are in a deep sleep state. The process in step S65 is an example of the first wake-up process.

[0170] Based on its determination that the acquired wake-up means number is "0" (S63: "0"), the management program 26 repeats the process from step S52 onwards. That is, if the co-sleeper is in a deep sleep state, or if at least one of the infant or toddler is awake, neither the blower 50 nor the speaker 55 is driven. The process from step S52 onwards is repeatedly executed until a wake-up means number of "1" or "2" is acquired.

[0171] To explain in more detail, if the two children being put to sleep fall asleep first and the parent putting them to sleep is awake, the fan 50 is activated, and the parent recognizes that the children have fallen asleep. If the two children and the parent fall asleep at almost the same time, and the two children enter a deep sleep state while the parent is in a first light sleep state, the speaker 55 is activated. If the parent falls asleep first and enters a deep sleep state before both children enter a deep sleep state, the fan 50 and speaker 55 will not be activated until the parent enters a light sleep state and both children enter a deep sleep state, at which point the speaker 55 is activated.

[0172] After processing in step S64 or step S65, the management program 26 acquires detection information output by the sleep detection sensor 60 (S66). Based on the acquired detection information, the management program 26 determines whether the co-sleeper has left the bed 40 (S67). For example, the management program 26 determines that the co-sleeper has left the bed 40 based on the fact that the detection information does not include a pressure greater than or equal to the first threshold pressure (S67: Yes). The management program 26 repeatedly executes the processing in step S60 at a predetermined sampling period until it determines that the co-sleeper has left the bed 40 (S67: No, S66).

[0173] Based on its determination that the co-sleeper has left the bed 40 (S67: Yes), the management program 26 stops the operation of the fan 50 or speaker 55 (S68). The management program 26 reads the termination notification screen data from the management memory 22 and sends it to the user terminal 30 via the LAN 11 (S69), ending the wake-up management process (end).

[0174] App 36 receives termination notification screen data (S69). App 36 displays the termination notification screen indicated by the termination notification screen data on the touch panel 34 (S70).

[0175] As shown in Figure 8(B), the completion notification screen includes the name of the person providing the bedtime assistance, the text "We are ending bedtime assistance. Thank you for your hard work. See you tomorrow," and an "OK" icon 92. The person providing the bedtime assistance selects the "OK" icon 92.

[0176] As shown in Figure 5, the app 36 terminates the wake-up management process and startup based on the selection of the "OK" icon 92 by the person sleeping next to the user (S71) (end).

[0177] [Effects of the Embodiment] The management program 26 activates the speaker 55, which is the first wake-up device, to sound an alarm when the child sleeping next to the parent is in a deep sleep state and the parent sleeping next to the child is in a light sleep state. Thus, the sleep management system 10 can wake up the parent who has fallen asleep with the child without waking the child.

[0178] The management program 26 activates the fan 50 to blow air onto the parent when the child sleeping next to the parent is in a deep sleep state and the parent sleeping next to the parent is awake. The awake parent recognizes that the child has fallen asleep when they feel the air blowing on them. The parent then moves away from the bed so as not to wake the child who is in a light sleep state. Thus, the sleep management system 10 can make the awake parent aware that the child has fallen asleep.

[0179] The management program 26 determines whether the co-sleeper is awake, in light sleep, or in deep sleep based on a sleep determination table containing sleep cycle information for people aged 5 and older, whether they have fallen asleep, and the elapsed time since they fell asleep. The management program 26 also determines whether the co-sleeper is awake, in light sleep, or in deep sleep based on a sleep determination table containing sleep cycle information for children aged 0 to under 5, whether they have fallen asleep, and the elapsed time since they fell asleep. Therefore, the sleep management system 10 can determine the sleep state of the co-sleeper and the co-sleeper by estimation without directly detecting their sleep states.

[0180] The management program 26 determines whether an infant's sleep state is awake, light sleep, or deep sleep based on a sleep determination table containing sleep cycle information for infants aged 0 to under 2 years, whether the infant has fallen asleep, and the elapsed time since falling asleep. Similarly, the management program 26 determines whether an infant's sleep state is awake, light sleep, or deep sleep based on a sleep determination table containing sleep cycle information for toddlers aged 2 to under 5 years, whether the infant has fallen asleep, and the elapsed time since falling asleep. Therefore, the sleep management system 10 can appropriately determine the sleep state of a child according to the child's age.

[0181] The management program 26 obtains input information, which is information about the household chores that the co-sleeper will perform after the child has fallen asleep, through the user terminal 30 (S38). Based on the obtained input information and the wake-up determination table, the management program 26 decides whether or not to wake the co-sleeper (S43, S46). Therefore, the bedtime management system 10 can appropriately wake the co-sleeper depending on the type and amount of household chores that the co-sleeper plans to perform after the child has fallen asleep.

[0182] Since the sleep detection sensor 60, the fan 50, and the speaker 55 are attached to the bed 40 where the co-sleeper and the child sleeping sleep, there is no need to install the sleep detection sensor 60, the fan 50, and the speaker 55 in the room where the child is put to sleep. Therefore, the sleep management system 10 can be easily introduced by the user.

[0183] The management program 26 activates speaker 55 to sound an alarm when the child sleeping next to the bed is in a deep sleep state and the parent sleeping next to the child is awake. Thus, the awake parent can recognize that the child is in a deep sleep state and leave the bed 40 with peace of mind. As a result, the sleep management system 10 can wake the parent without waking the child. [Differentiation]

[0184] In the embodiment, an example was described in which a user terminal 30 is used as an input interface for receiving user input and as a display for showing the screen. However, the input interface and display may be provided by the management device 20. In other words, the sleep-inducing management system 10 does not need to include a user terminal 30.

[0185] In the embodiment, the sleep-inducing management system 10 was described as having a user terminal 30, such as a smartphone (registered trademark) or tablet (registered trademark), as an example of an input interface. However, the user terminal 30 may also be a personal computer connected to a keyboard and mouse. The keyboard and mouse are just one example of an input interface. Alternatively, the sleep-inducing management system 10 may have a touch panel attached to the management device 20 instead of the user terminal 30. The user performs various inputs through the touch panel attached to the management device 20.

[0186] In the embodiment, an example was described in which the speaker 55 is driven when the person being co-slept with is in a deep sleep state and the co-sleeper is awake. However, when the person being co-slept with is in a deep sleep state and the co-sleeper is awake, the blower 50 may be driven instead of the speaker 55, or neither the speaker 55 nor the blower 50 may be driven.

[0187] In the embodiment, an example was described in which neither the fan 50 nor the speaker 55 is driven when both the co-sleeper and the person being co-sleeped are in a light sleep state. However, when both the co-sleeper and the person being co-sleeped are in a light sleep state, the fan 50 may be driven and the airflow directed only at the co-sleeper.

[0188] In the embodiment, a sleep detection sensor 60 comprising one pressure-sensitive sheet 62 was described. However, the sleep detection sensor 60 may comprise two pressure-sensitive sheets 62, one for the person sleeping next to the other and one for the person sleeping next to the other. Alternatively, the sleep-inducing management system 10 may comprise two or more sleep detection sensors 60, such as a sleep detection sensor 60 for the person sleeping next to the other and a sleep detection sensor 60 for the person sleeping next to the other.

[0189] In this embodiment, steps S52 to S61 were described as a process for determining the sleep state of the co-sleeper and the person being co-sleeped with. However, other processes may be executed if it is possible to determine the sleep state of the co-sleeper and the person being co-sleeped with. For example, a sleep state determination program module mounted on the control unit of a commercially available body movement sensor may be used as part of the management program 26.

[0190] In the embodiment, an example was described in which a body movement sensor equipped with a pressure-sensitive sheet 62 was used as the sleep detection sensor 60 for detecting the sleep state of the person sleeping next to the other person. However, the sleep detection sensor 60 may also be a wearable sensor worn by the person sleeping next to the other person. The wearable sensor outputs biometric information such as pulse rate, body temperature, respiratory rate, and blood pressure. The management program 26 determines the sleep state of the person sleeping next to the other person based on the biometric information output by the wearable sensor.

[0191] Alternatively, a digital camera with the bed 40 as its imaging area may be used as the sleep detection sensor 60. The management program 26 analyzes the body movements of the co-sleeper and the person being co-sleeped based on the video data captured by the digital camera, and determines the sleep state of the co-sleeper and the person being co-sleeped based on the analyzed body movements.

[0192] In the embodiment, an example was described in which the sleep-inducing management system 10 is equipped with a blower 50 and a speaker 55. However, the sleep-inducing management system 10 may be equipped with other waking devices instead of, or together with, the blower 50 and speaker 55. Other waking devices include devices such as wearable sensors worn by the person sleeping with the baby and having a vibration function. Alternatively, other waking devices are vibration devices attached to the mattress 43. Alternatively, other waking devices are spotlights that shine light towards the person sleeping with the baby. Alternatively, other waking devices are air conditioning devices attached to the room where the bed 40 is installed.

[0193] [Note 1] A sleep management system comprising a controller, memory, sleep detection sensor, and first wake-up device, The above controller is Based on the detection information from the sleep detection sensor mentioned above, a sleep state determination process is executed to determine the sleep state of the person sleeping next to the other person and the sleep state of the person being slept next to. The above sleep states include wakefulness, light sleep, and deep sleep. The above controller is Based on the fact that the sleep state of the person being co-slept with is the deep sleep state, and the sleep state of the person co-sleeping with the other person is the light sleep state, A sleep-inducing management system that performs a first wake-up process to activate the first wake-up device described above.

[0194] [Note 2] It is further equipped with a ventilation device, which is a second wake-up device. The above-mentioned first wake-up device is a speaker. The above controller is The sleep-inducing management system according to Appendix 1, further comprising: a second wake-up process that activates the second wake-up device based on the fact that the sleep state of the person being co-slept with is the light sleep state, and the sleep state of the person co-sleeping with the other person is the awake state.

[0195] [Note 3] The above sleep detection sensor is a sensor capable of detecting the timing of falling asleep, which is the moment when the person sleeping next to the person sleeping next to the person sleeping next to transitions from the awake state to the light sleep state. The above memory is The system stores information on the first sleep cycle corresponding to the age of the person sleeping next to the system, and information on the second sleep cycle corresponding to the age of the person being slept next to the system. The above sleep state determination process is: A first process to acquire the sleep onset timing based on the detection information from the sleep detection sensor, A sleep-inducing management system according to Appendix 1, comprising a second process for determining the sleep state of the person co-sleeping and the sleep state of the person being co-sleeped with, based on the elapsed time from the time of falling asleep, the first sleep cycle information, and the second sleep cycle information.

[0196] [Note 4] The above information on the second sleep cycle is, A sleep-in management system as described in Appendix 3, including first information corresponding to the above-mentioned co-sleeping person who is aged 0 or older but less than 2 years old, and second information corresponding to the above-mentioned co-sleeping person who is aged 2 or older but less than 5 years old.

[0197] [Note 5] It also features an input interface, The above controller is Through the above input interface, the acquisition process obtains planned household chore information indicating the household chores that the person sleeping with the child will perform after putting the child to sleep, A bedtime management system described in any of Appendix 1 to Appendix 4, further comprising: a wake-up determination process that determines whether or not to perform the above-mentioned first wake-up process based on the above-mentioned planned household information.

[0198] [Note 6] The bed for the person sleeping with the other person and the person being slept with, the bed being fitted with the sleep detection sensor, the first wake-up device, and the second wake-up device, as described in Appendix 2. [Explanation of Symbols]

[0199] 10. Sleep-inducing management system 11. Local Area Network 20...Management device 21..CPU 22...Management memory 23. Communication Interface 24... Clock Module 26. Management Program 30. User terminals 31..CPU 32. Terminal Memory 33. Communication Interface 34. Touch panel 36. Application Programs

Claims

1. A sleep management system comprising a controller, memory, sleep detection sensor, and first wake-up device, The above controller is Based on the detection information from the sleep detection sensor mentioned above, a sleep state determination process is executed to determine the sleep state of the person sleeping next to the other person and the sleep state of the person being slept next to. The above sleep states include wakefulness, light sleep, and deep sleep. The above controller is Based on the fact that the sleep state of the person being co-slept with is the deep sleep state, and the sleep state of the person co-sleeping with the other person is the light sleep state, A sleep-inducing management system that performs a first wake-up process to activate the first wake-up device described above.

2. It is further equipped with a ventilation device, which is a second wake-up device. The first wake-up device described above is a speaker. The above controller is The sleep-inducing management system according to claim 1, further comprising: a second wake-up process that drives the second wake-up device based on the fact that the sleep state of the person being co-slept with is the light sleep state and the sleep state of the person co-sleeping with the other person is the awake state.

3. The above sleep detection sensor is a sensor capable of detecting the timing of falling asleep, which is the moment when the person sleeping next to the person sleeping next to transitions from the awake state to the light sleep state. The above memory is The system stores information on the first sleep cycle corresponding to the age of the person sleeping next to the system, and information on the second sleep cycle corresponding to the age of the person being slept next to the system. The above sleep state determination process is: A first process to acquire the sleep onset timing based on the detection information from the sleep detection sensor, A sleep-inducing management system according to claim 1, comprising a second process for determining the sleep state of the person sleeping next to the other person and the sleep state of the person being slept next to, based on the elapsed time from the time of falling asleep, the first sleep cycle information, and the second sleep cycle information.

4. The above second sleep cycle information is, A sleep-inducing management system according to claim 3, comprising first information corresponding to the person being co-slept with whose age is 0 or older but less than 2 years old, and second information corresponding to the person being co-slept with whose age is 2 or older but less than 5 years old.

5. It also features an input interface, The above controller is Through the above input interface, the acquisition process obtains planned household chore information indicating the household chores that the person sleeping with the child will perform after putting the child to sleep, A bedtime management system according to any one of claims 1 to 4, further comprising: a wake-up determination process that determines whether or not to perform the first wake-up process based on the above-mentioned planned household information.

6. The bed for the person sleeping with the other person and the person being slept with, the bed being fitted with the sleep detection sensor, the first wake-up device, and the second wake-up device, according to claim 2.

Images