Information recommendation method, food material storage apparatus, and server

Abstract

This application discloses an information recommendation method, a food storage device, and a server, belonging to the field of electronic technology. The information recommendation method includes: sending a dish recommendation request to a server; receiving dish recommendation information sent by the server based on the dish recommendation request; and displaying the dish recommendation information. The dish recommendation information is determined by the server based on ingredients stored in a target food storage device and ingredients stored in auxiliary food storage devices that meet target conditions. The target conditions include at least one of the following: the distance to the target food storage device is less than a distance threshold, and the storage of login information for a target account logged into the target food storage device. This application solves the problem of the relatively limited functionality of food storage devices. This application is used for food storage and dish recommendation.

Description

Technical Field

[0001] This application relates to the field of electronic technology, and in particular to an information recommendation method, food storage equipment, and server. Background Technology

[0002] With the development of electronic technology, there are increasingly higher demands for the intelligent and multifunctional use of household appliances (such as refrigerators). Currently, refrigerators are primarily used for storing food, and their function is relatively simple. Summary of the Invention

[0003] This application provides an information recommendation method, a food storage device, and a server, which can solve the problem of the limited functionality of food storage devices. The technical solution is as follows:

[0004] On the one hand, an information recommendation method is provided for target food storage equipment, the method comprising:

[0005] Send a menu recommendation request to the server;

[0006] Receive the dish recommendation information sent by the server based on the dish recommendation request;

[0007] Display recommended information for the dishes;

[0008] The recommended information for the dishes is determined by the server based on the ingredients stored in the target ingredient storage device and the ingredients stored in the auxiliary ingredient storage device that meet the target conditions. The target conditions include at least one of the following: the distance to the target ingredient storage device is less than a distance threshold, and the login information of the target account logged in on the target ingredient storage device is stored.

[0009] On the other hand, an information recommendation method is provided for a server, the method comprising:

[0010] Receive a dish recommendation request sent by the target ingredient storage device;

[0011] Based on the dish recommendation request, an auxiliary food storage device that meets the target conditions is determined. The target conditions include at least one of the following: the distance between the auxiliary food storage device and the target food storage device is less than a distance threshold, and the target food storage device stores login information of the target account logged in.

[0012] Based on the ingredients stored in the target ingredient storage device and the ingredients stored in the auxiliary ingredient storage device, the recommended information for the dishes is determined;

[0013] Send the recommended information of the dish to the target ingredient storage device.

[0014] Furthermore, a food storage device is provided, the food storage device comprising:

[0015] A storage room, used for storing food ingredients;

[0016] Communication interface, used for communicating with the server;

[0017] The controller is configured to: send a dish recommendation request to the server via the communication interface; receive dish recommendation information sent by the server based on the dish recommendation request, wherein the dish recommendation information is determined by the server based on the ingredients stored in the target ingredient storage device and the ingredients stored in the auxiliary ingredient storage device that meet the target conditions, wherein the target conditions include at least one of the following: the distance to the target ingredient storage device is less than a distance threshold, and the login information of the target account logged in on the target ingredient storage device is stored;

[0018] A display screen is used to show recommended information about the dishes.

[0019] In another aspect, a server is provided, the server comprising:

[0020] A network interface unit is used to communicate with food storage equipment;

[0021] Processing unit, used for:

[0022] The network interface unit receives a dish recommendation request sent by the target ingredient storage device.

[0023] Based on the dish recommendation request, an auxiliary food storage device that meets the target conditions is determined. The target conditions include at least one of the following: the distance between the auxiliary food storage device and the target food storage device is less than a distance threshold, and the target food storage device stores login information of the target account logged in.

[0024] Based on the ingredients stored in the target ingredient storage device and the ingredients stored in the auxiliary ingredient storage device, the recommended information for the dishes is determined;

[0025] The network interface unit sends the recommended information of the dish to the target ingredient storage device.

[0026] The beneficial effects of the technical solution provided in this application include at least the following:

[0027] The information recommendation method provided in this application includes a target ingredient storage device capable of storing ingredients and recommending dishes. The dishes recommended by the target ingredient storage device to the user are determined based on the ingredients stored in the target ingredient storage device and those stored in auxiliary ingredient storage devices. This allows for the recommendation of suitable dishes to the user based on ingredients from multiple available storage devices, ensuring a relatively diverse selection of dishes recommended by the target ingredient storage device. Therefore, the target ingredient storage device offers rich functionality and high flexibility in use. Attached Figure Description

[0028] Figure 1 This is a schematic diagram of the structure of an information recommendation system provided in an embodiment of this application;

[0029] Figure 2 This is a schematic diagram of the structure of a food storage device provided in an embodiment of this application;

[0030] Figure 3 This is a schematic diagram of the structure of a server provided in an embodiment of this application;

[0031] Figure 4 This is a flowchart of an information recommendation method provided in an embodiment of this application;

[0032] Figure 5 This is a flowchart of another information recommendation method provided in the embodiments of this application;

[0033] Figure 6 This is a flowchart of another information recommendation method provided in the embodiments of this application;

[0034] Figure 7 This is a display interface diagram of a food storage device provided in an embodiment of this application;

[0035] Figure 8 This is a display interface diagram of another food storage device provided in an embodiment of this application;

[0036] Figure 9 This is a display interface diagram of another food storage device provided in this application embodiment;

[0037] Figure 10 This is a display interface diagram of another food storage device provided in this application embodiment;

[0038] Figure 11 This is a schematic diagram of the display interface of a food storage device provided in another embodiment of this application;

[0039] Figure 12 This is a schematic diagram of the display interface of another food storage device provided in another embodiment of this application;

[0040] Figure 13 This is a schematic diagram of the display interface of a food storage device provided in another embodiment of this application;

[0041] Figure 14 This is a flowchart of yet another information recommendation method provided in the embodiments of this application;

[0042] Figure 15 This is a flowchart of yet another information recommendation method provided in the embodiments of this application;

[0043] Figure 16 This is a flowchart of yet another information recommendation method provided in the embodiments of this application;

[0044] Figure 17 This is a flowchart of another information recommendation method provided in the embodiments of this application. Detailed Implementation

[0045] To make the objectives, technical solutions, and advantages of this application clearer, the embodiments of this application will be described in further detail below with reference to the accompanying drawings.

[0046] With the development of electronic technology and Artificial Intelligence & Internet of Things (AIoT) technology, the requirements for various household appliances are becoming increasingly higher. Currently, intelligent management of food storage equipment and intelligent information recommendation have become one of the trends in refrigerator development. At present, refrigerators have relatively limited functions, and even when they have information recommendation capabilities, the flexibility of information recommendation is low. The information recommendation method provided in the following embodiments of this application can enrich the functions of food storage equipment and improve the flexibility of information recommendation.

[0047] Figure 1 This is a schematic diagram of an information recommendation system provided in an embodiment of this application. The information recommendation system may include a server 20 connected via communication and multiple food storage devices 10. These food storage devices 10 can be refrigerators, freezers, wine cabinets, or fruit and vegetable cabinets, etc., capable of storing food. This embodiment of the application uses an example where the multiple food storage devices 10 include two food storage devices, such as a target food storage device and a backup food storage device. It should be noted that the information recommendation system may include one server 20 or multiple servers 20. Figure 1 Take an information recommendation system consisting of only one server 20 as an example.

[0048] It should be noted that the server 20 described in this embodiment can be a single server or a server cluster consisting of multiple servers. The food storage device 10 can communicate with the server 20 through various communication methods, such as allowing the food storage device 10 to communicate via a local area network (LAN), wireless local area network (WLAN), and other networks. The server 20 can provide various content to the food storage device 10 through this network.

[0049] Figure 2 This is a schematic diagram of the structure of a food storage device provided in an embodiment of this application. Figure 2 As shown, the food storage device 10 may include: a housing 101, a door 102, a display screen 103, a communication interface, and a controller. Figure 2 (Not shown in the image). The housing 101 includes a storage compartment with an opening K; a door 102 is movably connected to the housing 101 to cover the opening K; a display screen 103 is located on the surface of the door 102 opposite to the opening K and is used to display a graphical user interface (GUI). For example, the display screen 103 is a touch screen, allowing the user to operate on it to receive corresponding commands from the controller. A communication interface is a component used to communicate with external devices or servers according to various communication protocol types. For example, the communication interface can be a Wi-Fi chip, Bluetooth communication protocol chip, wired Ethernet communication protocol chip, or other network communication protocol chips or near-field communication protocol chips. The controller controls the operation of the food storage device 10 and responds to user operations through various software control programs within the food storage device. Optionally, application software can also be installed in the food storage device. The display screen 103 can display icons for various application software. The user can click on the icon of the application software, and the controller can then launch the application software and control the display screen 103 to display the corresponding interface of the application software. The communication interface and controller can be located anywhere inside or outside the housing 101 and the door 102. This application embodiment does not limit the location of the communication interface and controller.

[0050] Optionally, the food storage device may also include multiple structures such as an image acquisition device (e.g., a camera), a door open / close detector, a speaker, a microphone, and a memory, all of which can be communicatively connected to the controller. At least one of the speaker and the display screen can serve as an information output component to output information for user interaction; at least one of the microphone and the display screen can serve as an information input component to receive information from user interaction with the food storage device. When the information output component includes a speaker, the information output is the voice information played by the speaker; when the information output component includes a display screen, the information output is the information displayed on the display screen (e.g., text or image information). When the information input component includes a microphone, the information input is the voice information collected by the microphone; when the information input component includes a display screen, the information input is the information (e.g., text or image information) triggered by user operation on the display screen.

[0051] Optionally, the image acquisition device can be used to acquire images of the external environment to adaptively change display parameters; it can also be used to acquire user attributes or user interaction gestures to achieve interactive functionality with the user. For example, the food storage device may include a first image acquisition device 104a and a second image acquisition device 104b. The first image acquisition device 104a can be used to acquire images of the food in the storage room, such as when the first image acquisition device 104a is located on top of the housing 101; the second image acquisition device 104b can be used to acquire images of the environment outside the storage room or acquire user interaction gestures, etc., and is located outside the storage room, such as above the display screen 103. Optionally, the first image acquisition device 104a can acquire images of the storage room when the door of the food storage device is open, and stop acquiring images when the door of the food storage device is closed. Optionally, the first image acquisition device 104a can also be located inside the storage room, in which case it can acquire images of the food in the storage room when the door of the food storage device is closed. Optionally, a light source may also be provided in the storage room to illuminate the storage room when the door of the food storage equipment is closed, so that the first image acquisition device 104a can acquire images of the food in the storage room. The first image acquisition device 104a may also be located in other positions, such as the top of the door 102, which is not limited in this embodiment. It should be noted that the "top" of a certain structure described in this embodiment refers to the end of the structure away from the ground when the food storage equipment is placed on the ground for normal use.

[0052] Optionally, the memory can be located within the housing or door, or it can be independent of the housing and door. The memory can be used to store images acquired by the image acquisition device, recognition results obtained by the controller from recognizing the food images, and other information that needs to be stored. Optionally, a door switch detector can be used to detect whether the door is open or closed. For example, the door switch detector can be positioned within the housing where it can contact the door. When the door switch detector is not in contact with the door, it determines that the door is open; when the door switch detector contacts the door, it determines that the door is closed. The controller can control the display screen to show the recognition results of the food images or other information; in this case, the display screen acts as an information output component. The display screen can also be a touch screen, in which case the user can interact with the food storage device through the touch screen. For example, the user can touch the display screen to trigger the controller to generate corresponding instructions and execute those instructions; in this case, the display screen acts as an information input component.

[0053] Optionally, the speaker and microphone can be mounted on the housing or on the door. For example, the speaker and microphone can be positioned in the same location as the image acquisition unit. The speaker, microphone, and image acquisition unit can collectively form a sensing module located on the top of the housing. This sensing module can be connected to a drive component that can extend or retract the sensing module from the top of the housing. The controller can control the speaker to emit voice messages to prompt the user for appropriate operations. The controller can also control the microphone to collect sound information from the environment surrounding the food storage equipment to generate corresponding instructions.

[0054] Optionally, the controller can control the drive component to move the sensing module based on the door's state (open or closed) or a voice command from the user. For example, when the controller determines the door is open, it can control the drive component to push the sensing module closer to the door, and stop pushing it when it reaches a predetermined position. Then, the image acquisition unit in the sensing module is activated. When the controller determines the door is closed, it can control the image acquisition unit to stop working and control the drive component to retract the sensing module away from the door, stopping the retraction when the sensing module is returned to its original position.

[0055] The controller may include a central processing unit (CPU), a graphics processing unit (GPU), or a combination of a CPU and a GPU. The processor may further include hardware chips. These hardware chips may be application-specific integrated circuits (ASICs), programmable logic devices (PLDs), or combinations thereof. The PLDs may be complex programmable logic devices (CPLDs), field-programmable gate arrays (FPGAs), generic array logic (GALs), or any combination thereof.

[0056] The memory is connected to the controller via a bus or other means. The memory stores at least one instruction, at least one program, code set, or instruction set. The controller loads and executes the aforementioned instruction, program, code set, or instruction set to implement the information recommendation method provided in this application embodiment. The memory can be volatile memory, non-volatile memory, or a combination thereof. Volatile memory can be random-access memory (RAM), such as static random-access memory (SRAM) or dynamic random-access memory (DRAM). Non-volatile memory can be read-only memory (ROM), such as programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), or electrically erasable programmable read-only memory (EEPROM). Non-volatile memory can also be flash memory, magnetic storage such as magnetic tape, floppy disk, and hard disk. Optical discs can also be non-volatile memory.

[0057] Figure 3 This is a schematic diagram of a server structure provided in an embodiment of this application. The server 20 includes a central processing unit (CPU) 201, a system memory 204 including random access memory (RAM) 202 and read-only memory (ROM) 203, and a system bus 205 connecting the system memory 204 and the CPU 201. The server 20 also includes a basic input / output system (I / O system) 206 to facilitate the transmission of information between various devices within the computer, and a mass storage device 207 for storing the operating system 213, application programs 214, and other program modules 215.

[0058] The basic input / output system 206 includes a display 208 for displaying information and an input device 209 for user input, such as a mouse or keyboard. Both the display 208 and the input device 209 are connected to the central processing unit 201 via an input / output controller 210 connected to the system bus 205. The basic input / output system 206 may also include the input / output controller 210 for receiving and processing input from multiple other devices such as a keyboard, mouse, or electronic stylus. Similarly, the input / output controller 210 also provides output to a display screen, printer, or other types of output devices.

[0059] The mass storage device 207 is connected to the central processing unit 201 via a mass storage controller (not shown) connected to the system bus 205. The mass storage device 207 and its associated computer-readable media provide non-volatile storage for the server 20. That is, the mass storage device 207 may include computer-readable media (not shown) such as a hard disk or a CD-ROM drive.

[0060] Without loss of generality, the computer-readable medium may include computer storage media and communication media. Computer storage media include volatile and non-volatile, removable and non-removable media implemented using any method or technology for storing information such as computer-readable instructions, data structures, program modules, or other data. Computer storage media include RAM, ROM, EPROM, EEPROM, flash memory or other solid-state storage technologies, CD-ROM, DVD or other optical storage, magnetic tape cassettes, magnetic tape, disk storage, or other magnetic storage devices. Of course, those skilled in the art will recognize that the computer storage media are not limited to the above-mentioned types. The system memory 204 and mass storage device 207 described above can be collectively referred to as memory.

[0061] According to various embodiments of this application, the server 20 can also be connected to a remote computer on a network, such as the Internet. That is, the server 20 can be connected to the network 212 via the network interface unit 211 connected to the system bus 205, or the network interface unit 211 can be used to connect to other types of networks or remote computer systems (not shown).

[0062] The memory also stores one or more programs, and the central processing unit 201 executes the one or more programs to implement the information recommendation method provided in the following embodiments of this application.

[0063] In exemplary embodiments, a non-transitory computer-readable storage medium including instructions is also provided, such as a memory including instructions that can be executed by a server's processor to perform the information recommendation methods shown in various embodiments of this application. For example, the non-transitory computer-readable storage medium may be a ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, and optical data storage device, etc.

[0064] Figure 4 This is a flowchart illustrating an information recommendation method provided in an embodiment of this application. This method can be used in a target food storage device, which can be... Figure 1 Any one of the multiple food storage devices shown, or Figure 2 The food storage device 10 shown may include the following method:

[0065] Step 401: Send a dish recommendation request to the server.

[0066] Step 402: Receive the dish recommendation information sent by the server based on the dish recommendation request. The dish recommendation information is determined by the server based on the ingredients stored in the target ingredient storage device and the ingredients stored in the auxiliary ingredient storage device that meet the target conditions. The target conditions include at least one of the following: the distance to the target ingredient storage device is less than a distance threshold, and the login information of the target account logged in on the target ingredient storage device is stored.

[0067] Step 403: Display recommended information for the dishes.

[0068] In summary, the information recommendation method provided in this application embodiment allows the target food storage device to both store food ingredients and recommend dishes. The dishes recommended by the target food storage device to the user are determined based on the food ingredients stored in the target food storage device and those stored in auxiliary food storage devices. This allows for the recommendation of suitable dishes to the user based on the food ingredients available from multiple food storage devices, ensuring a relatively rich selection of dishes recommended by the target food storage device. Therefore, the target food storage device offers a wide range of functions and high flexibility in use.

[0069] Figure 5 This is a flowchart of another information recommendation method provided in an embodiment of this application. This method can be used for... Figure 1 or Figure 3 The method may include: (as shown in the server 20)

[0070] Step 501: Receive the dish recommendation request sent by the target ingredient storage device.

[0071] Step 502: Based on the dish recommendation request, determine the auxiliary food storage device that meets the target conditions. The target conditions include at least one of the following: the distance to the target food storage device is less than a distance threshold, and the login information of the target account logged in on the target food storage device is stored.

[0072] Step 503: Based on the ingredients stored in the target ingredient storage device and the ingredients stored in the auxiliary ingredient storage device, determine the recommended information for the dish.

[0073] Step 504: Send the recommended recipe information to the target ingredient storage device.

[0074] In summary, the information recommendation method provided in this application embodiment allows the server to determine recommended dish information based on the ingredients stored in the target ingredient storage device and the ingredients stored in the auxiliary ingredient storage device. The server then sends this recommended dish information to the target ingredient storage device for display. Thus, the target ingredient storage device not only stores ingredients but also recommends suitable dishes to the user based on ingredients from multiple available storage devices, ensuring a diverse selection of recommended dishes. Therefore, the target ingredient storage device offers rich functionality and high flexibility.

[0075] Figure 6 This is a flowchart of another information recommendation method provided in the embodiments of this application. This method can be used for Figure 1 The information recommendation system shown is illustrated below. The following embodiments of this application use an example where the information recommendation system includes a server, a target food storage device, and a backup food storage device, and a user operates on the target food storage device, to explain the information recommendation method provided in this application. Figure 6 As shown, the information recommendation method may include:

[0076] Step 601: The target food storage device identifies the food stored therein.

[0077] Optionally, the food storage device can identify the food when the stored food changes, in order to determine the food currently stored in the device. For example, the food storage device can identify the food stored inside when the door changes from an open state to a closed state. Alternatively, the food storage device can identify the food stored and retrieved in real time when the user puts in and takes out food, and then combine this information with the food originally stored in the device to determine the food currently stored in the device.

[0078] In the first method of food identification, the food storage equipment can use image recognition to identify the food.

[0079] For example, the controller of a food storage device can, when a door switch detector determines that the door of the food storage device has changed from an open state to a closed state, control the light source in the storage room to turn on and control the image acquisition device in the storage room to acquire images of the food in the storage room. The controller can input the images acquired by the image acquisition device into a food recognition model to obtain a recognition result, and determine the type of food stored in the food storage device based on the recognition result. Alternatively, when a door switch detector determines that the door of the food storage device has changed from a closed state to an open state, the controller can control the image acquisition device to acquire an image of the opening of the storage room, and then recognize the image to determine the user's storage or retrieval action, and determine the type of food stored or retrieved by the user. When it is determined that the user is storing food in the storage room, the previously stored food and the newly stored food are jointly identified as the currently stored food in the storage room. When it is determined that the user is retrieving food from the storage room, the food that is not the food to be retrieved from the previously stored food is identified as the currently stored food in the storage room. Optionally, image recognition can determine not only the type of food but also other information about the food, such as its volume and storage location in the storage room.

[0080] In the second method of food identification, food storage equipment can use radio frequency identification (RFID) to identify food.

[0081] For example, please continue to refer to Figure 2 The food storage device may also include an electronic tag box 105, which is used to hold electronic tags (not shown in the figure), each electronic tag corresponding to one type of food. It should be noted that... Figure 2 The illustration shows the label box 105 installed on the surface of the door 102 near the opening K. Optionally, the label box can also be installed on the surface of the door 102 away from the opening K. Alternatively, the label box can be located at any other position on the housing 101 or the door 102, which is not limited in this embodiment.

[0082] When a user places a food item into the storage compartment of the food storage device, they can retrieve the corresponding electronic tag from the electronic tag box and affix it to the food item. The controller of the food storage device can determine the type of food item stored in the storage compartment based on the food item corresponding to the missing electronic tag in the tag box. When the user retrieves food from the storage compartment, they can remove the electronic tag from the food item and place it back into the tag box. The controller of the food storage device can then determine the type of food item retrieved from the storage compartment based on the food item corresponding to the newly added electronic tag in the tag box. Furthermore, the controller can combine this information with the food items already stored in the storage compartment to determine the food items currently stored in the storage compartment.

[0083] Optionally, the food storage device may also include an antenna, which can be wired to the controller. The controller can transmit radio frequency (RF) signals through the antenna, and the transmitted RF signals can cover a certain range around the antenna. When an electronic tag is within this range, it can receive the RF signals and, using the energy gained under the excitation of the RF signals, transmit information stored in the electronic tag, such as the tag's identifier, to the antenna. The controller can then receive the information transmitted by the electronic tag through the antenna to identify the food item corresponding to the electronic tag. Optionally, the antenna can be located in the tag box, such as at the bottom of the tag box, which is made of a material capable of shielding RF signals, such as metal. In this case, the RF signals transmitted by the antenna can only cover the space within the tag box, and only the electronic tags within the tag box can receive the RF signals transmitted by the antenna and transmit the information stored in the electronic tag to the antenna; the controller can only detect the electronic tags within the tag box. Optionally, the controller can also adjust the transmission power of the RF signals to ensure that the RF signals only cover the space within the tag box; in this case, the tag box can be made of any material.

[0084] Optionally, the food storage device may also include a reader that can be connected to an antenna. The reader transmits radio frequency signals via the antenna and receives information transmitted by electronic tags via the antenna. The reader can communicate with a controller, receiving information from the electronic tags and then transmitting that information back to the controller.

[0085] In another optional method for determining ingredients, the user can input their action on the display screen each time they store or retrieve ingredients from the storage compartment. They can also input the type of ingredients being stored or retrieved. The controller can then determine the ingredients currently stored in the storage compartment based on the user's input and the type of ingredients. Optionally, the user can also input other information such as the storage location, volume, and shelf life of the ingredients.

[0086] It should be noted that step 601 can be executed by the controller in the target food storage device.

[0087] Step 602: Obtain the identifier of the local area network to which the target food storage equipment is connected.

[0088] For example, the target food storage device may be connected to a local area network (LAN) and connect to a server through that LAN. The identifier of this LAN can be its external Internet Protocol (IP) address. The target food storage device can obtain the identifier of this LAN from its network connection information.

[0089] It should be noted that step 602 can be executed by the controller in the target food storage device.

[0090] Step 603: The target food storage device sends information about the food stored therein and the identifier of the local area network to which the target food storage device is connected to the server.

[0091] The information about the food ingredient may include its type. Optionally, the information may also include its shelf life, volume, and storage location in the storage room, etc., which are not limited in this embodiment. Optionally, the target food ingredient storage device may also send its identifier to the server when sending the information about the food ingredient it stores, so that the server can store the information about the food ingredient from the device perspective. Optionally, the target food ingredient storage device may also be logged into a target account, and the target food ingredient storage device may also send the target account to the server when sending the information about the food ingredient it stores, so that the server can store the information about the food ingredient from both the device and account perspectives.

[0092] The target food storage device can also send the identifier of the network it is connected to to the server, so that the server can store the identifier of the network to which the target food storage device is connected and determine the location of the target food storage device through the network identifier. For example, when the target food storage device sends information about the food it stores to the server, it can simultaneously send the identifier of the local area network to the server. This reduces the number of times the target food storage device interacts with the server, thereby reducing network overhead. For example, the target food storage device can send the identifier of the local area network it is connected to only when it first sends information about the food it stores to the server; or the target food storage device can send the identifier of its currently connected local area network every time it sends information about the food it stores to the server.

[0093] Optionally, the target food storage device may send the identifier of its connected local area network (LAN) to the server separately, without simultaneously sending information about the stored food. For example, the target food storage device may send the identifier of its currently connected LAN to the server when its connected LAN changes; or the target food storage device may periodically send the identifier of its currently connected LAN to the server. Each time the server receives the identifier of the LAN sent by the target food storage device, it can update the stored identifier of the LAN corresponding to the target food storage device.

[0094] It should be noted that step 603 can be executed by the controller in the target food storage device through the communication interface.

[0095] Step 604: The server stores information about the food stored in the target food storage device and the identifier of the local area network to which the target food storage device is connected.

[0096] The server can store the information of the ingredients sent by the target ingredient storage device, along with the identifier of the local area network, in the storage space corresponding to the target ingredient storage device. This storage space can be used specifically to store the information of the ingredients stored in the relevant information of the target ingredient storage device. Optionally, the server can also store the correspondence between the identifiers of each ingredient storage device, the identifier of the local area network connected to each ingredient storage device, and the information of the ingredients stored in each ingredient storage device in a table format in a certain storage space.

[0097] It should be noted that step 604 can be executed by the central processing unit in the server to store the required information in the server's memory.

[0098] It should be noted that this embodiment of the application uses food storage equipment to identify food, thereby determining the food stored in the equipment and sending the information of the food to the server. Optionally, the food storage equipment can also directly send images of the food to the server, whereby the server identifies the food based on the images, determines the food stored in the equipment, and directly stores the information of the food stored in the equipment. Optionally, the server can also send the identified food information to the food storage equipment for display and storage.

[0099] Optionally, Figure 7 This is a display interface diagram of a food storage device provided in an embodiment of this application. Figure 8 This is a display interface diagram of another food storage device provided in this application embodiment. Figure 9 This is a display interface diagram of a display screen for another food storage device provided in this application embodiment. For example, after closing the door of the food storage device, the user can operate on the display screen to trigger the display to show the food currently stored in the storage compartment. For instance, the display screen may display a food management button, which the user can click to trigger the display to show... Figure 7 The food storage management interface is shown. Optionally, the food storage equipment includes multiple compartments such as a refrigerator compartment, a variable temperature compartment, and a freezer compartment. The controller can determine the food stored in each compartment and control the display screen to show information about the food stored in each compartment in different areas of the food management interface. Figure 7As shown, the food management interface includes: a first area D1 corresponding to the refrigerator compartment, a second area D2 corresponding to the variable temperature compartment, and a third area D3 corresponding to the freezer compartment. Each area can display a representative image P1 for each type of food stored in the corresponding compartment, and the name of the food is displayed below the representative image P1 (e.g., ...). Figure 7 (Tomatoes in the middle).

[0100] Optionally, such as Figure 7 As shown, the ingredient management interface can also display multiple target controls. These target controls may include a recipe recommendation control J1, an add ingredient control J2, and a photo control J3. Users can trigger the controller to execute corresponding instructions by clicking the corresponding controls. For example, when a user clicks the add ingredient control J2, the controller can trigger the display screen to show a virtual keyboard. The user can use this virtual keyboard to input the ingredient type, and the controller can then store the ingredient type and control the display screen to show the representative image and name of that ingredient type in the corresponding area of ​​the ingredient management interface. Similarly, when a user clicks the photo control J3, the controller can control the image acquisition device to capture images of the ingredients in the storage room, recognize the captured images, and then control the display screen to show the images. Figure 8 The food ingredient recognition interface shown.

[0101] For example, image acquisition devices can be installed in each compartment of the storage room. Figure 8 As shown, the food identification interface can include images of food in each compartment acquired by the image acquisition component. For example, Image 1 is an image of food in the refrigerator compartment, Image 2 is an image of food in the variable temperature compartment, and Image 3 is an image of food in the freezer compartment. The food identification interface can also include the identification results of the food in each compartment. For example, the identification result for each food can be displayed as a representative image P2, or as the food name, or as a combination of a representative image and the food name. Optionally, each food identification result also has a corresponding deletion control J4. For example, the deletion control J4 can be displayed as an icon with a small circle with a horizontal bar in the upper right corner of the representative image P2. The user can click the deletion control J4 to delete the corresponding identification result. Optionally, the food identification interface can also include a re-identification control J5 and a one-click entry control J6. The user can click the re-identification control J5 to trigger the controller to re-identify the food stored in the refrigerator compartment. The user can click the one-click entry control J6 to trigger the controller to store and display the identified information of the food in each compartment. For example, the controller can control the display screen to show the information. Figure 9The image shows the ingredient entry display interface. This interface can include information about newly added ingredients in each storage compartment, such as a representative image and name for each ingredient. Thus, when the user triggers the display screen to show the ingredient management interface again, that interface will include the information of the newly entered ingredient, which is the same information displayed in the ingredient entry display interface.

[0102] Step 605: The spare food storage equipment identifies the food stored therein.

[0103] It should be noted that step 604 can refer to step 601, and will not be repeated in this embodiment.

[0104] Step 606: The backup food storage equipment obtains the identifier of the local area network it is connected to.

[0105] It should be noted that step 606 can refer to step 602, and will not be repeated in this embodiment.

[0106] Step 607: The backup food storage device sends information about the food stored within it and the identifier of the local area network to which the backup food storage device is connected to the server.

[0107] It should be noted that step 607 can refer to step 603, and will not be repeated in this embodiment. In this embodiment, the example is that the backup food storage device and the target food storage device are connected to the same local area network (LAN), and the LAN identifier sent by the backup food storage device to the server is the same as the LAN identifier sent by the target food storage device to the server.

[0108] Step 608: The server stores information about the ingredients stored in the backup ingredient storage device and the identifier of the local area network to which the backup ingredient storage device is connected.

[0109] It should be noted that step 608 can refer to step 604, and will not be repeated in this embodiment.

[0110] Step 609: The target ingredient storage device receives the dish recommendation instruction.

[0111] Optionally, the target ingredient storage device may have recipe software installed. When the recipe software is running, the display screen can show recommended dishes. When the target ingredient storage device detects a launch operation for the recipe software, it can confirm that it has received a dish recommendation instruction. For example, if a recipe application icon is displayed on the display screen of the ingredient storage device, clicking the recipe application icon by the user is equivalent to launching the recipe, and thus the ingredient storage device can receive a dish recommendation instruction. Optionally, when the user clicks... Figure 7When the recipe recommendation control J1 is activated in the ingredient management interface shown, the target ingredient storage device can also receive the recipe recommendation instruction. There are other ways to trigger the target ingredient storage device to receive the recipe recommendation instruction, which are not limited in this embodiment.

[0112] It should be noted that step 609 can be executed by the controller in the target food storage equipment.

[0113] Step 610: The target ingredient storage device receives the instruction to select the reference ingredient.

[0114] Optionally, after receiving a recipe recommendation instruction, the target ingredient storage device can instruct the user to select a reference ingredient, which can be an ingredient the user intends to use in preparing the dish. When the user selects a reference ingredient, the target ingredient storage device receives the selection instruction for that reference ingredient and can determine the reference ingredient based on that selection instruction. For example, the user can directly input the identifier of the reference ingredient on the display screen of the target ingredient storage device to trigger the target ingredient storage device to receive the selection instruction for the reference ingredient; or the display screen of the target ingredient storage device can also display multiple candidate ingredients, and the user can select a reference ingredient from these multiple candidate ingredients to trigger the target ingredient storage device to receive the selection instruction for the reference ingredient.

[0115] For example, Figure 10 This is a schematic diagram of the display interface of a display screen for another food storage device provided in this application embodiment. Figure 11 This is a schematic diagram of the display interface of a food storage device according to another embodiment of this application. Figure 12 This is a schematic diagram of the display interface of another food storage device provided in another embodiment of this application. When the user clicks... Figure 7 After the recipe recommendation control J1 appears in the ingredient management interface, the display screen of the target ingredient storage device can show... Figure 10 The prompt interface shown may include a message asking the user whether to select reference ingredients, as well as multiple selection controls. For example... Figure 10 As shown, the prompt message can be "Please confirm whether to select the desired ingredients". The multiple selection controls can include: "Enter your own" control, "Select existing ingredients" control, and "No need to select" control.

[0116] When the user clicks the "Enter Manually" control, the display screen of the target food storage device can show... Figure 11The information input interface shown allows users to input the identifier of an ingredient. In this embodiment, the identifier of the ingredient can be its name, such as "tomato" or "potato". The information input interface may include an input box 111 and a virtual keyboard 112. Users can input the identifier of a reference ingredient into the input box 111 by clicking the virtual key 112a in the virtual keyboard 112. The information input interface may also include a "confirm" control and a "delete" control, allowing users to confirm or modify the input ingredient identifier. When the target ingredient storage device detects that the "confirm" control has been triggered, it can confirm that it has received the selection instruction for the reference ingredient and determine the identifier of the ingredient in the current input box as the identifier of the reference ingredient. The reference ingredient can be any ingredient selected by the user, can be an ingredient stored in the target ingredient storage device, or can be an ingredient not stored in the target ingredient storage device; this embodiment does not limit the scope of the reference ingredient.

[0117] When the user clicks the "Select Existing Ingredients" control, the display screen of the target ingredient storage device can show... Figure 12 The ingredient selection interface shown allows users to select reference ingredients. This interface may include identifiers for all ingredients stored in the target ingredient storage device. The identifier can be at least one of the ingredient's name and image; this embodiment uses both name and image to identify an ingredient. The interface may also include a "Selection Complete" control to confirm the selected ingredients. Users can click on the area marked with an ingredient's identifier on the display screen. When the area is clicked, the ingredient is marked, and the background color of the area may change to indicate selection. Users can click the area again to cancel the selection, and the background color returns to normal. After marking the desired ingredients among the various ingredient identifiers displayed on the screen, users can click the "Selection Complete" control to trigger the target ingredient storage device to receive a selection instruction for reference ingredients, and all marked ingredients are confirmed as reference ingredients.

[0118] The above embodiments of this application take the example of the target ingredient storage device first receiving a dish recommendation instruction, and then selecting a reference ingredient based on the dish recommendation instruction. Optionally, the target ingredient storage device may also simultaneously receive both a selection instruction for a reference ingredient and a dish recommendation instruction. For example, when the display screen of the target ingredient storage device shows the identifiers of the stored ingredients, the user can operate on any ingredient identifier (such as a long press) to trigger the display screen to show function options for that ingredient. These function options may include options to recommend dishes prepared with that ingredient. When the user selects this option, the target ingredient storage device can receive both the dish recommendation instruction and the reference ingredient selection instruction, and then make a dish recommendation based on the reference ingredient.

[0119] It should be noted that step 610 can be executed by the controller in the target food storage equipment.

[0120] Step 611: The target ingredient storage device generates a dish recommendation request based on the dish recommendation instruction and the selection instruction. The dish recommendation request carries the identifier of the reference ingredient, the identifier of the target ingredient storage device, and the target account logged in on the target ingredient storage device.

[0121] After a user selects a reference ingredient, the target ingredient storage device can trigger a dish recommendation request. This request is used to request the server to recommend a dish. Alternatively, upon receiving the selection instruction for the reference ingredient, the target ingredient storage device can directly generate a dish recommendation request based on that selection instruction. Or, after receiving the selection instruction, the target ingredient storage device can also display a prompt asking the user whether they confirm the recommendation of a dish prepared using that reference ingredient, and only generate the dish recommendation request after receiving the user's confirmation.

[0122] In this embodiment of the application, when the user clicks... Figure 10 When the "No Selection Required" control is selected, the display screen of the target ingredient storage device can stop showing the information prompt interface and directly generate a dish recommendation request and send it to the server. At this time, the dish recommendation request can only carry the identifier of the target ingredient storage device and the target account logged in on the target ingredient storage device.

[0123] It should be noted that step 611 can be executed by the controller in the target food storage equipment.

[0124] Step 612: The target ingredient storage device sends a dish recommendation request to the server.

[0125] After generating a dish recommendation request, the target ingredient storage device can send the request to the server through the communication connection between the target ingredient storage device and the server. It should be noted that step 612 can be specifically executed by the controller in the target ingredient storage device controlling the communication interface.

[0126] Step 613: Based on the dish recommendation request, the server determines the information of the ingredients stored in the target ingredient storage device.

[0127] After receiving a dish recommendation request from the target ingredient storage device, the server can obtain the identifier of the target ingredient storage device carried in the request. Then, based on this identifier, it can retrieve the information of the ingredients stored in the target ingredient storage device from the information of ingredients stored in various ingredient storage devices on the server. It should be noted that step 613 can be specifically executed by the central processing unit within the server.

[0128] Step 614: Based on the dish recommendation request, the server identifies the backup food storage device as the auxiliary food storage device that meets the target conditions among the food storage devices connected to the server.

[0129] In this embodiment, the server can determine the auxiliary food storage device that meets the target conditions based on the identifier of the target food storage device carried in the dish recommendation request and the target account logged in on the target food storage device. The target conditions may include at least one of the following: storing login information of the target account logged in on the target food storage device, and the distance to the target food storage device being less than a distance threshold.

[0130] Optionally, the food storage device storing the login information of the target account can be a food storage device currently logged in with the target account. For example, the server can obtain the currently logged-in account on each connected food storage device, determine whether the account is the target account, and thus determine whether the food storage device stores the login information of the target account. Alternatively, the food storage device storing the login information of the target account can also be a food storage device that has historically logged in with the target account. For example, the server can obtain the historically logged-in accounts on each connected food storage device, determine whether the target account is included among them, and thus determine whether the food storage device stores the login information of the target account. For another example, when a food storage device sends information about stored food to the server, it can also send the account logged in on the food storage device to the server. The server can store the accounts sent by each food storage device. The server can query the stored historical accounts sent by a particular food storage device to determine whether the target account exists on that food storage device.

[0131] Optionally, each food storage device can send the identifier of its connected local area network (LAN) to the server. Since a LAN only covers a small area, all devices connected to that LAN are located within that area. If the distance between devices within that area is less than a distance threshold, then the distance between two devices connected to the same LAN is less than that distance threshold. In this embodiment, the server can determine whether the distance between each food storage device is less than the distance threshold by determining whether each food storage device is connected to the same LAN. This means that the distance between the food storage device connected to the target food storage device and the target food storage device is less than the distance threshold. It should be noted that since LAN connections require password verification, devices connected to the same LAN can be devices within the same household. Therefore, determining the food storage device whose distance to the target food storage device is less than the distance threshold through the LAN also simultaneously determines that the food storage device and the target food storage device belong to the same household. Alternatively, each food storage device can send its location to the server, and the server can determine the food storage device whose distance to the target food storage device is less than the distance threshold based on the location of each food storage device.

[0132] For example, if the target condition for the auxiliary food storage device includes storing login information for the target account, then the dish recommendation request sent by the target food storage device to the server needs to include the target account. The server can determine the first food storage device storing the target account's login information from among its connected food storage devices, and then determine the auxiliary food storage device from the determined first food storage device. If the target condition only includes storing the target account's login information, the server can directly determine the determined first food storage device as the auxiliary food storage device.

[0133] For example, the target conditions for auxiliary food storage equipment include: the distance to the target food storage equipment is less than a distance threshold. In this case, the target food storage equipment needs to send the identifier of the local area network it is connected to to the server. Based on this identifier, the server can determine the second food storage equipment connected to that local area network among the connected food storage equipment, and then determine the auxiliary food storage equipment from the determined second food storage equipment. If the target condition only includes the distance to the target food storage equipment being less than a distance threshold, the server can directly determine the determined second food storage equipment as the auxiliary food storage equipment.

[0134] In this embodiment, the target conditions met by the auxiliary food storage device include: storing login information of the target account logged in on the target food storage device, and the distance to the target food storage device being less than a distance threshold. The server can first determine the first food storage device, and then determine the first food storage device connected to the same local area network as the target food storage device as the auxiliary food storage device. Alternatively, the server can first determine the second food storage device, and then determine the second food storage device storing the login information of the target account as the auxiliary food storage device. For example, the server can determine the account logged in on the backup food storage device as the target account based on a received menu recommendation request. Then, the server can query the identifier of the local area network connected to the backup food storage device, determine that the identifier of the local area network connected to the backup food storage device is the same as the identifier of the local area network connected to the target food storage device, and thus determine that the backup food storage device is an auxiliary food storage device that meets the target conditions. In this embodiment, the auxiliary food storage device is a food storage device that the user is not currently interacting with, but can access the food stored within it. If a family has multiple refrigerators, and each refrigerator is logged into with the same account, and the user is currently operating on one refrigerator, that refrigerator is the target food storage device, while the other refrigerators are auxiliary food storage devices.

[0135] It should be noted that step 614 can be executed by the central processing unit in the server.

[0136] In this embodiment, the information sent by the target food storage device to the server can be related to the target conditions that the auxiliary food storage device needs to meet. The above embodiment of this application takes the target conditions simultaneously including: storing login information of the target account and the distance to the target food storage device being less than a distance threshold. Therefore, the target food storage device needs to send the identifier of the connected local area network and the target account to the server. For example, after receiving the dish recommendation instruction in step 609, the target food storage device needs to detect whether the target account is logged in on the target food storage device. After confirming that the target account is logged in, it then executes step 611 to generate a dish recommendation request carrying the target account and sends the dish recommendation request to the server. If the target conditions only include storing login information of the target account, then in step 604, the target food storage device may not need to send the identifier of the connected local area network to the server; if the target conditions only include the distance to the target food storage device being less than a distance threshold, then in step 611, the dish recommendation request generated by the target food storage device to the server may not carry the target account.

[0137] Step 615: The server obtains information about the ingredients stored in the auxiliary ingredient storage device.

[0138] After identifying the auxiliary food storage device, the server can retrieve the information of the food stored in the auxiliary food storage device from the information of the food stored in each of the various food storage devices stored on the server. For example, in step 614, the server can determine the identifier of the auxiliary food storage device, and then the server can query the information of the food corresponding to the identifier of the auxiliary food storage device from the information of the food corresponding to the identifier of each of the various food storage devices stored on the server.

[0139] It should be noted that step 615 can be executed by the central processing unit in the server.

[0140] Step 616: The server determines the recommended information for the dish based on the reference ingredients, the ingredients stored in the target ingredient storage device, and the ingredients stored in the auxiliary ingredient storage device.

[0141] The server can determine at least one dish that can be prepared using candidate ingredients. These candidate ingredients include reference ingredients, ingredients stored in the target ingredient storage device, and ingredients stored in the auxiliary ingredient storage device. The recommended information for this dish may include an identifier for the at least one dish. Optionally, the ingredients for preparing each of the at least one dish may include at least one reference ingredient, or the ingredients for preparing each dish may include at least all reference ingredients. The ingredients for preparing each dish may also include other ingredients stored in the target ingredient storage device or the auxiliary ingredient storage device, which are different from the reference ingredients. Optionally, the recommended information for this dish may also include identifiers for other dishes besides the at least one dish. For example, these other dishes may include dishes that are most popular with users, dishes that are easiest to prepare, dishes with low fat content, etc. The ingredients required for preparing these dishes may be unrelated to the ingredients stored in the ingredient storage devices, and this application embodiment does not limit this.

[0142] Optionally, the server can determine the at least one dish based on a recipe library, which may include the preparation methods of various dishes and the ingredients required for each dish. If the server determines that the candidate ingredients include all the ingredients required to prepare a certain dish from the multiple dishes, then the server can determine that the dish is one that can be prepared using the candidate ingredients. Optionally, the at least one dish may include all dishes from the multiple dishes in the recipe library that can be prepared using the candidate ingredients. Optionally, the recipe library may be stored on the server, or it may be obtained by the server from the Internet or other locations.

[0143] In an optional example, the recommended information for the dish may further include: identifiers of the ingredients used to prepare each of the at least one dish, and identifiers of the storage devices where each ingredient is located. When the storage devices display the recommended information for the dish, users can clearly know the storage location of each ingredient, facilitating accurate retrieval of the prepared dish, improving the intelligence of the dish recommendations, and enhancing the usability of the storage devices.

[0144] In another alternative example, the aforementioned at least one dish may use ingredients stored in the target ingredient storage device as the main ingredient and ingredients stored in the auxiliary ingredient storage device as auxiliary ingredients. For example, the server may determine, from all dishes that can be made using the aforementioned alternative ingredients, a dish that uses ingredients stored in the target ingredient storage device as the main ingredient and ingredients stored in the auxiliary ingredient storage device as auxiliary ingredients, and then use the identifier of this determined dish as the identifier of at least one dish included in the dish recommendation information.

[0145] In another alternative example, the recommended dish information includes an identifier for at least one dish that is related to the dish type. This dish type may be related to the time of consumption, and could include breakfast, lunch, dinner, late-night snacks, and other similar items. For instance, after receiving a dish recommendation request, the server can obtain dish types corresponding to multiple time periods and determine the target time period in which the dish recommendation request was received. For example, if the time period corresponding to breakfast is 6:00 to 9:00, and the server receives the dish recommendation request at 7:00, then the target time period can be determined to be 6:00 to 9:00, and the dish type corresponding to this target time period is breakfast. Then, based on the dish type corresponding to the target time period, the server can determine at least one dish of that type that can be prepared using alternative ingredients, thereby determining that the recommended dish information includes the identifier of that at least one dish.

[0146] It should be noted that step 616 can be executed by the central processing unit in the server.

[0147] The embodiments described above all assume that the user triggers a selection instruction from the target ingredient storage device, which then sends a recipe recommendation request to the server carrying the identifier of the reference ingredient. Optionally, if the user does not select a reference ingredient, the target ingredient storage device may display an identifier on its screen. Figure 10 The user clicks on the interface shown. Figure 10When the "No Selection Required" control is used, the dish recommendation request may not include the identifier of the reference ingredients. Thus, in step 616, the server can determine the recommended dish information based solely on the ingredients stored in the target ingredient storage device and the ingredients stored in the auxiliary ingredient storage device. The aforementioned alternative ingredients may only include those stored in the target ingredient storage device and the auxiliary ingredient storage device. The method for determining the recommended dish information in this case can refer to the method described above, and will not be repeated in this embodiment.

[0148] Step 617: The server sends the recommended recipes to the target ingredient storage device.

[0149] After determining the recommended information for a dish, the server can send that information to the target ingredient storage device via a communication connection. It should be noted that step 617 can be specifically executed by the network interface unit controlled by the central processing unit within the server.

[0150] Step 618: The target ingredient storage device displays the recommended information of the received dishes.

[0151] Once the target ingredient storage device receives the dish recommendation information sent by the server, it can display the recommendation information for that dish on the screen. Figure 13 This is a schematic diagram of the display interface of a food storage device according to another embodiment of this application. The target food storage device can display information based on received recipe recommendations. Figure 13 The information recommendation interface shown. Figure 13 As shown, the information recommendation interface displays recommendations for various dishes, such as pickled fish, Mapo tofu, and sliced ​​beef and tripe in chili sauce. These dishes can be determined based on the ingredients stored in the target ingredient storage device and auxiliary ingredient storage devices. Optionally, each dish can also be identified by a corresponding image. Alternatively, please continue to refer to... Figure 13 The information recommendation interface may also include other dish recommendations, such as spicy crayfish, spicy stir-fried clams, and steamed hairy crabs. These dishes may not be determined based on the ingredients stored in the target ingredient storage device or the auxiliary ingredient storage device.

[0152] Optionally, information about the ingredients used to prepare the dish may also be displayed around the label of each dish, such as the label of the ingredients and the label of the storage device where the ingredients are stored. Figure 13The information regarding the ingredients used in the preparation and the type of dish are not shown. Optionally, after receiving the recommended information for a dish, the target ingredient storage device can directly display the information about the ingredients used in the preparation. Alternatively, it can initially only display the dish's identifier from the recommended information, such as displaying... Figure 13 The interface shown will display the information about the ingredients used to prepare the dish when it receives a selection instruction for the label of a dish.

[0153] Optionally, the recommended information for dishes determined by the server may also include the recommendation priority of each dish. After receiving the recommended information, the target ingredient storage device can display information about various dishes based on the recommendation priority of each dish in the recommended information. Subsequent embodiments of this application will describe in detail the method by which the server determines the recommendation priority of dishes; this will not be repeated here.

[0154] Optionally, the information recommendation interface may also display at least one user tag corresponding to the target account. For example... Figure 13 The target account can correspond to multiple user tags, including "Dad," "Mom," and "Big Baby." The information recommendation interface can also display relevant information for each user tag, such as the user's taste preferences and other information, including their favorite dishes or dietary restrictions. Optionally, the server can also create personalized dishes tailored to each user tag's preferences based on their taste preferences and other information. The server-generated dish recommendation information can then include the user tag corresponding to each dish. When displaying dish recommendations, the target food storage device can display the information for each dish corresponding to that user tag in the information recommendation interface for that user tag. Optionally, users can click on different user tags displayed on the target food storage device to trigger changes in the displayed dish information.

[0155] Optionally, each account can also correspond to only one user tag. The information recommendation interface for the target food storage equipment can display the user tag corresponding to the currently logged-in target account, as well as the user tags corresponding to previously logged-in accounts. For example, Figure 13 The user tag "Dad" displayed can also be the user tag corresponding to the target account. Figure 13 The user tags "Mom" and "Dabao" displayed can also be user tags corresponding to two different historically logged-in accounts. Optionally, users can change the target account currently logged into the target food storage device by clicking on the different user tags displayed.

[0156] It should be noted that step 618 can be executed by the controller in the target food storage equipment, which controls the display screen.

[0157] It should be noted that the above embodiments of this application take the example of the target ingredient storage device sending a dish recommendation request to the server when it receives a dish recommendation instruction triggered by the user. Optionally, the target ingredient storage device can also send a dish recommendation request to the server at a set time, such as a set breakfast time, lunch time, or dinner time. In this way, when the user needs to dine, they can directly see the dish recommendation information displayed on the target ingredient storage device without having to trigger the recommendation by the target ingredient storage device itself, thus improving the convenience of dish recommendations and the ease of use of the ingredient storage device. Optionally, the target ingredient storage device can also periodically send a dish recommendation request to the server; this embodiment of the application does not limit this.

[0158] In the above embodiments of this application, the server determines auxiliary food storage devices from among the food storage devices connected to it in step 614. This ensures that the determined auxiliary food storage devices are in normal working order, and dishes recommended to users based on the ingredients stored in these devices can be prepared normally. This avoids situations where food storage devices were previously used but are now out of service, making it impossible to prepare dishes based on their original ingredients. This ensures the effectiveness and practicality of dish recommendations and guarantees a better user experience with the food storage devices. Optionally, the server may also determine auxiliary food storage devices not from among the connected food storage devices, but from among all food storage devices that can obtain food information. This embodiment of the application does not limit this approach.

[0159] In the above embodiments of this application, the example is provided where the backup food storage device and the target food storage device are connected to the same local area network and both are logged into the target account. Optionally, the backup food storage device may not be connected to the same local area network as the target food storage device, or may not be logged into the target account. In this case, the server can determine the recommended dishes based solely on the ingredients stored in the target food storage device. When interacting with the user, the backup food storage device in this application embodiment can also act as the target food storage device, executing the same method as the target food storage device described above. Further details are omitted in this application embodiment.

[0160] In summary, the information recommendation method provided in this application embodiment allows the target food storage device to both store food ingredients and recommend dishes. The dishes recommended by the target food storage device to the user are determined based on the food ingredients stored in the target food storage device and those stored in auxiliary food storage devices. This allows for the recommendation of suitable dishes to the user based on the food ingredients available from multiple food storage devices, ensuring a relatively rich selection of dishes recommended by the target food storage device. Therefore, the target food storage device offers a wide range of functions and high flexibility in use.

[0161] Figure 14 This is a flowchart illustrating yet another information recommendation method provided in an embodiment of this application. The information recommendation system can execute... Figure 14 The method shown determines the recommendation priority of dishes, including the recommended information, and then enables the target ingredient storage device to display the recommended information based on the recommendation priority. For example... Figure 14 As shown, the method may include:

[0162] Step S1: When the target ingredient storage device displays the dishes, it receives a marking instruction for the first dish to be displayed.

[0163] For example, when the recipe software installed in the target ingredient storage device is running, the display screen can show multiple dishes, such as... Figure 13 The interface shown allows users to mark displayed dishes. When a user performs a specific action (such as a long press) on a dish, various control options will appear on the screen. The user can then click on the corresponding control to trigger the controller to perform the appropriate action. Figure 13 As shown, the various operation controls may include: a favorite control, a like control, a forward control, a save control, and a watch control, etc. Optionally, other operation controls may also be provided, which is not limited in this embodiment. Optionally, the user's click on these operation controls can all be a marking operation, or the user's click on certain specific operation controls can be a marking operation, such as the specific operation controls including: a favorite control and a like control. When the food storage device detects a marking operation for a certain dish (such as the first dish), the food storage device can determine that it has received a marking instruction for the first dish.

[0164] It should be noted that the above embodiments of this application take the startup of the recipe software to trigger the display of the recipe on the screen as an example. Optionally, at any time when the recipe is displayed on the screen of the food storage device, the user can mark the recipe. For example, when the user searches for a recipe on a webpage displayed on the screen, the user can also mark the recipe, or the search operation for the recipe can be directly defined as the marking operation for the recipe.

[0165] Step S2: The target ingredient storage device sends a tagging request for the first dish to the server based on the tagging instruction. The tagging request carries the target account.

[0166] When the target ingredient storage device receives the marking instruction for the first dish, it can send a marking request for the first dish carrying the target account to the server, so that the server can store the information of the first dish from the account perspective.

[0167] Step S3: Based on the tagging request of the first dish, the server determines the first dish as the reference dish corresponding to the target account.

[0168] In this embodiment, the reference dishes corresponding to the target account include dishes marked by the user of the target account, that is, dishes preferred by the user of the target account. The reference dishes corresponding to the target account can be used to reflect the personal preferences of the user of the target account. Optionally, when the server receives a marking request for a first dish, and the marking request carries the target account, it can store the information of the first dish in the storage space corresponding to the target account. This storage space can be used to specifically store the information of the reference dishes corresponding to the target account. It should be noted that the target account can correspond to multiple reference dishes. After the server receives a marking request for each dish, it can determine that dish as a newly added reference dish, without changing other reference dishes corresponding to the target account.

[0169] Step S4: After receiving the dish recommendation instruction, the target ingredient storage device sends a dish recommendation request to the server. The dish recommendation request carries the identifier of the target ingredient storage device and the target account.

[0170] After receiving a dish recommendation instruction, the target ingredient storage device can send a dish recommendation request to the server. This request can carry the identifier of the target ingredient storage device and the target account logged in on the device, so that the server can determine the recommended dish based on the device's identifier and the account.

[0171] It should be noted that the dish recommendation request in step S4 can be combined with... Figure 6 The same applies to the dish recommendation request. Step S4 can refer to the relevant content of steps 609 to 612 above, and will not be repeated in this embodiment.

[0172] Step S5: Based on the dish recommendation request, the server determines the ingredients stored in the target ingredient storage device, the ingredients stored in the auxiliary ingredient storage device, and the reference dish corresponding to the target account.

[0173] For example, after receiving a dish recommendation request, the server can retrieve the reference dish corresponding to the target account from the storage space corresponding to the target account, based on the target account carried in the request. The method by which the server determines the ingredients stored in the target ingredient storage device and the ingredients stored in the auxiliary ingredient storage device can be found in the relevant descriptions of steps 613 to 615 above, and will not be repeated in this embodiment.

[0174] Step S6: The server determines at least one dish that can be made using the ingredients stored in the target ingredient storage device and the ingredients stored in the auxiliary ingredient storage device.

[0175] It should be noted that step S6 can refer to the relevant description in step 616 above, and will not be repeated in this embodiment.

[0176] Step S7: The server determines the recommendation priority of each dish based on the similarity between each dish in the at least one dish and the reference dish corresponding to the target account.

[0177] After determining at least one dish that can be prepared using ingredients stored in the target ingredient storage device and ingredients stored in the auxiliary ingredient storage device, the server can determine the recommendation priority of each dish within that at least one dish based on the reference dishes corresponding to the target account. Since the reference dishes for the target account reflect the user's preferences, determining the recommendation priority based on these reference dishes, and then recommending dishes to the user according to this priority, ensures that the recommended dishes better match the user's preferences, thus improving the accuracy of dish recommendations.

[0178] Optionally, the recommendation priority of each dish is positively correlated with its similarity to reference dishes, such as the sum of the similarities between each dish and all reference dishes. For example, the recommendation priority of each dish can be equal to the sum of its similarities to all reference dishes. Optionally, the similarity between any two dishes can include similarity in taste and overlap in the ingredients used in their preparation.

[0179] For ease of distinction, each of the at least one type of dish will be referred to as a recommended dish below. For example, the server can compare the flavor of each recommended dish with the flavor of each reference dish to determine the similarity between their flavors. The server can also compare the ingredients used in each recommended dish with those used in each reference dish to determine the overlap between their ingredients. Furthermore, the server can determine the similarity between a recommended dish and a reference dish as the sum of their flavor similarity and the overlap of their ingredients.

[0180] Optionally, the similarity of flavors and the overlap of ingredients used can each be assigned a weight. The similarity between the two dishes can be calculated by multiplying the flavor similarity by its corresponding weight and adding the product of the overlap of ingredients used to its corresponding weight. For example, the weight of flavor similarity may be lower or higher than the weight of ingredient similarity. Optionally, different reference dishes can also be assigned weights. After determining the similarity of each reference dish for a recommended dish, the products of the similarities of each reference dish and its weight can be added together to obtain the final recommendation priority of the recommended dish.

[0181] Step S8: Determine the recommended information for the dish. The recommended information for the dish includes: the identifier of the at least one dish and the recommendation priority of the at least one dish.

[0182] After determining the at least one recommended dish and the recommendation priority of each recommended dish, the server can determine the recommended information for the dish corresponding to the target ingredient storage device. This recommended information includes: the identifier of the at least one recommended dish and the recommendation priority of each of the at least one recommended dishes. For example, the identifier of each recommended dish may include a representative image and name of that recommended dish.

[0183] Step S9: Send the recommended information of the selected dish to the target ingredient storage device.

[0184] Step S10: The target ingredient storage device displays the recommendation information of the dish according to the recommendation priority of the at least one dish in the received dish recommendation information.

[0185] Because recommended dishes with higher priority are more similar to the user's preferred dishes and better match the user's tastes, their information can be displayed in a more prominent position on the screen. This allows users to quickly notice the recommended dishes and avoids the frustration of not finding a satisfactory dish after viewing multiple options, thus improving the user experience. For example, since users typically view content on the screen from left to right and from top to bottom, the target ingredient storage device can display the recommended dishes with higher priority in the received dish recommendations at a higher and more left-hand position on the screen, making it easier for users to notice them and find a dish that suits their preferences more quickly.

[0186] Optionally, the display position of recommended dishes with higher priority can be set by the user. For example, if a user prefers to start viewing the content displayed on the screen from the center, the user can set the central area of ​​the screen to display recommended dishes with higher priority. Then, the food storage device can display recommended dishes with higher priority in the central area of ​​the screen based on the received dish recommendation information.

[0187] Optionally, the server may send the recipe for each dish to the target ingredient storage device, which may also include the recipe for that dish. The user can then interact with each dish displayed on the screen to trigger the display of that dish's recipe. Optionally, when the target ingredient storage device displays recommended dishes based on the received recipe information, the user may also mark the displayed recommended dishes. This allows the ingredient storage device to determine that the recommended dish is a target dish and confirm that it has received the marking instruction for the recommended dish, and subsequently send a marking request for the recommended dish to the server. Please refer to steps S1 to S3 for details; these will not be repeated in this embodiment.

[0188] It should be noted that the server can determine the recommended dishes based on the ingredients stored in the food storage device and the preference information corresponding to the target account. The above embodiments of this application illustrate this by using the preference information reflected in the user's historically marked reference dishes, and then determining the recommendation priority of dishes based on the similarity between the dishes and the reference dishes. Optionally, this preference information can also be reflected through other information input by the user, such as the user directly inputting their taste and ingredient preferences, such as liking sweet flavors or liking tomatoes; the server can then determine the recommendation priority of dishes based on this other information. Alternatively, the server can also infer the user's taste and ingredient preferences based on the user's historically marked reference dishes, and then determine the recommendation priority of dishes based on these taste and ingredient preferences.

[0189] In this embodiment, the at least one dish in the recommended dish information received by the food storage device may include all or some dishes that can be made using the ingredients stored in the food storage device; this embodiment does not impose any limitations. For example, a user can input information such as unacceptable flavors and ingredients via a display screen. The target food storage device can send this information and the target account to the server. When the server receives a dish recommendation request carrying the target account, the recommended dishes may not include dishes made with the specified ingredients or dishes with the specified flavor.

[0190] It should be noted that the above embodiments are all explained using the example of only one target account logged into the target food storage device. Optionally, multiple target accounts can be logged into the target food storage device, such as a first target account and a second target account. The server can determine the recommended information for the dish and the account to be carried in the tagging request based on the currently selected target account among the multiple target accounts logged into the target food storage device. If the currently selected target account is the first target account, the server determines the recommended information for the dish based on the reference dish corresponding to the first target account. If the currently selected target account is the second target account, the server determines the recommended information for the dish based on the reference dish corresponding to the second target account. When a dish is tagged on the page corresponding to the first target account, the generated tagging request carries the first target account. When a dish is tagged on the page corresponding to the second target account, the generated tagging request carries the second target account. For example, please continue to refer to... Figure 13 The three user tags displayed on the target ingredient storage device can each correspond to one of the three target accounts logged in on the target ingredient storage device. The currently selected target account can be the target account corresponding to the user tag "Dad". When the user selects different target accounts, the recommended dishes displayed on the screen can be different.

[0191] It should be noted that if a target account corresponds to multiple user tags, the target account in the above steps can be replaced by the various user tags corresponding to the target account. For example, when the target food storage device receives a tagging instruction for the first dish after selecting a target tag among the multiple user tags, the tagging request for the first dish sent to the server in step S2 can carry the target account and the target tag. In step S3, based on the tagging request, the server can determine the first dish as the reference dish corresponding to the target tag. In step S4, the dish recommendation request sent by the target food storage device to the server can carry the various user tags corresponding to the target account. In step S7, the server can determine the similarity between each dish and the reference dish corresponding to each user tag, thereby determining the recommendation priority for each dish under each user tag. In step S8, the recommendation information for the dishes determined by the server can include the identifier of at least one dish and the recommendation priority of that at least one dish under each user tag. In step S10, when a user tag is selected, the target ingredient storage device can display the identifier of the dish corresponding to that user tag based on the recommendation priority of the dish under that user tag.

[0192] In this embodiment, the steps performed by the food storage device can be executed by its controller, and the steps performed by the server can be executed by its processing unit. The display steps performed by the food storage device can be implemented by the controller of the food storage device controlling the display screen. The steps performed by the food storage device to interact with the server can be implemented by the controller in the food storage device through a communication interface. The steps performed by the server to interact with the food storage device can be implemented by the processing unit in the server through a network interface unit.

[0193] Figure 15 This is a flowchart illustrating an information recommendation method provided in an embodiment of this application. This method can be used for... Figure 1 Any of the multiple food storage devices shown, or Figure 2 The food storage device 10 shown may include the following method:

[0194] Step 401A: After receiving the dish recommendation instruction, send a dish recommendation request to the server. The dish recommendation request carries the identifier of the food storage device and the target account logged in on the food storage device.

[0195] Step 402A: Receive the dish recommendation information sent by the server. The dish recommendation information is determined by the server based on the dish recommendation request, the ingredients stored in the ingredient storage device, and the reference dishes corresponding to the target account.

[0196] Step 403A: Display recommended information for the dishes.

[0197] In summary, in the information recommendation method provided in this application embodiment, the dishes recommended by the food storage device to the user are determined based on the food stored in the food storage device and the reference dishes corresponding to the target account logged into the food storage device. If the reference dishes corresponding to the target account are different, the dishes recommended by the food storage device may also be different, thus improving the flexibility of the food storage device in recommending dishes.

[0198] Figure 16 This is a flowchart of another information recommendation method provided in an embodiment of this application. This method can be used for... Figure 1 or Figure 3 The method may include: (as shown in the server 20)

[0199] Step 501A: Receive a dish recommendation request sent by the food storage device. The dish recommendation request carries the identifier of the food storage device and the target account logged in on the food storage device.

[0200] Step 502A: Determine the ingredients stored in the ingredient storage device and the reference dishes corresponding to the target account based on the dish recommendation request.

[0201] Step 503A: Determine the recommended information for the dishes based on the ingredients stored in the food storage device and the reference dishes corresponding to the target account.

[0202] Step 504A: Send the recommended recipes to the food storage device.

[0203] In summary, in the information recommendation method provided in this application embodiment, the server can determine the recommended information of a dish based on the ingredients stored in the food storage device and the reference dishes corresponding to the target account logged in on the food storage device, and then send the recommended information of the dish to the food storage device for the food storage device to display. If the reference dishes corresponding to the target account are different, the determined recommended information of the dish will also be different, and thus the food storage device will recommend different dishes to the user based on the recommended information, thereby improving the flexibility of the food storage device in recommending dishes.

[0204] Figure 17 This is a flowchart of another information recommendation method provided in the embodiments of this application. This method can be used for Figure 1 The information recommendation system shown is illustrated below. The following embodiments of this application use an example where the information recommendation system includes a server, a first food storage device, and a second food storage device, and both the first and second food storage devices are logged into with a target account, to explain the information recommendation method provided in this application. Figure 17 As shown, the information recommendation method may include:

[0205] Step 601A: The first food storage device identifies the food stored therein.

[0206] Optionally, the food storage device can identify the food when the stored food changes, in order to determine the food currently stored in the food storage device. For example, the food storage device can identify the food stored inside when the door changes from an open state to a closed state. Alternatively, the food storage device can identify the food being stored and retrieved in real time when the user stores and retrieves food, and then combine this information with the food originally stored in the food storage device to determine the food currently stored in the food storage device.

[0207] In the first method of food identification, the food storage device can use image recognition to identify the food.

[0208] For example, the controller of a food storage device can, when a door switch detector determines that the door of the food storage device has changed from an open state to a closed state, control the light source in the storage room to turn on and control the image acquisition device in the storage room to acquire images of the food in the storage room. The controller can input the images acquired by the image acquisition device into a food recognition model to obtain a recognition result, and determine the type of food stored in the food storage device based on the recognition result. Alternatively, when the door switch detector determines that the door of the food storage device has changed from a closed state to an open state, the controller can control the image acquisition device to acquire an image of the opening of the storage room, and then recognize the image to determine the user's access action and the type of food stored or retrieved by the user. When it is determined that the user is storing food in the storage room, the previously stored food and the newly stored food are jointly identified as the food currently stored in the storage room. When it is determined that the user is retrieving food from the storage room, the food that is not the food to be retrieved from the previously stored food is identified as the food currently stored in the storage room. Optionally, image recognition can determine not only the type of food but also other information about the food, such as its volume and storage location in the storage room.

[0209] In the second method of food identification, food storage devices can use radio frequency identification (RFID) to identify food.

[0210] For example, please continue to refer to Figure 2 The food storage device may also include an electronic tag box 105, which can be used to hold electronic tags (not shown in the figure), each electronic tag corresponding to one type of food. It should be noted that... Figure 2 The illustration shows the label box 105 installed on the surface of the door 102 near the opening K. Optionally, the label box can also be installed on the surface of the door 102 away from the opening K. Alternatively, the label box can be located at any other position on the housing 101 or the door 102, which is not limited in this embodiment.

[0211] When a user places an ingredient into the storage compartment of the food storage device, they can retrieve the corresponding electronic tag from the electronic tag box and affix it to the ingredient. The controller of the food storage device can determine the type of ingredient stored in the storage compartment based on the ingredient corresponding to the missing electronic tag in the tag box. When the user retrieves an ingredient from the storage compartment, they can remove the electronic tag from the ingredient and place it back into the tag box. The controller can then determine the type of ingredient retrieved from the storage compartment based on the ingredient corresponding to the newly added electronic tag in the tag box. Furthermore, the controller can combine this information with the ingredients already stored in the storage compartment to determine the currently stored ingredients.

[0212] Optionally, the food storage device may also include an antenna, which can be wired to the controller. The controller can transmit radio frequency (RF) signals through the antenna, and the transmitted RF signals can cover a certain range around the antenna. When an electronic tag is within this range, it can receive the RF signals and, using the energy gained under the excitation of the RF signals, transmit information stored in the electronic tag, such as the tag's identifier, to the antenna. The controller can then receive the information transmitted by the electronic tag through the antenna to identify the food item corresponding to the electronic tag. Optionally, the antenna can be located in the tag box, such as at the bottom of the tag box, which is made of a material capable of shielding RF signals, such as metal. In this case, the RF signals transmitted by the antenna can only cover the space within the tag box, and only the electronic tags within the tag box can receive the RF signals transmitted by the antenna and transmit the information stored in the electronic tag to the antenna; the controller can only detect the electronic tags within the tag box. Optionally, the controller can also adjust the transmission power of the RF signals to ensure that the RF signals only cover the space within the tag box; in this case, the tag box can be made of any material.

[0213] Optionally, the food storage device may also include a reader that can be connected to an antenna. The reader transmits radio frequency signals via the antenna and receives information transmitted by electronic tags via the antenna. The reader can communicate with a controller, receiving information from the electronic tags and then transmitting that information back to the controller.

[0214] In another optional method for determining ingredients, the user can input their action on the display screen each time they store or retrieve ingredients from the storage compartment. They can also input the type of ingredients being stored or retrieved. The controller can then determine the ingredients currently stored in the storage compartment based on the user's input and the type of ingredients. Optionally, the user can also input other information such as the storage location, volume, and shelf life of the ingredients.

[0215] Step 602A: The first food storage device sends information about the food stored therein to the server.

[0216] The information about the food ingredient may include its type. Optionally, the information may also include its shelf life, volume, and storage location in the storage room, etc., which are not limited in this embodiment. Optionally, when sending the information about the food ingredient stored therein, the food storage device may also send its identifier to the server, so that the server can store the information about the food ingredient from the device perspective.

[0217] Step 603A: The server stores the information of the ingredients stored in the first ingredient storage device.

[0218] The server can store the information of the ingredients sent by the first ingredient storage device into the storage space corresponding to the first ingredient storage device. This storage space can be used specifically to store the information of the ingredients stored in the first ingredient storage device.

[0219] It should be noted that this embodiment of the application uses a food storage device to identify food ingredients, thereby determining the food ingredients stored in the food storage device, and then sending the information of the food ingredients to the server. Optionally, the food storage device can also directly send the captured image of the food ingredients to the server, whereby the server performs food identification based on the image, determines the food ingredients stored in the food storage device, and then directly stores the information of the food ingredients stored in the food storage device. Optionally, the server can also send the identified food ingredient information to the food storage device for display and storage.

[0220] Step 604A: The second food storage device identifies the food stored therein.

[0221] It should be noted that step 604 can refer to step 601, and will not be repeated in this embodiment.

[0222] Step 605A: The second food storage device sends information about the food stored therein to the server.

[0223] It should be noted that step 605 can refer to step 602, and will not be repeated in this embodiment.

[0224] Step 606A: The server stores the information of the ingredients stored in the second ingredient storage device.

[0225] It should be noted that step 606 can refer to step 603, and will not be repeated in this embodiment.

[0226] Step 607A: When the first food storage device displays the dish, it receives a marking instruction for the first dish to be displayed.

[0227] Optionally, the food storage device may have recipe software installed. When the recipe software is running, the display screen can show various dishes, and the user can mark the displayed dishes. If the user performs a specific operation (such as long-pressing) on ​​a displayed dish, it will trigger the display screen to show various operation controls. The user can click the corresponding operation control to trigger the controller to perform the corresponding operation. These operation controls may include: favorite control, like control, forward control, save control, and watch control, etc. Optionally, other operation controls may also be set; this application embodiment does not limit this. Optionally, the user's clicking of these operation controls can all be marking operations, or the user's clicking of certain specific operation controls can be marking operations, such as the favorite control and like control. When the food storage device detects a marking operation for a dish (such as the first dish), the food storage device can determine that it has received a marking instruction for the first dish.

[0228] It should be noted that the above embodiments of this application take the startup of the recipe software to trigger the display of the recipe on the screen as an example. Optionally, at any time when the recipe is displayed on the screen of the food storage device, the user can mark the recipe. For example, when the user searches for a recipe on a webpage displayed on the screen, the user can also mark the recipe, or the search operation for the recipe can be directly defined as the marking operation for the recipe.

[0229] Step 608A: The first food storage device sends a tagging request for the first dish to the server based on the tagging instruction. The tagging request carries the target account.

[0230] When the food storage device receives the tagging instruction for the first dish, it can send a tagging request for the first dish carrying the target account to the server, so that the server can store the information of the first dish from the account perspective.

[0231] Step 609A: Based on the tagging request of the first dish, the server identifies the first dish as the reference dish corresponding to the target account.

[0232] In this embodiment, the reference dishes corresponding to the target account include dishes marked by the user of the target account, that is, dishes preferred by the user of the target account. The reference dishes corresponding to the target account can be used to reflect the personal preferences of the user of the target account. Optionally, when the server receives a marking request for a first dish, and the marking request carries the target account, it can store the information of the first dish in the storage space corresponding to the target account. This storage space can be used to specifically store the information of the reference dishes corresponding to the target account. It should be noted that the target account can correspond to multiple reference dishes. After the server receives a marking request for each dish, it can determine that dish as a newly added reference dish, without changing other reference dishes corresponding to the target account.

[0233] Step 610A: When the second food storage device displays the dish, it receives a marking instruction for the displayed second dish.

[0234] It should be noted that step 610 can refer to step 607, and will not be repeated in this embodiment.

[0235] Step 611A: The second food storage device sends a tagging request for the second dish to the server based on the tagging instruction. The tagging request carries the target account.

[0236] It should be noted that step 611 can refer to step 608, and will not be repeated in this embodiment.

[0237] Step 612A: The server updates the reference dishes corresponding to the target account based on the tag request of the second dish. The reference dishes corresponding to the target account include the first dish and the second dish.

[0238] It should be noted that step 612A can refer to step 609A. The server can also determine the second dish as the reference dish corresponding to the target account. Since the reference dishes corresponding to the target account also include the first dish, the reference dishes corresponding to the target account can include both the first and second dishes at this time. This is equivalent to the server updating the reference dishes corresponding to the target account. In the embodiments of this application, both the first dish and the second dish are target dishes, which refer to the marked dishes displayed on the food storage device.

[0239] This embodiment of the application takes the execution of step 612A after step 609A as an example. After step 612A, the reference dishes corresponding to the target account determined by the server include the first dish and the second dish. Optionally, if before step 609A, that is, before the server receives the marking request for the first dish, if it also receives marking requests for other dishes, and these marking requests also carry the target account, then after step 609A, all reference dishes corresponding to the target account can include the other dishes and the first dish. After step 611A, the reference dishes corresponding to the target account include the first dish, the second dish, and the other dishes.

[0240] Step 613A: After receiving the dish recommendation instruction, the first ingredient storage device sends a dish recommendation request to the server. The dish recommendation request carries the identifier of the first ingredient storage device and the target account.

[0241] Optionally, the food storage device may have recipe software installed. When the recipe software is running, the display screen may show recommended dishes. When a startup operation for the recipe software is detected, the device can confirm that a dish recommendation instruction has been received. For example, the display screen of the food storage device may show a recipe application icon. When the user clicks the recipe application icon, it initiates a startup operation for that recipe, and the food storage device can then receive a dish recommendation instruction. Optionally, the food storage device can also receive a dish recommendation instruction when the user clicks the recipe recommendation control J1 in the food management interface. There may be other ways to trigger the food storage device to receive a dish recommendation instruction, which are not limited in this embodiment.

[0242] After receiving a dish recommendation instruction, the food storage device can send a dish recommendation request to the server. This request can carry the identifier of the food storage device and the target account logged in on the food storage device, so that the server can determine the recommended dish based on the food storage device and the target account.

[0243] Step 614A: Based on the dish recommendation request, the server determines the ingredients stored in the first ingredient storage device and the reference dish corresponding to the target account.

[0244] For example, after receiving a recipe recommendation request, the server can retrieve ingredient information from the storage space corresponding to the first ingredient storage device based on the identifier of the first ingredient storage device carried in the request, thereby determining the ingredients stored in the first ingredient storage device. It can also retrieve reference recipes corresponding to the target account from the storage space corresponding to the target account, based on the target account carried in the recipe recommendation request.

[0245] Step 615A: The server determines at least one dish that can be made using the ingredients stored in the first ingredient storage device.

[0246] Optionally, the server can determine the at least one dish based on a recipe library, which may include the preparation methods of various dishes and the ingredients required for each dish. If the server determines that the ingredients stored in the first ingredient storage device include all the ingredients required to prepare a certain dish among the various dishes, then the server can determine that the dish is one that can be prepared using the ingredients stored in the first ingredient storage device. Optionally, the at least one dish may include all dishes among the various dishes in the recipe library that can be prepared using the ingredients stored in the first ingredient storage device. Optionally, the recipe library may be stored on the server, or it may be obtained by the server from the Internet or other locations.

[0247] Step 616A: The server determines the recommendation priority of each dish based on the similarity between each dish in the at least one dish and the reference dish corresponding to the target account.

[0248] After determining that at least one dish can be made using the ingredients stored in the first ingredient storage device, the server can determine the recommendation priority of each dish within that at least one dish based on the reference dishes corresponding to the target account. Since the reference dishes corresponding to the target account reflect the user's preferences, determining the recommendation priority of dishes based on these reference dishes, and then recommending dishes to the user according to these priority levels, can ensure that the recommended dishes better match the user's preferences and improve the accuracy of dish recommendations.

[0249] Optionally, the recommendation priority of each dish is positively correlated with its similarity to reference dishes, such as the sum of the similarities between each dish and all reference dishes. For example, the recommendation priority of each dish can be equal to the sum of its similarities to all reference dishes. Optionally, the similarity between any two dishes can include similarity in taste and overlap in the ingredients used in their preparation.

[0250] For ease of distinction, each of the at least one type of dish will be referred to as a recommended dish below. For example, the server can compare the flavor of each recommended dish with the flavor of each reference dish to determine the similarity between their flavors. The server can also compare the ingredients used in each recommended dish with those used in each reference dish to determine the overlap between their ingredients. Furthermore, the server can determine the similarity between a recommended dish and a reference dish as the sum of their flavor similarity and the overlap of their ingredients.

[0251] Optionally, the similarity of flavors and the overlap of ingredients used can each be assigned a weight. The similarity between the two dishes can be calculated by multiplying the flavor similarity by its corresponding weight and adding the product of the overlap of ingredients used to its corresponding weight. For example, the weight of flavor similarity may be lower or higher than the weight of ingredient similarity. Optionally, different reference dishes can also be assigned weights. After determining the similarity of each reference dish for a recommended dish, the products of the similarities of each reference dish and its weight can be added together to obtain the final recommendation priority of the recommended dish.

[0252] Step 617A: Determine the recommended information for the dish. The recommended information for the dish includes: the at least one dish and the recommendation priority of the at least one dish.

[0253] After determining the at least one recommended dish and the recommendation priority of each recommended dish, the server can determine the dish recommendation information corresponding to the first ingredient storage device. The dish recommendation information includes: the identifier of the at least one recommended dish and the recommendation priority of each recommended dish among the at least one recommended dishes. For example, the identifier of each recommended dish may include a representative image and name of that recommended dish.

[0254] Step 618A: Send the recommended information of the selected dishes to the first food storage device.

[0255] Step 619A: The first food storage device displays the at least one dish according to the recommendation priority of the at least one dish in the received dish recommendation information.

[0256] Because recommended dishes with higher priority are more similar to the user's preferred dishes and better match the user's tastes, their information can be displayed in a more prominent position on the screen. This allows users to quickly notice the recommended dishes and avoid the frustration of not finding a satisfactory dish after viewing multiple options, thus improving the user experience. For example, since users typically view content on the screen from left to right and from top to bottom, the food storage device can display the recommended dishes with higher priority in the received dish recommendations at a higher and lefter position on the screen, making them easier for users to notice and find a dish that suits their preferences more quickly.

[0257] Optionally, the display position of recommended dishes with higher priority can be set by the user. For example, if a user prefers to start viewing the content displayed on the screen from the center, the user can set the central area of ​​the screen to display recommended dishes with higher priority. Then, the food storage device can display recommended dishes with higher priority in the central area of ​​the screen based on the received dish recommendation information.

[0258] Optionally, the server may send the recipe for each dish to the food storage device as a recommendation. Users can interact with each dish displayed on the screen to trigger the display of that dish's recipe. Alternatively, the recommendation information may also include other dishes besides the at least one mentioned above. These other dishes could include the most popular dishes, the easiest to prepare, or dishes with low fat content. The ingredients required for these dishes may be unrelated to those stored in the food storage device.

[0259] Optionally, when the food storage device displays recommended dishes based on the received dish recommendation information, the user also marks the displayed recommended dishes. The food storage device can then determine that the recommended dish is a target dish and confirm that it has received the marking instruction for the recommended dish, and can then send a marking request for the recommended dish to the server. Please refer to steps 607A to 609A for details; this embodiment will not repeat them here.

[0260] It should be noted that the server can determine the recommended dishes based on the preference information of the ingredients stored in the ingredient storage device and the target account. The above embodiments of this application illustrate this by using the preference information reflected in the user's historically marked reference dishes, and then determining the recommendation priority of dishes based on the similarity between the dishes and the reference dishes. Optionally, the preference information can also be reflected through other information input by the user, such as the user directly inputting their taste and ingredient preferences, such as liking sweet flavors or liking tomatoes; the server can then determine the recommendation priority of dishes based on this other information. Alternatively, the server can also infer the user's taste and ingredient preferences based on the user's historically marked reference dishes, and then determine the recommendation priority of dishes based on these taste and ingredient preferences.

[0261] In this embodiment, the at least one dish in the recommended dish information received by the food storage device may include all or some dishes that can be made using the ingredients stored in the food storage device; this embodiment does not impose any limitations. For example, a user can input information such as unacceptable flavors and ingredients via a display screen. The food storage device can send this information and the target account to the server. When the server receives a dish recommendation request carrying the target account, the recommended dishes may not include dishes made with the specified ingredients or dishes with the specified flavor.

[0262] It should be noted that the above embodiments are all explained using the example of a food storage device logging in with only one target account. Optionally, multiple target accounts can be logged in on the food storage device, such as a first target account and a second target account logged in on the first food storage device. The server can determine the recommended information for the dish and the account to be carried in the tagging request based on the currently selected target account among the multiple target accounts logged in on the food storage device. If the currently selected target account is the first target account, the server determines the recommended information for the dish based on the reference dish corresponding to the first target account. If the currently selected target account is the second target account, the server determines the recommended information for the dish based on the reference dish corresponding to the second target account. When a dish is tagged on the page corresponding to the first target account, the generated tagging request carries the first target account. When a dish is tagged on the page corresponding to the second target account, the generated tagging request carries the second target account. For example, three target accounts can be logged in on the food storage device, and these three target accounts are tagged using "Dad", "Mom" and "Da Bao" respectively. The user can choose their target account from these three target accounts, and the target account selected by the user is considered to be the target account currently used by the food storage device. The recommended dishes displayed on the screen will vary depending on the user's target account.

[0263] In related technologies, the information of ingredients stored in food storage devices is only marked at the account level. When the same account is logged into multiple food storage devices, each food storage device will recommend dishes based on all the ingredients stored in those multiple devices. Therefore, the ingredients for a recommended dish seen by a user on a particular food storage device may not actually be stored in that refrigerator, resulting in low accuracy in the dish recommendation.

[0264] In this embodiment, the server can store the user's preference information corresponding to the target account, as well as the information of the ingredients stored in the ingredient storage devices. That is, the server stores user-related information from the account perspective and ingredient-related information from the device perspective. The target account can log in on multiple ingredient storage devices. The server can determine the reference dishes corresponding to the target account based on the user's marking operations on dishes across these multiple ingredient storage devices. This ensures that the server collects more comprehensive user preference information, thereby more accurately recommending dishes that match the user's preferences and improving the accuracy of dish recommendations. Furthermore, when determining dish recommendation information, the server can only determine dishes that can be made using ingredients stored in the ingredient storage device that sent the dish recommendation request. Therefore, the dishes recommended by the ingredient storage device to the user are all dishes that can be directly prepared using ingredients stored in that storage device. This avoids recommending dishes based on ingredients stored in various ingredient storage devices logged in by the target account, which could lead to situations where some ingredients required for certain dishes are not stored in the currently used ingredient storage device, thus improving the effectiveness and practicality of the dish recommendation information.

[0265] In this embodiment, the steps performed by the food storage device can be executed by its controller, and the steps performed by the server can be executed by its processing unit. The display steps performed by the food storage device can be implemented by the controller of the food storage device controlling the display screen. The steps performed by the food storage device to interact with the server can be implemented by the controller in the food storage device through a communication interface. The steps performed by the server to interact with the food storage device can be implemented by the processing unit in the server through a network interface unit.

[0266] It should be noted that, in this embodiment, the first and second food storage devices are simply any two food storage devices connected to the server and logged into the same target account. The above steps can also be performed on other food storage devices logged into the target account. This embodiment uses the example of both the first and second food storage devices receiving a dish marking instruction to illustrate the information recommendation method. Optionally, only one food storage device may receive the dish marking instruction; this embodiment does not impose any limitations. Furthermore, this embodiment only uses the example of the first food storage device receiving a dish recommendation instruction to illustrate the information recommendation method. Optionally, if the second food storage device receives a dish recommendation instruction, steps 613A to 619A can also be performed.

[0267] In summary, in the information recommendation method provided in this application embodiment, the dishes recommended by the food storage device to the user are determined based on the food stored in the food storage device and the reference dishes corresponding to the target account logged into the food storage device. If the reference dishes corresponding to the target account are different, the dishes recommended by the food storage device may also be different, thus improving the flexibility of the food storage device's dish recommendation.

[0268] The display device provided in this application includes a display screen for displaying a user interface. The user interface can provide interactive functions for the user, and the user can realize different functions of the display device by operating different interactive controls in the user interface.

[0269] The display device provided in this application further includes a first controller, which controls the user interface to display a recommended recipe operation interface containing controls based on the determined recommended recipe data. The controls are used to jump to the recommended recipe details interface after receiving a confirmation operation from the user.

[0270] The following section will describe the technical solution for implementing recommended recipes using the display device provided in this application.

[0271] When a user launches the recommended recipe application, the first controller of the display device responds to the user's operation on the recommended recipe application and determines the recommended recipe data that the server can provide based on the main ingredients in the food stored in the user's refrigerator, which includes main ingredients and auxiliary ingredients.

[0272] In some embodiments, the server provided in this application includes a second controller, which identifies user-stored food items sent from the refrigerator as main ingredients and secondary ingredients.

[0273] The auxiliary ingredients can be scallions, and / or ginger, and / or garlic, while the main ingredients are all the ingredients stored in the user's refrigerator except for the auxiliary ingredients. For example, when the smart refrigerator identifies that its stored ingredients include: fish, beef, tomatoes, green peppers, scallions, ginger, and garlic, the server provided in this application determines that scallions, ginger, and garlic are auxiliary ingredients; and determines that fish, beef, tomatoes, and green peppers are main ingredients.

[0274] The smart refrigerator can automatically identify the food stored in the user's refrigerator and upload the identified food to the server provided in this application. When the recipe recommendation application in the display device provided in this application accesses the server, it can read the user's stored food information already saved on the server. It should be noted that the main ingredients and auxiliary ingredients can be preset according to actual conditions, and this application does not limit their specific content.

[0275] In some embodiments, the food stored in the user's refrigerator includes the name of the food and the length of time each food has been stored. In practical applications, the food information in the refrigerator can be obtained through the refrigerator itself. For example, the server provided in this application can send a query request to the user's refrigerator via wired or wireless means. After receiving the query request from the server, the refrigerator can obtain the food information of the food stored in the refrigerator by scanning the RFID tags on the food, and then feed the food information back to the server via wired or wireless means.

[0276] In some embodiments, the refrigerator can obtain information about stored food in real time through the following methods. First, the refrigerator controller acquires an image of the storage compartment and processes the image to obtain the compartment position. Then, the refrigerator acquires the user's hand trajectory and selects a corresponding fitting trajectory based on the movement trend of the hand trajectory. The fitting trajectory is the hand trajectory at the moment of item storage or retrieval. Based on the fitting trajectory and the compartment position, the item storage or retrieval position is calculated, thereby enabling real-time monitoring of the storage or retrieval of food in the refrigerator and obtaining detailed information about the user's stored food, such as the location of the food in the refrigerator, the storage time, and the remaining shelf life. Finally, the refrigerator uploads the information about the user's stored food to the server provided in this application.

[0277] In some embodiments, the recommended recipe data includes recipe attribute information, which includes attribute elements such as the main ingredients required for the recipe, the flavor profile, the cooking method, the target audience, the suitable occasion, the cuisine, the style, the efficacy, and the required kitchen tools. In practical applications, recipes and their attribute information are stored together in the media asset library of the server provided in this application for retrieval and use.

[0278] In some embodiments, the server provided in this application includes a media asset library for storing recipe data corresponding to ingredients. For example, the server's media asset library has a built-in dictionary of the correspondence between ingredients and recipes. This dictionary contains the names of all known ingredients and the correspondence between each ingredient and all recipes containing that ingredient. After obtaining the ingredient information of all ingredients in the refrigerator, the recipe corresponding to the ingredient name is retrieved from the dictionary based on the ingredient name in the ingredient information. Each ingredient name can correspond to one or several recipes.

[0279] For example, suppose the refrigerator contains onions and cucumbers. The recipes for onions and cucumbers can be obtained using the dictionary lookup described above. Furthermore, after obtaining the recipes for onions and cucumbers, recommended recipe data is obtained by calculating the union of the recipes for onions and cucumbers.

[0280] In some embodiments, the first controller, in response to a user's operation on the recommended recipe application, determines recommended recipe data that the server can provide based on the main ingredients in the user's refrigerator storage. This includes the first controller sending a first recommendation request to the server in response to a confirmation operation of the recommended recipe application. The first recommendation request is used to prompt the server to provide the determined recommended recipe data, which is determined by the server based on the identified main ingredients in the user's refrigerator storage. Then, the first controller receives the recommended recipe data sent by the server.

[0281] When the display device launches the recommended recipe application, the first controller sends a first recommendation request to the server to obtain recommended recipe data. Specifically, the server determines recommended recipe data that can be provided to the display device based on the main ingredients in the user's refrigerator (uploaded from the user's refrigerator). It should be noted that during the generation of recommended recipe data, the server's second controller filters out auxiliary ingredients from the user's refrigerator, specifically removing scallions, ginger, and garlic as described in the above embodiment. This allows the server to generate recommended recipe data that better matches the user's needs based on the main ingredients, avoiding situations where the server generates a recommended recipe based on auxiliary ingredients like scallions, ginger, and garlic, but the user's refrigerator does not store the required main ingredients.

[0282] After determining the recommended recipe data that the server can provide, the first controller of the display device controls the user interface to display a recommended recipe operation interface containing controls based on the recommended recipe data. The controls are used to jump to the recommended recipe details interface after receiving the user's confirmation operation.

[0283] The server's second controller receives a recommendation request from the display device, queries the media asset library for recommended recipe data based on the main ingredients stored in the user's refrigerator, and identifies the user's refrigerator ingredients as either main or secondary ingredients by the server; then sends the recommended recipe data to the display device.

[0284] For example, the server's second controller receives a first recommendation request from the display device. The first recommendation request indicates that the display device is powered on and online. That is, it can be assumed that the server will receive the first recommendation request from the display device whenever the display device starts the recommended recipe application. Then, the second controller queries the media asset library based on the main ingredients in the user's refrigerator storage to determine the recommended recipe data that can be provided, and sends the recommended recipe data to the display device.

[0285] In some embodiments, the user's smart refrigerator reports information about the food stored in the refrigerator to a cloud server. The server's second controller or the recipe recommendation system queries and determines the main food information of the refrigerator at regular intervals every day, queries and determines recommended recipe data based on the main food information, and saves the recommended recipe data. When the recommended recipe application on the display device requests recommended recipe data, the saved recommended recipe data is sent to the display device to improve response speed.

[0286] In some embodiments, the first controller controls the user interface to display a recommended recipe operation interface containing controls based on the recommended recipe data. When the received recommended recipe data includes first recommended recipe data and second recommended recipe data, the first controller constructs a mapping relationship between the recipes in the recommended recipe data and the preset matching features of different users bound to the display device. Based on the mapping relationship, a user list is generated, and a second recommendation window is controlled to display the recommended recipe data mapped to the user based on the user at the focus position in the user list. The user list and the second recommendation window are displayed simultaneously in the user interface.

[0287] When the server-generated recommended recipe data includes first recommended recipe data and second recommended recipe data, that is, when it contains multiple recommended recipe data, the first controller constructs a mapping relationship between the recipes in the recommended recipe data and the preset matching characteristics of different users bound to the display device. Based on the mapping relationship, a user list is generated. That is, the multiple recipes produced are classified according to different user preset matching characteristics, making the recommended recipes more targeted and improving the fit with user needs.

[0288] For example, the user list includes 3 users: Dad, Mom, and Da Bao Da Bao Da.

[0289] The user's father's preset matching characteristics are: taste: spicy, savory; other: lowering blood lipids;

[0290] The user's mother's preset matching characteristics are: taste: sour; other: early pregnancy;

[0291] The user "DaBaoDaBaoDa" has the following preset matching characteristics: Taste: Sweet; Other: Protect eyesight.

[0292] The first controller controls the left side of the user interface to display the user list and controls the right side of the user interface to generate a second recommendation window; the focus position in the user list is the user's father, and the first controller controls the second recommendation window to display the user's father's mapped recommended recipe data, including sauerkraut fish, mapo tofu, and sliced ​​beef and tripe in chili sauce, etc.

[0293] The first controller of the display device uses recipes with spicy, savory flavors and cholesterol-lowering properties from the server-determined recommended recipe data as the mapped recommended recipe data for the user's father. By manipulating the user list, the recommended recipe data for the corresponding user can be displayed in the second recommendation window.

[0294] In some embodiments, the first controller controls the user interface to display the recommended recipe operation interface containing controls based on the recommended recipe data. When the received recommended recipe data only contains the first recommended recipe data, the first controller controls the first recommended window to display the first recommended recipe data.

[0295] In some embodiments, a mapping relationship is constructed between the preset matching features of different users bound to the display device and the recipes in the recommended recipe data, wherein the preset matching features can also be preset from the following perspectives.

[0296] For example, the target audience can be roughly divided into infants, children, adults, the elderly, pregnant women, and students preparing for the college entrance examination; the scenarios can be divided into breakfast, lunch, dinner, and late-night snacks; the recipes can be divided into Hunan cuisine, Sichuan cuisine, Shandong cuisine, etc. according to geographical regions; the types of dishes can be divided into meat dishes, vegetarian dishes, soups, desserts, snacks, steamed dishes, boiled dishes, stir-fried dishes, etc.; the effects can be divided into blood replenishment, calcium supplementation, iron supplementation, blood pressure reduction, blood lipid reduction, etc.; taste preferences can include sour, spicy, bitter, sweet, salty, umami, etc.; and the cooking methods can be divided into steaming, boiling, stir-frying, deep-frying, baking, etc.

[0297] In some embodiments, a first controller of the display device controls a user interface to display a recommended recipe operation interface containing controls based on the recommended recipe data. The controls are used to jump to the recommended recipe details interface after receiving a user's confirmation operation. The recommended recipe operation interface includes a purchase control, which is used to jump to the purchase operation interface for the corresponding ingredients of the recommended recipe after receiving a user's confirmation operation.

[0298] In the recommended recipe interface containing donuts, after the user clicks the donut poster control, the first controller controls the donut poster control to jump to the operation interface of the recipe, including the recipe name, picture, description, ingredients, and preparation method. The preparation method can include a text tutorial or a video tutorial. The operation interface also includes a purchase control. By operating the purchase control, the operation interface can jump to the purchase operation interface of the corresponding ingredients for the recommended recipe, where the user can purchase various materials needed to make donuts online.

[0299] In some embodiments, the user interface displays a recommended recipe operation interface including multiple recipes, each recipe including a poster control that displays an image of the corresponding recipe; and the server pre-sets a URL or ID for the poster control when sending the recommended recipe data, so that the user interface loads a recommended recipe details interface after the user clicks the poster control. In some embodiments, the server includes recommended recipe details when sending the recommended recipe data, and after the user clicks the poster control, the user interface loads a recommended recipe details interface based on the recommended recipe details.

[0300] In some embodiments, the first controller of the display device, in response to a user's operation on a recommended recipe application, determines recommended recipe data that the server can provide based on the main ingredients in the user's refrigerator storage. This includes: the first controller constructing a first ingredient set in response to the user's selection of the user's refrigerator storage; sending a second recommendation request to the server, the second recommendation request including the first ingredient set, the second recommendation request being used to cause the server to determine recommended recipe data that the server can provide based on the main ingredients in the first ingredient set; and receiving the recommended recipe data sent from the server.

[0301] The first controller displays the user's refrigerator-stored food items received from the refrigerator by the server on the user interface. Based on the user's operation on the focus of the user interface, the first controller selects and confirms at least one food item to constitute a first food item set, and sends a second recommendation request containing the first food item set to the server.

[0302] The server's second controller receives a second recommendation request from the display device, which includes a first set of ingredients. The controller then queries the media asset library contained in the server to determine the recommended recipe data that can be provided based on the main ingredients in the first set of ingredients in the second recommendation request, and sends the recommended recipe data to the display device.

[0303] The first controller of the display device receives recommended recipe data from the server. This recommended recipe data is generated based on the main ingredients in a first set of ingredients selected by the user. This narrows down the scope of the recommended recipe data, making it more closely aligned with the user's needs.

[0304] In some embodiments, the first controller controls the first set of ingredients selected by the user to be less than 3 kinds of ingredients. The server matches the main ingredients in the first set of ingredients, constructs recommended recipe data based on the recipe with the highest matching degree, and provides feedback.

[0305] In some embodiments, the first controller of the display device constructs a first food set in response to a user's selection of food stored in the user's refrigerator, including displaying a side dish list generated based on the food stored in the user's refrigerator on a user interface, wherein the side dish list contains ingredients arranged in ascending order according to the remaining days of their shelf life; and constructing the first food set in response to a user's selection of an ingredient from the side dish list.

[0306] In the intelligent food preparation user interface, the first controller generates a food preparation list that includes all the ingredients stored in the user's refrigerator. The image displays the name, picture, and remaining shelf life of each ingredient. For example, the food preparation list in the image includes apples, broccoli, grapes, carrots, cabbage, ham, strawberries, watermelon, milk, bread, soy milk, fruit juice, red wine, shrimp, cherries, cake, etc.

[0307] The first controller arranges the ingredients in the side dish list from smallest to largest based on the remaining days of their shelf life. The ingredients with the shorter remaining days of their shelf life are placed at the front of the list, so as to prompt users to select and use ingredients that are close to their expiration date, avoid waste, and improve the relevance of the recommended recipes to user needs and practicality.

[0308] In some embodiments, the first controller generates a progress bar for the food based on the remaining days of its shelf life, and displays the progress bar of food with a remaining shelf life of less than or equal to a preset threshold as high brightness or a preset color to prompt the user to use the food as soon as possible.

[0309] This application also provides a method for recommending recipes on a display device.

[0310] In step 701B, after the recommended recipe application is launched, a first recommendation request is sent to the server. The first recommendation request is used to enable the server to provide recommended recipe data determined based on the main ingredients stored in the user's refrigerator.

[0311] In step 702B, the user interface displays a recommended recipe operation interface containing controls based on the recommended recipe data. The controls are used to jump to the recommended recipe details interface after receiving confirmation from the user.

[0312] The specific operation of the display device to implement the recommended recipe has been described in detail in the above introduction to the technical solution for implementing the recommended recipe on the TV side, and will not be repeated here.

[0313] In some embodiments, after the recommended recipe application is launched, the method further includes: sending a second recommendation request to the server, the second recommendation request including a first set of ingredients selected by the user from the ingredients stored in the user's refrigerator, the second recommendation request being used to enable the server to determine recommended recipe data that the server can provide based on the main ingredients in the first set of ingredients; and receiving the recommended recipe data sent from the server. The specific operations of the display device in implementing the recommended recipe have been described in detail in the above introduction to the technical solution for implementing recommended recipes on the television side, and will not be repeated here.

[0314] Based on the above-described technical solution for implementing recommended recipe data using display devices and servers, and the accompanying drawings, this application also provides a method for server-side recommended recipes.

[0315] In step 801B, a recommendation request is received from the display device, and recommended recipe data that can be provided is queried based on the main ingredients in the food stored in the user's refrigerator. The food stored in the user's refrigerator is identified by the server as either a main ingredient or a secondary ingredient.

[0316] In step 802B, the recommended recipe data is sent to the display device.

[0317] The specific operations of the server in implementing the recommended recipes have been described in detail in the above introduction to the technical solution for implementing recommended recipes on the TV side, and will not be repeated here.

[0318] In some embodiments, receiving a recommendation request from a display device and querying available recommended recipe data based on the main ingredients in the food stored in the user's refrigerator includes: receiving a second recommendation request from the display device containing a first set of ingredients; determining available recommended recipe data based on the main ingredients in the first set of ingredients in the second recommendation request; and sending the recommended recipe data to the display device. The specific operations of the server implementing the recommended recipes have been described in detail in the above introduction to the technical solution for implementing recommended recipes on the TV side, and will not be repeated here.

[0319] This application also provides a refrigerator that includes a camera, a display screen, and a third controller.

[0320] The refrigerator is a four-door refrigerator, and its camera is installed inside the refrigerator and configured to capture images of the refrigerator's interior, such as images of the refrigerator compartment and freezer compartment, and send them to a third controller for identifying ingredients and generating recommended recipe data.

[0321] The display screen, configured to show the user interface, is typically located on the exterior of the refrigerator's door panel.

[0322] In some embodiments, the third controller is configured to send user-stored food items, obtained from images of the refrigerator's interior captured by the camera, to a server. These user-stored food items are identified by the server as either main or secondary ingredients. In response to user actions on the recommended recipe application, the controller determines recommended recipe data that the server can provide based on the main ingredients in the user's refrigerator storage. The controller also controls the user interface to display a recommended recipe operation interface containing controls based on the recommended recipe data. These controls are used to redirect to the recommended recipe details interface upon receiving confirmation from the user. The specific operation of the third controller, camera, and display screen in the refrigerator to implement recommended recipes is similar to that on a television, and has been described in detail in the above introduction to the technical solutions for implementing recommended recipes on television and server sides, and will not be repeated here.

[0323] The beneficial effects of this application's embodiments are as follows: by constructing main ingredients and auxiliary ingredients, it avoids generating recommended recipe data based on auxiliary ingredients such as scallions, ginger, and garlic; further, by constructing a first recommendation request, it enables the application to automatically obtain recommended recipe data after startup; further, by constructing a first ingredient set and a second recommendation request, it enables the generation of more accurate recommended recipe data based on the user's selected ingredients; further, by constructing a side dish list, it enables the management of ingredient shelf life; and further, by constructing a purchase control, it enables the purchase of ingredients in the recommended recipe data, thereby distinguishing between main ingredients and auxiliary ingredients in the user's refrigerator and generating recommended recipe data based on the main ingredients, thus improving the accuracy of recipe recommendations.

[0324] This application also provides a computer program product containing instructions that, when run on a computer, cause the computer to execute the information recommendation method provided in any embodiment of this application.

[0325] It should be understood that the term "and / or" in this application is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, the character " / " in this document generally indicates that the preceding and following related objects are in an "or" relationship. In cases involving mathematical formula calculations, the character " / " represents the operator "divide". The term "at least one of A and B" in this application is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, at least one of A and B can represent: A existing alone, A and B existing simultaneously, or B existing alone. "Multiple" refers to "two or more". The terms "first", "second", "third", etc., in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate, for example, to implement the application in a sequence other than those given in the embodiments illustrated or described in this application. Furthermore, the terms “comprising” and “having”, and any variations thereof, are intended to cover but not exclusively include, for example, a product or device that includes a series of components is not necessarily limited to those that are explicitly listed, but may include other components that are not explicitly listed or that are inherent to such product or device.

[0326] The above description is merely an optional embodiment of this application and is not intended to limit this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the protection scope of this application.

Claims

1. An information recommendation method, characterized in that, Equipment for storing target food ingredients includes: Send a menu recommendation request to the server; In response to the dish recommendation information fed back by the server based on the dish recommendation request, the dish recommendation information is displayed; The recommended dish information is determined by the server based on the recommended dish request, according to the ingredients stored in the target ingredient storage device and at least one auxiliary ingredient storage device corresponding to the target ingredient storage device. The auxiliary ingredient storage device is determined by the target ingredient storage device based on at least one of the following: logging into the same target account and the distance between the auxiliary ingredient storage device and the target ingredient storage device is less than a distance threshold.

2. The information recommendation method according to claim 1, characterized in that, The auxiliary food storage device and the target food storage device are logged into the same target account, or they are on the same local area network as the target food storage device; The method further includes: Obtain the local area network identifier connected to the target food storage device, the target account logged into the target food storage device, and the food information corresponding to the food stored in the target food storage device; Send at least one of the local area network identifier and the target account along with the ingredient information to the server simultaneously; The ingredient information is updated by the target ingredient storage device based on at least one identification method, namely image recognition, radio frequency identification, and user records, when the ingredients change.

3. The information recommendation method according to claim 2, characterized in that, The step of obtaining the food information corresponding to the food stored in the target food storage device includes: Obtain the user's hand movement; Based on the movement trend of the hand trajectory, a corresponding fitting trajectory is selected, wherein the fitting trajectory is the hand trajectory at the moment of food storage and retrieval. Based on the fitted trajectory and the corresponding grid layer position, the food information corresponding to the food stored in the target food storage device is identified.

4. The information recommendation method according to claim 2, characterized in that, The display of the recommended dishes includes: Display at least one dish, and display information about the ingredients used to prepare the dish on the same interface as the dish; Alternatively, at least one dish may be displayed, and in response to a selection instruction for said dish, information on the ingredients for preparing said dish may be displayed.

5. The information recommendation method according to claim 2, characterized in that, The display of the recommended dishes includes: Display at least one user tag corresponding to the target account; the user tag is used to characterize user identity, user tastes, and user preferences; In response to a selection instruction for selecting a user tag, switch to the dish recommendation information corresponding to the user tag.

6. The information recommendation method according to claim 2, characterized in that, The display of the recommended dishes includes: Display at least one dish, and display the recommendation priority of the dish; The recommendation priority is positively correlated with the sum of the similarities between the dish and the corresponding reference dish, or the recommendation priority is equal to the sum of the similarities between the dish and the corresponding reference dish. The reference dish is a dish marked by a user in the target account. The similarity includes the taste similarity and ingredient overlap between the dish and the reference dish. The sum of the similarities is determined by the sum of the product of the taste similarity and the corresponding weight, and the product of the ingredient overlap and the corresponding weight.

7. The information recommendation method according to claim 2, characterized in that, The display of the recommended dishes includes: Display at least one of the target accounts; In response to a switching command for switching the target account, the system switches to the dish recommendation information corresponding to the target account.

8. The information recommendation method according to claim 1, characterized in that, The dish recommendation information includes at least one recommended recipe data and a shelf life progress bar for the ingredients in the recommended recipe data; The display of the recommended dishes includes: A mapping relationship is constructed between the preset matching features of different users and the recommended recipe data; Generate a user list based on the mapping relationship; Displays the recommended recipe data corresponding to the user at the focus position in the user list, and the shelf life progress bar of the ingredients corresponding to the recommended recipe data; Among them, the shelf life progress bar for ingredients with remaining shelf life less than or equal to a preset threshold is displayed using a preset color or high brightness.

9. An information recommendation method, characterized in that, For use on servers, including: Receive a dish recommendation request sent by the target ingredient storage device; Based on the dish recommendation request, at least one auxiliary food storage device corresponding to the target food storage device is determined according to at least one of the following methods: the auxiliary food storage device is logged into the same target account as the target food storage device, and the distance between the auxiliary food storage device and the target food storage device is less than a distance threshold. Based on the ingredients stored in the target ingredient storage device and the corresponding auxiliary ingredient storage device, recipe recommendation information is determined. Send the dish recommendation information to the target ingredient storage device.

10. The information recommendation method according to claim 9, characterized in that, The auxiliary food storage device and the target food storage device are logged into the same target account, or they are on the same local area network as the target food storage device; The method further includes: The system receives the local area network identifier connected to the target food storage device, the target account logged into the target food storage device, and the food information corresponding to the food stored in the target food storage device, sent by the target food storage device; wherein, at least one of the local area network identifier and the target account is received simultaneously with the food information; The local area network identifier, the target account, and the ingredient information are stored in the media library of the server.

11. The information recommendation method according to claim 9, characterized in that, The process of determining dish recommendation information based on the ingredients stored in the target ingredient storage device and the corresponding auxiliary ingredient storage device includes: Obtain the food stored in the auxiliary food storage device corresponding to the target food storage device from the media library of the server; The ingredients are identified as main ingredients and auxiliary ingredients; The recommended dish information is determined based on the main ingredients.

12. The information recommendation method according to claim 11, characterized in that, Sending dish recommendation information to the target food storage device includes: The menu recommendation information includes a preset URL and a preset identifier ID for the poster control, so that the target food storage device can display the menu recommendation information in response to the user's click on the poster control.

13. A server, characterized in that, include: The network interface is configured to communicate with the food storage equipment; The media library is configured to store ingredient information; The second controller is configured as follows: Receive dish recommendation requests sent by the food storage device through the network interface; Based on the dish recommendation request, at least one auxiliary food storage device corresponding to the food storage device is determined according to at least one of the following methods: the auxiliary food storage device is logged into the same target account as the food storage device, and the distance between the auxiliary food storage device and the food storage device is less than a distance threshold. Based on the ingredients stored in the food storage equipment and the corresponding auxiliary food storage equipment, recipe recommendation information is determined. Send the dish recommendation information to the food storage device.

14. A food storage device, characterized in that, include: The monitor is configured to display the user interface; The storage room was configured for storing food ingredients; The second communicator is configured to communicate with the server; The third controller is configured as follows: Send a menu recommendation request to the server; In response to the dish recommendation information fed back by the server based on the dish recommendation request, the display is controlled to show the dish recommendation information; The recommended dish information is determined by the server based on the recommended dish request, according to the ingredients stored in the ingredient storage device and at least one auxiliary ingredient storage device corresponding to the ingredient storage device. The auxiliary ingredient storage device is determined by the ingredient storage device based on at least one method, such as logging into the same target account and the distance between the auxiliary ingredient storage device and the auxiliary ingredient storage device being less than a distance threshold.

Images