Interoperable system and interoperable control method

Abstract

To easily implement the cooperation between two systems whose device representations to be used in cooperation-requiring commands are different from each other.SOLUTION: A first system includes at least one first computer that manages a plurality of first devices, and a first model that defines a relation between the at least one first computer and the plurality of first devices. A second system includes at least one second computer that manages a plurality of second devices, and a second model that defines a relation between the at least one second computer and the plurality of second devices. The at least one first computer obtains the second model from the second system, and updates the first model by integrating the obtained second model with the first model. When the at least one first computer cooperates with the second system, it writes a command according to the definition in the updated first model, and transmits the command to the at least one second computer.SELECTED DRAWING: Figure 2

Description

Technical Field

[0001] The present disclosure relates to a cooperation system and a cooperation control method for cooperating a plurality of systems.

Background Art

[0002] Japanese Patent Application Laid-Open No. 2021-152860 (Patent Document 1) discloses a cooperation system in a building environment including a building management system used by a building manager for building management and a general IoT (Internet of Things) environment provided for general users.

[0003] This cooperation system includes a cooperation control device that executes cooperation control so that cooperation of a predetermined function is realized among a group of devices including a facility-responsive device provided in the building management system and a device in the general IoT environment. As an aspect of application cooperation between the device of the building management system and the device of the general IoT environment, application cooperation is possible in which a cooperation command transmitted from the device of the building management system is used as a trigger, and the device of the building management system and one or more predetermined devices in the general IoT environment are cooperation destinations.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] When two systems are cooperating, a command for requesting cooperation is transmitted from one system to the other system, and the other system that has received the command executes processing according to the command. In this way, cooperation between the two systems is performed.

[0006] However, when different vendors are responsible for the development, construction, and operation of two systems, the representations of devices used in commands requesting cooperation (e.g., ID (identifier), device name, network address, and function name) may differ between the two systems. As a result, when one system sends a command specifying a target device to the other system, the receiving system may not be able to interpret the representation used in the command, and consequently, may not be able to execute the processing according to the command.

[0007] This disclosure has been made in view of the above-mentioned problems, and its purpose is to provide a cooperation system and a cooperation control method that can easily realize cooperation between two systems in which the device representations used in commands requesting cooperation are different from each other. [Means for solving the problem]

[0008] According to one aspect of this disclosure, the cooperative system comprises a first system and a second system that cooperates with the first system to manage the managed objects. The managed objects include a plurality of first devices and a plurality of second devices. The first system includes at least one first computer that is communicated to and manages the plurality of first devices, and a first model that defines the relationships between the at least one first computer and the plurality of first devices. The second system includes at least one second computer that is communicated to and manages a plurality of second devices, and a second model that defines the relationships between the at least one second computer and the plurality of second devices. The at least one first computer updates the first model by obtaining the second model from the second system and integrating the obtained second model with the first model. When cooperating with the second system, the at least one first computer writes commands according to the definitions in the updated first model and sends the commands to the at least one second computer.

[0009] Another aspect of this disclosure relates to a coordinated control method for managing a managed object in cooperation with a first system and a second system. The managed object includes a plurality of first devices and a plurality of second devices. The first system includes at least one first computer that is communicated to and manages the plurality of first devices, and a first model that defines the relationships between the at least one first computer and the plurality of first devices. The second system includes at least one second computer that is communicated to and manages a plurality of second devices, and a second model that defines the relationships between the at least one second computer and the plurality of second devices. The coordinated control method includes the steps of: at least one first computer updating the first model by obtaining the second model from the second system and integrating the obtained second model with the first model; and when the first system cooperates with the second system, at least one first computer writing a command according to the definition in the updated first model and sending the command to at least one second computer. [Effects of the Invention]

[0010] According to this disclosure, it is possible to easily achieve cooperation between multiple systems that use different device representations for commands requesting cooperation. [Brief explanation of the drawing]

[0011] [Figure 1] This diagram schematically shows an example of a building management system to which the collaborative system according to Embodiment 1 is applied. [Figure 2] This block diagram shows an example of the functional configuration of a central monitoring system and a lighting system. [Figure 3] This figure shows an example of a vocabulary list in a central monitoring system. [Figure 4] This figure shows an example of a vocabulary list for lighting systems. [Figure 5] This figure shows an example of a common model defining a central monitoring system. [Figure 6]It is a diagram showing an example of a common model that defines a lighting system. [Figure 7] It is a diagram explaining the flow of processing in the common model exchange section. [Figure 8] It is a diagram showing an example of the common model after combination in the central monitoring system. [Figure 9] It is a diagram explaining an example of processing in the cooperation request section and the cooperation response section. [Figure 10] It is a diagram explaining another example of processing in the cooperation request section and the cooperation response section. [Figure 11] It is a diagram showing an example of a common model that defines a central monitoring system. [Figure 12] It is a diagram showing an example of a common model that defines a lighting system. [Figure 13] It is a diagram showing an example of the common model after combination in the central monitoring system. [Figure 14] It is a diagram explaining an example of processing in the cooperation request section and the cooperation response section. [Figure 15] It is a diagram explaining another example of processing in the cooperation request section and the cooperation response section.

Mode for Carrying Out the Invention

[0012] Embodiments of the present disclosure will be described in detail with reference to the drawings. For the same or corresponding parts in the drawings, the same reference numerals are given and the description thereof will not be repeated.

[0013] Embodiment 1. <Application Example of the Cooperation System> FIG. 1 is a diagram schematically showing an example of a building management system to which the cooperation system according to Embodiment 1 is applied. As shown in FIG. 1, the building management system is a system for managing a plurality of devices (facility devices and measurement devices) installed in a building to be managed. The building management system includes a central monitoring system 100, a lighting system 200, and a network 300. The cooperation system according to the present embodiment realizes the cooperation between the central monitoring system 100 and the lighting system 200.

[0014] The central monitoring system 100 is a system for monitoring and controlling the operating states of the equipment installed in the building, and includes a management server 110, an air-conditioning controller 120, a power measurement controller 130, a plurality of temperature sensors 140_1 to 140_4, an indoor unit 150, and a power meter 160. The central monitoring system 100 corresponds to an embodiment of the "first system".

[0015] The management server 110 is connected to the network 300. The network 300 is a communication medium that realizes communication conforming to, for example, the BACnet (Building Automation and Control Networking) protocol. The management server 110 is a central monitoring device for managing and monitoring the state of the BACnet system, called, for example, B-OWS (BACnet Operator Workstation).

[0016] The air-conditioning controller 120 and the power measurement controller 130 are controllers that provide the input / output of the BACnet system as the lower side of the BACnet system, called, for example, B-BC (BACnet Building Controller). The management server 110, the air-conditioning controller 120, and the power measurement controller 130 correspond to an embodiment of "at least one first computer".

[0017] The air-conditioning controller 120 is connected to the management server 110 via the network 300. The indoor unit 150 and the temperature sensors 140_1 to 140_3 are installed in the building. The air-conditioning controller 120 is communicably connected to the temperature sensors 140_1 to 140_3 and the indoor unit 150, manages the measured values of the temperature sensors 140_1 to 140_3, and controls the operation of the indoor unit 150.

[0018] The power measurement controller 130 is connected to the management server 110 via the network 300. The electricity meter 160 is installed inside the building. The power measurement controller 130 is connected to the electricity meter 160 in a communication manner and manages the measured values ​​of the electricity meter 160.

[0019] The management server 110 receives data from the air conditioning controller 120 regarding the measured values ​​of temperature sensors 140_1 to 140_4. The management server 110 also receives data from the power measurement controller 130 regarding the measured values ​​of the energy meter 160. Based on this received data, the management server 110 generates a control command to control the operation of the indoor unit 150 and transmits the generated control command to the air conditioning controller 120. The air conditioning controller 120 controls the operation of the indoor unit 150 according to the control command from the management server 110. The multiple temperature sensors 140_1 to 140_4, the indoor unit 150, and the energy meter 160 correspond to one embodiment of "multiple first devices".

[0020] The lighting system 200 is a system for monitoring and controlling the operating status of lighting fixtures installed in a building, and includes a management server 210, a lighting controller 220, an illuminance sensor 230, and lighting fixtures 240. The lighting system 200 corresponds to one embodiment of the "second system".

[0021] The management server 210 is connected to the network 300. The management server 210 is, for example, a central monitoring device called B-OWS.

[0022] The lighting controller 220 is connected to the management server 210 via the network 300. The management server 210 and the lighting controller 220 correspond to one embodiment of "at least one second controller".

[0023] The illuminance sensor 230 and lighting fixture 240 are installed inside the building. The lighting controller 220 is communicatively connected to the illuminance sensor 230 and lighting fixture 240, managing the measured values ​​of the illuminance sensor 230 and controlling the operation of the lighting fixture 240.

[0024] The management server 210 receives data from the lighting controller 220 regarding the measured values ​​of the illuminance sensor 230. Based on the received data, the management server 210 generates a control command to control the operation of the lighting fixture 240 and transmits the generated control command to the lighting controller 220. The lighting controller 220 controls the operation of the lighting fixture 240 according to the control command from the management server 210. The illuminance sensor 230 and the lighting fixture 240 correspond to one embodiment of "multiple second devices".

[0025] In the building management system shown in Figure 1, the indoor unit 150 and lighting fixture 240 correspond to one embodiment of "equipment" installed in the building, and the temperature sensors 140_1 to 140_4, the energy meter 160, and the illuminance sensor 230 correspond to one embodiment of "measuring instruments" installed in the building. The equipment installed in the building is not limited to these and may also include air conditioning equipment other than indoor units, elevators, water supply and drainage equipment, sanitary equipment, disaster prevention equipment, and security equipment. Similarly, the measuring instruments are not limited to these and may also include surveillance cameras, surveillance monitors, etc. Furthermore, a controller for managing these equipment and measuring instruments may be connected to the management server 110 or management server 210 via the network 300.

[0026] <Hardware configuration of the management server and controller> In the building management system shown in Figure 1, the management server 110, air conditioning controller 120, power measurement controller 130, and lighting controller 220 are primarily computer-based.

[0027] The management server 110 includes a CPU (Central Processing Unit) 101, RAM (Random Access Memory) 102, ROM (Read Only Memory) 103, a communication interface 104, and a storage device 105. These are connected to each other via a bus so that they can communicate with one another.

[0028] The CPU 101 implements various functions of the management server 110 by loading programs stored in the ROM 103 into the RAM 102 and executing them. The ROM 103 stores programs that describe the processing procedures of the management server 110.

[0029] RAM102 serves as the workspace for the CPU101 when executing programs, and temporarily stores the program and data used to execute it.

[0030] The storage device 105 is a storage device that stores various types of information, including information on equipment and measuring instruments installed within the building. The storage device 105 also stores a common model for the central monitoring system 100. The common model will be explained in detail later. The storage device is, for example, an HDD (Hard Disk Drive) or an SSD (Solid State Drive).

[0031] The management server 110 exchanges signals and data with the air conditioning controller 120 and the power measurement controller 130 via the communication interface 104. Furthermore, when linking the central monitoring system 100 with the lighting system 200, the management server 110 exchanges signals and data with the lighting system 200's management server 210 via the communication interface 101.

[0032] Although not shown in the diagram, the management server 210 has a similar configuration to the management server 110.

[0033] The air conditioning controller 120 includes a CPU 121, RAM 122, ROM 123, communication IF 124, and I / O (input / output) interface 125. These are connected to each other via a bus so that they can communicate with one another.

[0034] The CPU 121 implements various functions of the air conditioning controller 120 by loading the program stored in the ROM 123 into the RAM 122 and executing it. The ROM 123 stores a program that describes the processing procedures of the air conditioning controller 120.

[0035] RAM 122 serves as a workspace for the CPU 121 when executing programs, and temporarily stores programs and data used during program execution. The air conditioning controller 120 may also be equipped with a non-volatile storage device, such as an HDD or SSD.

[0036] The air conditioning controller 120 communicates with the management server 110 via the communication interface 124. The air conditioning controller 120 receives data from temperature sensors 140_1 to 140_4 via the I / O interface 125. The air conditioning controller 120 outputs control signals to the indoor unit 150 via the I / O interface 125 to control the operation of the indoor unit 150.

[0037] Although not shown in the diagram, the power measurement controller 130 and the lighting controller 220 have a similar configuration to the air conditioning controller 120.

[0038] <Functional Configuration of the Integrated System> The collaborative system according to this embodiment is a system for realizing the collaboration between the central monitoring system 100 and the lighting system 200 in the building management system shown in Figure 1. By having the central monitoring system 100 and the lighting system 200 work together to comprehensively manage multiple pieces of equipment within the building (such as indoor units 150 and lighting fixtures 240), it is possible to operate multiple pieces of equipment efficiently and realize a comfortable living environment.

[0039] When linking these two systems, a command requesting the link is sent from one system to the other. This command may be, for example, a command requesting measurement data from measuring instruments included in the other system, or a command specifying the setting values ​​of equipment included in the other system.

[0040] The other system, upon receiving a command, executes the process according to the command. For example, the other system sends data of the measured values ​​of the measuring instrument specified in the command to the first system. Alternatively, the other system operates equipment according to the settings specified in the command. This is how the two systems cooperate.

[0041] However, if the vendors responsible for the development, construction, and operation of the central monitoring system 100 and the lighting system 200 are different, the representations of equipment and measuring instruments used in commands (e.g., ID (identifier), equipment name, network address, and function name) may differ between them. As a result, when one system sends a command specifying a target piece of equipment or measuring instrument to the other system, the receiving system may not be able to interpret the representation used in the command, and consequently, may not be able to perform the processing according to the command.

[0042] To solve these problems, the collaborative system according to this embodiment is configured such that each system defines a common model that represents the devices under its management, and exchanges this common model in advance with the system it collaborates with.

[0043] In the above configuration, each system, upon receiving a common model from a partner system, updates its own common model by integrating it with the partner system's common model. When coordinating with a partner system, it writes commands according to the definitions in the updated common model and sends the commands to the partner system. The partner system, upon receiving the commands, can interpret them by referring to its updated common model. As a result, it can execute processing according to the interpreted commands.

[0044] Figure 2 is a block diagram showing an example of the functional configuration of the central monitoring system 100 and the lighting system 200. Figure 2 shows the functional configuration of the parts related to the coordination processing in each of the central monitoring system 100 and the lighting system 200. This functional configuration is the same for both the central monitoring system 100 and the lighting system 200. This functional configuration is realized by the execution of programs by the management server 110 of the central monitoring system 100 and the management server 210 of the lighting system 200.

[0045] As shown in Figure 2, each of the central monitoring system 100 and the lighting system 200 includes a common model storage unit 10, a common model exchange unit 20, a cooperation request unit 30, a cooperation response unit 40, and a communication IF unit 50. Below, the configuration of each unit will be described assuming a case where a command requesting cooperation is sent from the central monitoring system 100 to the lighting system 200.

[0046] (Common model storage unit 10) The common model storage unit 10 stores common models within its own system. In this specification, a "common model" defines the relationships between at least one computer and multiple devices. Common models are generated, for example, by vendors responsible for the development, construction, and operation of the system.

[0047] In certain situations, object definitions in BACnet can be used in a common model. BACnet is an open communication protocol standard for building networks and is widely used as a communication standard for integrated monitoring, control, security, and maintenance of various equipment within a building. BACnet defines services used for communication between various devices, and objects that operate using those services. An object is information about the input / output and internal state of a BACnet-compatible device. An object is composed of various properties (attributes). Specifically, objects are defined for each signal and function, such as analog input, analog output, digital input, digital output, cumulative value, and schedule.

[0048] In another context, a common model can utilize ontology definitions such as Brick Schema. Brick Schema is a unified metadata schema for buildings, an open specification that semantically represents the physical, logical, and virtual assets within a building, as well as their relationships. An ontology describes how the target world is perceived (conceptualized).

[0049] In another context, building drawing definitions such as BIM (Building Information Modeling) can be used in a common model. BIM is a modeling method for information about buildings, and it is a comprehensive database of buildings, including their shape.

[0050] For example, when using ontology definitions in a common model, a vocabulary list is first defined for each system, containing the terminology used within the managed building. This vocabulary list includes terms and their meanings that represent the management server, controller, equipment, and measuring instruments shown in Figure 1. The meaning of each term is explained in the language used to exchange commands and data within that system.

[0051] Figure 3 shows an example of a vocabulary list in the central monitoring system 100. For example, if commands and data within the central monitoring system 100 are written in Japanese, the meaning of each term in the vocabulary list will be written in Japanese. For example, the first line of the vocabulary list indicates that "B-OWS" means "management server". The second line of the vocabulary list indicates that "B-BC" means "controller".

[0052] Figure 4 shows an example of a vocabulary list in the lighting system 200. For example, if commands and data within the lighting system 200 are written in English, the vocabulary list will show the meaning of each term in English. For example, the first line of the vocabulary list indicates that "B-OWS" means "management server." The second line of the vocabulary list indicates that "B-BC" means "controller."

[0053] Once the vocabulary list is defined, a common model is generated that represents the relationships between at least one computer and multiple devices included in the system. In the common model, the terms defined in the vocabulary list are used to represent each computer and each device. In the common model, the relationships between at least one computer and multiple devices are represented in a hierarchical structure. The common model may, for example, have a tree structure, but is not limited to that. A common model is generated for each system and stored in the management server's storage device 105 (Figure 1).

[0054] Figure 5 shows an example of a common model defining the central monitoring system 100. As shown in Figure 5(A), in the common model, the relationships between the management server 110, the air conditioning controller 120 and the power measurement controller 130, the indoor unit 150, the temperature sensors 140_1 to 140_4 and the energy meter 160 are described in a tree structure using terms defined in the vocabulary list (Figure 3). The common model shown in Figure 5(A) corresponds to one embodiment of the "first model".

[0055] Specifically, by connecting "B-BC" to "B-OWS" via "Management," the relationship "B-OWS manages B-BC" is expressed. Furthermore, by connecting "T-Sensor" to "B-BC" via "AI," the relationship "T-Sensor is the AI ​​of B-BC" is expressed. By connecting "PAC-IC" to "B-BC" via "DO," the relationship "PAC-IC is the DO of B-BC" is expressed. Finally, by connecting "P-Meter" to "B-BC" via "PI," the relationship "P-Meter is the PI of B-BC" is expressed.

[0056] Figure 5(B) is a table representation of the common model shown in Figure 5(A). In the table, the relationship between each element of the common model and the other elements is described. Note that "Management (X)" is a word that means managing X. "AI (X)" is a word that means having an analog input from X. "AO (X)" is a word that means having an analog output to X. "DO (X)" is a word that means having a digital output to X. "PI (X)" is a word that means having a pulse input from X. The common model shown in Figure 5(A) is stored in the common model storage unit 10 of the central monitoring system 100.

[0057] Figure 6 shows an example of a common model defining the lighting system 200. As shown in Figure 6(A), in the common model, the relationships between the management server 210, the lighting controller 220, the illuminance sensor 230, and the lighting fixtures 240 are described in a tree structure using terms defined in the vocabulary list (Figure 4). The common model shown in Figure 6(A) corresponds to one embodiment of the "second model".

[0058] Specifically, by connecting "B-BC" to "B-OWS" via "Management," the relationship "B-OWS manages B-BC" is expressed. Furthermore, by connecting "I-Sensor" to "B-BC" via "AI," the relationship "I-Sensor is the AI ​​of B-BC" is expressed. Finally, by connecting "Lighting" to "B-BC" via "AO," the relationship "Lighting is the AO of B-BC" is expressed.

[0059] Figure 6(B) shows the common model shown in Figure 6(A) represented in a table. The table describes the relationship between each element of the common model and the other elements. The common model shown in Figure 6(A) is stored in the common model storage unit 10 of the lighting system 200.

[0060] (Common model exchange section 20) Returning to Figure 2, the common model exchange unit 20 exchanges common models with the partner system. When the common model exchange unit 20 receives the common model from the partner system, it updates its own common model by integrating the common model of its own system stored in the common model storage unit 10 with the common model of the partner system.

[0061] Specifically, the common model exchange unit 20 includes an acquisition unit 21, a transmission unit 22, a reception unit 23, an extraction unit 24, a merging unit 25, and an update unit 26.

[0062] The acquisition unit 21 acquires the common model of its own system from the common model storage unit 10.

[0063] The transmitting unit 22 transmits the common model of its own system, acquired by the acquisition unit 21, to the partner system via the communication IF unit 50.

[0064] The receiving unit 23 receives the common model of the system to be linked via the communication IF unit 50.

[0065] The extraction unit 24 receives the common model of its own system from the acquisition unit 21 and the common model of the system to be linked from the receiving unit 23. The extraction unit 24 compares the common model of its own system with the common model of the system to be linked. The extraction unit 24 extracts elements that exist in the common model of the system to be linked but do not exist in the common model of its own system.

[0066] The coupling unit 25 integrates its own system's common model with the common model of the linked system by combining the elements extracted by the extraction unit 24 with the common model of its own system.

[0067] The update unit 26 updates the common model stored in the common model storage unit 10 based on the common model of its own system after integration.

[0068] Figure 7 illustrates the processing flow in the common model exchange unit 20. Figure 7 shows the processing flow in the common model exchange unit 20 of the central monitoring system 100. Therefore, the common model of the central monitoring system 100 shown in the upper left of Figure 7 corresponds to the "common model of its own system." Similarly, the common model of the lighting system 200 shown in the upper right of Figure 7 corresponds to the "common model of the system to which it is linked." Both common models are represented as tables.

[0069] In the common model exchange unit 20 of the central monitoring system 100, the extraction unit 24 extracts "I-Sensor" and "Lighting" as elements that exist in the common model of the lighting system 200 but not in the common model of the central monitoring system 100.

[0070] The coupling unit 25 combines the extracted elements into a common model of the central monitoring system 100. Specifically, based on the relationship that "I-Sensor is the AI ​​of B-BC," "I-Sensor" is connected to "B-BC" as "AI." Based on the relationship that "Lighting is the AO of B-BC," "Lighting" is connected to "B-BC" as "AO."

[0071] Figure 8 shows an example of a combined common model in the central monitoring system 100. As shown in Figure 8, an I-Sensor and Lighting are newly connected to B-BC. The combined common model is stored in the common model storage unit 10 by the update unit 26. In this way, the common model of the central monitoring system 100 is updated.

[0072] Although not shown in the diagram, the same process as in Figure 7 is performed in the common model exchange unit 20 of the lighting system 200. That is, the common model of the lighting system 200 is updated by integrating the common model of the lighting system 200 with the common model of the central monitoring system 100.

[0073] (Linkage request unit 30) Returning to Figure 2, the cooperation request unit 30 sends a command to the system to which it will be cooperating, requesting cooperation. When sending a command to the lighting system 200 from the central monitoring system 100, the cooperation request unit 30 of the central monitoring system 100 writes the command according to the definition in the common model stored in the common model storage unit 10, and sends the generated command to the lighting system 200.

[0074] Specifically, the cooperation request unit 30 includes a cooperation processing determination unit 31, a common model acquisition unit 32 for transmission, a common model mapping processing unit 33, a request command transmission unit 34, and a request command response reception unit 35.

[0075] The coordinating processing determination unit 31 determines the processing to be performed in cooperation with the lighting system 200 and generates a command to request the determined processing from the lighting system 200. Specifically, when the central monitoring system 100 controls the lighting fixtures 240 in cooperation with the lighting system 200, the coordinating processing determination unit 31 generates a command to request the lighting system 200 to provide the measured value of the illuminance sensor 230. Alternatively, the coordinating processing determination unit 31 generates a command to set the illuminance of the lighting fixtures 240 from the lighting system 200.

[0076] The transmission-time common model acquisition unit 32 acquires the common model from the common model storage unit 10. The common model is the one that has been updated by the common model exchange unit 20.

[0077] The common model mapping processing unit 33 converts the command generated by the linkage processing determination unit 31 into a command that the lighting system 200 can interpret by associating the terms used in the command with their definitions in the common model (Figure 8).

[0078] As an example, let's assume that the cooperation processing decision unit 31 generates a command "Get measured values ​​from the illuminance sensor" which requests the measured values ​​from the illuminance sensor 230, as shown in Figure 9.

[0079] In this case, the common model mapping processing unit 33 uses the relationships defined in the common model, namely "I-Sensor is the AI ​​of B-BC" and "B-OWS manages B-BC," to execute the command "GET http: / / <ip-address>This command is converted to " / b-ows / b-bc / i-sensor HTTP / 1.1". <ip-address> / b-ows / b-bc / i-sensor represents the location of the illuminance sensor 230 in the lighting system 200. The command is written according to the relationships between B-OWS, B-BC, and I-Sensor as defined in the common model.

[0080] As another example, consider the case shown in Figure 10 where the cooperation processing decision unit 31 generates a command, "Set the illuminance of the lighting fixture to 80lx," which sets the illuminance of the lighting fixture 240 to a predetermined value (for example, 80lx).

[0081] In this case, the common model mapping processing unit 33 uses the relationships defined in the common model, "Lighting is the AO of B-BC" and "B-OWS manages B-BC," to perform the command "POST http: / / <ip-address>This command is converted to " / b-ows / b-bc / lighting HTTP / 1.1 {"value":80}". <ip-address> / b-ows / b-bc / lighting indicates the location of the luminaire 240 in the lighting system 200. The command is written according to the relationship between B-OWS, B-BC, and Lighting as defined in the common model.

[0082] The request command transmission unit 34 sends the command generated by the common model mapping processing unit 33 to the management server 210 of the lighting system 200 via the communication interface unit 50.

[0083] The request command response receiving unit 35 receives a response to the transmitted command from the request command response transmitting unit 45 of the lighting system 200.

[0084] (Responding unit 40) Returning to Figure 2, the cooperation response unit 40 receives a command requesting cooperation from the system that will be the source of the cooperation. When a command requesting cooperation is sent from the cooperation request unit 30 of the central monitoring system 100 to the lighting system 200, the cooperation response unit 40 of the lighting system 200 receives the command. The cooperation response unit 40 interprets the command by referring to the common model stored in the common model storage unit 10 and manages the illuminance sensor 230 and lighting fixture 240 according to the interpreted command.

[0085] Specifically, the cooperation response unit 40 includes a cooperation processing receiving unit 41, a common model acquisition unit 42 at reception, a conversion processing unit 43, a request command execution unit 44, and a request command response transmission unit 45.

[0086] The collaborative processing receiving unit 41 receives commands from the central monitoring system 100 via the communication interface unit 50.

[0087] The receiving common model acquisition unit 42 acquires the common model from the common model storage unit 10. The common model is the one that has been updated by the common model exchange unit 20.

[0088] The conversion processing unit 43 refers to a common model and converts the terminology used in the command to the terminology used within its own system. For example, as shown in Figure 8, "GET http: / / <ip-address>When the command " / b-ows / b-bc / i-sensor HTTP / 1.1" is received, the conversion processing unit 43 interprets that "i-sensor" is "the illumination sensor" and that the command means "get the analog input from the illumination sensor," based on the relationship defined in the common model: "I-Sensor is the AI ​​of B-BC" and "B-OWS manages B-BC." Therefore, the conversion processing unit 43 converts the command into the command "get the measured value of the illuminance sensor."

[0089] As another example, as shown in Figure 9, "POST http: / / <ip-address>When the command " / b-ows / b-bc / lighting HTTP / 1.1 {"value":80}" is received, the conversion processing unit 43 interprets "lighting" as "the lighting equipment" and the command as meaning "set the analog output to the lighting equipment to 80," based on the relationship defined in the common model that "Lighting is the AO of B-BC" and "B-OWS manages B-BC." Therefore, the conversion processing unit 43 converts the command into the command "set the illumination of the lighting equipment to 80."

[0090] Returning to Figure 2, the request command execution unit 44 manages the illuminance sensor 230 and the lighting fixture 240 according to the command converted by the conversion processing unit 43. Specifically, the request command execution unit 44 obtains the measured value of the illuminance sensor 230 according to the command "get the measured value of the illuminance sensor". Alternatively, the request command execution unit 44 sets the illuminance of the lighting fixture 240 to 80 lx according to the command "set the illumination of the lighting equipment to 80", and controls the operation of the lighting fixture 240 to achieve the set illuminance.

[0091] The request command response transmission unit 45 transmits a response to the received command to the source system via the communication IF unit 50. Specifically, the request command response transmission unit 45 transmits the measured value of the illuminance sensor 230, acquired according to the command "get the measured value of the illuminance sensor," to the central monitoring system 100.

[0092] Alternatively, the request command response transmission unit 45 transmits information to the central monitoring system 100 that the illuminance of the lighting equipment 240 has been set according to the command "set the illumination of the lighting equipment to 80".

[0093] The request command response receiving unit 35 of the central monitoring system 100 receives a response from the request command response transmitting unit 45 of the lighting system 200 via the communication IF unit 50.

[0094] Although not shown in the diagram, when the lighting system 200 requests coordination from the central monitoring system 100, the coordination request unit 30 of the lighting system 200 sends a command to the central monitoring system 100 requesting coordination. At this time, the coordination request unit 30 converts the command into a command that the central monitoring system 100 can interpret by associating the terms used in the command with their definitions in the common model.

[0095] Then, when the central monitoring system 100's coordinate response unit 40 receives a command from the lighting system 200, it interprets the command by referring to a common model and manages the indoor unit 150, temperature sensors 140_1 to 140_4, and power meter 160 according to the command. The coordinate response unit 40 then sends a response to the received command to the lighting system 200.

[0096] As described above, according to the collaborative system of Embodiment 1, each system defines a common model that represents the relationships between at least one computer and multiple devices within its own system, and exchanges this common model with the system to be collaborated with in advance. In a scenario where the first system and the second system collaborate, the first system can generate a command requesting collaboration with the second system in association with the common model, and send the generated command to the second system. The second system can then interpret the command received from the first system by referring to the common model and execute processing according to the command. As a result, even if the command representations differ between the first and second systems, each system can understand the device indicated by the command from the other system, the connection relationship between that device and other devices, and the processing content requested.

[0097] Embodiment 2. Embodiment 1 describes a configuration in which a common model is generated that defines the relationships between multiple devices included in each system using an ontology, and this model is exchanged in advance between multiple systems.

[0098] Embodiment 2 describes a configuration in which a common model is generated by adding system-specific network information (instances) to the ontology, and this model is exchanged in advance between multiple systems. Note that the configuration of the collaborative system in Embodiment 2 is the same as the collaborative system in Embodiment 1 (Figures 1 and 2), except for the configuration of the common model, so the explanation will be omitted.

[0099] (Common model) Figure 11 shows an example of a common model defining the central monitoring system 100. As shown in Figure 11(A), in the common model, the relationships between the management server 110, the air conditioning controller 120 and the power measurement controller 130, the indoor unit 150, the temperature sensors 140_1 to 140_4 and the power meter 160 are described in a tree structure using terms defined in the vocabulary list (Figure 3).

[0100] The common model shown in Figure 11(A) differs from the common model shown in Figure 5(A) in that it includes information describing the network configuration of each element. As shown in Figure 1, the central monitoring system 100 consists of one management server 110, two controllers 120 and 130, four temperature sensors 140_1 to 140_4, one indoor unit 150, and one power meter 160. In the common model, an ontology is used to describe the connections between these devices.

[0101] Specifically, in the common model, the management server 110 is labeled "B-OWS1," and the two controllers 120 and 130 are labeled "B-BC1" and "B-BC2," respectively. The four temperature sensors 140_1 to 14_4 are labeled "T-Sensor1," "T-Sensor2," "T-Sensor3," and "T-Sensor4," respectively. The indoor unit 150 is labeled "PAC-IC1," and the energy meter 160 is labeled "P-Meter1."

[0102] Furthermore, by connecting "B-BC1" and "B-BC2" to "B-OWS1" via "Management," the relationship "B-OWS1 manages B-BC1 and B-BC2" is expressed. Additionally, by connecting "T-Sensor1," "T-Sensor2," and "T-Sensor3" to "B-BC1" via "AI," the relationship "T-Sensor1, T-Sensor2, and T-Sensor3 are the AI ​​of B-BC1" is expressed. By connecting "PAC-IC1" to "B-BC1" via "DO," the relationship "PAC-IC1 is the DO of B-BC1" is expressed. By connecting "P-Meter1" to "B-BC2" via "PI," the relationship "P-Meter1 is the PI of B-BC2" is expressed.

[0103] Figure 11(B) shows the common model shown in Figure 11(A) represented in a table. In the table, the relationships between each element of the common model are described. The common model is stored in the common model storage unit 10 of the central monitoring system 100.

[0104] Figure 12 shows an example of a common model defining the lighting system 200. As shown in Figure 12(A), in the common model, the relationships between the management server 210, the lighting controller 220, the illuminance sensor 230, and the lighting fixtures 240 are described in a tree structure using terms defined in the vocabulary list (Figure 4).

[0105] The common model shown in Figure 12(A) differs from the common model shown in Figure 6(A) in that it includes information indicating the network configuration of each element. Specifically, in the common model, the management server 210 is labeled "B-OWS2", the lighting controller 220 is labeled "B-BC3", the illuminance sensor 230 is labeled "I-Sensor1", and the lighting fixture 240 is labeled "Lighting1". By connecting "B-BC3" to "B-OWS2" as "management", the relationship "B-OWS2 manages B-BC3" is expressed. Furthermore, by connecting "I-Sensor1" to "B-BC3" as "AI", the relationship "I-Sensor1 is the AI ​​of B-BC3" is expressed. By connecting "Lighting1" to "B-BC3" as "AO", the relationship "Lighting1 is the AO of B-BC3" is expressed.

[0106] Figure 12(B) shows a table representation of the common model shown in Figure 12(A). The table describes the relationships between each element of the common model and the other elements. The common model is stored in the common model storage unit 10 of the lighting system 200.

[0107] Thus, a common model systematically connects multiple devices that constitute a single system and corresponds to a network of knowledge (knowledge graph) represented in a graph structure. Because an ontology is used, the representation of each device can be common regardless of the system.

[0108] The common model exchange unit 20 for each system exchanges common models with the system it is cooperating with. As shown in Figure 7, when the common model exchange unit 20 of the central monitoring system 100 receives a common model (Figure 12(A)) from the lighting system 200, it updates its own common model by integrating the common model of its own system (Figure 11(A)) stored in the common model storage unit 10 with the common model of the lighting system 200.

[0109] Figure 13 shows an example of a combined common model in the central monitoring system 100. As shown in Figure 13, the combined common model is formed by linking the common model shown in Figure 11(A) with the common model shown in Figure 12(A). According to the combined common model, the network of the linked system can be known. The combined common model is stored in the common model storage unit 10 by the update unit 26. In this way, the common model of the central monitoring system 100 is updated.

[0110] Although not shown in the diagram, the same process as in Figure 7 is performed in the common model exchange unit 20 of the lighting system 200. That is, the common model of the lighting system 200 is updated by integrating the common model of the lighting system 200 with the common model of the central monitoring system 100.

[0111] In Embodiment 2, as in Embodiment 1, the cooperation request unit 30 generates a command requesting cooperation using the common model stored in the common model storage unit 10, and transmits the generated command to the system to which the cooperation will take place. When the cooperation response unit 40 receives a command requesting cooperation from the system to which the cooperation will take place, it interprets the command by referring to the common model stored in the common model storage unit 10, and manages the equipment and measuring instruments according to the interpreted command. Therefore, the same effects as in Embodiment 1 can be obtained in Embodiment 2 as in Embodiment 1.

[0112] As an example, let's assume that, as shown in Figure 14, the central monitoring system 100's cooperation processing decision unit 31 generates a command, "Acquire measured values ​​from the illuminance sensor," which requests the measured values ​​from the illuminance sensor 230.

[0113] In this case, the common model mapping processing unit 33 uses the relationships defined in the common model (Figure 13), namely "I-Sensor1 is the AI ​​of B-BC3" and "B-OWS2 manages B-BC3," to execute the command "GET http: / / <ip-address>This command is converted to " / v1 / b-ows2 / b-bc3 / i-sensor1 HTTP / 1.1". <ip-address> / b-ows / v1 / b-ows2 / b-bc3 / i-sensor1 represents the location of the illuminance sensor 230 in the lighting system 200. The command is written according to the relationship between B-OWS2, B-BC3, and I-Sensor1 as defined in the common model.

[0114] As another example, consider the case shown in Figure 15, where the central monitoring system 100's linkage processing decision unit 31 generates a command, "Set the illuminance of the lighting fixture 240 to 80lx," which sets the illuminance of the lighting fixture 240 to a predetermined value (for example, 80lx).

[0115] In this case, the common model mapping processing unit 33 uses the relationships defined in the common model (Figure 13), namely "Lighting1 is the AO of B-BC3" and "B-OWS2 manages B-BC3," to execute the command "POST http: / / <ip-address>This command is converted to " / b-ows / v1 / b-ows2 / b-bc3 / lighting1 HTTP / 1.1 {"value":80}". <ip-address> / b-ows / v1 / b-ows2 / b-bc3 / lighting1 indicates the location of the luminaire 240 in the lighting system 200. The command is written according to the relationship between B-OWS2, B-BC3, and Lighting1 as defined in the common model.

[0116] Thus, in Embodiment 2, the cooperation request unit 30 of the central monitoring system 100 can send a command by specifying the equipment and measuring instruments of the lighting system 200 to be cooperated with. The cooperation response unit 40 of the lighting system 200 can immediately find out the equipment and measuring instruments specified by the received command by referring to a common model.

[0117] [Note] The embodiments described above are specific examples of the following appendix.

[0118] (Note 1) The first system and, The system comprises a first system and a second system that manages the managed objects in cooperation with the first system, The managed object includes a plurality of first devices and a plurality of second devices, The first system described above is A plurality of first devices are connected to a plurality of first devices by communication, and at least one first computer manages the plurality of first devices, The system includes a first model that defines the relationship between the at least one first computer and the plurality of first devices, The second system is A second computer that is connected to the plurality of second devices and manages the plurality of second devices, The system includes a second model that defines the relationship between the at least one second computer and the plurality of second devices, The aforementioned at least one first computer is The first model is updated by obtaining the second model from the second system and integrating the obtained second model with the first model. A cooperating system that, when cooperating with the second system, writes commands according to the definitions in the updated first model and sends the commands to the at least one second computer.

[0119] (Note 2) The aforementioned at least one second computer is The first model is obtained from the first system, and the second model is updated by integrating the obtained second model with the first model. The collaborative system described in Appendix 1, which, upon receiving the command from the first system, interprets the command by referring to the updated second model and manages the plurality of second devices in accordance with the interpreted command.

[0120] (Note 3) The aforementioned at least one first computer is Elements that are not present in the first model are extracted from the second model. The linkage system described in Appendix 1 or Appendix 2 updates the first model by combining the extracted elements with the first model.

[0121] (Note 4) The first model defines the relationship between the at least one first computer and the plurality of first devices using an ontology. The second model is a collaborative system according to any one of the appendices 1 to 3, which defines the relationship between the at least one second computer and the plurality of second devices using an ontology.

[0122] (Note 5) The first model includes first network information that defines the network configuration of the at least one first computer and the plurality of first devices using an ontology. The second model includes second network information that defines the network configuration of the at least one second computer and the plurality of second devices using an ontology. The aforementioned at least one first computer is The linked system described in Appendix 4 updates the first model by integrating the second network information in the second model obtained from the second system with the first network information in the first model.

[0123] (Note 6) The aforementioned at least one first computer is The integration system described in Appendix 5, which, when integrating with the second system, describes the command based on the updated second network information in the first model.

[0124] (Note 7) The first system and the second system are configured to cooperate with multiple devices installed within a building as the devices to be managed. The first model and the second model utilize object definitions in BACnet, ontology definitions in Brick Schema, or drawing definitions in BIM, as described in any one of the appendices 1 to 6.

[0125] (Note 8) A coordinated control method for managing managed objects by coordinating a first system and a second system, The managed object includes a plurality of first devices and a plurality of second devices, The first system described above is A plurality of first devices are connected to a plurality of first devices by communication, and at least one first computer manages the plurality of first devices, The system includes a first model that defines the relationship between the at least one first computer and the plurality of first devices, The second system is A second computer that is connected to the plurality of second devices and manages the plurality of second devices, The system includes a second model that defines the relationship between the at least one second computer and the plurality of second devices, The aforementioned coordinated control method is, The steps include: the at least one first computer obtaining the second model from the second system and updating the first model by integrating the obtained second model with the first model; A cooperation control method comprising the steps of: when the first system cooperates with the second system, the at least one first computer writes a command according to the definition in the updated first model and transmits the command to the at least one second computer.

[0126] (Note 9) The steps include: the at least one second computer obtaining the first model from the first system and updating the second model by integrating the obtained second model with the first model; The cooperative control method according to Appendix 8, further comprising the step of receiving the command from the first system, the at least one second computer interpreting the command with reference to the updated second model, and managing the plurality of second devices in accordance with the interpreted command.

[0127] While embodiments of this disclosure have been described, the embodiments disclosed herein should be considered in all respects to be illustrative and not restrictive. The scope of this disclosure is defined by the claims, and all modifications within the meaning and scope equivalent to the claims are intended. [Explanation of symbols]

[0128] 10 Common model storage unit, 20 Common model exchange unit, 21 Acquisition unit, 22 Transmission unit, 23 Reception unit, 24 Extraction unit, 25 Combination unit, 26 Update unit, 30 Cooperation request unit, 31 Cooperation processing determination unit, 32 Common model acquisition unit during transmission, 33 Common model mapping processing unit, 34 Request command transmission unit, 35 Request command response reception unit, 40 Cooperation response unit, 41 Cooperation processing reception unit, 42 Common model acquisition unit during reception, 43 Conversion processing unit, 44 Request command execution unit, 45 Request command response transmission unit, 50 Communication IF unit, 100 Central monitoring system, 101,121 CPU, 102,122 RAM, 103,123 ROM, 104,124 Communication IF, 105 Storage device, 110,210 Management server, 120 Air conditioning controller, 125 I / O, 130 Power measurement controller, 140_1~140_4; Temperature sensor, 150; Indoor unit, 160; Energy meter, 200; Lighting system, 220; Lighting controller, 230; Illuminance sensor, 240; Lighting fixture, 300; Network.

Claims

1. The first system and, The system comprises a first system and a second system that manages the managed objects in cooperation with the first system, The subject of control includes a plurality of first devices and a plurality of second devices. The first system is A plurality of first devices are connected to a plurality of first devices by communication, and at least one first computer manages the plurality of first devices, This includes a first model defined by representing the relationship between the at least one first computer and the plurality of first devices in a hierarchical structure, The second system is A second computer that is connected to the plurality of second devices and manages the plurality of second devices, This includes a second model defined by representing the relationship between the at least one second computer and the plurality of second devices in a hierarchical structure, The at least one first computer is The first model is updated by acquiring the second model from the second system and integrating the acquired second model with the first model. A cooperating system that, when cooperating with the second system, writes commands according to the definitions in the updated first model and transmits the commands to the at least one second computer.

2. The aforementioned at least one second computer is The first model is obtained from the first system, and the second model is updated by integrating the obtained first model and the second model. The cooperative system according to claim 1, which, upon receiving the command from the first system, interprets the command by referring to the updated second model and manages the plurality of second devices in accordance with the interpreted command.

3. The at least one first computer is Elements that are not present in the first model are extracted from the second model. The linkage system according to claim 1, which updates the first model by combining the extracted elements with the first model.

4. The first model defines the relationship between the at least one first computer and the plurality of first devices using an ontology. The second model is the collaborative system according to claim 1, wherein the relationship between the at least one second computer and the plurality of second devices is defined using an ontology.

5. The first model includes first network information that defines the network configuration of the at least one first computer and the plurality of first devices using an ontology. The second model includes second network information that defines the network configuration of the at least one second computer and the plurality of second devices using an ontology. The at least one first computer is The collaborative system according to claim 4, which updates the first model by integrating the second network information in the second model obtained from the second system with the first network information in the first model.

6. The at least one first computer is The collaboration system according to claim 5, wherein when collaborating with the second system, the command is described based on the updated second network information in the first model.

7. The first system and the second system are configured to cooperate with multiple devices installed within a building as the devices to be managed. The collaborative system according to claim 1, wherein the first model and the second model utilize object definitions in BACnet, ontology definitions in Brick Scheme, or drawing definitions in BIM.

8. A coordinated control method for managing managed objects by coordinating a first system and a second system, The subject of control includes a plurality of first devices and a plurality of second devices. The first system is A plurality of first devices are connected to a plurality of first devices by communication, and at least one first computer manages the plurality of first devices, The system includes a first model that defines the relationship between the at least one first computer and the plurality of first devices by representing it in a hierarchical structure, The second system is A second computer that is connected to the plurality of second devices and manages the plurality of second devices, This includes a second model that defines the relationship between the at least one second computer and the plurality of second devices by representing it in a hierarchical structure, The aforementioned coordinated control method is The steps include: the at least one first computer obtaining the second model from the second system and updating the first model by integrating the obtained second model with the first model; A cooperation control method comprising the steps of: when the first system cooperates with the second system, the at least one first computer writes a command according to the definition in the updated first model and transmits the command to the at least one second computer.

9. The steps include: the at least one second computer obtaining the first model from the first system and updating the second model by integrating the obtained first model and the second model; The cooperative control method according to claim 8, further comprising the step of receiving the command from the first system, the at least one second computer interpreting the command by referring to the updated second model, and managing the plurality of second devices in accordance with the interpreted command.

Images