Network systems, servers, and programs

Abstract

To provide a network system capable of automatically identifying a start date of menstruation based on the history of use of sanitary products.SOLUTION: A network system 1 includes: a storage device 200 for storing sanitary products; a server 100 for identifying a start date of a user's menstruation by identifying the number of used sanitary products based on data from the storage device; and a communication terminal 300 that displays the start date of the user's menstruation based on data from the server, receives an instruction to correct the start date of the menstruation, and transmits the instruction to the server.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to a useful information processing technology relating to consumption of sanitary products. [Background technology]

[0002] Conventionally, there have been known techniques for predicting menstrual cycles by measuring basal body temperature, etc. For example, such techniques are disclosed in Japanese Patent Laid-Open Publication No. 63-135144 (Patent Document 1) and Japanese Patent Laid-Open Publication No. 62-183807. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Publication No. 63-135144 [Patent Document 2] Japanese Patent Application Publication No. 183807 / 1983 Summary of the Invention [Problem to be solved by the invention]

[0004] An object of the present invention is to provide a network system that can automatically identify the start date of menstruation based on the usage history of sanitary products. [Means for solving the problem]

[0005] According to one aspect of the present invention, there is provided a network system comprising: a storage device for storing sanitary products; a server that identifies the start date of a user's period by determining the number of sanitary products used based on data from the storage device; and a communications terminal that displays the start date of the user's period based on the data from the server, and accepts instructions to correct the start date of the period and transmits the instructions to the server. Effect of the Invention

[0006] As described above, according to the present invention, a network system is provided that can automatically identify the start date of menstruation based on the usage history of sanitary products. [Brief description of the drawings]

[0007] [Figure 1] FIG. 1 is a conceptual diagram showing an overall configuration of a network system according to a first embodiment. [Diagram 2] FIG. 2 is an image diagram showing an example of a screen of the communication terminal according to the first embodiment. [Diagram 3] FIG. 2 is an image diagram showing an example of a screen of the communication terminal according to the first embodiment. [Figure 4] FIG. 1 is a block diagram showing a configuration of a storage device according to a first embodiment. [Diagram 5] FIG. 2 is a block diagram showing a configuration of a server according to the first embodiment. [Figure 6] FIG. 2 is a conceptual diagram showing user data according to the first embodiment. [Figure 7] FIG. 2 is an image diagram showing usage history data according to the first embodiment. [Figure 8] FIG. 2 is an image diagram showing physiological information data according to the first embodiment. [Figure 9] 6 is a flowchart showing information processing of a server according to the first embodiment; [Figure 10] FIG. 2 is an image diagram showing a sanitary product input / output history and a start / end score determination table according to the first embodiment. [Figure 11] FIG. 2 is an image diagram showing a transition of points earned from using sanitary products according to the first embodiment. [Figure 12] FIG. 2 is an image diagram showing an example of a screen of the communication terminal according to the first embodiment. [Figure 13] FIG. 2 is an image diagram showing an example of a screen of the communication terminal according to the first embodiment. [Figure 14] FIG. 2 is a block diagram showing a configuration of a communication terminal according to the first embodiment. [Figure 15]FIG. 13 is an image diagram showing the input / output history of sanitary products and a start / end score determination table according to the second embodiment. [Figure 16] FIG. 11 is an image diagram showing a transition of points earned from using sanitary products according to the second embodiment. [Figure 17] FIG. 13 is an image diagram showing the input / output history of sanitary products and a start / end score determination table according to the second embodiment. [Figure 18] FIG. 11 is an image diagram showing a transition of points earned from using sanitary products according to the second embodiment. [Figure 19] FIG. 13 is an image diagram showing the input / output history of sanitary products and a start / end score determination table according to the second embodiment. [Figure 20] FIG. 11 is an image diagram showing a transition of points earned from using sanitary products according to the second embodiment. [Figure 21] 13A to 13C are image diagrams showing screen transitions of a communication terminal according to a third embodiment. [Figure 22] 13 is a flowchart showing information processing by a server according to a third embodiment. [Diagram 23] FIG. 13 is an image diagram showing an example of a screen of a communication terminal according to a fourth embodiment. [Figure 24] 13 is a flowchart showing information processing by a server according to a fourth embodiment. [Diagram 25] 13 is an image diagram showing a screen transition of a communication terminal according to a fourth embodiment. FIG. [Figure 26] 13 is a flowchart showing information processing by a server according to a fourth embodiment. [Figure 27] 13 is a flowchart showing information processing by a server according to a fourth embodiment. [Figure 28] FIG. 13 is an image diagram showing an example of a screen of a communication terminal according to a fifth embodiment. [Figure 29] FIG. 13 is an image diagram showing an example of a screen of a communication terminal according to a fifth embodiment. [Diagram 30] FIG. 13 is an image diagram showing an example of a screen of a communication terminal according to a fifth embodiment. [Diagram 31]FIG. 13 is an image diagram showing prediction data according to the fifth embodiment. [Diagram 32] 23 is a flowchart showing information processing of a server according to the sixth embodiment. [Diagram 33] FIG. 13 is a conceptual diagram showing an overall configuration of a network system according to a seventh embodiment. [Diagram 34] 23 is a flowchart showing information processing by a server according to a ninth embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0008] 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. Their names and functions are also the same. Therefore, detailed description thereof will not be repeated. <First embodiment> <Overall configuration and operation of network system 1>

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

[0010] The storage device 200 stores sanitary products, measures the weight of the sanitary products, and transmits the measurement results to the server 100. In this embodiment, the storage device 200 is composed of a case section 201 that stores sanitary products by type, and a device section 205. In this embodiment, the case section 201 is provided with a first case 201A that stores sanitary products for when bleeding is light, a second case 201B that stores sanitary products for 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 according to different amounts of bleeding.

[0011] The server 100 can communicate with the storage device 200 and the communication terminal 300 via the Internet or the like. 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 acquired from the storage device 200. In this way, the server 100 can identify the start date and end date of a past period and the amount of blood loss in the past, calculate the menstrual cycle, predict the start date and end date of a future period and the amount of blood loss in the future, and transmit the information to the communication terminal 300 of the user.

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

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

[0014] First, referring to Fig. 4, one aspect of the configuration of the storage device 200 constituting the network system 1 will be described. As described 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 described below.

[0015] The storage device 200 includes, as main components, an MCU (Micro Controller Unit) 210, a memory 220, weight sensors 231, 232, and 233, a timer 250, a communication interface 260, a light 270, a speaker 280, and the like.

[0016] The MCU 210 controls each part of the storage equipment 200 by executing a program stored in a storage medium such as a ROM or a RAM.

[0017] The memory 220 is realized by various types of RAM, various types of ROM, etc., and stores programs executed by the MCU 210, data generated by the execution of the programs by the MCU 210, data measured by the weight sensors 231, 232, 233 and their history, and other information necessary to use this service.

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

[0019] The timer 250 measures the current time and the elapsed time from a predetermined timing, and inputs the results to the MCU 210 .

[0020] 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 WiFi communication or Bluetooth communication.

[0021] The light 270 emits light based on instructions from the MCU 210. For example, the light 270 emits a warning light to indicate that the remaining amount is low, to notify the user that a sanitary product should be used, or to indicate that a specified amount of a sanitary product has not been consumed.

[0022] The speaker 280 emits a sound based on an instruction from the MCU 210. For example, the speaker 280 emits a warning sound to indicate that the remaining amount is low, to inform the user that it is time to use the sanitary product, or to indicate that the specified amount of the sanitary product has not been consumed. <Server 100 Configuration>

[0023] Next, a configuration of server 100 constituting network system 1 according to the present embodiment will be described. Referring to Fig. 5, server 100 includes, as main components, a CPU (Central Processing Unit) 110, a memory 120, an operation unit 140, and a communication interface 160.

[0024] CPU 110 controls each unit of server 100 by executing a program stored in memory 120. For example, CPU 110 executes a program stored in memory 120 and performs various processes (described later) by referring to various data.

[0025] The 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 the server 100, may be detachable from various interfaces of the server 100, or may be a recording medium of another device accessible from the server 100. The memory 120 stores programs executed by the CPU 110, data generated by execution of programs by the CPU 110, input data, other databases used for the service according to this embodiment, and the like.

[0026] The memory 120 stores user data 121 as shown in Fig. 6. The user data 121 includes, for each user, the 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) that the user uses but that are not measured by the storage device 200), medication information, supplement information, disease information, and body fat percentage.

[0027] The memory 120 stores usage history data 122 as shown in Fig. 7. The 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 of data acquisition, the remaining amount of each type of sanitary product, the type of sanitary product used, and the number of sanitary products used.

[0028] The memory 120 stores physiological information data 123 as shown in Fig. 8. The physiological information data 123 is prepared for each user, i.e., for each storage device 200. The physiological information data 123 stores a history of the start date of a past menstruation, a history of the end date of a past menstruation, a history of the amount of blood loss in the past, the type of sanitary products used, a history of points, a past menstrual cycle, etc. From this data, the CPU 110 can calculate an average value of the menstrual cycle, a predicted start date of the next menstruation, a predicted end date of the next menstruation, a predicted amount of blood loss, etc.

[0029] Returning to FIG. 5, the operation unit 140 receives commands from a service manager, an operator, a service technician, or the like, and inputs the commands to the CPU 110.

[0030] 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 it to the CPU 110. <Information processing of server 100>

[0031] Next, a description will be given of information processing in the server 100 according to the present embodiment. The CPU 110 of the server 100 executes the following processing in accordance with the program in the memory 120.

[0032] Referring to FIG. 9, the CPU 110 receives data from the storage equipment 200 via the communication interface 160 (step S102).

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

[0034] CPU 110 reads out the weight of each type of sanitary product from the received data and stores it in usage history data 122. 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 sanitary product for each type, and stores this in usage history data 122 (step S106). If the weight of any sanitary product has increased, CPU 110 assumes that the sanitary product has been replenished and stores the latest weight in usage history data 122.

[0035] If the condition for the start of menstruation is met (YES in step S108), CPU 110 stores today as the start day of menstruation in menstruation information data 123 (step S110).

[0036] More specifically, as shown in FIG. 10 and FIG. 11, in this embodiment, when 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.

[0037] CPU 110 reads the start date of the previous menstruation from menstrual information data 123, and accumulates the period from the start date of the previous menstruation to the start date of the current menstruation as the current menstrual cycle in menstrual information data 123 (step S112).

[0038] CPU 110 calculates the average value of the menstrual cycle up to that point, and updates the average cycle in user data 121 (step S114).

[0039] 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 communication terminal 300 via communication interface 160 (step S116). As a result, as shown in Fig. 12, communication terminal 300 can display information indicating the start date of the current period.

[0040] If the condition for the start of menstruation is not met (NO in step S108), CPU 110 determines whether the condition for the end of menstruation is met (step S122). If the condition for the end of menstruation is met (YES in step S122), CPU 110 stores today as the end day of menstruation in menstrual information data 123 (step S124).

[0041] For example, as shown in Figures 10 and 11, in this embodiment, the CPU 110 determines that a day is the end of menstruation when no sanitary products are used for a whole day after a second predetermined number of days, such as three days, have passed since the day the sanitary products were used. More specifically, as shown in Figures 10 and 11, the number of sanitary products used is accumulated for each day, and the day when the number of sanitary products used reaches one or more is determined as the start day of menstruation, and the day when the number of sanitary products used reaches zero is determined as the end day of menstruation.

[0042] The CPU 110 transmits information indicating the remaining amount of each type of sanitary product, information indicating the end date of the menstrual 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 menstrual period, as shown in Fig. 13.

[0043] 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>

[0044] 14, a description will be given of one embodiment of the configuration of a communication terminal 300 of a user who uses the sanitary product and storage device 200. For example, the communication terminal 300 includes, as main components, a CPU 310, a memory 320, a display 330, an operation unit 340, a communication interface 360, a speaker 370, and a microphone 380.

[0045] The CPU 310 controls each unit of the communication terminal 300 by executing a program stored in the memory 320 .

[0046] The memory 320 is realized by various RAMs, various ROMs, etc. The memory 320 stores application programs for various services, data generated by execution of programs by the CPU 310, data received from the server 100, data input via the operation unit 340, information for identifying the user of the communication terminal 300, and the like.

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

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

[0049] The speaker 370 outputs various sounds based on signals from the CPU 310. The CPU 310 may output the answer received from the server 100 as sound, not limited to the display 330.

[0050] Microphone 380 receives voice and inputs the voice data to CPU 310. CPU 310 may receive a voice message from a user, not limited to operation unit 340, and transmit the voice message to server 100.

[0051] For example, the CPU 310 of the communication terminal 300 receives information on 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 causes the information to be displayed on the display 330 as shown in Fig. 2. The CPU 310 also causes the display 330 to display information such as the menstrual start date, menstrual end date, menstrual cycle, blood loss, and type of sanitary product used, 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. 12 and 13. <Second embodiment>

[0052] In the above embodiment, the day when the sanitary product is removed from the storage device 200 is recognized as the start date of menstruation, and the day when the sanitary product is not removed from the storage device 200 is recognized as the end date of menstruation. However, just because the sanitary product is removed from the storage device 200 does not necessarily mean that menstruation has started, and just because the sanitary product is not removed from the storage device 200 does not necessarily mean that menstruation has ended.

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

[0054] In this case, it is preferable that the CPU 110 specifies the amount of blood loss based on the points of the sanitary products used for each day during the menstrual period, and accumulates the amount of blood loss in the physiological information data 123. However, the CPU 110 may specify the amount of blood loss based on the points of the sanitary products used for the entire menstrual period, and accumulate the amount of blood loss in the physiological information data 123.

[0055] Furthermore, it is preferable that points are given differently for each type of sanitary product. For example, 2 points are set for sanitary products for light days, and 3 points are set for sanitary products for heavy days. With reference to Figs. 17 and 18, the CPU 110 of the server 100 counts the points of the sanitary product every time the sanitary product is taken out, and recognizes the day when the points reach a predetermined number or more in one day as the start day of menstruation, and recognizes the day when the points reach a predetermined number or less in one day as the end day of menstruation. More specifically, as shown in Figs. 17 and 18, the CPU 110 accumulates the usage points of the sanitary products every day, and recognizes the day when the points reach 4 or more as the start day of menstruation, and the day when the points reach 2 or less as the end day of menstruation.

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

[0057] 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. With reference to Fig. 19 and Fig. 20, the CPU 110 of the server 100 counts the points of the sanitary products every time the sanitary products are taken out, and recognizes the day when the points reach a predetermined point or more in one day as the start day of menstruation, and recognizes the day when the points reach a predetermined point or less in one day as the end day of menstruation. More specifically, as shown in Fig. 19 and Fig. 20, the CPU 110 accumulates the usage points of the sanitary products every day, and recognizes the day when the points reach 4 or more as the start day of menstruation, and the day when the usage points reach 2 or less as the end day of menstruation.

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

[0059] In addition, the server 100 can select from many methods for identifying the start and end dates of menstruation. For example, the server 100 can adopt a rule that, when the days of use are consecutive, the first day of use is recognized as the start date, or, even if there is a day of use, if there is no use on the next day, it is not recognized as the start date. <Third embodiment>

[0060] In addition to the functions of the above-described embodiment, the user can modify the start and end dates of the past period identified by the service via the communication terminal 300. For example, as shown in Fig. 21, the user can modify the start date of the period by touching the presented start date of the period and dragging it to the correct date.

[0061] More specifically, in this embodiment, the CPU 110 of the server 100 transmits the start date and end date of the menstruation 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.

[0062] 22, CPU 110 receives data from communication terminal 300 via communication interface 160 (step S302).

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

[0064] CPU 110 reads out an instruction to correct the start date and end date of menstruation from the data sent from communication terminal 300 (step S306).

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

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

[0067] For example, when the start date of menstruation is corrected to a later date, CPU 110 corrects the threshold value and points for determining the start date of menstruation to a higher value. Conversely, when the start date of menstruation is corrected to an earlier date, CPU 110 corrects the threshold value and points for determining the start date of menstruation to a lower value. Also, when the end date of menstruation is corrected to a later date, CPU 110 corrects the threshold value and points for determining the end date of menstruation to a lower value. Conversely, when the end date of menstruation is corrected to an earlier day, CPU 110 corrects the threshold value and points for determining the end date of menstruation to a higher value.

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

[0069] 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 of use. For example, as shown in FIG. 23, the communication terminal 300 presents the types of sanitary products in the order of use for each day based on information from the server 100. For example, on the 12th, an icon of a sanitary product of size S and an icon of a sanitary product of size M are displayed from the top. On the 13th, no sanitary product was used. On the 14th, an icon of a sanitary product of size M and an icon of a sanitary product for night use are displayed from the top. On the 15th, an icon of a sanitary product of size M, an icon of a sanitary product of size M, an icon of a sanitary product of size M, and an icon of a sanitary product for night use are displayed from the top.

[0070] In this embodiment, the CPU 110 of the server 100 executes the process shown in FIG.

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

[0072] 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).

[0073] The CPU 110 refers to the usage history data 122 and reads out the daily usage history of sanitary products from the most recent menstruation start date (step S406).

[0074] CPU 110 transmits the daily use history of sanitary products from the most recent start date of menstruation to communication terminal 300 via communication interface 160 (step S408). As a result, CPU 310 of communication terminal 300 displays on display 330, based on the data from server 100, icons indicating the types of sanitary products in the order of use for each day from the start date of menstruation.

[0075] A user may be able to input the relationship between the amount of bleeding and the sanitary product actually used. This increases the possibility of suggesting a more suitable sanitary product 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 of use on the display 330. As shown in the center diagram of FIG. 25, the user taps the icon of the sanitary product to be corrected. That is, the CPU 310 accepts a user operation, that is, a selection command via the operation unit 340, as to whether the size of the sanitary product was appropriate or not, that is, whether the capacity of the sanitary product was too small, just right, too large, or whether there was no bleeding. The CPU 310 transmits the feedback result to the server 100 via the communication interface 360, and also changes the display of the icon of the sanitary product that was not appropriate on the display 330, as shown in the right diagram of FIG. 25.

[0076] 26, CPU 110 receives data from communication terminal 300 via communication interface 160 (step S412).

[0077] CPU 110 reads the user ID from the data from communication terminal 300, and identifies the storage device ID by referring to user data 121 (step S414).

[0078] The CPU 110 reads out feedback of the specified date, the specified order, and the specified type of sanitary product from the data sent from the communication terminal 300 (step S416).

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

[0080] In this case, a selection command is received as to whether the capacity of the sanitary product was too small, just right, or too large, or whether there was no bleeding. However, as feedback, the communication terminal 300 may also receive an input of the appropriate type of sanitary product itself and transmit it to the server 100.

[0081] 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, in a state where icons of sanitary products are displayed on the communication terminal 300, the user presses and holds the icon of the sanitary product that the user wishes to modify. The communication terminal 300 displays icons of multiple types of sanitary products in a selectable manner. Based on the selection command, the communication terminal 300 transmits a command to the server 100 to modify the sanitary product to the icon selected by the user.

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

[0083] The CPU 110 reads the user ID from the data from the communication terminal 300, and identifies the storage device ID by referring to the user data 121 (step S424).

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

[0085] CPU 110 modifies or updates usage history data 122 based on the modification instruction (step S428). <Fifth embodiment>

[0086] In addition to the functions of the above embodiment, it is preferable that the server 100 presents the start and end dates of the next menstruation, the use schedule of sanitary products during the menstrual period, and the predicted amount of blood loss during the menstrual period to the user via the communication terminal 300 based on the past history of use of sanitary products for each user. For example, as shown in FIG. 28, the communication terminal 300 displays a daily predicted use of sanitary products for the entire next menstrual period based on information from the server 100. Alternatively, as shown in FIG. 29, the communication terminal 300 displays a solid icon indicating the use history of sanitary products for a day that has already passed, and a dotted icon indicating the predicted use of sanitary products for the current day, the next day, or 24 hours from now, based on information from the server 100. Alternatively, as shown in FIG. 30, the communication terminal 300 displays a solid icon indicating the use history of sanitary products for a day that has already passed, and a dotted icon indicating the predicted use of sanitary products for each day until the end of the menstrual period, based on information from the server 100.

[0087] In this embodiment, the memory 120 of the server 100 stores the 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 menstruation, the end date of the next menstruation, the average order of use of sanitary products every day during the menstrual period, and the average amount of blood loss every day during the menstrual period.

[0088] When the sanitary product use history data 122 is updated, such as when a sanitary product has been 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 calculates 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 based on the sanitary product use history of each user, and updates the prediction data 124.

[0089] Then, when the CPU 110 accepts a request from the 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 amount of blood loss each day during the menstrual period, for the user corresponding to the communication terminal 300, to the communication terminal 300 via the communication interface 160. As a result, the CPU 310 of the communication terminal 300 causes the display 330 to display the screens shown in Figs. 28, 29, and 30 based on the information from the server 100.

[0090] However, the server 100 may present the start and end dates of the next menstruation, the use schedule of sanitary products during the menstrual period, and the predicted amount of blood loss per day during the menstrual period, etc., to the user via the communication terminal 300, based on not only the user's but also other users of the same age and body type as the user's past use history of sanitary products. In this case, when the sanitary product use 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 menstruation are modified, the CPU 110 of the server 100 calculates the menstrual cycle, the start and end dates of the next menstruation, the average order of use of sanitary products per day during the menstrual period, and the predicted amount of blood loss per day during the menstrual period, based on the sanitary product use history of multiple users who have the same attributes as the user, and updates the prediction data 124.

[0091] Then, when the CPU 110 accepts a request from the 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 amount of blood loss each day during the menstrual period, for the user corresponding to the communication terminal 300, to the communication terminal 300 via the communication interface 160. As a result, the CPU 310 of the communication terminal 300 causes the display 330 to display the screens shown in Figs. 28, 29, and 30 based on the information from the server 100. Sixth embodiment

[0092] In addition to the functions of the above-described embodiment, 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 of that fact, or notify a designated hospital, doctor, clinic, etc. of that fact.

[0093] 32, when the sanitary product use history data 122 is updated (step S602), such as when a sanitary product is used, when feedback is received about 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 based on the sanitary product use history for each user (step S604). For example, it determines whether the sanitary product use points have increased by 3 points or more.

[0094] If the usage of sanitary products has increased significantly (YES in step S604), the CPU 110 notifies the user's communication terminal 300 or a designated expert's terminal, etc., via the communication interface 160 that the user's usage of sanitary products has increased suddenly (step S606).

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

[0096] 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 a designated expert's terminal, etc., via the communication interface 160 that the user's sanitary product use has decreased rapidly (step S610).

[0097] However, the CPU 110 of the server 100 may compare the user's past sanitary product use history with another user's past sanitary product use history for each user, and if significantly different data is obtained, the CPU 110 may notify the user or a designated hospital, doctor, clinic, etc. of the same. <Seventh embodiment>

[0098] 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 place an order for that type from an e-commerce site or a sanitary product company, or may 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 use of sanitary products.

[0099] When the sanitary product use history data 122 is updated, such as when a sanitary product is used, when feedback is received about the sanitary product used, when the sanitary product used is modified, when the start or end date of menstruation is modified, when the end date of menstruation is confirmed, etc., the CPU 110 of the server 100 calculates the number of each type of sanitary product that is expected to be consumed during the next menstrual period based on the sanitary product use history for each user. Then, if the number is less than the remaining amount in the storage device 200, the CPU 110 automatically places an order for the type to an EC 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.

[0100] 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 each 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 corrected, when the start date or end date of menstruation is corrected, or when the use history data 122 of the sanitary product is updated, the CPU 110 automatically orders the type from an EC 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 in the storage device 200 and the storage capacity of the storage device 200, if the storage capacity is greater than the number of sales units of the sanitary product. This allows the storage device 200 to store sanitary products with a surplus, reducing the possibility that users will rush to purchase products in a hurry during a disaster or when there is a shortage of products. <Eighth embodiment>

[0101] 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, so that the server 100 obtains the number of each type of sanitary product used. However, the present invention is not limited to this embodiment.

[0102] The storage device 200 may measure the distance to the top end of the sanitary product by irradiating light from the bottom surface of the top lid. Then, the CPU 110 of the server 100 may calculate the number of sanitary products used for each type based on the change in the distance.

[0103] Alternatively, the storage device 200 may use ultrasound or take images to allow the server 100 to calculate the number of sanitary products used, and the method of acquiring the number of sanitary products used is not particularly limited.

[0104] In the above embodiment, the storage device 200 has a storage space for each type of sanitary product, and transmits the measurement results for each type to the server 100. However, the storage device 200 may also be configured to stock multiple types of sanitary products in one 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 image, etc. from the storage device 200.

[0105] 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 and 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>

[0106] Some or all of the roles of the devices 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 realized by a plurality of devices on the cloud, or may be realized by the communication terminal 300. More specifically, various data may be transmitted from the storage equipment 200 directly to the communication terminal 300 via WiFi (registered trademark) or Bluetooth (registered trademark) without going through the server 100.

[0107] In this case, the CPU 310 of the communication terminal 300 executes the following process according to the program in the memory 320. Note that here, the memory 320 stores the usage history data 122 and physiological information data 123 of the user only. However, such data may be stored on the cloud.

[0108] Referring to FIG. 34, the CPU 310 receives data from the storage equipment 200 via the communication interface 360 ​​(step S502).

[0109] CPU 310 reads out the weight of each type of sanitary product from the received data and stores it in usage history data 122. 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 usage history data 122 (step S506). If the weight of each type has increased, CPU 110 assumes that the sanitary product has been replenished and stores the latest weight in usage history data 122.

[0110] If the condition for the start of menstruation is met (YES in step S508), CPU 310 stores today as the start day of menstruation in menstrual information data 123 (step S510).

[0111] More specifically, as shown in Figs. 19 and 20, in this embodiment, when a day on which a sanitary product is not used continues for a first predetermined number of days, for example 10 days, and the usage points of the sanitary product are equal to or greater than a first predetermined value, the CPU 310 identifies the day on which the sanitary product is not used as the start day of menstruation.

[0112] CPU 310 reads the start date of the previous menstruation from menstrual information data 123, and accumulates the period from the start date of the previous menstruation to the start date of the current menstruation as the current menstrual cycle in menstrual information data 123 (step S512).

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

[0114] As shown in FIG. 12, CPU 310 displays on 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).

[0115] If the condition for the start of menstruation is not met (NO in step S508), CPU 310 determines whether the condition for the end of menstruation is met (step S522). If the condition for the end of menstruation is met (YES in step S522), CPU 310 stores today as the end day of menstruation in menstrual information data 123 (step S524).

[0116] For example, as shown in Figures 19 and 20, in this embodiment, the CPU 310 determines that the day is the end of menstruation when the sanitary product has not been used for 24 hours or more after the use of the sanitary product continues for a second predetermined number of days, for example, three days or more. More specifically, as shown in Figures 19 and 20, the number of sanitary products used is accumulated for each day, and the day when the usage points of the sanitary product become equal to or less than the second predetermined value is determined to be the end of menstruation.

[0117] As shown in FIG. 13, the CPU 310 displays information indicating the remaining amount of sanitary products of each type, information indicating the end date of menstruation, the menstrual cycle, and the like on the display 330 (step S526).

[0118] If the condition for the end of menstruation is not met (NO in step S522), CPU 310 executes other processes (step S530).

[0119] Additionally, similar to the server 100 in 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>

[0120] In the above embodiment, a network system is provided that includes a storage device for storing sanitary products, a server that identifies the start date of a user's period by determining the number of sanitary products used based on data from the storage device, and a communication terminal that displays the start date of the user's period based on the data from the server and accepts instructions to correct the start date of the period and sends the instructions to the server.

[0121] Preferably, the server identifies the number of each type of sanitary product used based on data from the storage device, identifies the start date of the user's period in accordance with a first rule based on the usage history of multiple types of sanitary products, and changes the first rule for each user based on an instruction from the communication terminal to modify the start date.

[0122] Preferably, the server identifies the user's menstrual cycle based on the start dates of menstruation after multiple past corrections, and transmits the start date of the next menstruation to the user's communication terminal.

[0123] Preferably, the server identifies the number of each type of sanitary product used based on data from the storage device, identifies the end date of the user's period in accordance with a second rule based on the usage history of multiple types of sanitary products, and changes the second rule for each user based on an instruction from the communication terminal to modify the end date.

[0124] In the above embodiment, a server is provided that includes a communication interface for communicating with a storage device and a communication terminal, and a processor that identifies the start date of a user's period by determining the number of sanitary products used based on data from the storage device, and corrects the start date of the period based on a correction instruction from the communication terminal.

[0125] In the above embodiment, a program for a communication terminal is provided that causes a processor of the communication terminal to execute the steps of displaying the start date of the user's period on a display based on data from a server, accepting correction instructions from the user, and transmitting the correction instructions to the server via a communication unit.

[0126] The embodiments disclosed herein should be considered to be illustrative and not restrictive in all respects. The scope of the present invention is defined by the claims, not the above description, and is intended to include all modifications within the meaning and scope of the claims. [Explanation of symbols]

[0127] 1: Network system 100: Server 110: CPU 120:Memory 121: User data 122: Usage history data 123: Physiological information data 124: Forecast data 140:Operation unit 160: Communication interface 200: Storage device 201: Case part 201A: First case 201B: Second case 201C: Third case 205: Equipment section 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:Mike 530: Display

Claims

1. A storage device for storing sanitary products; a server that identifies the number of sanitary products used for each type of sanitary product based on the data from the storage device, and identifies the day when the sum of the points per sanitary product for each type of sanitary product used in a predetermined period becomes equal to or greater than a first predetermined value as the start date of the user's period; a communication terminal that displays the start date of the user's menstruation based on data from the server, and receives an instruction to correct the start date of the menstruation and transmits the instruction to the server; The server changes the first predetermined value for each user based on the modification instruction.

2. 2. The network system according to claim 1, wherein the server identifies the user's menstrual cycle based on the start dates of menstruation after multiple past corrections, and transmits the start date of the next menstruation to the communication terminal of the user.

3. the server identifies the number of sanitary products used for each type of sanitary product based on the data from the storage device, and identifies, based on a usage history of the plurality of types of sanitary products, the day on which a numerical value obtained by adding up the points per type of sanitary product for the number of sanitary products used in a predetermined period becomes less than a second predetermined value as the end date of the user's menstruation; 3. The network system according to claim 1, wherein the second predetermined value is changed for each user based on an instruction from the communication terminal to modify the end date.

4. a communication interface for communicating with the storage device and the communication terminal; a processor that identifies the number of each type of sanitary product used based on data from the storage device, identifies the day when the sum of the points per unit of each type of sanitary product used in a specified period becomes equal to or greater than a first specified value as the start date of the user's period, and changes the first specified value for each user based on a correction instruction from the communication terminal.

Images