Control system, schedule management method and program

Abstract

To provide a control system capable of improving user convenience when a user performs an operation to generate a work schedule of a virtual apparatus, a schedule management method and a program.SOLUTION: A cloud server 1 of a control system comprises: a schedule generation section 112 which identifies an apparatus 3 for realizing a virtual apparatus subjected to generating a work schedule and generates apparatus schedule information indicating a work schedule of each apparatus 3 for realizing the target virtual apparatus based on virtual apparatus schedule information indicating a work schedule regarding the target virtual apparatus and the identified apparatus 3; and an apparatus control section 115 which controls the apparatus 3 on the basis of the apparatus schedule information.SELECTED DRAWING: Figure 3

Description

[Technical Field]

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

[0002] A control system has been proposed that generates virtual device state information having properties different from the device states and environmental parameters, based on method information defined for a virtual device, from the device states of each of multiple devices used by a user and environmental parameters that indicate the environment in which each of the multiple devices is installed and are detected by each of the multiple devices (see, for example, Patent Document 1). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Patent No. 7221467 Summary of the Invention [Problem to be solved by the invention]

[0004] However, in a control system such as that described in Patent Document 1, when a user registers an operation schedule for a virtual device, if the user needs to separately register the operation schedule for each of at least one actual device that realizes the virtual device, the user may find the task of registering the operation schedule for the virtual device troublesome.

[0005] The present disclosure has been made in consideration of the above reasons, and aims to provide a control system, a schedule management method, and a program that can improve user convenience when the user performs operations to generate an operation schedule for a virtual device. [Means for solving the problem]

[0006] In order to achieve the above object, the control system according to the present disclosure comprises: a schedule generating unit that identifies at least one device that realizes a virtual device for which an operation schedule is to be generated, and generates device schedule information that indicates the operation schedule of each of the at least one device that realizes the target virtual device based on virtual device schedule information that indicates the operation schedule of the target virtual device and the identified at least one device; and a device control unit that controls the at least one device based on the device schedule information. [Effects of the Invention]

[0007] According to the present disclosure, a schedule generation unit identifies at least one device that realizes a virtual device for which an operation schedule is to be generated and the operation status of each of the at least one device, and generates device schedule information that indicates the operation schedule of each of the at least one device that realizes the target virtual device based on virtual device schedule information that indicates the operation schedule for the target virtual device and the operation information of the identified at least one device and each of the at least one device. As a result, a user only needs to perform an operation to generate an operation schedule for the virtual device for which an operation schedule is to be registered, and an operation schedule for at least one actual device that realizes the target virtual device is generated, thereby eliminating the need to perform an operation to generate an operation schedule for each of the at least one actual device that realizes the target virtual device. Therefore, the operation for generating an operation schedule for a virtual device is simplified for the user, and the user's convenience when performing an operation to generate an operation schedule for a virtual device is improved. [Brief explanation of the drawings]

[0008] [Figure 1] FIG. 1 is a diagram showing the overall configuration of a control system according to an embodiment. [Figure 2] FIG. 1 is a block diagram showing the hardware configuration of a cloud server and a terminal device according to an embodiment. [Figure 3]FIG. 1 is a block diagram showing a functional configuration of a control system according to an embodiment. [Figure 4] FIG. 10 is a diagram showing an example of information stored in a device schedule storage unit according to an embodiment; [Figure 5] FIG. 10 is a diagram illustrating an example of information stored in a virtual device schedule storage unit according to an embodiment. [Figure 6] FIG. 10 is a diagram showing an example of information stored in a virtual device storage unit according to an embodiment; [Figure 7] FIG. 10 is a diagram showing an example of a schedule notification image displayed on a display unit of a terminal device according to an embodiment; [Figure 8] FIG. 10 is a diagram showing an example of a registration image displayed on a display unit of a terminal device according to an embodiment; [Figure 9] FIG. 10 is a diagram showing another example of a registration image displayed on the display unit of the terminal device according to the embodiment; [Figure 10] FIG. 10 is a diagram showing another example of a registration image displayed on the display unit of the terminal device according to the embodiment; [Figure 11] FIG. 1 is a sequence diagram illustrating an example of a flow of processing executed by a control system according to an embodiment. [Figure 12] FIG. 1 is a sequence diagram illustrating an example of a flow of processing executed by a control system according to an embodiment. [Figure 13] 1 is a flowchart showing the flow of a schedule management process executed by a cloud server according to an embodiment. [Figure 14] 1 is a flowchart showing the flow of a schedule management process executed by a cloud server according to an embodiment. [Figure 15] FIG. 10 is a diagram showing an example of a registration image displayed on a display unit of a terminal device according to a modified example. [Figure 16] FIG. 10 is a diagram showing an example of a device selection screen image displayed on a display unit of a terminal device according to a modified example. [Figure 17] FIG. 10 is a diagram showing another example of a registration image displayed on the display unit of a terminal device according to a modified example. [Figure 18] FIG. 10 is a diagram showing an example of a device selection screen image displayed on a display unit of a terminal device according to a modified example. [Figure 19]FIG. 10 is a diagram showing an example of information stored in a virtual device storage unit according to a modified example;

[0009] Hereinafter, an embodiment will be described in detail with reference to the drawings. In the drawings, the same or corresponding parts are denoted by the same reference numerals. The control system according to this embodiment is a system that can remotely control multiple devices 3 installed inside a building H from outside the building H. As shown in FIG. 1, the control system according to this embodiment includes a cloud server 1, a terminal device 2, and multiple devices 3. The multiple devices 3 are installed inside the building H. The building H is, for example, a detached house, an apartment building, an office building, a commercial facility, a factory, etc.

[0010] Each of the multiple devices 3 is a device to be controlled in the control system. Specifically, each of the multiple devices 3 is an electrical device such as an air conditioner that conditions the air inside the building H, a ventilation device that ventilates the building H, or a water heater that heats water. Although not shown, each of the multiple devices 3 is connected to an operation device such as a remote control or a wall switch. A user in the building H can input instructions to the device 3, such as starting and stopping operation and adjusting the operation strength, by operating the operation device. Operation of the device 3 using the operation device is called "local operation." In contrast, operation of the device 3 remotely by a user using a terminal device 2 is called "remote operation." Each of the multiple devices 3 is connected to a local network NW2 established in the building H via a communication adapter, although not shown. The local network NW2 is connected to a wide area network NW1 via a broadband router (BBR) 5. The local area network NW2 is, for example, a wired local area network (LAN), a wireless LAN, or a network based on ECHONET Lite (registered trademark), and the wide area network NW1 is, for example, the Internet.

[0011] The cloud server 1 and the terminal device 2 can communicate with each other via a wide area network NW1. The cloud server 1 can communicate with multiple devices 3 via the wide area network NW1 and a local area network NW2. The cloud server 1 is a device that manages a control system, and specifically, a server that provides resources in cloud computing. As shown in FIG. 2, the cloud server 1 includes a control unit 11, a storage unit 12, and a communication unit 15. The control unit 11 includes a central processing unit (CPU), a read-only memory (ROM), and a random access memory (RAM). The CPU is also called a central processing unit, central arithmetic unit, processor, microprocessor, microcomputer, etc., and functions as a central processing 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 the ROM and uses the RAM as a work area to perform overall control of the cloud server 1. The storage unit 12 includes nonvolatile memory such as a flash memory, an EPROM (Erasable Programmable ROM), an EEPROM (Electrically Erasable Programmable ROM), or a hard disk, and serves as a so-called secondary storage device or auxiliary storage device. The storage unit 12 stores programs and data used by the control unit 11 to perform various processes. The storage unit 12 also stores data generated or acquired by the control unit 11 performing various processes. The communication unit 15 includes a communication interface that enables the cloud server 1 to communicate with external devices via the wide area network NW1. The communication unit 15 transmits and receives various information to and from the terminal device 2 and the multiple devices 3 via the wide area network NW1.

[0012] The terminal device 2 is a terminal that can be operated by a user outside the building H. The terminal device 2 may be, for example, a smartphone, a tablet device, or a personal computer. As shown in FIG. 2 , the terminal device 2 includes a control unit 21, a storage unit 22, an input unit 23, a display unit 24, and a communication unit 25. The control unit 21 includes a CPU, a ROM, and a RAM. The CPU is also called a central processing unit, a processor, a microprocessor, or a microcomputer, and functions as a central processing unit that executes 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 the ROM and uses the RAM as a work area to perform overall control of the terminal device 2. The storage unit 22 includes 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 to perform various processes. The storage unit 22 also stores data generated or acquired by the control unit 21 as a result of performing various processes. The input unit 23 includes input devices such as a keyboard, a mouse, a switch, a touchpad, and a touch panel, and receives operational inputs from a 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 operational instruction input from the user, it transmits the received operational instruction to the control unit 21. The display unit 24 includes a display device such as an LCD (Liquid Crystal Display) panel or an organic EL (Electro-Luminescence) panel. 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. The communication unit 25 includes a communication interface that enables the terminal device 2 to communicate with external devices. The communication unit 25 transmits and receives various information to and from the cloud server 1 via the wide area network NW1.

[0013] Next, the functional configuration of the control system will be described with reference to Fig. 3. As shown in Fig. 3, the cloud server 1 functionally includes a schedule registration request acquisition unit 111, a schedule generation unit 112, a registration possibility determination unit 113, a schedule registration unit 114, a device control unit 115, a schedule notification unit 116, an error notification unit 117, a virtual device registration request acquisition unit 118, a virtual device registration unit 119, and a device information acquisition unit 120. The terminal device 2 functionally includes a schedule registration request unit 211, a notification acquisition unit 212, a display control unit 213, and a virtual device registration request unit 214.

[0014] Each of these functions 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, 22. The CPU then executes the programs stored in the ROM or storage unit 12, 22 to realize each of these functions.

[0015] The cloud server 1 also includes a device schedule storage unit 121, a virtual device schedule storage unit 122, a device information storage unit 123, and a virtual device storage unit 124. These are constructed in appropriate storage areas of the storage unit 12. In the cloud server 1, the device schedule storage unit 121 stores device schedule information indicating the operation schedule of each device 3 in association with device identification information that identifies the device 3, as shown in FIG. 4, for example. The device schedule information stores operation status information indicating the operation status of the device 3 in association with day of the week information and time period information indicating the day of the week and time period during which the operation status is maintained. Furthermore, the device identification information can be, for example, MAC (Media Access Control) address information assigned to each device 3. For example, the example shown in Figure 4 indicates that during the time period from 7:00 to 12:00 on Mondays, the air conditioner identified by the device identification information IDE[0] operates in "dryer mode," the fan identified by the device identification information IDE[1] operates in "high" mode, and the environmental sensor identified by the device identification information IDE[2] remains on.

[0016] The virtual device schedule storage unit 122 stores virtual device schedule information indicating the operation schedule of each virtual device in association with virtual device identification information that identifies the virtual device, as shown in Fig. 5 for example. The virtual device schedule information stores operation state information indicating the operation state of the virtual device in association with day of the week information and time period information that indicate the day of the week and time period during which the operation state is maintained. For example, the example shown in Fig. 5 indicates that the virtual device identified by virtual device identification information IDVE[0] operates in the "clothes drying" mode during the time period from 7:00 to 12:00 on Mondays.

[0017] 3, the device information storage unit 123 stores various pieces of operation information indicating possible operation states of each device 3 in association with device identification information that identifies the device 3. The virtual device storage unit 124 stores device operation state information indicating the operation state of at least one device 3 that realizes a virtual device in association with the device identification information that identifies the at least one device 3, virtual device identification information that identifies the virtual device, and virtual device operation state information that indicates the operation state of the virtual device, as shown in FIG. 6, for example. The example shown in FIG. 6 indicates that the operation state of the virtual device identified by virtual device identification information IDVE[0] in the "clothes drying" mode is realized by the air conditioner identified by device identification information IDE[0] operating in the "heating mode," the fan identified by device identification information IDE[1] operating in the "high" mode, and the environmental sensor identified by device identification information IDE[2] maintaining the on state.

[0018] 3 , in the terminal device 2, when the user performs a schedule registration operation on the input unit 23 to newly register an operation schedule for at least one device 3 that realizes a virtual device in the device schedule storage unit 121, the schedule registration request unit 211 accepts the schedule registration operation and generates schedule registration request information. This schedule registration request information includes virtual device identification information that identifies the virtual device for which the operation schedule is to be registered, as well as day of the week information, time period information, and operating status information of the virtual device. Then, the schedule registration request unit 211 transmits the generated schedule registration request information to the cloud server 1.

[0019] When a user performs a virtual device registration operation on input unit 23 to register a new virtual device in virtual device storage unit 124 or to update a virtual device, virtual device registration request unit 214 accepts the virtual device registration operation and generates virtual device registration request information. This virtual device registration request information includes virtual device identification information that identifies the virtual device to be registered, and device identification information and operating state information for each of at least one device 3 that realizes the virtual device. Then, virtual device registration request unit 214 transmits the generated virtual device registration request information to cloud server 1.

[0020] When the notification acquisition unit 212 acquires schedule notification information or error notification information transmitted from the cloud server 1, it notifies the display control unit 213 of the acquired schedule notification information or error notification information. When the display control unit 213 is notified of the schedule notification information, it forms a schedule notification image for notifying the user of the operation schedules of the device 3 and the virtual device based on the notified schedule notification information, and displays the image on the display unit 24. The display control unit 213 forms a schedule notification image GA10 as shown in FIG. 7, for example, and displays it on the display unit 24. This schedule notification image GA10 includes a bar image BA10 indicating the time period during which the virtual device operates, a button image BU101 selected when specifying the day of the week on which the bar image BA10 is to be displayed, and a button image BU102 selected when a new operation schedule is to be registered or when the operation schedule is to be changed. The schedule notification image GA10 also includes message images M101, M102, M103, and M104 that indicate the operating modes of the virtual devices, and message images M105, M106, M107, and M108 that indicate the time and day of the week when the virtual devices start operating in each operating mode. The example shown in FIG. 7 indicates that the virtual devices operate in one of the following modes: "Automatic," "Custom," "Clothes Drying," and "Stop." In "Automatic" mode, the virtual devices operate adaptively to realize a preset environment that is comfortable for the user. In "Custom" mode, at least one device 3 that realizes the virtual devices operates in an operating mode set by the user. In "Clothes Drying" mode, the virtual devices operate in a preset operating mode suitable for drying clothes. The schedule notification image GA10 also includes button images BU103, BU104, BU105, and BU106 that can be selected to change the contents of each operating mode of the virtual devices. Furthermore, when the display control unit 213 is notified of the error notification information, it forms an error notification image based on the notified error notification information to notify the user that the registration of the operation schedules of the device 3 and the virtual device has failed, and displays the image on the display unit 24.

[0021] Furthermore, when the display control unit 213 receives a registration operation for registering an operation schedule of a new virtual device or a registration preparation operation for registering a new virtual device, which the user has performed on the input unit 23, the display control unit 213 forms a registration image for registering the operation schedule or the virtual device and displays it on the display unit 24. The registration preparation operation corresponds to an operation in which the user selects the above-mentioned button image BU102 or any of button images BU103, BU104, BU105, and BU106 via the input unit 23 when a schedule notification image GA10 as shown in Fig. 7 is displayed on the display unit 24 of the terminal device 2, for example.

[0022] The display control unit 213 forms and displays, as a registration image, an image representing a screen for setting a combination of the day of the week and time period for operating the virtual device, the operation mode of the virtual device, and the operation mode of at least one device 3 for realizing the virtual device. While viewing the operation schedule registration image displayed on the display unit 24, the user can register schedule information indicating a new operation schedule in the device schedule storage unit 121 and the virtual device schedule storage unit 122, and edit the device schedule information and virtual device schedule information already stored in the device schedule storage unit 121 and the virtual device schedule storage unit 122. The display control unit 213 operates the virtual device in automatic mode.

[0023] Suppose that, for example, while a schedule notification image GA10 as shown in Fig. 7 is displayed on the display unit 24 of the terminal device 2, the user performs an operation to select the above-mentioned button image BU102 or button image BU104 via the input unit 23. In this case, the display control unit 213 causes the display unit 24 to display, for example, a registration image GA11 as shown in Fig. 8. The registration image GA11 includes button images BU111, BU112, BU113, and BU114 selected when specifying the operation mode of the virtual device, a button image BU117 selected when specifying a time period, and a button image BU118 selected when specifying a day of the week. The registration image GA11 also includes a button image BU1110 selected when clearing the set operating schedule and a button image BU1111 selected when ending the setting of the operating schedule. 8 shows a case where "automatic" mode is selected as the operating mode of the virtual device, and in this case, the registration image GA11 includes button images BU115 and BU116 selected when specifying the operating mode of the air conditioner, and button image BU119 selected when specifying the set temperature. The operating modes of the air conditioner include an automatic cooling mode in which the air conditioner operates adaptively in cooling mode to achieve a specified set temperature, and an automatic heating mode in which the air conditioner operates adaptively in heating mode to achieve a specified set temperature. The example shown in FIG. 8 shows that an operation schedule is set in which the virtual device operates in automatic mode from 12:00 onwards from Monday to Friday, with the set temperature of the air conditioner at this time being 28°C and the operating mode of the air conditioner being automatic cooling mode.

[0024] Also, suppose that the user performs an operation to select the above-mentioned button image BU102 or button image BU106 via the input unit 23 while a schedule notification image GA10 as shown in Fig. 7 is displayed on the display unit 24 of the terminal device 2. In this case, the display control unit 213 causes the display unit 24 to display a registration image GA12 as shown in Fig. 9, for example. Note that in Fig. 9, the same components as in Fig. 8 are assigned the same reference numerals as in Fig. 8. The example shown in Fig. 9 illustrates a case where the "custom" mode is selected as the operation mode of the virtual device. In this case, the registration image GA12 includes button images BU121, BU122, BU123, BU124, BU125, BU126, and BU127 that are selected when specifying the operation mode of the air conditioner, button image BU128 that is selected when specifying the set temperature, and button images BU129, BU1210, and BU1211 that are selected when specifying the operation mode of the blower fan. The operating modes of an air conditioner include a cooling mode, a heating mode, a dehumidification mode, a fan mode, an automatic cooling mode in which the air conditioner operates adaptively in cooling mode to reach a specified set temperature, an automatic heating mode in which the air conditioner operates adaptively in heating mode to reach a specified set temperature, and a stop mode. The operating modes of the fan include a strong mode, a weak mode, and a stop mode. The example shown in Figure 9 indicates that an operation schedule is set in which the virtual device operates in custom mode during the time period from 6:00 PM on Monday through Friday, with the set temperature of the air conditioner at that time being 28°C, the operating mode of the air conditioner being cooling mode, and the operating mode of the fan being strong mode.

[0025] Also, suppose that the user performs an operation to select the aforementioned button image BU102 or button image BU103 via the input unit 23 while a schedule notification image GA10 such as that shown in FIG. 7 is displayed on the display unit 24 of the terminal device 2. In this case, the display control unit 213 causes the display unit 24 to display a registration image GA13 such as that shown in FIG. 10. Note that in FIG. 10, the same components as those in FIG. 8 are denoted by the same reference numerals. The example shown in FIG. 10 illustrates a case in which the "clothes drying" mode is selected as the operation mode of the virtual appliance. In this case, the registration image GA13 does not include button images for selecting the operation mode, set temperature, etc., of the appliance 3 that realizes the virtual appliance. The example shown in FIG. 10 illustrates an operation schedule in which the virtual appliance operates in the clothes drying mode from 6:00 a.m. on Monday through Friday.

[0026] Returning to Figure 3, in the cloud server 1, when the schedule registration request acquisition unit 111 acquires the schedule registration request information sent from the terminal device 2, it extracts the virtual device identification information, day of the week information, time period information, and virtual device operation status information contained in the acquired schedule registration request information and notifies the schedule generation unit 112.

[0027] When the virtual device registration request acquisition unit 118 acquires virtual device registration request information transmitted from the terminal device 2, it extracts the virtual device identification information included in the acquired virtual device registration request information and the device identification information and operating status information of at least one device 3 that realizes the virtual device identified by the virtual device identification information, and notifies the virtual device registration unit 119 of the same.

[0028] When the virtual device registration unit 119 is notified of the virtual device identification information, the device identification information, and the operating state information from the virtual device registration request acquisition unit 118, the virtual device registration unit 119 determines whether the notified operating state information exists in the operating state information corresponding to the acquired device identification information stored in the device information storage unit 123. If the virtual device registration unit 119 determines that the notified operating state information exists in the operating state information corresponding to the acquired device identification information stored in the device information storage unit 123, the virtual device registration unit 119 notifies the schedule generation unit 112 of the acquired virtual device identification information, the device identification information, and the operating state information. On the other hand, if the virtual device registration unit 119 determines that the notified operating state information does not exist in the operating state information corresponding to the acquired device identification information stored in the device information storage unit 123, the virtual device registration unit 119 notifies the error notification unit 117 of operating state non-existence notification information notifying that fact. Furthermore, when the virtual device registration unit 119 receives registration permission notification information from the registration permission determination unit 113, the virtual device registration unit 119 stores the acquired virtual device identification information, the acquired device identification information, and the acquired operating status information in the virtual device storage unit 124 in association with each other.

[0029] The schedule generation unit 112 identifies the device identification information and operation status information of the device 3 that are stored in the virtual device storage unit 124 and that are associated with the virtual device identification information and operation status information of the virtual device notified by the schedule registration request acquisition unit 111. Then, the schedule generation unit 112 generates device schedule information indicating an operation schedule for each of at least one device 3 that realizes a virtual device, based on the identified device identification information and operation status information and the notified day of the week information and time period information, and notifies the registration admissibility determination unit 113 of the generated device schedule information. Furthermore, the schedule generation unit 112 generates virtual device schedule information indicating the operation schedule of the virtual device, based on the notified virtual device identification information, day of the week information, time period information, and operation status information of the virtual device, and notifies the schedule registration unit 114 of the generated virtual device schedule information.

[0030] Furthermore, when the schedule generation unit 112 is notified of the virtual device identification information and the device identification information from the virtual device registration unit 119, it generates device schedule information for each of the devices 3 identified by the notified device identification information based on the virtual device schedule information stored in the virtual device schedule storage unit 122 and corresponding to the notified virtual device identification information, and the notified device identification information and the operating status information of the devices 3, and notifies the registration feasibility determination unit 113 of the device schedule information.

[0031] The registration possibility determination unit 113 determines whether there is an overlap in the operation schedules for the same device 3 between the operation schedule indicated by the device schedule information stored in the device schedule storage unit 121 and the operation schedule indicated by the newly generated device schedule information. If there is an overlap in the operation schedules for the same device 3, the registration possibility determination unit 113 determines that the newly generated device schedule information cannot be registered. In this case, the registration possibility determination unit 113 notifies the error notification unit 117 and the virtual device registration unit 119 of registration impossible notification information notifying that the newly generated device schedule information cannot be registered. On the other hand, if there is no overlap in the operation schedules for the same device 3, the registration possibility determination unit 113 determines that the newly generated device schedule information can be registered. In this case, the registration possibility determination unit 113 notifies the schedule registration unit 114 of the newly generated device schedule information. In addition, the registration possibility determination unit 113 notifies the virtual device registration unit 119 of registration possible notification information notifying that the newly generated device schedule information can be registered.

[0032] When the schedule registration unit 114 is notified of newly generated device schedule information from the registration possibility determination unit 113, it stores the notified device schedule information in the device schedule storage unit 121. At this time, the schedule registration unit 114 stores in the virtual device schedule storage unit 122 the virtual device schedule information of the virtual device realized by at least one device 3 corresponding to the device schedule information notified by the schedule generation unit 112.

[0033] The device control unit 115 controls each of the devices 3. The device control unit 115 controls the operation of the device 3 by transmitting a control command to the device 3 via the communication unit 15. More specifically, the device control unit 115 controls the device 3 according to a schedule stored in the device schedule storage unit 121. Furthermore, in addition to controlling the device 3 based on the schedule, the device control unit 115 can also control the device 3 based on operation information received from a user at the terminal device 2. Specifically, the user can remotely control any of the multiple devices 3 by inputting operations such as turning on or off, changing the operation mode, etc. to the input unit 23 of the terminal device 2.

[0034] The schedule notification unit 116 generates schedule notification information including the device schedule information newly stored in the device schedule storage unit 121 and the virtual device schedule information newly stored in the virtual device schedule storage unit 122, and transmits the schedule notification information to the terminal device 2. When the error notification unit 117 is notified of the above-mentioned registration failure notification information from the registration possibility determination unit 113, it generates error notification information and transmits it to the terminal device 2. Furthermore, when the error notification unit 117 is notified of the above-mentioned operating state absence notification information from the virtual device registration unit 119, it generates error notification information and transmits it to the terminal device 2.

[0035] The device information acquisition unit 120 acquires device identification information for each device 3 that can communicate with the cloud server 1 and operating status information indicating the operating status that each device 3 can be in, and stores the acquired information in association with each other in the device information storage unit 123.

[0036] Next, with reference to FIGS. 11 and 12, a flow of processing executed in the control system according to the embodiment will be described. First, with reference to FIG. 11, it is assumed that the terminal device 2 receives a schedule registration operation performed by a user via the input unit 23 to register an operation schedule for a virtual device (step S11). This schedule registration operation corresponds to an operation of registering only the operation schedule for the virtual device without changing the device 3 that realizes the virtual device. Specifically, in the examples shown in FIGS. 7 to 10, this corresponds to an operation of registering a schedule for operating the virtual device in one of the "clothes drying," "automatic," and "stopped" modes, or an operation of registering a schedule for operating the virtual device in the "custom" mode without changing the device 3 to be stopped when operating the virtual device in the "custom" mode. In this case, the terminal device 2 generates the schedule registration request information (step S12), and the generated schedule registration request information is transmitted from the terminal device 2 to the cloud server 1 (step S13).

[0037] On the other hand, when the cloud server 1 acquires the schedule registration request information, it extracts the virtual device identification information, day of the week information, time period information, and operation status information of the virtual device included in the acquired schedule registration request information. The cloud server 1 also identifies the device identification information and operation status information of the device 3 associated with the extracted virtual device identification information and operation status information of the virtual device, which are stored in the virtual device storage unit 124. The cloud server 1 then generates device schedule information indicating the operation schedule of each of at least one device 3 that realizes the virtual device, based on the identified device identification information and operation status information and the notified day of the week information and time period information (step S14).

[0038] Next, it is assumed that the cloud server 1 determines that there is no overlap in the operation schedule for the same device 3 between the operation schedule indicated by the device schedule information stored in the device schedule storage unit 121 and the operation schedule indicated by the newly generated device schedule information, and that the newly generated device schedule information can be registered (step S15). In this case, the cloud server 1 stores the generated device schedule information in the device schedule storage unit 121, and also stores virtual device schedule information of a virtual device realized by at least one device 3 corresponding to the device schedule information in the virtual device schedule storage unit 122 (step S16).

[0039] Next, the cloud server 1 generates schedule notification information including the device schedule information newly stored in the device schedule storage unit 121 and the virtual device schedule information newly stored in the virtual device schedule storage unit 122 (step S17). After that, the generated schedule notification information is transmitted from the cloud server 1 to the terminal device 2 (step S18). Meanwhile, upon receiving the schedule notification information transmitted from the cloud server 1, the terminal device 2 forms the above-mentioned schedule notification image based on the received schedule notification information and displays it on the display unit 24 (step S19).

[0040] Furthermore, after the processes of steps S11 to S14 described above have been executed, it is assumed that the cloud server 1 determines that there is an overlap in the operation schedule for the same device 3 between the operation schedule indicated by the device schedule information stored in the device schedule storage unit 121 and the operation schedule indicated by the newly generated device schedule information, and that the newly generated device schedule information cannot be registered (step S20). In this case, the cloud server 1 generates error notification information (step S21), and the generated error notification information is transmitted from the cloud server 1 to the terminal device 2 (step S22). Meanwhile, upon receiving the error notification information transmitted from the cloud server 1, the terminal device 2 forms the above-mentioned error notification image based on the received error notification information and displays it on the display unit 24 (step S23).

[0041] 12, it is assumed that the terminal device 2 receives a virtual device registration operation performed by the user via the input unit 23 to register a new virtual device or update a virtual device (step S24). This virtual device registration operation corresponds to an operation of changing the device 3 that realizes the virtual device or registering a new virtual device. Specifically, in the examples shown in FIGS. 7 to 10, this corresponds to an operation of changing the device 3 to a stopped state when the virtual device is operated in the "custom" mode. In this case, the terminal device 2 generates the above-mentioned virtual device registration request information (step S25), and the generated virtual device registration request information is transmitted from the terminal device 2 to the cloud server 1 (step S26).

[0042] On the other hand, when the cloud server 1 acquires the virtual device registration request information, it extracts the virtual device identification information, device identification information, and operation status information included in the acquired virtual device registration request information. Then, it is assumed that the cloud server 1 determines that the extracted operation status information exists in the operation status information stored in the device information storage unit 123 and corresponding to the extracted device identification information (step S27). In this case, the cloud server 1 generates device schedule information for each device 3 identified by the extracted device identification information based on the virtual device schedule information stored in the virtual device schedule storage unit 122 and corresponding to the extracted virtual device identification information, the extracted device identification information, and the operation status information of the device 3 (step S28).

[0043] Next, it is assumed that the cloud server 1 determines that there is no overlap in the operation schedule for the same device 3 between the operation schedule indicated by the device schedule information stored in the device schedule storage unit 121 and the operation schedule indicated by the newly generated device schedule information, and that the newly generated device schedule information can be registered (step S29). In this case, the cloud server 1 associates the extracted virtual device identification information, device identification information, and operation status information with each other and stores them in the virtual device storage unit 124 (step S30). Next, the cloud server 1 stores the generated device schedule information in the device schedule storage unit 121, and also stores virtual device schedule information of a virtual device realized by at least one device 3 corresponding to the device schedule information in the virtual device schedule storage unit 122 (step S16). Next, the series of processes from step S17 onwards are executed.

[0044] Furthermore, after the series of processes from step S24 to S28 are executed, it is assumed that the cloud server 1 determines that there is an overlap in the operation schedule for the same device 3 between the operation schedule indicated by the device schedule information stored in the device schedule storage unit 121 and the operation schedule indicated by the newly generated device schedule information, and that the newly generated device schedule information cannot be registered (step S31). In this case, the cloud server 1 generates error notification information (step S21), and executes the series of processes from step S22 onwards.

[0045] 13 and 14, the flow of schedule management processing executed by cloud server 1 will be described. This schedule management processing is executed whenever cloud server 1 is in a state where it can operate normally.

[0046] When the schedule management process starts, the schedule registration request acquisition unit 111 in the cloud server 1 determines whether schedule registration request information transmitted from the terminal device 2 has been acquired (step S41). If the schedule registration request acquisition unit 111 determines that schedule registration request information has not been acquired (step S41; NO), the process of step S47, which will be described later, is executed. On the other hand, if the schedule registration request acquisition unit 111 determines that schedule registration request information has been acquired (step S41; YES), the schedule registration request acquisition unit 111 extracts virtual device identification information, day of the week information, time period information, and operation status information of the virtual device included in the acquired schedule registration request information. In addition, the schedule generation unit 112 identifies the device identification information and operation status information of the device 3 associated with the extracted virtual device identification information and operation status information of the virtual device, which are stored in the virtual device storage unit 124. Then, the schedule generation unit 112 generates device schedule information indicating the operation schedule of each of at least one device 3 that realizes the virtual device, based on the identified device identification information and operation status information and the notified day of the week information and time period information (step S42).

[0047] Next, the registration possibility determination unit 113 determines whether there is no overlap in the operation schedule for the same device 3 between the operation schedule indicated by the device schedule information stored in the device schedule storage unit 121 and the operation schedule indicated by the newly generated device schedule information, and whether the device schedule information can be registered (step S43). Here, it is assumed that the registration possibility determination unit 113 determines that there is an overlap in the operation schedule for the same device 3, and that the newly generated device schedule information cannot be registered (step S43; NO). In this case, the registration possibility determination unit 113 notifies the error notification unit 117 of the above-mentioned registration impossible notification information, and the error notification unit 117 generates and transmits error notification information to the terminal device 2 (step S44). Then, the processing of step S47, which will be described later, is executed.

[0048] On the other hand, it is assumed that the registration possibility determination unit 113 determines that there is no overlap in the operation schedules for the same device 3 and that the newly generated device schedule information can be registered (step S43; YES). In this case, the registration possibility determination unit 113 notifies the schedule registration unit 114 of the newly generated device schedule information. Then, when the schedule registration unit 114 is notified of the newly generated device schedule information from the registration possibility determination unit 113, it stores the notified device schedule information in the device schedule storage unit 121. At this time, the schedule registration unit 114 stores virtual device schedule information of a virtual device realized by at least one device 3 corresponding to the device schedule information in the virtual device schedule storage unit 122 (step S45).

[0049] Next, the schedule notification unit 116 generates schedule notification information including the device schedule information newly stored in the device schedule memory unit 121 and the virtual device schedule information newly stored in the virtual device schedule memory unit 122, and transmits it to the terminal device 2 (step S46).

[0050] Thereafter, the virtual device registration request acquisition unit 118 determines whether or not virtual device registration request information transmitted from the terminal device 2 has been acquired (step S47). If the virtual device registration request acquisition unit 118 determines that virtual device registration request information has not been acquired (step S47; NO), the process of step S41 is executed again. On the other hand, if the virtual device registration request acquisition unit 118 determines that virtual device registration request information has been acquired (step S47; YES), the virtual device registration request acquisition unit 118 extracts virtual device identification information included in the acquired virtual device registration request information, and device identification information and operating status information of at least one device 3 that realizes the virtual device identified by the virtual device identification information. Next, the virtual device registration unit 119 determines whether or not the extracted operating status information exists in the operating status information corresponding to the acquired device identification information stored in the device information storage unit 123 (step S48). If the virtual device registration unit 119 determines that the extracted operating status information does not exist (step S48; NO), the process of step S51, which will be described later, is executed.

[0051] On the other hand, when virtual device registration unit 119 determines that the extracted operation status information exists (step S48; YES), it notifies schedule generation unit 112 of the extracted virtual device identification information, device identification information, and operation status information. Then, schedule generation unit 112 generates device schedule information for each device 3 identified by the notified device identification information, based on the virtual device schedule information corresponding to the notified virtual device identification information stored in virtual device schedule storage unit 122, and the notified device identification information and operation status information of device 3 (step S49).

[0052] Next, the registration possibility determination unit 113 determines whether there is no overlap in the operation schedule for the same device 3 between the operation schedule indicated by the device schedule information stored in the device schedule storage unit 121 and the operation schedule indicated by the newly generated device schedule information, and whether the device schedule information can be registered (step S50). Here, it is assumed that the registration possibility determination unit 113 determines that there is an overlap in the operation schedule for the same device 3, and that the newly generated device schedule information cannot be registered (step S50; NO). In this case, the registration possibility determination unit 113 notifies the error notification unit 117 of the above-mentioned registration impossible notification information, and the error notification unit 117 generates and transmits error notification information to the terminal device 2 (step S51). Then, the processing of step S41 is executed again.

[0053] On the other hand, it is assumed that the registration possibility determination unit 113 determines that there is no overlap in the operation schedules for the same device 3 and that the newly generated device schedule information can be registered (step S50; YES). In this case, the virtual device registration unit 119 associates the extracted virtual device identification information with the extracted device identification information and operation status information and stores them in the virtual device storage unit 124 (step S52). Next, the registration possibility determination unit 113 notifies the schedule registration unit 114 of the newly generated device schedule information. Then, when the schedule registration unit 114 is notified of the newly generated device schedule information from the registration possibility determination unit 113, it stores the notified device schedule information in the device schedule storage unit 121. At this time, the schedule registration unit 114 stores the virtual device schedule information of the virtual device realized by at least one device 3 corresponding to the device schedule information in the virtual device schedule storage unit 122 (step S53).

[0054] Thereafter, the schedule notification unit 116 generates schedule notification information including the device schedule information newly stored in the device schedule storage unit 121 and the virtual device schedule information newly stored in the virtual device schedule storage unit 122, and transmits the schedule notification information to the terminal device 2 (step S54). Next, the process of step S41 is executed again.

[0055] As described above, in the control system according to this embodiment, the schedule generation unit 112 identifies the devices 3 that realize the virtual devices for which an operation schedule is to be generated and the operation states of each of the devices 3, and generates device schedule information for each of the devices 3 that realize the target virtual devices based on virtual device schedule information indicating the operation schedule for the target virtual devices and the operation information of the identified devices 3 and each of the devices 3. As a result, the user only needs to perform an operation to generate an operation schedule for the virtual device for which an operation schedule is to be registered, and the operation schedule for the device 3 that realizes the target virtual device is generated, eliminating the need to perform an operation to generate an operation schedule for each of the actual devices 3 that realize the target virtual devices. This simplifies the operation for generating operation schedules for virtual devices for the user, thereby improving user convenience when generating operation schedules for virtual devices.

[0056] Furthermore, the terminal device 2 according to the present embodiment forms a schedule notification image showing the operation schedule of the virtual device based on the virtual device schedule information of the virtual device, and displays the image on the display unit 24. This allows the user to understand the operation schedule of the virtual device.

[0057] Furthermore, in the cloud server 1 according to this embodiment, the schedule notification unit 116 generates schedule notification information including device schedule information for each of the devices 3 that realize the virtual devices, and transmits the schedule notification information to the terminal device 2. Then, upon acquiring the schedule notification information, the terminal device 2 forms a schedule notification image showing the operation schedule of each of the devices 3 that realize the virtual devices, based on the device schedule information included in the acquired schedule notification information, and displays the image on the display unit 24. This makes it easier for the user to know which devices will actually operate when registering operation schedules for the virtual devices, thereby reducing the user's burden of managing the devices 3.

[0058] Furthermore, the registration possibility determination unit 113 according to this embodiment determines that the newly generated device schedule information cannot be registered if there is an overlap in the operation schedule for the same device 3 between the operation schedule indicated by the device schedule information stored in the device schedule storage unit 131 and the operation schedule indicated by the newly generated device schedule information, and determines that the newly generated device schedule information can be registered if there is no overlap in the operation schedule for the same device 3. This makes it possible to prevent malfunctions of the device 3 caused by overlapping operation schedules being set for the same device 3.

[0059] Although the embodiments of the present disclosure have been described above, the present disclosure is not limited to the configurations of the above-described embodiments. For example, when a schedule notification image GA10 as shown in FIG. 7 is displayed on the display unit 24 of the terminal device 2, if a user performs an operation to select the above-described button image BU102 or button image BU104 via the input unit 23, the display control unit 213 may cause the display unit 24 to display, for example, a registration image GA3011 as shown in FIG. 15. Note that in FIG. 15, components similar to those of the embodiment are denoted by the same reference numerals as in FIG. 8. Then, suppose that, for example, when a registration image GA3011 as shown in FIG. 15 is displayed on the display unit 24 of the terminal device 2, the user performs an operation to select a button image BU3101 included in the registration image GA3011 via the input unit 23. In this case, the display control unit 213 causes the display unit 24 to display, for example, a device selection image GA3002 as shown in FIG. 16. 16 is displayed on the display unit 24 of the terminal device 2. In this case, the display control unit 213 causes the display unit 24 to display a registration image GA3011, for example, as shown in FIG. 17. In FIG. 17, the same components as those in the embodiment are denoted by the same reference numerals as in FIG. 8. The registration image GA3011 includes button images BU3111 and BU3112 that are selected when specifying the operation mode of the virtual device. In the example shown in FIG. 17, the "air conditioning mode" is selected as the operation mode of the virtual device. In this case, the registration image GA3011 includes button images BU115 and BU116 that are selected when specifying the operation mode of the air conditioner, and a button image BU119 that is selected when specifying the set temperature.

[0060] Furthermore, when the terminal device 2 receives an operation to register a new operation schedule via the input unit 23, if there is an overlap in operation schedules for the same device based on the device schedule information of each already registered device 3, the terminal device 2 may exclude the device 3 from candidates for devices or virtual devices for which a new operation schedule is to be registered and display the excluded device on the display unit 24. For example, the terminal device 2 may form a device selection image GA2001, as shown in Fig. 18, for allowing the user to select the device 3 or virtual device for which an operation schedule is to be registered, and display the image on the display unit 24. The device selection image GA2001 shows a case where there is an overlap in operation schedules for an air conditioner corresponding to "air conditioner 2" and a ventilation device corresponding to "ventilation fan 1", and the user cannot make a selection.

[0061] According to this configuration, when a user performs a schedule registration operation, it is possible to prevent overlapping of operation schedules for the same device 3.

[0062] In an embodiment, the schedule generating unit 112 may identify only at least one device 3 that realizes a virtual device for which an operation schedule is to be generated, and generate device schedule information that indicates the operation schedule of each of the at least one device 3 that realizes the target virtual device, based on virtual device schedule information that indicates the operation schedule of the target virtual device and the identified at least one device 3. In other words, the schedule generating unit 112 may generate device schedule information for each of the at least one device 3 that realizes the virtual device, without using operation status information of the virtual device.

[0063] 19 , for example, the virtual device storage unit 4214 may store device identification information for identifying at least one device 3 realizing each virtual device, as well as control target information indicating whether each of the at least one device 3 is a control target controlled by the cloud server 1 in response to a user's operation, in association with the virtual device identification information. The schedule generation unit 112 may identify, based on the control target information stored in the virtual device storage unit 4214, at least one device identification information that corresponds to the virtual device identification information of a virtual device for which an operation schedule is to be generated and that is a control target. The schedule generation unit 112 may generate device schedule information indicating the operation schedule of each of the at least one device realizing the target virtual device, based on the virtual device schedule information indicating the operation schedule of the target virtual device and the identified at least one device identification information.

[0064] 19 shows that the "air conditioner" and the "fan" are objects to be controlled, and the "environmental sensor" is not an object to be controlled. In the example shown in this Fig. 19, the schedule generation unit 112 generates device schedule information indicating the operation schedule of only the "air conditioner" and the "fan", and does not generate device schedule information indicating the operation schedule of the "environmental sensor".

[0065] According to this configuration, the devices 3 for which device schedule information is to be generated can be limited to the minimum necessary number of devices 3, and the processing load on the cloud server 1 can be reduced accordingly.

[0066] In the embodiments, the functions of the units included in the cloud server 1 and the terminal device 2 may be provided in a device other than the cloud server 1 or the terminal device 2. For example, the virtual device storage unit 124, the device schedule storage unit 121, or the virtual device schedule storage unit 122 may be provided in a device external to the cloud server 1. In addition, the functions of the schedule registration request acquisition unit 111, the schedule generation unit 112, and the registration permission determination unit 113 may be provided in the terminal device 2.

[0067] In the above embodiment, the control unit 11 of the cloud server 1 functions as each unit shown in FIG. 3 by having the CPU execute a program stored in the ROM or the storage unit 12. Furthermore, the control unit 21 of the terminal device 2 functions as each unit shown in FIG. 3 by having the CPU execute a program stored in the ROM or the storage unit 22. However, the control units 11 and 21 may be dedicated hardware. Dedicated hardware may be, for example, a single circuit, a composite circuit, a programmed processor, an ASIC (Application Specific Integrated Circuit), an FPGA (Field-Programmable Gate Array), or a combination thereof. When the control units 11 and 21 are dedicated hardware, the functions of each unit may be implemented by individual hardware, or the functions of each unit may be implemented together by a single piece of hardware.

[0068] In addition, some of the functions of each unit may be realized by dedicated hardware, and other parts may be realized by software or firmware. In this way, the control units 11 and 21 can realize each of the above-mentioned functions by hardware, software, firmware, or a combination of these.

[0069] By applying a program that defines the operation of the cloud server 1 or the terminal device 2 to an existing computer such as a personal computer or an information terminal device, the computer can be made to function as the cloud server 1 or the terminal device 2.

[0070] Furthermore, the method of distribution of such a program is arbitrary, and for example, it may be stored on a computer-readable recording medium such as a CD-ROM (Compact Disk ROM), a DVD (Digital Versatile Disk), an MO (Magneto Optical Disk), or a memory card and distributed, or it may be distributed via a communication network such as the Internet.

[0071] The present disclosure allows various embodiments and modifications without departing from the broad spirit and scope of the present disclosure. Furthermore, the above-described embodiments are intended to illustrate the present disclosure and do not limit the scope of the present disclosure. That is, the scope of the present disclosure is defined by the claims, not the embodiments. Various modifications made within the scope of the claims and the meaning of equivalent disclosures are considered to be within the scope of the present disclosure.

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

[0073] (Appendix 1) a schedule generating unit that identifies at least one device that realizes a virtual device for which an operation schedule is to be generated, and generates device schedule information that indicates the operation schedule of each of the at least one device that realizes the target virtual device based on virtual device schedule information that indicates the operation schedule of the target virtual device and the identified at least one device; and a device control unit that controls the at least one device based on the device schedule information. Control system. (Appendix 2) a terminal device having a display unit, the terminal device forming a schedule notification image representing an operation schedule of the target virtual device based on the virtual device schedule information of the target virtual device and displaying the schedule notification image on the display unit; 10. The control system of claim 1. (Appendix 3) a terminal device having a display unit; a schedule notification unit that generates schedule notification information including the device schedule information of each of the at least one device that realizes the target virtual device, and transmits the schedule notification information to the terminal device; When the terminal device acquires the schedule notification information, it forms a schedule notification image representing an operation schedule of each of the at least one device that realizes the target virtual device based on the device schedule information included in the acquired schedule notification information, and displays the schedule notification image on the display unit. 3. The control system of claim 1 or 2. (Appendix 4) the schedule generation unit further identifies an operation state of each of the at least one device, and generates device schedule information indicating an operation schedule of each of the at least one device based on the virtual device schedule information, the identified at least one device, and the operation state of each of the at least one device. 4. The control system of any one of claims 1 to 3. (Appendix 5) a virtual device storage unit that stores device identification information for identifying at least one device that realizes at least one virtual device and operation status information indicating an operation status of each of the at least one device in association with the virtual device identification information for identifying the virtual device; the schedule generation unit identifies the at least one piece of device identification information and the operation status information corresponding to the virtual device identification information of a virtual device for which an operation schedule is to be generated, stored in the virtual device storage unit, and generates device schedule information indicating an operation schedule for each of the at least one piece of device that realizes the target virtual device, based on virtual device schedule information indicating an operation schedule for the target virtual device and the identified at least one piece of device identification information and operation information. 10. The control system of claim 4. (Appendix 6) a virtual device storage unit that stores device identification information for identifying at least one device that realizes at least one virtual device and control target information indicating whether each of the at least one device is a control target, in association with the virtual device identification information for identifying the virtual device; the schedule generation unit, based on the control target information stored in the virtual device storage unit, identifies the at least one piece of device identification information that corresponds to the virtual device identification information of a virtual device that is a target for generating an operation schedule and is a control target, and generates device schedule information that indicates an operation schedule for each of the at least one piece of device that realizes the target virtual device, based on virtual device schedule information that indicates an operation schedule for the target virtual device and the identified at least one piece of device identification information. 4. The control system of any one of claims 1 to 3. (Appendix 7) The device further includes a registration possibility determination unit that determines that the newly generated device schedule information cannot be registered when there is an overlap of operation schedules for the same device between the operation schedule indicated by the device schedule information stored in a device schedule storage unit that stores device schedule information indicating the operation schedule of the device and the operation schedule indicated by the newly generated device schedule information, and determines that the newly generated device schedule information can be registered when there is no overlap of operation schedules for the same device. 7. The control system of any one of claims 1 to 6. (Appendix 8) when the schedule generation unit newly registers at least one of the virtual devices or changes at least one device that realizes the virtual device, the schedule generation unit newly generates the device schedule information for the virtual device to be newly registered or for the at least one device that realizes the virtual device whose realization at least one device has been changed; 8. The control system of claim 7. (Appendix 9) an input unit and a display unit, and when a registration operation of a new operation schedule is received on the input unit, if there is an overlap of the operation schedules for the same device based on the device schedule information of each of the at least one device that has already been registered, the device is excluded from candidates for the device or the virtual device for which the new operation schedule is to be registered and displayed on the display unit; A control system according to any one of claims 1 to 8. (Appendix 10) Identifying at least one device that realizes a virtual device for which an operating schedule is to be generated; generating device schedule information indicating an operation schedule of each of the at least one device that realizes the target virtual device based on virtual device schedule information indicating an operation schedule of the target virtual device and the at least one identified device, How to manage your schedule. (Appendix 11) Computer, a schedule generating unit that identifies at least one device that realizes a virtual device for which an operation schedule is to be generated, and generates device schedule information that indicates the operation schedule of each of the at least one device that realizes the target virtual device, based on virtual device schedule information that indicates the operation schedule of the target virtual device and the identified at least one device; a device control unit that controls the at least one device based on the device schedule information; A program to function as a [Explanation of symbols]

[0074] 1 Cloud server, 2 Terminal device, 3 Device, 5 BBR, 11, 21 Control unit, 12, 22 Memory unit, 15, 25 Communication unit, 23 Input unit, 24 Display unit, 111 Schedule registration request acquisition unit, 112 Schedule generation unit, 113 Registration possibility determination unit, 114 Schedule registration unit, 115 Device control unit, 116 Schedule notification unit, 117 Error notification unit, 118 Virtual device registration request acquisition unit, 119 Virtual device registration unit, 120 Device information acquisition unit, 121 Device schedule storage unit, 122 Virtual device schedule storage unit, 123 Device information storage unit, 124, 4124 Virtual device storage unit, 211 Schedule registration request unit, 212 Notification acquisition unit, 213 Display control unit, 214 Virtual device registration request unit, BA10 Bar image, BU101,BU102,BU103,BU104,BU105,BU106,BU111,BU112,BU113,BU114,BU115,BU116,BU117,BU118,BU119,BU121,BU122,BU123,BU124,BU125,BU126,BU127,BU128,BU129,BU1110,BU1111,BU1210,BU1211 Button image, GA10 Schedule notification image, GA11,GA12,GA13,GA3001,GA3011 Registration image, GA2001,GA3002 Device selection image, H Building, M101, M102, M103, M104, M105, M106, M107, M108 message image, NW1 wide area network, NW2 local network

Claims

1. a schedule generating unit that identifies at least one device that realizes a virtual device for which an operation schedule is to be generated, and generates device schedule information that indicates the operation schedule of each of the at least one device that realizes the target virtual device based on virtual device schedule information that indicates the operation schedule of the target virtual device and the identified at least one device; a device control unit that controls the at least one device based on the device schedule information, Control system.

2. a terminal device having a display unit, the terminal device forming a schedule notification image representing an operation schedule of the target virtual device based on the virtual device schedule information of the target virtual device and displaying the schedule notification image on the display unit; The control system of claim 1 .

3. a terminal device having a display unit; a schedule notification unit that generates schedule notification information including the device schedule information of each of the at least one device that realizes the target virtual device, and transmits the schedule notification information to the terminal device; When the terminal device acquires the schedule notification information, it forms a schedule notification image representing an operation schedule of each of the at least one device that realizes the target virtual device based on the device schedule information included in the acquired schedule notification information, and displays the schedule notification image on the display unit.

3. A control system according to claim 1 or 2.

4. The schedule generation unit further identifies an operation state of each of the at least one device, and generates device schedule information indicating an operation schedule of each of the at least one device based on the virtual device schedule information, the identified at least one device, and the operation state of each of the at least one device.

3. A control system according to claim 1 or 2.

5. a virtual device storage unit that stores device identification information for identifying at least one device that realizes at least one virtual device and operation status information indicating an operation status of each of the at least one device in association with the virtual device identification information for identifying the virtual device; the schedule generation unit identifies the at least one piece of device identification information and the operation status information corresponding to the virtual device identification information of a virtual device for which an operation schedule is to be generated, stored in the virtual device storage unit, and generates device schedule information indicating an operation schedule for each of the at least one piece of device that realizes the target virtual device, based on virtual device schedule information indicating an operation schedule for the target virtual device and the identified at least one piece of device identification information and operation information. The control system of claim 4.

6. a virtual device storage unit that stores device identification information for identifying at least one device that realizes at least one virtual device and control target information indicating whether each of the at least one device is a control target, in association with the virtual device identification information for identifying the virtual device; the schedule generation unit, based on the control target information stored in the virtual device storage unit, identifies the at least one piece of device identification information that corresponds to the virtual device identification information of a virtual device that is a target for generating an operation schedule and is a control target, and generates device schedule information that indicates an operation schedule for each of the at least one piece of device that realizes the target virtual device, based on virtual device schedule information that indicates an operation schedule for the target virtual device and the identified at least one piece of device identification information.

3. A control system according to claim 1 or 2.

7. The device further includes a registration possibility determination unit that determines that the newly generated device schedule information cannot be registered when there is an overlap of operation schedules for the same device between the operation schedule indicated by the device schedule information stored in a device schedule storage unit that stores device schedule information indicating the operation schedule of the device and the operation schedule indicated by the newly generated device schedule information, and determines that the newly generated device schedule information can be registered when there is no overlap of operation schedules for the same device.

3. A control system according to claim 1 or 2.

8. when the schedule generation unit newly registers at least one of the virtual devices or changes at least one device that realizes the virtual device, the schedule generation unit newly generates the device schedule information for the virtual device to be newly registered or for the at least one device that realizes the virtual device whose realization at least one device has been changed. The control system of claim 7.

9. an input unit and a display unit, and when a registration operation of a new operation schedule is received on the input unit, if there is an overlap of the operation schedules for the same device based on the device schedule information of each of the at least one device that has already been registered, the device is excluded from candidates for the device or the virtual device for which the new operation schedule is to be registered and displayed on the display unit; The control system of claim 1 .

10. Identifying at least one device that realizes a virtual device for which an operation schedule is to be generated; generating, based on virtual device schedule information indicating an operation schedule for the target virtual device and the at least one device identified, device schedule information indicating an operation schedule for each of the at least one device that realizes the target virtual device; How to manage your schedule.

11. Computer, a schedule generating unit that identifies at least one device that realizes a virtual device for which an operation schedule is to be generated, and generates device schedule information that indicates an operation schedule for each of the at least one device that realizes the target virtual device, based on virtual device schedule information that indicates an operation schedule for the target virtual device and the identified at least one device; a device control unit that controls the at least one device based on the device schedule information; A program to function as a

Images