Information processing system, information processing method, and program

Abstract

To provide an information processing system, an information processing method, and a program that can improve convenience.SOLUTION: An information processing system includes a recipe registration section and a display control section. The recipe registration section receives registration of a first recipe and can set a subject for the first recipe, and receives registration for associating a second recipe related to the subject with the first recipe as part of the registration of the first recipe or in another processing when the subject is set for the first recipe. When the registration for associating the second recipe with the first recipe is performed, the display control section displays an operation section for displaying the second recipe on a display screen when displaying the first recipe on the display screen and displays the second recipe on the display screen when predetermined operation including operation of the operation section is performed.SELECTED DRAWING: Figure 8

Description

Technical Field

[0001] Embodiments of the present invention relate to an information processing system, an information processing method, and a program.

Background Art

[0002] There is known a recipe providing system capable of providing arrangement information such as curry flavor or light saltiness. Further improvement in convenience is expected for such an information processing system.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] The problem to be solved by the present invention is to provide an information processing system, an information processing method, and a program capable of improving convenience.

Means for Solving the Problems

[0005] The information processing system according to the embodiment includes a recipe registration unit and a display control unit. The recipe registration unit accepts registration of a first recipe and can set a title for the first recipe. When the title is set for the first recipe, it accepts registration of associating a second recipe related to the title with the first recipe as part of the registration of the first recipe or by another process. The display control unit, when registration of associating the second recipe with the first recipe has been performed and the first recipe is to be displayed on the display screen, displays an operation unit for displaying the second recipe on the display screen, and when a predetermined operation including an operation of the operation unit is performed, displays the second recipe on the display screen. The recipe registration unit can unassociate the second recipe with the first recipe, and if the association with the first recipe is unassociated with the second recipe for which a private setting has been registered to prevent it from being displayed on the recipe list screen, the private setting registration for the second recipe is maintained. [Brief explanation of the drawing]

[0006] [Figure 1] A diagram showing the overall configuration of the service provision system according to the first embodiment. [Figure 2] A block diagram showing the functional configuration of the device management server in the first embodiment. [Figure 3] A block diagram showing the functional configuration of the recipe management server in the first embodiment. [Figure 4] A diagram illustrating the recipe information of a representative recipe of the first embodiment. [Figure 5] A diagram illustrating the recipe information for the related recipe of the first embodiment. [Figure 6] A diagram illustrating the favorite recipe database of the first embodiment. [Figure 7] A block diagram showing the functional configuration of the terminal device according to the first embodiment. [Figure 8] A diagram illustrating an example of the recipe registration screen in the first embodiment. [Figure 9] A diagram illustrating another example of the recipe registration screen of the first embodiment. [Figure 10] A diagram illustrating the constraints when registering a recipe in the first embodiment. [Figure 11] A diagram illustrating another constraint when registering a recipe in the first embodiment. [Figure 12] A diagram illustrating an example of the recipe display screen of the first embodiment. [Figure 13] A diagram illustrating another example of the recipe display screen of the first embodiment. [Figure 14] A diagram illustrating the display of favorite recipes in the first embodiment. [Figure 15] A flowchart showing the control flow for displaying the recipe of the first embodiment. [Figure 16] A sequence diagram showing the control flow for displaying the recipe of the first embodiment. [Figure 17] A diagram illustrating an example of the recipe registration screen in the second embodiment. [Figure 18]A diagram illustrating the favorite recipe database of the third embodiment. [Figure 19] A sequence diagram showing the control flow for favorite registration in the third embodiment. [Modes for carrying out the invention]

[0007] The information processing system, information processing method, and program of the embodiments will be described below with reference to the drawings. In the following description, components having the same or similar functions will be denoted by the same reference numerals. Duplication of descriptions of these components may be omitted. In this application, "based on XX" means "based on at least XX," and may also include cases where XX is based on another element in addition to XX. Furthermore, "based on XX" is not limited to cases where XX is used directly, but may also include cases where XX has been processed or modified. In this application, "XX or YY" is not limited to cases where either XX or YY is used, but may also include cases where both XX and YY are used. This also applies when there are three or more optional elements. XX and YY are arbitrary elements (e.g., arbitrary information).

[0008] In this application, "acquisition" is not limited to actively acquiring information by sending a transmission request, but may also include acquiring information by passively receiving information transmitted from another device. Furthermore, "acquisition" may also include obtaining the target information by performing calculations or processing on information obtained from an external source to generate the target information. In this application, "database" is abbreviated as "DB".

[0009] (First Embodiment) <1. Overall configuration of the service delivery system> FIG. 1 is a diagram showing the overall configuration of a service providing system 1 according to the first embodiment. The service providing system 1 includes, for example, a cooking appliance 100, a device management server 200, a recipe management server 300, a home appliance management app APP of a terminal device 400, and a terminal device 500. The network NW described later may be used according to the situation, for example, the Internet, a cellular network, a Wi-Fi network, LPWA (Low Power Wide Area), WAN (Wide Area Network), LAN (Local Area Network), or other public lines or dedicated lines.

[0010] The cooking appliance 100 is a home appliance used by the user U and is arranged within the residence of the user U. The cooking appliance 100 is connected to the network NW via, for example, a wireless router WR and a modem M installed within the residence of the user U. The cooking appliance 100 can communicate with the device management server 200 via the network NW. Also, the cooking appliance 100 may be able to communicate directly with the terminal device 400 via the network NW or by using short-range wireless communication such as Bluetooth (registered trademark). The cooking appliance 100 is, for example, an oven range, a microwave oven, a toaster, or a rice cooker.

[0011] The device management server 200 is a management server that manages the cooking appliance 100. For example, the device management server 200 manages the cooking settings of the cooking appliance 100 by transmitting cooking setting information described later to the cooking appliance 100. The device management server 200 is composed of one or more server devices (for example, a cloud server). The device management server 200 can communicate with the cooking appliance 100, the recipe management server 300, and the terminal device 400 via the network NW. The device management server 200 may include an information processing unit that performs edge computing or fog computing, such as an information processing unit included in a router in the network NW. The device management server 200 is not limited to a cloud server and may be a computer in the residence of the user U or a home router (for example, a wireless router WR).

[0012] The recipe management server 300 is a server that manages services related to recipes. The recipe management server 300 is composed of one or more server devices (such as a cloud server). The recipe management server 300 can communicate with the device management server 200, the terminal device 400, and the terminal device 500 via the network NW. The recipe management server 300 may include an information processing unit that performs edge computing or fog computing, such as an information processing unit included in a router in the network NW. In this embodiment, for convenience of explanation, the device management server 200 and the recipe management server 300 are described as independent devices. However, the device management server 200 and the recipe management server 300 may be realized by one device.

[0013] The terminal device 400 is a computer used by the user U. The terminal device 400 is, for example, a mobile terminal device such as a smartphone or a tablet terminal device. However, the terminal device 400 is not limited to a mobile terminal device and may be a personal computer or the like. The terminal device 400 has, for example, a display device 401, an input device 402, and a communication unit 403. The display device 401 has a display screen 401a capable of displaying various information. The input device 402 can receive the input of the user U. The input device 402 is, for example, a touch panel provided overlapping the display screen 401a. The input device 402 may include a camera, a microphone, etc. provided in the terminal device 400. The communication unit 403 is a communication module capable of wireless communication. The communication unit 403 is connected to the network NW via a wireless router WR and a modem M or directly. The communication unit 403 can communicate with the device management server 200 and the recipe management server 300 via the network NW. Note that the communication unit 403 may communicate directly with the cooking appliance 100 via the network NW or by using short-range wireless communication such as Bluetooth as described above.

[0014] The terminal device 400 has application program P installed and supports the functions described below. Application program P is an application program that manages, for example, cooking appliances 100 and also provides services related to recipes. Hereinafter, the application software launched when application program P is executed will be referred to as the "appliance management app".

[0015] The terminal device 500 is a computer used by the operator OP who provides recipes. The terminal device 500 is a personal computer, but it may also be a portable terminal device such as a tablet. The terminal device 500 has, for example, a display device 501, an input device 502, and a communication unit 503. The display device 501 has a display screen 501a that can display various information. The input device 502 is a device that can receive input from the operator OP. The communication unit 503 can communicate with the recipe management server 300 via the network NW.

[0016] In this embodiment, an example of an "information processing system" is realized by the recipe management server 300 and the home appliance management application APP of the terminal device 400. However, the "information processing system" as used in this application is not limited to the above example, and may be realized by the recipe management server 300 alone, or by the home appliance management application APP of the terminal device 400 alone, or by any two or more combinations of the cooking appliance 100, the appliance management server 200, the recipe management server 300, the home appliance management application APP of the terminal device 400, and the terminal device 500. The appliance management server 200, the recipe management server 300, the terminal device 400, and the terminal device 500 are each examples of a "computer". The application program P is an example of a "program".

[0017] <2. Device Management Server> Next, we will describe the device management server 200. Figure 2 is a block diagram showing the functional configuration of the device management server 200. The device management server 200 includes, for example, a device registration unit 210, an information acquisition unit 220, a cooking setting transmission unit 230, and a storage unit 290.

[0018] The device registration unit 210, the information acquisition unit 220, and the cooking setting transmission unit 230 are implemented by one or more hardware processors, such as a CPU (Central Processing Unit) mounted on the device management server 200, executing a program. However, some or all of these functional units may be implemented by hardware such as an ASIC (Application Specific Integrated Circuit), PLD (Programmable Logic Device), or FPGA (Field Programmable Gate Array), or by the cooperation of software and hardware. Furthermore, one or more of these functional units may be provided in the cooking appliance 100, the recipe management server 300, or the appliance management application APP of the terminal device 400, instead of the device management server 200.

[0019] (Equipment Registration Department) The equipment registration unit 210 accepts equipment registration for the cooking appliance 100. In this application, "equipment registration" means associating the cooking appliance 100 with the user U who uses the cooking appliance 100. For example, equipment registration is performed by associating the user U's account (hereinafter referred to as "user ID") with the identification information of the cooking appliance 100 used by user U (hereinafter referred to as "equipment ID") and registering it in the equipment registration DB 291.

[0020] (Information acquisition department) The information acquisition unit 220 acquires various information from the cooking appliance 100 or the terminal device 400. For example, the information acquisition unit 220 receives a request from the terminal device 400 to send a desired cooking setting to the cooking appliance 100 (hereinafter referred to as the "cooking setting transmission request"). The cooking setting transmission request includes information indicating the content of the cooking setting to be set by the cooking appliance 100 (hereinafter referred to as the "cooking setting information"). The cooking setting information includes, for example, information indicating the content of the heating control performed by the cooking appliance 100, and includes one or more of the following: heating method, heating intensity, heating temperature, and heating time. The cooking setting information includes, for example, the content of the heating control corresponding to the cooking included in the recipe selected by the user U.

[0021] (Cooking setting transmission unit) When the cooking setting transmission unit 230 receives a cooking setting transmission request from the terminal device 400, it transmits the cooking setting information included in the received cooking setting transmission request to the cooking appliance 100. For example, based on the device registration DB 291, the cooking setting transmission unit 230 transmits the cooking setting information to the cooking appliance 100 that is managed in association with the user U of the terminal device 400 that sent the cooking setting transmission request. As a result, user U can, for example, simply press the cooking start operation button provided on the cooking appliance 100 to have the cooking appliance 100 perform the desired cooking without having to input cooking setting information.

[0022] (Storage part) The memory unit 290 is implemented by a combination of, for example, RAM (Random Access Memory), ROM (Read Only Memory), EEPROM (Electrically Erasable Programmable ROM), SSD (Solid State Drive), or HDD (Hard Disk Drive). The memory unit 290 stores various types of information. For example, the memory unit 290 stores the device registration DB 291.

[0023] <3. Recipe Management Server> Next, we will describe the recipe management server 300. Figure 3 is a block diagram showing the functional configuration of the recipe management server 300. The recipe management server 300 includes, for example, a recipe registration unit 310, a favorite recipe management unit 320, a request acquisition unit 330, a recipe provision unit 340, and a storage unit 390.

[0024] <3.1 Recipe Registration Section> The recipe registration unit 310 accepts recipe registrations. For example, the recipe registration unit 310 accepts recipe registrations in response to requests from terminal devices 500 based on the operations of operator OP. Alternatively, the recipe registration unit 310 may also accept recipe registrations in response to requests from terminal devices 400 based on the operations of user U. For this reason, in the following description, "operator OP" may be read as "user U," and "terminal device 500" may be read as "terminal device 400." The recipe registration unit 310 registers a recipe, for example, by registering the recipe information (for example, the recipe information RI described later) for each recipe in the recipe DB 391 stored in the storage unit 390.

[0025] In this embodiment, the recipe registration unit 310 can register multiple recipes. In this embodiment, one or more recipes can be assigned a title (theme), as described later. The recipe registration unit 310 accepts registrations that associate multiple recipes with each other based on the title set for a given recipe. For example, the recipe registration unit 310 can register a representative recipe (parent recipe) and related recipes (child recipes) as at least a portion of the multiple recipes registered in the recipe DB 391.

[0026] A "representative recipe" is a recipe to which one or more other recipes (related recipes) are linked (associated) with a theme (topic) described later. The representative recipe is the main recipe in a group of recipes formed by the representative recipe and one or more related recipes. A "representative recipe" is an example of a "first recipe".

[0027] A "related recipe" is a recipe that is related to the theme set for the representative recipe, and is registered in association with the representative recipe. In the above group of recipes, a related recipe is a subordinate recipe. A "related recipe" is an example of a "second recipe".

[0028] The terms "representative recipe" and "related recipe" are used for explanatory purposes only. In this embodiment, both "representative recipes" and "related recipes" are individual recipes registered independently in the recipe DB391. Each recipe that becomes a "representative recipe" or a "related recipe" can be either a "representative recipe" or a "related recipe" before the recipe DB391 associates the recipes with each other. In this embodiment, a recipe registered in the recipe DB391 that has a title set is referred to as a "representative recipe," and a recipe registered in the recipe DB391 that has been registered to associate with a representative recipe is referred to as a "related recipe."

[0029] Next, we will explain the recipe information RIA, which is the recipe information RI for a representative recipe. Figure 4 is a diagram illustrating the recipe information RIA of a representative recipe. The recipe information RIA of a representative recipe includes, for example, recipe identification information S1, recipe name information S2, recipe image S3, ingredient information S4, process information S5, cooking setting information S6, publication status information S7, and title information S8.

[0030] Recipe identification information S1 includes identification information for identifying a recipe (hereinafter referred to as "recipe ID"). Recipe name information S2 includes the recipe name, which is the name of the recipe. Recipe image S3 includes the image itself to be displayed as part of the recipe, or the address information of the storage location where the image is stored. Recipe image S3 may include, for example, a thumbnail image, but may also include images to explain each step of the cooking process instead of / in addition to the thumbnail image.

[0031] The ingredient information S4 includes information indicating the ingredients necessary for the recipe. For example, the ingredient information S4 includes the name of each ingredient, the quantity, the unit, and a descriptive string. In this embodiment, recipes are prepared and registered for the number of people the recipe corresponds to. For example, the recipe shown in Figure 4 (recipe A0001) is a recipe for two people. In this case, the ingredient information S4 registers the quantity of ingredients for two people.

[0032] Process information S5 includes information that shows the cooking steps of the recipe. For example, process information S5 registers information that shows how to make the dish, divided into steps.

[0033] Cooking setting information S6 is information added to recipes that utilize the cooking appliance 100. Cooking setting information S6 is, for example, information used to set the heating control of the cooking appliance 100. As described above, cooking setting information S6 is information that indicates the content of the heating control performed by the cooking appliance 100, and includes one or more of the following: heating method, heating intensity, heating temperature, and heating time. For example, the cooking setting information S6 illustrated in Figure 4 includes information indicating that the heating method is an oven, the heating temperature is medium, and the heating time is 5 minutes.

[0034] The publication status information S7 includes information indicating the publication status of a recipe, specifically whether it is registered as "public" or "private." "Publication status" refers to a setting that allows a recipe to be displayed on a recipe list screen where multiple recipes are displayed side-by-side. In this application, "recipe list screen" refers to a screen that displays search results for recipes based on keywords or ingredients, a screen that displays the history of recipes being viewed, a screen that displays a list of favorited recipes, or a screen that displays a list of recommended recipes based on the season or other criteria. However, the "recipe list screen" is not limited to the above examples and can be any screen where multiple recipes are displayed side-by-side.

[0035] "Public setting" is a registration that allows the recipe to be displayed on the recipe list screen. "Private setting" is a registration that prevents the recipe from being displayed on the recipe list screen. In this application, "preventing the display of a recipe" means, for example, not displaying the recipe on the recipe list screen, but is not limited to the above example, and may also include lowering the display priority of the recipe (for example, displaying it only if there are no other recipes to display).

[0036] Title information S8 is information added to recipe information RI when a title is set for the recipe in question. Title information S8 includes information about one or more titles (themes) set for the recipe in question, and information about one or more related recipes that are registered to associate with the recipe in question as recipes related to each title.

[0037] A "title" is an item set to associate multiple recipes. "Information about the title" refers to information including, for example, the title name, which is the name of the title. In this embodiment, any title can be set for each recipe. In this application, "any title" broadly refers to a title whose content can be set (changed), rather than a title whose content is fixed in advance. For example, "any title" is not limited to a string arbitrarily entered by the operator OP (for example, a title set by free word), but may also include titles that are set by being selected by the operator OP from among several pre-set options.

[0038] The "topic" can be set as, for example, "quantity of food (i.e., quantity of ingredients)" or "similar recipes." "Quantity of food" refers to the number of people the recipe is intended for (e.g., 1 serving or 2 servings). Note that "quantity of food" is not limited to the above examples and can also refer to the size of the dish (e.g., the diameter of a pizza or cake). "Similar recipes" means that the recipes are similar in one or more aspects such as ingredients, flavor, or cooking method. However, the "topic" is not limited to the examples above, and a variety of topics can be freely set.

[0039] In this embodiment, different titles can be set for multiple recipes. That is, title A may be set for recipe 1, and title B may be set for another recipe, recipe 2. Furthermore, two or more titles can be set for a single recipe.

[0040] "Information about related recipes" includes, for example, the recipe ID of a related recipe that is registered to be associated with the representative recipe, and a description of that related recipe. "Description of related recipes" is, for example, a string of characters displayed on the display screen 401a of the terminal device 400 as a description of the content of the related recipe when the representative recipe is displayed on the display screen 401a.

[0041] For example, if the title is "Serving Size," the description for related recipes will be a string indicating the number of servings the recipe corresponds to, such as "Serves 1" or "Serves 2." Alternatively, the description for related recipes may include dimensions such as "20cm" or "21cm." Similarly, if the title is "Similar Recipes," the description for related recipes will be a string indicating the recipe name, such as "Pork Curry," "Seafood Curry," or "Keema Curry."

[0042] In the example shown in Figure 4, the representative recipe with recipe ID A0001 has three categories set: "Serving Size," "Similar Recipes," and "Allergies." For the first category, "Serving Size," four recipes with different serving sizes and their respective descriptions are registered in association with each other. For the second category, "Similar Recipes," two recipes similar to the representative recipe and their respective descriptions are registered in association with each other. For the third category, "Allergies," two recipes that do not use specific allergenic ingredients and their respective descriptions are registered in association with each other.

[0043] Next, we will explain the recipe information RIB, which is the recipe information RI for related recipes. Figure 5 is a diagram illustrating the recipe information RIB for related recipes. The recipe information RIB for related recipes includes, for example, recipe identification information S1, recipe name information S2, recipe image S3, ingredient information S4, process information S5, cooking setting information S6, publication status information S7, and related destination information S9. Each of the recipe identification information S1, recipe name information S2, recipe image S3, ingredient information S4, process information S5, cooking setting information S6, and publication status information S7 in the recipe information RIB is the same as what was described in the recipe information RIA for the representative recipe.

[0044] The related recipe (recipe A0002) illustrated in Figure 5 is a recipe with different portion sizes compared to the representative recipe. Therefore, the contents of ingredient information S4 (quantity of ingredients) for the related recipe will differ from the contents of ingredient information S4 (quantity of ingredients) for the representative recipe. For example, the related recipe illustrated in Figure 5 is a recipe for one serving. In this case, the ingredient information S4 of the related recipe will contain the quantity for one serving. In addition, the cooking setting information S6 of the related recipe will contain cooking setting information corresponding to the quantity for one serving.

[0045] In this embodiment, when the recipe registration unit 310 registers one or more related recipes as being associated with a representative recipe for a given title, it automatically registers all of those related recipes as private. That is, upon receiving a registration to associate related recipes with a representative recipe, the recipe registration unit 310 registers those related recipes as private without requiring any operation from the operator OP. For this reason, the registration of private status is automatically included in the public status information S7 of the recipe information RIB for each related recipe.

[0046] Alternatively, when registering related recipes to a representative recipe, the recipe registration unit 310 may accept instructions from the operator OP indicating whether to register each related recipe as public or private. Furthermore, for related recipes that have been registered as private, the recipe registration unit 310 may accept instructions from the operator OP to cancel the private registration (switch to public registration) for each related recipe.

[0047] In this embodiment, the setting of a title is limited to the representative recipe, and the setting of titles for related recipes is restricted. For example, the recipe information RIB for a related recipe does not have title information S8. Therefore, the association of another recipe with the related recipe is suppressed.

[0048] Furthermore, unlike the recipe information RIA of the representative recipe, the recipe information RIB of the related recipe includes the associated destination information S9. The associated destination information S9 is information added to the recipe information RI when the association of the recipe with the representative recipe is registered. For example, only one recipe ID of the representative recipe to which the related recipe is associated can be registered in the associated destination information S9. In this embodiment, by restricting the number of representative recipe recipe IDs (the destination to which the related recipe is associated) that can be registered in the associated destination information S9 to one, the association of the related recipe with multiple representative recipes is suppressed.

[0049] Next, we return to Figure 3 and continue the explanation of the recipe registration unit 310. In the following, when it is not necessary to distinguish between the recipe information RIA of the representative recipe and the recipe information RIB of related recipes, we will simply refer to them as "recipe information RI".

[0050] In this embodiment, the recipe registration unit 310 accepts registration of a first recipe (a representative recipe) in response to a request from the terminal device 500 based on the operation of operator OP, and a title can be set for the first recipe. When a title is set for the first recipe, the recipe registration unit 310 accepts registration of a second recipe (a related recipe) related to the title, as part of the registration of the first recipe or in a separate process, associating it with the first recipe.

[0051] In this application, "a title can be set for the first recipe" is not limited to cases where a title can be set as part of the first recipe, but may also include cases where a title can be set separately from the first recipe (i.e., associated with the first recipe but using a database different from the recipe DB391). For example, in the above example, the recipe registration unit 310 sets a title for the representative recipe (first recipe) by registering the title in the title information S8 included in the recipe information RIA of the representative recipe (first recipe). Note that the title information S8, which includes the title, may be managed as information handled independently of the recipe information RIA, instead of being managed as part of the recipe information RIA.

[0052] In this application, "accepting registration to associate the second recipe with the first recipe as part of the registration of the first recipe" means, for example, a case where the second recipe is registered first, and the registration to associate the second recipe with the first recipe is performed together with the registration of the first recipe. On the other hand, in this application, "accepting registration to associate the second recipe with the first recipe in a separate process from the registration of the first recipe" means, for example, a case where the first recipe is registered first, the second recipe is registered later, and then the registration to associate the second recipe with the first recipe is performed thereafter.

[0053] In this application, "accepting registration to associate a second recipe with a first recipe" is not limited to cases where the recipe ID of the second recipe is registered as part of the first recipe, but may also apply to cases where the recipe ID of the second recipe is registered separately from the first recipe (i.e., associated with the first recipe but using a database different from recipe DB391). For example, in the above example, the recipe registration unit 310 registers the recipe ID of the related recipe (second recipe) in the title information S8 included in the recipe information RIA of the representative recipe (first recipe), thereby registering the related recipe to the representative recipe. Note that the title information S8, which includes the recipe ID of the related recipe, may be managed as information handled independently of the recipe information RIA, instead of being managed as part of the recipe information RIA.

[0054] In this embodiment, the recipe registration unit 310 can set two or more titles for the first recipe, and when two or more titles are set for the first recipe, it can accept registrations that associate the first recipe with a different recipe for each of the two or more titles (i.e., different recipes for each of the two or more titles). In the example shown in Figure 4, three titles are set for the representative recipe: "Dish Quantity," "Similar Recipes," and "Allergies," and registrations are made to associate one or more related recipes with the representative recipe for each title.

[0055] In this embodiment, the recipe registration unit 310 registers the "private setting" for each recipe registered as a related recipe. For example, the recipe registration unit 310 suppresses the display of the recipe on the recipe list screen by registering the "private setting" in the publication status information S7 included in the recipe information RIB of the related recipe.

[0056] In this embodiment, the recipe registration unit 310 can unassociate related recipes with a representative recipe. For example, the recipe registration unit 310 unassociates related recipes with a representative recipe in response to a request from the terminal device 500 based on an operation by operator OP. For example, the recipe registration unit 310 unassociates a related recipe with a representative recipe by deleting the registration of the recipe ID of the related recipe included in the title information S8 of the recipe information RIA of the representative recipe, and deleting the registration of the recipe ID of the representative recipe included in the related destination information S9 of the recipe information RIB of the related recipe.

[0057] In this embodiment, the recipe registration unit 310 maintains the registration of the private setting for a related recipe when the association with the representative recipe for that related recipe is removed. For example, the recipe registration unit 310 maintains the registration of the private setting for a related recipe when the association with the representative recipe is removed by maintaining the public status information S7 included in the recipe information RIB of the related recipe.

[0058] In this embodiment, for related recipes associated with a representative recipe, setting a title for that related recipe is restricted, thereby preventing other recipes from being associated with that related recipe. In the example shown in Figure 5, the recipe registration unit 310 registers the recipe ID of the representative recipe in the associated destination information S9 of the recipe information RIB of the related recipe when the related recipe is associated with the representative recipe. The recipe information RIB has a data structure (for example, a data structure that makes it impossible to set the title information S8) that restricts the setting of the title information S8 when the recipe ID of the representative recipe is registered in the associated destination information S9. Therefore, when the recipe ID of the representative recipe is registered in the associated destination information S9, the related recipe can no longer have a title set for it, and it can no longer be associated with another recipe.

[0059] Furthermore, restricting the setting of titles for related recipes, or preventing other recipes from being associated with a related recipe, may be achieved by the functions of the recipe registration unit 310 instead of the data structure. For example, the recipe registration unit 310 determines whether or not a recipe's recipe information RI has related destination information S9. If the recipe information RI has related destination information S9, the recipe registration unit 310 determines that the recipe is a related recipe and restricts the setting of titles for that recipe. On the other hand, if the recipe information RI does not have related destination information S9, the recipe registration unit 310 determines that the recipe is not a related recipe and allows the setting of titles for that recipe.

[0060] Furthermore, "suppressing the association of another recipe with a related recipe" is not limited to completely preventing another recipe from being associated with a related recipe, but may also include cases where another recipe is allowed to be associated with a related recipe only if certain conditions are met, such as when a public setting is registered in the public status information S7 of the recipe information RIB of the related recipe.

[0061] In this embodiment, for related recipes associated with a representative recipe, the number of associated destinations for that related recipe is restricted to one, thereby preventing the related recipe from being associated with another recipe (for example, another representative recipe or another related recipe). In the example shown in Figure 5, the recipe registration unit 310 registers the recipe ID of the representative recipe in the associated destination information S9 of the recipe information RIB of the related recipe when the related recipe is associated with one representative recipe. The recipe information RIB has a data structure that restricts the registration of additional representative recipe recipe IDs in the associated destination information S9 when one representative recipe recipe ID is registered in the associated destination information S9 (for example, a data structure that makes it impossible to register additional representative recipe recipe IDs). Therefore, when a representative recipe's recipe ID is registered in the associated destination information S9, the related recipe cannot be associated with another recipe.

[0062] Furthermore, restricting the number of associated recipes to one, or preventing them from being associated with other recipes, may be achieved by the functions of the recipe registration unit 310 instead of the data structure. For example, the recipe registration unit 310 determines whether or not the recipe information RI of a given recipe has associated information S9. If the recipe information RI has associated information S9, the recipe registration unit 310 determines that the recipe is an associated recipe and prevents it from being associated with other recipes. On the other hand, if the recipe information RI does not have associated information S9, the recipe registration unit 310 allows the recipe to be associated with other recipes.

[0063] Furthermore, "preventing association with other recipes" is not limited to completely preventing a related recipe from being associated with another recipe. It may also include cases where a related recipe is allowed to be associated with another recipe only if certain conditions are met, such as when a public setting is registered in the public status information S7 of the recipe information RIB of the related recipe.

[0064] <3.2 Favorite Recipe Management Section> The Favorite Recipe Management Unit 320 accepts and manages recipes registered as favorites by user U. "Favorite registration" is a registration indicating that a recipe has been specified by user U. The Favorite Recipe Management Unit 320 manages favorite recipes (hereinafter referred to as "favorite recipes") by registering the recipe ID of the favorited recipe in the Favorite Recipe DB 392 stored in the Storage Unit 390. Favorite recipes are displayed, for example, in a designated recipe list screen (Favorite Recipe List Screen) that contains only multiple favorite recipes.

[0065] Figure 6 is a diagram illustrating the Favorite Recipe DB392. In the Favorite Recipe DB392, the recipe IDs of favorite recipes are registered and managed.

[0066] Next, let's return to Figure 3 and continue the explanation of the favorite recipe management unit 320. In this embodiment, when the favorite recipe management unit 320 is displaying a related recipe associated with a representative recipe, if it detects an operation by user U instructing the user to register the related recipe as a favorite (for example, if an operation to the terminal device 400 is detected by the operation reception unit 430 described later), it determines whether or not the related recipe has been set to private based on the recipe information RIB of the related recipe.

[0067] Then, if the above determination indicates that a related recipe has been set to private, the Favorite Recipe Management Unit 320 accepts the registration of the representative recipe to which the related recipe is associated as a favorite, instead of the related recipe itself. For example, the Favorite Recipe Management Unit 320 obtains the recipe ID of the representative recipe to which the related recipe is associated based on the recipe information RIB of the related recipe, and registers the obtained recipe ID of the representative recipe in the Favorite Recipe DB 392, thereby registering the representative recipe as a favorite recipe.

[0068] On the other hand, the Favorite Recipe Management Unit 320 accepts the registration of a related recipe as a favorite if, based on the above determination, there is no registration of a private setting for the related recipe (i.e., there is a registration of a public setting). For example, the Favorite Recipe Management Unit 320 obtains the recipe ID of the related recipe based on the recipe information RIB of the related recipe, and registers the obtained recipe ID of the related recipe in the Favorite Recipe DB 392, thereby registering the related recipe as a favorite recipe.

[0069] <3.3 Request acquisition section> The request acquisition unit 330 acquires requests related to recipes from the terminal device 400. Requests acquired from the terminal device 400 include, for example, requests to send simplified information (for example, information including only the recipe ID, recipe name, and thumbnail image) for multiple recipes to be displayed on the recipe list screen (hereinafter referred to as "recipe list information acquisition requests"), and requests to send recipe information RI for a recipe specified by user U (hereinafter referred to as "recipe detailed information acquisition requests").

[0070] <3.4 Recipe Provision Department> The recipe provision unit 340 provides user U with information about recipes by transmitting the information about recipes to the terminal device 400 in response to requests obtained by the request acquisition unit 330. For example, if the recipe provision unit 340 receives a request to acquire recipe list information, it acquires simplified information for multiple recipes from the recipe DB 391 in response to the request and transmits the acquired simplified information for multiple recipes to the terminal device 400. Also, if the recipe provision unit 340 receives a request to acquire detailed recipe information for a desired recipe specified by user U, it acquires recipe information RI for the desired recipe from the recipe DB 391 in response to the request and transmits the acquired recipe information RI for the desired recipe to the terminal device 400.

[0071] <3.5 Storage section> The memory unit 390 is implemented by a combination of, for example, RAM, ROM, EEPROM, SSD, or HDD. The memory unit 390 stores various types of information. For example, the memory unit 390 stores the recipe DB 391 and the favorite recipe DB 392.

[0072] <4. User U's terminal device> Next, we will describe the terminal device 400 of user U. Figure 7 is a block diagram showing the functional configuration of the terminal device 400. The terminal device 400 includes, for example, an information acquisition unit 410, a display control unit 420, an operation reception unit 430, a cooking setting transmission unit 440, and a storage unit 490.

[0073] The information acquisition unit 410, the display control unit 420, the operation reception unit 430, and the cooking setting transmission unit 440 are realized by one or more hardware processors, such as a CPU mounted on the terminal device 400, executing the application program P. In other words, the information acquisition unit 410, the display control unit 420, the operation reception unit 430, and the cooking setting transmission unit 440 are software functions included in the home appliance management app APP. One or more of these functions may be provided on the device management server 200 or the recipe management server 300 instead of the home appliance management app APP.

[0074] <4.1 Information acquisition section> The information acquisition unit 410 communicates with the device management server 200 or the recipe management server 300 to acquire various information from the device management server 200 or the recipe management server 300. For example, based on the operation of user U detected by the operation reception unit 430 (described later), the information acquisition unit 410 sends a request to acquire recipe list information or a request to acquire detailed recipe information to the recipe management server 300, and acquires information about recipes (for example, simplified information for multiple recipes, or recipe information RI for a desired recipe) as a response to the transmitted request. The information acquisition unit 410 stores the information about recipes acquired from the recipe management server 300 (for example, simplified information for multiple recipes, or recipe information RI for a desired recipe) in the storage unit 490 at least temporarily as recipe-related information 491.

[0075] <4.2 Display Control Unit> The display control unit 420 controls the content displayed on the display screen 401a of the display device 401 of the terminal device 400 by controlling the display device 401 of the display device 401. The content displayed on the display screen 401a, as described below, is realized by the processing of the display control unit 420. Specific examples of the processing of the display control unit 420 will be described later.

[0076] <4.3 Operation Reception Section> The operation reception unit 430 receives user U operations performed on the input device 402 in connection with the home appliance management application APP. User U operations on the various operation buttons displayed on the display screen 401a, described later, are received by the operation reception unit 430. The operation reception unit 430 transmits information or signals corresponding to the various operations received by the operation reception unit 430 to the equipment management server 200 or the recipe management server 300.

[0077] <4.4 Cooking Settings Transmission Unit> The cooking setting transmission unit 440 transmits the cooking setting information S6 contained in the recipe information RI to the cooking appliance 100. For example, based on the user U's operation on the operation unit B25 (see Figure 12) displayed on the display screen 401a, the cooking setting transmission unit 440 transmits the cooking setting information S6 corresponding to the recipe displayed on the display screen 401a to the equipment management server 200.

[0078] <4.5 Storage section> The memory unit 490 is implemented by a combination of, for example, RAM, ROM, EEPROM, or SSD. The memory unit 490 stores various types of information. For example, the memory unit 490 stores the application program P and recipe-related information 491.

[0079] <5. Example Display> Next, we will describe examples of displays shown on terminal devices 400 and 500.

[0080] <5.1 Example of display when registering a recipe> <5.1.1 Example of how a representative recipe will be displayed when registered> Figure 8 is a diagram illustrating an example of the recipe registration screen D10. The recipe registration screen D10 is the screen displayed on the display screen 501a of the terminal device 500 when an operator OP registers a recipe. Figure 8 is an example of the recipe registration screen D10 when a representative recipe is registered (hereinafter, for distinction, this screen will be referred to as "recipe registration screen D11").

[0081] The recipe registration screen D11 includes, for example, an identification information display area A11, a recipe name input area A12, a publication status input area A13, a thumbnail image input area A14, an ingredient input area A15, a process input area A16, and a title input area A17.

[0082] The identification information display area A11 displays the recipe ID provided by the recipe management server 300. The recipe name input area A12 displays a text input box C12 that accepts input of, for example, the recipe name. The publication status input area A13 displays an operation unit B13 that allows the user to select whether to register the recipe as "public" or "private". The thumbnail image input area A14 displays an input unit C14 that accepts input of a thumbnail image. The ingredient input area A15 displays multiple text input boxes C15 that accept input related to ingredients. The process input area A16 displays multiple text input boxes C16 that accept input related to the cooking process.

[0083] The title input area A17 includes, for example, a first title input unit A171 that accepts input for the first title, a second title input unit A172 that accepts input for the second title, and an operation unit B17 for adding titles. When the operation unit B17 is operated by the operator OP (for example, pressed), the same set of title input units as the first title input unit A171 is added to the title input area A17.

[0084] The first topic input unit A171 includes a character input box C171a for receiving input for the first topic, one or more character input boxes C171b for receiving input for recipe IDs of related recipes associated with the representative recipe as recipes related to the first topic, one or more character input boxes C171c for receiving input for descriptions of the contents of the related recipes, an operation unit B181a for adding related recipes associated with the representative recipe as recipes related to the first topic, an operation unit B181b for deleting the setting of the first topic, and an operation unit B181c for unassociating related recipes with the representative recipe.

[0085] Similarly, the second topic input unit A172 includes a character input box C172a for receiving input for the second topic, one or more character input boxes C172b for receiving input for the recipe IDs of related recipes associated with the representative recipe as recipes related to the second topic, one or more character input boxes C172c for receiving input for descriptions of the contents of the related recipes, an operation unit B182a for adding related recipes associated with the representative recipe as recipes related to the second topic, an operation unit B182b for deleting the setting of the second topic, and an operation unit B182c for unassociating related recipes with the representative recipe.

[0086] When registering a recipe, the terminal device 500 displays the recipe registration screen D10 on its display screen 501a. The terminal device 500 transmits the information entered by the operator OP through the recipe registration screen D10 to the recipe management server 300.

[0087] <5.1.2 Example of display when registering related recipes> Figure 9 is a diagram illustrating another example of the recipe registration screen D10. Figure 9 is an example of the recipe registration screen D10 when related recipes are registered (hereinafter, for distinction, this screen will be referred to as "recipe registration screen D12").

[0088] The recipe registration screen D12 includes, for example, an identification information display area A11, a recipe name input area A12, a publication status input area A13, a thumbnail image input area A14, an ingredient input area A15, a process input area A16, and a title input area A17.

[0089] In this embodiment, when related recipes are associated with a representative recipe, the recipe management server 300 automatically registers the related recipes as "private." Therefore, the operation unit B13 for registering the publication status is not displayed in the publication status input area A13 of the recipe registration screen D12. Alternatively, the operation unit B13 may be displayed in a disabled state (for example, grayed out) in the publication status input area A13 of the recipe registration screen D12.

[0090] <5.1.3 Restrictions on Recipe Registration 1> Figure 10 is a diagram illustrating the constraints when registering a recipe. In this embodiment, the setting of the title of a related recipe is restricted. Therefore, when the operation unit B17 for adding a title in the title input area A17 of the recipe registration screen D12 is operated by the operator OP (for example, pressed), a predetermined display N1 is displayed on the display screen 401a, superimposed on the recipe registration screen D12.

[0091] Display N1 is, for example, a pop-up display indicating that a title cannot be set for the recipe because the recipe is a related recipe. Display N1 is displayed based on a signal received by the terminal device 500 from the recipe management server 300 as a response to a signal sent from the terminal device 500 to the recipe management server 300 indicating that the operation unit B17 has been operated. Alternatively, in the title input area A17 of the recipe registration screen D12, the operation unit B17 for adding a title does not have to be displayed, and may be displayed in an disabled state (for example, grayed out).

[0092] <5.1.4 Restrictions on Recipe Registration 2> Figure 11 illustrates another constraint during recipe registration. In this embodiment, the association of related recipes is restricted to one representative recipe. Therefore, if the recipe ID of a related recipe already associated with another representative recipe is entered into the text input box C171b of the title input area A17 on the recipe registration screen D11, a predetermined display N2 will be superimposed on the recipe registration screen D11 and displayed on the display screen 401a.

[0093] Display N2 is a pop-up display indicating, for example, that the recipe cannot be set as a related recipe because it is already associated with another representative recipe. Display N2 is displayed based on a signal received by the terminal device 500 from the recipe management server 300 as a response to the recipe ID entered in the text input box C171b being sent from the terminal device 500 to the recipe management server 300.

[0094] <5.2 Example of display when using the recipe> <5.2.1 Example of displaying a representative recipe> Figure 12 is a diagram illustrating an example of the recipe display screen D20. The recipe display screen D20 is the screen displayed on the display screen 401a of the terminal device 400 when user U views a recipe. The terminal device 400 sends a recipe details acquisition request to the recipe management server 300, requesting the transmission of the recipe information RI for the recipe selected by user U. Based on the recipe information RI received from the recipe management server 300 in response, the terminal device 400 displays the recipe display screen D20. Figure 12 is an example of the recipe display screen D20 displaying the recipe information RIA of a representative recipe (hereinafter, for distinction, this screen will be referred to as "recipe display screen D21").

[0095] The recipe display screen D21 includes, for example, a thumbnail image display area A21, a recipe name display area A22, an ingredient display area A23, a process display area A24, a cooking settings transmission area A25, and a related recipe selection area A26. The thumbnail image display area A21, the recipe name display area A22, the ingredient display area A23, the process display area A24, and the cooking settings transmission area A25 are arranged from top to bottom in this order, for example. The related recipe selection area A26 is placed, for example, between the recipe name display area A22 and the ingredient display area A23.

[0096] The thumbnail image display area A21 displays the thumbnail image included in the recipe information RI and a predetermined operation unit B21. The predetermined operation unit B21 is an operation unit for registering the recipe as a favorite recipe when operated (for example, pressed) by the user U. When the operation reception unit 430 detects an operation by the user U operating the operation unit B21, it sends a predetermined request to the recipe management server 300 to register the recipe as a favorite. The predetermined request includes the recipe ID of the recipe to be registered as a favorite. In this embodiment, when registering a recipe as a favorite while the representative recipe is displayed, the predetermined request includes the recipe ID of the representative recipe to which the related recipe is linked.

[0097] The recipe name display area A22 displays the recipe name included in the recipe information RI. The ingredient display area A23 displays the ingredient information S4 included in the recipe information RI. The process display area A24 displays the process information S5 included in the recipe information RI.

[0098] The cooking setting transmission area A25 displays a cooking setting transmission operation unit B25 for sending cooking setting information S6 contained in the recipe information RI to the equipment management server 200. When the operation reception unit 430 detects that the cooking setting transmission operation unit B25 has been operated by user U (for example, pressed), the cooking setting transmission unit 440 transmits the cooking setting information S6 contained in the recipe information RI of the currently displayed recipe to the equipment management server 200.

[0099] Next, we will explain the related recipe selection area A26. In this embodiment, when a related recipe is registered to be associated with a representative recipe, the display control unit 420 displays an operation unit B26 for displaying related recipes on the display screen 401a when the representative recipe is to be displayed on the display screen 401a, and displays the related recipes on the display screen 401a when a predetermined operation including the operation of operation unit B26 is performed. For example, when a predetermined operation including the operation of operation unit B26 is performed, the display control unit 420 switches the display of the representative recipe to the display of related recipes on the display screen 401a. In this application, the "operation unit for displaying related recipes" is not limited to an operation unit that displays related recipes in a single operation, but may also include, for example, an operation unit that displays related recipes by operating another operation unit that is displayed by operating the said operation unit. "Operating another operation unit (for example, operation unit B27 described later) that is displayed by operating an operation unit (for example, operation unit B26)" is an example of a "predetermined operation".

[0100] In the example shown in Figure 12, the display control unit 420 displays an operation unit B26 in the related recipe selection area A26 for switching the recipes to be displayed on the display screen 401a. Operation unit B26 is, for example, an operation unit that displays the title name of a set topic and an operation unit B27 for selecting related recipes associated with a representative recipe as recipes related to that topic. In the example shown in Figure 12, operation unit B27 is an operation unit that includes a list in which descriptions of related recipes related to the set topic are displayed.

[0101] The display control unit 420 displays an operation unit B27 for selecting the target related recipe when the operation unit B26 is operated (for example, pressed) by the user U. The operation unit B27 includes, for example, a description of the contents of the related recipe (for example, information entered into the text input box C171c and included in the title information S8 of the recipe information RI), as well as an operation unit B27a for selecting the target related recipe. The operation unit B27 is displayed, for example, by a pop-up on the recipe display screen D21, but it may also be displayed in another manner (for example, by a screen transition).

[0102] When the operation reception unit 430 detects that the operation unit B27a for selecting the destination recipe has been operated by user U, the information acquisition unit 410 sends a recipe details acquisition request to the recipe management server 300 requesting the recipe information RI of the destination recipe, and obtains the recipe information RI of the destination recipe from the recipe management server 300 in response. Then, the display control unit 420 switches the recipe displayed on the recipe display screen D20 based on the obtained recipe information RI of the destination recipe.

[0103] Figure 12 shows an example where a representative recipe with only one title is displayed, for the sake of explanation. If multiple titles are set for a single representative recipe, the display control unit 420 displays multiple operation units B26 corresponding to the multiple titles in the related recipe selection area A26. Each operation unit B26 displays the title corresponding to that operation unit B26 and also displays an operation unit B27 for selecting a related recipe associated with the representative recipe as a recipe related to that title when operated.

[0104] <5.2.2 Example of displaying related recipes> Figure 13 is a diagram illustrating another example of the recipe display screen D20. Figure 13 is an example of the recipe display screen D20 that displays the recipe information RIB of related recipes (hereinafter, for distinction, this screen will be referred to as "recipe display screen D22").

[0105] The recipe display screen D22 includes, for example, a thumbnail image display area A21, a recipe name display area A22, an ingredient display area A23, a process display area A24, a cooking settings transmission area A25, and a related recipe selection area A26.

[0106] In this embodiment, when the display control unit 420 displays the recipe information RIB of related recipes on the display screen 401a, it displays the operation units B26 and B27 for switching recipes based on the recipe information RIA of the representative recipe which was acquired earlier and stored in the storage unit 490 as part of the recipe related information 491. Alternatively, when the display control unit 420 displays the recipe information RIB of related recipes on the display screen 401a, it may also display an operation unit on the display screen 401a for returning to the recipe display screen D21 which displays the representative recipe.

[0107] <5.3 Example of display for favorite recipes> Next, we will explain an example of how your favorite recipes are displayed. Figure 14 is a diagram illustrating the display of favorite recipes. In Figure 14 (a), the recipe display screen D22 shows related recipes corresponding to four servings. When the user U operates the operation unit B21 for registering a favorite while the recipe display screen D22 is displayed, a request including the recipe ID of the currently displayed related recipe is sent to the recipe management server 300 as a request to register a favorite.

[0108] In this case, the favorite recipe management unit 320 of the recipe management server 300 determines the public status of the related recipe based on the recipe information RIB of the related recipe being displayed. If the related recipe is registered as private, it registers the recipe ID of the representative recipe to which the related recipe is associated (for example, a recipe with a quantity corresponding to one serving) in the favorite recipe DB 392 instead of the related recipe being displayed. On the other hand, if the related recipe is not registered as private (i.e., it is registered as public), the favorite recipe management unit 320 registers the recipe ID of the related recipe being displayed in the favorite recipe DB 392.

[0109] Alternatively, instead of the above process, the determination of the publication status of related recipes may be performed by the operation reception unit 430 of the terminal device 400. In this case, if the related recipe is registered as private, the operation reception unit 430 may send a request to the recipe management server 300 as a request for favorite registration, including the recipe ID of the representative recipe to which the related recipe is associated. On the other hand, if the related recipe is not registered as private, the operation reception unit 430 may send a request to the recipe management server 300 as a request for favorite registration, including the recipe ID of the related recipe.

[0110] Figure 14(b) shows an example of the display when the operation in Figure 14 is performed. Figure 14(b) shows an example of the favorite recipe display screen D30 which displays a list of favorite recipes. In this embodiment, the display control unit 420 displays the favorite recipe display screen D30, which displays a list of recipes that have been registered as favorites, on the display screen 401a in response to the operation of a predetermined operation unit. In this embodiment, when the operation unit B21 is operated while a related recipe (for example, a recipe with a quantity corresponding to 4 servings) is displayed on the display screen 401a, the representative recipe associated with the related recipe is registered as a favorite, and the display B31 of the representative recipe is displayed on the favorite recipe display screen D30. When this display B31 is operated by the user U (for example, pressed), the recipe information RI of the representative recipe is acquired by the information acquisition unit 410, and the acquired recipe information RI of the representative recipe is displayed on the display screen 401a by the display control unit 420.

[0111] <6. Control Flow> Next, I will explain the control flow. Figure 15 is a flowchart showing the control flow for displaying recipes on the terminal device 400. First, when the operation reception unit 430 detects that user U has selected one recipe from among several recipes displayed on the recipe list screen, for example, the information acquisition unit 410 sends a request to the recipe management server 300 to acquire detailed recipe information, including the recipe ID of the said recipe, and in response, acquires the recipe information RI of the said recipe from the recipe management server 300 (S101). The recipe information RI acquired by the information acquisition unit 410 is retained as part of the recipe-related information 491 in the storage unit 490, at least until the startup state of the home appliance management application APP is terminated.

[0112] Next, the display control unit 420 extracts information related to the recipe (for example, recipe name information S2, recipe image S3, ingredient information S4, and process information S5) from the acquired recipe information RI, and incorporates the extracted information into the display information (S102).

[0113] Next, the display control unit 420 determines whether or not title information S8 exists in the acquired recipe information RI (S103). If title information S8 exists in the acquired recipe information RI (S103: YES), the display control unit 420 incorporates the title included in title information S8, a list of related recipes, and a description of the contents of the related recipes into the display information (S104).

[0114] On the other hand, if the acquired recipe information RI does not contain title information S8 (S103: NO), the display control unit 420 obtains the recipe ID of the representative recipe that is associated with the acquired recipe based on the associated destination information S9 of the recipe information RI. Then, based on the recipe ID of the representative recipe, the display control unit 420 obtains the title information S8 contained in the recipe information RIA of the representative recipe from the recipe related information 491 stored in the storage unit 490. The display control unit 420 incorporates the title, the list of related recipes (including the representative recipe), and the description of the contents of the related recipes (including the description of the contents of the representative recipe) contained in the acquired title information S8 into the display information (S105).

[0115] Next, the display control unit 420 incorporates the display from the operation unit B25 for transmitting cooking setting information into the display information (S106). Then, the display control unit 420 displays the display information generated as described above on the display screen 401a (S107).

[0116] Figure 16 is a sequence diagram showing the control flow for displaying a recipe on the terminal device 400. First, when the operation reception unit 430 detects that user U has selected one recipe from among several recipes displayed on the recipe list screen, the information acquisition unit 410 of the terminal device 400 sends a request to the recipe management server 300 to acquire detailed recipe information, including the recipe ID of the selected recipe (S201). When the recipe management server 300 receives the request to acquire detailed recipe information from the terminal device 400, it extracts the recipe information RI for the selected recipe from the recipe DB 391 based on the recipe ID included in the request, and sends the extracted recipe information RI to the terminal device 400 (S202). The display control unit 420 of the terminal device 400 generates display information for the recipe based on the recipe information RI received from the recipe management server 300 and displays it on the display screen 401a (S203).

[0117] The operation reception unit 430 of the terminal device 400 receives an operation from user U who operates the operation unit B27 for switching recipes (S210). When the operation unit B27 for switching recipes is operated, the information acquisition unit 410 of the terminal device 400 sends a request to the recipe management server 300 to acquire detailed recipe information, including the recipe ID of the recipe to be switched (S211). When the recipe management server 300 receives the request to acquire detailed recipe information from the terminal device 400, it extracts the recipe information RI for the recipe from the recipe DB 391 based on the recipe ID included in the request to acquire detailed recipe information, and sends the extracted recipe information RI to the terminal device 400 (S212). The display control unit 420 of the terminal device 400 generates display information for the recipe based on the recipe information RI received from the recipe management server 300, and switches the display of the display screen 401a by displaying the generated display information on the display screen 401a (S213).

[0118] The operation reception unit 430 of the terminal device 400 receives an operation from user U who is operating the operation unit B25 that transmits cooking settings (S220). The cooking setting transmission unit 440 of the terminal device 400 transmits a cooking setting transmission request to the equipment management server 200, which includes cooking setting information S6 corresponding to the recipe displayed on the display screen 401a, when the operation unit 25 displayed on the display screen 401a is operated by user U (S221). When the equipment management server 200 receives a cooking setting transmission request from the terminal device 400, it transmits the cooking setting information S6 included in the received cooking setting transmission request to the cooking appliance 100 (S222). When the cooking appliance 100 has performed cooking settings based on the cooking setting information S6, it transmits the result of the cooking settings to the equipment management server 200 (S223). When the equipment management server 200 receives the result of the cooking settings from the cooking appliance 100, it transmits the received result of the cooking settings to the terminal device 400 (S224).

[0119] <7. Advantages> In this embodiment, the information processing system includes a recipe registration unit 310 and a display control unit 420. The recipe registration unit 310 accepts the registration of a first recipe, and if a title can be set for the first recipe, it accepts the registration of a second recipe related to the title as part of the registration of the first recipe or in a separate process, when a title is set for the first recipe. When the registration of the second recipe associating with the first recipe is performed, the display control unit 420 displays an operation unit B26 for displaying the second recipe on the display screen 401a when the first recipe is to be displayed on the display screen 401a. The display control unit 420 displays the second recipe on the display screen 401a when a predetermined operation, including the operation of the operation unit B26, is performed.

[0120] With this configuration, multiple recipes can be associated based on a set theme. As a result, it is possible to present not only recipes with slight changes in ingredients or characteristics, but also recipes with different quantities, similar recipes, or other recipes in the same category (spicy, Japanese style, or purpose, etc.). For example, if the theme can be freely set, related recipes can be set in a general way, not limited to specific content. Therefore, it becomes easier for user U to obtain information on recipes that interest them. This improves user U's convenience.

[0121] In this embodiment, the recipe registration unit 310 can set two or more titles for the first recipe, and when two or more titles are set for the first recipe, it can accept registrations associating each of the two or more titles with another first recipe. With this configuration, related recipes can be set for a single recipe from multiple perspectives. This further improves the convenience for user U.

[0122] In this embodiment, the above title refers to the quantity of ingredients. With this configuration, it becomes easier to obtain information on recipes with different quantities. This further improves the convenience for user U.

[0123] In this embodiment, when the recipe registration unit 310 receives a registration that associates a second recipe with a first recipe, it registers a private setting for the second recipe to prevent it from being displayed on the recipe list screen. With this configuration, low-priority recipes (for example, multiple recipes that simply differ in quantity) are displayed on the recipe list screen, which prevents the display of low-priority recipes from interfering with the search for the desired recipe. Furthermore, since the registration of the private setting is performed automatically by the recipe registration unit 310, the workload of the operator OP can be reduced.

[0124] In this embodiment, multiple recipes can be registered as second recipes, and the recipe registration unit 310 may accept registration or cancellation of the above-mentioned private setting for each recipe registered as a second recipe. With this configuration, public and private settings can be registered for each recipe, enabling detailed management.

[0125] Here, consider a scenario where a recipe provider wants to unlink a related recipe B, which is associated with a representative recipe A, and replace it with another related recipe C. When unlinking, it becomes necessary to determine whether it is better to make the recipe public or keep it private. Generally, recipes that were set to private when they were linked often have other recipes with almost identical content, so it is preferable to keep them private even after unlinking. On the other hand, recipes that were set to public when they were linked are independent recipes, and it is assumed that there will be no problem even if they remain public after unlinking. Therefore, from an operational standpoint, it is preferable for recipes that have been unlinked to retain the public status they had when they were linked.

[0126] Therefore, in this embodiment, the recipe registration unit 310 can unassociate the second recipe with the first recipe, and if the association of the second recipe with the private setting is unassociated with the first recipe, the registration of the private setting for the second recipe is maintained. Also, if the association of the second recipe with the public setting is unassociated with the first recipe, the recipe registration unit 310 maintains the registration of the public setting for the second recipe.

[0127] In this embodiment, for example, if the title is "Quantity," Recipe B associated with Recipe A will be forcibly made private. In this situation, if we set the title of Recipe B to "Similar Recipe" and associate another Recipe C with Recipe B, the recipe provision service cannot function unless Recipe B is made public, but a contradiction arises in the operation that recipes with different quantities are not displayed in the list.

[0128] Therefore, in this embodiment, the setting of a title for the second recipe associated with the first recipe is restricted, thereby preventing another recipe from being associated with the second recipe. With this configuration, the operational inconsistencies described above can be avoided, and a more user-friendly service can be provided for the user U or operator OP.

[0129] In this case, if a related recipe can be associated with multiple representative recipes, a contradiction may arise where recipe B is not publicly available in relation to recipe A, but is publicly available in relation to recipe C.

[0130] Therefore, in this embodiment, for a second recipe associated with a first recipe, the second recipe is restricted to being associated with only one other recipe, thereby preventing it from being associated with another recipe. With this configuration, the operational inconsistencies described above can be avoided, and a more user-friendly service can be provided for the user U or operator OP.

[0131] In this context, providing a recipe favorites feature in a recipe service would enhance user convenience. In such a system, the question arises: should a related recipe B be displayed in the favorites list? If recipe B is simply a variation of recipe A with different quantities, displaying duplicate recipes would be disruptive and undesirable. On the other hand, if the related recipe is a similar recipe to recipe A, it's a separate recipe and might be desirable to display in the list.

[0132] Therefore, in this embodiment, when the favorite recipe management unit 320 detects an operation by user U instructing the user to register the second recipe as a favorite, if the second recipe is registered as private, it accepts the registration of the first recipe as a favorite instead of the second recipe, and if the second recipe is not registered as private, it accepts the registration of the second recipe as a favorite. With this configuration, the appropriate recipe can be displayed on the favorite recipe list screen based on the relationship between the first recipe and the second recipe.

[0133] (Second Embodiment) Next, a second embodiment will be described. The second embodiment differs from the first embodiment in that the registration or cancellation of "public settings" and "private settings" for related recipes can be set for each title. Other than what is described below, the configuration is the same as the first embodiment.

[0134] Figure 17 is a diagram illustrating an example of the recipe registration screen D11 of the second embodiment. In this embodiment, it is possible to register the association of multiple related recipes with one representative recipe. The recipe registration unit 310 can also accept registration of a private setting for each title, which suppresses the display of multiple recipes registered as related recipes on the recipe list screen.

[0135] For example, in the example shown in Figure 17, the title input area A17 displays an operation panel B181d that allows the user to select whether to register all related recipes associated with the first title as "Public" or "Private" in terms of their publication status, and an operation panel B182d that allows the user to select whether to register all related recipes associated with the second title as "Public" or "Private" in terms of their publication status.

[0136] With this configuration, for example, you might not want to display recipes that only differ in quantity on the recipe list screen, but you might want to display related recipes on the recipe list screen if they share a similar theme. In this way, you can set the visibility status of multiple related recipes together on the recipe list screen. This configuration makes it easy to manage the visibility status of recipes.

[0137] (Third embodiment) Next, a third embodiment will be described. The third embodiment differs from the first embodiment in that related recipes are also managed in relation to favorite registration. Other than what is described below, the configuration is the same as that of the first embodiment.

[0138] In this embodiment, when the favorite recipe management unit 320 detects an operation by user U instructing to register a second recipe (related recipe) as a favorite, if the second recipe is registered as private, it registers the first recipe (representative recipe) as a favorite instead of the second recipe, and stores predetermined information in the storage unit 390 indicating that the favorite registration was made while the second recipe was being displayed. Then, the next time the favorite recipe management unit 320 detects an operation by user U to display the first recipe that was registered as a favorite, it displays the second recipe based on the predetermined information.

[0139] Figure 18 is a diagram illustrating the favorite recipe DB392 of the third embodiment. In the favorite recipe DB392, the recipe ID of each favorite recipe is registered, and for each favorite recipe, an additional information DI indicating which recipe was being displayed is stored in association with it. The additional information DI is an example of "predetermined information".

[0140] Figure 19 is a sequence diagram showing the control flow for registering a favorite recipe. First, when a user U performs an operation on the operation unit B21 to register a favorite recipe while a related recipe is displayed on the display screen 401a, the operation reception unit 430 of the terminal device 400 detects the operation by the user U (S301). When the operation reception unit 430 detects the operation by the user U, it sends a request to the recipe management server 300 as a request to register a favorite recipe, including the recipe ID of the related recipe currently on display (S302).

[0141] When the favorite recipe management unit 320 of the recipe management server 300 receives a request for the above-mentioned favorite registration from the terminal device 400, it determines whether or not the related recipe has been registered as private based on the recipe information RIB of the related recipe that has the recipe ID included in the request.

[0142] The Favorite Recipe Management Unit 320 accepts the registration of a related recipe as a favorite if, based on the above determination, there is no registration of a private setting for the related recipe (i.e., there is a registration of a public setting). For example, the Favorite Recipe Management Unit 320 registers the related recipe as a favorite recipe by registering the recipe ID of the related recipe in the Favorite Recipe DB 392.

[0143] On the other hand, if the Favorite Recipe Management Unit 320 determines that a related recipe is set to private, it accepts the registration of the representative recipe associated with that related recipe as a favorite instead of the related recipe. For example, the Favorite Recipe Management Unit 320 obtains the recipe ID of the representative recipe associated with that related recipe based on the recipe information RIB of the related recipe, and registers the obtained recipe ID of the representative recipe in the Favorite Recipe DB 392, thereby registering that representative recipe as a favorite recipe. At this time, the Favorite Recipe Management Unit 320 registers the recipe ID of the related recipe as an additional information DI to the recipe ID of the representative recipe (S303). Then, the Favorite Recipe Management Unit 320 sends a notification of completion of favorite registration to the terminal device 400 (S304).

[0144] Alternatively, instead of the above process, the determination of the publication status of related recipes may be performed by the operation reception unit 430 of the terminal device 400. In this case, if the related recipe is registered as private, the operation reception unit 430 may send a request to the recipe management server 300 as a request for favorite registration, including the recipe ID of the representative recipe to which the related recipe is associated. On the other hand, if the related recipe is not registered as private, the operation reception unit 430 may send a request to the recipe management server 300 as a request for favorite registration, including the recipe ID of the related recipe.

[0145] When viewing favorite recipes, the operation reception unit 430 of the terminal device 400 receives an operation from user U to select a representative recipe displayed on the recipe list screen. In this case, the operation reception unit 430 sends a request to the recipe management server 300 to obtain detailed recipe information, including the recipe ID of the representative recipe selected by user U (S311).

[0146] When the favorite recipe management unit 320 of the recipe management server 300 receives a request to obtain detailed recipe information from the terminal device 400, it determines, based on the additional information DI, whether or not the recipe ID of the related recipe is registered in correspondence with the recipe ID of the representative recipe included in the request (S312). If the recipe ID of the related recipe is not registered in the above determination, the recipe provision unit 340 sends the recipe information RIA of the representative recipe to the terminal device 400 as a response to the request to obtain detailed recipe information. On the other hand, if the recipe ID of the related recipe is registered in the above determination, the recipe provision unit 340 sends the recipe information RIB of the related recipe to the terminal device 400 as a response to the request to obtain detailed recipe information (S313).

[0147] With this configuration, when browsing favorite recipes, the system can remember related recipes that user U wants to see (for example, recipes with specific quantities that user U wants to see), making it easy for user U to access those related recipes.

[0148] Although several embodiments have been described above, the embodiments are not limited to the examples given. For example, the second and third embodiments may be implemented in combination.

[0149] According to at least one embodiment described above, the information processing system comprises a recipe registration unit and a display control unit. The recipe registration unit accepts registration of a first recipe, and a title can be set for the first recipe. When a title is set for the first recipe, the system accepts registration of a second recipe related to the title and associates it with the first recipe. When the display control unit displays the first recipe on the display screen, it displays an operation unit on the display screen for displaying the second recipe. With this configuration, convenience can be improved.

[0150] While several embodiments of the present invention have been described, these embodiments are presented as examples only and are not intended to limit the scope of the invention. These embodiments can be carried out in a variety of other forms, and various omissions, substitutions, and modifications can be made without departing from the spirit of the invention. These embodiments and their variations are included in the scope and spirit of the invention, as well as in the claims and their equivalents. [Explanation of symbols]

[0151] 1...Service provision system, 100...Cooking appliances, 200...Device management server, 300...Recipe management server, 310...Recipe registration unit, 320...Favorite recipe management unit, 330...Request acquisition unit, 340...Recipe provision unit, 400...Terminal device, 410...Information acquisition unit, 420...Display control unit, 430...Operation reception unit, 440...Cooking setting transmission unit, 500...Terminal device.

Claims

1. A recipe registration unit accepts registration of a first recipe, and allows a title to be set for the first recipe, and when a title is set for the first recipe, accepts registration of a second recipe related to the title as part of the registration of the first recipe or in a separate process, When the second recipe is registered in association with the first recipe, the display control unit displays an operation unit for displaying the second recipe on the display screen when the first recipe is to be displayed on the display screen, and displays the second recipe on the display screen when a predetermined operation including the operation unit is performed, Equipped with, The recipe registration unit can unassociate the second recipe with the first recipe, and if the association with the first recipe is unassociated with the second recipe for which a private setting has been registered to prevent it from being displayed on the recipe list screen, the unit maintains the private setting registration for the second recipe. Information processing system.

2. With respect to the second recipe associated with the first recipe, the setting of a title for the second recipe is restricted, and the association of another recipe with the second recipe is suppressed. The information processing system according to claim 1.

3. With respect to the second recipe associated with the first recipe, the number of recipients to which the second recipe can be associated is restricted to one, and the association of the second recipe with any other recipe in addition to the first recipe is suppressed. The information processing system according to claim 1 or claim 2.

4. A recipe registration unit that accepts registration of a first recipe, and allows a title to be set for the first recipe, and when a title is set for the first recipe, accepts registration of a second recipe related to the title as part of the registration of the first recipe or in a separate process, When the second recipe is registered in association with the first recipe, the display control unit displays an operation unit for displaying the second recipe on the display screen when the first recipe is to be displayed on the display screen, and displays the second recipe on the display screen when a predetermined operation including the operation unit is performed, The Favorite Recipe Management Department accepts registrations of favorite recipes, Equipped with, When the favorite recipe management unit detects a user action instructing the user to add the second recipe to their favorites, if there is a private setting registered for the second recipe that prevents it from being displayed on the recipe list screen, the unit accepts the user to add the first recipe to their favorites instead of the second recipe. If there is no private setting registered for the second recipe, the unit accepts the user to add the second recipe to their favorites. Information processing system.

5. A recipe registration unit that accepts registration of a first recipe, and allows a title to be set for the first recipe, and when a title is set for the first recipe, accepts registration of a second recipe related to the title as part of the registration of the first recipe or in a separate process, When the second recipe is registered in association with the first recipe, the display control unit displays an operation unit for displaying the second recipe on the display screen when the first recipe is to be displayed on the display screen, and displays the second recipe on the display screen when a predetermined operation including the operation unit is performed, The Favorite Recipe Management Department accepts registrations of favorite recipes, Equipped with, When the favorite recipe management unit detects a user action to register the second recipe as a favorite, and there is a setting to prevent the second recipe from being displayed on the recipe list screen from being made private, it registers the first recipe as a favorite instead of the second recipe, stores predetermined information indicating that the favorite registration was made while the second recipe was being displayed, and in subsequent instances, when the user action to display the first recipe is detected, it displays the second recipe based on the predetermined information. Information processing system.

6. A recipe registration unit that accepts registration of a first recipe, and allows a title to be set for the first recipe, and when a title is set for the first recipe, accepts registration of a second recipe related to the title as part of the registration of the first recipe or in a separate process, When the second recipe is registered in association with the first recipe, the display control unit displays an operation unit for displaying the second recipe on the display screen when the first recipe is to be displayed on the display screen, and displays the second recipe on the display screen when a predetermined operation including the operation unit is performed, Equipped with, As the second recipe, multiple recipes can be registered for each of the above titles. The recipe registration unit can accept an operation to register or unregister, in bulk, the private setting that prevents the multiple recipes from being displayed on the recipe list screen for each of the aforementioned titles. Information processing system.

7. A recipe registration unit that accepts registration of a first recipe, and allows a title to be set for the first recipe, and when a title is set for the first recipe, accepts registration of a second recipe, which is a recipe related to the title and was registered as a separate recipe prior to the registration of the first recipe, as part of the registration of the first recipe or in a separate process, to associate the second recipe with the first recipe. When the second recipe is registered in association with the first recipe, the display control unit displays an operation unit for displaying the second recipe on the display screen when the first recipe is to be displayed on the display screen, and displays the second recipe on the display screen when a predetermined operation including the operation unit is performed, An information processing system equipped with [the following features].

8. One or more computers, The system accepts registration of a first recipe, and allows a title to be set for the first recipe. If a title is set for the first recipe, the system accepts registration of a second recipe related to the title, either as part of the registration of the first recipe or in a separate process, associating the second recipe with the first recipe. When the second recipe is registered in association with the first recipe, when the first recipe is displayed on the display screen, an operation unit for displaying the second recipe is displayed on the display screen, and when a predetermined operation including operation of the operation unit is performed, the second recipe is displayed on the display screen. The association between the first recipe and the second recipe can be removed, and if the association between the second recipe and the first recipe is removed for the second recipe which has been set to private so that it is not displayed on the recipe list screen, the private setting for the second recipe will be maintained. Information processing methods that include the following.

9. One or more computers, The system accepts registration of a first recipe, and allows a title to be set for the first recipe. If a title is set for the first recipe, the system accepts registration of a second recipe related to the title, either as part of the registration of the first recipe or in a separate process, associating the second recipe with the first recipe. When the second recipe is registered in association with the first recipe, when the first recipe is displayed on the display screen, an operation unit for displaying the second recipe is displayed on the display screen, and when a predetermined operation including operation of the operation unit is performed, the second recipe is displayed on the display screen. When a user action instructing the user to add the second recipe to their favorites is detected, if there is a private setting registered for the second recipe that prevents it from being displayed on the recipe list screen, the user will accept the first recipe as a favorite instead of the second recipe. If there is no private setting registered for the second recipe, the user will accept the second recipe as a favorite. Information processing methods that include the following.

10. One or more computers, The system accepts registration of a first recipe, and allows a title to be set for the first recipe. If a title is set for the first recipe, the system accepts registration of a second recipe related to the title, either as part of the registration of the first recipe or in a separate process, associating the second recipe with the first recipe. When the second recipe is registered in association with the first recipe, when the first recipe is displayed on the display screen, an operation unit for displaying the second recipe is displayed on the display screen, and when a predetermined operation including operation of the operation unit is performed, the second recipe is displayed on the display screen. When a user action is detected instructing the user to add the second recipe to their favorites, and there is a setting registered to prevent the second recipe from being displayed on the recipe list screen from being made private, the first recipe is added to favorites instead of the second recipe, and predetermined information indicating that the favorite addition was made while the second recipe was being displayed is stored. In subsequent instances, when a user action is detected to display the first recipe, the second recipe is displayed based on the predetermined information. Information processing methods that include the following.

11. One or more computers, The system accepts registration of a first recipe, and allows a title to be set for the first recipe. If a title is set for the first recipe, the system accepts registration of a second recipe related to the title, either as part of the registration of the first recipe or in a separate process, associating the second recipe with the first recipe. When the second recipe is registered in association with the first recipe, when the first recipe is displayed on the display screen, an operation unit for displaying the second recipe is displayed on the display screen, and when a predetermined operation including operation of the operation unit is performed, the second recipe is displayed on the display screen. As the second recipe, multiple recipes can be registered for each title, and the system accepts an operation to register or unregister a private setting for each title, which prevents the multiple recipes from being displayed on the recipe list screen. Information processing methods that include the following.

12. One or more computers, The system accepts registration of a first recipe, and allows a title to be set for the first recipe. When a title is set for the first recipe, the system accepts registration of a second recipe, which is related to the title and was registered as a separate recipe prior to the registration of the first recipe, either as part of the registration of the first recipe or in a separate process, to associate it with the first recipe. When the second recipe is registered in association with the first recipe, and the first recipe is displayed on the display screen, an operation unit for displaying the second recipe is displayed on the display screen, and when a predetermined operation including operation of the operation unit is performed, the second recipe is displayed on the display screen. Information processing methods that include the following.

13. A computer which is a terminal device, The system accepts registration of the first recipe, and if a title can be set for the first recipe, then, as part of the registration of the first recipe or in a separate process, it accepts registration of a second recipe related to the title and associates it with the first recipe. When the second recipe is registered in association with the first recipe, when the first recipe is displayed on the display screen, an operation unit for displaying the second recipe is displayed on the display screen, and when a predetermined operation including operation of the operation unit is performed, the second recipe is displayed on the display screen. The association between the first recipe and the second recipe can be removed, and if the association between the second recipe and the first recipe is removed for the second recipe which has been set to private so that it is not displayed on the recipe list screen, the private setting for the second recipe will be maintained. program.

14. A computer which is a terminal device, The system accepts registration of the first recipe, and if a title can be set for the first recipe, then, as part of the registration of the first recipe or in a separate process, it accepts registration of a second recipe related to the title and associates it with the first recipe. When the second recipe is registered in association with the first recipe, when the first recipe is displayed on the display screen, an operation unit for displaying the second recipe is displayed on the display screen, and when a predetermined operation including operation of the operation unit is performed, the second recipe is displayed on the display screen. When a user action instructing the user to add the second recipe to their favorites is detected, if there is a private setting registered for the second recipe that prevents it from being displayed on the recipe list screen, the user is allowed to add the first recipe to their favorites instead of the second recipe. If there is no private setting registered for the second recipe, the user is allowed to add the second recipe to their favorites. program.

15. A computer which is a terminal device, The system accepts registration of the first recipe, and if a title can be set for the first recipe, then, as part of the registration of the first recipe or in a separate process, it accepts registration of a second recipe related to the title and associates it with the first recipe. When the second recipe is registered in association with the first recipe, when the first recipe is displayed on the display screen, an operation unit for displaying the second recipe is displayed on the display screen, and when a predetermined operation including operation of the operation unit is performed, the second recipe is displayed on the display screen. When a user operation instructing to add the second recipe to favorites is detected, and there is a setting to prevent the second recipe from being displayed on the recipe list screen from being made private, the user is instructed to add the first recipe to favorites instead of the second recipe, and predetermined information indicating that the favorite addition was made while the second recipe was being displayed is stored. In the future, when a user operation to display the first recipe is detected, the second recipe is displayed based on the predetermined information. program.

16. A computer which is a terminal device, The system accepts registration of the first recipe, and if a title can be set for the first recipe, then, as part of the registration of the first recipe or in a separate process, it accepts registration of a second recipe related to the title and associates it with the first recipe. When the second recipe is registered in association with the first recipe, when the first recipe is displayed on the display screen, an operation unit for displaying the second recipe is displayed on the display screen, and when a predetermined operation including operation of the operation unit is performed, the second recipe is displayed on the display screen. As the second recipe, multiple recipes can be registered for each title, and the system accepts an operation to register or unregister a private setting for each title, which prevents the multiple recipes from being displayed on the recipe list screen. program.

17. A computer which is a terminal device, The system accepts registration of the first recipe, and if a title can be set for the first recipe, then, as part of the registration of the first recipe or in a separate process, it accepts registration of a second recipe, which is related to the title and was registered as a separate independent recipe before the registration of the first recipe, associating it with the first recipe. When the second recipe is registered in association with the first recipe, and the first recipe is displayed on the display screen, an operation unit for displaying the second recipe is displayed on the display screen, and when a predetermined operation including operation of the operation unit is performed, the second recipe is displayed on the display screen. program.

Images