JP7329479B2 - heating cooking system - Google Patents

Description

The technology disclosed in this specification relates to a cooking system.

Patent Literature 1 discloses a cooking system including one cooker, a plurality of terminal devices, and a server. The server includes a server-side memory that associates and stores cooking action information generated by the heating cooker and action identification information for identifying the cooking action information. The first terminal device sends a first data request to the server. The server transmits the first cooking operation information to the terminal device when receiving the first data request from the first terminal device.

JP 2007-107766 A

In the heat cooking system of Patent Document 1, a heat cooking system including one heat cooker is considered, but a heat cooking system including a plurality of heat cookers is not considered at all. When the cooking system includes a plurality of cookers, cooking operation information generated by each of the cookers is stored in the server-side memory. In a situation where cooking operation information generated by a plurality of cookers is stored in a server-side memory, among a plurality of users using a first cooker among the plurality of cookers, There is a demand for a technique that can share the first action identification information that is stored and that corresponds to the first cooker.

In this specification, a plurality of users who use the first heating cooker can share the first operation identification information stored in the server and corresponding to the first heating cooker. Provide a cooking system.

A cooking system disclosed by this specification includes a plurality of cooking devices, a plurality of terminal devices, and a server. The server provides, for each of the plurality of cooking devices, device identification information that identifies the cooking device, cooking operation information related to the operation of the cooking device and generated by the cooking device, and A server-side memory that associates and stores action identification information for identifying cooking action information is provided. A first terminal device among the plurality of terminal devices sends a first data request including first device identification information for identifying a first cooking device among the plurality of cooking devices to the server. and, when receiving the first data request from the first terminal device, the server stores, in the server-side memory, correspondence to the first device identification information in the first data request. specifying the attached first cooking operation information and first operation identification information, and transmitting a first data list including said first cooking operation information and said first operation identification information to said first Send to the terminal device. A second terminal device different from the first terminal device transmits a second data request including the first device identification information to the server, and the server transmits the second data request from the second terminal device to the second data request. 2 data request, the first cooking operation information and the first cooking operation information associated with the first appliance identification information in the second data request are stored in the server-side memory. action identification information, and transmits a second data list including the first cooking action information and the first action identification information to the second terminal device.

According to the above configuration, when receiving the first data request from the first terminal device, the server performs the first cooking operation using the first device identification information included in the first data request. The information and the first action identification information are identified, and a first data list including the first cooking action information and the first action identification information is transmitted to the first terminal device. In this case, the user of the first terminal device designates the first operation identification information after the first terminal device receives the first data list from the server, thereby setting the first heating cooker to the first 1 can be executed according to the cooking operation information. Further, when the server receives the second data request from the second terminal device, the server uses the first device identification information included in the second data request to generate the first cooking operation information and the first data request. and transmits a second data list including the first cooking action information and the first action identification information to the second terminal device. In this case, the user of the second terminal device designates the first operation identification information after the second terminal device receives the second data list from the server, thereby setting the first heating cooker to the second data list. 1 can be executed according to the cooking operation information. Therefore, among a plurality of users who use the first cooking device (that is, a user who uses the first terminal device and a user who uses the second terminal device), the first can share the first action identification information corresponding to the cooking device.

After receiving the first cooking action information from the first cooking device, the first terminal device performs an operation for requesting transmission of the first cooking action information and the first device identification information. a registration instruction including the first cooking operation information and the first device identification information is transmitted to the server only when a first predetermined operation is accepted, and the server receives the first terminal device generates the first action identification information, and associates the first appliance identification information, the first cooking action information, and the first action identification information when the registration instruction is received from may be stored in the server-side memory. After receiving the first data list from the server, the first terminal device performs a second operation for changing the contents of the first cooking operation information in the first data list. Only when a predetermined operation is accepted, the first cooking operation information is changed to specific cooking operation information, and a change instruction including the specific cooking operation information and the first operation identification information is transmitted to the server. and, when receiving the change instruction from the first terminal device, the server updates the first cooking action information stored in association with the first action identification information in the server-side memory. It may be changed to the specific cooking operation information.

The server can communicate with multiple terminal devices. Therefore, frequent communication between the server and a plurality of terminal devices increases the processing load on the server. According to the above configuration, the first terminal device transmits the registration instruction to the server only when accepting the first predetermined operation after receiving the first cooking operation information from the first cooking device, After receiving the first data list from the server, the change instruction is transmitted to the server only when accepting the second predetermined operation. Therefore, for example, the processing load on the server can be reduced compared to a configuration in which an instruction including cooking operation information is transmitted to the server at each predetermined timing.

When the first terminal device accepts a third predetermined operation that is an operation for starting a specific application installed in the first terminal device, or accepts the third predetermined operation and The first data request may be transmitted to the server only when a fourth predetermined operation, which is an operation for requesting transmission of one data request, is received.

According to the above configuration, the first terminal device transmits the first data request to the server only when accepting the third predetermined operation or accepting the third and fourth predetermined operations. Therefore, for example, the processing load on the server can be reduced compared to a configuration in which the first data request is sent to the server at predetermined timings.

The first terminal device may include a terminal-side memory that stores, as the final communication information, device identification information for identifying the heating cooker with which communication was last executed among the plurality of heating cookers. The first terminal device may transmit the first data request including the first device identification information to the server when the first device identification information is stored as the final communication information in the terminal-side memory. .

The first terminal device can communicate with a plurality of cooking appliances. In such a situation, there is a high possibility that the action identification information desired by the user is the action identification information corresponding to the heating cooker with which communication was last performed. According to the above configuration, the first terminal device transmits to the server the first data request including the first device identification information stored as the final communication information in the terminal-side memory. Therefore, the first terminal device can receive the first action identification information desired by the user from the server.

The first terminal device makes a third data request including first device identification information and second device identification information for identifying a second cooking device different from the first cooking device. can be sent to the server. When the server receives the third data request from the first terminal device, the server stores the first cooking action information and the first action identification associated with the first device identification information in the server-side memory. and identifying the second cooking operation information associated with the second device identification information in the server-side memory when receiving the third data request from the first terminal device. , the second cooking operation information is associated with the first appliance identification information and the specific operation identification information different from the first operation identification information, and stored in the server-side memory, and the first cooking operation is performed. A third data list including the information and the first action identification information and including the second cooking action information and the specific action identification information may be sent to the first terminal device.

According to the above configuration, the first terminal device receives the second cooking action information and the specific action identification information generated by the second cooking device. Therefore, the user of the first terminal device can cause the first cooking device to perform an operation according to the second cooking operation information by designating specific operation identification information.

Also, the first action identification information and the action identification information associated with the second cooking action information (hereinafter referred to as "second action identification information") may be the same. Even if the first action identification information and the second action identification information are the same, the server identifies the first action identification information and the second action identification information based on the device identification information associated with the action identification information. 2 motion identification information. On the other hand, when the first action identification information and the second action identification information are the same, the user of the first terminal device cannot distinguish between the first action identification information and the second action identification information. According to the above configuration, the server stores the second cooking action information in association with the specific action identification information different from the first action identification information, and transmits the specific action identification information to the first terminal device. Send. Therefore, the user of the first terminal device can distinguish between the first action identification information and the specific action identification information. As a result, the user can appropriately select the action identification information.

When the server receives the first data request from the first terminal device, the server stores, in the server-side memory, the first cooking operation associated with the first appliance identification information in the first data request. The information and the operation identification information are specified, and are associated in the server-side memory with the third device identification information that identifies the third heating cooker that is the same model as the first heating cooker. specifying third cooking action information and third action identification information, including the first cooking action information and the first action identification information, and the third cooking action information and the third action identification information; may be transmitted to the first terminal device.

If the two cookers have the same model, the cooking operation information generated by one cooker can be used by the other cooker. According to the above configuration, when the server receives the first data request from the first terminal device, the server identifies the third cooker that is the same model as the first cooker. to the first terminal device, the first data list including the third cooking operation information associated with the device identification information; Therefore, the cooking operation information generated by each cooking device can be shared among users who use cooking devices with the same model.

The first cooking device may include a device-side memory that associates and stores the first cooking action information and the first action identification information.

For example, when the first terminal device is lost, the operation according to the first cooking operation information can be performed by operating the first cooking device and designating the first operation identification information. It is desirable that the heating cooker can be made to perform. However, generally, the storage capacity of the device-side memory provided in the first cooking device is smaller than the storage capacity of the server-side memory provided in the server. Therefore, it is desirable that the amount of information stored in the heating cooker is as small as possible. According to the above configuration, the amount of information to be stored in the device-side memory is reduced compared to the case where the device-side memory stores the first device identification information, the first cooking operation information, and the first operation identification information. can be reduced. Further, the user of the first terminal device operates the first heating cooker and designates the first action identification information to perform the first cooking operation according to the first cooking action information. can be executed by the device. Therefore, user convenience can be improved.

It is a figure which shows the structure of the heat cooking system which concerns on 1st Example. It is a figure which shows each table based on 1st Example and 2nd Example. FIG. 10 is a sequence diagram of a first registration process according to the first embodiment; FIG. 10 is a sequence diagram of an editing process according to the first embodiment; FIG. 4 is a sequence diagram of a first sharing process according to the first embodiment; FIG. FIG. 11 is a sequence diagram of a second registration process according to the first embodiment; FIG. 11 is a sequence diagram of a second sharing process according to the first embodiment; FIG. 11 is a sequence diagram of a third sharing process according to the first embodiment; FIG. 14 is a sequence diagram of a fourth sharing process according to the second embodiment;

(First embodiment)
(Configuration of cooking system 2)
As shown in FIG. 1 , the heat cooking system 2 includes a plurality of heat cookers 100 and 200, a plurality of terminal devices 300, 400 and 500, and a server 600. First cooker 100 , first terminal device 300 , and second terminal device 400 are devices mainly used in house 10 . The first heating cooker 100, the first terminal device 300, and the second terminal device 400 are connected via Bluetooth (hereinafter referred to as "BT") communication according to the Bluetooth (registered trademark) system. can communicate with each other. Also, the first terminal device 300 and the second terminal device 400 can communicate with the server 600 via the Internet 4 . The second cooking device 200 and the third terminal device 500 are devices mainly used in the house 20 . The second cooking device 200 and the third terminal device 500 can communicate with each other via BT communication. The third terminal device 500 can communicate with the server 600 via the Internet 4 .

(Configuration of first cooking device 100 and second cooking device 200)
The first heating cooker 100 includes a stove burner 112, an operation unit 114, a display unit 116, a BT interface (hereinafter referred to as "I/F") 118, a control unit 130, and a device-side memory. 132 and. A device ID “ck1” for identifying the first cooking device 100 is assigned to the first cooking device 100 .

The stove burner 112 is a burner for heating an object to be heated (for example, a cooking container). A gas supply path (not shown) is connected to the stove burner 112 . The gas supply path is provided with a stove adjustment valve (not shown) for adjusting the amount of gas supplied to the stove burner 112 . The stove burner 112 is ignited by operating an igniter (not shown) while gas is being supplied to the stove burner 112 . For example, the first cooking device 100 has three stove burners 112 .

The operation unit 114 is an operation unit for igniting and extinguishing the stove burner 112 and adjusting the heating amount. The display unit 116 is a display for displaying various information. The display unit 116 may function as a so-called touch panel (that is, an operation unit). The BTI/F 118 is a communication interface for performing BT communication with an external device (eg, first terminal device 300).

The control unit 130 controls the operation of the first heating cooker 100 according to a program (not shown) stored in a device-side memory 132 configured by a volatile memory, a nonvolatile memory, or the like. A device table 134 is stored in the device-side memory 132 .

The stove burner 212, the operation unit 214, the display unit 216, the BTI/F 218, the control unit 230, and the device-side memory 232 of the second cooking device 200 are the stove burner 112 and the operation unit of the first cooking device 100, respectively. 114 , display unit 116 , BTI/F 118 , control unit 130 , device-side memory 132 . A device table 234 is stored in the device-side memory 232 . A device ID “ck2” is assigned to the second cooking device 200 .

(Configuration of first terminal device 300, second terminal device 400, and third terminal device 500)
The first terminal device 300 is, for example, a portable terminal device such as a smart phone or a tablet terminal. The first terminal device 300 includes a display operation section 312 , a communication I/F 314 , a control section 330 and a terminal side memory 332 .

The display operation unit 312 functions as a touch panel. The display operation unit 312 can display various information. Further, the display operation unit 312 can accept various operations. Communication I/F 314 is an interface for executing BT communication and an interface for executing wireless communication according to the Wi-Fi (registered trademark) system.

The control unit 330 controls the operation of the first terminal device 300 according to a program (not shown) stored in a terminal-side memory 332 configured by a volatile memory, a non-volatile memory, or the like. A terminal-side memory 332 stores a cooking application (hereinafter simply referred to as an “application”) 334 and a terminal table 336 . The application 334 is an application provided by a plurality of cookers 100, 200 vendors.

The second terminal device 400 has the same structure as the first terminal device 300 except that an application 434 and a terminal table 436 are stored. Also, the third terminal device 500 has the same structure as the first terminal device 300 except that an application 534 and a terminal table 536 are stored. Note that the applications 334, 434, and 534 are the same application.

(Configuration of server 600)
The server 600 is a server provided on the Internet 4 by the vendors of the cooking appliances 100 and 200 . The server 600 is a server that manages information related to the operations of the plurality of cookers 100 and 200 . Server 600 includes communication I/F 614 , control unit 630 , and server-side memory 632 . A communication I/F 614 is an interface for performing wireless communication according to the Wi-Fi system.

The control unit 630 controls the operation of the server 600 according to a program (not shown) stored in a server-side memory 632 configured by volatile memory, non-volatile memory, or the like. A server table 634 is stored in the server-side memory 632 .

(Description of each table 134, 234, 336, 436, 536, 634)
Referring to FIG. 2 , equipment table 134 of first cooking device 100 , equipment table 234 of second cooking device 200 , terminal table 336 of first terminal device 300 , terminal of second terminal device 400 The table 436, the terminal table 536 of the third terminal device 500, and the server table 634 of the server 600 will be described.

Server table 634 stores one or more pieces of server-side information (eg, SI1, SI2, SI3). The server-side information includes management IDs, device IDs, recipe data, and recipe IDs. A management ID is information generated by the server 600 and is unique information. Recipe data is data indicating automatic cooking, and is data generated by heat cookers 100 and 200 . The recipe ID is information generated by the server 600 and is information for identifying recipe data. A recipe ID is unique information among the same device IDs. That is, when device IDs are different, the same recipe ID can be assigned to different recipe data.

The device tables 134 and 234 store one or more pieces of device-side information (eg, AI1, AI2, AI11). The device-side information includes recipe data and a recipe ID.

Terminal tables 336, 436, and 536 store one or more pieces of terminal-side information (for example, TI1, TI2, and TI11). The terminal-side information includes a management ID, recipe data, and a recipe ID.

(First registration process; Fig. 3)
A first registration process for registering recipe data RD1 generated by first cooker 100 in server table 634 of server 600 will be described with reference to FIG. In the initial state of FIG. 3 , a BT connection for executing BT communication is established between the first cooker 100 and the first terminal device 300 . Therefore, the terminal-side memory 332 of the first terminal device 300 stores the device ID "ck1" of the first cooking device 100 as the final communication information "ck1" indicating the last communication partner.

When the first terminal device 300 receives an operation for activating the application 334 (hereinafter referred to as "application activation operation") at T10, it activates the application 334, and displays an operation screen at T12. . The operation screen is a screen for accepting recipe data generation, recipe data editing, updating of the terminal table 336, and the like. At T14, first terminal device 300 receives a generation operation requesting generation of recipe data, and at T16, transmits a generation instruction to first cooker 100. FIG.

The first cooker 100 receives the generation instruction from the first terminal device 300 at T16, receives the ignition operation for igniting the stove burner 112 at T20, and starts storing the cooking process at T22. . The first heating cooker 100 receives an operation to change the heating power from "medium" to "low" at T24, 10 minutes after T20, and extinguishes the stove burner 112 at T26, 5 minutes after T24. When the operation is accepted, the stove burner 112 is extinguished, and the storage of the cooking process ends at T28. Then, recipe data RD1 is generated based on the stored cooking process. The recipe data RD1 indicates that after operating for 10 minutes with "medium" heating power, operating for 5 minutes with "low" heating power. Next, at T30, first cooker 100 transmits a registration instruction including recipe data RD1 and device ID “ck1” to first terminal device 300 .

When the first terminal device 300 receives the registration instruction from the first cooker 100 at T30, it displays a registration confirmation screen at T32. The registration confirmation screen is a screen for allowing the user to select whether or not to register the recipe data RD1. Upon receiving the registration operation at T34, the first terminal device 300 transmits a registration instruction including the recipe data RD1 and the device ID "ck1" to the server 600 at T36. The first terminal device 300 is configured to transmit a registration instruction to the server 600 only when accepting a registration operation.

When the server 600 receives the registration instruction from the first terminal device 300 at T36, the server table 634 determines that the server-side information including the device ID "ck1" in the registration instruction is not registered, and determines that the recipe ID specifies the smallest ID "F100h" among the IDs (values) that can be assigned as . In addition, the server 600 generates a management ID "mn1" that is a unique ID, and at T40, server-side information including the management ID "mn1", the device ID "ck1", the recipe data RD1, and the recipe ID "F100h". Store SI1 in server table 634 . Next, the server 600 transmits the management ID “mn1”, the recipe data RD1 and the recipe ID “F100h” to the first terminal device 300 at T42.

When the first terminal device 300 receives the management ID “mn1”, the recipe data RD1 and the recipe ID “F100h” from the server 600 at T42, the first terminal device 300 receives the management ID “mn1”, the recipe data RD1 and the recipe ID at T44. The terminal side information TI1 including "F100h" is stored in the terminal table 336. FIG. When T44 ends, the first registration process of registering the recipe data RD1 generated by the first cooker 100 in the server 600 ends.

(Editing process; Fig. 4)
Next, an editing process for editing the recipe data RD1 registered in the server 600 will be described with reference to FIG. FIG. 4 shows the state after FIG. Also, the terminal-side memory 332 of the first terminal device 300 stores final communication information “ck1”.

When the first terminal device 300 receives the application activation operation in T110, it activates the application 334, and in T112 displays the operation screen. Next, when the first terminal device 300 receives an edit operation requesting editing of the recipe data in T114, it specifies the final communication information "ck1" stored in the terminal-side memory 332, and in T116, the device ID Send a data request containing “ck1” to server 600 .

Upon receiving the data request from the first terminal device 300 at T116, the server 600 identifies the server-side information SI1 including the device ID “ck1” in the data request in the server table 634, and at T118 A data list including information “mn1, RD1, F100h” in SI1 is transmitted to the first terminal device 300 .

Upon receiving the data list from the server 600 at T118, the first terminal device 300 displays a recipe selection screen at T120. When first terminal device 300 accepts the selection of recipe ID "F100h" at T122, first terminal device 300 displays the cooking process indicated by recipe data RD1 corresponding to recipe ID "F100h" at T124. Next, at T126, the first terminal device 300 performs an operation to change the operating time at the "medium" heat power from 5 minutes to 3 minutes, and the seasoning at the timing when the heat power is changed from "medium" to "low". When the operation of adding a comment to the effect that it is put into the object to be heated is accepted, at T128, the recipe data RD1 in the terminal table 336 is changed, and at T130, the change including the management ID "mn1" and the recipe data RD1 Send the request to the server 600 . Upon receiving the change request from the first terminal device 300 at T130, the server 600 changes the recipe data RD1 associated with the management ID "mn1" in the server table 634 at T132. This completes the editing process for editing (changing) the recipe data RD1.

(First sharing process; FIG. 5)
Next, referring to FIG. 5, a first sharing process for sharing the recipe data RD1 generated by the first cooker 100 will be described. FIG. 5 shows the state after FIG. In the initial state of FIG. 5, the terminal-side memory (not shown) of the second terminal device 400 stores final communication information “ck1”.

When the second terminal device 400 accepts the application activation operation in T210, it activates the application 434, and in T212 displays the operation screen. Next, in T214, the second terminal device 400 accepts an acquisition operation requesting acquisition of recipe data, specifies the final communication information “ck1” stored in the terminal-side memory, and in T216, the device ID “ ck1” to the server 600.

When the server 600 receives the data request from the first terminal device 300 in T216, it identifies the server-side information SI1 including the device ID “ck1” in the request in the server table 634, and in T218 A data list including information “mn1, RD1, F100h” in SI1 is transmitted to the second terminal device 400 .

When the second terminal device 400 receives the data list from the server 600 in T218, it updates the terminal table 436 using the information in the data list in T220. Specifically, the second terminal device 400 stores the terminal-side information TI1 including the management ID “mn1”, the recipe data RD1, and the recipe ID “F100h” in the terminal table 436. FIG. Next, second terminal device 400 displays a recipe selection screen at T222, accepts the selection of recipe ID "F100h" at T224, and, at T226, prepares a recipe including recipe data RD1 and recipe ID "F100h". Send the request to the first cooker 100 .

Upon receiving the cooking request from the second terminal device 400 at T226, the first cooker 100 stores the device-side information AI1 including the recipe data RD1 and the recipe ID "F100h" in the device table 134 at T228. do. Next, first cooker 100 receives the ignition operation of stove burner 112 at T230, and controls the operation of stove burner 112 at T232 according to recipe data RD1.

(Second registration process; Fig. 6)
A second registration process for registering recipe data RD11 generated by second cooker 200 in server table 634 of server 600 will be described with reference to FIG. In the initial state of FIG. 6, the terminal-side memory (not shown) of the terminal device 500 stores final communication information “ck2”.

When the third terminal device 500 accepts the application activation operation in T310, it activates the application 534 and displays the operation screen in T312. Next, when the third terminal device 500 accepts the generation operation at T314, it transmits a generation instruction to the second cooking device 200 at T316.

Second cooker 200 receives the generation instruction from third terminal device 500 at T316, receives the ignition operation of stove burner 212 at T320, and starts storing the cooking process at T322. Next, at T324, 5 minutes after T320, the second heating cooker 200 receives an operation to change the heating power from "high" to "low", and at T326, 10 minutes after T324, the stove burner 212 is extinguished. When the operation is accepted, at T328, the storage of the cooking process is terminated, and recipe data RD11 is generated based on the stored cooking process. Next, second cooker 200 transmits a registration instruction including recipe data RD11 and device ID “ck2” to third terminal device 500 at T330.

When the third terminal device 500 receives the registration instruction from the second cooking device 200 in T330, it displays the registration confirmation screen in T332, and receives the registration operation in T334. and the device ID “ck2” to the server 600 .

When the server 600 receives the registration instruction from the third terminal device 500 at T336, the server 600 determines that the server-side information including the device ID "ck2" in the registration instruction is not registered in the server table 634, and Identify the smallest ID "F100h" among allocatable IDs (values). In addition, the server 600 generates a management ID "mn2" that is a unique ID, and at T340, server-side information including the management ID "mn2", the device ID "ck2", the recipe data RD11, and the recipe ID "F100h". Store SI2 in server table 634 . Next, the server 600 transmits the management ID “mn2”, the recipe data RD11 and the recipe ID “F100h” to the third terminal device 500 at T342.

When the third terminal device 500 receives the management ID “mn2”, the recipe data RD11, and the recipe ID “F100h” from the server 600 in T342, the third terminal device 500 receives the management ID “mn2”, the recipe data RD11, and the recipe ID in T344. The terminal side information TI11 including "F100h" is stored in the terminal table 536. FIG. Thus, the second registration process for registering recipe data RD11 generated by second cooking device 200 in server 600 is completed.

(Second sharing process; FIG. 7)
Next, with reference to FIG. 7, a second sharing process of sharing recipe data RD11 generated by second cooker 200 used in house 20 different from house 10 in house 10 will be described. For example, a user living in the house 10 and a user living in the house 20 are a family, and the user living in the house 10 receives recipe data generated by the user living in the house 20. Usage situation is assumed. The initial state in FIG. 7 is the state after FIGS. 3 and 6 . Also, the terminal-side memory 332 of the first terminal device 300 stores final communication information “ck1”.

When the first terminal device 300 receives the application activation operation in T410, it activates the application 334, and in T412 displays the operation screen. When the first terminal device 300 receives the input of the device ID “ck2” and the acquisition operation in T414, it specifies the final communication information “ck1” stored in the terminal-side memory 332, and in T416, the device A data request containing IDs “ck1” and “ck2” is sent to the server 600 . In the data request, the device ID "ck1" is described at the top, and the device ID "ck2" is described next to the device ID "ck1".

When the server 600 receives the data request from the first terminal device 300 in T416, the server 600 identifies that the recipe request includes two device IDs "ck1" and "ck2", The device ID “ck1” written at the beginning of the IDs is specified, and the server-side information SI1 including the device ID “ck1” is specified in the server table 634 . Next, the server 600 identifies the device ID "ck2" described next to the device ID "ck1" in the data request, and identifies the server-side information SI2 including the device ID "ck2" in the server table 634. and extracts the recipe data RD11 in the server-side information SI2. Next, the server 600 identifies the smallest ID (that is, "F100h") among the recipe IDs associated with the device ID "ck1", and determines the next largest value after the identified ID "F100h". F101h" is specified as the recipe ID corresponding to RD11. That is, the server 600 generates recipe IDs in ascending order of ID value. In a modified example, the server 600 may generate recipe IDs in descending order of ID values, or may generate recipe IDs randomly. The server 600 also identifies a unique management ID "mn3". Next, in T418, the server 600 stores the server-side information SI3 including the management ID "mn3", the device ID "ck1", the recipe data RD11 and the recipe ID "F101h" in the server table 634. Next, in T420, the server 600 sends a data list including the information "mn1, RD1, F100h" in the server-side information SI1 and the information "mn3, RD11, F101h" in the server-side information SI3 to the first terminal. Send to device 300 .

When the first terminal device 300 receives the data list from the server 600 in T420, it determines that the information corresponding to the information "mn3, RD11, F101h" in the data list is not stored in the terminal table 336, and T422. , terminal-side information TI2 including management ID “mn3”, recipe data RD11, and recipe ID “F101h” is stored in the terminal table 336 . Next, the first terminal device 300 displays a recipe selection screen at T424. Thereafter, by selecting a recipe ID displayed on the recipe selection screen, the user can cause first cooker 100 to perform an operation according to the recipe data corresponding to the recipe ID.

(Third sharing process; FIG. 8)
Referring to FIG. 8 , in a situation where a user living in house 10 is visiting house 20 , using first terminal device 300 , second heating cooker 200 used in house 20 A third sharing process for sharing the recipe data RD11 generated by . The initial state of FIG. 8 is after the user using the first terminal device 300 visits the house 20 and the BT connection is established between the second cooking device 200 and the first terminal device 300. state. Therefore, the terminal-side memory 332 of the first terminal device 300 stores the final communication information “ck2”.

When the first terminal device 300 receives the application activation operation in T510, it activates the application 334, and in T512 displays the operation screen. Next, when the first terminal device 300 accepts the acquisition operation in T514, it specifies the final communication information “ck2” stored in the terminal-side memory 332, and in T516, the data including the device ID “ck2”. Send the request to the server 600 .

Upon receiving the data request from the first terminal device 300 in T516, the server 600 identifies the server-side information SI2 including the device ID “ck2” in the data request in the server table 634, and in T518 A data list including information “mn2, RD11, F100h” in SI2 is transmitted to the first terminal device 300 .

Upon receiving the data list from the server 600 at T518, the first terminal device 300 updates the terminal table 336 at T520. Specifically, the first terminal device 300 stores terminal-side information TI11 including the management ID “mn2”, the recipe data RD11, and the recipe ID “F100h” in the terminal table 336. FIG. Next, the first terminal device 300 displays a recipe selection screen in T522. Thereafter, by selecting a recipe ID displayed on the recipe selection screen, the user can cause second cooking device 200 to perform an operation according to the recipe data corresponding to the recipe ID.

According to the above configuration, when the server 600 receives a data request from the first terminal device 300 (T416 in FIG. 7), the server 600 uses the device ID "ck1" included in the data request to obtain recipe data RD1 and The recipe ID "F100h" is specified, and a data list including the recipe data RD1 and the recipe ID "F100h" is transmitted to the first terminal device 300 (T420). Further, when receiving a data request from the second terminal device 400 (T216 in FIG. 5), the server 600 utilizes the device ID "ck1" included in the data request to obtain recipe data RD1 and recipe ID "F100h". ”, and transmits a data list including recipe data RD1 and recipe ID “F100h” to the second terminal device 400 (T218). Therefore, among a plurality of users using the first heating cooker 100 (that is, a user using the first terminal device 300 and a user using the second terminal device 400), and the recipe data RD1 corresponding to the first cooker 100 can be shared.

Further, first terminal device 300 issues a registration instruction only when accepting a registration operation (T34 in FIG. 3) after receiving recipe data RD1 from first cooker 100 (T30 in FIG. 3). After transmitting to server 600 (T36) and receiving the data list from server 600 (T118 in FIG. 4), a change instruction is transmitted to server 600 (T130) only when a change operation is accepted (T126). Therefore, for example, the processing load on the server 600 can be reduced compared to a configuration in which a registration instruction including recipe data is transmitted to the server 600 at each predetermined timing.

Further, first terminal device 300 transmits a data request to server 600 only when accepting an application activation operation (T410 in FIG. 7) and accepting an acquisition operation (T414). Therefore, for example, the processing load on the server 600 can be reduced compared to a configuration in which data requests are sent to the server 600 at predetermined timings.

Further, when the terminal-side memory 332 stores the device ID "ck2" as the final communication information (FIG. 8), the first terminal device 300 transmits a data request including the device ID "ck2" to the server 600. (T516 in FIG. 8). According to the above configuration, the first terminal device 300 can receive the recipe data RD11 desired by the user from the server 600 .

When the server 600 receives a data request including the device IDs "ck1" and "ck2" from the first terminal device 300 (T416 in FIG. 7), the server table 634 stores the device ID "ck1". recipe data RD1 and recipe ID "F100h" associated with , and recipe data RD11 associated with device ID "ck2" are identified. Then, the server 600 associates the recipe data RD11 with the device ID "ck1" and the recipe ID "F101h", stores it in the server table 634 (T418), and associates the recipe data RD1 with the recipe ID "F100h". and recipe data RD11 and recipe ID "F101h" to the first terminal device 300 (T420). According to the above configuration, first terminal device 300 receives recipe data RD11 generated by second cooker 200 and recipe ID "F101h". Therefore, the user of first terminal device 300 can cause first cooker 100 to perform an operation according to recipe data RD11 by designating recipe ID "F101h".

The server 600 also stores the recipe data RD11 in association with a recipe ID “F101h” different from the recipe ID “F100h”, and transmits the recipe ID “F101h” to the first terminal device 300 . Therefore, the user of the first terminal device 300 can distinguish between the recipe ID "F100h" and the recipe ID "F101h". As a result, the user can appropriately select the recipe ID.

In addition, recipe data and recipe IDs are associated and stored in the device table 134 in the device-side memory 132 of the first cooking-by-heating device 100 (see T228 in FIG. 5). Therefore, the amount of information to be stored in the device-side memory 132 can be reduced compared to the case where the device-side memory 132 stores the device ID, the recipe data, and the recipe ID. Further, the user of the first terminal device 300 operates the first heat cooker 100 and designates the recipe ID to cause the first heat cooker 100 to perform an operation according to the recipe data. can be done. Therefore, user convenience can be improved.

Further, as shown in FIG. 2, in a server table 634 of the server-side memory 632 of the server 600, device IDs, recipe data, recipe IDs, and management IDs are stored in association with each other. According to the above configuration, for example, a recipe ID "F100h" stored in association with the device ID "ck1" and the recipe data RD1, and a recipe stored in association with the device ID "ck2" and the recipe data RD11. Even if the ID "F100h" is the same ID, different IDs are set as management IDs, so each recipe data can be managed appropriately. That is, the server 600 can appropriately manage recipe data. Also, by using the same recipe ID, the number of IDs used as recipe IDs can be reduced. Therefore, when there is an upper limit to the number of IDs that can be used as recipe IDs, it is possible to increase the number of recipe data that can be registered in the server table 634 compared to a configuration in which different recipe IDs are associated with each recipe data. can.

(correspondence relationship)
The device ID and recipe data are examples of “device identification information” and “cooking operation information”, respectively. A management ID or a recipe ID is an example of "operation identification information." The device ID “ck1” and recipe data RD1 are examples of “first device identification information” and “first cooking operation information”, respectively. Management ID "mn1" or recipe ID "F100h" is an example of "first action identification information". The data request at T416 and the data list at T420 in FIG. 7 are examples of the "first data request" and the "first data list", respectively. The data request at T216 and the data list at T218 in FIG. 5 are examples of the "second data request" and the "second data list", respectively. The registration operation of T34 in FIG. 3 is an example of the "first predetermined operation". The changing operation of T126 in FIG. 4 is an example of the "second predetermined operation". The application activation operation at T410 and the acquisition operation at T414 in FIG. 7 are examples of the "third predetermined operation" and the "fourth predetermined operation", respectively. The device ID “ck2” and recipe data RD11 are examples of “second device identification information” and “second cooking operation information”, respectively. Recipe ID “F101h” is an example of “specific action identification information”. The data request at T416 and the data list at T420 in FIG. 7 are examples of the "third data request" and the "third data list", respectively.

(Second embodiment)
As shown in FIG. 2, in the second embodiment, the server-side information stored in the server table 634 of the server 600 differs from that in the first embodiment. The server-side information of the second embodiment includes management IDs, device IDs, recipe data, recipe IDs, and model names. The model name is information indicating the model of the cooker 100 or 200 . When the server 600 receives the registration instruction from the first terminal device 300 (for example, T36 in FIG. 3), the server 600 identifies the model name corresponding to the device ID based on the device ID in the registration instruction. , stores the specified model name in the server table 634 . The second embodiment differs from the first embodiment in that the recipe data generated by the cookers 100 and 200 having the same model name can be shared.

(Fourth sharing process; FIG. 9)
A fourth sharing process of the second embodiment will be described with reference to FIG. The initial state of FIG. 9 is the same as the initial state of FIG. That is, the server table 634 of the server 600 stores server-side information SI1 and SI2.

When the first terminal device 300 accepts the application activation operation in T610, it activates the application 334, and in T612 displays the operation screen. Next, when the first terminal device 300 accepts the acquisition operation in T614, it specifies the final communication information “ck1” stored in the terminal-side memory 332, and in T616 requests data including the device ID “ck1”. to the server 600 .

When the server 600 receives the data request from the first terminal device 300 in T616, the server table 634 specifies the server-side information SI1 including the device ID “ck1” included in the request. Next, the server 600 identifies the server-side information SI2 including the model name "MD1" included in the server-side information SI1 in the server table 634, and extracts the recipe data RD11 in the server-side information SI2. Next, the server 600 identifies "F101h" as the recipe ID corresponding to RD11 and identifies the unique management ID "mn3". Next, in T618, the server 600 stores server-side information SI3 including the management ID "mn3", the device ID "ck1", the recipe ID "F101h", the recipe data RD11, and the model name "MD1" in the server table 634. . Next, in T620, the server 600 sends a data list including the information "mn1, RD1, F100h" in the server-side information SI1 and the information "mn3, RD11, F101h" in the server-side information SI3 to the first terminal. Send to device 300 .

When the first terminal device 300 receives the data list from the server 600 in T620, it determines that the information corresponding to the information "mn3, F101h, RD11" in the data list is not stored in the terminal table 336, and T622. , terminal-side information TI2 including management ID “mn3”, recipe data RD11, and recipe ID “F101h” is stored in the terminal table 336 . Next, the first terminal device 300 displays a recipe selection screen at T624. Thereafter, by selecting a recipe ID displayed on the recipe selection screen, the user can cause first cooker 100 to perform an operation according to the recipe data corresponding to the recipe ID.

According to the above configuration, the recipe ID generated in each cooking device 100, 200 can be shared among users who use cooking devices 100, 200 of the same model.

Although each embodiment has been described in detail above, these are merely examples and do not limit the scope of the claims. The technology described in the claims includes various modifications and changes of the specific examples illustrated above.

(First Modification) The device table 134 may not be stored in the device-side memory 132 of the first cooker 100 . That is, T228 in FIG. 5 can be omitted. Also, in another modification, the contents of the device-side information stored in the device table 134 may be the same as the contents of the server-side information stored in the server table 634 of the server 600 .

(Second Modification) The first terminal device 300 may transmit a data request including the device ID "ck1" to the server 600 every time a predetermined period of time elapses.

(Third Modification) First terminal device 300 may transmit a data request including device ID “ck1” to server 600 when accepting an application activation operation. In this modified example, the user does not have to perform the acquisition operation (for example, T414 in FIG. 7).

(Fourth Modification) The first terminal device 300 stores the device ID input by the user in the terminal-side memory 332, and includes the device ID stored in the terminal-side memory 332 when accepting the acquisition operation. An acquisition request may be sent to the server 600 .

(Fifth Modification) The first terminal device 300 may be configured to acquire recipe data generated by a cooking device with a communication history.

(Sixth Modification) When the server 600 receives the data request from the first terminal device 300 at T416 in FIG. ck2", and a data list including information "mn1, F100h, RD1" in the server-side information SI1 and information "mn2, F100h, RD11" in the server-side information SI2. may be transmitted to the first terminal device 300 .

(Seventh Modification) "Device identification information" is not limited to a device ID, and may be, for example, a serial number, a manufacturing number, or the like.

The technical elements described in this specification or in the drawings exhibit technical usefulness alone or in various combinations, and are not limited to the combinations described in the claims as of the filing. In addition, the techniques exemplified in this specification or drawings can simultaneously achieve a plurality of purposes, and achieving one of them has technical utility in itself.

2: Cooking system 4: Internet 10, 20: House 100: First cooking device 112: Stove burner 114: Operation unit 116: Display unit 118: BTI/F
130: Control unit 132: Device side memory 134: Device table 200: Second heating cooker 212: Stove burner 214: Operation unit 216: Display unit 218: BTI/F
230: control unit 232: device side memory 234: device table 300: first terminal device 312: display operation unit 314: communication I/F
330: Control unit 332: Terminal side memory 334: Cooking application 336: Terminal table 400: Second terminal device 436: Terminal table 500: Third terminal device 536: Terminal table 600: Server 614: Communication I/F
630: Control unit 632: Server side memory 634: Server table

Claims (7)

A cooking system comprising a plurality of cookers, a plurality of terminal devices, and a server,
The server is
For each of the plurality of heating cookers, device identification information identifying the heating cooker, cooking operation information related to the operation of the heating cooker and generated by the heating cooker, and the cooking operation information A server-side memory for storing in association with operation identification information for identification,
The first terminal device
Sending to the server a first data request including first device identification information that identifies the first cooking device;
The server is
When the first data request is received from the first terminal device, the first data request associated with the first device identification information in the first data request is stored in the server-side memory. identifying the cooking motion information and the first motion identification information;
transmitting a first data list including the first cooking action information and the first action identification information to the first terminal device;
A second terminal device different from the first terminal device,
sending a second data request including the first device identification information to the server;
The server is
When the second data request is received from the second terminal device, the first device identification information associated with the first device identification information in the second data request is stored in the server-side memory. Identifying the cooking operation information and the first operation identification information of
transmitting a second data list including the first cooking action information and the first action identification information to the second terminal device;
heating cooking system. The first terminal device
A first predetermined operation, which is an operation for requesting transmission of the first cooking operation information and the first device identification information after receiving the first cooking operation information from the first cooking device. transmitting a registration instruction including the first cooking operation information and the first device identification information to the server only when accepting
The server is
generating the first action identification information when receiving the registration instruction from the first terminal device;
storing the first device identification information, the first cooking action information, and the first action identification information in association with each other in the server-side memory;
The first terminal device
Only when receiving a second predetermined operation that is an operation for changing the contents of the first cooking operation information in the first data list after receiving the first data list from the server, changing the first cooking action information to specific cooking action information, and transmitting a change instruction including the specific cooking action information and the first action identification information to the server;
The server is
When the change instruction is received from the first terminal device, the first cooking action information stored in association with the first action identification information is changed to the specific cooking action in the server-side memory. The cooking system according to claim 1, wherein the information is changed. The first terminal device
When accepting a third predetermined operation that is an operation for starting a specific application installed in the first terminal device, or accepting the third predetermined operation and the first data request 3. The cooking system according to claim 1, wherein said first data request is transmitted to said server only when a fourth predetermined operation, which is an operation for requesting transmission of said data, is received. The first terminal device
A terminal-side memory that stores, as final communication information, the device identification information that identifies the heating cooker with which communication was last executed among the plurality of heating cookers,
The first terminal device
2. When said terminal-side memory stores said first device identification information as said final communication information, said first data request including said first device identification information is transmitted to said server. 4. The cooking system according to any one of 3. The first terminal device
Sending to the server a third data request including the first device identification information and second device identification information for identifying a second cooking device different from the first cooking device death,
The server is
When the third data request is received from the first terminal device, the first cooking operation information associated with the first device identification information and the first data request are stored in the server-side memory. identify the behavior identifier of the
identifying second cooking operation information associated with the second device identification information in the server-side memory when receiving the third data request from the first terminal device;
storing the second cooking action information in the server-side memory in association with the first device identification information and specific action identification information different from the first action identification information;
a third data list including the first cooking action information and the first action identification information, and including the second cooking action information and the specific action identification information, to the first terminal device; The cooking system according to any one of claims 1 to 4, which transmits. The server is
When receiving the first data request from the first terminal device,
identifying, in the server-side memory, the first cooking action information and the action identification information associated with the first appliance identification information in the first data request;
In the server-side memory, third cooking operation information associated with third appliance identification information that identifies a third cooking appliance that is the same model as the first cooking appliance, and third cooking operation information. Identifying the action identification information of 3,
transmitting the first data list including the first cooking action information and the first action identification information and including the third cooking action information and the third action identification information to the first terminal; 6. The cooking system according to any one of claims 1 to 5, transmitting to a device. The first heating cooker is
7. The cooking system according to any one of claims 1 to 6, further comprising a device-side memory that associates and stores the first cooking action information and the first action identification information.

Images