Device management system, device management apparatus, device management method, and program

Abstract

To provide a device management system, a device management apparatus, a device management method, and a program configured to allow an administrator to smoothly manage a device that a user permits the administrator to manage.SOLUTION: A terminal device 5 includes: a target device specifying unit 512 which specifies candidate devices 31, 32 to be managed from among devices 31, 32 owned by a user, based on target device information indicating the type of device to be managed by an administrator; a management target determination unit 514 which determines whether the specified devices 31, 32 are devices to be managed by other administrators; and a registration management unit 519 which registers, when determining that the specified candidate devices 31, 32 are not the devices to be managed by other administrators, the specified candidate devices 31, 32 as devices to be managed by the administrator. A cloud server 1 includes a device control unit 117 which controls the devices 31, 32 registered as the devices to be managed by the administrator.SELECTED DRAWING: Figure 3

Description

Technical Field

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

Background Art

[0002] When receiving a demand for increasing or decreasing the required power from a user, the user is made to select whether to accept the received demand, and power control is performed according to the demand in which the request is determined based on the result of the selection made by the user. A power management system has been proposed (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] By the way, in the power management system as described in Patent Document 1, by determining the operation schedule of each device such as a power storage device and a heat storage device owned by a plurality of users according to the power supply and demand situation, the peak value of the power consumption amount consumed by all the devices owned by the plurality of users does not exceed a predetermined reference value. In some cases, it is used for a device management service that stably supplies power to a plurality of users. In this case, if a user erroneously permits a device to be subject to device management services by a plurality of administrators who provide the same device management service for one device, the device may be controlled redundantly by the plurality of administrators, and the device may not be appropriately controlled.

[0005] The present disclosure has been made in view of the above circumstances, and an object thereof is to provide a device management system, a device management apparatus, a device management method, and a program that can smoothly perform management on a device permitted by an administrator to be managed by a user.

Means for Solving the Problems

[0006] To achieve the above object, a device management system according to the present disclosure includes: a target device specifying unit that specifies a device to be a management target candidate from among at least one device held by a user based on at least one type of target device information indicating the type of a device to be managed by a first administrator; a management target determination unit that determines whether or not the specified device is a management target of a second administrator different from the first administrator; a registration management unit that, when it is determined that the specified device to be a management target candidate is not a management target of the second administrator, registers the specified device to be a management target of the first administrator; and a device control unit that controls the device registered as a management target of the first administrator.

Effects of the Invention

[0007] According to the present disclosure, when the registration management unit determines that a device specified as a management target of a first administrator is not a management target of a second administrator, the registration management unit registers the specified device as a management target of the first administrator. Thereby, it is possible to prevent control by a plurality of device management service providers from being executed in duplicate for the same device, and thus it is possible to smoothly provide a device management service for a device permitted by a device management service provider to be a target of a device management service by a user.

Brief Description of the Drawings

[0008]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Embodiments for Carrying Out the Invention

[0009] Hereinafter, a device management system according to an embodiment of the present disclosure will be described with reference to the drawings. The device management system includes a target device specifying unit that specifies a device to be a management target candidate from among at least one device owned by a user based on at least one type of target model information indicating the type of the device to be managed by a first administrator, a management target determination unit that determines whether the specified device is a management target of a second administrator different from the first administrator, a registration management unit that registers the specified device as a management target of the first administrator when it is determined that the specified device is not a management target of the second administrator, and a device control unit that controls the device registered as a management target of the first administrator.

[0010] As shown in Fig. 1, the device management system according to this embodiment is used together with devices 31 and 32 and power measurement devices 61 and 62 respectively connected to a plurality of local networks NW21 and NW22. The local networks NW21 and NW22 are each a LAN (Local Area Network) constructed in the residential area of users who utilize the devices 31 and 32, for example. The local networks NW21 and NW22 are each connected to the wide area network NW1 via broadband routers (hereinafter referred to as "BBRs") 41 and 42. The wide area network NW1 is the Internet, for example. The users are so-called end users who own the devices 31 and 32, such as residents living in single-family houses or apartment houses or people who temporarily use the devices 31 and 32 as guests. This device management system includes a cloud server 1, a terminal device 5 owned by an administrator who provides a device management service for the devices 31 and 32, and terminal devices 21 and 22 owned by users who use the devices 31 and 32 respectively. The administrator is, for example, an aggregator that provides a power aggregation service for appropriately controlling so-called energy storage devices, such as power conditioners for charging and discharging the batteries of electric vehicles and water heaters, according to the power supply and demand situation in the residential area of the users. This aggregator controls the devices 31 and 32 according to the power supply and demand in the corresponding residential area by being granted authorities such as control of the devices 31 and 32 owned by the users and monitoring of the states of the devices 31 and 32, and has concluded a contract with the users regarding the provision of a device management service. Note that the aggregator is not limited to being a single corporation, and may be, for example, a corporate group composed of a plurality of corporations. Also, the administrator is not limited to an aggregator, and may be, for example, a service provider that provides a monitoring service for monitoring users by operating or viewing the states of the devices 31 and 32 owned by the users. The cloud server 1 can communicate with the devices 31 and 32 via the wide area network NW1, BBRs 41 and 42, and local networks NW21 and NW22, and can communicate with the terminal devices 5, 21, and 22 via the wide area network NW1.Further, the terminal device 5 can directly communicate with the terminal devices 21 and 22 via the wide area network NW1.

[0011] The devices 31 and 32 are, for example, a power storage device, a power conditioner for charging and discharging the battery of an electric vehicle, an air conditioner, a water heater, etc., and each operates based on the control information for controlling each of the devices 31 and 32 transmitted from the cloud server 1. The power measurement devices 61 and 62 respectively measure the power consumption in the residential area where the devices 31 and 32 are installed at regular intervals, generate power consumption information indicating the measured power consumption, and transmit it to the cloud server 1.

[0012] As shown in FIG. 2, the terminal device 5 is, for example, a personal computer, and includes a CPU (Central Processing Unit) 501, a main memory unit 502, an auxiliary storage unit 503, a display unit 504, an input unit 505, a communication unit 506, and a bus 509 that connects these to each other. The main memory unit 502 has a volatile memory such as a RAM (Random Access Memory) and is used as the working area of the CPU 501. The auxiliary storage unit 503 is a non-volatile memory such as a semiconductor flash memory and stores programs for the CPU 501 to execute various processes. The display unit 504 is a display device such as a liquid crystal display or an organic EL (Electro-Luminescence) display. The input unit 505 is, for example, a keyboard. The communication unit 506 is connected to the wide area network NW1, transmits information transferred from the CPU 501 to the cloud server 1, the terminal devices 21 and 22 via the wide area network NW1, or transfers information received from the cloud server 1, the terminal devices 21 and 22 via the wide area network NW1 to the CPU 501.

[0013] The CPU 501 functions as a contract-related information notification unit 511, a target device identification unit 512, a management group information acquisition unit 513, a management target determination unit 514, a notification unit 515, a display control unit 516, a device information acquisition unit 517, and a registration management unit 519 as shown in FIG. 3 by reading and executing the program stored in the auxiliary storage unit 503 into the main storage unit 502. Further, as shown in FIG. 3, the auxiliary storage unit 503 shown in FIG. 2 has a device information storage unit 531, a target model information storage unit 532, and a manager information storage unit 533. The device information storage unit 531 stores the user identification information, user information, area identification information, area information, device identification information, device information, and device status information included in the device information notification information transmitted from the cloud server 1 in association with each other. Here, the user identification information is information for identifying the users of the devices 31 and 32. The user information includes information such as the email address information, login ID information, and password information held by the user. The area identification information is information for identifying the residential area where the devices 31 and 32 held by the user are installed. Therefore, the group of devices 31 and 32 installed in a certain residential area and capable of communicating with the cloud server 1 are all identified by the same area identification information. Note that this area identification information is strongly associated with physical properties such as residential areas and buildings, but is not limited to the case where they are installed in the same residential area. The area information includes information indicating the name of the residential area used in the application launched on the terminal devices 21 and 22, position information indicating the location where the devices 31 and 32 are installed, contract information including electricity unit price, presence or absence of a night-time electricity contract, information regarding the power generation amount of the power generation equipment installed in the residential area, information indicating the presence or absence of a gas contract, and the like. The device information indicates information regarding the specifications of the devices 31 and 32.

[0014] The target device information storage unit 532 stores target device information indicating the types of devices 31 and 32 to be managed. The types of devices 31 and 32 to be managed indicate so-called energy storage devices such as the aforementioned power conditioner and water heater. The administrator information storage unit 533 stores the administrator identification information, the management group identification information for identifying the management group, and the management type information of the administrator who owns the terminal device 5. The management group is composed of a group of devices 31 and 32 to be managed by the administrator. This management group includes the devices 31 and 32 to be managed in the device management service owned by each user who has concluded a contract with the administrator regarding the provision of the aforementioned device management service. For example, as shown in FIG. 4, it is assumed that administrator A has concluded a contract for providing a device management service with users A and B, with the "water heater" and "power conditioner" as the devices to be managed. In this case, among the devices 31 and 32 owned by users A and B, the "water heater" and "power conditioner" will belong to the management group of administrator A. On the other hand, the "air conditioner", which is not subject to the device management service among the devices 31 and 32 owned by users A and B, will be excluded from the management group of administrator A. Note that this management group can also be used when, in addition to the power aggregation service, a user entrusts an external vendor with the operation or status viewing of the devices 31 and 32 they own. For example, only the viewing authority of the devices is given to the service provider of the monitoring system in a monitoring system or the like.

[0015] Returning to FIG. 3, when the contract-related information notification unit 511 receives a contract invitation operation performed by the administrator on the input unit 505 to invite the user to conclude a contract regarding the management of the devices 31 and 32, in response thereto, the contract invitation information including the message information representing the contract content is generated and transmitted to the terminal devices 21 and 22. Further, when the contract-related information notification unit 511 receives a contract cancellation preparation operation performed by the administrator on the input unit 505 to cause the user to cancel the contract regarding the management of the devices 31 and 32, in response thereto, the cancellation information including the message information representing the content to be notified to the user when the user cancels the contract is generated and transmitted to the terminal devices 21 and 22. Furthermore, when the contract-related information notification unit 511 is notified of the deletion completion notification information from the registration management unit 519, based on the notified deletion completion notification information, the contract cancellation completion notification information is generated, and the generated contract cancellation completion notification information is transmitted to the terminal devices 21 and 22 that are the transmission sources of the management device deletion request information.

[0016] When the device information acquisition unit 517 acquires the contract commitment notification information transmitted from the terminal devices 21 and 22 notifying that the user has committed to the contract regarding the management of the devices 31 and 32 or the registration completion notification information notifying that the user has registered the devices 31 and 32 with the cloud server 1, in response thereto, the user device information request information for requesting the cloud server 1 to transmit the device identification information and device information of the devices 31 and 32 used by the user is generated and transmitted to the cloud server 1. Thereby, the device information acquisition unit 517 acquires the device information notification information including the area identification information, area information, device identification information, device information, and device status information transmitted from the cloud server 1. Here, the contract commitment notification information includes the user identification information and user information, and the device information acquisition unit 517 generates the user device information request information including the user identification information and user information included in the contract commitment notification information and transmits it to the cloud server 1. When the device information acquisition unit 517 acquires the device information notification information, the area identification information, area information, device identification information, device information, and device status information included in the acquired device information notification information are extracted, and the extracted information is associated with the corresponding user identification information and user information and stored in the device information storage unit 531.

[0017] The target device identification unit 512 compares the model information included in the device information newly stored in the device information storage unit 531 with the target model information stored in the target model information storage unit 532, and determines whether there is a device of the target model indicated by the target model information among the devices 31 and 32 owned by the user. Here, if the target device identification unit 512 determines that there is no device of the target model indicated by the target model information among the devices 31 and 32 owned by the user, it generates device registration prompting information for prompting the user to register the target device with the cloud server 1 and transmits it to the terminal devices 21 and 22.

[0018] When it is determined that there are devices 31 and 32 of the target model indicated by the target model information among the devices 31 and 32 owned by the user, the management group information acquisition unit 513 generates management group information request information including the device identification information of the devices 31 and 32 that are the target models and requests the cloud server 1 to transmit information regarding the management group to which the devices 31 and 32 belong, and transmits it to the cloud server 1. As a result, the management group information acquisition unit 513 acquires management group notification information including administrator identification information, management group identification information, and management type information transmitted from the cloud server 1. The management type information is information indicating the type of content managed by the administrator, and indicates, for example, management for controlling devices according to the power supply and demand situation, monitoring management of users, and the like. Then, the management group information acquisition unit 513 extracts the administrator identification information, management group identification information, and management type information included in the acquired management group notification information, and notifies the management target determination unit 514 of the extracted information. Further, when the management target determination unit 514 determines that the devices 31 and 32 do not yet belong to the management group of another administrator, the management group information acquisition unit 513 requests the cloud server 1 to transmit the management group identification information of the management group of the administrator who owns the terminal device 5, the management group information, and the device identification information of the devices 31 and 32 belonging to the management group, generates management device information request information, and transmits it to the cloud server 1. As a result, the management group information acquisition unit 513 acquires management device notification information including management group identification information, management group information, and device identification information transmitted from the cloud server 1. Then, the management group information acquisition unit 513 extracts the management group identification information, management group information, and device identification information included in the acquired management device notification information and notifies the display control unit 516.

[0019] The management target determination unit 514 determines whether the management type information stored in the administrator information storage unit 533 matches the management type information included in the acquired management group information. Here, when the management type information stored in the administrator information storage unit 533 matches the management type information included in the acquired management group information, the management target determination unit 514 determines that the devices 31 and 32 already belong to the management group of another administrator. On the other hand, when the management type information stored in the administrator information storage unit 533 does not match the management type information included in the acquired management group information or when the management group information is not included in the management group notification information, the management target determination unit 514 determines that the devices 31 and 32 do not yet belong to the management group of another administrator. That is, even when the management target determination unit 514 determines that the devices 31 and 32 already belong to the management group of another administrator, if the management type of that management group is different from the management type of the management group of the administrator who holds the terminal device 5, it makes a determination that they do not yet belong to the management group of another administrator. In other words, the devices 31 and 32 are not allowed to belong to the same management type management group redundantly.

[0020] When the notification unit 515 determines that the devices 31 and 32 already belong to the management group of another administrator, it generates error notification information notifying that the devices 31 and 32 cannot be added to the management group of the administrator who holds the terminal device 5 and notifies the display control unit 516. At the same time, it generates contract unfeasible notification information notifying that a contract to add the devices 31 and 32 to the administrator's management group cannot be made and transmits it to the terminal devices 21 and 22. Also, when schedule information is notified from the schedule generation unit 518, the notification unit 515 generates schedule notification information including the notified schedule information and transmits it to the terminal devices 21 and 22.

[0021] When the display control unit 516 is notified of the management group identification information, the management group information, and the device identification information from the management group information acquisition unit 513, it forms a management device list notification image that notifies a list of devices 31 and 32 managed by the administrator who owns the terminal device 5 based on these pieces of information and causes the display unit 504 to display it. Further, when the display control unit 516 is notified of error notification information from the notification unit 515, it forms an error notification image that notifies that the devices 31 and 32 cannot be added to the management group of the administrator who owns the terminal device 5 based on the error notification information and causes the display unit 504 to display it. Furthermore, when the display control unit 516 is notified of schedule information from the schedule generation unit 518, it forms a schedule notification image based on the notified schedule information and causes the display unit 504 to display it. Also, when the display control unit 516 is notified of additional registration completion notification information from the registration management unit 519, it forms an additional registration completion notification image that notifies that the devices 31 and 32 have been newly registered as management targets based on the additional registration completion notification information and causes the display unit 504 to display it. On the other hand, when the display control unit 516 is notified of deletion completion notification information from the registration management unit 519, it forms a deletion completion notification image that notifies that the devices 31 and 32 have been deleted from the management targets based on the deletion completion notification information and causes the display unit 504 to display it. Furthermore, when the display control unit 516 determines that the control end time indicated by the schedule information has arrived based on the schedule information notified from the schedule generation unit 518, it forms a control end notification image and causes the display unit 504 to display it.

[0022] When the registration management unit 519 receives a management group designation operation for designating a management group for adding devices 31 and 32, which is performed by the administrator on the input unit 505, in response thereto, the registration management unit 519 generates management device addition request information including device identification information, management group identification information, and administrator identification information of devices 31 and 32, and transmits the information to the cloud server 1. Then, when the registration management unit 519 acquires the additional registration completion notification information transmitted from the cloud server 1, the registration management unit 519 notifies the acquired additional registration completion notification information to the display control unit 516. On the other hand, when the registration management unit 519 acquires cancellation request information for requesting cancellation of the contract for the device management service for devices 31 and 32 from the terminal devices 21 and 22, in response thereto, the registration management unit 519 generates management device deletion request information including device identification information, management group identification information, and administrator identification information of devices 31 and 32, and transmits the information to the cloud server 1. Then, when the registration management unit 519 acquires the deletion completion notification information transmitted from the cloud server 1, the registration management unit 519 notifies the acquired deletion completion notification information to the display control unit 516 and the contract-related information notification unit 511.

[0023] When the day before the control target date for controlling the preset target devices 31 and 32 arrives, the schedule generation unit 518 generates power consumption history request information for requesting transmission of power consumption history information indicating the history of power consumption in the residential area to the cloud server 1, and transmits the information to the cloud server 1. As a result, the schedule generation unit 518 acquires the power consumption history information transmitted from the cloud server 1, and based on the acquired power consumption history information, generates schedule information indicating the operation schedule of the target devices 31 and 32. Then, the schedule generation unit 518 transmits the generated schedule information to the cloud server 1. After that, when the schedule generation unit 518 acquires the schedule registration completion notification information transmitted from the cloud server 1, the schedule generation unit 518 notifies the generated schedule information to the display control unit 516 and the notification unit 515.

[0024] Returning to FIG. 2, the terminal devices 21 and 22 are, for example, smartphones, and include a CPU 201, a main memory unit 202, an auxiliary storage unit 203, a display unit 204, an input unit 205, a communication unit 206, and a bus 209 that connects these to each other. The main memory unit 202 has a volatile memory and is used as a working area for the CPU 201. The auxiliary storage unit 203 is a non-volatile memory and stores programs for the CPU 201 to execute various processes. The display unit 204 is a display device such as a liquid crystal display or an organic EL display, and the input unit 205 is, for example, a transparent touch pad arranged over the display unit 204. The communication unit 206 is connected to the wide area network NW1, and transmits information transferred from the CPU 201 to the cloud server 1 and the terminal device 5 via the wide area network NW1, or transfers information received from the cloud server 1 and the terminal device 5 via the wide area network NW1 to the CPU 201.

[0025] The CPU 201 functions as a contract-related information acquisition unit 211, a display control unit 212, a contract management unit 213, a registration reminder acquisition unit 214, a device registration request unit 215, and a notification acquisition unit 216 as shown in FIG. 3 by reading out and executing the programs stored in the auxiliary storage unit 203 in the main memory unit 202. When the contract-related information acquisition unit 211 acquires contract invitation information or cancellation information transmitted from the terminal device 5, it notifies the acquired contract invitation information or cancellation information to the display control unit 212.

[0026] When the contract control unit 212 is notified of contract invitation information from the contract-related information acquisition unit 211, it forms a contract content notification image based on the notified contract invitation information and causes the display unit 204 to display it. Also, when the display control unit 212 is notified of registration completion notification information from the device registration request unit 215, it forms a registration completion notification image notifying the user that the registration of devices 31 and 32 has been completed based on the notified registration completion notification information and causes the display unit 204 to display it. Further, when the display control unit 212 is notified of cancellation information from the contract-related information acquisition unit 211, it forms a cancellation image based on the notified cancellation information and causes the display unit 204 to display it. Also, when the display control unit 212 is notified of device registration reminder information from the registration reminder acquisition unit 214, it forms a device registration reminder image based on the notified device registration reminder information and causes the display unit 204 to display it. Further, when the display control unit 212 is notified of contract impossible notification information from the notification acquisition unit 216, it forms a contract impossible notification image based on the notified contract impossible notification information and causes the display unit 204 to display it. Also, when the display control unit 212 is notified of schedule information from the notification acquisition unit 216, it forms a schedule notification image based on the notified schedule information and causes the display unit 204 to display it. Further, when the display control unit 212 is notified of deletion completion notification information from the contract management unit 213, it forms a cancellation completion notification image based on the notified deletion completion notification information and causes the display unit 204 to display it.

[0027] When the contract management unit 213 receives a contract commitment operation for notifying that the user has committed to the contract content represented by the invitation content notification image, which the user has performed on the input unit 205 in a state where the invitation content notification image is displayed on the display unit 204, it generates contract commitment notification information and transmits it to the terminal device 5. Also, when the contract management unit 213 receives a cancellation operation for canceling the contract for the service for managing devices 31 and 32, which the user has performed on the input unit 205, it generates cancellation request information for requesting the administrator to cancel the contract and transmits it to the terminal device 5. Thereafter, when the contract management unit 213 acquires the cancellation completion notification information transmitted from the terminal device 5, it notifies the acquired cancellation completion notification information to the display control unit 212.

[0028] When the registration reminder acquisition unit 214 acquires the aforementioned device registration reminder information transmitted from the terminal device 5, it notifies the acquired device registration reminder information to the display control unit 212. When the device registration request unit 215 receives a device registration operation performed by the user on the input unit 205 for newly registering the devices 31 and 32 to the cloud server 1, it generates device registration request information including the device identification information, device information, user identification information, user information, area identification information, and area information of the devices 31 and 32 and transmits it to the cloud server 1. After that, when the device registration request unit 215 acquires the registration completion notification information transmitted from the cloud server 1, it notifies the acquired registration completion notification information to the display control unit 212. Then, when receiving a registration completion notification operation performed by the user on the input unit 205, it generates registration completion notification information and transmits it to the terminal device 5.

[0029] When the notification acquisition unit 216 acquires the contract unavailability notification information transmitted from the terminal device 5, it notifies the acquired contract unavailability notification information to the display control unit 212. Also, when the notification acquisition unit 216 acquires the schedule notification information transmitted from the terminal device 5, it extracts the schedule information included in the acquired schedule notification information and notifies it to the display control unit 212.

[0030] As shown in FIG. 2, the cloud server 1 includes a CPU 101, a main memory unit 102, an auxiliary storage unit 103, a communication unit 106, and a bus 109 that interconnects these components. The CPU 101 is, for example, a multi-core processor. The main memory unit 102 has a volatile memory such as a RAM and is used as a working area for the CPU 101. The auxiliary storage unit 203 is composed of a large-capacity non-volatile memory and stores programs for realizing various functions of the cloud server 1. The communication unit 106 is connected to the wide area network NW1. When communicating with the devices 31 and 32, the communication unit 106 executes communication using an application layer protocol such as MQTT (Message Queuing Telemetry Transport) or HTTPS (Hypertext Transfer Protocol Secure).

[0031] The CPU 101 functions as a device registration unit 111, a device information notification unit 112, a management group information notification unit 113, a management group information management unit 114, a power information acquisition unit 115, a power consumption history notification unit 116, a device control unit 117, a device state acquisition unit 118, and a schedule acquisition unit 119, as shown in FIG. 3, by reading out and executing the program stored in the auxiliary storage unit 103 into the main storage unit 102. Further, as shown in FIG. 3, the auxiliary storage unit 103 shown in FIG. 2 includes a device information storage unit 131, a management group information storage unit 132, a power consumption information storage unit 133, and a schedule storage unit 134. As shown in FIG. 5(A), the device information storage unit 131 stores the device identification information, device information, and device state information of devices 31 and 32 in association with the user identification information and user information of the user who uses the devices 31 and 32, and the area identification information and area information of the residential area where the devices 31 and 32 are installed.

[0032] As shown in FIG. 5(B), the power consumption information storage unit 133 stores the power consumption amount information consumed in the residential area in association with the date information and the area identification information of the residential area. As shown in FIG. 6, the management group information storage unit 132 stores the device identification information of the devices 31 and 32 belonging to each management group in association with the management type information, management group identification information, management group information, manager identification information, and manager information. The manager information includes, for example, information related to the contract content with the manager.

[0033] Returning to FIG. 3, when the device registration unit 111 acquires device registration request information including user identification information, user information, area identification information, area information, device identification information, and device information transmitted from the terminal devices 21 and 22, the device registration unit 111 extracts these pieces of information included in the acquired device registration request information and stores them in the device information storage unit 131 in association with each other. Then, the device registration unit 111 generates registration completion notification information and transmits it to the terminal devices 21 and 22.

[0034] When the device information notification unit 112 acquires the aforementioned user device information request information transmitted from the terminal device 5, it selects, from among the area identification information, area information, device identification information, device information, and device status information stored in the device information storage unit 131, the area identification information, area information, device identification information, device information, and device status information corresponding to the user identification information and user information included in the acquired user device information request information. Then, the device information notification unit 112 generates device information notification information including the selected area identification information, area information, device identification information, device information, and device status information and transmits it to the terminal device 5.

[0035] When the management group information notification unit 113 acquires the aforementioned management group information request information transmitted from the terminal device 5, it searches for the administrator identification information, management group identification information, and management type information corresponding to the device identification information included in the acquired management group request information among the administrator identification information, management group identification information, and management type information stored in the management group information storage unit 132. Then, when the management group information notification unit 113 searches and detects the administrator identification information, management group identification information, and management type information, it generates management group notification information including the detected administrator identification information, management group identification information, and management type information and transmits it to the terminal device 5. On the other hand, when the administrator identification information, management group identification information, and management type information are not detected, the management group information notification unit 113 generates management group notification information not including the administrator identification information, management group identification information, and management type information and transmits it to the terminal device 5. Also, when the management group information notification unit 113 acquires the aforementioned management device information request information transmitted from the terminal device 5, it selects, from among the device identification information stored in the management group information storage unit 132, the management group identification information, management group information, and device identification information corresponding to the administrator identification information included in the acquired management device information request information, and generates management device notification information including the selected management group identification information, management group information, and device identification information and transmits it to the terminal device 5.

[0036] When the management group information management unit 114 acquires the aforementioned management device addition request information transmitted from the terminal device 5, it associates the management group identification information and the device identification information included in the acquired management device addition request information with each other and stores them in the management group information storage unit 132. Then, the management group information management unit 114 generates registration completion notification information notifying that the management group identification information and the device identification information included in the acquired management device addition request information have been newly stored in the management group information storage unit 132 in an associated manner, and transmits the information to the terminal device 5. On the other hand, when the management group information management unit 114 acquires the aforementioned management device deletion request information transmitted from the terminal device 5, it extracts the device identification information included in the acquired management device deletion request information, and updates the device identification information stored in the management group information storage unit 132 by deleting the extracted device identification information from the management group information storage unit 132. Then, the management group information management unit 114 generates deletion completion notification information notifying that the device identification information included in the acquired management device deletion request information has been deleted from the management group information storage unit 132, and transmits the information to the terminal device 5.

[0037] When the power information acquisition unit 115 acquires the power consumption notification information periodically transmitted from the power measuring devices 61 and 62, it extracts the power consumption information included in the acquired power consumption notification information and the area identification information identifying the residential area corresponding thereto, and associates the extracted power consumption information and area identification information with the date information indicating the date on which the power consumption notification information was acquired, and stores them in the power consumption information storage unit 133. When the power consumption history notification unit 116 acquires the aforementioned power consumption history request information transmitted from the terminal device 5, it generates power consumption history information indicating the history of the power consumption in the residential area corresponding to the area identification information included in the acquired power consumption history request information, and transmits the information to the terminal device 5.

[0038] When the schedule acquisition unit 119 acquires the above-described schedule notification information transmitted from the terminal device 5, it extracts the schedule information included in the acquired schedule notification information and stores the extracted schedule information in the schedule storage unit 134. Further, when the schedule acquisition unit 119 stores the schedule information in the schedule storage unit 134, it transmits schedule registration completion notification information to the terminal device 5.

[0039] When the preset control target date arrives, the device control unit 117 generates control information for controlling the devices 31 and 32 based on the schedule information stored in the schedule storage unit 134 and transmits the control information to the devices 31 and 32. Here, the device control unit 117 generates control information created in a telegram in, for example, JSON (JavaScript Object Notation) format. When the device state acquisition unit 118 acquires the device state notification information periodically transmitted from the devices 31 and 32, it extracts the device identification information and the device state information included in the acquired device state notification information, associates the extracted information with each other, and stores the information in the device information storage unit 131.

[0040] Next, the operation of the operation device management system according to the present embodiment will be described with reference to FIGS. 7 to 12. Here, it is assumed that the cloud server 1 executes a process of acquiring the device state notification information periodically transmitted from the devices 31 and 32, extracting the device identification information and the device state information included in the acquired device state notification information, and associating the extracted information with each other and storing the information in the device information storage unit 131 in parallel with the following processes. Further, when the cloud server 1 acquires the power consumption notification information periodically transmitted from the power measurement devices 61 and 62, it extracts the power consumption information included in the acquired power consumption notification information and the area identification information for identifying the residential area corresponding to the power consumption information, and associates the extracted power consumption information and the area identification information with the date information indicating the date when the power consumption notification information was acquired and stores the information in the power consumption information storage unit 133.

[0041] First, as shown in FIG. 7, assume that an administrator performs the above-described contract invitation operation on the input unit 505 of the terminal device 5. In this case, the terminal device 5 receives the contract invitation operation and generates contract invitation information including message information representing the contract content (step S1). Next, the generated contract invitation information is transmitted from the terminal device 5 to the terminal devices 21 and 22 held by the user (step S2). On the other hand, when the terminal device 5 acquires the contract invitation information, based on the acquired contract invitation information, the terminal device 5 forms the above-described contract content notification image and displays it on the display unit 204 (step S3).

[0042] Here, assume that in a state where the invitation content notification image is displayed on the display units 204 of the terminal devices 21 and 22, the user performs a contract commitment operation for notifying that the user commits to the contract content represented by the invitation content notification image on the input unit 205 of the terminal devices 21 and 22. In this case, the terminal devices 21 and 22 receive the contract commitment operation and generate the above-described contract commitment notification information (step S4), and the generated contract commitment notification information is transmitted from the terminal devices 21 and 22 to the terminal device 5 (step S5). On the other hand, when the terminal device 5 acquires the contract commitment notification information transmitted from the terminal devices 21 and 22, in response thereto, the terminal device 5 generates the above-described user device information request information (step S6), and the generated user device information request information is transmitted from the terminal device 5 to the cloud server 1 (step S7). On the other hand, when the cloud server 1 acquires the user device information request information, among the area identification information, area information, device identification information, device information, and device status information stored in the device information storage unit 131, the area identification information, area information, device identification information, device information, and device status information corresponding to the user identification information and user information included in the acquired user device information request information are selected, and device information notification information including the selected area identification information, area information, device identification information, device information, and device status information is generated (step S8). Subsequently, the generated device information notification information is transmitted from the cloud server 1 to the terminal device 5 (step S9).

[0043] On the one hand, when the terminal device 5 acquires the device information notification information, it extracts the area identification information, area information, device identification information, device information, and device status information included in the acquired device information notification information, and associates the extracted information with the corresponding user identification information and user information and stores it in the device information storage unit 531. Then, the terminal device 5 compares the model information included in the device information newly stored in the device information storage unit 531 with the target model information stored in the target model information storage unit 532 to determine whether there is a device of the target model indicated by the target model information among the devices 31 and 32 owned by the user. Here, assume that the terminal device 5 determines that there is a device of the target model indicated by the target model information among the devices 31 and 32 owned by the user (step S10). In this case, the terminal device 5 generates the above-mentioned management group information request information including the device identification information of the devices 31 and 32 that are the target models (step S11), and the generated management group information request information is transmitted from the terminal device 5 to the cloud server 1 (step S12). On the other hand, when the cloud server 1 acquires the management group information request information, it searches for the administrator identification information, management group identification information, and management type information stored in the management group information storage unit 132 for the administrator identification information, management group identification information, and management type information corresponding to the device identification information included in the acquired management group request information. Then, based on the search result, the cloud server 1 generates the above-mentioned management group notification information (step S13), and the generated management group notification information is transmitted from the cloud server 1 to the terminal device 5 (step S14).

[0044] On the one hand, when the terminal device 5 acquires the management group notification information, it extracts and extracts the administrator identification information, management group identification information, and management type information included in the acquired management group notification information. Then, based on the management type information stored in the administrator information storage unit 533 of the terminal device 5 and the management type information included in the acquired management group information, the terminal device 5 determines whether the devices 31 and 32 already belong to the management groups of other administrators. Here, as shown in FIG. 8, assume that the terminal device 5 determines that the devices 31 and 32 do not yet belong to the management groups of other administrators (step S15). In this case, the terminal device 5 generates the above-mentioned management device information request information (step S16), and the generated management device information request information is transmitted from the terminal device 5 to the cloud server 1 (step S17). On the other hand, when the cloud server 1 acquires the management device information request information, it selects, from the device identification information stored in the management group information storage unit 132, the management group identification information, management group information, and device identification information corresponding to the administrator identification information included in the acquired management device information request information, and generates management device notification information including the selected management group identification information, management group information, and device identification information (step S18). Then, the generated management device notification information is transmitted from the cloud server 1 to the terminal device 5 (step S19). On the other hand, when the terminal device 5 acquires the management device notification information, it forms a management device list notification image based on the management group identification information, management group information, and device identification information included in the acquired management device notification information and displays it on the display unit 504 (step S20).

[0045] Here, assume that an administrator performs a management group designation operation to designate a management group to which devices 31 and 32 are to be added by referring to the management device list notification image displayed on the display unit 504 of the terminal device 5, for example, with respect to the input unit 505 of the terminal device 5. In this case, the terminal device 5 accepts the management group designation operation and generates management device addition request information including the device identification information, management group identification information, and administrator identification information of devices 31 and 32 (step S21). Next, the generated management device addition request information is transmitted from the terminal device 5 to the cloud server 1 (step S22). On the other hand, when the cloud server 1 acquires the management device addition request information, it extracts the management group identification information and device identification information included in the acquired management device addition request information, and updates the information stored in the management group information storage unit 132 in such a way that the extracted information is associated with each other and stored in the management group information storage unit 132 (step S23). Subsequently, the cloud server 1 generates the above-mentioned additional registration completion notification information (step S24), and the generated additional registration completion notification information is transmitted from the cloud server 1 to the terminal device 5 (step S25). On the other hand, when the terminal device 5 acquires the additional registration completion notification information, based on the acquired additional registration completion notification information, it forms an additional registration completion notification image and displays it on the display unit 504 (step S26)

[0046] Also, assume that the terminal device 5 determines that the devices 31 and 32 already belong to the management group of another administrator based on the management type information stored in the administrator information storage unit 533 and the management type information included in the acquired management group information (step S27). In this case, the terminal device 5 forms an error notification image notifying that the devices 31 and 32 described above cannot be added to the administrator's management group and displays it on the display unit 504 (step S28). Then, as shown in FIG. 9, the terminal device 5 generates the above-described contract impossibility notification information notifying that a contract for adding the devices 31 and 32 to the administrator's management group cannot be made (step S29), and the generated contract impossibility notification information is transmitted from the terminal device 5 to the terminal devices 21 and 22 (step S30). On the other hand, when the terminal devices 21 and 22 acquire the contract impossibility notification information, they form the above-described contract impossibility notification image based on the acquired contract impossibility notification information and display it on the display unit 204 (step S31).

[0047] Also, assume that the terminal device 5 compares the model information included in the device information newly stored in the device information storage unit 531 with the target model information stored in the target model information storage unit 532 and determines that there is no device of the target model indicated by the target model information among the devices 31 and 32 owned by the user (step S32). In this case, the terminal device 5 generates device registration urging information for urging the user to register the target device to the cloud server 1 (step S33), and the generated device registration urging information is transmitted from the terminal device 5 to the terminal devices 21 and 22 (step S34). On the other hand, when the terminal devices 21 and 22 acquire the device registration urging information, they form a device registration urging image based on the acquired device registration urging information and display it on the display unit 204 (step S35).

[0048] Here, assume that the user refers to the device registration prompt image displayed on the display units 204 of the terminal devices 21 and 22 and performs the above-described device registration operation on the input units 205 of the terminal devices 21 and 22. In this case, the terminal devices 21 and 22 accept the device registration operation, generate the above-described device registration request information (step S36), and the generated device registration request information is transmitted from the terminal devices 21 and 22 to the cloud server 1 (step S37). On the other hand, when the cloud server 1 acquires the device registration request information, it extracts the user identification information, user information, area identification information, area information, device identification information, and device information included in the acquired device registration request information, and updates the information stored in the device information storage unit 131 in such a way that the extracted information is stored in the device information storage unit 131 in association with each other (step S38). Subsequently, the cloud server 1 generates registration completion notification information (step S39), and the generated registration completion notification information is transmitted from the cloud server 1 to the terminal devices 21 and 22 (step S40). On the other hand, when the terminal devices 21 and 22 acquire the registration completion notification information, they form a registration completion notification image based on the acquired registration completion notification information and display it on the display unit 204 (step S41). Thereafter, assume that the user performs the above-described registration completion notification operation for notifying the administrator that the registration of the target device to the cloud server 1 of the terminal devices 21 and 22 has been completed on the input units 205 of the terminal devices 21 and 22. In this case, the terminal devices 21 and 22 generate registration completion notification information (step S42), and as shown in FIG. 10, the generated registration completion notification information is transmitted from the terminal devices 21 and 22 to the terminal device 5 (step S43). Next, the series of processes from step S11 and later are executed again.

[0049] Also, when the day before the preset control target date arrives, the terminal device 5 generates power consumption history request information accordingly (step S44), and the generated power consumption history request information is transmitted from the terminal device 5 to the cloud server 1 (step S45). On the other hand, when the cloud server 1 acquires the power consumption history request information, it generates power consumption history information indicating the history of power consumption in the residential area corresponding to the area identification information included in the acquired power consumption history request information (step S46), and the generated power consumption history information is transmitted from the cloud server 1 to the terminal device 5 (step S47). On the other hand, when the terminal device 5 acquires the power consumption history information, it generates schedule notification information including schedule information indicating the operation schedules of the devices 31 and 32 to be managed based on the acquired power consumption history information (step S48). Subsequently, the generated schedule notification information is transmitted from the terminal device 5 to the cloud server 1 (step S49). On the other hand, when the cloud server 1 acquires the schedule notification information, it extracts the schedule information included in the acquired schedule notification information and stores the extracted schedule information in the schedule storage unit 134 (step S50). Thereafter, the above-mentioned schedule registration completion notification information is transmitted from the cloud server 1 to the terminal device 5 (step S51). On the other hand, when the terminal device 5 acquires the schedule registration completion notification information, it forms a schedule notification image based on the schedule information included in the acquired schedule registration completion notification information and displays it on the display unit 504 (step S52). Next, the terminal device 5 generates schedule notification information including the schedule information (step S53), and the generated schedule notification information is transmitted from the terminal device 5 to the terminal devices 21 and 22 (step S54). On the other hand, when the terminal devices 21 and 22 acquire the schedule notification information, they form a schedule notification image based on the schedule information included in the acquired schedule notification information and display it on the display unit 204 (step S55).

[0050] After that, as shown in FIG. 11, when the preset control target date arrives, the cloud server 1 generates control information for controlling the devices 31 and 32 based on the schedule information stored in the schedule storage unit 134 (step S56), and the generated control information is transmitted from the cloud server 1 to the devices 31 and 32 (step S57). On the other hand, when the devices 31 and 32 acquire the control information, they operate based on the acquired control information (step S58). Next, when the terminal device 5 determines that the control end time indicated by the generated schedule information has arrived based on the generated schedule information, it forms a control end notification image and displays it on the display unit 504 (step S59).

[0051] Also, assume that the administrator performs a cancellation preparation operation on the input unit 505 of the terminal device 5 to cause the user to cancel the contract regarding the management of the devices 31 and 32. In this case, the terminal device 5 receives the cancellation preparation operation, generates the above-described cancellation information (step S60), and transmits the generated cancellation information from the terminal device 5 to the terminal devices 21 and 22 (step S61). On the other hand, when the terminal devices 21 and 22 acquire the cancellation information, they form a cancellation image based on the acquired cancellation information and display it on the display unit 204 (step S62). Here, assume that the user performs a cancellation operation on the input unit 205 of the terminal devices 21 and 22 to cancel the contract for the service of managing the devices 31 and 32 by the administrator. In this case, the terminal devices 21 and 22 receive the cancellation operation, generate the above-described cancellation request information (step S63), and transmit the generated cancellation request information from the terminal devices 21 and 22 to the terminal device 5 (step S64). On the other hand, when the terminal device 5 acquires the cancellation request information, it generates management device deletion request information including the device identification information, management group identification information, and administrator identification information of the target devices 31 and 32 in response to this (step S65). As shown in FIG. 12, the generated management device deletion request information is transmitted from the terminal device 5 to the cloud server 1 (step S66). On the other hand, when the cloud server 1 acquires the management device deletion request information, it extracts the device identification information included in the acquired management device deletion request information and updates the device identification information stored in the management group information storage unit 132 in such a way as to delete the extracted device identification information from the management group information storage unit 132 (step S67). Subsequently, the cloud server 1 generates the above-described deletion completion notification information (step S68), and the generated deletion completion notification information is transmitted from the cloud server 1 to the terminal device 5 (step S69). On the other hand, when the terminal device 5 acquires the deletion completion notification information, it forms a deletion completion notification image based on the acquired deletion completion notification information and displays it on the display unit 504 (step S70). Thereafter, the terminal device 5 generates cancellation completion notification information based on the deletion completion notification information (step S71), and the generated cancellation completion notification information is transmitted from the terminal device 5 to the terminal devices 21 and 22 that are the transmission sources of the management device deletion request information (step S72).On the other hand, when the terminal devices 21 and 22 acquire the cancellation completion notification information, based on the acquired cancellation completion notification information, they form a cancellation completion notification image and display it on the display unit 204 (step S73).

[0052] Next, the device registration management process executed by the terminal device 5 according to the present embodiment will be described with reference to FIGS. 13 and 14. Note that this device registration management process starts when a program for executing the device registration management process in the terminal device 5 is activated. First, as shown in FIG. 13, the contract-related information notification unit 511 determines whether or not it has received the above-described contract invitation operation (step S201). Here, when the contract-related information notification unit 511 determines that it has not received the contract invitation operation (step S201: No), the process of step S221 described later is executed. On the other hand, when the contract-related information notification unit 511 determines that it has received the contract invitation operation (step S201: Yes), it generates the above-described contract invitation information and transmits it to the terminal devices 21 and 22 (step S202). Next, the device information acquisition unit 517 determines whether or not it has acquired the above-described contract commitment notification information transmitted from the terminal devices 21 and 22 (step S203). Here, when the device information acquisition unit 517 determines that it has not acquired the contract commitment notification information (step S203: No), the process of step S221 described later is executed. On the other hand, when the device information acquisition unit 517 determines that it has acquired the contract commitment notification information (step S203: Yes), in response thereto, it generates user device information request information for requesting the transmission of the device identification information and device information of the devices 31 and 32 used by the user to the cloud server 1 and transmits it to the cloud server 1 (step S204). As a result, the device information acquisition unit 517 acquires device information notification information including area identification information, area information, device identification information, device information, and device status information transmitted from the cloud server 1 (step S205).

[0053] Next, the target device specifying unit 512 compares the model information included in the device information newly stored in the device information storage unit 531 with the target model information stored in the target model information storage unit 532 to determine whether there is a device of the target model indicated by the target model information among the devices 31 and 32 owned by the user (step S206). Here, if the target device specifying unit 512 determines that there is a device of the target model indicated by the target model information among the devices 31 and 32 owned by the user (step S206: Yes), the process of step S209 described later is executed. On the other hand, if the target device specifying unit 512 determines that there is no device of the target model indicated by the target model information among the devices 31 and 32 owned by the user (step S206: No), it generates the above-mentioned device registration reminder information and transmits it to the terminal devices 21 and 22 (step S207). Subsequently, the device information acquisition unit 517 determines whether it has acquired the registration completion notification information transmitted from the terminal devices 21 and 22 (step S208). Here, if the device information acquisition unit 517 determines that it cannot acquire the registration completion notification information transmitted from the terminal devices 21 and 22 (step S208: No), the process of step S221 described later is executed. On the other hand, if the device information acquisition unit 517 determines that it has acquired the registration completion notification information transmitted from the terminal devices 21 and 22 (step S208: Yes), the management group information acquisition unit 513 generates the above-mentioned management group information request information including the device identification information of the devices 31 and 32 that are the target models and transmits it to the cloud server 1 (step S209). As a result, the management group information acquisition unit 513 acquires the management group notification information including the administrator identification information, the management group identification information, and the management type information transmitted from the cloud server 1 (step S210).

[0054] Thereafter, the management target determination unit 514 determines whether the devices 31 and 32 still belong to the management group of another administrator (step S211). Here, the management target determination unit 514 determines whether the devices 31 and 32 already belong to the management group of another administrator based on whether the management type information stored in the administrator information storage unit 533 matches the management type information included in the acquired management group information. Here, when the management target determination unit 514 determines that the devices 31 and 32 do not already belong to the management group of another administrator (step S211: Yes), the management group information acquisition unit 513 generates the above-mentioned management device information request information and transmits it to the cloud server 1 (step S212). As a result, the management group information acquisition unit 513 acquires management device notification information including management group identification information, management group information, and device identification information transmitted from the cloud server 1 (step S213). At this time, the management group information acquisition unit 513 extracts the management group identification information, management group information, and device identification information included in the acquired management device notification information and notifies the display control unit 516. Then, the display control unit 516 forms a management device list notification image for notifying a list of the devices 31 and 32 managed by the administrator based on the management group identification information, management group information, and device identification information notified from the management group information acquisition unit 513, and displays it on the display unit 504 (step S214).

[0055] Next, the registration management unit 519 determines whether it has received the above-described management group designation operation (step S215). Here, if the registration management unit 519 determines that it has not received the management group designation operation (step S215: No), the process of step S221 described below is executed. On the other hand, if the registration management unit 219 determines that it has received the management group designation operation (step S215: Yes), it generates management device addition request information including the device identification information, management group identification information, and administrator identification information of devices 31 and 32 and transmits it to the cloud server 1 (step S216). Subsequently, when the registration management unit 519 acquires the additional registration completion notification information transmitted from the cloud server 1 (step S217), it notifies the display control unit 516 of the acquired additional registration completion notification information. Then, based on the notified additional registration completion notification information, the display control unit 516 forms an additional registration completion notification image notifying that devices 31 and 32 have been newly registered as management targets and displays it on the display unit 504 (step S218), and then the process of step S211 described below is executed.

[0056] Also, if the management target determination unit 514 determines in step S211 that devices 31 and 32 already belong to the management group of another administrator (step S211: No), the notification unit 515 generates the above-described error notification information for devices 31 and 32 and notifies the display control unit 516. Then, based on the notified error notification information, the display control unit 516 forms the above-described error notification image and displays it on the display unit 504 (step S219). Thereafter, the notification unit 515 generates the above-described contract unavailability notification information for devices 31 and 32 and transmits it to the terminal devices 21 and 22 (step S220).

[0057] Next, as shown in FIG. 14, the schedule generation unit 518 determines whether the day before the control target date for controlling the devices 31 and 32 to be managed, which are preset, has arrived (step S221). Here, if the schedule generation unit 518 determines that the day before the control target date has not yet arrived (step S221: No), the process of step S228 described later is executed. On the other hand, if the schedule generation unit 518 determines that the day before the control target date has arrived (step S221: Yes), it generates power consumption history request information for requesting the transmission of power consumption history information indicating the history of power consumption in the residential area to the cloud server 1 and transmits it to the cloud server 1 (step S222). As a result, the schedule generation unit 518 acquires the power consumption history information transmitted from the cloud server 1 (step S223). Subsequently, the schedule generation unit 518 generates schedule information indicating the operation schedules of the devices 31 and 32 to be managed based on the acquired power consumption history information. Then, the schedule generation unit 518 generates schedule notification information including the generated schedule information and transmits it to the cloud server 1 (step S224). After that, when the schedule generation unit 518 acquires the schedule registration completion notification information transmitted from the cloud server 1 (step S225), it notifies the generated schedule information to the display control unit 516 and the notification unit 515. Then, the display control unit 516 forms a schedule notification image based on the notified schedule information and displays it on the display unit 504 (step S226). Also, the notification unit 515 generates schedule notification information including the notified schedule information and transmits it to the terminal devices 21 and 22 (step S227).

[0058] Next, the display control unit 516 determines whether or not the control end time indicated by the schedule information notified from the schedule generation unit 518 has arrived (step S228). Here, if the display control unit 516 determines that the control end time indicated by the schedule information has not yet arrived (step S228: No), the process of step S230 described later is executed. On the other hand, if the display control unit 516 determines that the control end time indicated by the schedule information has arrived (step S228: Yes), it forms a control end notification image and causes it to be displayed on the display unit 504 (step S229).

[0059] Subsequently, the contract-related information notification unit 511 determines whether it has received the above-described cancellation preparation operation (step S230). Here, if the contract-related information notification unit 511 determines that it has not yet received the cancellation preparation operation (step S230: No), the process of step S201 is executed again. On the other hand, if the contract-related information notification unit 511 determines that it has received the cancellation preparation operation (step S230: Yes), accordingly, it generates the above-described cancellation information and transmits it to the terminal devices 21 and 22 (step S231). Thereafter, the registration management unit 519 determines whether it has acquired the above-described cancellation request information (step S232). Here, if the registration management unit 519 determines that it has not been able to acquire the cancellation request information (step S232: No), the process of step S201 is executed again. On the other hand, if the registration management unit 519 determines that it has acquired the cancellation request information (step S232: Yes), accordingly, it generates management device deletion request information including the device identification information, management group identification information, and administrator identification information of the devices 31 and 32 and transmits it to the cloud server 1 (step S233). Next, when the registration management unit 519 acquires the deletion completion notification information transmitted from the cloud server 1 (step S234), based on the acquired deletion completion notification information notified to the display control unit 516 and the contract-related information notification unit 511, it forms a deletion completion notification image notifying that the devices 31 and 32 have been deleted from the management target and displays it on the display unit 504 (step S235). Also, the contract-related information notification unit 511 generates cancellation completion notification information based on the notified deletion completion notification information, and transmits the generated cancellation completion notification information to the terminal devices 21 and 22 that are the transmission sources of the management device deletion request information (step S236). Subsequently, the process of step S201 is executed again.

[0060] Next, the device management process executed by the cloud server 1 according to the present embodiment will be described with reference to FIGS. 15 and 16. This device management process starts when a program for executing the device management process in the cloud server 1 is launched. Note that when the device state acquisition unit 118 of the cloud server 1 acquires the device state notification information periodically transmitted from the devices 31 and 32 in parallel with this device management process, it extracts the device identification information and the device state information included in the acquired device state notification information, and executes a process of storing the extracted information in association with each other in the device information storage unit 131. Also, when the power information acquisition unit 115 of the cloud server 1 acquires the power consumption notification information periodically transmitted from the power measurement devices 61 and 62 in parallel with this device management process, it extracts the power consumption information included in the acquired power consumption notification information and the area identification information for identifying the residential area corresponding thereto, and stores the extracted power consumption information and area identification information in the power consumption information storage unit 133 in association with the date information indicating the date when the power consumption notification information was acquired.

[0061] First, as shown in FIG. 15, the device information notification unit 112 determines whether or not it has acquired the above-described user device information request information transmitted from the terminal device ⑤ (step S101). Here, when the device information notification unit 112 determines that it has not acquired the user device information request information (step S101: No), the process of step S103 described later is executed. On the other hand, when the device information notification unit 112 determines that it has acquired the user device information request information (step S101: Yes), it selects the area identification information, area information, device identification information, device information, and device state information corresponding to the user identification information and user information included in the acquired user device information request information from among the area identification information, area information, device identification information, device information, and device state information stored in the device information storage unit 131. Then, the device information notification unit 112 generates device information notification information including the selected area identification information, area information, device identification information, device information, and device state information, and transmits it to the terminal device ⑤ (step S102).

[0062] Next, the management group information notification unit 113 determines whether or not it has acquired the above-described management group information request information transmitted from the terminal device 5 (step S103). Here, if the management group information notification unit 113 determines that it has not acquired the management group information request information (step S103: No), the process of step S105 described later is executed. On the other hand, if the management group information notification unit 113 determines that it has acquired the management group information request information (step S103: Yes), it searches for the administrator identification information, management group identification information, and management type information stored in the management group information storage unit 132 that correspond to the device identification information included in the acquired management group request information. Then, the management group information notification unit 113 generates management group notification information according to the search result and transmits it to the terminal device 5 (step S104).

[0063] Subsequently, the management group information notification unit 113 determines whether or not it has acquired the above-described management device information request information transmitted from the terminal device 5 (step S105). Here, if the management group information notification unit 113 determines that it has not acquired the management device information request information (step S105: No), the process of step S107 described later is executed. On the other hand, if the management group information notification unit 113 determines that it has acquired the management device information request information (step S105: Yes), it selects the management group identification information, management group information, and device identification information corresponding to the administrator identification information included in the acquired management device information request information from among the device identification information stored in the management group information storage unit 132, and generates management device notification information including the selected management group identification information, management group information, and device identification information and transmits it to the terminal device 5 (step S106).

[0064] After that, the management group information management unit 114 determines whether it has acquired the above-described management device addition request information transmitted from the terminal device 5 (step S107). Here, if the management group information management unit 114 determines that it has not acquired the management device addition request information (step S107: No), the process of step S110 described below is executed. On the other hand, if the management group information management unit 114 determines that it has acquired the management device addition request information (step S107: Yes), it updates the information stored in the management group information storage unit 132 in such a way that the management group identification information and the device identification information included in the acquired management device addition request information are associated with each other and stored in the management group information storage unit 132 (step S108). Next, the management group information management unit 114 generates registration completion notification information notifying that the management group identification information and the device identification information included in the acquired management device addition request information have been newly stored in the management group information storage unit 132 in association with each other, and transmits the information to the terminal device 5 (step S109).

[0065] Subsequently, the device registration unit 111 determines whether it has acquired the above-described device registration request information transmitted from the terminal devices 21 and 22 (step S110). Here, if the device registration unit 111 determines that it has not acquired the device registration request information (step S110: No), the process of step S113 described below is executed. On the other hand, if the device registration unit 111 determines that it has acquired the device registration request information (step S110: Yes), it extracts these pieces of information included in the acquired device registration request information and updates the information stored in the device information storage unit 131 in such a way that they are associated with each other and stored in the device information storage unit 131 (step S111). After that, the device registration unit 111 generates registration completion notification information and transmits the information to the terminal devices 21 and 22 (step S112).

[0066] Next, the power consumption history notification unit 116 determines whether it has acquired the above-described power consumption history request information transmitted from the terminal device 5 (step S113). Here, if the power consumption history notification unit 116 determines that it has not acquired the power consumption history request information (step S113: No), the process of step S115 described later is executed. On the other hand, if the power consumption history notification unit 116 determines that it has acquired the power consumption history request information (step S113: Yes), it generates power consumption history information indicating the history of the power consumption in the residential area corresponding to the area identification information included in the acquired power consumption history request information and transmits it to the terminal device 5 (step S114).

[0067] Subsequently, as shown in FIG. 16, the schedule acquisition unit 119 determines whether it has acquired the above-described schedule notification information transmitted from the terminal device 5 (step S115). Here, if the schedule acquisition unit 119 determines that it has not acquired the schedule notification information (step S115: No), the process of step S118 described later is executed. On the other hand, if the schedule acquisition unit 119 determines that it has acquired the schedule notification information (step S115: Yes), it extracts the schedule information included in the acquired schedule notification information and stores the extracted schedule information in the schedule storage unit 134 (step S116). Thereafter, the schedule acquisition unit 119 transmits schedule registration completion notification information to the terminal device 5 (step S117).

[0068] Next, the device control unit 117 determines whether the control target date has arrived (step S118). Here, if the device control unit 117 determines that the control target date has not yet arrived (step S118: No), the process of step S120 described later is executed. On the other hand, if the device control unit 117 determines that the control target date has arrived (step S11B: Yes), based on the schedule information stored in the schedule storage unit 134, it generates control information for controlling the devices 31 and 32 and transmits it to the devices 31 and 32 (step S119).

[0069] Subsequently, the management group information management unit 114 determines whether it has acquired the aforementioned management device deletion request information transmitted from the terminal device 5 (step S120). Here, if the management group information management unit 114 determines that it has not acquired the management device deletion request information (step S120: No), the process of step S101 is executed again. On the other hand, if the management group information management unit 114 determines that it has acquired the management device deletion request information (step S120: Yes), it extracts the device identification information included in the acquired management device deletion request information, and updates the device identification information stored in the management group information storage unit 132 in such a way that the device identification information stored in the management group information storage unit 132 is deleted (step S121). After that, the management group information management unit 114 generates deletion completion notification information notifying that the device identification information included in the acquired management device deletion request information has been deleted from the management group information storage unit 132, and transmits it to the terminal device 5 (step S122). Next, the process of step S101 is executed again.

[0070] As described above, according to the device management system according to the present embodiment, when the registration management unit 519 determines that the devices 31 and 32 specified as the management targets of one administrator are not the management targets of other administrators, the specified devices 31 and 32 are registered as the management targets of the administrator. Thereby, since it is possible to prevent the control by a plurality of administrators from being executed repeatedly for the same devices 31 and 32, the administrator can smoothly provide the device management service for the devices 31 and 32 for which the user is permitted to be the target of the device management service.

[0071] Incidentally, in the power aggregation business, the administrator (aggregator) conducting the aggregation business obtains permission from users to control so-called energy storage devices in ordinary households, and controls the energy storage devices according to the power supply and demand situation. Specifically, in order to discharge the energy storage device and the battery of an electric vehicle during a time period when the power supply is insufficient, the power conditioner is controlled to charge the energy storage device and the battery of the electric vehicle before the time period when the power supply is insufficient, or the water heater is controlled to boil water for use during the time period when the power supply is insufficient before the time period when the power supply is insufficient. Alternatively, in order to charge the energy storage device and the battery of the electric vehicle during a time period when surplus power is generated, the power conditioner may be controlled to discharge the energy storage device and the battery of the electric vehicle before the time period when surplus power is generated to secure the charging capacity. Here, among the energy storage devices owned by users, there are also energy storage devices that do not want to be placed under the control of the administrator. Also, if permission is given to multiple administrators to control the same energy storage device, the control of the same energy storage device by multiple administrators may overlap, and as a result, there is a risk of a situation where the energy storage device cannot be controlled as intended by each of the multiple administrators. Furthermore, the energy storage devices installed in each residential area managed by the administrator generally vary in the region where the residential area exists or in terms of performance. Therefore, when controlling these energy storage devices, it is necessary to consider the region where the energy storage device is installed or its performance.

[0072] On the other hand, according to the device management system according to the present embodiment, in response to an operation of concluding a contract for providing a device management service or an operation of canceling the contract between the aggregator and the user, the devices 31 and 32 can be made the management targets of the aggregator or excluded from the management targets. Therefore, it becomes easier to grant the aggregator the authority to control the devices 31 and 32 according to the user's selection. For example, the control authority given to the aggregator can be limited to the control of energy storage devices used for power supply and demand, or the operation content of the energy storage devices that the aggregator can control can be limited to only the operations related to power supply and demand defined in the contract. Also, when newly granting control authority to the aggregator, if another competing aggregator already has the control authority, by preventing the new aggregator from being granted the authority, it is possible to prevent the control by a plurality of aggregators of the same devices 31 and 32 from being executed redundantly. Furthermore, according to the device management system according to the present embodiment, since the aggregator can divide and manage the devices 31 and 32 into different management groups according to the area where they are installed or their performance, the control of the devices 31 and 32 can be executed smoothly.

[0073] As described above, the embodiments of the present disclosure have been described, but the present disclosure is not limited to the foregoing embodiments. For example, when the registration management unit 519 receives a management group designation operation performed by the administrator on the input unit 505, it may generate additional notice information for notifying the user of adding the devices 31 and 32 to the management group in response thereto and transmit the additional notice information to the terminal devices 21 and 22. Then, after transmitting the additional notice information to the terminal devices 21 and 22, when the registration management unit 519 acquires additional permission notice information for notifying the administrator that the user permits adding the devices 31 and 32 to the management group, which is transmitted from the terminal devices 21 and 22, it may generate management device addition request information for the devices 31 and 32 in response thereto and transmit the management device addition request information to the cloud server 1.

[0074] According to this configuration, it is possible to inquire the user whether the devices 31 and 32 can be added to the management group. For example, it is possible to suppress a situation where the user forgets a contract with another administrator and multiple administrators duplicate the management of the devices 31 and 32.

[0075] In the embodiment, the terminal devices 21 and 22 may transmit operation information including user identification information and area identification information and for operating the devices 31 and 32 installed in the user's residential area to the cloud server 1 in response to an operation on the input unit 205 of the user. When the cloud server 1 acquires the operation information, it may include an authority determination unit (not shown) that determines whether the user identified by the user identification information included in the acquired operation information has the operation authority for the devices 31 and 32 installed in the residential area identified by the area identification information. When the device control unit 117 of the cloud server 1 determines that the user corresponding to the operation information has the operation authority to operate the devices 31 and 32, it may control the devices 31 and 32 by generating control information based on the operation information and transmitting it to the devices 31 and 32. Further, when the cloud server 1 determines that the user corresponding to the operation information does not have the operation authority to operate the devices 31 and 32, it may include a device state notification unit (not shown) that generates state notification information for notifying the state of the devices 31 and 32 corresponding to the operation information and transmits it to the terminal devices 21 and 22. Thereby, according to the operation authority given to the user, it is possible to individually set the operation authority, the browsing authority of the state, etc. of the devices 31 and 32 for the user in units of residential areas. For example, it is possible to manage the authority to give a so-called full control authority of the devices 31 and 32 to a certain user and to allow only the browsing of the state of the devices 31 and 32 to another user.

[0076] In the embodiment, even when the management target determination unit 514 determines that the devices 31 and 32 already belong to the management group of another administrator, if the management type of that management group is different from the management type of the management group to which the administrator owning the terminal device 5 belongs, an example of making a determination that they are regarded as not yet belonging to the management group of another administrator has been described. However, not limited to this, when the devices 31 and 32 already belong to the management group of another administrator regardless of the management type of the management group of another administrator, the management target determination unit 514 may determine that the devices 31 and 32 already belong to the management group of another administrator.

[0077] In the embodiment, an example in which there is one cloud server 1 has been described, but it is not limited to this, and a configuration in which a plurality of cloud servers 1 are connected to the terminal device 5 may also be possible.

[0078] Moreover, the various functions of the cloud server 1, terminal devices 5, 21, and 22 according to the present disclosure can be realized not by a dedicated system but by using a normal computer system. For example, a program for executing the above operations is stored in a non-temporary recording medium (such as a CD-ROM (Compact Disc Read Only Memory)) readable by the computer system and distributed to a computer connected to a network, and by installing the program in the computer system, the cloud server 1, terminal devices 5, 21, and 22 that execute the above-described processing may be configured.

[0079] Also, the method of providing the program to the computer is arbitrary. For example, the program may be uploaded to a bulletin board (BBS (Bulletin Board System)) of a communication line and distributed to the computer via the communication line. Then, the computer starts this program and executes it in the same manner as other applications under the control of the OS (Operating System). Thereby, the computer functions as the cloud server 1, terminal devices 5, 21, and 22 that execute the above-described processing.

[0080] As described above, each embodiment and modification example of the present disclosure have been explained, but the present disclosure is not limited thereto. The present disclosure includes those in which embodiments and modification examples are appropriately combined, and those in which appropriate changes are made thereto.

[0081] Hereinafter, various aspects of the present disclosure will be collectively described as appendices.

[0082] (Appendix 1) An object device specifying unit that specifies a device to be a management target candidate from among at least one device held by a user based on at least one type of target model information indicating the types of devices to be managed by a first administrator; A management target determination unit that determines whether or not the specified device is a management target of a second administrator different from the first administrator; A registration management unit that registers the specified management target candidate device as a management target of the first administrator when it is determined that the specified management target candidate device is not a management target of the second administrator; A device control unit that controls the device registered as a management target of the first administrator, and a device management system. Device management system. (Appendix 2) A management group information management unit that manages the specified device as a device belonging to a first management group configured by the management target of the first administrator; A schedule generation unit that generates an operation schedule for at least one device belonging to the first management group, and further includes: The device control unit controls at least one device belonging to the first management group based on the operation schedule. The device management system according to Appendix 1. (Appendix 3) The management target determination unit determines whether or not the specified management target candidate device already belongs to a second management group to which a device managed by the second administrator belongs; When it is determined that the identified device to be managed does not belong to the second management group, the registration management unit adds the identified device to a first management group composed of devices under the management of the first administrator. The device management system according to Appendix 1 or 2. (Appendix 4) A display unit, When it is determined that the identified device to be managed belongs to the second management group, a display control unit that forms an error notification image indicating that the identified device to be managed cannot be added to the first management group and displays it on the display unit, and further includes: The device management system according to Appendix 3. (Appendix 5) Further includes a terminal device owned by the user, When the registration management unit determines that the identified device to be managed is not under the management of the second administrator, it generates additional notice information to notify the user that the identified device will be registered as a device under the management of the first administrator and transmits it to the terminal device. After that, when it acquires additional permission notice information transmitted from the terminal device notifying the first administrator that the user permits the device to be registered as a device under the management of the first administrator, it registers the identified device as a device under the management of the first administrator. The device management system according to any one of Appendices 1 to 4. (Appendix 6) An object device identification unit that identifies a device to be managed as a candidate from among at least one device owned by the user based on at least one type of target device information indicating the type of device to be managed by the first administrator, A management target determination unit that determines whether the identified device is under the management of a second administrator different from the first administrator, When it is determined that the identified device to be managed is not under the management of the second administrator, a registration management unit that registers the identified device to be managed as a device under the management of the first administrator, and includes: Device management device. (Appendix 7) The step in which a device management system identifies devices that are candidates for management from among at least one device held by a user based on at least one type of target device model information indicating the types of devices to be managed by a first administrator, The step in which the device management system determines whether the identified device is under the management of a second administrator who is different from the first administrator, The step in which, when the device management system determines that the identified device that is a candidate for management is not under the management of the second administrator, the device management system registers the identified device that is a candidate for management as a device under the management of the first administrator, The step in which the device management system controls the device registered as a device under the management of the first administrator, and A device management method. (Appendix 8) A program for causing a computer to function as a target device identification unit that identifies devices that are candidates for management from among at least one device held by a user based on at least one type of target device model information indicating the types of devices to be managed by a first administrator, a management target determination unit that determines whether the identified device is under the management of a second administrator who is different from the first administrator, a registration management unit that, when it is determined that the identified device that is a candidate for management is not under the management of the second administrator, registers the identified device that is a candidate for management as a device under the management of the first administrator, and

Industrial Applicability

[0083] The present disclosure is suitable as a device management system for an aggregator to provide a device management service to a user.

Description of Signs

[0084] 1 Cloud server, 5, 21, 22 Terminal devices, 31, 32 Devices, 41, 42 BBR, 61, 62 Power measurement devices, 101, 201, 501 CPUs, 102, 202, 502 Main memory units, 103, 203, 503 Auxiliary memory units, 106, 206, 506 Communication units, 109, 209, 509 Buses, 111 Device registration unit, 112 Device information notification unit, 113 Management group information notification unit, 114 Management group information management unit, 115 Power information acquisition unit, 116 Power consumption history notification unit, 117 Device control unit, 118 Device status acquisition unit, 119 Schedule acquisition unit, 131, 531 Device information memory units, 132 Management group information memory units, 133 Power consumption information memory units, 134 Schedule memory units, 204, 504 Display units, 205, 505 Input units, 211 Contract-related information acquisition unit, 212, 516 Display control units, 213 Contract management unit, 214 Registration reminder acquisition unit, 215 Device registration request unit, 216 Notification acquisition unit, 511 Contract-related information notification unit, 512 Target device identification unit, 513 Management group information acquisition unit, 514 Management target determination unit, 515 Notification unit, 517 Device information acquisition unit, 518 Schedule generation unit, 519 Registration management unit, 532 Target model information memory unit, 533 Administrator information memory unit, NW1 Wide area network, NW21, NW22 Local area networks

Claims

1. A target device specifying unit that specifies a device to be a management target candidate from among at least one device held by a user based on at least one type of target model information indicating the type of device to be managed by a first administrator; A management target determination unit that determines whether the specified device is a management target of a second administrator different from the first administrator; A registration management unit that, when it is determined that the specified management target candidate device is not a management target of the second administrator, registers the specified management target candidate device as a management target of the first administrator; A device control unit that controls the device registered as a management target of the first administrator, A device management system.

2. A management group information management unit that manages the specified device as a device belonging to a first management group composed of management targets of the first administrator; A schedule generation unit that generates an operation schedule for at least one device belonging to the first management group, wherein the device control unit controls at least one device belonging to the first management group based on the operation schedule, The device management system according to claim 1.

3. The management target determination unit determines whether the specified management target candidate device already belongs to a second management group to which a device managed by the second administrator belongs; The registration management unit, when it is determined that the specified management target candidate device does not belong to the second management group, adds the specified management target candidate device to a first management group composed of management targets of the first administrator, The device management system according to claim 1 or 2.

4. A display unit; A display control unit that, when it is determined that the specified management target candidate device belongs to the second management group, forms an error notification image indicating that the specified management target candidate device cannot be added to the first management group and displays the error notification image on the display unit, The device management system according to claim 3.

5. Further comprising a terminal device held by the user, When the registration management unit determines that the identified device to be managed is not under the management of the second administrator, it generates additional notice information to notify the user that it will register the identified device as a device to be managed by the first administrator, and then transmits the information to the terminal device. After that, when it obtains additional permission notice information transmitted from the terminal device notifying the first administrator that the user permits the registration of the device as a device to be managed by the first administrator, it registers the identified device as a device to be managed by the first administrator. The device management system according to claim 1 or 2.

6. An object device identification unit that identifies a candidate device to be managed from among at least one device owned by a user based on at least one type of target model information indicating the types of devices to be managed by a first administrator; A management target determination unit that determines whether the identified device is under the management of a second administrator different from the first administrator; A registration management unit that, when it is determined that the identified candidate device to be managed is not under the management of the second administrator, registers the identified candidate device to be managed as a device to be managed by the first administrator. Device management apparatus.

7. A step in which a device management system identifies a candidate device to be managed from among at least one device owned by a user based on at least one type of target model information indicating the types of devices to be managed by a first administrator; A step in which the device management system determines whether the identified device is under the management of a second administrator different from the first administrator; A step in which the device management system, when it is determined that the identified candidate device to be managed is not under the management of the second administrator, registers the identified candidate device to be managed as a device to be managed by the first administrator; A step in which the device management system controls the device registered as a device to be managed by the first administrator. Device management method.

8. A computer, An object device identification unit that identifies a candidate device to be managed from among at least one device owned by a user based on at least one type of target model information indicating the types of devices to be managed by a first administrator, A management target determination unit that determines whether the identified device is under the management of a second administrator different from the first administrator, When it is determined that the device of the specified management target candidate is not under the management of the second administrator, a registration management unit that registers the device of the specified management target candidate as a management target of the first administrator A program for functioning as

Images