Cooking agency matching system and cooking agency matching method

Abstract

Provided are a cooking agency matching system and method for searching for a restaurant that serves as a request destination for cooking agency so that materials owned by the restaurant can be effectively utilized. 【Solution means】The method transmits presentation recipe information indicating a recipe to a terminal device of a person available for cooking agency, receives selection recipe identification information for identifying a selected recipe selected by the person available for cooking agency from among the recipes indicated by the presentation recipe information from the terminal device of the person available for cooking agency, and based on material information indicating materials used in the selected recipe and material possession status information indicating the possession status of materials that can be used by the restaurant for cooking agency among the food ingredients owned by the restaurant, searches for a restaurant that has the materials used in the selected recipe as materials that can be used for cooking agency, and transmits cooking agency request information indicating a request for substituting the cooking using the selected recipe to a restaurant terminal device used by the searched restaurant.

Description

Technical Field

[0001] The present invention relates to a method for matching cooking agency services.

Background Art

[0002] Conventionally, housework agency services have been known. Providers of housework agency services perform housework on behalf of requesters. For example, when the housework to be performed is cooking, the provider cooks the meal, and the requester eats the cooked meal. Also, a system for matching requesters of housework agency services and providers of housework agency services is known. For example, Patent Document 1 discloses that it is possible to set search conditions including the style of workers of housework agency services and search for workers having that style.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] As a place that provides services relatively similar to cooking agency services, restaurants can be mentioned. Restaurants cook meals and provide them to customers. The materials for those meals are stored in the restaurants. When it is difficult to predict how many customers will visit the restaurant, the restaurant may store some extra materials. By making use of such food ingredients, the restaurant may be able to implement cooking agency services.

[0005] The present invention has been made in view of the above points, and an example of the problem is to provide a cooking agency matching system and a cooking agency matching method capable of searching for a restaurant that becomes a request destination for cooking agency services so that the materials possessed by the restaurant are effectively utilized.

Means for Solving the Problem

[0006] (Application Example 1) The cooking agency matching system according to this application example includes a presenting recipe information transmitting means for transmitting presenting recipe information indicating that any one or a plurality of recipes among the viewable recipes can be presented to a cooking agency user terminal device used by a cooking agency user who can use cooking agency; a selected recipe identification information receiving means for receiving, from the cooking agency user terminal device, selected recipe identification information for identifying a selected recipe selected by the cooking agency user as a recipe for which a request for cooking agency of a dish is desired among the one or more recipes indicated by the transmitted presenting recipe information; a material information indicating the materials used in the selected recipe identified by the received selected recipe identification information; and the material availability status information indicating the availability status of the materials that the restaurant can use for cooking agency among the food materials owned by the restaurant, stored in the restaurant information storage means that stores the material availability status information for each restaurant. Based on these, a restaurant search means for searching for a restaurant that has the materials used in the selected recipe as materials that can be used for cooking agency; and a cooking agency request information transmitting means for transmitting, to the restaurant terminal device used by the searched restaurant, cooking agency request information indicating a request for substituting the cooking using the selected recipe identified by the received selected recipe identification information. It is characterized by comprising these.

[0007] According to this application example, material information is stored in the material information storage means. The material information indicates the materials used in the recipe. The restaurant information storage means stores the material availability status information. The material availability status information indicates the availability status of the materials that the restaurant can use for cooking agency among the food materials owned by the restaurant. Based on the material information and the material availability status information, a restaurant that has the materials used in the selected recipe as materials that can be used for cooking agency is searched. Cooking agency request information is transmitted to the restaurant terminal used by the searched restaurant. The cooking agency request information indicates a request for substituting the cooking using the selected recipe. Therefore, it is possible to search for a restaurant that is the destination of the cooking agency request so that the materials owned by the restaurant can be effectively utilized.

[0008] (Application Example 2) In the cooking agency matching system according to this application example, the material possession status information stored in the food and beverage store information storage means indicates the possession status of the materials that the food and beverage store has in excess of the quantity of the materials that the food and beverage store has for providing dishes at the food and beverage store. The food and beverage store search means is characterized by searching for the food and beverage stores that have the materials used in the selected recipe in excess.

[0009] According to this application example, the materials that the food and beverage store has in excess can be effectively utilized.

[0010] (Application Example 3) In the cooking agency matching system according to this application example, an input material possession status information receiving means for receiving, from the food and beverage store terminal device, the input material possession status information indicating the possession status input by the food and beverage store as the possession status of the materials that the food and beverage store can use for cooking agency, and a material possession status information storage control means for storing the received input material possession status information in the food and beverage store information storage means as the material possession status information are further provided. The food and beverage store search means is characterized by performing the search based on the material possession status information stored in the food and beverage store information storage means by the material possession status information storage control means.

[0011] According to this application example, the food and beverage store can input the possession status of the materials in the food and beverage store. The input material possession status information indicating the input possession status is stored as the material possession status information. Based on the stored material possession status information, the food and beverage stores that have the materials used in the selected recipe as the materials that can be used for cooking agency are searched. Therefore, the storage status used for searching the food and beverage stores can be input by the food and beverage store.

[0012] (Application Example 4) In the cooking proxy matching system according to this application example, the restaurant information storage means further stores, for each restaurant, range-of-offer information indicating the geographical range within which the restaurant can offer the dishes cooked by the cooking proxy. The restaurant search means further searches, based on the ingredient information, the ingredient availability information, the position information of the cooking proxy user indicating the position of the cooking proxy user, and the range-of-offer information stored in the restaurant information storage means, for restaurants that have the ingredients used in the selected recipe as ingredients available for cooking by the cooking proxy and within whose range of offer the position of the cooking proxy user is located.

[0013] According to this application example, among the restaurants that have the ingredients used in the selected recipe as ingredients available for cooking by the cooking proxy, restaurants are searched for whose range of offer within which they can offer the dishes cooked by the cooking proxy includes the position of the cooking proxy user. Therefore, it is possible to search for restaurants where cooking proxy is possible in terms of geographical location.

[0014] (Application Example 5) In the cooking proxy matching system according to this application example, the restaurant information storage means further stores, for each dish that each restaurant can cook by proxy, price information indicating the price set by the restaurant as the price of the dish, and further includes price condition information receiving means for receiving price condition information indicating the conditions of the price of the dish from the cooking proxy user terminal device. The restaurant search means searches, based on the ingredient information, the ingredient availability information, and the price information stored in the restaurant information storage means, for restaurants that have the ingredients used in the selected recipe identified by the received selected recipe identification information as ingredients available for cooking by the cooking proxy and for which the price of the dish that can be cooked using the selected recipe satisfies the conditions indicated by the received price condition information.

[0015] According to this application example, a restaurant can set the price for each dish that the restaurant can cook on behalf of others. A person who can use the cooking agency service can specify the conditions for the price of the dish. Then, among the restaurants that have the materials used in the selected recipe as materials that can be used for the cooking agency service, a restaurant whose price of the dish that can be cooked with the selected recipe meets the specified conditions is searched for. Therefore, it is possible to search for a restaurant that meets the conditions specified by the person who can use the cooking agency service in terms of the price of the dish.

[0016] (Application Example 6) In the cooking agency matching system according to this application example, the restaurant search means searches for one or more restaurants that have the materials used in the selected recipe as materials that can be used for the cooking agency service, and determines the presentation order of the one or more searched restaurants; a presentation restaurant information transmission means that transmits presentation restaurant information indicating the one or more searched restaurants in an order according to the determined presentation order to the terminal device of the person who can use the cooking agency service; and a selected restaurant identification information receiving means that receives, from the terminal device of the person who can use the cooking agency service, selected restaurant identification information for identifying a selected restaurant selected by the person who can use the cooking agency service as the request destination for the cooking agency service among the one or more restaurants indicated by the transmitted presentation restaurant information. The cooking agency request information transmission means is characterized by transmitting the cooking agency request information to the restaurant terminal device used by the selected restaurant identified by the received selected restaurant identification information.

[0017] According to this application example, the presentation order of those restaurants when the searched restaurants are presented based on the presentation restaurant information is determined. A person who can use the cooking agency service and has received the presentation of one or more searched cooking agencies selects one of them as the request destination for the cooking agency service. The cooking agency request information is transmitted to the requester terminal device used by the selected restaurant. Restaurants with a higher presentation order tend to be selected as the request destination for the cooking agency service by the person who can use the cooking agency service with a higher probability. Therefore, the ease of selection of a restaurant can be controlled by the presentation order.

[0018] (Application Example 7) In the cooking agency matching system according to this application example, the material possession status information stored in the restaurant information storage means indicates the materials that the restaurant has as materials available for cooking agency and the expiration dates of such materials, and the restaurant presentation order determination means, based on the material information and the material possession status information stored in the restaurant information storage means, increases the presentation order of the restaurant with a closer expiration date of the materials used in the selected recipe.

[0019] According to this application example, the material possession status information indicates the expiration dates of the materials that the restaurant has. Based on the material possession status information of the materials used in the selected recipe, the presentation order of those restaurants when presented based on the presented restaurant information of the searched restaurants is determined. At this time, the presentation order of the restaurants with materials having a closer expiration date becomes higher. Restaurants with a higher presentation order tend to be selected as the request destination for cooking agency by those who can use cooking agency with a higher probability. Therefore, it is possible to suppress the loss of materials due to the expiration of the expiration date.

[0020] (Application Example 8) In the cooking agency matching system according to this application example, the restaurant information storage means further stores price information indicating the price set by the restaurant as the price of each dish that the restaurant can perform cooking agency for, and the restaurant presentation order determination means determines the presentation order of the searched one or more restaurants based on the price information stored in the restaurant information storage means.

[0021] According to this application example, a restaurant can set the price of each dish that the restaurant can perform cooking agency for. And based on the price of the dish that can be cooked according to the recipe selected by those who can use cooking agency, the presentation order of the searched restaurants is determined. Therefore, it is possible to control the ease of selection of restaurants based on the price set by the restaurant for the dish that can be cooked according to the recipe.

[0022] (Applicable Example 9) In the cooking proxy matching system according to this applicable example, the restaurant information storage means further stores restaurant location information indicating the location of the restaurant for each restaurant, and the restaurant presentation ranking determination means is based on the location information of the cooking proxy available person indicating the location of the cooking proxy available person and the restaurant location information stored in the restaurant information storage means. It is characterized in that the presentation ranking of restaurants closer to the location of the cooking proxy available person is made higher.

[0023] According to this applicable example, it is possible to make it easier to select a restaurant closer to the location of the cooking proxy available person as the request destination for cooking proxy.

[0024] (Applicable Example 10) In the cooking proxy matching system according to this applicable example, the restaurant information storage means further stores usage fee information indicating the amount of the usage fee paid by the restaurant for using the cooking proxy matching system, which is the amount designated by the restaurant, for each restaurant, and the restaurant presentation ranking determination means is based on the usage fee information stored in the restaurant information storage means. It is characterized in that the presentation ranking of restaurants that set a higher usage fee amount is made higher.

[0025] According to this applicable example, the restaurant using the cooking proxy matching system is required to pay a usage fee. The restaurant can specify the amount of the usage fee it pays. And the presentation ranking of restaurants that set a higher usage fee amount becomes higher. Therefore, it is possible to give more preferential treatment to restaurants that pay a higher usage fee amount in the cooking proxy matching system.

[0026] (Applicable Example 11) In the cooking proxy matching system according to this applicable example, the material possession status information stored in the material possession status information indicates the materials that the restaurant has as materials available for cooking proxy and the expiration dates of the materials, and the restaurant search means is among the restaurants that have the materials used in the selected recipe as materials available for cooking proxy. It is characterized by searching for the restaurant with the closest expiration date of the materials used in the selected recipe.

[0027] According to this application example, the material possession status information indicates the expiration date of the materials possessed by the restaurant. Based on the material possession status information of the materials used in the selected recipe, among the restaurants that have the materials used in the selected recipe as materials available for cooking agency, the restaurant with the closest expiration date of the materials is searched. The cooking agency request information is transmitted to the restaurant terminal device of the searched restaurant. Therefore, it is possible to suppress the loss of materials due to expiration.

[0028] (Application Example 12) In the cooking agency matching system according to this application example, the restaurant information storage means further stores price information indicating the price set by the restaurant as the price of the dish for each dish that the restaurant can handle for cooking agency, and the restaurant search means is based on the material information, the material possession status information, and the price information stored in the restaurant information storage means, and among the restaurants that have the materials used in the selected recipe as materials available for cooking agency, searches for the restaurant with the lowest price of the dish that can be cooked according to the selected recipe.

[0029] According to this application example, a restaurant can set the price of each dish that the restaurant can handle for cooking agency. Then, among the restaurants that have the materials used in the selected recipe as materials available for cooking agency, the restaurant that has set the lowest price as the price of the dish is searched. The cooking agency request information is transmitted to the restaurant terminal device of the searched restaurant. Therefore, it is possible to search for a restaurant that is advantageous to those who can use the cooking agency in terms of price.

[0030] (Application Example 13) In the cooking agency matching system according to this application example, restaurant location information indicating the location of the restaurant is stored for each restaurant, and the restaurant search means is based on the material information, the material possession status information, and the restaurant location information stored in the restaurant information storage means, and among the restaurants that have the materials used in the selected recipe as materials available for cooking agency, searches for the restaurant closest to the location of the person who can use the cooking agency.

[0031] According to this application example, among restaurants that have materials used in the selected recipe as materials that can be used for cooking on behalf of others, the restaurant closest to the location of the person who can use cooking on behalf of others is searched. Therefore, it is possible to search for a restaurant with a small burden of movement between the location of the restaurant and the location of the person using cooking on behalf of others.

[0032] (Application Example 14) The cooking-on-behalf matching method according to this application example is a cooking-on-behalf matching method executed by a computer. Among the viewable recipes, presentation recipe information indicating that any one or more recipes can be presented is transmitted to a terminal device of a person who can use cooking on behalf of others, which is a presentation recipe information transmission step used by the person who can use cooking on behalf of others. A selection recipe identification information receiving step of receiving, from the terminal device of the person who can use cooking on behalf of others, selection recipe identification information for identifying a selected recipe selected by the person who can use cooking on behalf of others as a recipe for which a request for cooking on behalf of others is desired among the one or more recipes indicated by the transmitted presentation recipe information. Based on the material information indicating the materials used in the selected recipe identified by the received selection recipe identification information and the material possession status information stored in a restaurant information storage means that stores, for each restaurant, the material possession status information indicating the possession status of materials that the restaurant can use for cooking on behalf of others among the food ingredients the restaurant has, a restaurant search step of searching for a restaurant that has the materials used in the selected recipe as materials that can be used for cooking on behalf of others, and a cooking-on-behalf request information transmission step of transmitting, to a restaurant terminal device used by the searched restaurant, cooking-on-behalf request information indicating a request for substituting the cooking using the selected recipe identified by the received selection recipe identification information. It is characterized by including the above.

Effect of the Invention

[0033] According to the present invention, it is possible to search for a restaurant that is a request destination for cooking on behalf of others so that the materials possessed by the restaurant are effectively utilized.

Brief Explanation of Drawings

[0034]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

Figure 18

Figure 19

Figure 20

Figure 21

Figure 22

Figure 23

Figure 24

Figure 25

Figure 26

Figure 27

Figure 28

Figure 29

Figure 30

Figure 31

Figure 32

Figure 33

Figure 34

Figure 35

Figure 36

Figure 37

Figure 38

Figure 39

Figure 40

Figure 41

Figure 42

Figure 43

Figure 44

Figure 45

Mode for Carrying Out the Invention

[0035] [1. First Embodiment] [1-1. Configuration of Communication System] Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings. First, the configuration and functional overview of the communication system S according to this embodiment will be described with reference to FIGS. 1 and 2. FIG. 1 is a diagram showing an example of the schematic configuration of the communication system S according to this embodiment. As shown in FIG. 1, the communication system S includes a health management server 1, a recipe server 2, a point management server 3, a delivery management server 4, a plurality of cooking agent terminals 5, a plurality of recipe service user terminals 6, and a plurality of health management service user terminals 7. The health management server 1, the recipe server 2, the point management server 3, the delivery management server 4, each cooking agent terminal 5, each recipe service user terminal 6, and each health management service user terminal 7 are connected to a network NW. The network NW is constructed by, for example, the Internet, a dedicated communication line (for example, a CATV (Community Antenna Television) line), a mobile communication network (including base stations, etc.), and a gateway, etc.

[0036] The health management server 1 may be, for example, a server device that executes processes for providing a health management service. The health management service may be, for example, a service for assisting in improving and maintaining the user's health. For example, the health management service may include recording the user's diet, providing recipe information according to the user's nutritional intake status, matching a person who requests cooking of a recipe with a cook, etc. The health management service may be provided, for example, through a health management application that can be installed on the health management service user terminal 7. The health management application may be an application for the user to use the health management service. Also, the health management service may be provided through a predetermined website. Note that cooking a dish corresponds to making that dish.

[0037] The health management server 1 may transmit presentation information indicating information related to the health management service to at least one of the terminal devices of the cook terminal 5, the recipe service user terminal 6, and the health management service user terminal 7 so that the terminal device can present the information. As an example of presentation, the terminal device displaying the information on the screen can be mentioned. By transmitting the presentation information, the health management server 1 may cause the terminal device to present information related to the health management service. The presentation information may be, for example, screen information. The screen information may be information for causing the terminal device to display a specific screen related to the health management service. The specific screen may include the information to be presented. The screen information may be information for causing the terminal device to display a specific screen. By transmitting the screen information, the health management server 1 may cause the terminal device to display a screen related to the health management service. For example, the screen information may be an HTML (HyperText Markup Language) document of a web page corresponding to the screen. In this case, the screen can be referred to as a web page or a page. Alternatively, the screen information may include information indicating the information to be displayed or the elements to be displayed within the screen. Alternatively, the screen information may indicate an instruction to display the screen.

[0038] The recipe server 2 may be, for example, a server device that executes processes for operating a recipe service. The recipe service may be a service that provides recipe information. Furthermore, the recipe service may be a service that enables posting of recipes. In the recipe service, information on the posted recipes may be provided. Alternatively, the recipe service may be a service that provides information on recipes registered by the operator of the recipe service or a cooking expert. The recipe service may be provided, for example, through a recipe website. The recipe website may be a website for providing the recipe service. Also, the recipe service may be provided through a recipe app that can be installed on the recipe service user terminal 6 or the health management service user terminal 7. The recipe app may be an application for the user to use the recipe service.

[0039] Similar to the health management server 1, the recipe server 2 may transmit presentation information indicating the information related to the recipe service to at least one of the terminal devices among the cooking proxy terminal 5, the recipe service user terminal 6, and the health management service user terminal 7 so that the terminal device can present the information. By transmitting the presentation information, the recipe server 2 may cause the terminal device to present the information related to the recipe service. The presentation information may be, for example, screen information. By transmitting the screen information, the recipe server 2 may cause the terminal device to display a screen related to the recipe service.

[0040] The combination of the health management server 1 and the recipe server 2 may be an example of at least any one of a cooking agency request system, a cooking agency matching system, and a recipe submission reward giving system. The cooking agency request system may be, for example, a system for a user who can use the cooking agency to request the cooking agency from a cooking agent. The cooking agency matching system may be, for example, a system for matching a cooking agency requester and a cooking agent. The cooking agency matching system may include the cooking agency request system. The recipe submission reward giving system may be, for example, a system for giving a reward to a recipe submitter. Note that the health management server 1 and the recipe server 2 may be integrated into one server device.

[0041] The point management server 3 may be a server device that manages the points held by a user in a predetermined point program. The point program may be, for example, a service available to members of a predetermined service. The predetermined service may be the point program itself. Also, for example, members of at least one of a health management service and a recipe service may be able to use the point program. Alternatively, members of a predetermined comprehensive Internet service may be able to use the point program. The comprehensive Internet service may be a collection of multiple services. The services included in the comprehensive Internet service may include, for example, services provided using a computer network such as the network NW. These services may be provided, for example, using information and communication technology. The services provided using a computer network may include services provided through a website. The point program, the health management service, and the recipe service may be included in this comprehensive Internet service. The point program may be a service that awards points to a user in response to the user using any of the services included in the comprehensive Internet service. For example, points may be awarded to a user who purchases a transaction target through or with the use of that service. The transaction target may be, for example, something that can be commercially traded. Examples of transaction targets include goods and services. Furthermore, the point program may be a service that enables the points held by a user to be used for paying the purchase price of a transaction target. For example, points may be available for all or part of the purchase price. When purchasing a transaction target using any of the services included in the comprehensive Internet service, the user may be able to use points.

[0042] The delivery management server 4 may be a server device for managing the delivery status of dishes in a service that matches, for example, an orderer who orders food delivery and a delivery person who delivers the dishes from a restaurant or the like to the orderer. Each dish delivered by the delivery person may be attached with a delivery slip. A slip number is printed on this delivery slip. The slip number is information for identifying the dish as a package.

[0043] Each proxy cooking terminal 5 may be a terminal device used by a proxy cook who can use the proxy cooking matching system. The proxy cook may be a person or a group who substitutes for cooking. The proxy cook may include, for example, a proxy cooking service provider. That is, the proxy cook may include those who substitute for cooking as a business. Also, the proxy cook may include those who substitute for cooking although not as a business. Examples of the proxy cook include housework service providers, restaurants, individuals, etc. The plurality of proxy cooks registered in the health management service may include, for example, one or more housework service providers, one or more restaurants, and one or more individuals. The plurality of proxy cooks registered in the health management service may include only a plurality of housework service providers, only a plurality of restaurants, or only a plurality of individuals. When the proxy cook includes one or more restaurants, the "proxy cook" included in the terms described in this specification can all be read as "restaurant". Each proxy cooking terminal 5 may have applications such as a web browser and an email client installed.

[0044] Each recipe service user terminal 6 may be a terminal device used by a user of the recipe service. The user of the recipe service is referred to as a recipe service user. The recipe service user may be able to view recipes in the recipe service. Also, the recipe service user may be able to post recipes to the recipe service. Among the recipe service users, users who will post recipes and users who have posted recipes are referred to as recipe posters. The recipe service user terminal 6 used by a recipe poster is referred to as a recipe poster terminal 6. Each recipe service user terminal 6 may have applications such as a web browser and an email client installed. It may be possible to install a recipe app on a predetermined type of recipe service user terminal 6.

[0045] Each health management service user terminal 7 may be a terminal device used by a user of the health management service. The user of the health management service is referred to as a health management service user. The health management service user may be a user who can record meals, a user who can view recipes, and a user who can use a cooking agency system or a cooking agency matching system to have recipes cooked on their behalf. A user who can view recipes is referred to as a viewer. A user who can use a cooking agency is referred to as a cooking agency user. A user who requests a cooking agency is referred to as a cooking agency requester. A user who uses a cooking agency is referred to as a cooking agency user. A cooking agency requester may be a cooking agency user. Each health management service user terminal 7 may have applications such as a web browser and an email client installed. It may be possible to install a health management app on a predetermined type of health management service user terminal 7.

[0046] At least a part of the users of the health management service may also be users of the recipe service. Also, at least a part of the users of the recipe service may be users of the health management service. For example, the users of the aforementioned comprehensive Internet service may be able to use both the health management service and the recipe service. Alternatively, the user may be able to register separately for each of the health management service and the recipe service. Therefore, depending on the current situation of the user, the user may become any one of a health management service user, a recipe service user, and a recipe submitter. Accordingly, the terminal device used by the user may also become any one of the health management service user terminal 7, the recipe service user terminal 6, and the recipe submitter terminal 6.

[0047] Examples of each of the cooking agent terminal 5, the recipe service user terminal 6, and the health management service user terminal 7 include a personal computer, a set-top box, a smartphone, other mobile phones, a wearable computer, a tablet computer, a PDA (Personal Digital Assistant), etc.

[0048] FIG. 2 is a diagram showing an example of the processing flow in the present embodiment. As shown in FIG. 2, the recipe submitter operates the recipe submitter terminal 6 to submit a recipe (step S1). The recipe server 2 stores the information of the submitted recipe. On the other hand, the health management service user operates the health management service user terminal 7 to input the content of the meal consumed by the user. The health management service user terminal 7 transmits meal record information indicating the record of the meal to the health management server 1 (step S2). The health management server 1 stores the meal record information. The health management server 1 requests the recipe server 2 to search for a recipe for a dish according to the nutritional intake status of the health management service user based on the meal record information (step S3). The nutritional intake status may indicate which nutrients the health management service user has consumed. Also, the nutritional intake status may indicate the amount of nutrients the health management service user has consumed. It is possible to specify the nutritional intake status by diet from the meal record information. The recipe server 2 searches for a recipe corresponding to the request from the health management server 1 and transmits the result of the search to the health management server 1 (step S4). The health management server 1 transmits information on the recipe for a dish according to the nutritional intake status to the health management service user terminal 7 based on the search result (step S5).

[0049] A health management service user who has viewed one or more recipes selects one of those recipes as the recipe for the dish for which they request cooking assistance. In response to the selection, the health management service user terminal 7 sends a cooking assistance request to the health management server 1 (step S6). The cooking assistance request may be information indicating a request for cooking assistance from the health management server 1. The health management server 1 searches for one or more cooks who meet the conditions of the destination for the cooking assistance of the dish of the recipe selected by the cooking assistance requester (step S7). The health management server 1 sends the cooking assistance request information to the cook terminal 5 of the cook who is the destination for the cooking assistance among the searched cooks (step S8). The cooking assistance requester may select the cook who is the destination for the cooking assistance, or the health management server 1 may determine the cook who is the destination for the cooking assistance. The cooking assistance request information may be information indicating a request for cooking assistance to the cook. The cooking assistance request information may include information indicating the content of the request. When the cook who has viewed the cooking assistance request information determines that cooking assistance is possible, the cook performs an operation to accept the request for cooking assistance. In response to this operation, the cook terminal 5 sends acceptance information to the health management server 1 (step S9). The acceptance information may be information indicating that the cook has accepted the request for cooking assistance. When the health management server 1 receives the acceptance information, the health management service user may become the cooking assistance requester and the user of the cooking assistance. The cook starts cooking according to the recipe selected by the cooking assistance requester. If the selected cook performs an operation to reject the request for cooking assistance, the health management server 1 may send the cooking assistance request information to the cook terminal 5 of another cook among the searched cooks.

[0050] The health management server 1 that has received the reception information from the cooking agent terminal 5 transmits delivery request information to the delivery management server 4 (step S10). The delivery request information may be information indicating a request for delivering a dish from the cooking agent to the health management service user who is the cooking agency requester. The delivery management server 4 transmits information for instructing the delivery of the dish to a terminal device (not shown) used by the delivery person. The delivery person receives the dish from the cooking agent and delivers the dish to the cooking agency requester (step S11). After receiving the reception information, the health management server 1 grants a reward to the poster of the recipe of the delivered dish (step S12). Examples of the reward include points in a point program, coupons, electronic money, cash, and the like. In the present embodiment, it is assumed that points are granted as the reward.

[0051] In the example shown in FIG. 2, it is possible to request the cooking agency of the dish of the recipe according to the nutritional intake status of the health management service user. However, for example, the recipe server 2 may search for a recipe that satisfies the conditions specified by the recipe service user. Examples of the specifiable conditions include the title of the recipe, the name of the dish, the name of the ingredients, other keywords, the category of the recipe, and the like. Then, the recipe server 2 or the health management server 1 may be configured to be able to request the cooking agency of the dish of any recipe from among the recipes that satisfy the specified conditions. Also, instead of the delivery person delivering the dish, the cooking agent may go to the location of the cooking agency requester and perform the cooking agency there. In this case, the cooking agent may prepare the ingredients of the recipe, or the cooking agency requester may prepare the ingredients.

[0052] [1-2. Configuration of Server Device] [1-2-1. Health Management Server] Next, the configuration of the health management server 1 will be described with reference to FIGS. 3 to 6. FIG. 3 is a block diagram showing an example of the schematic configuration of the health management server 1 according to the present embodiment. As shown in FIG. 3, the health management server 1 includes a system control unit 11, a system bus 12, an input / output interface 13, a storage unit 14, and a communication unit 15. The system control unit 11 and the input / output interface 13 are connected via the system bus 12.

[0053] The system control unit 11 is composed of a CPU (Central Processing Unit) 11a, a ROM (Read Only Memory) 11b, a RAM (Random Access Memory) 11c, and the like.

[0054] The input / output interface 13 performs interface processing between the storage unit 14 and the communication unit 15 and the system control unit 11.

[0055] The storage unit 14 is constituted by, for example, a hard disk drive or the like. This storage unit 14 may function as an example of at least one of the means for storing food preparer information and the means for storing restaurant information. The means for storing food preparer information may store food preparer information for each food preparer. The food preparer information may be information regarding the food preparer. The means for storing restaurant information may store restaurant information for each restaurant. The restaurant information may be information regarding the restaurant. The food preparer information of the restaurant may correspond to the restaurant information. In the storage unit 14, databases such as a user DB 14a, a nutritional intake standard DB 14b, a food and drink DB 14c, a meal record DB 14d, a food preparer DB 14e, a cookable dish DB 14f, a status DB 14g of ingredients available for food preparation, and a food preparation request DB 14h may be stored. "DB" is an abbreviation for database. At least one of these databases may be stored not in the health management server 1 but in the recipe server 2 or another server device. The health management server 1 may be able to access the database via the server device. Also, the recipe server 2 may be able to access the database stored in the storage unit 14 via the health management server 1.

[0056] FIG. 4 is a diagram showing an example of information stored in the database of the health management server 1. User information regarding each health management service user may be stored in the user DB 14a. For example, as shown in FIG. 4, the user DB 14a may store user ID, name, gender, date of birth, address, weight, email address, and importance information, etc. as user information, associated with each other. The user ID may be identification information for identifying a health management service user in the health management service. This user ID may be, for example, identification information for identifying a user of an integrated Internet service. The importance information may be information indicating what a health management service user emphasizes in a diet for health. The importance information may be set to either "calorie emphasis" or "balance emphasis", for example. "Calorie emphasis" indicates that a health management service user emphasizes not exceeding calories. "Balance emphasis" indicates that a health management service user emphasizes the nutritional balance even if the calories exceed. For example, a health management service user may be able to set the information included in the user information using a health management application. The health management server 1 may store the user information including the set information in the user DB 14a.

[0057] In the nutritional intake standard DB14b, nutritional intake standard information indicating the standards for nutritional intake for health may be stored for each piece of predetermined information regarding the health management service user or for each combination of predetermined information. The predetermined information may be, for example, information indicating the physical characteristics of the health management service user. Examples of the predetermined information include gender, age, and weight range. The combination of the predetermined information may be, for example, a combination of any two pieces of information or a combination of all the information among gender, age, and weight range. Hereinafter, as an example, it is assumed that the nutritional intake standard information is stored for each combination of gender, age, and weight range. The standards for nutritional intake may be, for example, standards, targets, guidelines, or recommendations for the intake amounts of nutrients. The standards for nutritional intake indicated by the nutritional intake standard information may be the standards for nutritional intake for each predetermined length of the reference period. The length of the reference period may be one day or other lengths. For example, as shown in FIG. 4, in the nutritional intake standard DB14b, as the nutritional intake standard information, gender, age, weight range, nutritional intake amount standard information, calorie limit, etc. may be stored in association with each other. The nutritional intake amount standard information may be information indicating the standards for the nutritional intake amount. For example, the nutritional intake amount standard information may be information indicating the standards for the nutritional intake amount within the reference period by the health management service user specified by the combination of gender, age, and weight range. The amount corresponding to the standard for the nutritional intake amount is referred to as the reference amount. Examples of the reference amount include the target amount, guideline amount, recommended amount, required amount, and tolerance upper limit amount, etc. Here, the tolerance upper limit amount may indicate the upper limit of the habitual intake amount that is considered to have no risk of causing health problems. The standards for the nutritional intake amount may be set for each of one or more predetermined nutrients. The predetermined nutrients are referred to as target nutrients. Examples of the target nutrients include protein, lipid, potassium, calcium, magnesium, phosphorus, iron, zinc, selenium molybdenum, vitamin A, vitamin C, vitamin D, vitamin E, vitamin B1, vitamin B2, vitamin B&, vitamin B12, folic acid, salt, etc. Note that the information about a specific target nutrient may be substituted with the information about the nutrients belonging to the lower level of that target nutrient.Nutrient intake reference information may include any one of a target amount, a guideline amount, a recommended amount, and a requirement amount for each target nutrient. Further, the nutrient intake reference information may include a tolerable upper intake level in addition to any one of the target amount, the guideline amount, the recommended amount, and the requirement amount for at least one target nutrient. What kind of reference amount the nutrient intake reference information includes may be determined in advance for each target nutrient. The reference for nutrient intake may indicate that the nutrient intake is within a predetermined range. For example, the reference for nutrient intake may be that the intake amount is equal to or greater than a predetermined lower limit amount, or that the intake amount is equal to or less than a predetermined upper limit amount, or that the intake amount is equal to or greater than a predetermined lower limit amount and equal to or less than a predetermined upper limit amount. Which of these conditions is used may be determined in advance, for example, according to the type of reference amount or the target nutrient. The nutrient intake reference information may include at least one of a lower limit amount and an upper limit amount according to what kind of reference amount is used. For example, the tolerable upper intake level may correspond to the upper limit amount. Also, any one of the reference amounts of the target amount, the guideline amount, the recommended amount, and the requirement amount may include a lower limit amount and an upper limit amount. However, the reference amount for a specific target nutrient may include only one of the lower limit amount and the upper limit amount. For example, the nutrient intake reference information may include only the upper limit amount as the target amount of salt. The calorie upper limit may indicate the maximum value of calories that a health management service user specified by a combination of gender, age, and weight range may consume within a reference period.

[0058] Food and drink DB 14c may store food and drink information regarding each food and drink. For example, in food and drink DB 14c, as food and drink information, a food and drink ID, a food and drink category ID, a food and drink name, food and drink nutrient amount information, food and drink calories, and cooking price, etc. may be stored in association with each other. The food and drink ID may be identification information for identifying the food and drink. The food and drink category ID may be identification information for identifying the category to which the food and drink belongs. The food and drink name may be text indicating the name of the food and drink. For example, the food and drink name may include text indicating one or more ways of referring to the food and drink. The food and drink nutrient amount information is information regarding the nutrients contained in the food and drink. For example, the food and drink nutrient amount information may include the content of the target nutrient in the meal for each target nutrient. The food and drink nutrient amount information may indicate the amount generally or on average contained in the food and drink as the nutrient content. The food and drink calories may indicate the calories ingested with the food and drink. The food and drink calories may indicate the calories generally or on average ingested with the food and drink. The cooking price may be valid if the food and drink is a dish for which a request for cooking agency is possible. The cooking price may indicate the price of the dish. The cooking price may indicate the fee for cooking agency of the dish. The cooking price may include the material cost.

[0059] The dietary record DB 14d may store dietary record information that can identify the food and drink included in the diet as a record of the diet consumed by each health management service user. For example, as shown in FIG. 4, the dietary record DB 14d may store, as dietary record information, a user ID, a meal date, a meal category, a list of food and drink, dietary nutrient intake information, and dietary calories, etc., in association with each other. The user ID may indicate the health management service user who consumed the meal. The meal date may indicate the date on which the meal was consumed. The meal category is identification information for identifying the category of the consumed meal. The meal category may be a category in which the meal is classified according to the approximate time zone when the meal is consumed. For example, as meal categories, there may be breakfast, lunch, and dinner. Also, as meal categories, there may be snacks, etc. The list of food and drink is a list of food and drink IDs of the food and drink included in the meal. The dietary nutrient intake information is information regarding the nutrients consumed in the meal. For example, the dietary nutrient amount information may include the content of the target nutrient in the meal for each target nutrient. The dietary calories may indicate the calories consumed in the meal.

[0060] In the cooking agent DB14e, cooking agent basic information regarding cooking agents registered in the health management service as cooking agents who can use the cooking agency matching system may be stored for each cooking agent. The cooking agent basic information may be an example of cooking agent information and restaurant information. For example, as shown in FIG. 4, in the cooking agent DB14e, as cooking agent basic information, a cooking agent ID, a cooking agent name, an agent category ID, an address, a telephone number, an email address, corresponding area information, a cooking agent image URL (Uniform Resource Locator), appeal information, etc. may be stored in association with each other. The cooking agent ID may be identification information for identifying the cooking agent. The cooking agent name may indicate the name of the cooking agent. The agent category ID may be identification information for identifying the category of the cooking agent. Examples of the category of the cooking agent include housework agents, restaurants, individuals, etc. The corresponding area information may indicate one or more corresponding areas where the cooking agent can provide cooking. Examples of the corresponding area include municipalities, town blocks, etc. The area where the cooking agent can provide cooking usually includes the address of the cooking agent. For example, the cooking agent may be able to set the information included in the cooking agent basic information using an application such as a web browser. The health management server 1 may acquire the set information from the cooking agent terminal 5 and store the cooking agent basic information including the acquired information in the cooking agent DB14e. Note that the corresponding area information may not be set by the cooking agent, and corresponding area information assuming that the address of the cooking agent is in that area may be stored in advance in the storage unit 14 for each area. The cooking agent image URL may be identification information for identifying the image data of the cooking agent image. The cooking agent image may be an image related to the cooking agent. For example, the cooking agent image may be an image of the exterior or interior of the base, office, or business office of the cooking agent. Also, the cooking agent image may be an image of the cooking agent itself. Examples of the format of the image data include JPEG (Joint Photographic Experts Group), PNG (Portable Network Graphics), etc.The appeal information may be text indicating a statement for the cooking agent to appeal to the health management service user.

[0061] In the cookable dish DB 14f, cookable dish information regarding dishes that the cooking agent can cook may be stored for each cooking agent. For example, in the cookable dish DB 14f, cookable dish information may be stored for each combination of a cooking agent and a cookable dish. The cookable dish information may be an example of cooking agent information and food service information. For example, as shown in FIG. 4, in the cookable dish DB 14f, as cookable dish information, a cooking agent ID, a food and drink ID, etc. may be stored in association with each other. The food and drink ID may indicate a food and drink as a dish that can be cooked by the cooking agent indicated by the cooking agent ID. When the cooking agent is a food service, the dishes that the food service can cook may be dishes included in the menu of the food service, or may be dishes not included in the menu.

[0062] FIG. 5 is a diagram showing an example of a cookable dish. For example, as shown in FIG. 5, assume that the cooking agents include food services A and B. The dishes that can be cooked at food service A include tomato spaghetti, Napolitan, pomodoro, meat spaghetti, and arrabiata. The dishes that can be cooked at food service B include mushroom cream spaghetti, tomato sauce spaghetti, pescatore, arrabiata, and carbonara. Thus, the dishes that can be cooked may differ depending on the cooking agent.

[0063] In the cooking agency available material possession status DB14g, possession status information indicating the possession status of materials that can be used by a cooking agent may be stored for each cooking agent. For example, in the cooking agency available material possession status DB14g, possession status information may be stored for each combination of a cooking agent and a material. The possession status information may be an example of cooking agent information and restaurant information. What materials can be used for cooking agency or how much quantity of materials can be used for cooking agency may be determined by each cooking agent. The possession status information of a restaurant may indicate the possession status of the materials that the restaurant has in excess of the quantity of materials that the restaurant has for providing dishes in that restaurant among the materials that the restaurant has. As shown in FIG. 4, for example, in the cooking agency available material possession status DB14g, as possession status information, a cooking agent ID, a material ID, a possession status, etc. may be stored in association with each other. The possession status may indicate whether the cooking agent indicated by the cooking agent ID has the material indicated by the material ID or how much quantity is possessed. For example, the possession status may be set to either "Yes" or "No". "Yes" may indicate that the material is possessed by the cooking agent as a material that can be used for cooking agency. "No" may indicate that the material is not possessed by the cooking agent as a material that can be used for cooking agency. For example, the possession status may indicate in quantity how much of the material is possessed as a material that can be used for cooking agency. For example, the quantity may be the number, weight, or volume. The initial value of the possession status may be, for example, "No" or 0. Note that the possession status indicating "Yes" or "No" and the possession status indicating quantity may be stored in the cooking agency available material possession status DB14g in a mixed manner. Note that the possession status information about commonly used seasonings such as salt, sugar, and pepper may not be stored in the cooking agency available material possession status DB14g.

[0064] Figs. 6(a) and 6(b) are diagrams showing an example of the possession status of materials that can be used for proxy cooking. As shown in Fig. 6(a), assume that the proxy cook includes restaurant C. In Fig. 6(a), the possession status of each material is shown as either having or not having it. For example, restaurant C possesses carrots, leeks, and potatoes as materials that can be used for proxy cooking. Restaurant C may possess these materials in excess. Therefore, apart from the materials that can be used for proxy cooking, restaurant C may possess carrots, leeks, and potatoes as materials held for use in normal business. Restaurant C does not possess any of daikon radish, tomatoes, and onions as materials that can be used for proxy cooking. Restaurant C may possess all of at least one of daikon radish, tomatoes, and onions for use in normal business. Or, restaurant C may not originally use at least one of daikon radish, tomatoes, and onions in normal business.

[0065] In Fig. 6(b), the possession status of each material is shown by quantity. At restaurant C, the number of daikon radishes in stock is 0, the number of carrots in stock is 4, the number of tomatoes in stock is 0, the number of onions in stock is 0, the number of leeks in stock is 5, and the number of potatoes in stock is 4. Therefore, restaurant C possesses carrots, leeks, and potatoes as materials that can be used for proxy cooking.

[0066] The cooking agency request DB 14h may store cooking agency request record information regarding the cooking agency indicated by each cooking agency request information sent to the cooking agency 5. For example, as shown in FIG. 4, the cooking agency request DB 14h may store, as cooking agency request record information, a request ID, a requester ID, a destination cooking agency ID, a recipe ID, a recipe poster ID, a request date and time, a cooking price, the number of servings, a delivery fee, an amount to be paid, a request status, an invoice number, etc., in association with each other. The request ID may be identification information for identifying a request for a cooking agency. The requester ID may be the user ID of the cooking agency requester. The destination cooking agency ID may be the cooking agency ID of the cooking agency that is the destination of the cooking agency request. The recipe ID may be identification information for identifying the recipe of the dish for which the cooking agency is requested. The recipe poster ID may be the user ID of the recipe poster who posted the recipe. The request date and time may indicate the date and time when the cooking agency request information was sent. The cooking price may indicate the price per serving of the dish for which the cooking agency is requested. The number of servings may indicate how many servings of the dish are requested to be cooked. The delivery fee may indicate the fee for delivering the cooked dish from the cooking agency to the cooking agency requester. For example, the delivery fee may be set uniformly. Alternatively, the delivery fee may be determined according to the combination of the region where the cooking agency requester is located and the region where the cooking agency is located. The amount to be paid may indicate the amount of the fee that the cooking agency requester should pay to the health management service for the cooking agency. For example, the amount to be paid may be the total of the total price calculated by multiplying the cooking price by the number of servings and the delivery fee. The request status may indicate the status of the request for the cooking agency indicated by the request ID. For example, the request status may be set to any one of "request sent", "request rejected", "request received", "in delivery", and "delivery completed". "Request sent" may indicate that after the cooking agency request information is sent, the cooking agency that is the destination of the cooking agency request has not selected whether to accept the request. "Request rejected" may indicate that the request for the cooking agency has been rejected by the cooking agency."Accepted Request" may indicate that a request for cooking agency has been received by the cooking agent, and the dish to be cooked has not been picked up by the delivery person from the cooking agent. "In Delivery" may indicate that the dish to be cooked is in the process of delivery. "Delivery Completed" may indicate that the delivery of the dish to be cooked has been completed. The invoice number may indicate the number of the delivery invoice attached to the dish when the delivery person picks up the dish to be cooked from the cooking agent.

[0067] The storage unit 14 may further store the image data of each cooking agent image in association with the cooking agent image URL. Further, the storage unit 14 may store various programs such as an operating system, a DBMS (Database Management System), and a health management server program. The health management server program may be a program that causes the system control unit 11 to execute various processes related to the health management service. The health management server program may be obtained, for example, from another device via the network NW, or may be recorded on a recording medium such as a magnetic tape, an optical disk, or a memory card and read via a drive device.

[0068] The communication unit 15 may be configured by, for example, a network interface card or the like. The communication unit 15 may connect to a device different from the health management server 1 via the network NW and control the communication state with the connected device.

[0069] [1-2-2. Recipe Server] Next, the configuration of the recipe server 2 will be described with reference to FIGS. 7 and 8. FIG. 7 is a block diagram showing an example of the schematic configuration of the recipe server 2 according to the present embodiment. As shown in FIG. 7, the recipe server 2 includes a system control unit 21, a system bus 22, an input / output interface 23, a storage unit 24, and a communication unit 25. The system control unit 21 and the input / output interface 23 are connected via the system bus 22.

[0070] The system control unit 21 is composed of a CPU 21a, a ROM 21b, a RAM 21c, etc.

[0071] The input / output interface 23 performs interface processing between the storage unit 24 and the communication unit 25 and the system control unit 21.

[0072] The storage unit 24 is composed of, for example, a hard disk drive or the like. This storage unit 14 may function as an example of at least one of the recipe information storage means and the material information storage means. The recipe information storage means may store recipe information for each recipe. The recipe information may be information indicating a recipe. The material information storage means may store material information for each recipe. The material information may be information indicating materials used in a recipe. The recipe information may include the material information. For example, databases such as a recipe DB 24a and a material DB 24b may be stored in the storage unit 14. At least one of these databases may be stored not in the recipe server 2 but in the health management server 1 or another server device. The recipe server 2 may be able to access the database via the server device. Also, the health management server 1 may be able to access the database stored in the storage unit 24 via the recipe server 2.

[0073] FIG. 8 is a diagram showing an example of information stored in the database of the recipe server 2. The recipe DB 24a may store recipe information indicating each recipe posted to the recipe service. For example, as shown in FIG. 8, the recipe DB 24a may store, as recipe information, a recipe ID, a user ID, a recipe category ID, a recipe title, a cooking image URL, a recipe comment, the number of people corresponding to the ingredients, ingredient information, cooking method information, a cooking method image URL, a dish name, a food and beverage ID, recipe dish nutrient amount information, and the calorie of the recipe dish, etc., in association with each other. The recipe ID may be identification information for identifying the posted recipe. The user ID may be identification information for identifying the recipe poster who posted the recipe in the recipe service. This user ID may be identification information for identifying a user of the comprehensive Internet service. In this case, the user ID of the recipe service may be the same as the user ID of the health management service. The recipe category ID may be identification information for identifying the category of the recipe. The recipe title may be text indicating the title of the recipe. The recipe title may include the dish name of the dish cooked by the recipe. The cooking image URL may be identification information for identifying the image data of the cooking image. The cooking image may be an image of the dish cooked by the recipe. The recipe comment may be text indicating a simple explanation of the recipe by the recipe poster. The number of people corresponding to the ingredients may indicate how many servings the amount of ingredients in the recipe information is for. The ingredient information may be information about the ingredients used in the recipe. For one recipe, one or more pieces of ingredient information may be stored. Each piece of ingredient information may include, for example, the ingredient name and the amount. The ingredient name may be text indicating the name of the ingredient. The amount may be text indicating how much quantity of the ingredient is required. The cooking method information may be text indicating at least one of the cooking method and the procedure. The cooking method image URL may be identification information for identifying the image data of the cooking method image. The cooking method image may be an image showing the cooking method according to the recipe. The dish name is the name of the dish cooked by the recipe.If the recipe title includes the name of the dish, the recipe information may not include a name of the dish separate from the recipe title. The food and beverage ID may indicate the food and beverage of the dish that can be cooked by the recipe. The recipe dish nutrient amount information may be information that enables identification of the amount of nutrients contained in the dish that can be cooked by the recipe. For example, the food and beverage nutrient amount information may include, for each target nutrient, the content of the target nutrient in one serving of the dish. The recipe dish calorie may indicate the calories ingested in one serving of the dish of the recipe.

[0074] The ingredient DB 24b may store ingredient basic information regarding each ingredient of the dish. For example, as shown in FIG. 8, the ingredient DB 24b may store, as ingredient basic information, an ingredient ID, an ingredient category ID, an ingredient name, ingredient nutrient amount information, and an ingredient calorie, etc., in association with each other. The ingredient ID may be identification information for identifying the ingredient. The ingredient category ID may be identification information for identifying the category to which the ingredient belongs. The ingredient name may be text indicating the name of the ingredient. For example, the ingredient name may include text indicating one or more ways of referring to the ingredient. The ingredient nutrient amount information may indicate the amount of nutrients contained in the ingredient. For example, the ingredient nutrient amount information may include, for each target nutrient, the content of the target nutrient in the ingredient per unit quantity. The ingredient calorie may indicate the calories ingested per unit quantity of the ingredient.

[0075] In the storage unit 24, image data of cooking images for each recipe may be stored in association with the cooking image URLs. Also, in the storage unit 24, image data of cooking method images for each recipe may be stored in association with the cooking method image URLs. Further, in the storage unit 24, screen information of recipe screens for each recipe may be stored in association with the URLs of the screen information. The URL of the screen information of the recipe screen may include, for example, a recipe ID. The recipe screen may be a screen on which information of a specific recipe is displayed. The recipe screen may display information included in the recipe information. This screen information may be, for example, an HTML document, information indicating elements included in the screen, or information indicating instructions for displaying the screen. For example, each time the recipe information of a posted recipe is stored in the recipe DB 24a, the recipe server 2 may generate screen information of the recipe screen based on the recipe information and store the generated screen information in the storage unit 24.

[0076] Furthermore, various programs such as an operating system, a DBMS, and a recipe server program may be stored in the storage unit 24. The recipe server program may be a program that causes the system control unit 21 to execute various processes related to the recipe service. The recipe server program may be obtained, for example, from another device via the network NW, or may be recorded on a recording medium such as a magnetic tape, an optical disk, or a memory card and read via a drive device.

[0077] The communication unit 25 may be configured by, for example, a network interface card or the like. The communication unit 25 may connect to a device different from the recipe server 2 via the network NW and control the communication state with the connected device.

[0078] [1-2-3. Point Management Server] Next, the configuration of the point management server 3 will be described with reference to FIGS. 9 and 10. FIG. 9 is a block diagram showing an example of the schematic configuration of the point management server 3 according to the present embodiment. As shown in FIG. 9, the point management server 3 includes a system control unit 31, a system bus 32, an input / output interface 33, a storage unit 34, and a communication unit 35. The system control unit 31 and the input / output interface 33 are connected via the system bus 32.

[0079] The system control unit 31 is composed of a CPU 31a, a ROM 31b, a RAM 31c, and the like.

[0080] The input / output interface 33 performs interface processing between the storage unit 34 and the communication unit 35 and the system control unit 31.

[0081] The storage unit 34 is composed of, for example, a hard disk drive or the like. Databases such as an available point DB 34a may be stored in this storage unit 34. FIG. 10 is a diagram showing an example of information stored in the database of the point management server 3. Information regarding the available points of each user may be stored in the available point DB 34a. The available points may be the points held by the user that can be used for paying the purchase amount of the transaction target in the point program. For example, as shown in FIG. 10, the available point DB 34a may store the user ID, the number of available points, etc. in association with each other. The number of available points may indicate the number of available points held by the user indicated by the user ID.

[0082] The storage unit 34 may further store various programs such as an operating system, a DBMS, and a point management server program. The point management server program may be a program that causes the system control unit 31 to execute various processes related to points of the point program. The point management server program may be acquired, for example, from another device via the network NW, or may be recorded on a recording medium such as a magnetic tape, an optical disk, or a memory card and read via a drive device.

[0083] The communication unit 35 may be configured by, for example, a network interface card or the like. The communication unit 35 may be connected to a device different from the point management server 3 via the network NW and control the communication state with the connected device.

[0084] [1-3. Functional Overview] [1-3-1. Health Management Server] Next, the functional overview of the system control unit 11 in the health management server 1 will be described with reference to FIGS. 11 and 12. FIG. 11 is a diagram showing an example of a functional block of the system control unit 11 in the health management server 1 according to the present embodiment. The system control unit 11 functions as, for example, a cooking proxyable recipe information receiving unit 1101, a cooking proxyable recipe information storage control unit 1102, a cooking proxyable material possession status information receiving unit 1103, a cooking proxyable material possession status storage control unit 1104, a nutritional intake status information acquisition unit 1105, a nutritional intake amount standard information acquisition unit 1106, a recipe information search control unit 1107, a presented recipe information transmission unit 1108, a selected recipe identification information receiving unit 1109, a cooking proxy search unit 1110, a cooking proxy presentation order determination unit 1111, a presented cooking proxy information transmission unit 1112, a selected cooking proxy identification information receiving unit 1113, a cooking proxy request information transmission unit 1114, a reception information receiving unit 1115, a delivery request information transmission unit 1116, a reward granting unit 1117, etc. when the CPU 11a reads and executes various program codes included in the health management server program as shown in FIG. 11.

[0085] [1-3-1-1. Information Registration by Cooking Proxy] The cookable dish information receiving unit 1101 may receive cookable dish information from the cook agent terminal 5. The cookable dish information may indicate the dishes that can be cooked by the cook agent. For example, the cookable dish information may include identification information for identifying the dish for one or more cookable dishes. Examples of this identification information include the food and beverage ID of the dish and the dish name. The cookable dish information receiving unit 1101 may cause the cook agent terminal 5 to display a cookable registration screen, for example, by transmitting the screen information of the cookable registration screen to the cook agent terminal 5. The cookable registration screen may be a screen for registering cookable dishes. On the cookable registration screen, the cook agent may be able to input search conditions for the dishes. Examples of the search conditions include the dish name (food and beverage name), the category of the dish (food and beverage), etc. The health management server 1 may search for dishes that meet the input search conditions. For example, it may be possible to determine whether the food and beverage is a dish from the category of each food and beverage. The cookable dish information receiving unit 1101 may cause a list of the searched dishes to be displayed on the cookable registration screen, for example, by transmitting the information of the searched dishes to the cook agent terminal 5. The cook agent may select one or more cookable dishes from the list. The cook agent terminal 5 may transmit cookable dish information including, for example, a list of the food and beverage IDs of the selected dishes and the cook agent ID of the cook agent to the health management server 1.

[0086] The cookable dish information storage control unit 1102 may store the cookable dish information received by the cookable dish information receiving unit 1101 in the storage unit 14 in association with the cook agent. For example, the cookable dish information storage control unit 1102 may store each food and beverage ID included in the cookable dish information in the cookable dish DB 14f in association with the cook agent ID included in the cookable dish information.

[0087] The cooking agency available material possession status information receiving unit 1103 may receive cooking agency available material possession status information from the cooking agency agent terminal 5. The cooking agency available material possession status information may be information indicating the possession status of materials that can be used by the cooking agency agent for cooking agency. The cooking agency available material possession status information may be information indicating the possession status input by the cooking agency agent. The cooking agency available material possession status information may include, for example, a material ID and the possession status of the material indicated by the material ID. The possession status may be indicated, for example, by the presence or absence of the material. Alternatively, the possession status may be indicated by the quantity of the material. The cooking agency available material possession status information receiving unit 1103 may cause the cooking agency agent terminal 5 to display a cooking agency available material possession status setting screen, for example, by transmitting the screen information of the cooking agency available material possession status setting screen to the cooking agency agent terminal 5. The cooking agency available material possession status setting screen may be a screen for setting or changing the possession status of materials that can be used for cooking agency. A list of materials may be displayed on the cooking agency available material possession status setting screen, for example. For example, a list of materials pre-registered by the cooking agency agent as materials for managing the possession status may be displayed. The cooking agency agent may change the possession status of at least one of the materials displayed on the cooking agency available material possession status setting screen. The cooking agency agent terminal 5 may transmit cooking agency available material possession status information including the material ID of the material whose possession status has been changed, the changed possession status, and the cooking agency agent ID of the cooking agency agent to the health management server 1.

[0088] When the cooking agent is a restaurant, the information on the availability status of materials that can be used for cooking agency may be surplus material information. The surplus material information may indicate the holding status of the materials that the restaurant has in excess. For example, the surplus material information may indicate the holding status of the materials that the restaurant has in excess beyond the quantity of the materials that the restaurant has for providing dishes in the restaurant. Also, for example, the surplus material information may be information indicating the holding status of the materials among the materials held by the restaurant that are not planned to be used for providing dishes in the restaurant. Also, for example, the surplus material information may be information indicating the holding status of the materials that are not planned to be used for the restaurant to cook dishes according to the recipe determined by the restaurant itself. A restaurant, as its main business, cooks dishes according to the recipe determined by the restaurant for the customers who come to the restaurant and provides the cooked dishes to the customers. Therefore, the materials in the restaurant for providing dishes may not be included in the materials that can be used for cooking agency. For example, even if it is a material purchased by the restaurant to provide dishes to the customers of the restaurant, depending on the subsequent customer arrival situation, the material may be expected to be surplus. Also, the restaurant may have a margin in the quantity of materials to be purchased. In that case, there may be surplus materials from the beginning. The restaurant may input the holding status into the cooking agency available material holding status setting screen assuming that the materials that are no longer planned to be used for providing dishes in the restaurant or the surplus materials are materials that can be used for cooking agency.

[0089] When the cooking agent is a housework agency, all the materials held by the housework agency may be materials that can be used for cooking agency. The housework agency specializes in performing housework on behalf. Cooking agency is also included in housework. Usually, cooking materials are used only for cooking agency.

[0090] The cooking proxy available material possession status information storage control unit 1104 may store the cooking proxy available material possession status information received by the cooking proxy available material possession status information receiving unit 1103 in the storage unit 14. For example, the cooking proxy available material possession status information storage control unit 1104 may associate the material ID, possession status, and cooking proxy ID included in the cooking proxy available material possession status information with each other and store them in the cooking proxy available material possession status DB 14g. When the cooking proxy available material possession status information is surplus material information, the cooking proxy available material possession status information storage control unit 1104 may store the surplus material information in the storage unit 14 as the cooking proxy available material possession status information.

[0091] [1-3-1-2. Provision of Recipe Information] The nutrient intake status information acquisition unit 1105 may acquire nutrient intake status information. The nutrient intake status information may indicate the nutrient intake status of the health management service user. The nutrient intake status may include what nutrients the health management service user has ingested so far. Also, the nutrient intake status may include the amount of nutrients the health management service user has ingested so far.

[0092] The nutritional intake status information acquisition unit 1105 may acquire nutritional intake status information from, for example, the health management service user terminal 7. The nutritional intake status information acquired from the health management service user terminal 7 may be, for example, meal record information. In this case, the meal record information may not include either the meal nutritional intake amount information or the meal calories. The meal record information is information indicating the food and drink included in the meal taken by the health management service user. From the food and drink included in the meal taken by the health management service user, the status of nutritional intake can be specified. Therefore, even if neither the meal nutritional intake amount information nor the meal calories are included, the meal record information may correspond to the nutritional intake status information. The nutritional intake status information acquisition unit 1105 may cause the cooking proxy terminal 5 to display a meal addition screen by, for example, transmitting the screen information of the meal addition screen to the health management service user terminal 7. The meal addition screen may be a screen for adding the details of the meal taken by the health management service user. On the meal addition screen, the health management service user may be able to select the meal date and the meal category. Also, on the meal addition screen, it may be possible to input search conditions for food and drink. Examples of the search conditions include the name of the food and drink and the category of the food and drink. The nutritional intake status information acquisition unit 1105 may search for food and drink that meet the input search conditions. The nutritional intake status information acquisition unit 1105 may cause a list of the searched food and drink to be displayed on the meal addition screen by, for example, transmitting the information of the searched food and drink to the health management service user terminal 7. Also, the health management service user may take a picture of the food and drink to be taken with the camera provided in the health management service user terminal 7. The nutritional intake status information acquisition unit 1105 may identify the food and drink from the picture by image recognition based on the data of the taken picture. The nutritional intake status information acquisition unit 1105 may cause a list of the searched food and drink to be displayed on the meal addition screen by transmitting the information of the identified food and drink to the health management service user terminal 7. The health management service user may select the food and drink taken in the meal from the list. The health management service user terminal 7 may transmit meal record information including, for example, a list of the food and drink IDs of the selected food and drink, the user ID of the health management service user, the meal date, and the meal category to the health management server 1.

[0093] The nutrient intake status information acquisition unit 1105 may store the meal record information acquired from the health management service user terminal 7 in the meal record DB 14d. At this time, the nutrient intake status information acquisition unit 1105 may determine at least one of the dietary nutrient intake amount information and the dietary calories based on the meal record information. For example, the nutrient intake status information acquisition unit 1105 may acquire the dietary nutrient amount information and the dietary calories associated with the food and drink ID from the food and drink DB 14c for each food and drink ID included in the food and drink list. For example, the nutrient intake status information acquisition unit 1105 may add up the content of the target nutrient included in the acquired dietary nutrient amount information for each target nutrient to calculate the intake amount of the target nutrient in the meal. The nutrient intake status information acquisition unit 1105 may generate meal nutrient intake amount information including the intake amounts of the calculated target nutrients. Further, the nutrient intake status information acquisition unit 1105 may calculate the dietary calories by adding up the acquired dietary calories. The nutrient intake status information acquisition unit 1105 may store the meal nutrient intake amount information and the dietary calories in the meal record DB 14d.

[0094] The nutrient intake status information acquisition unit 1105 may acquire the nutrient intake status information from the storage unit 14. The nutrient intake status information acquired from the storage unit 14 may be, for example, at least one of the meal nutrient intake amount information and the dietary calories stored in the meal record DB 14d.

[0095] The nutritional intake status information acquisition unit 1105 may acquire nutritional intake status information indicating the nutritional intake status within a reference period including the current time. For example, the nutritional intake status information acquisition unit 1105 may acquire dietary record information including the meal days within the reference period. In this case, the nutritional intake status information acquisition unit 1105 may acquire, for example, the food and drink list included in all the acquired dietary record information as the final nutritional intake status information. Also, for example, the nutritional intake status information acquisition unit 1105 may acquire at least one of the dietary nutrient intake information and the dietary calories associated with the meal days within the reference period for the target health management service user from the dietary record DB 14d. In this case, the nutritional intake status information acquisition unit 1105 may calculate, for example, the intake amount of the target nutrient within the reference period by adding up the intake amounts of the target nutrient included in all the acquired dietary nutrient intake information for each target nutrient. Also, for example, the nutritional intake status information acquisition unit 1105 may calculate the calorie intake within the reference period by adding up all the acquired dietary calories. The calorie intake indicates the calories consumed within the reference period. The nutritional intake status information acquisition unit 1105 may acquire the final nutritional intake status information including at least one of the calculated intake amount of the target nutrient and the calculated dietary calories.

[0096] The nutrient intake standard information acquisition unit 1106 may acquire nutrient intake standard information indicating the standard of nutrient intake. Further, the nutrient intake standard information acquisition unit 1106 may acquire a calorie upper limit indicating the maximum value of calories that may be ingested. For example, the nutrient intake standard information acquisition unit 1106 may acquire the nutrient intake standard information and the calorie upper limit from the nutrient intake standard DB 14b. The nutrient intake standard information acquisition unit 1106 may acquire, for example, nutrient intake standard information indicating the standard of nutrient intake according to the physical characteristics of the health management service user. Examples of physical characteristics include gender, age, weight, etc. The nutrient intake standard information acquisition unit 1106 may acquire nutrient intake standard information indicating the standard of nutrient intake according to the purpose of the health management service user. In this case, the nutrient intake standard DB 14b may store the nutrient intake standard information and the calorie upper limit for each purpose. For example, each user may be able to select a purpose in advance. Or, the health management server 1 may cause the health management service user terminal 7 to present several questions. The health management service user may determine the final purpose by answering these questions. For example, identification information for identifying the selected purpose may be stored in the user DB 14a. The nutrient intake standard information acquisition unit 1106 may acquire the nutrient intake standard information and the calorie upper limit from the nutrient intake standard DB 14b based on the identification information stored in the user DB 14a. Or, the health management service user himself / herself may be able to set a standard amount of nutrient intake in advance for the desired nutrients. Also, the health management service user himself / herself may be able to set a calorie upper limit in advance. In this case, the nutrient intake standard DB 14b may store the nutrient intake standard information and the calorie upper limit for each user. The nutrient intake standard information acquisition unit 1106 may acquire the nutrient intake standard information including the set standard amount of nutrient intake and the set calorie upper limit from the health management service user terminal 7. The nutrient intake standard information acquisition unit 1106 may store the acquired nutrient intake standard information and the calorie upper limit in the nutrient intake standard DB 14b. And, the nutrient intake standard information acquisition unit 1106 may acquire the nutrient intake standard information and the calorie upper limit from the nutrient intake standard DB 14b again when necessary.

[0097] The recipe information search control unit 1107 may cause the recipe server 2 to search for recipe information of one or more recipes according to the nutritional intake status of the health management service user based on the nutritional intake status information acquired by the nutritional intake status information acquisition unit 1105. For example, the recipe information search control unit 1107 may cause the search by the recipe server 2 by sending a recipe search request to the recipe server 2. The recipe search request may include, for example, the nutritional intake status information. Further, the recipe search request may include the prioritized information stored in the user DB 14a for the health management service user. Here, in addition to the nutritional intake status information, the recipe information search control unit 1107 may further cause the recipe server 2 to search for recipe information based on the nutritional intake amount standard information acquired by the nutritional intake amount standard information acquisition unit 1106. The recipe search request in this case may include the nutritional intake status information and the nutritional intake amount standard information.

[0098] The recipe information search control unit 1107 may receive an input of recipe search conditions by the health management service user from the health management service user terminal 7. Examples of recipe search conditions include the title of the recipe, the name of the dish, the name of the ingredients, other keywords, the category of the recipe, and the like. The recipe information search control unit 1107 may send a recipe search request including the recipe search conditions to the recipe server 2.

[0099] The recipe information search control unit 1107 may acquire recipe search result information indicating the results of searching for recipes from the recipe server 2. The recipe search result information may include, for example, individual recipe information indicating each searched recipe. The individual recipe information may include information included in the recipe information stored in the recipe DB 24a for the searched recipe. The individual recipe information may include, for example, a recipe ID, a recipe title, a cooking image URL, ingredient information, a URL of the screen information of the recipe screen, a food and beverage ID of the cookable dish, a user ID of the recipe poster, etc. Further, the individual recipe information may further include the presentation order of the recipe. The presentation order of the recipe may indicate the priority order of presenting the recipe to the health management service user. Also, the presentation order may indicate at what position or at what timing the recipe is displayed. The higher the presentation order, the more preferentially the recipe may be presented. For example, the recipes may be presented in the order according to the presentation order.

[0100] There may be a case where the target health management service user does not input the meal record information of the meals consumed during the reference period. In this case, the nutrient intake status information acquisition unit 1105 may not be able to acquire the nutrient intake status information corresponding to the reference period. In this case, the recipe information search control unit 1107 may determine that the search for recipes is impossible. The recipe information search control unit 1107 may transmit presentation information indicating that the search for recipes is impossible, without sending a recipe search request, to the health management service user terminal 7.

[0101] The prompting recipe information transmission unit 1108 may transmit the prompting recipe information to the health management service user terminal 7. The prompting recipe information may be prompting information indicating that any one or more recipes among the recipes registered in the recipe service can be presented. For example, the prompting recipe information transmission unit 1108 may transmit prompting recipe information indicating that any one or more recipes among the viewable recipes or the recipes posted by the recipe poster can be presented. Alternatively, the prompting recipe information transmission unit 1108 may transmit prompting recipe information indicating that one or more recipes retrieved by the recipe server 2 can be presented to the health management service user terminal 7.

[0102] As an example of the prompting recipe information, the prompting recipe information transmission unit 1108 may transmit the screen information of the recipe search result screen to the health management service user terminal 7. The recipe search result screen may be a screen showing the search results of the recipes. For example, the recipe search result screen may include a prompting recipe information display area for each of the retrieved recipes. The prompting recipe information display area may include, for example, a recipe title, ingredient names, a cooking image, and the like. The prompting recipe information display area may be arranged in the recipe search result screen in the order according to the prompting order. The prompting recipe information transmission unit 1108 may generate the screen information of the recipe search result screen based on the recipe search result information obtained from the recipe server 2.

[0103] As another example of the presentation recipe information, the presentation recipe information transmission unit 1108 may transmit the screen information of the recipe screen of the recipe selected by the health management service user from among the recipes retrieved by the recipe server 2 to the health management service user terminal 7. For example, the health management service user can perform an operation of selecting the presentation recipe information display area of the desired recipe from the recipe search result screen displayed on the health management service user terminal 7. The health management service user terminal 7 may transmit a recipe screen request including the URL of the screen information of the recipe screen corresponding to the selected presentation recipe information display area to the health management server 1. The presentation recipe information transmission unit 1108 may obtain the screen information of the recipe screen from the recipe server 2, for example, by transmitting the URL included in the recipe screen request to the recipe server 2. The presentation recipe information transmission unit 1108 may display the recipe screen information on the health management service user terminal 7 by transmitting the obtained recipe screen information to the health management service user terminal 7. Alternatively, the system control unit 21 of the recipe server 2 may function as the presentation recipe information transmission unit 1108. In this case, the health management service user terminal 7 may transmit a recipe screen request to the recipe server 2. The recipe server 2 may transmit the screen information of the recipe screen to the health management service user terminal 7 in response to the recipe screen request. The recipe screen may include, for example, a recipe title, a cooking image, a recipe comment, the number of people corresponding to the ingredients, a list of ingredients, text indicating the cooking method, a cooking method image, a dish name, etc. The list of ingredients may include the ingredient name and the quantity for each ingredient. Further, the recipe screen may include a cooking price and a cooking agency request recipe selection element. The cooking price may indicate the price of the dish when the health management service user requests the cooking agency for the dish that can be cooked with that recipe. The cooking agency request recipe selection element may be an element operable to select the recipe corresponding to the recipe screen as the recipe for which the health management service user requests the cooking agency. Examples of the operable elements include buttons, icons, links, menu items, etc.

[0104] [1-3-1-3. Search for a cooking agent] The selection recipe identification information receiving unit 1109 may receive, from the health management service user terminal 7, selection recipe identification information for identifying a selection recipe selected by the health management service user as a recipe for which a cooking agency request is desired, from among one or more recipes indicated by the presented recipe information transmitted by the presented recipe information transmitting unit 1108. The selection recipe identification information may be, for example, a recipe ID. For example, the health management service user operates a cooking agency request recipe selection element included in the recipe screen displayed on the health management service user terminal 7. In response to this operation, the health management service user terminal 7 may transmit a selection recipe cooking agency request including the recipe ID of the recipe corresponding to the recipe screen to the health management server 1. Each presented recipe information display area included in the recipe search result screen may include a cooking agency request recipe selection element. When the health management service user operates the cooking agency request recipe selection element in any of the presented recipe information display areas, the health management service user terminal 7 may transmit a selection recipe cooking agency request including the recipe ID of the recipe corresponding to the operated cooking agency request recipe selection element to the health management server 1.

[0105] Here, the selected recipe identification information receiving unit 1109 may function so that a health management service user can specify cooking provision conditions. The cooking provision conditions may indicate conditions for providing the cooked food prepared by the cooking agency to the cooking agency requester. Examples of the cooking provision conditions include the number of people to be served, the provision location, the provision date and time, etc. The number of people to be served may indicate how many servings of food are to be provided. When the number of people to be served as the cooking provision condition is not specified, the selected recipe identification information receiving unit 1109 may consider the number of people to be served as 1. The provision location may indicate the location of the destination for the food. For example, the provision location may indicate the location of the delivery destination of the food. The provision location may be indicated by, for example, an address. When the provision location as the cooking provision condition is not specified, the selected recipe identification information receiving unit 1109 may consider the provision location as the address of the cooking agency requester. The provision date and time may indicate the date and time for providing the food. For example, the provision date and time may indicate the date and time for delivering the food. When the provision date and time as the cooking provision condition is not specified, the selected recipe identification information receiving unit 1109 may consider that the food is to be provided as soon as possible, for example. The health management service user terminal 7 may send a selected recipe cooking agency request including the cooking provision conditions to the health management server 1.

[0106] After the cooking agent search unit 1110 receives the selected recipe identification information from the selected recipe identification information receiving unit 1109, it may search for one or more cooking agents that meet predetermined conditions from among a plurality of cooking agents registered in the health management service as cooking agents available for use in the cooking agency matching system. These predetermined conditions are referred to as cooking agency request destination conditions. The cooking agency request destination conditions may be the conditions for the destination of a request to substitute for cooking using the selected recipe identified by the selected recipe identification information. For example, the cooking agent search unit 1110 may search for cooking agents that meet the cooking agency request destination conditions based on the cooking agent information stored in the storage unit 14 for each cooking agent. The cooking agent information may be information about the cooking agent. For example, the cooking agent information may include at least any one of the cooking agent basic information stored in the cooking agent DB 14e, the cookable dish information stored in the cookable dish DB 14f, and the possession status information stored in the available cooking material possession status DB 14g. The cooking agent search unit 1110 may search for one or more restaurants that meet the cooking agency request destination conditions based on the restaurant information stored in the storage unit 14 as cooking agent information.

[0107] The conditions for the requested cooking agent may or may not include that the location of the health management service user is within the geographical service area where the cooking agent can provide the cooked dishes. The cooking agent search unit 1110 may search for cooking agents whose location of the health management service user is within the service area. Here, the cooking agent search unit 1110 may search for one or more restaurants whose location of the health management service user is within the service area. The cooking agent search unit 1110 may perform the search based on, for example, the health management service user location information and the service area information. The health management service user location information may be information indicating the location of the health management service user. The health management service user location information may include, for example, the address of the dish delivery location. The address of the delivery location may be, for example, the address of the health management service user or the address of the delivery location specified by the health management service user as a dish delivery condition. The service area information may be information that can specifically indicate the service area where the restaurant can provide the cooked dishes by the cooking agent. The service area information may be information stored in the storage unit 14 for each cooking agent. The service area information may include, for example, the corresponding area information or the address of the cooking agent. The corresponding area information in the case where the cooking agent is a restaurant may correspond to the restaurant location information. When the service area information is the corresponding area information, that the location of the health management service user is within the service area may mean, for example, that the delivery location is within the area indicated by the corresponding area information. When the corresponding area information includes the address of the cooking agent, examples of the location of the health management service user being within the service area include that the delivery location is within a predetermined distance from the address of the cooking agent, that the travel time from the address of the cooking agent to the delivery location is within a predetermined time, and that the delivery location is included in the same area as the area including the address of the cooking agent. Examples of the distance from the address of the cooking agent to the delivery location include the straight-line distance between the address of the cooking agent and the delivery location, and the travel distance from the address of the cooking agent to the delivery location. The travel distance may be, for example, the distance when the delivery person travels using the road. The travel time may be, for example, the time required when the delivery person travels from the address of the cooking agent to the delivery location using the road. The storage unit 14 may store, for example, a map DB.The map DB may store, for example, the coordinates of the locations where each road connects to other roads, the distances of each road, etc. The cooking agent search unit 1110 may calculate the moving distance or the moving time based on the map DB. As described above, based on the address of the cooking agent, the straight-line distance, the moving distance, the moving time, or the area can be specified. Therefore, the address of the cooking agent may correspond to the provision range information that can specify the geographical provision range within which the cooking agent can provide the dishes cooked through the cooking agency service.

[0108] The cooking agency request destination conditions may or may not include the possibility of a cooking agent being able to perform the cooking of the dishes that can be cooked according to the selected recipe. The cooking agent search unit 1110 may search for a cooking agent who can perform the cooking of that dish. The cooking agent search unit 1110 may perform the search, for example, based on the selected recipe identification information and the cookable dish information stored in the cookable dish DB 14f. For example, the cooking agent search unit 1110 may obtain dish identification information for identifying the dishes that can be cooked according to the selected recipe. The dish identification information may be information included in the recipe information. Examples of the dish identification information include the food and beverage ID and the dish name. The cooking agent search unit 1110 may search the cookable dish DB 14f for the cooking agent ID associated with the food and beverage ID to search for a cooking agent who can perform the cooking of that dish. Alternatively, the cooking agent search unit 1110 may obtain the food and beverage ID of the dish indicated by the dish name from the food and beverage DB 14c. The cooking agent search unit 1110 may search the cookable dish DB 14f for the cooking agent ID associated with the obtained food and beverage ID to search for a cooking agent who can perform the cooking of that dish.

[0109] The conditions for the outsourcing destination may or may not include having the ingredients used in the selected recipe as ingredients available for outsourcing cooking. For example, the outsourcing cook search unit 1110 may search for outsourcing cooks who have the ingredients used in the selected recipe as ingredients available for outsourcing cooking. The outsourcing cook search unit 1110 may search for outsourcing cooks who have all the ingredients used in the selected recipe. The outsourcing cook search unit 1110 may perform the search based on, for example, the ingredient information included in the recipe information of the selected recipe among the recipe information stored in the recipe DB 24a and the possession status information stored in the outsourcing available ingredient possession status DB 14g. The outsourcing cook search unit 1110 may obtain, for example, the ingredient information stored in the recipe DB 24a for the selected recipe from the recipe server 2. Alternatively, the outsourcing cook search unit 1110 may obtain the ingredient information of the selected recipe from the recipe search result information. The outsourcing cook search unit 1110 may obtain the ingredient IDs of the ingredients used in the selected recipe from the ingredient DB 24b by searching the ingredient DB 24b for ingredient names that match each ingredient name included in the ingredient information. The outsourcing cook search unit 1110 may search the outsourcing available ingredient possession status DB 14g for the possession status associated with each obtained ingredient ID. The outsourcing cook search unit 1110 may determine whether the outsourcing cook indicated by the outsourcing cook ID associated with the searched possession status has each ingredient based on the searched possession status. For example, when the possession status indicates "yes", the outsourcing cook search unit 1110 may determine that the ingredient is possessed by the outsourcing cook. Also, for example, the outsourcing cook search unit 1110 may search for outsourcing cooks who have, as ingredients available for outsourcing cooking, the ingredients used in the selected recipe and in the amounts necessary for outsourcing cooking. Here, the outsourcing cook search unit 1110 may search for one or more restaurants that have, as ingredients used in the selected recipe and in the amounts necessary for outsourcing cooking, more ingredients than the quantity of ingredients the restaurant has for providing meals. For example, assume that the possession status indicates a quantity. In this case, the outsourcing cook search unit 1110 may calculate the amount per person of the ingredient by dividing the amount included in the ingredient information by the number of people corresponding to the ingredient in the recipe information.When the quantity indicated by the holding status is equal to or more than the amount for one person, the cooking agent search unit 1110 may determine that the material is held by the cooking agent. When the health management service user can specify the number of people to be served, the cooking agent search unit 1110 may multiply the amount for one person of the material by the number of people to be served to calculate the amount for the number of people to be served of the material. Then, when the quantity indicated by the holding status is equal to or more than the amount for the number of people to be served, the cooking agent search unit 1110 may determine that the material is held by the cooking agent.

[0110] The cooking agent search unit 1110 may search for one or more restaurants that have the materials used in the selected recipe as materials that can be used for cooking agency. Here, the cooking agent search unit 1110 may search for one or more restaurants that have extra materials used in the selected recipe. As described above, when the cooking agent is a restaurant, the cooking agency-useable material holding status information may be surplus material information indicating the holding status of the materials that the restaurant has in excess. The restaurant may have to discard the extra materials someday. By searching for restaurants that have extra materials used in the selected recipe, there is a possibility that the searched restaurants will be requested for cooking agency. The restaurant that has received the request for cooking agency can perform the cooking agency using the extra materials it has. Therefore, the loss of the materials held by the restaurant can be suppressed.

[0111] FIG. 12 is a diagram showing an example of searching for a cooking agent. As shown in FIG. 12, assume that the cooking agents registered in the health management service include at least restaurant D, restaurant E, and restaurant F. The dish that can be cooked according to the recipe selected by the health management service user is tomato sauce spaghetti. The ingredients used in the selected recipe are spaghetti, tomatoes, onions, garlic, olive oil, salt, and pepper. Here, salt and pepper may be considered to be possessed by all cooking agents. In this case, the possession status of salt and pepper may not be stored in the cooking agent available ingredient possession status DB14g. As shown in FIG. 12, restaurant D can act as a cooking agent for tomato sauce spaghetti. Also, restaurant D has spaghetti, tomatoes, garlic, and olive oil as ingredients that can be used for cooking agency. However, restaurant D does not have onions as an ingredient that can be used for cooking agency. Therefore, the cooking agent search unit 1110 may determine that restaurant D does not meet the cooking agency request destination conditions. Restaurant E can act as a cooking agent for tomato sauce spaghetti. Also, restaurant E has all of spaghetti, tomatoes, onions, garlic, and olive oil as ingredients that can be used for cooking agency. Therefore, the cooking agent search unit 1110 may determine that restaurant E meets the cooking agency request destination conditions. Restaurant F has all of spaghetti, tomatoes, onions, garlic, and olive oil as ingredients that can be used for cooking agency. However, restaurant F cannot act as a cooking agent for tomato sauce spaghetti. Therefore, the cooking agent search unit 1110 may determine that restaurant F does not meet the cooking agency request destination conditions.

[0112] The cooking agency request destination conditions may include two or more predetermined conditions. The cooking agent search unit 1110 may search for a cooking agent that satisfies all of these two or more conditions. For example, the cooking agent search unit 1110 may search for one or more cooking agents or restaurants among the cooking agents or restaurants that have the ingredients used in the selected recipe as ingredients that can be used for cooking agency and within the provided range of the location of the health management service user.

[0113] The cooking agent presentation order determination unit 1111 may determine the presentation order of the information of one or more cooking agents retrieved by the cooking agent search unit 1110. The presentation order of the cooking agents may indicate the priority order for presenting the retrieved cooking agents to the health management service user. Also, the presentation order of the cooking agents may indicate at what position or timing the cooking agents are displayed. The higher the presentation order, the more preferentially the information of the cooking agent may be presented. For example, the recipes may be presented in an order according to the presentation order.

[0114] The cooking agent presentation order determination unit 1111 may determine the presentation order, for example, based on the health management service user location information and the cooking agent location information. The cooking agent location information may be information indicating the location of the cooking agent. The cooking agent location information may be information stored in the storage unit 14 for each cooking agent. The cooking agent location information may include, for example, the address of the cooking agent stored in the cooking agent DB 14e. The cooking agent presentation order determination unit 1111 may, for example, increase the presentation order of the cooking agent as the distance from the providing location to the domicile of the cooking agent is closer. Examples of the distance from the providing location to the domicile of the cooking agent being close include the straight-line distance from the providing location to the domicile of the cooking agent being short, the moving distance being short, and the moving time being short. The straight-line distance, the moving distance, and the moving time can be calculated by the same method as the method described above.

[0115] The prompting cooking agent information transmission unit 1112 may transmit the prompting cooking agent information to the health management service user terminal 7. The prompting cooking agent information may be prompting information indicating one or more of the cooking agents registered in the cooking agent service. For example, the prompting cooking agent information transmission unit 1112 may transmit the prompting cooking agent information indicating one or more cooking agents retrieved by the cooking agent search unit 1110 to the health management service user terminal 7. As an example of the prompting cooking agent information, the prompting cooking agent information transmission unit 1112 may transmit the screen information of the cooking agent search result screen to the health management service user terminal 7. The cooking agent search result screen may be a screen showing the search results of the cooking agents. For example, the cooking agent search result screen may include a prompting cooking agent information display area for each retrieved cooking agent. Each prompting cooking agent information display area may include, for example, the cooking agent name, the cooking agent image, the address of the cooking agent, and the appealing information. Each prompting cooking agent information display area may further include a destination cooking agent selection element. The destination cooking agent selection element may be an element that can be operated for the health management service user to select the cooking agent corresponding to the destination cooking agent selection element as the cooking agent desired as the destination of the cooking agency request.

[0116] The prompting cooking agent information transmission unit 1112 may transmit the prompting cooking agent information indicating one or more cooking agents retrieved by the cooking agent search unit 1110 in the order according to the prompting order determined by the cooking agent prompting order determination unit 1111 to the health management service user terminal 7. For example, the prompting cooking agent information transmission unit 1112 may generate the screen information of the cooking agent search result screen such that the prompting cooking agent information display areas of the retrieved cooking agents are arranged in the cooking agent search result screen in the order according to the prompting order.

[0117] [1-3-1-4. Request for a cooking agent] The selected cooking agent identification information receiving unit 1113 may receive, from the health management service user terminal 7, selected cooking agent identification information for identifying a selected cooking agent selected by the health management service user as a cooking agent desired as a request destination for proxy cooking of the recipe dishes among the one or more cooking agents indicated by the presented cooking agent information transmitted by the presented cooking agent information transmitting unit 1112. The selected cooking agent identification information may be, for example, a cooking agent ID. For example, the health management service user operates a request destination cooking agent selection element in any of the presented cooking agent information display areas included in the cooking agent search result screen displayed on the health management service user terminal 7. In response to this operation, the health management service user terminal 7 may transmit a selected cooking agent proxy cooking request including the cooking agent ID of the cooking agent corresponding to the operated request destination cooking agent selection element to the health management server 1.

[0118] The cooking agency request information transmission unit 1114 may transmit cooking agency request information indicating a request for agency cooking using the selected recipe identified by the selected recipe identification information received by the selected recipe identification information receiving unit 1109 to the cooking agent terminal 5. For example, the cooking agency request information transmission unit 1114 may transmit the cooking agency request information to the cooking agent terminal 5 used by the cooking agent searched by the cooking agent search unit 1110. Here, the cooking agency request information transmission unit 1114 may transmit the cooking agency request information to the cooking agent terminal 5 used by any one of the one or more cooking agents searched by the cooking agent search unit 1110. For example, the cooking agency request information transmission unit 1114 may transmit the cooking agency request information to the cooking agent terminal 5 used by the selected cooking agent identified by the selected cooking agent identification information obtained by the selected cooking agent identification information receiving unit 1113. The cooking agency request information may include, for example, information about the health management service user who is the cooking agency requester. The cooking agency request information may include cooking provision conditions. The cooking agency request information may include information about the selected recipe. The information about the selected recipe may be, for example, information for presenting the information of the selected recipe to the cooking agent. For example, the information about the selected recipe may include the recipe information of the selected recipe. For example, the information about the selected recipe may include the recipe title, the name of the dish, the list of ingredients, and the cooking method information. The list of ingredients may include the ingredient name and quantity of each ingredient used in the selected recipe. The quantity of each ingredient may be, for example, the quantity for one serving. Also, the information about the selected recipe may include at least one of the cooking image and the cooking method image. Also, the information about the selected recipe may include the URL of the screen information of the recipe screen of the selected recipe. The cooking agency request information may include information for causing the cooking agent terminal 5 to display a cooking agency request acceptance selection screen display element. This information may be described in, for example, HTML. The cooking agency request acceptance selection screen display element may be an element operable to cause the cooking agent terminal 5 to display the cooking agency request acceptance selection screen. The cooking agency request acceptance selection screen may be a screen for accepting an operation of whether to accept the request for agency cooking indicated by the cooking agency request information.In addition, the cooking agency request information may include a request ID. The cooking agency request information transmission unit 1114 may transmit the cooking agency request information to the cooking agency agent terminal 5 by, for example, e-mail, push notification, or HTTP (HyperText Transfer Protocol). The cooking agency agent terminal 5 may display the cooking agency request information on the screen. Thereby, the cooking agency agent can confirm the cooking agency request information. When the cooking agency request information includes the URL of the screen information of the recipe screen, the cooking agency agent may be able to select the URL from the displayed cooking agency request information. When the URL is selected, the recipe server 2 may transmit the screen information of the recipe screen associated with the selected URL to the cooking agency agent terminal 5. The cooking agency agent terminal 5 may display the recipe screen based on this screen information.

[0119] The cooking agency request information transmission unit 1114 may store the cooking agency request record information in the cooking agency request DB 14h. For example, the cooking agency request information transmission unit 1114 may store the cooking agency request record information when the selected cooking agency agent identification information is acquired by the selected cooking agency agent identification information reception unit 1113, or may transmit the cooking agency request record information after the cooking agency request information transmission unit 1114 transmits the cooking agency request information. Here, the cooking agency request information transmission unit 1114 may store a request status indicating "request transmitted" in the cooking agency request DB 14h.

[0120] The reception information receiving unit 1115 may receive, from the proxy cook terminal 5, reception information indicating that the proxy cook has received the proxy cooking request indicated by the proxy cooking request information transmitted by the proxy cooking request information transmitting unit 1114. For example, the proxy cook operates the proxy cooking request reception selection screen display element included in the proxy cooking request information displayed on the proxy cook terminal 5. In response to this operation, the reception information receiving unit 1115 may transmit the screen information of the proxy cooking request reception selection screen to the proxy cook terminal 5. The reception information receiving unit 1115 may display the proxy cooking request reception selection screen based on the screen information. The proxy cook selects whether to accept the proxy cooking request on the proxy cooking request reception selection screen. Alternatively, in the proxy cooking request information displayed on the proxy cook terminal 5, the proxy cook may be able to select whether to accept the proxy cooking request. For example, the proxy cooking request information displayed on the screen may include a link corresponding to accepting the proxy cooking request and a link corresponding to rejecting the proxy cooking request. When accepting the proxy cooking request is selected, the proxy cook terminal 5 may transmit the reception information to the health management server 1. When rejecting the proxy cooking request is selected, the proxy cook terminal 5 may transmit rejection information to the health management server 1. The rejection information may be information indicating that the acceptance of the proxy cooking request has been rejected. Examples of cases where the proxy cooking request is rejected include cases where the materials used for the proxy cooking are actually insufficient, cases where the proxy cook has no time or human resources to perform the proxy cooking, and cases where the cooking method indicated in the selected recipe is not suitable for the proxy cook.

[0121] When the reception information receiving unit 1115 receives the reception information, it may store, in the proxy cooking request DB 14h, a request status indicating "request received" in association with the request ID of the proxy cooking request corresponding to the reception information. Also, when the reception information receiving unit 1115 receives the rejection information, it may store, in the proxy cooking request DB 14h, a request status indicating "request rejected" in association with the request ID of the proxy cooking request corresponding to the rejection information.

[0122] When the reception information receiving unit 1115 receives the reception information, the delivery request information transmitting unit 1116 may transmit the delivery request information to the delivery management server 4. The delivery request information may be information indicating a request to deliver the dish cooked by the cooking agent to the cooking agent requester who has received the request for cooking agency. The delivery request information may include information about the cooking agent who has received the request for cooking agency. The information about the cooking agent may include, for example, the name, address, and telephone number of the cooking agent. The delivery request information may include information about the cooking agent requester. The information about the cooking agent requester may include, for example, the name of the cooking agent requester, the address of the provided location as the delivery destination, and the telephone number. The delivery request information may include information about the dish to be delivered. The information about the dish may include, for example, the dish name and the number of people to be served.

[0123] The delivery management server 4 that has received the delivery request information may generate a slip number and transmit this slip number to the health management server 1. After that, the delivery management server 4 may transmit the delivery status to the health management server 1 in a timely manner together with the slip number for the requested delivery. The delivery status may indicate the state of the delivery of the dish. For example, the delivery status may be set to any one of "collecting", "delivering", and "delivery completed". "Collecting" indicates that the delivery person is on the way to the location of the cooking agent to pick up the dish. "Delivering" indicates that the delivery person is on the way to the provided location of the health management service user with the dish. "Delivery completed" indicates that the delivery to the health management service user has been completed. The health management server 1 may change the request status stored in the cooking agency request DB 14h according to the delivery status received from the delivery management server 4. For example, when the delivery status is "delivering", the health management server 1 may change the request status to "delivering". When the delivery status is "delivery completed", the health management server 1 may change the request status to "delivery completed".

[0124] [1-3-1-5. Granting of Remuneration] When the reception information receiving unit 1115 receives the reception information, the reward granting unit 1117 may grant a reward to the recipe submitter identified by the user ID included in the recipe information of the selected recipe identified by the selected recipe identification information received by the selected recipe identification information receiving unit 1109 among the recipe information stored in the recipe DB 24a. The reward granting unit 1117 may grant a reward on the condition that the reception information receiving unit 1115 has received the reception information. Examples of the types of rewards include points in a point program, electronic coupons, electronic money, cash, and the like. The value of the reward granted to the recipe submitter may be uniformly determined in advance. Alternatively, the value of the reward may be a value corresponding to the cooking price or payment amount of the dish that can be cooked with the selected recipe. For example, the value of the reward may be a value corresponding to a predetermined percentage of the cooking price or payment amount. The reward granting unit 1117 may directly obtain the user ID of the recipe submitter of the selected recipe from the recipe DB 24a of the recipe server 2. Alternatively, the reward granting unit 1117 may obtain the user ID of the recipe submitter of the selected recipe from the recipe search result information. The user ID included in the recipe search result information is also the user ID included in the recipe information originally stored in the recipe DB 24a.

[0125] When the reception information receiving unit 1115 receives the reception information, it indicates that the cook who is the recipient of the cooking agency request has received the cooking agency request. The cook who has received the cooking agency request cooks the dish using the selected recipe selected by the health management service user. The cooked dish is delivered from the cook to the health management service user by the delivery person. In this way, the submitted recipe is actually used. It is considered a pleasant thing for the recipe submitter that the submitted recipe is useful. Since a reward is granted when the recipe is used, the motivation to submit a recipe can be given to the recipe service user.

[0126] There may be an ownership target management system (or server device) that manages the ownership status of a target of the same type as the type of reward for the recipe submitter. This target is referred to as an ownership target. For example, when the reward and the ownership target are points, the ownership target management system may be the point management server 3. When the reward is an ownership target other than points, the ownership target management system may be a system or server device not shown in the figure. The ownership target management system may store, for example, for each user who can use or own the ownership target, ownership target ownership status information indicating the ownership status of the ownership target by that user, in association with that user. The ownership target ownership status information may indicate whether the user owns the ownership target. Also, the target ownership status information may indicate the quantity of the ownership targets currently held by the user. Also, the target ownership status information may indicate, for each of the one or more ownership targets currently held by the user, what kind of ownership target it is. When the reward is points, the ownership target ownership status information may be the available point number stored in the available point DB 34a of the point management server 3. When the reward and the ownership target 1 are electronic coupons, the ownership target ownership status information may be the owned coupon DB. In the owned coupon DB, for example, owned coupon information may be stored for each electronic coupon owned by each user. The owned coupon information may be information indicating the electronic coupon owned by the user. For example, the owned coupon information may include at least one of the following information: user identification information for identifying the user, provider identification information for identifying the provider of the transaction target for which the electronic coupon is available, transaction target identification information for identifying the transaction target for which the electronic coupon is available, and discount information indicating the discount rate or the amount to be discounted by the electronic coupon. When the reward is electronic money, the ownership target ownership status information may be the balance of the electronic money. The balance of the electronic money may be stored, for example, in any server device of the ownership target management system. Alternatively, the balance of the electronic money may be stored in an IC (Integrated Circuit) chip provided in the terminal device of the user (for example, the recipe submitter terminal 6).When the reward is cash, the ownership target management system may be a bank system (not shown) of each bank. The bank system may manage the balance of cash deposited in the deposit accounts of each depositor. In this case, the ownership status information of the ownership target may be the balance of the deposit account.

[0127] The reward awarding unit 1117 may award a reward by causing the ownership status information of the ownership target stored in a predetermined storage means in, for example, the ownership target management system to be updated by the ownership target management system. For example, the reward awarding unit 1117 may update the ownership status information of the ownership target stored in the storage means by sending a request to update the ownership status information of the ownership target to the ownership target management system. The request to update the ownership status information of the ownership target may be information indicating a request to update the ownership status information of the ownership target. The request to update the ownership status information of the ownership target may include user identification information for identifying the recipe submitter who is the recipient of the reward in the ownership target management system. Further, the request to update the ownership status information of the ownership target may include information on the ownership target to be awarded as a reward (hereinafter referred to as "awarded ownership target information"). For example, the awarded ownership target information may include the quantity of the ownership target to be awarded. For example, when the reward is points, the request to update the ownership status information of the ownership target may be a point addition request. The point addition request may be information indicating a request for addition to the available number of points. The awarded ownership target information included in the point addition request may be the number of added points. The number of added points may indicate the number of points to be awarded. When the reward is electronic money, the awarded ownership target information may indicate the amount of electronic money to be awarded. When the reward is cash, the request to update the ownership status information of the ownership target may be a remittance request. The remittance request may be, for example, information indicating a request for remittance from the deposit account of the operator of the health management service to the deposit account of the recipe submitter. The destination of the remittance request may be the banking system of the bank that manages the deposit account of the operator of the health management service. The awarded ownership target information included in the remittance request may indicate the amount of cash to be awarded. The user identification information included in the remittance request may include the account number, branch number, and bank code of the recipe submitter. Further, the remittance request may include the account number and branch number of the operator of the health management service. The awarded ownership target information may indicate the details of the ownership target to be awarded. For example, when the reward is an electronic coupon, the awarded ownership target information may be coupon information. The coupon information may be information indicating the coupon to be awarded. The types of information included in the coupon information may be the same as the types of information included in the owned coupon information.Upon receiving a request to update the ownership status information of an owned object from the health management server 1, the owned object management system may update the ownership status information of the owned object based on the request. For example, when the reward is points, the recipe server 2 may update the available point count by adding the number of points indicated by the granted owned object information to the available point count stored in the available point DB 34a associated with the user ID of the recipe contributor who is the recipient of the points. When the reward is an electronic coupon, the owned object management system may update the owned coupon DB by storing the coupon information as the granted owned object information in association with the user identification information of the recipe contributor in the owned coupon DB. When the reward is electronic money, the owned object management system may update the balance by adding the amount of electronic money indicated by the granted owned object information to the balance stored in association with the user identification information of the recipe contributor. When the reward is cash, the remitting bank system may cooperate with the receiving bank system to execute the remittance process. At this time, the receiving bank system may update the balance by adding the amount indicated by the granted owned object information to the balance associated with the account number and branch number of the recipe contributor.

[0128] After the reward granting unit 1117 receives the received information by the received information receiving unit 1115, the reward may be granted at any timing. For example, the reward granting unit 1117 may grant the reward at the timing when the received information is received, the timing when the payment amount related to the request for cooking agency is settled, the timing when the delivery person picks up the cooked food from the cooking agent, or the timing when the delivery person delivers the cooked food to the cooking agency requester.

[0129] [1-3-2. Recipe Server] Next, the functional overview of the system control unit 21 in the recipe server 2 will be described with reference to FIGS. 13 to 16. FIG. 13 is a diagram showing an example of the functional blocks of the system control unit 21 in the recipe server 2 according to the present embodiment. The system control unit 21 may function as a recipe information receiving unit 2101, a recipe information storage control unit 2102, a recipe information storage control unit 2102, a cooking nutrient amount calculation unit 2103, a cooking nutrient amount information storage control unit 2104, a recipe search unit 2105, a recipe presentation order determination unit 2106, etc., as shown in FIG. 13, when the CPU 21a reads and executes various program codes included in the recipe server program.

[0130] [1-3-2-1. Submission of Recipe] The recipe information receiving unit 2101 may receive recipe information indicating a recipe submitted by a recipe submitter from the recipe submitter terminal 6. The recipe information received from the recipe submitter terminal 6 may include, for example, the user ID of the recipe submitter, the recipe title, the image data of the cooking image, the recipe comment, the number of people corresponding to the ingredients, the ingredient information, the cooking method information, the image data of the cooking method image, and the cooking name. For example, the recipe information receiving unit 2101 may cause the recipe submitter terminal 6 to display a recipe submission screen by transmitting the screen information of the recipe submission screen to the recipe submitter terminal 6. The recipe submission screen may be a screen for receiving input of information on the recipe to be submitted. For example, on the recipe submission screen, the recipe submitter may be able to input the recipe title, the path of the image data of the cooking image, the recipe comment, the number of people corresponding to the ingredients, the ingredient information, the cooking method information, the path of the image data of the cooking method image, and the cooking name. Note that if the recipe submitter inputs a recipe title including the cooking name, the recipe submitter may not need to input the cooking name separately from the recipe title. When the recipe submitter performs an operation for applying for the publication of the recipe on the recipe submission screen, the recipe submitter terminal 6 may transmit recipe information corresponding to the input content on the recipe submission screen to the health management server 1. Thus, the recipe information receiving unit 2101 may receive the recipe information.

[0131] The recipe information storage control unit 2102 may store the recipe information acquired by the recipe information receiving unit 2101 in the storage unit 24. For example, the recipe information storage control unit 2102 may generate a recipe ID for the posted recipe. Also, for each of the cooking image and the cooking method image included in the recipe information, the recipe information storage control unit 2102 may generate a URL of the image data. Further, the recipe information storage control unit 2102 may acquire the dish name included in the recipe information. Alternatively, the recipe information storage control unit 2102 may acquire the dish name from the recipe title. For example, the recipe information storage control unit 2102 may extract each keyword constituting the recipe title by morphological analysis. The recipe information storage control unit 2102 may identify the keyword indicating the dish name from among the extracted keywords by searching for food and drink names that match each of the extracted keywords from the food and drink DB 14c of the health management server 1. The health management server 1 may acquire the food and drink ID associated with the dish name from the food and drink DB 14c. The recipe information storage control unit 2102 may add the recipe ID, the URL of the image data, and the food and drink ID to the recipe information. The recipe information storage control unit 2102 may delete the image data from the recipe information and store the deleted image data separately in the storage unit 14. Then, the recipe information storage control unit 2102 may store the recipe information in the recipe DB 24a.

[0132] [1-3-2-2. Determination of Nutrient Quantities of Dishes in Recipes] The cooking nutrient amount calculation unit 2103 may calculate the amount of nutrients contained in the dishes that can be cooked according to the recipes indicated by the recipe information stored in the storage unit 24 for each piece of recipe information. For example, the cooking nutrient amount calculation unit 2103 may calculate the amount of nutrients contained in the dishes that can be cooked according to the recipes indicated by the recipe information stored in the storage unit 24 by the recipe information storage control unit 2102. The cooking nutrient amount calculation unit 2103 may perform the calculation based on, for example, the material nutrient amount information stored in the material DB 24b and the material information included in the recipe information stored in the storage unit 24. For example, the cooking nutrient amount calculation unit 2103 may calculate the per-person amount of the materials used in the recipe by dividing the amount included in each piece of material information by the number of people for whom the materials are targeted in the recipe information. The cooking nutrient amount calculation unit 2103 may acquire the material nutrient amount information associated with the material name that matches the material name included in each piece of material information from the material DB 24b. At this time, the cooking nutrient amount calculation unit 2103 may also acquire the material calories. The cooking nutrient amount calculation unit 2103 may calculate the content of each target nutrient in the materials used in the recipe by multiplying the content of each target nutrient included in the material nutrient amount information by the per-person amount. The cooking nutrient amount calculation unit 2103 may calculate the content of the target nutrient in the dishes that can be cooked according to the recipe by adding up the contents of the target nutrient among the materials for each target nutrient. Also, the cooking nutrient amount calculation unit 2103 may calculate the calories ingested from the materials used in the recipe by multiplying the material calories of each material used in the recipe by the per-person amount. Then, the cooking nutrient amount calculation unit 2103 may calculate the recipe calories by adding up the calculated calories among the materials.

[0133] Even for the same dish, the amount of nutrients contained in the dish may vary depending on the recipe. Specifically, even for dishes with the same dish name, depending on the recipe, at least one of the ingredients used may be different from other recipes, or the amount used as the portion of the ingredient per person may be different from other recipes. The food and beverage nutrient amount information and food and beverage calories stored in the food and beverage DB 14c indicate the general or average amount of nutrients and calories, respectively. Even if a recipe is searched using the food and beverage nutrient amount information and food and beverage calories stored in the food and beverage DB 14c according to the nutrient intake status of the health management service user, a somewhat appropriate recipe can be searched. However, by searching for a recipe using the nutrient amount and calories calculated by the dish nutrient amount calculation unit 2103, a more appropriate recipe can be presented to the health management service user.

[0134] FIG. 14(a) is a diagram showing an example of materials used in a recipe. As shown in FIG. 14(a), for example, a recipe for tomato spaghetti was posted. The materials used in this recipe are spaghetti, tomatoes, onions, garlic, olive oil, salt, and pepper. The number of people targeted by the materials of this recipe is 1 person. The cooking nutrient amount calculation unit 2103 calculates the nutrient content in the materials used in the recipe based on the material DB24b. For example, in the material DB24b, the nutrient content per gram may be stored for spaghetti, olive oil, salt, and pepper. Also, for example, in the material DB24b, the nutrient content per piece may be stored for tomatoes, onions, and garlic. The amount of spaghetti used in the recipe is 100 grams. The amount of tomatoes is 1 piece. The amount of onions is 1 / 4 piece. The amount of garlic is 1 clove. The amount of olive oil is 2 tablespoons. The amount of salt is a little. The amount of pepper is a little. Here, the cooking nutrient amount calculation unit 2103 may calculate what fraction of a piece of garlic 1 clove of garlic corresponds to. Also, the cooking nutrient amount calculation unit 2103 may calculate the weight corresponding to 2 tablespoons of olive oil. Also, the cooking nutrient amount calculation unit 2103 may calculate the weight corresponding to each of a little salt and a little pepper. FIG. 14(b) is a diagram showing an example of the material nutrient amount information stored in the material DB24b. As shown in FIG. 14(b), 1 gram of spaghetti has 8 grams of protein. 1 tomato has 2 grams of protein. 1 onion has 0.25 grams of protein. 1 clove of garlic has 0.05 grams of protein. Olive oil, salt, and pepper do not contain protein. FIG. 14(c) is a diagram showing an example of the amount of nutrients contained in the materials used in the recipe. As shown in FIG. 14(c), 100 grams of spaghetti contains 8 grams of protein. 2 tomatoes contain 4 grams of protein. 1 / 4 onion contains 0.25 grams of protein. 1 clove of garlic is assumed to be equivalent to 10 times the amount. Therefore, 1 clove of garlic contains 0.05 grams of protein.Therefore, the amount of protein contained in the tomato spaghetti that can be cooked with this recipe is 12.3 grams.

[0135] The cooking nutrient amount information storage control unit 2104 may store, in the storage unit 24 in association with the recipe information, the recipe cooking nutrient amount information indicating the amount of nutrients calculated by the cooking nutrient amount calculation unit 2103. For example, the cooking nutrient amount information storage control unit 2104 may associate the recipe cooking nutrient amount information with the recipe information by adding the recipe cooking nutrient amount information to the recipe information stored in the recipe DB 24a. Alternatively, the cooking nutrient amount information storage control unit 2104 may associate the recipe cooking nutrient amount information with the recipe information by storing, in a predetermined database different from the recipe DB 24a, the recipe ID of the recipe information and the recipe cooking nutrient amount information in association with each other. The cooking nutrient amount information storage control unit 2104 may generate recipe cooking nutrient amount information including the content of each target nutrient calculated by the cooking nutrient amount information storage control unit 2104 as the content of the target nutrient in the dish that can be cooked with the recipe. The cooking nutrient amount information storage control unit 2104 may store the generated recipe cooking nutrient amount information. Further, the cooking nutrient amount information storage control unit 2104 may store, in the storage unit 24 in association with the recipe information, the recipe cooking calorie calculated by the cooking nutrient amount calculation unit 2103.

[0136] Note that the recipe server 2 may not calculate the amount of nutrients and the recipe cooking calorie contained in the dish that can be cooked with the recipe based on the ingredient information, but may acquire the food and drink nutrient amount information and the food and drink calorie of the dish from the food and drink DB 14c of the health management server 1. Then, the recipe server 2 may add the food and drink nutrient amount information and the food and drink calorie as the recipe cooking nutrient amount information and the recipe cooking calorie, respectively, to the recipe information.

[0137] [1-3-2-3. Search for Recipe] The recipe search unit 2105 may search for one or more recipes according to the nutritional intake status of the health management service user based on the nutritional intake status information acquired by the nutritional intake status information acquisition unit 1105 of the health management server 1 and the recipe dish nutrient amount information associated with the recipe information stored in the recipe DB 24a. Here, in addition to the nutritional intake status information and the recipe dish nutrient amount information, the recipe search unit 2105 may further search for one or more recipes according to the nutritional intake status of the health management service user based on the nutritional intake amount standard information acquired by the nutritional intake amount standard information acquisition unit 1106 of the health management server 1. For example, the recipe search unit 2105 may search for a recipe in which the nutritional intake amount of the health management service user meets the standard of the nutritional intake amount indicated by the nutritional intake amount standard information according to the nutritional intake status. The recipe search unit 2105 may use at least one of the recipe dish nutrient amount information and the recipe dish calories included in the recipe information. In addition, the recipe search unit 2105 may further perform the search using the information included in the recipe search request transmitted by the recipe information search control unit 1107 of the health management server 1.

[0138] The recipe dish nutrient amount information associated with the recipe information, which is used for searching the recipe, may be, for example, the recipe dish nutrient amount information included in the recipe information stored in the recipe DB 24a. Alternatively, the recipe dish nutrient amount information associated with the recipe information may be the food nutrient amount information stored in the food DB 14c in association with the food ID included in the recipe information. The food ID included in the recipe information indicates the dishes that can be cooked with the recipe indicated by the recipe information. Therefore, the food nutrient amount information associated with the same food ID as the food ID included in the recipe information may correspond to the recipe dish nutrient amount information associated with the recipe information.

[0139] The recipe search unit 2105 may search for a recipe in which the total amount of the nutrient intake indicated by, for example, the nutrient intake status information and the content of the nutrient indicated by the recipe dish nutrient amount information satisfies the nutrient intake standard indicated by the nutrient intake standard information. For example, the recipe search unit 2105 may calculate the difference between the reference amount of the nutrient intake within the reference period indicated by the nutrient intake standard information and the nutrient intake within the reference period indicated by the nutrient intake status information as the remaining reference amount. The recipe search unit 2105 may calculate the remaining reference amount for each target nutrient. The recipe search unit 2105 may search for a recipe that satisfies the nutrient intake standard based on the content of the nutrient in the dish that can be cooked according to the recipe indicated by the recipe dish nutrient amount information and the remaining reference amount. For example, the recipe search unit 2105 may determine for each target nutrient for each recipe whether the nutrient intake standard is satisfied. For example, when the nutrient intake standard information includes a lower limit as the reference amount of a certain target nutrient, the difference from the lower limit is calculated as the remaining reference amount. This difference is called the remaining lower limit. In this case, the recipe search unit 2105 may determine that the nutrient intake standard is satisfied when the content of the nutrient in the dish that can be cooked according to the recipe is equal to or higher than the lower limit. When the nutrient intake standard information includes an upper limit as the reference amount of a certain target nutrient, the difference from the upper limit is calculated as the remaining reference amount. This difference is called the remaining upper limit. In this case, the recipe search unit 2105 may determine that the nutrient intake standard is satisfied when the content of the nutrient in the dish that can be cooked according to the recipe is equal to or lower than the upper limit. When the nutrient intake standard information includes both a lower limit and an upper limit as the reference amount of a certain target nutrient, the recipe search unit 2105 may determine that the nutrient intake standard is satisfied when the content of the nutrient in the dish that can be cooked according to the recipe is equal to or higher than the lower limit and equal to or lower than the upper limit.

[0140] When the nutrient intake standard information includes the tolerable upper intake level as the upper limit for at least some of the target nutrients, the recipe search unit 2105 may search for recipes, for example, for those target nutrients, where the total amount of the nutrient intake within the reference period and the nutrient content in the dishes that can be cooked with the recipes indicated by the recipe dish nutrient amount information is equal to or less than the tolerable upper intake level. The recipe search unit 2105 may exclude from the search results recipes for which the total amount for at least one target nutrient exceeds the tolerable upper intake level. Thereby, it is possible to search for recipes for dishes with a low risk of causing health problems.

[0141] FIG. 15 is a diagram showing an example of the conditions for the amount of nutrients contained in dishes that can be cooked with a recipe. As shown in FIG. 15, assume that the target nutrients include protein, lipid, and carbohydrate. The tolerable upper intake level of protein is 100 grams. The tolerable upper intake level of lipid is 80 grams. The tolerable upper intake level of carbohydrate is 450 grams. A certain health management service user registered the meal record information for breakfast and lunch for today, which is the reference period. The protein intake amount up to that day calculated based on the meal record information is 30 grams. The lipid intake amount is 45 grams. The carbohydrate intake amount is 190 grams. Therefore, the recipe search unit 2105 may search for recipes in which the protein content is 70 grams or less, the lipid content is 80 grams or less, and the carbohydrate content is 260 grams or less.

[0142] When the nutrient intake standard information includes any one of the target amount, the guideline amount, the recommended amount, and the required amount as the standard amount for each target nutrient. In this case, the recipe search unit 2105 may calculate the number of target nutrients that satisfy the nutrient intake standard indicated by the standard amount. Thereby, it is possible to search for recipes for dishes that contribute to the maintenance or improvement of health.

[0143] The recipe search unit 2105 may determine a score for each recipe based on the number of target nutrients that meet the nutrient intake criteria. This score may indicate the priority of presenting the recipe. The higher the score, the higher the priority. For example, the recipe search unit 2105 may increase the score as the number of target nutrients that meet the nutrient intake criteria increases. The recipe search unit 2105 may search for recipes whose determined score is equal to or higher than a predetermined value.

[0144] FIG. 16 is a diagram showing an example of conditions for the amounts of nutrients included in dishes that can be cooked with a recipe. As shown in FIG. 16, assume that the target nutrients include protein, fat, and carbohydrates. The target amount of protein is 50 grams or more and 65 grams or less. The target amount of fat is 30 grams or more and 55 grams or less. The target amount of carbohydrates is 270 grams or more and 320 grams or less. Similar to the case of FIG. 15, the protein intake so far today is 30 grams. The fat intake is 45 grams. The carbohydrate intake is 190 grams. The recipe search unit 2105 may add 1 to the score of a recipe whose protein content is 20 grams or more and 35 grams or less. Also, the recipe search unit 2105 may add 1 to the score of a recipe whose fat content is 5 grams or less. Also, the recipe search unit 2105 may add 1 to the score of a recipe whose carbohydrate content is 80 grams or more and 130 grams or less. Note that for salt, the recipe search unit 2105 may add 1 to the score of a recipe in which the total of the salt intake during the reference period and the amount of salt included in the dish that can be cooked with the recipe is equal to or less than the target amount.

[0145] The recipe search unit 2105 may search for recipes based on the calorie limit, the calories consumed within the reference period included in the nutrient intake status information, and the recipe calories included in the recipe information. For example, when the information prioritized by the health management service user indicates "calorie prioritization", the recipe search unit 2105 may exclude from the search results recipes for which the total of the recipe calories and the calories consumed within the reference period exceeds the calorie limit. Thereby, the risk of calorie overage can be reduced. When the information prioritized by the health management service user indicates "balance prioritization" or when no prioritized information is set, the recipe search unit 2105 does not necessarily have to exclude the recipe from the search results even if the total of the recipe calories and the calories consumed within the reference period exceeds the calorie limit.

[0146] When the nutrient intake status information includes meal record information, the recipe search unit 2105 may calculate the amount of nutrients consumed within the reference period based on the meal record information. Then, the recipe search unit 2105 may search for recipes in the same manner as the method described above based on the calculated amount of nutrients.

[0147] During the reference period, the number of meals consumed by a health management service user so far may be considerably less than the number of meals corresponding to that reference period. For example, when the length of the reference period is one day, assume that the number of meals corresponding to the reference period is three. Assume that the number of meals consumed by the health management service user so far is one. Even in this case, if the total nutrient intake for two meals, which is the sum of the previous nutrient intake and the amount of nutrients contained in the dishes that can be cooked with the recipe, meets the nutrient intake standard, the recipe search unit 2105 may include that recipe in the search results as a recipe according to the nutrient intake situation. Also, during the reference period, the number of meals consumed by the health management service user so far may be equal to or more than the number of meals corresponding to that reference period. For example, when the length of the reference period is one day, assume that the number of meals consumed by the health management service user so far is three. Even in this case, if the total nutrient intake for four meals, which is the sum of the previous nutrient intake and the amount of nutrients contained in the dishes that can be cooked with the recipe, meets the nutrient intake standard, the recipe search unit 2105 may include that recipe in the search results as a recipe according to the nutrient intake situation. Regardless of the number of meals, it is only necessary to meet the nutrient intake standard.

[0148] When the health management service user can input recipe search conditions, the recipe search unit 2105 may search for a recipe that is according to the nutrient intake situation of the health management service user and that meets the search conditions. Here, the health management service user may perform the search based on the recipe information stored in the recipe DB 24a. For example, when the search conditions include keywords such as recipe title, dish name, or ingredient name. The recipe search unit 2105 may perform the search based on at least one of the recipe title, dish name, ingredient name, recipe comment, and cooking method information included in the recipe information. When the search conditions include the category of the recipe, the recipe search unit 2105 may perform the search based on the recipe category ID included in the recipe information.

[0149] The recipe search unit 2105 may transmit recipe search result information indicating the results of the recipe search to the health management server 1.

[0150] The recipe presentation order determination unit 2106 may determine the presentation order of the recipes searched by the recipe search unit 2105. For example, the recipe presentation order determination unit 2106 may calculate the score of each recipe in the same manner as the method described above. The recipe presentation order determination unit 2106 may set the presentation order of the recipe higher as the score is higher. The recipe search unit 2105 may transmit recipe search result information including the presentation order determined by the recipe presentation order determination unit 2106 for each searched recipe to the health management server 1. Note that the recipe search unit 2105 may also serve as the recipe presentation order determination unit 2106.

[0151] Note that the system control unit 21 may receive search conditions input by the recipe service user from the recipe service user terminal 6. The recipe search unit 2105 may search for recipes that meet the search conditions without considering the nutritional intake status of the recipe service user. The system control unit 21 may transmit the screen information of the recipe search result screen indicating the results of the recipe search by the recipe search unit 2105 to the recipe service user terminal 6. The system control unit 21 may transmit the screen information of the recipe screen of the recipe selected by the recipe service user among the searched recipes to the recipe service user terminal 6. The health management server 1 or the service server 2 may function so that the recipe service user can request the cooking agency using the recipe corresponding to this recipe screen.

[0152] [1-3-3. Point Management Server] Next, the functional overview of the system control unit 31 in the point management server 3 will be described with reference to FIG. 17. FIG. 17 is a diagram showing an example of the functional blocks of the system control unit 31 in the point management server according to the present embodiment. The system control unit 31 may function as a point addition request receiving unit 3101, a point addition unit 3102, etc. as shown in FIG. 17 by the CPU 31a reading and executing various program codes included in the point management server program.

[0153] The point addition request receiving unit 3101 may receive a point addition request transmitted by the reward granting unit 1117 of the health management server 1.

[0154] The point addition unit 3102 may increase the available point number of the recipe poster whose request for cooking agency has been received by the cook based on the point addition request received by the point addition request receiving unit 3101. For example, the point addition unit 3102 may update this available point number by adding the added point number included in the point addition request to the available point number stored in the available point DB 34a associated with the user ID of the recipe poster included in the point addition request.

[0155] [1-4. Operation of the Communication System] Next, the operation of the communication system will be described with reference to FIGS. 18 to 24. The system control unit 11 of the health management server 1, the system control unit 21 of the recipe server 2, and the system control unit 31 of the point management server 3 may execute the processes described below according to various program codes included in the server programs they each store.

[0156] The processes shown in FIGS. 18 to 24 are examples, and any process may be executed as long as the purpose is achieved. The order of the processes is not limited to the order shown in FIGS. 18 to 24. Also, at least one of the steps shown in FIGS. 18 to 24 may not be executed.

[0157] FIG. 18 is a sequence diagram showing a processing example of the communication system S at the time of information registration by the cooking proxy. As shown in FIG. 18, the cookable recipe information receiving unit 1101 of the health management server 1 transmits the HTML document of the cookable registration screen to the cooking proxy terminal 5 in response to a request from the cooking proxy terminal 5 (step S101). The cooking proxy terminal 5 displays the cookable registration screen based on this HTML document (step S102). The cooking proxy selects one or more cookable dishes on the cookable registration screen (step S103). The cooking proxy terminal 5 transmits the cookable recipe information including the food and beverage ID of each selected dish and the cooking proxy ID of the cooking proxy to the health management server 1 (step S104). The cookable recipe information storage control unit 1102 of the health management server 1 associates each food and beverage ID included in the cookable recipe information with the cooking proxy ID included in the cookable recipe information and stores it in the cookable recipe DB 14f (step S105).

[0158] After that, in response to a request from the cooking proxy terminal 5, the cooking proxy available material inventory status information receiving unit 1103 of the health management server 1 transmits the HTML document of the cooking proxy available material inventory status setting screen to the cooking proxy terminal 5 (step S106). The cooking proxy terminal 5 displays the cooking proxy available material inventory status setting screen based on this HTML document (step S107). The cooking proxy selects, as needed, the materials to be subject to inventory status management as materials available for cooking on the cooking proxy available material inventory status setting screen. A list of materials to be subject to inventory status management is displayed on the cooking proxy available material inventory status setting screen. The cooking proxy changes the inventory status of one or more materials (step S108). The cooking proxy terminal 5 transmits cooking proxy available material inventory status information including the material ID and the changed inventory status of each material whose inventory status has been changed, as well as the cooking proxy ID of the cooking proxy, to the health management server 1 (step S109). The cooking proxy available material inventory status information storage control unit 1104 of the health management server 1 updates the cooking proxy available material inventory status DB 14g based on the cooking proxy available material inventory status information (step S110). For example, for each material ID included in the cooking proxy available material inventory status information, the cooking proxy available material inventory status information storage control unit 1104 rewrites the inventory status stored in the cooking proxy available material inventory status DB 14g in association with the combination of the material ID and the cooking proxy ID included in the cooking proxy available material inventory status information with the changed inventory status.

[0159] FIG. 19 is a sequence diagram showing an example of the processing of the communication system S when a recipe contributor posts a recipe. As shown in FIG. 19, the recipe information receiving unit 2101 of the recipe server 2 transmits an HTML document of a recipe posting screen to the recipe contributor terminal 6 in response to a request from the recipe contributor terminal 6 (step S201). The recipe contributor terminal 6 displays a recipe posting screen based on this HTML document (step S202). The recipe contributor inputs recipe information on the recipe posting screen (step S203). The recipe contributor transmits the input information and recipe information including the user ID of the recipe contributor to the recipe server 2 (step S204). The recipe information storage control unit 2102 stores the transmitted recipe information in the recipe DB 24a (step S205). At this time, the recipe information storage control unit 2102 generates a recipe ID and a URL of each image data. In addition, the recipe information storage control unit 2102 acquires a food and beverage ID of a dish that can be cooked with the recipe based on the recipe title or dish name included in the recipe information. The recipe information storage control unit 2102 adds the recipe ID, URL, and food and beverage ID to the recipe information.

[0160] Next, for each ingredient information included in the recipe information stored in step S205, the cooked food nutrient amount calculation unit 2103 acquires the ingredient nutrient amount information and the ingredient calories associated with the ingredient name included in the ingredient information from the ingredient DB 24b (step S206). Next, for each ingredient information, the cooked food nutrient amount calculation unit 2103 calculates the nutrient content of the ingredient used in the recipe for each target nutrient amount based on the amount of the ingredient, the ingredient nutrient amount information, and the number of people for the ingredient (step S207). Next, the cooked food nutrient amount calculation unit 2103 calculates the nutrient content of the cooked food that can be cooked in the recipe by adding up the nutrient contents of those ingredients (step S208). Next, for each ingredient information, the cooked food nutrient amount calculation unit 2103 calculates the calories of the ingredient used in the recipe based on the amount of the ingredient, the ingredient calories, and the number of people for the ingredient (step S209). Next, the cooked food nutrient amount calculation unit 2103 calculates the recipe cooked food calories by adding up the calories of those ingredients (step S210). Next, the cooked food nutrient amount information storage control unit 2104 adds the recipe cooked food nutrient amount information including the content calculated in step S208 and the recipe cooked food calories to the recipe information stored in step S205 (step S211).

[0161] FIG. 20 is a sequence diagram showing a processing example of the communication system S when a health management service user records the content of a meal. For example, a health management service user performs an operation of selecting to add the content of a meal in a health management application. Then, as shown in FIG. 20, the health management service user selects a meal date and a meal category, and selects one or more foods and drinks consumed in the meal (step S301). The health management service user terminal 7 transmits meal record information including the selected meal date and meal category, a food and drink list including the food and drink IDs of the selected foods and drinks, and the user ID of the health management service user to the health management server 1 (step S302). The nutrient intake status information acquisition unit 1105 of the health management server 1 stores the transmitted meal record information in the meal record DB 14d (step S303). Next, the nutrient intake status information acquisition unit 1105 calculates the nutrient intake amount and meal calories in the meal based on the food and drink IDs included in the meal record information, and the food and drink nutrient amount information and meal calories stored in the food and drink DB 14c (step S304). Next, the calculated nutrient intake amount and meal calories are added to the meal record information stored in the meal record DB 14d in step S303 (step S305).

[0162] FIG. 21 is a sequence diagram showing a processing example of the communication system S when a recipe according to the nutritional intake status is presented to a health management service user. For example, a health management service user performs an operation of selecting a request for recipe proposal in the health management application. In response to this operation, the health management service user terminal 7 transmits a recipe proposal request including the user ID of the health management service user to the health management server 1 (step S401). The nutritional intake status information acquisition unit 1105 of the health management server 1 that has received the recipe proposal request searches the meal record DB 14d for meal record information including the user ID included in the recipe proposal request and the meal days within the reference period (step S402). Next, the nutritional intake status information acquisition unit 1105 calculates the intake amount of each target nutrient within the reference period and the calories consumed within the reference period based on the meal nutrient amount information and meal calories included in each acquired meal record information (step S403). Next, the nutritional intake standard information acquisition unit 1106 acquires nutritional intake standard information and calorie upper limit from the nutritional intake standard DB 14b (step S404). For example, the nutritional intake standard information acquisition unit 1106 acquires the gender, age, and weight associated with the user ID included in the recipe proposal request from the user DB 14a. The nutritional intake standard information acquisition unit 1106 acquires nutritional intake standard information and calorie upper limit corresponding to those gender, age, and weight. Next, the recipe information search control unit 1107 acquires the emphasis information associated with the user ID included in the recipe proposal request from the user DB 14a (step S405). Next, the recipe information search control unit 1107 transmits a recipe search request including the amount of nutrients consumed within the reference period, the calories consumed within the reference period, nutritional intake standard information, calorie upper limit, and emphasis information to the recipe server 2 (step S406).

[0163] Upon receiving a recipe search request, the recipe search section 2105 of the recipe server 2 searches for recipes among a plurality of recipes posted on the recipe service, where the total of the intake amount within the reference period included in the recipe search request and the nutrient content indicated by the recipe dish nutrient amount information stored in the recipe DB 24a is equal to or less than the tolerance upper limit amount (step S407). For example, for each nutrient for which a tolerance upper limit amount is set among the target nutrients, the recipe search section 2105 determines whether the total of the intake amount within the reference period and the nutrient content in the recipe dish is equal to or less than the tolerance upper limit amount. The recipe search section 2105 searches for recipes where the total of the intake amount within the reference period and the nutrient content in the recipe dish is equal to or less than the tolerance upper limit amount for all nutrients as search results. Next, the recipe search section 2105 excludes from the search results recipes where the total of the calories consumed within the reference period included in the recipe search request and the recipe dish calories stored in the recipe DB 24a exceeds the calorie upper limit included in the recipe search request (step S408). If the importance information included in the recipe search request is set to "balance importance", the recipe search section 2105 may skip step S408. Next, the cooking agent presentation order determination section 1111 determines a score for each recipe included in the search results (step S409). For example, the cooking agent presentation order determination section 1111 determines for each target nutrient whether the total of the amount of nutrients consumed within the reference period and the nutrient content indicated by the recipe dish nutrient amount information for the searched recipe meets the criteria indicated by the nutrient intake criteria information. The cooking agent presentation order determination section 1111 increases the score as the number of target nutrients meeting the criteria increases. Next, the cooking agent presentation order determination section 1111 determines the presentation order of each recipe according to the determined score (step S410). For example, the cooking agent presentation order determination section 1111 increases the presentation order as the score increases. Next, the cooking agent presentation order determination section 1111 transmits recipe search result information including the recipe ID, recipe title, cooking image URL, ingredient information, URL of the HTML document of the recipe screen, food and beverage ID of the cookable dish, and presentation order of each searched recipe to the health management server 1 (step S411).

[0164] The presentation recipe information transmission unit 1108 of the health management server 1 that has received the recipe search result information generates an HTML document for the recipe search result screen based on the recipe search result information (step S412). For example, the presentation recipe information transmission unit 1108 obtains a template of the HTML document for the recipe search result screen from the storage unit 14. The presentation recipe information transmission unit 1108 adds the recipe ID, recipe title, cooking image URL, and ingredient name of each searched recipe to this HTML document. At this time, the presentation recipe information transmission unit 1108 arranges the information of the searched recipes in the order according to the presentation order. Next, the presentation recipe information transmission unit 1108 transmits the generated HTML document to the health management service user terminal 7 (step S413). The health management service user terminal 7 displays a recipe search result screen based on this HTML document (step S414).

[0165] FIG. 22 is a sequence diagram showing a processing example of the communication system S when searching for a cooking agent. After step S414, the health management service user selects any one of the searched recipes from the recipe search result screen (step S501). The health management service user terminal 7 transmits a recipe screen request including the URL of the HTML document of the recipe screen of the selected recipe to the recipe server 2 (step S502). The recipe server 2 obtains the HTML document of the recipe screen associated with the URL included in the recipe screen request from the storage unit 24 and transmits this HTML document to the health management service user terminal 7 (step S503). The health management service user terminal 7 displays a recipe screen based on this HTML document (step S504).

[0166] The health management service user performs an operation of selecting the recipe corresponding to the recipe screen as the recipe for which cooking agency is requested on the recipe screen (step S505). In response to this operation, the health management service user terminal 7 transmits a selected recipe cooking agency request including the recipe ID of the selected recipe and the user ID of the health management service user to the health management server 1 (step S506).

[0167] Upon receiving a request for proxy cooking of a selected recipe, the proxy cook search unit 1110 of the health management server 1 searches for proxy cooks registered in the health management service whose provided location of the health management service user is within the corresponding area (step S507). For example, the proxy cook search unit 1110 may obtain the address of the health management service user associated with the user ID included in the proxy cooking request for the selected recipe from the user DB 14a as information indicating the provided location. The proxy cook search unit 1110 performs the search based on the address of the health management service user and the corresponding area information stored in the proxy cook DB 14e. Next, the proxy cook search unit 1110 extracts proxy cooks capable of proxy cooking the dishes of the selected recipe from the searched proxy cooks (step S508). For example, the proxy cook search unit 1110 obtains the food and beverage ID of the dishes that can be cooked with the recipe indicated by the recipe ID included in the proxy cooking request for the selected recipe from the recipe search result information received from the recipe server 2. The proxy cook search unit 1110 performs the extraction based on the food and beverage ID, the proxy cook ID stored in the proxy cookable dish DB 14f, and the food and beverage ID. Next, the proxy cook search unit 1110 extracts, as the search result, proxy cooks who have all the ingredients used in the selected recipe as ingredients that can be used for proxy cooking from among the proxy cooks extracted in step S508 (step S509). For example, the proxy cook search unit 1110 obtains the ingredient information of the selected recipe from the recipe search result information. The proxy cook search unit 1110 obtains the ingredient ID associated with the ingredient name included in each ingredient information from the ingredient DB 24b of the recipe server 2. For each proxy cook extracted in step S508, the proxy cook search unit 1110 obtains the possession status associated with each obtained ingredient ID from the proxy cooking available ingredient possession status DB 14g. The proxy cook search unit 1110 performs the extraction based on the obtained possession status. Next, the proxy cook presentation order determination unit 1111 determines the presentation order of each proxy cook extracted as the search result in step S509 according to the distance from the provided location of the health management service user to the place of residence of the proxy cook (step S510). For example, the proxy cook presentation order determination unit 1111 increases the presentation order as the distance gets shorter.Next, the presenting cooking agent information transmitting unit 1112 generates an HTML document for the cooking agent search result screen based on the basic cooking agent information stored in the cooking agent DB 14e (step S511). For example, the presenting cooking agent information transmitting unit 1112 acquires a template of the HTML document for the cooking agent search result screen from the storage unit 14. The presenting cooking agent information transmitting unit 1112 adds the cooking agent ID, cooking agent name, URL of the cooking agent image, address of the cooking agent, and appeal information of each searched cooking agent to this HTML document. At this time, the presenting cooking agent information transmitting unit 1112 arranges the information of the cooking agents extracted as search results in an order according to the presentation order. Next, the presenting cooking agent information transmitting unit 1112 transmits the generated HTML document to the health management service user terminal 7 (step S512). The health management service user terminal 7 displays the cooking agent search result screen based on this HTML document (step S513).

[0168] FIG. 23 is a sequence diagram showing a processing example of the communication system S at the time of requesting cooking assistance. After step S513, the health management service user selects one of the searched cooking assistants from the cooking assistant search result screen (step S601). The health management service user terminal 7 transmits a selected cooking assistant cooking assistance request including the cooking assistant ID of the selected cooking assistant and the user ID of the health management service user to the health management server 1 (step S602). The cooking assistance request information transmission unit 1114 of the health management server 1 that has received the selected cooking assistant cooking assistance request stores the cooking assistance request record information in the cooking assistance request DB 14h (step S603). For example, the cooking assistance request information transmission unit 1114 generates a request ID. Also, the cooking assistance request information transmission unit 1114 acquires the cooking price associated with the food and beverage ID of the dish that can be cooked with the selected recipe from the food and beverage DB 14c. Further, the cooking assistance request information transmission unit 1114 adds the delivery fee to the cooking price to calculate the payment amount. The cooking assistance request information transmission unit 1114 acquires the user ID and the cooking assistant ID included in the selected cooking assistant cooking assistance request as the requester ID and the requested cooking assistant ID, respectively. The cooking assistance request information transmission unit 1114 acquires, from the recipe server 2, the user ID stored in association with the recipe ID of the selected recipe in the recipe DB 24a of the recipe server 2 as the recipe poster ID. The cooking assistance request information transmission unit 1114 generates cooking assistance request record information including the request ID, the requester ID, the requested cooking assistant ID, the recipe ID of the selected recipe, the recipe poster ID, the cooking price, the number of servings, the delivery fee, the payment amount, etc. The cooking assistance request information transmission unit 1114 stores the generated cooking assistance request record information. Next, the cooking assistance request information transmission unit 1114 transmits the cooking assistance request information to the cooking assistant terminal 5 of the selected cooking assistant (step S604). For example, the cooking assistance request information transmission unit 1114 generates cooking assistance request information including the request ID, the recipe title of the selected recipe, the dish name, the ingredient list, and the cooking method information, the URL of the image data of the dish image, the URL of the image data of the cooking method image, and the URL of the HTML document of the recipe screen, the cooking price, the name of the cooking assistant, the address of the provided location, and the number of servings, etc.The cooking agency request information transmission unit 1114 transmits the generated cooking agency request information. Next, the cooking agency request information transmission unit 1114 stores a request status indicating "request transmitted" in the cooking agency request DB 14h in association with the generated request ID (step S605).

[0169] Upon receiving the proxy cooking request information, the proxy cooking terminal 5 displays the proxy cooking request information on the screen, for example, in response to an operation by the proxy cook (step S606). Next, the proxy cook performs an operation to select to accept the proxy cooking request (step S607). In response to this operation, the proxy cooking terminal 5 transmits the acceptance information including the request ID to the health management server 1 (step S608). The proxy cook starts cooking the dish according to the recipe. Here, the inventory status of the ingredients by the proxy cook may change. In that case, the inventory status information stored in the proxy cooking available ingredient inventory status DB 14g may be updated by executing the same processing as the processing shown in steps S106 to S110 shown in FIG. 18. The acceptance information receiving unit 1115 of the health management server 1 that has received the acceptance information changes the request status stored in the proxy cooking request DB 14h to "request accepted" in association with the request ID included in the acceptance information (step S609). Next, the acceptance information receiving unit 1115 executes a settlement process for the proxy cooking requester to pay the payment amount (step S610). Examples of settlement means available for the settlement process include credit cards, debit cards, electronic money, and the like. For example, the user DB 14a may store information on credit cards preset for each health management service user. The credit card information may include, for example, the card number, expiration date, name of the credit card user, and the like. The acceptance information receiving unit 1115 performs a settlement process in cooperation with a system (not shown) of the credit card company, for example, using the credit card information of the proxy cooking requester and the payment amount. Next, the delivery request information transmitting unit 1116 transmits the delivery request information to the delivery management server 4 (step S612). Next, the acceptance information receiving unit 1115 transmits a proxy cooking request acceptance notice indicating that the proxy cooking request has been accepted by the selected proxy cook to the health management service user terminal 7 (step S612). For example, the acceptance information receiving unit 1115 may transmit the proxy cooking request acceptance notice by push notification of the health management application or an email. Based on the proxy cooking request acceptance notice, the health management service user terminal 7 displays on the screen that the proxy cooking request has been accepted (step S613).

[0170] FIG. 24 is a sequence diagram showing a processing example of the communication system S when a reward is given to a recipe submitter. The processing shown in the flowchart of FIG. 24 is executed at any timing after the reception of the reception information by the health management server 1 (step S608). As shown in FIG. 24, the reward granting unit 1117 of the health management server 1 acquires the recipe submitter ID from the cooking proxy request record information stored in step S603 (step S701). Next, the reward granting unit 1117 sets the number of added points to a predetermined value (step S702). Next, the reward granting unit 1117 transmits a point addition request including the user ID of the recipe submitter and the number of added points to the point management server 3 (step S703). The point addition unit 3102 of the point management server 3 adds the number of added points included in the transmitted point addition request to the available point number stored in the available point DB 34a associated with the recipe submitter ID included in the point addition request, and updates this available point number (step S704). After transmitting the point addition request, the reward granting unit 1117 transmits a point grant notification indicating that points have been granted to the recipe submitter terminal 6 of the recipe submitter indicated by the acquired user ID (step S705). For example, the reward granting unit 1117 may transmit the point grant notification by email. Based on this point grant notification, the recipe submitter terminal 6 displays the added point number on the screen as the fact that points have been granted to the recipe submitter and the number of points granted (step S706).

[0171] As described above, according to the present embodiment, the health management server 1 may acquire nutritional intake status information. Further, the recipe server 2 may search for one or more recipes according to the nutritional intake status of the health management service user based on the nutritional intake status information and the cooking nutrient amount information associated with the recipe information stored in the storage unit 14. Further, the health management server 1 may transmit the presented recipe information of the searched recipe to the health management service user terminal 7. Further, the health management server 1 may receive, from the health management service user terminal 7, selection recipe identification information for identifying a selection recipe selected by the health management service user as a recipe for which a request for cooking agency is desired among the one or more recipes indicated by the presented recipe information. Further, the health management server 1 may transmit cooking agency request information indicating a request for cooking agency using the selection recipe to the cooking agency terminal 5 used by the cooking agency. In this case, when the cooking agency accepts the request for cooking agency, the cooking agency cooks the dish using the selected recipe. The cooked dish is provided to the health management service user. Therefore, the health management service user can eat the dish without having to cook the dish using the recipe selected by the health management service user. Therefore, it is possible to present a recipe considering the user's health and suppress the labor of cooking by the user.

[0172] Here, the health management server 1 may further search for one or more recipes according to the nutritional intake status of the health management service user based on the nutritional intake standard information. In this case, according to the previous nutritional intake status, it is possible to search for a recipe that can cook a dish such that the nutritional intake of the person who can use the cooking agency meets the standard.

[0173] Here, the recipe server 2 may search for a recipe in which the total of the amount of nutrients indicated by the nutrient intake status information and the amount of nutrients indicated by the cooking nutrient amount information associated with the recipe information satisfies the standard of the nutrient intake amount indicated by the nutrient intake amount standard information. In this case, a recipe is searched for in which the amount of nutrients ingested in the meals taken by the health management service user so far and the amount of nutrients included in the dishes that can be cooked with the recipe satisfy the standard of the nutrient intake amount. Therefore, it is possible to present a recipe considering the user's health.

[0174] Further, the recipe server 2 may calculate the amount of nutrients included in the dishes that can be cooked with the recipe indicated by the recipe information based on the material nutrient amount information stored in the storage unit 24 and the material information included in the recipe information. Further, the recipe server 2 may associate the recipe cooking nutrient amount information indicating the calculated amount with the recipe information and store it in the storage unit 24. Further, the recipe server 2 may search for one or more recipes according to the nutrient intake status of the health management service user based on the cooking nutrient amount information stored in the storage unit 24. In this case, even when the dishes that can be cooked are the same but the amount of nutrients included in the dishes varies depending on the recipe, the recipe can be searched using the material nutrient amount information indicating an appropriate amount as the amount of nutrients included in the dishes that can be cooked with the recipe.

[0175] Further, the health management server 1 may search for a cooking agent having the materials used in the selected recipe as materials that can be used for cooking on behalf of the user based on the material information included in the recipe information stored in the storage unit 24 and the material possession status information stored in the storage unit 14. In this case, it is possible to search for a cooking agent that satisfies the conditions of the request destination for cooking on behalf of the user using the recipe selected by the health management service user in terms of the materials possessed.

[0176] Further, the health management server 1 may further search for a cooking agent within the service range whose location is within the service range of the health management service user based on the health management service user location information and the service range information stored in the storage unit 14. In this case, a cooking agent whose service range capable of providing the dishes cooked by the cooking agent includes the location of the health management service user is searched for. Therefore, in terms of geographical location, a cooking agent that meets the conditions of the cooking agent request destination can be searched for.

[0177] Further, the health management server 1 may search for a cooking agent that meets the cooking agent request destination conditions predetermined as the conditions of the cooking agent request destination for substituting the cooking using the selected recipe identified by the selected recipe identification information based on the cooking agent information stored in the storage unit 14. Further, the health management server 1 may transmit the cooking agent request information to the cooking agent terminal 5 used by the searched cooking agent. In this case, it is possible to request a suitable cooking agent as the cooking agent request destination to substitute the cooking.

[0178] In addition, the health management server 1 may search for one or more cooking agents that meet the conditions of the cooking agency request destination. Also, the health management server 1 may determine the presentation order of the one or more cooking agents that have been searched. Further, the health management server 1 may transmit presentation cooking agent information that can be presented in the order according to the determined presentation order of the one or more cooking agents that have been searched to the health management service user terminal 7. Additionally, the health management server 1 may receive, from the health management service user terminal 7, selection cooking agent identification information for identifying a selected cooking agent selected by the health management service user as the cooking agency request destination among the one or more cooking agents indicated by the presentation cooking agent information. Moreover, the health management server 1 may transmit cooking agency request information to the cooking agent terminal 5 used by the selected cooking agent identified by the selection cooking agent identification information. In this case, the presentation order of the searched cooking agents is determined. The health management service user who has received the presentation of the one or more searched cooking agencies selects one of them as the cooking agency request destination. The cooking agency request information is transmitted to the requester terminal used by the selected cooking agent. Cooking agents with a higher presentation order tend to be more likely to be selected by the health management service user as the cooking agency request destination. Therefore, the ease of selection of the cooking agent can be controlled by the presentation order.

[0179] Here, the health management server 1 may increase the presentation order of the cooking agent closer to the position of the health management service user based on the health management service user location information and the cooking agent location information stored in the storage unit 14. In this case, the cooking agent closer to the position of the health management service user can be made more likely to be selected as the cooking agency request destination.

[0180] In addition, the health management server 1 may transmit presentation recipe information indicating that any one or more of the viewable recipes can be presented to the health service user terminal 7. Further, the health management server 1 may receive, from the health service user terminal 7, selection recipe identification information for identifying a selection recipe selected by the health service user as a recipe for which a request for proxy cooking is desired among the one or more recipes indicated by the presentation recipe information. Further, the health management server 1 may search for a restaurant that has the ingredients used in the selection recipe as ingredients that can be used for proxy cooking based on the ingredient information stored in the storage unit 24 and the ingredient possession status information stored in the storage unit 14. Further, the health management server 1 may transmit proxy cooking request information to the proxy cook terminal 5 used by the searched restaurant. In this case, it is possible to search for a restaurant that is the destination of the proxy cooking request so that the ingredients possessed by the restaurant are effectively used.

[0181] Here, the health management server 1 may search for a restaurant that has extra ingredients used in the selection recipe. In this case, the extra ingredients possessed by the restaurant can be effectively utilized.

[0182] In addition, the health management server 1 may receive, from the proxy cook terminal 5 used by the restaurant, input ingredient possession status information indicating the possession status input by the restaurant as the possession status of the ingredients that the restaurant can use for proxy cooking. Further, the health management server 1 may store the input ingredient possession status information in the storage unit 14 as ingredient possession status information. In this case, the storage status used for searching for a restaurant can be input by the restaurant.

[0183] In addition, the health management server 1 may receive, from the cooking agent terminal 5, reception information indicating that the cooking agent has accepted the cooking agency request indicated by the cooking agency request information. Further, when the reception information is received, the health management server 1 may give a reward to the recipe poster of the selected recipe based on the poster identification information included in the recipe information of the selected recipe among the recipe information stored in the storage unit 24. In this case, the poster of the recipe used for the cooking agency can obtain the reward. Therefore, the motivation to post a recipe can be given to the user.

[0184] Here, the health management server 1 may give points as a reward. In this case, the recipe poster can obtain points.

[0185] Further, the health management server 1 may give a reward by updating the ownership target status information stored in the storage unit 34 for the recipe poster.

[0186] [2. Second Embodiment] Next, the second embodiment will be described with reference to FIG. 25. Except for the points described below, this embodiment may be the same as the embodiments described so far. In the first embodiment, the health management server 1 causes the health management service user terminal 7 to present the information of the cooking agents searched under the cooking agency request destination conditions, and the health management service user selects the cooking agent to be the cooking agency request destination from among the presented cooking agents. In this embodiment, the health management server 1 may determine the cooking agent to be the cooking agency request destination among the cooking agents that satisfy the cooking agency request destination conditions.

[0187] For example, the cooking agent search unit 1110 may identify the cooking agent with the highest presentation rank using the same or a similar method as the method by which the cooking agent presentation rank determination unit 1111 determines the presentation rank. The cooking agent search unit 1110 may determine the cooking agent to be the cooking agency request destination as the cooking agent with the highest presentation rank.

[0188] The cooking proxy search unit 1110 may search for the cooking proxy at the closest location to the location of the available cooking proxy users based on the health management service user location information and the cooking proxy location information. Examples of being close from the location of the available cooking proxy users to the location of the cooking proxy include a short distance and a short travel time. The cooking proxy search unit 1110 may calculate the distance or travel time in the same manner as the method described in the first embodiment. The cooking proxy search unit 1110 may search for the cooking proxy or the food service establishment at the closest location to the location of the available cooking proxy users among the cooking proxies or food service establishments that have the ingredients used in the selected recipe as ingredients available for cooking proxy.

[0189] The cooking proxy request information transmission unit 1114 may transmit the cooking proxy request information to the cooking proxy terminal 5 used by the cooking proxy searched by the cooking proxy search unit 1110.

[0190] FIG. 25 is a sequence diagram showing an example of the processing of the communication system S at the time of searching for a cooking proxy. In FIG. 25, the same reference numerals are given to the same processes as in FIG. 22. As shown in FIG. 25, first, steps S501 to S509 are executed. Next, the cooking proxy search unit 1110 searches for the cooking proxy with the closest domicile from the provided location of the health management service user among the cooking proxies extracted in step S509 (step S521). Next, the cooking proxy request information transmission unit 1114 stores the cooking proxy request record information in the cooking proxy request DB 14h (step S621). At this time, the cooking proxy request information transmission unit 1114 includes the cooking proxy ID of the searched cooking proxy as the requested cooking proxy ID in the cooking proxy request record information. In other respects, step S621 may be the same as step S603 shown in FIG. 23. Next, the cooking proxy request information transmission unit 1114 transmits the cooking proxy request information to the cooking proxy terminal 5 of the searched cooking proxy (step S622). Thereafter, steps S605 to S613 shown in FIG. 23 are executed.

[0191] As described above, according to this embodiment, the cooking agent closest to the location of the health management service user is searched for. The cooking agent request information is transmitted to the cooking agent terminal 5 of the searched cooking agent. Therefore, it is possible to request a cooking agent with a small burden of movement between the location of the cooking agent and the location of the cooking agent user to perform cooking agency.

[0192] [3. Third Embodiment] Next, the third embodiment will be described with reference to FIGS. 26 to 28. Except for the points described below, this embodiment may be the same as at least one of the embodiments described so far. In this embodiment, the presentation order in the search results of the cooking agent may be determined according to the expiration date of the materials available for cooking agency.

[0193] FIG. 26(a) is a diagram showing an example of information stored in the cooking agency available material possession status DB 14g of the health management server 1. As shown in FIG. 26(a), in the cooking agency available material possession status DB 14g, as possession status information, a cooking agent ID, a material ID, a possession status, an expiration date, etc. may be stored in association with each other. The expiration date may be valid when the possession status indicates that the material is in possession. The expiration date may indicate until when the material indicated by the material ID can be used for cooking as a material possessed by the cooking agent indicated by the cooking agent ID. The expiration date may be indicated by a date or by a date and time. The expiration date may be settable by the cooking agent.

[0194] FIG. 26(b) is a diagram showing an example of the possession status of materials available for cooking agency. As shown in FIG. 26(b), the restaurant C possesses carrots, white leeks, and potatoes as materials available for cooking agency. The expiration date of the carrots is August 15th. The expiration date of the white leeks is August 12th. The expiration date of the potatoes is August 21st. The restaurant C does not possess any of daikon radish, tomatoes, and onions as materials available for cooking agency.

[0195] The cooking agency available material possession status information receiving unit 1103 may acquire, from the cooking agency user terminal 5, cooking agency available material possession status information indicating the materials possessed by the cooking agency user as materials available for cooking agency and the expiration dates of those materials. For example, the cooking agency available material possession status information receiving unit 1103 may transmit screen information of a cooking agency available material possession status setting screen on which the expiration date of the material can be set, to the cooking agency user terminal 5. On the cooking agency available material possession status setting screen, the cooking agency user sets or changes the possession status of the material and also sets or changes the expiration date. The expiration date to be set may be, for example, the expiration date, the best-before date, or a date determined by the cooking agency user. For materials among the materials available for cooking agency for which the expiration date is not imminent, the cooking agency user may leave the expiration date unset. The cooking agency user terminal 5 may transmit cooking agency available material possession status information including the material ID of the material for which the possession status or expiration date has been changed, the possession status and expiration date of that material, and the cooking agency user ID of that cooking agency user, to the health management server 1. The cooking agency available material possession status storage control unit 1104 may store the transmitted cooking agency available material possession status information in the cooking agency available material possession status DB 14g. For example, the cooking agency available material possession status storage control unit 1104 may, for each material ID included in the cooking agency available material possession status information, rewrite the possession status and expiration date stored in the cooking agency available material possession status DB 14g in association with the combination of the material ID and the cooking agency user ID included in the cooking agency available material possession status information, with the possession status and expiration date included in the cooking agency available material possession status information.

[0196] The cooking agent presentation order determination unit 1111 may determine the presentation order of one or more searched cooking agents based on the ingredient information included in the recipe information of the selected recipe and the cooking agent available ingredient possession status information stored in the cooking agent available ingredient possession status DB 14g, which indicates the possession status and expiration date of the ingredients. At this time, the cooking agent presentation order determination unit 1111 may increase the presentation order of the cooking agent whose expiration date of the ingredients used in the selected recipe is closer to the present. Thereby, the loss of ingredients due to the expiration of the expiration date can be suppressed. When a plurality of ingredients are used for cooking using the recipe, for example, the cooking agent presentation order determination unit 1111 may determine the presentation order for each cooking agent using the closest expiration date among the expiration dates of those ingredients.

[0197] FIG. 27 is a diagram showing an example of determining the presentation order of cooking agents. As shown in FIG. 27, the dish that can be cooked with the recipe selected by the health management service user is tomato sauce spaghetti. The ingredients used in the selected recipe are spaghetti, tomatoes, onions, garlic, olive oil, salt, and pepper. Here, salt and pepper may be considered to be possessed by all cooking agents. The cooking agents searched as cooking agents that satisfy the cooking agency request destination conditions include at least restaurant E and restaurant F. Restaurant E and restaurant F each have spaghetti, tomatoes, onions, garlic, and olive oil. In restaurant E, the expiration dates of spaghetti and olive oil are not set. The expiration date of tomatoes is August 10th. The expiration date of onions is August 12th. The expiration date of garlic is August 16th. Therefore, the closest expiration date is August 10th. In restaurant F, the expiration date of spaghetti is December 31st. The expiration date of tomatoes is August 12th. The expiration date of onions is August 11th. The expiration date of garlic is August 15th. The expiration date of olive oil is not set. Therefore, the closest expiration date is August 11th. Based on August 10th, which is the expiration date for restaurant E, and August 11th, which is the expiration date for restaurant F, the cooking agent presentation order determination unit 1111 makes the presentation order of restaurant E higher than that of restaurant F.

[0198] When there are a plurality of cooking agents with the same expiration date of ingredients, the cooking agent presentation order determination unit 1111 may further determine the presentation order for those cooking agents based on another condition. For example, the cooking agent presentation order determination unit 1111 may make the presentation order of a cooking agent higher as the domicile of the cooking agent is closer to the provided location of the health management service user.

[0199] FIG. 28 is a sequence diagram showing a processing example of the communication system S at the time of searching for a cooking agent. In FIG. 28, the same reference numerals are given to the same processes as those in FIG. 22. As shown in FIG. 28, first, steps S501 to S509 are executed. Next, for each cooking agent extracted as a search result in step S509, the cooking agent presentation order determination unit 1111 determines the presentation order of each extracted cooking agent based on the expiration date of the materials used in the selected recipe (step S531). For example, the cooking agent presentation order determination unit 1111 increases the presentation order as the expiration date is closer to the present. Next, steps S511 to S513 are executed.

[0200] As described above, according to the present embodiment, the presentation order of the cooking agent having the material with a closer expiration date becomes higher. The cooking agent with a higher presentation order tends to be selected as the request destination for cooking agency by the health management service user with a higher probability. Therefore, it is possible to suppress the loss of materials due to the expiration of the expiration date.

[0201] [4. Fourth Embodiment] Next, the fourth embodiment will be described. Except for the points described below, this embodiment may be the same as at least one of the embodiments described so far. In the third embodiment, the health management server 1 determines the presentation order of the cooking agents that satisfy the cooking agency request destination conditions based on the expiration date of the materials. In this embodiment, the health management server 1 may determine the cooking agent that becomes the request destination for cooking agency as the cooking agent with the shortest expiration date of the materials. Similar to the third embodiment, the expiration date may be stored in the available cooking material possession status DB 14g.

[0202] The cooking agent search unit 1110 may search for the cooking agent with the closest expiration date of the ingredients used in the selected recipe based on the ingredient information included in the recipe information of the selected recipe and the cooking agent available ingredient possession status information stored in the cooking agent available ingredient possession status DB 14g. Here, the cooking agent search unit 1110 may search for the cooking agent with the closest expiration date of the ingredients used in the selected recipe among the cooking agents that have the ingredients used in the selected recipe as ingredients available for cooking agency. For example, in step S521 shown in FIG. 25, the cooking agent search unit 1110 may search for the cooking agent with the closest expiration date of the ingredients used in the selected recipe among the cooking agents extracted in step S509. The cooking agency request information transmission unit 1114 may transmit the cooking agency request information to the cooking agent terminal 5 used by the cooking agent searched by the cooking agent search unit 1110. When there are a plurality of cooking agents with the closest expiration date of the ingredients used in the selected recipe, for example, steps S511 to S513 shown in FIG. 22 may be executed. Thereby, the health management service user may select a cooking agent to request cooking agency from among a plurality of cooking agents. The cooking agent search unit 1110 may search for the cooking agent or restaurant with the closest expiration date of the ingredients used in the selected recipe among the cooking agents or restaurants that have the ingredients used in the selected recipe as ingredients available for cooking agency.

[0203] As described above, according to the present embodiment, based on the ingredient possession status information of the ingredients used in the selected recipe, the cooking agent with the closest expiration date of the ingredients is searched. The cooking agency request information is transmitted to the cooking agent terminal 5 of the searched cooking agent. Therefore, it is possible to suppress the loss of ingredients due to the expiration date.

[0204] [5. Fifth Embodiment] Next, the fifth embodiment will be described with reference to FIGS. 29 to 31. Except for the points described below, this embodiment may be the same as at least one of the embodiments described so far. In the embodiments described so far, the cooking price in proxy cooking was determined in advance for each dish. In this embodiment, the proxy cook may be able to set the cooking price. The health management server 1 may determine the presentation order of the searched proxy cooks according to the cooking price set by the proxy cook.

[0205] FIG. 29(a) is a diagram showing an example of information stored in the proxy-cookable dish DB 14f of the health management server 1. As shown in FIG. 29(a), in the proxy-cookable dish DB 14f, as proxy-cookable dish information, a proxy cook ID, a food and drink ID, a cooking price, etc. may be stored in association with each other. The cooking price may indicate the price of the dish when the proxy cook indicated by the proxy cook ID performs proxy cooking of the dish indicated by the food and drink ID.

[0206] FIG. 29(b) is a diagram showing examples of proxy-cookable dishes. As shown in FIG. 5, the dishes that can be cooked on behalf of the diner at restaurant A include tomato spaghetti, Napolitana, pomodoro, meat spaghetti, and arrabiata. The cooking price of tomato spaghetti is 900 yen. The cooking price of Napolitana is 1,000 yen. The cooking price of pomodoro is 1,200 yen. The cooking price of meat spaghetti is 1,200 yen. The cooking price of arrabiata is 1,400 yen. The dishes that can be cooked on behalf of the diner at restaurant B include mushroom cream spaghetti, tomato sauce spaghetti, pescatore, arrabiata, and carbonara. The cooking price of cream spaghetti is 1,500 yen. The cooking price of tomato sauce spaghetti is 1,400 yen. The cooking price of pescatore is 1,600 yen. The cooking price of arrabiata is 1,500 yen. The cooking price of carbonara is 1,500 yen. Thus, even for the same dish, the cooking price may vary depending on the proxy cook.

[0207] The cooking proxy available recipe information receiving unit 1101 may acquire cooking proxy available recipe information indicating the recipes that can be cooked by the cooking proxy and the prices of those recipes from the cooking proxy terminal 5. For example, the cooking proxy available recipe information receiving unit 1101 may transmit the screen information of the cooking proxy available registration screen where the cooking price can be input to the cooking proxy terminal 5. On the cooking proxy available registration screen, the cooking proxy selects the recipes that can be cooked by the cooking proxy and inputs the cooking price for the selected recipes. The cooking proxy terminal 5 may transmit cooking proxy available recipe information including the food and drink ID of the selected recipe, the cooking price of that recipe, and the cooking proxy ID of the cooking proxy to the health management server 1. The cooking proxy available recipe information storage control unit 1102 may store the transmitted cooking proxy available recipe information in the cooking proxy available recipe DB 14f. For example, the cooking proxy available recipe information storage control unit 1102 may associate and store the food and drink ID with the cooking price and the cooking proxy ID included in the cooking proxy available recipe information for each food and drink ID included in the cooking proxy available recipe information.

[0208] The cooking proxy presentation order determination unit 1111 may determine the presentation order of one or more cooking proxies retrieved by the cooking proxy search unit 1110 based on the selected recipe identification information received by the selected recipe identification information receiving unit 1109 and the cooking prices stored in the cooking proxy available recipe DB 14f. Here, the cooking proxy presentation order determination unit 1111 may use the cooking prices of the recipes that can be cooked in the selected recipe for each of the retrieved cooking proxies. For example, the cooking proxy presentation order determination unit 1111 may acquire the food and drink ID of the recipe from the recipe information including the recipe ID of the selected recipe. The cooking proxy presentation order determination unit 1111 may use the cooking price associated with the cooking proxy ID of each of the retrieved cooking proxies and the acquired food and drink ID. The cooking proxy presentation order determination unit 1111 may set the presentation order of the cooking proxy with a lower cooking price higher.

[0209] FIG. 30 is a diagram showing an example of determining the presentation order of cooking agents. As shown in FIG. 30, the dish that can be cooked with the recipe selected by the health management service user is tomato sauce spaghetti. The cooking agents retrieved as cooking agents that satisfy the cooking agent request destination conditions include at least restaurant A and restaurant B. The cooking price of tomato spaghetti at restaurant A is 900 yen. The cooking price of tomato spaghetti at restaurant B is 1,400 yen. Therefore, the cooking agent presentation order determination unit 1111 sets the presentation order of restaurant A higher than the presentation order of restaurant B.

[0210] Note that the cooking agent presentation order determination unit 1111 may set the presentation order of a cooking agent with a higher cooking price higher. For example, the health management service user may be able to select whether to set the presentation order of a cooking agent with a lower cooking price higher or to set the presentation order of a cooking agent with a higher cooking price higher.

[0211] FIG. 31 is a sequence diagram showing an example of the processing of the communication system S during the search for a cooking agent. In FIG. 31, the same reference numerals are given to the same processes as those in FIG. 22. As shown in FIG. 31, first, steps S501 to S509 are executed. Next, for each cooking agent extracted as a search result in step S509, the cooking agent presentation order determination unit 1111 determines the presentation order of each extracted cooking agent based on the cooking price of the dish that can be cooked with the selected recipe (step S531). For example, the cooking agent presentation order determination unit 1111 sets the presentation order of a cooking agent with a lower cooking price higher. Next, steps S511 to S513 are executed. Here, each presentation recipe information display area included in the recipe search result screen may include the cooking price set by the cooking agent for the dish that can be cooked with the selected recipe.

[0212] As described above, according to this embodiment, the cooking agent can set the price for each dish that the cooking agent can substitute for cooking. Then, based on the price of the dish that can be cooked according to the recipe selected by the health management service user, the presentation order of the searched cooking agents is determined. Therefore, based on the price set by the cooking agent for the dish that can be cooked according to the recipe, the ease of selection of the cooking agent can be controlled.

[0213] [6. Sixth Embodiment] Next, the sixth embodiment will be described with reference to FIGS. 32 and 33. Except for the points described below, this embodiment may be the same as at least one of the embodiments described so far. In the fifth embodiment, the cooking agent could input the price of the dish. In addition to this, in this embodiment, as a condition for searching for cooking substitution, the health management service user can set a price condition for the dish. This condition is referred to as a price condition. Similar to the fifth embodiment, the cookable dish DB 14f may store the cooking price.

[0214] FIG. 32 is a diagram showing an example of the functional blocks of the system control unit 11 in the health management server 1 according to this embodiment. In FIG. 32, the same elements as those in FIG. 11 are denoted by the same reference numerals. As shown in FIG. 32, the system control unit 11 may function as a cookable dish information receiving unit 1101 to a reward granting unit 1117 and also function as a price condition information receiving unit 1118.

[0215] The price condition information receiving unit 1118 may receive price condition information from the health management service user terminal 7. The price condition information is information indicating price conditions. For example, the recipe screen may include an input field for entering price conditions near the cooking agency request recipe selection element. Alternatively, when the health management service user operates the cooking agency request recipe selection element, a window for receiving input of price conditions may be displayed on the recipe screen. Alternatively, in response to a selection recipe cooking agency request transmitted from the health management service user terminal 7 when the health management service user operates the cooking agency request recipe selection element, the price condition information receiving unit 1118 may transmit screen information of a screen for receiving price conditions to the health management service user terminal 7. The health management service user may be able to input an upper limit value of the cooking price as a price condition. Also, the health management service user may be able to input a lower limit value of the cooking price. Further, the health management service user may be able to input both the lower limit value and the upper limit value of the cooking price. The health management service user terminal 7 may transmit price condition information indicating the input price conditions to the health management server 1. The price condition information may include at least one of the lower limit value and the upper limit value of the price.

[0216] The cooking agent search unit 1110 may search for one or more cooking agents that satisfy the conditions indicated by the price condition information received by the price condition information receiving unit 1118, where the cooking price of the dishes that can be cooked with the selected recipe identified by the selected recipe identification information received by the selected recipe identification information receiving unit 1109 is based on the price information stored in the cookable dish DB 14f. For example, the cooking agent presentation order determination unit 1111 may obtain the food and beverage ID of the dish from the recipe information of the selected recipe. The cooking agent presentation order determination unit 1111 may specify the cooking price associated with the cooking agent ID of each searched cooking agent and the obtained food and beverage ID. The cooking agent presentation order determination unit 1111 may determine whether the cooking price satisfies the price condition by comparing each specified cooking price with at least one of the lower limit value and the upper limit value of the price included in the price condition information. The cooking agent search unit 1110 may search for one or more cooking agents or restaurants that satisfy the conditions indicated by the price condition information, among the cooking agents or restaurants that have the ingredients used in the selected recipe as ingredients that can be used for cooking on behalf of others, and for which the dishes that can be cooked with the selected recipe satisfy the conditions indicated by the price condition information.

[0217] FIG. 33 is a sequence diagram showing a processing example of the communication system S when searching for a cooking agent. In FIG. 33, the same reference numerals are given to the same processes as those in FIG. 22. As shown in FIG. 33, first, steps S504 to S505 are executed. In step S505, when the recipe corresponding to the recipe screen is selected as the recipe for which cooking agency is requested, the health management service user terminal 7 displays a window for inputting price conditions. Next, the health management service user inputs price conditions (step S551). The health management service user terminal 7 transmits a selected recipe cooking agency request including the recipe ID of the selected recipe, the user ID of the health management service user, and price condition information indicating the input price conditions to the health management server 1 (step S552). Next, steps S507 to S509 are executed. Next, the cooking agent search unit 1110 extracts, from the cooking agents extracted in step S509, a cooking agent that satisfies the condition indicated by the price condition information for the cooking price of the dish that can be cooked with the selected recipe as the final search result (step S553). Next, the cooking agent presentation order determination unit 1111 determines the presentation order of each cooking agent extracted as the search result in step S553 according to the distance from the provided location of the health management service user to the place of residence of the cooking agent (step S510). Note that the cooking agent presentation order determination unit 1111 may determine the presentation order of the cooking agents according to the cooking price of the dish that can be cooked with the recipe, as in the fifth embodiment. Next, steps S511 to S513 are executed.

[0218] As described above, according to the present embodiment, a cooking agent that satisfies the specified conditions is searched for whose cooking price for a dish that can be cooked with the recipe selected by the health management service user satisfies the specified conditions. Therefore, in terms of the price of the dish, it is possible to search for a cooking agent that satisfies the conditions specified by the health management service user as the conditions for the request destination of the cooking agency.

[0219] [7. Seventh Embodiment] Next, this embodiment may be the same as at least one of the embodiments described so far, except as described below for the seventh embodiment. In this embodiment, similar to the fifth embodiment, the cooking agent may be able to set the cooking price. The health management server 1 may search for the catering establishment with the lowest cooking price for the dishes that can be cooked with the selected recipe. Similar to the fifth embodiment, the cooking price may be stored in the cookable dish DB 14f.

[0220] Based on the cooking price stored in the cookable dish DB 14f, the cooking agent search unit 1110 may search for the catering establishment with the lowest price for the dishes that can be cooked with the selected recipe identified by the selected recipe identification information received by the selected recipe identification information receiving unit 1109. For example, in step S521 shown in FIG. 25, the cooking agent search unit 1110 may search for the catering establishment with the lowest price for the dishes that can be cooked with the selected recipe among the cooking agents extracted in step S509. The cooking agent search unit 1110 may search for the cooking agent with the lowest cooking price by comparing, for example, the cooking prices associated with the recipe information of the selected recipe among the cooking prices stored in the cookable dish DB 14f associated with the cooking agent IDs of the searched cooking agents. The cooking agent request information transmission unit 1114 may transmit the cooking agent request information to the cooking agent terminal 5 used by the cooking agent searched by the cooking agent search unit 1110. When there are multiple cooking agents with the lowest cooking price, for example, steps S511 to S513 shown in FIG. 22 may be executed. Thereby, the health management service user may select the cooking agent to request cooking from among multiple cooking agents. The cooking agent search unit 1110 may search for the cooking agent or catering establishment with the lowest price for the dishes that can be cooked with the selected recipe identified by the selected recipe identification information among the cooking agents or catering establishments that have the ingredients used in the selected recipe as ingredients available for cooking.

[0221] As described above, according to this embodiment, the cooking agent with the lowest price set as the price of the dish is searched for. The cooking agent request information is transmitted to the cooking agent terminal 5 of the searched cooking agent. Therefore, it is possible to search for a cooking agent that is advantageous to the health management service user in terms of price.

[0222] [8. Eighth Embodiment] Next, the eighth embodiment will be described with reference to FIGS. 34 to 36. Except for the points described below, this embodiment may be the same as at least one of the embodiments described so far. In this embodiment, the health management server 1 may determine the presentation order in the search results of the cooking agents according to the amount of the usage fee paid by the cooking agent for using the cooking agency matching system or the cooking agency request system.

[0223] Each cooking agent may conclude a contract for paying the usage fee, for example, monthly or annually, with the operator of the cooking agency matching system or the health management service. The amount of the usage fee paid by each cooking agent may be specified by the cooking agent itself. For example, at the start or application of using the cooking agency matching system, the cooking agent may be able to specify the amount of the usage fee. Also, for example, the cooking agent may be able to change the amount of the usage fee after starting to use the cooking agency matching system. The higher the amount of the usage fee, the more preferentially the cooking agent may be treated by the cooking agency matching system. For example, the cooking agent may be able to input the amount of the usage fee. Or, the cooking agent may be able to select any one of a plurality of fee options. The number of options is not limited to a specific number. For example, the cooking agent may be able to select any one of a plurality of fee plans. Each fee plan may be, for example, an option for the amount of the usage fee.

[0224] FIG. 34(a) is a diagram showing an example of information stored in the cooking agent DB 14e of the health management server 1. As shown in FIG. 34(a), the cooking agent DB 14e may store, as cooking agent basic information, a cooking agent ID, a cooking agent name, a proxy category ID, an address, a telephone number, an e-mail address, corresponding area information, a cooking agent image URL, appeal information, a fee plan ID, etc. in association with each other for each cooking agent. The fee plan ID may be identification information for identifying a fee plan selected by the cooking agent as a fee plan to be contracted by the cooking agent indicated by the cooking agent ID.

[0225] FIG. 34(b) is a diagram showing an example of a fee plan. For example, as shown in FIG. 34(b), the selectable fee plans may include Plan X, Plan Y, and Plan Z. The monthly usage fee for Plan X is 10,000 yen. The monthly usage fee for Plan Y is 20,000 yen. The monthly usage fee for Plan Z is 30,000 yen.

[0226] FIG. 35 is a diagram showing an example of a functional block of the system control unit 11 in the health management server 1 according to the present embodiment. In FIG. 35, the same elements as those in FIG. 11 are denoted by the same reference numerals. As shown in FIG. 35, the system control unit 11 may function as a receivable cooking information receiving unit 1101 to a reward granting unit 1117, and may also function as a usage fee information receiving unit 1119 and a usage fee information storage control unit 1120.

[0227] The usage fee information receiving unit 1119 may receive usage fee information from the cooking agent terminal 5. The usage fee information may be information indicating the amount of the usage fee designated by the cooking agent using the cooking agent terminal 5. The information indicating the amount of the usage fee may be, for example, a fee plan ID. It can be said that the fee plan ID indicating the fee plan designated by the cooking agent is information indicating the amount of the usage fee that the cooking agent pays under that fee plan. The usage fee information receiving unit 1119 may transmit the screen information of the fee plan selection screen to the cooking agent terminal 5, thereby transmitting the fee plan selection screen to the cooking agent terminal 5. The fee plan selection screen may be a screen that accepts an operation of selecting a fee plan. The cooking agent selects a fee plan on the fee plan selection screen. The cooking agent terminal 5 may transmit usage fee information including the fee plan ID of the selected fee plan and the cooking agent ID of the cooking agent to the health management server 1. Thereby, the usage fee information receiving unit 1119 may receive the usage fee information.

[0228] The usage fee information storage control unit 1120 may store the usage fee information received by the usage fee information receiving unit 1119 in the storage unit 14. For example, the usage fee information storage control unit 1120 may store the fee plan ID included in the usage fee information in the cooking agent DB 14e in association with the cooking agent ID included in the usage fee information.

[0229] The cooking agent presentation order determination unit 1111 may determine the presentation order of one or more cooking agents retrieved by the cooking agent search unit 1110 based on the usage fee information stored in the storage unit 14 by the usage fee information storage control unit 1120. For example, the cooking agent presentation order determination unit 1111 may set a higher presentation order as the usage fee is higher. In the example of FIG. 35, the cooking agent presentation order determination unit 1111 may set the highest presentation order for the cooking agent who has contracted the fee plan Z. The cooking agent presentation order determination unit 1111 may set the second highest presentation order for the cooking agent who has contracted the fee plan Y. The cooking agent presentation order determination unit 1111 may set the third highest presentation order for the cooking agent who has contracted the fee plan X.

[0230] Figure 36 is a sequence diagram showing an example of the processing of the communication system S when searching for a cooking agent. In Figure 36, the same reference numerals are assigned to the same processing as in Figure 22. As shown in Figure 36, first, steps S504 to S509 are executed. Next, the cooking agent presentation rank determination unit 1111 acquires the charge plan ID associated with the cooking agent ID of each cooking agent extracted as a search result in step S509 from the cooking agent DB14e (step S561). Next, the cooking agent presentation rank determination unit 1111 determines the presentation rank of each cooking agent extracted as a search result according to the usage charge corresponding to the charge plan indicated by the charge plan ID (step S562). For example, the cooking agent presentation rank determination unit 1111 may set a higher presentation rank for a cooking agent who has subscribed to a charge plan with a higher usage charge. Next, steps S511 to S513 are executed.

[0231] As described above, according to the present embodiment, the presentation rank of a cooking agent who has set a higher usage charge is higher. Therefore, a cooking agent who pays a higher usage charge can be more preferentially treated in the cooking agency matching system.

[0232] [9. Ninth Embodiment] Next, the ninth embodiment will be described with reference to FIGS. 37 to 41. Except for the points described below, this embodiment may be the same as at least one of the embodiments described so far. In this embodiment, at least one of the recipe service user and the health service user may be able to evaluate the recipes posted on the recipe service. The recipe server 2 may determine the presentation rank of the searched recipes according to the evaluation of the recipes.

[0233] FIG. 37 is a block diagram showing an example of the schematic configuration of the recipe server 2 according to the present embodiment. In FIG. 37, the same elements as those in FIG. 7 are denoted by the same reference numerals. As shown in FIG. 37, a recipe DB 24a, a material DB 24b, a user evaluation DB 24c, and a recipe evaluation DB 24d may be stored in the storage unit 24 of the recipe server 2.

[0234] FIG. 38 is a diagram showing an example of information stored in the user evaluation DB 24c and the recipe evaluation DB 24d of the recipe server 2.

[0235] The user evaluation DB 24c may store user evaluation information indicating the level of evaluation of a recipe from at least one of a recipe service user and a health service user each time the evaluation is performed. For example, as shown in FIG. 38, the user evaluation DB 24c may store, as user evaluation information, a recipe ID, a user ID, an evaluation date and time, an evaluation value, etc. in association with each other. The recipe ID may indicate the recipe that is the subject of the evaluation. The user ID may indicate the user who performed the evaluation. The evaluation date and time may indicate the date and time when the evaluation was performed. The evaluation value may be a value indicating the level of evaluation. For example, as the evaluation value, any integer from 1 to 5 may be indicated.

[0236] The recipe evaluation DB 24d may store recipe evaluation information indicating the level of evaluation of a recipe from at least one of a recipe service user and a health service user for each recipe. For example, as shown in FIG. 38, the recipe evaluation DB 24d may store, as recipe evaluation information, a recipe ID and an evaluation value, etc. in association with each other. The recipe ID may indicate the recipe that is the subject of the evaluation. The evaluation value may be a value indicating the level of evaluation. The initial value of the evaluation value may be "not evaluated". "Not evaluated" may indicate a state where no one has evaluated the recipe.

[0237] FIG. 39 is a diagram showing an example of a functional block of the system control unit 21 in the recipe server 2 according to the present embodiment. In FIG. 39, the same elements as those in FIG. 13 are denoted by the same reference numerals. As shown in FIG. 39, the system control unit 21 functions as a recipe information receiving unit 2101 to a recipe presentation order determining unit 2106, and may also function as a user evaluation information receiving unit 2107, a user evaluation information storage control unit 2108, a recipe evaluation information updating unit 2109, and the like.

[0238] The user evaluation information receiving unit 2107 may receive user evaluation information indicating the level of evaluation of a recipe from a viewer who has viewed the recipe from at least one of the recipe service user terminal 6 and the health management service user terminal 7. The viewer of the recipe may be, for example, a recipe service user who has viewed the recipe in the recipe service, a health management service user who has viewed the recipe in the health management service, or a cooking agency requester or a cooking agency user who has requested cooking agency in the health management service. The cooking agency requester and the cooking agency user are users who have viewed the recipe on the recipe screen or the recipe search result screen displayed on the health management service user terminal 7 and have requested cooking agency for the recipe. Therefore, the cooking agency requester and the cooking agency user may be included in the viewers of the recipe.

[0239] For example, the recipe screen may include an element that can be operated to display a window for selecting an evaluation value for the recipe corresponding to the recipe screen. Examples of this element include buttons, icons, links, and the like. The viewer selects an evaluation value in the window. The health management service user terminal 7 may transmit user evaluation information including the selected evaluation value, the user ID of the viewer, and the recipe ID of the recipe corresponding to the recipe screen to the recipe server 2. In this way, the user evaluation information storage control unit 2108 may receive the user evaluation information. Note that at least one of the presentation recipe information display areas included in the recipe screen and the recipe search result screen may include information indicating the level of evaluation of the recipe.

[0240] The user evaluation information storage control unit 2108 may store the user evaluation information received by the user evaluation information receiving unit 2107 in the user evaluation information DB 24c.

[0241] The recipe evaluation information update unit 2109 may update the recipe evaluation information stored in the recipe evaluation DB 24d based on the cooking proxy recipe evaluation information received by the user evaluation information receiving unit 2107. At this time, the recipe evaluation information update unit 2109 may perform the update based on the recipe evaluation information received by the user evaluation information receiving unit 2107 and the user evaluation information already stored in the user evaluation DB 24c. For example, the recipe evaluation information update unit 2109 may obtain each evaluation value associated with the recipe ID included in the recipe evaluation information received by the user evaluation information receiving unit 2107 from the user evaluation DB 24c. The recipe evaluation information update unit 2109 may determine a new evaluation value for the recipe indicated by the recipe ID based on the evaluation value included in the recipe evaluation information received by the user evaluation information receiving unit 2107 and the evaluation value obtained from the user evaluation DB 24c. For example, the user evaluation information receiving unit 2107 may calculate the average value of the evaluation values from the user as the evaluation value for the recipe. The user evaluation information receiving unit 2107 may rewrite the evaluation value stored in the recipe DB 24a in association with the recipe ID of the recipe with the determined evaluation value.

[0242] The recipe presentation order determination unit 2106 may determine the presentation order of one or more recipes searched by the recipe search unit 2105 based on the recipe evaluation information stored in the recipe evaluation DB 24d. For example, the recipe presentation order determination unit 2106 may set a higher presentation order for a recipe with a higher evaluation. Alternatively, the recipe presentation order determination unit 2106 may determine the score of each searched recipe based on the number of target nutrients that meet the nutrient intake criteria and the recipe evaluation information. For example, the recipe presentation order determination unit 2106 may increase the presentation order as the number of target nutrients that meet the nutrient intake criteria increases, and may also increase the presentation order as the evaluation is higher.

[0243] FIG. 40 is a sequence diagram showing an example of the processing of the communication system S when a recipe service user makes an evaluation. For example, the recipe service server 2 transmits an HTML document of a recipe search result screen of recipes that meet the search conditions input by the recipe service user to the recipe service user terminal 6, and the recipe service server 2 displays the recipe search result screen. When the recipe user selects any one of the searched recipes, as shown in FIG. 40, the recipe server 2 transmits an HTML document of the screen information of the recipe screen of the selected recipe to the recipe service user terminal 6 (step S801). The recipe service user terminal 6 displays the recipe screen based on this HTML document (step S802). On the recipe screen, the user selects an evaluation value for the recipe (step S803). The recipe service user terminal 6 transmits user evaluation information including the recipe ID of the recipe corresponding to the recipe screen, the selected evaluation value, and the user ID of the recipe service user to the recipe server 2 (step S804). The user evaluation information storage control unit 2108 of the recipe server 2 stores the transmitted user evaluation information in the user evaluation DB 24c (step S805). Next, the recipe evaluation information update unit 2109 updates the evaluation value stored in the recipe evaluation DB 24d in association with the recipe ID included in this user evaluation information (step S806).

[0244] FIG. 41 is a sequence diagram showing an example of the processing of the communication system S when a recipe according to the nutritional intake status is presented to the health management service user. In FIG. 41, the same reference numerals are given to the same processing as in FIG. 21. As shown in FIG. 41, first, steps S401 to S408 are executed. Next, the recipe presentation order determination unit 2106 determines a score for each recipe included in the search result according to the evaluation of the recipe (step S421). For example, the cooking agent presentation order determination unit 1111 acquires the evaluation value associated with the recipe ID of each recipe from the recipe evaluation DB 24d. The cooking agent presentation order determination unit 1111 sets a higher presentation order for a higher evaluation value. Next, steps S410 to S414 are executed.

[0245] As described above, according to the present embodiment, a viewer who has viewed a recipe can evaluate the recipe. Based on the level of this evaluation, the presentation order of those recipes when the searched recipes are presented based on the presented recipe information is determined. Therefore, the recipes can be presented in an order according to the level of evaluation.

[0246] [10. Tenth Embodiment] Next, the tenth embodiment will be described with reference to FIGS. 42 and 43. Except for the points described below, this embodiment may be the same as at least one of the embodiments described so far. In this embodiment, after a request for cooking assistance is received by a cooking assistant, the user of the cooking assistance who requested the cooking assistance may be able to evaluate the recipe used in the cooking assistance. The recipe server 2 may determine the presentation order of the searched recipes according to the evaluation of the recipes. The storage unit 24 of the recipe server 2 may store a user evaluation DB 24c and a recipe evaluation DB 24d.

[0247] FIG. 42 is a diagram showing an example of a functional block of a system control unit 11 in a health management server 1 according to the present embodiment. In FIG. 42, the same elements as those in FIG. 11 are given the same reference numerals. As shown in FIG. 42, the system control unit 11 may function as a cookable recipe information receiving unit 1101 to a reward granting unit 1117, and may also function as a user evaluation information receiving unit 1121.

[0248] At least one of the user evaluation information receiving unit 1121 of the health management server 1 and the recipe presentation order determination unit 2106 of the recipe server 2 may receive user evaluation information indicating the level of evaluation from the cooking proxy user for the selected recipe identified by the selected recipe identification information received by the selection recipe identification information receiving unit 1109 after receiving the reception information from the cooking proxy terminal 5 by the reception information receiving unit 1115 from the health management service user terminal 7. Here, when the health management server 1 receives the user evaluation information from the health management service user terminal 7, the recipe server 2 may receive the user evaluation information from the health management server 1. When the recipe server 2 receives the user evaluation information from the health management service user terminal 7, the health management server 1 may receive the user evaluation information from the recipe server 2. Note that the cooking proxy user may be an example of a viewer who has viewed the recipe. The cooking proxy user is a user who views the recipe on the recipe screen or the recipe search result screen displayed on the health management service user terminal 7 and requests the cooking proxy of the recipe.

[0249] The user evaluation information receiving unit 1121 may perform control so that the user who requested the cooking agency can evaluate the recipe used in the cooking agency corresponding to the cooking agency request information only after the health management server 1 receives the reception information from the cooking agency terminal 5 that has received the cooking agency request information from the health management server 1. Whether the health management server 1 has received the reception information from the cooking agency terminal 5 can be determined from the request status stored in the cooking agency request DB 14h. If the request status is set to any one of "request received", "in delivery", or "delivered", the health management server 1 has received the reception information. The time point from which evaluation becomes possible may be predetermined. For example, evaluation may be possible from the time when the health management server 1 receives the reception information, or evaluation may be possible from the time when the settlement process is completed, or evaluation may be possible from the time when the cooking is shipped from the cooking agency, or evaluation may be possible from the time when the cooking is delivered to the user of the cooking agency. For example, the user evaluation information receiving unit 1121 may transmit the screen information of the evaluation input screen to the health management service user terminal 7 of the user of the cooking agency. The evaluation input screen may be a screen for receiving input of an evaluation of the recipe used in the cooking agency used by the health management service user. The user evaluation information receiving unit 1121 may transmit the screen information of the evaluation input screen, for example, in response to a request from the health management service user terminal 7. For example, when the health management server 1 receives the reception information, when the settlement process is completed, when the cooking is shipped from the cooking agency, or when the cooking is delivered to the user of the cooking agency, the health management server 1 may transmit a notification corresponding to the event to the health management service user terminal 7. This notification may be presentation information that can indicate that the event has occurred. The user evaluation information receiving unit 1121 may transmit this notification, for example, by email or push notification of the health management application. This notification may include the URL of the screen information of the evaluation input screen for inputting an evaluation of the recipe used in the cooking agency corresponding to the event. This URL may include, for example, the request ID of the request for the cooking agency or the recipe ID of the recipe.The health management service user terminal 7 displays the notification content on the screen based on the notification information. By selecting the URL displayed on the screen by the health management service user, the health management service user terminal 7 may display an evaluation information input screen. When the health management service user inputs an evaluation value on the evaluation information input screen, the health management service user terminal 7 may send the user evaluation information to the health management server 1 or the recipe server 2.

[0250] The evaluation input screen may be, for example, a cooking agency usage history screen. The cooking agency usage history screen may be a screen showing the usage history of the cooking agency by the health management service user who uses the health management service user terminal 7. For example, the cooking agency usage history screen may include a cooking agency request record display area for each request received by the cooking agency. For example, the cooking agency request record display area may be displayed only for requests with a request status of "delivered". Alternatively, the cooking agency request record display area may be displayed only for requests with a request status of either "delivered" or "in delivery". Alternatively, the cooking agency request record display area may be displayed only for requests with a request status of any one of "delivered", "in delivery", and "request received". The cooking agency request record display area may be an area where information related to the cooking agency request is displayed. For example, each cooking agency request record display area may include the recipe name, dish name, cooking price, payment amount, name of the cooking agency of the request destination for the cooking agency, request date and time, etc. used for the cooking agency. Each cooking agency request record display area may further include an element that enables an operation to display a window for selecting an evaluation value for the recipe corresponding to the cooking agency request record display area. Then, the user evaluation information may be sent from the health management service user terminal 7 to the health management server 1 or the recipe server 2.

[0251] The health management server 1 and the recipe server 2 may operate so that the user of the cooking proxy service can evaluate the recipe only after accepting the request for the cooking proxy. Alternatively, after the user of the cooking proxy service accepts the request for the cooking proxy, the user of the cooking proxy service can evaluate the recipe, and, as in the ninth embodiment, regardless of whether it is the recipe for which the cooking proxy was requested, at least one of the recipe service user and the health management service user may be able to evaluate the recipe, for example, also from the recipe screen.

[0252] The recipe presentation order determination unit 2106 may determine the presentation order of the retrieved recipes in the same manner as the method described in the ninth embodiment.

[0253] FIG. 43 is a sequence diagram showing a processing example of the communication system S when a health management service user performs an evaluation. FIG. 43 shows an example in which an evaluation of a recipe can be performed after the delivery of the cooked food is completed. In FIG. 43, the same reference numerals are given to the same processes as in FIG. 41. In step S613 shown in FIG. 23, the health management service terminal 7 displays on the screen that a request for cooking on behalf of someone has been received. Thereafter, the cooked food prepared by the requested cooking on behalf of someone is delivered to the health management service user by the delivery person. The delivery person inputs to a terminal device (not shown) that the delivery has been completed in association with the invoice number of the cooked food. The terminal device transmits the invoice number for which the delivery has been completed to the delivery management server 4. Then, as shown in FIG. 43, the delivery management server 4 transmits to the health management server 1 a delivery status indicating "delivery completed" together with this invoice number (step S821). The user evaluation information receiving unit 1121 of the health management server 1 searches the cooking-on-behalf-of request record information including the invoice number received together with the delivery status from the cooking-on-behalf-of request DB 14h. The user evaluation information receiving unit 1121 changes the request status included in the searched cooking-on-behalf-of request record information to "delivered" (step S822). Since the request status has been changed to "delivered", the user evaluation information receiving unit 1121 transmits a delivery completion notice to the health management service user terminal 7 (step S823). The delivery completion notice may be in a presentation format indicating that the delivery of the cooked food has been completed. At this time, the user evaluation information receiving unit 1121 generates a URL including the request ID and the recipe ID included in the searched cooking-on-behalf-of request record information as the URL of the screen information of the evaluation input screen. The user evaluation information receiving unit 1121 includes this URL in the delivery completion notice. The health management service user terminal 7 displays the delivery completion notice on the screen (step S824).

[0254] The health management service user selects a URL from the delivery completion notification (step S825). In response to this selection, the health management service user terminal 7 sends a request for an evaluation input screen including the URL to the health management server 1 (step S826). The user evaluation information receiving unit 1121 sends an HTML document of the evaluation input screen to the health management service user terminal 7 in response to the request for the evaluation input screen (step S827). The health management service user terminal 7 displays an evaluation input screen based on this HTML document (step S828). The health management service user selects an evaluation value on the evaluation input screen (step S829). The health management service user terminal 7 sends user evaluation information including the recipe ID of the recipe corresponding to the evaluation input screen, the selected evaluation value, and the user ID of the health management service user to the health management server 1 (step S830). The user evaluation information receiving unit 1121 of the health management server 1 transfers the transmitted user evaluation information to the recipe server 2 (step S831). Note that the user evaluation information may be sent directly from the health management service user terminal 7 to the recipe server 2 instead of passing through the health management server 1. The recipe server 2 that has received the user evaluation information executes steps S805 and S806.

[0255] As described above, according to the present embodiment, it is possible to present recipes in an order according to the height of the evaluation determined by the requester for the recipe in consideration of the evaluation of the cooked food using the recipe when eating the cooked food.

[0256] [11. Eleventh Embodiment] Next, the 11th embodiment will be described with reference to FIGS. 44 and 45. Except for the points described below, this embodiment may be the same as at least one of the embodiments described so far. Also in this embodiment, as described in the 10th embodiment, after a request for cooking assistance is received by a cooking assistant, the cooking assistance user who requested the cooking assistance may be able to evaluate the recipe used in the cooking assistance. The health management server 1 may give a reward corresponding to this evaluation to the recipe submitter. The recipe server 2 may or may not determine the presentation order of the recipes according to the evaluation of the recipes. The storage unit 24 of the recipe server 2 may or may not store the user evaluation DB 24c. Also, the storage unit 24 may or may not store the recipe evaluation DB 24d.

[0257] Similar to the 10th embodiment, at least one of the user evaluation information receiving unit 1121 of the health management server 1 and the recipe presentation order determination unit 2106 of the recipe server 2 may receive user evaluation information indicating the level of evaluation from the cooking assistance user for the selected recipe from the health management service user terminal 7 after receiving the reception information from the cooking assistant terminal 5 by the reception information receiving unit 1115.

[0258] After the user evaluation information is received by either the user evaluation information receiving unit 1121 or the recipe presentation order determination unit 2106, the reward giving unit 1117 may give a reward to the recipe submitter who submitted the selected recipe. At this time, the reward giving unit 1117 may increase the value of the reward given as the evaluation indicated by the acquired user evaluation information is higher. For example, the value of the reward may correspond to the number of points, the discount rate or amount of an electronic coupon, or the amount of electronic money or the amount of money.

[0259] FIG. 44 is a diagram showing an example of the relationship between the evaluation of a recipe and the number of points given as a reward. As shown in FIG. 44, the higher the evaluation value, the larger the number of points given, and the lower the evaluation value, the smaller the number of points given. For example, when the evaluation value is 1, 10 points may be given. When the evaluation value is 2, 20 points may be given. When the evaluation value is 3, 30 points may be given. When the evaluation value is 4, 40 points may be given. When the evaluation value is 5, 50 points may be given.

[0260] FIG. 45 is a sequence diagram showing an example of the processing of the communication system S when a health management service user makes an evaluation and then a reward is given to the recipe submitter. In FIG. 45, the same processes as those in FIGS. 24 and 43 are denoted by the same reference numerals.

[0261] As shown in FIG. 45, first, steps S821 to S829 are executed. Next, the health management service user terminal 7 transmits user evaluation information including the request ID of the request corresponding to the evaluation input screen, the recipe ID of the recipe corresponding to the evaluation input screen, the selected evaluation value, and the user ID of the health management service user to the health management server 1 (step S841). The user evaluation information receiving unit 1121 of the health management server 1 transmits user evaluation information including information other than the request ID among the information included in the transmitted user evaluation information to the recipe server 2 (step S842). The recipe server 2 that has received the user evaluation information executes steps S805 and S806.

[0262] After transmitting the user evaluation information to the recipe server 2, the reward granting unit 1117 of the health management server 1 acquires the recipe contributor ID associated with the request ID included in the user evaluation information received from the health management service user terminal 7 from the cooking proxy request DB 14h (step S843). Next, the reward granting unit 1117 determines the number of added points to be a number corresponding to the evaluation value included in the user evaluation information (step S844). Next, the reward granting unit 1117 transmits a point addition request including the recipe contributor ID and the number of added points to the point management server 3 (step S703). Next, steps S704 to S706 are executed.

[0263] As described above, according to the present embodiment, the health management service user can evaluate the recipe after eating the cooked dish. The value of the reward given by the recipe contributor becomes a value corresponding to the evaluation from the health management service user. Therefore, the recipe contributor can obtain a reward of a value corresponding to the evaluation of the recipe including the evaluation of the cooked dish prepared using the recipe contributed by the recipe contributor.

[0264] (Appendix 1-1) Nutrition intake status information acquisition means for acquiring nutrition intake status information indicating the nutrition intake status of users who can use cooking agency services, the acquired nutrition intake status information, and recipe information indicating recipes are associated with recipe nutrient amount information indicating the amounts of nutrients included in the dishes that can be cooked according to the recipes, and stored in recipe information storage means. Based on the recipe nutrient amount information associated with the recipe information stored therein, recipe search means for searching for one or more recipes according to the nutrition intake status of the cooking agency service users, and presenting recipe information that can present the searched one or more recipes. Presentation recipe information transmission means for transmitting to the cooking agency service user terminal device used by the cooking agency service user, and among the one or more recipes indicated by the transmitted presentation recipe information, selection recipe identification information for identifying a selected recipe selected by the cooking agency service user as a recipe for which a request for cooking agency service is desired. Selection recipe identification information receiving means for receiving from the cooking agency service user terminal device, and cooking agency request information transmission means for transmitting cooking agency request information indicating a request for cooking agency service using the selected recipe identified by the received selection recipe identification information to the cooking agency operator terminal device used by the cooking agency operator. A cooking agency request system characterized by comprising.

[0265] (Appendix 1-2) The recipe search means further searches for the one or more recipes based on nutrition intake amount reference information indicating a reference of nutrition intake amount. The cooking agency request system according to Appendix 1-1, characterized in that.

[0266] (Appendix 1-3) The nutrition intake status indicated by the acquired nutrition intake status information includes the amounts of nutrients ingested by the cooking agency service users, and the recipe search means includes the amounts of nutrients indicated by the acquired nutrition intake status information and the recipe nutrient amount information associated with the recipe information. The cooking agency request system according to Appendix 1-2, characterized in that it searches for a recipe in which the total of the amounts of nutrients indicated by is satisfied with the reference of the nutrition intake amount indicated by the nutrition intake amount reference information.

[0267] (Appended Note 1-4) The recipe information stored in the recipe information storage means includes ingredient information indicating the ingredients used in the recipe, and the ingredient nutrient amount information stored in the ingredient nutrient amount information storage means that stores, for each ingredient, the amount of nutrients contained in the ingredient. Based on the ingredient nutrient amount information and the ingredient information included in the recipe information stored in the recipe information storage means, calculation means for calculating the amount of nutrients contained in the dish that can be cooked according to the recipe indicated by the recipe information, and recipe dish nutrient amount information indicating the calculated amount is stored in the recipe information storage means in association with the recipe information as the dish nutrient amount information by dish nutrient amount information storage control means. The recipe search means searches for the one or more recipes according to the nutrient intake status of the person who can use the cooking proxy service based on the dish nutrient amount information stored in the recipe information storage means by the dish nutrient amount information storage control means. The cooking proxy request system according to any one of Appended Notes 1-1 to 1-3, characterized in that

[0268] (Appended Note 1-5) The cooking proxy request system according to any one of Appended Notes 1-1 to 1-4, further comprising recipe presentation order determination means for determining the presentation order of the one or more searched recipes based on the evaluation information stored in the evaluation information storage means that stores, for each recipe, the evaluation information indicating the level of evaluation of the recipe by the viewer who has viewed the recipe. The presented recipe information transmission means transmits the presented recipe information, which indicates that the one or more searched recipes can be presented in the order according to the determined presentation order, to the cooking proxy available person terminal device.

[0269] (Appended Note 1-6) The evaluation information stored in the evaluation information storage means indicates the high level of evaluation of the recipe by the cooking agency users who used the cooking agency service among the viewers who viewed the recipe, and receives reception information indicating that the cooking agency has accepted the cooking agency request indicated by the transmitted cooking agency request information from the cooking agency terminal device. After the reception information is received by the reception information receiving means, cooking agency recipe evaluation information indicating the high level of evaluation of the selected recipe by the available cooking agency users is received from the available cooking agency user terminal device. And an update means for updating the evaluation information of the selected recipe stored in the evaluation information storage means based on the received cooking agency recipe evaluation information. The recipe presentation order determination means determines the presentation order of the retrieved one or more recipes based on the evaluation information updated by the update means. The cooking agency request system according to Appended Note 1-5, characterized in that

[0270] (Appended Note 1-7) Further provided with a cooking agency search means for searching for a cooking agency that satisfies the conditions predetermined as the conditions for the request destination of the cooking agency for using the selected recipe identified by the received selected recipe identification information based on the cooking agency information stored in the cooking agency information storage means that stores the cooking agency information for each cooking agency. The cooking agency request information transmitting means transmits the cooking agency request information to the cooking agency terminal device used by the retrieved cooking agency. The cooking agency request system according to any one of Appended Notes 1-1 to 1-6, characterized in that

[0271] (Appended Note 1-8) The recipe information stored in the recipe information storage means includes ingredient information indicating the ingredients of the recipe. The proxy cooking agent information stored in the proxy cooking agent information storage means includes ingredient possession status information indicating the possession status of the ingredients that the proxy cooking agent has and can use for proxy cooking among the ingredients the proxy cooking agent has. The proxy cooking agent search means searches for a proxy cooking agent who has the ingredients used in the selected recipe as ingredients that can be used for proxy cooking based on the ingredient information included in the recipe information of the selected recipe identified by the received selected recipe identification information and the ingredient possession status information stored in the proxy cooking agent information storage means. The proxy cooking request system according to Appended Note 1-7.

[0272] (Appended Note 1-9) The proxy cooking agent information stored in the proxy cooking agent information storage means includes provision range information that can specify the geographical provision range within which the proxy cooking agent can provide the dishes cooked by proxy cooking. The proxy cooking agent search means ...

Claims

1. A recipe presentation information transmission means for transmitting, to a terminal device of a person capable of using cooking agency service, presentation recipe information indicating that any one or more of the viewable recipes can be presented; A selected recipe identification information receiving means for receiving, from the terminal device of the person capable of using cooking agency service, selected recipe identification information for identifying a selected recipe selected by the person capable of using cooking agency service as a recipe for which a request for cooking agency service is desired among the one or more recipes indicated by the transmitted presentation recipe information; Based on the ingredient information indicating the ingredients used in the selected recipe identified by the received selected recipe identification information and the ingredient availability status information stored in the restaurant information storage means that stores, for each restaurant, the ingredient availability status information indicating the availability status of the ingredients that the restaurant has and can use for cooking agency service among the ingredients the restaurant has, a restaurant search means for searching for a restaurant that has the ingredients used in the selected recipe as ingredients that can be used for cooking agency service; A cooking agency request information transmission means for transmitting, to the terminal device of the restaurant found, cooking agency request information indicating a request for cooking agency service using the selected recipe identified by the received selected recipe identification information; A cooking agency matching system, characterized by comprising the above.

2. The ingredient availability status information stored in the restaurant information storage means indicates the availability status of the ingredients that the restaurant has in excess of the quantity of the ingredients that the restaurant has for providing dishes in the restaurant; The cooking agency matching system according to Claim 1, wherein the restaurant search means searches for a restaurant that has the ingredients used in the selected recipe in excess.

3. An input ingredient availability status information receiving means for receiving, from the terminal device of the restaurant, input ingredient availability status information indicating the availability status input by the restaurant as the availability status of the ingredients that the restaurant can use for cooking agency service; An ingredient availability status information storage control means for storing the received input ingredient availability status information in the restaurant information storage means as the ingredient availability status information; further comprising: The cooking agency matching system according to claim 1, wherein the food and beverage store search means performs the search based on the material possession status information stored in the food and beverage store information storage means by the material possession status information storage control means.

4. The food and beverage store information storage means further stores, for each food and beverage store, provision range information indicating a geographical provision range within which the food and beverage store can provide dishes cooked by cooking agency. The food and beverage store search means further searches, among food and beverage stores having the materials used in the selected recipe as materials available for cooking agency, for a food and beverage store within the provision range where the position of the cooking agency available user is located, based on the material information, the material possession status information, the cooking agency available user position information indicating the position of the cooking agency available user, and the provision range information stored in the food and beverage store information storage means. The cooking agency matching system according to any one of claims 1 to 3 is characterized by this.

5. The food and beverage store information storage means further stores, for each dish that each food and beverage store can cook by cooking agency, price information indicating the price set by the food and beverage store as the price of the dish. The cooking agency matching system further includes price condition information receiving means for acquiring price condition information indicating conditions of the price of the dish from the cooking agency available user terminal device. The food and beverage store search means searches, among food and beverage stores having the materials used in the selected recipe identified by the received selected recipe identification information as materials available for cooking agency, for a food and beverage store where the price of the dish cookable by the selected recipe satisfies the conditions indicated by the received price condition information, based on the material information, the material possession status information, and the price information stored in the food and beverage store information storage means. The cooking agency matching system according to any one of claims 1 to 3 is characterized by this.

6. The food and beverage store search means searches for one or more food and beverage stores having the materials used in the selected recipe as materials available for cooking agency. Food and beverage store presentation order determination means for determining the presentation order of the one or more searched food and beverage stores. Presentation food and beverage store information transmission means for transmitting, to the cooking agency available user terminal device, presentation food and beverage store information indicating the one or more searched food and beverage stores so that they can be presented in the order corresponding to the determined presentation order. Selection restaurant identification information receiving means for receiving, from the terminal device of the person who can use cooking agency, selection restaurant identification information for identifying a selected restaurant selected by the person who can use cooking agency as a request destination for cooking agency among the one or more restaurants indicated by the transmitted restaurant information. Further comprising The cooking agency request information transmitting means transmits the cooking agency request information to the restaurant terminal device used by the selected restaurant identified by the received selection restaurant identification information. The cooking agency matching system according to any one of claims 1 to 3, characterized in that.

7. The material possession status information stored in the restaurant information storage means indicates the materials that the restaurant has as materials available for cooking agency and the expiration dates of the materials. Based on the material information and the material possession status information stored in the restaurant information storage means, the restaurant presentation order determining means increases the presentation order of the restaurant with a closer expiration date of the materials used in the selected recipe. The cooking agency matching system according to claim 6, characterized in that.

8. The restaurant information storage means further stores, for each dish that a restaurant can perform cooking agency, price information indicating the price set by the restaurant as the price of the dish. Based on the price information stored in the restaurant information storage means, the restaurant presentation order determining means determines the presentation order of the one or more restaurants retrieved. The cooking agency matching system according to claim 6, characterized in that.

9. The restaurant information storage means further stores, for each restaurant, restaurant location information indicating the location of the restaurant. Based on the cooking agency user location information indicating the location of the person who can use cooking agency and the restaurant location information stored in the restaurant information storage means, the restaurant presentation order determining means increases the presentation order of the restaurant closer to the location of the person who can use cooking agency. The cooking agency matching system according to claim 6, characterized in that.

10. The restaurant information storage means further stores, for each restaurant, usage fee information indicating the amount of usage fee that the restaurant pays for using the cooking agency matching system, which is the amount designated by the restaurant. The cooking agency matching system according to claim 6, wherein the restaurant presentation order determination means raises the presentation order of a restaurant that sets a higher usage fee based on the usage fee information stored in the restaurant information storage means.

11. The material possession status information stored in the material possession status information indicates the materials that the restaurant has as materials available for cooking agency and the expiration dates of the materials. The restaurant search means searches for a restaurant with the closest expiration date of the materials used in the selected recipe among the restaurants that have the materials used in the selected recipe as materials available for cooking agency, according to any one of claims 1 to 3. The cooking agency matching system described.

12. The restaurant information storage means further stores price information indicating the price set by the restaurant as the price of the dish for each dish that the restaurant can perform cooking agency. The restaurant search means, based on the material information, the material possession status information, and the price information stored in the restaurant information storage means, among the restaurants that have the materials used in the selected recipe as materials available for cooking agency, The cooking agency matching system according to any one of claims 1 to 3, wherein a restaurant with the lowest price of the dish that can be cooked in the selected recipe is searched.

13. The restaurant information storage means stores restaurant location information indicating the location of the restaurant for each restaurant. The restaurant search means, based on the material information, the material possession status information, and the restaurant location information stored in the restaurant information storage means, among the restaurants that have the materials used in the selected recipe as materials available for cooking agency, The cooking agency matching system according to any one of claims 1 to 3, wherein a restaurant closest to the location of the person available for cooking agency is searched.

14. In a cooking agency matching method executed by a computer, A presentation recipe information transmission step of transmitting presentation recipe information that can present any one or a plurality of recipes among the viewable recipes to a cooking agency user terminal device used by a cooking agency user who can use the cooking agency. A selected recipe identification information receiving step of receiving, from the terminal device of the person available for entrusted cooking, the selected recipe identification information that identifies a selected recipe selected by the person available for entrusted cooking as a recipe for which a request for entrusted cooking of a dish is desired among the one or more recipes indicated by the transmitted presentation recipe information; A restaurant search step of searching for a restaurant that has, as materials available for entrusted cooking, the materials used in the selected recipe, based on the material information indicating the materials used in the selected recipe identified by the received selected recipe identification information and the material availability information stored in the restaurant information storage means that stores, for each restaurant, the material availability information indicating the availability status of the materials that the restaurant has and can use for entrusted cooking; A step of transmitting, to the restaurant terminal device used by the searched restaurant, entrusted cooking request information indicating a request for entrusted cooking using the selected recipe identified by the received selected recipe identification information; A method for entrusted cooking matching, characterized by including the above.

Images