JP7487546B2 - Terminal device and program - Google Patents

Description

The present invention relates to a technology that enables a user who has acquired a product to manage expiration information for the product that he or she owns.

In recent years, computer networks have been used to collect various information from consumers and provide services in an optimal manner to each individual consumer. Meanwhile, advances in sensor technology have recently led to the development of technology that detects the remaining amount of contents depending on usage. Furthermore, technology has been proposed that detects the remaining amount of consumables and provides support for purchasing consumables (see Patent Document 1).

JP 2013-200755 A

The technology described in Patent Document 1 is suitable for businesses that handle consumables, and is easy to use for businesses that handle a lot of information, but has the problem that it is difficult to use for general consumers who do not want to take the time to manage information and perform other tasks. It is particularly unsuitable for handling products that have a short shelf life, such as food products.

The present invention aims to provide a terminal device and program that can provide users with information about product expiration dates while minimizing the burden of information management and work on the user's side.

In order to solve the above problems, the present invention provides
A terminal device capable of data communication with a server device that manages tag information in which, for each tag ID that identifies an RFID tag attached to a product, a product ID that identifies the product to which the RFID tag in which the tag ID is recorded is attached, a device ID that identifies a detection device equipped with an RFID reader, and expiration date information of the product identified by the tag ID are associated,
The terminal device
a registration request means for requesting the server device to perform registration in which a device ID for identifying a detection device having an RFID reader for reading the tag ID from the RFID tag and a user ID for identifying a user are associated with each other;
a product information acquiring means for acquiring, from the server device, information on a product identified by a product ID corresponding to the tag ID, for which expiration date information of the product corresponding to the tag ID satisfies a predetermined condition;
and a display means for displaying the acquired product information.

The present invention also provides a method for producing a method for manufacturing a semiconductor device comprising the steps of:
A terminal device capable of data communication with a detection device having an RFID reader that reads a tag ID that identifies an RFID tag attached to a product from the RFID tag, and capable of data communication with a server device that manages tag information that associates, for each tag ID, a product ID that identifies a product to which the RFID tag is attached in which the tag ID is recorded, a device ID that identifies the detection device, and expiration date information of the product identified by the tag ID,
the terminal device includes a term information acquisition means for acquiring, from the server device, term information of a product corresponding to the tag ID received from the detection device;
a term information storage means for storing the acquired term information in association with the tag ID and the product ID;
A terminal device is provided which has: a display means for displaying information on a product identified by a product ID corresponding to a tag ID for which the expiration information stored in the expiration information storage means satisfies a predetermined condition.

In addition, the terminal device of the present invention is
A recipe storage means for storing recipe information that records dish items, product types, and amounts used;
The apparatus may further include a recipe suggestion means for referring to the tag information, and obtaining and suggesting recipe information corresponding to a product ID of a product corresponding to a tag ID whose expiration date information has not reached a predetermined expiration date from the recipe storage means.

The present invention also provides a method for producing a method for manufacturing a semiconductor device comprising the steps of:
a computer capable of data communication with a detection device having an RFID reader that reads a tag ID that identifies an RFID tag attached to a product from the RFID tag, and capable of data communication with a server device that manages tag information that associates, for each tag ID, a product ID that identifies a product to which the RFID tag is attached in which the tag ID is recorded, a device ID that identifies the detection device, and expiration date information of the product identified by the tag ID;
a registration request means for requesting the server device to perform registration in which a device ID for identifying a detection device having an RFID reader for reading a tag ID for identifying the RFID tag from the RFID tag is associated with a user ID for identifying a user;
a product information acquiring means for acquiring, from the server device, information on a product identified by a product ID corresponding to the tag ID, for the tag ID whose expiration date information satisfies a predetermined condition;
A display means for displaying the acquired product information and a program for causing the display means to function as the display means are provided.

The present invention also provides a method for producing a method for manufacturing a semiconductor device comprising the steps of:
a computer capable of data communication with a detection device having an RFID reader that reads a tag ID that identifies an RFID tag attached to a product from the RFID tag, and capable of data communication with a server device that manages tag information that associates, for each tag ID, a product ID that identifies a product to which the RFID tag is attached in which the tag ID is recorded, a device ID that identifies the detection device, and expiration date information of the product identified by the tag ID;
a time limit information acquiring means for acquiring from the server device time limit information of a product corresponding to the tag ID received from the detection device;
a term information storage means for storing the acquired term information in association with the tag ID and the product ID;
A program is provided for causing the tag ID, whose expiration information stored in the expiration information storage means satisfies a predetermined condition, to function as a display means for displaying information about a product identified by a product ID corresponding to the tag ID.

According to the present invention, it is possible to provide users with information regarding product expiration dates while reducing the burden of information management and work on the user side.

1 is a diagram showing a usage information management system using a user terminal which is a terminal device according to a first embodiment of the present invention; FIG. 1 is a hardware configuration diagram of a smartphone which is a user terminal 20 which is a terminal device according to a first embodiment of the present invention. FIG. 2 is a hardware configuration diagram of the server device 30. 4 is a diagram showing an example of product information stored in a server device 30. FIG. 4 is a flowchart showing a processing operation of the usage information management system according to the first embodiment. 4 is a diagram showing an example of user information stored in the server device 30. FIG. 10 is a diagram showing an example of tag information stored in the server device 30. FIG. 4 is a diagram showing an example of usage information stored in the server device 30. FIG. FIG. 11 is a diagram showing an example of analysis information obtained using acquired usage information. FIG. 11 is a diagram showing a usage information management system using a user terminal which is a terminal device according to a second embodiment of the present invention. 10 is a flowchart showing a processing operation of a usage information management system according to a second embodiment.

1. System Overview
A preferred embodiment of the present invention will be described in detail below with reference to the drawings. Fig. 1 is a diagram showing a usage information management system using a user terminal, which is a terminal device according to a first embodiment of the present invention. In Fig. 1, 10 is a detection device, 20 is a user terminal, 30 is a server device, 40 is a relay device, and 50 is a network. The user terminal 20, the server device 30, and the relay device 40 are connected to a public network 50 such as the Internet, and are capable of data communication with each other. The user terminal 20 shown in Fig. 1 is a terminal device that presents information regarding the expiration date of a product, and the usage information management system is a system for managing usage information when a user (user) uses a product.

The detection device 10 is a device that detects when the product M is in a used state, and includes an RFID reader 11, a processing module 12, and a communication module 13. The RFID reader 11 is a recorded information acquisition means that reads the recorded information of the RFID tag T attached to the packaging material P that wraps the product M by wireless communication. The detection device 10 usually includes one RFID reader 11. The processing module 12 is electrically connected to the RFID reader 11 and the communication module 13, and is a calculation processing means that performs a predetermined calculation process and controls the RFID reader 11 and the communication module 13. The processing module 12 also acquires the tag ID, which is the recorded information of the RFID tag T read by the RFID reader 11, and performs a process to determine whether the product to which the tag ID is attached is in a used state. If it is determined that the product is in a used state, it is detected that the product is in a used state. The communication module 13 is a transmission means that transmits the tag ID, which is detected as being in a used state, to the server device 30 via the relay device 40 when the processing module 12 detects the used state.

The processing module 12 periodically instructs the RFID reader 11 to read the recorded information of the RFID tag T, and obtains the tag ID, which is the recorded information read by the RFID reader 11. The time interval at which the reading is performed can be set arbitrarily, and can be, for example, 5 seconds. Furthermore, if the processing module 12 cannot obtain the same tag ID from the RFID reader 11 for a predetermined time, it determines that the product corresponding to that tag ID is in a used state. Specifically, a first elapsed time D1 is set as the predetermined time, and if the tag ID cannot be read for the first elapsed time D1 or more, it determines that the corresponding product is in a used state. The first elapsed time D1 for determining that the product is in a used state can also be set arbitrarily, and can be, for example, 60 seconds. If it is determined that the product is in a used state, the processing module 12 instructs the communication module 13 to transmit the tag ID, and the communication module 13 transmits the tag ID to the server device 30 via the relay device 40.

The RFID reader 11 can simultaneously read recorded information from multiple RFID tags T located within a readable distance. Therefore, the processing module 12 determines that only the tag ID of an RFID tag T that cannot be read for 60 seconds is in use. The processing module 12 also has a memory element, and stores a device ID, which is identification information that specifies the detection device 10, in this memory element.

The communication module 13 transmits the tag ID, which is the recorded information of the RFID tag read by the RFID reader 11, to the relay device 40. At this time, the device ID that identifies the detection device 10 is also transmitted along with the tag ID. If the RFID reader 11 is unable to read a certain tag ID for a specified period of time, it determines that the product M identified by that tag ID is in use. If it is determined that the product is in use, it transmits information to the communication module 13 that the product corresponding to that tag ID is in use along with the device ID that identifies the RFID reader 11 itself, and the communication module 13 transmits a signal to the outside using a specified communication method.

The user terminal 20 is a terminal device that communicates with the server device 30 via the network 50 to transmit information about the user (user) to the server device 30 and to perform various processes in cooperation with the server device 30. In particular, in this embodiment, the terminal device functions as a registration request means 21 that requests the server device 30 to register an association between an apparatus ID that identifies a detection device 10 equipped with an RFID reader 11 that reads a tag ID that identifies an RFID tag from an RFID tag and a user ID that identifies a user, a product information acquisition means 22 that acquires information about a product identified by a product ID corresponding to a tag ID from the server device 30 for a tag ID whose expiration information of the product corresponding to the tag ID satisfies a predetermined condition, and a display means 23 that displays the acquired product information. As the user terminal 20, various information processing devices capable of inputting and outputting information and performing calculations can be used, but in this embodiment, the user terminal 20 is realized by incorporating a dedicated program called an "app" into a smartphone, which is a multi-function mobile phone. Although the smartphone is a multi-function mobile phone, it also has a function as a computer that can be controlled by operating the screen with a touch panel. The user terminal 20 is not limited to a smartphone, but can be any device with data processing and network communication functions, such as a general computer or tablet.

The server device 30 is a server computer for managing information on users and products with RFID tags attached, etc., by communicating with the user terminal 20 and the relay device 40 via the network 50. The server device 30 is realized by executing a dedicated program in the hardware described later. In particular, in this embodiment, the server device 30 functions as a server device having an information management means 31 for managing various information such as tag information, product information, usage information, and analysis information, a usage information acquisition means 32 for acquiring usage information including the usage period of the product corresponding to the tag ID based on the information of the time when it was first received from the detection device 10 for each tag ID and the information of the time when it was received when the end of use was detected, and an information notification means 33 for notifying the corresponding user terminal 20 when the information managed by the information management means 31 satisfies a predetermined condition.

2 is a hardware configuration diagram of a smartphone that is a user terminal 20. As shown in FIG. 2, the user terminal (smartphone) 20 includes a CPU (Central Processing Unit) 20a, a RAM (Random Access Memory) 20b as a main memory, a large-capacity storage device 20c such as a hard disk or flash memory for storing programs and data executed by the CPU 20a, an instruction input unit 20d such as a keyboard or a touch panel, a data input/output I/F (interface) 20e for data communication with an external device such as a data storage medium, a display unit 20f which is a display device such as a liquid crystal display or an organic EL display, a network communication unit 20g that includes an RF circuit (high frequency circuit) and communicates with other computers via a mobile phone network and a network by radio, a camera 20h that has an image sensor such as a CCD or CMOS, and a short-range wireless communication unit 20i for directly communicating with other devices at a short distance by radio, which are connected to each other via a bus. In reality, a smartphone also includes a microphone, a speaker, etc. (not shown) in addition to those shown in FIG. 2.

The registration request means 21 shown in FIG. 1 is realized by the CPU 20a executing a program stored in the storage device 20c and coordinating with the instruction input unit 20d, the display unit 20f, and the network communication unit 20g. The product information acquisition means 22 is realized by the CPU 20a executing a program stored in the storage device 20c and coordinating with the instruction input unit 20d and the network communication unit 20g. The display means 23 is realized by the CPU 20a executing a program stored in the storage device 20c and outputting information to the display unit 20f.

Figure 3 is a hardware configuration diagram of the server device 30. The server device 30 is realized by incorporating a dedicated program into a general-purpose computer. It is usually managed by a company that is the same as or cooperates with the company that provides the RFID-tagged products, or by a company that is commissioned by such a company. As shown in Figure 3, the server device 30 includes a CPU (Central Processing Unit) 30a, a RAM (Random Access Memory) 30b as a main memory, a large-capacity storage device 30c such as a hard disk or flash memory for storing programs and data executed by the CPU 30a, an instruction input unit 30d such as a keyboard, a data input/output I/F (interface) 30e for data communication with external devices such as data storage media, a display unit 30f which is a display device such as a liquid crystal display, and a network communication unit 30g for network communication with other computers via a network, which are connected to each other via a bus. Note that the server device 30 often does not include the display unit 30f.

The storage device 30c stores various data used in this embodiment. The storage device 30c also stores a program that is loaded into the RAM 30b and executed by the CPU 30a to function as the server device 30.

The information management means 31 shown in FIG. 1 is realized by the CPU 30a executing a program stored in the storage device 30c and processing the data stored in the storage device 30c. The usage information acquisition means 32 is realized by the CPU 30a executing a program stored in the storage device 30c and cooperating with the network communication unit 30g. The information notification means 33 is realized by the CPU 30a executing a program stored in the storage device 30c and cooperating with the network communication unit 30g. In the example of FIG. 1, the server device 30 is shown in a standalone form, but the server device 30 does not mean a single computer, and also includes a cloud-type server device realized by multiple computers distributed over the network 50.

The relay device 40 is a device that accesses the network 50 and relays data between the detection device 10 and the server device 30. Any device can be used as the relay device 40 as long as it is capable of short-range wireless communication with the communication module 13 of the detection device 10 and capable of communication with the server device 30 via the Internet. For example, a smartphone, which is a multi-function mobile phone, or an IoT gateway specialized for data relaying can be used. An IoT gateway is a communication device that is capable of both short-range wireless communication and network communication. For example, Bluetooth (registered trademark) can be used as a method of short-range wireless communication.

In this embodiment, it is assumed that each product M is consumed through use. Therefore, each product M is wrapped in a packaging material P. An RFID tag T is attached to the packaging material P that wraps the product M. Therefore, in reality, the RFID tag T is attached to the packaging material P that wraps the product M, but in this specification, for convenience, it may be expressed as "RFID tag T attached to product M" or "product M with RFID tag T attached". In this embodiment, as an example, the product M is food, etc., and it is determined whether it is in use or not by assuming that it is put in and taken out of a refrigerator as a storage location. For this reason, the RFID reader 11 is installed in a position where it can read the entire area inside the refrigerator. By installing the RFID reader 11 in this way, the tag ID that identifies the product M present in the refrigerator is acquired by the processing module 12, and it can be considered that the product M whose tag ID cannot be acquired for a predetermined period is located away from the refrigerator, that is, is in use.

The specifications of the RFID reader 11 and the RFID tag T are not particularly limited, but since it is sufficient to be able to simultaneously read multiple tag IDs in the refrigerator, it is sufficient to adopt one with a reading distance of 1 m or more. For example, an RFID tag using a radio wave method with a frequency of 860 MHz to 900 MHz in the UHF band can be adopted. RFID tags using a radio wave method with a frequency of 860 MHz to 900 MHz have a long communication distance and are suitable for simultaneous reading. However, since products stored in the refrigerator are likely to be used in the kitchen, it is necessary to adjust the communication distance so that the kitchen is not within the reading range.

The method of attaching the RFID tag T to the packaging material P of the product M is not particularly limited. For example, the RFID tag T itself may be embedded in the packaging material P, or the RFID tag may be a label-fixed type and attached to the packaging material P using the adhesive layer of the label.

The server device 30 stores product information on products to be managed by tag ID. FIG. 4 is a diagram showing an example of product information stored in the server device 30. As shown in FIG. 4, the server device 30 stores product names, product types, content amounts, and standard usage amounts per use in association with product IDs, which are identification information for identifying products. The product name is the name of the product and is usually the product name. The product type is a type by which the specific contents of the product can generally be classified. The content amount is the amount of contents of one product, and is managed by the number of pieces or weight (grams), etc. The standard usage amount per use of the product is the standard usage amount per use, and may be fixed, but can be updated using usage information obtained from the user, as described below. The product information shown in FIG. 4 is an example, and various other information can be stored.

2. Processing Operation
Next, the processing operation of the usage information management system using the terminal device according to the first embodiment of the present invention will be described with reference to the flowchart of FIG. 5 together with the usage information management method according to the first embodiment of the present invention.

First, as a preliminary step, the user (general consumer) needs to prepare a refrigerator equipped with the detection device 10. This refrigerator may be purchased from a refrigerator manufacturer equipped with the detection device 10, or the user may install the detection device 10 in a refrigerator at home. A device ID that identifies the RFID reader 11 equipped in the detection device 10 is recorded, and the device ID is written on the outside of the detection device 10. The user performs an operation to associate the user with the detection device 10 of the refrigerator at home. This operation may be performed in any manner, but in this embodiment, it is performed using a user terminal 20 (smartphone) carried by the user.

A dedicated application program for making the smartphone function as the user terminal 20 is installed in the user terminal 20 (smartphone) owned by the user. To install the dedicated application program in the smartphone, a specific server (not shown, server device 30 may also serve as the server) is accessed via a network, and the dedicated application program (hereinafter referred to as the "app") is downloaded as a so-called "app" for the usage information management system. By starting this app on the smartphone, the smartphone functions as the user terminal 20 of the usage information management system and executes various processes in cooperation with the server device 30.

<2.1. Registration of user information (step S10)>
After the above-mentioned advance preparations are performed, the user first registers user information (step S10). The user information is registered by cooperation between the user terminal 20 and the server device 30. When the user starts the app, the registration request means 21 displays a predetermined screen on the display unit 20f in the user terminal 20 by the function of the app. The user inputs predetermined information and gives predetermined instructions using the screen provided by the registration request means 21. By the processing of the registration request means 21, various types of screens are displayed on the screen of the user terminal 20 realized by a smartphone, and the user can input and give instructions in various types. The specific types of input and instructions can be appropriately designed according to the design specifications of the app, so detailed explanations are omitted. When the user inputs predetermined information and gives predetermined instructions, the registration request means 21 transmits the input information to the server device 30. Then, in the server device 30, the information management means 31 registers the information received from the user terminal 20.

Specifically, a user is registered by inputting user attributes such as name, age, and gender as user-related information on a screen displayed on the display unit 20f of the user terminal 20. At this time, the user checks the device ID for identifying the detection device 10 and the RFID reader 11, which is indicated on the detection device 10 attached to the refrigerator, and inputs it together with the user's own user information. When the user issues a transmission instruction to the user terminal 20, the registration request means 21 in the user terminal 20 transmits the input user information and device ID together with a registration request to the server device 30. In the server device 30, the information management means 31 issues a user ID to the user information received from the user terminal 20 and registers it in the storage device 30c. The information management means 31 then notifies the user by transmitting the issued user ID to the user terminal 20. The user ID is user identification information that is different for each individual user.

The device ID can also be registered using code information such as a two-dimensional code. For example, a two-dimensional code recording the device ID is printed on the surface of the detection device 10. Then, the user switches to camera mode according to the instructions on the screen displayed on the display unit 20f and photographs the two-dimensional code formed on the surface of the detection device 10. For example, a QR code (registered trademark) can be used as the two-dimensional code. The user terminal 20 obtains the device ID recorded in the two-dimensional code by photographing. Then, the user inputs his/her own user information and gives a predetermined instruction. Then, the user terminal 20 transmits the device ID and the user information to the server device 30. In this way, by forming a two-dimensional code recording the device ID on the surface of the detection device 10, the user can easily register the device ID of the detection device 10 attached to the refrigerator at home.

As a result, the user information as shown in FIG. 6 is stored in the storage device 30c of the server device 30. In the example of FIG. 6, the device ID "R00001" is associated with the user ID "U00001," and the device ID "R00002" is associated with the user ID "U00002."

<2.2 Creating tag information (step S20)>
The server device 30 creates tag information (step S20). The server device 30 manages information on each RFID tag T. Specifically, tag information as shown in FIG. 7 is stored for each RFID tag T in the storage device 30c of the server device 30. FIG. 7 is a diagram showing the initial state of the tag information. A tag ID unique to each RFID tag T is stored in each RFID tag T, and the tag ID is transmitted in response to a read request from the RFID reader 11. Each RFID tag T is attached to a packaging material P that wraps a product M by a predetermined method, and the relationship between the RFID tag T and the product to which the RFID tag T is attached is managed as tag information as shown in FIG. 7.

As shown in FIG. 7, the tag ID unique to each RFID tag T is associated with the product ID of the product M to which it is attached. The product ID is identification information for identifying the product. As can be seen by comparing the first and second lines in FIG. 7, even if the product ID "M0001" is the same, different items will correspond to different tag IDs "T00001" and "T00002". In this way, it is possible to manage each item using the RFID tag T. As the product ID, other identification information already in use may be used, such as the JAN code, which is also used as the recording information for the product barcode. Furthermore, the tag information stores the product name and product type corresponding to each product ID.

In addition, the remaining quantity of a product is associated with each tag ID and stored. In the initial state, the remaining quantity is recorded as the content quantity when the product is new. In the examples of Figures 4 and 7, product M with product ID "M0001" identified by product "XX Cheese (large)" has a content quantity of 20 pieces, so the remaining quantities corresponding to tag IDs "T00001" and "T00002" are both recorded as "20 pieces." Similarly, product M with product ID "M0002" identified by product "XX Cheese (small)" has a content quantity of 10 pieces, so the remaining quantities corresponding to tag IDs "T10001" and "T10002" are both recorded as "10 pieces."

In addition, each tag ID is associated with and stored with expiration date information for the product. Expiration date information may be a use-by date, a best-before date, etc. Expiration date information may be managed on a daily or monthly basis. Expiration date information differs depending on the date and month when each individual product was manufactured, even if the product ID is the same.

Furthermore, a user ID and a device ID are stored in association with each tag ID. As described above, the user ID is identification information for identifying the user, and the device ID is identification information for identifying the detection device 10 and the RFID reader 11. As described above, the user ID and device ID are registered based on the user's work using the user terminal 20, but in the initial state before the product is shipped, the user ID and device ID are not stored in the tag information. This is because it is not yet determined which user the product M to be shipped will be delivered to.

The number of uses is the number of times the product corresponding to each tag ID has been used. The number of uses is incremented each time a tag ID is received from the detection device 10. The end status is status information indicating whether the product corresponding to each tag ID has been used up or down. In this embodiment, this is expressed as "Ended", which indicates that the product has been used up, or "Not yet", which indicates that the product has not been used up (not yet).

As shown in FIG. 7, in the initial state, the tag information corresponding to each tag ID has the remaining amount equal to the amount of content when the product was new, the user ID and device ID are not registered (blank in FIG. 7), the number of uses is 0, and the end status is "Not (not completed)". In this embodiment, the user information is registered (step S10), and then the tag information is created (step S20). However, since tag information is created for each RFID tag attached to a product that is manufactured at any time, some products may be created before the user information is registered. As tag information, various information other than that shown in FIG. 7 can be stored. For example, information about the store to which the product is shipped (such as the store name) and information about whether the product has actually been received or removed can also be recorded.

<2.3. Association of tag ID and device ID (step S30)>
Next, the server device 30 associates the tag ID with the device ID (step S30). The product M with the RFID tag T is shipped from the manufacturer and delivered to the user who purchased it via a store, etc. In this embodiment, since the product M is a refrigerated product, the user places the purchased product M in a refrigerator at home.

When the user places an item in the refrigerator in this state, the RFID tag T attached to the item will be located within the readable range of the RFID reader 11. The RFID reader 11 then acquires the tag ID, which is recorded information, from the RFID tag T attached to the item. As described above, the processing module 12 has a memory element and stores a tag ID that has been acquired once. Therefore, each time a tag ID is read, the processing module 12 refers to the memory element to check whether an identical tag ID exists and whether the acquired tag ID has been acquired for the first time. Then, if the acquired tag ID has been acquired for the first time, the communication module 13 associates the acquired tag ID with its own device ID and transmits it to the server device 30.

When the server device 30 receives the tag ID associated with its own device ID from the detection device 10, it references the tag information using the tag ID. If the reference results in a lack of a registered device ID corresponding to the tag ID, it registers the received device ID in association with the tag ID.

<2.4. Transmission of tag ID when in use (step S40)>
Once a product is placed in the refrigerator, the user will take out the product M every time they use it. When the user takes the product M out of the refrigerator, it moves away from the readable distance of the RFID reader 11. The RFID reader 11 will then be unable to read the tag ID from the RFID tag T attached to the taken-out product M. If the time during which the tag ID cannot be read exceeds a predetermined time (e.g., 60 seconds), the processing module 12 transmits the tag ID that can no longer be read, together with its own device ID, from the communication module 13 to the server device 30 (step S40).

<2.5. Updating the number of times a product is used (Step S50)>
Next, the number of uses of the product is updated (step S50). The communication module 13 transmits the tag ID, which is the acquired record information, to the relay device 40. The relay device 40 transmits the tag ID to the server device 30. The server device 30 refers to the tag information using the received tag ID, and updates the number of uses of the tag ID by adding 1. Furthermore, the server device 30 calculates and records the remaining amount of the product identified by the tag ID. Specifically, when the server device 30 acquires the tag ID from the detection device 10, it refers to the tag information ( FIG. 7 ) using the acquired tag ID and acquires the corresponding product ID. Next, it refers to the product information ( FIG. 4 ) using the acquired product ID and acquires the standard amount of use/time corresponding to the product ID. Then, it subtracts the acquired standard amount of use/time from the remaining amount recorded in the tag information to calculate a new remaining amount, and updates the remaining amount in the tag information with the new remaining amount.

For example, in the example of Figure 7, when tag ID "T00001" is obtained from detection device 10, the product information shown in Figure 4 for product M0001 is referenced to obtain the standard amount per use of "1". Then, this "1" is subtracted from the remaining amount of "20" in the tag information shown in Figure 7, updating it to "19". In this way, the server device 30 subtracts the standard amount per use from the remaining amount each time it receives a tag ID from detection device 10. Also, each time it receives a tag ID from detection device 10, the number of uses is incremented by one.

If the tag ID is received again after the remaining amount has reached 0, the remaining amount cannot be deducted any further, so the remaining amount in the tag information remains at 0. However, one usage is added to the number of uses. The remaining amount recorded in the tag information is an estimated value when the standard amount of usage per use is set to a predetermined value, and does not necessarily match the actual remaining amount. For example, in this embodiment, the remaining amount of product M with product ID "M0001" is calculated assuming that two products are used at one time, but in reality, this is not constant, such as one product being used at one time or three products being used at one time, and there are various usage patterns, such as three or more products being used each time.

The fee for one use varies for each user, and it cannot be said that the item has actually been used up. The remaining amount of the item calculated by the server device 30 is an estimate based on the average value of the usage information. Although it is not possible to know the exact quantity, an estimate can be obtained. Therefore, as described below, when the remaining amount of an item corresponding to a certain tag ID falls below a predetermined threshold, the server device 30 can notify the user terminal 20 that the remaining amount of the item is low.

<2.6. Acquisition of usage information (step S60)>
Next, the server device 30 acquires the usage information (step S60). Specifically, first, when the detection device 10 cannot read a tag ID for a predetermined time or more, it determines that the use of the corresponding product has ended. Specifically, a second elapsed time D2 is set as the predetermined time, and when the tag ID cannot be read for the second elapsed time D2 or more, it determines that the use of the corresponding product has ended. That is, the detection device 10 detects that the use of the product has ended. "End of use" means that the product has been used up. For example, if the product has a content of 10 pieces, it means that 10 pieces have been used up. The second elapsed time D2 can be set to any value longer than the above-mentioned first elapsed time D1. For example, the second elapsed time D2 can be set to 24 hours. This is because if the product has not been returned to the refrigerator after 24 hours, it can be considered that the product has been used up.

When the detection device 10 determines that use of a product corresponding to a certain tag ID has ended, it transmits the tag ID together with information indicating that use has ended. When the server device 30 receives the tag ID and information indicating that use has ended from the detection device 10, it calculates the usage period of the product corresponding to that tag ID based on the time information when the tag ID was first received and the time information received when it was detected that use had ended. Specifically, the start time of use is obtained from the time information when the tag ID was first received, and the end time of use is obtained from the time information received when it was detected that use had ended, and the period elapsed from the start time of use to the end time of use is calculated as the usage period.

As the information on the time when it was first received, information close to the time when it was first received can be used, rather than the exact time when it was received. For example, it may be information such as date and time obtained from the internal clock of the server device 30, or it may be date and time information transmitted by the detection device 10 together with the tag ID. Also, as the information on the time when it was received when it was detected that use had ended, information close to the time when it was first received can be used, rather than the exact time when it was received. In this case, it may be information such as date and time obtained from the internal clock of the server device 30, or it may be information such as date and time transmitted by the detection device 10 together with the tag ID. Furthermore, the server device 30 refers to the tag information using the received tag ID, adds 1 to the corresponding number of uses, and determines the number of uses after the addition. In this way, tag IDs are received from the RFID readers installed in the refrigerators of each household, and the final number of uses for each tag ID is recorded and accumulated as product usage information. Furthermore, the end status is changed to "Ended".

Figure 8 is a diagram showing an example of usage information that has been accumulated and acquired. As shown in Figure 8, the final usage period and number of uses are recorded as usage information corresponding to each tag ID. The usage information may include various information other than the usage period and number of uses. Also, only the usage period may be calculated. In this embodiment, analysis information is obtained using the acquired usage information. Specifically, in this embodiment, for each product ID, the average value of the final number of uses is calculated as the standard number of uses. This makes it possible to obtain the standard number of uses, which is the number of times the product will be used. The standard number of uses may be rounded off to an integer value, or may be used as a real value. Furthermore, the product information is referenced by the product ID to obtain the content volume of the product, and the standard amount of use per use is calculated by dividing it by the standard number of uses. In this way, various analysis information can be obtained using the accumulated usage information.

The obtained analysis information can also be recorded as part of the product information. In this embodiment, the standard amount of use per use calculated as the analysis information is added to the product information. Since the standard amount of use per use added to the product information is used to calculate the remaining amount, in this embodiment, it is rounded off to the nearest integer. However, since the calculated remaining amount is an estimated value, it does not necessarily have to be an integer value and may be a real value.

In addition, the analysis information can be linked to the attributes of the user, such as age and gender, and the number of uses. In this case, the server device 30 first refers to the usage information shown in FIG. 8 and acquires the corresponding tag ID for the specified product ID. Then, the server device 30 acquires the user ID by referring to the tag information shown in FIG. 7 for each acquired tag ID. Then, the user information shown in FIG. 6 for each acquired user ID is acquired to acquire the user's age and gender. In this way, information on the age and gender of multiple people is obtained for a specific product ID. Next, the tag ID corresponding to the user ID corresponding to a specific age and gender is acquired, and the average value of the number of uses is calculated using the usage information shown in FIG. 8, thereby obtaining information on the number of uses associated with attributes such as age and gender as analysis information. FIG. 9 is a diagram showing an example of analysis information obtained using the acquired usage information. In FIG. 9, the relationship between the attributes and the number of uses for a product of a certain product ID is shown as analysis information, and age and gender are used as attributes. With such analysis information, it is possible to know how the number of uses of a certain product differs depending on age or gender. This allows you to develop sales strategies such as product volume and packaging shape when targeting a certain age group or gender.

The usage period for each product can also be obtained as analytical information. In this case, the server device 30 first refers to the usage information shown in FIG. 8, obtains all usage periods for the corresponding tag ID for the identified product ID, and calculates the average value. This makes it possible to obtain information on the usage period for each product as analytical information. It is also possible to further calculate the usage period for each product for attributes such as age and gender.

It is also possible to obtain repeat information for each product as analytical information. In this case, the server device 30 first refers to the usage information shown in FIG. 8 and obtains the tag ID corresponding to the identified product ID. Then, for each obtained tag ID, it refers to the tag information shown in FIG. 7 and obtains the user ID. By obtaining the tag ID corresponding to the same user ID for the identified product ID, repeat information on how many of a specific product a specific user has purchased can be obtained as analytical information. Repeat information is information on how frequently a user repeatedly purchases a product. Repeat information can also be calculated for attributes such as age and gender.

<2.7. Notification to User (Step S70)>
The server device 30 notifies the user of various information regarding the calculated remaining amount (step S70). For example, the server device 30 can notify the user of the remaining amount of the product in response to a request from the user. In this case, the user starts a dedicated program on the user terminal 20, operates according to the contents displayed on the screen, and indicates that he/she wishes to obtain information on the products in his/her refrigerator. Then, in accordance with the user's operation, the product information obtaining means 22 on the user terminal 20 transmits a user ID and a request to obtain product information to the server device 30.

When the server device 30 receives a user ID and a request to obtain product information from the user terminal 20, the information notification means 33 references the tag information using the received user ID, obtains the corresponding tag ID, product name, and remaining amount, and transmits these to the user terminal 20 as a response to the obtainment request. In the user terminal 20, the product information obtaining means 22 obtains the tag ID, product name, and remaining amount from the server device 30 as a response to the obtainment request. The display means 23 then displays a list of the product name and remaining amount paired together. This allows the user to know the remaining amount of products in their home refrigerator all at once.

In addition, the information notification means 33 of the server device 30 can provide a predetermined notification when a predetermined condition is met regarding the remaining amount of the product. Specifically, when the remaining amount is less than the threshold value set in advance, the predetermined condition is met, and the registered user address is notified that the remaining amount is low. The user address is stored in association with the user ID in the user information shown in FIG. 6. The registered user address may be any address that can reach the user with information. As described above, when using an app installed in the user terminal 20, the address may be any address that can obtain information from the server device 30 by the app. For example, an address for push notifications of the app may be used. In the case of this service, the information notification means 33 transmits the tag ID, product name, and remaining amount to the registered user address in association with each other. Then, in the user terminal 20, the product information acquisition means 22 acquires the tag ID, product name, and remaining amount from the server device 30. Then, the display means 23 displays a list of the acquired product names and remaining amounts in pairs. This allows the user to know the remaining amounts of the products in the refrigerator at home all at once. If a user installs the app on their smartphone and sets it to notify them of incoming information, they can instantly find out on their smartphone when there is little product left in the refrigerator.

The product information also includes the product name, so the user will be notified, for example, with a message such as "Only a few large pieces of XX cheese left," letting the user know that there is only a little XX large cheese left in the refrigerator. This type of notification service is convenient in that it allows the user, who is primarily responsible for the food in the home, to be aware of the fact that there is only a small amount of a product remaining, even though it has been used by other family members without the user realizing it.

Similarly, the information notification means 33 of the server device 30 can provide a predetermined notification when a predetermined condition is met regarding the expiration date information of a product. Specifically, a predetermined period (e.g., a day or month) is set. Then, using the date information of the day managed by the server device 30, when it is within a predetermined period from the expiration date information, a notification is sent to the registered user address that the expiration date is approaching. Specifically, the information notification means 33 associates the tag ID, product name, and expiration date information and sends them to the registered user address. Then, in the user terminal 20, the product information acquisition means 22 acquires the tag ID, product name, and expiration date information from the server device 30. Then, the display means 23 displays a list of the acquired product name and expiration date in pairs. This allows the user to know which products in the refrigerator are approaching their best-before date (or expiry date), etc.

The server device 30 can also provide services such as a remaining amount confirmation service, an automatic ordering service, a marketing service, and a recipe suggestion service. The remaining amount confirmation service is a service that notifies the user of the remaining amount based on a request from the user terminal, even if the remaining amount is not below a threshold value.

The automatic ordering service is a service that, when the remaining quantity falls below a threshold, accesses a server that handles the purchasing procedures for the item and places an order. In this case, if the address has been registered in advance, the user will have the low-volume item delivered to their home without having to take any steps.

The marketing service is a service that acquires information such as the amount of usage for each product (same product) by dividing it into various indicators such as age and gender, and transmits data on trends for each indicator to businesses such as the product manufacturer and seller. As an extension of this marketing service, it is also possible to conduct surveys on services and products for users via the user terminal 20, and to implement incentive programs (campaigns such as giving away prizes according to the accumulated amount of usage).

The recipe suggestion service is a service that suggests recipes using food remaining in the refrigerator. When providing the recipe suggestion service, the server device 30 is equipped with a recipe suggestion means that manages recipe information separately. Specifically, the recipe information is stored in the storage device 30c in a structure that can be used as a recipe database, and a program that realizes the recipe suggestion means is stored. The recipe information is information that records the specific dish items and the types and amounts of ingredients used. In this embodiment, the product type shown in the product information in Figure 4 is used as the type of ingredients used. For example, it is possible to store nutritional information, allergy information, etc. for each ingredient for each dish item. In this case, nutritional information, allergy information, etc. are also stored in the product information in association with each product ID. This makes it possible to suggest recipes that take nutritional information and allergy information into consideration.

When providing a recipe suggestion service, the recipe suggestion means in the server device 30 refers to the tag information for a certain user ID, and extracts product information for all tag IDs for which the end status is not "Ended" and the expiration date indicated by the expiration date information has not been reached. At this time, the extracted product information for the same product ID is added together to calculate the remaining amount. As a result, the recipe suggestion means can obtain for a certain user the number (grams) of each product in the refrigerator that has not yet reached its expiration date, etc., as the remaining product amount for each user.

The recipe suggestion means then searches the recipe database by the remaining product quantity for each user, and extracts recipes that can be cooked using the combination of remaining quantities of each product in the remaining product quantity for each user. If multiple recipes are extracted, various rankings can be added, such as by popularity or by the closest expiration date. The recipe suggestion means transmits the extracted recipes to the user terminal 20 of that user ID. As a result, the user can learn recipes that use products in their home refrigerator that are within their expiration date.

3. Second embodiment
Next, the second embodiment will be described. FIG. 10 is a diagram showing a usage information management system using a user terminal, which is a terminal device according to the second embodiment of the present invention. In FIG. 10, 10 is a detection device, 20 is a user terminal, 30 is a server device, and 50 is a network. The user terminal 20 and the server device 30 are connected to a public network 50 such as the Internet, and are capable of transmitting and receiving data to and from each other. The user terminal 20 shown in FIG. 1 is a terminal device that presents information regarding the expiration date of a product, and the usage information management system is a system for managing usage information when a user uses a product. In the first embodiment, most of the product information and tag information are managed only by the server device 30, but in the second embodiment, part of the product information and tag information is also managed by the user terminal 20. Also, in the first embodiment, the detection device 10 communicates with the server device 30 via the relay device 40, but in the second embodiment, the user terminal 20 has the function of the relay device 40 and relays communication between the detection device 10 and the server device 30. Furthermore, the detection device 10 only includes an RFID reader 11 and a communication module 13, and the processes performed by the processing module 12, such as determining the usage state and end of usage, are performed by the user terminal 20. In the second embodiment, commands for executing functions performed by the processing module 12 and relay device 40 in the first embodiment are recorded in a dedicated application program called an app, and are executed by the user terminal 20.

In the second embodiment, in addition to the registration request means 21 having the same functions as in the first embodiment, the user terminal 20 functions as a terminal device having a deadline information acquisition means 24 that acquires from the server device 30 deadline information of the product corresponding to the tag ID received from the detection device 10, a deadline information storage means 25 that stores the acquired deadline information in association with the tag ID and the product ID, a display means 26 that displays information on the product identified by the product ID corresponding to the tag ID for which the deadline information stored in the deadline information storage means satisfies a predetermined condition, a recipe storage means 27 that stores recipe information that records the dish item, the product type, and the amount used, and a recipe suggestion means 28 that refers to the tag information, acquires from the recipe storage means 27 recipe information corresponding to the product ID of the product corresponding to the tag ID for which the deadline information has not yet reached the predetermined deadline, and suggests the recipe information.

The deadline information acquisition means 24 shown in FIG. 10 is realized by the CPU 20a executing a program stored in the storage device 20c and cooperating with the instruction input unit 20d and the network communication unit 20g. The deadline information storage means 25 and recipe storage means 27 are realized by the CPU 20a executing a program stored in the storage device 20c and processing data in the storage device 20c. The display means 26 is realized by the CPU 20a executing a program stored in the storage device 20c and outputting information to the display unit 20f. The recipe suggestion means 28 is realized by the CPU 20a executing a program stored in the storage device 20c.

4. Processing Operation
Next, the processing operation of the usage information management system according to the second embodiment of the present invention will be described together with the usage information management method according to the second embodiment with reference to the flowchart of Fig. 11. Fig. 11 is a flowchart showing the processing operation of the usage information management system according to the second embodiment.

The advance preparation is performed in the same manner as in the first embodiment, and the user (general consumer) prepares a refrigerator equipped with a detection device 10, and then in step S11 described below, associates the user with the detection device 10 in the refrigerator at home.

Then, in the same manner as in the first embodiment, an app, which is a dedicated application program, is downloaded to make the smartphone function as the user terminal 20. The user terminal 20 is a terminal device having at least a deadline information acquisition means for acquiring deadline information of a product corresponding to the tag ID received from the detection device 10 from the server device 30, a storage means for storing the acquired deadline information in association with the tag ID and the product ID, and a display means for displaying information of a product identified by the product ID corresponding to the tag ID for which the deadline information stored in the storage means satisfies a predetermined condition. The deadline information acquisition means, (information) storage means, and (product information) display means are realized by incorporating an app, which is a dedicated program, into the hardware shown in FIG. 2, i.e., the storage device 20c, the display unit 20f, the network communication unit 20g, etc., which is essentially a computer equipped with a memory function, an input/output function, and a communication function.

<4.1. Registration of user information (step S11)>
After the above-mentioned preparations have been made, the user registers user information in the same manner as in the first embodiment (step S11).

As a result, user information such as that shown in FIG. 6 is stored in the storage device 30c of the server device 30. In the example of FIG. 6, the device ID "R00001" is associated with the user ID "U00001", and the device ID "R00002" is associated with the user ID "U00002". In addition, at this time, the user address, which is the address at which information can reach the user, is obtained from the user terminal 20 and registered in association with the user ID.

<4.2 Creating tag information (step S21)>
The server device 30 creates tag information in the same manner as in the first embodiment (step S21). The process in step S21 is basically the same as the process in step S20 in the first embodiment.

<4.3. Association of tag ID and device ID (step S31)>
Next, the server device 30 associates the tag ID with the device ID (step S31). The product M with the RFID tag T attached is shipped from the manufacturer and delivered to the user who purchased it through a store or the like. When the user puts the item in the refrigerator in this state, the RFID tag T attached to the item is located within the readable range of the RFID reader 11. Then, the RFID reader 11 acquires the tag ID, which is the recorded information, from the RFID tag T attached to the item. Then, the communication module 13 transmits the acquired tag ID to the user terminal 20. The user terminal 20 stores the tag ID acquired once in the storage device 20c. Therefore, every time the tag ID is read, the storage device 20c is referred to to check whether the same tag ID exists and whether the acquired tag ID is acquired for the first time. Then, if the acquired tag ID is acquired for the first time, the network communication unit 20g associates the acquired tag ID with the registered device ID and transmits it to the server device 30. At this time, the user terminal 20 also requests the server device 30 to acquire tag information corresponding to the tag ID.

When the server device 30 receives a request to acquire tag information from the user terminal 20 in association with the tag ID and device ID, the server device 30 refers to the tag information using the tag ID. If the result of the reference is that a device ID corresponding to the tag ID is not registered, the server device 30 registers the received device ID in association with the tag ID. The server device 30 then transmits the tag information corresponding to the tag ID to the user terminal 20 that originated the acquisition request. The user terminal 20 stores and manages the tag information received from the server device 30 in the storage device 20c. Therefore, the user terminal 20 also manages tag information having the same items as the tag information managed by the server device 30. However, since one user terminal 20 basically corresponds to one user and one detection device 10, the tag information managed by the user terminal 20 does not need to have items for the user ID and device ID.

<4.4. Transmission of tag ID when in use (step S41)>
As described above, after a product is placed in the refrigerator once, the user will take out the product M every time he or she uses it. When the user takes the product M out of the refrigerator, the product M moves away from the readable distance of the RFID reader 11. The RFID reader 11 will then be unable to read the tag ID from the RFID tag T attached to the taken-out product M. If the time during which the tag ID cannot be read exceeds a predetermined time (e.g., 60 seconds), in the second embodiment, the user terminal 20 transmits the tag ID that can no longer be read, together with the device ID of the detection device 10, from the network communication unit 20g to the server device 30 (step S41).

<4.5. Updating the number of times a product is used (Step S51)>
Next, the number of times the product has been used is updated (step S51). The tag ID determined to be in a used state as described above is transmitted from the user terminal 20 to the server device 30. The server device 30 uses the received tag ID to update the number of times the product has been used in the same manner as in step S50 in the first embodiment. Furthermore, in the second embodiment, the same process as in step S50 in the first embodiment is also executed on the tag information managed within the user terminal 20, and the number of times the product has been used is updated. That is, in the second embodiment, the same tag information is updated in parallel with the server device 30.

<4.6. Acquisition of Usage Information (Step S61)>
Next, the server device 30 acquires the usage information (step S61). Specifically, first, when there is no transmission from the detection device 10 for a predetermined time or more for a certain tag ID, the user terminal 20 determines that the use of the corresponding product has ended. Specifically, as in the first embodiment, a second elapsed time D2 is set as the predetermined time, and when the tag ID cannot be read for the second elapsed time D2 or more, the server device 30 determines that the use of the corresponding product has ended. That is, the user terminal 20 detects that the use of the product has ended.

When the user terminal 20 determines that use of a product corresponding to a certain tag ID has ended, it transmits the tag ID together with information indicating that use has ended. When the server device 30 receives the tag ID and information indicating that use has ended from the user terminal 20, it calculates the usage period of the product corresponding to that tag ID based on the information on the time when the tag ID was first received and the information on the time when the tag ID was received when it was detected that use had ended, in the same manner as in step S60 in the first embodiment. Specifically, as in the first embodiment, the start time of use is obtained from the information on the time when the tag ID was first received, and the end time of use is obtained from the information on the time when the tag ID was received when it was detected that use had ended, and the period elapsed from the start time of use to the end time of use is calculated as the usage period.

As the information on the time when it was first received, it is possible to use information close to the time when it was first received, rather than the exact time when it was received. For example, it may be information such as date and time obtained from the internal clock of the server device 30, or it may be date and time information that the user terminal 20 transmits together with the tag ID. Also, as the information on the time when it is received when it is detected that use has ended, it is possible to use information close to the time when it was first received, rather than the exact time when it was received. In this case, it is also possible to use information such as date and time obtained from the internal clock of the server device 30, or it may be information such as date and time that the user terminal 20 transmits together with the tag ID.

In the second embodiment, the server device 30 executes the same process as in the first embodiment, and can obtain the usage information shown in FIG. 8 and the analysis information shown in FIG. 9.

<4.7. Notification to User (Step S71)>
The user terminal 20 notifies the user of various information using the tag information (step S71). Specifically, when the user starts the app, the tag information in the storage device 20c is referenced to obtain the corresponding tag ID, product name, and remaining amount, and the product name and remaining amount are paired and displayed in a list on the display unit 20f of the user terminal 20. This allows the user to know the remaining amount of the products in the refrigerator at home all at once.

In addition, a predetermined notification can be issued when a predetermined condition is met regarding the remaining amount of the product. An example of the predetermined condition can be when the remaining amount is less than a predetermined threshold. Specifically, the app is constantly running on the user terminal 20, and when the remaining amount of the product in the tag information is compared with a set threshold by the function of the app and the remaining amount becomes less than the threshold, the function of the app causes the user terminal 20 to notify the user by displaying a message on the display unit 20f indicating that the remaining amount of the product is low. With this function of the app, if the user installs the app on their smartphone and sets it to a mode that constantly monitors the remaining amount, the user can immediately know on their own smartphone that the remaining amount of the product in the refrigerator is low, without communicating with the server device 30.

The tag information in the user terminal 20 transmits a product information acquisition request together with the product ID to the server device 30 at any timing. An example of this timing is when tag information is received from the server device 30 and product information corresponding to the product ID included in the received tag information is not stored in the user terminal 20. In response to the product information acquisition request from the user terminal 20, the server device 30 transmits product information corresponding to the received product ID to the user terminal 20. The product information transmitted at this time may be all of the items shown in FIG. 4, or may be set arbitrarily, for example, to only the product name and product type.

By recording the product name in the product information stored in the user terminal 20, for example, "XX cheese (large) only a few left" will be displayed, allowing the user to be aware that there is only a little XX cheese (large) left in the refrigerator. This type of app function is convenient in that it allows the user, who is primarily responsible for managing the food in the home, to find out information about products that have been used by other family members and have unknowingly reduced in quantity.

Similarly, when a predetermined condition is met for the product's expiration information, a predetermined notification can be given. In this case, the expiration information acquisition means 24 acquires expiration information for the product corresponding to the tag ID from the server device 30. Next, the acquired expiration information is stored in the expiration information storage means 25 in association with the tag ID and the product ID. Then, for the tag ID whose expiration information stored in the expiration information storage means 25 satisfies the predetermined condition, the display means 26 displays information on the product identified by the product ID corresponding to that tag ID to notify the user. The predetermined condition can be, for example, that the date indicated in the expiration information is within a predetermined period from the current date. In this case, a predetermined period (for example, a day or month) is set in advance. Then, when the app is left running at all times on the user terminal 20, the user terminal 20 periodically compares the date information of the current day with the expiration information by the function of the app. Then, when a product ID whose current date is within a predetermined period from the expiration information is detected, the display means 26 in the user terminal 20 by the function of the app notifies the user by displaying on the display unit 20f that the product's expiration date is approaching. With this app's functionality, if a user installs the app on their smartphone and sets it to a mode that constantly monitors expiration date information, the user can immediately know on their own smartphone that the expiration date of products in the refrigerator is approaching, without communicating with the server device 30.

Furthermore, the server device 30 can provide services such as a remaining amount confirmation service, an automatic ordering service, a marketing service, and a recipe suggestion service, in the same manner as in the first embodiment. In the second embodiment, the app's functions can provide functions such as a remaining amount confirmation function, an automatic ordering function, and a recipe suggestion function, by utilizing tag information, product information, and the like stored in the user terminal 20. The remaining amount confirmation function is a function that notifies the user terminal 20 of the remaining amount in response to an instruction even if the remaining amount is not less than the threshold value as described above.

The automatic ordering function is a service where, when the remaining amount falls below a threshold, the user terminal 20 accesses a server that processes the purchase of the item and places an order. In this case, by simultaneously transmitting the delivery address, the user will have the low-remaining item delivered to their home without having to carry out any procedures.

The recipe suggestion function is a function that suggests recipes using food remaining in the refrigerator. To realize the recipe suggestion function, the user terminal 20 is provided with a recipe suggestion means that manages recipe information separately. Specifically, the recipe information is stored in the storage device 20c to realize the recipe storage means, and a structure that can be used as a recipe database is provided, and a program that realizes the recipe suggestion means is stored as part of an application or in association with the application. The recipe information is information that records the specific dish items and the types and amounts of ingredients used. In this embodiment, the product types shown in the product information in FIG. 4 are used as the types of ingredients used. For each dish item, for example, nutritional information, allergy information, etc. for each ingredient can also be stored. In this case, nutritional information, allergy information, etc. are also stored in the product information in association with each product ID. This makes it possible to suggest recipes that take nutritional information and allergy information into consideration.

When executing the recipe suggestion function, the recipe storage means 27, which stores recipe information that records the dish items, product type, and amount used, is configured using the storage device 20c. Then, in the user terminal 20, the recipe suggestion means 28, which is realized by executing the app, refers to the tag information in the recipe storage means 27 and extracts product information for all tag IDs whose end status is not "Ended" and whose expiration date indicated by the expiration information has not been reached. At this time, the extracted product information with the same product ID is added together to calculate the remaining amount. As a result, the recipe suggestion means 28 can obtain the number (grams) of each product in the refrigerator that has not reached its expiration date, etc., as the remaining product amount for that user.

The recipe suggestion means 28 then searches the recipe storage means 27 and extracts recipes that can be cooked using the combination of remaining amounts of each product in the product remaining amount. If multiple recipes are extracted, various rankings can be added, such as order of popularity or order of nearest expiration date. The recipe suggestion means 28 displays the extracted recipes on the display unit 20f. As a result, the user can learn recipes that use products in the refrigerator at home that are within their expiration date.

Although the preferred embodiment of the present invention has been described above, the present invention is not limited to the above embodiment, and various modifications are possible. For example, in the above first embodiment, the user terminal 20 is realized as a smartphone and the relay device 40 is realized as an IoT gateway, and the user terminal 20 and the relay device 40 are realized as separate hardware. However, the user terminal 20 and the relay device 40 may be realized as hardware that fits into a single housing. For example, a smartphone may be provided with the functions of both the user terminal 20 and the relay device 40 by incorporating a dedicated program.

In the second embodiment, a smartphone is used as the user terminal 20, and the user terminal 20 has the functions of the relay device 40. However, as in the first embodiment, the user terminal 20 and the relay device 40 may be realized by separate hardware.

In addition, in the above embodiment, information about users and RFID tags is stored and managed in the manner shown in Figures 4 and 6 to 8, but as long as it is configured to be able to obtain the necessary information based on the correspondence relationships defined by these, it is not limited to the manner shown in Figures 4 and 6 to 8.

In the above embodiment, the usage information management system is described with one server device 30 as an example, but the server device 30 may be physically composed of one computer or may be composed of multiple computers. Also, the system may be configured as a so-called cloud type in which multiple computers work together to perform processing on a network.

In the above embodiment, the product is a refrigerated food product, and a refrigerator is used as an example of a storage location. However, if the product is not a refrigerated food product, a food shelf, a pantry, a washing machine, a dresser, etc. can be used as a storage location. If the product is a non-food product, various locations such as a dresser can be used as a storage location as long as the product can be stored.

In addition, the information is not limited to that described in the above embodiment, and various other information can be recorded in the server device. The server device can be connected to the computers of various vendors in the distribution process, and the information input from them can be managed centrally by the server device. For example, in addition to the above product information and tag information, product images, product sizes, production dates, production locations, production conditions, inspection data, distribution conditions, shipping dates, etc. can be input from the manufacturer's computer, collection dates, delivery data, warehouse locations, shipping data, etc. can be input from the distributor's computer, and store names, locations, arrival data, prices, purchaser information, payment information, purchase dates, etc. can be input from the retailer's computer.

10: Detection device 11: RFID reader 12: Processing module 13: Communication module (transmission means)
20a, 30a...CPU
20b, 30b...RAM
20c, 30c... Storage device 20d, 30d... Instruction input unit 20e, 30e... Data input/output I/F
Description of the Invention 20f, 30f: Display unit 20g, 30g: Network communication unit 20h: Camera 20i: Short-range wireless communication unit 20: User terminal 21: Registration request means 22: Product information acquisition means 23: Display means 24: Expiration date information acquisition means 25: Expiration date information storage means 26: Display means 27: Recipe storage means 28: Recipe suggestion means 30: Server device 31: Information management means 32: Usage information acquisition means 33: Information notification means 40: Relay device 50: Network M: Product P: Packaging material T: RFID tag

Claims (2)

A terminal device capable of data communication with a server device that manages tag information in which, for each tag ID that identifies an RFID tag attached to a product, a product ID that identifies the product to which the RFID tag in which the tag ID is recorded is attached, a device ID that identifies a detection device equipped with an RFID reader, and expiration date information of the product identified by the tag ID are associated,
The terminal device
a registration request means for requesting the server device to perform registration in which a device ID for identifying a detection device having an RFID reader for reading the tag ID from the RFID tag and a user ID for identifying a user are associated with each other;
a product information acquiring means for acquiring, from the server device, information on a product identified by a product ID corresponding to the tag ID, for which expiration date information of the product corresponding to the tag ID satisfies a predetermined condition;
and a display means for displaying the acquired product information. a computer capable of data communication with a detection device having an RFID reader that reads a tag ID that identifies an RFID tag attached to a product from the RFID tag, and capable of data communication with a server device that manages tag information that associates, for each tag ID, a product ID that identifies a product to which the RFID tag is attached in which the tag ID is recorded, a device ID that identifies the detection device, and expiration date information of the product identified by the tag ID;
a registration request means for requesting the server device to perform registration in which a device ID for identifying a detection device having an RFID reader for reading a tag ID for identifying the RFID tag from the RFID tag is associated with a user ID for identifying a user;
a product information acquiring means for acquiring, from the server device, information on a product identified by a product ID corresponding to the tag ID, for the tag ID whose expiration date information satisfies a predetermined condition;
A program for causing the display means to function as a display means for displaying the acquired product information.