Program and terminal device
The program and terminal device convert weight sensor readings into user-friendly units like number or proportion of food items, addressing the challenge of unintuitive weight values and enhancing user understanding of food remaining amounts.
Patent Information
- Application Number
- JP2023218392
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2023-12-25
- Publication Date
- 2025-01-10
- Estimated Expiration
- 2040-06-22
AI Technical Summary
Existing systems fail to provide users with an easy understanding of the remaining amount of food based on weight sensor readings, as weight values are not intuitive for food quantities.
A program and terminal device that include a display unit for converting weight sensor readings into user-friendly units such as number of items or proportion of remaining food, allowing selection of units and displaying the converted values on a single screen.
Enables users to easily grasp the remaining amount of food by converting weight sensor readings into understandable units, facilitating accurate estimation of food quantities.
Smart Images

Figure 0007611490000001 
Figure 0007611490000002 
Figure 0007611490000003
Abstract
Description
[Technical field]
[0001] The present disclosure relates to a program and a terminal device. [Background technology]
[0002] Patent document 1 discloses a system that outputs information regarding the weight of a drink placed on a weight sensor to a refrigerator control unit, and the refrigerator control unit manages the start and end of storage of the drink based on the information regarding the weight of the drink. [Prior art documents] [Patent documents]
[0003] [Patent Document 1] JP 2017-133825 A Summary of the Invention [Problem to be solved by the invention]
[0004] The present disclosure provides a program and a terminal device that allow a user to easily grasp the weight of food detected by a weight sensor as the amount of food remaining. [Means for solving the problem]
[0005] The program of the present disclosure causes a control unit of a terminal device having a display unit to function as a program execution unit that displays, on a single screen, an area for displaying the weight of food detected by a weight sensor and an area for setting a unit for converting the weight of the food detected by the weight sensor, on the display unit. The unit setting area accepts selection of a unit for converting the weight of the food detected by the weight sensor into either a unit indicating the number of food pieces or a unit indicating the percentage of remaining food. .
[0008] The terminal device according to the present disclosure includes a display unit, an area for displaying the weight of food detected by a weight sensor, and an area for setting a unit for converting the weight of the food detected by the weight sensor, and a control unit for displaying the above on a single screen using the display unit. The unit setting area accepts selection of a unit for converting the weight of the food detected by the weight sensor into either a unit indicating the number of food pieces or a unit indicating the percentage of remaining food. . Effect of the Invention
[0011] The program and terminal device disclosed herein can convert the weight of the food detected by the weight sensor into a unit that is easy for the user to understand as the amount of food remaining, and notify the user of the converted amount. Therefore, the user can easily understand the weight of the food detected by the weight sensor as the amount of food remaining. [Brief description of the drawings]
[0012] [Figure 1] Diagram showing the configuration of a food control system [Diagram 2] A perspective view of the weight sensor from above [Diagram 3] An exploded perspective view of the front of the first weight detection unit as viewed from above. [Figure 4] An exploded perspective view of the front of the second weight detection unit as viewed from above. [Diagram 5] Block diagram showing the functional configuration of the weight sensor [Figure 6] Block diagram showing the functional configuration of a food management server and a terminal device [Figure 7] An example of a food management database [Figure 8] FIG. 13 is a diagram showing an example of a food management UI related to the remaining amount of food. [Figure 9] A diagram showing an example of a first screen. [Figure 10] FIG. 2 shows an example of a second screen. [Figure 11] A diagram showing an example of a third screen. [Figure 12] A diagram showing an example of a fourth screen. [Figure 13] Flowchart showing the operation of the food control system [Figure 14] Flowchart showing the operation of the food control system [Figure 15] A flowchart showing the operation of a terminal device in a generation process. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0013] (The knowledge and other information that formed the basis of this disclosure) When the weight of food detected by a weight sensor is notified to the user as the remaining amount of food as in the above-mentioned conventional technology, the user may not be able to easily grasp the remaining amount of food if the notification is simply a weight value. For example, when the weight sensor detects the weight of eggs, the user may not be able to easily grasp how many eggs are left even if the remaining amount of eggs is notified as a weight value. Therefore, the present disclosure provides a program and a terminal device that allow a user to easily grasp the weight of food detected by a weight sensor as the amount of food remaining.
[0014] Hereinafter, the embodiments will be described in detail with reference to the drawings. However, in some cases, more detailed explanations than necessary may be omitted. For example, detailed explanations of already well-known matters or duplicate explanations of substantially the same configurations may be omitted. It should be noted that the accompanying drawings and the following description are provided to enable those skilled in the art to fully understand the present disclosure, and are not intended to limit the subject matter described in the claims.
[0015] (Embodiment) Hereinafter, an embodiment will be described with reference to FIGS. 1 to 15. [1. Configuration] FIG. 1 is a diagram showing the configuration of a food management system 1000.
[0016] The food management system 1000 is a system that manages the remaining amount, the storage start date, the best-before date or expiration date, etc., of food F whose weight is detected by weight sensor 1. The food management system 1000 shown in Fig. 1 illustrates an example in which milk F1, beer F2, eggs F3, and onions F4 are managed as food F.
[0017] Food management system 1000 includes a refrigerator 2. The refrigerator 2 includes a main box 20 with an open front, in which a refrigerator compartment 21, an ice-making compartment 22, a fresh-freezing compartment 23, a freezer compartment 24, and a vegetable compartment 25 are formed. A rotating left door 21A and a right door 21B are provided at the opening at the front of the refrigerator compartment 21. The ice-making compartment 22, the fresh-freezing compartment 23, the freezer compartment 24, and the vegetable compartment 25 are each provided with drawers 22A, 23A, 24A, and 25A for storing food F.
[0018] Food management system 1000 includes four weight sensors 1: a first weight sensor 11, a second weight sensor 12, a third weight sensor 13, and a fourth weight sensor 14. Each of second weight sensor 12 and fourth weight sensor 14, together with case 3, constitutes first weight detection unit 15. Furthermore, third weight sensor 13, together with case 3 and egg holder 4, constitutes second weight detection unit 16.
[0019] First weight sensor 11, second weight sensor 12, and third weight sensor 13 are provided in refrigeration compartment 21 of refrigerator 2 installed in house H. A container filled with milk F1 is placed on the upper surface of first weight sensor 11, and first weight sensor 11 detects the weight of milk F1 filled in the placed container. A case 3 is placed on the upper surface of second weight sensor 12, and second weight sensor 12 detects the total weight of beer F2 contained in case 3. Third weight sensor 13 has the case 3 and egg holder 4 placed on the upper surface of third weight sensor 13, and third weight sensor 13 detects the total weight of eggs F3 contained in egg holder 4.
[0020] The fourth weight sensor 14 is provided on a shelf 5 arranged in the house H. The fourth weight sensor 14 has the case 3 placed on its upper surface, and detects the total weight of the onions F4 contained in the case 3.
[0021] The food F whose weight is detected by the first weight sensor 11 is not limited to milk F1, but may be another drink or a food F other than a drink. The same is true for the second weight sensor 12, the third weight sensor 13, and the fourth weight sensor 14, and the food F whose weight is detected is not limited to the above-mentioned food F.
[0022] Moreover, first weight sensor 11 may have case 3 placed on its upper surface to form first weight detection unit 15, and detect the total weight of food F contained in case 3. Furthermore, first weight sensor 11 may have case 3 and egg holder 4 placed on its upper surface to form second weight detection unit 16, and detect the total weight of egg F4 contained in egg holder 4. Furthermore, second weight sensor 12 and fourth weight sensor 14 may detect the weight of food F placed on its upper surface without case 3. Furthermore, second weight sensor 12 may have case 3 and egg holder 4 placed on its upper surface to form second weight detection unit 16, and detect the total weight of egg F4 contained in egg holder 4. Furthermore, third weight sensor 13 may detect the weight of food F placed on its upper surface without case 3. Furthermore, third weight sensor 13 may have case 3 placed on its upper surface to form first weight detection unit 15, and detect the total weight of food F contained in case 3.
[0023] Furthermore, the number and installation locations of weight sensors 1 provided in food management system 1000 of the present embodiment are merely an example, and are not limited to the number and installation locations shown in FIG.
[0024] FIG. 2 is a perspective view of the front surface of the weight sensor 1 as viewed from above. The weight sensor 1 has a substantially rectangular parallelepiped shape. When the weight sensor 1 is used alone without constituting the first weight detection unit 15 and the second weight detection unit 16, food F is placed on the upper surface, just like the first weight sensor 11.
[0025] FIG. 3 is an exploded perspective view of the front surface of the first weight detection unit 15 as viewed from above. The first weight detection unit 15 includes a weight sensor 1 and a case 3 . The case 3 is a box-shaped case with an open top. A storage section 3A is formed inside the case 3. The bottom surface of the storage section 3A is formed to be larger than the top surface of the weight sensor 1. The bottom surface of the case 3 is provided with an engagement section 3B that can engage with the weight sensor 1.
[0026] The first weight detection unit 15 is fixed to the bottom surface of the case 3 so that the weight sensor 1 does not move relative to the case 3 when the weight sensor 1 is engaged with an engagement portion of the case 3 to detect the weight of the food F.
[0027] FIG. 4 is an exploded perspective view of the front surface of the second weight detection unit 16 as viewed from above. The second weight detection unit 16 includes a weight sensor 1, a case 3, and an egg holder 4. The egg holder 4 is provided with a plurality of fixing holes 4A for fixing eggs in the egg holder 4. The egg holder 4 is accommodated in the case 3 such that the surface on which the fixing holes 4A are provided is the upper surface, and the members protruding from the periphery of the surface at a predetermined angle protrude downward from the surface. This allows the egg holder 4 to accommodate an egg F3 in an upright state in the case 3. In FIG. 4, the number of fixing holes 4A provided in the egg holder 4 is "10", but the number of fixing holes 4A provided in the egg holder 4 is not limited to "10" and may be more or less. In addition, the fixing holes 4A shown in FIG. 4 are arranged in two rows in the longitudinal direction of the egg holder 4, but the arrangement of the fixing holes 4A is not limited to two rows in the longitudinal direction.
[0028] The second weight detection unit 16 has a case 3 placed on the top surface of the weight sensor 1 and an egg holder 4 placed in the storage section 3A of the case 3, so that the weight sensor 1 detects the total weight of the egg F4 contained in the egg holder 4.
[0029] Returning to the explanation of FIG. 1, the food management system 1000 includes a terminal device 6 having a touch panel 62. The touch panel 62 corresponds to an example of a "display unit." The terminal device 6 is configured, for example, as a smartphone or a tablet terminal. An application program for managing food F whose weight is detected by the weight sensor 1 is installed on the terminal device 6, and the terminal device 6 communicates with a food management server 7 using the function of the application. In the following description, an application program for managing food F whose weight is detected by the weight sensor 1 is referred to as a "food management application" and is given the reference number "6130." The food management application 6130 corresponds to an example of a "program" and an "application program."
[0030] In this embodiment, when a communication connection is established with the communication device 8, the terminal device 6 communicates with the food management server 7 via the communication device 8, and when a communication connection is not established with the communication device 8, the terminal device 6 communicates with the food management server 7 without going through the communication device 8.
[0031] The communication device 8 connects to a global network GN including the Internet, a telephone network, and other communication networks, and communicates with the food management server 7 connected to the global network GN. The communication device 8 is an interface device for connecting the terminal device 6 to the global network GN. The communication device 8 has functions such as a modem-related function, a router function, and a NAT (Network Address Translation) function. The communication device 8 transfers data sent and received between the terminal device 6 and the food management server 7 connected to the global network GN.
[0032] Food management system 1000 includes a food management server 7. Food management server 7 is a server device that manages food F whose weight is detected by weight sensor 1, and is connected to global network GN. Note that in each figure, food management server 7 is represented by a single block, but this does not necessarily mean that food management server 7 is composed of a single server device. For example, food management server 7 may be composed of multiple server devices with different processing contents.
[0033] Next, the functional configurations of the weight sensor 1, the terminal device 6, and the food management server 7 will be described.
[0034] FIG. 5 is a block diagram showing the functional configuration of the weight sensor 1. As shown in FIG. The weight sensor 1 includes a sensor control unit 100, a sensor communication unit 101, a detection unit 102, and a power supply unit 103.
[0035] The sensor control unit 100 includes a sensor processor 110, which is a processor that executes programs such as a CPU or MPU, and a sensor storage unit 120, and controls each part of the weight sensor 1. The sensor control unit 100 executes various processes through cooperation between hardware and software, such that the sensor processor 110 reads out a control program 1201 stored in the sensor storage unit 120 and executes the processes.
[0036] The sensor storage unit 120 has a storage area for storing programs executed by the sensor processor 110 and data processed by the sensor processor 110. The sensor storage unit 120 stores a control program 1201 executed by the sensor processor 110, setting data 1202 related to the settings of the weight sensor 1, a sensor ID 1203 which is identification information of the weight sensor 1, and various other data. The sensor storage unit 120 has a nonvolatile storage area for nonvolatilely storing programs and data. The sensor storage unit 120 may also include a volatile storage area and constitute a work area for temporarily storing programs executed by the sensor processor 110 and data to be processed.
[0037] The sensor communication unit 101 includes communication hardware such as a communication circuit conforming to a predetermined communication standard, and communicates with the food management server 7 under the control of the sensor control unit 100. In this embodiment, the communication standard used by the sensor communication unit 101 is exemplified as a wireless communication standard, but may be a wired communication standard.
[0038] Detection unit 102 is composed of a sensor element such as a strain gauge type or an electrical resistance wire type, and detects the weight of food F placed on weight sensor 1 or the weight of food F contained in case 3 under the control of sensor control unit 100. Note that food F contained in case 3 also includes food F contained in egg holder 4. Detection unit 102 outputs the detection result to sensor control unit 100.
[0039] The power supply unit 103 includes a battery 1031 and supplies power to each part of the weight sensor 1 under the control of the sensor control unit 100. The power supply unit 103 may include a circuit that receives power from the refrigerator 2 and supplies the power supplied from the refrigerator 2 to each part of the weight sensor 1, instead of or in addition to the battery 1031.
[0040] FIG. 6 is a block diagram showing the functional configuration of the terminal device 6 and the food management server 7 included in the food management system 1000.
[0041] First, the functional configuration of the food management server 7 will be described. The food management server 7 includes a server control unit 70 and a server communication unit 71.
[0042] The server control unit 70 includes a server processor 700, which is a processor that executes programs such as a CPU or MPU, and a server memory unit 710, and controls each unit of the food management server 7. The server control unit 70 executes various processes through cooperation between hardware and software, such that the server processor 700 reads out a control program 7110 stored in the server memory unit 710 and executes processing.
[0043] The server storage unit 710 has a storage area for storing programs executed by the server processor 700 and data processed by the server processor 700. The server storage unit 710 stores a control program 7110 executed by the server processor 700, setting data 7120 related to the settings of the food management server 7, a food management database 7130, and various other data. The server storage unit 710 has a nonvolatile storage area for nonvolatilely storing programs and data. The server storage unit 710 may also include a volatile storage area and constitute a work area for temporarily storing programs executed by the server processor 700 and data to be processed.
[0044] FIG. 7 is a diagram showing an example of the food management database 7130. The food management database 7130 is a database that stores various information related to the food F whose weight is detected by the weight sensor 1.
[0045] Each record R stored in the food management database 7130 has a user ID 7131, a sensor ID 1203, sensor communication information 7132, type information 7133, detected weight information 7134, conversion unit information 7135, weight information at time of setting 7136, remaining amount information at time of setting 7137, storage location information 7138, storage start date information 7139, expiration date information 7140, expiration date notification timing information 7141, remaining amount notification timing information 7142, and food image data 7143.
[0046] Each record R stored in the food management database 7130 may further include one or more other types of information.
[0047] The user ID 7131 is identification information for identifying the user P who uses the food management application 6130, and is appropriately assigned to the user P who uses the food management application 6130.
[0048] As described above, the sensor ID 1203 is identification information for identifying the weight sensor 1. In one record R, one or more sensor IDs 1203 are associated with a user ID 7131.
[0049] The sensor communication information 7132 is information for communicating with the weight sensor 1 of the sensor ID 1203 associated with the same record R. The sensor communication information 7132 includes, for example, address information and the like.
[0050] The type information 7133 is information that indicates the type of food F whose weight is detected by the weight sensor 1. In one record R, the same number of type information 7133 as the sensor IDs 1203 are associated with the user ID 7131.
[0051] The detected weight information 7134 is information indicating the weight of food F detected by the weight sensor 1. In one record R, the same number of detected weight information 7134 as the sensor ID 1203 are associated with a user ID 7131. The detected weight information 7134 is appropriately updated by the food management server 7 every time the corresponding weight sensor 1 detects the weight of food F.
[0052] The conversion unit information 7135 is information indicating a unit into which the weight of food F detected by the weight sensor 1 is converted. In this embodiment, the unit indicated by the conversion unit information 7135 is either a unit indicating the number of food F or a unit indicating the proportion of the remaining amount of food F. The unit indicating the number of food F is "pieces", and the unit indicating the proportion of the remaining amount of food F is a percentage. Note that "pieces", which is the unit indicating the number of food F, is generally a counter word, but in this embodiment, it is treated as a unit. In one record R, the same number of conversion unit information 7135 as the sensor IDs 1203 are associated with a user ID 7131.
[0053] The weight information at setting 7136 is information indicating the weight of the food F detected by the weight sensor 1 when the setting of the unit indicated by the conversion unit information 7135 was performed in the food management application 6130. In one record R, the same number of pieces of weight information at setting 7136 as the number of sensor IDs 1203 are associated with a user ID 7131.
[0054] The remaining amount information at setting 7137 is information indicating the remaining amount of food F whose weight is detected by the weight sensor 1 when the unit indicated by the conversion unit information 7135 was set in the food management application 6130. The remaining amount of food F indicated by the remaining amount information at setting 7137 is set by the user P, and the unit is the unit indicated by the conversion unit information 7135 associated with the same record R. In one record R, the same number of remaining amount information at setting 7137 as sensor IDs 1203 are associated with a user ID 7131.
[0055] The storage location information 7138 is information indicating the storage location of the food F detected by the weight sensor 1. In this embodiment, the storage location information 7138 indicates one of "refrigerator", "storage", "disaster prevention", and "not set" as the storage location. In one record R, the same number of pieces of storage location information 7138 as the sensor IDs 1203 are associated with a user ID 7131.
[0056] The storage start date information 7139 is information indicating the storage start date of the food F detected by the weight sensor 1. In one record R, the same number of pieces of storage start date information 7139 as the number of sensor IDs 1203 are associated with a user ID 7131.
[0057] The expiration date information 7140 is information that indicates the expiration date of the best-before date or the expiration date of the food F whose weight is detected by the weight sensor 1. In one record R, the same number of pieces of expiration date information 7140 as the sensor IDs 1203 are associated with the user ID 7131.
[0058] Deadline notification timing information 7141 is information indicating the timing for notifying user P of the deadline indicated by the corresponding deadline information 7140. As shown in Fig. 7, the timing indicated by the deadline notification timing information 7141 is the number of days before the deadline indicated by the deadline information 7140. In one record R, the same number of pieces of deadline notification timing information 7141 as sensor IDs 1203 are associated with a user ID 7131.
[0059] The remaining amount notification timing information 7142 is information indicating the timing for notifying that the remaining amount of food F, the weight of which is detected by the weight sensor 1, is low. As shown in Fig. 7, the timing indicated by the remaining amount notification timing information 7142 is a timing such as a percentage or less or a number of pieces or less. In one record R, the same number of remaining amount notification timing information 7142 as the sensor IDs 1203 are associated with a user ID 7131.
[0060] The food image data 7143 is image data of a food image FOG, which is an image of food F. In one record R, the same number of food image data 7143 as the sensor IDs 1203 are associated with a user ID 7131.
[0061] One record R shown in FIG. 7 is a record R related to the first weight sensor 11, the second weight sensor 12, the third weight sensor 13, and the fourth weight sensor 14.
[0062] The user ID 7131 of one record R shown in Figure 7 is associated with "SE0001" as the sensor ID 1203 of the first weight sensor 11, "SE0002" as the sensor ID 1203 of the second weight sensor 12, "SE0003" as the sensor ID 1203 of the third weight sensor 13, and "SE0004" as the sensor ID 1203 of the fourth weight sensor 14.
[0063] 6, the server communication unit 71 includes communication hardware conforming to a predetermined communication standard, and communicates with devices connected to the global network GN according to the predetermined communication standard under the control of the server control unit 70. In this embodiment, the server communication unit 71 communicates with the terminal device 6 and the weight sensor 1.
[0064] Next, the functional configuration of the terminal device 6 will be described. The terminal device 6 includes a terminal control unit 60, a terminal communication unit 61, a touch panel 62, and a camera 63. The terminal control unit 60 corresponds to an example of a "control unit".
[0065] The terminal control unit 60 includes a terminal processor 600, which is a processor that executes programs such as a CPU or an MPU, and a terminal storage unit 610, and controls each unit of the terminal device 6. The terminal control unit 60 executes various processes by cooperation of hardware and software, such that the terminal processor 600 reads out a control program 6110 stored in the terminal storage unit 610 and executes the process. A food management application 6130 is pre-installed in the terminal device 6. The food management application 6130 is a program that causes the terminal control unit 60 to function as an application execution unit 6000 by being read out from the terminal storage unit 610 and executed by the terminal processor 600. The application execution unit 6000 corresponds to an example of a "program execution unit". Details of the application execution unit 6000 will be described later.
[0066] The terminal storage unit 610 has a storage area for storing programs executed by the terminal processor 600 and data processed by the terminal processor 600. The terminal storage unit 610 stores a control program 6110 executed by the terminal processor 600, setting data 6120 related to the settings of the terminal device 6, a food management application 6130, a user ID 7131, and various other data. The terminal storage unit 610 has a non-volatile storage area for non-volatilely storing programs and data. The terminal storage unit 610 may also include a volatile storage area and constitute a work area for temporarily storing programs executed by the terminal processor 600 and data to be processed.
[0067] The terminal communication unit 61 includes communication hardware such as a communication circuit conforming to a predetermined communication standard, and communicates with devices connected to the global network GN according to the predetermined communication standard under the control of the terminal control unit 60. In this embodiment, the terminal communication unit 61 communicates with the food management server 7 according to the predetermined communication standard under the control of the application execution unit 6000. In this embodiment, the communication standard used by the terminal communication unit 61 is exemplified as a wireless communication standard, but may be a wired communication standard.
[0068] The touch panel 62 includes a display panel such as a liquid crystal display panel, and a touch sensor that is overlaid on or integrated with the display panel. The display panel displays various images under the control of the terminal control unit 60. The touch sensor detects a touch operation and outputs it to the terminal control unit 60. The terminal control unit 60 executes a process corresponding to the touch operation based on an input from the touch sensor.
[0069] The camera 63 takes pictures under the control of the terminal control unit 60. The camera 53 outputs data of the captured image to the terminal control unit 60.
[0070] As described above, the terminal control unit 60 functions as the application execution unit 6000. The application execution unit 6000 controls the terminal communication unit 61 to send and receive various information to and from the food management server 7. If a communication connection between the terminal device 6 and the communication device 8 is possible, the application execution unit 6000 sends and receives various information to and from the food management server 7 via the communication device 8, and if not, sends and receives various information to and from the food management server 7 without going through the communication device 8. Therefore, even if the user P is not located inside or near the house H, the terminal device 6 can send and receive various information to and from the food management server 7 by using the functions of the food management application 6130.
[0071] The application executing unit 6000 also displays a user interface related to the management of food F whose weight is detected by the weight sensor 1 on the touch panel 62. In the following description, this user interface is referred to as a "food management UI" and is given the reference number "6300." By displaying the food management UI 6300 on the touch panel 62, the application executing unit 6000 provides the user P with various information related to the food F whose weight is detected by the weight sensor 1, and also receives various inputs from the user P related to the food F whose weight is detected by the weight sensor 1.
[0072] In this embodiment, the application executing unit 6000 displays a food management UI 6300 on the touch panel 62, thereby providing the user P with information on the remaining amount of food F, the weight of which is detected by the weight sensor 1. FIG. 8 is a diagram showing an example of a food management UI 6300 relating to the remaining amount of food F.
[0073] The food management UI 6300 related to the remaining amount of food F includes an object OB related to the remaining amount of food F for each food F. The food management UI 6300 shown in Fig. 8 includes an object OB1 related to the remaining amount of milk F1, an object OB2 related to the remaining amount of beer F2, an object OB3 related to the remaining amount of eggs, and an object OB4 related to the remaining amount of onions F4.
[0074] The one object OB includes a food image FOG and remaining amount information ZJ indicating the remaining amount of food F. The one object OB also includes, in a predetermined case, remaining amount warning information KJ1 that warns that the remaining amount of food F is low, and / or expiration date warning information KJ2 that warns that the expiration date of food F is approaching.
[0075] 8 includes a food image FOG1 showing the milk F1, remaining amount information ZJ1 showing the remaining amount of the milk F1, and remaining amount warning information KJ1. As shown in Fig. 8, the remaining amount information ZJ1 is an image showing the remaining amount of the milk F1 in five stages using a bar in 20% increments. 8 includes a food image FOG2 showing the beer F2, and remaining amount information ZJ2 showing the remaining amount of the beer F2. The remaining amount of the beer F2 shown by the remaining amount information ZJ2 is shown in units of "pieces." 8 includes a food image FOG3 showing the egg F3, remaining amount information ZJ3 showing the remaining amount of the egg F3, and expiration date warning information KJ2. The remaining amount of the egg F3 shown by the remaining amount information ZJ3 is shown in units of "pieces." 8 includes a food image FOG4 showing the onion F4, remaining amount information ZJ4 showing the remaining amount of the onion F4, and remaining amount warning information KJ1. As shown in FIG. 8, the remaining amount of onions F4 shown by the remaining amount information ZJ4 is shown in units of "pieces."
[0076] When the application execution unit 6000 displays the food management UI 6300 shown in Fig. 8 on the touch panel 62, the application execution unit 6000 receives the record R shown in Fig. 7 from the food management server 7 via the device communication unit 61. Then, based on the received record R, the application execution unit 6000 generates an object OB for each sensor ID 1203 included in the record R. The generation of the object OB1 will be described in detail with reference to Fig. 15.
[0077] 8, the application execution unit 6000 notifies the user P of the remaining amount of food F in units indicating the number of pieces of food F by displaying the food management UI 6300. The application execution unit 6000 also notifies the user P of the remaining amount of food F in the form of a bar indicating a percentage by displaying the food management UI 6300. This allows the user P to easily grasp the remaining amount of food F, the weight of which is detected by the weight sensor 1.
[0078] In FIG. 8, when the remaining amount of food F is shown as a percentage, as in remaining amount information ZJ1, a bar is displayed in 20% increments. However, the amount may be displayed in 10% increments as a string, such as "about 10%" or "about 20%", or the actual percentage may be displayed as a string.
[0079] The food management UI 6300 relating to the remaining amount of food F includes an all button B1, a refrigerator button B2, a storage button B3, and a disaster prevention button B4.
[0080] The all button B1 is a software button for displaying the object OB1 on the food management UI 6300 related to the remaining amount of food F for all of the sensor IDs 1203 included in the record R, regardless of the storage location indicated by the storage location information 7138. The refrigerator button B2 is a software button for narrowing down the objects OB displayed by the food management UI 6300 related to the remaining amount of food F to objects OB for the sensor ID 1203 whose storage location information 7138 indicates "refrigerator." The storage cabinet button B3 is a software button for narrowing down the objects OB displayed by the food management UI 6300 related to the remaining amount of food F to objects OB for the sensor ID 1203 whose storage location information 7138 indicates "storage cabinet." The disaster prevention button B4 is a software button for narrowing down the objects OB displayed by the food management UI 6300 related to the remaining amount of food F to objects OB for the sensor ID 1203 whose storage location information 7138 indicates "disaster prevention". By touching these buttons, the user P can change the object OB related to the remaining amount of food F displayed on the food management UI 6300 depending on the storage location.
[0081] In order to provide the above-described notification of the remaining amount of food F, the settings related to the weight sensor 1 are made by the user P in the food management application 6130. Note that in this embodiment, the settings related to the weight sensor 1 include settings made before starting to use the weight sensor 1, so-called initial settings, and settings when changing the settings from the previous settings. In the setting related to the weight sensor 1, in the food management UI 6300, the screen transitions in response to a touch operation by the user P.
[0082] The screen transition of the food management UI 6300 in the setting related to the weight sensor 1 and each screen in the screen transition will be described with reference to Figs. 9 to 12. In the setting related to the weight sensor 1, in response to a touch operation by a user P, the food management UI 6300 transitions between the first screen GM1, the second screen GM2, the third screen GM3, and the fourth screen GM4 in this order.
[0083] FIG. 9 is a diagram showing an example of the first screen GM1. The first screen GM1 includes the first explanatory information J1. The first explanatory information J1 shows an explanation of an operation performed by the user P on the first screen GM1.
[0084] The first screen GM1 includes an image G1 showing how to use the weight sensor 1. The image G1 shown in Fig. 9 includes an image G2 of the weight sensor 1 and an image G3 of the first weight detection unit. That is, the image G1 shows how to use the weight sensor 1 as a standalone unit and how to use it as the first weight detection unit 15. The image G1 may also include an image of the second weight detection unit 16, and show three ways to use the weight sensor 1: how to use it as a standalone unit, how to use it as the first weight detection unit 15, and how to use it as the second weight detection unit 16.
[0085] The first screen GM1 includes an update button B6 and a first weight display area HA1. The update button B6 is a software button for updating the display contents of the first weight display area HA1. The first weight display area HA1 is an area that displays the weight detected by the weight sensor 1 when the update button B6 is touched. In the example of FIG. 9, the first weight display area HA1 displays "100g".
[0086] The first screen GM1 includes a reset button B7. The reset button B7 is a software button for causing the weight sensor 1 to perform a zero setting for detecting weight thereafter by setting the currently detected weight to zero. When the update button B6 is touched after the reset button B7 is touched on the first screen GM1, the first weight display area HA1 displays a weight of "0g".
[0087] The first screen GM1 includes transition condition information J2. The transition condition information J2 indicates a condition for transitioning to the next screen. The transition condition information J2 illustrated in FIG. 9 indicates a condition for transitioning to the next screen when the weight displayed in the first weight display area HA1 becomes "0g".
[0088] The first screen GM1 includes a next button B8, which is a software button for transitioning to the second screen GM2.
[0089] FIG. 10 is a diagram showing an example of the second screen GM2. The second screen GM2 is a screen for setting the type of food F whose weight is to be detected by the weight sensor 1.
[0090] The second screen GM2 has a type input area NA1. The type input area NA1 is an area for the user P to input text indicating the type of food F detected by the weight sensor 1 by operating a software key or the like. By inputting text in the type input area NA1, the user P can set any type of food F on the second screen GM2 without any restrictions on the text.
[0091] The second screen GM2 includes a scan setting button B9. The scan setting button B9 is a software button for setting the type of food F whose weight is to be detected by the weight sensor 1 by reading a code such as a barcode or a QR code (registered trademark). When the scan setting button B9 is touched, the application execution unit 6000 activates the camera 63. Next, if the application execution unit 6000 is able to read a code from an image captured by the camera 63, it inquires of the food management server 7 about the type of food F indicated by the read data. The application execution unit 6000 sets the type of food F obtained as a response to the inquiry on the second screen GM2 as the type of food F whose weight is to be detected by the weight sensor 1.
[0092] The second screen GM2 has a food type display area HA2. The food type display area HA2 is an area in which icons IC indicating types of food that can be set as the type of food F whose weight is detected by the weight sensor 1 are displayed in a list. Each of the icons IC displayed in the food type display area HA2 can be selected by a touch operation. When an icon IC is selected, the application execution unit 6000 sets the type of food F indicated by the selected icon IC as the type of food F whose weight is detected by the weight sensor 1 on the second screen GM2.
[0093] The second screen GM2 includes a setting confirmation button B10. The setting confirmation button B10 is a software button for confirming the type of food F set on the second screen GM2 by any of the selection in the type input area NA1, the scan setting button B9, and the food type display area HA2. In the food management UI 6300, when the setting confirmation button B10 is touched on the second screen GM2, the second screen GM2 transitions to the third screen GM3.
[0094] FIG. 11 is a diagram showing an example of the third screen GM3. The third screen GM3 is a screen in which the display contents are changed according to a touch operation on a unit setting area TA, which will be described later.
[0095] The third screen GM3 includes third explanatory information J3. The third explanatory information J3 provides an explanation of the operation that the user P performs on the weight sensor 1 in the operation on the third screen GM3. The third explanatory information J3 includes text and an image encouraging the user P to place the food F, the weight of which is to be detected, on the weight sensor 1 directly or via the case 3.
[0096] The third screen GM3 has a second weight display area HA3. The second weight display area HA3 is an area that displays the weight detected by the weight sensor 1. If the reset button B7 is touched on the first screen GM1 before transitioning to the third screen GM3, the second weight display area HA3 displays the weight detected by the weight sensor 1 that has been set to zero. For example, if the reset button B7 is touched with the case 3 placed on the weight sensor 1, the second weight display area HA3 displays the weight minus the weight of the case 3.
[0097] The third screen GM3 has a unit setting area TA. The unit setting area TA is an area for setting a unit for converting the weight of food F detected by the weight sensor 1. The unit setting area TA has a check box C1 for selecting "pieces", which is a unit indicating the number of food items F, as a unit for converting the weight of food items F detected by the weight sensor 1, and a check box C2 for selecting a percentage, which is a unit indicating the proportion of the remaining amount of food items F.
[0098] In the figure, the third screen GM3 on the left shows the third screen GM3 when the check box C1 is checked by a touch operation by the user P. When the check box C1 is checked, a quantity input area NA2 is displayed in the unit setting area TA of the third screen GM3. The quantity input area NA2 is an area for the user P to input the number of any one of the foods F placed on the weight sensor 1, the foods F contained in the case 3, and the eggs F3 contained in the egg holder 4 by using a software key or the like.
[0099] In the figure, the third screen GM3 on the right shows the third screen GM3 when the user P has checked the check box C2 by a touch operation. When the check box C2 is checked, a ratio input area NA3 is displayed in the unit setting area TA of the third screen GM3. The ratio input area NA3 is an area for the user P to input, by a touch operation, a percentage in 10 percent increments of the remaining amount of any one of the foods F: the food F placed on the weight sensor 1, the food F contained in the case 3, and the eggs F3 contained in the egg holder 4.
[0100] If both the check boxes C1 and C2 are unchecked, the quantity input area NA2 and the ratio input area NA3 are not displayed in the unit setting area TA. Also, both the check boxes C1 and C2 cannot be checked at the same time.
[0101] The third screen GM3 includes a next button B11. The next button B11 is a software button for transitioning to the fourth screen GM4.
[0102] FIG. 12 is a diagram showing an example of the fourth screen GM4. The fourth screen GM4 has a food image display area HA4. The food image display area HA4 is an area for displaying a food image FOG.
[0103] When the scan setting button B9 is touched on the second screen GM2 to read the code, the food image display area HA4 displays the food image FOG of the type of food F inquired of the food management server 7. The food image data 7143 of this food image FOG is transmitted from the food management server 7 to the terminal device 6, for example, when the type of food F is inquired of. Furthermore, when an icon IC is selected on the second screen GM2, the food image display area HA4 displays a food image FOG of the type of food F indicated by the selected icon IC. Furthermore, on the second screen GM2, when the type of food F is input in the type input area NA1, the food image display area HA4 can display a photographed image stored in the terminal device 6 as the food image FOG.
[0104] The fourth screen GM4 has a type display area HA5. The type display area HA5 is an area where a description of the type of food F set on the second screen GM2 is displayed.
[0105] On the second screen GM2, when the scan setting button B9 is touched to read the code, the type display area HA5 displays the text of the type of food F returned from the food management server 7. Moreover, when an icon IC is selected on the second screen GM2, the type display area HA5 displays a message indicating the type of food F indicated by the selected icon IC. Furthermore, on the second screen GM2, when the type of food F is input in the type input area NA1, the type display area HA5 displays the text input in the type input area NA1 as the text of the type of food F.
[0106] The fourth screen GM4 displays remaining amount information at setting 7137. The fourth screen GM4 transitioned from the third screen GM3 displays remaining amount information at setting 7137 indicating the number of food F input in the quantity input area NA2 or the ratio input in the ratio input area NA3. The remaining amount information at setting 7137 shown in the example of Fig. 12 indicates "8 pieces".
[0107] The fourth screen GM4 has a saving start date display area HA6 in which the saving start date is displayed. The saving start date displayed in the saving start date display area HA6 can be changed by a touch operation by the user P. In the default saving start date display area HA6, the date on which the fourth screen GM4 is displayed is displayed as the saving start date.
[0108] The fourth screen GM4 has an expiration date display area HA7 in which the expiration date is displayed. The expiration date displayed in the expiration date display area HA7 can be set and changed by the user P's touch operation. When the type of food F is set on the second screen GM2 by a method other than reading a code, the expiration date is not displayed in the default expiration date display area HA7, and a character string indicating that the expiration date has not been set is entered. On the other hand, when the type of food F is set on the second screen GM2 by reading a code, the expiration date received from the food management server 7 is displayed in the default expiration date display area HA7.
[0109] The fourth screen GM4 has a storage location input area NA4 in which a storage location is input. The storage location input in the storage location input area NA4 is selected by the user P from among "refrigerator," "storage," "disaster prevention," and "not set."
[0110] The fourth screen GM4 has a deadline notification timing input area NA5 in which the timing for notifying the deadline is input. The timing input in the deadline notification timing input area NA5 is selected by the user P from among "Do not set", "1 day before", "2 days before", "3 days before", "4 days before", "5 days before", "6 days before", and "7 days before".
[0111] The fourth screen GM4 has a remaining amount notification timing input area NA6 in which the timing for notifying the remaining amount is input. The timing input in the remaining amount notification timing input area NA6 is set by the user P between 0 and 5 units if the unit set in the third screen GM is number, and between 0% and 90% if the unit set in the third screen GM3 is percentage.
[0112] The fourth screen GM4 includes a confirmation button B12 for confirming the contents inputted and displayed on the fourth screen GM4.
[0113] [2. Operation] Next, the operation of this embodiment will be described. First, the operation of the food management system 1000 in the setting related to the weight sensor 1 will be described. Fig. 13 is a flowchart showing the operation of food management system 1000 according to this embodiment. In Fig. 13, flowchart FA shows the operation of terminal device 6, flowchart FB shows the operation of food management server 7, and flowchart FC shows the operation of weight sensor 1.
[0114] The operation of the food management system 1000 shown in Fig. 13 is premised on the fact that the food management application 6130 installed in the terminal device 6 has been properly associated with the weight sensor 1. That is, the operation of the food management system 1000 shown in Fig. 13 is premised on the fact that the function of the food management application 6130 enables the terminal device 6 to obtain the weight detected by the weight sensor 1 via the food management server 7, and that the terminal device 6 can communicate with the weight sensor 1 to be set via the food management server 7. The operation of the food management system 1000 shown in Fig. 13 is also premised on the fact that the weight sensor 1 transmits detected weight information 7134 to the food management server 7, and that the food management server 7 properly updates the food management database 7130 based on the received detected weight information 7134. The weight sensor 1 transmits the detected weight information 7134 to the food management server 7 when it detects a change in weight. In addition to this trigger, the weight sensor 1 also transmits the detected weight information 7134 to the food management server 7 when a predetermined period of time (for example, 15 minutes) has passed since the previous transmission of the detected weight information 7134.
[0115] As shown in the flowchart FA, the application execution unit 6000 of the terminal device 6 determines whether or not to start setting related to the weight sensor 1 (step SA1). For example, when the application execution unit 6000 receives a touch operation on the food management UI 6300 instructing to start setting related to the weight sensor 1, the application execution unit 6000 makes a positive determination in step SA1.
[0116] When the application executing unit 6000 determines not to start the setting related to the weight sensor 1 (step SA1: NO), the application executing unit 6000 returns the process to step SA1 and performs the determination of step SA1 again.
[0117] On the other hand, when it is determined that the setting related to the weight sensor 1 is to be started (step SA1: YES), the application executing unit 6000 displays the food management UI 6300 of the first screen GM1 on the touch panel 62 (step SA2).
[0118] Next, the application executing unit 6000 determines whether or not the update button B6 on the first screen GM1 has been touched (step SA3).
[0119] If the application executing unit 6000 determines that the update button B6 has been touched (step SA3: YES), it displays the weight currently detected by the weight sensor 1 in the first weight display area HA1 of the first screen GM1 (step SA4).
[0120] Here, step SA4 will be described in detail. The application executing unit 6000 transmits weight request information requesting the weight detected by the weight sensor 1 to be set to the food management server 7 via the device communication unit 61. This weight request information includes the user ID 7131 stored in the device storage unit 610 and the sensor ID 1203 of the weight sensor 1 to be set. The food management server 7 transmits detected weight information 7134 corresponding to the combination of the user ID 7131 and the sensor ID 1203 included in the weight request information to the terminal device 6 via the server communication unit 71 as a response to the weight request information. The application executing unit 6000 displays the weight indicated by the received detected weight information 7134 in the first weight display area HA1.
[0121] Returning to the explanation of step SA3, if it is determined that the update button B6 has not been touched (step SA3: NO), the application executing unit 6000 determines whether or not the reset button B7 has been touched (step SA5).
[0122] When the application execution unit 6000 determines that the reset button B7 has been touched (step SA5: YES), it transmits zero setting instruction information instructing execution of zero setting to the food management server 7 via the device communication unit 61 (step SA6). The zero setting instruction information includes the user ID 7131 stored in the terminal storage unit 610 and the sensor ID 1203 of the weight sensor 1 to be set.
[0123] Referring to the flowchart FB, the server control unit 70 of the food management server 7 determines whether or not the server communication unit 71 has received zero setting instruction information from the terminal device 6 (step SB1).
[0124] When the server control unit 70 determines that the zero setting instruction information has not been received from the terminal device 6 (step SB1: NO), it shifts the process to step SB4.
[0125] On the other hand, if the server control unit 70 determines that it has received zero setting instruction information from the terminal device 6 (step SB1: YES), it identifies a record R from the food management database 7130 that includes the combination of user ID 7131 and sensor ID 1203 contained in the received zero setting instruction information (step SB2).
[0126] Next, the server control unit 70 transmits the zero setting instruction information received from the terminal device 6 to the weight sensor 1 through the server communication unit 71 based on the sensor communication information 7132 included in the record R identified in step SB2 (step SB3).
[0127] Referring to the flow chart FC, the sensor control unit 100 of the weight sensor 1 determines whether or not the sensor communication unit 101 has received zero setting instruction information from the food management server 7 (step SC1).
[0128] When the sensor control unit 100 determines that it has not received the zero setting instruction information from the food management server 7 (step SC1: NO), it performs the determination in step SC1 again.
[0129] On the other hand, if the sensor control unit 100 determines that it has received zero setting instruction information from the food management server 7 (step SC1: YES), it performs zero setting (step SC2).
[0130] For example, assume that the weight detected by weight sensor 1 is 100 g when zero setting instruction information is received. After that, when weight sensor 1 performs zero setting, it notifies food management server 7 of the weight obtained by subtracting 100 from the detected weight.
[0131] In this way, by performing zero setting, the weight sensor can notify the food management server 7 of the weight that does not include the weight of the case 3 or the egg holder 4. Furthermore, by performing zero setting, user P can also place a case having a different shape and weight from case 3 on weight sensor 1 and use weight sensor 1 as a weight detection unit. In other words, by performing zero setting, user P can use weight sensor 1 as a weight detection unit using a case of his or her choice.
[0132] Returning to the explanation of step SA5 of the flowchart FA, the application execution unit 6000 of the terminal device 6 determines whether or not the next button B8 has been touched (step SA7).
[0133] If the application executing unit 6000 determines that the next button B8 has not been touched (step SA7: NO), the application executing unit 6000 returns the process to step SA2 and performs the determination in step SA2 again.
[0134] On the other hand, if it is determined that the Next button B8 has been touched (step SA7: YES), the application executing unit 6000 displays the food management UI 6300 of the second screen GM2 on the touch panel 62 (step SA8).
[0135] Next, the application executing unit 6000 determines whether or not the setting confirmation button B10 has been touched (step SA9).
[0136] If the application executing unit 6000 determines that the setting confirmation button B10 has not been touched (step SA9: NO), the application executing unit 6000 performs the determination in step SA9 again.
[0137] On the other hand, if it is determined that the setting confirmation button B10 has been touched (step SA9: YES), the application executing unit 6000 displays the food management UI 6300 of the third screen GM3 on the touch panel 62 (step SA10).
[0138] Next, the application executing unit 6000 determines whether or not the Next button B11 has been touched (step SA11).
[0139] If it is determined that the Next button B11 has not been touched (step SA11: NO), the application executing unit 6000 performs the process of step SA11 again.
[0140] On the other hand, if it is determined that the Next button B11 has been touched (step SA11: YES), the application executing unit 6000 displays the food management UI 6300 of the fourth screen GM4 on the touch panel 62 (step SA12).
[0141] Next, the application executing unit 6000 determines whether or not the Confirm button B12 has been touched (step SA13).
[0142] If it is determined that the Confirm button B12 has not been touched (step SA13: NO), the application executing unit 6000 performs the process of step SA13 again.
[0143] On the other hand, if the application executing unit 6000 determines that the Confirm button B12 has been touched (step SA13: YES), it generates storage request information for requesting storage of information in the food management database 7130 (step SA14).
[0144] Here, step SA14 will be described in detail. When generating the storage request information, the application execution unit 6000 associates the sensor ID 1203 to be set with the user ID 7131 .
[0145] Furthermore, when generating the storage request information, the application executing unit 6000 associates the setting time weight information 7136 indicating the weight displayed in the second weight display area HA3 of the third screen GM3 with the sensor ID 1203 of the setting target.
[0146] Furthermore, when the number of food items F is input in the quantity input area NA2, the application executing unit 6000 associates conversion unit information 7135 indicating the number of food items F and remaining amount at setting information 7137 indicating the number of food items F input in the quantity input area NA2 with the sensor ID 1203 to be set. On the other hand, when the percentage of the remaining amount of food items F is input in the percentage input area NA3, the application executing unit 6000 associates conversion unit information 7135 indicating the percentage of the remaining amount of food items F and remaining amount at setting information 7137 indicating the percentage input in the percentage input area NA3 with the sensor ID 1203 to be set.
[0147] Furthermore, when generating the storage request information, the application execution unit 6000 associates the food image data 7143 of the food image FOG displayed in the food image display area HA4 with the sensor ID 1203 to be set.
[0148] Furthermore, when generating the storage request information, the application executing unit 6000 associates type information 7133 indicating the type of food F displayed in the type display area HA5 with the sensor ID 1203 of the setting target.
[0149] Furthermore, when generating the storage request information, the application execution unit 6000 associates the storage start date information 7139 indicating the storage start date input in the storage start date display area HA6 with the sensor ID 1203 of the setting target.
[0150] Furthermore, when generating the storage request information, the application executing unit 6000 associates deadline information 7140 indicating the deadline entered in the deadline display area HA7 with the sensor ID 1203 of the setting target.
[0151] Furthermore, when generating the storage request information, the application execution unit 6000 associates the storage location information 7138 indicating the storage location input in the storage location input field NA4 with the sensor ID 1203 of the setting target.
[0152] Furthermore, when generating the storage request information, the application execution unit 6000 associates deadline notification timing information 7141 indicating the timing input in the deadline notification timing input field NA5 with the sensor ID 1203 to be set.
[0153] Furthermore, when generating the storage request information, the application executing unit 6000 associates remaining amount notification timing information 7142, which indicates the timing input in the remaining amount notification timing input field NA6, with the sensor ID 1203 to be set.
[0154] Then, the application executing unit 6000 generates storage request information that includes the associated information and requests the food management database 7130 to store the information.
[0155] After generating the storage request information, the application executing unit 6000 transmits the generated storage request information to the food management server 7 via the terminal communication unit 61 (step SA15).
[0156] Referring to the flow chart FC, the server control unit 70 determines whether or not storage request information has been received by the server communication unit 71 (step SB4).
[0157] When the server control unit 70 determines that the storage request information has been received by the server communication unit 71 (step SB4: YES), it stores various information included in the received storage request information in the food management database 7130 (step SB5).
[0158] In step SB5, the server control unit 70 identifies a record R having a combination of the user ID 7131 and the sensor ID 1203 included in the received storage request information from the records R stored in the food management database 7130. If the server control unit 70 can identify the record R, it stores various information included in the received storage request information in the identified record R.
[0159] Next, the operation of food management system 1000 after the weight sensor 1 has been set will be described. Figure 14 is a flowchart showing the operation of the food management system 1000. The operation in Figure 14 is premised on the premise that the food management server 7 appropriately updates the detected weight information 7134 in the food management database 7130 every time the weight sensor 1 detects the weight of the food F.
[0160] In FIG. 14, a flowchart FD shows the operation of the terminal device 6, and a flowchart FE shows the operation of the food management server 7.
[0161] The application execution unit 6000 of the terminal device 6 determines whether or not to display the food management UI 6300 relating to the remaining amount of food F on the touch panel 62 (step SD1). For example, when the application execution unit 6000 receives a touch operation on the food management UI 6300 instructing to display the remaining amount of food F, the application execution unit 6000 makes a positive determination in step SD1.
[0162] When the application execution unit 6000 determines that the food management UI 6300 related to the remaining amount of food F is to be displayed on the touch panel 62 (step SD1: YES), the application execution unit 6000 transmits record request information requesting record R from the food management server 7 via the device communication unit 61 (step SD2). The record request information transmitted in step SD2 includes the user ID 7131 stored in the device storage unit 610.
[0163] Referring to flowchart FE, when the server control unit 70 of the food management server 7 receives record request information via the server communication unit 71 (step SE1), it identifies a record R containing the user ID 7131 included in the received record request information from the food management database 7130 (step SE2).
[0164] Then, the server control unit 70 transmits the record R identified by the server communication unit 71 to the terminal device 6 (step SE3).
[0165] Referring to the flowchart FD, when the application execution unit 6000 of the terminal device 6 receives the record R via the terminal communication unit 61 (step SD3), it executes a generation process for generating a food management UI 6300 relating to the remaining amount of food F (step SD4).
[0166] FIG. 15 is a flowchart showing the operation of the terminal device 6 in the generation process. The application execution unit 6000 references the record R received in step SD3, and identifies one sensor ID 1203 (step SD11).
[0167] Next, the application execution unit 6000 calculates the weight of food F per unit in the unit indicated by the conversion unit information 7135 corresponding to the sensor ID 1203 identified in step SD11 based on the set weight information 7136 and set remaining amount information 7137 corresponding to the sensor ID 1203 identified in step SD11 (step SD12).
[0168] Next, the application execution unit 6000 converts the weight of the food F indicated by the detected weight information 7134 associated with the sensor ID 1203 identified in step SD11 based on the weight calculated in step SD12 into the unit indicated by the conversion unit information 7135 (step SD13).
[0169] Next, the application executing unit 6000 generates remaining amount information ZJ1 indicating the converted weight of food F as the remaining amount of food F (step SD14).
[0170] Next, the application executing unit 6000 determines whether the remaining amount of food F indicated by the remaining amount information ZJ generated in step SD14 corresponds to the timing indicated by the remaining amount notification timing information 7142 (step SD15).
[0171] If the application execution unit 6000 determines that the timing corresponds to the timing indicated by the remaining amount notification timing information 7142 (step SD15: YES), it generates remaining amount warning information KJ1 (step SD16), and if it determines that the timing does not correspond (step SD15: NO), it transitions to step SD17.
[0172] The application executing unit 6000 determines whether the current date corresponds to the timing indicated by the deadline notification timing information 7141 (step SD17).
[0173] If the application execution unit 6000 determines that the timing corresponds to the timing indicated by the deadline notification timing information 7141 (step SD17: YES), it generates deadline warning information KJ2 (step SD18), and if it determines that the timing does not correspond (step SD17: NO), it transitions to step SD19.
[0174] The application execution unit 6000 generates an object OB including the information generated in steps SD12 to SD18 and the food image FOG indicated by the food image data 7143 associated with the sensor ID 1203 identified in step SD11 (step SD19).
[0175] Next, the application execution unit 6000 determines whether or not there is a sensor ID 1203 in record R that has not been specified in step SD11 (step SD20).
[0176] If the application execution unit 6000 determines that there is a sensor ID 1203 that has not been identified in step SD11 (step S20: YES), the application execution unit 6000 returns to the process in step SD11, identifies the unidentified sensor ID 1203 in step SD11, and executes the process from step SD12 onwards again.
[0177] On the other hand, if the application execution unit 6000 determines in step SD11 that there is no unspecified sensor ID 1203 (step SD20: NO), it generates a food management UI 6300 including all of the objects OB generated in step SD17 (step SB21).
[0178] Here, the operation shown in FIG. 15 will be specifically described by taking as an example a case where the food management UI 6300 shown in FIG. 8 is generated based on the record R shown in FIG.
[0179] The application executing unit 6000 generates an object OB1 based on various information associated with the sensor ID 1203 of the first weight sensor 11. The application executing unit 6000 calculates the weight of milk F1 per 1 percent of the remaining amount of milk F1 filled in the container based on the weight information at time of setting 7136 and the remaining amount information at time of setting 7137. Next, the application executing unit 6000 converts the weight of milk F1 indicated by the detected weight information 7134 into a percentage based on the calculated weight. Then, the application executing unit 6000 generates remaining amount information ZJ1 by changing the color of the bar of the number corresponding to the converted weight of milk F1. Next, the application executing unit 6000 determines that the remaining amount of milk F1 indicated by the remaining amount information ZJ1 corresponds to the timing indicated by the remaining amount notification timing information 7142, and generates remaining amount warning information KJ1. On the other hand, the application executing unit 6000 determines that the current date does not correspond to the timing indicated by the deadline notification timing information 7141, and does not generate deadline warning information KJ2. Then, the application execution unit 6000 generates an object OB1 including the generated remaining amount information ZJ1, the generated remaining amount warning information KJ1, and the food image FOG of milk F1 indicated by the food image data 7143.
[0180] As described above, when the remaining amount of food F is indicated as a percentage, the notification is not limited to a configuration in which the amount is indicated by a bar in 20% increments, and may be indicated by a character string in 10% increments, such as "about 10%" or "about 20%", or may be indicated by an actual percentage. For example, when the weight of milk F1 indicated by the detected weight information 7134 is converted into a percentage unit and the result is "8%, " the application execution unit 4000 may generate remaining amount information ZJ1 indicating the character string "about 10%" instead of an image of a bar. The application execution unit 4000 may also generate remaining amount information ZJ1 indicating the character string "8%," which is the actual converted value, instead of an image of a bar.
[0181] The application execution unit 6000 generates an object OB2 based on various information associated with the sensor ID 1203 of the second weight sensor 12. The application execution unit 6000 calculates the weight of one beer F2 based on the weight information at time of setting 7136 and the remaining amount information at time of setting 7137. Next, the application execution unit 6000 converts the weight of the beer F2 indicated by the detected weight information 7134 into units of "pieces" based on the calculated weight. Then, the application execution unit 6000 generates remaining amount information ZJ2 indicating the converted weight of the beer F2 as the remaining amount of the beer F2. The application execution unit 6000 determines that the remaining amount of beer F2 indicated by the remaining amount information ZJ2 does not correspond to the timing indicated by the remaining amount notification timing information 7142, and also determines that the current date does not correspond to the expiration date notification timing information 7141, and does not generate remaining amount warning information KJ1 and expiration date warning information KJ2. Then, the application execution unit 6000 generates an object OB2 including the generated remaining amount information ZJ2 and the food image FOG of the beer F2 indicated by the food image data 7143.
[0182] The application executing unit 6000 generates an object OB3 based on various information associated with the sensor ID 1203 of the third weight sensor 13. The application executing unit 6000 calculates the weight of one egg F3 based on the setting weight information 7136 and the setting remaining amount information 7137. Next, the application executing unit 6000 converts the weight of the eggs F3 indicated by the detected weight information 7134 into units of "pieces" based on the calculated weight. The application executing unit 6000 then generates remaining amount information ZJ3 indicating the converted weight of the eggs F3 as the remaining amount of the eggs F3. Next, the application executing unit 6000 determines that the remaining amount of eggs F3 indicated by the remaining amount information ZJ3 does not correspond to the timing indicated by the remaining amount notification timing information 7142, and does not generate remaining amount warning information KJ1. On the other hand, the application executing unit 6000 determines that the current date corresponds to the deadline notification timing information 7141, and generates deadline warning information KJ2. Then, the application executing unit 6000 generates an object OB3 including the generated remaining amount information ZJ2, the generated expiration date warning information KJ2, and the food image FOG of the egg F3 indicated by the food image data 7143.
[0183] The application execution unit 6000 generates an object OB4 based on various information associated with the sensor ID 1203 of the fourth weight sensor 14. The object OB4 is determined in the same manner as the object OB1 described above, and is generated in the same manner.
[0184] When the application execution unit 6000 generates the objects OB1, OB2, OB3, and OB4, it includes these generated objects OB in the food management UI 4300.
[0185] Returning to the explanation of the flowchart FD shown in FIG. 14, when the application execution unit 6000 executes the generation process, it displays the food management UI 6300 executed in the generation process on the touch panel 62 (step SD5).
[0186] [3. Effects, etc.] As described above, in this embodiment, the food management app 6130 causes the terminal control unit 60 of the terminal device 6 equipped with the touch panel 62 to function as an app execution unit 6000 that acquires the weight of food F detected by the weight sensor 1, converts the acquired weight of food F into a unit indicating the number of food F, and displays the converted weight of food F on the touch panel 62 as the remaining amount of food F.
[0187] The terminal device 6 also includes a touch panel 62 and a terminal control unit 60 that acquires the weight of food F detected by the weight sensor 1, converts the acquired weight of food F into a unit indicating the number of pieces of food F, and displays the converted weight of food F on the touch panel 62 as the remaining amount of food F.
[0188] The food management application 6130 and the terminal device 6 can convert the weight of the food F detected by the weight sensor 1 into a unit that allows the user P to easily grasp the remaining amount of food F, and then notify the user P. Therefore, the user P can easily grasp the weight of the food F detected by the weight sensor 1 as the remaining amount of food F.
[0189] The application execution unit 6000 accepts an input of the number of pieces of food F by the user P, and converts the acquired weight of food F based on the accepted number of pieces of food F and the weight of food F acquired when the number of pieces of food F was accepted.
[0190] This allows the weight of each piece of food F to be calculated, and the weight of the food F detected by the weight sensor 1 can be accurately converted into a unit indicating the number of pieces of food. Therefore, the user P can easily and accurately grasp the weight of the food F detected by the weight sensor 1 as the remaining amount of food F.
[0191] In addition, in this embodiment, the food management app 6130 causes the terminal control unit 60 of the terminal device 6 equipped with the touch panel 62 to function as an app execution unit 6000 that acquires the weight of food F detected by the weight sensor 1, converts the acquired weight of food F into a unit indicating the percentage of remaining amount of food F, and displays the converted weight of food F as the remaining amount of food F on the touch panel 62.
[0192] The terminal device 6 also includes a touch panel 62 and a terminal control unit 60 that acquires the weight of food F detected by the weight sensor 1, converts the acquired weight of food F into a unit indicating the percentage of remaining food F, and displays the converted weight of food F as the remaining amount of food F on the touch panel 62.
[0193] The food management application 6130 and the terminal device 6 can convert the weight of the food F detected by the weight sensor 1 into a unit that allows the user P to easily grasp the remaining amount of food F, and then notify the user P. Therefore, the user P can easily grasp the weight of the food F detected by the weight sensor 1 as the remaining amount of food F.
[0194] In addition, the application execution unit 6000 accepts input of the remaining percentage of food F from user P, and converts the acquired weight of food F based on the accepted remaining percentage of food F and the weight of food F acquired when the remaining percentage of food F was accepted.
[0195] This makes it possible to obtain the weight of food F per unit of proportion, and therefore the weight of food F detected by weight sensor 1 can be accurately converted into a unit that indicates the proportion of the remaining amount of food. Therefore, user P can easily and accurately grasp the weight of food F detected by weight sensor 1 as the remaining amount of food F.
[0196] In addition, in this embodiment, the food management app 6130 causes the terminal control unit 60 of the terminal device 6 equipped with the touch panel 62 to function as an app execution unit 6000 that acquires the weight of food F detected by the weight sensor 1, sets the unit for converting the weight of food F detected by the weight sensor 1 to a unit selected by the user P from a unit indicating the number of foods F and a unit indicating the percentage of remaining food F, and converts the acquired weight of food F into a unit indicating the number of foods F if the set unit is a unit indicating the percentage of remaining food F, and converts the acquired weight of food F into a unit indicating the percentage of remaining food F if the set unit is a unit indicating the percentage of remaining food F, and displays the converted weight of food F as the remaining amount of food F on the touch panel 62.
[0197] The terminal device 6 includes a touch panel 62 and a terminal control unit 60. The terminal control unit 60 acquires the weight of food F detected by the weight sensor 1, sets the unit into which the weight of food F detected by the weight sensor 1 is converted to a unit selected by the user P from a unit indicating the number of food F and a unit indicating the percentage of the remaining amount of food F, converts the acquired weight of food F into a unit indicating the number of food F when the set unit is a unit indicating the percentage of the remaining amount of food F, and displays the converted weight of food F on the touch panel 62 as the remaining amount of food F.
[0198] According to this food management app 6130 and terminal device 6, the weight of food F detected by the weight sensor 1 can be converted into a unit that allows the user P to easily grasp the remaining amount of food F and then notified to the user P. Therefore, the user P can easily grasp the weight of food F detected by the weight sensor 1 as the remaining amount of food F. In addition, since the weight of food F detected by the weight sensor 1 can be converted into a unit selected by the user P and then notified to the user P, the user P can more easily grasp the weight of food F detected by the weight sensor 1 as the remaining amount of food F.
[0199] The application execution unit 6000 accepts either an input of the number of foods F by the user P or an input of the percentage of remaining amount of food F by the user P. When the application execution unit 6000 accepts an input of the number of foods F, it converts the weight of food F into a unit indicating the number of foods F based on the accepted number of foods F and the weight of food F obtained when the number of foods F is accepted, and when the application execution unit 6000 accepts an input of the percentage of remaining amount of food F, it converts the weight of food F into a unit indicating the percentage of remaining amount of food F based on the accepted percentage of remaining amount of food F and the weight of food F obtained when the percentage of remaining amount of food F is accepted.
[0200] This makes it possible to obtain the weight of food F per unit in the unit selected by the user, and therefore the weight of food F detected by weight sensor 1 can be accurately converted into the unit selected by user P. As a result, user P can more easily and accurately grasp the weight of food F detected by weight sensor 1 as the remaining amount of food F.
[0201] Also, in this embodiment, the application execution unit 6000 causes the weight sensor 1 to perform a zero setting, which detects the weight by setting the currently detected weight to zero, and obtains the weight of the food F detected by the weight sensor 1 that has been set to zero.
[0202] This allows the user P to be notified of the weight excluding the weights of the case 3 and the egg holder 4 as the remaining amount of food F. Therefore, the user P can easily and more accurately grasp the weight of food F detected by weight sensor 1 as the remaining amount of food F.
[0203] In this embodiment, the food management application 6130 is an application program that can be installed in the terminal device 6.
[0204] As a result, a terminal device 6 that does not have a function for notifying the weight of food F detected by the weight sensor 1 as the remaining amount of food F can be made into a terminal device 6 that has this function by installing the food management application 6130. Therefore, a general-purpose terminal device 6 can be made into a terminal device 6 that allows the user P to easily grasp the weight of food F detected by the weight sensor 1 as the remaining amount of food F.
[0205] (Other embodiments) As described above, the embodiments have been described as examples disclosed in this application. However, the technology in this disclosure is not limited to this, and can be applied to embodiments in which modifications, substitutions, additions, omissions, etc. are made. In addition, it is also possible to combine the components described in the above embodiments to create new embodiments. Therefore, other embodiments will be exemplified below.
[0206] For example, in the embodiment described above, record R is stored in food management database 7130 and food F detected by weight sensor 1 is managed by food management server 7, but record R may be stored in device storage unit 410 and food management app 6130 may manage various information related to food F whose weight is detected by weight sensor 1. In this configuration, app execution unit 6000 appropriately updates the content of record R stored in device storage unit 410 in the same way as food management server 7 described above. In this configuration, food management system 1000 does not need to include food management server 7, and the system configuration is simplified.
[0207] Also, for example, in the above-described embodiment, in the settings related to weight sensor 1, weight sensor 1 and terminal device 6 are configured to communicate via food management server 7, but weight sensor 1 and terminal device 6 may also communicate without via food management server 7. In this configuration, weight sensor 1 and terminal device 6 may be configured to communicate via communication device 8, or may be configured to communicate directly.
[0208] Also, for example, in each of the above-mentioned embodiments, "pieces" is exemplified as a unit indicating the number of food items F, but the unit indicating the number of food items F is not limited to "pieces" and may be other counter words such as "book", "sheet", "piece", "set", etc., and may be different depending on the type of food items F. Also, although percentage is exemplified as a unit indicating the proportion of the remaining amount of food items F, the unit indicating the proportion of the remaining amount of food items F is not limited to percentage and may be other units indicating proportions such as per thousand or commission.
[0209] In addition, for example, when the expiration date information 7140 included in the received storage request information includes information indicating that an expiration date has not been set, the server control unit 70 may calculate an expiration date based on the storage start date information 7139 included in the received storage request information, and store the expiration date information 7140 indicating the calculated expiration date in the food management database 7130.
[0210] For example, the above-mentioned food management system 1000 has been exemplified as managing food F inside the refrigerator 2 and food F outside the refrigerator 2. However, the weight sensor 1 may be provided only inside the refrigerator 2, and the food management system 1000 may manage only food F inside the refrigerator 2. The food management system 1000 may also manage only food F outside the refrigerator 2.
[0211] For example, the types of compartments formed in main box 20 of refrigerator 2 are not limited to refrigeration compartment 21, ice-making compartment 22, fresh-freezing compartment 23, freezer compartment 24, and vegetable compartment 25, and may be fewer or may have other types of compartments. Also, the number of doors provided at the opening on the front of refrigeration compartment 21 may be one.
[0212] For example, the functions of the server control unit 70, the terminal control unit 60, and the sensor control unit 100 may be realized by multiple processors or semiconductor chips.
[0213] Each unit shown in Figures 5 and 6 is an example, and the specific implementation form is not particularly limited. In other words, it is not necessarily necessary to implement hardware corresponding to each unit individually, and it is of course possible to configure the functions of each unit by executing a program by one processor. Also, some of the functions realized by software in the above-mentioned embodiment may be hardware, or some of the functions realized by hardware may be software. In addition, the specific detailed configurations of the weight sensor 1, the terminal device 6, and the other units of the food management server 7 may also be changed arbitrarily without departing from the spirit of the present invention.
[0214] Also, for example, the step units of the operation shown in Figs. 13-15 are divided according to the main processing contents in order to facilitate understanding of the operation of the food management system 1000, and the present invention is not limited by the manner of division or the names of the processing units. The operation may be divided into more step units according to the processing contents. Also, one step unit may be divided to include more processing. Also, the order of the steps may be appropriately changed within a range that does not interfere with the purpose of the present invention. For example, the flowchart shown in Fig. 13 is a flowchart in which the screen transition is performed in the order of the first screen GM1, the second screen GM2, the third screen GM3, and the fourth screen GM4 without returning from the destination screen to the source screen, but the operation of the flowchart shown in Fig. 13 may include a step for returning from the destination screen to the source screen, and may be an operation that takes into account returning to the source screen.
[0215] It should be noted that the above-described embodiments are intended to illustrate the technology of the present disclosure, and various modifications, substitutions, additions, omissions, and the like can be made within the scope of the claims or their equivalents. [Industrial Applicability]
[0216] As described above, the program and terminal device according to the present invention can be used to notify a user of the weight of food detected by a weight sensor as the amount of food remaining. [Explanation of symbols]
[0217] 1 Weight Sensor 6 Terminal Equipment 7. Food Management Server 11 First weight sensor 12 Second weight sensor 13 3rd Weight Sensor 14 4th Weight Sensor 60 Terminal control unit (control unit) 62 Touch panel (display) 6000 Application execution unit (program execution unit) 6130 Food management applications (programs, application programs) F Food P User
Claims
1. A control unit of a terminal device having a display unit, a program execution unit that displays, on a single screen, an area for displaying the weight of the food detected by the weight sensor and an area for setting a unit for converting the weight of the food detected by the weight sensor, using the display unit; the unit setting area accepts selection of a unit into which the weight of the food detected by the weight sensor is converted, from a unit indicating the number of food pieces and a unit indicating the percentage of remaining food. program.
2. The program execution unit is When a selection of a unit indicating the number of food items is received in the area for setting the unit, In the area for setting the unit, an area for inputting the number of food items detected by the weight sensor is displayed. The program according to claim 1.
3. The program execution unit is When the selection of a unit indicating the percentage of remaining food is accepted in the area for setting the unit, In the area for setting the unit, an area for inputting the percentage of the remaining amount of food detected by the weight sensor is displayed. The program according to claim 1.
4. A display unit; a control unit that displays, on a single screen, an area for displaying the weight of the food detected by the weight sensor and an area for setting a unit for converting the weight of the food detected by the weight sensor, and the unit setting area accepts selection of a unit into which the weight of the food detected by the weight sensor is converted, from a unit indicating the number of food pieces and a unit indicating the percentage of remaining food. Terminal device.
Citation Information
Patent Citations
Smart Scales - Cooking Proportion System
JP2016521348A
Sensor communicating with refrigerator and refrigerator control system including the sensor
JP2017133825A