Control apparatus, control system, control method, and program

Abstract

To provide a control apparatus, a control system, a control method, and a program, capable of reducing a workload of a user when performing a setting for operating equipment.SOLUTION: A cloud server 1 comprises: a scene acquisition part 113 that acquires scene information containing operation content information of equipment 3A; a template generation part 116 that generates template information containing model information contained in the scene information and the operation content information; an equipment information acquisition part 112 that acquires equipment identification information of equipment 3B and the model information; and a scene generation part 118 that selects the equipment identification information corresponded to the model information that is matched to the model information contained in the template information including the scene identification information included in scene information request information from the equipment identification information of the equipment 3B, and generates the scene information containing the model information contained in the template information containing the equipment identification information to be selected and the scene information containing the operation content information.SELECTED DRAWING: Figure 3

Description

[Technical field]

[0001] The present disclosure relates to a control device, a control system, a control method, and a program. [Background technology]

[0002] A home appliance control system has been proposed that includes an operation means having a display and an operation section for operating network home appliances connected to a home network, and a control means for controlling the network home appliances in response to an operation on an operation screen displayed on the display section of the operation means, the operation means displays on the display section convenient buttons for collectively controlling the operation of multiple types of network home appliances designated in advance as control targets in response to life scenes such as "go out," "sleep," and "return," and the control means collectively controls the operation of the network home appliances to be controlled when the convenient buttons are operated (see, for example, Patent Document 1). In this home appliance control system, when the "go out" button is operated, for example, an air conditioner, which is a network home appliance, is stopped and a light is turned off in response. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2006-350819 A Summary of the Invention [Problem to be solved by the invention]

[0004] Incidentally, in a home appliance control system such as that described in Patent Document 1, there is a demand for reducing the burden placed on users in setting up the home appliance by allowing settings for operating multiple appliances in a coordinated manner, such as a convenience button, set for a network home appliance connected to one home network to be reused for network home appliances connected to other home networks.

[0005] The present disclosure has been made in consideration of the above-mentioned reasons, and aims to provide a control device, a control system, a control method, and a program that can reduce the workload of a user when configuring settings to operate an equipment. [Means for solving the problem]

[0006] In order to achieve the above object, the control device according to the present disclosure includes: an operation setting acquisition unit that acquires operation setting information including model information indicating the type of at least one first device and operation content information indicating operation content when operating the at least one first device, and first device identification information identifying the at least one first device, and operation setting identification information that identifies the operation setting information; a template generating unit that generates template information on which the operation setting information is based, the template information including the model information and the operation content information included in the operation setting information and the operation setting identification information; a device information acquisition unit that acquires device information including second device identification information that identifies at least one second device and model information that indicates a type of the at least one second device; an operation setting generation unit that selects, from the second device identification information of the at least one second device, at least one second device identification information associated with model information that matches model information included in template information corresponding to the operation setting identification information included in operation setting information request information transmitted from a terminal device, the operation setting identification information including the operation setting identification information and requesting new generation of the operation setting information, and generates operation setting information of the at least one second device including the selected at least one second device identification information and the model information, the operation setting information, and the operation setting identification information included in the template information corresponding to the operation setting identification information included in the operation setting information request information; and a device control unit that controls at least one second device identified by the at least one selected second device identification information based on the operation content information included in the operation setting information of the at least one second device. Effect of the Invention

[0007] According to the present disclosure, the template generation unit generates template information, which is the basis of the operation setting information, including model information and operation content information included in the acquired operation setting information, and operation setting identification information. Also, the device information acquisition unit acquires second device identification information and model information of the second device. Furthermore, the operation setting generation unit selects, from the second device identification information of the second device, second device identification information associated with model information that matches model information included in template information including operation setting identification information included in operation setting information request information transmitted from the terminal device, and generates operation setting information including the selected second device identification information and model information and operation content information included in the template information including operation setting identification information included in the operation setting information request information. Then, the device control unit controls at least one second device identified by each of the selected at least one second device identification information based on the operation content information included in the operation setting information of the second device. This allows the user to simply transmit, via the terminal device, operational setting information request information including the operational setting identification information specified by the user, and to operate, from among the second devices, the second device that matches the operational setting identification information included in the operational setting information request information based on the operational setting information corresponding to the operational setting identification information. This reduces the user's workload when making settings to operate the second device. [Brief description of the drawings]

[0008] [Figure 1] 1 is a schematic configuration diagram of a control system according to a first embodiment of the present disclosure. [Diagram 2] FIG. 1 is a block diagram showing a hardware configuration of a control system according to a first embodiment. [Diagram 3] FIG. 1 is a block diagram showing a functional configuration of a control system according to a first embodiment. [Figure 4] FIG. 1A is a diagram showing an example of information stored in a scene storage unit according to the first embodiment, and FIG. 1B is a diagram showing an example of information stored in an event-driven scene storage unit according to the first embodiment. [Diagram 5]FIG. 1 is a diagram showing an example of information stored in a template storage unit according to the first embodiment; [Figure 6] FIG. 1 is a sequence diagram showing an operation of the control system according to the first embodiment. [Figure 7] FIG. 1A is a diagram showing an example of a setting screen image displayed on a terminal device according to the first embodiment; FIG. 1B is a diagram showing another example of a setting screen image displayed on a terminal device according to the first embodiment; and FIG. 1C is a diagram showing another example of a setting screen image displayed on a terminal device according to the first embodiment. [Figure 8] FIG. 1A is a diagram showing an example of a setting screen image displayed on a terminal device according to the first embodiment; FIG. 1B is a diagram showing another example of a setting screen image displayed on a terminal device according to the first embodiment; and FIG. 1C is a diagram showing another example of a setting screen image displayed on a terminal device according to the first embodiment. [Figure 9] FIG. 1 is a sequence diagram showing an operation of the control system according to the first embodiment. [Figure 10] FIG. 1 is a sequence diagram showing an operation of the control system according to the first embodiment. [Figure 11] FIG. 1 is a sequence diagram showing an operation of the control system according to the first embodiment. [Figure 12] FIG. 1A is an operational explanatory diagram showing a process flow for generating scene information in the control system according to the first embodiment; FIG. 1B is an operational explanatory diagram showing a process flow for generating event-driven scene information in the control system according to the first embodiment; [Figure 13] 1 is a flowchart showing an example of the flow of a device control process executed by a cloud server according to the first embodiment. [Figure 14] 1 is a flowchart showing an example of the flow of a device control process executed by a cloud server according to the first embodiment. [Figure 15] Schematic configuration diagram of a control system according to a second embodiment [Figure 16] FIG. 13 is a diagram showing an example of information stored in a device information storage unit according to the second embodiment; [Figure 17] A sequence diagram showing the operation of the control system according to the second embodiment. [Figure 18]11 is a flowchart showing an example of the flow of a device control process executed by a cloud server according to a second embodiment. [Figure 19] 1 is a schematic configuration diagram of a control system according to a third embodiment. [Figure 20] A sequence diagram showing the operation of a control system according to a third embodiment. [Figure 21] A sequence diagram showing the operation of a control system according to a third embodiment. [Figure 22] 11 is a flowchart showing an example of the flow of a device control process executed by a cloud server according to a third embodiment. [Diagram 23] FIG. 11 is a diagram showing an example of information stored in a template storage unit according to a modified example. [Figure 24] FIG. 11 is a sequence diagram showing the operation of a control system according to a modified example. [Diagram 25] FIG. 11 is a sequence diagram showing the operation of a control system according to a modified example. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] (Embodiment 1) A control device according to an embodiment of the present disclosure will be described below with reference to the accompanying drawings. The control device according to the present embodiment includes an operation setting acquisition unit that acquires operation setting information including model information indicating the type of at least one first device when operating the at least one first device, operation content information indicating operation content set for the first device, first device identification information identifying at least one first device, and operation content identification information identifying the operation content information, a template generation unit that generates template information on which the operation setting information is based, including the model information, operation content information, and operation content identification information included in the operation setting information, a device information acquisition unit that acquires device information including second device identification information identifying at least one second device, and model information indicating the type of each of the at least one second device, and an operation setting request unit that includes the operation content identification information and requests the generation of new operation setting information. When information request information is acquired, an operation setting information generation unit selects, from the second device identification information of at least one second device, second device identification information associated with model information that matches model information included in template information including operation content identification information included in the acquired operation setting information request information, and generates operation setting information for the at least one second device including the selected second device identification information and the model information, operation content information and operation content identification information included in the template information including the operation content identification information included in the operation setting information request information; and a device control unit controls at least one second device identified by each of the at least one selected second device identification information based on the operation content information included in the operation setting information of the at least one second device.

[0010] As shown in FIG. 1, the control system according to the present embodiment includes a cloud server 1 and terminal devices 2A and 2B. The cloud server 1 is a control device that can communicate with devices 3A and 3B via a wide area network NW1, gateway devices 8A and 8B, and local networks NW21 and NW22, and controls the devices 3A and 3B. Here, the wide area network NW1 is, for example, the Internet, and the local networks NW21 and NW22 are, for example, wireless LANs (Local Area Networks) or wired LANs. The cloud server 1 is capable of communicating with terminal devices 2A and 2B owned by users of the devices 3A and 3B via the wide area network NW1. The cloud server 1 may also be capable of communicating with the terminal devices 2A and 2B via the local networks NW21 and NW22.

[0011] The devices 3A and 3B are air conditioners, water heaters, ventilation fans, temperature sensors, etc. equipped with wireless modules, and communicate with the gateway devices 8A and 8B, or relay devices (not shown), or the cloud server 1 via the local networks NW21 and NW22 using communication middleware such as ECHONET Lite (registered trademark). When the devices 3A and 3B acquire device information request information transmitted from the cloud server 1 via the wide area network NW1, the gateway devices 8A and 8B, and the local networks NW21 and NW22, they generate device information including multiple device identification information for identifying the devices themselves and model information indicating the type of the devices themselves in response to the request. Here, the model information is determined based on the group to which the devices 3A and 3B belong when classified based on the functions of the devices 3A and 3B. The groups (categories) may be determined independently by the manufacturers of the devices 3A and 3B, or may be determined according to a standard protocol such as ECHONET Lite. Then, the devices 3A and 3B transmit the generated device information to the cloud server 1 via the local networks NW21 and NW22, the gateway devices 8A and 8B, and the wide area network NW1. Here, the device identification information is a uniquely assigned identification such as MAC address information given to the devices 3A and 3B. In addition, when the devices 3A and 3B acquire device status request information requesting notification of the status of the devices 3A and 3B transmitted from the cloud server 1, the devices 3A and 3B generate device status information indicating their own status in response to the request and transmit the information to the cloud server 1. Here, if the devices 3A and 3B are, for example, temperature sensors, the devices 3A and 3B generate device status information including temperature information indicating the temperature around the devices detected by the devices and transmit the information to the cloud server 1. Note that the devices 3A and 3B may generate and transmit device status information to the cloud server 1 when the status of the devices changes or periodically.

[0012] The terminal devices 2A and 2B are, for example, smartphones, and include a CPU (Central Processing Unit) 201, a main memory unit 202, an auxiliary memory unit 203, a display unit 204, an input unit 205, a communication unit 206, and a bus 209 connecting these units to each other, as shown in FIG. 2. The main memory unit 202 has a volatile memory such as a RAM (Random Access Memory) and is used as a working area for the CPU 201. The auxiliary memory unit 203 is a non-volatile memory such as a semiconductor flash memory, and stores programs for the CPU 201 to execute various processes. The display unit 204 is a display device such as a liquid crystal display or an organic EL (Electro-Luminescence) display. The input unit 205 is, for example, a transparent touch pad arranged on top of the display unit 204. The communication unit 206 is connected to the wide area network NW1 and transmits information transferred from the CPU 201 to the cloud server 1 via the wide area network NW1, and transfers information received from the cloud server 1 via the wide area network NW1 to the CPU 201.

[0013] The CPU 201 reads out a program stored in the auxiliary storage unit 203 into the main storage unit 202 and executes it, thereby functioning as a device information acquisition unit 211, a display control unit 212, a scene generation unit 213, a scene notification unit 214, an event-driven scene generation unit 215, an event-driven scene notification unit 216, a scene registration unit 217, an event-driven scene registration unit 218, and a control request unit 219, as shown in Fig. 3. The auxiliary storage unit 203 shown in Fig. 2 also has a device information storage unit 231, a scene storage unit 232, and an event-driven scene storage unit 233, as shown in Fig. 3. The device information storage unit 231 stores device identification information and model information of each of the devices 3A and 3B used by the users who own the terminal devices 2A and 2B in association with each other.

[0014] The scene storage unit 232 stores scene information including operation content information indicating operation content set for at least one device 3A, 3B by a user who owns the terminal device 2A, 2B, device identification information identifying the device 3A, 3B, and model information indicating the type of the device 3A, 3B, in association with the scene identification information identifying the scene. The event-driven scene storage unit 233 stores action information indicating an operation to be performed by the device 3A, 3B, and event information indicating an event that is a trigger for performing the operation, in association with each other. The event information includes condition information indicating a condition for determining that an event has occurred, and device identification information and model information of the device 3A, 3B from which information for determining whether the condition is satisfied is obtained. The action information includes operation content information indicating the operation to be performed by the device 3A, 3B when a corresponding event has occurred, and device identification information and model information of the device 3A, 3B to be operated.

[0015] The device information acquisition unit 211 acquires the device information transmitted from the cloud server 1 by transmitting device information request information to the cloud server 1, the device information request information including user identification information for identifying the users of the devices 3A and 3B. Then, the device information acquisition unit 211 stores the device identification information and model information included in the acquired device information in the device information storage unit 231 in association with each other.

[0016] When the user performs a setting preparation operation on the input unit 205 to set the contents of a scene or an event-driven scene for the devices 3A and 3B, the display control unit 212 forms a setting screen image for the user to set scene information and event-driven scene information based on the device identification information and model information stored in the device information storage unit 231 in response to this, and displays it on the display unit 204. Furthermore, when the display control unit 212 is notified of scene information and scene identification information from the scene registration unit 217, it forms a scene confirmation image, which is an operation setting notification image for notifying the user of the contents of the scene information set for the devices 3A and 3B used by the user, based on the notified scene information and scene identification information, and displays it on the display unit 204. Furthermore, when the display control unit 212 is notified of the event driven scene information and the event driven scene identification information from the event driven scene registration unit 218, it forms an event driven scene confirmation image, which is an operation setting notification image for notifying the user of the contents of the event driven scene information set for the devices 3A and 3B used by the user, based on the notified event driven scene information and event driven scene identification information, and displays it on the display unit 204. Also, when the user performs a control content selection preparation operation on the input unit 205 to select a scene and an event driven scene to be applied to the devices 3A and 3B, the display control unit 212 forms a control content selection screen image based on the scene information and scene identification information stored in the scene storage unit 232 and the event driven scene information and event driven scene identification information stored in the event driven scene storage unit 233 in response to this, and displays it on the display unit 204.

[0017] The scene generation unit 213 is an operation setting generation unit that generates scene information for the devices 3A and 3B, including operation content information indicating operation content, device identification information identifying the devices 3A and 3B, and model information indicating the type of the devices 3A and 3B, according to the operation content of the scene setting operation when the user performs a scene setting operation on the input unit 205. The scene generation unit 213 stores the generated scene information in the scene storage unit 232 in association with scene identification information identifying the scene information. The scene notification unit 214 generates scene notification information including the scene information stored in the scene storage unit 232, the scene identification information, and user identification information identifying the user, and transmits the scene notification information to the cloud server 1.

[0018] The event-driven scene generation unit 215 is an operation setting generation unit that generates event-driven scene information including the above-mentioned event information and action information for the devices 3A and 3B according to the operation content of the event-driven scene setting operation when the user performs an event-driven scene setting operation on the input unit 205 to set an event-driven scene for the devices 3A and 3B. The event-driven scene generation unit 215 stores the generated event-driven scene information in the event-driven scene storage unit 233 in association with event-driven scene identification information that identifies the event-driven scene information. The event-driven scene notification unit 216 generates event-driven scene notification information including the event-driven scene information stored in the event-driven scene storage unit 233, the event-driven scene identification information, and user identification information that identifies the user, and transmits the event-driven scene notification information to the cloud server 1.

[0019] When the user performs a registration scene selection operation on the input unit 205 to select a scene to be registered in the cloud server 1 for the devices 3A and 3B used by the user, the scene registration unit 217 generates scene information request information and transmits it to the cloud server 1. Here, the scene information request information is operation setting information request information including scene identification information for identifying the selected scene and user identification information. Then, when the scene registration unit 217 obtains scene notification information transmitted from the cloud server 1 by transmitting the scene information request information, it notifies the display control unit 212 of the scene information and scene identification information contained in the obtained scene notification information. Thereafter, when the user performs a scene registration operation on the input unit 205 to newly register a scene whose contents are displayed in the scene check image while the above-mentioned scene check image is displayed on the display unit 204, the scene registration unit 217 generates scene registration request information in response to this and transmits it to the cloud server 1.

[0020] When the user performs a registration event-driven scene selection operation on the input unit 205 to select an event-driven scene to be registered in the cloud server 1 for the devices 3A and 3B used by the user, the event-driven scene registration unit 218 generates event-driven scene information request information and transmits it to the cloud server 1. Here, the event-driven scene information request information is operation setting information request information including event-driven scene identification information for identifying the selected event-driven scene and user identification information. Then, when the scene registration unit 217 acquires scene notification information transmitted from the cloud server 1 by transmitting the scene information request information, it notifies the display control unit 212 of the scene information and scene identification information contained in the acquired scene notification information. Thereafter, when the user performs an event-driven scene registration operation on the input unit 205 to newly register an event-driven scene whose contents are displayed in the event-driven scene confirmation image while the above-mentioned event-driven scene confirmation image is displayed on the display unit 204, the event-driven scene registration unit 218 generates event-driven scene registration request information in response to this and transmits it to the cloud server 1.

[0021] When a control content selection screen image is displayed on the display unit 204 and a user performs a scene selection operation on the input unit 205 to select a scene to be applied to the devices 3A and 3B, the control request unit 219 generates selected scene notification information including scene identification information and user identification information of the selected scene in response to this and transmits it to the cloud server 1.

[0022] Returning to FIG. 2, the cloud server 1 includes a CPU 101, a main memory unit 102, an auxiliary memory unit 103, a communication unit 106, and a bus 109 connecting the various units. The CPU 101 is, for example, a multi-core processor. The main memory unit 102 is made up of a volatile memory and is used as a working area for the CPU 101. The auxiliary memory unit 103 is made up of a large-capacity non-volatile memory and stores programs for implementing various functions of the cloud server 1. The communication unit 106 is connected to a wide area network NW1. Note that the configuration of the cloud server 1 is not limited to that realized by a so-called server machine, and may be constructed in a so-called serverless manner.

[0023] The CPU 101 loads a program stored in the auxiliary storage unit 103 into the main storage unit 102 and executes it, thereby functioning as a device information notification unit 111, a device information acquisition unit 112, a scene acquisition unit 113, an event-driven scene acquisition unit 114, a device control unit 115, a template generation unit 116, a scene registration management unit 117, a scene generation unit 118, an event-driven scene registration management unit 119, an event-driven scene generation unit 120, and a device status acquisition unit 121, as shown in Fig. 3. Furthermore, the auxiliary storage unit 103 shown in Fig. 2 has a device information storage unit 131, a scene storage unit 132, an event-driven scene storage unit 133, a template storage unit 134, and a device status storage unit 135, as shown in Fig. 3. The device information storage unit 131 associates device identification information and model information of each of the devices 3A and 3B used by the users who own the terminal devices 2A and 2B, and also stores the device identification information and user identification information in association with each other.

[0024] The scene storage unit 132 stores scene information including operation content information indicating operation content set by a user who owns the terminal device 2A or 2B for at least one of the devices 3A or 3B, device identification information for identifying the devices 3A or 3B, and model information indicating the type of the devices 3A or 3B, in association with the scene identification information for identifying the scene and the user identification information, as shown in Fig. 4(A), for example. In the example shown in Fig. 4(A), the scene identified by the scene identification information "IDS[0]" corresponding to the user identified by the user identification information "IDU[0]" indicates that the device X1 identified by the device identification information "IDE[0]" whose model is "air conditioner" is operated at a set temperature of "28°C" in cooling mode. As shown in FIG. 4B, for example, the event-driven scene storage unit 133 stores event-driven scene information including action information indicating an operation to be performed by the appliances 3A and 3B and event information indicating an event that triggers the execution of the operation, in association with event-driven scene identification information that identifies the event-driven scene information and user identification information. In the example shown in FIG. 4B, the event-driven scene identified by scene identification information "IDSC[0]" corresponding to the user identified by user identification information "IDU[0]" indicates that when the temperature Th detected by the appliance W1 identified by appliance identification information "IDE[j]" whose model is "temperature sensor" exceeds 30°C, the appliance X1 identified by appliance identification information "IDE[0]" whose model is "air conditioner" is operated at a set temperature of "28°C" in cooling mode. In addition, when the event-driven scene storage unit 133 controls at least one appliance 3A, 3B according to a schedule set by the user, the schedule information indicating the schedule is stored as event information.

[0025] 5, the template storage unit 134 stores template information serving as the basis of scene information, the template information including operation content information indicating operation content set for the devices 3A and 3B and model information indicating the types of the devices 3A and 3B, in association with template identification information that identifies the template information. The template storage unit 134 also stores template information including at least one of action template information serving as the basis of action information and event template information serving as the basis of event information, in association with template identification information that identifies the template information. Here, the event template information includes condition information and model information, and the action template information includes operation content information indicating the content of an operation to be performed by the devices 3A and 3B when an event indicated by the corresponding event template information occurs, and model information.

[0026] 3, the device status storage unit 135 stores device status information indicating the respective states of the devices 3A and 3B in association with device identification information for identifying the devices 3A and 3B. Here, if the devices 3A and 3B are, for example, temperature sensors, the device status information includes temperature information indicating the ambient temperatures detected by the devices 3A and 3B.

[0027] Returning to Fig. 3, when the device information notification unit 111 acquires the device information notification request information transmitted from the terminal devices 2A and 2B, it generates device information request information that requests the devices 3A and 3B used by the user identified by the user identification information to transmit device information based on the user identification information included in the device information notification request information, and transmits the information to the devices 3A and 3B. After transmitting the device information request information to the devices 3A and 3B, the device information notification unit 111 generates device information notification information including the device identification information and model information of the devices 3A and 3B stored in the device information storage unit 131, and transmits the generated device information notification information to the terminal devices 2A and 2B owned by the user identified by the corresponding user identification information. When the device information acquisition unit 112 acquires the device information transmitted from the devices 3A and 3B, it extracts the device identification information, model information, and user identification information included in the acquired device information, associates the extracted device identification information and model information, and stores the device identification information and the extracted user identification information in the device information storage unit 131 in association with each other.

[0028] When the scene acquisition unit 113 acquires scene notification information transmitted from the terminal devices 2A and 2B, it extracts scene information, scene identification information and user identification information included in the acquired scene notification information, and stores the extracted scene information, scene identification information and user identification information in association with each other in the scene storage unit 132. When the event driven scene acquisition unit 114 acquires event driven scene notification information transmitted from the terminal devices 2A and 2B, it extracts event driven scene information, event driven scene identification information and user identification information included in the acquired event driven scene notification information, and stores the extracted event driven scene information, event driven scene identification information and user identification information in association with each other in the event driven scene storage unit 133.

[0029] The device status acquisition unit 121 acquires device status notification information transmitted from the devices 3A and 3B by generating device status request information requesting device status information from the devices 3A and 3B and transmitting the request information to the devices 3A and 3B each time a preset device status notification time arrives. The device status acquisition unit 121 then extracts device status information and device identification information contained in the acquired device status notification information, and stores the extracted device status information and device identification information in the device status storage unit 135 in association with each other. Note that the device status acquisition unit 121 may acquire device status information transmitted from the devices 3A and 3B without generating device status request information if the devices 3A and 3B are configured to transmit device status information to the cloud server 1 when the status of the devices 3A and 3B changes or periodically.

[0030] When the device control unit 115 acquires selected scene notification information transmitted from the terminal devices 2A, 2B, it identifies scene information corresponding to the scene identification information and user identification information included in the acquired selected scene notification information from the scene information stored in the scene storage unit 132, generates control information based on the identified scene information, and transmits it to the devices 3A, 3B. Furthermore, when the device control unit 115 refers to the device status information stored in the device status storage unit 135 and determines that an event has occurred based on the event information included in the event-driven scene information stored in the event-driven scene storage unit 133, it generates control information based on the corresponding action information and transmits it to the devices 3A, 3B.

[0031] The template generation unit 116 generates template information on which scene information is based, including model information and action information included in the scene information acquired by the scene acquisition unit 113, and scene identification information. The template generation unit 116 also generates template information on which event-driven scene information is based, including event template information including model information and condition information included in the event information of the event-driven scene information acquired by the event-driven scene acquisition unit 114, action table information including model information and action information included in the action information, and event-driven scene identification information. Then, the template generation unit 116 stores the generated template information in the template storage unit 134 in association with the template identification information that identifies the template information.

[0032] When the scene registration management unit 117 acquires the above-mentioned scene information request information transmitted from the terminal devices 2A and 2B, it notifies the scene generation unit 118 of the scene identification information included in the acquired scene information request information. In addition, the scene registration management unit 117 generates scene notification information including the scene information generated by the scene generation unit 118 and the scene identification information included in the acquired scene information request information, and transmits the generated scene notification information to the terminal devices 2A and 2B that are the transmission source of the scene information request information. After that, when the scene registration management unit 117 acquires scene registration request information from the terminal devices 2A and 2B that are the transmission destination of the scene notification information, it stores the scene information generated by the scene generation unit 118 in the scene storage unit 132 in association with the corresponding scene identification information and user identification information.

[0033] When the scene generation unit 118 is notified of the scene identification information from the scene registration management unit 117, it selects, from the device identification information of the devices 3A and 3B stored in the device information storage unit 131, device identification information associated with model information that matches the model information included in the template information including the notified scene identification information. Furthermore, the scene generation unit 118 generates scene information including the selected device identification information and the model information and operation content information included in the template information including the notified scene identification information. Then, the scene generation unit 118 notifies the scene registration management unit 117 of the generated scene information.

[0034] When the event-driven scene registration management unit 119 acquires the above-mentioned event-driven scene information request information transmitted from the terminal devices 2A and 2B, it notifies the event-driven scene generation unit 120 of the event-driven scene identification information included in the acquired event-driven scene information request information. In addition, the event-driven scene registration management unit 119 generates event-driven scene notification information including the event-driven scene information generated by the event-driven scene generation unit 120 and the event-driven scene identification information included in the acquired event-driven scene information request information, and transmits the generated event-driven scene notification information to the terminal devices 2A and 2B that are the transmission source of the event-driven scene information request information. After that, when the event-driven scene registration management unit 119 acquires the event-driven scene registration request information from the terminal devices 2A and 2B that are the transmission destination of the event-driven scene notification information, it stores the event-driven scene information generated by the event-driven scene generation unit 120 in the event-driven scene storage unit 133 in association with the corresponding event-driven scene identification information and user identification information.

[0035] When the event-driven scene generation unit 120 is notified of the event-driven scene identification information from the event-driven scene registration management unit 119, the event-driven scene generation unit 120 selects, from the device identification information of the devices 3A and 3B stored in the device information storage unit 131, device identification information associated with model information that matches model information included in the template information including the notified event-driven scene identification information. The event-driven scene generation unit 120 also generates event-driven scene information including the selected device identification information, event information including model information and condition information included in the event template information constituting the template information including the notified event-driven scene identification information, and action information including model information and operation content information included in the action template information constituting the template information including the notified event-driven scene identification information. The event-driven scene generation unit 120 then notifies the event-driven scene registration management unit 119 of the generated event-driven scene information.

[0036] Next, the operation of the control system according to the present embodiment will be described with reference to FIG. 6 to FIG. 11. First, as shown in FIG. 6, when a user who owns the terminal device 2A performs the above-mentioned setting preparation operation via the terminal device 2A, the terminal device 2A accepts the setting preparation operation and generates device information request information including the user identification information of the user of the terminal device 2A for the cloud server 1 (step S1). Next, the generated device information request information is transmitted from the terminal device 2A to the cloud server 1 (step S2). On the other hand, when the cloud server 1 acquires the device information notification request information transmitted from the terminal device 2A, the cloud server 1 generates device information request information that requests the device 3A used by the user identified by the user identification information to transmit device information based on the user identification information contained in the device information notification request information (step S3). Next, the generated device information request information is transmitted from the cloud server 1 to the device 3A (step S4). On the other hand, when the device 3A acquires the device information request information transmitted from the cloud server 1, the device 3A generates device information including the device identification information and model information of the device 3A in response to the acquisition (step S5). Thereafter, the generated device information is transmitted from the device 3A to the cloud server 1 (step S6). On the other hand, when the cloud server 1 acquires the device information transmitted from the device 3A, it extracts the device identification information, model information, and user identification information included in the acquired device information, associates the extracted device identification information and model information, and stores the device identification information and the extracted user identification information in the device information storage unit 131 in association with each other (step S7). Next, the cloud server 1 generates device information notification information including the device identification information and model information of each device 3A stored in the device information storage unit 131 (step S8), and the generated device information notification information is transmitted from the cloud server 1 to the terminal device 2A possessed by the user identified by the corresponding user identification information (step S9). On the other hand, when the terminal device 2A acquires the device information notification information, it stores the device identification information and model information included in the acquired device information notification information in the device information storage unit 231.Then, based on the device identification information and model information stored in the device information storage unit 231, the terminal device 2A forms a setting screen image for the user to set scene information or event-driven scene information, and displays it on the display unit 204 (step S10).

[0037] Here, the terminal device 2A forms setting screen images G11, G12, and G13 as shown in, for example, Figs. 7(A) to (C) and displays them on the display unit 204. The setting screen image GA11 includes a message image M111 indicating the contents of the scene identification information, a button image BU112 selected when changing the scene identification information, a button image BU113 selected when adding a device 3A corresponding to a scene, a button image BU114 selected when determining the operation contents for the device 3A, and a button image BU111 selected when newly registering a scene. When the button image BU113 is selected in a state in which the setting screen image G11 shown in Fig. 7(A) is displayed on the display unit 204 of the terminal device 2A, the setting screen image G12 shown in Fig. 7(B) is displayed on the display unit 204. The setting screen image G12 includes a plurality of button images BU121 representing the devices 3A formed based on the device information acquired from the cloud server 1. Then, when the setting screen image G12 shown in FIG. 7(B) is displayed on the display unit 204 of the terminal device 2A and, for example, a button image BU121 corresponding to "air conditioner 1" is selected, a setting screen image G13 shown in FIG. 7(C) is displayed on the display unit 204. The setting screen image G13 includes an image G131 showing an area for setting the operation start or stop of the device 3A, an image G132 showing an area for setting the operation mode of the device 3A, and an image G133 showing an area for setting the set temperature. The image G131 includes a button image BU132 selected when specifying the start or stop of the operation of the device 3A, the image G132 includes a button image BU133 selected when specifying the operation mode of the device 3A, and the image G133 includes a button image BU134 selected when changing the set temperature and a message image M132 indicating the set temperature. In addition, the setting screen image G13 includes a button image BU131 that is selected when finalizing the setting contents for the device 3A. When the button image BU131 is selected while the setting screen image G13 is displayed on the display unit 204 of the terminal device 2A, the setting screen image G11 shown in FIG. 7(A) is displayed on the display unit 204 again.

[0038] Returning to FIG. 6, when the user performs a scene setting operation on the input unit 205 to set a scene for the device 3A, the terminal device 2A generates scene notification information including operation content information indicating the operation content, device identification information identifying the device 3A, and model information indicating the type of the device 3A, and the scene identification information and user identification information for the device 3A according to the operation content of the scene setting operation (step S11). Here, when the user performs an operation to input information via the input unit 205 while displaying each of the setting screen images G11, G12, and G13 shown in FIG. 7(A) to (C) on the display unit 204, for example, and then performs an operation to select the button image BU111 shown in FIG. 7(A), the terminal device 2A generates scene notification information. Returning to FIG. 6, the generated scene notification information is transmitted from the terminal device 2A to the cloud server 1 (step S12). Meanwhile, when the cloud server 1 acquires scene notification information transmitted from the terminal device 2A, it extracts the scene information, scene identification information, and user identification information included in the acquired scene notification information, and stores the extracted scene information, scene identification information, and user identification information in the scene storage unit 132 in association with each other (step S13). After that, the cloud server 1 generates template information including the model information and operation content information stored in the scene storage unit 132 and the scene identification information, and stores the generated template information in the template storage unit 134 in association with the template identification information that identifies the template information (step S14).

[0039] Furthermore, when the terminal device 2A forms a setting screen image for the user to set a schedule for executing scene information based on the device identification information and model information stored in the device information storage unit 231 and displays it on the display unit 204, the terminal device 2A forms setting screen images G21, G22, and G23 as shown in Fig. 8 (A) to (C), for example, and displays them on the display unit 204. The setting screen image GA21 includes a message image M211 indicating the schedule name for executing the operation indicated by the scene information, a button image BU212 selected when changing the schedule name, a message image M212 indicating the time for executing the operation indicated by the scene information, a button image BU212 selected when changing the time, a button image BU214 selected when specifying the day of the week for executing the operation indicated by the scene information, a button image BU113 selected when adding a device 3A corresponding to the scene information, a button image BU215 selected when deciding the operation content or scene information for the device 3A, and a button image BU211 selected when newly registering scene information. When the button image BU215 is selected while the setting screen image G21 shown in Fig. 8(A) is displayed on the display unit 204 of the terminal device 2A, the setting screen image G22 shown in Fig. 8(B) is displayed on the display unit 204. The setting screen image G22 includes a plurality of button images BU221 representing the respective scenes, and a plurality of button images BU121 representing the respective devices 3A formed based on the device information acquired from the cloud server 1. Then, when the button image BU221 corresponding to "bathroom central heating", for example, is selected while the setting screen image G22 shown in Fig. 8(B) is displayed on the display unit 204 of the terminal device 2A, the setting screen image G23 in which the button image BU221 representing the scene is not selectable is displayed on the display unit 204 as shown in Fig. 8(C). When the setting screen image G23 shown in FIG. 8(C) is displayed on the display unit 204 of the terminal device 2A, when a button image BU121 corresponding to, for example, “air conditioner 1” is selected, the setting screen image G13 shown in FIG. 7(C) described above is displayed on the display unit 204.

[0040] Returning to FIG. 6, when the user performs an event-driven scene setting operation on the input unit 205 to set an event-driven scene for the device 3A, the terminal device 2A generates event-driven scene notification information including the event-driven scene information including the event information and action information described above, the event-driven scene identification information, and the user identification information for the device 3A according to the operation content of the event-driven scene setting operation (step S15). Returning to FIG. 6, the generated event-driven scene notification information is transmitted from the terminal device 2A to the cloud server 1 (step S16). On the other hand, as shown in FIG. 9, when the cloud server 1 acquires the event-driven scene notification information transmitted from the terminal device 2A, it extracts the event information, action information, event-driven scene identification information, and user identification information included in the acquired event-driven scene notification information, and stores the extracted event information, action information, event-driven scene identification information, and user identification information in the event-driven scene storage unit 133 in association with each other (step S17). After that, the cloud server 1 generates template information including event template information including model information and condition information included in the event information stored in the event driven scene storage unit 133, action template information including model information and action content information included in the action information, and event driven scene identification information, and stores the generated template information in the template storage unit 134 in association with the template identification information that identifies the template information (step S18).

[0041] Next, it is assumed that the user who owns the terminal device 2B performs a setting preparation operation via the terminal device 2B. In this case, the terminal device 2B accepts the setting preparation operation and generates device information request information including the user identification information of the user of the terminal device 2A for the cloud server 1 (step S19). Then, the generated device information request information is transmitted from the terminal device 2B to the cloud server 1 (step S20). Meanwhile, when the cloud server 1 acquires the device information notification request information transmitted from the terminal device 2B, the cloud server 1 generates device information request information that requests the device 3B used by the user identified by the user identification information to transmit device information based on the user identification information included in the device information notification request information (step S21). Then, the generated device information request information is transmitted from the cloud server 1 to the device 3B (step S22). Meanwhile, when the device 3B acquires the device information request information transmitted from the cloud server 1, the device 3B generates device information including the device identification information and model information of the device 3B in response to the device information (step S23). Next, the generated device information is transmitted from the device 3B to the cloud server 1 (step S24). Meanwhile, when the cloud server 1 acquires the device information transmitted from the device 3B, it extracts the device identification information, model information, and user identification information contained in the acquired device information, associates the extracted device identification information with the model information, and stores the device identification information and the extracted user identification information in association with each other in the device information memory unit 131 (step S25).

[0042] Next, assume that the user performs a registration scene selection operation on the input unit 205 of the terminal device 2B to select a scene to be registered in the cloud server 1 for the device 3B used by the user. In this case, the terminal device 2B generates scene information request information including scene identification information for identifying the selected scene and user identification information (step S26), and the generated scene information request information is transmitted from the terminal device 2B to the cloud server 1 (step S27). On the other hand, when the cloud server 1 acquires the scene information request information transmitted from the terminal device 2B, it selects device identification information associated with model information that matches model information included in template information including scene identification information included in the acquired scene information request information from the device identification information of the device 3B stored in the device information storage unit 131. In addition, the cloud server 1 generates scene information including the selected device identification information and model information and operation content information included in the template information including the notified scene identification information (step S28). Then, the cloud server 1 generates scene notification information including the generated scene information and the scene identification information included in the acquired scene information request information (step S29). Thereafter, the generated scene notification information is transmitted from the cloud server 1 to the terminal device 2B that is the transmission source of the scene information request information (step S30). On the other hand, upon receiving the scene notification information transmitted from the cloud server 1, the terminal device 2B forms the above-mentioned scene confirmation image based on the scene information and scene identification information included in the received scene notification information, and displays it on the display unit 204 (step S31).

[0043] Next, assume that, with terminal device 2B displaying a scene check image on display unit 204, the user performs a scene registration operation on input unit 205 of terminal device 2B to newly register the scene whose contents are displayed in the scene check image. In this case, terminal device 2B generates scene registration request information (step S32), and the generated scene registration request information is transmitted from terminal device 2B to cloud server 1 (step S33). Meanwhile, upon acquiring the scene registration request information, cloud server 1 stores the generated scene information in scene storage unit 132 in association with the scene identification information included in the acquired scene information request information (step S34), as shown in Fig. 10.

[0044] Next, assume that the user performs a registration event-driven scene selection operation on the input unit 205 of the terminal device 2B to select an event-driven scene to be registered in the cloud server 1 for the device 3B used by the user. In this case, the terminal device 2B generates event-driven scene information request information including event-driven scene identification information for identifying the selected event-driven scene and user identification information (step S35), and the generated event-driven scene information request information is transmitted from the terminal device 2B to the cloud server 1 (step S36). On the other hand, upon acquiring the event-driven scene information request information transmitted from the terminal device 2B, the cloud server 1 selects, from the device identification information of the device 3B stored in the device information storage unit 131, device identification information associated with model information that matches model information included in template information including the event-driven scene identification information included in the acquired event-driven scene information request information. Furthermore, the cloud server 1 generates event-driven scene information including the selected device identification information, the model information and condition information included in the event template information included in the template information including the notified event-driven scene identification information, and the model information and operation content information included in the action template information (step S37). Then, the cloud server 1 generates event-driven scene notification information including the generated event-driven scene information and the event-driven scene identification information included in the acquired event-driven scene information request information (step S38). After that, the generated event-driven scene notification information is transmitted from the cloud server 1 to the terminal device 2B that is the transmission source of the event-driven scene information request information (step S39). Meanwhile, when the terminal device 2B acquires the event-driven scene notification information transmitted from the cloud server 1, it forms the above-mentioned event-driven scene confirmation image based on the event-driven scene information and the event-driven scene identification information included in the acquired event-driven scene notification information, and displays it on the display unit 204 (step S40).

[0045] Next, assume that, with terminal device 2B displaying the event-driven scene confirmation image on display unit 204, the user performs an event-driven scene registration operation on input unit 205 of terminal device 2B to newly register an event-driven scene whose contents are displayed in the event-driven scene confirmation image. In this case, terminal device 2B generates event-driven scene registration request information (step S41), and the generated event-driven scene registration request information is transmitted from terminal device 2B to cloud server 1 (step S42). Meanwhile, upon acquiring the event-driven scene registration request information, cloud server 1 stores the generated event-driven scene information in scene storage unit 132 in association with the event-driven scene identification information included in the acquired event-driven scene information request information (step S43).

[0046] Also, when the user who owns the terminal device 2B performs a scene selection preparation operation on the input unit 205 of the terminal device 2B to select a scene to be applied to the device 3B, the terminal device 2B forms a scene selection screen image and displays it on the display unit 204 (step S44). Next, it is assumed that the user performs a scene selection operation on the input unit 205 of the terminal device 2B to select a scene while the terminal device 2B is displaying the scene selection screen image on the display unit 204. In this case, the terminal device 2B generates selected scene notification information including scene identification information of the scene selected by the scene selection operation (step S45), and the generated scene notification information is transmitted from the terminal device 2B to the cloud server 1 (step S46). On the other hand, as shown in FIG. 11, when the cloud server 1 acquires the selected scene notification information transmitted from the terminal device 2B, it identifies scene information corresponding to the scene identification information and user identification information included in the acquired selected scene notification information from the scene information stored in the scene storage unit 132, and generates control information based on the identified scene information (step S47). Next, the generated control information is transmitted from the cloud server 1 to the device 3B (step S48). On the other hand, upon receiving the control information, the device 3B operates based on the received control information (step S49).

[0047] Furthermore, when the cloud server 1 determines that a preset action execution time has arrived based on the schedule information stored as event information in the event-driven scene storage unit 133, it identifies action information corresponding to the schedule information from among the action information stored in the event-driven scene storage unit 133, and generates control information based on the identified action information (step S47). Then, the generated control information is transmitted from the cloud server 1 to the device 3B (step S48). On the other hand, upon acquiring the control information, the device 3B operates based on the acquired control information (step S49).

[0048] Then, it is assumed that a preset device status notification time has arrived. In this case, the cloud server 1 generates device status request information requesting device status information from the device 3B (step S50), and the generated device status request information is transmitted from the cloud server 1 to the device 3B (step S51). On the other hand, when the device 3B acquires the device status request information, the device 3B generates device status notification information including device status information and device identification information indicating its own status in response to the request (step S52). Next, the generated device status notification information is transmitted from the device 3B to the cloud server 1 (step S53). On the other hand, when the cloud server 1 acquires the device status notification information transmitted from the device 3B, the cloud server 1 extracts the device status information and device identification information included in the acquired device status notification information, and stores the extracted device status information and device identification information in the device status storage unit 135 in association with each other (step S54). Here, it is assumed that the cloud server 1 refers to the device state information stored in the device state storage unit 135 and determines that an event has occurred based on the event information included in the event-driven scene information stored in the event-driven scene storage unit 133 (step S55). In this case, the cloud server 1 generates control information based on the corresponding action information (step S56), and the generated control information is transmitted from the cloud server 1 to the device 3B (step S57). On the other hand, upon acquiring the control information, the device 3B operates based on the acquired control information (step S58).

[0049] In the end, in the control system according to the present embodiment, for example, as shown in FIG. 12(A), it is assumed that a user identified by user identification information IDU[0] generates scene information 1 identified by scene identification information IDS[0] that specifies that an appliance "X1" of the model "air conditioner" is to be "cooled at a set temperature of 28°C" via terminal device 2A. In this case, template information is generated in cloud server 1 that is identified by template identification information IDT[0] that specifies that an arbitrary appliance of the model "air conditioner" is to be "cooled at a set temperature of 28°C". Then, when a user identified by user identification information IDU[1] requests cloud server 1 to generate scene information 2 similar to scene information 1 via terminal device 2B, cloud server 1 selects appliances "X2" and "Z" of the model "air conditioner" indicated by the template information from appliances 3B used by the user, and generates scene information 2 identified by scene identification information IDS[1] that specifies that the selected appliances "X2" and "Z" are to be "cooled at a set temperature of 28°C".

[0050] In the control system according to the present embodiment, for example, as shown in FIG. 12B, a user identified by user identification information IDU[0] generates event-driven scene information 1 identified by event-driven scene identification information IDSC[0] that specifies an action to perform "cooling operation at a set temperature of 28°C" on device "X1" of model "air conditioner" when an event occurs in which the temperature detected by device "W1" of model "temperature sensor" becomes "over 30°C" via terminal device 2A. In this case, in the cloud server 1, template information is generated that is identified by template identification information IDT[m] that specifies that an arbitrary device of model "air conditioner" is to perform "cooling operation at a set temperature of 28°C" on device "X1" of model "air conditioner" when an event occurs in which the temperature detected by an arbitrary device of model "temperature sensor" becomes "over 30°C". Then, when a user identified by user identification information IDU[1] requests the cloud server 1 to generate event-driven scene information 2 similar to the event-driven scene information 1 via a terminal device 2B, the cloud server 1 selects device "X2" which is a model "temperature sensor" indicated by the template information, and devices "X2" and "Z" which are models "air conditioner". Here, device "X2" functions as an air conditioner and also as a temperature sensor. After that, when an event occurs in which the temperature detected by the selected device "X2" is "over 30°C", the cloud server 1 generates event-driven scene information 2 identified by event-driven scene identification information IDSC[1] which specifies that the selected devices "X2" and "Z" are to be "cooled at a set temperature of 28°C".

[0051] Next, the device control process executed by the cloud server 1 according to the present embodiment will be described with reference to Figs. 13 and 14. This device control process is started, for example, when a program for executing the device control process is started in the cloud server 1. First, as shown in Fig. 13, the device information notification unit 111 judges whether or not device information notification request information transmitted from the terminal devices 2A and 2B is acquired (step S101). Here, if the device information notification unit 111 judges that the device information notification request information has not been acquired (step S101: No), the process of step S105 described later is executed. On the other hand, if the device information notification unit 111 judges that the device information notification request information has been acquired (step S101: Yes), the device information notification unit 111 generates device information request information and transmits it to the devices 3A and 3B used by the user identified by the user identification information included in the device information notification request information (step S102). Next, when the device information acquisition unit 112 acquires the device information transmitted from the devices 3A and 3B in response to the device information request information, it extracts the device identification information, model information, and user identification information included in the acquired device information, associates the extracted device identification information with the model information, and stores the device identification information and the extracted user identification information in the device information storage unit 131 in association with each other (step S103). Next, the device information notification unit 111 generates device information notification information including the device identification information and model information of each of the devices 3A and 3B stored in the device information storage unit 131, and transmits the generated device information notification information to the terminal devices 2A and 2B carried by the users identified by the corresponding user identification information (step S104).

[0052] After that, the scene acquisition unit 113 judges whether or not it has acquired scene notification information transmitted from the terminal devices 2A and 2B (step S105). Here, if the scene acquisition unit 113 judges that it has not acquired scene notification information (step S105: No), the process of step S108 described later is executed. On the other hand, if the scene acquisition unit 113 acquires scene notification information (step S105: Yes), it extracts scene information, scene identification information, and user identification information included in the acquired scene notification information, and stores the extracted scene information, scene identification information, and user identification information in the scene storage unit 132 in association with each other (step S106). Next, the template generation unit 116 generates template information that is the basis of the scene information, including the model information and operation content information included in the scene information stored in the scene storage unit 132, and the scene identification information, and stores the generated template information in the template storage unit 134 in association with the template identification information that identifies the template information (step S107).

[0053] Next, the event-driven scene acquisition unit 114 judges whether or not it has acquired the event-driven scene notification information transmitted from the terminal devices 2A and 2B (step S108). If the event-driven scene acquisition unit 114 judges that it has not acquired the event-driven scene notification information (step S108: No), the process of step S111 described later is executed. On the other hand, if the event-driven scene acquisition unit 114 acquires the event-driven scene notification information (step S108: Yes), it extracts the event-driven scene information, the event-driven scene identification information, and the user identification information included in the acquired event-driven scene notification information, and stores the extracted event-driven scene information, the event-driven scene identification information, and the user identification information in the event-driven scene storage unit 133 in association with each other (step S109). Thereafter, the template generation unit 116 generates template information on which the event-driven scene information is based, including event template information including model information and condition information included in the event information of the event-driven scene information stored in the event-driven scene storage unit 133, action table information including model information and action content information included in the action information, and event-driven scene identification information. Then, the template generation unit 116 stores the generated template information in the template storage unit 134 in association with the template identification information that identifies the template information (step S110).

[0054] Next, the scene registration management unit 117 judges whether or not it has acquired scene information request information transmitted from the terminal devices 2A and 2B (step S111). If the scene registration management unit 117 judges that it has not acquired scene information request information (step S111: No), the process of step 116 described below is executed. On the other hand, if the scene registration management unit 117 judges that it has acquired scene information request information (step S111: Yes), it notifies the scene generation unit 118 of the scene identification information included in the acquired scene information request information. Furthermore, when the scene generation unit 118 is notified of the scene identification information from the scene registration management unit 117, it selects, from the device identification information of the devices 3A and 3B stored in the device information storage unit 131, device identification information associated with the model information that matches the model information included in the template information including the notified scene identification information. Furthermore, the scene generation unit 118 generates scene information including the selected device identification information and the model information and operation content information included in the template information including the notified scene identification information (step S112), and notifies the scene registration management unit 117 of the generated scene information. Then, the scene registration management unit 117 generates scene notification information including the scene information generated by the scene generation unit 118 and the scene identification information included in the acquired scene information request information, and transmits the generated scene notification information to the terminal device 2A, 2B that is the source of the scene information request information (step S113). Next, the scene registration management unit 117 determines whether or not it has received scene registration request information from the terminal device 2A, 2B that is the destination of the scene notification information (step S114). Here, if the scene registration management unit 117 determines that it has not received scene registration request information from the terminal device 2A, 2B that is the destination of the scene notification information within a preset time after transmitting the scene notification information (step S114: No), the process of step S116 described later is executed. On the other hand, if the scene registration management unit 117 determines that it has received scene registration request information from the terminal device 2A, 2B to which the scene notification information was sent within a preset time after sending the scene notification information (step S114: Yes), it stores the scene information generated by the scene generation unit 118 in the scene memory unit 132 in association with the corresponding scene identification information and user identification information (step S115).

[0055] 14, the event-driven scene registration management unit 119 judges whether or not it has acquired event-driven scene information request information transmitted from the terminal devices 2A and 2B (step S116). If the event-driven scene registration management unit 119 judges that it has not acquired the event-driven scene information request information (step S116: No), the process of step S121 described later is executed. On the other hand, if the event-driven scene registration management unit 119 judges that it has acquired the event-driven scene information request information (step S116: Yes), it notifies the event-driven scene generation unit 120 of the event-driven scene identification information included in the acquired event-driven scene information request information. Furthermore, when the event-driven scene generation unit 120 is notified of the event-driven scene identification information from the event-driven scene registration management unit 119, it selects device identification information associated with the model information that matches the model information included in the template information including the notified event-driven scene identification information from the device identification information of the devices 3A and 3B stored in the device information storage unit 131. Furthermore, the event-driven scene generation unit 120 generates event-driven scene information including the selected device identification information, event information including model information and condition information included in the event template information included in the template information including the notified event-driven scene identification information, and action information including model information and operation content information included in the action template information included in the template information including the notified event-driven scene identification information (step S117), and notifies the event-driven scene registration management unit 119 of the generated event-driven scene information. Then, the event-driven scene registration management unit 119 generates event-driven scene notification information including the event-driven scene information generated by the event-driven scene generation unit 120 and the event-driven scene identification information included in the acquired event-driven scene information request information, and transmits the generated event-driven scene notification information to the terminal device 2A, 2B that is the source of the event-driven scene information request information (step S118).Next, the event-driven scene registration management unit 119 judges whether or not it has acquired event-driven scene registration request information from the terminal device 2A, 2B to which the event-driven scene notification information is to be transmitted (step S119). If the event-driven scene registration management unit 119 judges that it has not acquired event-driven scene registration request information from the terminal device 2A, 2B to which the event-driven scene notification information is to be transmitted within a preset time after the event-driven scene notification information is transmitted (step S119: No), the process of step S121 described below is executed. On the other hand, if the event-driven scene registration management unit 119 judges that it has acquired event-driven scene registration request information from the terminal device 2A, 2B to which the event-driven scene notification information is to be transmitted within a preset time after the event-driven scene notification information is transmitted (step S119: Yes), it stores the event-driven scene information generated by the event-driven scene generation unit 120 in the event-driven scene storage unit 133 in association with the corresponding event-driven scene identification information and user identification information (step S120).

[0056] Next, the device control unit 115 determines whether or not the selected scene notification information transmitted from the terminal devices 2A and 2B has been acquired (step S121). If the device control unit 115 determines that the selected scene notification information has not been acquired (step S121: No), the device control unit 115 executes the process of step S121 described below. On the other hand, if the device control unit 115 determines that the selected scene notification information has been acquired (step S121: Yes), the device control unit 115 identifies scene information corresponding to the scene identification information and user identification information included in the acquired selected scene notification information from among the scene information stored in the scene storage unit 132, generates control information based on the identified scene information, and transmits the control information to the devices 3A and 3B (step S122).

[0057] Thereafter, the device status acquisition unit 121 determines whether or not a preset device status notification time has arrived (step S123). If the device status acquisition unit 121 determines that the device status notification time has not yet arrived (step S123: No), the process of step S101 is executed again. On the other hand, if the device status acquisition unit 121 determines that the device status notification time has arrived (step S123: Yes), the device status acquisition unit 121 generates device status request information and transmits it to the devices 3A and 3B (step S124) to acquire device status notification information transmitted from the devices 3A and 3B. Then, the device status acquisition unit 121 extracts the device status information and device identification information included in the acquired device status notification information, and stores the extracted device status information and device identification information in the device status storage unit 135 in association with each other (step S125). Next, the device control unit 115 refers to the device status information stored in the device status storage unit 135 and determines whether or not an event has occurred based on the event information included in the event-driven scene information stored in the event-driven scene storage unit 133 (step S126). If the device control unit 115 determines that an event has not occurred (step S126: No), the process of step S101 is executed again. On the other hand, if the device control unit 115 determines that an event has occurred (step S126: Yes), the device control unit 115 generates control information based on the corresponding action information and transmits it to the devices 3A and 3B (step S127). Then, the process of step S101 is executed again.

[0058] As described above, in the cloud server 1 according to the present embodiment, the template generation unit 116 generates template information including the model information and operation content information included in the acquired scene information, and the scene identification information. Furthermore, the device information acquisition unit 112 acquires the device identification information and the model information of each of the devices 3A and 3B. Furthermore, the scene generation unit 118 selects, from the device identification information of the devices 3A and 3B, the device identification information associated with the model information that matches the model information included in the template information including the scene identification information included in the scene information request information transmitted from the terminal devices 2A and 2B. Then, the scene generation unit 118 generates scene information including the selected device identification information, and the model information and operation content information included in the template information including the scene identification information included in the scene information request information. Then, the device control unit 115 controls the device 3B identified by the selected device identification information, based on the operation content information included in the scene information. This allows the user to simply transmit scene information request information including scene identification information designated by the user via the terminal device 2A, 2B, and the device 3A, 3B that matches the scene identification information included in the scene information request information can be operated based on the operation content information corresponding to the scene identification information, from among the devices 3A, 3B. This reduces the workload of the user when making settings to operate the devices 3A, 3B.

[0059] In this embodiment, the event-driven scene information includes condition information indicating a condition under which the operation contents indicated by the operation contents information are executed by at least one of the devices 3A and 3B. The template information includes the model information, operation contents information, event-driven scene identification information, and condition information included in the event-driven scene information. This makes it easier to share the event-driven scene information.

[0060] Furthermore, the model information according to this embodiment is determined based on the group to which each of the devices 3A and 3B belongs when the devices 3A and 3B are classified based on their respective functions. This makes it possible to generate scene information and event-driven scene information that are the same type as the scene information and event-driven scene information applicable to the device 3A connected to the local network NW21 and applicable to the device 3B connected to the local network NW22 even if the device 3A connected to the local network NW21 and the device 3B connected to the local network NW22 are not the same. This has the advantage that the scene information and event-driven scene information can be easily shared between the users of the devices 3A and 3B.

[0061] (Embodiment 2) The cloud server of this embodiment differs from embodiment 1 in that it includes a function determination unit that determines whether or not devices 3A, 3B identified by device identification information selected based on template information have a function to execute the operation content indicated by the operation content information in the scene information, or whether or not devices 3A, 3B have a function to execute the operation content indicated by the operation content information included in the action information of the event-driven scene information.

[0062] The hardware configuration of the cloud server 2001 according to this embodiment shown in FIG. 15 is the same as the hardware configuration of the cloud server 1 described in the embodiment. Therefore, the hardware configuration of the cloud server 2001 will be described using the symbols shown in FIG. 2 as appropriate. The CPU 101 of the cloud server 2001 loads a program stored in the auxiliary storage unit 103 into the main storage unit 102 and executes it, thereby functioning as a device information notification unit 111, a device information acquisition unit 112, a scene acquisition unit 113, an event-driven scene acquisition unit 114, a device control unit 115, a template generation unit 116, a scene registration management unit 117, a scene generation unit 2118, an event-driven scene registration management unit 119, an event-driven scene generation unit 2120, a device state acquisition unit 121, and a function determination unit 2122. In FIG. 15, the same symbols as those in FIG. 3 are used for the same components as those in the embodiment. The auxiliary storage unit 103 also includes a device information storage unit 2131, a scene storage unit 132, an event-driven scene storage unit 133, a template storage unit 134, and a device state storage unit 135. The device information storage unit 2131 stores, as shown in Fig. 16 for example, device identification information and model information of devices 3A and 3B used by users who own terminal devices 2A and 2B, as well as operation content list information indicating a list of operation contents that can be executed by the devices 3A and 3B. The example shown in Fig. 16 indicates that automatic operation is possible for the air conditioner X identified by device identification information IDE[0].

[0063] When the scene generation unit 2118 is notified of the scene identification information from the scene registration management unit 117, the scene generation unit 2118 selects, from the device identification information of the devices 3A and 3B stored in the device information storage unit 131, device identification information associated with model information that matches the model information included in the template information including the notified scene identification information. Then, the scene generation unit 2118 notifies the function determination unit 2122 of the selected device identification information and the operation content information included in the template information. After that, when the scene generation unit 2118 is notified of the device identification information of the devices 3A and 3B having a function for executing the operation content indicated by the operation content information from the function determination unit 2122, the scene generation unit 2118 generates scene information including the device identification information notified from the function determination unit 2122 and the model information and operation content information included in the template information including the scene identification information notified from the scene registration management unit 117. Then, the scene generation unit 118 notifies the scene registration management unit 117 of the generated scene information.

[0064] When the event-driven scene generation unit 2120 is notified of the event-driven scene identification information from the event-driven scene registration management unit 119, it selects, from the device identification information of the devices 3A, 3B stored in the device information storage unit 131, device identification information associated with model information that matches the model information included in the template information including the notified event-driven scene identification information. Then, the event-driven scene generation unit 2120 notifies the function determination unit 2122 of the selected device identification information and the action content information included in the action template information that constitutes the template information. Thereafter, when the event-driven scene generation unit 2120 is notified by the function determination unit 2122 of the device identification information of the devices 3A, 3B having the function of executing the operation content indicated by the operation content information, the event-driven scene generation unit 2120 generates event-driven scene information including the device identification information notified by the function determination unit 2122, event information including model information and condition information included in the event template information constituting the template information including the event-driven scene identification information notified by the event-driven scene registration management unit 119, and action information including model information and operation content information included in the action template information constituting the template information including the event-driven scene identification information notified by the event-driven scene registration management unit 119. Then, the event-driven scene generation unit 2120 notifies the event-driven scene registration management unit 119 of the generated event-driven scene information.

[0065] The function determination unit 2122 determines whether the devices 3A and 3B identified by the device identification information selected based on the template information have a function to execute the action contents indicated by the action contents information of the scene information. Specifically, when the device identification information and the action contents information are notified from the scene generation unit 2118, the function determination unit 2122 refers to the action contents list information corresponding to each of the notified device identification information stored in the device information storage unit 2131 and determines whether there is action contents information matching the notified action contents information. Then, the function determination unit 2122 notifies the scene generation unit 2118 of the device identification information corresponding to the action contents list information in which the matching action contents information exists. In addition, the function determination unit 2122 determines whether the devices 3A and 3B identified by the device identification information selected based on the template information have a function to execute the action contents indicated by the action contents information included in the action template information. Specifically, when the function determination unit 2122 is notified of device identification information and operation information from the event driven scene generation unit 2120, the function determination unit 2122 determines whether or not there is operation information matching the notified operation information by referring to the operation list information corresponding to each of the notified device identification information stored in the device information storage unit 2131. Then, the function determination unit 2122 notifies the event driven scene generation unit 2120 of the device identification information corresponding to the operation list information in which the matching operation information exists.

[0066] Next, the operation of the control system according to the present embodiment will be described with reference to FIG. 17. Note that in FIG. 17, the same processes as those in the embodiment are denoted by the same reference numerals as those in FIG. 6 to FIG. 11. First, after the processes from steps S1 to S18 described in the embodiment are performed, as shown in FIG. 17, it is assumed that a user who possesses the terminal device 2B performs a setting preparation operation via the terminal device 2B. In this case, a series of processes from steps S19 to S25 is performed. Next, it is assumed that the user performs a registration scene selection operation on the input unit 205 of the terminal device 2B to select a scene to be registered in the cloud server 2001 for the device 3B used by the user. In this case, the terminal device 2B generates scene information request information including scene identification information and user identification information for identifying the selected scene (step S26), and the generated scene information request information is transmitted from the terminal device 2B to the cloud server 2001 (step S27). On the other hand, when the cloud server 2001 acquires the scene information request information transmitted from the terminal device 2B, it selects, from among the device identification information of the device 3B stored in the device information storage unit 131, device identification information associated with the model information that matches the model information included in the template information including the scene identification information included in the acquired scene information request information. Then, the cloud server 2001 determines whether the device 3B identified by the device identification information selected based on the template information has a function to execute the operation contents indicated by the operation content information included in the template information (step S2001). Next, the cloud server 2001 generates scene information including the device identification information of the device 3B that has the function to execute the operation contents indicated by the operation content information, and the model information and operation content information included in the template information including the notified scene identification information (step S2002). After that, the cloud server 2001 generates scene notification information including the generated scene information and the scene identification information included in the acquired scene information request information (step S28). Then, a series of processes from step S29 onwards are executed.

[0067] Next, the device control process executed by the cloud server 2001 according to the present embodiment will be described with reference to FIG. 18. In FIG. 18, the same processes as those in the embodiment are denoted by the same reference numerals as those in FIG. 13 and FIG. 14. First, after a series of processes from step S101 to S110 are executed, the scene registration management unit 117 judges whether or not it has acquired scene information request information transmitted from the terminal devices 2A and 2B (step S111). Here, if the scene registration management unit 117 judges that it has not acquired scene information request information (step S111: No), the process of step S115 is executed. On the other hand, if the scene registration management unit 117 judges that it has acquired scene information request information (step S111: Yes), it notifies the scene generation unit 118 of the scene identification information included in the acquired scene information request information. Then, when the scene generation unit 118 is notified of the scene identification information from the scene registration management unit 117, the scene generation unit 118 selects, from the device identification information of the devices 3A and 3B stored in the device information storage unit 131, device identification information associated with model information that matches the model information included in the template information including the notified scene identification information. The scene generation unit 2118 notifies the function determination unit 2122 of the selected device identification information and the operation content information included in the template information. On the other hand, when the function determination unit 2122 is notified of the device identification information and the operation content information from the scene generation unit 2118, it refers to the operation content list information stored in the device information storage unit 2131 and corresponding to each of the notified device identification information, and determines whether or not there is operation content information that matches the notified operation content information (step S2101). Here, the function determination unit 2122 notifies the scene generation unit 2118 of the device identification information corresponding to the operation content list information in which the matching operation content information exists. Next, the scene generation unit 2118 generates scene information including the device identification information notified by the function determination unit 2122 and the model information and operation content information included in the template information including the scene identification information notified by the scene registration management unit 117 (step S2102), and notifies the scene registration management unit 117 of the generated scene information.Then, the scene registration management unit 117 generates scene notification information including the scene information generated by the scene generation unit 118 and the scene identification information included in the acquired scene information request information, and transmits the generated scene notification information to the terminal device 2A, 2B that is the transmission source of the scene information request information (step S2103). After that, the processes of steps S114 and S115 are executed.

[0068] Next, the event-driven scene registration management unit 119 judges whether or not it has acquired event-driven scene information request information transmitted from the terminal devices 2A and 2B (step S116). If the event-driven scene registration management unit 119 judges that it has not acquired the event-driven scene information request information (step S116: No), the process of step S121 described below is executed. On the other hand, if the event-driven scene registration management unit 119 judges that it has acquired the event-driven scene information request information (step S116: Yes), it notifies the event-driven scene generation unit 2120 of the event-driven scene identification information included in the acquired event-driven scene information request information. Furthermore, when the event-driven scene generation unit 2120 is notified of the event-driven scene identification information from the event-driven scene registration management unit 119, it selects device identification information associated with the model information that matches the model information included in the template information including the notified event-driven scene identification information from the device identification information of the devices 3A and 3B stored in the device information storage unit 131. The event-driven scene generation unit 2120 notifies the function determination unit 2122 of the selected device identification information and the action content information included in the action template information. On the other hand, when the function determination unit 2122 is notified of the device identification information and the action content information from the event-driven scene generation unit 2120, it refers to the action content list information stored in the device information storage unit 2131 and corresponding to each of the notified device identification information, and determines whether or not there is action content information matching the notified action content information (step S2104). Here, the function determination unit 2122 notifies the event-driven scene generation unit 2120 of the device identification information corresponding to the action content list information in which the matching action content information exists. Next, the event-driven scene generation unit 2120 generates event-driven scene information including the device identification information notified by the function determination unit 2122 and the model information and operation content information included in the template information including the event-driven scene identification information notified by the event-driven scene registration management unit 119 (step S2105), and notifies the event-driven scene registration management unit 119 of the generated event-driven scene information.Then, the event-driven scene registration management unit 119 generates event-driven scene notification information including the event-driven scene information generated by the event-driven scene generation unit 2120 and the event-driven scene identification information included in the acquired event-driven scene information request information, and transmits the generated event-driven scene notification information to the terminal device 2A, 2B that is the sender of the event-driven scene information request information (step S2106). After that, a series of processes from step S119 onwards are executed.

[0069] As described above, according to this embodiment, it is possible to selectively set scene information and event-driven scene information for devices 3A, 3B that have the function of executing the operation content indicated by the operation content information in the scene information, or for devices 3A, 3B that have the function of executing the operation content indicated by the operation content information included in the action information of the event-driven scene information, so that it is possible to appropriately set scene information and event-driven scene information.

[0070] (Embodiment 3) The cloud server of this embodiment differs from embodiment 1 in that it includes a model determination unit that determines whether or not it is possible to select at least one device identification information associated with model information that matches the scene identification information transmitted from terminal devices 2A and 2B, scene information request information that includes event-driven scene identification information and requests the generation of new scene information or event-driven scene information, the scene identification information included in the event-driven scene information request information, and model information included in template information that includes the event-driven scene identification information, from the device identification information of devices 3A and 3B, and an error notification unit that generates error information and transmits it to terminal devices 2A and 2B when it is determined that it is not possible to select at least one device identification information.

[0071] The hardware configuration of the cloud server 3001 according to this embodiment shown in FIG. 19 is the same as the hardware configuration of the cloud server 1 described in the first embodiment. Therefore, the hardware configuration of the cloud server 3001 will be described using the symbols shown in FIG. 2 as appropriate. The CPU 101 of the cloud server 3001 loads a program stored in the auxiliary storage unit 103 into the main storage unit 102 and executes it, thereby functioning as a device information notification unit 111, a device information acquisition unit 112, a scene acquisition unit 113, an event-driven scene acquisition unit 114, a device control unit 115, a template generation unit 116, a scene registration management unit 117, a scene generation unit 2118, an event-driven scene registration management unit 119, an event-driven scene generation unit 120, a device status acquisition unit 121, a model determination unit 3123, and an error notification unit 3124. In FIG. 19, the same symbols as those in FIG. 3 are used for the same components as those in the embodiment.

[0072] The model determination unit 3123 determines whether or not it is possible to select, from the device identification information of the devices 3A and 3B, at least one piece of device identification information associated with model information that matches the scene identification information transmitted from the terminal devices 2A and 2B, scene information request information including event-driven scene identification information and requesting the generation of new scene information or event-driven scene information, scene identification information included in the event-driven scene information request information, and model information included in template information including the event-driven scene identification information. If it is determined that it is not possible to select at least one piece of device identification information, the error notification unit 3124 generates error information and transmits it to the terminal devices 2A and 2B.

[0073] Next, the operation of the control system according to the present embodiment will be described with reference to FIG. 20 and FIG. 21. Note that in FIG. 20 and FIG. 21, the same processes as those in the embodiment are denoted by the same reference numerals as those in FIG. 6 to FIG. 11. First, after the processes from steps S1 to S18 described in the embodiment are performed, as shown in FIG. 20, it is assumed that a user who possesses the terminal device 2B performs a setting preparation operation via the terminal device 2B. In this case, a series of processes from steps S19 to S25 is performed. Next, it is assumed that the user performs a registration scene selection operation to select a scene to be registered in the cloud server 2001 for the device 3B used by the user, on the input unit 205 of the terminal device 2B. In this case, the terminal device 2B generates scene information request information including scene identification information and user identification information for identifying the selected scene (step S26), and the generated scene information request information is transmitted from the terminal device 2B to the cloud server 2001 (step S27). On the other hand, when the cloud server 2001 acquires the scene information request information transmitted from the terminal device 2B, it is determined that it is possible to select device identification information associated with model information that matches the model information included in the template information including the scene identification information included in the acquired scene information request information from the device identification information of the device 3B stored in the device information storage unit 131 (step S3001). In this case, the cloud server 2001 generates scene information including the selected device identification information and the model information and operation content information included in the template information including the notified scene identification information (step S3002). After that, the cloud server 2001 generates scene notification information including the generated scene information and the scene identification information included in the acquired scene information request information (step S29). After that, a series of processes from step S30 onwards are executed.

[0074] Also, after a series of processes from step S19 to S25 are executed, as shown in FIG. 21, it is assumed that the user performs the above-mentioned registration scene selection operation on the input unit 205 of the terminal device 2B. In this case, the terminal device 2B generates scene information request information including scene identification information for identifying the selected scene and user identification information (step S26), and the generated scene information request information is transmitted from the terminal device 2B to the cloud server 3001 (step S27). On the other hand, when the cloud server 3001 acquires the scene information request information transmitted from the terminal device 2B, it is assumed that the cloud server 3001 determines that it is impossible to select device identification information associated with model information that matches model information included in template information including scene identification information included in the acquired scene information request information from among the device identification information of the device 3B stored in the device information storage unit 131 (step S3003). In this case, the cloud server 3001 generates error notification information (step S3004), and the generated error notification information is transmitted from the cloud server 3001 to the terminal device 2B (step S3005). On the other hand, when the terminal device 2B acquires the error notification information, it forms an error notification image based on the acquired error notification information and displays it on the display unit 204 (step S3006).

[0075] Next, the device control process executed by the cloud server 3001 according to the present embodiment will be described with reference to FIG. 22. In FIG. 22, the same processes as those in the embodiment are denoted by the same reference numerals as those in FIG. 13 and FIG. 14. First, after a series of processes from step S101 to S110 are executed, the scene registration management unit 117 judges whether or not it has acquired scene information request information transmitted from the terminal device 2A, 2B (step S111). Here, if the scene registration management unit 117 judges that it has not acquired scene information request information (step S111: No), the process of step 115 is executed. On the other hand, if the scene registration management unit 117 judges that it has acquired scene information request information (step S111: Yes), it notifies the scene generation unit 118 and the model determination unit 3123 of the scene identification information included in the acquired scene information request information. Then, when the model determination unit 3123 is notified of the scene identification information from the scene registration management unit 117, the model determination unit 3123 determines whether or not it is possible to select device identification information associated with model information that matches the model information included in the template information including the notified scene identification information from the device identification information of the devices 3A and 3B stored in the device information storage unit 131 (step S3101). If the model determination unit 3123 determines that it is unable to select device identification information (step S3101: No), the process of step S3103 described below is executed. On the other hand, it is assumed that the model determination unit 3123 determines that it is possible to select device identification information (step S3101: Yes). In this case, when the model determination unit 3123 is notified of the scene identification information from the scene registration management unit 117, the model determination unit 3123 selects device identification information associated with model information that matches the model information included in the template information including the notified scene identification information from the device identification information of the devices 3A and 3B stored in the device information storage unit 131. Then, scene generating unit 118 generates scene information including the selected device identification information and the model information and operation content information included in the template information including the scene identification information notified from scene registration managing unit 117 (step S112). Next, a series of processes from step S113 to step S115 are executed.

[0076] Next, the event-driven scene registration management unit 119 judges whether or not it has acquired event-driven scene information request information transmitted from the terminal device 2A, 2B (step S116). If the event-driven scene registration management unit 119 judges that it has not acquired the event-driven scene information request information (step S116: No), the process of step S121 is executed. On the other hand, if the event-driven scene registration management unit 119 judges that it has acquired the event-driven scene information request information (step S116: Yes), it notifies the event-driven scene generation unit 120 and the model determination unit 3123 of the event-driven scene identification information included in the acquired event-driven scene information request information. Then, when the event-driven scene identification information is notified from the event-driven scene registration management unit 119, the model determination unit 3123 determines whether or not it is possible to select, from the device identification information of the devices 3A and 3B stored in the device information storage unit 131, device identification information associated with model information that matches the model information included in the action template information constituting the template information including the notified event-driven scene identification information (step S3102). Here, it is assumed that the model determination unit 3123 determines that it is not possible to select device identification information (step S3102: No). In this case, the error notification unit 3124 generates error notification information and transmits it to the terminal devices 2A and 2B (step S3103). Thereafter, the process of step S101 is executed again. On the other hand, it is assumed that the model determination unit 3123 determines that it is possible to select device identification information (step S3102: Yes). In this case, the event-driven scene generation unit 120 selects device identification information associated with model information that matches model information included in action template information constituting template information including the notified event-driven scene identification information, from the device identification information of the devices 3A and 3B stored in the device information storage unit 131. Then, the scene generation unit 118 generates event-driven scene information including the selected device identification information and the model information and operation content information included in the action template information constituting template information including the event-driven scene identification information notified by the event-driven scene registration management unit 119 (step S117).Next, a series of processes from step S118 onwards are executed.

[0077] However, the device 3A connected to the local network NW21 and the device 3B connected to the local network NW22 do not necessarily have the same functions. For this reason, if a user who uses the device 3A tries to apply scene information set for at least one device 3A to at least one device 3B connected to the local network NW22 as is, a problem may occur in which the device 3B cannot execute the operation indicated by the operation content information included in the scene information. For example, in a case where a ventilation device and an air conditioner are connected to the local network NW21 but a ventilation device is not connected to the local network NW22, even if a user of the ventilation device connected to the local network NW21 generates scene information for example, in which the ventilation device performs ventilation while the air conditioner performs heating and cooling, and applies the scene information to the device 3B connected to the local network NW22, the effect intended by the user may not be obtained because there is no ventilation device connected to the local network NW22.

[0078] In contrast, according to the present embodiment, if there is no device 3A, 3B corresponding to the model information included in the template information, the generation of scene information or event-driven scene information is avoided, so that the scene information and event-driven scene information can be set appropriately. Therefore, the same scene information and event-driven scene information as the scene information and event-driven scene information generated for the device 3A connected to the local network NW21 are generated for the device 3B only when they can be appropriately applied to the device 3B connected to the local network NW22. Therefore, the scene information and event-driven scene information generated for the device 3B can be used to obtain the effect intended by the user of the device 3B.

[0079] Although the embodiments of the present disclosure have been described above, the present disclosure is not limited to the above-described embodiments. For example, in each embodiment, the template information may include model information, operation content information, operation setting identification information, and installation location information included in the operation setting information. In this case, for example, as shown in FIG. 23, the template storage unit 4134 stores template information including operation content information and model information as well as installation location information indicating the installation locations of the devices 3A and 3B in association with template identification information that identifies the template information. In addition, the template storage unit 4134 stores template information including at least one of action template information and event template information in association with template identification information that identifies the template information, and the action template information includes installation location information as well as operation content information and model information indicating the content of an operation to be performed by the devices 3A and 3B when an event indicated by the corresponding event template information occurs.

[0080] According to this configuration, scene information and event-driven scene information can be generated taking into account the installation locations of the devices 3A and 3B, so that scene information and event-driven scene information suitable for the installation locations of the devices 3A and 3B can be generated.

[0081] In each embodiment, the user may change at least a part of the scene information and the event-driven scene information generated based on the template information for the devices 3A and 3B through the terminal devices 2A and 2B. In this case, when the scene registration unit 217 of the terminal devices 2A and 2B performs a scene registration operation to newly register the changed scene information generated by the user performing a scene change operation on the input unit 205 to change the scene information whose contents are displayed in the scene check image while the above-mentioned scene check image is displayed on the display unit 204, the scene registration unit 217 may generate scene registration request information including the changed scene information and the scene identification information in response to the scene registration operation and transmit it to the cloud server 1. Then, when the scene registration management unit 117 of the cloud server 1 acquires the scene registration request information from the terminal devices 2A and 2B to which the scene notification information is to be transmitted, the scene registration management unit 117 may extract the scene information included in the acquired scene registration request information, and store the extracted scene information in the scene storage unit 132 in association with the corresponding scene identification information and user identification information.

[0082] Furthermore, when a user performs an event-driven scene registration operation on input unit 205 to change the event-driven scene information whose contents are displayed in the event-driven scene confirmation image while the above-mentioned event-driven scene confirmation image is displayed on display unit 204, thereby performing an event-driven scene registration operation to newly register the changed event-driven scene information generated by performing an event-driven scene change operation on input unit 205 to change the event-driven scene information whose contents are displayed in the event-driven scene confirmation image, the event-driven scene registration unit 218 of terminal devices 2A, 2B accordingly generates event-driven scene registration request information including the changed event-driven scene information and event-driven scene identification information, and transmits it to cloud server 1. Then, when the event-driven scene registration management unit 119 of the cloud server 1 acquires the event-driven scene registration request information from terminal devices 2A, 2B to which the event-driven scene notification information is to be transmitted, it extracts the event-driven scene information included in the acquired event-driven scene registration request information, and stores the extracted event-driven scene information in the event-driven scene storage unit 133 in association with the corresponding event-driven scene identification information and user identification information.

[0083] Here, the operation of the control system according to this modification will be described with reference to FIG. 24 and FIG. 25. Note that in FIG. 24 and FIG. 25, the same processes as those in the embodiment are denoted by the same reference numerals as those in FIG. 6 to FIG. 11. Also, it is assumed that the template storage unit 134 has already stored template information. First, it is assumed that the user performs a registration scene selection operation on the input unit 205 of the terminal device 2B to select a scene to be registered in the cloud server 1 for the device 3B used by the user. In this case, the terminal device 2B generates the above-mentioned scene information request information (step S26), and the generated scene information request information is transmitted from the terminal device 2B to the cloud server 1 (step S27). Next, after a series of processes from steps S28 to S30 described in the first embodiment are executed, the terminal device 2B acquires the scene notification information transmitted from the cloud server 1, and forms the above-mentioned scene confirmation image based on the scene information and scene identification information included in the acquired scene notification information, and displays it on the display unit 204 (step S31).

[0084] Here, assume that, in a state where the terminal device 2B displays a scene check image on the display unit 204, the user performs a scene change operation on the input unit 205 of the terminal device 2B to change the scene information whose contents are displayed in the scene check image. In this case, the terminal device 2B generates new scene information in response to the scene change operation (step S5001). Next, when the user performs a scene registration operation to newly register the changed scene information, the terminal device 2B generates scene registration request information including the newly generated scene information and scene identification information in response to this (step S5002), and the generated scene registration request information is transmitted from the terminal device 2B to the cloud server 1 (step S5003). On the other hand, when the cloud server 1 acquires the scene registration request information, it extracts the scene information and the scene identification information included in the acquired scene registration request information, and stores the extracted scene information and the scene identification information in the scene storage unit 132 in association with each other (step S5004).

[0085] Also, assume that the user performs a registration event-driven scene selection operation on the input unit 205 of the terminal device 2B to select an event-driven scene to be registered in the cloud server 1 for the device 3B used by the user. In this case, the terminal device 2B generates the above-mentioned event-driven scene information request information (step S35), and the generated event-driven scene information request information is transmitted from the terminal device 2B to the cloud server 1 (step S36). Thereafter, a series of processes from steps S37 to S39 described in the first embodiment are executed. Next, when the terminal device 2B acquires the event-driven scene notification information transmitted from the cloud server 1, the terminal device 2B forms the above-mentioned event-driven scene confirmation image based on the event-driven scene information and the event-driven scene identification information included in the acquired event-driven scene notification information, and displays the image on the display unit 204 (step S40).

[0086] Here, assume that, with the event-driven scene confirmation image displayed on the display unit 204 of the terminal device 2B, the user performs an event-driven scene change operation on the input unit 205 of the terminal device 2B to change the event-driven scene information whose contents are displayed in the event-driven scene confirmation image, as shown in Fig. 25. In this case, the terminal device 2B generates new event-driven scene information in response to the event-driven scene change operation (step S5005). Next, when the user performs an event-driven scene registration operation to newly register the changed event-driven scene information, in response to this, the terminal device 2B generates event-driven scene registration request information including the newly generated event-driven scene information and the event-driven scene identification information (step S5006), and the generated event-driven scene registration request information is transmitted from the terminal device 2B to the cloud server 1 (step S5007). On the other hand, when the cloud server 1 acquires the event-driven scene registration request information, it extracts the event-driven scene information and the event-driven scene identification information contained in the acquired and generated event-driven scene registration request information, and stores the extracted and acquired event-driven scene information and the event-driven scene identification information in the event-driven scene memory unit 133 in association with each other (step S5008).

[0087] According to this configuration, the scene information and the event-driven scene information for the devices 3A and 3B can be customized to suit the preferences of the user, thereby improving convenience for the user.

[0088] In addition, the various functions of the cloud servers 1, 2001, 3001 and the terminal devices 2A and 2B according to the present disclosure may be realized by software, firmware, or a combination of software and firmware. In this case, the software or firmware may be written as a program, and the program may be stored and distributed in a computer-readable recording medium such as a flexible disk, a CD-ROM (Compact Disc Read Only Memory), a DVD (Digital Versatile Disc), or an MO (Magneto-Optical Disc), and the program may be read and installed in a computer to configure a computer capable of realizing each of the above-mentioned functions. In addition, when each function is realized by sharing the work between an OS (Operating System) and an application, or by cooperation between the OS and an application, only the parts other than the OS may be stored in the recording medium.

[0089] Furthermore, each program may be superimposed on a carrier wave and distributed via a communication network. For example, the program may be posted on a bulletin board (BBS, Bulletin Board System) on the communication network and distributed via the network. These programs may then be started and executed under the control of the OS in the same way as other application programs, thereby enabling the above-mentioned processing to be performed.

[0090] Various aspects of the present disclosure are summarized below as appendices.

[0091] (Appendix 1) an operation setting acquisition unit that acquires operation setting information including model information indicating the type of at least one first device and operation content information indicating operation content when operating the at least one first device, and first device identification information identifying the at least one first device, and operation setting identification information that identifies the operation setting information; a template generating unit that generates template information on which the operation setting information is based, the template information including the model information and the operation content information included in the operation setting information and the operation setting identification information; a device information acquisition unit that acquires device information including second device identification information that identifies at least one second device and model information that indicates a type of the at least one second device; an operation setting generation unit that selects, from the second device identification information of the at least one second device, at least one second device identification information associated with model information that matches model information included in template information corresponding to the operation setting identification information included in operation setting information request information transmitted from a terminal device, the operation setting identification information including the operation setting identification information and requesting new generation of the operation setting information, and generates operation setting information of the at least one second device including the selected at least one second device identification information and the model information, the operation setting information, and the operation setting identification information included in the template information corresponding to the operation setting identification information included in the operation setting information request information; and a device control unit that controls at least one second device identified by the at least one selected second device identification information based on the operation content information included in the operation setting information of the at least one second device. Control device. (Appendix 2) The operation setting information further includes condition information indicating a condition for the operation content indicated by the operation content information to be executed by the at least one first device, the template information includes the model information, the operation content information, the operation setting identification information, and the condition information, which are included in the operation setting information; 2. The control device according to claim 1. (Appendix 3) the model information is determined based on a group to which the at least one first device and the at least one second device belong when classified based on the functions of the at least one first device and the at least one second device; 3. The control device according to claim 1 or 2. (Appendix 4) The operation setting information further includes installation location information indicating an installation location of the at least one first device, the template information includes the model information, the operation content information, the operation setting identification information, and the installation location information, which are included in the operation setting information; 4. The control device according to claim 1, (Appendix 5) a function determination unit that determines whether or not a second device identified by the second device identification information selected by the operation setting generation unit has a function for executing the operation content indicated by the operation content information, the operation setting generation unit generates operation setting information including operation content information for only a second device having a function of executing an operation content indicated by the operation content information, for any of the second devices selected by the operation setting generation unit; 5. The control device according to claim 1, (Appendix 6) a model determination unit that determines whether or not at least one second device identification information associated with model information that matches model information included in template information including the operation setting identification information included in operation setting information request information that includes the operation setting identification information transmitted from the terminal device and requests new generation of operation setting information can be selected from the second device identification information of the second device; and an error notification unit that generates error information and transmits the error information to the terminal device when it is determined that the at least one second device identification information cannot be selected. 6. The control device according to claim 1, (Appendix 7) an operation setting acquisition unit that acquires operation setting information including model information indicating the type of at least one first device and operation content information indicating operation content when operating the at least one first device, and first device identification information identifying the at least one first device, and operation setting identification information that identifies the operation setting information; a template generating unit that generates template information on which the operation setting information is based, the template information including the model information and the operation content information included in the operation setting information and the operation setting identification information; a device information acquisition unit that acquires device information including second device identification information that identifies at least one second device and model information that indicates a type of the at least one second device; a terminal device having an input unit, which generates operation setting information request information including the operation setting identification information input by a user via the input unit and requesting the generation of new operation setting information; an operation setting generation unit that selects, from the second device identification information of the at least one second device, at least one second device identification information associated with model information that matches model information included in template information corresponding to the operation setting identification information included in operation setting information request information that includes the operation setting identification information and is transmitted from the terminal device, and generates operation setting information of the at least one second device including the selected at least one second device identification information and the model information, the operation setting information, and the operation setting identification information included in the template information corresponding to the operation setting identification information included in the operation setting information request information; and a device control unit that controls at least one second device identified by the at least one selected second device identification information based on the operation content information included in the operation setting information of the at least one second device. Control system. (Appendix 8) the terminal device has a display unit and an input unit, and in a state in which an operation setting notification image for notifying a user of the contents of the operation of the second device is formed based on the operation setting information and displayed on the display unit, when the user performs an operation setting change operation on the input unit to change the operation setting information whose contents are displayed in the operation setting notification image, thereby performing an operation setting registration operation for newly registering the changed operation setting information, the terminal device generates operation setting registration request information including the changed operation setting information and the operation setting identification information, An operation setting registration unit that, when receiving the operation setting registration request information, extracts the operation setting information included in the received operation setting registration request information, the device control unit controls at least one second device identified by each of the at least one selected second device identification information based on operation content information included in the extracted operation setting information. 8. The control system of claim 7. (Appendix 9) A step in which a control device acquires operation setting information including model information indicating the type of at least one first device and operation content information indicating operation content when operating the at least one first device, and first device identification information identifying the at least one first device, and operation setting identification information identifying the operation setting information; a step of generating template information on which the operation setting information is based, the template information including the model information and the operation content information included in the operation setting information, and the operation setting identification information, by the control device; The control device acquires device information including second device identification information for identifying at least one second device and model information indicating a type of the at least one second device; the control device selects, from the second device identification information of the at least one second device, at least one second device identification information associated with model information that matches model information included in template information corresponding to the operation setting identification information included in operation setting information request information that includes the operation setting identification information and is transmitted from a terminal device and requests new generation of the operation setting information, and generates operation setting information including the at least one selected second device identification information and the model information, the operation setting information, and the operation setting identification information included in the template information corresponding to the operation setting identification information included in the operation setting information request information; and controlling, by the control device, at least one second device identified by each of the at least one selected second device identification information based on the operation content information included in the operation setting information of the at least one second device. Control methods. (Appendix 10) Computer, an operation setting acquisition unit that acquires operation setting information including model information indicating a type of at least one first device and operation content information indicating an operation content when operating the at least one first device, and first device identification information identifying the at least one first device, and operation setting identification information that identifies the operation setting information; a template generating unit that generates template information on which the operation setting information is based, the template information including the model information and the operation content information included in the operation setting information, and the operation setting identification information; a device information acquisition unit that acquires device information including second device identification information that identifies at least one second device and model information that indicates a type of the at least one second device; an operation setting generation unit that selects, from the second device identification information of the at least one second device, at least one second device identification information associated with model information that matches model information included in template information corresponding to the operation setting identification information included in operation setting information request information that includes the operation setting identification information and is transmitted from a terminal device and requests new generation of the operation setting information, and generates operation setting information including the at least one selected second device identification information, and the model information, the operation setting information, and the operation setting identification information included in the template information corresponding to the operation setting identification information included in the operation setting information request information; a device control unit that controls at least one second device identified by the at least one selected second device identification information based on the operation content information included in the operation setting information of the at least one second device; A program to function as a [Industrial Applicability]

[0092] The present disclosure is suitable as a control system for remotely controlling equipment from a cloud server. [Explanation of symbols]

[0093] 1,2001,3001 Cloud server, 2A,2B Terminal device, 3A,3B Device, 8 Gateway device, 101,201 CPU, 102,202 Main memory, 103,203 Auxiliary memory, 106,206 Communication unit, 109,209 Bus, 111 Device information notification unit, 112 Device information acquisition unit, 113 Scene acquisition unit, 114 Event-driven scene acquisition unit, 115 Device control unit, 116 Template generation unit, 117 Scene registration management unit, 118,2118 Scene generation unit, 119 Event-driven scene registration management unit, 120,2120 Event-driven scene generation unit, 121 Device status acquisition unit, 131,2131 Device information storage unit, 132 Scene storage unit, 133 Event-driven scene storage unit, 134,4134 Template storage unit, 135 device state storage unit, 211 device information acquisition unit, 212 display control unit, 213 scene generation unit, 214 scene notification unit, 215 event-driven scene generation unit, 216 event-driven scene notification unit, 217 scene registration unit, 218 event-driven scene registration unit, 218 control request unit, 231 device information storage unit, 232 scene storage unit, 233 event-driven scene storage unit, 2122 function determination unit, 3123 model determination unit, 3124 error notification unit, NW1 wide area network, NW21, NW22 local network

Claims

1. an operation setting acquisition unit that acquires operation setting information including model information indicating a type of at least one first device and operation content information indicating an operation content when operating the at least one first device, and first device identification information identifying the at least one first device, and operation setting identification information identifying the operation setting information; a template generating unit that generates template information on which the operation setting information is based, the template information including the model information and the operation content information included in the operation setting information and the operation setting identification information; a device information acquisition unit that acquires device information including second device identification information that identifies at least one second device and model information that indicates a type of the at least one second device; an operation setting generation unit that selects, from the second device identification information of the at least one second device, at least one second device identification information associated with model information that matches model information included in template information corresponding to the operation setting identification information included in operation setting information request information transmitted from a terminal device, the operation setting identification information including the operation setting identification information and requesting new generation of the operation setting information, and generates operation setting information of the at least one second device including the selected at least one second device identification information and the model information, the operation setting information, and the operation setting identification information included in the template information corresponding to the operation setting identification information included in the operation setting information request information; and a device control unit that controls at least one second device identified by the at least one selected second device identification information based on the operation content information included in the operation setting information of the at least one second device. Control device.

2. The operation setting information further includes condition information indicating a condition for the operation content indicated by the operation content information to be executed by the at least one first device, the template information includes the model information, the operation content information, the operation setting identification information, and the condition information, which are included in the operation setting information; The control device according to claim 1 .

3. the model information is determined based on a group to which the at least one first device and the at least one second device belong when classified based on functions of the at least one first device and the at least one second device, respectively; The control device according to claim 1 or 2.

4. The operation setting information further includes installation location information indicating an installation location of the at least one first device, the template information includes the model information, the operation content information, the operation setting identification information, and the installation location information, which are included in the operation setting information; The control device according to claim 1 or 2.

5. a function determination unit that determines whether or not a second device identified by the second device identification information selected by the operation setting generation unit has a function for executing the operation content indicated by the operation content information, the operation setting generation unit generates operation setting information including operation content information for only a second device having a function of executing an operation content indicated by the operation content information, for any of the second devices selected by the operation setting generation unit; The control device according to claim 1 or 2.

6. a model determination unit that determines whether or not at least one second device identification information associated with model information that matches model information included in template information including the operation setting identification information included in operation setting information request information that includes the operation setting identification information transmitted from the terminal device and requests new generation of operation setting information can be selected from the second device identification information of the second device; and an error notification unit that generates error information and transmits the error information to the terminal device when it is determined that the at least one second device identification information cannot be selected. The control device according to claim 1 or 2.

7. an operation setting acquisition unit that acquires operation setting information including model information indicating a type of at least one first device and operation content information indicating an operation content when operating the at least one first device, and first device identification information identifying the at least one first device, and operation setting identification information identifying the operation setting information; a template generating unit that generates template information on which the operation setting information is based, the template information including the model information and the operation content information included in the operation setting information and the operation setting identification information; a device information acquisition unit that acquires device information including second device identification information that identifies at least one second device and model information that indicates a type of the at least one second device; a terminal device having an input unit, which generates operation setting information request information including the operation setting identification information input by a user via the input unit and requesting the generation of new operation setting information; an operation setting generation unit that selects, from the second device identification information of the at least one second device, at least one second device identification information associated with model information that matches model information included in template information corresponding to the operation setting identification information included in operation setting information request information transmitted from the terminal device, the operation setting identification information including the operation setting identification information and requesting new generation of the operation setting information, and generates operation setting information of the at least one second device including the selected at least one second device identification information and the model information, the operation setting information, and the operation setting identification information included in the template information corresponding to the operation setting identification information included in the operation setting information request information; and a device control unit that controls at least one second device identified by the at least one selected second device identification information based on the operation content information included in the operation setting information of the at least one second device. Control system.

8. the terminal device has a display unit and an input unit, and in a state in which an operation setting notification image for notifying a user of the contents of the operation of the second device is formed based on the operation setting information and displayed on the display unit, when the user performs an operation setting change operation on the input unit to change the operation setting information whose contents are displayed in the operation setting notification image, thereby performing an operation setting registration operation for newly registering the changed operation setting information, the terminal device generates operation setting registration request information including the changed operation setting information and the operation setting identification information, An operation setting registration unit that, when receiving the operation setting registration request information, extracts the operation setting information included in the received operation setting registration request information, the device control unit controls at least one second device identified by the selected at least one second device identification information based on operation content information included in the extracted operation setting information; 8. The control system of claim 7.

9. A step in which a control device acquires operation setting information including model information indicating a type of at least one first device and operation content information indicating an operation content when operating the at least one first device, and first device identification information identifying the at least one first device, and operation setting identification information identifying the operation setting information; a step of generating template information on which the operation setting information is based, the template information including the model information and the operation content information included in the operation setting information, and the operation setting identification information, by the control device; The control device acquires device information including second device identification information for identifying at least one second device and model information indicating a type of the at least one second device; the control device selects, from the second device identification information of the at least one second device, at least one second device identification information associated with model information that matches model information included in template information corresponding to the operation setting identification information included in operation setting information request information that includes the operation setting identification information and is transmitted from a terminal device and requests new generation of the operation setting information, and generates operation setting information including the at least one selected second device identification information, and the model information, the operation setting information, and the operation setting identification information included in the template information corresponding to the operation setting identification information included in the operation setting information request information; and controlling, by the control device, at least one second device identified by the selected at least one second device identification information based on the operation content information included in the operation setting information of the at least one second device. Control methods.

10. Computer, an operation setting acquisition unit that acquires operation setting information including model information indicating a type of at least one first device and operation content information indicating an operation content when operating the at least one first device, and first device identification information identifying the at least one first device, and operation setting identification information identifying the operation setting information; a template generating unit that generates template information on which the operation setting information is based, the template information including the model information and the operation content information included in the operation setting information, and the operation setting identification information; a device information acquiring unit that acquires device information including second device identification information that identifies at least one second device and model information that indicates a type of the at least one second device; an operation setting generation unit which selects, from the second device identification information of the at least one second device, at least one second device identification information associated with model information that matches model information included in template information corresponding to the operation setting identification information included in operation setting information request information transmitted from a terminal device, the operation setting identification information including the operation setting identification information and requesting new generation of the operation setting information, and generates operation setting information including the at least one selected second device identification information, and the model information, the operation setting information, and the operation setting identification information included in the template information corresponding to the operation setting identification information included in the operation setting information request information; a device control unit that controls at least one second device identified by the at least one selected second device identification information based on the operation content information included in the operation setting information of the at least one second device; A program to function as a

Images