JP2024037347A - Information processing system, information processing method, and program - Google Patents

Abstract

An object of the present invention is to provide an information processing system, an information processing method, and a program that can improve convenience. An information processing system according to an embodiment includes an objective acquisition section and a recipe proposal section. The purpose acquisition unit acquires a recipe search purpose according to a user's action schedule. The recipe proposal unit proposes one or more recipes based on the search purpose acquired by the purpose acquisition unit. [Selection diagram] Figure 7

Description

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

An information processing system has been proposed that provides recipes in accordance with search conditions regarding the content of dishes. Such information processing systems are expected to further improve in convenience.

JP2022-052768A

The problem to be solved by the present invention is to provide an information processing system, an information processing method, and a program that can improve convenience.

The information processing system of the embodiment includes a purpose acquisition section and a recipe proposal section. The purpose acquisition unit acquires a recipe search purpose according to a user's action schedule. The recipe proposal unit proposes one or more recipes based on the search purpose acquired by the purpose acquisition unit.

FIG. 1 is a diagram showing the overall configuration of an information processing system according to an embodiment. FIG. 1 is a block diagram showing the functional configuration of a terminal device according to an embodiment. The figure which shows an example of the home screen of embodiment. The figure which shows an example of the search purpose input screen of embodiment. The figure which shows an example of the summary recipe list display screen of embodiment. The figure which shows an example of the detailed recipe display screen of embodiment. FIG. 2 is a block diagram showing the functional configuration of a server according to an embodiment. The figure which shows an example of the content of recipe DB of embodiment. The figure which shows an example of the content of user information DB of embodiment. The figure which shows an example of the content of the registered recipe DB of embodiment. FIG. 3 is a first sequence diagram showing an example of the overall flow of processing according to the embodiment. FIG. 7 is a second sequence diagram showing an example of the overall flow of processing in the embodiment. The figure which shows an example of the flow of a recipe search process of embodiment. The figure which shows an example of the flow of time planning processing of an embodiment. FIG. 3 is a diagram for explaining an example of time planning processing according to the embodiment. The figure which shows an example of the flow of notification condition setting processing of an embodiment. The figure which shows an example of the time plan display screen of embodiment. The figure which shows the other example of the summary recipe list display screen of embodiment. The figure which shows an example of the recipe search screen of embodiment.

Hereinafter, an information processing system, an information processing method, and a program according to embodiments will be described with reference to the drawings. In the following description, components having the same or similar functions are denoted by the same reference numerals. Further, redundant explanations of these configurations may be omitted. In this application, "based on XX" means "based on at least XX," and may include cases where it is based on another element in addition to XX. Furthermore, "based on XX" is not limited to the case where XX is used directly, but may also include the case where it is based on calculations or processing performed on XX. In this application, "XX or YY" is not limited to either XX or YY, but may include both XX and YY. This also applies when there are three or more selective elements. XX and YY are arbitrary elements (for example, arbitrary information).

In this application, "acquisition" is not limited to actively acquiring information by transmitting a transmission request, but may also include acquiring information by passively receiving information transmitted from another device. Furthermore, "acquisition" may also include acquiring target information by performing calculations or processing on information obtained from an external source to generate target information. In this application, "database" is expressed as "DB". In this application, there is no particular distinction between the terms "designation" and "setting." Therefore, in the following description, the terms "designation" and "setting" may be used interchangeably.

FIG. 1 is a diagram showing the overall configuration of an information processing system 1 according to an embodiment. The information processing system 1 includes, for example, a server 200 and a terminal device 300. Note that the "information processing system" referred to in this application is not limited to the information processing system 1, and may be realized only by the server 200, or may be realized only by the home appliance management application APP of the terminal device 300, and the home appliance management application APP of the terminal device 300. The network NW may be, for example, the Internet, cellular network, Wi-Fi network, LPWA (Low Power Wide Area), WAN (Wide Area Network), LAN (Local Area Network), or other public lines or private lines. You can use it accordingly.

(Configuration of terminal device)
Terminal device 300 is a terminal device used by user U. The terminal device 300 may be, for example, a mobile terminal device such as a smartphone or a tablet terminal device, or a personal computer. The terminal device 300 is connected to the network NW via, for example, a wireless router WR and a modem M, and transmits and receives data to and from the server 200. The terminal device 300 includes a display device 301 including a display screen 301a such as a liquid crystal display, and an input device 302 capable of receiving input from the user U. The input device 302 is, for example, a touch panel provided so as to overlap the display screen 301a of the display device 301. The input device 302 may include a camera, a microphone, etc. provided in the terminal device 300.

As shown in FIG. 2, the terminal device 300 includes, for example, a storage section 310, a display control section 311, an operation reception section 312, a search purpose setting section (search purpose reception section) 313, and a cooking condition setting section (cooking condition reception section). 314, a recipe search request section 315, a detailed recipe request section 316, a recipe registration section 317, an information acquisition section 318, and a calendar setting section 319. The storage unit 310 is a hardware function unit and stores data of an application program P installed in advance and internal terminal information 350. A software functional unit constructed by one or more hardware processors such as a CPU (Central Processing Unit) installed in the terminal device 300 executing an application program P is collectively referred to as a "home appliance management application APP". ”.

The internal terminal information 350 includes user identification information that is unique to the user U and is shared between the terminal device 300 and the server 200. Hereinafter, the user identification information will be referred to as a user ID (Identifier).

The display control unit 311, operation reception unit 312, search purpose setting unit 313, cooking condition setting unit 314, recipe search request unit 315, detailed recipe request unit 316, recipe registration unit 317, information acquisition unit 318, and calendar setting unit 319 are , is a software functional unit included in the home appliance management application APP described above.

For example, the display control unit 311 outputs data related to displaying images, characters, etc. to the display device 301 by itself, or receives and outputs them from other functional units, thereby displaying images, characters, etc. according to the data. is displayed on the display screen 301a. The display control unit 311 displays, for example, a home screen 501 shown in FIG. 3 on the display screen 301a.

The operation accepting unit 312 accepts a predetermined operation from the user U. More specifically, the operation reception unit 312 detects an operation performed by the user U on the input device 302, and outputs a control signal according to the detected operation. For example, assume that the user U operates the operation unit 51 that includes the character string "recipe" provided in the image of the home screen 501 in FIG. Note that the operation performed by the user U on the input device 302, which is a touch panel, is, for example, a tap operation. In this case, the operation reception unit 312 detects an operation in which the position of the operation unit 51 on the input device 302 is tapped. The operation reception unit 312 outputs a control signal according to the detected operation and the conditions under which the operation was detected.

The search purpose setting unit 313 accepts designation of a recipe search purpose according to user U's activity schedule. For example, the above-mentioned search purpose is a search purpose that includes a temporal condition according to the user U's action schedule. In this embodiment, the search purpose setting unit 313 displays a search purpose input screen 502 shown in FIG. 4 on the display screen 301a via the display control unit 311. In this embodiment, the search purpose setting unit 313 displays the search purpose input screen 502 during screen transition from the home screen 501 shown in FIG. 3 to the summary recipe list display screen 503 shown in FIG. Here, the description of the process of "displaying ... on the display screen 301a via the display control unit 311" means that the display control unit 311 captures some data output from other functional units, and from the captured data. This refers to the process of displaying a generated image or the like on the display screen 301a.

In the search purpose input screen 502, for example, an area surrounded by a broken line indicated by the reference numeral 53 is an input section (hereinafter referred to as "input section 53"). The input unit 53 receives content input to the input unit 53 by the user U via the operation reception unit 312 . The input unit 53 receives an input from the user U regarding the purpose of searching for a recipe.

For example, the input unit 53 accepts an input from the user U who specifies a cooking recipe to be started within a predetermined time as a search objective. The "predetermined time" is, for example, 30 minutes. An input by the user U specifying a recipe for cooking to be started within a predetermined time as a search object is received by the operation unit accompanied by a character string such as "Make it now", for example. Note that an operation unit with a character string such as "make it now" may be provided to receive an input from the user U who specifies a recipe for which cooking can be completed within a predetermined time as a search objective. Further, instead of/in addition to the above example, the input unit 53 may accept input regarding the scheduled cooking date, or may accept input regarding the cooking start time, cooking end time, or meal start time. The cooking start time, the cooking end time, and the meal start time are examples of "start time or end time of a user's predetermined action." The "predetermined action" is not limited to the start of cooking, the end of cooking, or the start of eating, but may also be the time when user U goes out, goes to bed, or starts another task. In the following, a case where "meal start time (meal start date and time)" is input will be described as a representative case. Therefore, in the following explanation, "meal start time (meal start date and time)" refers to "cooking end date and time (cooking end time)," "start time of user's predetermined action," and "end time of user's predetermined action." ” may be read as appropriate.

In the present embodiment, the input unit 53 has four selection candidates: "Normal", "Make it now", "Specify meal start date and time", and "Anniversary/Party", and operations corresponding to each of the four selection candidates. portions 53-1, 53-2, 53-3, 53-4, a date and time input portion 53-5 used when the selection candidate for “meal start date and time specification” is selected, and a character string for “decision”. and an operation section 54 including. The date and time input unit 53-5 is an example of an input unit that accepts time-related information (for example, meal start date and time) as a recipe search purpose.

Each of the operation units 53-1, 53-2, 53-3, and 53-4 is provided corresponding to the selection candidate on the right side. The operating units 53-1, 53-2, 53-3, and 53-4 are operating units that are selected in response to an operation by the user U, and any one of the operating units can be selected. FIG. 4 shows, as an example, a state in which the operation unit 53-3 corresponding to "specify meal start date and time" is selected.

Among the four selection candidates, three of them, "Make it now," "Specify meal start date and time," and "Anniversary/Party" are selection candidates for specifying the recipe search purpose according to user U's activity schedule. It is. On the other hand, "normal" selection candidates are selection candidates for not specifying a search purpose. “Make it now” and “Specify meal start date and time” are, for example, temporal conditions according to user U's activity schedule. “Meal start date and time designation” is a selection candidate for specifying, as a search purpose, to start a meal at the date and time input by the user U in the date and time input section 53-5. “Anniversary/Party” is a selection candidate for specifying a special dish according to the user U's activity schedule, for example, an anniversary such as a birthday, or a party, etc. as a search objective. Here, the special dish is, for example, a dish that looks luxurious or a dish that uses expensive ingredients. A recipe corresponding to a special dish is set in advance to be a special dish.

When the operation unit 54 is operated by the user U and the search purpose setting unit 313 receives a control signal output from the operation reception unit 312 that detects the operation, the search purpose setting unit 313 detects information indicating the selection candidate selected by the input unit 53. . When the detected selection candidate is "specify meal start date and time," the search purpose setting section 313 further detects information indicating the date and time input into the date and time input section 53-5. The search purpose setting unit 313 transmits to the server 200 a search purpose setting instruction signal including content indicating the detected information and the user ID included in the internal terminal information 350.

The cooking condition setting unit 314 receives information indicating cooking conditions specified by the user U, such as the number of stoves and oven ranges owned by the user U, and transmits the received information to the server 200.

Recipe search request section (recipe acquisition section) 315 transmits a recipe search request signal including the user ID included in internal terminal information 350 to server 200 . The recipe search requesting unit 315 receives the recipe search response signal from the server 200, and displays a message on the display screen 301a via the display control unit 311 based on the data included in the received recipe search response signal, for example, as shown in FIG. Displays a summary recipe list display screen 503 shown in FIG. The summary recipe list display screen 503 is, for example, a screen that displays a list of thumbnail images and names of each of a plurality of recipes. Hereinafter, data related to individual recipes displayed on the summary recipe list display screen 503 of FIG. 5 will be referred to as summary recipe data to distinguish it from detailed recipe data to be described later.

The detailed recipe request unit (recipe acquisition unit) 316 is activated, for example, when the user U operates the operation unit 62 corresponding to the image area of “recipe image A001” included in the image of the summary recipe list display screen 503. do. The operation unit 62 is associated with a recipe ID previously assigned to recipe A001. Recipe ID is recipe identification information that can identify each recipe.

For example, when the detailed recipe requesting unit 316 is activated due to an operation on the operating unit 62, the detailed recipe requesting unit 316 retrieves the recipe ID of the recipe A001 associated with the operating unit 62 and the user ID included in the internal information 350. A detailed recipe request signal including the detailed recipe request signal is transmitted to the server 200. The detailed recipe requesting unit 316 receives the detailed recipe response signal from the server 200, and displays the detailed recipe data on the display screen 301a via the display control unit 311, for example, based on the detailed recipe data included in the received detailed recipe search response signal. A detailed recipe display screen 504 shown in FIG. 6 is displayed. The detailed recipe display screen 504 includes information indicating, for example, a thumbnail image of one recipe, a list of ingredients, and a cooking procedure. In this embodiment, the detailed recipe display screen 504 includes an operation unit 63 that includes the character string "Set meal start date and time." The operation unit 63 is associated with the recipe ID of recipe A001. When the operation unit 63 is operated, information regarding time (for example, meal start date and time) can be input. The operation unit 63 is an example of an input unit that accepts time-related information (for example, meal start date and time) in order to associate it with a recipe to be prepared.

The recipe registration unit 317 sets the recipe ID selected by the user U as the registered recipe ID. For example, the recipe registration unit 317 receives a registered recipe ID and a meal start date and time designated by the user U for the registered recipe ID, and receives a recipe registration instruction that includes the received registered recipe ID and information indicating the meal start date and time. Send a signal to server 200.

The information acquisition unit 318 receives and acquires information received from the server 200, such as notification information notifying the start of cooking and time planning information indicating a time plan for the cooking process. The information acquisition unit 318 displays the acquired information on the display screen 301a via the display control unit 311.

The calendar setting unit 319 receives information indicating a specific time range designated by the user U and information indicating the user U's plans for going out, etc., and transmits the received information to the server 200. Here, the time range includes not only a range where the date is indicated by two same times, but also a range where the date is indicated by two different times.

(Server configuration)
The server 200 is configured by one or more server devices (for example, a cloud server). The server 200 includes a communication module (not shown), and is connected to, for example, a network NW. The 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 server 200 is not limited to a cloud server, and may be a computer located at the residence of the user U, or a home router (for example, a wireless router WR).

As shown in FIG. 7, the server 200 includes, for example, a storage unit 201, a clock unit 202, a DB management unit 203, a search purpose acquisition unit 204, a recipe proposal unit 205, a time planning unit 206, a daily time acquisition unit 207, and a notification unit. 208. The clock section 202, the DB management section 203, the search purpose acquisition section 204, the recipe proposal section 205, the time planning section 206, the daily time acquisition section 207, and the notification section 208 are configured using a CPU such as a CPU installed in the server 200, for example. It is a software functional unit realized by executing a program by two or more hardware processors. The functional units included in the server 200 may be provided separately in a plurality of server devices. Further, one or more of the functional units included in the server 200 may be included in the terminal device 300 instead of the server 200.

The storage unit 201 is a hardware function unit, and includes a recipe DB 251, a user information DB 252, a registered recipe DB 253, and a calendar DB 254.

For example, as shown in FIG. 8, the recipe DB 251 stores recipe IDs, recipe names, recipe images, ingredients lists, cooking procedures, cooking process conditions, cooking times, and standby times in association with each other. Hereinafter, data in one row in the recipe DB 251, that is, data associated with one recipe ID, will be referred to as a recipe record. In this application, when the term "recipe" is used, it basically refers to a recipe record, but it may also refer to detailed recipe data or summary recipe data generated from a part of a recipe record.

The “recipe ID” item stores a recipe ID assigned to each recipe record. The "ingredients list" item stores each type of ingredients used in each recipe and the amount of each ingredient. The "cooking procedure" item has sub-items "cooking process content" and "cooking process time." The item "Cooking process content" stores information indicating the content of the recipe for each recipe record, that is, the content of cooking performed for each cooking process. Here, the information indicating the content of cooking includes, in addition to the content indicating specific steps in text, information indicating the type of each cooking process, such as "preparation," "non-heating process," and "heating process." Contains information such as "process". The information indicating the type of cooking process of "heating process" further includes information indicating the difference in cooking equipment used, such as whether the heating process uses a stove or an oven range. The "cooking process time" item stores the cooking time for each cooking process. The "recipe name" and "recipe image" items each store the name of a dish and image data (thumbnail image data) of an example of the dish.

The item "Cooking process conditions" stores information indicating the conditions for how to proceed with cooking in the cooking process shown in the "Cooking process contents" of the "Cooking procedure". For example, the waiting time that exists in the cooking process is stored as information indicating the conditions for how to proceed with the cooking. Here, the waiting time refers to a time during which the user cannot proceed with cooking, such as time for preparing food or fermenting bread dough. In addition, as information indicating the conditions for how to proceed with cooking, for example, in the cooking process shown in the item "Cooking procedure", based on the principle that it is okay to leave time between cooking processes as long as the process order is followed, Information indicating combinations of cooking steps that must be performed consecutively is also stored. Note that when there are no cooking process conditions, such as recipe ID "A021," the item "Cooking process conditions" is left blank.

The "cooking time" item stores the total time for each cooking process shown in the "cooking process time" item of the "cooking procedure". The "waiting time" item stores the total time of the waiting times shown in the "cooking process conditions" item. Note that when there is no waiting time, such as with recipe ID "A021," the "waiting time" item is blank.

For example, as shown in FIG. 9, the user information DB 252 stores information indicating the user's search purpose and information indicating the user's cooking conditions in association with each other for each user ID.

For example, as shown in FIG. 10, the registered recipe DB 253 stores, for each user ID, meal start date and time, registered recipe ID, cooking start date and time (scheduled cooking start date and time), time plan information, and notification date and time (notification schedule). date and time), notification information (notification content), and notification status are stored in association with each other. The meal start date and time is the date and time when the user U starts eating, and is, for example, the date and time specified by the user U. The registered recipe ID is a recipe indicating a dish that the user U plans to eat at the corresponding meal start date and time, and is a recipe ID indicating a recipe selected by the user U. As in the example of the meal start date and time "August 1st 19:00" in FIG. 10, a plurality of recipe IDs indicating a plurality of dishes can be registered in association with one meal start date and time.

The cooking start date and time (scheduled cooking start date and time) is the date and time at which cooking of the recipe with the recipe ID indicated in the corresponding "registered recipe ID" item should start. The time planning information is information indicating the start date and time and end date and time of each cooking process for each registered recipe that the user U cooks.

The notification date and time (scheduled notification date and time) is the date and time to notify the user U that cooking should start, in other words, the date and time to notify the arrival of the cooking start date and time. Announcement information is information that is presented along with the announcement when the announcement is made on the corresponding announcement date and time. Hereinafter, the combination of notification date and time and notification information will also be referred to as notification conditions. In the "notification status" item, "notified" is stored if the notification has already been made, and "not notified" is stored if the notification has not been made yet.

The calendar DB 254 stores calendar information for each user ID, for example. Here, calendar information is information that includes dates from January to December for each year, and information that indicates the user's schedule such as going out is stored in association with a time range. be.

In the server 200, the clock unit 202 is, for example, a clock, and upon receiving a request from another functional unit, outputs time information indicating the time at the time of receiving the request to the requesting functional unit. Hereinafter, the time information output by the timer 202 will be referred to as current time information for convenience of explanation.

The DB management unit 203 performs processing such as recording and changing data in the recipe DB 251, user information DB 252, registered recipe DB 253, and calendar DB 254.

The search purpose acquisition unit 204 acquires the search purpose of a recipe according to the user U's action schedule.
In the present embodiment, the search purpose acquisition unit 204 acquires the search purpose of a recipe according to the user U's action schedule based on the user U's input to the terminal device 300. For example, the search purpose acquisition unit 204 receives a search purpose setting instruction signal from the terminal device 300, and acquires a search purpose for a recipe according to the action schedule of the user U based on the received search purpose setting instruction signal. . When the search purpose acquisition unit 204 acquires the search purpose for a recipe according to the action schedule of the user U, the search purpose acquisition unit 204 records data in the user information DB 252. Note that, as will be explained later in a modification example, the search purpose acquisition unit 204 estimates the user U's action schedule instead of/in addition to the user U's input to the terminal device 300, and makes a guess regarding the user U's action schedule. A recipe search purpose may be obtained based on the results. The search purpose acquisition unit 204 is an example of a “purpose acquisition unit”.

When the search purpose acquisition unit 204 acquires the search purpose of a recipe according to the action schedule of the user U, the recipe suggestion unit 205 selects, for example, the search purpose of the user U from a plurality of recipes registered in advance in the recipe DB 251. One or more recipes are selected and proposed to the user U according to the following. In this application, "proposing a recipe to user U" means, for example, transmitting information indicating the selected recipe to the terminal device 300.

In this embodiment, upon receiving the recipe search request signal from the terminal device 300, the recipe proposal unit 205 generates summary recipe data from the data stored in the recipe DB 251. The recipe proposal unit 205 transmits a recipe search response signal including the generated summary recipe data to the terminal device 300. When receiving the detailed recipe request signal from the terminal device 300, the recipe proposal unit 205 generates detailed recipe data from the data stored in the recipe DB 251. The recipe proposal unit 205 transmits a detailed recipe response signal including the generated detailed recipe data to the terminal device 300.

The time planning unit 206 performs time planning processing on the registered recipe ID newly recorded in the registered recipe DB 253 to generate time planning information. The time planning process will be described in detail later.

The living time acquisition unit 207 acquires information regarding the available cooking time during which the user U can cook. In this embodiment, the living time acquisition unit 207 detects calendar information corresponding to the user ID of the user U from the calendar DB 254, and based on the schedule of the user U indicated in the detected calendar information, the user U does not exist at home. Detect a range of time. The living time acquisition unit 207 calculates the possible cooking time based on the detected range of time when the user U is not present in the house and the sleeping time zone of the user U that is set in advance by the user U. Here, the possible cooking time is the time when the user is present in the house and is not sleeping, and is the time during which the user U can cook if the user U receives some kind of notification. .

When a meal start time is input for search purposes or to associate with a recipe to be cooked, the notification unit 208 provides notification regarding the arrival of the cooking start time calculated backward from the meal start time. For example, when the time planning unit 206 newly generates time planning information, the notification unit 208 calculates the notification date and time for each meal start date and time based on the newly generated time planning information and the available cooking time. , further generates broadcast information. When the notification date and time arrive, the notification unit 208 transmits notification information corresponding to the notification date and time to the information acquisition unit 318. Note that the notification unit 208 inputs the start time or end time of another predetermined action of the user U instead of the meal start date and time (meal start time) for search purposes or to associate with the recipe to be cooked. If so, similar processing is performed based on the input start time or end time, and the above notification information is generated and transmitted. For example, the notification unit 208 calculates the notification date and time based on the cooking process time plan (time plan information) generated by back calculation from the input start time or end time of the action and the available cooking time, and Generate broadcast information.

When a plurality of recipes are registered for one meal, the notification unit 208 suppresses notification regarding the arrival of the cooking start time for all of the plurality of recipes (for example, only once).

The notification unit 208 changes the notification content regarding the arrival of the cooking start time when a plurality of recipes are registered for one meal or when one recipe is registered for one meal. For example, if one recipe is registered for one meal, it will notify you "Let's start cooking XX", but if multiple recipes are registered for one meal, it will simply notify you. It announces, "Let's start cooking." These contents will be described in detail later.

Note that the timekeeping unit 202, DB management unit 203, search purpose acquisition unit 204, recipe proposal unit 205, time planning unit 206, living time acquisition unit 207, and notification unit 208 of the server 200 are realized by software function units. Not limited. Some or all of these functional units may be realized by hardware such as an ASIC (Application Specific Integrated Circuit), a PLD (Programmable Logic Device), or an FPGA (Field Programmable Gate Array), or may be realized by a combination of software and hardware. This may be achieved through collaboration with

The storage unit 310 of the terminal device 300 and the storage unit 201 of the server 200 are, for example, RAM (Random Access Memory), ROM (Read Only Memory), EEPROM (Electrically Erasable Programmable ROM), or SSD (Solid State Drive). This is achieved through a combination.

(Processing by information processing system)
11 and 12 are sequence diagrams showing the overall flow of processing performed by the information processing system 1. In the following, it is assumed that the user U of the terminal device 300 is assigned the user ID "U100". In the following, by a predetermined operation by the user U, the calendar setting unit 319 and the DB management unit 203 change the calendar information corresponding to the user ID "U100" of the calendar DB 254 to include user U's going out within a specific time range, etc. It is assumed that information indicating the schedule of is recorded.

Through a predetermined operation by the user U, the cooking condition setting unit 314 and the DB management unit 203 add information indicating cooking conditions to the “cooking conditions” item of the table corresponding to the user ID “U100” of the user information DB 252. is now recorded. For example, assume that information indicating the cooking conditions of user U shown in FIG. 9 is recorded in the "cooking conditions" item of the table corresponding to the user ID "U100" of the user information DB 252.

First, the search purpose setting section 313 displays the search purpose input screen 502 of FIG. 4 on the display screen 301a via the display control section 311. Here, for example, it is assumed that the user U performs an operation on the operation unit 53-2 corresponding to the selection candidate "Create now". The operation reception unit 312 detects the operation and outputs a control signal corresponding to the detected operation to the search purpose setting unit 313. As a result, the selection candidate "Create now" is selected.

Subsequently, when the operation unit 54 is operated by the user U, the operation reception unit 312 detects the operation and outputs a control signal corresponding to the detected operation to the search purpose setting unit 313. When the search purpose setting unit 313 receives the control signal, it detects information indicating the selection candidate selected by the input unit 53. Here, the search purpose setting section 313 detects information indicating the operation section 53-2. The search purpose setting unit 313 stores in advance an identification signal corresponding to a selection candidate in an internal storage area in association with each of the operation units 53-1 to 53-4. The search purpose setting unit 313 transmits a search purpose setting instruction signal including the identification signal corresponding to the detected selection candidate and the user ID "U100" to the server 200 (S11).

The search purpose acquisition unit 204 receives the search purpose setting instruction signal and selects the table corresponding to the user ID "U100" included in the received search purpose setting instruction signal in the user information DB 252. As shown in FIG. 9, the search purpose acquisition unit 204 records the contents of the selection candidate corresponding to the identification signal included in the search purpose setting instruction signal in the "search purpose" item of the selected table (S12). .

Next, the recipe search request unit 315 transmits a recipe search request signal including the user ID to the server 200 (S13). At this time, when the user U specifies a dish or ingredients, the recipe search request signal includes information indicating the dish or ingredients specified by the user. Upon receiving the recipe search request signal, the recipe proposal unit 205 starts a recipe search processing subroutine shown in FIG. 13 (S14).

(Recipe search processing subroutine)
The recipe proposal unit 205 detects information indicating the search purpose included in the received recipe search request signal from the user information DB 252. Note that when the information indicating the search purpose is "designation of meal start date and time," time information indicating the meal start date and time input by user U is also stored in the "search purpose" item of the user information DB 252. In this case, the recipe proposal unit 205 detects the time information as well as the search purpose of "specify meal start date and time" (Sa1).

The recipe proposal unit 205 determines whether the detected information indicating the search purpose is "normal", "cook now", "designate meal start date and time", or "anniversary/party" (Sa2). When the recipe suggestion unit 205 determines that the information indicating the search purpose is "normal" (Sa2, normal), the recipe suggestion unit 205 selects all recipe IDs (such as dishes or ingredients by user U) in the order stored in the recipe DB 251. If a condition is specified, a recipe ID that satisfies the condition is detected.

The recipe proposal unit 205 generates summary recipe data based on recipe records corresponding to each of the detected recipe IDs. The recipe proposal unit 205 transmits a recipe search response signal including the generated summary recipe data to the terminal device 300 (Sa7).

When the recipe proposal unit 205 determines that the information indicating the search purpose is “make it now” (Sa2, make it now), the recipe suggestion unit 205 selects the “cooking time” and “waiting time” of each recipe data stored in the recipe DB 251. Recipe IDs whose total time is within a predetermined time (for example, 30 minutes) are detected from the recipe DB 251 (Sa4). In the example shown in FIG. 8, for recipe ID "A001", the total time of cooking time and standby time is "20 minutes". For recipe ID "A011", the total time of cooking time and standby time is "26 hours and 30 minutes". Further, for recipe ID "A021", the total time of cooking time and standby time is "50 minutes". Therefore, in this case, the recipe proposal unit 205 detects the recipe ID "A001". The recipe proposal unit 205 performs the process of Sa7 based on the recipe ID detected in the process of Sa4.

Note that when the recipe suggestion unit 205 determines that the information indicating the search purpose is "make it now", instead of the above example, the recipe suggestion unit 205 selects a recipe whose "cooking time" is within a predetermined time (for example, 30 minutes). The recipe ID may be detected from the recipe DB 251, or the recipe ID whose "waiting time" is within a predetermined time (for example, 0 minutes) may be detected from the recipe DB 251. "Waiting time" of 0 minutes or less means that there is no waiting time (that is, there is no preparation that requires waiting time).

When the recipe suggestion unit 205 determines that the information indicating the search purpose is “meal start date and time specification” (Sa2, meal start date and time specification), the recipe suggestion unit 205 acquires current time information from the timer unit 202. The recipe proposal unit 205 calculates the total time by adding up the times shown in the "cooking time" and "standby time" items of each recipe data stored in the recipe DB 251. The recipe proposal unit 205 calculates, as the determination time, a time obtained by adding the calculated total time to the time indicated by the current time information. The recipe proposal unit 205 detects from the recipe DB 251 a recipe ID for which the calculated determination time is a time before the time indicated by the search purpose "meal start date and time specification" and the time information detected in the process of Sa1 (Sa5). . For example, if the time indicated by the current time information is "August 1st 17:00" and the date and time input into the date and time input section 53-5 is "August 1st 18:00", the recipe suggestion section 205 detects recipe IDs “A001” and “A021”. The recipe proposal unit 205 performs the process of Sa7 based on the recipe ID detected in the process of Sa5.

When the recipe suggestion unit 205 determines that the information indicating the search purpose is "anniversary/party" (Sa2, anniversary/party), the recipe suggestion unit 205 detects the recipe ID corresponding to the special dish stored in the recipe DB 251 ( Sa6). The recipe proposal unit 205 performs the process of Sa7 based on the recipe ID detected in the process of Sa6. After the process of Sa7, the recipe proposal unit 205 ends the subroutine.

Here, since the recipe proposal unit 205 detects "make it now" as information indicating the search purpose in the process of Sa1, the process of Sa7 is performed after the process of Sa4 is performed.

Returning to FIG. 11, the recipe proposal unit 205 transmits a recipe search response signal including the summary recipe data generated in the recipe search process to the terminal device 300 (S15).

Recipe search request section 315 receives the recipe search response signal. The recipe search request unit 315 displays the summary recipe list display screen 503 on the display screen 301a via the display control unit 311 based on each piece of summary recipe data included in the received recipe search response signal (S16). . As a result, recipe image data and recipe names included in each piece of summary recipe data are displayed in a list in the format shown in FIG.

The example shown in FIG. 5 is an example where the information indicating the search purpose is "normal", and when the information indicating the search purpose is "make it now", at least the summary recipe data with the recipe ID "A001" is A list display screen 503 of summary recipes including the recipe will be displayed. For example, when the user U operates the operation unit 62 corresponding to the recipe image area with the recipe ID “A001”, the detailed recipe requesting unit 316 requests the recipe ID “A001” (hereinafter, detailed A detailed recipe request signal including the recipe ID of the recipe is generated. The detailed recipe requesting unit 316 transmits the generated detailed recipe request signal to the server 200 (S17).

The recipe proposal unit 205 detects from the recipe DB 251 a recipe record corresponding to the recipe ID "A001" of the detailed recipe included in the received detailed recipe request signal. The recipe proposal unit 205 generates detailed recipe data from the recipe record corresponding to the recipe ID "A001" of the read detailed recipe. The recipe proposal unit 205 transmits a detailed recipe response signal including the generated detailed recipe data to the terminal device 300 (S18).

Detailed recipe requesting section 316 receives the detailed recipe response signal. The detailed recipe request unit 316 displays the detailed recipe display screen 504 on the display screen 301a via the display control unit 311 based on the detailed recipe data of the recipe ID “A001” of the detailed recipe included in the received detailed recipe response signal. is displayed (S19). As a result, the detailed recipe data of the recipe ID "A001" of the detailed recipe is displayed in the format shown in FIG.

Proceeding to FIG. 12, it is assumed that the user U decides to cook the dish with the recipe ID "A001" shown on the detailed recipe display screen 504. In this case, the user U operates the operation unit 63 of the detailed recipe display screen 504. Here, the operation unit 63 is associated with the recipe ID "A001". When the operation reception unit 312 detects the operation of the user U on the operation unit 63, the operation reception unit 312 outputs a control signal including the recipe ID “A001” corresponding to the detected operation to the recipe registration unit 317. The recipe registration unit 317 displays a predetermined meal start date and time setting screen associated with the recipe ID “A001” on the display screen 301a via the display control unit 311.

When the user U inputs information indicating the meal start date and time and performs a completion operation on a predetermined meal start date and time setting screen, the operation reception unit 312 detects the operation. Here, it is assumed that the user U inputs "August 1st 12:00" as information indicating the meal start date and time. When detecting the operation, the operation reception unit 312 receives the input information indicating the meal start date and time "August 1, 12:00" and the recipe ID "A001" associated with the predetermined meal start date and time setting screen. ” is detected. The operation reception unit 312 outputs to the recipe registration unit 317 a control signal including information “August 1, 12:00” indicating the detected meal start date and time and the recipe ID “A001”. The recipe registration unit 317 sets the recipe ID "A001" obtained from the control signal as the registered recipe ID. The recipe registration unit 317 transmits a recipe registration instruction signal including the registered recipe ID "A001" and information indicating the meal start date and time "August 1, 12:00" to the server 200 (S20).

Upon receiving the recipe registration instruction signal, the DB management unit 203 adds information “8” indicating the meal start date and time included in the received recipe registration instruction signal to the “meal start date and time” item of the table corresponding to the user ID “U100”. 12:00 on the first day of the month" and records the registered recipe ID "A001" included in the received recipe registration instruction signal in the "registered recipe ID" field (S21). As a result, the contents of the items "meal start date and time" and "registered recipe ID" in the record in the first line shown in FIG. 10 are recorded in the registered recipe DB 253.

When the process of S21 is completed, the DB management unit 203 outputs to the time planning unit 206 an activation instruction signal including information “August 1, 12:00” indicating the meal start date and time included in the recipe registration instruction signal. When the time planning unit 206 receives the activation instruction signal, it starts a subroutine for time planning processing shown in FIG. 14 (S22).

(Time planning processing subroutine)
When a meal start time is input for the purpose of searching for a recipe or for associating it with a recipe to be cooked, the time planning unit (time plan output unit) 206 provides a time plan for the cooking process calculated backward from the meal start time. generate. Here, a case will be described in which a meal start time is input in order to be associated with a recipe to be cooked. However, in the description of this embodiment, the "meal start time" may be the meal start time input as a recipe search purpose instead of the meal start time input to be associated with the recipe to be cooked. Note that, as described above, the meal start time is an example of "the start time or end time of a user's predetermined action." In place of the meal start time, the time planning section (time plan output section) 206 receives input of the cooking end time, or the start time or end time of a predetermined action of the user, such as going out, going to bed, or starting another task. If so, a time plan for the cooking process is generated by calculating backward from the input start time or end time of the action. Therefore, "meal start time" in the following description may be read as "cooking end date and time,""start time of user's predetermined action," and "end time of user's predetermined action" as appropriate. .

In this embodiment, the time planning unit 206 selects the table corresponding to the user ID "U100" included in the captured activation instruction signal in the registered recipe DB 253. The time planning unit 206 detects a record in which the content of the item "Meal start date and time" of the selected table matches the information "August 1st 12:00" indicating the meal start date and time included in the imported activation instruction signal. do. Here, the time planning unit 206 detects the record in the first line shown in FIG. 10. The time planning unit 206 reads the registered recipe ID "A001" stored in the "registered recipe ID" field of the detected record (Sb1). The time planning unit 206 determines whether the number of read registered recipe IDs is one or multiple (Sb2).

(Processing when there is only one registered recipe ID)
Here, since the registered recipe ID read by the time planning unit 206 is one “A001”, the time planning unit 206 determines that there is one (Sb2, one). The time planning unit 206 detects a recipe record corresponding to the registered recipe ID "A001" from the recipe DB 251. The time planning unit 206 acquires information indicating the cooking procedure stored in the “cooking procedure” item of the detected recipe record and information indicating the cooking process conditions stored in the “cooking process condition” item. (Sb3).

Based on the acquired information indicating the cooking procedure, the information indicating the cooking process conditions, and the information indicating the meal start date and time "August 1st 12:00" included in the acquired activation instruction signal, the time planning unit 206 A time plan for registered recipe "A001" is generated. For example, the time planning unit 206 uses the information "August 1 The start time (scheduled start time) and end time (scheduled end time) for each cooking process are calculated based on 12:00 p.m. The start time and end time of each cooking process calculated by the time planning unit 206 and the information associated with the registered recipe ID "A001" become the time planning information. The time planning unit 206 sets the start time of the first cooking process as the cooking start time (scheduled cooking start time) (Sb4). Here, as shown in FIG. 8, the total time of the cooking time and standby time for the registered recipe ID "A001" is 20 minutes, so the cooking start time for the registered recipe ID "A001" is "August 1, 11 :40".

As shown in FIG. 10, the time planning unit 206 performs the following process on the record detected from the registered recipe DB 253 in the process of Sb1. The time planning unit 206 records the cooking start time "August 1, 11:40" in the "Cooking start time" item, and records the meal start date and time "August 1, 12:40" in the "Time planning information" item. 00'' is recorded (Sb5). The time planning unit 206 ends the subroutine.

(Processing when there are multiple registered recipe IDs)
A description will be given of a process when the number of registered recipe IDs read out by the time planning unit 206 is plural in the process of Sb1. To explain this process, assume the following situation. The registered recipe IDs "A012" and "A051" are already in the "registered recipe ID" field of the record whose "meal start date and time" field is "August 1st 19:00" in the registered recipe DB 253 shown in FIG. Let us assume that the following is stored. In this state, assume that the DB management unit 203 adds and records a new registered recipe ID "A073" in the process of S21 in FIG. In this case, the time planning unit 206 receives an activation instruction signal from the DB management unit 203 including the user ID “U100” and information indicating the meal start date and time “August 1st 19:00”.

The time planning unit 206 reads three registered recipe IDs "A012", "A051", and "A073" in the process of Sb1 in FIG. 14, and determines "multiple" in the process of Sb2 (Sb2, multiple). . The time planning unit 206 detects recipe records corresponding to each of the registered recipe IDs "A012", "A051", and "A073" from the recipe DB 251. The time planning unit 206 acquires information indicating the cooking procedure stored in the "cooking procedure" item and information indicating the cooking process conditions stored in the "cooking process condition" item from each of the detected recipe records. (Sb6).

The time planning unit 206 selects the table corresponding to the user ID "U100" included in the activation instruction signal in the user information DB 252, reads out the cooking conditions stored in the "cooking conditions" item of the selected table, and reads out the cooking conditions stored in the "cooking conditions" item of the selected table. Acquire (Sb7). Here, it is assumed that the time planning unit 206 reads out "stove: 2 pieces" and "microwave oven: 1 piece" shown in FIG. 9 as conditions related to cooking.

The time planning unit 206 creates three registered recipes "A012", "A051", and "A051" as shown in FIG. ”, “A073” is generated. The time planning unit 206 arranges the registered recipes "A012", "A051", and "A073" in ascending order of the cooking time of the heating process using the stove indicated in the information indicating the cooking procedure. Here, for example, it is assumed that the time planning unit 206 arranges the registered recipes "A073", "A051", and "A012" in order from the right side, as shown in the diagram 101 in FIG.

It is assumed that the information indicating the cooking process conditions of each of the registered recipes "A073", "A051", and "A012" does not indicate a condition that the heating process and the non-heating process must be performed consecutively. Furthermore, since user U's time is occupied by work on one non-heating process, it is necessary to prevent non-heating processes from running in parallel. Furthermore, since the information indicating the cooking conditions indicates that there are two stoves, it is necessary to ensure that the number of heating processes that use the stoves in parallel is two or less. Therefore, as shown in the diagram 102 in FIG. 15, the time planning unit 206 separates the cooking process 1, which is a non-heating process, of the registered recipe "A051" from the cooking process 2, which is a heating process. It is moved before the cooking step 1-4 which is the non-heating step of “A073”.

The time planning unit 206 determines the heating process using the stove of the registered recipe "A012" so that the cooking time of the cooking process 2 of the registered recipe "A051" does not overlap so that there are two heating processes that use the stove in parallel. The cooking process 4 is moved. Cooking step 3 of registered recipe "A012" is a heating step using an oven range, and can be performed overlappingly with any cooking steps of other registered recipes "A073" and "A051". Therefore, the time planning unit 206 allocates the cooking time for the cooking process 3 before the cooking process 4 of the registered recipe "A012".

The cooking process 1-2, which is the non-heating process of the last remaining registered recipe "A012", must not overlap with the cooking processes of the other registered recipes "A073" and "A051". Therefore, the time planning unit 206 moves cooking step 1-2, which is a non-heating step, of the registered recipe "A051" before cooking step 1, which is a non-heating step, of the registered recipe "A051". As a result, the order of each cooking process of the registered recipes "A073", "A051", and "A012" is determined, as shown in the diagram 102 in FIG. 15.

The time planning unit 206 calculates the cooking time for each cooking process indicated in the acquired information indicating the cooking procedure and the information "August 1st 19:00" indicating the meal start time included in the activation instruction signal. The start time and end time for each cooking process are calculated. The time planning information includes the start time and end time of each cooking process calculated by the time planning unit 206, and information in which the registered recipe ID corresponding to each cooking process is associated. The time planning unit 206 sets the start time of the first cooking process 1 of the registered recipe "A073", "August 1, 17:10", as the cooking start time of the registered recipe "A073". The time planning unit 206 sets the start time of the first cooking process 1 of the registered recipe "A051", "August 1, 17:00", as the cooking start time of the registered recipe "A051". The time planning unit 206 sets the start time of the first cooking process 1 of the registered recipe "A012", "August 1st 16:30", as the cooking start time of the registered recipe "A012" (Sb8).

In the process of Sb1, the time planning unit 206 performs the following process on the record detected from the registered recipe DB 253. The time planning unit 206 records the cooking start date and time “August 1st 16:30” in the “Cooking start date and time” item corresponding to the registered recipe ID “A012”. The time planning unit 206 records the cooking start date and time “August 1st 17:00” in the “Cooking start date and time” item corresponding to the registered recipe ID “A051”. The time planning unit 206 records the cooking start date and time “August 1st 17:10” in the “Cooking start date and time” item corresponding to the registered recipe ID “A073”. The time planning unit 206 records time planning information corresponding to the meal start date and time "August 1st 19:00" in the "time planning information" item (Sb9). As a result, the items from "meal start date and time" to "time planning information" of the record corresponding to the meal start date and time "August 1 19:00" in the registered recipe DB 253 are in the state shown in FIG. 10. The time planning unit 206 ends the subroutine.

Returning to FIG. 12, the time planning unit 206 outputs the captured activation instruction signal to the notification unit 208. The notification unit 208 outputs an acquisition request signal including the user ID “U100” included in the activation instruction signal to the living time acquisition unit 207. When receiving the acquisition request signal, the living time acquisition unit 207 detects calendar information corresponding to the user ID "U100" included in the received acquisition request signal from the calendar DB 254. The living time acquisition unit 207 calculates the available cooking time from the calendar information corresponding to the detected user ID "U100". The living time acquisition unit 207 outputs an acquisition response signal including the calculated available cooking time to the notification unit 208. The notification unit 208 takes in the acquisition response signal (S23). When the notification unit 208 takes in the acquisition response information, it starts a subroutine of notification condition setting processing shown in FIG. 16 that sets notification date and time as notification conditions and notification information (S24).

(Notification condition setting process)
The notification unit 208 detects, from the registered recipe DB 253, time planning information corresponding to the information indicating the meal start date and time included in the captured activation instruction signal (Sc1).

The notification unit 208 determines whether there is a standby time in the detected time plan information and each standby time is within a predetermined time (Sc2). Here, the predetermined time is preset to a relatively long time such as 12 hours, for example. The reason for setting a relatively long time is that, for example, for a recipe that requires cooking steps such as preparation the day before, it is necessary to set a relatively long time both when the preparation and cooking steps are done the day before and when cooking is done on the day. This is because it is desirable to make a notification.

For example, assume that the predetermined time is 12 hours. In this case, the recipe ID "A011" shown in FIGS. 8 and 10 has a waiting time that is not within the predetermined time of 24 hours. Therefore, in the case of the meal start date and time "August 3rd 19:00" corresponding to the registered recipe ID "A011", the notification unit 208 makes a negative determination in the determination process of Sc2 (Sc2, No). . On the other hand, it is assumed that the notification unit 208 determines that the meal start date and time other than the meal start date and time "August 3rd 19:00" shown in FIG. Yes). In this case, the notification unit 208 sets the earliest cooking start date and time as the notification date and time, and records the notification date and time in the "Notification date and time" item of the corresponding record (Sc3). In the case of the meal start date and time "August 1st 12:00" and "August 2nd 6:00" in the first and third lines of Figure 10, the date and time indicated in the "Cooking start date and time" item becomes the notification date and time.

On the other hand, in the case of the meal start date and time "August 1st 19:00" in the second line of FIG. ” as the notification date and time. By doing this, when there are multiple cooking start dates and times for one meal, the notification will not be made for each of the multiple cooking start dates and times, but once for the earliest cooking start date and time. As a result, the annoyance of the user U can be reduced. Note that if it is possible to suppress notifications for all of the plurality of registered recipe IDs, that is, to suppress notifications for all of them and to suppress the number of notifications, it is possible to reduce the annoyance of the user U. . Therefore, for example, instead of setting only the earliest cooking start date and time as the notification date and time, a portion of a plurality of cooking start dates and times may be selected and each of the selected cooking start dates and times may be set as the notification date and time.

On the other hand, when the determination of Sc2 is "No", the notification unit 208 informs the earliest cooking start date and time and the cooking start date and time after the waiting time exceeding the predetermined time for the process of Sc2 ends. Set as the notification date and time, and record the notification date and time in the "Notification date and time" item of the corresponding record (Sc4). Note that the notification unit 208 detects the cooking start date and time after the waiting time exceeding a predetermined time has ended from the time planning information. In the case of the meal start date and time “August 2nd 19:00” in the fourth line of FIG. For example, assume that "August 3rd 17:00" is detected from the time planning information as the previous cooking start date and time, for example, as the cooking start date and time after the waiting time has ended.

The notification unit 208 determines whether the number of registered recipe IDs corresponding to the set notification date and time is one or multiple (Sc5). Note that when performing the determination process of Sc5 via the process of Sc4, the notification unit 208 performs the determination process of Sc5 for each of the plurality of set notification dates and times.

If the notification unit 208 determines that the number of registered recipe IDs corresponding to the set notification date and time is one (Sc5, one), then in the determination process of Sc5, it is determined that there are multiple set notification dates and times. It is determined whether or not to do so (Sc6). For example, in the case of the meal start dates and times "August 1st 12:00" and "August 2nd 6:00" in the first and third lines of Figure 10, there is only one notification date and time, respectively. Furthermore, only one registered recipe ID "A001" or "A009" exists as a registered recipe.

Therefore, the notification unit 208 determines "one" for the meal start dates and times "August 1st 12:00" and "August 2nd 6:00" in the process of Sc5, and determines "one" in the process of Sc6. Make a “No” decision. In this case, the notification unit 208 generates notification information by combining the registered recipe ID and a predetermined character string "Let's start cooking," and inserts the generated notification information into the corresponding record. It is recorded in the "notification information" item (Sc7). For example, if the meal start date and time in the first line is "August 1st 12:00", the notification unit 208 generates the notification information "Let's start cooking A001". Thereby, the user U can receive notification indicating which recipe to start cooking at the time to start cooking.

On the other hand, in the case of the meal start date and time "August 3rd 19:00" in the fourth line of FIG. 00'' exists, and the registered recipe ID corresponding to each notification date and time is one of ``A011''. Therefore, for the meal start date and time "August 3rd 19:00", the notification unit 208 determines "one" in the process of Sc5, and determines "Yes" in the process of Sc6. In this case, the notification unit 208 detects the cooking process corresponding to each of the two notification dates and times from the time planning information, and detects the type of cooking process corresponding to the detected cooking process from the recipe DB 251. Here, the notification unit 208 detects "preparation" as the type of cooking process for the notification date and time "August 2nd 16:30," and for the notification date and time "August 3rd 17:00," Assume that "non-heating process" is detected as the type of process.

For each notification date and time, the notification unit 208 displays the registered recipe ID corresponding to the notification date and time, the type of cooking process corresponding to the notification date and time, and a predetermined character string "Let's start cooking." The broadcast information is generated by combining the The notification unit 208 records the notification information generated for each notification date and time in the "Notification Information" item of the corresponding record (Sc8). For example, the notification unit 208 generates notification information "Let's start cooking A011 (preparation)" for the notification date and time "August 2nd 16:30", and generates notification information saying "Let's start cooking A011 (preparation)" and :00'', notification information such as ``Let's start cooking A011 (non-heating process)'' is generated. As a result, in the case of a recipe that requires preliminary preparation on the previous day, the user U can be notified twice: at the timing of starting the cooking of the previous day's preparation and at the timing of starting the cooking of the current day. Note that the determination process shown in the process of Sc2 is an example, and even if the waiting time is short, if the user U wants to be notified every time there is a waiting time, the user U may shorten the predetermined time, etc. The determination process may be replaced with an arbitrary determination process so that the number of times the notification is performed is notified.

On the other hand, if the notification unit 208 determines in the determination process of Sc5 that the number of registered recipe IDs corresponding to the notification date and time is plural (Sc5, plural), the notification unit 208 selects a predetermined number without including the registered recipe ID. The character string "Let's start cooking" is used as the notification information. The notification unit 208 records the notification information in the "Notification Information" item of the corresponding record (Sc9). In the case of the meal start date and time "August 1st 19:00" in the second line of FIG. ”, “A073” exist. Therefore, in the process of Sc5, the notification unit 208 determines "multiple" and records the character string "Let's start cooking" in the "Notification information" item. Here, as a comparative example, if you perform the process of Sc7 instead of the process of Sc9, the notification information will be "Let's start cooking A012" corresponding to the registered recipe ID "A012" where cooking starts first. , "A012", "A051", and "A073" are inappropriate as notification information for notifying the start of cooking. Therefore, by employing the process of Sc9, it is possible to prevent the user U from misunderstanding.

The notification unit 208 adjusts the newly recorded notification date and time according to the possible cooking time included in the acquisition response signal acquired in the process of S23 (Sc10), and ends the subroutine. Here, it is assumed that "5:00 to 23:00" from August 1st to August 3rd is shown as the possible cooking time. Regarding the meal start dates and times "August 1st 12:00", "August 1st 19:00", and "August 3rd 19:00" in the 1st, 2nd, and 4th lines of Figure 10, Since the notification date and time is within the range of possible cooking time, the notification unit 208 does not make any adjustment. On the other hand, regarding the meal start date and time "August 2nd 6:00" in the third line of FIG. 10, the notification date and time is "August 2nd 4:00" which is the same as the cooking start date and time. This means that it is outside the cooking time range. Therefore, the notification unit 208 records the latest available cooking time, “23:00, August 1st,” which is a time before the cooking start date and time “August 2nd, 4:00,” in the “Notification date and time” field. . Thereby, the user U can reliably receive notification within the range of available cooking time.

Returning to FIG. 12, the notification unit 208 repeatedly acquires current time information from the clock unit 202 at regular intervals of, for example, several seconds. The notification unit 208 stores a record (hereinafter referred to as a record) in which the “notification status” item in the registered recipe DB 253 is “unreported” and the time indicated in the “notification date and time” item is before the time indicated by the acquired current time information. , the following process is performed on the corresponding record). The notification unit 208 generates a notification instruction signal that includes the user ID corresponding to the corresponding record and notification information stored in the "notification information" item of the corresponding record, and sends the generated notification instruction signal to the network NW. (S25). When the information acquisition unit 318 of the terminal device 300 receives the notification instruction signal from the server 200, it displays notification information included in the notification instruction signal on the display screen 301a via the display control unit 311 (S26). Thereby, the user U receives notification regarding the arrival of the cooking start date and time.

For example, the user U operates the operation unit 52 provided on the home screen 501 in FIG. The acquisition unit 318 is activated. The information acquisition unit 318 transmits a time plan acquisition signal including the user ID "U100" included in the internal terminal information 350 to the server 200 (S31).

When a meal start time is input for the purpose of searching for a recipe or for associating it with a recipe to be cooked, the time planning unit 206 displays on the terminal device 300 a time plan for the cooking process calculated backward from the meal start time. Information to be displayed on the screen 301a is output.

In this embodiment, upon receiving the time plan acquisition signal, the time planning unit 206 selects the table corresponding to the user ID "U100" included in the time plan acquisition signal in the registered recipe DB 253. The time planning unit 206 reads out all the time planning information recorded in the "time planning information" item of the selected table. The time planning unit 206 detects a recipe record corresponding to the recipe ID included in the read time planning information from the recipe DB 251. The time planning unit 206 detects information indicating the type of each cooking process stored in the item ``cooking process content'' of ``cooking procedure'' of the detected recipe record, and stores information indicating the type of each detected cooking process. , associated with information indicating the cooking process included in the time planning information.

The time planning unit 206 generates image data for screen display in which each cooking process is displayed in the form of a timetable, based on time planning information associated with information indicating the type of each cooking process. The time planning unit 206 combines the generated image data and generates a time plan acquisition response signal that includes the combined image data and the user ID "U100" included in the time plan acquisition signal. The time planning unit 206 transmits the generated time plan acquisition response signal to the terminal device 300 (S32).

When the information acquisition unit 318 receives the time plan acquisition response signal, it displays the image data included in the received time plan acquisition response signal on the display screen 301a via the display control unit 311 (S33). As a result, for example, a time plan display screen 505 shown in FIG. 17 is displayed on the display screen 301a. The time plan display screen 505 in FIG. 17 shows that the meal start date and time is 19:00 on "August 16th", and in the previous stage at 18:00, cooking other than the preparation for the registered recipe ID "A081" is shown. It is shown that the preparation for the registered recipe ID "A081" will be done at 17:00, and furthermore, the preparation for the registered recipe ID "A081" will be done at 16:00 on the previous day "August 15th". It is shown that one more preliminary preparation is to be made.

As a result, for example, the user U knows that it is necessary to make preparations on the day before the meal and on the day of the meal, and that the cooking process starts at 18:00 after the preparation on the day of the meal. You can see that you have about 30 minutes of free time until then. Thereby, for example, the user U can make plans in advance to do other things (such as laundry) during free time. Further, it is assumed that the user U operates an image formed as the operation unit 71, which is an image of cooking at around 18:00 on “August 16th”. When the operation reception unit 312 detects the operation, it outputs a control signal corresponding to the operation to the information acquisition unit 318. The information acquisition unit 318 enlarges and displays a plurality of cooking steps other than preparation on the display screen 301a via the display control unit 311, and displays the start time and end time of each of the plurality of cooking steps. Thereby, the user U can grasp the details of the plurality of cooking processes to be performed around 18:00 on "August 16th".

Note that on the time plan display screen 505 in FIG. 17, only the time plans for August 15th and August 16th are displayed. In a state where the time plan display screen 505 is displayed on the display screen 301a, when the user U performs a scrolling operation on the display screen 301a, time plans for other dates are displayed. Moreover, the timing to perform the process of S31 can be performed at any timing as long as the time planning process of S22 has been completed.

(advantage)
In the above embodiment, the server 200 selects one of the following to search for a recipe according to the user U's purpose of action: "make it now", "designate meal start date and time", or "anniversary/party". A recipe corresponding to the search purpose selected by the user U is searched and provided to the user U. Therefore, in this embodiment, the user U can save the effort of combining keywords for searching, and simply select the search purpose to create a recipe appropriate for the user U's behavioral purpose. Obtainable.

When cooking a dish using a recipe obtained through such a search, if there is a time difference between the time of the search and the time of cooking, it is inefficient to search again at the time of cooking. Therefore, in this embodiment, the time when the user starts eating the dish indicated by the recipe, that is, the meal start date and time, can be registered in association with the recipe obtained through the search. Thereby, in this embodiment, the time to start cooking is calculated by backward calculation in time for the meal start date and time, and the user U is notified that cooking will start at the calculated time. Therefore, for example, it is possible to prevent a situation in which food cannot be served on the meal start date and time due to insufficient preparation. This makes it possible to improve convenience.

(First modification)
In the above embodiment, the summary recipe list display screen 503 of FIG. 5 is displayed on the display screen 301a from the home screen 501 of FIG. 3, via the search purpose input screen 502 of FIG. 4. In the first modification, when the operation unit 51 is operated by the user U on the home screen 501 in FIG. 503a may be displayed. In this case, the recipe search request section 315 includes the search purpose setting section 313.

Further, the search purpose setting unit 313 may be activated as follows. For example, when the operation unit 81 for settings (for selecting setting items) shown in FIGS. 5 and 6 is displayed on the display screen 301a, when the user U operates the operation unit 81, the setting screen is displayed. It is displayed on the display screen 301a. When the user U performs a predetermined operation on the setting screen, the search purpose input screen 502 of FIG. 4 may be displayed on the display screen 301a. Here, the predetermined operation is, for example, when a plurality of options for selecting setting items are shown on a setting screen, and selecting an option for displaying the input section 53 from among the plurality of options. It's a manipulation.

The search purpose setting unit 313 may display the search purpose input screen 502 of FIG. 4 on the display screen 301a before the summary recipe list display screen 503. The search purpose setting section 313 may display the input section 53 in a dialog box-like format on the summary recipe list display screen 503. The search purpose setting section 313 may display the input section 53 as a floating operation section so that the input section 53 remains at a fixed position on the display screen 301a even when the summary recipe list display screen 503 is scrolled. .

(Second modification)
In the second modified example, the display control unit 311 displays search objectives according to user U's behavior as part of an input screen 509 (see FIG. 19) for accepting recipe search conditions including ingredients or types of dishes. An input section 53a for accepting input is displayed. Note that instead of displaying the input section 53a as part of the input screen 509, the display control section 311 may display the input section 53a superimposed on the input screen 509 (for example, in a floating state).

For example, when the user U operates the search window-shaped operation unit 61 while the summary recipe list display screen 503 of FIG. 5 is displayed on the display screen 301a, the recipe search request unit 315 displays the recipe search screen. It is displayed on the screen 301a. Here, the recipe search screen is an input screen for accepting recipe search conditions. In this case, the recipe search requesting unit 315 may display a recipe search screen 506 shown in FIG. 19 on the display screen 301a. The recipe search screen 506 in FIG. 19 includes, for example, an input section 53a obtained by removing the operation section 54 from the input section 53 shown in FIG. The user U selects a desired selection candidate related to the search purpose according to the user U's action schedule in the input unit 53a, and then selects an arbitrary option indicating the type of dish or the type of ingredients in the area 61a of the search window, for example. A predetermined search start operation is performed by inputting a character string or by selecting a search item indicating the type of dish or the type of ingredients shown in the range shown by reference numeral 65. Thereby, the recipe search requesting unit 315 can generate a search condition by further including a search purpose according to the action schedule of the user U in the search condition formed by an arbitrary character string or search item. .

(Third modification)
In the third modification, the cooking condition setting unit 314 provides information regarding the cooking skill of the user U, such as information such as "beginner", "average", and "expert" that directly indicates the skill, and Information indicating cooking speed such as "slow", "normal", and "fast" may be accepted. In this case, the cooking condition setting section 314 may correspond to an example of a "skill acquisition section (skill information acquisition section)."

The cooking condition setting unit 314 records the received information indicating the cooking skill of the user U in the "skill" item provided in the table corresponding to the user U of the user information DB 252. When the recipe proposal unit 205 uses the cooking time of the recipe DB 251 in the recipe search process shown in FIG. 13, and when the time planning unit 206 uses the cooking time of the recipe DB 251 in the time planning process shown in FIG. The cooking time may be changed as follows based on the information indicating the cooking skill of the person. For example, the recipe proposal unit 205 and the time planning unit 206 set the time obtained by multiplying the cooking time by a predetermined coefficient according to information indicating cooking skill as the cooking time. For example, if the information indicating the cooking skill is "beginner" or "slow", the information indicating the cooking skill is multiplied by a coefficient that increases the cooking time (a coefficient greater than 1), and the information indicating the cooking skill is "expert" or "slow". If the cooking time is "fast", multiply by a coefficient that shortens the cooking time (a coefficient smaller than 1), and if the information indicating the cooking skill is "fair", multiply by a coefficient (for example, 1) that does not change the cooking time. It's okay. Thereby, the cooking time can be changed according to the cooking skill of the user U, and it becomes possible to search for a more accurate (flexible) recipe and plan time for cooking. Note that the search purpose setting unit (skill acquisition unit) 313 displays selection candidates of information indicating skills on the search purpose input screen 502 shown in FIG. You may also acquire information indicating.

(Fourth modification)
In the above embodiment, the search purpose acquisition unit 204 of the server 200 acquires information indicating the search purpose selected by the user U via the search purpose setting unit 313 of the terminal device 300. In the fourth modification, the search purpose acquisition unit 204 may acquire information indicating the search purpose as follows. For example, a home appliance owned by the user U (for example, a cooking home appliance such as an oven range) is connected to the network NW. The terminal device 300 and the home appliance transmit operation information indicating the operation received from the user U to the server 200. This operation information may also include, for example, operation information indicating that the terminal device 300 operates the cooking home appliance via the server 200. Therefore, these pieces of operation information indicate the user U's action history. The server 200 stores the received operation information in the storage unit 201 in the chronological order in which it was received. In this state, the search purpose acquisition unit 204 may estimate a search purpose according to the action schedule of the user U based on the operation information, and acquire the estimated search purpose. For example, it is assumed that the search purpose acquisition unit 204 detects that the user U searches for a recipe on a weekday evening and then immediately operates a cooking appliance with a frequency that is equal to or higher than a threshold. In this case, the search purpose acquisition unit 204 can infer that the search purpose when the user U searches for a recipe on a weekday evening is a search purpose corresponding to the above-mentioned "make it now".

(Fifth modification)
In the fifth modified example, the search purpose input screen 502 in FIG. You may also perform a process like this. The user U selects the option "Specify cooking start date and time" and inputs the cooking start date and time into the date and time input section. In this case, the recipe proposal unit 205 of the server 200 determines in the process Sa2 of FIG. 13 that the information indicating the search purpose is "cooking start date and time." The recipe proposal unit 205 calculates the total time by adding up the times indicated in the "cooking time" and "standby time" items of each recipe data stored in the recipe DB 251. The recipe proposal unit 205 retrieves from the recipe DB 251 a recipe ID for which the time obtained by adding the total time to the cooking start date and time is within the date indicated by the "month" and "day" parts included in the cooking start date and time. To detect. After that, the process of Sa7 is performed. As a result, for example, recipes that have a long waiting time and whose cooking is not completed on the same day when cooking is started on the cooking start date and time are excluded. Therefore, the user U can obtain a recipe that starts cooking at the cooking start date and time and completes the cooking on that day.

(Sixth variation)
In the sixth modification, the search purpose input screen 502 in FIG. 4 is further provided with a selection item "Specify cooking date", and a date input section for inputting the date is also provided, and the following processing is performed. Good too. The user U selects the option "Specify cooking date" and inputs a date indicating the cooking date into the date input section. In this case, the recipe proposal unit 205 of the server 200 determines that the information indicating the search purpose is "cooking date" in the process of Sa2 in FIG. The recipe proposal unit 205 acquires current time information from the timekeeping unit 202. The recipe proposal unit 205 calculates the total time by adding up the times indicated in the "cooking time" and "standby time" items of each recipe data stored in the recipe DB 251. The recipe proposal unit 205 detects from the recipe DB 251 a recipe ID for which the time obtained by adding the total time to the time indicated by the current time information is within the cooking date. After that, the process of Sa7 is performed. As a result, for example, recipes that have a long waiting time and whose cooking is not completed on the cooking day are excluded. Therefore, the user U can obtain, as a search result, a recipe whose cooking can be completed on the day set as the cooking date.

(Seventh modification)
In the above embodiment, when multiple recipes are registered for one meal start date and time, they are registered one at a time. Therefore, each time one recipe is registered, time planning section 206 and notification section 208 perform time planning processing and notification condition setting processing, respectively. In the seventh modification, the recipe registration unit 317 registers a plurality of recipes in a group called ``Dinner'', associates one meal start date and time with the group ``Dinner'', and then registers the recipes via the DB management unit 203. It is recorded in the registered recipe DB 253 of the server 200. As a result, in the registered recipe DB 253, multiple recipes are recorded at once for one meal start date and time, so the time planning section 206 and the notification section 208 can perform time planning only once for one meal start date and time. All you need to do is perform the processing and notification condition setting process. Therefore, the processing load on the server 200 can be reduced.

(Other variations)
In the above embodiment, the time planning unit 206 does not perform the time planning process of S22 in FIG. ”, “A051”, and “A073”, the notification may be made only for the registered recipe ID “A073” which has the longest cooking time. This reduces the number of notifications, so it is possible to reduce user U's annoyance.

In the above embodiment, when "make it now" is selected as the search purpose, the recipe proposal unit 205 performs Sa4 processing using a predetermined time period in the recipe search process shown in FIG. 13. . On the other hand, for example, on the search purpose input screen 502 in FIG. The time input to the predetermined time input section may be used as the predetermined time in the process of Sa4.

In the above embodiment, the user U can be notified by the input operation on the date and time input section 53-5 of the search purpose input screen 502 in FIG. The user then enters the meal start date and time. On the other hand, instead of the meal start date and time, the cooking end date and time may be input. In this case, the search purpose input screen 502 in FIG. 4 displays "Specify cooking end date and time" instead of "Specify meal start date and time," and the text "Set cooking end date and time" is displayed on the operation unit 63 in FIG. columns will be included. In the case of the cooking end start date and time, in the process of Sa5 in FIG. 13 and the process of S20 to S24 in FIG. 12, the process is performed in which the "meal start date and time" is read as the "cooking end date and time".

According to at least one embodiment described above, the information processing system can provide a recipe appropriate for the user's behavioral purpose by acquiring the recipe search purpose according to the user's behavioral purpose. . Thereby, convenience can be improved.

Although several embodiments of the invention have been described, these embodiments are presented by way of example and are not intended to limit the scope of the invention. These embodiments can be implemented in various other forms, and various omissions, substitutions, and changes can be made without departing from the gist of the invention. These embodiments and their modifications are included within the scope and gist of the invention as well as within the scope of the invention described in the claims and its equivalents.

DESCRIPTION OF SYMBOLS 1... Information processing system, 200... Server, 201... Storage unit, 202... Time measurement unit, 203... DB management unit, 204... Search purpose acquisition unit, 205... Recipe proposal unit, 206... Time planning unit, 207... Life time acquisition unit Section, 208...Notification section, 300...Terminal device, 310...Storage section, 311...Display control section, 312...Operation reception section, 313...Search purpose setting section, 314...Cooking condition setting section, 315...Recipe search request section, 316... Detailed recipe request section, 317... Recipe registration section, 318... Information acquisition section, 319... Calendar setting section

Claims (17)

a purpose acquisition unit that acquires a recipe search purpose according to the user's action schedule;
a recipe proposal unit that proposes one or more recipes based on the search purpose acquired by the purpose acquisition unit;
An information processing system equipped with The search purpose includes temporal conditions according to the user's action schedule,
The information processing system according to claim 1. further comprising a display control unit that displays on a display screen an input unit for accepting input of the search purpose;
The information processing system according to claim 1. The display control unit displays the input unit as part of an input screen for accepting recipe search conditions including types of ingredients or dishes, or in a manner overlapping with the input screen.
The information processing system according to claim 3. The input unit is capable of accepting input regarding the scheduled cooking date.
The information processing system according to claim 3. The input unit is capable of accepting input regarding a cooking start time, a cooking end time, or a meal start time.
The information processing system according to claim 3. The purpose acquisition unit estimates the user's schedule based on the user's action history, and acquires the search purpose based on the guessed result.
The information processing system according to claim 1. further comprising a notification unit that notifies the user,
When the start time or end time of a predetermined action of the user is input as the search purpose or to associate with the recipe to be prepared, the notification unit calculates the time from the start time or the end time. Announcement of the arrival of cooking start time,
The information processing system according to claim 1. When a plurality of recipes are registered for one meal, the notification unit suppresses notification regarding the arrival of the cooking start time for all of the plurality of recipes.
The information processing system according to claim 8. The notification unit changes the notification content regarding the arrival of the cooking start time when a plurality of recipes are registered for one meal, or when one recipe is registered for one meal.
The information processing system according to claim 8. further comprising a living time acquisition unit that acquires information regarding cooking available time during which the user can cook;
The notification unit provides notification regarding the arrival of the cooking start time according to the cooking available time of the user.
The information processing system according to claim 8. When the start time or end time of a predetermined action of the user is input as the search purpose or to associate with the recipe to be cooked, the time plan of the cooking process calculated backward from the start time or end time. further comprising a time planning output unit that outputs information for displaying on the display screen;
The information processing system according to claim 1. further comprising a skill acquisition unit that acquires information regarding the cooking skill of the user,
The recipe suggestion unit proposes the one or more recipes based on the search purpose and the information regarding the skill.
The information processing system according to claim 1. The computer is
Obtain the recipe search purpose according to the user's action schedule,
Suggesting one or more recipes based on the obtained search purpose;
Information processing methods that include to the computer,
a recipe acquisition unit that acquires one or more recipes according to the user's action schedule;
a display control unit that displays the one or more recipes acquired by the recipe acquisition unit on a display screen;
A program that makes this possible. The display control unit displays on the display screen an input unit for receiving an input of a recipe search purpose according to the user's action schedule.
The program according to claim 15. When the start time or end time of the predetermined action of the user is input, the display control unit causes the display screen to display a notification regarding the arrival of a cooking start time calculated backward from the start time or end time.
The program according to claim 15.

Images