JP7745374B2 - Network systems and programs - Google Patents

Description

The present invention relates to useful information processing technology related to the consumption of sanitary products.

Technologies for predicting menstrual cycles by measuring basal body temperature and other parameters have been known for some time. For example, these techniques are disclosed in Japanese Patent Laid-Open Publication Nos. 63-135144 (Patent Document 1) and 62-183807.

Japanese Patent Application Publication No. 63-135144 Japanese Unexamined Patent Publication No. 183807/1983

The object of the present invention is to provide a network system that can suggest sanitary products to be used in the future based on the sanitary product usage history.

According to one aspect of the present invention, a network system is provided that includes a storage device for storing sanitary products, a communication terminal used by a user, and a server that accumulates the sanitary product usage history of each user based on data from the storage device and presents to the communication terminal at least the type of sanitary product that is likely to be used next.

As described above, this invention provides a network system that can suggest sanitary products to be used in the future based on the sanitary product usage history.

1 is a conceptual diagram illustrating an overall configuration of a network system according to a first embodiment; FIG. 2 is an image diagram showing an example of a screen of the communication terminal according to the first embodiment. FIG. 2 is an image diagram showing an example of a screen of the communication terminal according to the first embodiment. 1 is a block diagram showing a configuration of a storage device according to a first embodiment; FIG. 2 is a block diagram illustrating a configuration of a server according to the first embodiment. FIG. 3 is a conceptual diagram showing user data according to the first embodiment; FIG. 3 is a conceptual diagram showing usage history data according to the first embodiment. FIG. 2 is a conceptual diagram showing physiological information data according to the first embodiment. 10 is a flowchart illustrating information processing by a server according to the first embodiment; 10 is a conceptual diagram showing the input/output history of sanitary products and a start/end score determination table according to the first embodiment. FIG. FIG. 10 is an image diagram showing the transition of points earned from using sanitary products according to the first embodiment. FIG. 2 is an image diagram showing an example of a screen of the communication terminal according to the first embodiment. FIG. 2 is an image diagram showing an example of a screen of the communication terminal according to the first embodiment. FIG. 2 is a block diagram illustrating a configuration of a communication terminal according to the first embodiment. FIG. 11 is an image diagram showing a sanitary product input/output history and a start/end score determination table according to the second embodiment. FIG. 11 is an image diagram showing the transition of points earned from using sanitary products according to the second embodiment. FIG. 11 is an image diagram showing a sanitary product input/output history and a start/end score determination table according to the second embodiment. FIG. 11 is an image diagram showing the transition of points earned from using sanitary products according to the second embodiment. FIG. 11 is an image diagram showing a sanitary product input/output history and a start/end score determination table according to the second embodiment. FIG. 11 is an image diagram showing the transition of points earned from using sanitary products according to the second embodiment. 11A and 11B are image diagrams showing screen transitions of a communication terminal according to a third embodiment. 13 is a flowchart illustrating information processing by a server according to a third embodiment; FIG. 13 is an image diagram showing an example of a screen of a communication terminal according to the fourth embodiment. 13 is a flowchart illustrating information processing by a server according to a fourth embodiment; 13A and 13B are image diagrams showing screen transitions of a communication terminal according to a fourth embodiment. 13 is a flowchart illustrating information processing by a server according to a fourth embodiment; 13 is a flowchart illustrating information processing by a server according to a fourth embodiment; FIG. 13 is an image diagram showing an example of a screen of a communication terminal according to a fifth embodiment. FIG. 13 is an image diagram showing an example of a screen of a communication terminal according to a fifth embodiment. FIG. 13 is an image diagram showing an example of a screen of a communication terminal according to a fifth embodiment. FIG. 13 is a conceptual diagram showing prediction data according to the fifth embodiment. 13 is a flowchart illustrating information processing by a server according to a sixth embodiment; FIG. 13 is a conceptual diagram illustrating an overall configuration of a network system according to a seventh embodiment. 22 is a flowchart illustrating information processing by a server according to a ninth embodiment;

Hereinafter, an embodiment of the present invention will be described with reference to the drawings. In the following description, the same components are denoted by the same reference numerals. The names and functions of the components are also the same. Therefore, detailed description thereof will not be repeated.
First Embodiment
<Overall Configuration and Operational Overview of Network System 1>

First, the overall configuration of the network system 1 according to this embodiment will be described with reference to Figure 1. The network system 1 according to this embodiment is mainly composed of a storage device 200, a server 100, and a communication terminal 300.

The storage device 200 stores sanitary products, measures their weight, and transmits the measurement results to the server 100. In this embodiment, the storage device 200 is composed of a case unit 201 that stores sanitary products by type, and a device unit 205. In this embodiment, the case unit 201 is provided with a first case 201A that stores sanitary products for use when bleeding is light, a second case 201B that stores sanitary products for use when bleeding is heavy, and a third case 201C that stores sanitary products to be used while sleeping. Note that cases for multiple types of sanitary products with different uses or functions may be provided, not limited to types corresponding to different bleeding amounts.

The server 100 can communicate with the storage device 200 and the communication terminal 300 via the Internet or other means. The server 100 manages the number of sanitary products used by the user of the storage device 200 based on the remaining amount of sanitary products obtained from the storage device 200. This allows the server 100 to identify the start date and end date of past periods and the amount of blood loss in the past, calculate the menstrual cycle, predict the start date and end date of future periods and the amount of blood loss in the future, and send this information to the user's communication terminal 300.

The communication terminal 300 may be realized by a smartphone, tablet, personal computer, wearable device, or the like. Based on data from the server 100, the communication terminal 300 displays the remaining amount of each type of sanitary product in the storage device 200, as shown in FIG. 2. Based on data from the server 100, the communication terminal 300 also displays the past usage history of sanitary products, as shown in FIG. 3. As described below, the communication terminal 300 may also display the start date and end date of past menstruation and the amount of past blood loss, the menstrual cycle, and the start date and end date of future menstruation and the amount of blood loss, based on data from the server 100.

The detailed configuration of the network system 1 for realizing such functions will be described below.
<Configuration of storage device 200>

First, referring to Figure 4, we will explain one aspect of the configuration of the storage device 200 that makes up the network system 1. As mentioned above, the storage device 200 is composed of a case unit 201 that stores sanitary products by type, and a device unit 205. The configuration of the device unit 205 will be explained below.

The storage device 200 mainly includes an MCU (Micro Controller Unit) 210, memory 220, weight sensors 231, 232, and 233, a timer 250, a communication interface 260, a light 270, and a speaker 280.

The MCU 210 controls each part of the storage device 200 by executing programs stored in storage media such as ROM and RAM.

Memory 220 is realized by various types of RAM, ROM, etc., and stores programs executed by MCU 210, data generated by program execution by MCU 210, data measured by weight sensors 231, 232, and 233 and its history, and other information necessary to use this service.

Weight sensor 231 is realized by a load cell or the like and measures the weight of case 201A, which stores sanitary products. Weight sensor 232 is realized by a load cell or the like and measures the weight of case 201B, which stores sanitary products. Weight sensor 233 is realized by a load cell or the like and measures the weight of case 201C, which stores sanitary products.

The timer 250 measures the current time and the elapsed time from a specified timing and inputs this information to the MCU 210.

The communication interface 260 exchanges data with the server 100 via a router or the Internet. The communication interface 260 may also exchange data with the communication terminal 300 using Wi-Fi communication or Bluetooth communication.

The light 270 emits light based on instructions from the MCU 210. For example, it emits a warning light to indicate that the remaining amount is low, to notify that it is time to use sanitary products, or to indicate that the specified amount of sanitary products has not been consumed.

The speaker 280 emits sounds based on instructions from the MCU 210. For example, the speaker 280 emits sounds to warn that the remaining amount is low, that it is time to use sanitary products, or that the specified amount of sanitary products has not been consumed.
<Configuration of Server 100>

Next, we will explain one aspect of the configuration of the server 100 that constitutes the network system 1 according to this embodiment. Referring to Figure 5, the server 100 includes, as its main components, a CPU (Central Processing Unit) 110, a memory 120, an operation unit 140, and a communication interface 160.

The CPU 110 controls each part of the server 100 by executing programs stored in the memory 120. For example, the CPU 110 executes programs stored in the memory 120 and performs various processes described below by referencing various data.

Memory 120 is realized by various types of RAM (Random Access Memory), various types of ROM (Read-Only Memory), etc., and may be included in server 100, may be detachable from various interfaces of server 100, or may be a recording medium of another device accessible from server 100. Memory 120 stores programs executed by CPU 110, data generated by execution of programs by CPU 110, input data, and other databases used in the services according to this embodiment.

Memory 120 stores user data 121 as shown in Figure 6. For each user, user data 121 includes correspondence between the user's identification information, the identification information of the storage device 200 used, the user's name, age, weight, height, average menstrual cycle, other sanitary product information (such as information on sanitary products (such as shorts) used by the user but not measured by the storage device 200), medication information, supplement information, disease information, body fat percentage, etc.

The memory 120 stores usage history data 122 as shown in Figure 7. Usage history data 122 is prepared for each storage device 200. Each time data is received from the storage device 200, the usage history data 122 stores the date and time the data was acquired, the remaining amount of each type of sanitary product, the type of sanitary product used, and the number of sanitary products used.

Memory 120 stores physiological information data 123 as shown in Figure 8. Physiological information data 123 is prepared for each user, i.e., for each storage device 200. Physiological information data 123 stores a history of past menstrual start dates, a history of past menstrual end dates, the amount of blood flow in the past, the type of sanitary products used, a history of points, and past menstrual cycles. From this data, CPU 110 can calculate the average menstrual cycle value, the predicted start date of the next menstrual period, the predicted end date of the next menstrual period, the amount of blood flow, etc.

Returning to Figure 5, the operation unit 140 accepts commands from the service administrator, operator, service technician, etc., and inputs those commands to the CPU 110.

The communication interface 160 transmits data from the CPU 110 to the storage equipment 200, the communication terminal 300, and other devices via the Internet, a carrier network, a router, etc. Conversely, the communication interface 160 receives data from the storage equipment 200, the communication terminal 300, and other devices via the Internet, a carrier network, a router, etc., and passes the data to the CPU 110.
<Information Processing of Server 100>

Next, we will explain the information processing in the server 100 according to this embodiment. The CPU 110 of the server 100 executes the following processing in accordance with the program in the memory 120.

Referring to Figure 9, the CPU 110 receives data from the storage device 200 via the communication interface 160 (step S102).

The CPU 110 reads the device ID from the received data and identifies the corresponding user (step S104).

The CPU 110 reads the weight of each type of sanitary product from the received data and stores it in the usage history data 122. The CPU 110 calculates the number of items used for each type from the difference between the previous weight and the current weight for each type and the weight of each item of sanitary product for each type, and stores this in the usage history data 122 (step S106). If the weight of any sanitary product has increased, the CPU 110 assumes that the sanitary product has been replenished and stores the latest weight in the usage history data 122.

If the conditions for the start of menstruation are met (YES in step S108), the CPU 110 stores today as the start date of menstruation in the menstrual information data 123 (step S110).

More specifically, as shown in Figures 10 and 11, in this embodiment, if a sanitary product is used after a first predetermined number of days, such as 10 days, without the use of the sanitary product continues, the CPU 110 identifies the day of use as the start of menstruation.

The CPU 110 reads the start date of the previous period from the physiological information data 123 and stores the period from the start date of the previous period to the start date of the current period as the current menstrual cycle in the physiological information data 123 (step S112).

The CPU 110 calculates the average value of the menstrual cycle to date and updates the average cycle in the user data 121 (step S114).

The CPU 110 transmits information indicating the remaining amount of each type of sanitary product, information indicating the start date of the current period, the menstrual cycle, etc. to the communication terminal 300 via the communication interface 160 (step S116). As a result, the communication terminal 300 can display information indicating the start date of the current period, as shown in Figure 12.

If the conditions for menstruation start are not met (NO in step S108), the CPU 110 determines whether the conditions for menstruation end are met (step S122). If the conditions for menstruation end are met (YES in step S122), the CPU 110 stores today as the menstruation end date in the menstruation information data 123 (step S124).

For example, as shown in Figures 10 and 11, in this embodiment, the CPU 110 determines that a day has passed since the last day of menstrual use when no menstrual products have been used for a whole day after a second predetermined number of consecutive days, such as three days, has passed since the last day of menstrual use. More specifically, as shown in Figures 10 and 11, the number of sanitary products used is accumulated each day, and the day when the number of sanitary products used reaches one or more is recognized as the start day of menstruation, and the day when the number of sanitary products used reaches zero is recognized as the end day of menstruation.

The CPU 110 transmits information indicating the remaining amount of each type of sanitary product, information indicating the end date of the period, the menstrual cycle, etc. to the communication terminal 300 via the communication interface 160 (step S126). As a result, the communication terminal 300 can display information indicating the end date of the current period, as shown in Figure 13.

If the condition for the end of menstruation is not met (NO in step S122), CPU 110 executes other processes (step S130).
<Configuration of communication terminal 300>

With reference to Figure 14, one embodiment of the configuration of a communication terminal 300 for a user who uses the sanitary product and storage device 200 will be described. For example, the communication terminal 300 includes, as its main components, a CPU 310, memory 320, display 330, operation unit 340, communication interface 360, speaker 370, and microphone 380.

The CPU 310 controls each part of the communication terminal 300 by executing programs stored in the memory 320.

Memory 320 is realized by various types of RAM, various types of ROM, etc. Memory 320 stores application programs for various services, data generated by program execution by CPU 310, data received from server 100, data input via operation unit 340, information for identifying the user of communication terminal 300, etc.

The display 330 displays images and text based on data from the CPU 310. The operation unit 340 is composed of a pointing device, switches, etc., and inputs various commands from the user to the CPU 310. The communication terminal 300 may also have a touch panel 350 that includes the display 330 and the operation unit 340.

The communication interface 360 transmits and receives data to and from other devices such as the server 100 and storage device 200 via the Internet, a carrier network, a router, etc. For example, the CPU 310 exchanges various information with other devices such as the server 100 and storage device via the communication interface 360 in accordance with a web browser application program or a dedicated service application program.

The speaker 370 outputs various sounds based on signals from the CPU 310. The CPU 310 may output answers received from the server 100 as audio, not just from the display 330.

The microphone 380 receives voice and inputs the voice data to the CPU 310. The CPU 310 may also receive voice messages from the user, not just the operation unit 340, and transmit the voice messages to the server 100.

For example, the CPU 310 of the communication terminal 300 receives information about the remaining amount of sanitary products from the server 100 or the storage device 200 via the communication interface 360 in accordance with the application program in the memory 320, and displays the information on the display 330 as shown in Fig. 2. The CPU 310 also displays information such as the menstrual start date, menstrual end date, menstrual cycle, blood loss, and type of sanitary product used on the display 330 based on the information from the server 100 or the storage device 200 via the communication interface 360 in accordance with the application program in the memory 320, as shown in Figs.
Second Embodiment

In the above embodiment, the day on which sanitary products were removed from the storage device 200 was recognized as the start date of menstruation, and the day on which sanitary products were not removed from the storage device 200 was recognized as the end date of menstruation. However, removing sanitary products from the storage device 200 does not necessarily mean that menstruation has started, and not removing sanitary products from the storage device 200 does not necessarily mean that menstruation has ended.

In this embodiment, referring to Figures 15 and 16, the CPU 110 of the server 100 counts points each time a sanitary product is taken out, and recognizes the day when the points reach a predetermined number or more as the start of menstruation, and recognizes the day when the points reach a predetermined number or less as the end of menstruation. More specifically, as shown in Figures 15 and 16, the CPU 110 accumulates sanitary product usage points each day, and recognizes the day when the points reach 3 or more as the start of menstruation, and the day when the points reach 2 or less as the end of menstruation.

In this case, it is preferable that the CPU 110 determine the amount of blood loss based on the points for the sanitary products used for each day during the menstrual period and store this amount of blood loss in the physiological information data 123. However, the CPU 110 may also determine the amount of blood loss based on the points for the sanitary products used for the entire menstrual period and store this amount of blood loss in the physiological information data 123.

Furthermore, it is preferable that different points be awarded for each type of sanitary product. For example, 2 points are assigned to sanitary products for light days, and 3 points are assigned to sanitary products for heavy days. Referring to Figures 17 and 18, the CPU 110 of the server 100 counts the points for that type of sanitary product each time the product is taken out, and recognizes the start of menstruation when the points reach a predetermined number or more within a day, and recognizes the end of menstruation when the points fall below the predetermined number within a day. More specifically, as shown in Figures 17 and 18, the CPU 110 accumulates the points for use of the sanitary product each day, and recognizes the day when the points reach 4 or more as the start of menstruation, and the day when the points reach 2 or less as the end of menstruation.

In this case, too, it is preferable that the CPU 110 determine the amount of blood loss based on the points for the sanitary products used for each day during the menstrual period and store that amount of blood loss in the physiological information data 123. However, the CPU 110 may also determine the amount of blood loss based on the points for the sanitary products used for the entire menstrual period and store that amount of blood loss in the physiological information data 123.

Alternatively, 1 point is set for sanitary products for light days, 2 points for sanitary products for normal days, and 3 points for sanitary products for heavy days. Referring to Figures 19 and 20, the CPU 110 of the server 100 counts the points for that type of sanitary product each time the product is taken out, and recognizes it as the start of menstruation if the points reach a predetermined number or more in one day, and recognizes it as the end of menstruation if the points fall below a predetermined number in one day. More specifically, as shown in Figures 19 and 20, the CPU 110 accumulates the points for sanitary products used each day, and recognizes the day when the points reach 4 or more as the start of menstruation, and the day when the points reach 2 or less as the end of menstruation.

In this case, too, it is preferable that the CPU 110 determine the amount of blood loss based on the points for the sanitary products used for each day during the menstrual period and store that amount of blood loss in the physiological information data 123. However, the CPU 110 may also determine the amount of blood loss based on the points for the sanitary products used for the entire menstrual period and store that amount of blood loss in the physiological information data 123.

In addition, the server 100 can select from many methods for specifying the start and end dates of menstruation. For example, the server 100 can adopt a rule that if the days of use are consecutive, the first day of use is recognized as the start date, or if there is a day of use but no use on the following day, it is not recognized as the start date.
Third Embodiment

In addition to the functionality of the above embodiment, the user can also modify the start and end dates of past periods identified by the service via the communication terminal 300. For example, as shown in FIG. 21, the user can modify the start date of their period by touching the displayed start date of their period and dragging it to the correct date.

More specifically, in this embodiment, the CPU 110 of the server 100 transmits the start date and end date of the menstrual period to the communication terminal 300 via the communication interface 160, and then executes the following processing based on the data from the communication terminal 300.

Referring to FIG. 22, the CPU 110 receives data from the communication terminal 300 via the communication interface 160 (step S302).

The CPU 110 reads the user ID from the data from the communication terminal 300 (step S304).

The CPU 110 reads instructions to correct the start and end dates of the period from the data sent from the communication terminal 300 (step S306).

The CPU 110 corrects or updates the physiological information data 123 based on the correction instruction (step S308).

In particular, in this embodiment, if the start or end date of menstruation is modified, the CPU 110 changes the rules for determining the start or end date of menstruation for the target user (step S310).

For example, if the start date of menstruation is corrected to a later date, the CPU 110 corrects the threshold value and points used to determine the start date of menstruation to a higher value. Conversely, if the start date of menstruation is corrected to an earlier day, the CPU 110 corrects the threshold value and points used to determine the start date of menstruation to a lower value. Also, if the end date of menstruation is corrected to a later date, the CPU 110 corrects the threshold value and points used to determine the end date of menstruation to a lower value. Conversely, if the end date of menstruation is corrected to an earlier day, the CPU 110 corrects the threshold value and points used to determine the end date of menstruation to a higher value.

Alternatively, if frequent adjustments are made, the CPU 110 may be modified to determine the start date and end date of menstruation based on the time of use of sanitary products, the length of time between uses of sanitary products, or whether or not a specific sanitary product is used.
<Fourth embodiment>

Furthermore, in addition to the functions of the above-described embodiment, it is preferable that the server 100 presents the types of sanitary products to the communication terminal 300 in the order in which they were used. For example, as shown in FIG. 23, the communication terminal 300 presents the types of sanitary products for each day in the order in which they were used, based on information from the server 100. For example, on the 12th, an icon for a small sanitary product and an icon for a medium sanitary product are displayed from top to bottom. On the 13th, no sanitary product was used. On the 14th, an icon for a medium sanitary product and an icon for a nighttime sanitary product are displayed from top to bottom. On the 15th, an icon for a medium sanitary product, an icon for a medium sanitary product, an icon for a medium sanitary product, and an icon for a nighttime sanitary product are displayed from top to bottom.

In this embodiment, the CPU 110 of the server 100 executes the process shown in Figure 24.

The CPU 110 receives data from the communication terminal 300 via the communication interface 160 (step S402).

The CPU 110 reads the user ID from the data from the communication terminal 300 and identifies the ID of the storage device based on the user data 121 (step S404).

The CPU 110 references the usage history data 122 and reads the daily usage history of sanitary products from the start date of the most recent menstruation (step S406).

The CPU 110 transmits the daily sanitary product usage history from the most recent start date of menstruation to the communication terminal 300 via the communication interface 160 (step S408). Based on the data from the server 100, the CPU 310 of the communication terminal 300 then displays on the display 330 icons indicating the types of sanitary products used in the order they were used for each day since the start date of menstruation.

The user may be able to input the relationship between the sanitary product actually used and the amount of blood loss. This increases the likelihood that more appropriate sanitary products can be suggested to the user in the future. For example, as shown in the left diagram of FIG. 25, the CPU 310 of the communication terminal 300 displays icons of sanitary products in the order in which they were used on the display 330. As shown in the center diagram of FIG. 25, the user taps the icon of the sanitary product they wish to modify. In other words, the CPU 310 accepts user operation via the operation unit 340, i.e., a selection command as to whether the size of the sanitary product was appropriate, i.e., whether the capacity of the sanitary product was too small, just right, or too large, or whether there was no bleeding. The CPU 310 transmits the feedback results to the server 100 via the communication interface 360, and also changes the display of the icon of the inappropriate sanitary product on the display 330, as shown in the right diagram of FIG. 25.

Referring to FIG. 26, the CPU 110 receives data from the communication terminal 300 via the communication interface 160 (step S412).

The CPU 110 reads the user ID from the data from the communication terminal 300 and identifies the storage device ID by referencing the user data 121 (step S414).

The CPU 110 reads feedback on the specified date, the specified order, and the specified type of sanitary product from the data received from the communication terminal 300 (step S416).

The CPU 110 corrects or updates the usage history data 122 based on the feedback (step S418). More specifically, if the capacity of the sanitary product is too small, the CPU 110 corrects the data to increase the size of the sanitary product, and if the capacity is too large, the CPU 110 corrects the data to decrease the size of the sanitary product. It is preferable to set a correction flag for corrected history.

Note that, while the system receives a selection command to indicate whether the volume of the sanitary product was too small, just right, too large, or whether there was no bleeding, the communication terminal 300 may also receive input of the appropriate type of sanitary product itself as feedback and transmit this to the server 100.

Alternatively, the user may simply be able to modify the type of sanitary product identified by the server 100. This is because the server 100 may mistakenly recognize the sanitary product used. For example, as shown in FIG. 23, with icons of sanitary products displayed on the communication terminal 300, the user presses and holds the icon of the sanitary product they wish to modify. The communication terminal 300 displays icons of multiple types of sanitary products so that they can be selected. Based on the selection command, the communication terminal 300 sends a command to the server 100 to modify the sanitary product to the icon selected by the user.

Referring to FIG. 27, the CPU 110 receives data from the communication terminal 300 via the communication interface 160 (step S422).

The CPU 110 reads the user ID from the data from the communication terminal 300 and identifies the storage device ID by referencing the user data 121 (step S424).

The CPU 110 reads correction instructions, including the specified date, specified order, and specified type of sanitary product, from the data from the communication terminal 300 (step S426).

Based on the correction instruction, the CPU 110 corrects or updates the usage history data 122 (step S428).
Fifth Embodiment

In addition to the functions of the above embodiments, it is preferable that the server 100 presents to the user, via the communication terminal 300, the start and end dates of the next period, the planned use of sanitary products during the period, and a predicted daily blood loss during the period, based on the user's past sanitary product use history. For example, as shown in FIG. 28, the communication terminal 300 displays a daily predicted sanitary product use for the entire next period based on information from the server 100. Alternatively, as shown in FIG. 29, the communication terminal 300 displays, based on information from the server 100, solid line icons indicating the sanitary product use history for days that have already passed and dotted line icons indicating predicted sanitary product use for the current day, the next day, or the next 24 hours. Alternatively, as shown in FIG. 30, the communication terminal 300 displays, based on information from the server 100, solid line icons indicating the sanitary product use history for days that have already passed and dotted line icons indicating predicted sanitary product use for each day until the end of the period.

In this embodiment, the memory 120 of the server 100 stores prediction data 124. As shown in FIG. 31, the prediction data 124 stores, for each user, the menstrual cycle, the start date of the next period, the end date of the next period, the average order in which sanitary products are used each day during the menstrual period, and the average amount of blood loss each day during the menstrual period.

When the sanitary product usage history data 122 is updated, such as when a sanitary product is used, when feedback is received regarding the sanitary product used, when the sanitary product used is modified, or when the start or end date of the period is modified, the CPU 110 of the server 100 calculates the menstrual cycle, the start date of the next period, the end date of the next period, the average order in which sanitary products are used each day during the period, and the average daily blood loss during the period based on each user's sanitary product usage history, and updates the prediction data 124.

When the CPU 110 receives a request from the communication terminal 300, it transmits information indicating the menstrual cycle, the start date of the next period, the end date of the next period, the average order of sanitary product use each day during the menstrual period, and the average daily blood loss during the menstrual period for the user corresponding to the communication terminal 300 via the communication interface 160 to the communication terminal 300. As a result, the CPU 310 of the communication terminal 300 displays the screens shown in Figures 28, 29, and 30 on the display 330 based on the information from the server 100.

However, the server 100 may also present the user with the start and end dates of their next period, their planned use of sanitary products during their period, and a predicted daily blood loss during their period via the communication terminal 300, based on the past sanitary product usage history of not only the user but also other users of the same age and build as the user. In this case, when the sanitary product usage history data 122 is updated, such as when a sanitary product is used, when feedback is received regarding the sanitary product used, when the sanitary product used is modified, or when the start and end dates of the period are modified, the CPU 110 of the server 100 calculates the menstrual cycle, the start and end dates of the next period, the average daily order of sanitary product use during their period, and a predicted average daily blood loss during their period based on the sanitary product usage history of multiple users with the same attributes as the user, and updates the prediction data 124.

Then, when CPU 110 receives a request from communication terminal 300, it transmits information indicating the menstrual cycle, the start date of the next menstruation, the end date of the next menstruation, the average order of use of sanitary products each day during the menstrual period, and the average daily blood loss during the menstrual period, related to the user corresponding to communication terminal 300, to communication terminal 300 via communication interface 160. As a result, CPU 310 of communication terminal 300 causes the display 330 to display the screens shown in Figures 28, 29, and 30 based on the information from server 100.
Sixth Embodiment

In addition to the functions of the above embodiments, the server 100 may, for each user, based on the sanitary product usage history, if significantly different data is obtained from the past sanitary product usage history, notify the user or a designated hospital, doctor, clinic, etc.

More specifically, as shown in FIG. 32, when the sanitary product usage history data 122 is updated (step S602), such as when a sanitary product is used, when feedback is received regarding the sanitary product used, when the sanitary product used is modified, or when the start or end date of menstruation is modified, the CPU 110 of the server 100 determines whether the amount of sanitary product used has increased significantly (step S604) based on the sanitary product usage history for each user. For example, it determines whether the sanitary product usage points have increased by 3 points or more.

If the amount of sanitary products used has increased significantly (YES in step S604), the CPU 110 notifies the user's communication terminal 300 or the terminal of a designated expert via the communication interface 160 that the user's sanitary product use has increased dramatically (step S606).

If, based on the user's sanitary product usage history, the amount of sanitary product usage has not increased significantly (step S604), the CPU 110 determines whether the amount of sanitary product usage has decreased significantly (step S608). For example, it determines whether the points for sanitary products have decreased by 3 or more points.

If the amount of sanitary products used has decreased significantly (YES in step S608), the CPU 110 notifies the user's communication terminal 300 or the terminal of a designated expert via the communication interface 160 that the user's sanitary product use has decreased dramatically (step S610).

However, the CPU 110 of the server 100 may compare the user's past sanitary product usage history with that of another user based on the user's sanitary product usage history, and if significantly different data is obtained, the CPU 110 may notify the user or a designated hospital, doctor, clinic, etc. of this fact.
Seventh Embodiment

In addition to the functions of the above-described embodiment, as shown in FIG. 33, when a type of sanitary product is about to run out, the server 100 may automatically order that type from an e-commerce site or sanitary product company, or request permission to place an order from the user's communication terminal 300, based on the remaining amount of sanitary products in the storage device 200 and the user's predicted sanitary product usage.

When the sanitary product usage history data 122 is updated, such as when a sanitary product is used, when feedback is received regarding the sanitary product used, when the sanitary product used is modified, when the start or end date of the period is modified, or when the end date of the period is confirmed, the CPU 110 of the server 100 calculates the number of each type of sanitary product expected to be consumed during the next period based on each user's sanitary product usage history. If this number is less than the remaining amount in the storage device 200, the CPU 110 automatically places an order for that type of sanitary product from an e-commerce site or sanitary product company via the communication interface 160, or requests permission to place an order from the user's communication terminal 300.

Alternatively, the memory 120 of the server 100 stores the storage capacity of each type for each storage device 200. The memory 120 also stores the number of units per sales unit for each type of sanitary product. When a sanitary product is used, when feedback is received regarding the sanitary product used, when the sanitary product used is modified, when the menstrual start or end date is modified, or when the sanitary product usage history data 122 is updated, the CPU 110 automatically places an order for that type of sanitary product from an e-commerce site or a sanitary product company via the communication interface 160, or requests permission to place an order from the user's communication terminal 300, based on the remaining amount and storage capacity of the storage device 200, if the storage capacity is greater than the number of units per sales unit of the sanitary product. This allows the storage device 200 to store sanitary products with a surplus, reducing the possibility of users rushing to purchase products during disasters or shortages.
Eighth Embodiment

In the above embodiment, the storage device 200 measures the weight of each type of sanitary product and transmits the measurement results to the server 100, which then obtains the number of sanitary products used for each type. However, this is not limited to this embodiment.

The storage device 200 may measure the distance to the top of the sanitary product by irradiating light from the bottom surface of the top lid. The CPU 110 of the server 100 may then calculate the number of sanitary products used for each type based on changes in this distance.

In addition, the storage device 200 may use ultrasound or take images to have the server 100 calculate the number of sanitary products used; the method for obtaining the number of sanitary products used is not particularly limited.

In the above embodiment, the storage device 200 has a storage space for each type of sanitary product, and transmits measurement results for each type to the server 100. However, the storage device 200 may also stock multiple types of sanitary products in a single storage space. In this case, the CPU 110 of the server 100 will identify the type of sanitary product used based on the weight, distance, camera images, etc. from the storage device 200.

In the above embodiment, the storage device 200 transmits the measurement results to the server 100, and the CPU 110 of the server 100 acquires the number of sanitary products used. However, the CPU 210 of the storage device 200 may identify the type and number of sanitary products used based on the measurement results of the weight sensors 231, 232, 233 or other sensors. In other words, the storage device 200 may transmit the type and number of sanitary products used to the server 100 via the communication interface 160.
Ninth Embodiment

Some or all of the roles of each device in the network system 1 of the above embodiment may be performed by other devices. For example, the role of the server 100 may be performed by multiple devices on the cloud, or by the communication terminal 300. More specifically, various data may be sent from the storage device 200 directly to the communication terminal 300 via Wi-Fi (registered trademark) or Bluetooth (registered trademark) without going through the server 100.

In this case, the CPU 310 of the communication terminal 300 executes the following process in accordance with the program in the memory 320. Note that in this case, the memory 320 stores the user's usage history data 122 and physiological information data 123 only. However, such data may also be stored on the cloud.

Referring to FIG. 34, the CPU 310 receives data from the storage device 200 via the communication interface 360 (step S502).

The CPU 310 reads the weight of each type of sanitary product from the received data and stores it in the usage history data 122. The CPU 310 calculates the number of sanitary products used for each type from the difference between the previous weight and the current weight for each type and the weight of each sanitary product for each type, and stores this in the usage history data 122 (step S506). Note that if the weight for each type has increased, the CPU 110 assumes that the sanitary products have been replenished and stores the latest weight in the usage history data 122.

If the conditions for the start of menstruation are met (YES in step S508), the CPU 310 stores today as the start date of menstruation in the menstrual information data 123 (step S510).

More specifically, as shown in Figures 19 and 20, in this embodiment, if a day on which sanitary products are not used continues for a first predetermined number of days, such as 10 days, and the sanitary product usage points are equal to or greater than a first predetermined value, the CPU 310 identifies that day as the start of menstruation.

The CPU 310 reads the start date of the previous period from the physiological information data 123 and stores the period from the start date of the previous period to the start date of the current period as the current menstrual cycle in the physiological information data 123 (step S512).

The CPU 310 calculates the average value of the menstrual cycle up to that point and updates the average cycle in the menstrual information data 123 (step S514).

As shown in FIG. 12, the CPU 310 displays on the display 530 information indicating the remaining amount of sanitary products by type, information indicating the start date of menstruation, information indicating the menstrual cycle, etc. (step S516).

If the conditions for menstruation start are not met (NO in step S508), the CPU 310 determines whether the conditions for menstruation end are met (step S522). If the conditions for menstruation end are met (YES in step S522), the CPU 310 stores today as the menstruation end date in the menstruation information data 123 (step S524).

For example, as shown in Figures 19 and 20, in this embodiment, the CPU 310 determines that a period has ended when sanitary products have not been used for 24 hours or more after a second predetermined number of consecutive days, such as three days, have passed. More specifically, as shown in Figures 19 and 20, the number of sanitary products used is accumulated each day, and the day on which the sanitary product usage points fall below a second predetermined value is recognized as the day on which the period ended.

As shown in FIG. 13, the CPU 310 displays information indicating the remaining amount of sanitary products by type, information indicating the end date of menstruation, menstrual cycle, etc. on the display 330 (step S526).

If the condition for the end of menstruation is not met (NO in step S522), the CPU 310 performs other processing (step S530).

Additionally, similar to the server 100 of the above embodiment, the communication terminal 300 may predict a future start date, predict the order in which sanitary products will be used, and display this information.
<Summary>

In the above embodiment, a network system is provided that includes a storage device for storing sanitary products, a communication terminal used by a user, and a server that accumulates the sanitary product usage history of each user based on data from the storage device and presents to the communication terminal at least the type of sanitary product that is likely to be used next.

Preferably, the server presents to the communication terminal at least one day's worth of types of sanitary products that are likely to be used.

Preferably, the communication terminal accepts input regarding the relationship between the amount of blood loss and the sanitary product used, or the type of sanitary product that should actually be used, and transmits this information to the server. The server then accumulates a sanitary product usage history based on the information.

Preferably, when the server detects, based on data from the storage device, that usage of sanitary products differs from the user's average usage history, it notifies the communication terminal of this.

Preferably, when the server detects, based on data from the storage device, that the usage history of sanitary products differs from the average usage history of other users, it notifies the communication terminal of this.

Preferably, the server identifies at least the type of sanitary product that is likely to be used next based not only on the target user's sanitary product usage history, but also on the sanitary product usage history of multiple other users.

Preferably, the server orders new sanitary products when all of the newly purchased sanitary products can be stored in the storage device based on the storage capacity of the storage device.

Preferably, the server orders new sanitary products when the number of sanitary products remaining in the storage device is less than the number of sanitary products to be used within the next menstrual period.

Preferably, a program for a communication terminal is provided that causes a processor of the communication terminal to execute the steps of accumulating a usage history of sanitary products for each user based on data from the storage device, and identifying at least the type of sanitary product that is likely to be used next and displaying it on a display.

The embodiments disclosed herein should be considered in all respects to be illustrative and not restrictive. The scope of the present invention is indicated by the claims, not the above description, and is intended to include all modifications that are equivalent in meaning to and within the scope of the claims.

1: Network system 100: Server 110: CPU
120: Memory 121: User data 122: Usage history data 123: Physiological information data 124: Prediction data 140: Operation unit 160: Communication interface 200: Storage device 201: Case unit 201A: First case 201B: Second case 201C: Third case 205: Device unit 210: CPU
220: Memory 231: Weight sensor 232: Weight sensor 233: Weight sensor 250: Timer 260: Communication interface 270: Light 280: Speaker 300: Communication terminal 310: CPU
320: Memory 330: Display 340: Operation unit 350: Touch panel 360: Communication interface 370: Speaker 380: Microphone 530: Display

Claims (7)

a storage device capable of storing a plurality of types of sanitary products, the storage device being configured to transmit data including weights of the plurality of types of sanitary products or distances from a bottom surface of an upper cover of the storage device to the top ends of the plurality of types of sanitary products;
a communication terminal used by a user;
a server that accumulates a usage history of multiple types of sanitary products for each user based on a difference between the previous data and the current data sent from the storage device and data including the weight or thickness of each type of sanitary product, and that presents to the communication terminal the type of sanitary product that is likely to be used next based on the usage history;
When the server detects, based on the data from the storage device, that the user's sanitary product usage history differs from the user's average sanitary product usage history, the server notifies the communication terminal of this. a storage device capable of storing a plurality of types of sanitary products, the storage device being configured to transmit data including weights of the plurality of types of sanitary products or distances from a bottom surface of an upper cover of the storage device to the top ends of the plurality of types of sanitary products;
a communication terminal used by a user;
a server that accumulates a usage history of multiple types of sanitary products for each user based on a difference between the previous data and the current data sent from the storage device and data including the weight or thickness of each type of sanitary product, and that presents to the communication terminal the type of sanitary product that is likely to be used next based on the usage history;
When the server detects, based on the data from the storage device, that the sanitary product usage history differs from the average usage history of other multiple users, it notifies the communication terminal of this fact. a storage device capable of storing a plurality of types of sanitary products, the storage device being configured to transmit data including weights of the plurality of types of sanitary products or distances from a bottom surface of an upper cover of the storage device to the top ends of the plurality of types of sanitary products;
a communication terminal used by a user;
a server that accumulates a usage history of multiple types of sanitary products for each user based on a difference between the previous data and the current data sent from the storage device and data including the weight or thickness of each type of sanitary product, and that presents to the communication terminal the type of sanitary product that is likely to be used next based on the usage history;
The server orders new sanitary products when all of the newly purchased sanitary products can be stored in the storage device based on the storage capacity of the storage device. The network system described in any one of claims 1 to 3, wherein the server presents to the communication terminal at least one day's worth of types of sanitary products that are likely to be used. The communication terminal receives an input of the relationship between the amount of blood loss and the sanitary product used, or an input of the type of sanitary product to be actually used, and transmits the information to a server;
The network system according to claim 1 , wherein the server accumulates a usage history of the sanitary product based on the information. The network system according to any one of claims 1 to 5, wherein the server identifies the type of sanitary product that is likely to be used next based not only on the target user's sanitary product use history but also on the sanitary product use history of multiple other users. 7. The network system according to claim 1, wherein the server orders new sanitary products when the number of sanitary products remaining in the storage device is less than the number of sanitary products to be used within the next menstrual period.