JP7489610B2 - Food Control System - Google Patents

Description

The present invention relates to a food management system.

Conventionally, there is known a system for managing food whose weight is detected by a weight sensor (see, for example, Patent Document 1). Patent Document 1 discloses a system in which information relating to the weight of a drink placed on a weight sensor is output to a refrigerator control unit, and the refrigerator control unit manages the start and end of storage of the drink based on the information about the drink's weight.

JP 2017-133825 A

However, the system described in Patent Literature 1 is based on the premise that the type of food whose weight is to be detected by the weight sensor is predetermined, and therefore the type of food whose weight is to be detected by the weight sensor cannot be set to a type desired by the user. Therefore, the system described in Patent Literature 1 may not be able to manage the type of food desired by the user.
In view of the above-mentioned circumstances, an object of the present invention is to enable a user to manage the type of food desired in food management using a weight sensor.

In order to achieve the above-mentioned object, the present invention provides a food management system which comprises a weight sensor and a terminal device, and which manages food whose weight is detected by the weight sensor, the weight sensor being provided inside or outside a refrigerator, the terminal device acquiring sensor identification information which identifies the weight sensor, accepting a selection of a combination from a list of combinations of food images and food types as a user's input of a food image and a type of the food, accepting a selection of the captured image from captured images stored in the terminal device as an input of a food image, accepting an input of the type of food by the user when the input of the food image is accepted by the selection of the captured image, and when the combination is selected, associating the acquired sensor identification information with type information indicating the type of food included in the accepted combination and food image data indicating the food image included in the accepted combination, and when the captured image is selected, associating the acquired sensor identification information with type information indicating the type of food included in the accepted combination and food image data indicating the food image which is the selected captured image .

According to the present invention, the type of food whose weight is detected by the weight sensor can be set to the type desired by the user, so that when managing food using a weight sensor, the type of food desired by the user can be managed.

According to the present invention, when managing food using a weight sensor, the user can manage the type of food desired.

FIG. 1 is a diagram showing the configuration of a food management system. FIG. 4 is a perspective view of the front of the weight sensor as viewed from above. FIG. 4 is a diagram showing the functional configuration of a weight sensor. FIG. 2 is a diagram showing the functional configuration of a terminal device and a food management server. FIG. 13 is a diagram showing an example of a food management database. FIG. 13 is a diagram showing an example of a food management UI. 11A and 11B are diagrams showing an example of screen transitions in a food management UI. 4 is a flowchart showing the operation of the food management system. 4 is a flowchart showing the operation of the food management system. 4 is a flowchart showing the operation of the food management system.

A first invention is a food management system that includes a weight sensor and a terminal device and manages food whose weight is detected by the weight sensor.The terminal device acquires sensor identification information that identifies the weight sensor, accepts input of the type of the food by a user, and associates the acquired sensor identification information with type information indicating the accepted type of the food.
According to this, the type of food whose weight is detected by the weight sensor can be set to the type desired by the user, so that the type of food desired by the user can be managed in food management using the weight sensor.

In a second invention, the terminal device acquires the weight of the food detected by the weight sensor, and associates remaining amount information indicating the remaining amount of the food corresponding to the acquired weight of the food with the sensor identification information and the type information.
This allows the weight sensor to be associated with the type of food whose weight is detected by the weight sensor, and the remaining amount of food whose weight is detected by the weight sensor, so that when managing food using the weight sensor, the remaining amount of the type of food desired by the user can be managed.

In a third aspect, the terminal device is capable of communicating with the weight sensor, and acquires the sensor identification information from the weight sensor when a communication connection with the weight sensor is established for the first time.
This allows the sensor identification information obtained when a communication connection is established with the weight sensor for the first time to be associated with type information, and allows the user to start managing the type of food desired from after a communication connection is established for the first time between the weight sensor and the terminal device.

In a fourth aspect of the present invention, when a communication connection is established for the first time with the terminal device, the weight sensor notifies the user that a communication connection is being established.
This allows the user to easily determine whether or not a communication connection has been established with the terminal device, so that even if there are multiple weight sensors, the user can easily determine which weight sensor the terminal device has established a communication connection with.

In a fifth aspect of the present invention, the terminal device associates storage start date information, which indicates a storage start date when storage of the food, the weight of which is detected by the weight sensor, with the sensor identification information and the type information.
This allows the weight sensor to be associated with the type of food whose weight is detected by the weight sensor, and the storage start date of the food whose weight is detected by the weight sensor, so that when managing food using the weight sensor, the storage start date of the type of food desired by the user can be managed.

In a sixth aspect, the terminal device associates the storage start date information with the sensor identification information and the type information, using the date on which the sensor identification information and the type information are associated as the storage start date.
According to this, the date on which the sensor identification information and type information are associated may be the date on which storage of the food began, so that the appropriate storage start date can be managed for the type of food desired by the user.

In a seventh aspect, the terminal device determines the day when an increase in weight detected by the weight sensor exceeds a predetermined threshold as the storage start date, and associates the storage start date information with the sensor identification information and the type information.
According to this, since the day on which the weight detected by the weight sensor changes significantly may be the day on which storage of new food begins, the user can manage the appropriate storage start date for the type of food desired.

In an eighth aspect of the present invention, the terminal device receives an input of the storage start date by a user, and associates the storage start date information indicating the received storage start date with the sensor identification information and the type information.
This allows the user to manage the storage start date as any date of their choice, making it possible to manage an appropriate storage start date for the type of food desired by the user, regardless of the food's usage status.

In a ninth aspect of the present invention, the weight sensor is provided in a refrigerator and detects the weight of the food stored in the refrigerator.
According to this, in food management using a weight sensor, it is possible to manage the food that the user stores in the refrigerator and that is the type of food that the user desires.

Hereinafter, an embodiment of the present invention will be described with reference to the drawings.
FIG. 1 is a diagram showing the configuration of a food management system 1000.

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 the weight sensor 1. The food management system 1000 shown in Figure 1 exemplifies a case in which milk F1, apples F2, and rice F3 are managed as food F.

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

The food management system 1000 is equipped with three weight sensors 1: a first weight sensor 11, a second weight sensor 12, and a third weight sensor 13.

The first weight sensor 11 and the second weight sensor 12 are provided in a refrigerator 2 installed in a house H. In detail, the first weight sensor 11 is provided in a door pocket in the refrigerator compartment 21 of the refrigerator 2, and the second weight sensor 12 is provided in a drawer 25A provided in the vegetable compartment 25 of the refrigerator 2. The first weight sensor 11 has a container filled with milk F1 placed on its upper surface, and detects the weight of the milk F1 filled in the placed container. The second weight sensor 12 has a storage case 3 placed on its upper surface, and detects the total weight of the apples F2 stored in the storage case 3.

The third weight sensor 13 is provided on a shelf 7 installed in the house H. The storage case 3 is placed on the upper surface of the third weight sensor 13, and detects the total weight of the rice F3 stored in the storage case 3.

The food F whose weight is detected by the first weight sensor 11 is not limited to milk F1, but may be other drinks or foods F other than drinks. The same applies to the second weight sensor 12 and the third weight sensor 13. The first weight sensor 11 may have a storage case 3 placed on its upper surface and detect the total weight of the food F contained in the placed storage case 3. The second weight sensor 12 and the third weight sensor 13 may detect the weight of the food F placed on its upper surface without going through the storage case 3, like the first weight sensor 11. The number and installation locations of the weight sensors 1 provided in the food management system 1000 of this embodiment are merely examples and are not limited to the number and installation locations shown in FIG. 1.

FIG. 2 is a perspective view of the weight sensor 1 in an installed state, as viewed from above.
The weight sensor 1 has a substantially rectangular parallelepiped shape, and includes an LED light 1031 on the front side. The weight sensor 1 also includes recesses 1051 on the front, rear, left side, and right side.

When the weight sensor 1 detects the weight of the food F without using the storage case 3 like the first weight sensor 11, the food F is placed on the upper surface.

When the storage case 3 is placed on the upper surface, as in the case of the second weight sensor 12 and the third weight sensor 13, the weight sensor 1 is fixed to the bottom surface of the storage case 3 with the engagement portion provided on the bottom surface of the storage case 3 engaging with the recess 1051.

Returning to the explanation of Fig. 1, the food management system 1000 includes a terminal device 4 having a touch panel 43. The terminal device 4 is, for example, 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 4, and the terminal device 4 communicates with the weight sensor 1 and the food management server 6 through the function of the application.
In the following description, the 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 "4130".

In this embodiment, if the terminal device 4 can establish a communication connection with the communication device 5, it communicates with the food management server 6 via the communication device 5, and if it cannot establish a communication connection with the communication device 5, it communicates with the food management server 6 without going through the communication device 5.

The communication device 5 connects to a global network GN, which includes the Internet, a telephone network, and other communication networks, and communicates with a food management server 6 connected to the global network GN. The communication device 5 is an interface device for connecting the terminal device 4 to the global network GN. The communication device 5 has functions related to a modem, a router function, a NAT (Network Address Translation) function, etc. The communication device 5 transfers data sent and received between the terminal device 4 and the food management server 6 connected to the global network GN.

The food management system 1000 includes a food management server 6. The food management server 6 is a server device that manages the food F whose weight is detected by the weight sensor 1, and is connected to the global network GN. Note that in each figure, the food management server 6 is represented by a single block, but this does not necessarily mean that the food management server 6 is composed of a single server device. For example, the food management server 6 may be composed of multiple server devices with different processing contents.

Next, the functional configurations of the weight sensor 1, the terminal device 4, and the food management server 6 will be described.
FIG. 3 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, an alarm unit 103, and a power supply unit 104.

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 the cooperation of hardware and software, such as the sensor processor 110 reading out a control program 1201 stored in the sensor storage unit 120 and executing the process.

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 6132 which is identification information of the weight sensor 1, and various other data. The sensor ID 6132 corresponds to the sensor identification information of the present invention. The sensor storage unit 120 has a non-volatile storage area for non-volatilely storing programs and data. The sensor storage unit 120 may also have a volatile storage area and constitute a work area for temporarily storing programs executed by the sensor processor 110 and data to be processed.

The sensor communication unit 101 includes communication hardware that complies with a specific communication standard, and communicates with the terminal device 4 under the control of the sensor control unit 100. In this embodiment, the Bluetooth (registered trademark) standard is exemplified as the communication standard used by the sensor communication unit 101, but the communication standard used by the sensor communication unit 101 may be a short-range wireless communication standard other than the Bluetooth standard, a wireless communication standard other than the short-range wireless communication standard, or a wired communication standard.

The 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 the food F placed on the weight sensor 1 under the control of the sensor control unit 100. The detection unit 102 outputs the detection result to the sensor control unit 100.

The notification unit 103 includes an LED light 1031, and notifies various information to the outside by turning on, off, or blinking the LED light 1031 according to the control of the sensor control unit 100. The LED light 1031 is provided, for example, on the exterior side surface of the weight sensor 1.

The power supply unit 104 includes a battery 1041 and supplies power to each part of the weight sensor 1 according to the control of the sensor control unit 100. The power supply unit 104 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 1041.

Figure 4 is a block diagram showing the functional configuration of the terminal device 4 and food management server 6 of the food management system 1000.

First, the functional configuration of the food management server 6 will be described.
The food management server 6 includes a server control unit 60 and a server communication unit 61 .

The server control unit 60 includes a server processor 600, which is a processor that executes programs such as a CPU or MPU, and a server memory unit 610, and controls each part of the food management server 6. The server control unit 60 executes various processes through cooperation between hardware and software, such that the server processor 600 reads out a control program 6110 stored in the server memory unit 610 and executes the processes.

The server memory unit 610 has a storage area for storing programs executed by the server processor 600 and data processed by the server processor 600. The server memory unit 610 stores a control program 6110 executed by the server processor 600, setting data 6120 related to the settings of the food management server 6, a food management database 6130, and various other data. The server memory unit 610 has a non-volatile storage area for non-volatilely storing programs and data. The server memory unit 610 may also have a volatile storage area and constitute a work area for temporarily storing programs executed by the server processor 600 and data to be processed.

FIG. 5 is a diagram showing an example of the food management database 6130.
The food management database 6130 is a database that stores various information related to the food F whose weight is detected by the weight sensor 1.

A record R stored in the food management database 6130 includes a user ID 6131, a sensor ID 6132, type information 6133, weight information 6134, remaining amount information 6135, storage start date information 6136, storage location information 6137, expiration date information 6138, and food image data 6139.

In addition, one record R stored in the food management database 6130 may further include one or more other types of information.

The user ID 6131 is identification information that identifies the user P who uses the food management app 4130, and is appropriately assigned to the user P who uses the food management app 4130.

The sensor ID 6132 is identification information that identifies the weight sensor 1. In one record R, one or more sensor IDs 6132 are associated with a user ID 6131.

The type information 6133 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 6133 as the sensor IDs 6132 are associated with a user ID 6131.

The weight information 6134 is information indicating the weight of the food F detected by the weight sensor 1. In one record R, the same number of pieces of weight information 6134 as the sensor IDs 6132 are associated with a user ID 6131.

The remaining amount information 6135 is information indicating the remaining amount of food F corresponding to the weight of food F detected by the weight sensor 1. In one record R, the same number of remaining amount information 6135 as sensor IDs 6132 are associated with a user ID 6131. The remaining amount of food F indicated by the remaining amount information 6135 may be indicated in units corresponding to the type of food F, as shown in FIG. 5.

The storage start date information 6136 is information that indicates the storage start date of the food F detected by the weight sensor 1. In one record R, the same number of storage start date information 6136 as sensor IDs 6132 are associated with a user ID 6131.

The storage location information 6137 is information that indicates the storage location of the food F detected by the weight sensor 1. In one record R, the same number of storage location information 6137 as sensor IDs 6132 are associated with a user ID 6131.

The expiration date information 6138 is information that indicates the expiration date of the best-before date or use-by 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 6138 as sensor IDs 6132 are associated with a user ID 6131.

The food image data 6139 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 6139 as sensor IDs 6132 are associated with a user ID 6131.

The record R shown in FIG. 5 is a record R relating to the first weight sensor 11, the second weight sensor 12, and the third weight sensor 13.

The user ID 6131 of one record R shown in Figure 5 corresponds to "SE0001" as the sensor ID 6132 of the first weight sensor 11, to "SE0002" as the sensor ID 6132 of the second weight sensor 12, and to "SE0003" as the sensor ID 6132 of the third weight sensor 13.

The sensor ID 6132 of the first weight sensor 11 corresponds to type information 6133 indicating "Milk", weight information 6134 indicating a weight of "0.5 kgf", remaining amount information 6135 indicating a remaining amount of "500 ml", storage start date information 6136 indicating a storage start date of "2020/3/3", storage location information 6137 indicating a storage location in the "refrigerator", expiration date information 6138 indicating an expiration date of "2020/3/10", and food image data 6139 named "XXX.jpg".

The sensor ID 6132 of the second weight sensor 12 corresponds to type information 6133 indicating "apple", weight information 6134 indicating a weight of "0.913 kgf", remaining amount information 6135 indicating a remaining amount of "817.4 g", storage start date information 6136 indicating the storage start date of "2020/3/19", storage location information 6137 indicating the storage location of the "vegetable compartment", expiration date information 6138 indicating the expiration date of "2020/4/19", and food image data 6139 named "YYY.jpg".

The sensor ID 6132 of the third weight sensor 13 corresponds to type information 6133 indicating "rice", weight information 6134 indicating a weight of "1.567 kgf", remaining amount information 6135 indicating a remaining amount of "1.4 kg", storage start date information 6136 indicating the storage start date of "2020/3/14", storage location information 6137 indicating the storage location of "sensor 3", expiration date information 6138 indicating the expiration date of "2020/4/19", and food image data 6139 named "ZZZ.jpg".

Returning to the explanation of FIG. 4, the server communication unit 61 has communication hardware that complies with a specific communication standard, and communicates with devices connected to the global network GN according to the specific communication standard under the control of the server control unit 60. In this embodiment, the server communication unit 61 communicates with the terminal device 4.

Next, the functional configuration of the terminal device 4 will be described.
The terminal device 4 includes a terminal control unit 40 , a first terminal communication unit 41 , a second terminal communication unit 42 , and a touch panel 43 .

The terminal control unit 40 includes a terminal processor 400, which is a processor that executes programs such as a CPU or MPU, and a terminal storage unit 410, and controls each unit of the terminal device 4. The terminal control unit 40 executes various processes through cooperation of hardware and software, such that the terminal processor 400 reads out a control program 4110 stored in the terminal storage unit 410 and executes the process. A food management app 4130 is pre-installed in the terminal device 4. The food management app 4130 is a program that is read out from the terminal storage unit 410 by the terminal processor 400 and executed, causing the terminal control unit 40 to function as an app execution unit 4000. Details of the app execution unit 4000 will be described later.

The terminal storage unit 410 has a storage area for storing programs executed by the terminal processor 400 and data processed by the terminal processor 400. The terminal storage unit 410 stores a control program 4110 executed by the terminal processor 400, setting data 4120 related to the settings of the terminal device 4, a food management app 4130, and various other data. The terminal storage unit 410 has a non-volatile storage area for non-volatilely storing programs and data. The terminal storage unit 410 may also have a volatile storage area and constitute a work area for temporarily storing programs executed by the terminal processor 400 and data to be processed.

The first terminal communication unit 41 has communication hardware that complies with a specific communication standard, and communicates with devices connected to the global network GN according to the specific communication standard under the control of the terminal control unit 40. In this embodiment, the first terminal communication unit 41 communicates with the food management server 6 according to the specific communication standard under the control of the application execution unit 4000. In this embodiment, the communication standard used by the first terminal communication unit 41 is exemplified as a wireless communication standard, but may also be a wired communication standard.

The second terminal communication unit 42 is configured with communication hardware that complies with a specific communication standard, and communicates with the weight sensor 1 under the control of the application execution unit 4000 of the terminal control unit 40. In this embodiment, the Bluetooth standard is exemplified as the communication standard used by the second terminal communication unit 42, but the communication standard used by the second terminal communication unit 42 may be a short-range wireless communication standard other than the Bluetooth standard, a wireless communication standard other than the short-range wireless communication standard, or a wired communication standard.

The touch panel 43 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 40. The touch sensor detects touch operations and outputs the detected operations to the terminal control unit 40. The terminal control unit 40 executes processing corresponding to the touch operations based on the input from the touch sensor.

As described above, the terminal control unit 40 functions as the application execution unit 4000.

The application execution unit 4000 controls the second terminal communication unit 42 to pair with the weight sensor 1 and establish a communication connection between the terminal device 4 and the weight sensor 1. If the weight sensor 1 with which the application execution unit 4000 has previously been paired is capable of establishing a communication connection with the terminal device 4, the application execution unit 4000 controls the second terminal communication unit 42 to automatically establish a communication connection between the terminal device 4 and the weight sensor 1. The application execution unit 4000 transmits and receives various information to and from the weight sensor 1 with which the application execution unit 4000 has established a communication connection.

The app execution unit 4000 also controls the first terminal communication unit 41 to send and receive various information to and from the food management server 6. If a communication connection between the terminal device 4 and the communication device 5 is possible, the app execution unit 4000 sends and receives various information to and from the food management server 6 via the communication device 5, and if not, sends and receives various information to and from the food management server 6 without going through the communication device 5. Therefore, even if the user P is not located inside or near the house H, the terminal device 4 can send and receive various information to and from the food management server 6 through the functions of the food management app 4130.

The application execution unit 4000 also displays on the touch panel 43 a user interface related to the management of food F whose weight is detected by the weight sensor 1. In the following description, this user interface is referred to as a "food management UI" and is given the reference number "4300." By displaying the food management UI 4300 on the touch panel 43, the application execution unit 4000 provides the user P with various information related to the food F whose weight is detected by the weight sensor 1, and also accepts various inputs from the user P related to the food F whose weight is detected by the weight sensor 1.

For example, the application execution unit 4000 displays a food management UI 4300 on the touch panel 43 to provide the user P with information regarding the remaining amount of food F, the weight of which is detected by the weight sensor 1 .
FIG. 6 is a diagram showing an example of a food management UI 4300 relating to the remaining amount of food F.

The food management UI 4300 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 4300 shown in FIG. 6 includes an object OB1 related to the remaining amount of milk F1, an object OB2 related to the remaining amount of apples F2, and an object OB3 related to the remaining amount of rice F3.

The object OB relating to the remaining amount of food F includes a food image FOG, storage location information 6137, and a remaining amount image ZG which is an image showing the remaining amount of food F. The remaining amount image ZG is an image showing the remaining amount of food F in three stages.

The object OB1 relating to the remaining amount of milk F1 includes a food image FOG1 indicating the milk F1, storage location information 6137 indicating the "refrigerator", and a remaining amount image ZG1 indicating the remaining amount of milk F1.
The object OB2 relating to the remaining amount of apples F2 includes a food image FOG2 indicating the apples F2, storage location information 6137 indicating the "vegetable compartment", and a remaining amount image ZG2 indicating the remaining amount of apples F2.
The object OB3 relating to the remaining amount of rice F3 includes a food image FOG3 indicating rice F3, storage location information 6137 indicating "sensor 3", and a remaining amount image ZG3 indicating the remaining amount of rice F3.

When the app execution unit 4000 displays the food management UI 4300 shown in FIG. 6 on the touch panel 43, it receives the record R shown in FIG. 4 from the food management server 6 via the first terminal communication unit 41. The app execution unit 4000 then generates an object OB1 based on the remaining amount information 6135 corresponding to the sensor ID 6132 of the first weight sensor 11, the storage location information 6137, and the food image data 6139 in the received record R, and includes the generated object OB1 in the food management UI 4300 relating to the remaining amount of food F. The app execution unit 4000 also generates objects OB2 and OB3 in the same manner as object OB1, and includes them in the food management UI 4300 relating to the remaining amount of food F.

In this way, by providing information regarding the remaining amount of food F to the user P through the display of the food management UI 4300, the user P can easily recognize how much of the food F is remaining, the weight of which is detected by the weight sensor 1.

The information provided by the app execution unit 4000 to the user P is not limited to information related to the remaining amount of food F. The app execution unit 4000 may provide the user P with information related to the storage start date, the best-before date or expiration date, etc., for the food F whose weight is detected by the weight sensor 1, by displaying the food management UI 4300 on the touch panel 43. The app execution unit 4000 may also cooperate with other applications to provide the user P with cooking recipes that can be made using the food F whose weight is detected by the weight sensor 1.

In order to provide the above-mentioned services, the weight sensor 1 is registered by the user P in the food management application 4130 .
In registering the weight sensor 1, the user P launches the food management application 4130, displays the food management UI 4300 on the touch panel 43, and performs a touch operation on the food management UI 4300. In the food management UI 4300, the screen transitions in response to the user P's touch operation.

7 is a diagram showing an example of screen transitions of the food management UI 4300. When registering the weight sensor 1, the food management UI 4300 transitions in the order of a first screen GM1, a second screen GM2, a third screen GM3, and a fourth screen GM4.
It should be noted that the screen transitions shown in FIG. 7 are merely an example, and transitions to other screens may occur before or after each screen shown in FIG.

The first screen GM1 has a display area HA1. In the display area HA1, icons IC indicating weight sensors 1 that have previously established a communication connection with the terminal device 4 through the functions of the food management app 4130 are displayed in a list. In the display area HA1 of Figure 5, one icon IC is displayed. This indicates that there is already one weight sensor 1 that has previously established a communication connection with the terminal device 4.

The first screen GM1 has an add button B1. The add button B1 is a software button for registering a new weight sensor 1 that can be connected to the terminal device 4 for communication. When the add button B1 is touched by the user P, the food management UI 4300 transitions from the first screen GM1 to the second screen GM2.

The second screen GM2 includes instruction information J1 that instructs the user to turn on the power of the weight sensor 1 to be newly registered. The second screen GM2 also includes an image G1 of the weight sensor 1. The second screen GM2 also includes a back button B2 and a next button B3. The back button B2 is a software button for transitioning from the second screen GM2 to the first screen GM1. The next button B3 is a software button for starting the establishment of a communication connection with the weight sensor 1 to be newly registered. When the next button B3 is touched by the user P, the food management UI 4300 transitions from the second screen GM2 to the third screen GM3.

The third screen GM3 changes the display content depending on the progress of the establishment of the communication connection. When the Next button B3 on the second screen GM2 is touched, the food management UI 4300 transitions to the third screen GM3 in which an image G2 indicating that the communication connection is being established is superimposed on the image G1 of the weight sensor 1. Once the communication connection has been established, the third screen GM3 displays an image G3 indicating that the communication connection has been established, in place of image G2. After displaying image G3, the third screen GM3 displays an image G4 that asks the weight sensor 1 with which the communication connection has been established whether or not to register the type of food F whose weight is to be detected.

Image G4 has a no-registration button B4 and a registration button B5. The no-registration button B4 is a software button for not registering the type of food F. When the no-registration button B4 is touched by the user P, the food management UI 4300 transitions from the third screen GM to, for example, the home screen. The registration button B5 is a software button for registering the type of food F. When the registration button B5 is touched by the user P, the food management UI 4300 transitions from the third screen GM3 to the fourth screen GM4.

The fourth screen GM4 has a first input area NA1 and a second input area NA2.
The first input area NA1 has a food image input area NA11 and a food type input area NA12. The food image display area NA11 is an area for inputting a food image FOG. The food type input area NA12 is an area for inputting the type of food F.

The first input area NA1 has a first selection button B6 and a second selection button B7.

The first selection button B6 is a software button that allows the user P to select one combination from a list of combinations of food images FOG input in the food image input area NA11 and types of food F input in the food type input area NA12. When the first selection button B6 is touched, the food management UI 4300 transitions from the fourth screen GM4 to a screen that displays a list of combinations of food images FOG and types of food F. When one combination is selected from this screen, the food management UI 4300 transitions to the fourth screen GM4 where the food images FOG included in the selected combination are displayed in the food image input area NA11 and the type of food F included in the selected combination is input in the food type input area NA12.

The second selection button B7 is a software button for selecting a food image FOG to be input into the food image input area NA1 from among the captured images stored in the terminal device 4. When the second selection button B7 is touched, the food management UI 4300 transitions from the fourth screen GM4 to a screen displaying a list of captured images stored in the terminal device 4. When one captured image is selected from this screen, the food management UI 4300 transitions to the fourth screen GM4 in which the selected captured image is input into the food image input area NA11. Note that when the second selection button B7 is touched, the type of food F is not input into the food type input area NA12, so the user P operates a software key or the like to input the type of food F into the food type input area NA12.

The second input area NA2 includes a storage start date input area NA21 in which the storage start date is input. The storage start date input in the storage start date input area NA21 can be changed by a touch operation by the user P. The date on which the fourth screen GM4 is displayed is input as the storage start date in the default storage start date input area NA21.

The second input field NA2 also includes a deadline input field NA22 in which a deadline is input. The deadline input in the deadline input field NA22 can be set by a touch operation by the user P. In the default deadline input field NA22, no deadline information 6138 is input, and a character string indicating that a deadline has not been set is input.

The second input area NA2 also includes a storage location input area NA23 in which the storage location is input. The storage location input in the storage location input area NA23 can be changed by a touch operation by the user P. A character string indicating the weight sensor 1 to which a new communication connection has been established is input as the storage location in the default storage location input area NA23.

The fourth screen GM4 includes a Confirm button B8 for confirming the contents entered in the first input area NA1 and the second input area NA2.

Next, the operation of the food management system 1000 of this embodiment will be described.
8 is a flowchart showing the operation of food management system 1000. The flowchart shown in FIG.
8, a flowchart FA shows the operation of the weight sensor 1 that has not yet established a communication connection with the terminal device 4. A flowchart FB shows the operation of the terminal device 4. A flowchart FC shows the operation of the food management server 6.

Note that it is assumed that the food management application 4130 is running at the start of the flowchart in Figure 8.

As shown in the flowchart FB, the application execution unit 4000 determines whether or not to register a new weight sensor 1 that can be connected to the terminal device 4 for communication (step SB1). If the add button B1 is touched on the first screen GM1, the application execution unit 4000 makes a positive determination in step SB1, and if the add button B1 is not touched on the first screen GM1, the application execution unit 4000 makes a negative determination in step SB1.

When the application execution unit 4000 determines that a new weight sensor 1 is to be registered (step SB1: YES), it determines whether or not to establish a communication connection with the weight sensor 1 to be registered (step SB2). When the Next button B3 is touched on the second screen GM2, the application execution unit 4000 makes a positive determination in step SB2, and when the Next button B3 is not touched on the second screen GM2, it makes a negative determination in step SB2.

If the application execution unit 4000 determines that a communication connection will not be established with the weight sensor 1 to be registered (step SB2: NO), the process returns to step SB1. On the other hand, if the application execution unit 4000 determines that a communication connection will be established with the weight sensor 1 to be registered (step SB2: YES), the application execution unit 4000 starts establishing a communication connection with the weight sensor 1 (step SB3).

As shown in the flowchart FA, when the user P turns on the power of the weight sensor 1 (step SX1), the sensor control unit 100 starts to establish a communication connection with the terminal device 4 (step SA1).

When the sensor control unit 100 starts establishing a communication connection with the terminal device 4, it turns on the LED light 1031 (step SA2). In step SA2, the sensor control unit 100 turns on the LED light 1031 in a lighting state indicating that the communication connection is being established, and notifies the user P that the communication connection is being established.

Next, the sensor control unit 100 determines whether or not the establishment of a communication connection with the terminal device 4 has been completed (step SA3).

If the sensor control unit 100 determines that the communication connection with the terminal device 4 has been established (step SA3: YES), it turns off the LED light 1031 (step SA4).

Referring to the flowchart FB, the application execution unit 4000 determines whether or not the establishment of a communication connection with the weight sensor 1 has been completed (step SB4).

If the application execution unit 4000 determines that the communication connection with the weight sensor 1 has been established (step SB4: YES), the second terminal communication unit 42 sends ID request information requesting the sensor ID 6132 to the weight sensor 1 with which the communication connection has been established (step SB5).

Referring to the flowchart FA, the sensor control unit 100 determines whether or not ID request information has been received from the terminal device 4 via the sensor communication unit 101 (step SA5).

If the sensor control unit 100 determines that it has received ID request information from the terminal device 4 (step SA5: YES), it reads the sensor ID 6132 from the sensor storage unit 120 and transmits the read sensor ID 6132 to the terminal device 4 via the sensor communication unit 101 (step SA6).

Referring to flowchart FB, the application execution unit 4000 receives the sensor ID 6132 from the weight sensor 1 via the second terminal communication unit 42 (step SB6).

Next, the application execution unit 4000 determines whether or not to register the type of food F for the weight sensor 1 with which the communication connection has been established (step SB7). If the registration execution button B5 is touched on the third screen GM3, the application execution unit 4000 makes a positive determination in step SB7. On the other hand, if the registration non-execution button B4 is touched on the third screen GM3, the application execution unit 4000 makes a negative determination in step SB7.

If the app execution unit 4000 determines that the type of food F is not to be registered (step SB7: NO), it terminates this process.

On the other hand, if the app execution unit 4000 determines that the type of food F is to be registered (step SB7: YES), it displays the food management UI 4300 of the fourth screen GM4 on the touch panel 43 (step SB8).

Next, the application execution unit 4000 determines whether the input has been confirmed on the fourth screen GM4 (step SB9). If the Confirm button B8 on the fourth screen GM4 has been touched, the application execution unit 4000 makes a positive determination in step SB9.

If the application execution unit 4000 determines that the input has been confirmed on the fourth screen GM4 (step SB9: YES), it generates storage request information requesting storage of information in the food management database 6130 (step SB10).

When generating the storage request information, the application execution unit 4000 associates the sensor ID 6132 received in step SB7 with the user ID 6131. When generating the storage request information, the application execution unit 4000 also associates type information 6133 indicating the type of food F entered on the fourth screen GM, expiration date information 6138 indicating the expiration date entered on the fourth screen GM, storage location information 6137 indicating the storage location entered on the fourth screen GM, and food image data 6139 of the food image FOG entered on the fourth screen GM with the sensor ID 6132. The application execution unit 4000 then generates storage request information that includes this associated information and requests storage of this information in the food management database 6130.

When the app execution unit 4000 generates the storage request information, it transmits the generated storage request information to the food management server 6 via the first terminal communication unit 41 (step SB11).

Referring to the flowchart FC, the server control unit 60 determines whether storage request information has been received by the server communication unit 61 (step SC1).

If the server control unit 60 determines that storage request information has been received by the server communication unit 61 (step SC1: YES), it stores the various information contained in the received storage request information in the food management database 6130 (step SC2).

In step SC2, the server control unit 60 identifies, from the records R stored in the food management database 6130, a record R having a user ID 6131 that matches the user ID 6131 included in the received storage request information. If the server control unit 60 is able to identify the record R, it stores the various information included in the received storage request information in the identified record R. On the other hand, if the server control unit 60 is unable to identify the record R, it creates a new record R including the various information included in the received storage request information, and stores the created record R in the food management database 6130.

Here, a case where the third weight sensor 13 is newly registered will be taken as an example.
In this example, on the fourth screen GM, the type of food F indicating "rice", the storage start date indicating "2020/3/14", the storage location indicating "sensor 3", the expiration date indicating "2020/4/13", and the food image FOG "ZZZ.jpg" are input on the fourth screen GM4.

In this example, the server control unit 60 receives from the terminal device 4 storage request information including a user ID 6131, a sensor ID 6132 of the third weight sensor 13, type information 6133 indicating "rice", storage start date information 6136 indicating the storage start date of "2020/3/14", storage location information 6137 indicating the storage location of "sensor 3", expiration date information 6138 indicating the expiration date of "2020/4/13", and food image data 6139 of "ZZZ.jpg". Then, the server control unit 60 stores the sensor ID 6132 included in the storage request information, type information 6133 indicating "rice", storage start date information 6136 indicating the storage start date of "2020/3/14", storage location information 6137 indicating the storage location of "sensor 3", expiration date information 6138 indicating the expiration date of "2020/4/13", and food image data 6139 of "ZZZ.jpg", for record R having the user ID 6131 included in the received storage request information.

The storage request information may include weight information 6134 and remaining amount information 6135 in association with other information. In this case, the app executor 4000 establishes a communication connection with the weight sensor 1 and then receives weight information 6134 from the weight sensor 1. The app executor 4000 then determines the remaining amount of food F corresponding to the weight indicated by the received weight information 6134, and includes remaining amount information 6135 indicating the determined remaining amount and the received weight information 6134 in the storage request information.

In addition, in the operation of FIG. 8, the terminal device 4 is configured to obtain the sensor ID 6132 from the weight sensor 1 by transmitting ID request information, but the weight sensor 1 may transmit the sensor ID 6132 to the terminal device 4 even if it does not receive ID request information after establishing a communication connection. In this configuration, the processing of steps SA5 and SB5 is omitted in the operation of FIG. 8.

Next, the operation of the food management system 1000 after registration of the weight sensor 1 will be described.
FIG. 9 is a flowchart showing the operation of the food control system 1000.

In FIG. 9, the flowchart FD shows the operation of the weight sensor 1 registered by the food management application 4130. The flowchart FE shows the operation of the terminal device 4. The flowchart FC shows the operation of the food management server 6.

At the start of the flowchart in Figure 9, it is assumed that the weight sensor 1 registered by the food management application 4130 has established a communication connection with the terminal device 4.

Referring to the flowchart FE, the application execution unit 4000 of the terminal device 4 transmits, via the second terminal communication unit 42, first weight request information requesting the weight of the food F to the weight sensor 1 with which a communication connection has been established (step SE1). The processing of step SE1 may be executed at a fixed cycle, or may be executed when a predetermined screen (e.g., the food management UI 4300) is displayed.

Referring to the flow chart FD, when the sensor control unit 100 of the weight sensor 1 receives the first weight request information via the sensor communication unit 101 (step SD1), the sensor control unit 100 detects the weight of the food F via the detection unit 102 (step SD2).

Next, the sensor control unit 100 associates the weight with the sensor ID 6132 stored in the sensor memory unit 120 and transmits weight information 6134 indicating the detected weight to the terminal device 4 via the sensor communication unit 101 (step SD3).

Referring to flowchart FE, the application execution unit 4000 receives weight information 6134 and sensor ID 6132 from the weight sensor 1 via the second terminal communication unit 42 (step SE2).

Next, the application execution unit 4000 transmits second weight request information requesting weight information 6134 corresponding to the received sensor ID 6132 to the food management server 6 via the first terminal communication unit 41 (step SE3). The second weight request information includes the sensor ID 6132 received in step SE2.

Referring to flowchart FF, the server control unit 60 of the food management server 6 receives the second weight request information via the server communication unit 61 (step SF1).

The server control unit 60 obtains weight information 6134 corresponding to the sensor ID 6132 contained in the received second weight request information from the food management database 6130 (step SF2).

Next, the server control unit 60 associates the sensor ID 6132 included in the received second weight request information and transmits the weight information 6134 obtained from the food management database 6130 to the terminal device 4 via the server communication unit 61 (step SF3).

Referring to flowchart FE, the app execution unit 4000 receives the weight information 6134 and the sensor ID 6132 from the food management server 6 via the first terminal communication unit 41 (step SE4).

The application execution unit 4000 calculates a subtraction value by subtracting the weight indicated by the weight information 6134 received from the food management server 6 from the weight indicated by the weight information 6134 received from the weight sensor 1 (step SE5).

Next, the application execution unit 4000 determines whether the weight detected by the weight sensor 1 has increased based on the calculated subtraction value (step SE6). If the calculated subtraction value is greater than 0, the application execution unit 4000 makes a positive determination in step SE6, and if the calculated subtraction value is equal to or less than 0, the application execution unit 4000 makes a negative determination in step SE6.

If the application execution unit 4000 determines that the weight detected by the weight sensor 1 has not increased (step SE6: NO), it sends update request information requesting an update of the food management database 6130 to the food management server 6 via the first terminal communication unit 41 (step SE7).

The update request information sent in step SE7 includes the user ID 6131, weight information 6134 received from weight sensor 1, remaining amount information 6135 indicating the remaining amount of food F corresponding to the weight indicated by the weight information 6134 received from weight sensor 1, and the sensor ID 6132 received in step SE2. The remaining amount of food F is calculated by the app execution unit 4000 based on the weight indicated by the weight information 6134 received from weight sensor 1.

As described below, the food management database 6130 is updated by sending the update request information. Therefore, by sending the update request information, the application execution unit 4000 can associate the remaining amount information 6135 with the sensor ID 6132 and type information 6133 in the food management database 6130.

On the other hand, if the application execution unit 4000 determines that the weight detected by the weight sensor 1 has increased (step SE6: YES), it determines whether the subtraction value corresponding to the increase is greater than a predetermined threshold (step SE8). This predetermined threshold may be a uniform value that is independent of the type of food F, or may be a value that differs depending on the type of food F.

If the application execution unit 4000 determines that the calculated subtraction value does not exceed the predetermined threshold value (step SE8: NO), it executes the processing of step SE7.

On the other hand, if the application execution unit 4000 determines that the calculated subtraction value exceeds the predetermined threshold value (step SE8: YES), it sends update request information including the storage start date information 6136 to the food management server 6 via the first terminal communication unit 41 (step SE9).

In step SE9, the application execution unit 4000 transmits update request information including storage start date information 6136, in which the storage start date is the date on which it was determined that the calculated subtraction value exceeded the predetermined threshold value, the user ID 6131, weight information 6134 received from the weight sensor 1, remaining amount information 6135 indicating the remaining amount of food F corresponding to the weight detected by the weight sensor 1, and the sensor ID 6132 received in step SE2.

As described below, the food management database 6130 is updated by sending the update request information. Therefore, by sending the update request information, the application execution unit 4000 can associate the storage start date information 6136 with the sensor ID 6132 and type information 6133 in the food management database 6130.

Referring to flowchart FF, when the server control unit 60 receives the update request information (step SF1), it updates the food management database 6130 based on the received update request information (step SF2).

In step SF2, the server control unit 60 identifies, from the records R stored in the food management database 6130, a record R including a user ID 6131 that matches the user ID 6131 included in the received update request information.
The server control unit 60 updates the weight information 6134 of the identified record R to the weight information 6134 included in the update request information.
Furthermore, the server control unit 60 updates the remaining amount information 6135 of the identified record R to the remaining amount information 6135 included in the update request information.
Furthermore, if the update request information includes the storage start date information 6136, the server control unit 60 updates the storage start date information 6136 of the specified record R to the storage start date information 6136 included in the update request information.

In the operation of FIG. 9, the terminal device 4 is configured to obtain the weight information 6134 and the sensor ID 6132 from the weight sensor 1 by transmitting the first weight request information, but the weight sensor 1 may transmit the weight information 6134 and the sensor ID 6132 to the terminal device 4 after establishing a communication connection, even if it does not receive the first weight request information. In this configuration, the processing of steps SD1 and SE1 is omitted in the operation of FIG. 9.

In addition, in the operation of FIG. 9, the app execution unit 4000 requests weight information 6134 corresponding to a specific sensor ID 6132 from the food management server 6, but information corresponding to the user ID 6131 may have been received in advance from the food management server 6, for example, when the food management app 4130 is launched. In this configuration, the processing of steps SE3, SE4, SF1, SF2, and SF3 is omitted in the operation of FIG. 9.

In the above explanation, the storage start date of food F is set automatically, but in the food management system 1000, user P can set the storage start date of food F to any date.
Next, the operation of food management system 1000 when user P sets a storage start date will be described.
FIG. 10 is a flowchart showing the operation of the food control system 1000.

In FIG. 10, flowchart FG shows the operation of the terminal device 4. Also, flowchart FH shows the operation of the food management server 6.

The application execution unit 4000 of the terminal device 4 determines whether or not input of the storage start date by a touch operation by the user P has been accepted (step SG1). If the storage start date is entered on the screen for setting the storage start date of the food management UI and the input is then confirmed, the application execution unit 4000 makes a positive determination in step SG1.

If the app execution unit 4000 determines that input of the storage start date has been accepted (step SG1: YES), it sends update request information including storage start date information 6136 indicating the accepted storage start date to the food management server 6 via the first terminal communication unit 41 (step SG2).

As described above, the food management database 6130 is updated, and the application execution unit 4000 can associate the storage start date information 6136 with the sensor ID 6132 and type information 6133 in the food management database 6130 by sending update request information.

The update request information sent to the food management server 6 in step SG2 includes storage start date information 6136 indicating the accepted storage start date, as well as a user ID 6131 and a sensor ID 6132.

Referring to flowchart FH, when the server control unit 60 receives the update request information (step SH1), it updates the food management database 6130 based on the received update request information (step SH2).

In step SH2, the server control unit 60 identifies a record R that contains a user ID 6131 that matches the user ID 6131 included in the received storage request information from the records R stored in the food management database 6130. The server control unit 60 updates the storage start date information 6135 of the identified record R to the storage start date information 6135 included in the update request information.

As described above, the food management system 1000 includes a weight sensor 1 and a terminal device 4, and manages food F whose weight is detected by the weight sensor 1. In the food management system 1000, the terminal device 4 acquires a sensor ID 6132 that identifies the weight sensor 1, accepts a setting by the user P of the type of food F whose weight is to be detected by the weight sensor 1, and associates the acquired sensor ID 6132 with type information 6133 that indicates the accepted type of food F.

With this configuration, the type of food F whose weight is detected by the weight sensor 1 can be set to the type desired by the user P, so that when managing food F using the weight sensor 1, the type of food F desired by the user P can be managed.

The terminal device 4 acquires the weight of the food F detected by the weight sensor 1, and associates the remaining amount information 6135 indicating the remaining amount of food F corresponding to the acquired weight of the food F with the sensor ID 6132 and type information 6133.

With this configuration, the weight sensor 1, the type of food F whose weight is detected by the weight sensor 1, and the remaining amount of food F whose weight is detected by the weight sensor 1 can be associated with each other, so that when managing food F using the weight sensor 1, the remaining amount of the type of food F desired by the user P can be managed.

The terminal device 4 is capable of communicating with the weight sensor 1, and acquires the sensor ID 6132 from the weight sensor 1 when establishing a communication connection with the weight sensor 1 for the first time.

With this configuration, the sensor ID 6132 obtained when a communication connection with the weight sensor 1 is established for the first time can be associated with the type information 6133, and management of the type of food F desired by the user P can begin after the communication connection with the weight sensor 1 is established for the first time.

When the weight sensor 1 establishes a communication connection with the terminal device 4 for the first time, it notifies the user that a communication connection is being established.

With this configuration, user P can easily determine whether a communication connection with the terminal device 4 is being established, so even if there are multiple weight sensors 1, user P can easily determine which weight sensor 1 the terminal device 4 has established a communication connection with.

The terminal device 4 associates the storage start date information 6136, which indicates the storage start date when storage of the food F, whose weight is detected by the weight sensor 1, with the sensor ID 6132 and type information 6133.

With this configuration, the weight sensor 1, the type of food F whose weight is detected by the weight sensor 1, and the storage start date of the food F whose weight is detected by the weight sensor 1 can be associated with each other, so that when managing food F using the weight sensor 1, the storage start date of the type of food F desired by the user P can be managed.

The terminal device 4 associates the storage start date information 6136 with the sensor ID 6132 and the type information 6133, setting the date on which the sensor ID 6132 and the type information 6133 are associated as the storage start date.

The date on which the sensor ID 6132 and type information 6133 are associated may be the date on which storage of the food F began. Therefore, the food management system 1000 can manage the appropriate storage start date for the type of food F desired by user P.

The terminal device 4 associates the storage start date information 6136 with the sensor ID 6132 and type information 6133, taking the date on which the increase in weight detected by the weight sensor 1 exceeded a predetermined threshold as the start date.

The day on which the weight detected by the weight sensor 1 changes significantly may be the day on which storage of a new food F begins. Therefore, the food management system 1000 can manage the appropriate storage start date for the type of food F desired by the user P.

The terminal device 4 accepts the input of the storage start date by the user P, and associates the storage start date information 6136 indicating the accepted storage start date with the sensor ID 6132 and type information 6133.

In place of a certain food F, another food F different from the certain food F may be placed on the weight sensor 1. In this case, the storage start date of the other food F is not necessarily the date it was placed on the weight sensor 1. For example, the other food F may have already been used in cooking, etc., and may already be stored in, for example, the refrigerator 2 or shelf 7. The food management system 1000 allows the user P to set the storage start date for managing the type of food F desired by the user to any date. Therefore, the food management system 1000 can manage an appropriate storage start date for the type of food F desired by the user P.

Weight sensor 1 is installed in refrigerator 2 and detects the weight of food F stored in refrigerator 2.

With this configuration, when managing food F using the weight sensor 1, it is possible to manage food F that is stored in the refrigerator 2 by the user P and is the type of food F that the user P desires.

The above-described embodiment merely shows one aspect of the present invention, and any modification and application is possible within the scope of the present invention.

For example, in the embodiment described above, record R is stored in the food management database 6130 and the correspondence related to the weight sensor 1 is managed by the food management server 6, but record R may be stored in the device storage unit 410 and various information related to food F whose weight is detected by the weight sensor 1 may be managed by the food management app 4130. In this configuration, the app execution unit 4000 appropriately updates the contents of record R stored in the device storage unit 410 in the same way as the food management server 6 described above. In this configuration, the food management system 1000 does not need to include a food management server 6, and the system configuration is simplified.

For example, in the embodiment described above, the weight information 6134 indicating the weight detected by the weight sensor 1 is transmitted to the food management server 6 via the terminal device 4, but the weight sensor 1 may be configured to transmit the weight information 6134 directly to the food management server 6 without passing through the terminal device 4. In this configuration, the weight sensor 1 is configured to be connectable to the global network GN or to be able to communicate with a refrigerator 2 connected to the global network GN. In this configuration, the food management system 1000 can update the food management database 6130 even if the terminal device 4 is not located near the weight sensor 1.

In addition, for example, in the above-described embodiment, the weight sensor 1 notifies the terminal device 4 that a communication connection is being established by turning on the LED light 1031, but the notification method is not limited to turning on the LED light 1031, and may be other methods such as audio output.

In addition, for example, when the expiration date information 6138 included in the received storage request information includes information indicating that an expiration date has not been set, the server control unit 60 may calculate the expiration date based on the storage start date information 6136 included in the received storage request information, and store the expiration date information 6138 indicating the calculated expiration date in the food management database 6130.

For example, the types of compartments formed in the main box 20 of the refrigerator are not limited to the refrigerator compartment 21, ice-making compartment 22, fresh-freezing compartment 23, freezer compartment 24, and vegetable compartment 25, and there may be fewer compartments, or other types of compartments may be formed. Also, the number of doors provided at the opening on the front of the refrigerator compartment 21 may be one.

Also, for example, the above-mentioned food management system 1000 has been illustrated 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. Also, the food management system 1000 may manage only food F outside the refrigerator 2.

Furthermore, the functions of the sensor control unit 100, the terminal control unit 40, and the server control unit 60 may be realized by multiple processors or semiconductor chips.

The components shown in Figures 3 and 4 are merely examples, and the specific implementation form is not particularly limited. In other words, it is not necessary to implement hardware that corresponds to each component individually, and it is of course possible to implement a configuration in which one processor executes a program to realize the functions of each component. 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 4, and the other components of the food management server 6 may be changed as desired without departing from the spirit of the present invention.

In addition, for example, the step units of the operations shown in Figures 8, 9, and 10 are divided according to the main processing content in order to make it easier to understand the operation of each part of the food management system 1000, and the present invention is not limited by the manner in which the processing units are divided or the names of the processing units. Depending on the processing content, the processing units may be divided into more step units. Also, one step unit may be divided so as to include more processing. Also, the order of the steps may be changed as appropriate within the scope of the present invention.

As described above, the food management system of the present invention can be used to manage food whose weight is detected by a weight sensor.

REFERENCE SIGNS LIST 1 Weight sensor 2 Refrigerator 4 Terminal device 11 First weight sensor 12 Second weight sensor 13 Third weight sensor 1000 Food management system 6132 Sensor ID (sensor identification information)
6133 Type information 6136 Storage start date information F Food P User

Claims (9)

A food management system including a weight sensor and a terminal device, the weight sensor detecting the weight of food,
The weight sensor is provided inside or outside the refrigerator,
The terminal device
acquiring sensor identification information for identifying the weight sensor;
accepting a selection of a combination from a list of combinations of the food image and the food type as an input of the food image and the food type by a user;
accepting a selection of a photographed image from photographed images stored in the terminal device as an input of a food image, and when the input of the food image is accepted through the selection of the photographed image, accepting an input of a type of the food by a user;
When the combination is selected, the acquired sensor identification information is associated with type information indicating the type of the food included in the received combination, and food image data indicating the food image included in the received combination;
When the photographed image is selected, the acquired sensor identification information, type information indicating the received type of the food, and food image data indicating the food image that is the selected photographed image are associated with each other .
A food control system comprising: The terminal device
acquiring a weight of the food detected by the weight sensor, and associating remaining amount information indicating a remaining amount of the food corresponding to the acquired weight of the food with the sensor identification information and the type information.
The food control system according to claim 1 . The terminal device
A device capable of communicating with the weight sensor;
acquiring the sensor identification information from the weight sensor when establishing a communication connection with the weight sensor for the first time;
3. The food control system according to claim 1 or 2. When establishing a communication connection with the terminal device for the first time, the weight sensor notifies the user that the communication connection is being established.
The food control system according to claim 3 . The terminal device
and associating storage start date information, which indicates a storage start date on which storage of the food was started when the weight sensor detects the weight, with the sensor identification information and the type information.
A food control system according to any one of claims 1 to 4. The terminal device
a date on which the sensor identification information and the type information are associated with each other is set as a storage start date, and the storage start date information is associated with the sensor identification information and the type information.
The food control system according to claim 5 . The terminal device
a date on which the weight increase amount detected by the weight sensor exceeded a predetermined threshold value, the date being set as the storage start date, and the storage start date information is associated with the sensor identification information and the type information.
The food control system according to claim 5 or 6. The terminal device
accepting an input of the storage start date by a user, and associating the storage start date information indicating the accepted storage start date with the sensor identification information and the type information;
A food control system according to any one of claims 5 to 7. The weight sensor is provided in a refrigerator and detects the weight of the food stored in the refrigerator.
A food control system according to any one of claims 1 to 8.

Images