Network systems and programs

Abstract

To provide a network system capable of presenting sanitary products to be used in the future based on the history of use of the sanitary products.SOLUTION: A network system 1 includes: a storage device 200 for storing sanitary products; a communication terminal 300 used by a user; and a server 100 for storing a use history of the sanitary products for each user based on data from the storage device, and presenting, to the communication terminal, at least a type of sanitary product that is likely to be used next.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a useful information processing technology relating to the 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, these techniques are disclosed in Japanese Patent Laid-Open No. 63-135144 (Patent Document 1) and Japanese Patent Laid-Open No. 62-183807. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Unexamined Patent Publication No. 63-135144 [Patent Document 2] Japanese Patent Application Publication No. 62-183807 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 suggest sanitary products to be used in the future based on the sanitary product usage history. [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 communication terminal used by a user; and a server for accumulating a usage history of sanitary products for each user based on data from the storage device and presenting to the communication terminal at least the type of sanitary product that is likely to be used next. [Effects of the Invention]

[0006] As described above, according to the present invention, a network system is provided that can suggest sanitary products to be used in the future based on the sanitary product usage history. [Brief explanation of the drawings]

[0007] [Figure 1] FIG. 1 is a conceptual diagram illustrating an overall configuration of a network system according to a first embodiment. [Figure 2] FIG. 2 is an image diagram showing an example of a screen of a communication terminal according to the first embodiment. [Figure 3] FIG. 2 is an image diagram showing an example of a screen of a communication terminal according to the first embodiment. [Figure 4] 1 is a block diagram showing a configuration of a storage device according to a first embodiment. [Figure 5] FIG. 2 is a block diagram showing a configuration of a server according to the first embodiment. [Figure 6] FIG. 3 is a conceptual diagram showing user data according to the first embodiment. [Figure 7] FIG. 2 is a conceptual 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] 10 is a flowchart showing information processing by a server according to the first embodiment; [Figure 10] FIG. 2 is an image diagram showing the input / output history of sanitary products and a start / end score determination table according to the first embodiment. [Figure 11] FIG. 2 is an image diagram showing the 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 a communication terminal according to the first embodiment. [Figure 13] FIG. 2 is an image diagram showing an example of a screen of a 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. 10 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. 10 is an image diagram showing the transition of points earned from using sanitary products according to the second embodiment. [Figure 17] FIG. 10 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. 10 is an image diagram showing the transition of points earned from using sanitary products according to the second embodiment. [Figure 19] FIG. 10 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. 10 is an image diagram showing the transition of points earned from using sanitary products according to the second embodiment. [Figure 21] 10A and 10B are image diagrams showing screen transitions of a communication terminal according to a third embodiment. [Figure 22] 10 is a flowchart showing information processing by a server according to a third embodiment; [Figure 23] FIG. 10 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 of a server according to the fourth embodiment; [Figure 25] FIG. 10 is an image diagram showing a screen transition of a communication terminal according to a fourth embodiment. [Figure 26] 13 is a flowchart showing information processing of a server according to the fourth embodiment; [Figure 27] 13 is a flowchart showing information processing of a server according to the 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. [Figure 30] FIG. 13 is an image diagram showing an example of a screen of a communication terminal according to a fifth embodiment. [Figure 31]FIG. 13 is a conceptual diagram showing prediction data according to the fifth embodiment. [Figure 32] 13 is a flowchart showing information processing of a server according to the sixth embodiment. [Figure 33] FIG. 13 is a conceptual diagram showing the overall configuration of a network system according to a seventh embodiment. [Figure 34] 13 is a flowchart showing information processing by a server according to a ninth embodiment. DETAILED DESCRIPTION OF THE INVENTION

[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. The names and functions of the components 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 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 the types of cases are not limited to those corresponding to different bleeding amounts, and multiple types of sanitary product cases with different uses or functions may also be provided.

[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 obtained from the storage device 200. This enables the server 100 to identify the start date and end date of past menstruation and the amount of blood loss in the past, calculate the menstrual cycle, predict the start date and end date of future menstruation and the amount of blood loss in the future, and transmit this information to the user's communication terminal 300.

[0012] The communication terminal 300 is 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. Note that, as described below, the communication terminal 300 may also display the start date and end date of past menstruation and the amount of blood loss in the past, display the menstrual cycle, or display the start date and end date of future menstruation and the amount of blood loss in the future, based on 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 RAM.

[0017] The memory 220 is realized by various RAMs, various ROMs, etc., and stores programs executed by the MCU 210, data generated by the execution of 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 time elapsed 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 Wi-Fi communication or Bluetooth communication.

[0021] The light 270 emits light based on instructions from the MCU 210. For example, the light 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 sanitary product has not been consumed.

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

[0023] Next, a description will be given of one aspect of the configuration of server 100 constituting network system 1 according to the present embodiment. 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] The CPU 110 controls each unit of the server 100 by executing a program stored in the memory 120. For example, the CPU 110 executes a program stored in the memory 120 and performs various processes, which will be 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 the execution of programs by the CPU 110, input data, other databases used for the service according to this embodiment, etc.

[0026] The memory 120 stores user data 121 as shown in Fig. 6. The user data 121 includes, for each user, 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, body fat percentage, etc.

[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 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.

[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 past menstrual start dates, a history of past menstrual end dates, a history of past blood loss, the types of sanitary products used, a history of points, past menstrual cycles, etc. From this data, the CPU 110 can calculate the average menstrual cycle value, the predicted start date and end date of the next menstrual period, the predicted blood loss, etc.

[0029] Returning to FIG. 5, the operation unit 140 receives commands from a service manager, operator, service technician, etc., 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 the data 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 this 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] CPU 110 reads the device ID from the received data and identifies the corresponding user (step S104).

[0034] 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 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 S106). If the weight of any sanitary product has increased, the CPU 110 considers that the sanitary product has been replenished and stores the latest weight in the 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 date of menstruation in menstruation information data 123 (step S110).

[0036] More specifically, as shown in FIGS. 10 and 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 physiological information data 123, and stores the period from the start date of the previous menstruation to the start date of the current menstruation as the current menstrual cycle in physiological 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] 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 Fig. 12.

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

[0041] 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 consecutive days, such as three days, have passed since the day on which sanitary products have been used. More specifically, as shown in FIGS. 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 determined to be the start day of menstruation, and the day when the number of sanitary products used reaches zero is determined to be 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 for 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] Memory 320 is realized by various RAMs, various ROMs, etc. Memory 320 stores application programs for various services, data generated by execution of programs by CPU 310, data received from server 100, data input via operation unit 340, information for identifying the user of communication terminal 300, etc.

[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 also have a touch panel 350 that includes 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 exchanges various types of information with 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, instead of the display 330.

[0050] Microphone 380 receives voice and inputs the voice data to CPU 310. CPU 310 may receive a voice message from the 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 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. Furthermore, the CPU 310, in accordance with the application program in the memory 320, displays information such as the start date and end date of menstruation, the menstrual cycle, the amount of blood loss, and the type of sanitary product used on the display 330 as shown in Figs. 12 and 13, based on the information from the server 100 or the storage device 200 via the communication interface 360. <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] 15 and 16, in this embodiment, 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 date of menstruation, and recognizes the day when the points reach a predetermined number or less as the end date of menstruation. More specifically, as shown in Figures 15 and 16, the CPU 110 accumulates usage points for sanitary products each day, and recognizes the day when the points reach 3 or more as the start date of menstruation, and the day when the points reach 2 or less as the end date of menstruation.

[0054] In this case, it is preferable that the CPU 110 specifies the amount of blood loss based on the points for the sanitary products used for each day during the menstrual period, and stores the specified 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 for the sanitary products used for the entire menstrual period, and store the specified amount of blood loss in the physiological information data 123.

[0055] 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 FIGS. 17 and 18, the CPU 110 of the server 100 counts the points for that type of sanitary product each time the user takes out the product, and recognizes the day when the points reach a predetermined number or more in a day as the start of menstruation, and recognizes the day when the points fall below the predetermined number or less in a day as the end of menstruation. More specifically, as shown in FIGS. 17 and 18, the CPU 110 accumulates the usage points for the sanitary products 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.

[0056] In this case, it is also preferable that the CPU 110 specifies the amount of blood loss based on the points for the sanitary products used for each day during the menstrual period and stores 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 for the sanitary products used for the entire menstrual period and store the amount of blood loss in the physiological information data 123.

[0057] Alternatively, 1 point is assigned to sanitary products for light days, 2 points to sanitary products for normal days, and 3 points to sanitary products for heavy days. Referring to Figures 19 and 20, the CPU 110 of the server 100 counts the points of the sanitary product each time the user takes out the sanitary product, and recognizes the day when the points reach a predetermined number of points or more in a day as the start of menstruation, and recognizes the day when the points fall below the predetermined number of points as the end of menstruation. More specifically, as shown in Figures 19 and 20, the CPU 110 accumulates the usage points of the sanitary products each day, and recognizes the day when the points reach 4 or more as the start of menstruation, and the day when the usage points reach 2 or less as the end of menstruation.

[0058] In this case, it is also preferable that the CPU 110 specifies the amount of blood loss based on the points for the sanitary products used for each day during the menstrual period and stores 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 for the sanitary products used for the entire menstrual period and store the amount of blood loss in the physiological information data 123.

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

[0060] In addition to the functions of the above-described 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.

[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] Referring to FIG. 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 corrected, CPU 110 changes the rules for determining the start date or end date of menstruation for the target user (step S310).

[0067] For example, if 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, if 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. Furthermore, if 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, if the end date of menstruation is corrected to an earlier date, CPU 110 corrects the threshold value and points for determining the end date of menstruation to a higher value.

[0068] Alternatively, if frequent adjustments are made, 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>

[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 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.

[0070] In this embodiment, the CPU 110 of the server 100 executes the processing 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 usage history of sanitary products from the most recent start date of menstruation to communication terminal 300 via communication interface 160 (step S408). Based on the data from server 100, CPU 310 of communication terminal 300 then displays on display 330 icons indicating the types of sanitary products in the order in which they were used for each day from the start date of menstruation.

[0075] 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 of suggesting more appropriate sanitary products 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 want to modify. That is, the CPU 310 accepts a 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, 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, as shown in the right diagram of FIG. 25, changes the display 330 to display the icon of the inappropriate sanitary product.

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

[0077] 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 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, the CPU 110 corrects or updates the usage history data 122 (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 the corrected history.

[0080] Here, the command to select whether the capacity of the sanitary product was too small, just right, too large, or there was no bleeding was accepted, but as feedback, the communication terminal 300 may also accept input of the appropriate type of sanitary product itself and send 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, when 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 wants to modify. The communication terminal 300 displays icons of multiple types of sanitary products so that the user can select the icon. 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 corrects or updates usage history data 122 based on the correction instruction (step S428). <Fifth embodiment>

[0086] In addition to the functions of the above-described embodiment, it is preferable that the server 100 presents the user with the start and end dates of their next menstruation, their planned use of sanitary products during their menstrual period, and a predicted daily blood loss during their menstrual period via the communication terminal 300, 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 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, based on information from the server 100, solid line icons indicating the use history of sanitary products for days that have already passed and dotted line icons indicating predicted use of sanitary products 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 use history of sanitary products for days that have already passed and dotted line icons indicating predicted use of sanitary products for each day until the end of the menstrual period.

[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 each day during the menstrual period, and the average amount of blood loss each day during the menstrual period.

[0088] 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 date 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 for each user, and updates the prediction data 124.

[0089] 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 daily order of use of sanitary products during the menstrual period, and the average daily blood loss during the menstrual period, related to the user corresponding to that communication terminal 300, to that 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 Fig. 28, 29, and 30 based on the information from server 100.

[0090] However, the server 100 may present the user with the start and end dates of their next period, a sanitary product use schedule during their period, and a predicted daily blood loss during their period, based on the past sanitary product use history of not only the user but also other users of the same age and body type as the user, via the communication terminal 300. 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 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 use histories of multiple users who have the same attributes as the user, and updates the prediction data 124.

[0091] 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 daily order of use of sanitary products during the menstrual period, and the average daily blood loss during the menstrual period, related to the user corresponding to that communication terminal 300, to that 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 Fig. 28, 29, and 30 based on the information from server 100. Sixth Embodiment

[0092] Furthermore, 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 or a designated hospital, doctor, clinic, etc.

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

[0094] 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, etc., via the communication interface 160 that the user's sanitary product use has increased suddenly (step S606).

[0095] If the amount of sanitary products used has not increased significantly based on the sanitary product use history for each user (step S604), the CPU 110 determines whether the amount of sanitary products used has decreased significantly (step S608), for example, 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 the terminal of a designated expert, etc., via the communication interface 160 that the user's sanitary product use has decreased dramatically (step S610).

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

[0098] In addition to the functions of the above-described embodiment, as shown in FIG. 33, when a certain type of sanitary product is about to run out, the server 100 may automatically order 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, or when the end date of menstruation 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 menstrual period based on the sanitary product use history for each user. If the calculated 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 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 of sanitary product for each storage device 200. The memory 120 also stores the number of units sold for each type of sanitary product. When a sanitary product is used, when feedback about the sanitary product used is received, when the sanitary product used is modified, when the start or end date of menstruation is modified, or when the sanitary product use 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 remaining storage capacity is greater than the number of units sold for the sanitary product. This allows the storage device 200 to store sanitary products with a surplus, reducing the likelihood of users rushing to purchase sanitary products during disasters or shortages. <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, thereby obtaining the number of used sanitary products of each type in the server 100. However, the present invention is not limited to this embodiment.

[0102] 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, and the CPU 110 of the server 100 may then 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 have the server 100 calculate the number of sanitary products used, and the method for obtaining the number of used sanitary products 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 store multiple types of sanitary products in a single storage space. In this case, the CPU 110 of the server 100 identifies 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 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>

[0106] Some or all of the roles of the devices in the network system 1 of the above-described embodiment may be performed by other devices. For example, the role of the server 100 may be performed by multiple devices on a cloud, or 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, CPU 310 of communication terminal 300 executes the following process in accordance with the program in memory 320. Here, memory 320 stores only the user's usage history data 122 and physiological information data 123. 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] The CPU 310 reads out 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). If the weight for each type has increased, the CPU 110 considers that the sanitary products have been replenished and stores the latest weight in the 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 date of menstruation in menstrual information data 123 (step S510).

[0111] 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, for example, 10 days, and the sanitary product usage points are equal to or greater than a first predetermined value, the CPU 310 identifies the day on which sanitary products are used as the start date of menstruation.

[0112] CPU 310 reads the start date of the previous menstruation from physiological information data 123, and stores the period from the start date of the previous menstruation to the start date of the current menstruation as the current menstrual cycle in physiological 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, 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).

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

[0116] 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 FIGS. 19 and 20, the number of sanitary products used is accumulated each day, and the day when the sanitary product usage points become equal to or less than a second predetermined value is determined to be the day that a period has ended.

[0117] As shown in FIG. 13, the CPU 310 displays information indicating the remaining amount of each type of sanitary product, information indicating the end date of menstruation, menstrual cycle, etc. 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 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>

[0120] 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.

[0121] 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.

[0122] Preferably, the communication terminal receives input of the relationship between the amount of blood loss and the sanitary product used, or the type of sanitary product to actually be used, and transmits the information to the server. The server accumulates a usage history of the sanitary product based on the information.

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

[0124] Preferably, when the server detects, based on the data from the storage device, that the sanitary product has been used in a way that is different from the average usage history of a plurality of other users, the server notifies the communication terminal of this.

[0125] 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.

[0126] 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.

[0127] 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.

[0128] 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.

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

[0130] 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 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.

2. 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.

3. 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.

4. The network system according to claim 1 , 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.

5. 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.

6. 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. 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.

Images