Control system, scheduling method, and program

Abstract

To make it easy for a user to understand which equipment operates when combining scene-based control and schedule-based control.SOLUTION: In a control system, a scene information storage unit 121 stores scene information that defines at least one device and at least one operation to be performed by the at least one device. A schedule storage unit 122 stores a schedule in which at least one operation determined by the scene information stored in the scene information storage unit 121 is executed. A device schedule acquisition unit 115 acquires a device schedule that is a combination of at least one device and a schedule time from among the schedules stored in the schedule storage unit 122.SELECTED DRAWING: Figure 3

Description

Technical Field

[0001] The present disclosure relates to a control system, a schedule management method, and a program.

Background Art

[0002] A technique for controlling the operation of a device based on a scene control file describing the control content for each device is known (see, for example, Patent Document 1).

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] In a control system that controls a device using a scene as described above, when combining scene-based control and schedule-based control, there is a problem that it is difficult for the user to understand which device operates when.

[0005] The present disclosure has been made in view of the above circumstances, and an object thereof is to provide a control system and the like that can make it easy for the user to understand which device operates when in the case of combining scene-based control and schedule-based control.

Means for Solving the Problems

[0006] To achieve the above object, the control system according to the present disclosure First aspect is a scene information storage unit that stores scene information defining at least one device and at least one operation to be executed on the at least one device, A schedule storage unit that stores a schedule for executing at least one operation determined by the scene information stored in the scene information storage unit, A device schedule acquisition unit acquires a device schedule, which is a combination of at least one device and a scheduled time, from among the schedules stored in the schedule storage unit. An input receiving unit that receives input to update at least some of the scene information among the multiple scene information stored in the aforementioned scene information storage unit, A duplication determination unit determines, based on the equipment schedule acquired by the equipment schedule acquisition unit, whether or not a schedule overlap for the same equipment occurs in the schedule stored in the schedule storage unit due to the updating of at least some of the scene information, Equipped with 、 The duplicate determination unit determines whether there is a schedule overlap for the same device between a schedule in which at least one operation determined by at least some of the scene information is executed after the input reception unit receives an update input, and the schedules stored in the schedule storage unit other than the schedules for at least some of the scene information that are the target of the update. To achieve the above objective, a second aspect of the control system relating to this disclosure is: A scene information storage unit that stores scene information defining at least one device and at least one operation to be performed by the at least one device, A schedule storage unit that stores a schedule for executing at least one operation determined by the scene information stored in the scene information storage unit, A device schedule acquisition unit acquires a device schedule, which is a combination of at least one device and a scheduled time, from among the schedules stored in the schedule storage unit. An input receiving unit that receives input to register a new schedule to the schedule storage unit, A control system comprising: a duplication determination unit that determines, based on the equipment schedule acquired by the equipment schedule acquisition unit, whether or not a schedule duplication for the same equipment occurs in the schedule stored in the schedule storage unit as a result of the registration of the new schedule, When the input receiving unit receives input to register the new schedule, it receives the selection of the equipment or scene information to which the new schedule applies, and the input of the time of the new schedule. The control system is When the input receiving unit receives the input of the time, the display control unit further includes, based on the equipment schedule for the time acquired by the equipment schedule acquisition unit, a display control unit that excludes equipment to be operated at the time or scene information including equipment to be operated at the time from the candidates for equipment or scene information to be targeted for the new schedule, and displays it. The input receiving unit accepts the selection of equipment or scene information to be the target of the new schedule from among the candidates displayed by the display control unit. [Effects of the Invention]

[0007] According to this disclosure, a device schedule is obtained from among the schedules in which at least one operation defined by the scene information is performed, which is a combination of at least one device and a scheduled time. Therefore, when combining scene-based control and schedule-based control, it is possible to make it easy for the user to understand which devices are operating and when. [Brief explanation of the drawing]

[0008] [Figure 1] Diagram showing the overall configuration of the control system according to Embodiment 1. [Figure 2] Block diagram showing the hardware configuration of the cloud server and terminal device according to Embodiment 1 [Figure 3] Block diagram showing the functional configuration of the control system according to Embodiment 1 [Figure 4] Figure showing an example of information stored in the scene information storage unit according to Embodiment 1 [Figure 5] Figure showing an example of a device selection screen displayed on the terminal device according to Embodiment 1 [Figure 6] Figure showing an example of an operation specification screen displayed on the terminal device according to Embodiment 1 [Figure 7] Figure showing an example of information stored in the schedule storage unit according to Embodiment 1 [Figure 8] Figure showing an example of a schedule display screen displayed on the terminal device according to Embodiment 1 [Figure 9] Figure showing an example of a schedule setting screen displayed on the terminal device according to Embodiment 1 [Figure 10] Figure showing an example of a scene selection screen displayed on the terminal device according to Embodiment 1 [Figure 11] Figure showing an example of a device schedule obtained from the schedule storage unit according to Embodiment 1 [Figure 12] Figure showing an example of a device schedule display screen displayed on the terminal device according to Embodiment 1 [Figure 13] Sequence diagram showing the flow of scene information registration process, schedule registration process and schedule acquisition process executed by the control system according to Embodiment 1 [Figure 14] Flowchart showing the flow of device control process executed by the cloud server according to Embodiment 1 [Figure 15] Sequence diagram showing the flow of device schedule acquisition process executed by the control system according to Embodiment 1 [Figure 16] Block diagram showing the functional configuration of the control system according to Embodiment 2 [Figure 17] Sequence diagram showing the flow of schedule registration process executed by the control system according to Embodiment 2 [Figure 18] Figure showing an example of a device selection screen displayed on the terminal device according to Embodiment 5 [Figure 19]This figure shows an example of a scene selection screen displayed on a terminal device according to Embodiment 5. [Modes for carrying out the invention]

[0009] The embodiments will be described in detail below with reference to the drawings. In the drawings, the same or corresponding parts are denoted by the same reference numerals.

[0010] (Embodiment 1) Figure 1 shows the overall configuration of the control system according to Embodiment 1. The control system is capable of remotely controlling multiple devices 3 installed inside building H from outside building H.

[0011] As shown in Figure 1, the control system according to Embodiment 1 comprises a cloud server 1, a terminal device 2, and a plurality of devices 3. The plurality of devices 3 are installed inside a building H. The building H is, for example, a detached house, an apartment building, an office building, a commercial facility, a factory, etc.

[0012] Each of the multiple devices 3 is a device that is controlled by the control system. Specifically, each of the multiple devices 3 is an electrical device such as an air conditioning unit that provides air conditioning to the building H, a ventilation unit that provides ventilation to the building H, or a water heater that heats water.

[0013] Each of the multiple devices 3 is connected to an operating device such as a remote control or wall switch, although this is not shown in the diagram. A user inside building H can input commands to the devices 3, such as starting and stopping operation and adjusting the intensity of operation, by operating the operating device. Operating the devices 3 using the operating device is called "local operation." In contrast, when a user operates the devices 3 remotely using a terminal device 2, it is called "remote operation."

[0014] Multiple devices 3, though not shown in the diagram, are each connected to a local network NW2 constructed within building H via a communication adapter. Local network NW2 is connected to wide area network NW1 via a broadband router (BBR) 5. Local network NW2 is, for example, a wired LAN (Local Area Network), wireless LAN, or ECHONET Lite (registered trademark) network. Wide area network NW1 is, for example, the internet.

[0015] Cloud server 1 and terminal device 2 can communicate with each other via the wide-area network NW1. Cloud server 1 can communicate with multiple devices 3 via the wide-area network NW1 and the local network NW2.

[0016] Cloud Server 1 is a device that manages the control system, and specifically, it is a server that provides resources in cloud computing. As shown in Figure 2, Cloud Server 1 comprises a control unit 11, a storage unit 12, and a communication unit 15.

[0017] The control unit 11 comprises a CPU (Central Processing Unit), ROM (Read Only Memory), and RAM (Random Access Memory). The CPU, also called a central processing unit, central computing unit, processor, microprocessor, or microcomputer, functions as a central computing unit that executes processing and calculations related to the control of the cloud server 1. In the control unit 11, the CPU reads programs and data stored in ROM and uses RAM as a work area to comprehensively control the cloud server 1.

[0018] The storage unit 12 is equipped with non-volatile memory such as flash memory, EPROM (Erasable Programmable ROM), EEPROM (Electrically Erasable Programmable ROM), and hard disk, and plays the role of a so-called secondary storage device or auxiliary storage device. The storage unit 12 stores programs and data used by the control unit 11 for various processing. It also stores data generated or acquired by the control unit 11 through various processing.

[0019] The communication unit 15 is equipped with a communication interface for the cloud server 1 to communicate with external devices via the wide-area network NW1. The communication unit 15 sends and receives various information between the terminal device 2 and multiple devices 3 via the wide-area network NW1.

[0020] Terminal device 2 is a terminal that can be operated by a user located outside of building H. Terminal device 2 is, for example, a smartphone, a tablet, or a personal computer. As shown in Figure 2, terminal device 2 comprises a control unit 21, a storage unit 22, an input unit 23, a display unit 24, and a communication unit 25.

[0021] The control unit 21 includes a CPU, ROM, and RAM. The CPU, also called a central processing unit, central computing unit, processor, microprocessor, or microcomputer, functions as a central computing unit that performs processing and calculations related to the control of the terminal device 2. In the control unit 21, the CPU reads programs and data stored in ROM and uses RAM as a work area to comprehensively control the terminal device 2.

[0022] The storage unit 22 is equipped with non-volatile semiconductor memory such as flash memory, EPROM, or EEPROM, and serves as a so-called secondary storage device or auxiliary storage device. The storage unit 22 stores programs and data used by the control unit 21 for various processing tasks. It also stores data generated or acquired by the control unit 21 through various processing tasks.

[0023] The input unit 23 is equipped with input devices such as a keyboard, mouse, switch, touchpad, and touch panel, and accepts operation input from the user. The user can input various instructions to the terminal device 2 by operating the input unit 23. When the input unit 23 receives an operation instruction from the user, it transmits the received operation instruction to the control unit 21.

[0024] The display unit 24 includes a display device such as an LCD (Liquid Crystal Display) panel or an organic EL (Electro-Luminescence) display. The display unit 24 is driven by a display drive circuit (not shown) and displays various images under the control of the control unit 21.

[0025] The communication unit 25 is equipped with a communication interface for the terminal device 2 to communicate with external devices. The communication unit 25 sends and receives various information to and from the cloud server 1 via the wide area network NW1.

[0026] Next, the functional configuration of the control system will be described with reference to Figure 3. As shown in Figure 3, the cloud server 1 functionally comprises a scene information management unit 111, a schedule management unit 112, an equipment control unit 113, and an equipment schedule acquisition unit 115. The terminal device 2 functionally comprises an input reception unit 211 and a display control unit 213.

[0027] Each of these functions is implemented by software, firmware, or a combination of software and firmware. The software and firmware are written as programs and stored in ROM or memory units 12,22. The CPU then implements each of these functions by executing the programs stored in ROM or memory units 12,22.

[0028] Furthermore, the cloud server 1 includes a scene information storage unit 121 and a schedule storage unit 122. These are stored in appropriate storage areas of the storage unit 12.

[0029] <Scene Information Storage Unit 121> In the cloud server 1, the scene information storage unit 121 stores scene information. Scene information is information that defines the content of scene control, which is control using scenes. Here, scene control means control that performs operations on at least one device 3 all at once. By using scene control, the user can avoid the trouble of individually selecting operations for each device 3, thereby improving user convenience when controlling the devices 3.

[0030] Specifically, scene information defines at least one device 3 and at least one operation to be performed by that device 3. When scene control is performed using a single scene information, a control command is sent to cause at least one device 3 to perform the at least one operation defined in that scene information all at once. Note that "executed all at once" does not necessarily mean that the operations are performed at the same time, but may be performed at different times.

[0031] Specifically, as shown in Figure 4, the scene information storage unit 121 stores multiple scene information. Each of the multiple scene information includes a "scene name," which is the name of the scene; a "scene ID" to identify the scene information; an "operation" indicating the control content; and a "device ID" to identify the device to be controlled. For example, the MAC (Media Access Control) address assigned to each device 3 can be used as the device ID.

[0032] For example, the "Good morning" scene information defines the actions to turn on the living room air conditioner and turn off the bedroom air conditioner. The "I'm leaving" scene information defines the actions to turn off the living room air conditioner and turn off the ventilation fan.

[0033] Furthermore, a single scene information entry may define multiple devices 3 and multiple operations to be performed on each of those devices 3, or it may define a single device 3 and a single operation to be performed on that device 3. Even when a scene information entry defines a single device 3 and a single operation, combining the device 3 and the operation into a single scene information entry can improve user convenience when controlling the device 3.

[0034] Returning to Figure 3, in terminal device 2, the input receiving unit 211 receives instructions from the user to the input unit 23. For example, the user can input instructions to register new scene information in the scene information storage unit 121, and instructions to update scene information already stored in the scene information storage unit 121. The user can also input instructions to register a new schedule in the schedule storage unit 122, and instructions to update a schedule already stored in the schedule storage unit 122. The input receiving unit 211 receives such inputs from the user.

[0035] When the input receiving unit 211 receives input to register new scene information or to update scene information, the display control unit 213 displays a scene setting screen for setting the scene information on the display unit 24. Here, the scene setting screen is a screen for selecting the basic settings when generating scene information.

[0036] The display control unit 213 displays a screen as a scene setting screen for setting a combination of at least one device 3 defined in the scene information and an operation to be performed by that at least one device 3. The user can register new scene information in the scene information storage unit 121 and edit scene information already stored in the scene information storage unit 121 while viewing the scene setting screen displayed on the display unit 24.

[0037] When registering new scene information, the display control unit 213 displays a screen for selecting device 3 as the first scene setting screen. Specifically, the display control unit 213 displays a device selection screen 241 on the display unit 24, as shown in Figure 5.

[0038] On the device selection screen 241, the display control unit 213 displays multiple candidates for selectable devices 3 in the scene information, such as "water heater 1", "dressing room heater 1", and "bathroom heater 1". The user operates the input unit 23 to select at least one device 3 to be included in the scene information from among the multiple candidates displayed on the device selection screen 241.

[0039] When the user selects device 3, the display control unit 213 displays a second scene setting screen, which is a screen for setting the operation to be performed by the selected device 3. For example, if device 3 "Ventilation fan 1" is selected on the device selection screen 241, the display control unit 213 displays an operation specification screen 242 on the display unit 24, as shown in Figure 6.

[0040] On the operation selection screen 242, the display control unit 213 displays several candidate operations to be performed by the selected device 3. In the example in Figure 6, the display control unit 213 displays the following as candidate operations to be performed by "ventilation fan 1": an operation to ventilate with a strong airflow labeled "Strong", an operation to ventilate with a weak airflow labeled "Weak", and an operation to stop the fan labeled "Stop". The user operates the input unit 23 to specify the operation to be performed by the selected device 3 from among the multiple candidates displayed on the operation selection screen 242.

[0041] When multiple devices 3 are selected on the device selection screen 241, the display control unit 213 displays an operation specification screen 242 for each of the selected devices 3. The display control unit 213 then receives a specification from the user for the operation to be performed on each of the selected devices 3.

[0042] Returning to Figure 3, in the cloud server 1, the scene information management unit 111 manages the registration and updating of scene information stored in the scene information storage unit 121. Specifically, when the input reception unit 211 receives input for scene information registration, the scene information management unit 111 acquires the scene information generated based on the user's input to the scene setting screen from the terminal device 2 via the communication unit 15. The scene information management unit 111 then registers the acquired scene information in the scene information storage unit 121. The registered scene information defines a combination of at least one device selected on the device selection screen 241 and at least one operation specified on the operation specification screen 242.

[0043] <Schedule memory unit 122> Returning to Figure 3, the schedule storage unit 122 stores the schedule. The schedule is information that determines the time at which the device 3 will perform an operation.

[0044] Specifically, as shown in Figure 7, the schedule storage unit 122 stores the following in association: "scheduled time," "operation" representing the content of the scheduled operation, "operation type" indicating whether the scheduled operation is a scene-based operation or an equipment operation, and "scene ID / equipment ID" for identifying the scheduled operation.

[0045] Here, if the device type is "Scene," scene control based on scene information is executed at the scheduled time. The content of the scene control is defined in the scene information storage unit 121. For example, in the schedule shown in Figure 7, two operations defined in the scene information "Good morning" are executed at 7:00. Also, two operations defined in the scene information "I'm leaving" are executed at 9:00.

[0046] In contrast, if the device type is "device operation," then at the scheduled time, a single operation by one device 3 will be performed. For example, in the schedule shown in Figure 7, at 17:00, the operation to turn on one device 3, the living room air conditioner, will be performed.

[0047] Thus, the schedule storage unit 122 stores, as schedules, a schedule that causes at least one target device 3 to execute at least one operation determined by each of the multiple scene information stored in the scene information storage unit 121, and a schedule for device operations, which are operations to be executed by one device 3 alone.

[0048] In terminal device 2, the display control unit 213 displays the schedule stored in the schedule storage unit 122 on the display unit 24. Based on user input, the display control unit 213 sends a schedule acquisition instruction from the cloud server 1. The display control unit 213 then acquires a list of schedules stored in the schedule storage unit 122 and displays it on the display unit 24.

[0049] Specifically, the display control unit 213 displays a schedule display screen 243, as shown in Figure 8, on the display unit 24. On the schedule display screen 243, the display control unit 213 displays multiple schedule names in chronological order as a list of schedules.

[0050] When the input receiving unit 211 receives input to register a new schedule or to update a schedule, the display control unit 213 displays a schedule setting screen 244 for setting the schedule on the display unit 24, as shown in Figure 9.

[0051] The display control unit 213 displays items on the schedule setting screen 244 for setting the schedule name, the schedule execution time, and the operations to be performed in the schedule. In the example in Figure 9, a schedule named "Morning Air Conditioning" is set to execute one equipment operation and one scene control at 9:00 from Monday to Friday.

[0052] When the input receiving unit 211 receives input to register a new schedule, it accepts the selection of the device 3 or scene information to which the new schedule will apply, and the input of the time for the new schedule, on the schedule setting screen 244.

[0053] To explain in more detail, when setting a schedule for equipment operation, the display control unit 213 displays the equipment selection screen 241 shown in Figure 5 and the operation specification screen 242 shown in Figure 6 on the display unit 24, similar to when setting a scene.

[0054] On the device selection screen 241, the display control unit 213 displays multiple candidate devices 3 that can be selected as targets for a new schedule. The input reception unit 211 then accepts the selection of a device 3 to be operated on at the entered time from among the multiple candidates displayed on the device selection screen 241.

[0055] On the operation specification screen 242, the display control unit 213 displays multiple candidate operations to be performed by the device 3 selected on the device selection screen 241. The input reception unit 211 then receives a specification of the operation to be performed by the selected device 3 from among the multiple candidates displayed on the operation specification screen 242.

[0056] In contrast, when setting a scene control schedule, the display control unit 213 displays a scene selection screen 245 on the display unit 24, as shown in Figure 10. On the scene selection screen 245, the display control unit 213 displays multiple candidate scene information that can be selected as the target of a new schedule. The user operates the input unit 23 to select the scene information that defines the scene control to be executed at the input time from among the multiple candidates displayed on the scene selection screen 245.

[0057] Returning to Figure 3, in the cloud server 1, the schedule management unit 112 manages the registration and updating of schedules stored in the schedule storage unit 122. Specifically, when the input reception unit 211 receives input for schedule registration, the schedule management unit 112 obtains the user's input information for the schedule setting screen 244 from the terminal device 2 via the communication unit 15. Then, the schedule management unit 112 registers the schedule based on the acquired input information in the schedule storage unit 122.

[0058] <Equipment Control Unit 113> In the cloud server 1, the equipment control unit 113 controls each of the multiple devices 3. The equipment control unit 113 controls the operation of the controlled device 3 by transmitting control commands to the controlled device 3 among the multiple devices 3 via the communication unit 15.

[0059] More specifically, the device control unit 113 controls the device 3 according to the schedule stored in the schedule storage unit 122. To explain in more detail, when the scheduled time for an operation determined by the scene information arrives, the device control unit 113 causes at least one of the target devices 3 to perform at least one of the operations determined by that scene information.

[0060] For example, in the schedule shown in Figure 7, when 7:00 arrives, which is the time when the "Good morning" scene information is defined, the equipment control unit 113 refers to the scene information storage unit 121 and identifies the combination of operations defined in the "Good morning" scene information: "Turn on the living room air conditioner" and "Turn off the bedroom air conditioner." The equipment control unit 113 then sends control commands to the living room air conditioner and the bedroom air conditioner to turn on the living room air conditioner and turn off the bedroom air conditioner.

[0061] On the other hand, when the scheduled time for an operation to be performed by one of the devices 3 arrives, the device control unit 113 instructs that device 3 to perform the operation specified in the schedule. For example, when 17:00 arrives, the time specified for the operation "Turn on the living room air conditioner" in the schedule shown in Figure 7, the device control unit 113 sends a control command to the living room air conditioner to turn it on.

[0062] Furthermore, in addition to controlling the equipment 3 based on a schedule, the equipment control unit 113 can also control the equipment 3 based on operation information received from the user at the terminal device 2. Specifically, the user can input operations such as turning on, turning off, or changing the operating mode of any of the multiple equipment 3 as remote operations into the input unit 23 of the terminal device 2.

[0063] When the input receiving unit 211 receives such an operation from the user, it transmits operation information indicating the content of the received operation to the cloud server 1 via the communication unit 25. The operation information transmitted to the cloud server 1 is supplied to the device control unit 113. When the device control unit 113 receives the operation information from the terminal device 2, it causes the target device 3 to execute the operation entered by the user based on the received operation information.

[0064] <Equipment Schedule Acquisition Unit 115> In the cloud server 1, the device schedule acquisition unit 115 acquires a device schedule from the schedules stored in the schedule storage unit 122, which is a combination of at least one device 3 and a scheduled time. Here, the device schedule is a schedule obtained by rearranging the schedules stored in the schedule storage unit 122 on a device 3 basis.

[0065] The schedules stored in the schedule storage unit 122 include the schedules of multiple devices 3 that are to be controlled, and are not grouped by individual device 3. Therefore, there is a problem in that it is difficult for the user to understand the schedules on a per-device basis.

[0066] In particular, the schedule stored in the schedule storage unit 122 defines both a schedule for an operation to be performed independently by one device 3 whose operation type is "device operation," and a schedule for at least one operation to be performed by at least one device 3 whose operation type is "scene."

[0067] When the operation type is "scene," it is difficult for the user to immediately grasp which device 3 will operate in that "scene" simply by looking at the schedule. To solve this problem of the user having difficulty understanding which device 3 will operate and when, the device schedule acquisition unit 115 generates a device schedule by combining the scheduled times in which operations will be performed for each of the multiple devices 3 from the schedules stored in the schedule storage unit 122.

[0068] To explain in more detail, the device schedule acquisition unit 115 acquires the device ID, which is the identification information of each device 3 for which a scheduled time is defined in the schedule stored in the schedule storage unit 122. Then, the device schedule acquisition unit 115 acquires the device schedule by combining the acquired device ID of each device 3 with the scheduled time.

[0069] Firstly, if the operation type in the schedule storage unit 122 is "device operation", the device schedule acquisition unit 115 acquires the device ID associated with that "device operation". Then, the device schedule acquisition unit 115 combines the acquired device ID with the schedule time associated with that device ID in the schedule storage unit 122.

[0070] Secondly, if the operation type in the schedule storage unit 122 is "scene", the device schedule acquisition unit 115 acquires the scene ID associated with that "scene". Furthermore, the device schedule acquisition unit 115 refers to the scene information storage unit 121 and acquires at least one device ID associated with the acquired scene ID. Then, the device schedule acquisition unit 115 combines each of the acquired at least one device IDs with the schedule time associated with that scene ID in the schedule storage unit 122.

[0071] In this way, the device schedule acquisition unit 115 combines the device ID and schedule time for each operation of operation type "device operation" and "scene" in the schedule storage unit 122. As a result, the device schedule acquisition unit 115 acquires the device schedule. In other words, the device schedule acquisition unit 115 acquires the device schedule from among the schedule in which at least one operation determined by the scene information stored in the schedule storage unit 122 is executed, and the schedule for an operation to be executed by a single device alone.

[0072] Specifically, as shown in Figure 11, the equipment schedule acquisition unit 115 generates information as an equipment schedule, in which "equipment ID," "scheduled time," and "operation" are associated. Here, if one equipment 3 is operated at multiple scheduled times, the equipment schedule acquisition unit 115 combines the operations corresponding to those multiple scheduled times with the single equipment ID in the equipment schedule.

[0073] For example, in the device schedule shown in Figure 11, the living room air conditioner with device ID "DEVICE_AAA" is managed by combining the following into a single device ID: it is turned ON at 7:00, turned OFF at 9:00, and turned ON again at 17:00. As a result, the device schedule acquisition unit 115 generates a device schedule, which is a schedule in which the scheduled time and operation content are grouped together for each device 3.

[0074] In terminal device 2, the display control unit 213 obtains the device schedule acquired by the device schedule acquisition unit 115 from the cloud server 1 via the communication unit 25, and displays the acquired device schedule on the display unit 24 for each device 3. Specifically, the display control unit 213 displays a device schedule display screen 246 on the display unit 24 as shown in Figure 12.

[0075] On the device schedule display screen 246, the display control unit 213 sorts and displays the complete set of device schedules for each device 3. Specifically, the display control unit 213 displays time information vertically and the names of multiple devices 3 horizontally. Then, on the device schedule display screen 246, the display control unit 213 displays whether each of the multiple devices 3 is operating at each time, listed for each device 3. This allows the user to easily check when each of the multiple devices 3 is operating and when it is not, for each device 3.

[0076] Next, with reference to Figures 13 to 15, the processing flow executed in the control system according to Embodiment 1 will be described.

[0077] First, referring to Figure 13, we will explain the flow of the scene information registration process (steps S11-S13) for registering scene information, the schedule registration process (steps S21-S23) for registering schedules, and the schedule acquisition process (steps S31-S35) for displaying schedules. The scene information registration process, schedule registration process, and schedule acquisition process are examples of the scene information registration step, schedule registration step, and schedule acquisition step, respectively.

[0078] Firstly, the scene information registration process is executed when new scene information is to be registered in the scene information storage unit 121. When the scene information registration process is started, the control unit 21 in the terminal device 2 functions as an input receiving unit 211 and accepts the registration of scene information (step S11).

[0079] Specifically, the control unit 21 displays the device selection screen 241 shown in Figure 5 and the operation specification screen 242 shown in Figure 6 as scene setting screens. Through this, the control unit 21 receives at least one device 3 and at least one operation from the user as scene information registration.

[0080] Upon receiving a request to register scene information, the control unit 21 sends the scene information to be registered to the cloud server 1 (step S12). On the cloud server 1, the control unit 11 receives the scene information sent from the terminal device 2. The control unit 11 then functions as a scene information management unit 111 and registers the received scene information in the scene information storage unit 121 (step S13). With this, the scene information registration process is completed.

[0081] Secondly, the schedule registration process is executed when registering a new schedule in the schedule storage unit 122. When the schedule registration process starts, the control unit 21 in the terminal device 2 functions as an input receiving unit 211 and accepts the registration of the schedule (step S21).

[0082] Specifically, the control unit 21 displays the schedule setting screen 244 shown in Figure 7. This allows the control unit 21 to register a new schedule by selecting the target device 3 or scene information, and by inputting the time for the new schedule.

[0083] Upon receiving a schedule registration request, the control unit 21 sends the schedule to be registered to the cloud server 1 (step S22). On the cloud server 1, the control unit 11 receives the schedule sent from the terminal device 2. The control unit 11 then functions as a schedule management unit 112 and registers the received schedule in the schedule storage unit 122 (step S23). With this, the schedule registration process is completed.

[0084] Thirdly, the schedule acquisition process is performed when the user wishes to check the schedule. When the schedule acquisition process is started, the control unit 21 in the terminal device 2 functions as an input receiving unit 211 and receives a schedule acquisition instruction from the user via the input unit 23 (step S31).

[0085] Upon receiving a schedule acquisition instruction, the control unit 21 transmits the received schedule acquisition instruction to the cloud server 1 (step S32). In the cloud server 1, when the control unit 11 receives the schedule acquisition instruction transmitted from the terminal device 2, it acquires a list of schedules from the schedule storage unit 122 (step S33).

[0086] When the schedule list is obtained, the control unit 11 sends the obtained schedule list to the terminal device 2 (step S34). In the terminal device 2, the control unit 21 receives the schedule list sent from the cloud server 1.

[0087] Upon receiving the schedule list, the control unit 21 functions as a display control unit 213 and displays the received schedule list on the display unit 24 (step S35). For example, the control unit 21 displays the schedule display screen 243 shown in Figure 8. With this, the schedule acquisition process is completed.

[0088] Next, with reference to Figure 14, the flow of the device control process performed by the device control unit 113 will be explained. The device control process is performed as needed when the cloud server 1 is in a state where it can operate normally. The device control process is an example of a device control step.

[0089] When the device control process is started, the control unit 11 in the cloud server 1 determines whether or not the scheduled time for any of the device operations stored in the schedule storage unit 122 has arrived (step S41).

[0090] When the scheduled time for equipment operation arrives (step S41; YES), the control unit 11 controls one of the target devices 3 to perform the operation specified in the schedule (step S42).

[0091] In contrast, if the scheduled time for equipment operation has not yet arrived (step S41; NO), the control unit 11 then determines whether or not the scheduled time for any scene control stored in the schedule storage unit 122 has arrived (step S43).

[0092] When the scheduled time for scene control arrives (step S43; YES), the control unit 11 acquires the target scene information from the scene information storage unit 121 (step S44). As a result, the control unit 11 identifies at least one target device 3 and at least one operation.

[0093] Upon acquiring scene information, the control unit 11 controls at least one target device 3 to perform at least one operation determined by that scene information (step S45).

[0094] If the scheduled time for an equipment operation or scene control stored in the schedule storage unit 122 has not yet arrived (step S43; NO), the control unit 11 stops processing at step S41 and waits until the scheduled time for any equipment operation or scene arrives. Then, each time the scheduled time arrives, the control unit 11 executes the equipment operation or scene control specified in the schedule.

[0095] Next, referring to Figure 15, the flow of the device schedule acquisition process will be explained. The device schedule acquisition process is executed when the user wishes to check the schedule for each device 3. The device schedule acquisition process is an example of the device schedule acquisition step.

[0096] When the equipment schedule acquisition process is started, the control unit 21 in the terminal device 2 functions as an input receiving unit 211 and receives an instruction from the user to acquire the equipment schedule via the input unit 23 (step S51).

[0097] Upon receiving an instruction to acquire the equipment schedule, the control unit 21 transmits the received instruction to acquire the equipment schedule to the cloud server 1 (step S52). In the cloud server 1, the control unit 11 receives the instruction to acquire the equipment schedule transmitted from the terminal device 2.

[0098] Upon receiving an instruction to acquire an equipment schedule, the control unit 11 functions as an equipment schedule acquisition unit 115 and acquires equipment IDs from the schedule stored in the schedule storage unit 122 (step S53). Specifically, the control unit 11 acquires equipment IDs, which are the identification information of all equipment 3 whose operation is scheduled in the schedule, regardless of whether the operation type is "equipment operation" or "scene".

[0099] Upon obtaining the device ID, the control unit 11 functions as a device schedule acquisition unit 115 and combines the acquired device ID with the schedule time (step S54). As a result, the control unit 11 obtains the device schedule shown in Figure 11, for example.

[0100] When the device schedule is acquired, the control unit 11 transmits the acquired device schedule to the terminal device 2 (step S55). In the terminal device 2, the control unit 21 receives the device schedule transmitted from the cloud server 1.

[0101] Upon receiving the device schedule, the control unit 21 functions as a display control unit 213 and displays the received device schedule on the display unit 24 (step S56). For example, the control unit 21 displays the device schedule display screen 246 shown in Figure 12. With this, the device schedule acquisition process shown in Figure 15 is completed.

[0102] As described above, the control system according to Embodiment 1 includes a scene information storage unit 121 that stores scene information defining at least one device 3 and at least one operation, and a schedule storage unit 122 that stores a schedule for executing at least one operation defined by the scene information stored in the scene information storage unit 121. The system acquires a device schedule, which is a combination of at least one device 3 and a scheduled time, from among the schedules stored in the schedule storage unit 122. This makes it easy for the user to understand which device operates and when, when scene-based control and schedule-based control are combined.

[0103] (Embodiment 2) Next, Embodiment 2 will be described. Descriptions of the same configuration and functions as in Embodiment 1 will be omitted as appropriate.

[0104] Figure 16 shows the functional configuration of the control system according to Embodiment 2. Functionally, the cloud server 1 according to Embodiment 2 further includes a duplicate detection unit 117 in addition to the parts shown in Figure 3. The function of the duplicate detection unit 117 is realized by software, firmware, or a combination of software and firmware. The software and firmware are written as programs and stored in the ROM or storage unit 12. The CPU then realizes the function of the duplicate detection unit 117 by executing the programs stored in the ROM or storage unit 12.

[0105] In terminal device 2, the input receiving unit 211 receives input to register a new schedule to the schedule storage unit 122. Schedule registration is performed based on user input to the schedule setting screen 244, similar to embodiment 1.

[0106] In the cloud server 1, when the input receiving unit 211 receives input to register a new schedule, the duplicate determination unit 117 determines, based on the equipment schedule acquired by the equipment schedule acquisition unit 115, whether or not a schedule duplication for the same equipment 3 occurs in the schedule stored in the schedule storage unit 122 due to the registration of the new schedule.

[0107] Here, schedule overlap means that two or more different schedules specify that the same device 3 should be operated at the same time. For example, if device 3 to be operated at the time entered in a new schedule is already scheduled to be operated at the same time in a schedule already registered in the schedule storage unit 122, then schedule overlap occurs.

[0108] When registering a new schedule, the user may input a schedule that overlaps with a schedule already registered in the schedule storage unit 122. To avoid such schedule overlaps, the overlap determination unit 117 determines whether or not there is a schedule overlap for the same device 3 between the new schedule and the schedules stored in the schedule storage unit 122.

[0109] Specifically, the duplicate determination unit 117 extracts equipment schedules from the equipment schedule acquisition unit 115 that match the time of the new schedule whose registration input has been received by the input reception unit 211. The duplicate determination unit 117 then determines whether or not the same equipment 3 exists between the equipment 3 specified in the new schedule and the equipment 3 specified in the extracted equipment schedule. If the duplicate determination unit 117 finds that the same equipment 3 exists, it determines that there is a schedule overlap and notifies the user accordingly.

[0110] The flow of the schedule registration process in Embodiment 2 will be explained in more detail with reference to Figure 17. The schedule registration process is executed when the user wishes to register a new schedule in the schedule storage unit 122.

[0111] When the schedule registration process is started, the control unit 21 in the terminal device 2 functions as an input receiving unit 211 and accepts the registration of the schedule (step S61). Specifically, the control unit 21 displays the schedule setting screen 244 shown in Figure 7. As a result, the control unit 21 accepts the selection of the equipment 3 or scene information to be the target of the new schedule, and the input of the time for the new schedule, as part of the schedule registration.

[0112] Upon receiving a schedule registration request, the control unit 21 sends the new schedule to be registered to the cloud server 1 (step S62). The control unit 11 receives the schedule sent from the terminal device 2 on the cloud server 1.

[0113] When a new schedule is received, the control unit 11 obtains the device ID from the received new schedule (step S63). Specifically, the control unit 11 obtains the device ID of each device 3 whose operation is scheduled in the new schedule, regardless of whether the operation type is "device operation" or "scene".

[0114] Upon obtaining the device ID, the control unit 11 retrieves a device schedule from the schedules stored in the schedule storage unit 122 that matches the time of the new schedule (step S64). Specifically, the control unit 11 functions as a device schedule acquisition unit 115 and retrieves device schedules for all times from the schedules stored in the schedule storage unit 122. The process of acquiring device schedules for all times is the same as the process by the device schedule acquisition unit 115 described in Embodiment 1. After acquiring device schedules for all times, the control unit 11 refers to the schedule time information included in the device schedule and extracts the schedule that matches the time of the new schedule from all the acquired device schedules for all times.

[0115] When a device schedule is acquired, the control unit 11 functions as a duplication determination unit 117 and determines whether there is a matching device ID between the new schedule and the acquired device schedule (step S65). If no matching device ID exists (step S65; NO), it is determined that no schedule duplication occurs. In this case, the control unit 11 functions as a schedule management unit 112 and registers the received new schedule in the schedule storage unit 122 (step S66).

[0116] If a matching device ID exists (step S65; YES), the control unit 11 sends an error message to the terminal device 2 (step S67). In the terminal device 2, when the control unit 21 receives the error message sent from the cloud server 1, it functions as a display control unit 213 and displays the received error message on the display unit 24 (step S68). As a result, the user is notified that a schedule overlap will occur and therefore a new schedule cannot be registered. With this, the schedule registration process in Embodiment 2 is completed.

[0117] Thus, in Embodiment 2, when an input for registering a new schedule is received, the duplicate determination unit 117 determines whether or not there is a schedule overlap for the same device 3 between the new schedule and the schedule stored in the schedule storage unit 122. This makes it possible to avoid schedule overlaps for the same device 3 when registering a schedule.

[0118] (Embodiment 3) Next, Embodiment 3 will be described. Descriptions of the same configurations and functions as in Embodiments 1 and 2 will be omitted as appropriate.

[0119] In Embodiment 3, the input receiving unit 211 receives input to update at least some of the schedules stored in the schedule storage unit 122. In this case, the duplication determination unit 117 determines, based on the equipment schedules acquired by the equipment schedule acquisition unit 115, whether or not the update of at least some of the schedules results in a schedule duplication for the same equipment 3 in the schedules stored in the schedule storage unit 122.

[0120] Here, updating the schedule means changing the time of a schedule already registered in the schedule storage unit 122, or changing the equipment operation or scene information specified in a registered schedule. Schedule updates, like schedule registration, are performed based on user input to the schedule setting screen 244.

[0121] When a schedule is updated, similar to the schedule registration process described in Embodiment 2, there is a possibility of schedule overlap between the updated schedule and other schedules stored in the schedule storage unit 122 that are not subject to update.

[0122] For example, if the time of a registered schedule is changed to a different time, it is possible that an operation for the same device 3 as the schedule being updated is already scheduled for the changed time in a schedule other than the one being updated, which is stored in the schedule storage unit 122. Alternatively, if the device operation or scene information in a registered schedule is changed to a different device operation or scene information, it is possible that an operation for the same device 3 as the changed device operation or scene information is already scheduled for the same time in a schedule other than the one being updated, which is stored in the schedule storage unit 122.

[0123] To avoid such schedule overlaps, the overlap determination unit 117 determines whether there is an overlap in schedules for the same device 3 between the schedule after the input reception unit 211 has received the update input and the schedules stored in the schedule storage unit 122 other than the schedule to be updated.

[0124] To explain in more detail, the equipment schedule acquisition unit 115 acquires an equipment schedule, which is a combination of at least one equipment 3 and a scheduled time, from among the schedules stored in the schedule storage unit 122, excluding the schedule to be updated.

[0125] The duplicate detection unit 117 extracts equipment schedules from the equipment schedule acquisition unit 115 that match the time of the schedule after the update input is received by the input reception unit 211. The duplicate detection unit 117 then compares the equipment IDs of the equipment 3 specified in the schedule after the update input is received with the equipment 3 specified in the extracted equipment schedule to determine whether or not identical equipment 3s exist. If the duplicate detection unit 117 determines that identical equipment 3s exist, it determines that there is a schedule overlap and notifies the user accordingly.

[0126] The flow of the schedule update process in Embodiment 3 can be similarly explained by replacing "new schedule" with "schedule after receiving update input" in Figure 17, which was described in Embodiment 2.

[0127] Thus, in Embodiment 3, when the schedule storage unit 122 receives an input to update at least some of the schedules stored in the schedule storage unit 122, the duplicate determination unit 117 determines whether there is a schedule overlap for the same device 3 between the schedule after receiving the update input and the schedules stored in the schedule storage unit 122 other than the schedule to be updated. This makes it possible to avoid schedule overlaps for the same device 3 when updating schedules.

[0128] (Embodiment 4) Next, Embodiment 4 will be described. Descriptions of configurations and functions similar to those in Embodiments 1 to 3 will be omitted as appropriate.

[0129] In Embodiment 4, the input receiving unit 211 receives input to update at least some of the scene information stored in the scene information storage unit 121. In this case, the duplication determination unit 117 determines, based on the device schedule acquisition unit 115, whether the update of at least some of the scene information results in a schedule duplication for the same device 3 in the schedule stored in the schedule storage unit 122.

[0130] Here, updating the scene information means changing one of the at least one device 3 defined in any of the scene information already registered in the scene information storage unit 121 to another device 3, or adding a new device 3 to the at least one device 3 defined in the scene information.

[0131] When scene information is updated, if the scene control based on that scene information is included in the schedule stored in the schedule storage unit 122, schedule duplication may occur. For example, if a schedule other than the one with the updated scene information among the schedules stored in the schedule storage unit 122 specifies that an operation should be performed at the same time on the same device 3 as the device 3 that has been changed or added to the updated scene information, schedule duplication will occur.

[0132] To avoid such schedule overlaps, the overlap determination unit 117 determines whether there is a schedule overlap for the same device 3 between the schedule in which at least one operation determined by the scene information after receiving the update input from the input reception unit 211 is executed, and the schedules stored in the schedule storage unit 122 other than the scene information to be updated.

[0133] To explain in more detail, the equipment schedule acquisition unit 115 acquires an equipment schedule, which is a combination of at least one equipment 3 and a scheduled time, from among the schedules stored in the schedule storage unit 122, excluding the scene information to be updated. Here, the schedules excluding the scene information to be updated are schedules that are not changed by the update of the scene information that has been received as input, and specifically correspond to schedules in which scene control by scene information other than the scene information to be updated is defined, or schedules in which equipment operation is defined.

[0134] The duplicate detection unit 117 extracts equipment schedules from the equipment schedule acquisition unit 115 that match the time of a schedule in which at least one operation defined by the scene information to be updated is performed. The duplicate detection unit 117 then compares the equipment IDs of the equipment 3 that has been changed or added in the scene information after the update input has been received with the equipment 3 defined in the extracted equipment schedule to determine whether or not identical equipment 3 exists. If, as a result of the determination, identical equipment 3 exists, the duplicate detection unit 117 determines that there is a schedule overlap and notifies the user accordingly.

[0135] The flow of the scene information update process in Embodiment 4 can be similarly explained by replacing "new schedule" with "scene information after receiving update input" in Figure 17, which was described in Embodiment 2.

[0136] Thus, in Embodiment 4, when the Scene Information Storage Unit 121 receives an input to update at least some of the scene information stored in the Scene Information Storage Unit 121, the Duplication Determination Unit 117 determines whether there is a schedule overlap for the same device 3 between the schedule in which at least one operation determined by the scene information after receiving the update input is executed and the schedules stored in the Schedule Storage Unit 122 that do not include the scene information to be updated. This makes it possible to avoid schedule overlaps for the same device 3 when updating scene information.

[0137] (Embodiment 5) Next, Embodiment 5 will be described. Descriptions of configurations and functions similar to those in Embodiments 1 to 4 will be omitted as appropriate.

[0138] In Embodiment 5, when the input receiving unit 211 receives input to register a new schedule, it receives the selection of the device 3 or scene information to be the target of the new schedule, and the input of the time of the new schedule. Specifically, when the input to register a new schedule is received, the display control unit 213 displays the schedule setting screen 244, the device selection screen 241, and the scene selection screen 245 on the display unit 24, similar to Embodiment 1.

[0139] On the schedule setting screen 244, in the "Time" field, the input reception unit 211 accepts the user's input for the time of the new schedule. Furthermore, when setting a new schedule for equipment operation, the input reception unit 211 accepts the selection of the equipment 3 to be the target of the new schedule on the equipment selection screen 241. On the other hand, when setting a new schedule for scene control, the input reception unit 211 accepts the selection of the scene information to be the target of the new schedule on the scene selection screen 245.

[0140] In Embodiment 5, if the input receiving unit 211 receives input for a new schedule time before selecting equipment 3 or scene information on the schedule setting screen 244, the equipment schedule acquisition unit 115 acquires the equipment ID of equipment 3 that will be operated at the time of the newly entered schedule from among the equipment schedules acquired.

[0141] The device ID obtained here corresponds to the device ID of device 3 that is already scheduled to perform some operation at the time of the new schedule. In other words, the input receiving unit 211 identifies device 3 that, if selected in the new schedule, would result in a schedule overlap.

[0142] The display control unit 213 excludes the device 3 indicated by the acquired device ID on the device selection screen 241 and the scene selection screen 245 from the list of candidates for device 3 that can be selected for the new schedule, as selecting it would result in a schedule overlap. As a result, the display control unit 213 displays, in the schedule stored in the schedule storage unit 122, devices 3 other than the device 3 whose operation will be performed at the time of the new schedule, or scene information other than the scene information containing the device 3 whose operation will be performed at the time of the new schedule, as candidates for device 3 or scene information that can be targeted for the new schedule. In other words, based on the device schedule for the time of the new schedule acquired by the device schedule acquisition unit 115, the display control unit 213 excludes and displays device 3 whose operation will be performed at the time of the new schedule, or scene information containing the device 3 whose operation will be performed at the time of the new schedule, from the list of candidates for device 3 or scene information that can be targeted for the new schedule.

[0143] Specifically, as shown in Figure 18, the display control unit 213 displays the equipment 3 indicated by the acquired equipment ID among multiple candidates for equipment 3 that are the target of the new schedule on the equipment selection screen 241 as an unselectable candidate. In this example, since equipment 3 "Water heater 1" is unselectable, it is displayed in a different color from the other selectable equipment 3s. In contrast, the display control unit 213 displays the equipment 3 other than the equipment 3 indicated by the acquired equipment ID among multiple candidates for equipment 3 as selectable candidates.

[0144] Alternatively, as shown in Figure 19, the display control unit 213 displays, on the scene selection screen 245, as an unselectable candidate, scene information that includes device 3, indicated by the acquired device ID, as the target of operation, among multiple candidate scene information for the new schedule. In contrast, the display control unit 213 displays, as selectable candidates, scene information that does not include device 3, indicated by the acquired device ID, as the target of operation, among multiple candidate scene information.

[0145] The input receiving unit 211 accepts the selection of a new device 3 or scene information to be scheduled from among the selectable device 3 candidates displayed on the device selection screen 241 or the selectable scene information candidates displayed on the scene selection screen 245. This makes it possible in Embodiment 5 to avoid scheduling overlaps for the same device 3 at the time of schedule registration, before the user selects the device 3 or scene information.

[0146] (modified version) The embodiments have been described above, but it is possible to combine the embodiments or modify or omit them as appropriate.

[0147] For example, in the above embodiment, the cloud server 1 and the terminal device 2 had the functions of the parts shown in Figure 3 or Figure 16. However, the functions of the parts of the control system may be provided in devices other than the cloud server 1 or the terminal device 2. For example, the scene information storage unit 121 or the schedule storage unit 122 may be provided in a device outside the cloud server 1.

[0148] Furthermore, the functions of the device schedule acquisition unit 115 and the duplicate determination unit 117 may be provided in the terminal device 2. If the terminal device 2 is equipped with the function of the device schedule acquisition unit 115, the device schedule acquisition unit 115 acquires a list of schedules stored in the schedule storage unit 122 from the cloud server 1. Then, as described above, the device schedule acquisition unit 115 acquires the device ID from the schedule list and performs a process to combine the device ID and the schedule time, thereby acquiring the device schedule from the acquired schedule list.

[0149] In the above embodiment, the control unit 11 of the cloud server 1 functioned as the respective components shown in Figure 3 by having the CPU execute a program stored in ROM or storage unit 12. Similarly, the control unit 21 of the terminal device 2 functioned as the respective components shown in Figure 3 by having the CPU execute a program stored in ROM or storage unit 22. However, the control units 11 and 21 may be dedicated hardware. Dedicated hardware includes, for example, single circuits, complex circuits, programmed processors, ASICs (Application Specific Integrated Circuits), FPGAs (Field-Programmable Gate Arrays), or combinations thereof. If the control units 11 and 21 are dedicated hardware, the functions of each component may be implemented with separate hardware, or the functions of each component may be implemented together with a single piece of hardware.

[0150] Furthermore, some of the functions of each part may be implemented by dedicated hardware, while other parts may be implemented by software or firmware. In this way, the control units 11 and 21 can implement the above-mentioned functions by hardware, software, firmware, or a combination thereof.

[0151] It is also possible to make an existing computer, such as a personal computer or information terminal device, function as cloud server 1 or terminal device 2 by applying a program that defines the operation of cloud server 1 or terminal device 2 to that computer.

[0152] Furthermore, the method of distribution of such programs is optional. For example, they may be distributed by storing them on computer-readable storage media such as CD-ROMs (Compact Disk ROMs), DVDs (Digital Versatile Disks), MOs (Magneto Optical Disks), or memory cards, or they may be distributed via communication networks such as the Internet.

[0153] This disclosure allows for various embodiments and modifications without departing from the broad spirit and scope of this disclosure. Furthermore, the embodiments described above are for illustrative purposes only and do not limit the scope of this disclosure. In other words, the scope of this disclosure is indicated by the claims, not by the embodiments. Various modifications made within the scope of the claims and the equivalent significance of the disclosure are considered to be within the scope of this disclosure. [Explanation of Symbols]

[0154] 1 Cloud server, 2 Terminal device, 3 Equipment, 5 BBR, 11,21 Control unit, 12,22 Storage unit, 15,25 Communication unit, 23 Input unit, 24 Display unit, 111 Scene information management unit, 112 Schedule management unit, 113 Equipment control unit, 115 Equipment schedule acquisition unit, 117 Duplicate detection unit, 121 Scene information storage unit, 122 Schedule storage unit, 211 Input reception unit, 213 Display control unit, 241 Equipment selection screen, 242 Operation specification screen, 243 Schedule display screen, 244 Schedule setting screen, 245 Scene selection screen, 246 Equipment schedule display screen, H Building, NW1 Wide area network, NW2 Local network

Claims

1. A scene information storage unit that stores scene information defining at least one device and at least one operation to be performed by the at least one device, A schedule storage unit that stores a schedule for executing at least one operation determined by the scene information stored in the scene information storage unit, A device schedule acquisition unit acquires a device schedule, which is a combination of at least one device and a scheduled time, from among the schedules stored in the schedule storage unit. An input receiving unit that receives input to update at least some of the scene information among the multiple scene information stored in the aforementioned scene information storage unit, The system includes a duplication determination unit that determines, based on the equipment schedule acquired by the equipment schedule acquisition unit, whether or not a schedule overlap for the same equipment occurs in the schedule stored in the schedule storage unit due to the updating of at least some of the scene information, The duplicate determination unit determines whether there is a schedule overlap for the same device between a schedule in which at least one operation determined by at least some of the scene information is executed after the input reception unit receives an update input, and the schedules stored in the schedule storage unit other than the schedules of the at least some of the scene information that are the target of the update. Control system.

2. A scene information storage unit that stores scene information defining at least one device and at least one operation to be performed by the at least one device, A schedule storage unit that stores a schedule for executing at least one operation determined by the scene information stored in the scene information storage unit, A device schedule acquisition unit acquires a device schedule, which is a combination of at least one device and a scheduled time, from among the schedules stored in the schedule storage unit. An input receiving unit that receives input to register a new schedule to the schedule storage unit, A control system comprising: a duplication determination unit that determines, based on the equipment schedule acquired by the equipment schedule acquisition unit, whether or not a schedule duplication for the same equipment occurs in the schedule stored in the schedule storage unit as a result of the registration of the new schedule, When the input receiving unit receives input to register the new schedule, it receives the selection of the equipment or scene information to which the new schedule applies, and the input of the time of the new schedule. The control system is When the input receiving unit receives the input of the time, the display control unit further includes, based on the equipment schedule for the time acquired by the equipment schedule acquisition unit, a display control unit that excludes equipment to be operated at the time or scene information including equipment to be operated at the time from the candidates for equipment or scene information to be targeted for the new schedule, and displays it. The input receiving unit receives the selection of equipment or scene information to be the target of the new schedule from among the candidates displayed by the display control unit. Control system.

3. The system further includes a display unit that displays the equipment schedule acquired by the equipment schedule acquisition unit for each of the equipment. The control system according to claim 1 or 2.

4. The device control unit further comprises a device control unit that causes the device to perform the at least one operation specified in the scene information according to the schedule stored in the schedule storage unit. The control system according to any one of claims 1 to 3.

5. The input receiving unit receives input to register a new schedule to the schedule storage unit. The duplicate determination unit determines whether or not there is a schedule overlap for the same device between the new schedule and the schedule stored in the schedule storage unit. The control system according to any one of claims 1 to 4.

6. The input receiving unit receives input to update at least some of the schedules stored in the schedule storage unit. The duplicate determination unit determines whether there is a schedule overlap for the same device between at least some of the schedules after the input reception unit has received the update input and the schedules stored in the schedule storage unit other than the at least some of the schedules that are the target of the update. The control system according to any one of claims 1 to 5.

7. The aforementioned schedule storage unit further stores schedules for operations to be performed by a single device independently. The equipment schedule acquisition unit acquires the equipment schedule from among the schedules stored in the schedule storage unit, which include a schedule for executing at least one operation determined by the scene information, and a schedule for an operation to be performed by one equipment unit independently. The control system according to any one of claims 1 to 6.

8. A scene information registration step of registering scene information that defines at least one device and at least one operation to be performed by the at least one device, A schedule registration step for registering a schedule in which at least one operation defined by the scene information registered in the scene information registration step is performed, A device schedule acquisition step, which acquires a device schedule that is a combination of at least one device and a schedule time from among the schedules registered in the schedule registration step, An input receiving step that receives input to update at least some of the scene information among the multiple scene information registered in the aforementioned scene information registration step, The system includes a duplication determination step which determines, based on the equipment schedule acquired in the equipment schedule acquisition step, whether or not a schedule overlap for the same equipment occurs in the schedule registered in the schedule registration step due to the update of at least some of the scene information, In the duplicate determination step, it is determined whether there is a schedule overlap for the same device between a schedule in which at least one operation determined by at least some of the scene information is executed after the update input is received in the input acceptance step, and the schedules registered in the schedule registration step other than the schedules of at least some of the scene information that are the target of the update. Schedule management methods.

9. A scene information registration step of registering scene information that defines at least one device and at least one operation to be performed by the at least one device, A schedule registration step for registering a schedule in which at least one operation defined by the scene information registered in the scene information registration step is performed, A device schedule acquisition step, which acquires a device schedule that is a combination of at least one device and a schedule time from among the schedules registered in the schedule registration step, An input receiving step that receives input to register a new schedule for the schedule registered in the schedule registration step, A schedule management method including: a duplication determination step which determines whether the registration of the new schedule results in a schedule duplication for the same equipment in the schedule registered in the schedule registration step, based on the equipment schedule acquired in the equipment schedule acquisition step; In the input acceptance step, when accepting input to register the new schedule, the selection of the equipment or scene information to which the new schedule applies, and the input of the time of the new schedule are accepted. The aforementioned schedule management method is: If the input of the time is received in the input acceptance step, the method further includes a display step in which, based on the equipment schedule for the time obtained in the equipment schedule acquisition step, equipment that will be operated at the time, or scene information including equipment that will be operated at the time, are excluded from the candidates for equipment or scene information that will be subject to the new schedule, and displayed. In the input acceptance step, the selection of equipment or scene information to be the target of the new schedule is accepted from among the candidates displayed in the display step. Schedule management methods.

10. A scene information storage unit that stores scene information defining at least one device and at least one operation to be performed by the at least one device, A schedule storage unit that stores a schedule for executing at least one operation determined by the scene information stored in the scene information storage unit, A computer equipped with, A device schedule acquisition unit acquires a device schedule, which is a combination of at least one device and a scheduled time, from among the schedules stored in the schedule storage unit. An input receiving unit that receives input to update at least some of the scene information among the multiple scene information stored in the aforementioned scene information storage unit, The system functions as a duplication determination unit that determines, based on the equipment schedule acquired by the equipment schedule acquisition unit, whether or not a schedule overlap for the same equipment occurs in the schedule stored in the schedule storage unit due to the update of at least some of the scene information, The duplicate determination unit determines whether there is a schedule overlap for the same device between a schedule in which at least one operation determined by at least some of the scene information is executed after the input reception unit receives an update input, and the schedules stored in the schedule storage unit other than the schedules of the at least some of the scene information that are the target of the update. program.

11. A scene information storage unit that stores scene information defining at least one device and at least one operation to be performed by the at least one device, A schedule storage unit that stores a schedule for executing at least one operation determined by the scene information stored in the scene information storage unit, A computer equipped with, A device schedule acquisition unit acquires a device schedule, which is a combination of at least one device and a scheduled time, from among the schedules stored in the schedule storage unit. An input receiving unit that receives input for registering a new schedule to the schedule storage unit, A program that functions as a duplication determination unit, which determines whether or not a schedule overlap for the same device occurs in the schedule stored in the schedule storage unit as a result of the registration of the new schedule, based on the device schedule acquired by the device schedule acquisition unit, When the input receiving unit receives input to register the new schedule, it receives the selection of the equipment or scene information to which the new schedule applies, and the input of the time of the new schedule. The aforementioned program, the computer, When the input receiving unit receives the input of the time, it further functions as a display control unit that, based on the equipment schedule for the time acquired by the equipment schedule acquisition unit, excludes equipment that will be operated at the time or scene information including equipment that will be operated at the time from the candidates for equipment or scene information that will be targeted for the new schedule and displays it. The input receiving unit receives the selection of equipment or scene information to be the target of the new schedule from among the candidates displayed by the display control unit. program.

Images