JP7727964B2 - Control infrastructure server, device control system, method and program - Google Patents

Description

The present invention relates to a control infrastructure server and a device control system using the same, and more specifically to a control infrastructure server and device control system that generates control commands for controlled devices according to multiple independent application software programs.

Device control systems, such as smart houses and HEMS (Home Energy Management Systems), have been proposed for some time. These device control systems allow remote control of target devices such as storage batteries, EV chargers, heat pump water heaters, and solar power generators, and are known to improve quality of life by making energy more visible and increasing convenience.

In a device control system, application software (hereinafter also referred to as apps) provided by various application vendors can be used to enable controlled devices to perform various functions. For example, if the controlled device is an EV charger/discharger, a timer charging app can be used to enable the EV charger to perform a timer charging function, and an emergency departure app can be used to enable emergency charging when away from home.

However, because each application software generates device control commands according to its own independent algorithm, multiple application software may generate conflicting device control commands for the same controlled device. When conflicting device control commands are generated, the device control commands interfere with each other, resulting in the functions controlled by all application software not functioning properly.

Furthermore, with the recent liberalization of the electricity market, a technology called resource aggregation is becoming more widespread. This technology uses information and communications technology to remotely control and aggregate electricity from dispersed virtual power generation facilities, making it function as if it were a single power plant (virtual power plant (VPP)). With resource aggregation, a resource aggregator that manages electricity consumers with virtual power generation facilities performs demand response (hereinafter also referred to as "DR") on the electricity consumer side in accordance with the electricity supply and demand situation, and an equipment control system remotely controls the electricity consumer's controlled equipment in accordance with the DR, thereby balancing electricity supply and demand.

Patent Document 1 describes an equipment control system that compares the priority of equipment control information sent from application software with the threshold value for electrical equipment set by threshold setting information included in power supply and demand coordination request information, and does not execute operational control of electrical equipment based on equipment control information below the set threshold. With this equipment control system, when a power supply and demand coordination request such as demand response is made, priority is given to control aimed at power supply and demand coordination for the power consumer's equipment and facilities, and control aimed at improving quality of life is restricted.

Japanese Patent Application Laid-Open No. 2015-41201

In the device control system of Patent Document 1, as long as the threshold value for an electrical device set by the threshold setting information included in the power supply and demand coordination request information is set to a high value, control based on device control information sent from other application software cannot be executed, even if control is not being performed for the purpose of demand response.

However, as long as control aimed at demand response is not performed, there is no problem in achieving a balance between power supply and demand in resource aggregation, even if control aimed at improving quality of life is not restricted.

Furthermore, when an electricity consumer finds themselves in a situation where they need to leave their car urgently, they may want to prioritize control of their EV charger/discharger to enable emergency charging using an emergency trip app over demand response control.

In other words, for equipment control systems to become widespread, it is important that they operate stably and with flexible control that does not cause inconvenience to the daily lives and work of users who are electricity consumers, and that contributes to the smooth business operations of resource aggregators and other related parties.

The inventors of this application therefore recognized the need for technology that would enable flexible control in a device control system that generates control commands for controlled devices according to multiple independent application software programs.

The present invention has been developed in consideration of the above-mentioned problems, and its object is to provide a control infrastructure server and device control system that can achieve flexible control in a device control system that generates control commands for controlled devices according to multiple independent application software programs.

A control infrastructure server according to a representative embodiment of the present invention is communicatively connected to a device attribute management server that manages device attribute values of control-target devices and to multiple device control servers that generate device control commands, including control commands for the control-target devices. The control infrastructure server includes: an application priority storage unit that stores application priorities set for each application software executed by the device control servers and indicating the priority of execution authority for the device control commands; a receiving unit that receives the device control commands from the device control servers; an acquiring unit that acquires from the device attribute management server the priority threshold set for the control-target devices; a comparison/determination unit that compares the application priority set for the application software executed by the device control server that generated the received device control command with the priority threshold set for the control-target devices that are the targets of the device control commands, and determines whether the application priority is higher than the priority threshold; and a control permission unit that transmits the device control command to the device attribute management server only if the comparison and determination result shows that the application priority is higher than the priority threshold, thereby permitting the control command for the control-target devices.

The present invention provides a control infrastructure server and device control system that can achieve flexible control in a device control system that generates control commands for controlled devices according to multiple independent application software programs.

1 is a diagram showing a configuration of a device control system according to an embodiment of the present invention; 2 is a diagram illustrating an example of a connection configuration between a device attribute management server and devices in the device control system according to the present embodiment. FIG. FIG. 10 is a diagram illustrating an example of the configuration of a device attribute value table. FIG. 10 is a diagram illustrating an example of the configuration of an application priority table. FIG. 10 is a diagram illustrating an example of the configuration of a device status table. FIG. 10 is a diagram illustrating a processing flow of priority control processing. FIG. 2 is a diagram illustrating an example of the configuration of a device control command. FIG. 10 is a diagram illustrating an example of a combination of a control command and a control value. FIG. 10 is a diagram showing a processing flow of state recognition and state change processing. FIG. 10 is a diagram illustrating an example of the configuration of a device control command inquiry. FIG. 10 is a diagram showing a processing flow of a latest update information inquiry process. FIG. 10 is a diagram illustrating an example of the configuration of a priority threshold last update information query.

1. Overview of the Embodiments First, an overview of representative embodiments of the invention disclosed in this application will be described. Note that in the following description, as an example, reference numerals in the drawings corresponding to components of the invention are written in parentheses.

[1] A control infrastructure server according to a representative embodiment of the present invention is communicatively connected to a device attribute management server that manages device attribute values of control-target devices and to multiple device control servers that generate device control commands, including control commands for the control-target devices. The control infrastructure server includes: an application priority storage unit that stores application priorities set for each piece of application software executed by the device control servers and indicating the priority of execution authority for the device control commands; a receiving unit that receives the device control commands from the device control servers; an acquiring unit that acquires from the device attribute management server the priority threshold set for the control-target devices; a comparison/determination unit that compares the application priority set for the application software executed by the device control server that generated the received device control command with the priority threshold set for the control-target devices that are the targets of the device control commands, and determines whether the application priority is higher than the priority threshold; and a control permission unit that permits the control command for the control-target devices by transmitting the device control command to the device attribute management server only if, as a result of the comparison and determination, the application priority is higher than the priority threshold.

[2] In the control infrastructure server described in [1] above, the application priority and the priority threshold may be set using the same number of levels, which may be three or more.

[3] In the control infrastructure server described in [1] or [2] above, the device control command may include a control command for responding to a request for power supply and demand coordination.

[4] In the control infrastructure server described in [3] above, the application priority stored in the application priority storage unit may be a fixed value previously set for each piece of application software executed by the device control server, may include a value previously determined between the power supply and demand coordination requester and the user of the controlled device, and may be a value that cannot be updated based on the device control command from the device control server.

[5] The control infrastructure server described in [1] to [4] above may further include a notification unit, and when the receiving unit receives an inquiry regarding whether the device control command can be executed, the comparison and determination unit compares the application priority set for application software executed by the device control server that generated the device control command related to the received inquiry with a priority threshold set for the controlled device that is the target of the device control command, and the notification unit notifies the device control server of information regarding whether the device control command can be executed corresponding to the result of the comparison and determination, and the control permission unit may not send the device control command to the device attribute management server regardless of the result of the comparison and determination.

[6] In the control infrastructure server described in [5] above, when the receiving unit receives an inquiry about the latest update information of the priority threshold set for the controlled device, the acquiring unit may acquire the device attribute value of the controlled device from the device attribute management server, and the notifying unit may notify the device control server of the acquired device attribute value.

[7] In the control infrastructure server described in [1] to [6] above, the device attribute value may include a priority threshold set for the controlled device, a last-updated app ID that identifies application software executed by the device control server that generated a device control command that includes a control command instructing updating to the priority threshold, and a last-updated date and time that indicates the date and time of the update.

[8] A representative embodiment of the present invention provides a device control system comprising: a device attribute management server that manages device attribute values of the control target devices; a plurality of device control servers that generate device control commands including control commands for the control target devices; and a control infrastructure server described in [1] to [7]. The device control server generates device control commands including control commands for changing the priority threshold set for the control target devices. The device attribute management server has a device attribute value storage unit that stores the device attribute values of the control target devices. Upon receiving a device control command including a control command to change the priority threshold set for the control target devices, the device attribute management server updates information about the priority threshold set for the control target devices, which is included in the device attribute values stored in the device attribute value storage unit.

[9] In the device control system described in [8] above, the device control server may generate a device control command including a control command for changing the priority threshold set for the controlled device within a range of values not exceeding the application priority value set for the application software to be executed.

[10] In the device control system described in [8] above, the device control server may have a device status storage unit that stores information indicating the control status for each of the control-target devices, and upon receiving a notification of information indicating whether the device control command can be executed, the device control server may update the information indicating the control status stored in the device status storage unit for each of the control-target devices.

[11] A method according to a representative embodiment of the present invention is executed on a control infrastructure server communicatively connected to a device attribute management server that manages device attribute values of control-target devices and to multiple device control servers that generate device control commands, including control commands for the control-target devices. The method includes the steps of: storing application priorities that indicate the priority of execution authority for the device control commands, set for each application software executed by the device control servers; receiving the device control commands from the device control servers; acquiring a priority threshold set for the control-target devices from the device attribute management server; comparing the application priority set for the application software executed by the device control server that generated the received device control command with a priority threshold set for the control-target devices that are the targets of the device control commands, and determining whether the application priority is higher than the priority threshold; and permitting the control command for the control-target devices by transmitting the device control command to the device attribute management server only if the application priority is higher than the priority threshold as a result of the comparison and determination.

[12] A program according to a representative embodiment of the present invention causes a control infrastructure server communicably connected to a device attribute management server that manages device attribute values of control-target devices and to multiple device control servers that generate device control commands, including control commands for the control-target devices, to function as: means for storing application priorities that indicate the priority of execution authority for the device control commands, set for each application software executed by the device control servers; means for receiving the device control commands from the device control servers; means for acquiring a priority threshold set for the control-target devices from the device attribute management server; means for comparing the application priority set for the application software executed by the device control server that generated the received device control command with a priority threshold set for the control-target devices that are the targets of the device control commands, and determining whether the application priority is higher than the priority threshold; and means for permitting the control commands for the control-target devices by transmitting the device control command to the device attribute management server only if the application priority is higher than the priority threshold as a result of the comparison and determination.

2. Specific Examples of Embodiments Specific examples of embodiments of the present invention will be described below with reference to the drawings. In the following description, components common to the embodiments will be designated by the same reference numerals, and repeated description will be omitted.

Figure 1 shows the configuration of a device control system according to this embodiment.

The device control system is configured such that device attribute management servers 100A, 100B, and 100C, a control infrastructure server 200, and device control servers 300A, 300B, and 300C are communicatively connected via networks N1 and N2. When there is no need to distinguish between the device attribute management servers 100A, 100B, and 100C, device control servers 300A, 300B, and 300C, and devices M1, M2, and M3, they may be simply referred to as "device attribute management server 100," "device control server 300," and "device M."

The device attribute management servers 100A, 100B, and 100C, the control infrastructure server 200, and the device control servers 300A, 300B, and 300C may each be implemented as a single computer, or multiple servers may be implemented as a single computer. For example, the device attribute management servers 100A, 100B, and 100C may each be implemented as a single computer, or the device attribute management servers 100A, 100B, and 100C may each be implemented as a single computer. Similarly, the control infrastructure server 200 and the device attribute management servers 100A, 100B, and 100C may each be implemented as a single computer, or may each be implemented as a single computer. Each computer may have communication capabilities. The device attribute management servers 100A, 100B, and 100C, the control infrastructure server 200, and the device control servers 300A, 300B, and 300C implement various functions, described below, using programs installed in each.
The device control server 300 has installed thereon application software that realizes various control functions by generating device control commands for the devices M to be controlled. Examples of control functions realized by generating device control commands include, but are not limited to, a resource aggregator (power supply and demand coordination requester) in resource aggregation issuing a demand response (DR) command to a power consumer (user of device M) according to the power supply and demand situation, and remote control of a device M such as an EV charger according to conditions such as a timer. The device control server 300 has installed thereon different application software for each of these various control functions.
The application software is a program installed on the device control server 300, and when executed by the device control server 300, it not only generates device control commands for the controlled devices M, but also realizes functions (hereinafter also referred to as app functions) such as generating inquiries about the device control commands, changing the control status records of the controlled devices, and inquiring about the latest update information of the priority thresholds of the controlled devices. In this specification, the processing realized by the device control server 300, on which the application software program is installed, executing the installed application software may be described as the application software being the subject of the processing.
Note that, in this embodiment, a case where one application software is installed on one device control server 300 will be described as an example, but this is not limiting. Multiple application software may be installed on one device control server 300. In this case, one device control server 300 executes multiple application software, and one device control server 300 realizes multiple types of control functions in accordance with the multiple application software.

In the device control system according to this embodiment, the Internet or a dedicated network can be used as network N1 and network N2. Network N1 and network N2 may be configured as separate networks, or may be configured using the same network.

In the device control system according to this embodiment, devices M1, M2, and M3 are further connected to device attribute management servers 100A, 100B, and 100C in a manner that allows communication. When devices M1, M2, and M3 do not need to be distinguished from one another, they may be simply referred to as "device M."

Device M is the "device to be controlled (controlled device)" in this embodiment. Device M includes storage batteries, EV chargers, heat pump water heaters, solar power generators, etc., as well as other home appliances such as air conditioners and lighting fixtures.

Device attribute management servers 100A, 100B, and 100C respond to inquiries from the control infrastructure server 200 and manage the control status of devices M1, M2, and M3, which are the control target devices, respectively.

Device attribute management servers 100A, 100B, and 100C each include device connection units 101A, 101B, and 101C, device attribute value tables 102A, 102B, and 102C, and device attribute management units 103A, 103B, and 103C. When there is no need to distinguish between the device connection units 101A, 101B, and 101C, the device attribute value tables 102A, 102B, and 102C, and the device attribute management units 103A, 103B, and 103C, they may be simply referred to as the "device connection unit 101," the "device attribute value table 102," and the "device attribute management unit 103."

The device connection unit 101 is an interface that connects directly or indirectly to device M so that communication is possible, and also connects to the control infrastructure server 200 so that communication is possible.

The device attribute value table 102 is a table that stores device attribute values for managing device attributes, including priority thresholds, of the device M to be controlled, and is accessed by the device attribute management unit 103.

Figure 3 shows an example of the configuration of a device attribute value table.

As shown in FIG. 3, the device attribute value table 102 is configured as a data table linking a priority threshold, a last-updated app ID, and a last-updated date and time for each device M. In the example of FIG. 3, only a device attribute value for one device is stored. The device attribute value includes a device ID, a priority threshold, a last-updated app ID, and a last-updated date and time for each device M. When the device attribute management server 100 manages multiple devices, multiple device attribute values can be stored by linking the device attribute value in FIG. 3 to the device ID of the corresponding device M.

The priority threshold is a value set in device M, and is used during comparison and determination on the control infrastructure server 200 as a criterion for determining whether or not a device control command from application software can be executed. The priority threshold is set using the same number of levels as the application priority, which will be described later. The priority threshold is updated by the device control command from the application software.

The last updated app ID is the app ID of the application software that last updated the priority threshold of device M. App IDs are described below. The last updated date and time is a value that indicates the date and time when the priority threshold of device M was last updated. The last updated app ID and last updated date and time are updated when the priority threshold of device M is updated.

The device attribute management unit 103 is a functional unit executed by a program installed on the device attribute management server 100, and manages device attribute values, including priority thresholds, for device M while accessing the device attribute value table 102. Specifically, the device attribute management unit 103 sends device control commands sent from the control infrastructure server 200 to device M to execute control, and returns device attribute values stored in the device attribute value table 102 based on inquiries from the control infrastructure server 200.

The device attribute management unit 103 updates the priority threshold in the device attribute value table 102 based on the control command for setting the priority threshold.

The control infrastructure server 200 is a server that executes processing based on information received from the device control server 300. When the control infrastructure server 200 receives a device control command for a controlled device or an inquiry about a device control command, it determines whether the device control command can be executed based on a comparison between the application priority associated with the application ID included in the device control command and the priority threshold associated with the device ID included in the device control command. Details of this comparison will be described later. As a result of the comparison, the control infrastructure server 200 sends executable device control commands to the device attribute management server 100 and notifies the device control server 300 of the comparison result.

When the control infrastructure server 200 receives a query for last update information from the device control server 300, it obtains the device attribute values from the device attribute management server 100 and returns them to the device control server 300.

The control infrastructure server 200 includes an interconnection unit 201 (receiving unit), an application priority table 202 (corresponding to an application priority storage unit), and a priority control unit 203 (corresponding to an acquisition unit, comparison and determination unit, control permission unit, and notification unit).

The interconnection unit 201 is an interface that is communicatively connected to the device attribute management servers 100A, 100B, and 100C via network N1, and to the device control servers 300A, 300B, and 300C via network N2.

The application priority table 202 is a table that stores information about application priorities set for each piece of application software, and is accessed by the priority control unit 203 when comparing the priority with the priority threshold.

Figure 4 shows an example of the configuration of an application priority table.

As shown in Figure 4, the application priority table 202 is configured as a data table that links application IDs with application priorities. The application IDs are IDs set to identify application software installed on each of the device control servers 300A, 300B, and 300C.

The application priority is a value (e.g., a higher numerical value indicates a higher priority) used when determining whether a device control command from the associated application software will execute control on the controlled device, and is a value compared with the priority threshold. For example, if there is a higher possibility that control should be executed, the priority is set higher. In this way, the application priority is a value used for comparison with the priority threshold, and is not compared with application priorities associated with other application software.

In the example shown in Figure 4, consider application software with an application ID of AP2 and application software with an application ID of AP3. According to Figure 4, the application priority of AP2 is "3" and the application priority of AP3 is "5". Therefore, when the priority threshold of the control target device is "3", both AP2 and AP3 can be controlled. However, when the priority threshold of the control target device is "5", AP3 can be controlled but AP2 cannot. However, when both AP2 and AP3 can be controlled, both can be controlled, and so device control commands are executed in the order received by the control infrastructure server 200. Application priorities are preset, and the device control servers 300A, 300B, and 300C cannot change their own application priorities.

Application priorities are set using the same number of stages as the priority thresholds. The number of stages is set to three or more. The application priorities stored in the application priority table 202 are fixed values set in advance for each of the device control servers 300A, 300B, and 300C, and may include values determined in advance between the power supply and demand coordination requester and the user of device M.

In resource aggregation, a power supply and demand coordination requester is a resource aggregator that performs DR (Demand Response) on the side of power consumers (users of equipment M) who manage virtual power generation facilities, depending on the power supply and demand situation. In resource aggregation, to balance power supply and demand, a contract is concluded between the power consumer who owns the virtual power generation facility and the resource aggregator to enable the equipment control server 300 managed by the power supply and demand coordination requester to remotely control the equipment M managed by the power consumer using DR. When making this contract, it is possible to decide the degree of priority to be given to DR execution, and by setting the application priority of the equipment control server 300 to a high value, DR can be executed with priority over equipment control commands from other application software.

The application priority is a preset value that cannot be updated based on a device control command from the device control server 300 on which the application software is installed, as described below. The application priority may also be set by a control unit (not shown) within the control infrastructure server 200.

The priority control unit 203 is a functional unit executed by a program installed on the control infrastructure server 200. When it receives a device control command or a device control command inquiry for a controlled device from the device control server 300, it performs the above-mentioned comparison and judgment, and executes processing based on the results of the comparison and judgment. When it receives a last updater information inquiry from the device control server 300, the priority control unit 203 obtains the necessary information from the device attribute management server 100 and returns it to the device control server 300.

Here, we will explain the comparison and determination made by the priority control unit 203. When the priority control unit 203 (corresponding to the acquisition unit) receives a device control command for a controlled device or an inquiry about a device control command from the device control server 300, it accesses the application priority table 202 to acquire the application priority value associated with the application ID included in the device control command, and also requests and acquires from the device attribute management server 100 the priority threshold value associated with the device ID included in the device control command.

The priority control unit 203 (corresponding to the comparison/determination unit) compares the acquired application priority value with the priority threshold value to determine whether or not the device control command can be executed. When the application priority value is compared with the priority threshold value and the application priority is found to be higher than the priority threshold value, the priority control unit 203 determines that the device control command should be executed. For example, consider a case where a high value between the application priority and the priority threshold is defined as a high priority. In this case, the application priority is considered to be higher than the priority threshold value when the application priority value is equal to or greater than the priority threshold value. Therefore, when the application priority value is equal to or greater than the priority threshold value, the priority control unit 203 determines that the control can be executed, and when the application priority value is less than the priority threshold value, the priority control unit 203 determines that the control cannot be executed.
Conversely, for example, a low value between the application priority and the priority threshold may be defined as a high priority. In this case, when the application priority value is equal to or less than the priority threshold, the application priority is considered to have a higher priority than the priority threshold. Therefore, when the application priority value is equal to or less than the priority threshold, it is determined that control is executable, and when the application priority value is greater than the priority threshold, it is determined that control is not executable.

When a device control command has been received, the priority control unit 203 (corresponding to the control permission unit) transmits the device control command to the device attribute management server 100 only if the application priority is higher than the priority threshold (if it is determined that control execution is possible), thereby permitting the control command for the controlled device. If the application priority is not higher than the priority threshold (if it is determined that control execution is not possible) or if the received command was an inquiry about a device control command, the priority control unit 203 does not transmit the device control command to the device attribute management server 100.

The priority control unit 203 (corresponding to the notification unit) notifies the device control server 300 of information on whether or not the device control command can be executed, depending on the result of the comparison.

The device control server 300 is a server managed by an application vendor (Company α, Company β, and Company γ in Figure 1). The application vendor is the entity that provides the application software that generates device control commands. The application software is a program installed on the device control server 300, and is executed by the device control server 300 to realize the app functions.

Device control servers 300A, 300B, and 300C each include communication units 301A, 301B, and 301C, device status management tables 302A, 302B, and 302C, and application function units 303A, 303B, and 303C. When there is no need to distinguish between communication units 301A, 301B, and 301C, device status management tables 302A, 302B, and 302C, and application function units 303A, 303B, and 303C, they may be simply referred to as "communication unit 301," "device status management table 302," and "application function unit 303."

The communication unit 301 is an interface that connects to the control infrastructure server 200 via the network N2 so that communication is possible.

The device status management table 302 stores an app ID for identifying application software and a device status table that records the control status of the controlled device.

Figure 5 shows an example of the configuration of a device status table.

As shown in Figure 5, the device status table is configured as a data table linking device IDs with control states. The device ID is an ID for identifying the controlled device M. The control state is information indicating the execution status of a control command, and stores values such as "Controlling", which indicates that a control command has been sent and is being executed, "Paused", which indicates that a control command has been sent but not executed, and "Control Not Executed", which indicates that no control command has been sent. The control state for the controlled device M can be managed based on the states stored in the device status table.

The application function unit 303 is a function unit that realizes the function of executing processing by application software. Specifically, it accesses the device status management table 302 as needed, generates device control commands, generates device control command inquiries, changes the control status records of controlled devices, and generates inquiries for last update information.

The device control command may include a control command for responding to a request for power supply and demand coordination. A control command for responding to a request for power supply and demand coordination is a DR (demand response) command issued by a resource aggregator (power supply and demand coordination requester) in resource aggregation to a power consumer (user of device M) in accordance with the power supply and demand situation. The device control server 300 used by the resource aggregator (power supply and demand coordination requester) generates a device control command including a control command for responding to the power supply and demand coordination request. As a result, the device control server 300 generates a device control command including DR for the power consumer in accordance with the power supply and demand situation, and remotely controls the power consumer's controlled devices, thereby balancing power supply and demand.

In the device control system of this embodiment described above, the device attribute management server 100, control infrastructure server 200, and device control server 300 each execute the above-mentioned processes to perform priority control processing, situation assessment/status change processing, and causer identification processing. Here, "priority control processing" refers to processing that allows only device control commands from application software with a higher priority than the priority threshold set for the device to be controlled to be executed. "Situation assessment/status change processing" refers to processing that confirms whether the generated device control command is executable and reflects the confirmed control status in the device status management table. "Causal party identification processing" refers to processing that makes it possible to identify the application software that generated the device control command that caused the control status to be interrupted and the date and time the cause occurred. The specific processing flows for these priority control processing, situation assessment/status change processing, and causer identification processing are described below.

In the device control system of this embodiment, "priority control processing" can reject device control commands from application software with a priority lower than the priority threshold, and execute only device control commands from application software with a priority higher than the priority threshold. Setting priorities allows for highly flexible control.

In the device control system of this embodiment, the "situation recognition and status change processing" allows the application software to appropriately check whether the generated device control command is executable as needed. The application software can use the status change processing to reflect the results of the situation recognition processing in the control status of device M, the controlled device, managed in the device status management table 302.

Furthermore, in the device control system of this embodiment, when a device control command is interrupted, the "cause-causing entity identification process" allows the application software to identify the application software that generated the device control command that caused the interruption and the date and time the cause occurred.

For example, consider the case where an equipment control command including a demand response is interrupted. When demand response is interrupted, the resource aggregator's processing would be to start controlling another device in its place and impose a contractual penalty on the device that caused the interruption. However, by identifying the application software that generated the equipment control command that caused the interruption, it is possible to increase the degree of flexibility in the contract. If the application software that generated the equipment control command that caused the interruption is an emergency outing app, it would be possible to enter into a contract that exempts the supplier from liability for demand response interruptions up to two times a month. On the other hand, if the application software that generated the control command that caused the interruption is a breaker trip prevention app, it would also be possible to enter into a contract that exempts the supplier from liability for demand response interruptions in consideration of user convenience.

These processes will now be described in more detail.
[Priority Control Processing]
FIG. 6 is a diagram showing a processing flow of the priority control processing.

The device control server 300 generates a device control command and sends it to the control infrastructure server 200 (S101).

Figure 7 shows an example of the configuration of a device control command. Figure 8 shows an example of a combination of a control command and a control value.

As shown in Figure 7, a device control command is a command that includes an application ID, a device ID, a control command, and a control value. The application ID is the application ID of the application software that generated the device control command. The device ID is the device ID of the controlled device that is the target of the device control command. The control command and control value can be selected from predetermined combinations such as those shown in Figure 8. That is, if the control command is "charging setting," the control value can be either "start charging" or "stop charging." Similarly, if the control command is "charging allowable power setting," the power value to be set can be the control value, and if the control command is "priority threshold setting," the priority threshold to be set can be the control value.

The device control server 300 can generate device control commands that include a control command for changing the priority threshold set for a controlled device in accordance with application software, within a range of values that does not exceed the application priority value set for that application software. This device control command, including a control command for changing the priority threshold, is not executed if the application priority set for the application software executed by the generated device control server 300 is less than the priority threshold set for the controlled device. As a result, the device control server 300 can change the priority threshold only if the application priority is equal to or greater than the priority threshold. Furthermore, by using a "priority threshold setting" control command, the device control server 300 can set the priority threshold to be equal to the application priority set for the application ID of the target application software, thereby preventing the device control server 300 from controlling the controlled device in accordance with other application software with an application priority lower than that value.

When the control infrastructure server 200 receives a device control command, it accesses the application priority table 202 and obtains the application priority value associated with the application ID included in the device control command (step S102).

The control infrastructure server 200 further requests and obtains from the device attribute management server 100 the priority threshold value associated with the device ID included in the device control command (step S103). In step S103, in response to the request from the control infrastructure server 200, the device attribute management server 100 extracts the priority threshold value included in the device attribute value associated with the requested device ID from the device attribute value table 102 and passes it to the control infrastructure server 200.

The control infrastructure server 200 compares the acquired application priority value with the priority threshold value to determine whether the device control command can be executed (step S104). If the application priority is higher than the priority threshold value, specifically if the application priority value is equal to or greater than the priority threshold value (step S104: YES), the control infrastructure server 200 determines that control can be executed. On the other hand, if the application priority is not higher than the priority threshold value, specifically if the application priority value is less than the priority threshold value (step S104: NO), the control infrastructure server 200 determines that control cannot be executed.

If the control infrastructure server 200 determines that control cannot be executed (step S104: NO), it notifies the device control server 300 of the result of the comparison that control is rejected (step S105).

If the control infrastructure server 200 determines that control can be executed (step S104: YES), it notifies the device control server 300 that control is permitted (control execution) as a result of the comparison (step S106), and sends a device control command to the device attribute management server 100 that obtained the priority threshold (step S107).

When the device control server 300 receives notification of either control denial or control permission, it can update the control status of the controlled device in the device status table stored in the device status management table 302.

When the device attribute management server 100 receives the device control command, it causes the device M to execute the control command (step S108) and transmits the control results of the device control command to the control infrastructure server 200 (step S109).

When the control infrastructure server 200 receives the control result of the device control command, it transmits the control result to the device control server 300 corresponding to the application ID included in the device control command (step S110).
[Status Grasping and Status Change Processing]
FIG. 9 is a diagram showing a processing flow of the status recognition and status change processing.

The device control server 300 generates a device control command query and sends it to the control infrastructure server 200 (S201).

Figure 10 shows an example of the configuration of a device control command query.

A device control command inquiry inquires as to whether a device control command can be executed. As shown in FIG. 10, a device control command inquiry is an inquiry that includes an application ID, a device ID, a control command, and a control value, just like a device control command. In the device control server 300, the application function unit 303 selects a device whose control status in the device status table stored in the device status management table 302 is "under control" and generates a device control command inquiry. Note that the application function unit 303 may also generate device control command inquiries for device control commands whose control status in the device status table stored in the device status management table 302 is other than "under control." The application function unit 303 may generate device control command inquiries at predetermined time intervals.

When the control infrastructure server 200 receives a device control command, it accesses the application priority table 202 and obtains the application priority value associated with the application ID included in the device control command (step S202).

The control infrastructure server 200 further requests and obtains from the device attribute management server 100 the priority threshold value associated with the device ID included in the device control command (step S203). In step S203, in response to the request from the control infrastructure server 200, the device attribute management server 100 extracts the priority threshold value included in the device attribute value associated with the requested device ID from the device attribute value table 102 and passes it to the control infrastructure server 200.

The control infrastructure server 200 compares the acquired application priority value with the priority threshold value to determine whether the device control command can be executed (step S204). If the application priority is higher than the priority threshold value, specifically if the application priority value is equal to or greater than the priority threshold value (step S204: YES), the control infrastructure server 200 determines that control can be executed. On the other hand, if the application priority is not higher than the priority threshold value, specifically if the application priority value is less than the priority threshold value (step S204: NO), the control infrastructure server 200 determines that control cannot be executed.

If the control infrastructure server 200 determines that control cannot be executed (step S204: NO), it notifies the device control server 300 that control is denied (step S205).If the control infrastructure server 200 determines that control can be executed (step S204: YES), it notifies the device control server 300 that control is permitted (step S206).

When the device control server 300 receives the notification, it determines from the notification whether control execution was possible (step S207). If it determines that control execution was possible (step S207: YES), it waits for a certain period of time to periodically check the control status of device M (step S208), and then returns to the inquiry processing of step S201.

If it is determined in step S207 that control execution is not possible (step S207: NO), the control status in the device status table stored in the device status management table 302 is changed to "pause" (step S209). After the control status is changed, causer identification processing is performed as necessary.
[Causal party identification process]
FIG. 11 is a diagram showing the processing flow of the latest update information inquiry processing.

The device control server 300 generates a last update information inquiry and sends it to the control infrastructure server 200 (S301).

Figure 12 shows an example of the configuration of a last update information query.

The last update information query includes a device ID, as shown in Figure 12. The device ID included in this query indicates that you want to obtain the last update information for device M linked to this device ID.

When the control infrastructure server 200 receives the latest update information inquiry, it requests and obtains from the device attribute management server 100 the device attribute values associated with the device ID included in the device control command, i.e., the priority threshold, the last updated app ID, and the last update date and time (step S302). In step S302, in response to the request from the control infrastructure server 200, the device attribute management server 100 extracts the device attribute values associated with the requested device ID from the device attribute value table 102 and passes them to the control infrastructure server 200.

The control infrastructure server 200 transmits the acquired device attribute values associated with the device ID, i.e., the priority threshold, last updated app ID, and last update date and time, to the device control server 300 (step S303).

The device control server 300 identifies the last updated app ID based on the device attribute value associated with the transmitted device ID (step S304).

In the device control system of this embodiment described above, consider a case where, for example, application software on device control server 300B with an application priority of "3" generates a device control command and executes it, and then application software on device control server 300C with an application priority of "5" generates a device control command and changes the priority threshold as shown in Figure 3.

The device control server 300B executes periodic status assessment and status change processing at 11:20:00. The device control server 300B sends a device control command query to the control infrastructure server 200 (S201). The control infrastructure server 200 acquires the application priority associated with the application ID and the priority threshold associated with the device ID included in the device control command query (steps S202 and S203), and because the application priority "3" is lower than the priority threshold "5," notifies the device control server 300B of a control denial (step S205).

Upon receiving the notification, the device control server 300B determines whether control is being executed (step S207). If it determines that control is not being executed, it changes the control status in the device status management table (step S209) and executes the causer identification process.

In the causer identification process, the device control server 300B generates a last update information inquiry (step S301). The control infrastructure server 200 acquires the device attribute values associated with the device ID included in the last update information inquiry (step S302) and sends them to the device control server 300B (step S303).

As shown in Figure 3, the device attribute values include a priority threshold of "5", a last updated app ID of "AP3", and a last updated date and time of "2021/5/31 11:19:55". Based on these values, device control server 300B can determine that the application software with the app ID of "AP3" set the priority threshold to 5, and that the priority threshold change occurred at "2021/5/31 11:19:55". Based on these values, device control server 300B can generate any further necessary device control commands.

The control infrastructure server 200 according to the embodiment described above is a control infrastructure server 200 communicably connected to a device attribute management server 100 that manages device attribute values of control target devices and a plurality of device control servers 300 that generate device control commands including control commands for control target devices, and includes an application priority storage unit (202) that stores application priorities that indicate the priority of execution authority for device control commands set for each application software executed by the device control server 300, a receiving unit (201) that receives device control commands from the device control server 300, and a priority threshold set for the control target devices (M1, M2, M3) that is received from the device attribute management server (100A, 100B, 100C). a comparison and determination unit (203) that compares the application priority set for application software executed by the device control server (300A, 300B, 300C) that generated the received device control command with a priority threshold set for the control target device (M1, M2, M3) that is the target of the device control command to determine whether the application priority is higher than the priority threshold, and a control permission unit (203) that transmits the device control command to the device attribute management server (100A, 100B, 100C) only if the comparison and determination result shows that the application priority is higher than the priority threshold, thereby permitting the control command to be sent to the control target device (M1, M2, M3). This enables flexible control to be achieved in a device control system that generates control commands for control target devices according to multiple independent application software programs.

In addition, the application priority and priority threshold may be set using the same number of levels, three or more. This allows values to be set that do not cause inconvenience to the daily lives and work of users who are electricity consumers, and that contribute to the smooth operation of business for related parties such as resource aggregators.

The device control command may also include a control command for responding to a power supply and demand coordination request. In this way, the device control server 300 can generate device control commands including DR for the power consumer side according to the power supply and demand situation, and remotely control the power consumer's controlled devices, thereby balancing power supply and demand.

The application priority stored in the application priority storage unit may be a fixed value preset for each piece of application software executed by the device control server, may include a value previously determined between the power supply and demand coordination requester and the user of the controlled device, and may be a value that cannot be updated based on a device control command from the device control server. In this way, when the device control server 300 managed by the power supply and demand coordination requester concludes a contract to enable remote control of the device M managed by the power consumer using DR, the content of the decision on the degree of priority given to DR execution can be reflected as the application priority setting value of the device control server 300.

The control infrastructure server 200 according to the embodiment further includes a notification unit. When the receiving unit receives an inquiry regarding the executable status of a device control command, the comparison/determination unit compares the application priority set for the application software executed by the device control server that generated the device control command related to the received inquiry with a priority threshold set for the controlled device that is the target of the device control command. The notification unit notifies the device control server of the executable status of the device control command corresponding to the result of the comparison/determination. The control permission unit may not send the device control command to the device attribute management server regardless of the result of the comparison/determination. In this way, the device control server can learn whether its device control command has been accepted or rejected, even after some time has passed since the device control command was generated.

In the control infrastructure server 200 according to the embodiment, when the receiving unit receives an inquiry about the latest update information of the priority threshold set for the controlled device, the acquiring unit may acquire the device attribute value of the controlled device from the device attribute management server, and the notifying unit may notify the device control server of the acquired device attribute value. In this way, if the device control server learns that a device control command it generated has been rejected, it can learn the cause of this result.

In the control infrastructure server 200 according to the embodiment, the device attribute value may include a priority threshold set for the controlled device, a last-updated app ID that identifies the application software executed by the device control server that generated the device control command, including a control command instructing updating to that priority threshold, and a last-updated date and time indicating the date and time of the update. In this way, if the device control server learns that a device control command it generated has been rejected, it can determine which application's operation resulted in that outcome and when.

The device control system according to the embodiment described above is a device control system comprising a device attribute management server that manages device attribute values of controlled devices, multiple device control servers that generate device control commands including control commands for the controlled devices, and the control infrastructure server. The device control server generates device control commands including control commands for changing the priority threshold set for the controlled devices, and the device attribute management server has a device attribute value storage unit that stores the device attribute values of the controlled devices. Upon receiving a device control command including a control command to change the priority threshold set for the controlled devices, the device attribute management server updates the information on the priority threshold set for the controlled devices, which is included in the device attribute values stored in the device attribute value storage unit. This allows the device control server to set the priority threshold as needed.

In the device control system according to the embodiment described above, the device control server may generate device control commands that include control commands for changing the priority threshold set for the controlled device within a range of values that does not exceed the application priority value set for the application software being executed. In this way, by setting the priority threshold equal to its own application priority, the device control server can prevent the device control server 300 from executing control over the controlled device in accordance with other application software that has an application priority lower than that value.

In the device control system according to the embodiment described above, the device control server may have a device status storage unit that stores information indicating the control status of each controlled device, and upon receiving a notification of whether a device control command can be executed, the device control server may update the information indicating the control status stored in the device status storage unit for each controlled device. This allows the device control server to know the control status of the controlled device.

(Extension of the embodiment)
The invention made by the present inventors has been specifically described above based on an embodiment, but it goes without saying that the invention is not limited thereto and can be modified in various ways without departing from the spirit of the invention.

For example, the configuration example shown in Figure 1 shows a case where the device attribute management server 100 and device M are connected in the manner shown in Figure 2(a), in which they are directly connected to the device, but this is not limited to this and they may be connected in other manners as shown in Figures 2(a) to 2(c). Furthermore, the manners shown in Figures 2(a) to 2(c) may be mixed. Also, while a configuration in which one device M is connected to one device attribute management server 100 is shown, a configuration in which multiple devices M are connected to one device attribute management server 100 may also be used.

Figure 2 shows an example of the connection configuration between the device attribute management server and devices in the device control system according to this embodiment. In Figure 2, (a) shows a direct connection to the device, (b) shows a connection via the device server, and (c) shows a connection via the controller.

2, the device attribute management server 100 is communicably connected to a device M installed in a home or the like of an electric power consumer via the Internet. In the embodiment shown in Fig. 2(a), the device attribute management server 100 and the device M are directly communicably connected. In this case, the device M has a communication function via the Internet.
2B, the device attribute management server 100 and device M are communicatively connected via a device server 401. In this case, device M also has a communication function via the Internet. The device server 401 has an interface function between device M and device attribute management server 100.
2(c), the device attribute management server 100 and device M are communicatively connected via a controller 402. In this case, the controller 402 has a communication function via the Internet, and the controller 402 and device M are communicatively connected via a wired connection or other wireless communication function. The controller 402 can be used to input manual control for the device, in addition to remote control.

Furthermore, the processing flows described using Figures 6, 9, and 11 in the above embodiments are not limited to those shown. For example, the order of processing S102 and S103 in Figure 6 and the order of processing S202 and S203 in Figure 9 may be reversed.

Furthermore, in the above embodiment, it was explained that higher values for priority and priority threshold are given priority, but lower values may also be given priority.

In addition, while the above embodiment has been described with reference to an example in which power demand and supply are controlled for controlled devices, the present invention is not limited to this. It is also applicable to controlling devices that are not managed by an administrator.

100 (100A, 100B, 100C)...Device attribute management server, N1, N2...Network, M1, M2, M3...Device, 101 (101A, 101B, 101C)...Device connection unit, 102 (102A, 102B, 102C)...Device attribute value table, 103 (103A, 103B, 103C)...Device attribute management unit, 200...Control infrastructure server, 201...Interconnection unit, 202...Application priority table, 203...Priority control unit, 300 (300A, 300B, 300C)...Device control server, 301 (301A, 301B, 301C)...Communication unit, 302 (302A, 302B, 302C)...Device status management table, 303 (303A, 303B, 303C)...Application function unit

Claims (12)

A control infrastructure server that is communicably connected to a device attribute management server that manages device attribute values of control target devices and a plurality of device control servers that generate device control commands including control commands for the control target devices,
an application priority storage unit that stores application priorities that are set for each piece of application software executed by the device control server and indicate priorities of execution authority for the device control command;
a receiving unit that receives the device control command from the device control server;
an acquisition unit that acquires the priority threshold set for the control target device from the device attribute management server;
a comparison and determination unit that compares an application priority set for application software executed by a device control server that generated the received device control command with a priority threshold set for a control target device that is the target of the device control command, and determines whether the application priority is higher than the priority threshold;
a control permission unit that permits a control command to be issued to a control target device by transmitting the device control command to the device attribute management server only when, as a result of the comparison and determination, the application priority has a priority higher than the priority threshold. The control infrastructure server according to claim 1,
The application priority and the priority threshold are set to the same number of stages, which is equal to or greater than three.
Control infrastructure server. 3. The control infrastructure server according to claim 1,
The equipment control command includes a control command for responding to a power supply and demand coordination request.
Control infrastructure server. The control infrastructure server according to claim 3,
the application priority stored in the application priority storage unit is a fixed value previously set for each application software executed by the device control server, includes a value previously determined between a power supply and demand coordination requester and a user of the control target device, and is a value that cannot be updated based on the device control command from the device control server;
Control infrastructure server. The control infrastructure server according to any one of claims 1 to 4,
Further comprising a notification unit,
When the receiving unit receives an inquiry about whether or not the device control command can be executed, the comparison and determination unit compares and determines an application priority set for application software executed by a device control server that generated the device control command related to the received inquiry with a priority threshold set for a control target device that is the target of the device control command, the notification unit notifies the device control server of information about whether or not the device control command can be executed, which corresponds to the result of the comparison and determination, and the control permission unit does not transmit the device control command to the device attribute management server regardless of the result of the comparison and determination.
Control infrastructure server. The control infrastructure server according to claim 5,
When the receiving unit receives an inquiry about last update information of the priority threshold set for the control target device, the acquiring unit acquires a device attribute value of the control target device from the device attribute management server, and the notifying unit notifies the device control server of the acquired device attribute value.
Control infrastructure server. The control infrastructure server according to any one of claims 1 to 6,
the device attribute value includes a priority threshold set for the control target device, a last-updated application ID that identifies application software executed by a device control server that generated a device control command including a control command instructing updating to the priority threshold, and a last-updated date and time that indicates the date and time of the update;
Control infrastructure server. 8. A device control system comprising: a device attribute management server that manages device attribute values of the control target devices; a plurality of device control servers that generate device control commands including control commands for the control target devices; and the control infrastructure server according to any one of claims 1 to 7,
the device control server generates a device control command including a control command for changing a priority threshold set for the control-target device;
the device attribute management server has a device attribute value storage unit for storing device attribute values of the control target devices, and when receiving a device control command including a control command for changing the priority threshold set for the control target devices, updates information on the priority threshold set for the control target devices, which information is included in the device attribute values stored in the device attribute value storage unit;
Equipment control system. 9. The device control system according to claim 8,
the device control server generates a device control command including a control command for changing the priority threshold set for the control target device within a range of values not exceeding the application priority value set for the application software to be executed;
Equipment control system. The device control system according to claim 8 or 9, which relies on claim 5,
the device control server has a device status storage unit that stores information indicating a control status for each of the control target devices;
when the device control server receives the notification of the information on whether the device control command can be executed, the device control server updates the information indicating the control status stored in the device status storage unit for each of the control target devices.
Equipment control system. A method executed in a control infrastructure server communicably connected to a device attribute management server that manages device attribute values of control target devices and a plurality of device control servers that generate device control commands including control commands for the control target devices, comprising:
storing application priorities that indicate priorities of execution authority for the device control commands, set for each of the application software executed by the device control server;
receiving the device control command from the device control server;
acquiring a priority threshold set for the control target device from the device attribute management server;
comparing an application priority set for application software executed by the device control server that generated the received device control command with a priority threshold set for a control target device that is the target of the device control command, and determining whether the application priority is higher than the priority threshold;
and permitting a control command to be issued to the control target device by transmitting the device control command to the device attribute management server only when the application priority is higher than the priority threshold as a result of the comparison and determination.
method. a control infrastructure server communicably connected to a device attribute management server that manages device attribute values of control target devices and a plurality of device control servers that generate device control commands including control commands for the control target devices;
a means for storing application priority levels set for each application software executed by the device control server, the application priority levels indicating the priority levels of execution authority for the device control commands;
means for receiving the device control command from the device control server;
means for acquiring a priority threshold set for the control target device from the device attribute management server;
means for comparing an application priority set for application software executed by a device control server that generated the received device control command with a priority threshold set for a control target device that is the target of the device control command, and determining whether the application priority is higher than the priority threshold;
and causing the device attribute management server to function as a means for permitting a control command to be issued to a control target device by transmitting the device control command to the device attribute management server only when the application priority is higher than the priority threshold as a result of the comparison and determination.
program.