JP7240936B2 - Server, server control method and program - Google Patents

Description

The present disclosure relates to a server and its control method .

Many people, not just housewives who cook every day, are troubled by the fact that they cannot think of the dishes to make and their recipes when they have an opportunity to cook. On the other hand, as one of the answers to these problems, there is a service that accepts recipe submissions from various people, regardless of whether they are cooking professionals or amateurs, and distributes and publishes them on the Internet.

However, a huge number of recipes are open to the public in the above-mentioned services, and there is a possibility that considerable effort and time will be required for the user to select a suitable recipe.

As a technique related to such recipe selection, Patent Document 1 discloses, based on cooking environment information representing the cooking environment such as the time of day and weather conditions, one of a plurality of cooking information corresponding to the corresponding cooking environment as recommended cooking information. An information processing apparatus is disclosed that determines and recommends this to a user.
According to Patent Document 1, it is possible to propose recipes to users according to conditions such as time of day and weather conditions.

Japanese Patent Application Laid-Open No. 2007-334605

In the above-described conventional technology, it is possible to propose a recipe according to the environment in which the user is placed. However, given so-called smart kitchen technology, there are other considerations that need to be addressed as well.

In smart kitchen technology, recipes are set in kitchen appliances to automatically execute various cooking operations. However, the specifications of the kitchen appliances of each user, which are targets of such settings, vary.

Therefore, even if a recipe is simply proposed according to the external environment, etc., depending on the user who uses the recipe, the performance of the kitchen appliance may not be fully demonstrated, and the efficiency and quality of cooking may not be appropriate. There is also

In addition, users who want to cook using such recipes tend to prefer efficient cooking without trouble. On the other hand, there is also a tendency to expect the completion of high-quality dishes by recipes filled with various know-how by professional culinary researchers.
However, no technique has been proposed for recommending recipes suitable for users based on the use of recipes as described above.
Accordingly, an object of the present disclosure is to provide a technology that enables proposal of recipes suitable for the user .

To achieve the above object, a server in one aspect of the present disclosure includes acquisition means for acquiring first information about a recipe used by a user; and control means for controlling to propose a recipe in response to receiving the proposal request from the reception means, wherein the first information and the user plan to use the suggested recipe. and control means for controlling to propose a recipe based on the date and time of the user, when the date and time when the user plans to use the suggested recipe is a first date and time, and when it is a second date and time. A different recipe is proposed depending on the case.

Further, the server according to one aspect of the present disclosure may perform control so as to propose different recipes depending on whether the user plans to use the suggested recipe on a weekday or on a holiday. .

Further, the server according to one aspect of the present disclosure obtains information about the difficulty level of the recipe used by the user from the first information, and performs control so as to propose different recipe groups according to the difficulty level of the recipe. You may

Further, the server according to one aspect of the present disclosure may suggest recipe groups based on the difficulty level of recipes that appear more frequently among the recipes used by the user.

Further, the server according to one aspect of the present disclosure may be characterized in that the first information includes information indicating the recipe used by the user and the date and time when the recipe was used.

Further, in a server control method according to an aspect of the present disclosure, an obtaining step of obtaining first information about a recipe used by a user; a receiving step of receiving a proposal request for proposing a recipe to the user; a control step for controlling to propose a recipe in response to the reception of the proposal request in the reception step, the first information and a date and time when the user plans to use the proposed recipe; and a control step for controlling to propose a recipe based on the first date and time when the user plans to use the proposed recipe, and when it is a second date and time. It may feature that different recipes are suggested.

According to the present disclosure, it is possible to propose a recipe suitable for the user .

1 is a diagram of a network configuration example including a recipe proposal device of this embodiment; FIG. It is a figure which shows the structural example of the recipe proposal apparatus in this embodiment. It is a figure which shows the structural example of the user terminal in this embodiment. It is a figure which shows the structural example of the kitchen household appliance in this embodiment. It is a figure which shows the structural example of the specification information in this embodiment. It is a figure which shows the structural example of the recipe table in this embodiment. It is a figure which shows the structural example of the usage log table in this embodiment. It is a figure which shows the structural example of the cooking characteristic table in this embodiment. It is a figure which shows the flow example of the recipe proposal method in this embodiment. FIG. 10 is a diagram showing an example 1 of a screen in this embodiment; FIG. 10 is a diagram showing an example 2 of a screen in this embodiment; FIG. 10 is a diagram showing an example 3 of a screen in this embodiment; FIG. 10 is a diagram showing an example 4 of a screen in this embodiment;

<Network configuration including recipe proposal device>
Embodiments of the present disclosure will be described in detail below with reference to the drawings. FIG. 1 is a diagram of a network configuration example including a recipe proposal device 10 of this embodiment.

As the recipe proposal device 10 of this embodiment, a device for managing and operating a so-called recipe posting site is assumed. The recipe proposal device 10 exemplified here is a web server that publishes the recipe posting site described above on a network 1 such as the Internet.

On the recipe posting site published by the recipe proposal device 10, various people, whether famous or unknown or professionals or amateurs, post their own recipes. Similarly, various people access and view recipes of genres necessary for themselves or of favorite contributors.

The data format of such recipes to be posted and browsed is not limited, but for example, recipes in MRR (Machine Readable Recipe) format can be assumed.

A recipe in the MRR format is a recipe that can be read by a cooking appliance such as a microwave oven (a kitchen appliance 30 to be described later). On the other hand, a recipe that includes both qualitative and quantitative expressions and is human-readable is called an HRR (Human Readable Recipe) recipe.

In the case of conventional recipes such as the above-mentioned HRR format, even one cooking operation is often described in various different expressions by the contributor, and even if this is set in the cooking equipment, the cooking accuracy is unstable. easy to become. Therefore, recipes in the MRR format eliminate descriptions unrelated to cooking operations, inconsistent spellings, grammatical errors, and the like, which may exist in conventional recipes.

Such an MRR-format recipe is represented as data by, for example, a graph (directed graph) consisting of a plurality of nodes and edges between the nodes. In this graph, nodes define state transitions for each material, and edges represent actions required for state transitions between nodes.
Table 1 shows the types of nodes mentioned above.

Each node can be given the attributes shown in Table 2, for example, as node attributes. Assume here that the node is a material node and that this material node represents "carrot".

また、各エッジには、エッジの属性として、表３に示す属性を付与可能である。

Further, attributes shown in Table 3 can be assigned to each edge as edge attributes.

Note that the above-mentioned actions refer to basic procedures constituting cooking, and for example, procedures such as "cutting" and "warming" correspond to actions. Actions include specific temperature settings, cooking times, and work details for the equipment.

A specific example of each node will now be described. When creating a dish "salad", the dish node is "salad". Ingredient nodes are, for example, "onion", "cucumber", "tomato", "ketchup", and "mayonnaise". Each material node is given an ID that uniquely identifies the material.

The material node 'onion' is connected with the intermediate node 'chopped onion' by the edge (action) 'cut'. Also, the material node "cucumber" is connected to the intermediate node "1 cm square cucumber" by the edge (action) "cut".

Further, the material node "tomato" is connected to the intermediate node "1/2 tomato" by the edge (action) "cut". Furthermore, the material node "ketchup" and the material node "mayonnaise" are connected to the intermediate node "aurora sauce" by the edge (action) "mix". An ID that uniquely identifies the action is assigned to each of "cut" and "mix".

Then, the intermediate nodes 'chopped onion', '1 cm square cucumber' and '1/2 tomato' are connected to the dish node 'salad' by the edge (action) 'Serve'. In addition, the intermediate node "aurora sauce" is connected to the dish node "salad" by the edge (action) "kake". An ID that uniquely identifies the action is assigned to each of "Serve" and "Sprinkle".

Also, the order between edges is set so that "putting on" is performed after "arranging". It should be noted that an action of "playing" may be used instead of "playing".

In this way, when expressing the state transition of each material as a graph, each material is given a material ID that uniquely identifies the material, and each action required for state transition has an action ID that uniquely identifies the action. Granted.

Therefore, the machine can easily and reliably decode the recipe information based on the ID. In addition, since it is not necessary to specify in the recipe information which device should perform the action, it is easy to deal with various devices including new devices that will appear in the future. Furthermore, since each action is expressed as an edge, it is easy to extract each action from the recipe information.

A user of a recipe posting site can be a contributor or a reader at will, but for the sake of convenience, the contributor and the reader will be collectively referred to as users in the following description. Therefore, in addition to the recipe proposal device 10, user terminals 20 of posters and viewers are communicably connected to the network 1 illustrated in FIG.

As the user terminal 20 described above, a smart phone, a tablet terminal, a notebook PC, or the like having an appropriate communication function to the network 1 can be assumed. In addition, the user terminal 20 performs data communication with the kitchen appliance 30 (for example, data communication when setting recipe contents). It is assumed that the communication function of Also, as an example of software held by the user terminal 20, a mobile application that operates on a mobile terminal, that is, an application 29 is assumed.

This application 29 enables viewing of recipes via a browsing function on the recipe posting site published by the recipe proposal device 10, and a function for posting recipes to the recipe posting site as necessary. Also prepare.

A person who operates such a user terminal 20 accesses the recipe posting site via the user terminal 20 . Then, the user browses the desired recipe, sets it in his/her own kitchen appliance 30, and intends to use it effectively for cooking. A person who actually uses a recipe with such an intention is called a recipe user.
The specific configuration of the recipe proposal device 10 of the present embodiment, its processing procedure, and the like will be sequentially described below.
<Configuration of Recipe Proposal Device>

The configuration of the recipe proposal device 10 in this embodiment includes a storage unit 11, a memory 12, a calculation unit 13, an input unit 14, an output unit 15, and a communication unit 16, as shown in FIG.

Among them, the storage unit 11 is composed of non-volatile storage elements such as HDD (Hard Disk Drive) and SSD (Solid State Drive).

The storage unit 11 stores at least a recipe table 120, a usage history table 121, and a cooking characteristics table 122, in addition to the program 17 for implementing the functions necessary for the recipe proposal device of this embodiment. Details of these tables will be described later. Also, the memory 12 is composed of a volatile memory element such as a RAM.

Also, the calculation unit 13 is assumed to be a CPU that loads the program 17 held in the storage unit 11 into the memory 12 and executes it, and implements the necessary functions as a recipe proposal device.
The functions implemented here are a recipe storage unit 100, a recipe proposal unit 101, and a usage history storage unit 102. FIG. Details of these will be described later.

Also, the input unit 14 is assumed to be a keyboard, mouse, keypad, touch panel, microphone, or the like that receives key input or voice input from the user. Also, the output unit 15 is assumed to be a display or the like that displays the processed data.

Also, the communication unit 16 is assumed to be a NIC (Network Interface Card) or the like that connects to the network 1 and performs communication processing with other devices such as the user terminal 20 and the kitchen appliance 30 .

Note that the input unit 14 and the output unit 15 described above are not essential components. These are necessary configurations when the recipe proposal device 10 accepts each request for recipe posting or recipe search from the user in its own input unit 14 and displays the processing results on the output unit 15. be.

<Configuration of user terminal>
Next, a configuration example of the user terminal 20 according to this embodiment will be described. FIG. 3 is a diagram showing a configuration example of the user terminal 20 in this embodiment. The user terminal 20 of this embodiment includes a storage unit 21, a memory 22, a calculation unit 23, an input unit 24, an output unit 25, a first communication unit 26, and a second communication unit 27, as shown in FIG. .

Among them, the storage unit 21 is composed of non-volatile storage elements such as HDD (Hard Disk Drive) and SSD (Solid State Drive).

The storage unit 11 stores at least an application 29 as a program 28 for implementing functions necessary for the user terminal of this embodiment. As already described, this application 29 enables the browsing of recipes via the browsing function on the recipe posting site published by the recipe proposal device 10 . Also, the memory 22 is composed of a volatile memory element such as a RAM. Also, the computing unit 23 is assumed to be a CPU that loads and executes the program 28 held in the storage unit 21 into the memory 22 and implements the necessary functions as a user terminal.

Also, the input unit 24 is assumed to be a keyboard, mouse, keypad, touch panel, microphone, etc. for receiving key input and voice input from the user. Also, the output unit 25 is assumed to be a display or the like that displays the processed data.

Also, the first communication unit 26 is assumed to be a NIC (Network Interface Card) or the like that connects to the network 1 and performs communication processing with other devices such as the recipe proposal device 10 .

Also, the second communication unit 27 is assumed to be a unit that performs short-range wireless communication such as wireless communication and infrared communication with the kitchen appliance 30 at a specific frequency (eg, 2.4 GHz band).

<Composition of kitchen appliances>
Also, a configuration example of the kitchen appliance 30 according to the present embodiment will be described. FIG. 4 is a diagram showing a configuration example of the kitchen appliance 30 according to this embodiment. The kitchen appliances 30 are cooking appliances used by the user of the user terminal 2 for cooking. A microwave oven and a water oven can be assumed as a main specific example thereof. In any case, it is an apparatus that automatically executes a cooking operation according to a recipe by setting predetermined data corresponding to the recipe.

The kitchen appliance 30 includes a storage unit 31, a memory 32, a calculation unit 33, an input unit 34, an output unit 35, a first communication unit 36, a second communication unit 37, a program 38, and a cooking mechanism 39. .

Among them, the storage unit 31 is composed of non-volatile storage elements such as HDD (Hard Disk Drive) and SSD (Solid State Drive).

The storage unit 31 stores at least a program 38 for implementing functions necessary for the kitchen appliance 30 of the present embodiment. This program 38 controls the cooking mechanism 39 according to the content of the data setting according to the recipe.

Also, the kitchen appliance 30 holds the specification information 381 (see FIG. 5) of the kitchen appliance 30 . The specification information 381 is specification information of the kitchen appliance 30, and is information indicating values related to items such as a heating method, maximum output, temperature control range, and internal capacity, for example. Also, the memory 32 is composed of a volatile memory element such as a RAM. Further, the calculation unit 33 is assumed to be a CPU that loads the program 38 held in the storage unit 31 into the memory 32 and executes it, and implements functions necessary for kitchen appliances.

Also, the input unit 34 is assumed to be a touch panel, buttons, a microphone, or the like for receiving key input or voice input from the user. Also, the output unit 35 is assumed to be a display or the like that displays the processed data.

Also, the first communication unit 36 is assumed to be a NIC (Network Interface Card) or the like that connects to the network 1 and performs communication processing with other devices such as the recipe proposal device 10 .

Also, the second communication unit 37 is assumed to be a unit that performs short-range wireless communication such as wireless communication and infrared communication with the user terminal 20 at a specific frequency (eg, 2.4 GHz band).

In addition, the cooking mechanism 39 is generally provided in the above-described microwave oven, water oven, etc., and is responsible for various cooking operations such as heating, adding water, rotating, exhausting, sensing, and taking, for example, the material to be cooked and the cooking space. It is an integrated body of units.

The cooking mechanism 39 is controlled by the program 38, and performs various cooking operations such as heating up to a predetermined reference value, adding water, rotating, exhausting, etc. based on the ingredients sensed by the sensing unit and the temperature and humidity of the cooking space. do.

<Specific example of data>
Next, various databases used by the recipe proposal device 10 of this embodiment will be described. FIG. 6 shows an example of the recipe table 120 in this embodiment.

The recipe table 120 is a table that stores recipes that have been posted from the user terminal 20, for example. The structure includes, for example, a recipe ID that uniquely identifies a recipe as a key item, a user ID that indicates the person who posted the recipe, attributes of the person who posted the recipe (eg, professional/amateur), recipe title, cooking genre, and difficulty level. , required cooking time, file name (or storage destination address), and other data are associated with each other.

Also, FIG. 7 shows an example of the usage history table 121 in this embodiment. The usage history table 121 is a table that stores the usage history of the recipes stored in the recipe table 120 described above.

The structure includes, for example, a user ID that uniquely identifies a recipe user as a key item, the recipe ID of the recipe used by the recipe user, the date and time of use, the actual cooking time when the recipe user used the recipe, and , cooking contents, etc. are associated with each other. It should be noted that, as the above-described cooking content, for example, the type of kitchen appliance 30 used by the recipe user can be assumed.

Also, FIG. 8 is a diagram showing a configuration example of the cooking characteristic table 122 in this embodiment. The cooking characteristics table 122 shows the lifestyle of the recipe user and the lifestyle determined based on at least one of the actual cooking time of each recipe user, the details of cooking, and the predetermined attribute of the recipe used by the recipe user. This is a table that stores characteristics personally desired by recipe users regarding cooking using recipes.

The structure includes, for example, an ID that uniquely identifies a record as a key, the recipe user's lifestyle, cooking characteristics desired by the recipe user, cooking date and time, cooking time, cooking details, and recipe attributes. It is an aggregate of records associated with items.

As a specific example of the record, for example, for a recipe user whose lifestyle is "busy and gourmet-oriented", if the cooking date and time is "weekdays", cooking time: "1 hour or less" Cooking content: "use microwave oven" , recipe attribute: “professional recipe, medium difficulty level”, are defined as cooking characteristics desired by the recipe user of the lifestyle.

In addition, for the recipe user with the lifestyle, if the cooking date and time is "holiday", cooking time: "2 hours or less", cooking content: "use of water oven", recipe attribute: "professional recipe, high difficulty level" , are defined as the cooking characteristics desired by the recipe user.

<Function of recipe storage>
The functions of the recipe proposal device 10 are the recipe storage unit 100, the recipe proposal unit 101, and the usage history storage unit 102, as described above. Of these, the recipe storage unit 100 receives recipe submissions from the user terminal 20 and stores them in the recipe table 120 of the storage unit 11 .

When storing recipes, the recipe storage unit 100 assigns a recipe ID according to a predetermined rule or algorithm. Using this as a key, a user ID indicating the person who posted the recipe and attributes of the person who posted the recipe (eg, professional/amateur) are stored. , recipe title, description, cooking genre, degree of difficulty, required cooking time, file name (which may be a storage destination address), and other data are associated with each other to generate a record.

Each of the above-mentioned user ID, attributes of the contributor (e.g. professional/amateur), recipe title, description, cooking genre, difficulty level, required cooking time, file name (storage destination address is acceptable). All of the values are included in the data of recipes posted from the user terminal 20 .

<Functions of recipe suggestion part>
Also, the recipe proposal unit 101 receives a predetermined recipe proposal request from the user terminal 20 and requests the user terminal 20 or the kitchen appliance 30 to acquire the specification information 381 of the recipe user's kitchen appliance 30 . The specification information 381 obtained here is the specification information of the kitchen appliance 30, and is information indicating values related to items such as the heating method, maximum output, temperature control range, and internal capacity, for example.

In addition, the recipe proposal unit 101 determines that the value of the cooking operation corresponding to the quantitative description in the recipe among the recipes stored in the recipe table 120 is the performance upper limit and the predetermined range in the spec information 381 acquired as described above. to identify close ones.

For example, if the spec information 381 obtained for the recipe user's "microwave oven" indicates that the "maximum output", which is the upper limit of performance, is "1200 W", among the recipes stored in the recipe table 120, Regarding the cooking operation "heating operation" of the "microwave oven", specify the set output value that is smaller than the above "1200 W" within the range of "10%", that is, "1080 W to 1200 W" . Also, the recipe proposal unit 101 distributes the specified recipe to the user terminal 20 that has sent the recipe proposal request described above.

It should be noted that the recipes specified and distributed as described above are, of course, subject to the wishes of the recipe user regarding other conditions such as dish names such as "meat and potatoes", "Japanese food", and "two servings", cooking genres, and portions. It is assumed that the recipe matches in advance.

Alternatively, as will be described later, the recipe proposal unit 101 identifies recipes with attributes that fit the recipe user as a population based on the usage history table 121 and the cooking characteristics table 122, and from this population, the above-mentioned It is assumed that the recipe is specified as being close to the performance upper limit within a predetermined range.

In this case, the recipe suggesting unit 101 determines at least one of the actual cooking time and cooking content for the recipe user indicated by each usage history in the usage history table 121, and the predetermined attribute of the recipe used by the recipe user. Based on this, the characteristics that the recipe user personally desires for cooking using the recipe are determined and stored in the cooking characteristics table 122 .

More specifically, the recipe proposal unit 101 searches for records in the usage history table 121 using the user ID of the recipe user as a key, and the recipe ID, date and time of usage, and the recipe ID of the recipe that is indicated by each retrieved record. It acquires values such as the actual cooking time when the recipe user uses the recipe and the content of cooking (for example, the type of kitchen appliance 30 used).

In addition, the recipe proposal unit 101 statistically processes the values of each record obtained as described above, specifies cooking characteristics specific to the recipe user, and stores them in the cooking characteristics table 122 . In this statistical processing, for example, the average value of "cooking time" in all target records and the average value of cooking times in other recipe users are calculated. When comparing the two, if the recipe user's average cooking time is shorter, ie, if the recipe user's cooking time tends to be short, the lifestyle of the recipe user is determined to be "busy".

In addition, the frequency of occurrence of the "cooking date and time" of "weekday" and "holiday" is calculated and compared, and the attribute with the higher appearance frequency is regarded as one of the cooking characteristics desired by the recipe user. judge.

In addition, the frequency of occurrence of “use of microwave oven” and “use of water oven” for “cooking content” are calculated, and the two are compared. It is determined as one of

In addition, as cooking characteristics desired by such recipe users, the frequency of occurrence of recipe attributes of "professional recipe" and "amateur recipe" is calculated, and the two are compared. is one of the lifestyles of the recipe user (e.g., those who tend to use professional recipes are gourmet-oriented, and those who tend to use amateur recipes are ordinary-oriented), and the cooking characteristics desired by the recipe user (eg, high desire to use professional recipes/high desire to use amateur recipes). The determination regarding the attribute of this recipe is similarly performed regarding the "difficulty".

In this way, the recipe proposal unit 101 generates a combination condition for each item such as "cooking date and time", "cooking time", "cooking content", and "recipe attribute" for the recipe user's "lifestyle". This is stored in the cooking characteristics table 122 as one record.
The records stored in this cooking characteristics table 122 are commonly applied to other recipe users who match in terms of "lifestyle".

Therefore, the recipe proposal unit 101 refers to the cooking characteristics table 122 described above for the cooking characteristics of the recipe user who has sent the recipe proposal request and the recipe user who has the same "lifestyle" value, and includes the cooking characteristics in the attributes. The recipes are identified in the recipe table 120, the identified recipe group is taken as a population, and the recipes identified as being close to the upper limit of performance within a predetermined range from this population are sent to the user terminal 20 of the recipe user. To deliver.

Specifically, regarding the recipe user who sent the recipe proposal request, as described above, from the recipe user's usage history, if the lifestyle is "busy and gourmet-oriented" and the cooking date and time is "weekdays", the cooking time: When cooking characteristics such as “one hour or less”, cooking content: “microwave use”, recipe attribute: “professional recipe, medium difficulty” are specified, the recipe table 120 lists recipes that match the conditions of each of these items. , and the recipe group identified here is used as a population, and among the recipes included in this population, the value of the cooking operation corresponding to the quantitative description in the recipe is within the performance upper limit and the predetermined range in the specification information 381 A close one is specified and distributed to the user terminal 20 .

<Functions of usage history storage unit>
In addition, the usage history storage unit 102 stores various information about recipe users who browsed and used recipes via the recipe posting site and their usage details, for example, various logs such as recipe browsing from the user terminal 20 on the recipe posting site. Alternatively, it is obtained from the user terminal 20 and stored in the usage history table 121 .

As shown in FIG. 7, the information to be stored here includes, as shown in FIG. Data such as the actual cooking time when used and the content of cooking are associated with each other.

<Recipe proposal method>
Next, the actual procedure of the recipe proposal method in this embodiment will be described with reference to the drawings. Various operations corresponding to the recipe proposal method described below are implemented by, for example, a program executed by the recipe proposal device 10 . Also, the program is composed of codes for performing various operations described below. FIG. 9 is a diagram showing a flow example 1 of a recipe proposal method according to this embodiment. Here, a flow of processing mainly performed by the recipe proposal unit 101 will be described.

In this case, it is assumed that a certain user (recipe user) of the recipe posting site requests to receive a proposal of a recipe suitable for him/herself, and the user terminal 20 notifies the recipe proposal device 10 to that effect as a recipe proposal request. do.

On the other hand, it is assumed that the recipe proposal device 10 distributes to the user terminal 20 a screen (screen 900 in FIG. 10) for accepting requests for such recipe proposals. As exemplified on the screen 900 of FIG. 10, the recipe proposal request includes a user ID 901 of the recipe user, a desired cooking genre 902, a scheduled date and time for using the recipe 903, a type 904 of the kitchen appliance 30 to be used, and specification information 905. Among these values, at least the user ID, the desired cooking genre, and the scheduled date and time of use can be included.

Note that the specification information 905 of the kitchen appliance 30 scheduled to be used is specification information of the kitchen appliance 30, and includes, for example, values related to items such as the heating method, maximum output, temperature control range, and internal capacity. information to be displayed.

Therefore, the recipe proposal unit 101 of the recipe proposal device 10 receives the recipe proposal request from the user terminal 20 via the screen 900 described above, and acquires each value included in the recipe proposal request (s10).

If the value acquired in s10 contains only information on each value of the user ID, the desired cuisine genre (example: Japanese food), and the scheduled date and time of use (example: 2018/9/20 (Thursday)) ( s11:y1), the recipe suggesting unit 101 selects at least one of the actual cooking time and cooking content of the recipe user and the predetermined attribute of the recipe used by the recipe user indicated by each usage history in the usage history table 121. Based on this, the lifestyle of the recipe user and the characteristics personally desired for cooking using the recipe are determined (s12).

The recipe proposal unit 101 in s12 searches for records in the usage history table 121 using the user ID obtained in s10 as a key. Then, the recipe ID of the used recipe indicated by each retrieved record, the date and time of use, the actual cooking time when the recipe user used the recipe, and the cooking content (eg, the type of kitchen appliance 30 used, Obtain values such as the changed temperature and time from the recipe contents. Also, the recipe proposal unit 101 statistically processes the values of each record acquired as described above, and identifies the lifestyle and unique cooking characteristics of the recipe user.

In this statistical processing, for example, the average value of "cooking time" in all target records and the average value of cooking times in other recipe users are calculated. When comparing the two, if the recipe user's average cooking time is shorter, ie, if the recipe user's cooking time tends to be short, the lifestyle of the recipe user is determined to be "busy".

In addition, as cooking characteristics desired by such recipe users, the frequency of occurrence of recipe attributes of "professional recipe" and "amateur recipe" is calculated, and the two are compared. is determined as one of the recipe user's lifestyles and desired cooking characteristics. The determination regarding the attribute of this recipe is similarly performed regarding the "difficulty".

In addition, the frequency of occurrence of “use of microwave oven” and “use of water oven” for “cooking content” are calculated, and the two are compared. It is determined as one of

In this way, the recipe proposal unit 101 generates a combination condition of items such as the recipe user's "lifestyle" and "cooking date and time", and items such as "cooking time", "cooking content", and "recipe attributes". Become.

Therefore, the recipe proposal unit 101 uses the characteristics of the recipe user determined in s12, that is, the "lifestyle" of the recipe user who sent the recipe proposal request, and the "cooking date and time (weekday/weekday/ holiday)”, the cooking property table 122 is referred to for a cooking property record whose values match each combination of “cooking time length”, “cooking content”, and “recipe attribute” (s13). ).

For example, among records related to a recipe user with a lifestyle of "busy and gourmet", the cooking date and time is "weekdays", the cooking time is "one hour or less", and "professional recipe, medium difficulty" by "use of microwave oven". Refers to a record of cooking characteristics, such as a recipe for

In addition, the recipe proposal unit 101 includes the specified cooking characteristics regarding the situation in which the recipe user who has the "busy and gourmet-oriented" lifestyle cooks on "weekdays" in this way as an attribute, and obtains from the recipe proposal request in s10. A recipe related to the cooking genre that is currently in use is specified in the recipe table 120 (s14).

In the case of the above-mentioned specific example, the cooking characteristics such as the cooking time of "one hour or less" and the recipe of "professional recipe, medium difficulty" with "use of microwave oven", and obtained from the recipe suggestion request in s10. In the recipe table 120, a recipe related to the cooking genre (eg, Japanese food) is specified.

Subsequently, the recipe proposal unit 101 distributes the recipe information 1001 specified in s14 to the user terminal 20 (screen 1000 in FIG. 11) (s15), and ends the process. If the recipe information 1001 is MRR (Machine Readable Recipe) format data, it is transmitted and set from the user terminal 20 to the kitchen appliance 30 and used for automatic control of the kitchen appliance 30 .

On the other hand, in the determination of s12 described above, the value acquired in s10 is the user ID, the desired cooking genre (eg Japanese food), the scheduled date and time of use (eg next Monday), and the kitchen appliance to be used. 30, that is, the specification information 381 is also included (s11: y2), the recipe proposal unit 101 sets the recipe specified in s14 as a population, and among the recipes included in this population, quantitatively The value of the cooking operation corresponding to the description specifies a value that is close to the performance upper limit in the above spec information 381 within a predetermined range (s16).

For example, if the spec information 381 obtained in s10 relates to a “microwave oven” and indicates that its performance upper limit “maximum output” is “1200 W”, among the recipes included in the above population, Regarding the cooking operation "heating operation" of the "microwave oven", specify the set output value that is smaller than the above "1200 W" within the range of "10%", that is, "1080 W to 1200 W" .

Subsequently, the recipe proposal unit 101 distributes the recipe information 1101 specified in s16 to the user terminal 20 (screen 1100 in FIG. 12) (s15), and ends the process. If the recipe information 1101 is MRR (Machine Readable Recipe) format data, it is transmitted and set from the user terminal 20 to the kitchen appliance 30 and used for automatic control of the kitchen appliance 30 .

On the other hand, in the above determination of s12, if the values acquired in s10 are only the user ID, the desired cooking genre (eg, Japanese food), and the information of the kitchen appliance 30 to be used, that is, the specification information 381 ( s11: y3), the recipe proposal unit 101 determines that the cooking genre of the recipes stored in the recipe table 120 is the one desired by the recipe user, and that the value of the cooking operation corresponding to the quantitative description in the recipe is , which is close within a predetermined range to the upper limit of performance in the specification information 381 (s17).

For example, if the desired cooking genre is "Japanese food" and the spec information 381 obtained for the recipe user's "microwave oven" indicates that the performance upper limit "maximum output" is "1200 W", the recipe Among the recipes of "Japanese food" stored in the table 120, regarding the cooking operation "heating operation" of the "microwave", the set output value, which is quantitative description, is within the range of "10%" from the above "1200 W". A small one, ie, "1080 W to 1200 W" is specified.

Also, the recipe proposal unit 101 distributes the specified recipe information 1201 to the user terminal 20 that sent the recipe proposal request (screen 1200 in FIG. 13) (s18), and ends the process. If the recipe information 1201 is MRR (Machine Readable Recipe) format data, it is transmitted and set from the user terminal 20 to the kitchen appliance 30 and used for automatic control of the kitchen appliance 30 .

Although the best mode for carrying out the present disclosure has been specifically described above, the present disclosure is not limited to this, and various changes can be made without departing from the scope of the present disclosure.

According to this embodiment, it is possible to propose appropriate recipes corresponding to specifications of kitchen appliances and personal tastes of users.

In addition, by recording a program for realizing each function constituting the recipe proposal device in a computer-readable recording medium, reading the program recorded in this recording medium into a computer system, and instructing it, the present invention can be implemented. The recipe suggestion method of the embodiment may be implemented.

Specifically, the program provides an information processing device that stores recipes with a step of acquiring spec information of a cooking appliance of a predetermined user from the user's terminal or the cooking appliance; a step of identifying a cooking operation value corresponding to the specified description that is close to the upper limit of performance in the spec information within a predetermined range; and a step of distributing the identified recipe to the terminal of the user. It is a program for realization by a computer.

In addition, the program further stores the actual cooking time, cooking content, and recipes used by the user, indicated by the usage history, in an information processing device that further stores the recipe usage history of the user. a predetermined attribute, a characteristic that the user personally desires for cooking using a recipe is determined, a recipe that includes the characteristic as an attribute is specified, and the specified recipe is delivered to the terminal of the user. It is a program for realizing the operation of executing the distributing step by a computer.

The "computer system" here includes hardware such as an OS and peripheral devices. In addition, "computer-readable recording medium" refers to portable media such as flexible disks, magneto-optical disks, ROM, CD-ROM, USB memory, and storage devices such as hard disks and SSDs built into computer systems. Say.

Furthermore, "computer-readable recording medium" means a medium that dynamically stores programs for a short period of time, such as a communication line for transmitting a program via a network such as the Internet or a communication line such as a telephone line. , such as a volatile memory inside a computer system serving as a server or a client in that case, which holds the program for a certain period of time.

In addition, the program may be for realizing part of the functions described above, or may be capable of realizing the functions described above in combination with a program already recorded in the computer system. .

1 network 10 recipe proposal device 11 storage unit 12 memory 13 calculation unit 14 input unit 15 output unit 16 communication unit 17 program 100 recipe storage unit 101 recipe proposal unit 102 usage history storage unit 120 recipe table 121 usage history table 122 cooking characteristics table 20 User terminal 21 storage unit 22 memory 23 calculation unit 24 input unit 25 output unit 26 first communication unit 27 second communication unit 28 program 29 application 30 kitchen appliance 31 storage unit 32 memory 33 calculation unit 34 input unit 35 output unit 36 first Communication unit 37 Second communication unit 38 Program 381 Spec information 39 Cooking mechanism

Claims (11)

Acquisition means for acquiring first information about a recipe used by a user;
receiving means for receiving a proposal request for making a recipe proposal to the user;
Control means for controlling to propose a recipe in response to receiving the proposal request from the receiving means,
The cooking characteristics desired by the user are determined based on the first information and the date and time when the user plans to use the proposed recipe, and a recipe is proposed from a recipe group including the cooking characteristics as an attribute. and a control means for controlling to
A server, wherein different recipes are proposed depending on whether the date and time when the user plans to use the suggested recipe is a first date and time and when it is a second date and time. 2. The method according to claim 1, wherein said control means performs control so as to propose different recipes depending on whether the user plans to use the suggested recipe on a weekday or on a holiday. Servers listed. The acquisition means acquires information about the difficulty level of the recipe used by the user from the first information,
3. The server according to claim 1, wherein said control means performs control so as to propose different recipes according to the difficulty of said recipes. 4. The server according to claim 3, wherein said control means performs control so as to suggest a recipe based on the degree of difficulty of a recipe that appears more frequently among the recipes used by said user. 5. The server according to any one of claims 1 to 4, wherein the first information includes information indicating the recipe used by the user and the date and time when the recipe was used. When the date and time when the user plans to use the proposed recipe is the first date and time, the control means proposes a recipe based on the recipe used by the user at the date and time to which the first date and time belong. If the date and time when the user plans to use the proposed recipe is the second date and time, the recipe is proposed based on the recipe used by the user at the date and time to which the second date and time belong. 6. A server according to claim 5, characterized in that it controls. When the user makes the suggestion request, the user can specify a recipe genre,
The control means controls to propose a recipe based on the first information and the date and time when the user plans to use the proposed recipe, and which belongs to a recipe genre specified by the user. 7. The server according to any one of claims 1 to 6, characterized by: 6. The server according to claim 5, wherein said first information includes information indicating the recipe used by said user and an actual cooking time for said recipe. The control means proposes a different recipe depending on whether the actual cooking time of the recipe used by the user is shorter than or longer than the average cooking time of other users who used the recipe. 9. A server according to claim 8 , characterized in that it controls. an obtaining step of obtaining first information about a recipe used by a user;
a receiving step of receiving a proposal request for making a recipe proposal to the user;
A control step for controlling to propose a recipe in response to receiving the proposal request in the receiving step,
A cooking characteristic desired by the user is determined based on the first information and the date and time when the user plans to use the proposed recipe, and a recipe is proposed from a recipe group including the cooking characteristic as an attribute. and a control step to control to
A server control method, wherein different recipes are proposed depending on whether the date and time when the user plans to use the proposed recipe is a first date and time and when it is a second date and time. the computer,
Acquisition means for acquiring first information about the recipe used by the user;
receiving means for receiving a proposal request for making a recipe proposal to the user;
Control means for controlling to propose a recipe in response to the reception of the proposal request by the reception means,
A cooking characteristic desired by the user is determined based on the first information and a date and time when the user plans to use the proposed recipe, and a recipe is proposed from a recipe group including the cooking characteristic as an attribute. control means for controlling,
function as
Different recipes are proposed depending on whether the date and time when the user plans to use the proposed recipe is a first date and time and when it is a second date and time,
program.

Images